Filter
Top Products
v If no error can be found, look for other symptoms in the log file.
2.
Find the first occurrence of the error in the log file. You will either see an error
message or an error exception with a stack trace.
3. Review the proper error message. It will be either from WebSphere Application
Server or from the application that caught and properly handled the exception.
Review the message and investigate.
4. Check the Java exception with the stack trace:
v Check the stack trace and follow the classes, with the package names, and
try to identify them.
v If all the classes belong to the application server and you can easily identify
them by package names, you probably have a configuration error.
v Try to detect the source of the problem based on class names, which are
usually very descriptive.
v If you find any class in the stack trace that belongs to the enterprise
application, you need to check the application.
SystemOut.log
successful startup breakdown:
Administration service
AdminInitiali A ADMN0015I: AdminService initialized
Secure Authentication Services (LDAP)
Configuration A SECJ0215I: Successfully set JAAS login provider
configuration class to
com.ibm.ws.security.auth.login.Configuration.
SecurityDM I SECJ0231I: The Security component’s FFDC Diagnostic Module
com.ibm.ws.security.core.SecurityDM
registered successfully: true.
SecurityCompo I SECJ0309I: Java 2 Security is disabled.
SecurityCompo I SECJ0212I: WCCM JAAS configuration information successfully
pushed to login provider class.
SecurityCompo I SECJ0240I: Security service initialization completed
successfully
SASRas A JSAS0001I: Security configuration initialized.
SASRas A JSAS0002I: Authentication protocol: CSIV2/IBM
SASRas A JSAS0003I: Authentication mechanism: LTPA
SASRas A JSAS0004I: Principal name: todaix05.think.lab.austin.-
ibm.com:389/wasadmin
SASRas A JSAS0005I: SecurityCurrent registered.
SASRas A JSAS0006I: Security connection interceptor initialized.
SASRas A JSAS0007I: Client request interceptor registered.
SASRas A JSAS0008I: Server request interceptor registered.
SASRas A JSAS0009I: IOR interceptor registered.
Map Tivoli Intelligent Orchestrator resource references
ResourceMgrIm I WSVR0049I: Binding DataSource as jdbc/KulaDB
ResourceMgrIm I WSVR0049I: Binding Default Datasource as
DefaultDatasource
ResourceMgrIm I WSVR0049I: Binding QueueConnectionFactory as
jms/factory/QueueConnectionFactory
ResourceMgrIm I WSVR0049I: Binding DeploymentEnginePrivateRequests
as jms/factory/DeploymentEngine/
PrivateRequests
ResourceMgrIm I WSVR0049I: Binding DeploymentEngineHighLevelOutput
as jms/factory/DeploymentEngine/
HighLevelOutput
ResourceMgrIm I WSVR0049I: Binding TopicConnectionFactory as
jms/factory/TopicConnectionFactory
ResourceMgrIm I WSVR0049I: Binding DeploymentEngineHighLevelOutputForTEC
as jms/factory/DeploymentEngine/HighLevelOutputForTEC
ResourceMgrIm I WSVR0049I: Binding DeploymentEnginePrivateRequests
as queue/thinkcontrol/DeploymentEngine/PrivateRequests
ResourceMgrIm I WSVR0049I: Binding DeploymentEngineHighLevelOutput
as topic/thinkcontrol/DeploymentEngine/HighLevelOutput
ResourceMgrIm I WSVR0049I: Binding ThinkControlInternalMessages as
topic/thinkcontrol/Invocation
Chapter 2. Problem determination essentials for Tivoli Intelligent Orchestrator 15