wp_61_configure_cluster_node_config_pre_federation
Runs all pre-federation tasks for primary or secondary nodes in IBM WebSphere Portal cluster.
For primary node configures: <WAS_PROF_HOME>/ConfigEngine/properties/wkplc.properties as: WasRemoteHostName=ND_HOST_NAME WasSoapPort=ND_SOAP_PORT PrimaryNode=true ClusterName=WP_CLUSTER_NAME
For secondary node configures: <WAS_PROF_HOME>/ConfigEngine/properties/wkplc.properties as: WasRemoteHostName=ND_HOST_NAME WasSoapPort=ND_SOAP_PORT PrimaryNode=false ClusterName=WP_CLUSTER_NAME
The configure.properties file[1] at the cell scope is required. The
configuration generator creates this file and sets these properties:
WAS_USERNAME, WAS_PASSWORD, WP_USERNAME, WP_PASSWORD
The install.properties file[2] at the node scope is required. The
configuration generator creates this file and sets these properties:
WAS_HOME, WP_HOME, WAS_PROF_HOME, WP_SETUP_TYPE, WP_MANAGED,
WP_MANAGED_PRIMARY, WP_STARTING_POINT, BASE_STARTING_POINT,
WP_ADMIN_STARTING_POINT, WP_EMPTY_PORTAL, WP_INSTALL_WPS,
HOST_NAME, WP_INSTALL_TYPE, PROFILE_NAME, OS_USER, OS_GROUP[3]
Provide values for the following variables:
In <cell path>/configure.properties [3], set these properties:
ND_HOST_NAME Network Deployment host name.
ND_SOAP_PORT Network Deployment soap port.
PRIMARY_NODE Primary IBM WebSphere Portal cluster node.
WP_CLUSTER_NAME IBM WebSphere Portal cluster name.
WAS_USERNAME IBM WebSphere Application Server administrator's user
name.
WAS_PASSWORD IBM WebSphere Application Server administrator's user
password.
WP_PASSWORD IBM WebSphere Portal administrator's user password.
In <cell path>/install.properties [2], set these properties:
WAS_PROF_HOME IBM WebSphere Application Server profile path.
Example: /opt/IBM/WebSphere/AppServer/profiles/node01
execute
node
This action is not supported on z/OS target systems.
This action runs the "cluster-node-config-pre-federation" configuration task
using:
UNIX: <WAS_PROF_HOME>/ConfigEngine/ConfigEngine.sh
Windows: <WAS_PROF_HOME>/ConfigEngine/ConfigEngine.bat
See IBM WebSphere Portal Information Center documentation for more details
on this task.
[1]Applies to UNIX and Linux environments
[2] The scope home is relative to the environment tree path and is
specific to the supplied SCOPE arguments:
RAFW_HOME/user/environments
cell path: ENV_NAME/cells/CELL_NAME
cluster path: <cell path>/clusters/CLUSTER_NAME
node path: <cell path>/nodes/NODE_NAME
server path: <node path>/servers/SERVER_NAME
[3] The configuration generator creates configure.properties at the cell scope
in RAFW_HOME/user/environments.
cell: <env_name>/cells/<cell_name>
The configuration generator creates install.properties at the node scope in
RAFW_HOME/user/environments.
node: <env_name>/cells/<cell_name>/nodes/<node_name>
References:
Related Information Center links:
- http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/
index.jsp?topic=/com.ibm.wp.ent.doc/install/production.html
- (AIX example) http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/
index.jsp?topic=/com.ibm.wp.ent.doc/install/aix_cluster.html