The zpmt command uses the values that you specify for the variables defined in a response file to create customization data and instructions for configuring a managed (custom) node with the feature pack enabled.
SYSPROG1.WAS70.TESTCELL.APPSERVIn this example, the following two datasets will be created when the customization definition is uploaded to the target z/OS system:
SYSPROG1.WAS70.TESTCELL.APPSERV.CNTL SYSPROG1.WAS70.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.
The customization process creates this mount point if it does not already exist.
If you specify an intermediate symbolic link, symbolic links are created from the configuration file system to the intermediate symbolic link; otherwise, they are created directly to the product file system.
The default value for zEnableIntermediateSymlink is true.
If you specify an intermediate symbolic link, symbolic links are created from the configuration file system to the intermediate symbolic link; otherwise, they are created directly to the product file system.
The default value is true.
The BBOCTIOO sample parmlib member in the SBBOJCL dataset can be used to create this CTRACE parmlib member.
This name identifies the node as displayed through the administrative console.
This value is used by other WebSphere Application Server for z/OS functions to connect to this server.
This is set to the configuration file system mount point/Daemon and cannot be changed.
Caution: When configuring a new cell, be sure to choose a new daemon job name value.
Select either * or a dotted decimal IP address for this value.
The default value is *.
Choose the value carefully. It is difficult to change, even in the middle of customization.
You must specify this even if you selected false for Generate Certificate Authority (CA) certificate.
The key ring names created for repertoires are all the same within a cell.
You can choose one of the following three options for administrative security.
Your WebSphere Application Server environment will not be secured until you configure and enable security manually.
For this security option, you must decide whether to include a SAF prefix and choose an administrator user ID as well as an unauthenticated (guest) user ID.
For this security option, you must choose an administrator user ID and password.
For this security option, there are no other choices to make. Your WebSphere Application Server environment will not be secured until you configure and enable security manually.
It provides the federation process with knowledge of which deployment manager is the target of the federation.
This is the security domain administrator user ID and cannot be changed.
Specify DefaultNodeGroup if the node is in the same sysplex as the deployment manager.
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.
This is the server's job name, as specified in the MVS START command JOBNAME parameter. This value identifies the server to z/OS facilities such as SAF.
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 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).
Security certificate customization should be done only if product-managed security or no security has been specified.