The Automation Adapter Environment Configuration File
To start the automation adapter, you need to setup the environment variables in the configuration file ingadapter.properties. Specify the configuration file in the start procedure DD STDENV.
See also Prerequisites and Environment Setup
| Parameter | Default Value | Description |
|---|---|---|
| E2E_INSTALL_ROOT | /usr/lpp/ing/adapter | The automation adapter installation path. |
| E2E_CUSTOM_ROOT | /usr/lpp/ing/adapter | The automation adapter customization path for modified configuration files, logger and SSL related files. |
| E2E_JAVA_XMX | 256 | The maximum memory that the automation adapter is allowed to allocate. You can specify the maximum memory allocated by JVM in MB. |
| E2E_SSL_PASSW | password | The password for the truststore that is generated by the generateSampleKeys function. This is only needed if you plan to generate sample keys for test purposes. |
| E2E_SSL_VERSION | TLS | The version of the SSL protocol that is used for SSL communication, for example, TLSv1.2. If you change it here, you must change it for the E2E agent (INGAGT_SSL_VERSION) and for the Z Automation Web Console server (com.ibm.eez.adapter.ssl.version) as well. |
| E2E_USRJP | Here you can add user specific Java system properties, for example, SSL debugging
options.This parameter is useful if you need to debug SSL handshake exceptions. |
|
| E2E_USRCP | /u/mydir/my.jar | Here you can add user specific classpath if needed. |
| E2E_DEBUG | ON | The switch to set on the logger function. Needed only if problem analysis is required. |
| E2E_JAVA_HOME | /local/java/J6.0 | The Java runtime and SDK paths to invoke Java and the Java keytool respectively if the default java is not appropriate. |
| E2E_DROPCON | NO or YES | Set NO if you do not want the start script to drop possible open or unused connections. |
| E2E_TCPNAME | Empty string | The name of the TCP/IP stack where you want to isolate E2E Automation and NetView E/AS. System symbols are supported here. |