B2B Integration with SAP NetWeaver Process Orchestration

EDI-XML conversion in SAP B2B Add-on: Some known problems & solutions

Ruchir Sinha — Mon, 13 May 2013 08:47:35 GMT

Why read this blog:

After sharing experiences with some of the customers I came across some common problems faced by them. I became very keen to write about this as it might help some people who are adopting PI B2B Addon. Please share your experiences as well.

Problem in focus:

Similar problem can be seen with different combinations of Message Type / Version.

Route to the problem :

Mentioned below are the steps that are generally followed by the customers. In executing these steps you will encounter the error that has been discussed in this blog

1. PI B2B add-on is deployed and the requirement is to use the EDI - XML converters. Mainly EDIFACT and ANSI X12.

2. Import the B2B content file via the Import option available in EDI Content Manager.

3. To modify an existing message type use the Control Key Copy functionality in the Message Editor view of EDI Content Manager.

4. This creates a new Control key (Demo1) with the selected Message types (say for example INVOIC, DESADV for version 96A) from SAP Control Key. They have this Control Key for these message types.

5. To test some of the conversions create a scenario association.

6. If the correct Control Key Name/ Interface index is selected, then testing the conversion for INVOIC and DESADV is successful. Hence, select the correct control key in this case it is Demo 1/2.

7. The problem becomes apparent when the user wants to convert a different message type that is not included in the control key Demo1. For example ORDERS is present in SAP Control key. But even on selecting the combination of SAP / 1 while conversion the error persists.

8. The error look something like below:

Solution:

In above example since both the rows in the scenario association table has all the entries as '.*' so during conversion time control key Demo1 is picked (even though in the conversion page SAP / 1 was selected). As we know Demo1 did not include ORDERS message type so the conversion error occurs.

This is not a bug. The mistake the end user does is in step number 5. If one goes through the PI B2B Addon's official documentation then it is mentioned that a PI scenario (i.e combination of Sender Party, Sender Service, Receiver Party, Receiver Service, Interface name, Interface namespace) should be associated with only one Control Key Name.

This essentially means that there should be no two same PI scenarios associated with different control keys because each control key is meant to be executed with a different PI scenario.

So if the second row is changed to some thing similar to below screen shot then the conversion will work. (Provided FS_ER is a valid Party )

The SAP PI B2B add-on EDI capabilities unveiled

Dimitri Sannen — Sun, 28 Apr 2013 12:21:00 GMT

Why this blog?

After working with the Seeburger Generic EDI adapter for years, I was really keen on exploring the EDI capabilities of SAP's new B2B add-on. I wrote this blog to share my thoughts and experiences with the community.

Scope and context

The content of this document is based on experience with several scenarios I created on a SAP PO 7.31 (AEX) system using both UTILMD and UTILTS message structures.

I started using the B2B add-on beginning of February 2013 and had these scenarios in mind:

Processing incoming EDI messages
Create EDI messages, based on data coming from an SAP ECC backend system
Generate CONTRL messages
Use the Number Range Object to meet message requirements

It all began with downloading and installing the PI B2B ADDON 1.0…

The journey to success

Before going into details, let me first highlight a brand new tool: the B2B Integration Cockpit.

It has been introduced as a new central console that contains relevant links to all B2B components and it is a central application that allows you to monitor and access the B2B add-on from a SAP NetWeaver Process Integration or Process Orchestration platform.

With the installation files, SAP ships content, which must be loaded into the edifact tables within the EDI content manager. There my first problem popped up…

The shipped content is not 100% compliant with the message structures we use in Belgium. Therefore I needed to modify them.

Doing this was really not easy and made me longing for the Seeburger Workbench, where editing message structures is a piece of cake.

Once the message structures were ready, I loaded them into the ESR, using the B2B integration cockpit for generating the XSD files.

After a lot of try-outs and encountering many problems, I had to upgrade to support pack 1, due to several bugs in the EDI part. You can find release notes in OSS note 1785396.

After experimenting with splitting EDI messages and trying to process them, I again had to apply 2 OSS notes (1833693 and 1848340) to solve problems with the EDISeparator adapter.

This brand new adapter is used to split, convert and process EDI messages, together with the new adapter module EdifactConverterModule.

Please be careful with the module name. It’s case sensitive and in some SAP reference materials, the Edifact part is stated in capitals.

My conclusion

In the beginning, I encountered a lot of problems and bugs and was not able to generate CONTRL messages.

Now, SAP fixed a lot of bugs and the B2B Integration Cockpit is very nice to use, except for editing message structures.

The EDISeparator adapter integrates smoothly and is very straight-forward.

My guess is that, in the longer term, SAP’s B2B add-on could be dreaded competition for the Seeburger Generic EDI adapter.

Next steps

In the near future, I will explore the functional monitoring as stated in OSS note 1815991 and will try to improve my scenarios and the system (via for example OSS note 1832269).

Questions or remarks?

If you have a (technical) question concerning the installation, configuration or usage of the B2B add-on, feel free to send me an e-mail or post your thought or question.

SAP PI Integration with SBN/Crossgate

Jaya Prakash Kavuri — Tue, 05 Mar 2013 10:31:13 GMT

We have good number of articles in SCN listing the benefits of an On Demand solution

