11 Scheduling Trading Partner Downtime
This chapter describes how to schedule Trading Partner downtime, which allows Trading Partners to notify each other about downtime and to delay message delivery during downtime.
In a competitive B2B world with high volume message flow, it is not possible to compromise on the processing capability of the B2B infrastructure, thereby creating the need of scheduling Trading Partner downtime. This results in processing the messages, even during trading partner's downtime, from the sender's perspective, and managing the maintenance or load of the recipient.
This chapter includes the following sections:
Introduction to Scheduling Trading Partner Downtime
Various Trading Partners schedule their downtimes for different reasons and notify their partners about the downtime. Scheduling the trading partner downtime in Oracle B2B ensures that messages are not delivered during the downtime period, yet are processed by Oracle B2B such that the messages are ready for delivery when the Trading Partner becomes available after downtime.
Trading Partner Downtime can be scheduled using a command line utility. See Scheduling Trading Partner Downtime for more information.
It is not possible to reduce the length of scheduled downtime using either the console or the command line utility. To interrupt a scheduled downtime, or end an open-ended downtime, you can delete the schedule. See Deleting Scheduled Downtime for information.
At present the functionality to extend the time of a schedule using the console is not available. To extend the length of a scheduled downtime use the command line utility. See Extending Trading Partner Downtime for an explanation of the options.
Scheduling Trading Partner Downtime
As a pre-requisite, it is required to enable the dispatcher in Oracle B2B. The number of dispatchers depends on the load and configuration of the system. The Outbound Dispatcher Count should be at least 1.
Note:
For more information, refer to Configuring B2B System Parameters .
To schedule downtime:
Deleting Scheduled Downtime
To interrupt a scheduled downtime, or end an open-ended downtime, you can delete the schedule.
To delete a scheduled downtime:
Extending Trading Partner Downtime
You can overlap schedules or use the Extend
option to alter an existing schedule.
The following options enable you to alter an existing schedule.
Overlapping Schedules
Overlap is allowed using different schedule names. Overlap is not allowed with the same schedule name.
Consider a schedule X between 4:00 AM to 6:00 AM. It is possible to create a new schedule Y with start time 5:00 AM to end time 7:00 AM. This makes the effective schedule from 4:00 AM to 7:00 AM.
Using the Extend Option
By default an error is thrown while extending an earlier created schedule. User can extend the schedule using the command line option -Dextend
.
Consider a schedule X between 4:00 AM to 6:00 AM, it is possible to extend it by creating a new schedule X with option -Dextend=true
between 6:00 AM to 8:00 AM. This makes the effective schedule from 4:00 AM to 8:00 AM.
See Scheduling Trading Partner Downtime for information and examples about using the command line options.