Enabling persistence

The Orchestration pane contains an Enable Persistence check box that by default is selected. The setting of the Enable Persistence check box affects the way orchestration jobs are restarted after a failure.

About this task

The effect of setting of the Enable Persistence check box is described by the following two options:
Enable Persistence check box is selected
During run time if an orchestration job is running and a failure occurs that causes the job to stop, when the orchestration is restarted, the original job continues processing where it stopped and no in-flight messages are lost.
Enable Persistence check box is cleared
During run time if an orchestration job is running and a failure occurs that causes the job to stop,  when the orchestration is restarted, the current job does not complete and the in-flight messages are lost.

When the Enable Persistence check box is cleared the run time performance is improved.

Note:

When an orchestration that has Web Services Provide service starter activity with Transport type set to Local, referred to as sub-orchestration, then persistence setting for the main orchestration and the sub-orchestration should be same within the same project.

For example, if the persistence is enabled for the main orchestration, then it should be enabled for the sub-orchestration also. If the persistence is disabled in the main orchestration, then it should be disabled for the sub-orchestration and vice-versa.

Note:

You should enable persistence for the FTP Poll Directory activity:

  • If you have an orchestration job with a FTP Poll Directory activity that is processing large input files. Otherwise, you can experience problems like "Variable 'Lotdata' is too large, please turn on persistence for this orchestration".
  • If you disable persistence and have an orchestration job with a FTP Poll Directory activity with the Keep in place option selected, and during run time if a failure occurs that causes the job to stop, when the orchestration is restarted it processes the file again. The state of the job is lost and Integration Appliance does not know that it has already processed the file.

The following activities require that persistence be enabled when the Exactly Once option is selected in the Delivery Rules for the activity:
Database
Poll Table
Get Inserted Row
Get Updated Rows
Get Deleted Rows
Insert Rows
Update Rows
Delete Rows
Call Procedure
Email
Get Email
FTP
Poll Directory
JMS
Subscribe Message
Poll Message
MQ
Poll Message
SAP
Receive IDOC
Send IDOC
SFDC
Poll Deleted Objects
Poll Updated Objects
Domino®
Get Created Documents
Get Deleted Documents
Get Updated Documents

Procedure

  1. To change the setting of the Enable Persistence check box, select Orchestration > Properties from the toolbar menu. The Orchestration pane is displayed.
  2. Select Enable Persistence check box.



Feedback | Notices


Timestamp icon Last updated: Sunday, 09 September 2018


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.doc/enabling_persistence.html