Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Metadata Manager 10.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Using Metadata Manager
  3. Configuring Metadata Manager
  4. Application Resources
  5. Business Glossary Resources
  6. Business Intelligence Resources
  7. Custom Resources
  8. Data Integration Resources
  9. Data Modeling Resources
  10. Database Management Resources
  11. Universal Resources
  12. Managing Resources
  13. Loading and Monitoring Resources
  14. Managing Permissions
  15. Resource Migration
  16. Repository Migration
  17. Appendix A: Metadata Manager Login
  18. Appendix B: Metadata Manager Properties Files
  19. Appendix C: Resource Configuration Files
  20. Appendix D: Glossary

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

Back Next

Business Objects Configuration Properties

Business Objects Configuration Properties

Update the configuration properties when you create or edit a Business Objects resource.
The following table describes the Business Objects configuration properties:
Property
Description
Agent URL
Host name and port number of the Metadata Manager Agent. You can use the Metadata Manager Agent installed on any machine.
Source system version
Name and version of the resource.
Version
Version of the SAP Business Objects repository. Select a version or configure the Metadata Manager Agent to detect the version.
Default is auto-detect.
System
Name of the Business Objects repository. For Business Objects 11.x and 12.x, specify the name of the Business Objects Central Management Server. Specify the server name in the following format:
<server name>:<port number>
If the Central Management Server is configured on a cluster, specify the cluster name in the following format:
<host name>:<port>@<cluster name>
Default port is 6400.
If the version of the Business Objects repository is 14.0.6, do not specify a port number in the repository name. If you specify the port number, Metadata Manager cannot extract the Web Intelligence reports.
Authentication mode
The authentication mode for the user account that logs in to the Business Objects repository.
Specify one of the following values:
  • Enterprise. Log in using the Business Objects Enterprise authentication mode.
  • LDAP. Log in using LDAP authentication configured to Business Objects.
  • Windows AD. Log in using a Windows Active Directory server.
Default is enterprise.
User name
User name to log in to the Business Objects repository.
Password
Password of the user account for the Business Objects repository.
Repository browsing mode
Specifies the objects that are extracted while browsing for objects in the Business Objects repository. You can specify one of the following values:
  • All. The tree of universes, folders, and documents is extracted.
  • Universes only. The tree of universes and folders is extracted. Documents are not extracted.
  • Connections only. The list of connections is extracted.
Default is all.
Incremental import
Load changes since the previous resource load or load complete metadata. Specify one of the following values:
  • True. Load recent changes only.
  • False. Perform a complete load of the metadata.
Default is true.
Add dependent objects
Choose the documents that depend on the universe you selected. Specify one of the following values:
  • True. Imports the documents that depend on the specified universe.
  • False. Ignores the documents that depend on the specified universe.
Dependency information is retrieved from the Business Objects repository metadata cache. If modified or moved reports are not reflected in the Metadata Manager load, refresh the cache by loading these reports and refreshing the queries.
Default is true.
Add specific objects
Specifies additional objects to the universe. Specify one of the following values:
  • None. Ignores all objects.
  • Universe independent documents. Imports documents that do not depend on any universe.
Default is none.
Crystal CORBA port
Specifies the client port number on which the Crystal SDK communicates with the report application server (RAS).
The RAS server uses the port to send metadata to the local client computer. If you do not specify a port, the server randomly selects a port for each execution.
Verify that the local Windows firewall is disabled, or enables communication on the port.
Class representation
Controls how the tree structure of classes and sub classes are imported.
Metadata Manager Agent imports each class containing objects as a dimension or as a tree of packages. Specify one of the following values:
  • As a flat structure. Creates no packages.
  • As a simplified flat structure. Creates a package for each class with a subclass.
  • As a full tree structure. Creates a package for each class.
Default is as a flat structure.
Import joins
Specify whether joins and contexts are imported. Default value is True.
Choose one of the following values:
  • True. Joins and contexts are imported.
  • False. Joins and contexts are not imported.
Import hierarchies
Specify whether hierarchies are imported. Default value is True.
Choose one of the following values:
  • True. Hierarchies are imported.
  • False. Hierarchies are not imported.
Multiple threads
Number of worker threads that the Metadata Manager Agent uses to extract metadata asynchronously. Leave blank or enter a positive integer value.
If blank, the Metadata Manager Agent calculates the number of worker threads. The Metadata Manager Agent allocates between one and six threads based on the JVM architecture and the number of available CPU cores on the machine that runs the Metadata Manager Agent. If you specify a value that is not valid, the Metadata Manager Agent allocates one worker thread.
Reduce the number of worker threads if the Metadata Manger Agent generates out of memory errors when it extracts metadata. You can increase the number of worker threads if the machine that runs the Metadata Manager Agent has a large amount of available memory, for example, 10 GB or more. However, if you specify too many worker threads, performance can decrease.
Default is blank.
Miscellaneous
Allows you to specify miscellaneous options in a comma separated string.
You can configure the following Java environment options:
  • Configure the Java memory size for 64-bit JRE. Use
    -java.memory
     option to configure the maximum Java memory size. Default Java memory size for 64-bit JRE is 1 GB. For example, 
    -java.memory 8G
-java.memory 800M
  • Configure the Java runtime command line parameters. Use the
    -java.parameters
     option to configure the parameters.
    You must use the
    -java.parameters
     option as the final miscellaneous option.
    For example, 
    -java.parameters -Dname=value -Xms1G
    To download the required third party software libraries using proxy server, use the following option: 
    -java.parameters -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass -Dhttps.proxyUser=user -Dhttps.proxyPassword=pass
  • Configure the Java location for Windows or Linux. Use
    -java.executable
    option to configure the Java location. For example, 
    -java.executable "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"
Depending on the JRE version or edition, the following are the compatible SAP BusinessObjects versions:
  • OpenJDK 11 version is compatible with the MIMB JRE version.
  • SAP Business Objects Repository XI 4.2 and previous versions are compatible with 32-bit JRE if the SAP BusinessObjects universes use ODBC or OLEDB connections.
Hence, MIMB must use the JRE version packaged with the BusinessObjects. For example, 
-java.executable "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\jre8\bin\javaw.exe"
Configure the following JRE options for the BusinessObjects Information Design Tool (IDT):
  • The Java location for Windows to be used for the IDT. Use the
    -businessobjects.idt.java32.executable
     option to configure the Java location. For example, 
    -businessobjects.idt.java32.executable "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\jre8\bin\javaw.exe"
  • The JRE memory size for the IDT. Use the
    -businessobjects.idt.java32.memory
     option to configure the maximum memory size. For example, 
    -businessobjects.idt.java32.memory 1G
-businessobjects.idt.java32.memory 1024M
Auto assign connections
Metadata Manager configures connection assignments to relational database resource types during the resource load. If you disable this option, configure connection assignments in the resource properties after you create the resource.
Repository subset
Accesses objects stored in a remote Business Objects repository. Specify the IDs of universes, reports, and folders. Separate multiple values with a semicolon.
0 COMMENTS
We’d like to hear from you!