or a Cloud based solution. This article outlines the integration approach while integrating

with EDI Trading partners through SBN/Crossgate using PI.

Canonical Integration pattern is the underlying EAI pattern used while integrating

with Crossgate or SAP Information Interchange (SAP II) On Demand Solution.

There is a SAP II message format for each of the business transactions like Purchase Orders

(EDI 850) or Purchase Order changes (EDI 860) or Invoices (EDI 810). This SAP II message

format would be the intermediary structure or the canonical message format.

For outbound interfaces, in PI we will map the IDOC structure to the corresponding SAP II XML

message format and send it over to SBN over HTTPs. In SBN, the SAP II message format will be

transformed into EDI message (like EDI 850) and sent over the trading partner’s mode of

communication (like AS2/VAN etc.) based on trading partner profile maintained at SBN.

Since SAP II XML message is the canonical format, we only need to map from IDOC to SAP II XML

message format per EDI transaction, the customer specific mappings would be taken care at SBN

depending on the EDI Guidelines document of trading partner shared with SBN. So, it is all the more

important to share the latest or updated EDI Guidelines document of trading partner with SBN.

For inbound interfaces, in PI we will map the SAP II XML message format received over HTTPs in PI

to the IDOC structure and post the IDOCs into ECC.We can also have a reconciliation of the EDI

messages sent out by receiving the EDI 997 (Functional Acknowledgement) from trading partners

through SBN. SBN also provides a web based monitoring solution called Satellite

for monitoring the EDI traffic and reconciliation.

While this is one of the integration approaches while working with an On Demand Solution like SBN,

the contractual agreements with SBN spell out the actual segregation of work like what functionality SBN

will provide and what Customer/SI needs to do. There could be other ways of integrating with SBN and

depending upon the integration approach, the contractual agreements with SBN may also vary.

B2B AddOn and SFTP PGP (secure connectivity addon) SP1 released

Piyush Gakhar — Mon, 04 Feb 2013 19:01:42 GMT

Business to business Add-On and Secure connectivity add-on SP1 is released with lot of new enhancements.

Installation: All existing customers who are on SP0 can use standard SAP tools (MOPZ to download the latest SP) and install it using SUM/JSPM tools. All new customers can directly go to SMP, download SP1 from support package and patches area and install it using SUM/JSPM tool. For more details, please refer to SP1 installation guide on SMP. You should have installed SP1 of secure connectivity Add-On first before installing B2B Add-ON.

Documentation:

Configuration guides (Application Help) is now available at help.sap.com (along with NetWeaver PI documentation). Corresponding links are:
http://help.sap.com/nw-b2b-addon
http://help.sap.com/nw-secure-connect
Installation/Master/EDI Content/Security guides are available at https://service.sap.com/instguides > SAP NetWeaver > SAP NetWeaver Process Orchestration, secure connectivity add-on > SAP NetWeaver Process Orchestration, secure connectivity add-on 1.0 SP01/business to business add-on SP1

What's New:

Secure Connectivity Add-on (SFTP PGP Add-on)

Operating System Command support has been introduced for both the sender and receiver channel.
Polling interval has been changed from minutes to seconds
User defined time configuration option has been introduced for duplicate check
PGP Module has been enhanced to indicate an error in case of wrong choice or missing algorithm instead of choosing default algo.

Business to business Add-on (B2B Add-on)

All Adapters: Acknowledgment handling and Monitoring:

A new XI message can be created from the received technical acknowledgment. These options are provided in the receiver communication channels of OFTP, AS2 and sender communication channel of X400. The created XI messages can be configured based on receipt of both negative and positive or only negative acknowledgments. Such XI messages are processed by newly introduced special ack sender communication channel modes in AS2, OFTP and X400 adapters.
Local message monitoring of PI has been enhanced to support monitoring of acknowledgments as well. You can monitor sent/received technical (MDN, ERP, Delivery Reports) acknowledgements and functional acknowledgments (Control, 997) related to the XI messages via local message monitoring. Both consolidated and detailed status views are available. For more details, refer to SAP Note 1815991.
Now you can search and view all related messages. You can use this option to display all the correlated or referenced messages (Original bulk message and corresponding split messages by EDI Separator, original message and technical acknowledgment messages created as new XI messages).
MDN, ERP and Delivery Report definitions are shipped as part of ESR content.

AS2 Adapter:

AS2 adapter has been enhanced to provide SHA-2 signature algorithm support for messages and MDNs.
Incoming HTTP(s) authentication is made mandatory.
Duplicate message check has been introduced on sender channel with user defined time duration based configuration.

OFTP Adapter:

Duplicate Message check has been introduced on sender channel with user defined time duration based configuration.
Both sender and receiver channel have been enhanced to provide archiving at different stages (incoming/outgoing raw wired message, encryption/decryption, encoded/decoded).
Few parameters are made optional in AMD for flexibility.

EDI Separator and Functional Acknowledgments

Support of CONTRL has been introduced with different levels and flexible configuration options.
997 support has been enhanced with multiple configurable options.
EDI Separator is enhanced to accept any of the four predefined message types EDIFACT, X12, ODETTE, VDA in one communication channel (earlier you had to select from drop down and only once EDI format as supported per receiver communication channel).

