- SAP Managed Tags:
Automatic cache refresh in SAP PI ensures that the runtime environment has the latest configuration without manual intervention. This blog outlines essential checks and steps to ensure that automatic cache refreshes occur smoothly, maintaining the latest configuration.
The first and foremost thing is to ensure that the PI system is deployed with the latest patch levels for the following components:
- MESSAGING
- SAP_XIADMIN
- SAP_XIAF
- SAP_XIESR
- SAP_XIGUILIB
- SAP_XITOOL
Once we have the latest patch for the above components in place, we can further conduct the below checks to ensure the automatic cache refresh is getting triggered successfully.
Below are the common categories of IBC issues along with the steps to troubleshoot each:
1) PI Runtime Cache is not getting updated automatically in Integration Directory after a system upgrade/migration
As this is a case of System Migration, this means that the host configuration and respectively the SLD registration of the system have changed. Please follow the steps below in this case:
- Re-register the system in SLD with the CTC wizard and restart the system.
To re-register PI/PO system components in SLD (depending on your system type) use the dedicated configuration wizard in NWA:
- Java Only system: SAP Note 2034226 - Configuration Wizard: PI AEX SLD Self Registration - SAP for Me
- Dual or Split stack system: SAP Note 1292803 - Configuration Wizard: PI SLD Self Registration - SAP for Me
- If the issue still exists, clear the SLD runtime cache of the repository and directory before trying to perform a new cache test.
- Run a Cache connectivity test to confirm that all the status is correct.
- Check the SLD registration page and confirm that no errors are shown.
- "SLD.selfregistration.hostName"
- "SLD.selfregistration.httpPort"
- "SLD.selfregistration.httpsPort"
- Check if the "XPI Service: CPA Cache" in NWA -> Configuration -> Infrastructure -> Java System Properties -> Services also has correctly set properties.
- Pay special attention to "selfregistration" properties to ensure correct details:
2) Cache Status Overview in Integration Builder or Repository is grayed out or red.
When we perform a change in the Integration builder or Repository objects, the change doesn't get reflected in run time, and upon checking the cache status overview, it is found that the status is red (error) or gray (waiting). It should be green.
In this case, we need to conduct the following checks:
- Check for Pending Changes: Verify all necessary objects are activated.
- Clear Cache: Manually clear the cache.
- Perform a dummy change again and check if the cache status overview is working correctly after a manual cache refresh.
- Further check for user roles/permissions in NWA under Java aii properties:
- Search for user.name and check the users configured, and ensure that the configured user(s) is also present in the Identity management page.
- Make sure that the user is not locked or unavailable.
- If locked, then the password needs to be checked in Java aii properties and should be maintained correctly.
- After the user is verified, search for the property: com.sap.aii.hmi.client.config and make sure the value assigned to it is correct.
- Next, search for the host and see if the fully qualified domain name is maintained or not.
- Check for the property: com.sap.aii.connect.secure_connections.
- If https connection is used, then "all" should be maintained in the custom calculated value.
- Else for http connection, it should be maintained as blank("").
5.Check if the following user authorizations are there or not under Identity Management in NWA Key Roles:
- SAP_XI_ADMINISTRATOR_J2EE: Administration, monitoring, and cache management.
- SAP_XI_CONFIGURATOR_J2EE: Configuration of integration scenarios.
- SAP_XI_MONITOR_J2EE: Monitoring integration processes and cache status.
- SAP_XI_CONTENT_ORGANIZER_J2EE: Managing content within ESR and Integration Directory.
- If the above authorizations are missing, assign the roles and save changes.
6.If the issue still persists,then consider Restart of cache services in NWA. But as this would mean a change in system state,it is suggested to consider this as the last step and best to involve the development team for further analysis.
After performing the above troubleshooting steps, the cache status overview should start working correctly. If not, then further steps can be considered, as this might be related to JMS topic.
- Collect XPI trace for example, 100, by selecting the packages
- com.sap.jms,
- com.sap.aii.ib.server
- com.sap.aii.ibdir.server and analyze the traces.
- The above trace has to be collected by triggering a dummy change in the Integration builder or repository, depending on where the issue is happening, and performing cache connectivity test after activating the changed object.
- Collect the default trace by noting the timestamp at which the issue is encountered and analyze.
The above steps can be followed for most of the cache-related issues/errors. By following the steps outlined in this blog, you can efficiently identify and resolve common problems, ensuring the smooth and reliable operation of your integration processes.
For complex issues or ongoing challenges, don't hesitate to seek further assistance from SAP support. Thank you for using this troubleshooting guide, and we hope it serves as a valuable resource in your efforts to maintain a robust SAP PI IBC environment. Please feel free to ask any questions or provide any additional points in the comments section.
For more of such content follow the SAP Process Orchestration environment Topic page https://community.sap.com/topics/process-orchestration.Please feel free to ask and answer questions on https://answers.sap.com/tags/477916618626075516391832082074785
and read other posts on the topic https://blogs.sap.com/tags/477916618626075516391832082074785/
If you find the content insightful, will appreciate a follow to my profile for similar content.
