Oracle Bi Server Odbc Driver Download

2) The OBIEE BI Admin Tool uses the ODBC DSNs that are managed by the second (1b) above. 3) Installing the Oracle 10g Client (either 32-bit or 64-bit) on a Windows x64 server creates an ODBC driver that is seen by the first (1a) above but not the second. This should lead to an obvious problem, which. The Microsoft SQL Server ODBC Driver ships in the Windows oper. Power BI; Teams; Visual Studio. Windows Data Access Components Microsoft ODBC Driver for Oracle.

Introduction The Repository, or ‘RPD’, is the file that contains the metadata for the BI Server in Fusion Applications. This includes database connections, tables, joins, and structure by which these are presented to the report writer. In order to read, or make changes to the RPD file, the BI Administration Tool must be installed. While the install is fairly simple, there are a couple of ‘gotchas’ that can slow the process down.

This post provides these steps. Details Installing the BI Admin Tool The BI Admin tool needs to be run on Windows OS. Furthermore, it should be installed on a 64 bit version of windows.

While it will run on 32 bit, the user will likely experience memory issues opening and editing the large RPD file that comes with Fusion Applications. The version of the BI Admin tool used is also important. If the RPD is opened in the incorrect version, the RPD may be upgraded and rendered incompatible with the version of Fusion Applications.

Locating and Installing Software There are 2 preferred methods to obtain the correct version of the BI Admin tool. • From the Oracle Fusion Applications BIEE Analytics Home – download the 64 bit windows Oracle BI Client Installer: or, • copy it from the BI Server from this path: FA_HOME/fusionapps/bi/clients/biserver/biee_client_install_x64.exe On the 64 bit windows machine, run the biee_client_install_x64.exe executable and install the BI Admin tool. Set up ODBC Connection to Fusion Applications Before you can set up the ODBC connection from the windows machine, you will need to locate the correct port on the Fusion Applications BI Server – typically it’s 10206, but if ports were changed as part of the FA install. • Login to the BI Server’s Enterprise Manager Console.

• Expand ‘Business Intelligence’ within the ‘Farm_BIDomain’ and select ‘coreapplication’. Select ‘Overview’ and the sub tab ‘Processes’.

• Expand the BI Servers, and make a note of the port number. On the windows machine, create a new ODBC Connection. Select the ‘Oracle BI Server’ driver.

Enter the Server name for the host that contains the BI Domain. If necessary – add an entry to the windows/system32/drivers/etc file, so that the windows machine can resolve the host name. Enter the BI Server port (from previous step) and the user name / password you plan to connect with.

Connect to RPD in BI Admin Tool The user can now connect to the BI Server in On-Line mode and can update the ‘live’ RPD. Depending on network speed and the size of the RPD – this can be a very slow process. It can also be dangerous – updating the live RPD that Fusion Applications users and reports are currently working with should only be used with extreme caution.

A better solution is to copy the RPD file from the BI Server to a local or shared drive that the windows client can access, updating the RPD in off-line mode, and then publishing through the BI Server’s Enterprise Manager console. The RPD files are stored in the following path on the BI Server: BIInstance/bifoundation/OracleBIServerComponent/coreapplication_obis1/repository directory This directory contains both the current RPD, and all previous versions. To identify which is the current version – log into Enterprise Manager, go to the ‘Business Intelligence / coreapplication’ section and select the ‘Deployment / Repository’ tabs. This will identify the current version of the RPD.

Copy that RPD version locally or to the shared directory so that you know you are working with the most recent version of the RPD. Summary This post provided the steps to locate and install the BI Administration Tool software, to set up the ODBC connections, and to identify the correct RPD file within Fusion Applications to connect to. For additional documentation on Fusion Applications, see. All site content is the property of Oracle Corp.

Redistribution not allowed without written permission.

18/27 8 Integrating Other Clients with Oracle Business Intelligence You can connect to the Oracle BI Server with a wide variety of ODBC-compliant query and reporting tools, as well as other clients such as remote Administration Tool clients. To connect with a remote client, you configure an ODBC DSN for the Oracle BI Server on the remote client computer, and then use that DSN to connect to a repository from the query tool. Oracle BI Presentation Services clients also connect to the Oracle BI Server using an ODBC DSN. A default ODBC DSN for Presentation Services is created and configured for you during Oracle Business Intelligence installation. Administration Tool clients on the same host as a Presentation Services instance can also use the default DSN to connect to the Oracle BI Server. Or, you can create a separate DSN for the Administration Tool to use. The connection parameters for the Cluster Controller in the default DSN are centrally managed by Fusion Middleware Control.