New Generic adapter module: New adapter module is introduced that can be used with both sender and receiver channels. It automatically detects the predefined EDI formats supported by SAP and process them accordingly. Now you can use one communication channel for receiving/sending multiple EDI formats.

New Customization UIs: New intuitive UIs have been introduced to maintain, view and customize the EDI content with version control mechanisms. This UI is role based and is restricted by authorized access.

All Converter Modules (including new Generic module) are enhanced to provide new adapter module parameters like encoding, indent, copy etc.

New EDI Content:New EDI messages types have been introduced for VDA (4921) and many more for EDIFCAT. Please refer EDI Content guide available on SMP for more details.

B2B Integration Cockpit: A central page has been created to access all B2B tools (NRO, EDI Content Manager, OFTP Log Viewer). You can access it via http(s)://host:port/b2bic

NRO and Archiving Module: NRO configuration values can now be dyncamically configured/customized by APIs. You can also use these APIs for mass configuration/migration. Archiver module now supports multiple archive files for different use-cases.

Performance Optimizations: Cache optimizations have been done for various EDI converters.

Solving Authentication Issue by using TCPMON Tool

VENKATA RAMESH BOPPANA — Sat, 02 Feb 2013 20:13:06 GMT

Scenario: SOAP to RFC Scenario.

Problem: For our client requirement, we have done the SOAP to RFC scenario development. We generated the WSDL file and tested the interface by using SOAP UI tool and it is working perfectly. When Web sphere commerce team started testing the interface, they are getting 401 unauthorized errors; though they are using the same credentials.

Investigation: We tried to different options like

Anonymous login (disable the options in PI) but later we realize that this is not possible for one scenario
Implement HTTP to RFC scenario (remove the SOAP headers by using XSLT mapping) instead of having SOAP to RFC interface, but our client is not agreed for this.
Other option is needs to select security profile parameter as no in service interface but we are using PI 7.1 server so this option is not available

Resolution: Then we tried digging the issue why it is working for SOAP UI but not Web sphere commerce, for this we used TCPMON tool to get some inputs/logs.

We installed the TCPMON tool in our machine.

Go to build directory (\tcpmon-1.0-bin\tcpmon-1.0-bin\build) then double click on “tcpmon.bat” file

Now go to Admin tab

127.0.0.1 Is the default IP for the local machine (Any machine).

Here Listen port we can give any free (available [no application is using this port]) port (7878 or 6969 …) and provide the target system details (PI Host and port), then click on Add

Then we got another tab like

Actual URL:

http://<<Host_Name>>:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_WebCommerce&receiverParty=&receiverService=&interface=SI_GIA_OB_Sync&interfaceNamespace=urn:venkataramesh.com

But we are sending data through TCPMON so give the TCPMON IP and port details, finally URL is

http://127.0.0.1:7878/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_WebCommerce&receiverParty=&receiverService=&interface=SI_GIA_OB_Sync&interfaceNamespace=urn:venkataramesh.com

Now we sent request to PI from SOAP UI tool through TCPMON.

Once TCPMON tool get the request it re-directs to XI/PI server.

After sending the request from SOAP UI tool TCPMON captured some data in header, that header contains "Authorization: Basic UElXU1VTRVI6RTNqdms0NjM=" line, but when we send the data from our actual source (Web sphere commerce) we don’t get this tag, so always PI expects the data in the form of encryption.

TCP MON Screen after it receives the request

Initially Web sphere commerce screen was

We added below code to “wc-server.xml” file and enabled the option userNameHttpAuthentication and passwordHttpAuthentication as true

Code:

<EditableProperty

Admin="userNameHttpAuthentication"

display="false"

editable="yes"

name="setBasicAuthenticationName" value=""/>

<EditableProperty

Admin="passwordHttpAuthentication"

display="false"

editable="yes"

encrypt="Yes"

name="setBasicAuthenticationPassword" value=""/>

<EditableProperty

Admin="SOAPAction"

display="false"

editable="yes"

name="setSOAPAction" value=""/>

After adding the code screen is

Note: Before adding above code, in web sphere screen we have only User Name and Password fields, after add the above code userNameHttpAuthentication and passwordHttpAuthentication fields are came; now we are giving the credentials in this area.

Now, we send request by giving the PI credentials and monitored the data in TCPMON, at this time web sphere commerce sends the user credentials in encryption format and data was posted in ECC system successfully.

B2B- EDI Inbound -Step by Step Configuration

Rahul Malani — Thu, 27 Sep 2012 11:36:14 GMT

I believe readers of this blog aware of new B2B Add-on for SAP PI through available content on B2B integration space. Those who are not aware, it's new offering by SAP for B2B integration in SAP PI space.

In this blog I’ll discuss step by step configuration in inbound EDI (EDI from Partner) scenario.

Scenario: Inbound EDI (EDI from Partner)

In this example scenario I have configured file sender to pick EDI Message, instead of AS2 Sender or some other technical adapter. Receiver side, instead of IDoc receiver I am storing IDoc in XML format in file system.

Incoming EDI message comprises of following EDI message of ANSI X12 Message format.

810: Invoice 850: Orders

Message format: ANSI X12 Message format: ANSI X12

Version: 4010 Version: 4010

ESR Objects:

