krishna.moorthyp

11 Posts

Probably think of following scenarios:
• How to trace an atomic level of any transaction in a real-time?
• Operational Metrics of large volume of events processed in any company
• How to find out real-time traffic in any Highway?
• How to trace the CO2 emission in real-time?
• How to trace my shipment in a heterogeneous landscape?
• How to get a feel of consumer sentiments?
• How to find the electricity consumption in an AMI/Smart Metering world?
• Mission Critical Alerts/Notifications
• Etc
In order to achieve above requirements, there is good news for all of us from SAP. I.e. nothing but one of the highlights of today's keynote - i.e. SAP Business Object Event Insight 4.0 (Internally termed as Live Enterprise) - new, fresh offering from SAP on event management!!. Looks damn cool - definitely a real real-time event management solution.
SAP Event Insight is a complex event processing engine helps in managing the events in a heterogeneous landscape. It will help in collecting, managing & publishing the business events into an integrated framework. SAP Event Insight will help in providing a "Single View" on event Data. So at the end of the day, business user can easily evaluate the atomic details of the series of happenings in a given landscape using SAP Event Insight. In summary, SAP Event Insight will provide the comprehensive outlook of the series of events.
For more on SAP Event Insight and its features, it is prefer to be part of TechEd sessions - PMC106  , PMC164 .Now think a case, where I need to use these events to get the business value using analytics and business process /rules. So as per the information gathered and whatever demos seen, Event Management + Business Process/Rule Management + Business Intelligence will help in achieving Operational BI solution. Good to be part of POD29

Also there is a very good demo in SCN:SAP BusinessObjects Event Insight XI 4.0 with Sybase CEP: Enabling Operational BI Oil & Gas
After watching the demo, I thought let me put my understanding of SAP Event Insight here. So I am eagerly looking for SAP Event Insight Ramp-up program (expected to be available for Ramp-up during end of Nov 2010). What about you?

Stop by for a 1 Hr early morning (8:00 am to 9:00 am) lecture session - PMC237 on 21st Oct 2010 at session room- Lido 3001A. In the session let us discuss about optimized business outcome for Master Data processing in an Organization using SAP NetWeaver platform. It will also help in understanding the collective result of SAP MDM Solution enhanced & powered by SAP NW BPM.

             Abstract:

The objective of this session is to showcase seamless collaborative master data processing in a heterogeneous landscape using SAP NetWeaver BPM. Also we will discuss about complex interrelationship between Master Data and Processes. During the journey, we will discuss following two scenarios:

  1.  Seamless Customer Master Data Processing using SAP NetWeaver BPM, SAP NetWeaver PI, SAP NetWeaver MDM, SAP ERP Central Component (SAP ECC), SAP NetWeaver Portal in an A2A scenario (Approval Workflow management using SAP NetWeaver BPM and KPI measurement) - A Case Study
  2.  Seamless Product Master Data Processing using SAP NetWeaver BPM, SAP NetWeaver PI, SAP NetWeaver MDM, SAP ECC in a B2B Scenario; ( showcases integration of SAP NetWeaver BPM with SAP NetWeaver PI)

Outcome of this session will help us in understanding the SAP NetWeaver BPM use cases in a heterogeneous landscape for the Master Data Governance for A2A and B2B scenarios.

See you there!

Its already a week, and I am remembering the last week's important moments in which one of them was the evening event. What a wonderful evening it was. It was the Process Design Slam night with Domain experts, UI experts, and Process experts to design a future business process for forming a virtual community based power plant for residential customers. I thought I will just recap the design slam that happened at Phoenix so that excitement carries on through Vienna and Bangalore.

About Process Design Slam 2009:

As you all know, (and according to the wiki) "the Design Slam is a virtual community collaboration applying BPM design and implementation tools and methodologies to solve a particular business challenge that has been posed by a panel of experts from SAP's customers and partners"

The idea behind this is to achieve a virtual collaboration team which will provide more dynamic, flexible, slim business and technical solution for the current business challenge.

The process chosen was to automate the business scenarios for power plant which is made up of resident's personal solar wind generation. Given the green evolution and sustainability aspects, these will lead a better TCO, more throughputs due to reduction in loss of power transportation and also support environment friendliness.

For more details: https://wiki.sdn.sap.com/wiki/display/bpxproj/Process+Design+Slam+2009

Highlights of Process Design Slam 2009:

We had a 6 different physical teams at Phoenix and also had a virtual team from Europe (with their late night hours) collaboratively working together to come with swim lane flow of the business process and model of the business scenario. This collaboration was/is a true representation of virtual community based company with business and technical experts working towards the common goal.

The team and outcome of that night was:

  1. Vision/Use Case : To provide the vision and goal with the business case
  2. Collaborative Modeling - Wave/Gravity: modeling via Google wave collaboratively to synchronize and enrich the virtual power plant process
  3. Business Rules : team identified different business rules
  4. UI and Dashboards: this team to provide a UI mock up screens and dashboard requirements
  5. Service Implementation: Team responsible to realize the model, I was part of this team
  6. BPM Methodologies: very critical team to provide overall methodologies and lifecycle management process
  7. Virtual Team: team virtually provided the inputs for the process design

In addition to this, we had a few independent great personalities join the group to provide value add and their expertise to all of us.

I was part of Service Implementation team where we had a great time. We were able to conceptualize the business process model using Visual Composer and provide the model with the place holders which can be enhanced and extended. Great Team work!!

For more details Marilyn's blog: Process Design Slam SAP TechEd Phoenix- First Iteration

Summary:

I was there till midnight; the time just went away with lots of interactions within the team and comparatively less interaction with the other teams. However the outcome of the entire 3-4 hours collaborative work was really amazing. I was/am thinking this virtual community team just rock. During the workshop  I was realizing it was similar to the ES workshop happened in the 2007 TechEd at Las Vegas, where multiple teams have come up with the different process challenges and we all designed the end-to-end process in a paper. However Process Design slam was different because as outcome of this was kind of high level business/technical design of the business process with the project methodologies.

Totally, for me it was a great experience and looking forward to be part of similar one in future.

I am sure friends at Vienna are just counting down for this great event. I hope we will have our design enhanced by next week. All the best to Vienna participants and wish you safe trip to Vienna.

Sign up for Vienna and Bangalore is here: http://www.bit.ly/bpxslam09

The objective of this blog is to provide different approaches for governing "Secure File transfers" between XI/PI and any third party systems in a System Landscape.

Business Case:

In many implementations Business requirement is to "secure" the file/data transfer between XI and any third-party system. So there is a need of secured connection between XI/PI and any file based third-party legacy systems.

Following solutions are proposed to cater secure connection between XI/PI and any third party systems.

1) SFTP (Secure File Transfer Protocol)

 "SSH File Transfer Protocol" or SFTP is a network protocol that provides file transfer and manipulation functionality over any reliable data stream. It is typically used with the SSH-2 protocol to provide secure file transfer. SFTP encrypts the session, preventing the casual detection of username, password or anything that is being transmitted. One key benefit to SFTP is its ability to handle multiple secure file transfers over a single encrypted pipe. By using a single encrypted pipe, there are fewer holes in the corporate firewall.

2) FTPS (FTP over SSL)

FTPS (FTP-SSL) is a real ftp that uses TSL/SSL to encrypt the control session and if required the data session. With FTPS, the control session is always encrypted, but the data session may not be always encrypted. FTPS is a file transport layer on top of SSL. SSL, or Secure Sockets Layer, is a method by which an encrypted ‘pipe' or tunnel is established between the FTP client and FTP server. Once the secure tunnel has been established (which is done using 128-bit encryption techniques), standard FTP is used to transfer data over the secure connection.

Feasibility of SFTP and FTPS in XI:

SFTP:

As per the latest SAP PI/XI support pack, it does not support SFTP via File Adapter.

So alternative approach to cater this requirement from XI is to make use of Unix Script at OS level to transfer the files from/to third-party systems.

  • Inbound Interface - i.e. third-party system ->XI->SAP: 

    File is transferred to a folder in SAP XI landscape from the third-party legacy system using UNIX Script with secured protocol. Once the file is ready in the XI landscape, File Adapter will poll this directory and file is picked up by NFS protocol.

  • Outbound Interface – i.e. SAP->XI->third-party system: 

    XI is responsible for writing a file into a folder in the XI landscape. These files are transferred to the third-party system by executing UNIX scripts with secured protocol i.e. via sFTP.

