The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Before you can run TES, you need to run through the licensing procedure. This applies whether you are just trying out the software, or have already decided to implement TES. TES provides different types of licenses to fit your needs.
Note Ensure that your database is licensed in line with your database vendors licensing terms and conditions.
Extensions and modules that add extra functionality to TES may require separate licenses. For example, SACmd (TES command line interface), the job monitoring tool and intermaster dependencies all require individual licenses. For more information and current availability, contact your sales representative.
You can license TES with a Demo license or a Full license. During installation, the installer will prompt you for a demo code, and if you give it a code, then it will create this file for you. When your Demo license expires, or if you did not enter it during installation, you can manually license TES.
The Registered License dialog displays by selecting Activities>Registered License from the main menu of the Tidal Web client.
This tab displays the following information about the master:
The Licensed Agents tab displays information about the agents licensed to work with the master.
Note If your license has a floating agent provision or if you are running an unrestricted demo, you can define your own agents. Consequently, the Licensed Agents tab will display no information.
This tab displays the following information about the agents:
Warning Restart the Client Manager after a new license has been loaded.
Registering the license for TES is done from the Tidal Web client.
To license with a Demo license:
Step 1 Stop the master. You must stop the master before you can load a license file. An error message will display if you attempt to load a license while the master is still running.
a. Click Start and select Programs>TIDAL Software>Scheduler>Master>Service Control Manager .
b. Verify that the master is displayed in the Service list and click the Stop button to stop the master.
Step 2 Create a file called demo.lic .
Step 3 Type the demo code into the demo.lic file.
Step 4 Save and place the file in the C:\Program File\TIDAL\Scheduler\Master\config directory.
– For Windows, restart the master by clicking Start in the Service Control Manager.
– For Unix, restart the master by entering tesm start .
The master will read and apply the demo code when it starts.
To license with a Full license:
a. Click Start and select Programs>TIDAL Software>Scheduler>Master>Service Control Manager .
b. Verify that the master is displayed in the Service list and click the Stop button to stop the master.
Step 2 Rename your Full license file to master.lic.
Step 3 Place the file in the C:\Program File\TIDAL\Scheduler\Master\config directory.
– For Windows, restart the master by clicking Start in the Service Control Manager.
– For Unix, restart the master by entering tesm start .
The master will read and apply the demo code when it starts.
The Tidal Web client has many built-in features designed for productivity and easy access to your production data.
The Main Menu bar is accessible from any pane. However, some menu options are not available from all panes.
For more information about the main menus, see Main Menus.
Note Context menus, available when you right-click the Navigator pane or current pane, are context-sensitive. The menus change according to your current, active pane.
The Navigator pane lists all the components of the Tidal Web client in a hierarchal format. Each TES function has a different pane.
An arrow sign next to a folder indicates that there are folders hidden underneath. Click the plus sign to expand the listing. A solid arrow sign next to a folder indicates that the listing is expanded. Click the minus sign to collapse the listing.
This panel contains the following containers:
In addition, Actions , Events and Agent Lists both have sub-panes that correspond to different types of actions, events and agent lists.
The File main menu has the following options:
Note The Print option on the File menu provides the same functionality as the Print button on the TES toolbar.
The View main menu has the following options:
The Activities main menu has the following options:
Note After selecting Create Schedule, a dialog denotes the success or failure of the compilation.
See Reports Pane for more information about the Reports main menu Job Last Status , Schedule Summary , Dependency Cross Reference and Event History selections.
Enter text that you want to search for within the columns displayed.
Note This field at the top right of the grids will only search text columns that are not grayed out and are string-based. See Searchable Columns below.
The Create Schedule dialog displays by selecting Activities>Create Schedule from the main menu bar. You can also right-click in the Schedules pane and select the Create Schedule option (and other options) from the context menu to recompile a schedule but the options in the context menu do not provide as much control when creating a schedule. It is recommended to use the Create Schedule dialog when creating a schedule.
Use the Create Schedule dialog to recreate the production schedule invoking the compilation process for the dates specified. Only jobs whose calendars include the date(s) specified are included in the schedule.
This dialog contains the following elements:
A forecast schedule is not automatically updated when jobs are modified. If a job within the forecast schedule is modified, the job’s runs within the forecast are deleted rather than modified. The information contained within the forecast schedule is only relevant for the moment that it was created. You must recompile a new forecast schedule to account for modifications to any job parameters since the original forecast was created. The production schedule is recompiled at the beginning of each production day for this reason.
For example: If a job repeats every five minutes, for a total of five times, and no time window is specified for the job, the job will normally run immediately after the automatic compilation at midnight. The result would run separate job occurrences at 12:00 AM, 12:05, 12:10, 12:15 and 12:20. If you manually create the schedule after 12:20 without this setting checked, none of the occurrences will be added to the schedule.
By selecting the For today’s repeating Jobs with no time window, start repeating ASAP option, all five occurrences will run after the schedule is re-created. For example, if you create the schedule at 4:00 PM, separate occurrences run at 4:00 PM, 4:05, 4:10, 4:15 and 4:20.
The Job Activity pane is the key to monitoring and controlling job operations. Within the bounds of your security policy, you can view either the jobs and job groups that are owned by you and owned by any workgroups to which you belong or all the jobs and job groups on the master. For detailed information about the Job Activity pane , see Job Activity Pane Interface.
To display the Job Activity pane, select Operations>Job Activity from the Navigator pane.
Right-clicking in the Job Activity pane displays a context menu providing easy access to job control functions.
The Job Activity pane display can be customized to suit your monitoring needs. You can:
From the Job Activity pane , you can perform job control functions (rerun a job, check dependencies, hold a job, etc.). For example, if a job requires Operator release (such as when the job must ensure that an external resource is free before the job starts), you (as the Operator) can manually release the job from the Job Activity pane using the Release control command.
After installing masters, agents and Tidal Web clients on various machines, you must still configure the connections properly. You configure your TES network connections through the Connections pane. You can also update each machine’s name, activate or deactivate agents for scheduling, change the communication port numbers and adjust the number of jobs that can run concurrently from an agent.
The agent architecture was overhauled to promote faster processing of jobs with a new agent. With the original agent, the master consistently queried the agent for its status. To reduce the workload on the master, the time-consuming task of communicating the status of the agent is now shifted to the agent. The new agent now sends status reports to the master without prompting, allowing the master to concentrate on other tasks and reducing network traffic. Thus new agents do not need an Agent-to-Master file transfer port when defining an agent connection.
Unlike other agents, the new agent has very simple configuration options. Besides the port number and the job limit there is not much to configure with the new agent.
From the Navigator pane, select Administration>Connections to display the Connections pane.
The Connections pane contains the following buttons:
Note You must select a connection for the Edit and Delete connection buttons to activate in the Connections pane. If no connection is selected, these buttons are grayed out.
The Connections pane contains the following columns:
– A green light indicates that the connection is healthy (but does not indicate whether a fault tolerance failover occurred).
– A yellow light in front of the backup master is normal when in fault tolerant mode and indicates that the backup master is in standby mode. A yellow status light also temporarily displays when a master first starts up but changes to green as the master comes online.
– A red light indicates that the connection has failed.
– A gray light indicates that a connection is disabled.
– If Type = Master , the number of minutes of difference between the master and the Client Manager.
– If Type = Agent , the number of minutes of difference between the master and the agent from the point of view of the master.
– If Type = Remote Master , the number of minutes of difference between the local master and the remote master.
Enter text that you want to search for within the columns displayed into this field.
Note This field at the top right of the grids will only search text columns that are not grayed out and are string-based. See Searchable Columns.
From the main menu, select View>Preferences while viewing the Connections pane to display the Connections Preferences dialog.
From the Connections Preferences dialog, you can select which columns display in the Connections pane and arrange the order they appear.
When you right-click in the Navigator pane while viewing the Connections pane, the Navigator context menu displays.
The Connections Navigator context menu contains the following options:
When you right-click in the Connections pane, the Connections pane context menu displays.
Note A connection must be selected in order for the Edit and Delete options to be available in the context menu.
The Connections pane context menu contains the following options:
Note This option does not apply to all connection types.
The Connection Definition dialog displays by adding or editing a licensed component to your TES network. The type of connection being defined displays at the top of the Connection dialog.
The General tab contains the following elements:
Windows agents have a concurrent job execution limitation based on the amount of memory the agent has. It is recommended that you do not set the agent job limit to a value higher than this limitation. In most instances, it is recommended to limit agents to running no more than 80 concurrent jobs. In general, agents should have 5 MB of memory for each concurrent job. Some jobs may require additional memory to process depending upon the needs of the job.
On this tab, the machine name and port number are specified for the connection. The actual name of the fields varies according to the type of connection being defined.
Depending on the connection type, this tab contains the following elements:
Note Do not use port values that are in use by other software programs. Connection performance will be unpredictable.
There is also a Service log file named Service.log for each corresponding adapter. This log is located inside of the corresponding adapter GUID. For example, the SAP Service Log location would be:
C:\Program Files\TIDAL\Scheduler\Master\services\{51C57049-3215-44b7-ABE1-C012FF786010}\log.
Note Changing the level of the Host Environment Log will directly effect the debug level of every adapter.
If you are defining a remote connection, then your Connection tab is slightly different. There are two machine name fields and a Communication Port field.
This tab only appears in the Connections Definition dialog when defining an agent or adapter connection and allows you to add, edit, and delete an agent or adapter outage.
This tab lists the time windows when the agent/adapter will not be available. The actual parameters of the outage are defined from the Outage Definition dialog. Tes will use the information entered here to manage jobs that may not complete before an outage window begins. From a system configuration viewpoint, use the Defaults tab to configure how Tes handles jobs at risk of failing due to a planned outage.
This tab only appears in the Connections Definition dialog when defining an agent connection and displays all the system resources and current values collected for the connection.
This tab only appears in the Connections Definition dialog when defining an agent connection and allows you to add, edit, or delete name/value connection parameters.
This tab only appears in the Connections Definition dialog when defining a remote master.
This tab lists the various names and types of variables published by the specified remote master. The actual value of a variables is only determined when needed as the job processes. The list of variables published by the remote master is regularly updated and cached by the subscribing master with the intermaster dependency.
To change the name of the computer:
Step 1 From the Connections pane, double-click the licensed computer to edit or select the computer and click the Edit button . The licensed computer’s Connection Definition displays.
Step 2 In the Name field, change the computer’s name. This name is used when referring to the computer on TES panes and dialogs.
To change the hostname of the computer:
Step 1 From the Connections pane, double-click the licensed computer to edit, or select the computer and click the Edit button to display the licensed computer’s Connection Definition dialog.
Step 2 Click the Connection tab.
Step 3 In the Machine Name field, update the computer’s name.
This name can be found in the DNS section of the TCP/IP protocol of your network configuration. See your System Administrator for more information.
You can update communication port numbers for licensed connections if they conflict with other programs that use the same numbers.
To change the connection port numbers:
Step 1 From the Connections pane, double-click the desired connection or select the connection and click the Edit button to display the licensed computer’s Connection Definition dialog.
Step 2 Click the Connection tab.
Step 3 Different fields are displayed, according to the type of connection selected:
– Master – The Agent-to-Master Port field is used when defining a master connection. The default is 5591 . This number is specified during installation. Update this port if it conflicts with other programs.
– Agent – The Master-to-Agent Port field is used when defining an agent connection. Update this port number if it conflicts with other programs. The default is 5912 .
– Backup Master – The Backup-To-Master Port field is used when defining a backup master connection. Update this port if it conflicts with other programs. The default is 6704 .
– Fault Monitor – The Fault Monitor Master Port field is used when defining a fault monitor connection. Update this port if it conflicts with other programs. The default is 6703 .
The Fault Monitor Client Port field is a JMS port used by the Client Manager to communicate with the Fault Monitor. The default is 6705 .
– Remote Master – The Communication Port field on this tab is used for communicating between the local master and the remote master. There is always one remote master that will use this port but this port is also available to the remote backup master if the remote master is in fault tolerant mode. The default port for this connection is 6215 , so change the value if there is a conflict. This same JMS Port is also used for the Client Manager to Master communication.
To operate TES, ensure that the master, Client Manager and agent are running on their respective machines. Once installed, the master, its database, the Client Manager and agents should remain running. If any of these components stop, you can restart them on the Windows platform by using the Tidal Service Manager. If you are running fault tolerance, you also need to start the backup master and fault monitor.
The Unix platform does not use the Tidal Service Manager. Controlling the Unix master and its components is done from the command line of the specific machine. The commands for starting, stopping and checking the status of the Unix master, Client Manager and agent are noted.
The Tidal Service Manager is a central point of control for stopping and starting TES services on the Windows platform. Any Enterprise component on the Windows platform running as a service can be manipulated from the service manager. Through the Tidal Service Manager, you can also configure various aspects of how the component service runs.
Click the Windows Start button, and select Programs>Tidal Software>Tidal Service Manager.
This dialog contains the following elements:
The selected service’s status displays at the bottom of the Tidal Service Manager.
Clicking the Browse button while in the initial dialog of the Tidal Service Manager opens a Service Configuration dialog where settings for the master or other services can be adjusted.
The Service tab contains the following elements:
– Automatic – The service starts upon every reboot.
– Manual – The service is only started when you manually start it, for example, through the Tidal Service Manager.
– Disabled – The service will not start as long as the Disabled option is selected.
The Logon tab contains the following elements:
– Allow Service to interact with Desktop – The service runs with the local desktop.
– Password – Type the password for the account specified in the Other Account field.
The Dependencies tab is only available when the service is stopped. You create services dependencies on this tab. Select a service listed in the Available Services column and click the arrow button to move it to the Depends On column.
Normally, after installation and after a reboot, the TES master is automatically started. On Unix, the master is NOT automatically started. You can check the status, start, and stop the master service manually from the Tidal Service Manager for a Windows master or from the command line for a Unix master .
Note If you are using an Oracle or MSSQL Server, ensure that your database is running prior to starting the master service.
The Unix master does not use the Tidal Service Manager so the command line is used to check the status of the master. From the command line of the master machine type:
Step 1 On the machine with the master installation, click the Windows Start button and then select Programs>Tidal Software>Tidal Service Manager to display the Tidal Service Manager .
Step 2 Verify that the Scheduler Master displays in the Service field.
The master status displays at the bottom of the Tidal Service Manager.
The Unix master does not use the Tidal Service Manager so the command line is used to start the master. From the command line of the master machine type:
Step 1 On the machine with the master installation, click the Windows Start button and then select Programs>Tidal Software>Tidal Service Manager to display the Tidal Service Manager.
Step 2 Verify that the Scheduler Master displays in the Service field.
The Unix master does not use the Tidal Service Manager so the command line is used to stop the master. From the command line of the master machine type:
Step 1 On the machine with the master installation, click the Windows Start menu button, then select Programs>Tidal Software>Tidal Service Manager to display t he Tidal Service Manager .
Step 2 Verify that the Scheduler Master displays in the Service field.
You can define timezones where target application environments are based. This allows you to schedule a job or job group across a different timezone. For example, if the Master associated with your job is based in the PST timezone and you want the job to run in an alternative timezone, you can select the defined timezone. The Master internal process will self-adjust the scheduled time or DST (Daylight Savings Times) period differences.
To configure the Master timezone for a job:
Step 1 From the Activity menu, select System Configuration to display the System Configuration dialog.
Step 2 Click the Timezone tab.
Step 3 Click Add or Edit to display the Timezone for Job Definition dialog.
Step 4 In the Name field, enter a unique name to represent job timezone.
Note If the Use Agent Time Zone is selected, the following step does not apply.
Step 5 From the Timezone list, select the timezone ID.
Note As of TES 6.0.3, this option has been relocated from the Master tab to the new Timezone tab.
The following fields pre-populate depending on the Timezone list selection:
– Timezone Full Name – Java build-in timezone long name.
– Master Timezone Offset – The time differences between Master timezone and selected Java timezone.
–
UTC/GMT Timezone Offset
– The time differences between standard
UTC/GMT and selected Java timezone.
– Current in DST Timezone Period – Checked if current in Daylight Saving Time (DST) period for this selected timezone.
– DST Time Differences – The amount of time to be added to selected timezone if it is in DST period.
See Timezone Tab for further instruction.
You can start and stop agents in your network at any time.
Note Before starting or stopping the agent, check the agent’s status using the Tidal Service Manager.
You can change an agent’s job limit to specify the number of jobs that can run on it concurrently. You can also control the number of jobs running concurrently using queues. Refer to Controlling Production , to learn more ways of controlling job execution.
To change an agents job limit:
Step 1 From the Navigator pane, select Administration>Connections to display the Connections pane with the licensed computers.
Step 2 Double-click the agent to edit or select the agent and click the Edit button on the TES toolbar to display the agent’s connection definition.
Step 3 Click the General tab if it is not showing.
Step 4 In the Job Limit field on the General tab, change the job limit to the desired value. See your agent-related documentation on setting the job limit.
Step 1 On the agent machine, click the Windows Start button and then select Programs>Tidal Software>Tidal Service Manager to display the Tidal Service Manager .
Step 2 In the Service drop-down list, select the agent you wish to check so that it displays in the Service field.
Step 3 At the bottom of the Tidal Service Manager, the status of the selected service displays.
You can disable an agent if you do not want it to run jobs submitted by TES. If a job tries to run on a disabled agent, its status changes to Agent Disabled .
To enable or disable an agent:
Step 1 From the Navigator pane, select Administration>Connections to display t he Connections pane.
Step 2 Double-click the agent to edit or select the agent and click the Edit button on the TES toolbar to display the agent’s connection definition .
Step 3 Do one of the following:
– To enable the agent, select the Enabled option.
– To disable the agent, clear the Enabled option.
Step 1 Click the Windows Start button and then select Programs>Tidal Software>Tidal Service Manager .
Step 2 Select the correct agent if it is not displayed in the Service field and click the Start button. The light will turn green when the agent starts.
Note The Agent for Unix does not use the Tidal Service Manager so the command line is used to start, stop and check the status of the agent. Use the following commands:
To start: ./tagent <agent name> start
To stop: ./tagent <agent name> stop
To check status: ./tagent <agent name> status
Step 1 Click the Windows Start button and then select Programs>Tidal Software>Tidal Service Manager .
Step 2 Select the correct agent if it is not displayed in the Service field and click the Stop button. The light will turn red when the agent stops.
You can check the status, start, and stop the client manager manually from the Tidal Service Manager or from the command line.
The Unix Client Manager does not use the Tidal Service Manager so the command line is used to check the status of Client Manager. From the command line type:
Step 1 On the machine with the master installation, click the Windows Start button and then select Programs>Tidal Software>Tidal Service Manager to display the Tidal Service Manager .
Step 2 Verify that the Client Manager displays in the Service field.
The Client Manager status displays at the bottom of the Tidal Service Manager.
The Unix Client Manager does not use the Tidal Service Manager so the command line is used to start Client Manager. From the command line of the master machine type:
Step 1 On the machine with the Client Manager installation, click the Windows Start button and then select Programs>Tidal Software>Tidal Service Manager to display the Tidal Service Manager.
Step 2 Verify that Client Manager displays in the Service field.
Before using TES on a regular basis, you should spend some time in the System Configuration dialog. By tailoring TES’s configuration to your needs, you will receive greater benefits from using the product.
You can configure the following options:
Select Activities>System Configuration from the menu bar of the Tidal Web client to display the System Configuration dialog.
The Master tab configures actions managed by the master. This tab contains the following elements:
Note When you change the Future Days to Include in Schedule value, the new value will not take effect until the production schedule is compiled. Compilation will take place at midnight, by default.
Note By default, alerts are kept for seven days. Alerts that are older than the Operator Alert Retention value are purged daily.
TES stores the passwords in encrypted form within its own database. At no time is an unencrypted password echoed to the screen or made otherwise accessible to any user. Passwords are also encrypted when passed from a master to an agent.
TES stores the passwords using 64-bit block cipher encryption within its own database. At no time is an unencrypted password echoed to the screen or made otherwise accessible to any user. Passwords are also encrypted when passed from a master to an agent.
Note The master will log any errors when purge is performed automatically.
When this option is not selected, TES will not automatically purge your database of old information history.
Note If the production day offset is modified, you must recompile the current and future production schedule for the changes to take effect. If a negative offset is specified, the master should be restarted and then the current and future production schedules must be recompiled.
Displays default settings for job definitions. The Defaults tab also configures whether job events, system events, actions, variables and calendars will default to public availability.
This tab contains the following elements:
– Run Anyway – Run another job instance even if the previous instance is still running.
– Skip – Do not run another job instance if the previous instance is running.
– Defer until Normal – Run another job instance only if the current job instance completes with a Normal status.
– Defer until Complete – Run another job instance only after the current job instance completes.
– Estimated Duration – The estimated duration for the command or executable as specified in the job definition. If the job has run more than once with the same command or executable, the estimated duration is the historical average of the job's previous run times. You can also manually set the estimated duration time of a job in its definition.
– Maximum Duration – The maximum duration for the command or executable as specified in the job definition.
– Run Anyway – Run the job anyway.
– Defer – Wait and run the job after the connection outage has ended.
– Discard – Does not save the job output. (Default)
– Append – Saves the complete output from each job instance, adding the output to the previous job instance’s output.
– Replace – Saves the complete output from each job instance, overwriting the previous job instance’s output.
The Mail tab of the System Configuration dialog displays email settings. TES uses actions to send email to users about job scheduling information.
Note For more information about using email with TES, see Actions and Alerts and your TES Installation & Configuration Guide.
This tab contains the following elements:
– None – No mail system is selected.
– Internet Mail SMTP – Simple Mail Transfer Protocol.
The Logging tab configures the length of time to keep audit and error messages. You can also choose to suppress messages from a specific source. More information on diagnostic logging is available in Troubleshooting . For more information about logging and log messages, see Monitoring Production.
This tab contains the following elements:
– Master – Displays audit messages that originate from the master.
– Client – Displays audit messages that originate from all Tidal Web clients connected to the master.
– Agent Manager – Displays audit messages that originate from licensed agents that run jobs. The Agent Manager: CQD category displays messages dealing with the underlying agent communications protocol.
– Fault Tolerance – Displays audit messages from the Fault Monitor machine.
– Dependency Manager – Displays messages about when dependencies for jobs and job groups are met.
– Job Manager – Displays messages about the status of jobs.
– Action Manager – Displays messages about all configured actions.
– Queue Manager – Displays messages about queue activity.
– Agent Messenger: CQD – Displays messages regarding the agent communications protocol, CQD. The Agent Manager category displays other messages originating from licensed agents.
Note Because of the volume of CQD diagnostic messages, you can clear the Agent Messenger: CQD source for messages while still gathering information regarding your agent(s) from the Agent Manager source.
Often the error messages displayed in the Tidal Web client that are generated by a problem, provide an indication of the source of the problem revealing which component should be monitored. If no source is indicated in the error message, check the messages in the system log for clues to the source of the problem. Once the source of the problem is identified, you can enable diagnostic logging for that system component. Be careful when using the diagnostic logging function as logging messages can consume a large amount of disk space very quickly. Carefully monitor the size of the log file being created as excessive logging consumes system resources as well as disk space. Try to repeat the scenario that produced the problem, so system activity can be recorded for Technical Services to interpret. Once the problem occurs again, contact Technical Services and send them the logging file.
If you are enabling diagnostics before contacting Technical Services, start at the Info level and Technical Services will provide additional instructions after receiving the diagnostic files.
The following components are monitored:
Each component has a drop-down list with seven levels of progressively more detailed logging. Each level includes the messages of the previous levels of logging. The levels of logging are:
Lists all the audit messages TES can issue. All audit messages can be viewed from the Logs console view. From this tab, you can include or exclude audit messages for TES to record.
Job audit messages can be viewed by individual job from the Job Details dialog for that job (accessed from the Job Activity pane). The first audit message listed (with the 1000 ID number) is blank because it is available for creating a custom audit message.
This tab contains the following elements:
Double-click the message to display the Audit Message dialog.
– Exclude Selected Messages – The selected audit messages will be issued.
– Exclude All Messages – None of the audit messages listed on this tab will be issued.
– Include Selected Messages – The selected audit messages listed on this tab will be issued.
– Include All Messages – All of the audit messages listed on this tab will be issued.
– Log Selected As Windows Event(s) – The selected audit messages listed on this tab will be logged as Windows Events.
– Log All As Windows Events – All audit messages listed on this tab will be logged as Windows Events.
– No Windows Event Logging For Selected – The selected audit messages listed on this tab will not have Windows Event logging.
– No Windows Event Logging – All audit messages will not have Windows Event logging.
For more information about audit messages, see Monitoring Production.
Lists all the error messages TES can issue. Error messages can be viewed from the Logs pane . The first error message listed (with the 2000 ID number) is blank because it is available for creating a custom error message. Here you can instruct TES to exclude specific error messages.
(For more information about error messages, see Monitoring Production.)
This tab contains the following elements:
Double-click the message to display the Error Message dialog.
– Exclude Selected Messages – The selected error messages will be issued.
– Exclude All Messages – None of the audit error listed on this tab will be issued.
– Include Selected Messages – The selected error messages listed on this tab will be issued.
– Include All Messages – All of the error messages listed on this tab will be issued.
– Log Selected As Windows Event(s) – The selected error messages listed on this tab will be logged as Windows Events.
– Log All As Windows Events – All error messages listed on this tab will be logged as Windows Events.
– No Windows Event Logging For Selected – The selected error messages listed on this tab will not have Windows Event logging.
– No Windows Event Logging – All error messages will not have Windows Event logging.
Lists the job statuses and lets you change the job status order used for sorting jobs and job groups by status in the Job Activity pane .
This tab contains the following elements:
The sort order defaults to alphabetical, but you may want to change that if there is a sort order that makes more sense to you. For example, jobs always enter the Launched status before they enter the Active status. Thus, you may want to place Active after Launched in this list.
The Fault Tolerance tab of the System Configuration dialog allows you to turn on fault tolerance and configure the settings.
Note The Fault Tolerance tab is not displayed if you are not licensed for fault tolerance.
This tab contains the following elements:
The following fields do not display unless the Enable Failover option is selected.
– Machine Name (Backup Master) – The name of the machine the backup master is on.
– Backup-To-Master Port – The port number for the backup master to primary master connection.
– Machine Name (Fault Monitor) – The name of the machine the fault monitor is on.
– Fault Monitor Master Port – The port number for the fault monitor to master connection.
– Fault Monitor Client Port – The port number for the fault monitor to Client Manager connection.
The Timezone tab of the System Configuration dialog allows you to define timezones where target application environments are based. This allows you to schedule a job or job group across a different timezone. See also, Working with timezones.
This tab contains the following elements:
Note It is not recommended to use the Agent Time Zone option with the Production Day Offset option unless you thoroughly understand the scheduling complexities. Using the master time zone means that the agents reference the same time zone when launching jobs but using the agent’s time zone means that each agent launches jobs according to the time zone that the agent resides in. Due to the time zone differences, from the agents’ perspective a 11 am job launches correctly but from the master’s perspective the 11 am job may launch at noon, 1 pm, 2 pm, etc.
Adding a production day offset to a system network spread over a large geographic area encompassing multiple time zones vastly complicates scheduling. A production day offset may entail that jobs will be launching on different days from the master’s perspective. Tidal Software’s consulting services can help resolve complicated scheduling issues.
To configure the Master timezone for a job:
Step 1 From the Activity menu, select System Configuration to display the System Configuration dialog.
Step 2 Click the Timezone tab.
Step 3 Click Add or Edit to display the Timezone for Job Definition dialog.
Step 4 In the Name field, enter a unique name to represent job timezone.
Step 5 From the Timezone list, select the timezone ID.
Step 6 The following fields pre-populate depending on the Timezone list selection:
– Timezone Full Name – Java build-in timezone long name.
– Master Timezone Offset – The time differences between Master timezone and selected Java timezone.
–
UTC/GMT Timezone Offset
– The time differences between standard
UTC/GMT and selected Java timezone.
– Current in DST Timezone Period – Checked if current in Daylight Saving Time (DST) period for this selected timezone.
– DST Time Differences – The amount of time to be added to selected timezone if it is in DST period.
The Other tab controls how schedules are compiled, sets time zones, length of alert retention, offsets and job carryover.
This tab contains the following elements: