Hi ,

I have written a piece of code to monitor the ERP application connectivity in webmethods.
The code will have to check for ERP connectivity, if that is not available, the webMethods trigger has to be suspended and then it will repeatively check for the connectivity. if its avalable, the triggers will be resumed.

Now the issue is, I have scheduled the code for every three minutes.
The moment the connectivity is not available the flow executes and then it is suspending the triggers, Ideally it has to repeat the loop to check for the connectivity but what is happenning is the flow completely executes once it reaches 3 minutes which is resuming the triggers.

I need clarifications with respect to scheduler, to handle this situation.

Hi,

You can have a Scheduler for executing this code for every 30 seconds or 60 seconds. Since you are checking the connectivity, Scheduling your service for every 30 seconds would be fine.

Now, since you are checking the connectivity for every 30 seconds there is no need to check for the connectivity repeatively inside your code.

Just follow the below simple logic inside your code:

-> First check for the connectivity

if(ERP not available)
Disable triggers
else
Check for the trigger status(disabled/enabled)
if(disabled)
enable them
else
exit(main sequence)

So if there is no connectivity then only you will be disabling the triggers, if your connection is active then it will just check for your disabled triggers(if any) and enables them.



Thanks

Thanks for the reply.

I will implement it and let you know the status.

Regards,
vinodini

Did it worked ?

KK

Hi ,

This way of implementation resolved the actual issue.

But with one constraint, I have configured email option when there is any issue and when it is resolved in my previous logic.

With the new logic, when there is any issue the email is triggered for every execution and I am unable to place the resolved email .

Thanks,
Vino

Hi,

Try the place the email/smtp service like below:

-> First check for the connectivity

if(ERP not available)
Disable triggers
Send email
else
Check for the trigger status(disabled/enabled)
if(disabled)
enable them
else
exit(main sequence)

So When there is ERP unavailable then only you would be sending the mail until its up.


Thanks

Hi ,

Thanks for the reply.

I have done in the same way as you mentioned above.

But earlier when the issue was resolved , I use to send the mail stating it has resolved. which was really helpful.
But now I was not able to place that logic.

Regards,
vino

Hi Vino,

Try this:

-> First check for the connectivity

if(ERP not available)
Disable triggers
Send email(Configure your Failure message here)
else
Check for the trigger status(disabled/enabled)
if(disabled)
enable them
[b]Send email(Configure your Success message here)[/b]
else
exit(main sequence)

So When there is ERP unavailable then only you would be sending the mail until its up and when it's up immediately you will receive a notification of the ERP availability status.

Hope this resolves your issue.

Thanks.