Configuring an ODBC DSN for the Oracle BI Server on Windows

Integrating Other Clients with Oracle Business Intelligence 10-7

2. 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

3. 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

4. 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

5. Select Verify Peer.

6. 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 7. 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

8. For Cipher List, enter the list of ciphers to be used. For example:

EXP-DES-56-SHA

9. For Certificate Verification Depth, specify 1.

10. For Trusted Peer Distinguished Names, enter DNs of servers that will allowed to

connect. For example: C=USST=CAL=Redwood ShoresO=Oracle OU=BICN=servercertificate

11. Click OK.

12. Complete the additional steps to configure the DSN, starting from Step 11 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.

10.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, the Primary and Secondary Cluster Controller and Port parameters, or the SSL parameters for the centrally managed default DSN. To create an ODBC DSN for the Oracle BI Server on Linux or UNIX: 10-8 Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition 1. Log on as a separate telnet session. 2. Open the odbc.ini file for editing. You can find this file at: ORACLE_INSTANCE bifoundationOracleBIApplicationcoreapplicationsetupodbc.ini 3. 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 4. Add a section for the new DSN and provide parameters as follows: [my_new_dsn] Driver = ORACLE_HOMEbifoundationserverbincall_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. 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. 5. 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.