Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Content Management Service
  4. Data Integration Service
  5. Data Integration Service Architecture
  6. Data Integration Service Management
  7. Data Integration Service Grid
  8. Data Integration Service Applications
  9. Metadata Manager Service
  10. Model Repository Service
  11. PowerCenter Integration Service
  12. PowerCenter Integration Service Architecture
  13. High Availability for the PowerCenter Integration Service
  14. PowerCenter Repository Service
  15. PowerCenter Repository Management
  16. PowerExchange Listener Service
  17. PowerExchange Logger Service
  18. Reporting Service
  19. Reporting and Dashboards Service
  20. SAP BW Service
  21. Search Service
  22. System Services
  23. Test Data Manager Service
  24. Web Services Hub
  25. Application Service Upgrade
  26. Application Service Databases
  27. Connecting to Databases from Windows
  28. Connecting to Databases from UNIX
  29. Updating the DynamicSections Parameter of a DB2 Database

Scheduler Service Properties

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.