I would like get a reliable information related to PI to PO upgrade with B2B solution.

Present system:

SAP PI 7.3 with SP04  and have SeeBurger for B2B solution

Future:

Plan 1:   SAP PI 7.4 AEX Installation + SeeBurger B2B Solution = results No cost to company

Plan 2:   SAP PI 7.4 AEX Installation + SAP B2B Addon  = Results some licencing cost to company

Plan 3:   SAP PO (Includes SAP PI 7.4+ BPM+BRM and SAP B2B Addon ) = Results some more licencing cost to company more than plan 2.

Now coming to installation:

We are currently aware of the efforts of direct move from current to any of the above plans.

But If I move to either plan 1 or 2 at present,  and in near future, i we need to move to Plan 3, what would be the technical efforts.

- Can I move from AEX 7.4 to PO 7.4 with install of the BPM+BRM+B2B Add on on the same system without affecting the existing mapping & configuration ( shouldn't have any Development effort for changes/ testing )

- Or Does it require a complete new install of PO 7.4 and migrate the mapping & config of existing PI 7.4 AEX.

Appreciate your inputs.

Best Regards,

VR

Dear All,

We are planning to install SAP PO 7.4 Latest version for integration.

Need installation and post installation documentation.

Please share the prerequisite steps for installation of SAP PO 7.4

Thanks

Niraj

My scenario is SFTP to IDoc_AAE. It is a pass through Interface. I am getting IDoc flat file at SFTP sender side, which I am trying to convert into XML using the module IDOCFlatToXmlConvertor module. The issue I am facing is since parent-child relationship is missing, it's failing. Any workarounds ?

Hi All,

I have a new requirement for integration between SAP Retail & GK POS , can anyone help on the below ?

1. What adapters can be used for integration between SAP Retail & GK POS ?
2. Is there a standard content available for download for the development .

Any Information on this would be of great help.

This is regarding CBMA in single stack SAP PI 7.3.1. I have set up the alert mail using default java mail client.I do receive the alerts via mail. But my requirement is to direct all the alert mails to Business workplace inbox in ECC.

So I need to set up PI to redirect mails to ECC Business workplace user inbox (sbwp). From here rules are set up & routed per distribution list.

Please guide me how I can achieve this requirement.

Hi Experts,

Has anyone been able to use the 90 day trial server on AWS "SAP NetWeaver Process Orchestration" gives the error "Error while processing the request

Invalid attribute value item "maximilianocolman@gmail.com" for userId item type. "

Greetings.

Hi All, Can you please guide and disable WSDL authentication in PO 7.4. Where to change com.sap.aii.ibdir.wsdl.servlet.authentication with  off in PO 7.4 java stack. Regards, Venkata

Hi All, We have Sybase + ECC+PO 7.4 java stack (PI) on Suse Linux OS. From PO 7.4 wanted to connect external SQL Server Database. Please provide the steps and drivers location. Do we need to apply using SUM or any other option we have. Regards, Karthik

Hi Everyone:

          My scenario is SOAP--> PO -->  REST, now the rest provider ask me to add extra http header when I post my request.

otherwise,"A specified precondition has failed for this request (Missing context parameter 'X-tenantId'.)."

          Who can help me to solve this problem

Thank you

APIs have been around for over a decade now. Early APIs were message 'contracts' exchanged between programs. With the advent of Internet, in the early 2000s, slowly there was an explosion of APIs that were web enabled. SOA then helped further shape the API paradigm.

Today the term API is predominantly synonymous with a service that is RESTful in nature and used extensively in area that concern the modern rich web and mobile. With the mass explosion of APIs, there has been a foray of technology and tools that proposes to deliver API management.

The first question that should probably come to ones mind is, 'What is so special about APIs that we need new technologies/tools in delivering and managing APIs?'.

To answer this, it is important that we understand what APIs really mean today and what managing them comprise of.

What is an API in the context of this article?

An API is;

1. A piece of code that will allow two software programs (applications) communicate with each other.

2. This communication is based on web protocols (HTTP/HTTPS) and is usually based on REST

3. An API will help connect business processes, services and data to both external and internal consumers (devices, applications etc)

4. Abstracts the consumer (ex. web or mobile developer) from the back-end application

Yes. You have guessed it right. This sound so much like a service (or if you prefer interface) one would develop on any integration platform like SAP Process Orchestration, Oracle Fusion, Webmethods etc. So why am I reinventing the wheel?

Now that we have a fair idea of what an API means let's look at some examples of where APIs are being used. Interestingly, we in many ways are interacting in a world of APIs. Every time you open Facebook or Google, there is an API at work. When you place an order or search for items on Amazon, there are APIs being invoked. Further on, if you have one of those smart watches or fitness devices (wearables) like the NikeFuel, APIs are core to them.

Note: Have you read about the famous Jeff Bezos' mandate?

So now that we have established that APIs are actually very much integral to our day-today life, let us look at what API management means.

An API Management platform will have the following key characteristics (not limited to the below);

1. Tools for developing APIs (obviously!)

2. Discovery of APIs i.e. cataloguing, searching etc

3. Version and life cycle management

4. Developer Engagement- Controlled access to developer to discover and consume APIs, collaboration opportunities etc

5. Security - Support of standards such as oAuth, SSL, threat protection, encryption, SAML, IAM etc

6. Orchestration - API mashing, branching etc (Orchestration is a big word but try not to confuse this with heavy process based orchestration)

7. API Analytics

8. Caching and Optimization - ex. caching of frequently requested data, compression of messages etc

9. Monetization - A method for monitoring and recording the consumption and traffic of APIs thus incentivising (or the billing) them.

Q: Do we still need a platform for doing APIs? Cant investments in existing enterprise grade Integration/BPM technologies realize this for us?

It is important that we answer this question right away because only then is it possible for us to understand the value proposition that API management will deliver.

The core requirements/use cases APIs will serve are around mobile, web and the IoT space. This means we are looking at real time service calls that requires low latency to be maintained throughout. APIs usually do not accommodate heavy logic or orchestration and are philosophically KISS (Keep It Simple Stupid!) in nature.

The enterprise service bus, SOA and business process management platforms are sophisticated tools that manage a wide variety of integration and orchestration patterns but what makes API management a bit unique from the traditional A2A and B2B integration, is the aspect of functionalities like Developer Engagement, Caching, Incentivisation and support for standards such as OAuth. Analytics and reporting around APIs is also a key aspect.

More on Analytics & Incentivisation of APIs:

Some examples of what Analytics, reporting and Metrics means in the case of API management;

a. Analysis of traffic - This could be number of transactions, the source of the traffic etc

b. API trends - Availability, top trending API, least used API, error categories, error rates etc

c. Developer statistics - Number of Developers engaged, top developers, APIs by developers etc

Incentivisation is all about how to monetize APIs. There can be different models that organizations might wish to adopt. Some may be a 'Pay as You go' model or an unit based where the costs are proportioned according to the consumption of the APIs, another could be a revenue sharing model where the organization pays the developer or say a partner based on the revenue generated by the APIs developed by them, some organizations might even just simply choose to give away APIs for free so as to drive market adoption.

By now, it should have become clear that the Enterprise Integration and the API management technologies both have overlaps but are distinctly unique in the use cases they cater to serve. Thus in an organization that is finding itself stepping into significant mobile adoption, the consumerization of IT and those with predominant B2C interactions along with B2E and B2B, setting up APIs and the required technology to manage it becomes an exciting value proposition.

If your organization answers 'Yes' to the majority of the below questions, then you should potentially start evaluating the benefits of an API management solution;

1. Does your organisation have a strategy or vision around the adoption of mobility?

2. Are you looking to extend the collaboration and development of APIs to external parties, vendors or developers?

3. Will you be exposing your organization business data for public consumption?

4. Do you want to analyse trends of data consumption and utilize sentiment analysis of your social channels?

5. Is your business primarily front ended by the web or is the web the core channel your customer engage with you?

6. Does the word 'User Experience' keep getting mentioned in your strategic meetings?

In the modern enterprise landscape, thus the core integration and orchestration technologies (ESB, BPM, MFT etc) will continue to hold their place but will now start finding itself possibly accompanied by the new stack i.e. API management, each serving purposes, it is best capable to deliver.

SAP has also realized the technological gaps it has in its product suite. The recent partnership with the industry leader in API management, Apigee, is a sign of SAP desperately trying to bridge gaps and strengthen its overall solution stack.

Note: Refer this blog for insights into the Integration and Orchestration offerings from SAP

So now I come back to the title of this blog and would like to ask the reader, 'Should we be really bothered about API management?'. Do post your thoughts in the comment section of this blog and hope to have an engaging discussion.

Hi All,

where we can use soap adapter?

we can use soap adapter all cases or any specific case like web service.

Hi guys,

I want to test the interface in my new environment 7.4 single stack file --proxy(soap xi)

can anybody help me how to test in a clear way plz..

we had place the file in a folder by basis.

I just want to know my interface is working or not in 7.4 singlestack.

Reply me ASAP

Thanks,

Danii

Hi All,

We are upgrading one interface from ABAP mapping to Graphical/Java mapping in PI upgrade.(7.1 dual stack to 7.4 version)

In ABAP mapping there is character conversion like below.

  encoding    = '1164'

      replacement = '?'

We want to implement the same functionality either through Java or graphical mapping . But we are not sure what are the range  of characters that need to be converted to '?' and also what is the most optimized way to achieve this functionality.

Below are few sample of characters coming in the file:

б,л,к,У,М,л,и,о,ф..etc

Java Development within the SAP Process Orchestration Platform

Introduction:The stability, robustness and capabilities of the SAP process orchestration makes it increasingly a platform of choice as an ESB, BPM, BRM and composite service platform. More so, this is made possible with the toolset and infrastructure provided by SAP. These tools include; Java Only installation for PI, NetWeaver Development Infrastructure (NWDI), NetWeaver Developer Studio (NWDS), JEE Application server. In this blog, I will highlight some custom java development use cases that underscores the power of the SAP Process Orchestration Platform. Subsequent blogs will provide details on how to achieve these use cases within SAP PO. The custom Java development use cases to be considered include;

1. Process Orchestration with Java proxies
2. Custom mapping functions in BPM with EJBs
3. Java Mappings in PO operation mappings
4. Creating Adapter Modules with EJBs

Tools, Infrastructure Needed:  Certain essential tools within a specific infrastructure is needed to implement some of the use cases mentioned above, they include;

1. SAP Process Orchestration Java Only installation
2. NetWeaver Developer Infrastructure (NWDI)-optional
3. NetWeaver Developer Studio

Case 1: Process Orchestration with Java Proxies:Java Development with java proxies on the SAP PO platform comes handy in use cases where system-to-system orchestration needs to be implemented, especially for synchronous calls. However, when system-human interaction orchestration is necessary, then SAP BPM becomes the implementation method of choice. The use of java proxies has its pros and cons;

Pros: Better performance for system-to-system orchestration, leverages the AS Java infrastructure provided by SAP, desirable and comprehensive integration logic can be built in Java.

Cons: Availability of Developers/Architects with good Java knowledge is essential, Troubleshooting can be a difficult task

There are two flavors of Java proxies that can be developed in NWDS for building orchestration logic; the client java proxy and server java proxy.

a) Java Client Proxy: The Java client proxy is developed as the client application that consumes the Integrated Configuration (ICO) created in the Integration Directory. To develop a client proxy, a number of steps need to be implemented, these are described in high level here; 1) Create a development component of type EJB (from development infrastructure perspective) 2) Create a development component of type EAR (from development infrastructure perspective) and add the EJB dc created earlier as a dependency 3) add necessary SAP standard component (engine.jee5.facade, tc/esi/esp/wsrm/facade) as dependencies 4) Import a WSDL (file system) or a modelled outbound service interface (from ESR). 5) Generate a webservice client on the WSDL/service

6) Create a wrapper class to implement the bunch of classes generated in step 4. This is done by creating a session bean with a local interface, the session bean implementing class contains the logic to call the port and pass the request into the ICO. 7) Build the EAR and EJB dcs, then deploy the EAR file on the AS Java. 8) Go to the NetWeaver Administrator and configure the client proxy to consume the ICO. Within the NWAèSOAèApplication and Scenario CommunicationèSingle Service AdministrationèConsumer Proxies (search for the name of the WSDL/service interface on which the client proxy classes were created). Navigate to the “Configuration tab”, with the option “New” follow the wizard to configure consumption of the ICO (use the import from WSDL URL) option to import the WSDL of the ICO from the integration directory as well the endpoint. Follow the wizard and complete the configuration.

b) Java Server Proxy: The Java server proxy is developed as the service provider where the integration logic that drives the orchestration is developed. Integration logic capabilities that can be developed include; calling the client proxy EJBs, data transformation (mapping functionalities) or request and response data. To develop a server proxy, a number of high level steps are implemented; 1) Create a development component of type EJB (from development infrastructure perspective) 2) Create a development component of type EAR (from development infrastructure perspective) and add the EJB dc created earlier as a dependency 3) add necessary SAP standard component (engine.jee5.facade, tc/bl/logging/api, tc/je/webservices/api) and client proxy dcs as dependencies 4) Import a WSDL (file system) or a modelled inbound service interface (from ESR). 5) Generate a webservice Java Bean Skeleton on the WSDL/service

5) Develop the logic within the created “implementation bean class”. To be able to create annotations on the local interfaces of the client EJBs, the client classes must be exposed in the “public parts”  7) Build the EAR and EJB dcs, then deploy the EAR file on the AS Java system. 8) Go to the NetWeaver Administrator and configure the client proxy to consume the ICO. Within the NWAèSOAèApplication and Scenario CommunicationèSingle Service Administrationè Service Definitions (search for the name of the WSDL/service interface on which the server proxy classes were created). Navigate to the “Configuration tab”, with the option “New” follow the wizard to generate a new WSDL that will be used as the entry point into this service. Follow the wizard and complete the configuration. The WSDL URL can be used in the receiver channel configuration in the Directory.

N:B- The Sender channel for the ICO to be consumed by the client proxy is of type SOAP, also the receiver channel used in the ICO that calls the server proxy is also of type SOAP. However asynchronous calls, SOAP Sender channel with XI.30 message protocol can also be used for WS-RM. This also has to be stated during the configuration of the client proxy in NWA.

Case 2: Custom mapping functions in BPM with EJBs :  Often complex data transformations between two steps in the process flow of BPM becomes essential. In situations where basic mapping is not enough within the expression editor and also where operation mapping from the ESR cannot be imported for use, creating an EJB function becomes an alternative. To create an EJB for mapping use within the BPM, perform the following steps; 1) Create a development component of type EJB (from development infrastructure perspective) 2) Create a development component of type EAR (from development infrastructure perspective) and add the EJB dc created earlier as a dependency 3) add necessary SAP standard component (engine.jee5.facade, tc/bl/logging/api, tc/bpem/mapping/façade, /api, tc/je/sdo21/api) as dependencies 4) Create a session bean with a local interface, the local interface extends the “function” and “Sdo” SAP standard classes. Implement the session bean class to invoke the data object, perform the necessary mapping transformations and set the output back into the process 5) Deploy the EAR file of the ejb to the AS Java. 6) Navigate to the JNDI tree browser and search for the deployed ear, the JNDI via which this object can be located at runtime can be seen. 7) Create a mapping function artifacts  with the process development dc, configure the mapping artifact with input and output parameters as well as reference to the JNDI name of the deployed EAR file.8) Use the custom mapping from the expression editor.

Case 3: Java Mappings in PO operation mappings:SAP PI/PO provides different mapping possibilities to achieve transformation from the source message structure to the target message structure. Graphical mapping is often the first choice, but when graphical mapping is unable to achieve the mapping functionality, then XSLT mapping can be of irrelevance. However, implementing a Java mapping within PO might be the best option. The steps necessary to implement a Java mapping are highlighted here;

1. Create a Java project in Eclipse or NWDS, thereafter create the rest of the necessary artifacts vis-à-vis package, class
2. Add the necessary SAP jar files needed as dependencies to the project
3. Implement the logic for the mapping within the Java Class
4. Export the java class as a jar file to a local directory
5. Create an Imported Archive object in the ESR
6. Import the jar file into the Imported Archive object
7. Select the java mapping jar file within the Operation Mapping

Case 4: Creating Adapter Modules with EJBs: In order to extend the functionalities of the SAP standard adapters (file, JMS, SOAP) during message processing, it is possible to create adapter modules with java classes. To create an adapter module, the following high level steps should be implemented;

1) Create a development component of type EJB (from development infrastructure perspective) 2) Create a development component of type EAR (from development infrastructure perspective) and add the EJB dc created earlier as a dependency 3) add necessary SAP standard component (engine.jee5.facade) and client proxy dcs as dependencies 4) Create a session bean and implement the necessary logic for the adapter module. 5) Define the JNDI name within the “ejb-j2ee-engine.xml” file as well as the EJB name within the “ejb-jar.xml” file. These names must be unique in order to avoid naming conflicts and the class loader loading a different bean than expected. 6) Build and deploy the EAR file, configure the communication channel with the adapter module based on the JNDI name.

Conclusion: In this first blog, I have highlighted a number of custom java developments that can be achieved by leveraging the SAP PO Platform. These blog series aims to help putting the essential possibilities into perspective for SAP PO consultants, Developers, Solution Architects and Enterprise Integration consultants. They can adopt these, to realize certain process integration/orchestration requirements within projects. It also aims to help tick the checklist box of essential skills set to consider when working with the SAP PO platform. Detailed step by step guide on how to realize these use cases will be discussed in my subsequent blogs. 

Working with REST Adapter: A REST to SOAP Scenario in SAP PI/PO

Introduction:With the introduction of the REST Adapter in SAP PI/PO, consuming a REST service or exposing a REST service in PI becomes more fun. This is with respect to the fact that the SAP PI/PO ESB extends its capabilities to handle and process REST-based messages (XML, JSON) easily. Prior to this time, implementing or consuming a REST-based service had to be done via third party adapters (e.g Advantco) or manipulation of the AXIS Framework within SAP PI, which is often a tough task. In this blog, my aim is to highlight simple steps needed to expose a REST-based service in SAP PI/PO. An end-to-end implementation of simple REST to SOAP scenario is described.

Prerequisite: SAP NetWeaver 7.31 SP14 or SAP NetWeaver 7.40 SP 09 and above, knowledge of creating objects in Enterprise Service Repository and Integration Builder.

Scenario:The REST to SOAP scenario is implemented such that, an XML-based/JSON-based request is triggered from SOAP UI/Chrome REST Client. It is received by the Configured REST Adapter, processed and passed to the Receiver SOAP Adapter (configured to connect with the currency converter webservice from www.webservicex.com ).

Figure: Exposing REST-based Service via SAP PI as shown in REST-to-SOAP Scenario diagram

ESR and Configuration Objects: In this scenario, the necessary ESR objects creation steps are only listed below, with more emphasis on the configuration.

ESR Objects: Create the following ESR objects

1)      Download the WSDL from: http://www.webservicex.com/ws/WSDetails.aspx?CATID=2&WSID=10

2)      Import the WSDL as external definition in the sender and receiver namespaces

3)      Create the service interfaces for sender and receiver (use the same XSD on both sides)

4)      Create the message mappings and operation mappings

Directory Objects: Described below the necessary configurations steps for each object;

Sender REST Adapter: Create the Sender Communication channel by selecting the “REST Adapter” option.  Configure the REST Adapter as show below;

• Input message format: XML
• Quality of Service: Best Effort
• Output message format: XML

Figure: Sender REST Adapter Configuration with input message as XML

Navigate to the “Channel Selection” and specify a URL path.  This is optional, but useful to distinguish the different scenarios exposing REST-based services in SAP PI, as this will be added in the URL of the sender application (in this case: SOAP UI).

Figure: Sender REST Adapter Configuration Endpoint

Receiver SOAP Adapter: Create the receiver communication channel and provide the necessary connection details to the currency converter webservice.

Figure: Receiver SOAP Adapter Configuration

Integrated Configuration: Configure the integrated configuration (ICO) using the sender and the receiver channels created earlier.

Test the Scenario with XML: To test the scenario, SOAP UI is used as the sender application. The endpoint URL to fire the message to is constructed as shown below;

http://<server>:<port>/RESTAdapter/<pathspecifiedinthecommunicationchannel>

eg: http://xxxxxxx:50000/RESTAdapter/Rojo/CurrencyConverter/201503

Obtain a sample XML message from the test tab of the “Message Mapping” object in the ESR to be used as the XML to be sent from SOAP UI.

Figure: XML Request message from SOAP UI

Change The Sender Adapter Configuration (for JSON to XML conversion)

In addition to the above test, change the sender adapter configuration from XML to JSON, so that SAP PI receives a JSON request message from SOAP UI;

• Input message format: JSON with the following additional configuration
• Convert to XML
• Add wrapper element
• Element name (name of the request message as in the XSD in ESR)
• Element namespace (namespace of the request as in the XSD in ESR)
• Quality of Service: Best Effort
• Output message format: XML

Figure: Sender REST Adapter Configuration with input message as JSON

Test the Scenario with JSON: To test the scenario, SOAP UI is used as the sender application. The endpoint URL to fire the message to is the same as in the previous test. The SOAP UI JSON request and response messages are shown below;

Figure: JSON Request from SOAP UI

Figure: JSON Request from Chrome REST Client

The results of the calls to consume the exposed REST service in SAP PI based on the REST adapter are also shown above in both test cases.

Conclusion: With this blog, I have been able to provide an insight into how to expose a REST service in SAP PI/PO using the REST Adapter as the sender communication channel. Additional settings of the adapter can also be used as well, e.g. sending a JSON message as input or output message.

Hi Folks,

We recently upgraded to a PO 7.4 (latest SP) from a dual stack 7.3 and now I would like to use NWDS instead of the Swing Tools.

Unfortunately already in the beginning I am facing some Problems.

I have an external WSDL file which I would like to Import in NWDS as an external Definition, but I cannot find the Option to do this. All I am finding is the Option to create a normal data type out of the WSDL which is not sufficient.

Could you give me any pointer how to achieve the ED creation in NWDS?

I also read that you cannot test data element Queues in the mapping Editor in NWDS, is that true? What other obstacles are still existing in NWDS which make you still use the swing Clients from time to time?

This post show a simple example of connection from source iFlow to BPM, call an Operation Mapping in BPM, then send output to target iFlow.

The flow :
a. Sender (BC_S1) send a text file contain message FirstNameLastName via sender file adapter to first iFlow(PI to BPM).
b. First iFlow(PI to BPM) route message FirstNameLastName via receiver SOAP adapter to BPM(BC_BPM).
c. BPM(BC_BPM) call an Operation Mapping to combine message FirstNameLastName to FullName.
d. BPM(BC_BPM) route message FullName via sender SOAP adapter to second iFlow(BPM to PI).
e. Second iFlow(BPM to PI) save text file contain message FullName via receiver file adapter to Receiver (BC_R1).

The steps:
1. Create and activate interface objects in ESR
2. Create, activate and deploy source iFlow (PI to BPM) using NWDS
3. Create, activate and deploy target iFlow(BPM to PI) using NWDS
4. Create, activate and deploy BPM process. using NWDS
5. Test run it.

All sub steps:
1.1 Create data types DT_FirstNameLastName, DT_FullName

1.2 Create message types MT_FirstNameLastName, MT_FullName

1.3 Create below service interfaces :
SI_FirstNameLastName_OUT, outbound interface from Sender(S1).

SI_FirstNameLastName_IN_XI30, inbound interface to BPM(BC_BPM). Stateless XI30 compatible.

SI_FullName_OUT_XI30, outbound interface from BPM(BC_BPM). Stateless XI30 compatible.

SI_FullName_IN, inbound interface to Receiver(R1).

1.4 Create message mapping MM_FirstNameLastName_to_FullName to combine message FirstNameLastName to FullName.

1.5 Create operation mapping OM_FirstNameLastName_to_FullName, for use in BPM.

2.1 Create iFlow EIP_simplebpm_IF_01_FILE2BPM
2.2 Assign sender BC_S1, receiver BC_BPM
2.3 Assign sender interface SI_FirstNameLastName_OUT, receiver interface SI_FirstNameLastName_IN_XI30

2.4 Configure sender file adapter CC_SND_FILE_S1, receiver SOAP adapter CC_RCV_SOAP_BPM.
Receiver SOAP adapter use these URL “http://<hostname>:<port>/MessagingSystem/receive/JPR/XI” to send to BPM.

2.5 Activate and deploy. ICO generated.

3.1 Create iFlow EIP_simplebpm_IF_02_BPM2FILE
3.2 Assign sender BC_BPM, receiver BC_R1
3.3 Assign sender interface SI_FullName_OUT_XI30, receiver interface SI_FullName_IN

3.4 Configure sender SOAP adapter CC_SND_SOAP_BPM, receiver file adapter CC_RCV_FILE_R1.

3.5 Activate and deploy. ICO generated.

4.1 Create new project eip_simplebpm in NWDS using perspective “Proces Development”.
4.2 Import WDSL for SI_FirstNameLastName_IN_XI30
4.3 Import WDSL for SI_FullName_OUT_XI30
4.4 Import WDSL for OM_FirstNameLastName_to_FullName

4.5 Create new process pro_simple. The completed process is like below:

4.6 Create data objects act as variables to temporarily hold values before map to next steps.

4.7 At Start step, Event trigger, add StartMsg.

4.8 Add automated activity, OM_FirstNameLastName_to_FullName to bpm process.

4.9 Add  automated activity, SI_FullName_OUT_XI30 to bpm process.

4.10 Ensure service references is correct:
For SI_FullName_OUT_XI30, Type is “XI”, then maintain sender component “BC_BPM”

For OM mapping, type is “WS”.

5.1 Load source file, then file will go through source iFlow to BPM to target iFlow and finally create target file with fullname.

5.2 Communication Channel Monitoring:

5.3 Go to process repository and view it detail:

5.4 Go to manage processes, view process instances completed.

Reference:
http://scn.sap.com/community/process-orchestration/blog/2012/06/11/using-netweaver-pi-s-mapping-in-netweaver-bpm
Using Operation Mappings (PI) in a BPM Process
Configuring Message Processing from BPM to PI
Integrating PI Operation Mapping with SAP BPM

Thanks for viewing.

Dear Team,

Currently we are on PI 7.3 version and client has come up with the expectation of exploring the possibility of PI queue monitoring through Mobile apps.

We are going to upgrade our system to 7.4 in couple of month so any solution for ver 7.3 or 7.4 would work for us.

I have searched sdn links but don't find convincing solution. Any suggestions/Inputs ?

Regards,

Deepti

Hellow guys,

when we create an fso it inturns will push fso info to pi then pi will do some mapping that inturns provides a hexadecimal  this hexadecimal will be our "info path" this info path will convert something and it send a mail.

this info path will be in our email body this  is something a micorsoft tool .so we want to get away from this info path.

Now we are trying do the same with using SOAP to MAIL use HTML in the email body to send a mail(it is something outbound mail) the html is like below

<html>

<body>

<form action="mailto:danii5456@gmail.com>"

  First name: <input type="text" name="fname" value="Test1"><br>

  Last name: <input type="text" name="lname"><br>

  <input type="submit" value="Submit"><br>

</form>

</body>

</html>

and the input is like this

<MT_INPUT>

<FIRST_NAME>test1</FIRST_NAME>

<LAST_NAME>test2</LAST_NAME>

</MT_INPUT>

My requirement is. when we trigger from SOAP UI  it should drop a mail to given mail id.

So Experts, need your suggestions to finish this.

We are doing this in SAP 7.4

Thanks,

Danii

Dear Experts.

Any idea if we can send HTTP 202 instead of HTTP 200 from PI REST Sender Adapter , like we have a similar functionality for SOAP adapter.

Regards,

Vishal