Whenever you start a cluster member, make sure the application
server associated with that cluster member is fully started before
you take any further action. This procedure applies to a clustered
installation of WebSphere® Application Server.
About this task
Even though the status of a cluster member might show as
Started within the IBM®
InfoSphere® Information Server Web console,
or the status returned by the serverStatus command
indicates that the application server is STARTED, it might still not
be available for use by InfoSphere Information Server until
the InfoSphere Information Server applications
are fully initialized. The InfoSphere Information Server applications
typically complete initialization within two to four minutes after
the application server status first changes to Started.
Procedure
Follow this procedure to determine if the InfoSphere Information Server applications
have completed initialization.
- Log in to each computer that hosts a cluster member.
- On the computer, locate the SystemOut.log file.
The file can be found in the following directory:
WAS_install_path/profiles/profile/logs/serverx
- Check the SystemOut.log file in each
server instance:
- In the SystemOut.log file, in the
timeframe in which the application server is being started, look for
the following line. This line indicates that InfoSphere Information Server is
fully initialized and ready for operation:
Initialization: EJB Initializations complete
The SystemOut.log file
might contain log entries that span multiple application server restarts.
For this reason, the file might contain multiple lines that read EJB
Initializations complete
. Use the timestamps of the log entries
to determine if this message is associated with the application server
startup that you want.
- Repeat this procedure for each computer that hosts a cluster
member.
What to do next
InfoSphere Information Server can
be used as soon as one cluster member is fully initialized. However,
for best performance, wait until all members of the cluster are fully
initialized. Allowing all the members of the cluster to initialize
fully also maximizes the number of members that can take over in case
of a failover.