Adapters in a Separate JVM Overview
- Installing a patch
- Restarting the system to pick up property file updates
- Out-of-memory and other system errors
- Isolate adapters from engine failure.
- Isolate engine from adapter failure.
- Isolate one adapter failure from another adapter.
- Separate lifecycle for adapters.
- Receive data for adapter even if engine application server independent virtual machine (ASI VM) is down, but the database must be up.
You can run adapters in a separate JVM by creating an adapter container JVM. The adapter container JVM acts like a cluster node, but with limited functions. If you are running Sterling B2B Integrator in a single node environment, the adapter container JVM is listed as a cluster node. Similarly, if you are running Sterling B2B Integrator in a cluster environment, it is listed as a node along with other nodes, but you cannot schedule a business process to run in the adapter container JVM.
Sterling B2B Integrator requires a range of 100 consecutive open ports between 1025 and 65535. However, if you are running Sterling B2B Integrator in a vertical cluster environment, the ports reserved by Sterling B2B Integrator are higher than 100 ports. This can be calculated by the following formula:
(Number of nodes * 100)
- Sterling Connect:Direct®