Invoking Runtime Engine Using CLI
The runtime engine is invoked using the djengine command. The standalone engine must be already installed.
Note: You can also use the runtime engine that is embedded in the DataConnect Design Studio.
Before invoking the Runtime Engine, make sure that you have set the following environment variables:
• Set the path of the initialization file. By default, the initialization file is cosmos.ini.
• DJLIB:
• Windows: C:\ProgramData\Actian\DataConnect\actian-dc-studio-64-bit-<DataConnect_version>
• Set the path of the djengine.exe file:
• PATH:
• Windows: <installation_directory>\di-standalone-engine-64-bit-<DataConnect_version>\runtime\di9
• Linux: <installation_directory>/di-standalone-engine-64-bit-<DataConnect_version>/runtime/di9
Note: On Windows, the default Actian DataConnect installation folder is C:\Program Files\Actian\di-standalone-engine-64-bit-<DataConnect_version>. On Linux, it is /opt/Actian/di-standalone-engine-64-bit-<DataConnect_version>.
Note: Also, for Linux set LD_LIBRARY_PATH to the same location as PATH.
To run properly, Runtime Engine must locate the initialization file that contains the required information, including the library path and the license file paths. The default initialization file is
cosmos.ini. You can specify your own initialization file using the
-initialization_info command line option. See
Command Line Options.
When Runtime Engine is installed, the library path entry is saved in the Runtime Engine cosmos.ini file. The library path is set to the path where the product DLLs are installed. The license file path must be set manually after installation.
If the Runtime Engine environment is not set up properly, it returns a 25003 error during execution. If there is an issue with the license path or file, it returns a 30010 error during execution. The license path must be properly mentioned in the
cosmos.ini file. For information about the error codes, see
Message Component Framework Engine Error Codes.
Last modified date: 02/09/2024