cancel
Showing results for 
Search instead for 
Did you mean: 

Manual Cancellation of integration process possible?

Former Member
0 Kudos

Hello,

is it possible to cancel an integration process which is not in error status but waiting for a message or is just open because of a waiting step etc.? How would I do that?

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
0 Kudos

There is an option of deleting these open instances using SWWL transaction. But t should be used carefully in Production.

Regards,

Prateek

Former Member
0 Kudos

Hmm, so this should be done only in "emergencies" but never as a regular way to close processes?

prateek
Active Contributor
0 Kudos

Exactly. But the best design would be when such a requirement almost never arises. This could be achieved if you use proper error handling (using branch with exception).

Regards,

Prateek

Former Member
0 Kudos

Yes, sure, from a design point of view such situations should be avoided completely, I fully agree.

However I just found out (as I activate a correlation ID in the start step) that there may be some rare cases where a message could be resent which contains the same correlation ID and question was whether a running process could be stopped before.

By the way what would happen if you send a message containing the same ID used for correlation that is already activated in an open process?

prateek
Active Contributor
0 Kudos

a message could be resent which contains the same correlation ID and question was whether a running process could be stopped before.

In such rare cases, SWWL should help. This will ensure that there will be new instance created. The thing to be kept in mind here is that if there are multiple systems involved you need to inform each one about resending file.

By the way what would happen if you send a message containing the same ID used for correlation that is already activated in an open process?

If there are more receive steps waiting for same messages, then there would be duplicate message picked up in the same instance. If the receive step is not for same message, new instance would get created.

Regards,

Prateek

Former Member
0 Kudos

There is only one receive step, that would activate the correlation ID and another receive step waiting for message to be correlated.

So if two instances with the same correlation ID are created (and active) what would happen if I receive another message to be correlated to an existing instance?

prateek
Active Contributor
0 Kudos

Say the message activating correlation is M1 and other correlated message in M2. Now if you receive two files with structure M1, two correlation instances would get created I1 and I2. Once you receive M2, I1 process gets completed. In the meantime if another M1 is received, there will be again 2 open instances which will keep on waiting for M2 messages.

I hope this haven't confused you.

Regards,

Prateek

Answers (1)

Answers (1)

Former Member
0 Kudos

Thank you very much for the additional explanation. I think I understand now the mechanism for several correlations.