Solved

Admin console not opening on websphere application server

Posted on 2009-05-07
3
2,781 Views
Last Modified: 2013-12-11
Dear Experts,
I have installed two websphere application server on two different servers & a deployment manager on a third server for the purpose of clustering. Before federating WAS with deployment manager, the admin. console & samples gallery pages of application server open up, but after federation both the pages are not opening up.Please provide me a solution.
I have attached one of my server console below.
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>

Open in new window

0
Comment
Question by:pageast
3 Comments
 
LVL 41

Expert Comment

by:HonorGod
ID: 24327986
When you federate an application server into a deployment manager, the administration application is removed.  So, in order to administer any federated, or clustered application server, you must use the administration console on the Deployment Manager.

Does that make sense?
0
 

Accepted Solution

by:
fightinghippo earned 500 total points
ID: 24341961
if you want the samples to be included you shoul dhave used addnode -includeApps option.
The reason for federating the nodes to deployment manager is to centrally manage all the servers from the deployment manager so once you do addnod/ federation you cannot access individual profiles using their own admin consoles. You have to go to the deployment managers admin console. After you log in slick application server and then you should see the  list of all the servers for your federated nodes. hope this helps
0
 

Author Comment

by:pageast
ID: 24364081
thank you very much
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Most of the developers using Tomcat find it easy to configure the datasource in Server.xml and use the JNDI name in the code to get the connection.  So the default connection pool using DBCP (or any other framework) is made available and the life go…
There are numerous questions about how to setup an IBM HTTP Server to be administered from WebSphere Application Server administrative console. I do hope this article will wrap things up and become a reference for this task. You need three things…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

827 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question