Create profiles with command line

最新推荐文章于 2021-04-02 20:27:31 发布

congpang5009

最新推荐文章于 2021-04-02 20:27:31 发布

阅读量195

点赞数

创建Deployment manager:

D:IBMWebSphereAppServerbin>manageprofiles -create -profileName Dmgr -profilePath d:IBMWebSphereAppServe
rprofilesDmgr -templatePath D:IBMWebSphereAppServerprofileTemplatesdmgr -cellName J5EECell -nodeName dm
gr -hostName J5EE
INSTCONFSUCCESS: 成功：概要文件 Dmgr 现在存在。有关此概要文件的更多信息，请参阅 d:
filesDmgr/logs/AboutThisProfile.txt。

在该机器上再创建一个Node:

D:IBMWebSphereAppServerbin>manageprofiles -create -profileName j5ee -profilePath d:IBMWebSphereAppServe
rprofilesj5ee -templatePath D:IBMWebSphereAppServerprofileTemplatesdefault -nodeName
j5eeNode -hostName J5EE
INSTCONFSUCCESS: 成功：概要文件 j5ee 现在存在。有关此概要文件的更多信息，请参阅 d:
filesj5ee/logs/AboutThisProfile.txt。

[@more@]

创建Deployment manager:

在该机器上再创建一个Node:

联合:

D:IBMWebSphereAppServerbin>addNode J5EE -profileName j5ee -registerservice

在Linux 上联合接点时,由于时区不同造成的问题:

sles:/opt/IBM/WebSphere/AppServer/bin # date
Mon Apr 23 00:54:51 BST 2007
sles:/opt/IBM/WebSphere/AppServer/bin # date
Mon Apr 23 00:01:44 BST 2007
sles:/opt/IBM/WebSphere/AppServer/bin # ./addNode.sh J5EE -profileName sles
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/sles/logs/addNode.log
ADMU0128I: Starting tool with the sles profile
ADMU0001I: Begin federation of node slesNode with Deployment Manager at
J5EE:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: J5EE:8879
ADMU0124I: The system clock of the new node (23-Apr-2007 00:02:01) is not
synchronized with that of the deployment manager (22-Apr-2007
17:02:02).
ADMU0125E: Change the clock of the new node to be within 5 minutes of the clock
of the deployment manager.
ADMU0111E: Program exiting with error:
com.ibm.ws.management.tools.DoNotDoAddNodeException
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file:
/opt/IBM/WebSphere/AppServer/profiles/sles/logs/addNode.log
sles:/opt/IBM/WebSphere/AppServer/bin # cat /opt/IBM/WebSphere/AppServer/profiles/sles/logs/addNode.log
************ Start Display Current Environment ************
Host Operating System is Linux, version 2.6.16.21-0.8-default
Java version = J2RE 1.4.2 IBM build cxia32142sr1w-20041028 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = /opt/IBM/WebSphere/AppServer
user.install.root = /opt/IBM/WebSphere/AppServer/profiles/sles
Java Home = /opt/IBM/WebSphere/AppServer/java/bin/../jre
ws.ext.dirs = /opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime:/opt/mqm/java/lib:/opt/wemps/lib
Classpath = /opt/IBM/WebSphere/AppServer/profiles/sles/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/j2ee.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar
Java Library path = /opt/IBM/WebSphere/AppServer/java/bin/../jre/bin:/opt/IBM/WebSphere/AppServer/java/jre/bin/classic:/opt/IBM/WebSphere/AppServer/java/jre/bin:/opt/IBM/WebSphere/AppServer/bin:/opt/mqm/java/lib:/opt/wemps/lib:/usr/lib
Current trace specification = *=info:com.ibm.ws.management.tools.*=all
************* End Display Current Environment *************
[23/04/07 00:54:12:849 BST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.ws.management.tools.*=all.
[23/04/07 00:54:12:857 BST] 0000000a AdminTool 3 Our guess at the profile dir: /opt/IBM/WebSphere/AppServer/profiles/sles
[23/04/07 00:54:12:999 BST] 0000000a AdminTool A ADMU0128I: Starting tool with the sles profile
[23/04/07 00:54:13:000 BST] 0000000a AdminTool 3 executing utility with arguments: /opt/IBM/WebSphere/AppServer/profiles/sles/config SLESNode01Cell slesNode J5EE
[23/04/07 00:54:13:567 BST] 0000000a AdminTool A ADMU0001I: Begin federation of node slesNode with Deployment Manager at J5EE:8879.
[23/04/07 00:54:15:129 BST] 0000000a AbstractNodeC 3 DeploymentManager handle is ==> WebSphere:cell=J5EECell,diagnosticProvider=true,mbeanIdentifier=DeploymentManager,name=DeploymentManager,node=dmgr,platform=common,process=dmgr,spec=1.0,type=DeploymentManager,version=6.1.0.0
[23/04/07 00:54:15:129 BST] 0000000a AdminTool A ADMU0009I: Successfully connected to Deployment Manager Server: J5EE:8879
[23/04/07 00:54:15:366 BST] 0000000a AbstractNodeC 3 ConfigRepository handle is ==> WebSphere:cell=J5EECell,mbeanIdentifier=repository,name=repository,node=dmgr,platform=common,process=dmgr,spec=1.0,type=ConfigRepository,version=5.0
[23/04/07 00:54:19:457 BST] 0000000a AbstractNodeC 3 Server handle is ==> WebSphere:cell=J5EECell,j2eeType=J2EEServer,mbeanIdentifier=cells/J5EECell/nodes/dmgr/servers/dmgr/server.xml#Server_1,name=dmgr,node=dmgr,platform=proxy,process=dmgr,processType=DeploymentManager,spec=1.0,type=Server,version=6.1.0.0
[23/04/07 00:54:19:897 BST] 0000000a AbstractNodeC 3 JVM handle is ==> WebSphere:J2EEServer=dmgr,cell=J5EECell,j2eeType=JVM,mbeanIdentifier=JVM,name=JVM,node=dmgr,platform=proxy,process=dmgr,spec=1.0,type=JVM,version=6.1.0.0
[23/04/07 00:54:20:327 BST] 0000000a AbstractNodeC 3 JVM handle is ==> WebSphere:J2EEServer=dmgr,cell=J5EECell,j2eeType=JVM,mbeanIdentifier=JVM,name=JVM,node=dmgr,platform=proxy,process=dmgr,spec=1.0,type=JVM,version=6.1.0.0
[23/04/07 00:54:20:814 BST] 0000000a AdminTool A ADMU0124I: The system clock of the new node (23-Apr-2007 00:54:20) is not synchronized with that of the deployment manager (22-Apr-2007 16:59:18).
[23/04/07 00:54:21:006 BST] 0000000a AdminTool A ADMU0125E: Change the clock of the new node to be within 5 minutes of the clock of the deployment manager.
[23/04/07 00:54:21:008 BST] 0000000a AdminTool E ADMU0111E: Program exiting with error: com.ibm.ws.management.tools.DoNotDoAddNodeException
at com.ibm.ws.management.tools.NodeFederationUtility.failAddNodeBecauseClocksNotInSync(NodeFederationUtility.java:1026)
at com.ibm.ws.management.tools.NodeFederationUtility.doCheckIfAddNodeIsOkToRun(NodeFederationUtility.java:821)
at com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:403)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:209)
at com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFederationUtility.java:224)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)

[23/04/07 00:54:21:128 BST] 0000000a AdminTool A ADMU0111E: Program exiting with error: com.ibm.ws.management.tools.DoNotDoAddNodeException
at com.ibm.ws.management.tools.NodeFederationUtility.failAddNodeBecauseClocksNotInSync(NodeFederationUtility.java:1026)
at com.ibm.ws.management.tools.NodeFederationUtility.doCheckIfAddNodeIsOkToRun(NodeFederationUtility.java:821)
at com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:403)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:209)
at com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFederationUtility.java:224)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)

