Configuring an Oracle Business Intelligence Enterprise Edition Resource in Metadata Manager

Transcription

1 Configuring an Oracle Business Intelligence Enterprise Edition Resource in Metadata Manager 2011 Informatica

2 Abstract This article shows how to create and configure an Oracle Business Intelligence Enterprise Edition (OBIEE) resource in Metadata Manager to extract metadata from OBIEE Supported Versions Metadata Manager Table of Contents Oracle Business Intelligence Enterprise Edition Configuring Oracle Business Intelligence Enterprise Edition Install the Metadata Manager Agent Configure Permissions Convert the Repository RPD File to a UDML File Enable OBIEE Web Services Export and Import the Keystore Certificate Creating an Oracle Business Intelligence Enterprise Edition Resource Troubleshooting Reference Objects Extracted Alias Physical Table Data Lineage Number of Child Nodes in the Load Details Oracle Business Intelligence Enterprise Edition Oracle Business Intelligence Enterprise Edition (OBIEE) is a business intelligence tool that includes analysis and reporting capabilities. You can create and configure an OBIEE resource to extract metadata from OBIEE. Metadata Manager extracts schema and reporting metadata from OBIEE. The schema metadata includes the presentation, business, and physical models. Configuring Oracle Business Intelligence Enterprise Edition Before you create an OBIEE resource, you must configure the metadata source. If you do not correctly configure the metadata source, the metadata load can fail or the metadata can be incorrectly loaded in the Metadata Manager warehouse. To configure OBIEE, complete the following tasks: Install the Metadata Manager Agent. Convert the Repository RPD file to a UDML file. Configure permissions. Enable OBIEE web services. Export and import the keystore certificate. 2

3 Install the Metadata Manager Agent The Metadata Manager Agent is a program that Metadata Manager uses to access metadata sources and extract source metadata. By default, the Metadata Manager Agent runs on the nodes where the Metadata Manager Service runs. If the Metadata Manager Service runs on UNIX, you must install the Metadata Manager Agent separately on a Windows machine. The Metadata Manager Agent does not run on UNIX. Configure Permissions Metadata Manager connects to the OBIEE Presentation Server to extract the report metadata. The OBIEE user account for which you provide the user name and password must have read permission on the metadata that Metadata Manager extracts from OBIEE. The metadata includes subject areas, report folders, and reports. Metadata Manager extracts the schema metadata from the UDML file. The OBIEE user account does not require permissions on the schema metadata. The OBIEE utility program extracts all schema metadata from the RPD file and writes the metadata to the UDML file. Metadata Manager extracts all metadata from the UDML file. Convert the Repository RPD File to a UDML File When you load an OBIEE resource, Metadata Manager connects to the Presentation Server to extract the metadata for the reports. However, Metadata Manager cannot extract the schema metadata directly from the repository. The OBIEE schema metadata is stored in an RPD file. Because Metadata Manager cannot read RPD files, you must convert the RPD file to a UDML file. Metadata Manager extracts the schema metadata from the UDML file, extracts the reports from the Presentation Server, and links the reporting metadata to the presentation model when you load the resource. OBIEE has a utility program to convert an RPD file to a UDML file. This utility is part of the OBIEE server installation. Use the following command to convert the repository RPD file to a UDML file: <OBIEE home directory>\server\bin\nqudmlgen.exe -U <user name> -P <password> -R <RPD file>.rpd -O <UDML file>.udml -N -Q -8 Enable OBIEE Web Services Metadata Manager uses OBIEE web services to extract metadata from OBIEE. As a result, you must enable OBIEE web services. OBIEE web services is available to licensed users of OBIEE. The OBIEE installer generates the appropriate licensing entries in the analyticsweblicense.xml file based on the installation key. To verify that OBIEE web services are enabled, check that the kmsglicensesoapaccess entry exists in the following file: <OBIEE home directory>\web\config\analyticsweblicense.xml Export and Import the Keystore Certificate Before you extract metadata from an OBIEE Presentation Server in HTTPS mode, you must export the keystore certificate from OBIEE and import it into the Metadata Manager Agent Java Runtime Environment (JRE). When you export the certificate, you create a self-signed certificate that you can import into the Metadata Manager Agent JRE. Use the keytool utility to export and import the certificate. To export and import the certificate: 1. To export the OBIEE keystore certificate and create a self-signed keystore certificate, use the following command: keytool -export -alias <alias name> -keystore <keystore file name> -rfc -file <certificate file name> 2. Copy the certificate file to the following directory: <Metadata Manager Agent installation directory>\java\jre\lib\security 3