Pre-Requisites: 

  • Public key should be exchanged between external systems and the PI system.
  • UNIX shell script has to be developed and scheduled.

Advantages: 

  • Highly Secured.
  • Ability to handle multiple secure file transfers over a single encrypted pipe .By using a single encrypted pipe, there are fewer holes in the corporate firewall.

Disadvantages:

  • Two-Step process i.e. XI-->Temporary folder-->External System and vice-versa
  • Files have to be temporarily stored in XI server.
  • Multiple failure points i.e. XI and Unix script execution
  • Maintenance of an external UNIX script.
  • Difficulty in monitoring the execution of the shell script as it cannot be monitored thru XI.
  • Need to generate keys and install it in the SFTP site as a pre-requisite i.e. SFTP clients must install keys on the server.
  • SFTP uses keys rather than certificates. This means that it can't take advantage of the "chains of trust" paradigm facilitated through Certificate Authorities.
  • Files from the XI server should be deleted/archived in a periodic manner to increase the disc space so that it will increase the performance.

Note: UNIX shell Script can be executed as a background job ‘or' can be triggered from SAP XI through OS command at File adapter level.

FTPS (File Transfer Protocol Using SSL/TLS):

This is a built-in feature of File adapter in XI. But SAP Java Cryptographic Toolkit must be deployed as a prerequisite. (Refer to note https://service.sap.com/sap/support/notes/821267 Question 28). By default following ports are used:

  • Implict FTPs 990 (Control) and 989 (Data)
  • Explicit FTPs 21 (Control) and 20 (Data)

Both use cases can be combined with active and passive mode.

Advantages:

  • Direct transfer of files to/from third-party systems. It is not required to store the files in the XI server temporarily.
  • Built-In feature from XI File adapter
  • No extra effort in development and maintenance of Unix Script.
  • Centralized Monitoring tool from XI
  • FTPS uses certificates and therefore can take advantage of "chains of trust" paradigm facilitated through Certificate Authorities. This paradigm makes it possible for two entities to establish a trust relationship without directly exchanging security information, which is important for some applications.

Disadvantages:

  • Requires opening multiple ports forenabling SSLin the firewall. So there are multiple holes in the corporate firewall.
  • Not every FTP server supports FTPS and many that do, require a configuration change to activate the FTPS protocol extension.
  • Cryptographic toolkit should be installed in XI system though it is not very complex or expensive.

Conclusion:

Though SFTP seems more secure as it works through one port, FTPS is easier to configure, monitor and maintain from XI point of view. However, the decision depends on many parameters like, cost/effort, flexibility in use, ease of maintenance, company security policy, failure possibilities etc.

Thanks to my colleagues for their valuable inputs during the discussion.

Did you see HTML editor in Integration Repository/Directory? I am sure that it is not a new one. If not, this blog is describing the one of the feature available in XI on documentation and it also describes how to use it, how much useful it may be.

As part of huge XI implementation project, handling hundreds of interfaces, it is very difficult to keep track of attributes of all the objects like Data Type/Message Type/Message Interfaces/Mappings etc. Let me define attributes now. The attributes are nothing but, Name of the Object, Descriptions about the object, Author of the object, Date Created, Reason for the Object, Revision history etc.

It is very important that there should be proper documentation for each object. Otherwise if any changes needs to be done in future and it is very tedious task for the people who are not developed the objects. Whenever any changes are done it should be documented properly with providing Date changed, Reason for the change, Descriptions about the changes etc. So like change history of ABAP programs/or any Java Programs are maintained, we can maintain this developer log for each object.

Here is step-by-step procedure to achieve the same
Go to View from Menu->Documentation

image

Click on Create Button
image


Click on Dropdown Box
image


Here enter the description , details, date,modification log etc

image

After entering, save it . Then it will be like this
image


Activate the object. and then look into the object by View->Documentation
image

This can be done in object level or namespace level or software component level.

Real-time Best Practices –where it is prefer to use
1.Software Component:
• Describe Integration Scenario with Source and Target System details with brief- i.e functionality.
• Describe different namespaces used and purpose
• Name of the Imported Objects and the purpose

2.Mapping:
• Mapping functionality and Logic i.e. pseudo code
• User defined functions and purpose
• Validations if any
• Enhancement/modification log and the reason.
• If we use Java Mapping, many places we will not put .java file in the imported archive for security or other reasons. So it is better to explain the entire logic/pseudo code to understand the implementation.

3. Integration Process:
• If the scenario contains very complex business process, then it is required if it is explained in the documentation. It can be good if flowchart kind of description is given here.

4. In the Integration Directory
It is good practice to describe the flow of the message processing by describing sequence of XI pipeline steps.
-Sender Agreement
-Receiver Determination
-Interface Determination/mapping
-Receiver Agreement
If the documentation describes all the sequence of steps executed in the multiple receivers/complex scenarios, it can be very easy to handle the interfaces for any successor consultant.

This feature may be useful in any of the future XI implementation project.
Krishna Moorthy P

Http* Errors in XI

Posted by Krishna Moorthy P Jul 23, 2006

 

There are many forum discussions about Http Errors. This blog is collective information about most common HTTP errors occurring during XI implementations and possible tips to solve the problems.

 

Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.



Possible Tips:


Because of J2EE application com.sap.aii.af.ms.app not active

• Try to (re)start the application using the Visual Administrator
Choose Server --> Services --> Deploy --> View on Application
or restart the J2EE engine


• The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.

• Refer SAP Note 803145,807000,791655



Reference: For Http code description--www.w3.org/Protocols/rfc2616/rfc2616-sec10.html


http://service.sap.com/instguidesnw04 -> Operations -> SAP XI -> Troubleshooting Guide - SAP XI 3.0/2.0.

 

 

This blog is a continuation of blog- Reconciliation of Messages in BPM and it also describes about How to restart the Integration Process in XI after BPM errors.

 

 

 

 

Once mapping exception occurs, alert will be triggered. In SXMB_MONI- it clearly shows error in BPM.

 

image

 

Technical Details of BPM- To see the complete technical details

image

 

Check Alert in the Alert Inbox of RWB-

image

 

To check Reconciliation-


Make the required corrections to fix the errors in BPM and activate the component in Integration Repository. Also make sure that Cache is refreshed.
In this example I will change the code, so that it will not affect the file.
To test the Reconciliation, Workflow should be restarted.

Restart Workflow-


Business process can be restarted using the transaction code SWF_XI_SWPR in XI. Or go to SXMB_MONI_BPE->Restart Process After Error

 

image

 

After clicking on Execute button , following screen appears-

 

image

 

After selecting specific,required workflow- clicking on Restart Workflow button takes into following screen.

 

image

Now workflow is successfully restarted and Integration process started executing from that point where alert has been triggered and file is written successfully into Receiver system. And here is the original output as required.-

image

Here you go with the required result. Hence Reconciliation of Messages in BPM.

Note: There will be a performance overhead of transformation step in the BPM. Still ultimate aim with respect to business is to reconcile the messages/data. It will be beneficial, when BPM executes huge amount of Business Logic and runtime exceptions within the BPM after the successful execution of some steps will lead into the message loss.

 

 

Reconciliation is a process of re-submission of messages after corrections that were failed in the previous run. This failure is may be because of Application errors, Run time Exceptions etc.  Business Requirement is to trigger an alert for Application errors and continue the process from that point, after correcting the application errors (e.g. Mapping Runtime Exceptions). So to trigger an alert for application errors with dynamic text, BPM is used here.  If the control step triggers an alert at runtime, Alert Management sends the alert to the relevant user. The process is not terminated and resumes on completion of the control step. The user is informed by Alert Management and then user needs to decide to discard the process or change the application which caused applications errors. But after correcting the application error , if the message should process from that point( where Alert has been triggered), without alter the rest of the process, then some workaround needs to be done in the BPM , so that after restarting the workflow instance, the process run smoothly. Note: This blog explains, necessary steps required in the BPM to reconcile the message from Mapping Runtime Exception. Here I have taken simple File->XI->File Scenario with Runtime Mapping Exception. Interface Flow:File is picked by Sender File Adapter and sent into BPM and in BPM transformation step is executed , if any runtime exceptions comes, alert is triggered from the BPM and if not it is sent to file successfully by Receiver File Adapter. After triggering an alert, if user wants to reconcile the message, then BPM needs to be configured accordingly so that user gets required, transformed data in the output. Reconciliation Logic: After getting the alert, user needs to go and fix the errors. If user restarts the Workflow after fixing the error, user will not get transformed data as required. Once user/developer restarts the workflow instance, message should be mapped as required. For this reason, Transformation step is executed once again in the BPM and this step will follow once workflow is restarted. Rest of the logic will remain same. Thus user can reconcile the message without reprocessing whole file/complete scenario.  In this scenario, user needs to fix the Mapping, activate the Mapping. So that new, changed mapping should reflect in the BPM. It is so often that, you may need to refresh the cache, check for the Integration Process status in SXI_CACHE. Step 1:  Integration Repository- Design   Assumptions- Data Types, Message Types, Message Interfaces are in place. Create a simple 1:1 message mapping with small user defined function. This function is used here to demo this runtime exception in the Mapping. imagecheckError is the small user defined function used here. The code is as follows. image Create an Interface mapping between two abstract interfaces so that this can be used in the Transformation step of BPM.  Create Integration Process with following steps. 1)     Receive Step-  To receive the File Input Message ( Abstract Message Interface of type File Input Message) 2)     Transformation Step – to execute the Mapping 3)     Block Step to trigger an Exception when any mapping runtime occurs 4)     Control Step- To trigger an alert based on the Application Error/Runtime Exception 5)     Transformation Step – ( After Triggering Alert- to reconcile the message- Please look into Reconciliation Logic section ) 6)     Send Step- to send the transformed data  Two container Variables: •     To Receive the Message- File Input Message Type- Abstract •     To Send the Message- File Output Message Type-Abstract Integration process design looks like this:-image Following screenshot shows descriptions of steps used in the BPM.  1) Receive Step – of File Input Message Type, Abstract, Asynchronous Message Interfaceimage2) Block Step- Used to raise/define an Exception with Exception Branch. In this fig, I have given Exception Name as “runTime" image 3) Transformation Step- To execute the Mapping. Whenever mapping exception occurs, it throws an exception to Exception Branch. image 4) Exception Branch- It used to handle the defined exception.image 5) Control Step – Within the Exception Branch – Control Step used to here to trigger an alert whenever Exception occurs. Observe the properties of Control Step. The mentioned Alert Category is defined in the Integration Server using transaction code ALRTCATDEF.image Once Alert has been triggered, it resumes the process. To reconcile the message or to restart the process after fixing the errors, workflow should be restarted from that point.  6) Transformation Step – This is used here to execute the Transformation once again, after restarting the workflow. Once workflow restarts, Transformation step will be executed so that you will get the expected output as the normal flow. image 7) Send Step – to send the output to Receiver- Output File Message type- Abstract, Asynchronous Message Interface. imageFor Alert Configuration- Quick Steps1)     Create an Alert Category in XI with the Tcode- ALRTCATDEF 2)     As user required, throwing alert from the BPM with dynamic text, check the option of dynamic text. Even static text will also do. 3)     As this alert is triggered from BPM, no need of any Alert Rules created in the RWB. 4)     Use the Alert Category name created, in the properties of the Control Step in the BPM. And also provide Dynamic text in the Properties.  Now Repository objects are done and activated. Step 2: Integration Directory: Configuration Create the configuration scenario, assign the Business system, created the communication channels of type File for Sender and Receiver, and create Sender Agreement. Create two Receiver Determinations-  1)     File Sender ->BPM ( No Mapping) 2)     BPM->File Receiver ( No Mapping) Create the Receiver Agreement. Save and activate all. Now Design and Development is done.  To test the Scenario and Restart the Workflow please refer next blog.
A use case for Legacy System->XI->R/3 System. The purpose of this interface to update some custom tables in R/3 system based on data provided in Legacy system in flat file format. Flat file from Legacy system is sent to XI via File Adapter and Mapping is executed according to the business rules and sent to R/3 system via ABAP proxy which in turn updates the custom table. Here design and configuration part is been ignored.
The idea behind this blog is to monitor the processed XML messages for receiver ABAP proxy. Inspite of chequered flag in XI, proxy need not be triggered and with respect to this case we cannot see any log in the SXMB_MONI of XI Server, therefore it is very difficult to check the status of the Interface based on the processed XML messages in the XI server.
Let me explain a scenario where my status in XI Monitor is a chequered flag but when I check my custom table the data is still not updated. Now this gets me mind boggling and get to debug my ABAP code which has update query to update DB table in R/3. After all this analysis, I got to know that the ABAP proxy is not triggered from XI.
Following screen shows SXMB_MONI of XI server

