Post installation configuration SAP XI

I will now describe the configuration steps that are required for setting up the SAP NW with usage type PI (XI).

As i mentioned in the previous post, you can use the wizard-based configuration but i would recommend that at first you should do it manually. But alas, if you decide to use the wizard you must know to do this only on systems that haven't been configured before. If you have modified the system already or upgraded it from an older version, you should do these steps manually.

1. Configuration Wizard

If you want to use the wizard then open the SAP NW Administrator in a browser with the path http://host:httpport/nwa and log on as Administrator.
Then navigate to the Deploy and Change tab, select a task from the list and Start it. Enter the required data and just follow the screens, it's pretty straightforward.

2. Manual Configuration

• Ok. The first thing you should do is check if some essential sap.com services are started. To do this you must log on to the Visual Administrator tool, go to Cluster --> Server --> Service --> Deploy. In the right frame, select Application.Through the list of deployed services, check if the next services are started:

All services beginning with:
- sap.com/com.sap.aii*
-sap.com/com.sap.lcr*
-sap.com/com.sap.xi*
And service: sap.com/com.sap.rprof.remoteProfile

• Performing automatic customizing

In order to use the Business Process Engine you must perform automatic customizing on the Netweaver Web Application Server (ABAP).
So :
1. Log on with SAP_ALL rights (don't use users DDIC or SAP*).
2. Call transaction SWF_XI_CUSTOMIZING to execute the basic customization. This transaction sets all the required technical settings. The screen Automatic Workflow Customizing will appear.
3. Make sure that the Maintain Runtime Environment node has a green check (not a red cross).
If there is a red cross, do the following:
a. Select the Maintain Runtime Environment node and choose Perform Automatic Workflow Customizing.

The system will now execute the automatic customizing including all sub nodes.

4. Choose Maintain Definition Environment --> Maintain Prefix Numbers.
5. Choose Execute. The Prefix Numbers for Workflow and Organizational Management screen will appear.
6. Choose Display <-> Change to activate the edit mode.
7. In the Available Prefix Numbers for Workflow and Organizational Management box, choose Create.
8. In the dialog box, enter a Prefix number equal to or higher than 900 and choose the Save button.
9. Choose Maintain Definition Environment --> Check Entries from HR Control Tables.
10.Choose Execute. The Consistency Check of Workflow Installation screen appears. The control tables must be complete.

If you encounter any problems, i suggest you execute transaction SE38 and execute report RHTTCP77. Ignore the red cross errors regarding the transport objects PDST or PDWS.After that execute report RSWF_CATID select with the options ABAP Classes and XML Object types selected.

You should be ok now.

• The next step is to assign application roles to user groups. You do this in the J2EE Visual Administrator. Go to Cluster --> Server --> Services --> SLD Data Supplier. Then click on the Runtime tab which is located in the right frame, then choose Assign Application Roles To User Groups and confirm the dialog.

• Now we need to maintain a product for the tehnical system and a business system for the Integration Server.

Perform the following steps:
1. On the SLD start page of your SLD host, choose Technical Systems. The Technical Systems page appears.
2. Select Web AS ABAP as type of your technical system.
3. In the table displayed, choose the technical system () that you have created for the Integration Server with transaction RZ70. See the Installation Guide SAP NetWeaver 7.0 at SAP Service Marketplace at service.sap.com/installNW70.
A details screen appears, where you can maintain the technical system.
4. On the Installed Products tab page, choose Add new Product.
5. In the product list, select the product SAP NetWeaver 7.0.
6. Make sure that at least the component SAP BASIS 700 is selected in the software component version list.
7. Don't forget to Save.

• Maintaining a Business System for the Integration Server

Now we must define a business system with the role of an Integration Server in the SAP System Landscape Directory (SLD).

Perform the following steps:

1. On the SLD start page of your SLD host, choose Business Systems. The Business Systems page appears.
2. Choose New Business System…. The Business System Wizard appears.
3. Select system type Web AS ABAP and choose Next.
4. Select the technical system for your business system by selecting the system () and client of your Integration Server and choose Next.
5. Enter a name for your business system and choose Next. An installed products list appears.
6. If there are products displayed on the left that are not installed on the system, deselect them by deselecting the Installed indicator and choose Next.
7. Select Integration Server as the role of the business system and enter the following in the Pipeline URL field: http://:/sap/xi/engine?type=entry
In this Internet address, and are the ABAP host name and port number of the Integration Server. You can find by logging on to the Integration Server and running transaction SMICM (choose Goto --> Services and check the entry for HTTP).
8. Choose Finish.
9. Make sure that the host name of the Integration Server specified in the SLD matches the name specified in the exchange profile (in section Connections, property com.sap.aii.connect.integrationserver.name). If there is a mismatch, change the name specified in the exchange profile so that it matches the one specified in the SLD.

Remember that if you change the host name of the Integration Server after the installation in either the SLD or the exchange profile, you must adjust it accordingly in the exchange profile or the SLD, respectively.

Ok, we have made the first 5 configuration steps manually. We have another 7 steps to go through. The next ones involve creating RFC destinations in the ABAP and JAVA environments and i will go through all of them but in the next post.

...to be continued...

Installing SAP Exchange Infrastructure (PI)

After the short description of the SAP XI components it's time to start with how to install and configure the SAP usage type PI (former Exchange Infrastructure).

In the first place you should know that all installation-related guides can be found at http://service.sap.com/instguides. In the left panel you will find SAP NW 7.0 (2004s) version which we will use. There, under Installation you will find the Master Guide that you must read. There are a few steps that must be done before proceeding with the installation.

1. First you check the hardware and software requirements.
2. You need to check the Windows File System (NTFS is a must).
3. You need to check the size of the file cache.
4. You must install the Java Development Kit (JDK). I would recommend version 1.4.2. Also, the installation tool (SAPINST) requires the JRE to function. So, install JDK + JRE.
5. Install your chosen database (Oracle, MSSQL etc). Be sure to check the master guide before installing because for example Microsoft SQL Server 2005 is required to have a certain collation (Unicode collation SQL_Latin1_General_CP850_BIN2) to work with SAP. This collation is not installed by default so you must manually change it in the installation process.
6. Prepare the installation DVDs or download from SAP site.
7. Before you start the installation, make sure to download from the Sun site the Java Cryptographic Extension Policy Archive (JCE_policy) for the JDK version that you installed earlier.
7. When you install a new PI System you can either register the PI System in a local or in a remote System Landscape Directory.

So after the SAPINST has finished installing the SAP PI, you need to make a couple of post-installation steps.

Firstly, you need to map the Security Role to User:

• Log on to the Visual Administrator of the J2EE engine of the SLD host. You'll find the path to look like this: "X:\usr\sap\\DVEBMGS00\j2ee\admin\go.bat"
• Choose Cluster --> Server --> Services --> Security Provider.
• In the Runtime tab, you must choose Policy Configurations and then the column Components, and select the component.
• Switch to the Security Roles tab to display the assigned nodes.
• Select role LcrInstanceWriterLD. You should see the user SLDAPIUSER.
• Use the Edit mode and add user PIAPPLUSER with the same role LcrInstanceWriterLD.

Secondly:

• Log on to SAP XI System with user DDIC and call the transaction SLDAPICUST. You will see the Maintain SLD Access Data screen.
• Choose Display --> Change and:

1. Replace the existing SLDAPIUSER with PIAPPLUSER;
2. Make sure your entry is marked as Primary;
3. Save the settings;

Well, now we have performed the post installation steps and we must move on to the configuration steps. There are 2 options to do this: either using the template (which i advice against), and doing the steps manually, which i recommend.

So here we will maintain the configuration steps manually.


..to be continued..