Online Tutorials & Training Materials | STechies.com
Register Login

Configuration Changes For SAP PI High Availability

|| 0

Configuration Changes For SAP PI High Availability
Stechies

PI 7.1 (and higher) High Availability (ASCS) setup needs configuration changes in load-balanced connection setup of HTTP, RFC, RMI connections.

Need to Install

  • Load Balancer for HTTP (e.g. SAP Web Dispatcher):
  • Setup of an SAP Web Dispatcher as an additional component in an SAP
  • Cluster Group (HA Cluster) is Recommended

Configuration

For local RFC connections (within same Instance) ABAP <=> Java, a wildcard addressing possibility is used:
hostname               localhost
gwservice               'sapgw$$'
instno                      '$$'

At runtime, $$ is substituted with the local Instance number.

Parameter Value Description
<virtual host> SAP Web Dispatcher Hostname
<httpport>  SAP Web Dispatcher HTTP Port
<httpsport>  SAP Web Dispatcher HTTPS Port
< SID> SAP System ID
SPACE  Default RFC Logon Group 'SPACE'
<empty> Leave blank
<ascs virt. host> ASCS Message Server Hostname check parameter rdisp/mshost in DEFAULT.PFL 
<scs virt. host>  SCS Message Server Hostname check parameter j2ee/scs/host in DEFAULT.PFL
<mshttpport> 

ASCS Message Server HTTP Port check instance parameter ms/server_port_<XX>

 in ASCS instance profile for the port number 

Default: 81<ASCS instance number>

<mshttpsport>

ASCS Message ServerHTTPS Port check instance parameter ms/server_port_<XX>

in ASCS instance profile for the port number

<SCSinstno>  SCS Instance Number
<is sld name>  Integration Server name in SLD Default: is.<cisysnr>.<cihost> 


Steps on ABAP Integration Server client

  • First login to Integration Server client and then navigate to t-code SM59.
  • Navigate to ABAP Connections -> SAPXIPP<client> and then check if Target Host and System Number has been set. If this scenario, please navigate to transaction SXMB_ADMIN --> 'Configure Principal Propagation' and execute 'Recreate'.
  •   Now for destination CentralMonitoringServer-XIAlerts user need to check if Load Balancing has been set. If not then delete this RFC destination. It will be recreated during next alert creation.
  • Now navigate to HTTP Connections to External Server and there change Target Host and Service No. to <virtual host> and <httpport> for the following destinations (if available):
    • SAP_PROXY_ESR
    • ADS
  • Navigate to HTTP Connections to ABAP System -> INTEGRATION_DIRECTORY_HMI and change Target Host and Service No. to <virtual host> and <httpport>.
  • Navigate to TCP/IP connections and then delete Gateway Options under Technical Settings for the following destinations:
    • AI_RUNTIME_JCOSERVER
    • AI_VALIDATION_JCOSERVER
    • LCRSAPRFC
    • SAPSLDAPI
  • Navigate to transaction SXMB_ADMIN --> 'Integration Engine Configuration' and change the following settings:

           Set "Corresponding Integ. Server" to <virtual host>:< httpport> or reload configuration from SLD.
           If a SM59 destination was maintained here, please change it accordingly.

  • Navigate to transaction SLDAPICUST and change the following settings:
    • Host Name                <virtual host>
    • Port                      <httpport>

 This change is only needed if a local SLD is used.

If an SM59 destination, e.g. SAP_CIM_SRV_SAP_DEFAULT, was maintained here, then user need to change it accordingly.

  • Navigate to transaction RZ70 and change 'RFC Connection to SLD' to:
    • Gateway Host:             <scs virt. host>
    • Gateway Service:          sapgw<SCSinstno>

 This change is only needed if a local SLD is used.

  • Navigate to transaction SMLG and create a Logon Group PUBLIC with all available instances.

Steps on NetWeaver Administrator

  • Logon to the NetWeaver Administrator with the J2EE admin user: http://<host>:<hport>/nwa
  • Navigate to 'Configuration Management -> Security -> Destinations'. For the destinations "UMEBackendConnection" and "I18NBackendConnection" (if available) activate 'Local System Connection' in tab strip 'Connection and Transport'. Save the change.

Please change the URL server:port to <virtual host>:< httpport> in tab strip 'Connection and Transport' for the following destinations (if available):

    • DASdefault
    • FP_ICF_DATA_<SID>
    • SLD_Client
      This change is required only if a local SLD is used.
    • SLD_DataSupplier
      This change is required only if a local SLD is used.
    • pmistore

