Configuration of Node

Before deploying an application 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 can be done via the z/OS operator START command appropriate for your installation or the startNode.sh command in the profiles/<federated profile name>/bin directory of the WebSphere Application Server for z/OS 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 for z/OS configuration for a basic installation, and should be followed with the differences identified below. When saving the master configuration, ensure you synchronize your changes as described in Synchronizing Changes.

Set up the System JAAS Login Module 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 for z/OS 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 application .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 (EAR) file. For more information on the web.xml file consult the Cúram Web Client Reference Manual.