Process Integration Post Installation Process

Step 1

– Logon to ABAP system

Logon to ABAP sap system with sap* / DDIC for client 001 and 000.

Step 2

– Logon to J2ee system

Logon to j2ee system with j2ee_admin or any admin id.

URL for home page - hostname. <domain>.<ext>: port

Step 3

– Install the SAP License.

Register your new SAP system on SAP marketplace and request for the license.

Step 4

– STMS in ABAP system

Use below mentioned steps for transport organizer

Call t-code SE06.

Select standard installation.

Choose perform post-installation action.

Call STMS for configuring the domain controller in TMS if you select standalone system.

Step 5

– Perform Basis operation in ABAP system

Call t-code RZ10 and select the Instance profile.

Click on new to add below mentioned parameters in Instance profile.

Icm/host_name_full –

hostname. <domain>.<ext>

Login/system_client – 100

Icm/server_port_0 - PROT=HTTP, PORT=80$$, TIMEOUT=30, PROCTIMEOUT=600

Step 6

– Perform the Client copy

Perform the Client copy from 001 to 100 clients.

Create the new user which is copy of sap* on client 001.

Call t-code SCCL for local client copy with SAP_ALL profile.

Refer link for client copy for the process - https://www.sdn.sap.com/irj/sdn/thread?threadID=815814&messageID=5204061#5204061 

Step 7

– Change the client for J2ee side

The integration server is by default installed and configured in client 001.

I have used the new client as 100 instead of SAP default client 001.

Enter the URL as http://

hostname.<domain>.<ext>:port/nwa

Click on configuration Management

   Infrastructure    destination.

Change the client from 001 to 100 for RFC destination as 18NBackendConnection and UMEBackendConnection.

Step 8

– Run the configuration wizard for J2ee stack.

Run the wizard from http://

hostname.<domain>.<ext>:port/nwa and click on Configuration management    Scenarios   Configuration Wizard and select the Net weaver initial setup task from all configuration tasks.

Please refer to the screenshot below:

If above steps fail during the importing of XI object, then download the XI objects SAP_BASIS (XI7_1_SAP_BASIS.tpz) from SAP Marketplace and manually upload in ESR.

Step 9

- Adapter engine configuration task

Run the wizard from http://

hostname.<domain>.<ext>:port/nwa and click on Configuration management    Scenarios   Configuration Wizard and select Initial setup of functional unit PI adapter engine (AE) from all configuration task.

Step 10

– Check the configuration of SLD on ABAP

Call t-code SM59 and Check RFCs for LCRSAPRFC, SAPSLDAPI, and SAP_UC under TCP/IP connection. Check the gateway host and gateway services and click on connection test.

Call t-code SLDAPICUST and check the host name and gateway entry and PISUPER password and click on connection test.

Call t-code RZ70 and check host name and gateway host and click on execute.

Call t-code SLDCHECk and it will open the new page for SLD (http://hostname.<domain>.<ext>:port/sld) and on ABAP side it will shows whether SLD connection OK or not.

Also check the SLD connection settings in http://

hostname.<domain>.<ext>:port/sld

Step 11

– Check connection for INTEGRATION_DIRECTORY_HMI

Call t-code SM59 and check INTEGRATION_DIRECTORY_HMI in H type connection.

Enter the Hostname, service port and path prefix as /dir/hmi_cache_refresh_service/ext and click on connection test to test the connection.

Step 12

– Check entries for Integration engine configuration in SXMB_ADM.

For client 100 – entry should be Integration server

For client 001 – Not yet configured

Click on Manage queue and Register and activate the queue.

Step 13

– Check or create the Jco connection.

Enter the URL as http://

hostname.<domain>.<ext>:port/

Click on Web Dynpro

   Content administrator    Maintain Jco destination and check the Jco destination details such as client, host name, message server and system name for below mentioned Jco connection. For testing, click on Test.

WD_ALV_METADATA_DEST

WD_ALV_MODELDATA_DEST

WD_MODELDATA_DEST

WD_RFC_METADATA_DEST

Please refer to the screenshot below:

Step 14 -

JCo RFC Provider

Enter the URL as http://

hostname.<domain>.<ext>:port/nwa and Click on configuration Management    Infrastructure -> JCo RFC Provider'. Change the client in tab strip 'repository Configuration' to the new client and save.

Do this for the following destinations:

AI_RUNTIME_<SID>

SAPSLDAPI_<SID>

AI_VALIDATION_<SID>

LCRSAPRFC_<SID>

Enter the Host name, instance no. and client for all above destination.

Please refer to the screenshot below:

Step 15

– Check the Exchange Profile parameters

http://

hostname.<domain>.<ext>:port/exchangeProfile

Check the client and hostname entries for Integration sever, Runtime Work Bench and Integration builder.

Testing the PI 7.1 System

After the successfully installation, post-installation and configuration, test the below mentioned URLs:

URL for NWA: http://hostname.<domain>.<ext>:port/nwa

URL for SLD: http://hostname.<domain>.<ext>:port/sld

URL for RWB: http://hostname.<domain>.<ext>:port/rwb

URL for REP: http://hostname.<domain>.<ext>:port/rep

Issues During Post Installation

I have faced some major issues during the post installation task and I have described them in this document.

Issue 1

Installation task of PI 7.1 is simple as compare to previous version but I have faced the major issue of deadlock.

Deadlock situation occurred while restarting the central services instance hence j2ee stack not come up.

Remove all krnlreg entries from profiles for Deadlock situation – Refer to SAP Note - 966416

1. Log on as user <sapsid>adm.

2. Go to /usr/sap/<SAPSID>/SYS/profile.

3. Edit the instance profiles for all SAP system instances <SAPSID>_ <INSTANCE_NAME>_<host_name>, for example KB1_DVEBMGS01_pwdf2308

4. Remove all 'krnlreg' entries from all instance profiles.

Issue 2

There is some known issue in PI 7.1 for Central SLD hence I have used the local SLD at the time of template installation configuration of j2ee side.

The basic idea behind using the Local SLD instead of Central SLD is due to issue of SLD –

"Incomplete Registration of PI components in SLD". I have also referred to SAP Note - 1117249. But the issue of SLD, RWB, cache update etc.