Transaction Manager

Overview

The Transaction Manager application provides a solution to handle transaction processing across multiple queues and priorities with typical queue management features such as throughput handling, parallel execution, batch processing. If you have work items to be processed, or need to manage your resource utilisation the Transaction Manager can help you.

Below are some use-case examples.  Details about these use-cases are available as part of the documentation provided in the download package.

  • Maintain a continuous backlog of user tasks
  • Cancel a scheduled transaction
  • Schedule an item for future execution
  • Configure a recurring schedule
  • Priortise the order my transactions are processed
  • Limit the time period my transactions are processed
  • Retry X times before passing to a system administrator

Key Features & Functionality

  • Multi-queue processing
  • Throughput and scaling of individual queues
  • Resource utilisation management
  • Parallel execution across process engines
  • Microbatch processing for high-throughput use cases
Anonymous
Parents
  • Hi,

    has anyone used this application with the Kafka tools plug-in? I looked through the documentation and the application objects in Appian but couldn't find where the Kafka events would be stored and how I can retrieve them from my application.

    Thanks in advance

  • Hi!

    The events you consume from Kafka will be stored in "tm_job_transaction" table in BBDD once you be able to suscribe to your topics. After this implementation, you should create Job Types in Transaction Manager Site, which each Job Type is related to each Kafka Topic, so TM will be triggered, in 60-seconds batches (configurable), several instances of the Process(s) Model(s) (via Job Type in TM Site) who manages the event and its information.

    Hope this helps you!

Comment
  • Hi!

    The events you consume from Kafka will be stored in "tm_job_transaction" table in BBDD once you be able to suscribe to your topics. After this implementation, you should create Job Types in Transaction Manager Site, which each Job Type is related to each Kafka Topic, so TM will be triggered, in 60-seconds batches (configurable), several instances of the Process(s) Model(s) (via Job Type in TM Site) who manages the event and its information.

    Hope this helps you!

Children
No Data