Do not update these parameters. If you attempt to manually update the centrally managed parameters, the values will be overwritten the next time the system is started. In addition, do not change the name of the centrally managed default DSN. The default DSN has a name similar to 'coreapplication_OH id_number,' where id_number is a number specific to an installed Oracle home. This chapter explains how you can integrate with the Oracle BI Server as a data source using ODBC on both Windows and UNIX platforms. This chapter includes the following topics: • • • •. 8.1 About Integrating with the Oracle BI Server as a Data Source Open Database Connectivity (ODBC) is an industry standard interface for connecting to databases.

A Data Source Name (DSN) is used to store the information about connecting to a given database as a given database user over ODBC. You use the Oracle BI Server ODBC driver to configure a DSN to connect to a set of clustered Oracle BI Servers through the Cluster Controllers, or to an individual Oracle BI Server.

The DSN you configure can be used with any ODBC-compliant query and reporting tool. The Presentation layer lets you configure the presentation of a business model to be consistent with the rules and conventions of your tools to take advantage of the analytical engine and data abstraction of the Oracle BI Server. This makes it much easier to include columns involving complex aggregation and calculation rules in queries and reports. Also, if your organization is currently using query and reporting tools, using the Oracle BI Server as a data source makes these tools more valuable and simplifies the work entailed when using them. Note: In a non-English environment, you can use a direct ODBC connection from a remote client to the Oracle BI Server. However, the translation and localization option that is provided with Oracle BI Presentation Services is not available. Instead, the translation and localization included in the Oracle BI Server metadata (the Oracle BI repository) is available.

For example, if Presentation layer metadata objects are defined in French, they are displayed in French through a third-party application. 8.1.1 About Routing Requests to the Physical Layer Oracle BI Server clients can create a dedicated physical connection to the Oracle BI Server over which all SELECT queries are treated as SELECT_PHYSICAL queries.

SELECT_PHYSICAL queries directly query objects in the Physical layer of the metadata repository, bypassing the Presentation layer and the Business Model and Mapping layer. To enable this direct connection for your ODBC client, select Route Requests To Physical Layer in the DSN configuration. Note that you cannot have a single ODBC connection that sends queries to both the Presentation layer, and the Physical layer. Instead, you can create one regular connection that sends requests to the Presentation layer, and one connection that sends requests to the Physical layer. See 'Syntax and Usage Notes for SELECT_PHYSICAL' in for more information about SELECT_PHYSICAL queries. 8.3 Configuring an ODBC DSN for the Oracle BI Server on Windows This section explains how to create an ODBC DSN for the Oracle BI Server on Windows to enable remote client access. You use the Oracle BI Server DSN Configuration Wizard to set up an ODBC DSN that you can use to connect to a repository through the Oracle BI Server.

The Oracle BI Server ODBC driver is a 32-bit application. Use the 32-bit version of ODBC Data Source Administrator located at C: Windows SysWOW64 odbcad32.exe.

The 64-bit version of the ODBC Data Source Administrator (located at C: Windows system32 odbcad32.exe) does not show the Oracle BI ODBC driver. To create a DSN for the Oracle BI Server on Windows: • Open the Windows Control Panel by selecting Start >Settings >Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC). • In the ODBC Data Source Administrator dialog, click the System DSN tab, and then click Add. • In the Create New Data Source dialog, select the driver Oracle BI Server 11g_OH id_number (where id_number is a number specific to an installed Oracle home), and then click Finish.

The first page of the Oracle BI DSN Configuration wizard is displayed. • Type a name for the data source in the Name field. Note: Do not change the name of the centrally managed default DSN for Presentation Services and the Administration Tool.

• Optionally, enter a description in the Description field. • To connect to a single Oracle BI Server that is not part of a cluster, in the Server field, select the computer on which the Oracle BI Server is running. If the server name does not appear in the list, then type the computer name in the Server field. Note: This field is not used for the default DSN created for Presentation Services, because the Oracle Business Intelligence system is clustered by default. • To connect to a set of clustered Oracle BI Servers through the Cluster Controllers, do the following: • Select Clustered DSN.

• Enter information for the primary and secondary Cluster Controllers, as follows: • In the Primary Controller field, enter the name of the computer that is specified as the primary Cluster Controller. Then, enter the port number for the Primary Controller in the appropriate Port field. • If a secondary Cluster Controller has been set up, then type the name of the host where the Secondary Controller is running in the Secondary Controller field. Then, enter the port number for the Secondary Controller in the appropriate Port field. You can find information about the Primary and Secondary Controller hosts and ports on the Availability tab of the Capacity Management page in Fusion Middleware Control. • To test the connection to the Cluster Controllers, click Test Cluster Connect. If the test is not successful, then correct any errors identified in the message and test the connection again.