To maintain the focus on Configuration using new B2B adapters, I am not going into details of ESR objects here.

Integration Directory:

Message Flow:

Step 1. EDI message comprising multiple business transactions received in SAP PI by available technical adapters.

Step 2. Receiver EDI Separator Adapter split received message into individual business transaction message.

Step 3. Individual messages then mapped to target messages in SAP PI.

Step 4. Acknowledgement generated and sent back to sender of EDI message [Only available in case of ANSI X12 messages now].

Step 5. Transformed message then sent to receiver using available technical adapters.

To configure this scenario we have to configure two types of Interfaces.

Interface 1: From EDI Sender to EDI separator adapter [Step 1 and 2 above]

Deliver the incoming EDI message [Comprises multiple business transaction] to EDI separator adapter.
Split EDI message [Comprises multiple business transaction] into individual business transaction message.
No need to create any service interface in ESR. Use dummy interface.
No EDI to EDI XML conversion in this interface.
No mapping.

Interface 2: From EDI Receiver to backend system [Steps 3 and 5 above]

Process individual messages separated in interface 1.
Interface needs to be configured for each individual message and for each pair of sender and receiver.
EDI message converted in EDI XML format.
EDI XML message transformed to target message.

Interface 1 Configuration:

Sender Agreement:

File Sender Communication Channel:

I’ll describe the reason to keep file name as ‘*ANSI*.*’ later in the blog.

Receiver determination:

Interface determination:

No mapping in this interface.

Receiver Agreement:

EDISeparator Receiver communication channel:

Message Protocol is ANSI X12, since in example inbound EDI message contains ANSI X12 messages.

After processed through Separator interface EDI message split into individual EDI message. Here in our example incoming EDI message splitting into two messages - 810 and 850.

Once message separated, adapter start searching sender communication channel for the particular business transaction and partners. In our example it will search for following sender communication channels

Transaction 810, Version 4010, Sender ID 1111, Receiver Id 2222
Transaction 850, Version 4010, Sender ID 3333, Receiver Id 4444

It is required to configure two interfaces to process these messages.

Interface 2 Configuration:

Here I have configured interface only for Transaction 810, Version 4010, Sender ID 1111, and Receiver Id 2222. Similarly it can be configured for other message.

Sender Agreement:

In ESR configure service interface using XSD of transaction 810 and Version 4010.

EDI Separator Sender Communication Channel:

EDISeparator sender Communication channel configured for Transaction 810, Version 4010, Sender ID 1111, and Receiver Id 2222.

Module X12ConverterModule configured in Module parameter of communication channel to convert EDI into EDI XML.

Receiver determination:

Interface determination:

In ESR mapping has to be developed to map EDI XML to Invoice IDoc.

Receiver Agreement:

I have not configured IDoc receiver channel, instead I am using file receiver channel to store invoice xml in file system.

In similar way interface can be configured for other separated message. Please find below the screenshot of the EDISeparator communication channel which I have configured in this scenario.

Execution:

You can see in the above screenshot, first message belong to the interface which split the messages and other two messages belongs to the 810 and 850 message processing.

Scenario 2:

In real-time scenarios it may possible that same EDI partner sends different formats of messages, say ANSI and EDIFACT. In that case we have to configure separate EDISeprator receiver communication channel in Interface 1 for EDIFACT message Foramt. Route the message based on content [message format] to the different receiver [EDIFACT or ANSI].

Since in interface1 EDI to EDI XML conversion not occurred, so inbound payload remains in raw EDI format [not in EDI XML], so it is not possible to add condition using XPATH in receiver determination. Possible solution from the discussion raised in SDN:

1) Use different communication channels on sender side. They may point to same input folder where you can provide different file names for EDIFACT and ANSI bulk messages respectively.

I have opted this solution in this example for simplicity and to maintain focus on the main objective.

2) Wait for new support package for B2B where SAP planning to provide this enhancement.

I believe from the planned enhancement there will be no need to configure message format in EDISeparator receiver.

3) Workaround:

a) Write a custom adapter module (to be used on sender side) which can read incoming message and create an XML message with root tag describing the message type (say EDIFACT or something) based on received bulk message. You need to add these XML tags after reading the headers of the incoming EDI messages. Add this custom module to your sender channel.

b) Add two different receivers to the same scenario. And provide condition based on value of XMl Tags you have added during your module development.

c) Now your message is routed in the right manner to the respective EDI Seperator receiver channel. Write another module (or enhance the same adapter module) which can remove these XML tags and convert the payload back to plain EDI bulk message (which you received initially) and use this module in EDI Separator receiver channels.

Thanks for reading !!

Quick guide to the SAP’s B2B offering with SAP NetWeaver Process Orchestration

Katrin Ahsen — Tue, 25 Sep 2012 07:39:11 GMT

After introducing the B2B add-on for SAP NetWeaver Process Orchestration and the new Rapid Deployment Solution (RDS) for Electronic Data Interchange (EDI) we have seen a lot of interest and questions. This blog aims to address main questions in a comprehensive way and help you understand the B2B offering with SAP NetWeaver Process Orchestration.

