Define variables for federate base Application Server node - definitions

This article lists definitions for the terms you will come across in the WebSphere Application Server for z/OS Customization Dialog.

Note: Some term definitions--those that you cannot set in the related panel--are not displayed. To see the definition, you must to go to the Information Center article for the panel on which you can change that particular term.

Rules:

WebSphere Application Server home directory
Directory in which the base Application Server configuration resides.

Note: Depending on your service level and the variables you loaded in the "Load customization variables" step, you may need to modify this value to reflect the correct directory.

Deployment Manager Access

Node host name
IP name or address of the system on which the deployment manager server is configured. This value, equivalent to "cell host" in addNode.sh, is used by other WebSphere Application Server for z/OS functions to connect to this server in order to federate the designated node into the deployment manager cell.

Note: The node host name must always resolve to an IP stack on the system where the Application Server runs. The node host name cannot be a DVIPA or a DNS name that, in any other way, causes the direction of requests to more than one system.

JMX SOAP port
JMX (Java Management Extensions) SOAP (Simple Object Access Protocol) connector port that the add node request uses to connect to the deployment manager. It provides the federation process with knowledge of which deployment manager is the target of the federation.
Deployment manager security is enabled
Specify "Y" to enable deployment manager security.
Include Apps
Specify "Y" if you want to include applications with your deployment manager node. Enabling this option instructs the addNode program to include applications from the node, as it would remove them prior to federation otherwise. If the application already exists in the cell, a warning is printed and the application is not installed into the cell.

Note: You must use this option to migrate all the applications to the new cell. Federating the node to a cell using the addNode command does not merge any cell-level configuration information, including that from virtualHost.

Launch the node agent after node federation
Specify "N" if you do not want to start the node agent after federating a node.

Note: This option was added in WebSphere Application Server for z/OS Version 5.1.x.

Base server ORB port
Port for IIOP requests which acts as the bootstrap port for this server and also as the port through which the ORB accepts IIOP requests. The port value cannot be 0.

Note: The add node operation creates the nodeagent administrative server with a default ORB port equivalent to the INS CosNaming default bootstrap port. Because this same port was previously used by the node's initial base server, the initial base server's ORB port must change to a new port value. The default value to which the Application Server's ORB port is set is 9810. If you configure multiple cells that intersect the same systems, use of the default value will cause a port conflict between these cells. This option helps you set the port number in case port 9810 was previously assigned.

Node Agent Definitions

Server name (short)
Name of the node agent server. This is the server's job name, as specified in the MVS START command JOBNAME parameter. This value is also passed as a parameter to the server's start procedures to specify the location of the server's configuration files and identify the server to certain WebSphere Application Server for z/OS-exploited z/OS facilities (for example, SAF).

Rule: Name must usually contain 7 or fewer all-uppercase characters. If you wish to instead specify 8 characters, you must follow the steps outlined in the Information Center article "Converting a 7-character jobname to 8 characters."

Server name (long)
Name of the node agent and the primary external identification of the nodeagent server. This name identifies the server as displayed through the administrative console and also appears as part of the directory path under the WebSphere Application Server for z/OS home's configuration directory.

Rule: Name must be 60 or fewer characters and can be of mixed case.

JMX SOAP Connector port
Port number for the JMX HTTP connection to this server based on the SOAP protocol. JMX is used for remote administrative functions and is invoked through scripts such as wsadmin.sh.

Rule: Value cannot be 0.

DRS Client Address port
Port used to access the server's data replication service. This is important for configurations that define replication groups.

Rule: Value cannot be 0.

Node Discovery port
Defines the TCP/IP port to which the node agents listens for discovery requests that originate from the deployment manager.
Node Multicast Discovery port
Defines the multicast TCP/IP port to which the node agent listens for discovery requests that originate from its managed servers. This is a CLASS D address.
ORB listener host name
IP address on which the server's ORB listens for incoming IIOP requests. The default is "*", which instructs the ORB to listen on all available IP addresses.
ORB port
Port for IIOP requests which acts as the bootstrap port for this server and also as the port through which the ORB accepts IIOP requests.

Rule: Value cannot be 0.

ORB SSL port
Port for secure IIOP requests. The default is "0", which allows the system to choose this port.

Related concepts
Setting up WebSphere Application Server for z/OS security
Related tasks
Warning: no string named [tins_dialogdefvarsteps] found.
Related reference
Define variables for federate base Application Server node - worksheets



Searchable topic ID:   rinsdefvar5def
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/rins_defvar5def.html

Library | Support | Terms of Use | Feedback