SAP AG.co in Will Give information of SAP related meterials Like SAP Platform and Operation,,SAP Security , SAP Enterprise Portal (EP), ,SAP Knowledge Management (KW), SAP Business Intelligence (BI), Exchange Infrastructure (XI),Application Server, Mobile (MI), Master Data Management MDM, Composit Appications Frame work,Web Dynpros,OOPABAP,Blog,Intergration Bulder, Integration Repository (IB),Integration Directory (ID).System Landscape Directory (SLD), And Adopter Configuration like File to File,File to JDBC, File to IDoc, File Content Convertion, RFC, HTTP,SOAP,XI Interview Questions,Xi Sertification Questions, and many more about SAP Netweaver Platform XI Training And Tutorial and XI interview Questions ..

SAP Exchange Infrastructure Tutorials

SAP XI Exercises BPM async-sync

Exercise 5 – Business Process Management – Async/Sync bridge

•  Interface mapping: PO_abs__ZBAPI_PO_CREATE

•  Receiver agreement (communication channel): XIWS_RFC_receiver

•  Create a new receiver communication channel for the business system XIWS_legacy_BS_[XX], named ‘POResp_file_receiver':

•  Adapter type: File

•  Direction: Receiver

•  Adapter Engine: Integration Server

•  Target directory: D:/workshop/group[XX]

•  File Name scheme: POResponse.xml

•  File Construction mode: ‘Add message ID' (this will append the message ID to the name of the file being created).

•  Create a new receiver determination from BPM to the file adapter:

•  Sender service: XIWS_PO_async_sync_XX

•  Sender interface: PurchaseOrderResp_async_abstract

•  Sender namespace: urn:xiworkshop:groupXX:webapp

•  Receiver service: XIWS_legacy_BS_[XX]

•  Inbound interface: PurchaseOrderResp_in_async

•  Interface mapping: none

•  Receiver agreement (communication channel): POResp_file_receiver

•  Activate all objects

Step 4 – Test

The testing procedure will be similar to the one used in exercise 3.

•  Use the plain HTTP client to send a request asynchronously:

•  Sender service: XIWS_web_purchasing_XX

•  Sender interface: PurchaseOrder_out_async_BPM

•  Sender namespace: urn:xiworkshop:groupXX:webapp

•  QoS: EO

•  Payload: use the contents of file ‘PORequest_template.xml' and replace the vendor number with your own.

•  Examine your message in transaction SXMB_MONI. Notice that the message was sent to the process engine, and that the status of the workflow is ‘completed'.

•  Drill down to the workflow details

•  Display the workflow log

•  Display the technical details of the workflow log

•  Display the graphical details of the workflow log

•  Examine the other messages in the monitor. In total there are 4 messages:

•  Asynchronous request HTTP à BPM

•  Synchronous request BPM à R/3

•  Synchronous response R/3 à BPM

•  Asynchronous response BPM à file

•  Open your folder \\<hostname>\workshop\groupXX . There you should find a file containing the purchase order response.

•  Verify in the R/3 system (transaction ME23) that the PO was created.

Step 5 (advanced) – Alert management

We will now enhance the process, such that if the PO is not created successfully, then an alert will be triggered.

•  Add a Switch step to your process, in order to determine if the PO response contains a PO number

•  Step Name: PO Success

•  Branch 1 à outcome name: success

•  Branch 1 à condition: use the condition editor to check for the existence of the field ‘PurchaseOrder': “PO_resp./p2:PurchaseOrderResponse/PurchaseOrder EX “

•  Within the switch step, leave the Branch 1 (outcome name: success) empty. In our case no action will be taken in case of successful PO creation. Of course, some additional process steps could be inserted here.

•  In the bottom branch (BranchOtherwise), insert a control step:

•  Step name: ‘No PO created'

•  Action: ‘throw alert'

•  Alert Category: ‘XIWSALERT'

•  Alert Message: “GROUP XX: PO was not created” (or some other text of your choice.)

•  The completed process should look like this:

•  Check, save and activate your process.

•  Before testing, go to the alert inbox and subscribe to the alert category ‘XIWSALERT'. The instructor will demonstrate how to create an alert category in the system. For this exercise, it is not practical for every group to create a new alert category at the same time, because this would create a locking situation. Therefore, XIWSALERT will be used for everybody. In real life, you could create your own alert category and assign a single recipient to it.

•  Go to the alert inbox (instructor will provide the URL): http://<host>:<port>/sap/bc/bsp/sap/ALERTINBOX/index.htm

•  Go to ‘Alert subscription' and subscribe to the alert category ‘Alert for PO creation' (classification: ‘alerts for XI workshop')

•  Go back to the ‘Alert Inbox' screen.

•  Now send a PO request with erroneous data (for example, a bad material number).

•  Monitor your message in SXMB_MONI. In the workflow log, verify that the step ‘Trigger a process alert in the background' occurred. Under goto à ‘list with technical details', notice the instance number for the workflow object.

•  In order for the alerts to be collected and delivered, two programs must be run. The instructor will execute them manually.

•  SXMSALERT_PROCESS_DATA_GET (to collect XI-specific alerts).

•  RSALERTPROC (for the delivery of alerts to the recipients).

•  Refresh your alert inbox. Now you should see the alert corresponding to the process instance. Look at the long text to ensure that the alert is yours. Again, for exercise purposes we are all subscribing to the same alert category, so you will receive everybody's alerts.

•  Under ‘Subsequent Action', you will find a link to your shared folder \\<hostname>\workshop\groupXX . Look at the latest message to view the error message.

Note: in this exercise we have demonstrated a simple use of alert management. In general, alerts should be used to monitor technical errors only. In the case of an application error like this one, the correct approach would be to generate a new message, which would be considered a negative application acknowledgement.
Appendix: naming conventions and terminology

Exercise 6

Previous

 Back to SAP XI Tutorials