Overview

Services Framework runs and maintains tasks that were created by using the Services Framework SDK.

Services Framework consists of the following components.
  • Engine
  • User interface
  • SDK

The purpose of the runtime engine is to manage and initiate tasks. The tasks are business-specific functions to help run the daily processing for a financial institution. Tasks are specific pieces of code, either purchased or customer-written, that do a function. The obtained task is added to the Services Framework runtime engine. It is then registered and configured by using the Services Framework user interface. When a task is configured, it is available for processing.

Services Framework can be deployed to one or more machines. Multiple machines provide workload handling and high availability. All instances share the message queues and database.

The following tasks are included with Services Framework and installed in its runtime engine. These tasks need only to be registered and configured before you can use them for processing.
  • Sample Task
    • Used to assist with writing tasks and how to use them.
    • Used to help you understand how tasks receive work and how the work relates to a unit of work artifact.
  • Activity Purge Task
    • Used to purge the activity records that reached their expired time.
  • Application Log Purge Task
    • Used to purge the application log records that reached their expired time.
  • Performance Monitor Purge Task
  • Usage Purge Task
    • Used to purge the usage records that reached a specified expiration time.
  • Inactive Users Task
    • Used to lock Control Center user accounts that are no longer active.
    • Used to remove Control Center user accounts that are no longer active.

Some Common Services components provide more Services Framework tasks. Refer to the documentation for each component for more information about the Services Framework tasks it provides.