Tuesday 10 March 2015

Federating Application Server with Dmgr Profile using addNode Command

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>addNode.bat was.local.com 8879 -conntype soap -profileName AppSrv01 -username wasadmin -password wasadmin


The process carried when you run the addNode Command is
ADMU0116I: Tool information is being logged in file
C:\Progra~1\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
CWPKI0308I: Adding signer alias “CN=WASCell.local.com, ” to local
keystore “ClientDefaultTrustStore” with the following SHA digest:
BF:9B:69:F2:3A:88:53:A2:D7:6B:7F:8A:02:E5:F7:7A:BE:2D:98:22
CWPKI0308I: Adding signer alias “default” to local keystore
“ClientDefaultTrustStore” with the following SHA digest:
F9:E9:87:BC:ED:CA:B3:64:53:71:F9:1B:13:19:AA:C8:55:2C:88:A0
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 AppSrv01node with Deployment Manager at
dmgr01:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: Dmgr01:8879
ADMU0507I: No servers found in configuration under:
C:\Progra~1\IBM\WebSphere\AppServer\profiles\AppSrv01\config/cells/WASCell/nodes/AppSrv01node/servers
ADMU2010I: Stopping all server processes for node AppSrv01node
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: AppSrv01node
ADMU0014I: Adding node Appsrv01node configuration to cell: WASCell
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: AppSrv01node
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:
6308
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: nodeagent
ADMU0300I: The node AppSrv01node was successfully added to the WASCell
cell.
ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone WASCell
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the WASCell 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 WASCell cell using
wsadmin $AdminApp or the Administrative Console.
ADMU0003I: Node AppSrv01node has been successfully federated.


For UNIX Flavours:

/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/bin>./addNode.sh was.local.com 8879 -conntype soap -profileName AppSrv01 -userName wasadmin -password wasadmin


NOTE: 1.HostName of DMGR is was.local.com
           2.SOAP port of DMGR is 8879
           3. we can use below options with addNode command 
                       [-includebuses] [-startingport <portnumber>] [-portprops
                       <qualified-filename>] [-nodeagentshortname <name>] [-nodegroupname
                      <name>] [-registerservice] [-serviceusername <name>]
                       [-servicepassword <password>] [-coregroupname <name>] [-noagent]
                       [-statusport <port>] [-quiet] [-nowait] [-logfile <filename>]
                       [-replacelog] [-trace] [-username <username>] [-password <pwd>]
                       [-localusername <localusername>] [-localpassword <localpassword>]
                       [-profileName <profile>] [-excludesecuritydomains] [-asExistingNode]
                       [-help]

No comments:

Post a Comment