Webservice down and everyone messages whith error

[Former Member]

I have a big problem, we have an integration that is CRM -> XI <-> WS.

For server problems, legacies down the services (WS) at night, but a user can perform some process conectarce and in that time.

The problem is that all messages fall and these messages can not relanzarce, there is some solution to handle the calls are in stop until the legacy services are on top.

[Former Member]

Hi Ximen,

First of all it should not happen in production like this. Anyways we never know.

If I understand your question correctly you dont want to send the message when the webservice is down. We may unable to do because if you dont know the time when the webservice will be down we may not do it. So instead check with the webservice/legacy team when this will be down. Then if you are using idocs from CRM then dont send the idocs at that time so that it wont come into pi itself. Run the program for idocs whenever the system is ready, but here you should know the definite timings for the webservice.

Regards,

---Satish

[Former Member]

Hi Satish

First, thanks for answering.

Indeed you understood my question, but in CRM asynchronous RFC were created so I can not handle if the service is up or not because you're sending IP and does not expect an answer.

The project is integrated to receive from SAP CRM movements: high, low and client modification, which must be reported to 2 legacy systems. BPM was used for this, which receives data asynchronously from CRM through a channel Sender RFC (RFC makes sending only 1 client or case-by called PI). After making the appropriate mappings BPM performs the call to 3 synchronous web services (SOAP 3ch Receiver, where the first giving the information needed to Reliz these movements, the second and third items of data are the legacies ).

As the scheme is as follows:

receives asynchronous -> synchronous transmission to service 1 -> Synchronous sending to service 2 -> synchronous transmission to service 3.