When you install a new Stambia DI Runtime there are some things you have to think about.
Complete installation procedure can be found in reference documentation.
You can find it on stambia.org at the following location.
You can also find it in Stambia DI Designer's Help Contents under Runtime Installation and Configuration Guide.
Refer to those documentation entries to learn how to install a new Stambia DI Runtime.
This article only gives additional tips about the installation procedure.
If you are upgrading from a previous version, please refer to this article.
Choosing a Java version
The correct Java version to use will depend on your environment and what you will do with the Runtime.
You can find below some important advices about how to choose the correct Java version for your case:
- Stambia DI Runtime S17.x.x works well with java versions 6, 7, and 8.
Make sure to select a Java version compatible with:
- your JDBC drivers (Oracle, Mysql, Sqlserver...)
- the Components you will use (SAP, Salesforce, Amazon...)
- the encryption algorithms you may need for SSL-secured connections (SFTP, SSH, HTTPS...)
- Make sure to use the same Java version on all your environment, such as your development, testing, or production environments! This is a really good practice to avoid bad surprise when deploying jobs in production.
Tips and advices
Here is some other useful tips which may help you during the process.
First run: Check the output of the startengine
Before installing Stambia DI Runtime as a service, check if everything is working by starting the Runtime with the
startengine.bat (or startengine.sh) script.
It is easier to see the errors that might happen during the startup this way.
Then if everything is correct and working, you can install it as a service.
Example of Output:
21/08/2015 11:00:18,485 - Runtime version: s17.2.14_20150625
21/08/2015 11:00:18,486 - Java version: 1.6.0_43 vendor: Sun Microsystems Inc. home: C:\Program Files\Java\jdk1.6.0_43\jre
21/08/2015 11:00:19,052 - Internal Database is started: stambia-pc20:42100
21/08/2015 11:00:19,073 - Internal Database Web Server is started: http://stambia-pc20:42101
21/08/2015 11:00:21,885 - RMI server is started: rmi://stambia-pc20:42000
21/08/2015 11:00:24,400 - Scheduler is started
21/08/2015 11:00:25,633 - SOAP Endpoint: http://stambia-pc20:42200/wsi/DeliverableService?WSDL
21/08/2015 11:00:25,633 - SOAP Legacy "Non WSI-Compliant" Endpoint: http://stambia-pc20:42200/StambiaDeliveryService?WSDL
21/08/2015 11:00:25,633 - HTTP Rest Endpoint: http://stambia-pc20:42200/rest/StambiaDeliveryService/1/<deliveryName>
Prevent the command line from closing when errors at startup
When launching the startengine script, if there are errors at startup then the console's window opens and closes immediately, and you cannot see the errors.
To avoid that:
- Open a command line prompt
- Then, type
cmd(in windows, or
bashfor example in linux) in order to open a sub process.
- Navigate to the place where the startengine script is and execute it.
Now, if the Runtime closes on errors it will come back to the first command line process, and you will still have the errors displayed.
Once the reasons for the errors are solved (most often Java installation issues), of course you do not need to do this again.