4 3. Navigate to the following directory: <Metadata Manager Agent installation directory>\java\jre\lib\security 4. To import the OBIEE keystore certificate into the Metadata Manager Agent JRE, use the following command: keytool -import -alias -ca -file <certificate file name> -keystore <certificate file name> -storepass <keystore password> Note: The default keystore password is changeit. Creating an Oracle Business Intelligence Enterprise Edition Resource Before you create an OBIEE resource, configure the OBIEE source. 1. On the Load tab, click Actions > New Resource. The Resource Selection window appears. 2. Click Business Intelligence > Oracle Business Intelligence. 3. Click Next. The Properties page appears. 4. Enter the following information: Property Name Description Description Name for the resource. The resource appears in the Resources panel with this name. The name must be unique and have from 1 through 256 characters. It cannot include the following characters: / \ : * '? " < > [ ] Description for the resource. Description cannot exceed 4000 characters. 5. Click Next. The Configuration page appears. 6. Configure the following resource properties: Property Agent URL Source system version Always use latest source files Server URL Login User Description Host name and port number of the Metadata Manager Agent. You can use the Metadata Manager Agent installed on any machine. Name and version of the metadata source. You cannot edit this field. Uses the metadata source file in the location you provide each time you load the resource. If you enable this option, the path to the file must include an absolute path that is accessible from the Metadata Manager Agent machine. If you disable this option, Metadata Manager copies the metadata source file to the Metadata Manager application directory when you finish configuring the resource. Each time you load the resource, Metadata Manager uses the copied metadata source file in the Metadata Manager application directory. URL of the Presentation Server. Use the following format: name>:<port>/analytics/saw.dll User name for the Presentation Server. 4

5 Property Login Password Repository Subset Auto Assign Connections File Description Password for the Presentation Server user name. Folder path in the Presentation Server that contains the reports that you want to extract. Enter the path to any of the folders in the Oracle Answers catalog from which you want to extract objects. Separate multiple values with a semicolon (;). Use "/" to indicate the root repository path, use "/shared" to indicate the shared repository path, or use "/users/<user_name>/<folder_name>" to indicate a personal folder path. For example: /shared/financials;/shared/human Resources;/shared/Procurement and Spend Default is /. Metadata Manager configures connection assignments to relational database resource types during the resource load. If you disable this option, you must configure connection assignments in the resource properties after you create the resource. OBIEE repository file in UDML format. You export the repository from the Oracle BI Administration tool to an RPD file, and then convert the RPD file to a UDML file. 7. To add a metadata source file, click Select. If you configured Metadata Manager to use the latest source files, include an absolute path to the file that is accessible from the Metadata Manager Agent machine. If you did not configure Metadata Manager to use the latest source files, select a file and click OK. 8. Click Test Connection to validate the source file configuration. Metadata Manager validates the Metadata Manager Agent URL. If you configured Metadata Manager to use the latest source file, Metadata Manager also validates that the source file exists in the specified path. If the UDML source file is uploaded to Metadata Manager, Metadata Manager validates that the file is compatible with the resource type and version. If Metadata Manager cannot validate the source file configuration, an error message appears. Correct any error and test the connection again. 9. Click Next. The Schedules window appears. 10. To add a schedule, select Attach a Schedule, and select a schedule in the Schedule list. If you have not created a schedule, you can assign a schedule to a resource after you create the resource. 11. Click Finish. The resource appears in the Resources panel on the Load tab. Troubleshooting When I load an OBIEE resource, the Metadata Manager Agent reports the following error: Not enough storage is available to process this command. To load a large amount of metadata for an OBIEE resource, you can increase the Java Virtual Machine (JVM) heap size for the Metadata Manager Agent to increase performance. For example, increase the JVM heap size to 1 GB. To increase the JVM heap size: 1. Open MIRSetup.xml from the following location in a text editor: <Metadata Manager Agent Installation Directory>\conf 5

