Configuration of Node

Before deploying an application on the registered node, the server must first be configured. This is done through the Deployment Manager Administration Console and the configuration is then synchronized with the node's federated servers.

The Node Agent, which enables communication between the Deployment Manager and its federated servers, is required to be started. This must be done via the startNode.bat or startNode.sh command in the profiles/<federated profile name>/bin directory of the WebSphere Application Server installation.

After the Node Agent is started, all control is handed over to the Deployment Manager for this Node's servers. To start or stop a server in the Deployment Manager Administration Console:

Navigate to Servers > Server Types > WebSphere application servers;
Check the server to be started/stopped from the list and click the Start or Stop button as required.

The next step in the process is to configure the federated servers. As mentioned before, all configuration is done through the Deployment Manager Administrative Console. Manual WebSphere Application Server Configuration describes the manual WebSphere Application Server configuration for a basic installation, and should be followed with the differences identified below. When saving the master configuration ensure you manually force synchronization via the Administrative Console:

Navigate to System Administration > Save Changes to Master Repository;
Check the Synchronize changes with Nodes check box;
Click the Save button. The synchronization may take some time;
Check the system and/or WebSphere Application Server logs for synchronization completion. These messages may vary by WebSphere Application Server release, but you are looking for something like:
```
ADMS0208I: The configuration synchronization complete for cell.
```
Once synchronization is complete, review the server status and various WebSphere Application Server logs to ensure success;

Configure Administration Security details the security setup required during manual configuration. This setup requires the Registry.jar to be copied to a directory within the WebSphere Application Server installation. The Registry.jar should be copied from CuramSDEJ/lib to the lib directory of the Deployment Manager installation and any federated installations.

Note: Before building the Curam.ear for deployment it is worth noting the BOOTSTRAP_ADDRESS of the server that these will be installed onto. The BOOTSTRAP_ADDRESS is located in the same list of ports as the SOAP_CONNECTOR_ADDRESS described previously.

By default the BOOTSTRAP_ADDRESS expected by the application is 2809. To solve this issue either change this address or alternatively change the relevant property in your AppServer.properties file.

The property that should be changed is the curam.server.port value in the AppServer.properties file. Changing this affects the port value in the web.xml file when building an EAR file. For more information on the web.xml file consult the Cúram Web Client Reference Manual.