Technical details about the B2B offering can be found in the B2B Integration with SAP NetWeaver Process Orchestration space on SCN - see http://scn.sap.com/community/b2b-integration. The learning series about the B2B add-on provide information how to configure adapters, modules, implementing B2B integration scenarios etc. For details check "Process Orchestration Resource Center: Business to business add-on".

The new Rapid Deployment Solution (RDS) for Electronic Data Interchange (EDI) in a nutshell

In general, SAP RDS is a packaged solution offering which consists of SAP software, pre-configuration and an implementation service. The RDS for EDI consists of the following components:

the B2B add-on (the SAP software)
a set of mapping templates (meaning pre-configuration) and
the installation of the B2B add-on and mappings and the configuration of B2B integration scenarios (or the implementation service).

Shall we license the RDS for EDI or can I only license the B2B add-on?

The B2B add-on is the software piece of the RDS as described above and is identical with the one which you can license independently from this RDS, too.

Several SAP customers are already implementing the B2B add-on separately. Others opted for the Rapid Deployment Solution offering to get avail of the pre-configuration and implementation services from SAP.

The Rapid Deployment Solution (RDS) for EDI is based on the B2B Add-On but delivers predefined mappings for the order-to-cash and procure-to-pay processes (IDoc <-> EDIFACT or ANSI X.12). As usual for an SAP RDS, it comes together with an implementation service.

Depending on your business needs and project timelines you can choose the option that fits your organization best.

Can I get the mapping templates of the RDS independent from the same?

No. But the B2B add-on already comes with a set of mapping templates allowing implement some B2B integration scenarios quickly which is often needed when performing proof-of-concepts. For this purpose the B2B add-on contains some sample mappings for all EDI standards supported by this solution.

Opportunities for SAP Partners organizations

Rapid Deployment Solutions provide lots of opportunities for SAP Partners, ranging from reselling to co-innovation. Partners can sell and implement SAP RDSs and/or define partner-led RDS. Actually the latter case is very appealing for EDI with SAP NetWeaver Process Orchestration as there are lots of opportunities for delivering industry specific RDS in addition to the new SAP RDS for EDI. Partners who are interested can find general information how partners can contribute and benefit from RDS here.

SAP provides SAP software products at special terms and conditions for partners for non-productive use. Find overview information, prerequisites and contacts in the “Get started section”. Explore possible options at SAP Partner Edge here. The B2B add-on is included in many SAP Test and Demo licenses for partners - such as the Demo SAP NetWeaver Foundation Package and the Demo SAP NetWeaver Foundation Package for 3rd Party Application Package.

Accessing SAP content on SMP

Anyone who is registered with SAP Service Marketplace can search for the SAP notes about the B2B add-on at http://service.sap.com/notes.

In addition to the B2B offering with SAP NetWeaver Process Orchestration, SAP provides a very comprehensive solution portfolio for B2B integration options with Crossgate.

Many of our existing customers can drive the greatest benefits from consolidating their middleware solutions including legacy B2B gateway solutions via upgrading to SAP NetWeaver Process Orchestration.

Also recommended: Read this blog by Piyush Gakhar who introduces the SAP Strategy for B2B Integration. SAP has a 360 degree solution approach covering all aspects of the B2B integration needs of your organization: OnPremise, OnDemand and Hybrid. Covering all available B2B solutions from SAP, this paper helps you determine when each of them is best to be used.

We look forward to your feedback.

Configure the HTTP_AAE receiver communication channel with SSL

VENKATA RAMESH BOPPANA — Tue, 18 Sep 2012 19:11:32 GMT

In this blog I would like to discuss how to configure Java based HTTP adapter (HTTP_AAE) receiver communication channel configuration by using HTTPS URL.

Business requirement: Currently we are using SAP PI 7.31 Java only system, we need to send the data to customer by using java based HTTP (HTTP_AAE) adapter with HTTPS URL.

To use the HTTPS url we need to activate SSL and apply HTTPS certificate

Generate SSL:

Lo-gin to NWA->Configuration->Security->Certification and Keys

Select “Service_ssl” key store view then click on Create button

Provide the Entry name, Algorithm, Key length and valid date details and click on Next

Provide the details then click on Finish.

Download the entry which we created by clicking “Generate CSR Request” button.

Apply the certificate (After download we will send this to certificate authority like VeriSign or mail or ….. then they will add keys and send back to us).

Now we have 2 or 3 certificates (Root, Intermediate [optional, if any 3^rd party person is there in the middle then we can get this certificate] and system certificates). Place all the certificate keys in one file [must be in order as Root, Intermediate and System certificate keys] then import the same file to PI server by clicking “Import CSR Response”

Then provide the certificate path

Activate SSL

NWA->Configuration->Security->SSL

Click on Edit then click on Add button in SSL Access points

