This article discusses about how to automate recovery of certain activities.
Below activities can be configured for recovery.- All activities (for example, wait activities and OnAlarm branches of pick activities) that have an associated expiration date and are scheduled with the SOA Infrastructure to be rescheduled
- All activities that are not complete over a provided threshold time
- All invoke and callback messages that are unresolved
Login to EM console,go to SOA Infrastructure Home=> SOA Administration > BPEL Properties.Now click More BPEL Configuration Properties.
We can see two types of scheduling for auto recovery.
- RecurringScheduleConfig
- StartupScheduleConfig
Recurring Schedule is used to configure a repeated execution of recovery process periodically.It is time window based and always better to execute this during off-peak hours.
Startup Schedule is used to make all faulted instances are automatically retried when the SOA server is restarted.
MaxMessageRaiseSize denotes maximum no.of messages to be retired in every retry attempt and other attributes are reminiscent.
No comments:
Post a Comment