6 2. Add the following option to the <RunTime> section: <Options>-Xmx1024m</Options> 3. Save MIRSetup.xml. 4. Restart the Metadata Manager Agent service. When I load an OBIEE resource, I get the following error: MITI.MIRException: [MBI_OBIEE_E0002] Failed to login as '<user_name>' on server ' name>:<port>/analytics/' This error can occur for the following reasons: The user name and password provided to log in to the Presentation Server is incorrect. Verify that the user name and password are correctly entered in the OBIEE resource properties. The Presentation Server URL is incorrect. Verify that the following format is used in the OBIEE resource properties: name>:<port>/analytics/saw.dll The default port for Apache Tomcat Server is The default port for Microsoft Internet Information Services (IIS) is 90. To verify that the URL is correct, access the following URL and log in with the user account provided in the OBIEE resource properties: name>:<port>/analytics/saw.dll?dashboard When I load an OBIEE resource, I get the following error: Subject Area 'WB_GEN Marketing Program Contacts' available on the Presentation Server is not defined in the UDML file. MITI.MIRException: [MBI_OBIEE_F0019] The UDML file does not correspond to the RPD used by the Presentation Server. This error occurs when the UDML file specified in the OBIEE resource properties does not contain the same metadata as the RPD file used by the Presentation Server. Convert the RPD file currently being used by the Presentation Server to a UDML file. When I load an OBIEE resource, I get the following error: Consistency: pnc.power of PNC" UPGRADE ID ICON INDEX 6: a Database Catalog must not contain any Model Objects. The Model is not consistent. This error occurs when objects in the UDML file have UPGRADE ID information which Metadata Manager cannot extract. When you convert the RPD file to a UDML file, make sure to use the -N parameter. This parameter removes the UPGRADE ID information from the UDML file. Use the following command: <OBIEE home directory>\server\bin\nqudmlgen.exe -U <user name> -P <password> -R <RPD file>.rpd -O <UDML file>.udml -N -Q -8 When I load an OBIEE resource, I get the following error: An error occurred while importing model <UDML_File>. MITI.MIRException: org.xml.sax.saxparseexception: Invalid byte 1 of 1-byte UTF-8 sequence. MITI.MIRException: [MBI_OBIEE_F0016] No Oracle BI Server model could be imported. This error occurs when the UDML file contains characters that are not in the UTF-8 character set. When you convert the RPD file to a UDML file, make sure to use the -8 parameter. This parameter ensures that the UDML file uses the UTF-8 character set. Use the following command: <OBIEE home directory>\server\bin\nqudmlgen.exe -U <user name> -P <password> -R <RPD file>.rpd -O <UDML file>.udml -N -Q -8 Reference After you create and load an OBIEE resource, you can view and run data lineage on the metadata objects that Metadata Manager extracted. 6

7 Objects Extracted The following table lists the objects that Metadata Manager extracts or does not extract from OBIEE: Extracted AliasPhysicalTable AnswersReport BusinessModel Catalog Column Criteria Dimension Display Folders DynamicVariable Folder InitializationBlocks Key KeyColumn KeyLogicalColumn Layout Level LevelAssociation LevelAttribute LevelKey LogicalColumn LogicalForeignKey LogicalJoin LogicalTable Measure Model Note PhysicalColumn PhysicalForeignKey PhysicalJoin PhysicalSelectTable PhysicalTable PivotTable PresentationCatalog PresentationColumn PresentationTable Report RepositoryInitializationBlock RepositoryVariables Results Schema SessionInitBlock SessionVariable SessionVariables StaticVariable StaticVariables StoredProcedureTable Table Variables Not Extracted Axis Chart Database Hierarchy HierarchyLevelAssociation Operation Shortcuts created under display folders Text View Workspace Alias Physical Table An alias physical table is a synonym object of a physical table. When Metadata Manager loads an OBIEE resource, it extracts physical table columns and copies them to the corresponding alias physical table. Metadata Manager sets the class type for a copied column as a physical column, even if the original column is a key column or a normal column. 7

8 Data Lineage Metadata Manager displays data lineage between columns and tables in the OBIEE physical model and other resources. In addition, Metadata Manager displays data lineage for the following OBIEE objects: Tables and table columns Logical tables, logical columns, and measures Dimensions and levels Presentation tables, presentation columns, and measures Number of Child Nodes in the Load Details When you load an OBIEE resource, Metadata Manager displays the nodes from which it extracts metadata on the Load Details tab. Metadata Manager displays 300 child nodes for any parent node in the load details. To see a complete list of all nodes extracted, save the contents of the Load Details tab to a Microsoft Excel file. Author Alison Taylor Technical Writer Acknowledgements The author would like to acknowledge Erwin Dral, Umer Farooque, Ramesh Kumar, Vasu Nagarajan, and Vivek Singla. 8