Note: Do not change the Primary Controller, Secondary Controller, and Port parameters of the centrally managed default DSN for Presentation Services. • Select Route Requests To Physical Layer to create a dedicated physical connection to the Oracle BI Server for clients using this DSN. All SELECT queries over this connection will be treated as SELECT_PHYSICAL queries. SELECT_PHYSICAL queries directly query objects in the Physical layer of the metadata repository, bypassing the Presentation layer and the Business Model and Mapping layer. • Select Use Forward Only Cursor to change the ODBC cursor from its default scrollable mode to forward only.

• To configure this DSN to communicate over SSL, select Use SSL. To configure advanced settings for SSL, see for additional instructions. • Click Next.

The second page of the Oracle BI DSN Configuration wizard is displayed. • Optionally, for Login ID and Password, enter a user name and corresponding password for the Oracle BI Server. • To save the user name in the Windows registry for this client, select Save login ID.

If you select this option, you will not have to enter your user name each time you connect. You will still have to enter a password. • Enter a port number for the Oracle BI Server in the Port field. This option is enabled when Clustered DSN has not been selected on the first page of the wizard. You can find information about the Oracle BI Server port on the Availability tab of the Capacity Management page in Fusion Middleware Control. • If you want to connect to a repository other than the default repository, then select Change the default repository to, and then type the logical name of the repository to which you want to connect.

You can only use this setting if you have configured the Oracle BI Server to host multiple repositories. Note that hosting multiple repositories on a single Oracle BI Server is not recommended for production deployments. Note: For Presentation Services clients, each Presentation Services instance can only access a single repository. To configure multiple Presentation Services instances to access multiple repositories, follow these steps: • Install Presentation Services on one computer for each repository instance.

For example, if you have three repositories running on your Oracle BI Server, install three Presentation Services instances on three separate computers. • Adjust the setting Change the default repository to in the DSN for each Presentation Services instance. • As a Web client end user, you can choose which repository to access from your client browser by substituting the appropriate Web server computer name or IP address in the URL for the Presentation Services instance that points to the repository you want to work with: • Optionally, select Connect to obtain default settings for the additional configuration options. If you select this option, the wizard will attempt to connect to the server to obtain default values for the configuration settings on the next screen.

If you do not select this option, then you can still configure the DSN by manually entering the information in the next screen. If you select this option, you must provide values for Login ID and Password.

• Click Next. The third page of the Oracle BI DSN Configuration wizard is displayed.

• To change the name of the default subject area, select Change the default subject area to and then enter the name of the subject area. If you selected the Connect option in the previous screen, you can choose a name from the list. Do not select this option for the DSN used by Oracle BI Presentation Services.

If you do not select this option, the default subject area is the one defined in the internal call query metadata. You can use the DATABASE SQL function to determine the default subject area; see for more information. • To change the default error message language, select Change the default error message language to and then select the language you want to use for error messages. See for more information about choosing the error message language. • If needed, select Use Regional Settings when outputting dates and times.

When this option is enabled, data in Date, Time, or DateTime format is displayed using Windows regional settings, rather than the default format for the Oracle BI Server. To see the Windows regional settings, open the Control Panel and double-click Regional and Language Options. • If the repository has been set up for database-specific login IDs and passwords, you can enter the user names and passwords for the underlying databases. The database-specific credentials allow privileged users to connect to the underlying databases at the level of authority granted to those users in the databases. To enter user names and passwords for the underlying databases, follow these steps: • Select the database for which you want to enter a user name and password and click Edit. • Enter the login ID and password corresponding to the database you selected and click OK. • Repeat these steps for other databases if necessary.

• Click Finish to save the DSN configuration. 8.3.1 Configuring the ODBC DSN for Advanced SSL Settings Follow the steps in this section to configure additional advanced settings for SSL. To configure the Oracle BI Server DSN for advanced SSL settings: • On the first page of the Oracle BI DSN Configuration wizard, after selecting Use SSL, click the Configure SSL button.

Liquor License Lubbock Texas. The Secure Socket Layer Configuration dialog appears. • For Certificate File, enter the path and file name of the Client Certificate file, or click Select to browse for the file. For example: ORACLE_HOME ssl client-cert.pem • For Certificate Private Key File, enter the path and file name of the Client Private Key file, or click Select to browse for the file.

For example: ORACLE_HOME ssl client-key.pem • For File Containing Passphrase, enter the path and file name of the passphrase file for the Client Key, or click Select to browse for the file. For example: ORACLE_HOME ssl clientpwd.txt • Select Verify Peer. • If you are using the hashed version of the CA certificate, enter the directory where the hashed file is located in the CA Certificate Directory field.

