Skip to Content

Audit configuration for BI 4.1 with Oracle database

As we already know the Audit universe and reports needs to be deployed manually in BI platform as it is no longer out of box functionality in BI 4.x. For BI 4.0 Auditor configuration, I have already written a blog here http://scn.sap.com/community/bi-platform/blog/2013/01/07/sap-businessobjects-40-auditor-configuration-deployment-end-to-end

The difference between earlier blog and this blog is the deployment method. In BI 4.0 the Auditor will be configured by extracting from the file system (.unx universe & Crystal reports) but where as in BI 4.1 SPx we do have the LCMBIAR file which holds the required universe and reports. Please continue reading the blog for step by step procedure to configure auditor.

You can download all the required universe and reports from the document here http://scn.sap.com/docs/DOC-53904

and make sure you enabled Auditor in CMC.  Refer here BusinessObjects Auditing – Considerations & Enabling


You need to select the appropriate .unx file according to your database middleware. Since I am going to deploy it in Oracle database I validated the supported Oracle client installation and the corresponding TNSNAMES.ora file with the Audit database service entry.


/wp-content/uploads/2014/11/1_588067.jpg

In order to import the LCMBIAR content, we are going to use command line batch file (LCM_CLI.bat) with .LCMBIAR file and a property file with import parameters.

/wp-content/uploads/2014/11/2_588107.jpg

/wp-content/uploads/2014/11/3_588108.jpg

/wp-content/uploads/2014/11/4_588113.jpg


Sample properties file

————————————————————————————

Auditing.properties

————————————————————————————

action=promote

importLocation=<biar_folder_path>\OracleAuditing.lcmbiar

LCM_CMS=<hostname>:<port>

LCM_username=Administrator

LCM_password=<password>

Destination_CMS=<hostname>:<port>

Destination_userName=Administrator

Destination_password=<password>

includeSecurity=false

exportDependencies=false

consolelog=false

————————————————————————————

Run the LCM_CLI.bat file with the property file as a parameter something like below

/wp-content/uploads/2014/11/5_588114.jpg

The import status

/wp-content/uploads/2014/11/6_588115.jpg
/wp-content/uploads/2014/11/7_588119.jpg

Once the BIAR file is imported successfully, we need to modify the universe connection in such a way that it points to the right audit schema.

Furthermore, Create a Project in Information Design Tool and import the universe.

/wp-content/uploads/2014/11/8_588120.jpg

/wp-content/uploads/2014/11/9_588121.jpg

/wp-content/uploads/2014/11/10_588125.jpg

/wp-content/uploads/2014/11/11_588126.jpg

/wp-content/uploads/2014/11/12_588127.jpg

/wp-content/uploads/2014/11/13_588128.jpg

/wp-content/uploads/2014/11/14_588129.jpg

You should have Adobe flash player 11 or higher to launch the crystal reports from BI Launchpad.

Here is the deployed report for you.

/wp-content/uploads/2014/11/15_588130.jpg

Here are some of the blogs related to Auditing


BusinessObjects Administration – Audit reporting vs Metadata reporting

BusinessObjects Auditing – What is changed in BO 4.0?

BusinessObjects Auditing – Considerations & Enabling

BusinessObjects Administration – Extending capabilities of BI 4.x Audit reporting


Hope this could help people who are looking for BI 4.1 audit configuration. Thanks for reading!


8 Comments
You must be Logged on to comment or reply to a post.
  • Using your documentation (and after resolving an error not mentioned here) I was able to finally get to a point where I could (attempt to) test the universe connection (though the resolution was awful, so I had to guess at what you were selecting).  But when I try to test the connection using the Oracle (32-bit) ODBC connection and the Oracle Client connection, it fails.

    I am able to successfully connect to the db using the 32-bit ODBC connection in the ODBC connection administrator.

    The error with the ODBC connection test in IDT is: com/businessobjects/connectionserver/PropertySet%CancelSupportLevel.

      • The Oracle Client (using tnsnames) uses 64-bit. (And I was told by tech support that using “Oracle Client” will not work (and it didn’t).)

        The Universe needs a 32-bit connection. I have both the 64-bit and 32-bit Oracle clients installed because the CMS dbs need 64-bit.The Universe needs the 32-bit one. I can test the 32-bit ODBC client in ODBC Administrator, and it works fine. The thing is to get the Universe connection to use the 32-bit ODBC client. I moved it to the beginning of the path in the environmental variables, but that didn’t work. I have all of the products installed on the same server.