Hi All,
In this post I will try to demonstrate the use of composite sensors and this will help all of us to understand its importance.
Composite sensors helps to track required fields from the messages.
Ex: StudentID from StudentInfo Payload
We define composite sensors on service and reference binding components or
On service components that have business event subscriptions.
Composite sensors enable us to perform below tasks:
1. Monitor incoming and outgoing messages.
2. Create Search box for composite sensor details in the instances page of a SOA composite application in Enterprise Manager . This helps us to easily locate a particular instance.
3. Publish to JMS with data computed from incoming and outgoing messages.
4. Track composite instances initiated through business event subscriptions.
During runtime, composite sensor data is persisted in the database.
Demonstration:
1. Create a xsd as below:
6. Select StudentID click on apply and ok.
4. Go to Dashboard in em console under Add Fields we will be able to see the composite sensor which we created 'StudentID'
6. Hola! here we obtain the same instance from our previous test case.
In this post I will try to demonstrate the use of composite sensors and this will help all of us to understand its importance.
Composite sensors helps to track required fields from the messages.
Ex: StudentID from StudentInfo Payload
We define composite sensors on service and reference binding components or
On service components that have business event subscriptions.
Composite sensors enable us to perform below tasks:
1. Monitor incoming and outgoing messages.
2. Create Search box for composite sensor details in the instances page of a SOA composite application in Enterprise Manager . This helps us to easily locate a particular instance.
3. Publish to JMS with data computed from incoming and outgoing messages.
4. Track composite instances initiated through business event subscriptions.
During runtime, composite sensor data is persisted in the database.
Demonstration:
1. Create a xsd as below:
2. Build OneWay bpel process accepting Student as input; expose it as soap service
In Composite.xml Choose the higlighted icon for creating sensors.
3. Choose as below
4. Create StudentID as the field to be tracked in the input payload ; under expression select variable and choose StudentID.
5. Choose EM console to manage sensors features.
6. Select StudentID click on apply and ok.
7. Save all your composite and deploy to the em console
Testing:
1. Provide inputs and test the webservice
2. Launch Flowtrace
3. We can see a fields under Sensors Tab
4. Go to Dashboard in em console under Add Fields we will be able to see the composite sensor which we created 'StudentID'
5. Choose that Provide the StudentID which we entered earlier or from any previous test searches
6. Hola! here we obtain the same instance from our previous test case.
That's all!
We can easily track the instances by setting composite sensors on the required fields either from the payloads at service/reference sides and also on the components which are subscribed to events.
Let's keep exploring SOA! :)
Drop in your comments for any doubts .. :)
Will be happy to help!
No comments:
Post a Comment