Typically, you will iterate multiple times in the optimization phase before porting your integration solution to a test environment. You must begin load testing once you have the basics available to view how it performs in a real time environment.

You can package the artifacts from the IDE into a portable archive file called a *.djar and execute this file with the Runtime Engine CLI. For detailed instructions, see Packaging and Deploying Integration Artifacts.

Make sure you have a test server available that matches the production server on which the Actian DataConnect Runtime Engine will be installed. The specs for your test server must optimally be identical to the production server so that there are no surprises when you go live. DataConnect is container friendly so one way to achieve this is by using the same container image in both the environments.

Run your tests methodically and record the results. Use various sample sizes that span from very small to very large and identify relative performance differences. Make sure to capture log files, execution dates and times, the size of each data sample, and other key metrics so that you can track them with the modifications you will make in the future.

Most of this information is stored in the Integration Manager job history database when executing in Integration Manager. However, it is not stored when you execute directly with the standalone Runtime Engine. For detailed instructions, see Using Runtime Engine.