Deploying Deliverables | ||
---|---|---|
Previous | Next | |
Installation | Executing a deliverable |
A configuration is a set of values specific to an environment.
For example, the
Production environment is configured with specific servers (host), users, passwords, folders, etc.
These values (or properties) differ from one environment to another.
In Semarchy Convergence for DI, every property can be configured and can take a different value from one environment to another:
The specific values of each environment are used when an integration job runs in this environment.
A deliverable is what is ultimately executed or scheduled. It is an XML file which contains the complete sequence of tasks to execute. It also contains pre-defined connections (server, ports, passwords, etc.). The deliverable is entirely configured for runtime. It is a self-sufficient artifact that only needs the runtime engine for execution.
Bringing an integration job to production is a two-step process:
The development team may deliver already configured deliverables. However, in most cases, the production team has to manage the configuration for production.
A package is an archive containing all the required files and folders to generate a deliverable. When the development team generates the package, it already contains default configuration. There is no need to uncompress a package. The operations required to configure and generate a deliverable are performed through a command line interface.
When the development team generates a package, this package contains a default configuration.
In the following section, you will learn the operations required to go to production. The commands and scripts used are available in the runtime root installation folder.
Note: The following instructions explain how to deploy from a command line. It is also possible to use Semarchy Convergence for DI Analytics to deploy the deliverables in a graphical user interface.
Note: Commands are given with the Linux/UNIX syntax, Windows users have access to similar scripts in .bat form for their platform.
In order to set the configuration specific properties, you must extract the configuration file using the following command:
./buildDelivery.sh [PACKAGE_NAME] -conf [CONFIGURATION_NAME] -extract
or
./buildDelivery.sh [PACKAGE_NAME] -confFile [FILE_NAME] -extract
This command generates a file into which you can change the properties. The configuration name can be any text. The file’s default name will be
.[CONFIGURATION_NAME].conf
. You can choose this file name with the
-confFile
option.
The extracted file contains properties that have to be left as is or modified. The properties to change depend on the data integration job and the differences between the development and production configurations.
#################################################################
### Name: super/Rdbms MetaData/Hypersonic SQL/ServerDatamart_HSQL.rdbms
### Type: com.stambia.rdbms.server
#_hXz80FvYEeGmhptGa6rXTA/url=jdbc:hsqldb:hsql://localhost:62211
#_hXz80FvYEeGmhptGa6rXTA/user=sa
#_hXz80FvYEeGmhptGa6rXTA/password=3951C0D79B227B95C1DC348DD0BCE8F1
#################################################################
### Name: super/Rdbms MetaData/Hypersonic SQL/ServerDatamart_HSQL.rdbms/DATAMART
### Type: com.stambia.rdbms.schema
#_ha9XcFvYEeGmhptGa6rXTA/TABLE_SCHEM=DATAMART
#################################################################
### Name: super/Rdbms MetaData/Hypersonic SQL/ServerMotel_HSQL.rdbms
### Type: com.stambia.rdbms.server
#_Pu1T8FvYEeGmhptGa6rXTA/url=jdbc:hsqldb:hsql://localhost:62210
#_Pu1T8FvYEeGmhptGa6rXTA/user=sa
#_Pu1T8FvYEeGmhptGa6rXTA/password=3951C0D79B227B95C1DC348DD0BCE8F1
#################################################################
### Name: super/Rdbms MetaData/Hypersonic SQL/ServerMotel_HSQL.rdbms/MOTEL
### Type: com.stambia.rdbms.schema
#_P0qPIFvYEeGmhptGa6rXTA/TABLE_SCHEM=MOTEL
Usually, elements to modify include URLs, users, passwords, schemas, folders and such.
To modify this file, the user must un-comment the line (remove the “#” at the beginning of the line), and modify the values. You can specify a property not visible in this file using the following syntax:
[object identifier]/[property name]=[value]
The object identifier and property name are unique. This means you can reuse a configuration file for several deliveries if they use the same servers, schemas, etc, and not have to extract the configuration file for each delivery.
The
password
property requires an encrypted password.
In order to encrypt, open a command with:
./startcommand.sh
Then in the command line, enter:
encrypt PASS_WORD@
This command returns a string which is the encrypted password which can be copied into the configuration file.
Use the following command to generate a deliverable from a package and a configuration:
./buildDelivery.sh [PACKAGE_NAME] -conf [CONFIGURATION_NAME]
Or
./buildDelivery.sh [PACKAGE_NAME] -confFile [CONF_FILE_NAME]
Example:
./buildDelivery.shTEST_LAUNCH.pck -confPROD
or
./buildDelivery.sh TEST_LAUNCH.pck -confFileproduction.conf
The deliverable is generated in the
build/deliveries
sub-folder.
When using
-confFile
, you can use a configuration file that includes all the elements required for the production environment.
Previous | Top | Next |
Installation | Executing a deliverable |