Cisco Tidal Enterprise Scheduler 6.2 Installation Guide

Installation Prerequisites

---

This chapter discusses the system requirements, user requirements, installation prerequisites and the supported databases for the various components of Cisco Tidal Enterprise Scheduler (TES) version 6.2.0.

Minimum System Requirements

The following table contains the minimum system requirements for installing and running TES. The specified quantities of CPU, memory and disk space must be available for exclusive use by TES. Use additional RAM and disk space as necessary for your particular environment.

Table 1-1 System Requirements

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.

Note Although the minimum memory required is 4GB for PCs running the Web Client, additional memory helps with better performance. At least 2GB of free memory must be available for the browser.

Note When installing a 64-bit master for use with an Oracle database, the installer requires that 32-bit oracle client software in order to connect to the Oracle database. After installing, the master does not require the 32-bit client software to run.

Browser Compatibility

Table 1-2 Browser Compatibility

Note For Client Manager installation instructions and compatibility matrix, refer to Installing Client Manager.

User Security Requirements

The security requirements for TES vary according to the task the user account needs to accomplish. The user account that installs the components of TES requires different security rights than an account that runs TES as a service. The user account that will operate TES has its own security needs. The following points and Table 1-3 illustrate security rights differences between the various TES components.

• If you are planning to use an Oracle or Microsoft SQL database, your database administrator will be required during installation of the Client Manger and the master. Passwords to the database and connections to the database are necessary for installing the product. Agent and master installations also require a Windows administrator to provide passwords during installation.
• The Client Manager and agent should be installed under the same user name with equivalent capabilities.
• When installing TES Agent for Unix, you must be able to log in as root.
• The Tidal Agent for Unix provides another layer of security by having its single java process run as the agent owner with the same security rights as its owner. By default, the agent does not have access to all of the dependent files, scripts and environment variables it may need. A Unix job cannot complete successfully unless you ensure that the agent has the proper access rights to all of the files needed during the processing of a job.
• The Windows components require access to COM objects. Verify that the user doing the installation can access COM objects or an access violation error will occur when you attempt installation. If necessary, the procedure to verify and provide access to COM objects is explained in Java Path Mismatch in the Troubleshooting chapter.
• LDAP users can be imported into TES for improving user audit trails. These imported users inherit security from multiple LDAP groups. Imported LDAP user information is stored into a user definition that includes email, telephone, etc. Imported LDAP users are allowed to be owners of scheduling constructs such as jobs if their security permits it. User definitions must be migrated to LDAP groups.
• The Administration group in 6.2 has three distinct entries for adding users, “Interactive Users”, “Runtime Users” and “LDAP Groups”. TES 6.0 allows for the setup of a user that authenticates against Active Directory/LDAP. TES also supports AD/LDAP only users.
• At login, user credentials are validated against Active Directory/LDAP. Once authenticated, TES obtains the users AD/LDAP groups and other information such and phone number and email.
• Once login has completed, a record is established in TES to represent the Active Directory/LDAP only user if not already present and only if the user belongs to an Active Directory/LDAP group defined in TES. All user activity logging is then done against this new user record allowing for correct auditing and reporting.
• Active Directory/LDAP only users will be allowed to create and own jobs and other objects if their security permissions permit.
• TES LDAP groups are supported by the creation of groups within the TES application.
• Security policies can be defined and specialized by application administrators.
• Each group within TES can be assigned one security policy.
• The security capabilities of a user are based upon the summation of the security policies defined for each of the groups that the user is a member of and any security policy directly assigned to the user. The latter is only available for users created within TES not imported from AD/LDAP.
• Workgroups are also available within the TES application. These workgroups can be used to own related objects. Users and groups can be made a member of one or more workgroups. Workgroup security allows for additional security policies to be applied to scheduling constructs (jobs, view, alerts, etc.) owned by the workgroup for a particular user associated with the workgroup.
• When a user or a group is made a member of a workgroup then additional security policies can be applied to this relationship. The users total security capabilities will then be a summation of their user applied security policy, the security policy associated with each of the groups they are a member of, and the security policies contained in the relationship between the user or group and the workgroups they are a member of (in the context of objects contained in that workgroup).

