Welcome Guest! Log in


A package is an archive containing all the needed files and folders to generate a delivery.
Most of the time, a package is generated by the development team when they have finished working on a Mapping / Process.
The package can then be used to generate the delivery that will be executed by the Runtimes.

To generate a package, there is two solutions:

  • Generate the package directly from Stambia Designer.
  • Generate the package from command line.

 

Generating a package from Stambia Designer

The most common way to generate the Package corresponding to a Mapping / Process is to do it from Stambia Designer.

The procedure for this is quite simple:

  1. Right click on the Mapping / Process
  2. From the menu, choose Build > Package [with documentation]

 

That’s all, you can now find the generated package under:

<Designer Installation>/stambiaRuntime/build/packages

Generating a package from command line

The other possibility is to generate the Package corresponding to a Mapping / Process from command line.

For this you’ll have to write a file containing the list of Packages to build, that will be specified on the command line tool.

The procedure is as follow:

  1. Create first a text file
  2. Add in the file the list of individual Packages or Launch Package Configurations to be built
  3. Use the command line utility to execute the script file

 

Prerequisites:

  • Stambia DI Designer S18.3.2 or higher

 

Preparing the script file

The first step is to prepare the script file listing the individual Packages or Launch Package Configurations to build.

Create a text file and add in a new line for each operation to perform.

 

Specifying individual Packages to build

If you want to build individual Packages you can process as follow.

You must add in the script a new line for each Package you want to build, with the following syntax:

build package "<PROCESS_PATH_WITHIN_WORKSPACE>" -target "<TARGET_DIRECTORY>"

 

Or if you want the Package with its documentation:

build packageWithDocumentation "<PROCESS_PATH_WITHIN_WORKSPACE>" -target "<TARGET_DIRECTORY>"

 

The following parameters are available:

Parameter Description
package | packageWithDocumentation <PATH_WITHIN_WORKSPACE>

Relative path within the workspace to the Process to build the package from.

If you want to generate the Package of a Mapping, specify the path of the Mapping’s built Process file (under indy.build folder)

Note:

The packageWithDocumentation mode requires a graphical UI on the machine where the generation is performed.

-target <TARGET_DIRECTORY> Target directory in which the generated package will be created.

 

Example of file script file:

build package "Tutorial - Fundamentals/Processes/Load All Datamart.proc" -target "D:/Packages/"
build package "My Project - 01/Process01.proc" -target "D:/Packages/"
build package "My Project - 01/indy.build/mymapping.proc" -target "D:/Packages/"
build packageWithDocumentation "My Project - 01/Process02.proc" -target "D:/Packages/"

 

Specifying a Launch Package Configuration to build

If you want to build Launch Package Configurations you can process as follow.

You must add in the script a new line for each Launch Package Configuration you want to build, with the following syntax:

launch <LAUNCH_PACKAGE_CONFIGURATION_NAME> [-conf confName]

 

The following parameters are available:

Parameter Description
launch <LAUNCH_PACKAGE_CONFIGURATION_NAME>

Name of the Launch Configuration to build.

The Launch Configuration Specification file must exist in the workspace on which the command will be performed.

 

Example of file script:

launch "Tutorial Launch 01"
launch "Tutorial Launch 02"

 

Prerequisites:

  • Stambia DI Designer S19.0.0 or higher

Important Note:

Packages generated through a Launch Package Configuration are supported in build scripts since Stambia DI Runtime S17.6.0 and not yet in Analytics (this is being implemented and will be supported in upcoming releases.)

Refer to this article for further information about Launch Package Configurations

 

Running the script with the command line tool

As we now have the required script file, we can generate the Packages with the command line tool.
For this, navigate to the Designer installation root folder, and use the command below:

java -jar plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar  -application com.indy.shell.application -data "WORKSPACE_PATH" -script "SCRIPT_PATH"  [-logFile "LOG_FILE_PATH"] -console –noSplash

 

The following parameters are available:

Parameter Mandatory Required Designer Description
-data «WORKSPACE_PATH» Yes S18.3.2 or higher Path to the Stambia Designer workspace where the Processes are stored
-script «SCRIPT_PATH» Yes S18.3.2 or higher Path to the script file containing the list of packages to build, created earlier
-logFile «LOG_FILE_PATH» No S18.3.2 or higher Path to a log file where information about the Packages generation will be logged
-console -noSplash Yes S18.3.2 or higher These two options are required and used to launch the tool in command line mode
-cleanProjects No S18.3.3 or higher Rebuild all the Processes before executing the script (It corresponds to the Project > Clean menu that can be used in the Designer)
-rebuildCache No S18.3.3 or higher Rebuild the cache before executing the script (It corresponds to the Rebuild Cache menu of the Impact View in the Designer)
-importFrom No S18.3.3 or higher

This option allows to import other projects that are not in the workspace which is defined with -data option.

Specify here the path to a folder containing Projects that you want to import in the workspace before executing the script.

This offers the possibility to build Packages from Projects that are not already present in the workspace.

Important:

  • This will automatically create the Projects reference in the workspace (it does not copy the Projects.)
  • The folder specified must be outside of the workspace defined with -data option

 

 

When using this command line tool, make sure that the workspace it is working on is not opened by any Designer or any other instance of the tool

 

Example:

java -jar plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar -application com.indy.shell.application -data "D:/workspace/development" -script "D:/resources/scripts/packagesToGenerate.txt" -console -noSplash

 

You have no rights to post comments

Articles

Suggest a new Article!