Editing BI ODBO System Properties
Use
The BI ODBO (OLE DB for OLAP) system template provides business intelligence functionality to systems you create based on ODBO-compliant OLAP data sources such as Microsoft Analysis Services, SAS, Microsoft PivotTable Services, and SAP BI systems. The template for a BI ODBO system defines the specific parameters needed to connect to these data sources and contains a reference to the BI ODBO Connector. The BI ODBO system inherits these properties, some with default values, others that require the setting of values. You edit the system by inserting needed property values and by modifying default values, if necessary.
The template contains many properties, not all of which can be edited, and not all of which are necessary to establish a connection to the back-end system.
The table below lists the properties needed to create a system based on the BI ODBO system template. Each has an explanation of the value that should be set.
Prerequisites
● Supported systems are Microsoft Windows 2000 / NT / XP or greater, configured with Microsoft Data Access Components (MDAC) 2.6 or greater.
● You must first ensure that an OLE DB for OLAP driver for your data source has been loaded in the server’s Visual Administrator.
Procedure
...
1. From the top-level navigation bar, choose System Administration → System Configuration.
2. From Detailed Navigation, choose System Landscape.
3. In the Portal Catalog, right-click the system whose properties you want to edit, and from the drop-down list choose Open → Properties. This opens the System Landscape Editor.
4. Set your BI ODBO system properties according to the details in the table below.
Property |
Value |
Category: BI / Business Intelligence |
|
BI Directory Provider
|
If Yes, specifies that this BI system is accessible from applications in the Business Explorer suite, where supported. |
Category: Connection Properties |
|
Account Domain of Windows User |
● Windows domain account name. ● Optional. Empty string means property not set. ● See Note below table. |
Account Name of Windows User |
● Username of a given windows domain account. ● Optional. Empty string means property not set. |
Account Password of Windows User |
● Password for a given windows domain account. ● Optional. Empty string means property not set. |
Connection String |
● Connection string information such as provider name, file name, remote provider, remote server, and URL. Mandatory. ● Examples: ○ Local cube: Provider=MSOLAP;Location ○ Microsoft Analysis Server: Provider=MSOLAP;data source=name ○ BI system OLAP provider: Data
Source=BWP; |
Category: Information
|
The property values in this category are assigned during the running of the System wizard and, except for Description, Object is a Template, and System Name are not for editing. |
Description |
An optional description of the system, if one was not inserted during the running of the System wizard. |
Object is a Template |
Defines the system you have created as a template upon which you can base other systems. If selected, this sytem will appear as a template the next time you go to create a system. |
System Name |
● The name assigned to the system when running the System wizard. ● Mandatory, exists for each system. |
Category: User Management |
|
User Mapping Type |
● Defines the type of user mapping needed for connection; who can perform user mapping ● Valid values: user/admin/admin,user For more information, see System Properties for User Mapping. |
Category: Show All |
|
CodeLink |
● A reference to the portal component upon which the system is based. ● Mandatory; assigned while running the System wizard. |
com.sap.portal.reserved.system. |
● The JNDI name of the BI ODBO Connector, through which the system connects. ● It must take the form SDK_XXXX and the letters must be all upper-case. ● Mandatory when working with a connector. |
ComponentType |
● The portal component (system) you have just created. ● Mandatory; required by the system landscape service. |
System Type |
● Type of system. ● Mandatory; assigned while running the System wizard. |
Note -- Using a specific Windows domain account:
You may wish to set a specific Windows domain account in certain situations where the system needs to use security credentials different from the credentials used by the server itself. Examples of this include when the OLE DB driver for Microsoft Analysis Server supports only Windows domain security and ignores credentials supplied in the connection string, if any, or with a connection to an MS SQL Server where the server is configured for Windows authentication only.
5. Save your settings.
To finish configuring your system, assign an alias and, if necessary, configure user mapping. See:
User Mapping and the
Portal