Your application or website rely on your database to deliver information about products and services to your customers. You can’t afford to have your database lose performance, lose availability or become unresponsive – even for just a few minutes.
Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator.CLUSTERWAS>cd C:\Program Files\IBM\WebSp here\AppServer\bin C:\Program Files\IBM\WebSphere\AppServer\bin>addNode.bat 172.17.42.23 ADMU0116I: Tool information is being logged in file C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\addNode.log ADMU0128I: Starting tool with the AppSrv01 profile ADMU0001I: Begin federation of node Wascluster1Node01 with Deployment Manager at 172.17.42.23:8879. ADMU0009I: Successfully connected to Deployment Manager Server: 172.17.42.23:8879 ADMU0505I: Servers found in configuration: ADMU0506I: Server name: server1 ADMU2010I: Stopping all server processes for node Wascluster1Node01 ADMU7702I: Because server1 is registered to run as a Windows Service, the request to stop this server will be completed by stopping the associated Windows Service. ADMU0116I: Tool information is being logged in file C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\stopServ er.log ADMU0128I: Starting tool with the AppSrv01 profile ADMU3100I: Reading configuration for server: server1 ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server server1 stop completed. ADMU0024I: Deleting the old backup directory. ADMU0015I: Backing up the original cell repository. ADMU0012I: Creating Node Agent configuration for node: Wascluster1Node01 ADMU0014I: Adding node Wascluster1Node01 configuration to cell: wasmainCell01 ADMU0016I: Synchronizing configuration between node and cell. ADMU0018I: Launching Node Agent process for node: Wascluster1Node01 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: 3672 ADMU9990I: ADMU0300I: Congratulations! Your node Wascluster1Node01 has been successfully incorporated into the wasmainCell01 cell. ADMU9990I: ADMU0306I: Be aware: ADMU0302I: Any cell-level documents from the standalone Wascluster1Node01Cell configuration have not been migrated to the new cell. ADMU0307I: You might want to: ADMU0303I: Update the configuration on the wasmainCell01 Deployment Manager with values from the old cell-level documents. ADMU9990I: ADMU0306I: Be aware: 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 wasmainCell01 cell using wsadmin $AdminApp or the Administrative Console. ADMU9990I: ADMU0003I: Node Wascluster1Node01 has been successfully federated. C:\Program Files\IBM\WebSphere\AppServer\bin>
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
Join the community of 500,000 technology professionals and ask your questions.