APIs for managing application and transaction mapping

You can use the following APIs to manage the application and transaction-to-cache mapping.

Note

LoadOne and LoadAll can work whether the application settings are stored in the file or in the database; the other APIs can only work when the settings are stored in the database. See Storing database connections in the database for how to store the settings in a database (instead of the default file).

Syntax

Description

/api/Application/LoadOne/{appName}

Loads the configuration of an application.

/api/Application/LoadAll

Loads the configuration of all applications.

/api/Application/Add

Adds an application and configuration.

/api/Application/Edit

Edits the configuration of an application.

/api/Application/Remove/{appName}

Removes an application and configuration.

/api/Application/AddTransactionMapping/{appName}/{transName}

Adds a transaction-to-cache mapping.

/api/Application/EditTransactionMapping/{appName}/{transName}

Edits a transaction-to-cache mapping.

/api/Application/RemoveTransactionMapping/{appName}/{transName}

Removes a transaction-to-cache mapping.