To add a new InfoSphere® MDM node
member to an existing IBM® WebSphere® Application Server cluster,
you must create the node, attach it to the cluster, and then configure
the node-cluster relationship.
About this task
A node in a WebSphere Application
Server cluster is defined as a profile. It can exist on a separate
machine or on a machine that already has one or more existing profiles
configured.
If the WebSphere Application
Server version is 8.5.5.2 or below, then step 5 is mandatory. Otherwise,
you can skip step 5.
Procedure
- Create a new WebSphere Application
Server node and attach it to an existing WebSphere Application Server cluster by
running the following command from a command line on the application
server:
cd /opt/IBM/WebSphere/AppServer/bin
./manageprofiles.sh -create -profileName profile_name –profilePath /opt/IBM/WebSphere/AppServer/profiles/profile_name –templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/managed –federateLater false -dmgrAdminUserName username -dmgrAdminPassword password –dmgrHost dmgr_host -dmgrPort dmgr_port
Replace
the variables in the command with the appropriate profile name, path,
user name, password, DMgr host, and DMgr port with the values appropriate
for your deployment. For example:
cd /opt/IBM/WebSphere/AppServer/bin
./manageprofiles.sh -create -profileName AppSrv03 –profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv03 –templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/managed –federateLater false -dmgrAdminUserName perf01 -dmgrAdminPassword perf01 –dmgrHost warhol-10ge -dmgrPort 8879
- Navigate to to confirm that the new
node is present.
- Add a new server instance to the cluster on the new node. Assuming that the name of the cluster is MDMCluster:
- In the WebSphere Application
Server Integrated Solutions Console, navigate to and click New.
- Give a name to the new member, select the new node from
the drop down list, then save and synchronize the settings.
- Navigate to to confirm that the new member is
present in the list of nodes.
- Start the nodes and all of the cluster members.
- If the WebSphere Application
Server version is 8.5.5.2 or below, uninstall and then reinstall the
business level application. Otherwise, any applications
that use bundles will fail after the new node is added to the Network
Deployment environment.
- Uninstall the business level application:
- Log into the WebSphere Application
Server Integrated Solutions Console on the server where InfoSphere MDM is
installed.
- Navigate to and delete the component unit and corresponding properties
JAR file. Save the change.
- Navigate to and delete the MDM-operational-server-EBA-<instanceID> application.
Save the change.
- Navigate to and delete the bundles com.ibm.mdm.mds.api.app, com.ibm.mdm.mds.jni.app, com.ibm.mdm.server.jaxrpcws.cba,
and com.ibm.mdm.thirdparty.cba. Save
the changes.
- Navigate to and delete the component unit and properties JAR file.
Save and synchronize the change.
- Reinstall the business level application using the provided
madconfig scripts:
- Copy the file <MDM_INSTALL_HOME>/properties/install_mdm_eba.properties to
the folder <MDM_INSTALL_HOME>/mds/scripts.
- Rename the copied file install_mdm_eba.local.properties.
- Modify install_mdm_eba.local.properties to
change all of the encrypted passwords to plain text passwords.
Tip: The value of the trustFilePwd property
is WebAS.
- Run the install_mdm_eba madconfig script.
- For Microsoft Windows systems, run the following
command:
<MDM_INSTALL_HOME>\mds\scripts\madconfig install_mdm_eba -propertyfile
<MDM_INSTALL_HOME>\mds\scripts\install_mdm_eba.local.properties
- For UNIX based systems,
run the following command:
<MDM_INSTALL_HOME>/mds/scripts/madconfig.sh install_mdm_eba -propertyfile
<MDM_INSTALL_HOME>/mds/scripts/install_mdm_eba.local.properties
- Copy the file <MDM_INSTALL_HOME>/properties/install_prop_file_jar.properties to
the folder <MDM_INSTALL_HOME>/mds/scripts.
- Rename the copied file install_prop_file_jar.local.properties.
- Modify install_prop_file_jar.local.properties to
change all of the encrypted passwords to plain text passwords.
Tip: The value of the trustFilePwd property
is WebAS.
- Run the install_prop_file_jar madconfig script.
- For Microsoft Windows systems, run the following
command:
<MDM_INSTALL_HOME>\mds\scripts\madconfig install_prop_file_jar -propertyfile
<MDM_INSTALL_HOME>\mds\scripts\install_prop_file_jar.local.properties
- For UNIX based systems,
run the following command:
<MDM_INSTALL_HOME>/mds/scripts/madconfig.sh install_prop_file_jar -propertyfile
<MDM_INSTALL_HOME>/mds/scripts/install_prop_file_jar.local.properties
- Run the configureNewNodeInCluster madconfig
script:
Results
The configureNewNodeInCluster madconfig
target requests values for the following parameters:
- Node name
- Name of the new member added to the cluster
- WebSphere Application
Server password
- Database password
- Trust file password
- Application instance ID
After receiving the parameter values, the configureNewNodeInCluster madconfig
target performs the following operations:
- Installs the native operational server (engine) on the newly added
member by invoking the install_native_engine_ear madconfig
target.
- Configures the application server for physical and virtual components;
including JDBC, class path, and environment variables on the newly
added member by invoking the install_server_config madconfig
target.
- Creates the Security role mapping and RunAs role mapping for the
EBA and web services EAR file on the newly added member by invoking
the map_roles_to_users madconfig target.
- Synchronizes the nodes in the server deployment to reflect the
user security for InfoSphere MDM by
invoking the full_sync madconfig target.
- Adds the details of the new member to the APPINSTANCE and CONFIGELEMENT
tables.
- Restarts the cluster.
- Encrypts passwords in the properties files.