image

After double clicking the above message following screen appears. If we observe the screen below, we are not able to see the payload for Receiver Interface.

image

Solution:
Follow up the below steps which helped me to analyse the Proxy communication.
Step 1:
Log on to SAP Application system(R/3)
Step 2: Go to Transaction code SXMB_MONI. Then following screen appears.

image

Click on Monitor for Processed XML Messages link. (As highlighted in the screen) we can see following screen.

image

Enter selection parameters and execute the same. We can see following screen of Monitoring for Processed XML Messages like Monitor in XI server. Now we can continue with our analysis.
According to my pre assumptions the below pic tells the error in proxy monitor(SXMB_MONI of Application Server). The screen shot is shown below.

image

image

Above two pictures shows two different instances when proxy is not triggered.
Now we got to know an error has been occurred in the proxy side. Errors can be 1)Mapping error 2)Receiver Agreement not found 3)connection problem and can be any…Fix the error and process it again, if successful chequered flag is displayed as shown below.

image

After double clicking on messages you can see following screen which shows payload, SOAP header, trace details etc.

image

So this blog explains how to monitor the messages, while handling File to ABAP Proxy scenarios.
Done with Integration Process in Repository and imported into the Directory. Many times Integration Process (BPM) is not reflected in the Integration Directory. In these cases many are landed up with importing the Integration Process again in the Directory and also ending up with doing configuration for associated objects.  The concept behind this is after activating of the Integration Process an equivalent workflow definition is generated in the Integration Server. This workflow is however has not been activated. This problem can be avoided by use of Transaction Code SXI_CACHE. This blog explains how to activate the Integration Process, when it is not reflected in the Directory. Step 1: Go to Transaction Code: SXI_CACHE in XI Server. You can see following screen. imageStep 2: Following screen is displayed with list of all the Integration Process, which are all designed in the Repository/Directory.  image You can see the list of Integration Process configured. Here Service column shows the BPM imported in the Directory.  If you observe, there is one column called Return Code. It shows status of the Integration Process. Return code for the creation of the runtime version: •     0: The runtime version was created without errors. •     Not equal to 0: Errors occurred.  If it is not equal to Zero, then you need to activate the same. Otherwise it will not be reflected in the Directory.   Step 3: The following screen shows the IP which is having the Return Code as 99. If the return code 99 is displayed in the runtime cache for the IP, then you need to check conditions given in the IP are valid, Correlations are used/activated properly and then we need to activate the IP by clicking the Activate Button (Ctrl+F5) image Following screen appears after clicking the Activate Button. image Pressing the Activate Button once again, will lead into following screen. imageimage If the status bar in the screen shows with checked flag as above, then it is understood that runtime version for the IP is created.
Business Process Management is an implementation methodology for the management of business process that interacts with people and systems both within and across the organization.