Give PSE file path (File path is //usr/sap/<SID>/J<Instance_number>/sec)

Note: PSE file generates when we are installing the PI server, this file stores in the above path and this file contains system information.

Now SSL is active.

HTTPS certificate.

This is a separate certificate we need to generate and send to the certificate authority then apply the certificate (same like above process but here we need to apply the root, intermediate and system certificates separately).

Root certificate

And next update the Intermediate and system certificates on “Trusted CAs” tab

restart the server.

HTTP_AAE Receiver Communication Channel Configuration

My client provided 2 URLs, one is HTTP URL and the second one is HTTPS URL.

URLs are as follows

In receiver HTTP_AAE communication channel with HTTP URL is normal, we just gives the HTTP server and URL details.

HTTPS URL Configuration:

HTTP_AAE communication channel with HTTPS URL

Use SSL: If we select this option means we are using HTTPS URL, if customer wants certificates then we can select certificate checkbox and provide the certificate details.

Let’s go to communication channel monitoring and ping the communication channel (HTTP)

Ping the communication channel in communication channel monitoring (HTTPS).

Conclusion:

I believe this blog would provide better understanding of how to configure the java based HTTP adapter receiver communication channel by using HTTP and HTTPS URLs.

References:

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/6d/c2b39dae45482e90d3352345cbf427/frameset.htm

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/cbb493cea80783e10000000a42189d/frameset.htm

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4a/015cc68d863132e10000000a421937/frameset.htm

B2B Integration Strategy (OnPremise, OnDemand and Hybrid)

Piyush Gakhar — Mon, 17 Sep 2012 11:05:21 GMT

In all different industry verticals, there is a growing need for connecting to Business partners and networks. The B2B integration space is diverse and vast. There is growing demand from business perspective including Process Management, low TCO, quick ROI, leveraging existing investment, outsourcing, support for different EDI formats etc. Also, B2B technical (protocols and security) integration capabilities that customers desire to use out of the box with a B2B integration solution.

Different needs resulted in different integration models for organizations and a 360 degree solution approach from SAP covering all aspects

1) OnPremise: SAP NetWeaver Process Orchestration/Integration with inbuilt B2B capabilities

2) OnDemand: SAP Information Interchange OnDemand

3) Hybrid: Mix of OnPremise and OnDemand (1 and 2)

Various B2B solutions are available from SAP, so the obvious question is When to use What?

Have a look at the below article and it will give you a glimpse of EDI introduction, customer requirements, market trends, available solutions from SAP and the most common decision criterias.

SAP’s B2B Integration Strategy: OnPremise, OnDemand and Hybrid: https://scn.sap.com/docs/DOC-31685

We look forward to your feedback.

Regards,

Piyush

Dynamically providing URL and action values to receiver SOAP communication channel

VENKATA RAMESH BOPPANA — Sun, 16 Sep 2012 21:33:58 GMT

In this Blog I would like to explain how to provide the URL and Action values dynamically to the receiver SOAP communication channel.

Scenario: ABAP Proxy to SOAP Synchronous scenario.

Requirement: Get the currency conversion (exchange) rates by requesting one of the web services (Xignite), Here we have 3 types of scenarios are there

Get the daily conversion rates
Get the monthly average conversion rates
Get the month end conversion rates

We are using one SOAP sender communication (XI as message protocol) channel for all the 3 types of scenarios. Initially we thought to create 3 separate SOAP receiver communication channels for 3 scenarios because the action and URL is different for all those 3 scenarios, Later tried to use single communication channel and provided the URL and action dynamically.

For every scenario, sender side we creates 2 data types for Request and Response and receiver side we are using WSDL methods.

Similarly we create Message types and Service interfaces

In request mapping we need to create one UDF to dynamically provide the URL and action parameters

Created simple type UDF (dynamicallyProvidingURLAndAction), this UDF takes 2 inputs, First one is for the URL and second one is for Action.

UDF is as follows

Code:

DynamicConfiguration conf = (DynamicConfiguration)container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);

DynamicConfigurationKey key=DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TServerLocation");

conf.put(key, url);

key=DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "THeaderSOAPACTION");

conf.put(key, action);

return "";

This UDF output map to the root node of target structure

We provided below 2 values as input to the UDF

URL value is http://www.xignite.com/xCurrencies.asmx

Action value is http://www.xignite.com/services/GetRealTimeCrossRates

For other 2 scenarios in requesting mapping UDF, these 2 input values are different.

Configuration:

Business system/service, Sender communication channel and integrated configurations are normal.

Receiver CC

Target URL parameter is the mandatory field so we can give any value (at runtime it is replaced by the value which is provided in request mapping), and no need to give any value at action field because it is not a mandatory parameter. If any credentials required to login to web service then we can give those credentials by selecting checkbox of “Configure user Authentication”.

In advanced tab, we need to select the Use adapter specific message attributes and Variable transport binding check boxes then provide the values (these values we used in the Dynamic configuration UDF). At runtime TServerLocation parameter takes the URL value from dynamic UDF and THeaderSOAPACTION parameter takes the action value from dynamic UDF.

Scenario configuration is completed.

Testing

Scenario-1:

Input from Sproxy transaction of ECC system

Output

Scenario-2:

Input

Output

Scenario-3:

Input

Output

Conclusion:

I believe this blog would provide better understanding of how to provide the URL and Action values to Receiver SOAP communication channel in order to create n-number of receiver communication channels for a same web-service.

References:

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/327519a3af58d8e10000000a421937/frameset.htm

SFTP Adapter - Installing SFTP Server on Windows - Part 04

Sivasubramaniam Arunachalam — Mon, 13 Aug 2012 15:30:44 GMT

This is the forth and final post in the series "SFTP Adapter - Installing SFTP Server on Windows". If you have not read the previous posts, you can refer the below links.

