regarding stopping channel temporarily

[Former Member]

Hi All,

I have RFC to JDBC one way communication. I need to stop channel from sending data to JDBC for some time. I stopped JDBC receiver channel from JAVA stack Communication channel Monitor (can't stop RFC sender as it is used in other scenarios also) but when i started again, it is sending data which couldn't go while channel was stopped.

Any idea how to avoid this missing data.These records were not intended to pass to JDBC.

Thanks in advance.

[former_member186851]

Hello Mohd,

As Inaki suggested best approach is to have specific RFC sender channel for this scenario.

[iaki_vila]

Hi Mohd,

It is not a good idea to share the same channel between scenarios with different business meaning, and your problem is a classical example to understand because is not a good idea. The best way to stop a channel is to use the ATP: Planning Availability Times - Process Integration Monitoring - SAP Library, but this doesn't solve your current issue. However, if you channel must be stopped, why do you go to lose any data?, if the channel must be stopped, no data would need to be passed.

IMO, you should have a specific RFC sender channel.

Regards.

[aby_jose]

Hi Mohd, There are web services available for "Cancel/Resend" Message or start/stop channels. If you want to perform it automatically, can consume the exposed web services (required ones) and can create a small application (web service client) and also can schedule it as per your requirement (if needed). Please refer the below blog for Cancel/Resend of messages. http://scn.sap.com/community/pi-and-soa-middleware/blog/2015/01/22/reading-messages-from-pi-system Thanks & Regards, Aby

[former_member186851]

Hello Mohd,

Cancel the messages before the starting the channel.

[nitindeshpande]

Hi Mohd,

You can avoid this by cancelling the messages which were generated during the channel was stopped.

Once your JDBC channel is stopped, the messages sent will fail in Adapter Engine and then you can cancel these messages and re-start the JDBC communication channel and these messages will not be processed to your JDBC 3rd Party.

And if you dont want to cancel the messages as they are huge in number, then you can change the Number of Retries parameter to 1 with Retry interval as 5 minutes, hence the messages will fail permanently and go in system error, which can be resent only if it is manually restarted.

To Change the number of retries please navigate through the below mentioned path -

NWA -> Configuration -> Infrastructure -> Java System Properties -> Services -> "XPI Adapter: XI"

Set the below mentioned parameter to minimum values -

"xiadapter.inbound.numberRetries.default" and "xiadapter.inbound.retryInterval.default"

Please find the screenshot for the value to be set -

Regards,

Nitin Deshpande