Package Structure within the Webapp

This section shows how Design Studio package builder pulls the raw DSPackageInstaller.war artifact from the nexus repository. The following convention is used to embed a DS package within the webapp.

You need to create the following structure within the WAR file:

The content highlighted in yellow represents a standard DS package content, named R17_FT_Modelbank_1_JAVA_17.0. It should be extracted under a packages directory, which is available under WEB-INF.

A WAR file can contain multiple packages. Packages are referenced within the package-list file, which should be generated by DS package builder.

A package content is listed within the package-detail file, which should be generated by DS package builder.

Package-list File

The package-list contains the list of all packages, represented by their name, corresponding to the root directory level of the package.

Packages part of the package-list are visible for staging, and must be present under WEB-INF/packages. That is:

R17_FT_Modelbank_1_JAVA_17.0
R17_FT_Modelbank_1_JAVA_17.1

Package-detail File

The package-detail represents the list of files or package entries, which are visible for staging. Files not intended to be staged and part of a package, must not be part of this list. A package entry format is made of two parts separated with # sign.

technicalUniquePackageEntryKey#path/To/The/File/Within/The/Package

The first part is a technical key generated by DS package builder; it must be unique as it will be used as a primary key within the staging area. Since the record management will be handled differently by Temenos Transact based on its type, this type is also a part of the key. It can be built by using the following convention:

 package name + “-“ + sequence ID + “.” + file type

Re-using same key will lead to a record overwrite at staging time, in case of an existing key with same value is already defined in the staging area.

The second part after # sign is the path to the record from the package root directory. The file must exist under this path to be read by the installer. That is:

R17_FT_Modelbank_1_JAVA_17.0-9.xml#R17_FT_Modelbank_1_JAVA_17.0/ds-generated/PP.STANDING.ORDER.enquiry.xml
R17_FT_Modelbank_1_JAVA_17.0-10.eson#R17_FT_Modelbank_1_JAVA_17.0/Eson/CATEGORY!1001!GB0010001.eson
R17_FT_Modelbank_1_JAVA_17.0-11.event#R17_FT_Modelbank_1_JAVA_17.0/IF/ACCOUNT.event
R17_FT_Modelbank_1_JAVA_17.0-12.flow#R17_FT_Modelbank_1_JAVA_17.0/IF/ACCOUNT.flow
R17_FT_Modelbank_1_JAVA_17.0-13#R17_FT_Modelbank_1_JAVA_17.0/R17_FT_Modelbank_1
R17_FT_Modelbank_1_JAVA_17.0-14#R17_FT_Modelbank_1_JAVA_17.0/R18_IF_TestIF_1
R17_FT_Modelbank_1_JAVA_17.0-15.d#R17_FT_Modelbank_1_JAVA_17.0/REC001
R17_FT_Modelbank_1_JAVA_17.0-16.d#R17_FT_Modelbank_1_JAVA_17.0/REC002
R17_FT_Modelbank_1_JAVA_17.0-17.d#R17_FT_Modelbank_1_JAVA_17.0/REC003