Using BIEE to connect SQL Server business data sources in a Linux environment _mssql

1. Client

When the client configures the ODBC data source first, you can enter ODBCAD32 directly in the run, open the Configuration Interface-System DNS---Add
Select the relevant driver of SQL Server, generally choose Wire Protocol driver, configure SQL Server database connection information, test whether the connection is successful, and save exit.
Note that the ODBC data source name is logged at this time, and it is best not to change it once you are sure. Because if you change, the server side will also make changes.
Open Administrator Tools, select Import Metadata, choose a configured SQL Server ODBC data source, and other procedures are exactly the same as Oracle operations.

2. Service End

What the server has to do is add an ODBC data source to the Linux environment, so that BIEE can match the database connection according to ODBC name at runtime.
Operations on the server side because BIEE already has its own data source for SQL Server, the configuration is relatively simple. It is divided into two steps:
A, modify the environment variables, user.sh

oracle_instance/bifoundation/oraclebiapplication/coreapplication/setup/user.sh

The purpose of this step is to add the SQL Server driver to the startup environment variable, which is
After opening the user.sh file, add the following at the bottom:

#SQLServer Parameters
#---------------------------------------
ld_library_path=/user/local/oracle_ bi1/common/odbc/merant/5.3/lib:$ ld_library_path
Export Ld_library_path

Save and exit after add complete
B, modify the ODBC configuration file, odbc.sh, the same path as the user.sh:

Oracle_instance/bifoundation/oraclebiapplication/coreapplication/setup/odbc.ini

Configured according to SQL Server configuration, the sample is an Oracle Official sample:

[sqlserver_db]
driver=/usr/oracle_bi1/common/odbc/merant/5.3/lib64/armsss23.so
description=datadirect 5.1 SQL Server Wire Protocol
address=111.111.111.111,1433
alternateservers= ansinpw=yes
Connectionretrycount=0
connectionretrydelay=3
database=dbschema_name
loadbalancing=0
logonid=
password=
quoteid=no
reportcodepageconversionerrors=0

It is important to modify the contents of the yellow shaded area above, where the sqlserver_db in brackets are the names of the ODBC data sources and need to be consistent with the names in RPD