You can use the command line to federate middleware nodes
to a WebSphere® Virtual Enterprise cell.
Before you begin
- Augment a WebSphere Application Server deployment
manager profile to use WebSphere Virtual Enterprise.
Install the middleware agent on the node.
- Each of your middleware nodes must have the same network view
for each endpoint and resource that is related to WebSphere Application Server. All host entries
or host alias entries that are related to WebSphere Application Server within a hosts file
must be included in the hosts file on each of the other middleware
nodes in the configuration, including hosts files on nodes that run
the middleware agent. For example, if you define a product related
host alias called agentA in the hosts file for the nodeA node, then
the hosts file on each middleware node must contain an entry for the
agentA host alias.
Restriction: You cannot federate a
middleware node into a deployment manager that is running on the z/OS® operating system.
About this task
Federate a middleware node if it was not federated into the
cell during the middleware agent installation. You can perform this
task by using a command line or the administrative console.
Procedure
- To federate the node from the command line:
- Run the addAgent.sh or addAgent.bat command
from the middleware node. The command has the following
format:
agent_install_root/bin/addAgent.sh(bat) -host deployment_manager_host
-port deployment_manager_console_port [-username administrative_id]
[-password administrative_password] [-nodename node_name] [-noadmin]
Note: The -username and -password parameters
are required if security is turned on in the cell. The -noadmin parameter
is required if the administrative console application is not running
on the deployment manager at the time of federation. You can use the -nodename parameter
to specify the name of the middleware agent that is being federated.
If you do not specify this parameter, the host name of the middleware
agent is used as the name instead.
The following
example federates a middleware agent node to a cell in which the deployment
manager is running on xdblade03b:addAgent.sh -host xdblade03b -port 9060 -username admin -password admin
- Start the agent. Run the following command
from the middleware node:
agent_install_root/bin/startAgent.sh(bat)
- To start the agent from the administrative console:
- In the administrative console, select .
- From the Select operational action menu,
select Start agent.
- Click Run.
Results
The middleware node is displayed as an unmanaged node in
the product cell. If problems occur, check the following log files:
- install_root/logs/addAgent.log file for addNode
command errors
- install_root/logs/middlewareagent/SystemOut.log file
- install_root/logs/middlewareagent/SystemErr.log file
What to do next
Configure middleware servers and dynamic clusters.