Appendix › Import the BIAR File with the BICONFIG Utility

Import the BIAR File with the BICONFIG Utility

Use the BICONFIG utility to import the CCA to CMDB Export Group, the CA CMDB Export report, BOXI_GRLoader.jar (a wrapper jar to GRLoader.jar), and the CA Business Intelligence Universe into CA Business Intelligence. The utility provides a solution for various CA Business Intelligence object functions, such as the command line import of the BIAR (xml_biar_import.biar) file to BusinessObjects Enterprise. The utility also modifies the database connection information for the BIAR file dynamically.

Note: To use the BICONFIG utility, set the JAVA_HOME variable in the system environment or the utility displays an error message.

Important! If you use an OLE DB while importing the BIAR file, modify the oledb.sbo file to prevent a connection error.

To import the BIAR file with the BICONFIG Utility

1. Copy the contents of the BIConfig folder to the computer where you are deploying the solution.
2. Set the required parameter values in the xml_biar_import.xml file located in the samples folder.
3. Modify the parameters, such as the following example Network Layer and RDMS combinations:
   • If you are using SQL Server:

     <networklayer>OLE DB</networklayer>
     <rdms>MS SQL Server 2005</rdms>
     

   • If you are using Oracle:

     <networklayer>Oracle OCI</networklayer>
     <rdms>Oracle 10</rdms>
     

   Note: For more information about setting these parameters, see the sample BIAR files for SQL Server and Oracle.

4. Set the BIAR file location, the username and password of the database, the datasource name, and database server name.
5. Run the following utility from the command line:

   biconfig -h "host" [-n "port"] -u "<user>" [-p "password"] [-s "security"] -f "XML-config-file-name" | -x "XML-config-string" [-i[f] "BIAR-file-path"] [--help]
   

   host

   Specifies the BusinessObjects CMS host.

   port

   (Optional) Specifies the BusinessObjects CMS port.

   Default: 6400

   user

   Specifies the BusinessObjects CMS user.

   password

   (Optional) Specifies the BusinessObjects CMS password.

   Default: (empty string)

   security

   (Optional) Specifies the BusinessObjects Security.

   Default: secEnterprise

   XML-config-file-name

   Specifies the XML configuration file name or absolute path. If you only specify the file name, the BIConfig folder is used to search for the configuration file.

   BIAR-file-path

   (Optional) Specifies the BIAR file name or absolute path. If you only specify the file name, the BIConfig folder is used to search for the configuration file.

   The utility generates the BIConfig.log file in the BIConfig folder. This log displays the status of the import.

   Note: If the BIAR file does not import successfully, the log file displays any error messages.

6. After you import the BIAR file, add users to the CCA to CMDB Export Group in CA Business Intelligence, so that they have full control to access the CA CMDB Export Report, the CCA_CMDB universe, and CCA_CMDB connections on importing the BIAR file.

   Note: For more information about adding users to groups in CA Business Intelligence, see the CA Business Intelligence r3.2, or r3.3 SP1 Administration Guide.

Modify the oledb.sbo File

If you use an OLE DB while importing the BIAR file, you must modify the oledb.sbo file in your CA Business Intelligence directory. Modifying this file prevents an error when using the OLE DB with SQL Server.

To modify the file

1. Open the oledb.sbo file located in the following default installation directory:

   %BOXI_installation_directory%\BusinessObjects Enterprise 12.0\win32_x86\dataAccess\connectionServer\

2. Locate the <DataBase Active="Yes" Name="MS SQL Server 2005"> line and edit the following parameters:

   Provider CLSID

   Change the value to SQLOLEDB.

   Enumerator CLSID

   Change the value to SQLOLEDB Enumerator.

3. Restart the Server Intelligence Agent (SIA).

   The OLE DB changes take effect.

SQL Server Example

The following example shows the sample XML file for SQL Server:

<?xml version="1.0"?>
<biconfig version="1.0">
  <!-- Import BIAR file -->
  <step priority="1">
    <add>
    <biar-file name="C:\biconfigmuthu\ccacmdb.biar">
            <networklayer>OLE DB</networklayer>
            <rdms>MS SQL Server 2005</rdms>
            <username>ccartm</username>
            <password>ccartm</password>
            <datasource>ccartm</datasource>
            <server>testpc</server>
        </biar-file>
    </add>
  </step>
</biconfig>