When to use BPM
1.Control/Monitor the messages in XI
2. Collect/Merge the messages in XI
3. Split the messages in XI
4. To Multicast an Message
5. Send an Alert

The following scenario describes how to start with BPM.
Business Scenario: File to File communication through XI using BPM.
Overview: The purpose of this document is to implement an asynchronous interface between two Legacy Application via XI. As a result of this scenario, you will become familiar with basic sequence of steps to implement this scenario in XI using BPM.
Process Flow of the scenario is given below.
image
The following steps describes entire scenario.

Integration Repository-Design

1. Create Software Component version.
2. Create Namespace under above software component.
3. Create Data Type for both source structure as well as target structure. In my scenario I am considering source structure and target structure are same.
For example data type created is as follows.
image
4. Create Message Type based on data type created above. For E.g MT_File is created as below.
image
5. Create Message Interface
While creating message interface we need to create have 3 message interfaces.

Message Interface I: Outbound, Asynchronous: used in picking the file. E.g.; MI_FILE_to_BPM_OB is shown below.

image

Message Interface II:
As per the flow, we have created one outbound interface for file. This outbound interface should give data to Integration Process. But Integration Process will not understand outbound/inbound interfaces. It will only understand Abstract Interfaces. The Abstract Interface is nothing but any other interface but it does not have any direction.
So we need to create an Asynchronous, Abstract Interface of above message type.
For e.g. MI_FILE_to_BPM_ABS is created as below.
image
Message Interface III: Inbound, Asynchronous: used in receiving side. E.g. MI_FILE_to_BPM_IB is created as below.
image
6. Create Message Mapping
Create one-to-one message mapping as my source and target structure are same.
For e.g. MM_File_to_File is created as below.
image
7. Create Interface Mapping
Interface mapping is created based on outbound asynchronous interface and Abstract interface. Make sure that target interface should be Abstract Interface which is created in one of the above steps.
For e.g. IM_File_to_BPM is created as below. image
8. Create Integration Process
As shown in below, create Integration Process. For e.g IP_File_to_File is created.
image
After clicking on New, give Integration Process name and click on Create button. It will take into following screen. Now it is ready to design integration process.
image
Step1: Create Container element
To process message in BPM, it is required to create Container Elements. Because it is not possible to use abstract interface directly. The Container elements are variables used in the BPM. It is declared during design time. At runtime, the container elements then contain the references to the relevant data.
Following screen shows that ReceiveMsg as Container Element of type Abstract interface.
image
Step2: Insert RECEIVE Step
To process messages, Integration Process should receive the messages. To do this insert RECEIVE step as shown below. It has its own properties.

