Specify values for the variables in the Profile Management Tool to create customization data and instructions that you can use to federate an application server.
The Profile Management Tool creates customization data and instructions that are used to configure a WebSphere Application Server for z/OS runtime environment. A z/OS runtime profile is not created, however, until the actions listed in the generated instructions are performed on the target z/OS system.
This name is used on the workstation to identify the customization data and instructions that are created. The name chosen has no effect on the WebSphere Application Server for z/OS configuration.
When this value is specified, the input fields are preloaded with the values in the response file.
Options for generating default values for this customization definition
If you specified a response file for setting default values, any default selected here will override the corresponding response file values.
When this option is not selected, each port value defaults to an IBM-provided number. When this option is selected, each port default value is selected from the following port number range.
The port range must contain at least 10 ports.
SYSPROG1.WAS80.TESTCELL.APPSERVIn this example, the following two datasets will be created when the customization definition is uploaded to the target z/OS system:
SYSPROG1.WAS80.TESTCELL.APPSERV.CNTL SYSPROG1.WAS80.TESTCELL.APPSERV.DATAThe CNTL dataset will be a partitioned dataset (PDS) with fixed block 80-byte records that will contain the customization jobs. The DATA dataset will be a PDS with variable length data to contain the other customization data.
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.
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.
It provides the federation process with knowledge of which deployment manager is the target of the federation.
The user ID and password are required when global security is enabled on the Network Deployment cell unless an RMI connector is being used. If an RMI connector is being used, the identity information will be extracted from the thread of execution of the addNode job if the user ID and password are not specified.
This name identifies the server as displayed through the administrative console. The node agent server long name is set to the fixed value of nodeagent.
JMX is used for remote administrative functions and is invoked through scripts such as wsadmin.sh.
The default is *, which instructs the ORB to listen on all available IP addresses.
The default is 0, which allows the system to choose this port.
The multicast IP address on which the discovery port is opened is defaulted by WebSphere Application Server for z/OS to 232.133.104.73. 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.
The connector uses "local comm" communications protocol, which means that the port is used only for communications that are local to the z/OS system image (or sysplex).
This user ID also owns all of the configuration file systems.
Specify DefaultNodeGroup if the node is in the same sysplex as the deployment manager.
Enabling this option instructs the addNode command to include applications from the node; otherwise, it would remove them prior to federation. If the application already exists in the cell, a warning is printed and the application is not installed into the cell.
You must use this option to migrate all of 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.
All the customization jobs that will be tailored for you will need a job statement. Enter a valid job statement for your installation. The customization process will update the job name for you in all the generated jobs, so you need not be concerned with that portion of the job statement. If continuation lines are needed, replace the comment lines with continuation lines.