Table 1-3 Rights Required for Installation and Usage of Scheduler Components

	Installation Rights	Service Rights	User Rights
Windows Master	Local Administrator Able to access COM objects	Local Administrator or Local System Logon as a service Able to access COM objects	Local Administrator or Local System
Unix Master	Must be installed under a user created by root Access rights to JVM	Access rights to JVM	User account must be created by root Access rights to JVM
Windows Agent	Local Administrator Able to access COM objects	Local System or if running under Domain\User must have local administrator rights including: Logon as a batch job Logon as a service Act as part of the operating system Replace a process level token Able to access COM objects On machines running Windows 2003, you also need the following privileges: Bypass traverse checking Adjust memory quotas for the process User must be root or created by root Access rights to JVM	Local System or if running under Domain\User must have local administrator rights including: Logon as a batch job Logon as a service Act as part of the operating system Replace a process level token User must be root or created by root Access rights to JVM Ability to change to the runtime user
Unix Agent	Logon as root	N/A	N/A
Client Manager	Local Administrator Able to access COM objects	N/A	General user rights

Installation Requirements

• Determine which components you are going to install and where you are going to install them before you install TES. Because the InstallShield Wizard/Scheduler Setup requires information about the location of masters, Client Managers and agents, decide beforehand where they will be installed. Obtain machine names, host names, port numbers and IP addresses before beginning the installation.
• Ensure that each computer used for TES can communicate with the other machines on the network. If you cannot ping to and from each component machine, TES cannot function properly. Network conditions affect the operation of TES.
• Ensure that you are logged on with an account that has Administrator privileges.
• Download the latest set of hotfixes for Tidal Enterprise Scheduler from cisco.com.
• Review any supplementary documentation provided with your software such as the release notes or Read Before Installing. Last-minute instructions may be contained in these documents.
• If you are upgrading TES, install the program in the same directory in which the previous version was installed to keep your data intact.
• Exit all Windows programs before running any installation.
• Contact Support if you have any questions.

Supported Databases

Before installing TES you should already have database software installed on your machine.

The Master supports the following databases:

• MSSQL Server 2008 or SQL Server 2012 single or multi-instance: 128 MB Data, 32 MB Log
• Oracle 10g, 11g, 11gR2 (Oracle provided software for Scheduler client): 400MB Data, 300MB index, 200MB temp

---

Note TES does not support case-sensitive sort-ordered databases.

---

You need the following number of database access licenses:

• Each master should have access to up to 20 database client licenses to use as needed during processing

Client Manager supports the following databases:

• Derby (default)
• SQL server (external)
• Oracle 11g R2 (external)

Licensing

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.

Licensed Agents Tab

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:

• Agent – The machine name for the licensed agent.
• Serial – The serial number of the licensed agent.
• Floating – Specifies if the license is floating or not.
• Operating System – The operating system type of the licensed agent. Scheduler supports MPE/iX, MVS, z/OS, OS/400, Windows and Unix platforms.
• Expiration – The license’s expiration date. You may need to renew your license before the expiration date.
• Max Jobs – The maximum number of jobs that you can run on the agent concurrently. You can configure a lower value for the agent from the Connections pane, but this value cannot exceed your licensed value.
• Jobs – Displays the current count of jobs, tracking the number of jobs to enforce the license restriction on an agent as shown in the Max Jobs column.
• CPU – The number of CPUs on an agent machine. If the number of CPUs on a machine exceeds the authorized number, the master disables the agent connection and logs a licensing error. The licensing discrepancy must be resolved by contacting the Licensing Administrator for Tidal Software before the agent connection can be re-established.

Warning Restart the Client Manager after a new license has been loaded.

Licensing Procedure

Registering the license for TES is done from the Tidal Web client.

Note Before you start the licensing procedure, set the system queue to 0. Select Queues> System Queue, and set the value to 0. This will stop all jobs from launching. Wait until all running jobs have completed.

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.

For Windows:

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.

For Unix:

Enter tesm stop.

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.

Step 5 Restart the master:

• 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:

Step 1 Stop the master:

For Windows:

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.

For Unix:

Enter tesm stop.

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.

Step 4 Restart the master:

• 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.