TIDAL ENTERPRISE SCHEDULER VERSION 5.3.1

TIDAL ENTERPRISE SCHEDULER VERSION 5.3.1 These release notes highlight new features, enhancements and changes within Tidal 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 XBP Version Determination 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. As with other Tidal events, an action can be associated to the event. 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. 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. ʺ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. Note A failure logging onto XBP 1.0 is a final failure. 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. 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. 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. Copyright 2004 2007 by Tidal Software, Inc. 1

Tidal Enterprise Scheduler Version 5.3.1 Release Notes Windows Vista and Windows Server "Longhorn" Support Support For the Windows Aero Interface Support For the New User Account Control The Scheduler Client now creates any new files/folders in the userʹs Application Data folder as recommended. No files are created under ʹProgram Filesʹ after the installation has taken place. 2 Copyright 2004 2007 by Tidal Software, Inc.

New Features Scheduler Master Installation on Windows Server Longhorn Scheduler Master can now be installed on Windows Server ʺLonghornʺ Referencing Local Variables Local variables can now be referenced in a file dependency. Adding Images For a Job To make adding images for a job more intuitive, 5.3.1 includes Add, Edit/Rename, Replace and Delete buttons. Check User's Access to Runtime User Client modified to ensure the user that is about to edit a job has access to the runtime user and the agent for which this job has been defined and only then allow the edit operation. This has to be done both for Job Activity and Job Definition screens. Option to Add Runtime Users A superuser now has access to all runtime users by default. File Lookup Browse Configuration A system wide configuration option has been added that allows the File Lookup Browse button to be hidden. Output Storage Job event does not fire off before output has been processed for trigger Error Occurred While Launching Job. The output is now stored before setting status to Error (which fires a job trigger, which could want the output) Copyright 2004 2007 by Tidal Software, Inc. 3

Tidal Enterprise Scheduler Version 5.3.1 Release Notes New Variable for Transporter Users can now use Scheduler 5.2 FTP host as a variable for Transporter when transporting jobs. Additional Security Security for ʺJob Logʺ and ʺJob Spoolʺ for SAP job details added. Operator Release Function MDELETE Option for FTP Jobs A job that requires operator release can now be released by the operator independent of whether or not its dependencies are satisfied. Additionally, for any job in the schedule that has not yet launched, the operator can set and modify the requirement that the operator must release the job, independent of the job s state. The following changes have been made: A Job Activity context menu option Require Operator Release will have two states, checked and unchecked indicating the current setting for the job. Once the job has launched or gone into Waiting on Operator status, the option is grayed out. Two new Job Actions are available, Require Operator Release and Override Operator Release. The WaitOp column in the JAC is updated when the operator release requirement changes. You can now delete multiple files on a remote host with an FTP job (Any protocol). Explicit FTPS Support (FTP Over Secure Sockets) We now support the TLS protocol of FTPS to transfer files via the Secure Socket Layer (SSL) as specified in RFC 4217. 4 Copyright 2004 2007 by Tidal Software, Inc.

Changes from 5.3.0 to 5.3.1 Changes from 5.3.0 to 5.3.1 SAP Added SAP Security The following security functions have been added to the SAP jobs Security Policy: SAP Jobs With Large Output View Job Log SAP Connection Definition Dialog View Job Spool These two new security functions will control a user s ability to view the SAP job s job log and job spool. Functionality has been enhanced to provide more information about a job s spool and output. Scheduler can now be configured to specify an upper limit on SAP Job Log and Spool. Functions BAPI_XBP_JOB_READ and BAPI_XBP_JOB_DEFINITION_GET have been enhanced to return more information about the spool lists and job log created by a job. Scheduler will determine whether or not to retrieve Job Log/Spool if either of these returns high values for the Job Log/Spool size. The SAP Connection Definition dialog is now enhanced to allow user limits on log and spool size. The following specifications have been added to limit collection of large Job Log and Spool. Maximum Job Log size (in kbytes) Maximum Job Log size (in kbytes) These options are used to determine whether or not SAP Job Log and Spool should be retrieved during output collection. With these options, users may specify an upper limit for Job Log and Spool. Prior to Scheduler saving Job Log and Spool as output, it will read the job s Log and Spool attributes and avoid Log and Spool collection, if these limits are exceeded. Note Job Log and Spool apply only to jobs defined to collect output. Copyright 2004 2007 by Tidal Software, Inc. 5

