Configure a Server Node

   Journey Manager (JM) The transaction engine for the platform.  |    System Manager / DevOps  |  All versions This feature is related to all versions.

Manager allows you to create and configure server nodes.

To configure a server node:

1. Select System > Server Nodes.
2. Locate a service node and click Edit.



3. Provide the unique server name and server node URL.
4. Select the Form Space Portal Server checkbox if a server node handles public facing Internet traffic. It is not selected by default.
5. Change the Max Form Worker Queue value, which is a maximum length of the concurrent PDF form worker queue before throttling is imposed. The default is 25.  |  18.05 This feature was introduced in 18.05.
6. Change the Max Form Worker Threads value, which is a maximum number of the concurrent PDF form worker threads. The default is 25.  |  18.05 This feature was introduced in 18.05.
7. Select the Journey Manager Server checkbox to mark it as a Manager console server that supports development and operations staff.
8. Select the Transact PDF Receipt Server checkbox to mark it as a background PDF receipt generation server.
9. Select the LC Form Server checkbox if the server node is an Adobe LiveCycle Form Server.
10. Select the server node mode from the Form Server Mode dropdown list:
• Active – if the node handles Form requests and keeps LiveCycle repository synchronized
• Standby – is a hot standby server, which doesn’t handle requests, but keeps the LiveCycle repository synchronized.
• Inactive – doesn’t handle form request neither keep the LiveCycle repository synchronized.
Note

To deactivate a server node for a server node, change its status to Inactive.

11. Change the Max LC Process Load value, which is the maximum concurrent LiveCycle process load (%) before throttling is imposed. The default is 16.  |  18.05 This feature was introduced in 18.05.
12. Select the LC Service Connection from the dropdown list, which represents the LiveCycle Form Server local EJB connection detail:
• FormServer Connection.  |  18.05 This feature was introduced in 18.05.
13. Click Test Connection to establish a network connection to the server. The expected result is a successful message such as:
    'ip-192-168-140-46.us-west-2.compute.internal - TM Server' health status - CPU: 5% Executing Processes: null Errors: null Update Time: 10:37:58 AM.
    In case of an error message, check the server node configuration and re-test it again. The error message looks like:
    'ip-192-168-140-46 - TM Server' is unavailable.  |  18.05 This feature was introduced in 18.05.
14. Click Save to update the changes.

Next, learn how to remove a server node.