Engine Considerations

Edit online

Refer to the following considerations when configuring or editing an engine definition:

When you configure an engine, you identify either the host name or the IP address in the definition. Define only one engine definition for each engine you install.
To run two engines that use different network interface cards (NICs) on one computer, install the engine and use the configureAcceptor script to change the IP address and port to listen on. Create an engine definition for each NIC card and make sure that the IP address in the engine definition is the same as the one specified in the script. If you want the engine's local perimeter server to use a specific NIC for adapter traffic, you must edit the perimeter.properties file and change the localmode.interface parameter to the desired IP address. Refer to the documentation library.
When the engine is installed on Solaris 10 and you use SSL or TLS, the AES_256 and DES40 ciphers fail. To enable these ciphers, refer to Remove the PKCS11 Security Provider.
The default session limit is 20 and allows only about six users with browser sessions. If you use an application such as myFileGateway or Dashboard, change this limit.
If you get the following out of memory error, the engine does not have enough memory to create new threads. This error could result in an abnormal termination.
```
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start (Thread.java:574)
```
Take one or more of the following actions:
- If you have more physical memory on the server, install and configure another engine on the server and move some adapters to the new engine. Refer to Planning and Installation and Other Configuration Options on the documentation library for instructions.
- Decrease the size of the thread pool defined for SFTP adapters. For each adapter definition, change the following parameters to the same value:
  - sftp_acceptthreads - Identifies how many threads are available to accept inbound client connections. The default value is 50.
  - sftp_connectthreads - Identifies how many threads are available for permanent connect threads. When existing SSH connections make socket connections through port forwarding, these threads manage the asynchronous connection process. The default value is 50.
  - sftp_xferthreadpools - Identifies how many threads are available for permanent transfers. This thread asynchronously performs the IO for the socket. The default value is 50.
    Refer to SFTP Adapter Definition - Propertiesin the documentation library for instructions on changing these values.
- Make more memory available for a Java process and increase the maximum number of threads allowed. Refer to your operating system documentation.
- Adjust your system kernel values to allow a larger number of files, processes, and threads per user.