- Integrated Systems
- About Us
- Integrated Systems
- About Us
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
09-19-2005 04:49 PM
It is same as DSN on Windows. In unix for MySQL, you will configure it in odbc.ini file.
09-19-2005 05:01 PMSolution
also note that, A typical datasource will contain the following:
Data Source Class: com.evermind.sql.DriverManagerDataSource
JDBC URL: jdbc:oracle:thin:@hostname:port:sid
where: hostname = the hostname where the database is installed
port = the database port number.
sid = the database System Identifier (SID).
JDBC Driver: oracle.jdbc.driver.OracleDriver
09-19-2005 05:06 PM
A data source name (DSN) is a data structure that contains the information about a specific database that an Open Database Connectivity (ODBC) driver needs in order to connect to it. Included in the DSN, which resides either in the registry or as a separate text file, is information such as the name, directory and driver of the database, and, depending on the type of DSN, the ID and password of the user. The developer creates a separate DSN for each database. To connect to a particular database, the developer specifies its DSN within a program. In contrast, DSN-less connections require that all the necessary information be specified within the program.
There are three kinds of DSN: user DSNs (sometimes called machine DSNs); system DSNs; and file DSNs. User and system DSNs are specific to a particular computer, and store DSN information in the registry. A user DSN allows database access for a single user on a single computer, and a system DSN for any user of a particular computer. A file DSN contains the relevant information within a text file with a .DSN file extension, and can be shared by users of different computers who have the same drivers installed.
09-19-2005 06:35 PM
Start of changeSet the ODBCINI environment variable to point to the file, specifying a full path and file name. If you do not set this variable, the path defaults to /var/mqsi/odbc, which is a directory created when WebSphere Business Integration Event Broker is installed. The file must have file permissions of mqm:mqbrkrs. End of change
A sample template is provided as the file
The entries in the stanzas that you must configure to match your local requirements are shown in italics (descriptions of these entries are provided in ODBC.ini Parameters). You must retain all the entries shown, but you can remove a complete stanza if you do not require it for your configuration (for example, if you are using an Oracle database, you can remove the stanzas shown for DB2 and Sybase).
Make a copy of the default file, set ODBCINI to point to this copy, and make any changes to the copied file rather than to the default.
Ensure that the appropriate library search path environment variable (LD_LIBRARY_PATH on Solaris and Linux) is set to reflect the database products to be used. Refer to your database product documentation for more details.
[ODBC Data Sources]
WBRKBKDB=IBM DB2 ODBC Driver
MYDB=IBM DB2 ODBC Driver
ORACLEDB=DataDirect 410 Oracle Driver
SYBASEDB=DataDirect 410 Sybase ASE Driver
Description=WBRKBKDB DB2 ODBC Database
Description=MYDB DB2 ODBC Database