SFTP Adapter - Installing SFTP Server on Windows - Part 01

SFTP Adapter - Installing SFTP Server on Windows - Part 02

SFTP Adapter - Installing SFTP Server on Windows - Part 03

This post describes the steps to test the localhost SFTP server using private key based authentication feature which available in SFTP Adapter which is a part of Secure Connectivity add-on.

Navigate to http://localhost:50000/nwa/key-storage
Create a view called "SFTP_KEY"

Click on "Create" which is under "View Entries" Tab
Provide the Entry Name (e.g. mykey)
Select the "Store Certificate" option
Click on "Next"

Provide the common name (e.g. mykey)
Click on "Finish"

Select the certificate entry (e.g. mykey-cert)
Click on "Export Entry"
Choose "Base 64 x.509"
Click on "Download" link

Save the certificate in the user's home directory

Open the ssh console by using the steps mentioned in SFTP Adapter - Installing SFTP Server on Windows - Part 02
Convert the SSL keys into SSH keys using openSSL utility
- $ openssl x509 -in mykey.cert -noout -pubkey > mykey.pkey

Convert the SSH key into OpenSSH key format using ssh-keygen utility
- $ ssh-keygen -i -m PKCS8 -f mykey.pkey > mykey.ssh.pkey

Add/Append the content of the OpenSSH key to "~/.ssh/authrorized_keys" file
$ cat mykey.ssh.pkey > .ssh/authorized_keys
Verify the read access

Modify the SFTP sender channel configuration to use the above created private key

Activate & Start the channel. The channel short logs should look like below

The above logs shows that it can able to successfully connect to the SFTP server using the configured private key and downloaded the file.

That's end the series. Cheers

SFTP Adapter - Installing SFTP Server on Windows - Part 03

Sivasubramaniam Arunachalam — Mon, 13 Aug 2012 14:16:08 GMT

This is the third post in the series "SFTP Adapter - Installing SFTP Server on Windows". If you have not read the previous posts, you can refer the below links.

SFTP Adapter - Installing SFTP Server on Windows - Part 01

SFTP Adapter - Installing SFTP Server on Windows - Part 02

This post describes the steps to test the localhost SFTP server using SFTP Adapter which available as part of Secure connectivity add-on. It also consists of steps to generate public key finger print and channel configuration for password based authentication.

Create a test file in the SFTP server using the following command
- $ cat >test.txt
- Enter the test data
- Ctrl + Z to save the file

Check the existance of the file and relevant permission
- $ ls -l

Generate the public key finger print using the steps mentioned in How to Determine the Public Key Finger Print of a SSH Server
- $ ssh-keygen -lf /etc/ssh_host_rsa_key.pub

Configure the SFTP Sender with the following values
- Configure the server host as localhost
- Use the above generated server finger print
- Use the OS user credential for authentication (The user account which is used for testing in the previous post)
- Use the created test file in the first step

Activate & Start the channel. During execution, the channel short log will look like below

The content of the message can be verified by opening the same message in monitoring

This verifies that the the locally installed SFTP server works perfect with PI SFTP Adapter. The next post in this series covers the steps to generate the SSH Private Key and test the SFTP Adapter using the locally installed SFTP Server(using private key based authentication)

RDS for EDI available now!

Katrin Ahsen — Mon, 13 Aug 2012 12:52:43 GMT

Would you like to migrate from your legacy B2B gateway solution towards SAP NetWeaver Process Orchestration with the B2B add-on but are concerned about the effort this might take? Then take a look at our new SAP NetWeaver Process Orchestration Rapid Deployment Solution for Electronic Data Interchange (RDS for EDI). With this solution B2B integration scenarios related to the order-to-cash and/or procure-to-pay process of SAP ERP are being implemented through a service. Fixed scope and price provides maximum predictability and lowers risk. As usual this RDS comprises of SAP software, an implementation service and content.

Software scope: B2B add-on & predefined mappings

The RDS for EDI integration comprises of the B2B add-on for SAP NetWeaver Process Orchestration and pre-defined mappings and configurations for the order-to-cash and procure-to-pay process allowing to convert SAP IDocs into EDI messages of the EDIFACT or ANSI X.12 standard and vice versa. Predefined mappings ensure a fast implementation at high quality allowing to onboard your business partners smoothly. Please note that this RDS technically runs on the SAP NetWeaver Process Integration product. This means that you don't require a SAP NetWeaver Process Orchestration license or SAP NetWeaver BPM for being able to use this RDS.

Service scope: Selectable number of B2B integration scenarios

The predefined service allows you to go live with your new B2B integration scenarios on SAP NetWeaver Process Orchestration in roughly 5 weeks assuming your business partners will be ready on time, too. In summary the following services are being delivered as part of the RDS:

Installation of the B2B add-on
Deployment of the predefined mappings
Enablement workshop
Implementation of a selectable number of B2B integration scenarios based on the predefined mappings in a non-productive environment
Go live support

As you can select the number of B2B integration scenarios to be implemented through this predefined service you have the choice of leveraging this RDS as jumpstart for your migration project only or to do further migrations with it.

Content & Enablement: SAP Best Practices for Process Orchestration