Navigate to 'Configuration Management -> Infrastructure -> Jco RFC Provider'.

 The user needs to change gateway settings in tab strip 'Server Configuration' to:

    • Gateway Host:             localhost
    • Gateway Service:          sapgw$$

Change system settings in tab strip 'Repository Configuration' to:

    • Application Server Host:  localhost
    • System Number:            $$

Do this for the following destinations:

    • AI_RUNTIME_<SID>
    • AI_VALIDATION_<SID>
    • LCRSAPRFC_<SID>
    • SAPSLDAPI_<SID>

Start the destinations after you have saved them.

Afterwards Navigate to ABAP transaction SM59 -> TCP/IP connections, open the respective connections and press 'Connection Test'.        

Create additional destinations for serving connections from external business systems (needed in case ABAP XI Proxies are used in these business systems):

    • LCRSAPRFC_<SID>_SCS
      use settings from LCRSAPRFC_<SID>, but change
      Gateway Host to <scs virt. host>
      Gateway Service to sapgw<SCSinstno>
    • SAPSLDAPI_<SID>_SCS
      use settings from SAPSLDAPI_<SID>, but change
      Gateway Host to <scs virt. host>
      Gateway Service to sapgw<SCSinstno>

           Start the destinations after you have saved them.
           
Note: *_SCS destinations are required only if ABAP backends use RFC destinations LCRSAPRFC, SAPSLDAPI. If ABAP backends use HTTP destinations SAP_PROXY_ESR, SAP_CIM_SRV_SAP_DEFAULT, then user can skip creating these destinations.

  • Navigate to 'SOA Management -> Destination Template Management'. For the destination "ConfigPort_Document" (if available) change URL server:port to <virtual host>:<httpport>.
  • Navigate to 'Configuration Management -> Infrastructure -> Java System Properties'. For Usage_Type_All_in_One, Service "XPI Service: CPA Cache" set following properties:
    • SLD.selfregistration.hostName:  <virtual host>
    • SLD.selfregistration.httpPort:  <httpport>
    • SLD.selfregistration.httpsPort: <httpsport>

Steps on Exchange Profile

  • Call the PI start page http://<host>:<hport>/dir/start/index.jsp and navigate to 'Administration -> Exchange Profile'.
  • For secured access from Java to ABAP, a destination XI_EXCHANGE_PROFILE was introduced.

If destination XI_EXCHANGE_PROFILE exists (can be checked via NWA 'Configuration Management -> Security -> Destinations'), also check if 'Local System Connection' is activated (otherwise activate it).
This destination does NOT exist only if in case, the adapt connection settings in Exchange Profile UI directly.

Navigate to 'Connection' and set the ABAP Connection as follows:

Load Balancing:  Yes
Message Server:  <ascs virt. host>
System ID: <SID>
Logon Group: SPACE

1) Navigate to 'Parameters -> Connections' and change as follows:

com.sap.aii.connect.repository.name                   <virtual host>
com.sap.aii.connect.repository.httpport              <httpport>
com.sap.aii.connect.repository.httpsport              <httpsport>
com.sap.aii.connect.repository.mshost                 <ascs virt. host>
com.sap.aii.connect.repository.mshttpport            <mshttpport>
com.sap.aii.connect.repository.mshttpsport <mshttpsport>
com.sap.aii.connect.directory.name                    <virtual host>
com.sap.aii.connect.directory.httpport                <httpport>
com.sap.aii.connect.directory.httpsport              <httpsport>
com.sap.aii.connect.directory.mshost                  <ascs virt. host>
com.sap.aii.connect.directory.mshttpport              <mshttpport>
com.sap.aii.connect.directory.mshttpsport <mshttpsport>
com.sap.aii.connect.integrationserver.name            <virtual host>
com.sap.aii.connect.integrationserver.httpport        <httpport>
com.sap.aii.connect.integrationserver.httpsport       <httpsport>
com.sap.aii.connect.integrationserver.r3.httpport     <httpport>
com.sap.aii.connect.integrationserver.r3.httpsport    <httpsport>
com.sap.aii.connect.integrationserver.r3.mshost       <ascs virt. host>
com.sap.aii.connect.integrationserver.r3.r3name       <SID>
com.sap.aii.connect.integrationserver.r3.group        SPACE
com.sap.aii.connect.integrationserver.sld.name        <is sld name>
com.sap.aii.connect.rwb.name                          <virtual host>
com.sap.aii.connect.rwb.httpport                      <httpport>
com.sap.aii.connect.rwb.httpsport                    <httpsport>
com.sap.aii.connect.rwb.r3.mshost                    <ascs virt. host>
com.sap.aii.connect.rwb.r3.r3name                     <SID>
com.sap.aii.connect.rwb.r3.group                      SPACE
only if a local SLD is used:
com.sap.aii.connect.cr.name                          <virtual host>
com.sap.aii.connect.cr.httpport                      <httpport>
com.sap.aii.connect.cr.httpsport                      <httpsport>
com.sap.aii.connect.landscape.name                    <virtual host>
com.sap.aii.connect.landscape.httpport                <httpport>
com.sap.aii.connect.landscape.httpsport              <httpsport>

