Cache issues when PI is connected to older SLD

If an SAP PI 7.1 or newer release system is connected to SLD 7.0, the cache update may fail with the following error;

com.sap.aii.ib.core.abapcache.CacheRefreshException: Unable to find the SLD element (SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, SID_NNN, string])

The error occurs as the wizard to create a new business system in the SLD 7.0 does not create enough information for proper functionality of the PI Integration Directory. An association to HTTP Service Port required by cache refresh for notifying AS ABAP about changes in the configuration is not created.

To fix this problem, create missing information in SLD by following these steps:

  1. Call the SLD URL in a browser: http://host:port/sld > Administration > Content Maintenance
  2. Select Subset: All With Instances; Class: HTTP Service Port
  3. Click on 'New HTTP Service Port'
  4. Fill following fields:
    • CreationClassName: SAP_HTTPServicePort
    • Name: <SID>_<CLIENT>
    • SystemCreationClassName: SAP_BCApplicationServer
    • SystemName: <SID>
    • Caption: Http Service Port for <SID>_<CLIENT>
    • URL: http://<host>:<port>
  5. Click 'Save'
  6. Select another Class to browse: Business System
  7. Click on the required Business System, i.e. on SID_NNN
  8. Click on "X Associated Instances"
  9. Click on 'New Association'
  10. Select Association Type: Business System HTTP Service Port
  11. Select just created http port (i.e. SID_NNN)
  12. Click 'Associate'
  13. Now go to Integration Directory and clear SLD Cache : Menu-> Environment-> Clear SLD Data Cache.
  14. Goto Menu->Environment->Cache Status Overview and repeat all failed cache refresh events for the required ABAP backend.

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