As part of the service delivery many knowledge transfer measures are provided – for instance as part of the enablement workshop, training of key users and hand over procedure. In addition to that high quality documentation and SAP Best Practice documents will enable you to develop your B2B implementation further as needed. The following SAP Best Practices for SAP NetWeaver Process Orchestration are delivered as part of this RDS:

SAP Best Practice for General Configuration within Integration Directory
SAP Best Practice for B2B Add-On Deployment and Configuration
SAP Best Practice for Configuration Design Objects within Enterprise Service Repository

Looking for more information?

You can find more details about the RDS for EDI Integration such as scope of predefined mappings and service, system requirements at the SAP Service Marketplace at http://service.sap.com/rds-edi (requiring SMP user login).

SFTP Adapter - Installing SFTP Server on Windows - Part 02

Sivasubramaniam Arunachalam — Sat, 11 Aug 2012 04:20:07 GMT

This is the second post in the series "SFTP Adapter - Installing SFTP Server on Windows". If you have not read the previous post, you can refer the below link.

http://scn.sap.com/community/b2b-integration/blog/2012/08/10/installing-sftp-server-on-windows--part-01

This post describes steps for auto configuring, starting the SSH service and testing using SSH & SFTP Clients.

Open the "Cygwin Terminal" from the start menu

It will automatically create all the files which is required for user profile (Similar to Linux/Unix)

To configure the SSH Service (where SFTP Server runs) automatically, execute the following command

$ ssh-host-config

It will automatically creates all the keys & certificates required for the SSH Service/SFTP Server
After that it will try to install the SSH Service/SFTP Server as a windows service
Answer "Yes" for all the question except the last query mentioned in the below snippet
For the question "Do you want to use a different name? (yes/no)", Answer "No"

Answer "Yes" for the next question to create the username and provide the password for the same user to be created
It will complete all the required steps to configure the SSH Service/SFTP Server

Next, the SSH Service/SFTP Server should be started manually by executing the following command

$ cygrunsrv.exe -S sshd &

The SSH access can be tested by executing the following SSH Client command

$ ssh admin@localhost

Accept the finger print and provide the password for the user 'admin' (or any OS user)

The "pwd" command (present working directory) can be used to find the location of home directory. By default it would be "C:\cygwin\home\admin"

The SFTP access can be tested by using any of third party SFTP supported clients like FileZilla. The default port for SSH Service & SFTP Server is 22

Click "Quick Connect" and accept the finger print

It will successfully connect to the SFTP Server.

It is verified that SFTP Server is installed properly and up & running. Now, it can be used with SFTP Adapter for file transfers.

The next post in this series covers the steps to configure and test the SFTP Adapter using the locally installed SFTP Server.

SFTP Adapter - Installing SFTP Server on Windows - Part 01

Sivasubramaniam Arunachalam — Fri, 10 Aug 2012 16:09:26 GMT

The recently launched SFTP Adapter (as part of SAP Secure Connectivity add-on) is merely a client like a standard File/FTP adapter. In order to test this adapter, we need a SFTP Server which is up and running. Usually system admins install/configure the SFTP server for us in a Linux/Unix server and used to provide the limited access.

If we want to install the SFTP adapter in our own PCs (like FileZilla FTP Server) for unlimited access , it will be very easy if we use Unix/Linux(It will be covered in upcoming post). But for windows, its a nightmare because there is no readily installer is available(?).

Fortunately, the OpenSSH for Windows is available, but still there are lot of post installation steps are required which would be complex for a novice user. I have faced lot of Windows service related issues to start the SFTP server due to anti-virus and firewall restrictions which requires hours of troubleshooting effort to fix the same for beginners. You can try the same by just following steps mentioned in http://www.worldgoneweb.com/2011/installing-openssh-on-windows-7/

Since PI NWA key storage doesn't support SSH keys for Private key based authentication, OpenSSL utility is required convert SSL keys to SSH keys and vice versa. OpenSSL can be installed separately and again searching for the windows binary and installing the same is a huge pain.

If we use Cygwin (never heard about this? here you go http://en.wikipedia.org/wiki/Cygwin), both SFTP Server, SFTP Client (for testing) and OpenSSL utility are available under one roof. The following steps will explain how to download and install Cygwin.

My PI instance is installed on a Windows 2003 Server and I am using the same machine for installing the 'localhost' SFTP server.

Go to http://cygwin.com/install.html and click on setup.exe

Click on "Run"

Trust the "Unknown Publisher" by clicking "Run" again

Click on "Next"

Choose "Install from Internet" and click "Next"

Leave the default directory (or) provide a directory path which doesn't have spaces

Choose a location to store all the downloaded setup files

Choose "Use Internet Explorer Proxy Settings"

Choose any Mirror and Click "Next"

It will download the setup files which has the meta data about all the available packages/tool/utilities

Click "OK" for the alert

Search for "ssh" then click on the highlighted icon to choose all the SSH/SFTP tools to install (Don't click on "Next" Immediately)

Then Search for "openssl" and choose the highlighted packages for install and Click on "Next"

Verify the list of packages and dependencies to be installed

Wait till all the selected packages to be installed(I will take a while and I am sure you can grab a coffee in the mean time)

We are done. Click "Finish" to complete the setup

The next post in this series covers the steps for auto configuring and starting the SSH service(where SFTP runs).