Hi,

Do we have an option to configure direct connection in PO 7.4 using WS adapter. We do not have WS in this version but we have WS_AAE.

Could you please guide me on how to use this.

Thank you,

Manish

Hi,

So having read the great blog series PI Rest Adapter - Don't be afraid by Alexander Bundschuh and I decided to try and set up my first scenario using the REST adapter in the same vain as Working with REST Adapter: A REST to SOAP Scenario in SAP PI/PO .

When I come to test the service from SOAPUI I get a 404 error with the message "Invalid number of elements in URL "/". 3 expected, 0 received."

As you can see it is hitting the correct sender communication channel as the response comes back with the channel name "RESTSenderMyService".

The Channel has been set up as follows:

• Input and output format = XML
• Channel selection = MyService   (The 'Specify Endpoint' flag is ticked)
• There is no limit set for the HTTP operation.
• Everything else is left unchanged....left as their default values

Also I've tried adding the full URL in SOAPUI in the endpoint field - the attached screenshot shows when I tried moving the /RESTAdapter/MyService into the Resource field.

I've also fiddled with the media type of the payload from text/xml to application/xml.

So the mystery is what does the error message refer to and what are the 3 elements it's expecting?

Thanks in advance.

IFG global Survey 2015 for SAP Process Integration

As in the previous years, the Global Special Interest Group for Integration conducts its annual survey for SAP Process Integration / Process Orchestration.

Focus of the survey is to collect the latest state of the positioning, organization and use of SAP PI/PO and SAP integration in companies around the globe. Target group are employees and consultants from companies using SAP PI or SAP PO as an integration platform.

The survey results serve the IFG as a strong basis for the discussion with SAP and for the active influencing of SAP's product and release strategy. In 2013 the survey set a new record with over 350 participants.

The survey contains 27 general questions and 11 questions about this year’s special topic 'RESTful web services and cloud integration'. The general questions stay the same each year, so that the survey can identify changes and developments in the use and positioning of PI over the years.

The survey for 2015 can be found at the following URL:

International Focus Group for Integration - 2015 Global Survey

Time Schedule

• May 4th 2015: Official start of survey
• August 21st 2015: End of survey
• End of September 2015: Publication of results within the SAP user groups and on SAP SCN

Recent Blogs

An extract of the results of the surveys can be found in the following blogs:

• Results of the global NetWeaver PI Survey 2014 (Part 1 of 2)
• Results of the global NetWeaver PI Survey 2014 (Part 2 of 2)

For more background about our interest group see our central blog International Focus Group for Integration.

Questions and feedback are welcome.

Dear All expertd,

We have set up a new SAP PO server and just want to know how to do below configurations which was done in ABAP stack in previous versions..

• How to peform SLDCHECK ?
• Message Schedulling (RZ70)
• ECC / PO cennection set up..
• and How to check ECC and PO connections are working fine and SLD working fine.

Thanks

This blog is part of a collection of blog entries that shows architectural concepts and configuration of the SAP PI REST Adapter. We also added some sample scenarios to make it easier for you to understand how your scenario can be implemented using the PI REST Adapter.

If you haven’t done so far, best is to start with the very first blog PI Rest Adapter - Don't be afraid within the blog series covering the concepts of the REST adapter. A complete list of all blog entries can be accessed from here PI REST Adapter - Blog Overview.

The current blog shows you along a sample scenario which kind of dynamic attributes are supported and how you can use them.

Scenario

Referring to the flight scenario that we have introduced in the previous blogs PI REST Adapter – JSON to XML conversion and PI REST Adapter – Defining a dynamic endpoint, we will do further enhancements by using the dynamic adapter specific message attributes of the REST adapter. If you haven’t done so far, you should first read the previous blogs to make yourself familiar with the scenario. In short, we provide a RESTful service in order to read different kind of flight information. Within PI, the calls are routed to either function modules BAPI_FLIGHT_GETDETAIL or BAPI_FLIGHT_CHECKAVAILABILITY.

In this blog, we would like to introduce a GET variable mode to distinguish between an expert and a default usage of the service. In the expert mode, in addition to the flight details we add the information of the return table of the function modules to the response of the service call.

To recall, this is how the respective Integration Flow looks like:

Configuring the REST sender channel

In the SAP Process Integration Designer perspective of the NetWeaver Developer Studio (NWDS), we open the existing Integration Flow, and double-click on the sender channel of type REST to open the channel editor. Switch to the REST Resources tab below the Adapter-Specific tab. The rest of the settings remain unchanged.

