Steps for running SAP Netweaver PI on high availability (HA)

Steps for running SAP Netweaver PI on high availability (HA)

1. SAP Webdispatcher Installation
2. A load balanced set-up  of HTTP, RFC and RMI connections

• Configure HTTP and RFC connections on the Integration server to use loading balancing feature

Local RFC Connections

For local RFC connections between AS ABAP and AS Java (that is, for RFC connections within the same instance), the variable $$ is used for local addressing.

Specify the following parameters:

hostname : localhost

gwservice : 'sapgw$$'

instno : '$$'

At runtime, rfcengine substitutes '$$' with the local instance number.

AS ABAP

1. Call transaction SM59.
2. Choose the HTTP destination INTEGRATION_DIRECTORY_HMI.
3. Set the HTTP connect data to <virtual host>:<httpport> .

4.      Choose the RFC destination AI_RUNTIME_JCOSERVER.

5.      Delete the gateway settings.

     6. Repeat step 5 for the following RFC destinations:

1. LCRSAPRFC

     b. SAPSLDAPI

AS Java

1. Start the SAP NetWeaver Administrator.
2. Choose  Configuration Management -> Infrastructure Management -> Jco RFC Provider
3. Select the RFC destination AI_RUNTIME_JCOSERVER.
4. Change the gateway connection data to localhost , sapgw$$ .
5. Change the repository connection data to localhost , $$ .

     6. Repeat steps 4 and 5 for the following RFC destinations:

     a. LCRSAPRFC

     b. SAPSLDAPI

     7. Choose  Configuration Management -> Security -> Destinations .

     8. Select the HTTP destination pmistore .

     9. Set the HTTP connect data to <virtual host>:<httpport> .

    3. Configuration Changes to the following components :

1. Local System Landscape Directory
2. Exchange profile
3. User management engine
4. Integration Server
5. Central Adapter Engine
6. Dialog instance

1. Local System Landscape Directory

• Configuring the Local System Landscape Directory

If you want to run PI in a high availability (HA) environment with a local System Landscape Directory (SLD), you have to change the local SLD configuration

Procedure

1. Call ABAP transaction SLDAPICUST and set the HTTP connect data to <virtual host>:<httpport> .

          2. Go to Java SLD Administration, i.e login to NWA -> Configuration -> Infrastructure -> SLD Data Supplier Configuration, change the gateway                settings to < ms virtual host> and sapgw<SCSinstno> .  —– If this path don’t exists, then go to below path

Goto to SLD Administration page -> Settings -> Section : Data supplier. Change gateway host and gateway service .

Gateway host : msvirtual host

Gateway service : sapgw<SCSinstno>

          3. Call ABAP transaction RZ70 and change the gateway settings to < ms virtual host> and sapgw<SCSinstno> .

     4. Start the SAP NetWeaver Administrator and choose Configuration -> Security  -> Destinations .

     5.  Select the destination SLD_DataSupplier .

              6. Set the HTTP connection data to <virtual host>:<httpport> .

          7. Repeat step 6 for the destination SLD_Client .

b) Configuring the Exchange Profile

1. Call the exchange profile at: http://<pisystemhost:httpport>/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp.

Login with user “pisuper”, Goto Parameters -> Connections

Check the following parameters:

2)    If you are using a local SLD, also change the following parameters:

          3. Change the database connection of the exchange profile as follows:

1. Choose Connection .
2. Select Load Balancing .
3. Set the following values:

Message Server: < ms virtual host>

SID: <SID>

Logon Group: SPACE

c)  User Management Engine

1. Configuring the Connection to the User Management Engine

To enable local RFC connections between the user management engine (AS Java) and AS ABAP, the variable $$ is used for addressing. Perform the following steps:

1. Start the SAP NetWeaver Administrator.
2. Choose, Configuration Management -> Security Management -> Destinations.
3. Select the destination UMEBackendConnection.
4. Specify the following values:

Target host: localhost

System number: $$

d) Integration Server 

Maintaining the Pipeline URL of the Integration Server

To enable load balancing for SAP applications that retrieve the URL of the Integration Server from the System Landscape Directory (SLD), for example, Adapter Engines, the pipeline URL registered in SLD needs to be adapted.

To change this, go to Business Systems in SLD and select the Integration Server’s business system. Enter the virtual hostname and the port of the SAP Web Dispatcher in the field Pipeline URL.

Pipeline URL

http://virtualhostname:port/sap/xi/eng

Configuration URL :

http://virtualhostname:port/sap/xi/eng

More information: Maintaining a Business System for the Integration Server.

e) Central Adapter Engine 

Maintaining the HTTP Service Port of the Adapter Engine

To enable load balancing between the Integration Server and the central Adapter Engine, the hostname property used for the SLD registration of an AS Java node needs to be adapted. Perform the following steps:

1.   Start the SAP NetWeaver Administrator.
2.   Choose -> Configuration Management -> Infrastructure Management -> Java System    Properties -> Details -> Services
3. Select the service XPI Service: CPA Cache.
4. Enter the virtual hostname and the ports of the SAP Web Dispatcher for the properties:
5. SLD.selfregistration.hostName 

Virtualhostname i.e webdispatcher hostname

1. SLD.selfregistration.httpPort

Webdispatcher http port

1. SLD.selfregistration.httpsPort

Not changed since HTTPS port is not available for webdispatcher

• v.  Restart the XPI service.

f)  Configuring the Dialog Instance

To ensure that update and spool processing is always possible, you should configure at least one separate UPD work process and one separate SPO work process.

1. Check the dialog instance profile.
2. If required, configure a UPD work process and an SPO work process.