For example: ORACLE_HOME ssl • If you are using the CA certificate, provide the path and file name of the CA Certificate file in the CA Certificate File field. For example: ORACLE_HOME ssl cacert.pem • For Cipher List, enter the list of ciphers to be used. For example: EXP-DES-56-SHA • For Certificate Verification Depth, specify 1.

• For Trusted Peer Distinguished Names, enter DNs of servers that will allowed to connect. For example: C=US/ST=CA/L=Redwood Shores/O=Oracle/ OU=BI/CN=servercertificate • Click OK.

• Complete the additional steps to configure the DSN, starting from Step of the procedure in the previous section. After you complete these steps, copy the client certificate, client private key, and passphrase files (for example, client-cert.pem, client-key.pem, and clientpwd.txt) to the directory specified in the parameters. If you have set the CA Certificate File parameter, you must also copy the CA certificate file (for example cacert.pem) to the directory specified. If you have set the CA Certificate Directory parameter, copy the hash version of the CA certificate to the directory specified. 8.4 Configuring an ODBC DSN for the Oracle BI Server on Linux or UNIX This section explains how to create an ODBC DSN for the Oracle BI Server on Linux or UNIX to enable remote client access.

On Linux and UNIX systems, the file odbc.ini contains the standard or clustered Oracle BI ODBC connection details that are used by Oracle BI Presentation Services and nqcmd processes. Do not change the DSN logical name, or the Primary and Secondary Cluster Controller and Port parameters for the centrally managed default DSN. To create an ODBC DSN for the Oracle BI Server on Linux or UNIX: • Log on as a separate telnet session. • Open the odbc.ini file for editing.

You can find this file at: ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup/odbc.ini • In the section [ODBC Data Sources], add the new data source name you want to create and define it as an Oracle BI Server data source. For example: [ODBC Data Sources] my_new_dsn = Oracle BI Server • Add a section for the new DSN and provide parameters as follows: [my_new_dsn] Driver = ORACLE_HOME/bifoundation/server/bin/ call_interface.

Library_suffix ServerMachine = local Port = bi_server_port_number ForwardOnlyCursor = No SelectPhysical = No Regional = Yes Note the following: • For call_interface, enter nqsodbc for ODBC35 (the default), or nqsodbc20 for ODBC20. • For library_suffix, use the library suffix appropriate for your operating system. Download Film Horor Indonesia Terbaru 2013. For example, use.so for Linux, Solaris, or AIX, or use.sl for HP-UX. • For Port, enter the Oracle BI Server port number. Do not provide this option if you want this data source to connect to clustered Oracle BI Servers.

You can find information about the Oracle BI Server port number on the Availability tab of the Capacity Management page in Fusion Middleware Control. • Set ForwardOnlyCursor to Yes to change the ODBC cursor from its default scrollable mode to forward only. • Set SelectPhysical to Yes to enable integrating clients to create a dedicated physical connection to the Oracle BI Server over which all SELECT queries are treated as SELECT_PHYSICAL queries.

• Set Regional to Yes to display data in Date, Time, or DateTime format using the regional settings for your operating system, rather than the default format for the Oracle BI Server. • If you want this data source to connect to clustered Oracle BI Servers, supply the following additional parameters. Note that the primary CCS and secondary CCS should not be on the same computer. IsClusteredDSN=Yes PrimaryCCS= primary_cluster_controller_name PrimaryCCSPort= primary_cluster_controller_port_number SecondaryCCS= secondary_cluster_controller_name SecondaryCCSPort= secondary_cluster_controller_port_number Note the following: • If you want this data source to connect to a single Oracle BI Server, set IsClusteredDSN to No. • You can find information about the Primary and Secondary Controller hosts and ports on the Availability tab of the Capacity Management page in Fusion Middleware Control. • To configure SSL for this data source, supply the following additional parameters as appropriate for your SSL deployment: SSL = Yes SSLCertificateFile = path_to_client_certificate_file SSLPrivateKeyFile = path_to_client_private_key_file SSLPassphraseFile = path_to_passphrase_file_for_client_key SSLCipherList = list_of_cipers SSLVerifyPeer = Yes SSLCACertificateDir = path_to_hashed_version_of_ca_certificate_file SSLCACertificateFile = path_to_ca_certificate_file SSLTrustedPeerDNs = list_of_server_DNs_allowed_to_connect SSLCertVerificationDepth = 1 • Save and close the file. • If you are updating the DSN used by Presentation Services, you must restart Presentation Services.

Scripting on this page enhances content navigation, but does not change the content in any way.