cancel
Showing results for 
Search instead for 
Did you mean: 

designing a synchronous scenario

sabyasachi_mohapatra3
Participant
0 Kudos

Hello experts

we have a proxy to webservice scenario.The requirement is to get back the response within 3 seconds or else raise a timeout exception.Any idea about how to design this.

Accepted Solutions (0)

Answers (5)

Answers (5)

sabyasachi_mohapatra3
Participant
0 Kudos

OK

Former Member
0 Kudos

Hey

Why not configure CCMS monitoring,you can specify this interface and specify the threshold value for it(3 sec in your case).

CCMS can also monitor your total XI landscape

/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2

In the above blog he has shown how to configure CCMS for threshold.

Thanks

Aamir

sabyasachi_mohapatra3
Participant
0 Kudos

Hi

can anyone please suggest how to set the deadline step with the deadline time in seconds.

because we can set only minutes,hours,days in the deadline step.

thanks

sabyasachi

sabyasachi_mohapatra3
Participant
0 Kudos

Hi

can anyone please suggest how to set the deadline step with the deadline time in seconds.

because we can set only minutes,hours,days in the deadline step.

thanks

sabyasachi

former_member200962
Active Contributor
0 Kudos

you can use a BPM...include a Block Step ---> put a Deadline Branch ---> set time as 3 sec...put a control step in it and choose the action as Throw Alert...check if this design approach suits your req...

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

>>>you can use a BPM...include a Block Step ---> put a Deadline Branch ---> set time as 3 sec...put a control step in it and choose the action as Throw Alert...check if this design approach suits your req...

1. you cannot (or should never) use a BPM for a sync scenario - it is very likely it will always be more then 3 sec with a BPM

2. this is not possible without a BPM for one interface

Regards,

Michal Krawczyk

former_member200962
Active Contributor
0 Kudos

thanks for the correction:)

Thanks,

Abhishek.