only if the local system is used as Central Monitoring Server:

com.sap.aii.rwb.server.centralmonitoring.httpport     <httpport>
com.sap.aii.rwb.server.centralmonitoring.httpsport    <httpsport>
com.sap.aii.rwb.server.centralmonitoring.name         <virtual host>
com.sap.aii.rwb.server.centralmonitoring.r3.mshost    <ascs virt. host>
com.sap.aii.rwb.server.centralmonitoring.r3.r3name    <SID>
com.sap.aii.rwb.server.centralmonitoring.r3.group     SPACE

Steps on SLD

Navigate to "Business Systems" and select the entry INTEGRATION_SERVER_<SID>.       
Navigate to tab strip "Integration" and change Pipeline URL server:port to <virtual host>:<httpport>.        
Save the Business System.

This change is required only if a local SLD is used.

Steps on ABAP Business System clients

Note: It is strongly recommended to create separate messaging exchange users with the corresponding role SAP_XI_APPL_SERV_USER on Integration Server representing individual business systems in a productive environment.

 Set "Corresponding Integ. Server" to <virtual host>:< httpport> or reload configuration from SLD.

If an SM59 destination was maintained here, please change it accordingly.

Change Program ID for LCRSAPRFC to LCRSAPRFC_<SID> _SCS, for SAPSLDAPI to SAPSLDAPI_<SID>_SCS. For each destination press 'Connection Test' to verify the connection.        

The change for SAPSLDAPI is required only if the SLD on the PI Integration Server is used.

Note: using RFC destinations LCRSAPRFC, SAPSLDAPI is not necessary for newer releases (SAP BASIS>=7.1). USer can instead use HTTP destinations SAP_PROXY_ESR, SAP_CIM_SRV_SAP_DEFAULT.

This change is only needed if the SLD on the PI Integration Server is used.

If an SM59 destination, e.g. SAP_CIM_SRV_SAP_DEFAULT, was maintained here, then please change it accordingly.

This change is only needed if the SLD on the PI Integration Server is used.

    • Load Balancing:           Yes
    • Message Server:           <ascs virt. host>
    • System ID:                <SID>
    • Logon Group:              SPACE
    • Navigate to 'Parameters -> RuntimeWorkbench' and change as follows:
    • Login to the SLD: http://<host>:<port>/sld
    • Navigate to 'Administration -> Settings'. In Section "datasupplier" change gateway settings:
      • Gateway Host:             <scs virt. host>
      • Gateway Service:          sapgw<SCSinstno>
    • Logon to Business System client.
    • Navigate to transaction SXMB_ADMIN --> 'Integration Engine Configuration' and change the following settings:
    • Navigate to transaction SM59 --> ABAP Connections and please check if a connection to PI Integration Server exists. In this case, enable Load Balancing and set:
      • Msg. Server to <ascs virt. host>
      • Group SPACE
    • Navigate to HTTP Connections to External Server and change Target Host and Service No. to <virtual host> and <httpport> for destination SAP_PROXY_ESR (if available).
    • Navigate to TCP/IP connections and change Gateway Options under Technical Settings for destinations LCRSAPRFC, SAPSLDAPI (if available):
      • Gateway Host:             <scs virt. host>
      • Gateway Service:          sapgw<SCSinstno>
    • Navigate to transaction SLDAPICUST and change the following settings:
      • Host Name                <virtual host>
      • Port                      <httpport>
    • Navigate to transaction RZ70 and change 'RFC Connection to SLD' to:
      • Gateway Host:             <scs virt. host>
      • Gateway Service:          sapgw<SCSinstno>