Oracle® Argus Mart Installation Guide Release 1.0 E38590-01 |
|
|
PDF · Mobi · ePub |
Before running the Initial ETL (Extract, Transform, and Load) process, you need to configure the AM Common Profile Switches to have control over the data that you want to transfer from the Argus Safety database to the AM database. These Common Profile Switches are configured using the Argus Safety Console.
This sections explains these Common Profile Switches along with the step-by-step procedure to configure these profile switches using the Argus Safety Console.
The following figure depicts your progress in the complete installation process:
To configure the Common Profile Switches using the Argus Safety Console, execute the following steps:
Log on to the Argus Safety Console and navigate to System Configuration > System Management (Common Profile Switches), as shown in the following figure:
This displays the Common Profile Screen with the list of configuration options in the left pane, as depicted in the following figure:
Click Argus Mart. This displays the Modify Argus Mart Screen with the list of AM Common Profile Switches that you need to configure, in the right pane, as depicted in the following figure:
There are 12 AM Common Profile Switches that you can configure using this screen. See Table 6-1 for description about these profile switches along with their type (Global or Enterprise-specific).
The Global switches are visible only if you are logged in from a default enterprise. If you are logged in from a non-default enterprise, only the enterprise-specific switches are visible in the list of Common Profile Switches, as depicted in the following figure:
Enter the required input in the text box (or select the radio buttons in case of the ENABLE SM PROCESSING profile switch) adjacent to the name of each profile switch and click Save.
Note:
The Global Switches, as mentioned in the table below, impact all enterprises configured for AM whereas the Enterprise specific Switches impact the enterprise to which user is logged in, to access the Argus Safety console.The following table lists the Common Profile Switches that you can configure for AM, their type, and their description:
Table 6-1 Common Profile Switches for AM
Profile Switch | Type | Description |
---|---|---|
ENABLE SM PROCESSING |
Global switch |
This switch is used to enable or disable SM Processing for AM. Yes - Enable SM Processing for Argus Mart. No - Disable SM Processing for Argus Mart. The value for this switch cannot be changed once initial ETL has been executed. |
REVISIONS TO PROCESS |
Global switch |
This switch refers to the Configuration Flag to process maximum number of revisions in an incremental ETL run. Setting the value as 0 for this switch represents that the Configuration Flag is not set. |
FIRST HUMAN LANGUAGE |
Enterprise specific switch |
This switch refers to first human language for derived decoded items. This value should not be changed after data mart is initialized. For information on the First Human Language profile switch columns in SM Tables, refer to the ETL Mapping document. |
SECOND HUMAN LANGUAGE |
Enterprise specific switch |
This switch refers to second human language for derived decoded items. This value should not be changed after data mart is initialized. For information on the Second Human Language profile switch columns in SM Tables, refer to the ETL Mapping document. |
CUSTOM DATASHEET FOR LISTEDNESS |
Enterprise specific switch |
This switch refers to the specific datasheet value to be used for the SM_EVENT_PRODUCT.LISTEDNESS_CDS_VE column. This value should not be changed after data mart is initialized. |
SMQ/CMQ FOR FATAL TERMS |
Enterprise specific switch |
This switch refers to the specific SMQ/CMQ to be used for determining fatal terms for the FATAL_YN_DV column. This value should not be changed after data mart is initialized. |
CUSTOM ROUTINE BEFORE STAGE TABLES POPULATION |
Global switch |
This switch refers to the full path of the custom routine to be executed before population of the Signal Staging Tables. If this routine fails or is not found, the ETL is not run and an error message is displayed. |
CUSTOM ROUTINE BEFORE REPORTING TABLES POPULATION |
Global switch |
This switch refers to the full path of the custom routine to be executed before population of Signal Reporting Tables. If this routine fails or is not found, the ETL is not run and an error message is displayed. |
CUSTOM ROUTINE AFTER REPORTING TABLES POPULATION |
Global switch |
This switch refers to the full path of the custom routine to be executed after population of Signal Reporting Tables. If this routine fails or is not found, the ETL is not run and an error message is displayed. |
CUSTOM ROUTINE BEFORE SIGNAL HELPER TABLES POPULATION |
Global switch |
This switch refers to the full path of the custom routine to be executed before population of Signal Helper Tables. If this routine fails or is not found, the ETL is not run and an error message is displayed. |
CUSTOM ROUTINE AFTER SIGNAL HELPER TABLES POPULATION |
Global switch |
This switch refers to the full path of the custom routine to be executed after population of Signal Helper Tables. If this routine fails or is not found, the ETL is not run and an error message is displayed. |
CUSTOM ROUTINE AFTER ETL |
Global switch |
This switch refers to the full path of the custom routine to be executed after Initial/Incremental ETL (post ETL commit). If this routine fails or is not found, the ETL is not run and an error message is displayed. |