image

In Properties Window, click help against Message as shown above. After clicking, you can see following screen that shows Interface Variable. Here it will show all the Container elements that are declared as Abstract Interface category. From this interface variable list choose appropriate interface that should refer to original message. Following screen shows the same.

image
Step 3: SEND Step
Once messages are received, BPM needs to send these messages. (As this is a simple scenario) If you want to collect messages, split messages you need to use Transformation step after the receive step that refers to N: 1 Interface Mapping or 1: N Interface Mapping created.
The following screen shows how to select messages for the Send Step.

image

image
9. Save all and activate all.

Integration Directory: Configuration

1. Create Configuration Scenario.
2. Create Business System/Business Service.
In Business Service mention Inbound Interfaces and Outbound Interfaces as shown below. (I.e. created in the Repository). E.g. The Business Service BS_FILE_BPM is created.
image
image

3. Import the Integration Process
As Integration Process is used to hold messages in XI, it should receive the messages and should send the messages. So Integration Process itself acts as a Receiver Service and Sender Service.
After clicking on New in the following screen, you can create Integration Process in Directory by selecting Integration Process, which is created in the Repository. This step is to import the Integration Process as it acts as a Sender/Receiver Service.
image
4. Create Communication Channels

Both Sender and Receiver Communication Channels of adapter type FILE are created.

5. Create Receiver Determination/Interface Determination/Receiver Agreement

As per the flow diagram entire scenario will look like this.
image
So we need to create two Receiver Determinations. One Receiver Determination is used from Source to BPM and second one is used from BPM to Target.
The following screen shows First Receiver Determination where Sender Service is Business Service created for File interface and Receiver Service is used as Integration Process. Message Interface used here is outbound file interface.
In Interface Determination, interface mapping is mentioned. This interface mapping is created based on Outbound Message Interface and Abstract Message Interface.
As the receiver is Integration Process (BPM) no need of Receiver Agreement.
The following screen depicts the Receiver Determination, Interface Determination and Receiver Agreement.

image

While creating second Receiver Determination, make sure that Sender Service is Integration Process (i.e. imported in one of the above steps), Interface is Abstract Interface and Receiver Service is actual receiver, in this case Business Service created for File. Interface Determination is created for Inbound File Interface. No interface mapping is required, because BPM itself contains mapped data. Unlike in first receiver determination, in this case Receiver Agreement is required, as file is a receiver.
Following screen explains the Second Receiver Determination, where actual receivers are determined. Make sure that Sender Service is BPM and Receiver Service is actual Business Service created for File.

image

6. Create Sender Agreement
As file system is source in this scenario, sender agreement is created based on sender file communication channel.
7. Save all and activate all

To monitor Integration process log, go to transaction SXMB_MONI_BPE ->Process Selection->Select corresponding integration process (in Service Field) ->Execute->Select work item.

Actions

Filter Blog

By date: