Configuring the Archive Database
To use non-partitioned archiving, you must define the Archive database.
The following instructions provide a high level overview of the steps for creating the Archive database. For complete instructions, see the chapter, “Creating and Dropping Database Components” in Installing Software AG Products. The section, “Product Database Component Descriptions and Installation Requirements, describes specific details for each database provider.
To configure data archiving
1. Using Database Component Configurator, create the Archive database for the Process Audit schema.
a. In the Action fields, select the following values from the table below:
Field | Properties |
Action Type | Create |
Action Component | Archive |
Version | Latest |
b. In the Connection fields, define the connection to your Archive database, as follows in the table below.
Field | Properties |
RDBMS | Select the database provider. The Process Audit and Archive databases must be of the same type. |
URL | URL address |
User ID | Username to access the database. This must be a new user and have sufficient privileges to access both the source and target Process Audit database. |
Password | Password |
c. In the Create Database and Database User fields, define the database Administrator, as follows in the table below.
Field | Properties |
Admin ID | Add the Archive database administrator. |
Admin Password | Password for the Archive database administrator |
Database | Name of the Archive database, for example, wmProcessAuditArchive. |
d. Click Execute.
For detailed instructions on creating the Archive database, see the chapter, “Creating and Dropping Database Components” in Installing Software AG Products.
2. In the Database Administration console, assign the user the appropriate permissions for the tables in the Archive and Process Audit database.
3. Connect the Archive database to an Integration Server. For complete instructions on connecting to a database, see the section on configuring databases in webMethods Integration Server Administrator’s Guide.
4. Define a new JDBC connection pool alias settings.
a. In Integration Server Administrator, click Settings > JDBC Pools.
b. In Pool Alias Definitions, click Edit.
c. Add the URL, user ID and password to match the Connection settings defined with the Database Component Configurator and click Save Settings.
5. Define the JDBC pools for the Archive database.
a. In Integration Server Administrator, click Settings > JDBC Pools.
b. In Functional Alias Definitions, click Edit for Archiving.
c. In Associated Pool Alias, select the alias and click Save Settings.
d. Click Restart.
6. Configure the default archiving parameter in the OPERATION_PARAMETER table.
a. In Designer, run the pub.monitor.archive:setOperationParameters service.
b. Specify the input parameters as follows. pub.monitor.archive:setOperationParameters sets the values you specify in the OPERATION_PARAMETER table of the Archive database.
The following table lists these parameters.
Parameter | Entry |
PROCESS_SCHEMA | To archive data from the Process Audit Log tables, specify the following information for your database provider: Oracle: Process Audit Log database user SQL Server: Process Audit Log database name DB2: Process Audit Log schema name |
ISCORE_SCHEMA | To archive data from the IS Core Audit Log database, specify the following: Oracle: IS Core Audit Log database user SQL Server: IS Core Audit Log database name DB2: IS Core Audit Log schema name |
Note:
You can set additional parameters not listed in the table. For example, you can specify how many days of audit information to keep in the IS Core Audit Log and Process Audit Log schemas. For more information, see the setOperationParameters service in webMethods Monitor Built-In Services Reference.
7. Set database permissions to allow the Archive database user permission to select and delete data from the IS Core Audit Log tables, the Process Audit Log tables, or both, depending on the data you want to archive. To do so, execute the following SQL:
GRANT SELECT ANY TABLE, UPDATE ANY TABLE, DELETE ANY TABLE, INSERT ANY TABLE
Verify that you set permission for the Archive tables listed in
Archive Tables.