How to install the new B2B add-on
I see a lot of people facing problems setting up the new B2B add-on for SAP PI or PO. In this blog, based on a SAP PO 7.31 SP07 system, I will explain all the steps necessary to do the set up. Please note that the software used in this blog was downloaded on September 9th 2013. The product evolves very fast and within a few weeks, higher patch levels could be available.
Make sure these 2 roles are added to the user executing the setup
Make sure the users PIAF<SAPSID>, PIDIR<SAPSID> and PIIS<SAPSID> are added to the Administrators group and they have role SAP_XI_ADMINISTRATOR_J2EE assigned.
STEP 1 – download the correct software
Go to the Download Center on the SAP Service Marketplace via URL http://service.sap.com/swdc
You can go for Installations and Upgrades, but please note you need to upgrade this software!
Within the Support Packages and Patches, go to A-Z Index -> P -> PI B2B ADDON and to PI SFTP PGP ADDON for all relevant components.
Make sure you download them all. Choose for every component if you are on SP0 or SP1.
STEP 2 – deploy the software
Use the JSPM to deploy all downloaded components.
STEP 3 – verify the deployment
Go to the start page of the java stack (http://<host>:<port>/startPage) -> System Information -> Components Info and take B2B for the Name. This is the result:
Please note SP1 is installed.
STEP 4 – add content to the Enterprise Services Repository
The downloaded B2B Toolkit ZIP file contains all the relevant information. Go to the ESR -> Tools -> Import Design Objects and import file XI7_11_B2B_TOOLKIT_1.0_01_02.tpz.
Do the same for the B2B Mapping Kit and import file XI7_11_B2B_MAPPING_KIT_1.0_01_00.tpz.
In case you want to use the SFTP adapter too, make sure to import the content as well into the ESR.
STEP 5 – configure the EDI content manager
Go to the B2B Integration Cockpit (http://<port>:<host>/b2bic) -> EDI Content Manager. In my case, I want to configure different EDI scenarios, so I go for Edifact in the menu. You can also go for another message format. The steps are similar.
STEP 5.1 – import content
The downloaded B2B content part (file PIB2BCONTENT01_5-20009370.ZIP) contains the Runtime Content you need. Make sure all the relevant files with the .b2b extension are imported. With relevant I mean the ones for your message format. In my case, I need to import files B2B_EDI_TABLES-93A_99B-v1.0.b2b and B2B_EDI_TABLES-00A_10B-v1.0.b2b.
You can verify the table’s content using the Tables menu item
STEP 5.2 – control keys
Make sure the Control Key Scenario Association part and the Control Key Description Editor part are filled in properly. If not, you will face errors mentioning no conversion rules available or unkown message type. Basically, the system needs this to identify the incoming message and map it to XML or vice versa (TIP: use this configuration in conjunction with adapter module localejbs/EdifactConverterModule)
STEP 5.3 – generate XSD
Generate an XSD and use this one as an external definition in your ESR
STEP 6 – Integration Directory
Verify if the new adapters are available to use.
As of this point, you can start creating your own scenarios.