Cisco Cisco Tidal Enterprise Scheduler 6.2 Release Notes
Copyright ©2004–2007 by Tidal Software®, Inc.
1
T
IDAL
E
NTERPRISE
S
CHEDULER
V
ERSION
5.3.1
These release notes highlight new features, enhancements and changes within Tidal
Enterprise Scheduler
Enterprise Scheduler
™
(Scheduler) v5.3.1. If you encounter any problems or have any
questions, contact Tidal Software Technical Services at (650) 475‐4600.
New Features
The following new features are included in this release of Tidal Enterprise Scheduler.
SAP Event Monitoring
Scheduler can be configured to monitor SAP events and to then take some action given
this event trigger. This feature is only available for SAP connections defined as XBP 3.0.
this event trigger. This feature is only available for SAP connections defined as XBP 3.0.
As with other Tidal events, an action can be associated to the event.
XBP Version Determination
XBP (External Interface for Job Background Processing) is SAPʹs open interface that
allows software vendors such as Tidal to schedule and monitor SAP jobs. After
connecting to the SAP server, Scheduler then logs onto the corresponding XBP interface.
allows software vendors such as Tidal to schedule and monitor SAP jobs. After
connecting to the SAP server, Scheduler then logs onto the corresponding XBP interface.
Previously the XBP version to log onto was determined by the R/3 version as follows:
ʺ4.5xʺ (XBP 1.0)
ʺ4.6xʺ (XBP 2.0)
ʺ6.xʺ (XBP 2.0)
ʺ7.xʺ (XBP 2.0)
If we fail to log onto XBP 3.0, then we will try again with XBP 2.0 and a warning message
similar to the following will be logged.
similar to the following will be logged.
ʺXBP 3.0 is not available. Trying XBP 2.0ʺ
Similarly, if we fail to log onto XBP 2.0, then we will try to log onto XBP 1.0.
For added flexibility, we now provide an option to specify the XBP version in the
connection definition, as different features are available depending on the XBP version.
connection definition, as different features are available depending on the XBP version.
For upgraded connections defined prior to Scheduler 5.3.1, where the XBP version was
not defined in the connection definition, the same logic explained above will be utilized.
not defined in the connection definition, the same logic explained above will be utilized.
For new connections defined in Scheduler 5.3.1, the XBP version will be defaulted to 2.0.
In this case, the XBP Version is now a required field and you will not be able to save the
connection w/o first defining a value here.
In this case, the XBP Version is now a required field and you will not be able to save the
connection w/o first defining a value here.
Note A failure logging onto XBP 1.0 is a final failure.