Hi Guys,
This is my first Document so please let me know if I can improve on certain areas.
The reason for this document is that we had a requirement to send out an SMS when there is a problem/error with our critical interfaces. This is mainly for the support guys that monitor the system.
The problem was that we did not have a SMS server in our environment but we did have a service provider that we would send the data of the SMS to the service provider via HTTP_AAE and they would then send out the SMS.
After I built the interface I thought it would be a good idea to share the knowledge with everyone that wanted to use the same solutions.
Im only going to cover how to retrieve the messages from the JMS queue and how to convert them into XML.
System Details:
7.31 Single Stack Patch 11
These were my Steps:
1. Component Based Alerts Setup:
Followed the below links to setup my Component Based Alerting. All this does is it takes the ICO that you
created and produces errors if there were any. These Errors are stored in a JMS
queue on SAP PI.
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/03/27/alerting-on-aaeaex
2. ESR (Enterprise Service Builder) Objects:
b. MessageTypes
c. ServiceInterfaces
d. .JavaMapping(The data Stores in the JMS queue is stored in JSON format)
e. package simpleJSONToXML;
e. Operational Mapping
2. Receiver Channel (HTTP_AAE)
3. ICO (Integrated Configuration)
{
"AdapterType":"XI_J2EE_MESSAGING_SYSTEM",
"Component":"",
"ErrCat":"XI_J2EE_ADAPTER_ENGINE",
"ErrCode":"CHANNEL_STOPPED",
"ErrLabel":"1402",
"ErrText":"Channel stopped by administrative task.",
"FromParty":"",
"FromService":" _com_ ",
"Interface":"ORDERS.ORDERS05.ORDERS05",
"MonitoringUrl":"http://webdynpro/resources/ ",
"MsgId":"4cb299e3-196f-11e4-c7fa-0000007e49e2",
"Namespace": "urn:sap-com:document:sap:idoc:messages",
"RuleId":"d42a9af9fdc53609843f5a1d9f211911",
"ScenarioId":"dir://ICO/4bbe4a73043e3a3bbc0c23b35781c7ab",
"Timestamp":"2014-08-01T11:30:56Z",
"ToParty":"",
"ToService":""
}
<XmlRoot>
<AdapterType>XI_J2EE_MESSAGING_SYSTEM</AdapterType>
<Component>af.pd1.berlux21</Component>
<ErrCat>XI_J2EE_ADAPTER_ENGINE</ErrCat>
<ErrCode>CHANNEL_STOPPED</ErrCode>
<ErrLabel>1402</ErrLabel>
<ErrText>Channel
stopped by administrative task.</ErrText>
<FromParty></FromParty>
<FromService>barloworld_com_SAPECC_QAS</FromService>
<Interface>ORDERS.ORDERS05.ORDERS05</Interface>
<MonitoringUrl>"http</MonitoringUrl>
<MsgId>4cb299e3-196f-11e4-c7fa-0000007e49e2</MsgId>
<Namespace>"urn</Namespace>
<RuleId>d42a9af9fdc53609843f5a1d9f211911</RuleId>
<ScenarioId>"dir</ScenarioId>
<Timestamp>"2014-08-01T11</Timestamp>
<ToParty>DHL</ToParty>
<ToService>SQLServer</ToService>
</XmlRoot>
If there is anything you would like to know or advice me on then please dont hesitate to se me a message or comment. Thank you taking the time to read.
References :
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/03/27/alerting-on-aaeaex
Regards,
Jannus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
12 | |
12 | |
7 | |
5 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |