How do IR ID RWB Adapter Engine and Integration Engine register their URLs?

In XI/PI, the URLs used by various components are registered by the individual components in the SLD. These URLs are then used by other components for intra-XI/PI communications. The configurations are stored as follows:

For Integration Repository/Integration Directory/Runtime Workbench the details are configured on Exchange Profile. Following are the most important parameters that define the component URLs:

  • 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

For Integration Engine, the details are configured in the Business System maintained in the SLD. Edit the Pipeline URL maintained in the Business System if there is a hostname or network change. Check the Pipeline URL maintained in SXMB_ADM --> Integration Engine Configuration. If it is blank, leave it blank. If it incorrect, update it.

For Adapter Engine, the details are configured in "SAP XI AF CPA Cache" or "XPI Service: CPA Cache" service depending on PI release. To check/update it call Visual Administrator or NWA and verify the following properties:

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

If these values are changed:

  1. Restart the applicatons: "com.sap.aii.af.cpa.app" and "com.sap aii.af.app". Restarting these applications or J2EE engine will re-register the AE URL in SLD. To can check the URL registered in SLD, navigate to "CIM Instances" > "XI Adapter Framework". As part of the "associated instances" you can find e.g. at "XI Adapter Service XIRA -> Associated Instances -> Port for XIRA of af.<SID>.<hostname>"
  2. Call SXI_CACHE transaction and choose Goto -> Adapter-Engine-Cache. You will see the cached URLs for Adapter Engine maintained there. You have to delete those entries by selecting the row and clicking on delete icon. The URLs will re-cached when Integration Engine sends are message to Adapter Engine.

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