PI 7.31 - Adapter Engine Cache Missing

[jorge_velasquez]

Hi Experts,

In tx SXI_CACHE --> Menu--> Goto --> Adapter Engine Cache

Link is missing after system copy, SLDCHECK works fine and also in SLD Registration all nodes are green

On the other hand in http://hostname:50200/CPACache/refresh?mode=full    --> Delta Cache I got the following error  "Couldn't parse Configuration Data cache update XML string from Directory"

[Former Member · Accepted solution]

Hello Jorge.

Nabendu is right. We were facing the same problem with exactly the same error message.

In the chache History you can see when the problem came up the first time. Check which Softwarecomponents have been imported or changed from that time on. I our case it was one of the SAP-Standard components that we have imported in the ESR. After deleting this Softwarecomponent the Cache was working fine again.

Now we are searching for the exact problem but the most important thing is that the CPA-Cache is working now.

Regards,

Thomas

[nabendu_sen]

Hi Jorge,

For SXI_CACHE --> Menu--> Goto --> Adapter Engine Cache missing, please keep in mind that this entry is only filled when one message is triggered to the AE. Not before that.

Refer Note : 817920

For Full Cache Refresh issue:

Please check SAP Note 764176. It should resolve this issue. If not check the below configuration and SAP NOTE 999962

NWA-Configuration management-Infrastructure-java system properties:

choose XPI service:CPA Cache there we can see the following property SLD access =False.

Setting it to True and restarting the CPA Cache.

Also check:  http://wiki.sdn.sap.com/wiki/display/XI/SXI_CACHE+Common+Errors

[jorge_velasquez]

Hi Nabendu,

Still have the issue.

In Tx SXI_CACHE i found this error:

All users are unlocked and SLDCHECK is working fine.

However this error is also appearing:

com.sap.aii.ib.core.abapcache.CacheRefreshException: Unexpected error on server for system REPOSITORY with application REPOSITORY. Detailed information: Tag empty is not permitted as a root element. definitions is expected. Server stack trace:

com.sap.aii.utilxi.wsdl.api.WsdlParseException: Tag empty is not permitted as a root element. definitions is expected

On the other hand I have a doubt concerning to CPA Cache Service and XPI Adapter Service. I found that some default parameters takes localhost and port 50000 .. our PI is 02..Do I have to change this or not?

Regards.

[nabendu_sen]

Hi Jorge,

If SLD access =True, you dont need to change directoryURL.

Please find the below doc:

directoryURL directoryUser directoryPwd

Value type: String In the case of a central or non-central Adapter Framework, the HTTP connection information for connecting to the Integration Directory is usually read from the SLD. If the SLDAccess property is manually set to false, the connection information for the Integration Directory can be explicitly maintained. These properties are provided for SAP internal testing purposes only and can be modified online. They must not be changed in a productive environment.

http://help.sap.com/saphelp_nw73/helpdata/en/48/CBB57BCEA80783E10000000A42189D/frameset.htm

xiadapter.isconfig.url should also not be changed.

Name  Description

xiadapter.isconfig.url

xiadapter.isconfig.username

xiadapter.isconfig.password

xiadapter.isconfig.sapClient

xiadapter.isconfig.sapLanguage

Default:

http://localhost:50080/sap/xi/engine?type=entry

Default: XIAFUSER

Default: 

Default: 100

Default: de

The XI adapter as part of the J2EE Adapter

Engine gets the required connection information

for sending XI messages to the Integration Server

(IS) from the Landscape System Directory (SLD)

and the Exchange Profile (EP).

If the SLDAccess property of the J2EE Service

SAP XI AF CPACache is set to false, the

connection information of the Integration Server

can be explicitly set with the properties listed

above.

In the PCK environment (SAP XI CPA Cache

Service property cacheType is set to PCK), the

property values are ignored at runtime. The

connection information to communicate with the

Integration Server has to be provided by the

channel definition and the collaboration

agreement configuration in the Integration

Directory.

These properties must not be changed.

Reference: Page 92 of the below document

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/ac6de690-0201-0010-54ac-8923089dc...

[jorge_velasquez]

Hi Nabendu,

Thank you for your support.

Do you have any idea about the error:

com.sap.aii.ib.core.abapcache.CacheRefreshException: Unexpected error on server for system REPOSITORY with application REPOSITORY. Detailed information: Tag empty is not permitted as a root element. definitions is expected. Server stack trace:

com.sap.aii.utilxi.wsdl.api.WsdlParseException: Tag empty is not permitted as a root element. definitions is expected

Regards

[sunil_singh13]

Jorge,

Error "Unexpected error on server for system REPOSITORY with application REPOSITORY" is consequence of Cache issue you are facing.

Get rid of Cache issue and above error will go by itself. Can you check RFC destination

"INTEGRATION_DIRECTORY_HMI" through Transaction SM59 and see if it properly maintained?

Also go to RWB -> Cache Connectivity Test and check if you are able to collect addition trace from their.

Thanks,

Sunil Singh

[nabendu_sen]

Hi Jorge,

This error is coming due to some issue at ESR. Check whether you have any inactive objects is there (for All users). If yes, then try to activate that, if its throwing any problem, then either resolve the issue / reject the change.

"Tag empty is not permitted as a root element. definitions is expected" - may be with any External Definition of type XSD/WSDL issue.

Also ensure ID objects and then perform Cache Refresh.

Check the below blog:

http://scn.sap.com/thread/3164367

Let us know your findings after that.

[jorge_velasquez]

Hi Sunil,

"INTEGRATION_DIRECTORY_HMI" RFC works fine!

It has hostname with FQDN and port 50200

However , What is RWB? Is not a Transaction Code.

Regards.

[nabendu_sen]

Hi Jorge,

Sunil meant 'RWB' means Runtime Workbench. If you go to <http://<server>:<port>/dir/start/index.jsp>, you can find it at the Right hand below.

Runtime Workbench -> Component Monitoring -> Choose 'Display' -> Cache Connectivity Test

Please find the below document for more information:

http://help.sap.com/saphelp_nwpi711/helpdata/en/13/a051421705be30e10000000a155106/content.htm