Tidal Enterprise Scheduler Version 5.3.1 Release Notes Oracle Applications Connection Definition Dialog Has a New Options Tab The new Options tab describes existing options ORADEBUG and OraAppsDBConnection which had been previously specified in master.props. These are now defined in Configuration Parameters under Options. New parameters have been added. The parameter values below are the default values: BATCH_STATUS_CHECK indicates whether the status of requests will be performed in batches (default = Y). If set, BATCH_STATUS_CHECK_SIZE specifies the batch size (default=100). When request statuses are checked in batches, fewer Database transactions are sent to the server. Only after the batch size limit is reached, will a single Database transaction be initiated to get the status of all requests defined in the batch. Using this parameter may result in a slight delay in retrieving request statuses, if many requests are running. If BATCH_STATUS_CHECK = N, then request statuses are not performed in batches. This means a Database transaction is initiated for every request, resulting in more transactions being sent to the server. With this option, there is no delay in waiting for the batch limit to be reached, however it may result in slower performance as more Database transactions are initiated, 1 for every request. DATA_CACHE_TIMEOUT specifies the expiration time (in seconds) of any cached data. The default is 600 seconds or 10 minutes. Connection Definition Dialog Change for Oracle Apps New Oracle Apps Agent List New View Parameters Button The connection method has changed. It no longer requires master.props values for the TNS file to be defined to connect. The new connection method uses jdbc to connect, similar to the OracleDB Adapter. You now have the option to add an Oracle Apps agent list. The Intercepted Job Details screen now includes a View Parameters button to allow viewing of this jobʹs parameters. Selecting the View Parameters displays the runtime values for this job. 6 Copyright 2004 2007 by Tidal Software, Inc.

System Configuration Requirements System Configuration Requirements The minimum hardware and software specifications required for Scheduler may change with a new release. The software applications supported by Scheduler change to reflect the current versions of the software application. Each product release from Tidal Software is updated to keep pace with the upgrade releases of other software applications. The upgrade cycle for Scheduler is not always synchronized with the upgrade cycle of the software applications supported by Scheduler. New versions may be released after this release of Scheduler went to testing so supported software application versions may get out of sync with Scheduler. Always verify that the software applications that you are using are supported by the new release. Operating System Requirements Consult the following table to ensure that your system meets the minimum requirements for installing and running Tidal Scheduler. The operating system requirements are updated during each release to stay abreast of the changes that constantly occur as operating system standards evolve. Successful operation of Scheduler depends upon using an operating system that has been tested and is supported by Tidal. The current shelf report listing the versions of applications and operating systems that are supported for use with Scheduler is available on the corporate Web site in the Technical Services area at www.tidalsoftware.com. Be sure to use additional RAM and disk space as necessary for your particular environment. Minimum System Requirements UNIX System Requirements The hardware and software requirements for the Scheduler have changed in 5.3.1. Be sure to check the specifications for your system to ensure compatibility with the most recent release of Scheduler. The following table lists the current minimum system requirements for running Scheduler 5.3.1. The following table lists the hardware and software requirements for using Scheduler on Unix. The specified quantities of CPU, memory and disk space must be available for exclusive use by Scheduler. Be sure that a user has access to the JVM. Table 1 Minimum System Requirements for UNIX Operating Systems System Client Master Agent Hardware CPU Intel Pentium 800 MHz or higher Dual 500 Mhz or higher 800 Mhz or higher Memory 512 MB RAM 1 GB RAM (The use of any Scheduler adapters requires an additional 1 GB.) Disk Space 50 MB 300 MB (product & logs) 256 MB RAM 100 MB (program & data) Copyright 2004 2007 by Tidal Software, Inc. 7

