Table of Contents
Advertisement
Adminconsole application startup
Unlike Version 5.1, the adminconsole application now is running on the application server,
WebSphere_Portal, using the default port 10027. The following lines identify its successful
startup:
[8/2/07 11:53:00:672 EDT] 0000000a ApplicationMg A
application: adminconsole
[8/2/07 11:53:08:781 EDT] 0000000a WebGroup
Module: adminconsole.
[8/2/07 11:53:11:125 EDT] 0000000a ServletWrappe A
[/ibm/console] [EventInitializer]: Initialization successful.
Once you see these lines, you can access the adminconsole, even though the portal server is
not yet started.
Portal startup
The following line in the log signals the startup of the portal servlet:
[8/2/07 11:53:21:625 EDT] 0000000a WebGroup
Module: WebSphere Portal Server.
There is a misconception that the following line in SystemOut.log signals the Portal startup:
[8/2/07 11:58:29:609 EDT] 0000000a WsServerImpl A
WebSphere_Portal open for e-business
As a matter of fact, it only tells us that the application server is started. It does not mean that
the Portal servlet has actually started. The applications and services will be initialized after
the application server is successfully started. Failure of one or more portal services could
result in the failure of the portal servlet. Usually, failure of one or more individual portlet
applications would not affect the entire portal server, but some may affect the usage of the
server, such as the Login portlet. Failure of the Login portlet would prevent the normal login
process. As described in 4.1.5, "WebSphere Portal login process" on page 91, there are still
other ways to access the system, which in some cases are the ways to correct the problem of
the Login portlet.
The failure of PumaService shown below was caused by the WMM initialization failure
mentioned in "WMM startup" on page 120:
[8/14/07 15:11:29:672 EDT] 0000000a Servlet
init EJPFD0016E: Initialization of service failed.
com.ibm.wps.util.DataBackendException: EJPSG0015E: Data Backend Problem
java.rmi.ServerException: RemoteException occurred in server thread; nested
exception is:
com.ibm.ejs.container.CreateFailureException: ; nested exception is:
java.lang.reflect.InvocationTargetException
at
com.ibm.wps.services.puma.RealmAwareURManager.initRealms(RealmAwareURManager.java:
152)
at
com.ibm.wps.services.puma.RealmAwareURManager.<init>(RealmAwareURManager.java:91)
at com.ibm.wps.services.puma.PumaServiceImpl.init(PumaServiceImpl.java:184)
(more stacktrace)
[8/14/07 15:11:29:750 EDT] 0000000a WebExtensionP W
unavailable: Initialization of one or more services failed.
[8/14/07 15:11:29:766 EDT] 0000000a WebExtensionP E
Error]-[javax.servlet.UnavailableException: Initialization of one or more services
failed.
WSVR0200I: Starting
A
SRVE0169I: Loading Web
SRVE0242I: [adminconsole]
A
SRVE0169I: Loading Web
WSVR0001I: Server
E com.ibm.wps.engine.Servlet
Servlet portal is currently
SRVE0026E: [Servlet
Chapter 4. WebSphere Portal security
121
Advertisement
Table of Contents
Troubleshooting
