Federating custom nodes to a deployment manager

You can use the addNode command to federate a custom node into a deployment manager cell. The following instructions guide you through the process of federating and deploying custom nodes.

1. First you should take  dmgr profiles configuartion backup

2. you must be start DMGR before federating custom node profile.

[oracle@websphe bin]$ pwd

/u03/local/opt/was/was70/profiles/dmgr/bin

[oracle@websphe bin]$ ./startManager.sh

ADMU0116I: Tool information is being logged in file

/u03/local/opt/was/was70/profiles/dmgr/logs/dmgr/startServer.log

ADMU0128I: Starting tool with the dmgr profile

ADMU3100I: Reading configuration for server: dmgr

ADMU3200I: Server launched. Waiting for initialization status.

ADMU3000I: Server dmgr open for e-business; process id is 5067

Issue the addNode command.

Syntax

./addNode.sh deployment_manager_host deployment_manager_SOAP_port

[oracle@websphe was]$ cd was70/profiles/

[oracle@websphe profiles]$ ls

dmgr  node01

[oracle@websphe profiles]$ cd node01/

[oracle@websphe node01]$ cd bin/

[oracle@websphe bin]$ ./addNode.sh websphe.tech.com 8879

If Global security is enabled 


[kumar@websphe bin]$ ./addNode.sh websphe.tech.com 8879 -username bharath -password welcome321

ADMU0116I: Tool information is being logged in file

           /u03/local/opt/was/was70/profiles/node01/logs/addNode.log

ADMU0128I: Starting tool with the node01 profile

CWPKI0308I: Adding signer alias "root" to local keystore

           "ClientDefaultTrustStore" with the following SHA digest:

           5A:E1:59:6F:63:11:9A:08:B4:3E:7F:F9:84:F9:95:AA:39:FE:35:8A

CWPKI0308I: Adding signer alias "datapower" to local keystore

           "ClientDefaultTrustStore" with the following SHA digest:

           A9:BA:A4:B5:BC:26:2F:5D:2A:80:93:CA:BA:F4:31:05:F2:54:14:17

ADMU0001I: Begin federation of node Node01 with Deployment Manager at

           websphe.tech.com:8879.

ADMU0009I: Successfully connected to Deployment Manager Server:

           websphe.tech.com:8879

ADMU0507I: No servers found in configuration under:

u03/local/opt/was/was70/profiles/node01/config/cells/webspheNode01Cell/nodes/Node01/servers

ADMU2010I: Stopping all server processes for node Node01

ADMU0024I: Deleting the old backup directory.

ADMU0015I: Backing up the original cell repository.

ADMU0012I: Creating Node Agent configuration for node: Node01

ADMU0014I: Adding node Node01 configuration to cell: PRODUSG

ADMU0016I: Synchronizing configuration between node and cell.

ADMU0018I: Launching Node Agent process for node: Node01

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:   5338

ADMU0300I: The node Node01 was successfully added to the PRODUSG cell.

ADMU0306I: Note:

ADMU0302I: Any cell-level documents from the standalone PRODUSG configuration

           have not been migrated to the new cell.

ADMU0307I: You might want to:

ADMU0303I: Update the configuration on the PRODUSG Deployment Manager with

           values from the old cell-level documents.

ADMU0306I: Note:

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 PRODUSG cell using wsadmin $AdminApp

           or the Administrative Console.

ADMU0003I: Node Node01 has been successfully federated.