f. Similarly, view the Insert Audit Records step information. Refer to the following screens. Click Cancel.
g. Open the Oracle SQL developer and expand the ODI_STAGE connection (for the password, enter ODI_STAGE). Select Tables node and if necessary click the Refresh
button
. Double–click the Audit table TRG_SALES_H, click Data tab, and verify that your Audit table was created and populated with audit records, as shown next.
3. In addition, you create an option for your new knowledge module to make your KM more user-friendly. This option will enable an end user to choose when to generate audits.
a. In Designer, click the Projects tab, right-click IKM Oracle UI – Audit, and select New Option. Name this option AUDIT_CHANGES, set Type to Check Box, and Default
Value to true. Click Save and close the AUDIT_CHANGES option tab.
b. Now you need to link this option to your steps in KM. Double-click IKM Oracle UI -Audit, and click the Details tab. Double-click your new step, Create Audit Table, to edit it, and then scroll down and click the Options.
c. Deselect the Always Execute check box. Select AUDIT_CHANGES. This will conditionthe execution of these steps with the value set by the end user. Click Save. Click the
Details tab.
d. Repeat the previous step for the Insert Audit Records command, as shown in the following screens. Click Save to save your KM and close the tab.
e. Double-click INT-Exp-FF-RT-Audit to edit it. Click the Flow tab, click Target (ODI_STAGE), and verify that the option AUDIT_CHANGES is set to true.Execute the interface
f. If not opened, open ODI Operator, select All Executions, and then click the Refresh button and view the execution results. Both Create Audit Table and Insert Audit Records steps should be present.
g. In Designer, edit the interface to set the option AUDIT_CHANGES to false. Save your interface and then execute your interface again
h. In ODI Operator, click the Refresh button and view the execution results. The new KM steps to create and populate an audit table are not executed.
g. Open the Oracle SQL developer and expand the ODI_STAGE connection (for the password, enter ODI_STAGE). Select Tables node and if necessary click the Refresh
button
. Double–click the Audit table TRG_SALES_H, click Data tab, and verify that your Audit table was created and populated with audit records, as shown next.3. In addition, you create an option for your new knowledge module to make your KM more user-friendly. This option will enable an end user to choose when to generate audits.
a. In Designer, click the Projects tab, right-click IKM Oracle UI – Audit, and select New Option. Name this option AUDIT_CHANGES, set Type to Check Box, and Default
Value to true. Click Save and close the AUDIT_CHANGES option tab.
b. Now you need to link this option to your steps in KM. Double-click IKM Oracle UI -Audit, and click the Details tab. Double-click your new step, Create Audit Table, to edit it, and then scroll down and click the Options.
c. Deselect the Always Execute check box. Select AUDIT_CHANGES. This will conditionthe execution of these steps with the value set by the end user. Click Save. Click the
Details tab.
d. Repeat the previous step for the Insert Audit Records command, as shown in the following screens. Click Save to save your KM and close the tab.
e. Double-click INT-Exp-FF-RT-Audit to edit it. Click the Flow tab, click Target (ODI_STAGE), and verify that the option AUDIT_CHANGES is set to true.Execute the interface
f. If not opened, open ODI Operator, select All Executions, and then click the Refresh button and view the execution results. Both Create Audit Table and Insert Audit Records steps should be present.
g. In Designer, edit the interface to set the option AUDIT_CHANGES to false. Save your interface and then execute your interface again
h. In ODI Operator, click the Refresh button and view the execution results. The new KM steps to create and populate an audit table are not executed.
No comments:
Post a Comment