My dmgr successfully running but
I cannot open admin console So i follow
the below procedure then i resolve it .
[kumar@websphe bin]$
./startManager.sh
ADMU0116I: Tool information is being logged in file
/u02/local/opt/was/was80/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 7639
I Got above error
1. First I take backup of dmgr
[kumar@websphe bin]$ ./backupConfig.sh
ADMU0116I: Tool information is being logged in file
/u02/local/opt/was/was80/profiles/dmgr/logs/backupConfig.log
ADMU0128I: Starting tool with the dmgr profile
ADMU5001I: Backing up config directory
/u02/local/opt/was/was80/profiles/dmgr/config to file
/u02/local/opt/was/was80/profiles/dmgr/bin/WebSphereConfig_2014-04-27.zip
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: dmgr
ADMU2010I: Stopping all server processes for node Manager01
ADMU0510I: Server dmgr is now STOPPED
.........................................................
ADMU5002I: 1,255 files successfully backed up
[kumar@websphe bin]$
Backup also successfully done then
2. I remove admin console application using below command
[kumar@websphe bin]$ ./wsadmin.sh -f deployConsole.py remove
WASX7023E: Error creating "SOAP" connection to host
"localhost"; exception information:
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
[SOAPException: faultCode=SOAP-ENV:Protocol; msg=;
targetException=java.net.MalformedURLException]
WASX7213I: This scripting client is not connected to a server process;
please refer to the log file
/u02/local/opt/was/was80/profiles/dmgr/logs/wsadmin.traceout for additional
information.
WASX8011W: AdminTask object is not available.
WASX7303I: The following options are passed to the scripting
environment and are available as arguments that are stored in the argv
variable: "[remove]"
Removing Admin Console...
WASX7017E: Exception received while running file
"deployConsole.py"; exception information:
com.ibm.ws.scripting.ScriptingException: WASX7206W: The application management
service is not running. Application management commands will not run.
I got error because of DMGR has Down . So i start the DMGR.
[kumar@websphe bin]$ ./startManager.sh
ADMU0116I: Tool information is being logged in file
/u02/local/opt/was/was80/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 8149
Then Again i run below command .
[kumar@websphe bin]$ ./wsadmin.sh -f deployConsole.py remove
WASX7209I: Connected to process "dmgr" on node Manager01
using SOAP connector; The type of
process is: DeploymentManager
WASX7303I: The following options are passed to the scripting
environment and are available as arguments that are stored in the argv
variable: "[remove]"
Removing Admin Console...
ADMA5017I: Uninstallation of isclite started.
ADMA5104I: The server index entry for
WebSphere:cell=localhostCell01,node=Manager01 is updated successfully.
ADMA5103E: The deletion of the configuration data for isclite from the
configuration repository failed.
ADMA5011I: The cleanup of the temp directory for application isclite is
complete.
ADMA5106I: Application isclite uninstalled successfully.
WASX7017E: Exception received while running file
"deployConsole.py"; exception information:
com.ibm.websphere.management.exception.ConfigServiceException
com.ibm.ws.sm.workspace.WorkSpaceException
com.ibm.websphere.management.exception.DocumentIOException:
cells/localhostCell01/cus/isclite/cver/BASE/controlOpDefs.xml
WASX7341W: No "save" was performed before the interactive
scripting session exited; configuration changes will not be saved.
Its successfully removed admin console application.
3. I install DMGR admin console application using below command
[kumar@websphe bin]$ ./wsadmin.sh -f deployConsole.py install
WASX7209I: Connected to process "dmgr" on node Manager01
using SOAP connector; The type of
process is: DeploymentManager
WASX7303I: The following options are passed to the scripting
environment and are available as arguments that are stored in the argv
variable: "[install]"
Installing Admin Console...
Deploying isclite.ear
ADMA5016I: Installation of isclite started.
ADMA5058I: Application and module versions are validated with versions
of deployment targets.
ADMA5005I: The application isclite is configured in the WebSphere
Application Server repository.
ADMA5005I: The application isclite is configured in the WebSphere
Application Server repository.
ADMA5081I: The bootstrap address for client module is configured in the
WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package
are created.
ADMA5005I: The application isclite is configured in the WebSphere
Application Server repository.
ADMA5110I: The application isclite is installed as a hidden application
and will not be exposed via administrative interfaces such as GUI client,
wsadmin or MBean Java API. In order to
perform management operations on this application, the application name must be
known.
ADMA5005I: The application isclite is configured in the WebSphere
Application Server repository.
EJPPC0011I: Validation of the portlet.xml file is completed.
SECJ0400I: Successfully updated the application isclite with the
appContextIDForSecurity information.
CWLAA1007I: The help plug-in of the Integrated Solutions Console module
was deployed successfully.
CWLAA1001I: The Integrated Solutions Console module was deployed
successfully.
ADMA5005I: The application isclite is configured in the WebSphere
Application Server repository.
ADMA5005I: The application isclite is configured in the WebSphere
Application Server repository.
ADMA5113I: Activation plan created successfully.
ADMA5011I: The cleanup of the temp directory for application isclite is
complete.
ADMA5013I: Application isclite installed successfully.
Mapping isclite to admin_host
ADMA5075I: Editing of application isclite started.
ADMA5058I: Application and module versions are validated with versions
of deployment targets.
ADMA5005I: The application isclite is configured in the WebSphere
Application Server repository.
ADMA5005I: The application isclite is configured in the WebSphere
Application Server repository.
ADMA5005I: The application isclite is configured in the WebSphere
Application Server repository.
ADMA5113I: Activation plan created successfully.
ADMA5011I: The cleanup of the temp directory for application isclite is
complete.
ADMA5076I: Application isclite edited successfully. The application or
its web modules may require a restart when a save is performed.
Updating deployment.xml
Setting IEHS classloader to PARENT_LAST
Its Successfully installed and I
Bounce the DMGR.
[kumar@websphe bin]$ ./stopManager.sh
ADMU0116I: Tool information is being logged in file
/u02/local/opt/was/was80/profiles/dmgr/logs/dmgr/stopServer.log
ADMU0128I: Starting tool with the dmgr profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server dmgr stop completed.
[kumar@websphe bin]$ ps -ef|grep java
kumar 7536 7133 0
22:21 pts/1 00:00:00 grep java
[kumar@websphe bin]$
./startManager.sh
ADMU0116I: Tool information is being logged in file
/u02/local/opt/was/was80/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 7639
Now open the admin console.
Now Dmgr admin console working fine and i added all tasks
No comments:
Post a Comment