IR ID cache refresh in the Background Job

[Former Member]

Hello,

I just wanted to check, whether is it possible to run the job for periodic IR ID cache refresh in a single stack environment?

For cite, suppose we have a planed maintenance activity from Basis side (on the back-end system e.g. ECC) and we want to perform cache refresh after this (automatically in the background task, at a particular time may be).

Basically we want to have refresh the communication channels after this activity.

Please suggest and let me know if this can be achieved in SAP PI. Thanks!

Regards,

Akshay

[former_member182412]

Hi Akshay,

You need to identify the root cause for the problem which you are facing with cache refresh and fix it rather than doing automatic cache refresh because it is not preferable solution, in fact there is no job for this.

Can you explain what is the problem which you are facing with cache refresh??

Regards,

Praveen.

[Former Member]

Hi Praveen,

We do not have any problem with cache refresh.

Actually, whenever Basis team performs maintenance activity on ECC, communication channels gets failed to connect to the system. Even after ECC systems are available the communication channels not able to connect.

We then have to perform cache refresh activity after which communication channels are able to connect back to the system.

[former_member182412]

Hi Akshay,

Which type of channels?? RFC channels??

Regards,

Praveen.

[Former Member]

Yes RFC channels.

[former_member182412]

Hi Akshay,

Check question 25 in below SAP Note.

730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2/ 7.3 RFC Adapter

Q 25: An RFC sender channel is registered at an SAP Gateway which is shutdown. Does the RFC sender channel automatically reconnect to the SAP Gateway after it is available again?
              A: The SAP Gateway is shutdown due to e.g. offline backup of the R/3 database while a RFC-Adapter sender channel is registering at this SAP Gateway. After restarting the SAP Gateway, the RFC sender channel does not seem to automatically perform a reconnect.
              Actually the RFC sender channel will try to reconnect to the SAP Gateway. If this reconnect fails, the next reconnect attempt is made after a waiting period of 1 second. If the next reconnect fails also, the waiting period is doubled and so on. This will lead to a reconnect timing of 1, 2, 4, 8, ..., 3600 seconds. Saving recources is the aim of this technique.
              Once the maximum time is reached, the RFC channel does not stop connecting. It continues to try connecting indefinitely. The waiting period is a constant interval of the maximum time that is set, i.e. after every 3600seconds.
              If not configured, the maximum waiting time is defined in the middleware layer of SAP JCO, which is 3600 seconds. But this maximum time can be configured for each RFC sender channel in the XI Integration Directory. Open the Advanced Mode for the RFC Server Parameter.

Before XI 3.0 SP 12: Add a line to the table and use 'jco.server.max_startup_delay' as name and the maximum number of seconds to wait between reconnect attempts as value.


Since XI 3.0 SP 12: Enter the maximum number of seconds to wait between reconnect attempts in the field Maximum Reconnect Delay.

              For some PI releases it is also possible to configure the maximum waiting time globally for all RFC channels via the RfcServer.maximumReconnectDelay property of the J2EE service SAP XI Adapter: RFC/XPI Adapter: RFC. For more information about this option and the releases in which it is available refer to note 1510793.

Regards,

Praveen.

[Former Member]

Hi Praveen,

Thanks for your quick reply.

We are facing issue at the Receiver RFC channels.

/Akshay

[former_member182412]

Hi Akshay,

Check below blog for RFC receiver adapter reconnect issue.

XI : RFCAdapter ReConnect Issue | SCN

In case of RFC Adapter, XI by default checks for connectivity with the end system only when the channel is updated. This behavior of RFC Adapter is controlled by the service property initialRfcClientConnectCheck which is by default set to true. By setting this property to false we can force RFC Adapter to check the connection for every message being sent to the end system

Also check question 20 in the below SAP Note.

730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2/ 7.3 RFC Adapter

Regards,

Praveen.