The Profile Management tool or Customization Dialog has created jobs based on the information you
provided. These instructions tell you how to modify the operating
system and run the jobs to customize WebSphere Application Server for z/OS.
When you upload the customization jobs to the target system, a text version of
these instructions will be written to:
The Profile Management Tool does not attempt to update configuration data for your base operating system or existing subsystems. You need to perform the following manual steps prior to running the WebSphere for z/OS configuration jobs.
Type | Number |
---|---|
SOAP JMX Connector port | ${zFederateJmxSoapConnectorPort} |
Node Discovery port | ${zFederateNodeDiscoveryPort} |
Node Multicast Discovery Port | ${zFederateNodeMulticastDiscoveryPort} |
Node IPv6 multicast discovery port | ${zFederateNodeIPv6MulticastDiscoveryPort} |
Node Agent's ORB port | ${zFederateOrbPortName} |
High Availability Manager Communication port | ${zFederateHamCommPort} |
Node Agent's ORB SSL port | ${zFederateOrbSslPortName} |
Application Server's ORB Port | ${zFederateAppServerOrbPort} |
Add the contents of the cntl/bbotcpia file within this customization definition to the PORT section of the file referenced by the DD statement for the TCP/IP profile in the TCP/IP start procedure. Copy and paste from this file into the data set used by your installation.
Note: The addNode process introduces a special utility server to the node. This utility server is called a nodeagent and exists to support administrative functions on the node.
By default the nodeagent takes over ORB port 2809. Be aware that on WebSphere z/OS the ORB port doubles as the INS CosNaming bootstrap port. By default, this port (2809) was assigned to the Application Server. Usually you want the nodeagent to be the INS CosNaming bootstrap point for the entire node, so that RMI/IIOP clients that do not override the INS CosNaming bootstrap defaults can locate within the namespace, EJBs installed on any server on that node.
In order for the nodeagent to take over port 2809, the Application Server must be assigned a new ORB port. The default new ORB port for the Application Server is 9810. The nodeagent will take over an Application Server's ORB port if and only if the nodeagent's ORB port is equal to an Application Server's ORB port. You can specify the nodeagent's ORB port in the 'ORB port' field. You can specify the new ORB port for the Application Server in the 'Appplication Server's ORB Port' field.
Attention: If another application has already reserved any of these ports for its own use, you must resolve the resulting conflict before you continue. If you update the WebSphere for z/OS Customization Dialog or Profile Management tool with new port specifications, be sure to regenerate the customization jobs, data, and instuctions.Status of task | Date |
---|---|
The Profile Management Tool built a number of batch jobs with the variables you supplied. You need to run the jobs in the order listed below, using user IDs with the appropriate authority.
If the UNIXPRIV profile CHOWN.UNRESTRICTED is defined, then the SUPERUSER.FILESYS.CHOWN is not required. For information about the UNIXPRIV class, see the z/OS Unix System Services Planning book.
If the Network Deployment cell uses a z/OS LocalOS (SAF) registry, then the user ID used to run this job must be connected to the Network Deployment cell's configuration group.
If SSL certificates are stored in the SAF keyrings, then the user ID used to run this job must have a SAF keyring whose name matches the value of com.ibm.ssl.keyStore in the application server's WAS_HOME/profiles/default/properties/ssl.client.props file, and this keyring must contain the Network Deployment cell's CA certificate.
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Status of task | Date |
---|---|