Add the secondary node to the deployment manager's cell
on IBM® i. Adding the secondary
node to the cell allows a central point of administration for the
network deployment by using the deployment manager's Integrated Solutions
Console.
Before you begin
Expected state: the deployment manager is running.
About this task
For additional information about default paths, see Directory conventions.
Procedure
- Make sure that the system clocks on the deployment manager
and the secondary node are within five minutes of each other and set
for the same timezone. Federation fails if the clocks are not synchronized
within five minutes.
- Ping the deployment manager node from the secondary node
to make sure the deployment manager host name is resolvable.
- Log in to the IBM i
system where the deployment manager node is installed with administrative
privileges.
- On the IBM i command
line, run the STRQSH (Start Qshell) command.
- Navigate to the
profile_root/bin
directory
for the deployment manager profile. - Run the following command to obtain the SOAP_CONNECTOR_ADDRESS port
number. Make a note of the port number as you will need it to add
nodes to the cluster:
- Log into the secondary node.
- On the IBM i command
line, run the STRQSH (Start Qshell) command.
- Navigate to the
profile_root/bin
directory
for the secondary node profile. - Run the following command to add the secondary node to
the deployment manager's cell. Note the omission of the
-includeapps
qualifier.
addNode DM_server_host_name DM_SOAP_port -username WAS_Admin_user_name_on_DM
-password WAS_Admin_password_on_DM
where:
- DM_server_host_name is the resolvable host
name of the deployment manager.
- DM_SOAP_port is the port that the deployment
manager's SOAP port is listening on.
- WAS_Admin_user_name_on_DM is the user ID of
the WebSphere® Application
Server administrator account on the deployment manager.
- WAS_Admin_password_on_DM is the password associated
with the WebSphere Application
Server administrator account.
For example:
addNode gateway_dm.example.com 8880 -username wasadmin -password waspassword
- When prompted, provide the deployment manager's administrative
user ID and password.
Wait for the operation to complete
before proceeding. Look for a success message similar to the following
when complete:
Node Machine22NodeSecondary has been successfully federated.
- For each additional IBM i
secondary node, repeat the preceding steps.
- Navigate to the
profile_root/bin
directory
for the deployment manager profile. - Restart the deployment manager by typing the following
commands. Wait for the first command to finish before starting the
deployment manager:
./stopServer.sh dmgr -username username -password password
./startServer.sh dmgr
What to do next
When you have finished installing and federating secondary
nodes into the Deployment manager, continue with the cluster configuration
as instructed in the topic, Creating a cluster and proxy servers.