Payload modification in case of ESB Resequencer in 10g for Customer Hub PIP

Question

Hi all,
We are implementing customer hub PIP and in that PIP there is a particular ESB consumer (SyncContSiebelAggrEventConsumer) where the routing service AIASystem_Siebel_ABCS_SyncContSiebelAggrEventConsumer_RS.esbsvc is implementing FIFO ESB Resequence pattern.
Now we have enabled ESB re-sequence by modifying the esb_config.ini file and testing the scenario.
This is what we observer:
When we publish a particular contact belonging to a particular group say 'XYZ' then for any kind of payload error in the contact information the SyncContactSiebelReqABCSImpl is errored out which I can see both from BPEL console and from ESB console.
As a result the group gets locked and subsequent messages belonging to the same group is getting queued up.
Now the execution rule between SyncContSiebelAggrEventConsumer and SyncContactSiebelReqABCSImpl is Asynchronous and so from ESB console I am getting the option to modify the payload and re-submit it after unlocking the group using resequencer_restart_processing_group.sql script.
However I find that the payload I modified is not getting reflected and the ESB resequencer is submitting the same old payload and as a result the business error is getting re-generated and the group again getting relocked.
How do I modify the payload and re-submit the message when I am using ESB re-sequencer?
Thnks
Mandrita.

Answer 1

Hi all,
We are implementing customer hub PIP and in that PIP there is a particular ESB consumer (SyncContSiebelAggrEventConsumer) where the routing service AIASystem_Siebel_ABCS_SyncContSiebelAggrEventConsumer_RS.esbsvc is implementing FIFO ESB Resequence pattern.
Now we have enabled ESB re-sequence by modifying the esb_config.ini file and testing the scenario.
This is what we observer:
When we publish a particular contact belonging to a particular group say 'XYZ' then for any kind of payload error in the contact information the SyncContactSiebelReqABCSImpl is errored out which I can see both from BPEL console and from ESB console.
As a result the group gets locked and subsequent messages belonging to the same group is getting queued up.
Now the execution rule between SyncContSiebelAggrEventConsumer and SyncContactSiebelReqABCSImpl is Asynchronous and so from ESB console I am getting the option to modify the payload and re-submit it after unlocking the group using resequencer_restart_processing_group.sql script.
However I find that the payload I modified is not getting reflected and the ESB resequencer is submitting the same old payload and as a result the business error is getting re-generated and the group again getting relocked.
How do I modify the payload and re-submit the message when I am using ESB re-sequencer?
Thnks
Mandrita.