Scheduler Service
The Scheduler Service manages schedules for profiles, scorecards, deployed mappings, and deployed workflows.
Use schedules to run deployed mappings and workflows at a specified time. You can schedule the objects to run one time, or on an interval. Enable the Scheduler Service to create, manage, and run schedules.
The Scheduler Service is associated with a Model Repository Service. The Model repository stores metadata for the schedules that users configure. Both the Model Repository Service and the Scheduler Service must be available for scheduled objects to run.
The Scheduler Service is highly available. High availability enables the Service Manager and the Scheduler Service to react to network failures and failures of the Scheduler Service. The Scheduler Service has the restart and failover high availability feature. If a Scheduler Service becomes unavailable, the Service Manager can restart the service on the same node or on a back-up node.
Before You Enable the Scheduler Service
Before you enable the Scheduler Service, complete the prerequisite tasks for the service.
Before you enable the Scheduler Service, complete the following tasks:
- •If the domain uses Kerberos authentication and you set the service principal level at the process level, create a keytab file for the service. For more information about creating the service principal names and keytab files, see the Informatica Security Guide.
- •Configure a Model repository for the service.
Scheduler Service Properties
You can configure general properties, logging options, and a Model Repository Service for the Scheduler Service. To configure the Scheduler Service properties, select the service in the Domain Navigator and click Edit in the Properties view. You can change the properties while the service is running, but you must recycle the service for the modifications to take effect.
General Properties
The following table describes the general properties for the service:
Property | Description |
|---|
Name | Name of the service. You cannot change the name of the Scheduler Service. |
Description | Description of the service. The description cannot exceed 765 characters. |
Node | Node on which the service runs. |
Backup Nodes | Nodes on which the service can run if the primary node is unavailable. |
Logging Options
Configure the Logging Level property to determine the level of error messages that are written to the Scheduler Service log.
The following table describes the logging level properties for the service:
Property | Description |
|---|
Logging Level | Determines the default severity level for the service logs. Choose one of the following options: - - Fatal. Writes FATAL messages to the log. FATAL messages include nonrecoverable system failures that cause the service to shut down or become unavailable.
- - Error. Writes FATAL and ERROR code messages to the log. ERROR messages include connection failures, failures to save or retrieve metadata, service errors.
- - Warning. Writes FATAL, WARNING, and ERROR messages to the log. WARNING errors include recoverable system failures or warnings.
- - Info. Writes FATAL, INFO, WARNING, and ERROR messages to the log. INFO messages include system and service change messages.
- - Trace. Write FATAL, TRACE, INFO, WARNING, and ERROR code messages to the log. TRACE messages log user request failures.
- - Debug. Write FATAL, DEBUG, TRACE, INFO, WARNING, and ERROR messages to the log. DEBUG messages are user request logs.
|
Model Repository Service Options
Configure a Model repository to store information about the schedules. The Model Repository Service must be available for the Scheduler Service to run scheduled objects.
If the Model repository is integrated with a version control system, synchronize the Model repository before you associate it with the Scheduler Service.
The following table describes the Model repository options for the service:
Property | Description |
|---|
Model Repository Service | Model Repository Service associated with the Scheduler Service. |
Username | User name of an administrator user in the Informatica domain. Not available for a domain with Kerberos authentication. |
Password | Password of the administrator user in the Informatica domain. Not available for a domain with Kerberos authentication. |
Security Domain | LDAP security domain for the user who manages the Scheduler Service. The security domain field does not appear for users with Native or Kerberos authentication. |
Storage Properties
Configure a temporary file location when you configure the Scheduler Service to run on multiple nodes. Use the temporary file location to store parameter files for deployed mappings and workflows. The file location must be a directory that all of the nodes can access.
The following table describes the Temporary File Location property:
Property | Description |
|---|
Temporary File Location | Path to the directory where parameter files are read from and written to. |
Scheduler Service Process Properties
When the Scheduler Service is configured to run on primary and back-up nodes, a service process is enabled on each node. Only a single process runs at any given time, and the other processes maintain standby status. You can configure the service process properties differently for each node.
To configure the Scheduler Service process properties, select the service in the Domain Navigator and click the Processes view. You can change the properties while the service is running, but you must restart the service process for the changed properties to take effect.
Security Properties
When you set the HTTP protocol type for the Scheduler Service to HTTPS or both, you enable the Transport Layer Security (TLS) protocol for the service. Depending on the HTTP protocol type of the service, you define the HTTP port, the HTTPS port, or both ports for the service process.
The following table describes the Scheduler Service security properties:
Property | Description |
|---|
HTTP Port | Unique HTTP port number for the Scheduler Service process when the service uses the HTTP protocol. Default is 6211. |
HTTPS Port | Unique HTTPS port number for the Scheduler Service process when the service uses the HTTPS protocol. When you set an HTTPS port number, you must also define the keystore file that contains the required keys and certificates. |
HTTP Configuration Options
Configure the HTTP options when the Scheduler Service uses the HTTPS protocol.
The following table describes the HTTP configuration options:
Property | Description |
|---|
Keystore File | Path and file name of the keystore file that contains the keys and certificates. Required if you use HTTPS connections for the service. You can create a keystore file with a keytool. Keytool is a utility that generates and stores private or public key pairs and associated certificates in a keystore file. You can use the self-signed certificate or use a certificate signed by a certificate authority. |
Keystore Password | Password for the keystore file. |
Truststore File | Path and file name of the truststore file that contains authentication certificates trusted by the service. |
Truststore Password | Password for the keystore file. |
SSL Protocol | Secure Sockets Layer protocol to use. Default is TLS. |
Advanced Options
You can configure maximum heap size and JVM command line options for the Scheduler Service.
The following table describes the advanced options:
Property | Description |
|---|
Maximum Heap Size | Amount of RAM allocated to the Java Virtual Machine (JVM) that runs the service process. Use this property to increase the performance. Append one of the following letters to the value to specify the units: - - b for bytes.
- - k for kilobytes.
- - m for megabytes.
- - g for gigabytes.
|
JVM Command Line Options | Java Virtual Machine (JVM) command line options to run Java-based programs. When you configure the JVM options, you must set the Java SDK classpath, Java SDK minimum memory, and Java SDK maximum memory properties. You must set the following JVM command line options: - - Xmx. Maximum heap size. Default value is 640 m.
- - Xms. Minimum heap size. Default value is 256 m.
- - MaxPermSize. Maximum permanent generation size. Default is 192 m.
- - Dfile.encoding. File encoding. Default is UTF-8.
|
Environment Variables
You can configure environment variables for the Scheduler Service process.
The following table describes the environment variables:
Property | Description |
|---|
Environment Variable | Enter a name and a value for the environment variable. |
Enabling, Disabling, and Recycling the Scheduler Service
You can enable, disable, and recycle the Scheduler Service from the Administrator tool.
By default, the Scheduler Service is disabled. Enable the Scheduler Service when you want to manage schedules or run scheduled objects. When you enable the Scheduler Service, a service process starts on the node designated to run the service. The service is available to schedule and run objects.
You might disable the Scheduler Service for maintenance, or recycle the service if you change a property.
When you recycle or disable a Scheduler Service, you must choose a mode to recycle or disable it in. You can choose one of the following modes:
- •Complete. Wait for all subtasks to complete.
- •Stop. Wait up to 30 seconds for all subtasks to complete.
- •Abort. Stop all processes immediately.
Optionally, you can choose to specify whether the action is planned or unplanned, and enter comments about the action. If you complete these options, then the information appears in the service Events and Command History panels in the Domain view on the Manage tab.
To enable the service, select the service in the Domain Navigator and click Enable the Service.
To disable the service, select the service in the Domain Navigator and click Disable the Service.
To recycle the service, select the service in the Domain Navigator and click Recycle the Service. When you recycle the service, the Service Manager restarts the service. You must recycle the Scheduler Service whenever you change a property for the service.