We can use dynamic attributes to store information of the service call which we then can be used to control the message flow. The REST adapter comes with a set of predefined adapter specific message attributes such as resource, service, and id which are commonly used among RESTful services. In addition to the predefined attributes you can also define custom attributes which are then added to the header of the PI message.

First, we would like to define the resource as constant value flights. Add a new dynamic attribute REST Resource (resource) from the Dynamic Attribute drop down menu, select Manual Value as Value Source, and enter flights into the Static Value field.

Next, we would like to define two IDs based on the JSON payload, one for the airline identity, and one for the connection number. Add a new dynamic attribute REST ID (id) from the Dynamic Attribute drop down menu, select JSON Content Element from the Value Source drop down menu, and enter the respective JSON Element from the JSON payload, here FlightDetails.AirlineID. Proceed accordingly for the JSON element FlightDetails.ConnID.

Finally, we define a custom attribute called mode. Select --- Custom Attribute --- from the Dynamic Attribute drop down menu, enter the Custom Attribute Namemode, select GET Variable from the Value Source drop down menu, and enter the GET Variable Name mode. Though I have chosen here the same name, the custom attribute name and the GET variable name do not have to be identical. Note, that you must not add the GET variable to the url pattern, in our example it remains /{service_part}.

Enhancing the mapping of the response

Based on the mode attribute, we either like to add the return table to the response or not. So, we need to change the message mapping of the response message. Within the mapping, we need to access the dynamic attribute. I have created a user defined function getASMA to read the value of the dynamic attribute which we will use in the mapping:

@LibraryMethod(title="getASMA", description="get adapter specific message attribute", category="UDFPool", type=ExecutionType.SINGLE_VALUE

     public String getASMA (

       @Argument(title="") String namespace,

              @Argument(title="") String attribute,

               Container container)  throws StreamTransformationException{

            Map<String, Object> all = container.getInputHeader().getAll();

            DynamicConfiguration dynConf = (DynamicConfiguration)all.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);

            DynamicConfigurationKey key = DynamicConfigurationKey.create( namespace, attribute);

            String value = dynConf.get(key);

                          return value;

     }

From the Integration Flow, you can double click on the operation mapping to navigate to the respective message mapping in the ESR. Expand the source and target structure, and define a new field mapping for the node return. The target node return should be created if the attribute mode equals expert. As you can see from the figure below, we first call the user defined function getASMA. As input parameter of the function I pass the key of the attribute, in our case name mode with namespace http://sap.com/xi/XI/System/REST. The output value of the getASMA function is compared with the constant value expert using standard function equalsS. In case of boolean true, the node is created. Below the return node, the child nodes need to be mapped from the respective nodes of the source structure.

Running the scenario

For testing the scenario we use the Advanced REST Client Application in the Google Chrome browser. The endpoint URL of your RESTful service starts with http://<host>:<port>/RESTAdapterwith host and port of the SAP PI system, followed by what you have defined in the sender channel, here /demo/flight/<service>. Since we have defined a GET variable, we need to add the GET variable to the URL. Let’s stick here to the checkavail service.

First, I call the service with the default mode info. The URL is as follows: http://<host>:<port>/RESTAdapter/demo/flight/checkavail?mode=info

The response is as follows:

Let’s change the date of the flight details intentionally to a flight that does not exist, and call the service with the expert mode. The URL is as follows: http://<host>:<port>/RESTAdapter/demo/flight/checkavail?mode=expert

In the response you can see that the return items have been added.

You can access the dynamic attributes values from the DynamicConfiguration message header. In the message monitor, select the corresponding message, switch to tab Message Content, and open the DynamicConfiguration message header.

Here you can see additional attribute values that we have added.

I hope this blog was helpful to understand the various options that you have to define dynamic attributes within the SAP PI REST adapter. If you like to learn more, check out the other blogs in the series, accessible from the main blog PI REST Adapter - Blog Overview.

Hi Experts,

i had a requirement where i need to integrate the data between the third party system and C4C Via process orchestration. and the third party can only be communicated through the API . So how can i expose the Rest based webservice in process orchestration.Please help me

Thanks

Giridhar

Dear

We are currently configuring a sender REST adapter which be called as such:

http://host:port/RESTAdapter/pi/query/jira/solman/getsystems?sap-client=001&cust=00009999

(even encoding the question url or only question mark and ampersand doesn't help)

However whenever we try this, we can see following error returned by PI:

The sender adapter is configured properly according to the documentation on SAP Help:

Has anyone encountered this issue before?

We might think this is a bug, as the interface works fine when we use following pattern:

But only when we use the url as follows:

http://host:port/RESTAdapter/pi/query/jira/solman/getsystems%3Fsap-client=001&cust=00009999

We had to encode the question mark in the URL (%3F) in order for PI to pick the right channel with the correct parameters.

When using the normal question mark (e.g. used with the Chrome Advanced REST Client), we basically receive the same error as above:

Have any of you encountered this before, or have any of you used multiple parameters before in the sender REST adapter.

Thanks for any feedback.

Hi,

My Basis team have installed a PI Solution in out landscape. My question is what happens if they install all the functional units available on NWA (not consider a specific scenario: AEX / DUAL / PO) but only has been activated the functional units related to PI Dual Stack Scenario?. I have some performance problems on my server and I don't see the following objects on my Integration builder tool: receiver agreement, receiver determination, interface determination and sender agreement. Also the "Channel independent log" throws the following error when I called this monitoring tool: java.lang.IndexOutOfBoundsException ... Any help would be appreciated

Best Regards,

Danisay

Eng Swee YeohHareesh GampaIñaki VilaHarish MistriRaghu Vamseedhar Reddy Kadipi Reddy

Hi Everyone

We have approx 20 NW BPMs which were developed locally. I have to upload all the BPMs in NWDI. I have set up one SC called Z_PO_BPM. The issue is that each BPM has its own SC.

Is there a way to import existing BPMs under various SCs and upload under 1 SC created in NWDI track?

Any input much appreciated.

Regards

Sonal

Hello Experts,

I am trying to get data from wsdl url from sap backend or PI.

The wsdl is created form a function module through backend soamanager. The url is like below.

http://xxxxxxxxxxxx:8020/sap/bc/srt/wsdl/srvc_7A4EFF55AACC1ED4BD91D50F63294E16/wsdl11/allinone/ws_policy/document?sap-client=400/

I created the same function module call in pi and i have a wsdl pi url also like below.

http://xxxxxxxxx:54000/dir/wsdl?p=ic/3799bfbd06cb3a19b03ccc2bbf085316

when i use this url in wsnavigator or soapui, i get the result.

Could someone tell me which url i have to use in sapui5 to retrieve the data and how?

I searched already different posts like below but not working to me.

Consuming Web service in SAPUI5

JSON Adapter for ABAP Function Modules ( not allowed to do this in our environment )

Thanks in advance.

Regards,

Antony.

Hi,

Currently I've SAP PI 7.31 SP6.

Can I migrate it to PO?

What are the steps required to migrate it to PO for SAP PI 7.31 SP6?

Should I've to upgrade to SP7?

Thanks,

Parin Chahwala.

Hi,

I quite new to the topic and defined a (simple) message mapping in the ESR.

If I "test" it in the NWDS (Rightclick on the MM -> Run As -> ESR Messaage Mapping) and feed it with the following message

<?xml version="1.0" encoding="UTF-8"?><foo:MT_TestABZ xmlns:foo="http://my/test/namespace">  <A>0</A>  <B>false</B>  <Z>90210</Z></foo:MT_TestABZ>

everything is fine!

If I feed it with the following message (which is equivalent to the above, to my understanding)

<?xml version="1.0" encoding="UTF-8"?><MT_TestABZ xmlns="http://my/test/namespace">  <A>0</A>  <B>false</B>  <Z>90210</Z></MT_TestABZ>

then the following error appears: Cannot create target element /ns0:MT_TestABZ/A. Values missing in queue context ...

The thing is that I would like to use the mapping on the "returning" way of a synchronous soap-to-soap integration flow and the soap response has the form in my second example.

Am I doing something wrong?

Hi All,

I am configuring NWDI using CMS for PO 7.4. However, during the step Upload Default ACL Settings, I have the following error:

Following is the extracted error log:

I would be very grateful for any feedback to troubleshoot the error.

Best regards,

Duy

Dear Experts ,

i am using SAP PI 7.31 dual stack and I am creating BPM scenario using SAP PI and NWDS .  I have connected  NWDS  to SAP PI ESR But When I am trying to connect SAP Integration Directory to NWDS Then I did not find this perspective SAP Process Integration Designer in NWDS and When I checked NWDS preference there I did not find PI tool configuration .

Please suggest me how can i connect integration directory into NWDS .

Regards ,

Pradeep

Introduction: workingwith OData services on the SAP NetWeaver platform seems to be getting streamlined and simple. This is from an end-to-end perspective of developing an OData service in a SAP Backend system (with SAP Gateway component installed) as well exposing this OData service in SAP Process Orchestration. The advantages of this are enormous because, this already eliminates the use of SAP Gateway hub for exposing Gateway services. The existing SAP Backend system and SAP Process Orchestration can be leveraged, reducing the complexity of the landscape, while also reducing the total cost of ownership. Previously, developing OData services within the SAP Gateway platform seemed to be also a complex process. But also with the availability of the Gateway service builder tool (T-code: SEGW), a lot of the steps can also be easily automated. In this blog, I will try to achieve the following;

1. Develop an OData service in SAP Backend (with Gateway component installed)
2. Expose the developed OData service via the OData Provisioning Administration console in SAP PO.

Prerequisites:

• v SAP Backend system (with SAP Gateway component installed: IW_BEP 200 )
• v SAP NetWeaver 7.3 EHP 1 SP 13/ SAP NetWeaver 7.4 SP 08
• Following Authorization to user: GW_ADMIN and GW_USER

A)  Developing OData Service in SAP Backend

