Installing and Configuring SAP Web Dispatcher for SAP XI

Most installations begin with one application instance. If the instance number is NN, the http port will be 5NN000. With time, you may require more number of instances to scale with the growing requirements with increasing message volume. If you have installed an additional application instance MM, the instance listens to http requests on 5MM000 port. Most of your existing configuration would have been set to use 5NN000 http port.

In order to balance load between instances NN and MM, you require a web dispatcher (WD) and update your configuration to use the WD.


Before you install the WD, check SAP note 908097 to verify which release is supported for the release of the application installed.

Extract the CAR files in a new directory where you want to install the web dispatcher and call this command
sapwebdisp -bootstrap
You will be prompted to give inputs

  • Host name of the server where Message server instance runs (rdisp/mshost)
  • Message server's HTTP port (ms/http_port: 81<Instance Number of the Message Server>)
  • SAP Web Dispatcher instance number (SAPSYSTEM: Choose a desired instance number for WD)
  • Desired SAP Web Dispatcher HTTP port (icm/server_port_0: Choose a desired port number for WD)

If you are installing the WD for a dual-stack system, the message server HTTP port and host should point to the ABAP central services instance and not SCS. For example: If the central instance ABAP is 02 and SCS intance is 01, ms/http_port will be 8102.

The bootstrap will not configure SSL on WD. This has to be done separately.

We will now focus on the configuration changes required when you are using WDs to load blance on an XI system.

Call the exchange profile and update the following parameters to WD's host and port.
com.sap.aii.connect.directory.name
com.sap.aii.connect.directory.httpport
com.sap.aii.connect.directory.httpsport
com.sap.aii.connect.integrationserver.name
com.sap.aii.connect.integrationserver.httpport
com.sap.aii.connect.integrationserver.httpsport
com.sap.aii.connect.integrationserver.r3.httpport
com.sap.aii.connect.integrationserver.r3.httpsport
com.sap.aii.connect.repository.name
com.sap.aii.connect.repository.httpport
com.sap.aii.connect.repository.httpsport
com.sap.aii.connect.rwb.name
com.sap.aii.connect.rwb.httpport
com.sap.aii.connect.rwb.httpsport
com.sap.aii.rwb.server.centralmonitoring.name
com.sap.aii.rwb.server.centralmonitoring.httpport
com.sap.aii.rwb.server.centralmonitoring.httpsport

Update the Pipeline URL in the Business System's details in SLD to http://<Hostname of WD>:<WD HTTP port>/sap/xi/engine?type=entry. This will be the URL of the Integration Engine to which the Adapter Engine will send the messages. You can also change the URL using SXMB_ADM --> Integration Engine Configuration.

Go to Visual Administrator --> Global Configuration tab --> Server --> Services --> SAP XI AF CPA Cache and change the following parameters to point to the WD:

  • SLD.selfregistration.hostName
  • SLD.selfregistration.httpPort
  • SLD.selfregistration.httpsPort

This will be the URL of the Adpater Engine to which the Integration Engine will send the messages.

Call transaction SLDAPICUST and change the host and port to those of WD. Call Visual Admin and navigate to Data Supplier service. Change the HTTP connection details to use WD. These changes will ensure that the data sent to SLD is load balanced. If you are using SLD of another system (say ABC), do not change these values to use the WD you are installing now. Change it to use the WD of ABC or leave it unchanged.

Edit the HTTP destination INTEGRATION_DIRECTORY_HMI using transaction SM59 and change the connection details to use WD.

Delete Adapter Engine cache from SXI_CACHE transaction and restart the Java cluster to activate the changes.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more