Tidal Enterprise Scheduler Version 5.3.1 Release Notes Table 1 Minimum System Requirements for UNIX Operating Systems System Client Master Agent Software Operating System Windows 2000 (SP4) Professional, Server and Advanced Server Windows XP Pro (SP2) Windows Server 2003 (SP1) MDAC 2.7 or later Windows Vista Windows Longhorn HPUX 11i(RISC) JVM 1.5+ HPUX 11i v1, v2(itanium) JVM 1.5+ Solaris 2.8, 2.9 or 2.10 (Sparc) JVM 1.5+ AIX 5.1, 5.2 or 5.3 JVM 1.5 Linux Redhat Enterprise Server v3 Intel kernel 2.4.21(Sun JVM 1.5+); v4 Intel (x86) kernel 2.6.9 (Sun JVM 1.5+) Linux SUSE Enterprise Server v8 Intel (x86) kernel 2.4.21(Sun JVM 1.5+); v9.3 Intel (x86) kernel 2.6.9 (Sun JVM 1.5+) HPUX 11.x(RISC) JVM 1.5+ HPUX 11i(Itanium) JVM 1.5+ Solaris 2.8, 2.9, 2.10 JVM 1.5 Linux Redhat Enterprise Server v3 Intel kernel 2.4.21 Sun JVM 1.5+; v4 Intel (x86) kernel 2.6.9 Sun JVM 1.5+ Linux SUSE Enterprise Server v8 Intel (x86) kernel 2.4.2 Sun JVM 1.5+; v9.3 Intel kernel 2.6.9 Sun JVM 1.5+ AIX 5.1, 5.2, 5.3 JVM 1.5+ Tru64 v5.1a JVM 1.5 Databases Oracle UNIX 9.2 and 10g (Oracle Provider software for Scheduler client) 200 MB data, 100 MB index, 200 MB temp Windows System Requirements The following table lists the minimum system requirements for installing and running Scheduler on Windows. The specified quantities of CPU, memory and disk space must be available for exclusive use by Scheduler. Use additional RAM and disk space as necessary for your particular environment. Be sure that a user has access to the JVM. Table 2 Minimum System Requirements for Windows Operating Systems System Client Master Agent Hardware CPU Intel based Pentium 800 MHz or higher Intel based Pentium 1GHz or higher Intel based Pentium 800 MHz or higher Memory 512 MB RAM 1 GB RAM (The use of any Scheduler adapters requires an additional 1 GB.) 256 MB RAM Disk Space 50 MB 300 MB 20 MB CD ROM 2x 2x 2x Network Card Network card (Windows for TCP/IP) Network card (Windows for TCP/IP) Network card (Windows for TCP/IP) 8 Copyright 2004 2007 by Tidal Software, Inc.

System Configuration Requirements Table 2 Minimum System Requirements for Windows Operating Systems System Client Master Agent Software Operating System Windows 2000 (SP4) Professional, Server and Advanced Server Windows XP Pro(SP2) Windows Server 2003 (SP1) Windows Vista Windows Longhorn Standard or Enterprise MDAC 2.7 or later Windows 2000 (SP4) Server and Advanced Server JVM 1.5+ Windows Server 2003 (SP1) Standard or Enterprise JVM 1.5+ Windows Longhorn Windows 2000 (SP4) Server and Advanced Server Windows 2000 Advanced Server cluster Windows Server 2003 (SP1) Standard and Enterprise Windows NT (SP6a) Windows Longhorn Databases MSSQL Server v2000 (SP3a or SP4) and MSSQL Server 2005 single or multi instance 128 MB Data, 32 MB Log Oracle 9.2 and 10g Oracle Provides software for Scheduler client 200MB Data, 100MB index, 200MB temp Warning It is recommended that no more than five agents be run on the minimum hardware platform. However, the number of agents that can be run on a given server depends upon the CPU and memory resources available on the machine. Add a single agent at a time and gauge the effect of each added agent on system performance before adding more. You have to experiment with the configuration to achieve optimal results. Tidal Enterprise Scheduler v5.3.1 supports virtual machines on the following: Microsoft Virtual Server 2005 VMware GSX Server 3.1 VMware ESX Server 2.5 Copyright 2004 2007 by Tidal Software, Inc. 9

Tidal Enterprise Scheduler Version 5.3.1 Release Notes Known Issues Sun Java Bug# 6501839 Workaround: After applying Microsoft DST patch, the Java Runtime fails to read the timezone correctly from the OS. After the Windows DST patch is applied, open ʺDate and Timeʺ in the Windows control panel, select the Time Zone tab, then click OK. Unhandled PeopleSoft Exception Retrieving Run Controls Workaround: When defining App Engine AR_AUTOMNT with run control FSYS using PS 8.45 on Microsoft SQL and selecting the Run Control tab, an unhandled exception dialog displays. Run controls appear after clicking OK through 2 exception dialogs. From within Internet Explorer, select Tools>Internet Options to display the Internet Options dialog and then click the Advanced tab. Figure 1 Internet Options Dialog Under Browsing, select Disable script debugging (Internet Explorer). If this option is not selected, it may cause the html script to be debugged, resulting in an exception because java scripting was disabled in the html. 10 Copyright 2004 2007 by Tidal Software, Inc.