Developing an OData service in SAP Backend requires that the gateway component mentioned earlier is installed on the backend system. The Service Builder Tool is used to kick-start the process of building the OData service and essentials steps required are mentioned explicitly.

     Create OData Service: The following actions will be performed to develop this service;

1. Run the T-code: SEGW to access the service builder tool

2. Create a project and name it appropriately as “ZODATA_SERVICE” and save as local object,

After this, the following components are created within the project;

• Data Model
• Service Implementation
• Runtime Artifacts
• Service Maintenance

3.The Data Model for the OData service can be obtained/created in several ways; there is a possibility to create Entity types and entity set from scratch, but better still Data model can be imported in three ways taking advantage of existing data structures; DDIC, File (.edmx extension), RFC/BOR. Here, a DDIC will be imported. Click on the edit mode, right click on the Data Model component and select the option “Import DDIC”

Note: you could search the DDIC structure to be imported based on; View, ABAP structure or Database Table.

4. Select any existing ABAP Structure “/1BEA/FBCB_BDI”, provide object name “Z_BillingDetails”, Mark Client field property as Key and click ‘Continue’, It creates an Entity Type;

5. Create ‘Entity Set’ as below, with the name “BillingDetailsRequest” and select the Entity Type previously created;

6.  Open the ‘Entity Sets’  object and select the following properties Creatable, Updatable and Deletable;

7. After the previous step,  the following methods created for the “Service Implementation”

8. Now generate the “Runtime Artifacts” by clicking on the button shown below; this automatically generates the artifacts for the OData service with predefined classes which can be modified, but we keep it as default. The newly created classes are added as local objects.

Click continue and select the“Local Object” option in the next screen

9. The generated definition for the OData service is contained in this class: ZCL_ZODATA_SERVICE_MPC, however, to implement the desired logic, the ZCL_ZODATA_SERVICE_MPC_EXT class will be extended with the additional code. Right click on ZCL_ZODATA_SERVICE_MPC_EXT, choose the option below;

10. Switch to edit mode, select the “DEFINE” option and click on the Redefine button; add the following code below; then save and activate the class.

Register OData Service in the Gateway system: After the OData service has been created based on the previous steps described, the OData service needs to be registered in the Gateway system. To do this, perform the following actions

1. Run the T-Code in the backend system: /IWFND/MAINT_SERVICE to navigate to the service maintenance screen.

2. Choose the add service option to add the service created earlier in the backend system. Providing the following information shown in the screen and  ‘Enter’

3.Select the Technical Service Name and click on the local object as package, the package is filled with $TMP which is a local package;

After successful registration of the service, the following message should be displayed;

4. The OData service has been registered and it can be viewed as one of the services in the service maintenance screen.

Test the OData Service:A quick test can be confirmed on the newly created OData service can be done by;

1. Select ‘ZODATA_SERVICE_SRV’ and click ‘Call Browser’. This will open Service definition in browser.

2. The Details of this newly created OData service is shown below;

B.  Exposing OData Service in SAP Process Orchestration

In the previous section, a step by step guide was provided on how to create an OData service within the SAP Backend system with installed gateway component. This newly Created OData service will be exposed for consumption. Such that, this service can be consumed by Mobile Devices, by a receiver adapter (REST Adapter) in PO as well as by UIs within the SAP BPM deployed on AS Java. To expose the OData service as a Gateway service in PO, there are two essential activities to be performed;

• Create HTTP Destination to the Backend System
• Register OData Service in the OData Provisioning Admin

Create HTTP Destination to the Backend System: To create the http destination from SAP PO to the backend system where the OData service resides; perform the following actions;

1.Navigate to the NetWeaver Administrator URL

http://<hostname>:<port>/nwa

2. Navigate through the following to Configuration è Destinations

3. Click on the Create button; choose the Hosting System, assign a Destination Name and select the Destination Type “HTTP“:

4.Click on the next option from the wizard and provide the connection information to the SAP Gateway IW_BEP service;

5. Select the following option to access IW_BEP service in the SAP backend and provide the necessary logon credentials;

Click on the finish tab to complete the process of creating the http destination.

6. Additionally, the new created destination can be tested by clicking the Ping Destination button; if the configuration is done properly, the ping operation should return a successful message: “     Successfully connected to HTTP destination CRD with response code 200. Content type text/html”

Register OData Service in the OData Provisioning Administration: Once the http destination to the backend system where the OData service resides has been set up, then we are ready to register our OData service as a Gateway service. To do this, perform the following actions;

1. Navigate to the SAP PO Gateway OData Provisioning Administration via the url below:

http://<hostname>:<Port>/igwj/Admin 

NB: It is important to note that these two roles (GW_USER and GW_ADMIN) should be added to your user in order to be able access the OData Provisioning Administration and perform necessary actions

2. Once in the OData service cockpit, select the “Register a New Service”

3. Choose the http backend destination created earlier in the NetWeaver Administrator and do a wild card search, select the OData service created earlier in the Backend system from the list;

4. Click on the service to be registered and select the “Register” option, once this is done successfully, the following message is popped up;

5. The Service Document can be opened to view the details of this service in the browser, the metadata can also be accessed by providing the following information in the URL extension of the service: /$metadata eg;

http://<hostname>:<port>/igwj/odata/SAP/ZODATA_SERVICE_SRV;v=1/$metadata

The metadata URL contains the EDMX (Entity Data Model for XML) which contains the service definition for the OData service.

6. Click on the service name to view all the properties of this gateway service;

After all of the steps above have been performed, the Gateway service is ready and available for consumption by different devices and applications.

Conclusion:

Providing an entry point to consume complex enterprise services available in the SAP backend system is possible via the OData service. This extensive article has been able to provide an end-to-end overview of the steps and actions required to create an OData service in a SAP Backend system with the Gateway add-on component installed. It provides an overview on how to expose an OData service in the backend as a Gateway service with the SAP Process Orchestration Java Gateway component. Once this service has been registered, it is available for consumption by devices and applications.

Hello everyone,

I have a question related to the migration from ccBPM (dual stack PI) to PO (Java only)

In the original dual stack system the customer has implemented a ccBPM process (ABAP based) that uses Technical acknowledgement for message routing (in a mapping step I prepare 2 messages, I send the first message from ccBPM to PI that writes a file, the file adapter of PI sends the Technical ACK back to ccBPM and in case the ACK is green then the ccBPM send the second message)

First of all as far as I've understood there are no "migration tools" from ccBPM to Netweaver BPM, so we have to create everything from scratch (you should be able to import inside Netweaver BPM the message structures and you should be able to reuse operation mappings via WebService)

The second question is related to ACK support inside PO: is it possible to natively configure one step inside the Netweaver BPM of PO where we wait for a Technical or Application ACK coming from the PI component of the same PO instance?

Third question: when will end the PI double stack installation support?

These are by my point of view the main questions that anyone who has faced this migration should have met.

Anyone has found official answers?

Thank you

Best Regards

Enrico Barsali

Hi all,

is it possible to measure the number of messages in JAVA Stack of a specific adaptor within a specific time period ?

For example: All messages sent via SOAP adaptor in February.

What about the performance-monitor ? Is it able to do just that ?

SAP PI 7.31

No Solution Manager implemented.

Thanks in advance and BR

Lars

Dear All expertd,

We have set up a new SAP PO server and just want to know how to do below configurations which was done in ABAP stack in previous versions..

• How to peform SLDCHECK ?
• Message Schedulling (RZ70)
• ECC / PO cennection set up..
• and How to check ECC and PO connections are working fine and SLD working fine.

Thanks

Hello Experts,

In a specific scenario, I need to use PI Axis receiver channel to push the message to a IBM MQ (SOAP over JMS).

I have been able to configure it properly with the FAQ attached to SAP Note 1039369 and the message is getting properly delivered to MQ. But, I am not able to set the "ReplyTo" header. I looked at related SAP Note 1893092 but could not resolve the issue.

Please let me know as how to achieve this.

Thanks & Regards,

Ankit

Hi Experts,

i had a requirement where i need to integrate the data between the third party system and C4C Via process orchestration. and the third party can only be communicated through the API . So how can i expose the Rest based webservice in process orchestration.Please help me

Thanks

Giridhar