[23/04/07 00:54:21:129 BST] 0000000a AdminTool 3 Returning from auxiliary method issueMessage with return code: 111
[23/04/07 00:54:21:243 BST] 0000000a AdminTool A ADMU1211I: To obtain a full trace of the failure, use the -trace option.
[23/04/07 00:54:21:410 BST] 0000000a AdminTool A ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/sles/logs/addNode.log
[23/04/07 00:54:21:411 BST] 0000000a AdminTool 3 Returning from auxiliary method issueMessage with return code: 211
[23/04/07 00:54:21:411 BST] 0000000a AdminTool 3 Returning from executeUtility method with return code: -1
************ Start Display Current Environment ************
Host Operating System is Linux, version 2.6.16.21-0.8-default
Java version = J2RE 1.4.2 IBM build cxia32142sr1w-20041028 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = /opt/IBM/WebSphere/AppServer
user.install.root = /opt/IBM/WebSphere/AppServer/profiles/sles
Java Home = /opt/IBM/WebSphere/AppServer/java/bin/../jre
ws.ext.dirs = /opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime:/opt/mqm/java/lib:/opt/wemps/lib
Classpath = /opt/IBM/WebSphere/AppServer/profiles/sles/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/j2ee.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar
Java Library path = /opt/IBM/WebSphere/AppServer/java/bin/../jre/bin:/opt/IBM/WebSphere/AppServer/java/jre/bin/classic:/opt/IBM/WebSphere/AppServer/java/jre/bin:/opt/IBM/WebSphere/AppServer/bin:/opt/mqm/java/lib:/opt/wemps/lib:/usr/lib
Current trace specification = *=info:com.ibm.ws.management.tools.*=all
************* End Display Current Environment *************
[23/04/07 00:01:54:344 BST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.ws.management.tools.*=all.
[23/04/07 00:01:54:352 BST] 0000000a AdminTool 3 Our guess at the profile dir: /opt/IBM/WebSphere/AppServer/profiles/sles
[23/04/07 00:01:54:504 BST] 0000000a AdminTool A ADMU0128I: Starting tool with the sles profile
[23/04/07 00:01:54:505 BST] 0000000a AdminTool 3 executing utility with arguments: /opt/IBM/WebSphere/AppServer/profiles/sles/config SLESNode01Cell slesNode J5EE
[23/04/07 00:01:55:146 BST] 0000000a AdminTool A ADMU0001I: Begin federation of node slesNode with Deployment Manager at J5EE:8879.
[23/04/07 00:01:56:723 BST] 0000000a AbstractNodeC 3 DeploymentManager handle is ==> WebSphere:cell=J5EECell,diagnosticProvider=true,mbeanIdentifier=DeploymentManager,name=DeploymentManager,node=dmgr,platform=common,process=dmgr,spec=1.0,type=DeploymentManager,version=6.1.0.0
[23/04/07 00:01:56:723 BST] 0000000a AdminTool A ADMU0009I: Successfully connected to Deployment Manager Server: J5EE:8879
[23/04/07 00:01:56:960 BST] 0000000a AbstractNodeC 3 ConfigRepository handle is ==> WebSphere:cell=J5EECell,mbeanIdentifier=repository,name=repository,node=dmgr,platform=common,process=dmgr,spec=1.0,type=ConfigRepository,version=5.0
[23/04/07 00:02:01:062 BST] 0000000a AbstractNodeC 3 Server handle is ==> WebSphere:cell=J5EECell,j2eeType=J2EEServer,mbeanIdentifier=cells/J5EECell/nodes/dmgr/servers/dmgr/server.xml#Server_1,name=dmgr,node=dmgr,platform=proxy,process=dmgr,processType=DeploymentManager,spec=1.0,type=Server,version=6.1.0.0
[23/04/07 00:02:01:463 BST] 0000000a AbstractNodeC 3 JVM handle is ==> WebSphere:J2EEServer=dmgr,cell=J5EECell,j2eeType=JVM,mbeanIdentifier=JVM,name=JVM,node=dmgr,platform=proxy,process=dmgr,spec=1.0,type=JVM,version=6.1.0.0
[23/04/07 00:02:01:901 BST] 0000000a AbstractNodeC 3 JVM handle is ==> WebSphere:J2EEServer=dmgr,cell=J5EECell,j2eeType=JVM,mbeanIdentifier=JVM,name=JVM,node=dmgr,platform=proxy,process=dmgr,spec=1.0,type=JVM,version=6.1.0.0
[23/04/07 00:02:02:384 BST] 0000000a AdminTool A ADMU0124I: The system clock of the new node (23-Apr-2007 00:02:01) is not synchronized with that of the deployment manager (22-Apr-2007 17:02:02).
[23/04/07 00:02:02:526 BST] 0000000a AdminTool A ADMU0125E: Change the clock of the new node to be within 5 minutes of the clock of the deployment manager.
[23/04/07 00:02:02:527 BST] 0000000a AdminTool E ADMU0111E: Program exiting with error: com.ibm.ws.management.tools.DoNotDoAddNodeException
at com.ibm.ws.management.tools.NodeFederationUtility.failAddNodeBecauseClocksNotInSync(NodeFederationUtility.java:1026)
at com.ibm.ws.management.tools.NodeFederationUtility.doCheckIfAddNodeIsOkToRun(NodeFederationUtility.java:821)
at com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:403)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:209)
at com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFederationUtility.java:224)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)

[23/04/07 00:02:02:656 BST] 0000000a AdminTool A ADMU0111E: Program exiting with error: com.ibm.ws.management.tools.DoNotDoAddNodeException
at com.ibm.ws.management.tools.NodeFederationUtility.failAddNodeBecauseClocksNotInSync(NodeFederationUtility.java:1026)
at com.ibm.ws.management.tools.NodeFederationUtility.doCheckIfAddNodeIsOkToRun(NodeFederationUtility.java:821)
at com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:403)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:209)
at com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFederationUtility.java:224)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)

[23/04/07 00:02:02:657 BST] 0000000a AdminTool 3 Returning from auxiliary method issueMessage with return code: 111
[23/04/07 00:02:02:780 BST] 0000000a AdminTool A ADMU1211I: To obtain a full trace of the failure, use the -trace option.
[23/04/07 00:02:03:010 BST] 0000000a AdminTool A ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/sles/logs/addNode.log
[23/04/07 00:02:03:011 BST] 0000000a AdminTool 3 Returning from auxiliary method issueMessage with return code: 211
[23/04/07 00:02:03:011 BST] 0000000a AdminTool 3 Returning from executeUtility method with return code: -1
sles:/opt/IBM/WebSphere/AppServer/bin # date

根据时区，重新修改时间：中国时间00:02 英国时间17:02

Mon Apr 23 00:02:36 BST 2007
sles:/opt/IBM/WebSphere/AppServer/bin # date
Sun Apr 22 17:04:57 BST 2007
sles:/opt/IBM/WebSphere/AppServer/bin # ./addNode.sh J5EE -profileName sles
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/sles/logs/addNode.log
ADMU0128I: Starting tool with the sles profile
ADMU0001I: Begin federation of node slesNode with Deployment Manager at
J5EE:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: J5EE:8879
ADMU0507I: No servers found in configuration under:
/opt/IBM/WebSphere/AppServer/profiles/sles/config/cells/SLESNode01Cell/nodes/slesNode/servers
ADMU2010I: Stopping all server processes for node slesNode
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: slesNode
ADMU0014I: Adding node slesNode configuration to cell: J5EECell
ADMU0016I: Synchronizing configuration between node and cell.
oldVarTable: {}
newVarTable: {}
diffTable: {}
ADMU0018I: Launching Node Agent process for node: slesNode
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:
7237
ADMU9990I:
ADMU0300I: Congratulations! Your node slesNode has been successfully
incorporated into the J5EECell cell.
ADMU9990I:
ADMU0306I: Be aware:
ADMU0302I: Any cell-level documents from the standalone SLESNode01Cell
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the J5EECell 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 J5EECell cell using wsadmin $AdminApp
or the Administrative Console.
ADMU9990I:
ADMU0003I: Node slesNode has been successfully federated.