There are many reason for soa server to be in warning state, I am focusing on which was cause of my soa-infra to be in warning state.
1. MDB application soa-infra is NOT connected to messaging system.
Reason:
All MDBs are used by SOA
BamActionMDB
CubeActionMDB
PeopleQueryMDB
All MDBs are used by SOA
BamActionMDB
CubeActionMDB
PeopleQueryMDB
if you have upgraded your soa server with Patchset 2 or added BAM server later in your domain. you may face this issue, and may be those queue and Topics, connection factory is not configured properly(Cross verify)
Solution is to create JMS Connection factories and topics
Look at a Domain Structure >JMS Modules >SOAJMSModule. Inhere you should create the following objects JMS connectionfactories en Topics:
jms/bpm/PeopleQueryConnectionFactory
Look at a Domain Structure >JMS Modules >SOAJMSModule. Inhere you should create the following objects JMS connectionfactories en Topics:
jms/bpm/PeopleQueryConnectionFactory
jms/bpm/CubeCommandXAConnectionFactory
jms/bpm/PeopleQueryConnectionFactory
jms/bpm/MeasurementTopic
jms/bpm/PeopleQueryTopic
jms/testfwk/TestFwkQueue
jms/Queue/NotificationSenderQueue
jms/bpm/CaseEventQueue
Hope it will help you!!
This blog gives very important info ,
ReplyDeleteOracle SOA Online Training
The images in this post are not available..can u please update..
ReplyDelete