This topic applies only on the z/OS operating system.

Customization Dialog variables: Federating an application server node

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

Rules:

WebSphere Application Server for z/OS home directory

WebSphere Application Server home directory
Directory in which the stand-alone application server configuration resides.
Note: Depending on the variables you loaded in the "Load customization variables" step, you might 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 deployment manager 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 (formerly known as 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" if global security is enabled on the Network Deployment cell and the deployment manager.
User ID
A user ID with full administrative privileges for the Network Deployment cell. This is set to the security domain administrator ID and cannot be changed.
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 the node agent to start automatically after federating a node.
Application server's ORB port
Port for IIOP requests that acts as the bootstrap port for this server and also as the port through which the ORB accepts IIOP requests. Port value cannot be 0.
Note: The add node operation creates the node agent 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 stand-alone server, the initial stand-alone 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 group name
The node group into which the node will be placed. Specify DefaultNodeGroup if the node is in the same sysplex as the deployment manager.

Node Agent Definitions

As part of the federation process, a node agent is created. This special server administers the node and its servers on behalf of the deployment manager.
Server name (short)
Name of the node agent server. This is the server's jobname, as specified in the MVS™ START command JOBNAME parameter. This value identifies the server to certain z/OS facilities used by WebSphere Application Server for z/OS (SAF for example).

Rule: Name must usually contain seven or fewer all-uppercase characters. To change the jobname later to an eight-character value, you must follow the steps outlined in the "Converting a 7-character server short name to 8 characters" article in the information center.

Server name (long)
Name of the node agent and the primary external identification of the node agent server. This name identifies the server as displayed through the administrative console. The node agent server long name is set to the fixed value "nodeagent".
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.

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 port through which the node agent sends discovery requests to its managed servers.

The multicast IP address on which the discovery port is opened is defaulted to 232.133.104.73 by WebSphere Application Server for z/OS. This default address can be changed using the administrative console. This is a CLASS D address. The valid IP range is from 224.0.0.0 to 239.255.255.255.

High Availability Manager communication port
Port on which the High Availability Manager listens.
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 that 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.

Service integration bus

Do you wish to federate service integration busses that exist on this node? (Y/N)
Specify "Y" to federate service integration busses that exist on this node.

Web Server Configuration

Note: Web server configuration setup was removed from stand-alone application server federation in WebSphere Application Server for z/OS Version 6.0.2. Create Web server definitions for local or remote z/OS Web servers in a Network Deployment cell using the deployment manager customization job BBODCFGW.

You can configure your Web server using this panel.
Web Server Name
Name used to define the Web server in the administrative console.
Host
IP name or address of z/OS system on which Web server resides.
Node Name (long)
Node name of your federated node.
Port
HTTP port on which the Web server listens.
Application Mapping
Determines whether you want to map all applications (A), none of the applications (N), or the default application (D) to the Web server.



Related reference
Customization Dialog worksheet: Federating an application server node
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 8:25:23 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=rins_defvar5def
File name: rins_defvar5def.html