Team,

Need one query/help on auto - re-submission of the webMethods service: pub.monitor.serviceControl:resubmit

We are trying to resubmit a failed service/transaction automatically, rather than manually logging into MWS and do the job.

Scenario: A service by name sendAcknowledgement have a logic to do it’s ack job. In case if the service is getting failed, it will log an error OR a failed transaction in MWS.

Now, we have built another service, called: resubmitACK, where we are using the service: pub.monitor.serviceControl:resubmit to perform the task. The submission will happen based on the contextID which is generated for each transaction.

Issue:

While running the resubmitACK service, the transactions are not getting submitted; But when we log into MWS, navigate under the service section and search for the failed transaction; then if we resubmit the data, the service gets executed successfully.

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/97694f62f43223bcad40f5a05c448c6659c48256.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/97694f62f43223bcad40f5a05c448c6659c48256.jpeg 2x" data-dominant-color="E8E8EA">

2.JPG757×423 63.6 KB

What is the output of pub.monitor.service:isResubmittable when you run it by contextID?

You can resubmit services to any Integration Server that is defined as a remote
server in the Integration Server Administrator for the local Integration Server (that
is, the Integration Server on which Monitor is installed). If you want to resubmit
services on the local Integration Server, that Integration Server must be defined to
itself as a remote server. The remote server alias you enter in the Integration Server
Administrator must be the complete DNS name for the Integration Server (for example,
titanium.east.webmethods.com).

Hi,

When the picture 1.JPG as shown below, the value is getting ture; Now as shown in the WMS pciture 2.JPG, this is the service which we are trying to submit manually from the service as shown previously using the service: pub.monitor.serviceControl:resubmit.

But still it is not working.

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/d921f1eed3f85b4552c6dd55e1b760191c638d63_2_1035x285.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/d921f1eed3f85b4552c6dd55e1b760191c638d63.jpeg 2x" data-dominant-color="E4E8EC">

2.JPG1151×317 41.7 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/11bdfcc317e56b062e7b485d2f971138715cfa3c.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/11bdfcc317e56b062e7b485d2f971138715cfa3c.jpeg 2x" data-dominant-color="EBEAE9">

1.JPG910×432 64.8 KB

Now, as you can see, initially we are searching the transaction which are failed as shown in picture 1.JPG and as shown in picture 2.JPG there are so many failed transactions been populated.

In our service, what we are trying to do is:

1. get all failed transactions for a particular service
2. populate each failed transaction information under a string inside a document and populate as many documents as the failed transactions are under a document list
3. loop over them and based on context id, resubmit automatically.

Picture 3 explains all.

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/ba94ed00972f199e0be7df8d5846f00d8013ab39_2_1035x124.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/ba94ed00972f199e0be7df8d5846f00d8013ab39.jpeg 2x" data-dominant-color="C6D3DF">

2.JPG1130×136 39 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/7a4d3d1a5aad2215fbd1ccb4bc735f9d45508b41_2_1035x432.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/7a4d3d1a5aad2215fbd1ccb4bc735f9d45508b41.jpeg 2x" data-dominant-color="E6EAED">

1.JPG1122×469 66.6 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/1584a50b1278f320da3284509cb8e4aab42cde76_2_1035x502.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/1584a50b1278f320da3284509cb8e4aab42cde76.jpeg 2x" data-dominant-color="E6E5E5">

3.JPG1363×662 225 KB

Can you confirm why the service failed in the first execution, due to data error or connection error?

If data error, you have to get the current pipeline by its context id (pub.monitor.service:getPipeline) and then modify the pipeline and pass it to pub.monitor.serviceControl:resubmit

I tried the same and it is working as expected.

Manju, are you sure you have done right code as Mahes was able to run it successfully. Better share your code what all needed to us ( Remove org specfic Util services if any from your service ) so that we can correct if any.

Thanks,

Manju, are you sure you have done right code as Mahes was able to run it successfully. Better share your code what all needed to us ( Remove org specfic Util services if any from your service ) so that we can correct if any.

Thanks,

Hi Manju,

Can you trace your code up to the control:resubmit step and verify pipeline if in the run-time variable are getting populated properly.As in the earlier post you have mentioned you are able to manually resubmit from mws,hopes there should not be any problem with audit settings or monitor related issue.

Also before resubmit you can use isResubmittable service to verify if the particular service is resubmittable.

Thanks
Baharul Islam

Hi,
I’m also facing the issue while re-submitting from flow servie.Scenerio i tested is i created one service which divides to numbers.I ran this service giving input as 1 and 0 deliberately so that the service will be failed.Then i went mws and got the context id of this failed service.Then by using this context id i fetched the pipeline using in buile monitor service then modified the pipeline by entering a number instead of 0,then i called “pub.monitor.serviceControl:resubmit” by giving the same contextid and pipeline to it.Then i verified in MWS still i see the old failed service only.And i don;t find the service with re-submitted status.I’m attacing the code.Please correct if i’m doing any thing wrong in this scenerio.

Mahesh – Can you please share the sample code which you have written as a few members could not able to resolve the issue.

Thanks,

Hi Mahesh,

Is it possible, can you please do send / post the code; Not sure where we are lost in between.

Thank you.

Sure, attaching the code sample on request.

Make sure the remote server is correctly set as shown in screen shot Capture_1

Run the service MonitoringServicesCodeSamples:resubmitServices with the failed context ID with the input as show in the screen shot

After resubmission you will a new contextID see Capture_2

MonitoringServicesCodeSamples.zip (6.53 KB)

Attaching screen shots

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/c8ef64c087f06001191ec7a664d780c49aa50041_2_1035x54.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/c8ef64c087f06001191ec7a664d780c49aa50041.jpeg 2x" data-dominant-color="C9D7DE">

Capture_2.JPG1125×60 31.9 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/1ed5380cfd69fb92878496f1e91b3c3e6296cef2_2_1035x369.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/1ed5380cfd69fb92878496f1e91b3c3e6296cef2.jpeg 2x" data-dominant-color="E8EBEA">

Capture_1.JPG1250×447 80 KB

Thank you Mahesh sir; Well we did follow as you mentioned, it worked just fine.

There were a small hiccup when we had to work on in multiple IS instances and multiple MWS instances. We where having a rough time in figuring out a way to submit the service w.r.t specific serverID. Now we got that, done!

Thanks a ton.

You are welcome

@ Jack,
Are we good now?

Yep we are.

Yes Mahesh…we are good now.Thanks a lot