Page Comparison

 Image Added offers the possibility to output information to user-defined database tables. This means that several workflows may output information about the same batch to the same table, which makes it possible to trace batches/UDRs between workflows. To increase this traceability, it is highly recommended to add fields to the UDRs, to make it possible to identify their origin. Useful values may be:

The audit table column types are defined in an Audit profile configuration.

...

To create a new Audit profile configuration, click the New Configuration button in the upper left part in the Desktop, and then select Audit Profile from the menu.

...

The contents of the menus in the menu bar may change depending on which configuration type that has been opened. The Audit profile uses the standard menu items and buttons that are visible for all configurations, and these are described in 2.1 Menus and Buttons.

...

Setting	Description
Database	This is the database that the agent will connect and send data to. Click the Browse... button to get a list of all the database profiles that are available. For further information see 8.5 6 Database Profile. Note title Note! For performance reasons, Audit information is logged directly from an EC to the database. If an external EC is unable to connect to the database, a "Workflow performance warning" is logged in System Log. If this warning appears, the firewall might need to be reconfigured to allow the EC to communicate directly with the database. The Audit functionality is supported for use with the following databases: Oracle TimesTen Derby SQL Server PostgreSQL SAP HANA
Refresh	Select Refresh to reload the meta data metadata for the tables residing in the selected database.
Use Default Database Schema	Check this to use the default database schema that was added in the Usernamefield of the Default Connection Setup in the Database profile configuration. When using the default database schema the names of the audit tables listed in Table will appear without schema prefix. For more details on how to add a default database schema, see 8.5 6 Database Profile. Note title Note! This is not applicable for to all database types. Use Default Database Schema is only available for selection when accessing Oracle or TimesTen databases.
Table	A list of selected audit tables. For further information about adding and editing tables, see the section below, Adding and Editing a Table Mapping.

...

From the Add and Edit Audit Table Attributes dialogs, the existing table columns are mapped to valid types in Image Added.

Add Audit Table Attributes

...

...

The output on each route is to be logged in an audit table, including information on canceled batches. An entry in the table is made for each batch , and for each route. Hence two entries per batch.

...

1. Design the tables:

   • One column (of type NUMBER) must be reserved for the transaction transaction handling. This column should be indexed in order to achieve the best performance. The contents will be of low cardinality and could therefore be compressed if supported.

   • Consider which column/columns contain tag information, that is, the key. A key may consist of one or several columns.
      

2. Create an Audit profile. For further information, see the section below, Adding the Table Mapping.
    

3. Map parameters in the Workflow Preferences Audit tab to the Audit profile. For further information, see the section below, Workflow Properties - Audit Tab.
    

4. Design APL code to populate the tables. For further information, see the section below, Populating Audit Tables.

...

In the Audit profile configuration, the column types are configured. To create a new Audit profile configuration, click the New Configuration button in the upper left part of the Desktop the Desktop window, and then select Audit Profile from the menu. Select the database in which the table(s) resideresides, then select Add.

Anchor
Adding the Table Mapping Adding the Table Mapping

Adding the Table Mapping

From the Add and Edit Audit Table Attributes dialogs, the existing table columns are mapped to Image Added valid types.

The Audit profile

The data to insert , will be put in the UDRs column. Setting it to type Counter, makes it possible to use the auditAdd function to increment the corresponding column value. If Value is used, the auditSet function can be used to assign a value.

...

Workflow Properties - The Audit tab

The COMPLETE, INVALID, and PARTIALS columns in the the Audit table are populated by using the APL audit functions. COLLECTION_DATE and FILENAME are populated by the workflow MIM values.  The CANCELED column name might be mapped directly to an existing MIM value or populated by the APL audit functions using the Analysis Agent.

...

Counter Increment

...

// Define counters
int complete = 0;
int partials = 0;
int invalid = 0;

//Publish a new MIM
mimPublish(trailer, "My Trailer",string);

consume {
    // Check if the UDR is of type complete
    if(input.causeForOutput == 0){
        // Increment complete counter
        complete = complete + 1;
        // Increment value of column COMPLETE
        auditAdd( "Default.PRF_AUDIT","MZADMIN.MZ_AUDIT","COMPLETE",1 ); 
        // Route UDR on outgoing route "COMPLETE"
        udrRoute(input, "COMPLETE");
    }
    // Check if the UDR is of type partial
    else if(input.causeForOutput == 1 ||input.causeForOutput == 2){
        // Increment partial counter
        partials = partials + 1;  
        // Increment value of column PARTIAL
        auditAdd( "Default.PRF_AUDIT","MZADMIN.MZ_AUDIT","PARTIAL",1 ); 
        // Route UDR on outgoing route "PARTIALS"
        udrRoute(input, "PARTIALS");
    }
    else{
        // Increment invalid counter
        invalid = invalid + 1;
        // Set the value of column INVALID
        auditSet( "Default.PRF_AUDIT","MZADMIN.MZ_AUDIT","INVALID",invalid );
    }
    
}