IBM

3.3.5 Federating a custom node to a cell

You only have to do this if you created a custom profile and chose not to federate it at the time. This requires that you have a deployment manager profile and that the deployment manager is up and running.

An custom profile is used to define a node that can be added to a cell. To federate the node to the cell...

1. Start the deployment manager.

2. Open a command window on the system where you created the custom profile for the new node. Switch to the <profile_home>/bin directory (for example, cd C:\myWAS61Profiles\cstmProfiles\CstmProfile1).

3. Run the addNode command. Here we need the host name of the deployment manager and the SOAP connector address (see Figure 3-7 and Figure 3-8): 

addNode <dmgrhost> <dmgr_soap_port>

Example 3-1 shows an example of using the addNode command on a Windows system to add Node06 to the deployment manager using 8879 as the SOAP connector address.

Example 3-1 addNode command 

C:\WebSphere\ND\profiles\Node06\bin>addnode localhost 8879



ADMU0116I: Tool information is being logged in file



           c:\WebSphere\ND\profiles\Node06\logs\addNode.log



ADMU0128I: Starting tool with the Node06 profile



CWPKI0308I: Adding signer alias "dummyclientsigner" to local keystore



           "ClientDefaultTrustStore" with the following SHA digest:



           0B:3F:C9:E0:70:54:58:F7:FD:81:80:70:83:A6:D0:92:38:7A:54:CD



CWPKI0308I: Adding signer alias "dummyserversigner" to local keystore



           "ClientDefaultTrustStore" with the following SHA digest:



           FB:38:FE:E6:CF:89:BA:01:67:8F:C2:30:74:84:E2:40:2C:B4:B5:65



CWPKI0308I: Adding signer alias "default_2" to local keystore



           "ClientDefaultTrustStore" with the following SHA digest:



           CC:60:A6:33:99:B0:D9:34:B2:6A:89:5F:A7:5F:C8:C1:9E:CC:8C:2A



CWPKI0308I: Adding signer alias "default_1" to local keystore



           "ClientDefaultTrustStore" with the following SHA digest:



           20:83:69:46:D9:B9:95:51:00:99:3C:D9:3B:EF:E4:1B:C1:9A:C1:84



CWPKI0308I: Adding signer alias "default" to local keystore



           "ClientDefaultTrustStore" with the following SHA digest:



           DA:29:33:E3:61:67:91:79:B4:54:EA:95:04:D0:47:8A:14:70:DF:90



ADMU0001I: Begin federation of node Node06 with Deployment Manager at



           localhost:8879.



ADMU0001I: Begin federation of node Node06 with Deployment Manager at



           localhost:8879.



ADMU0009I: Successfully connected to Deployment Manager Server: localhost:8879



ADMU0507I: No servers found in configuration under:



           c:\WebSphere\ND\profiles\Node06\config/cells/kadw028Node04Cell/nodes



Node06/servers



ADMU2010I: Stopping all server processes for node Node06



ADMU0024I: Deleting the old backup directory.



ADMU0015I: Backing up the original cell repository.



ADMU0012I: Creating Node Agent configuration for node: Node06



ADMU0014I: Adding node Node06 configuration to cell: kadw028Cell01



ADMU0016I: Synchronizing configuration between node and cell.



ADMU0018I: Launching Node Agent process for node: Node06



ADMU0020I: Reading configuration for Node Agent process: nodeagent



ADMU0022I: Node Agent launched. Waiting for initialization status.



ADMU0030I: Node Agent initialization completed successfully. Process id is:



           2120



ADMU0505I: Servers found in configuration:



ADMU0506I: Server name: nodeagent



ADMU9990I:



ADMU0300I: The node Node06 was successfully added to the kadw028Cell01 cell.



ADMU9990I:



ADMU0306I: 

 


ADMU0302I: Any cell-level documents from the standalone kadw028Cell01



           configuration have not been migrated to the new cell.



ADMU0307I: You might want to:



ADMU0303I: Update the configuration on the kadw028Cell01 Deployment Manager



           with values from the old cell-level documents.



ADMU9990I:



ADMU0306I: 

 


ADMU0304I: Because -includeapps was not specified, applications installed on



           the standalone node were not installed on the new cell.



ADMU0307I: You might want to:



ADMU0305I: Install applications onto the kadw028Cell01 cell using wsadmin



           $AdminApp or the Administrative Console.



ADMU9990I:



ADMU0003I: Node Node06 has been successfully federated.



C:\WebSphere\ND\profiles\Node06\bin>

4. Open the deployment manager console and view the node and node agent:

Select System Administration  | Nodes. You should see the new node.

Select System Administration  | Node agents. You should see the new node agent and its status. It should be started. If not, check the status from a command window on the custom node system:

cd <profile_home>\bin

serverStatus -all

If you find that it is not started, start it with this command:

cd <profile_home>\bin

startNode

Redbooks ibm.com/redbooks

Next