Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

To connect Altibase in iBatis, the user can set the Altibase JDBC Driver and specify the dataSource for Altibase in the SqlMapConfig file. This chapter section describes how to get the Altibase JDBC driver, how to set the JDBC Driver, and how to set the dataSource in SqlMapConfig. In addition, this section explains how to use the FailOver function, how to work with multiple versions of Altibase, and how to call the stored procedure/function.

How to Get Altibase JDBC Driver

The JDBC driver provided by Altibase is Altibase.jar file. This file is located in the $ALTIBASE_HOME/lib directory of the server where Altibase  is installed.

As of ALTIBASE 5, Altibase.jar and Altibase5.jar files exist in the $ALTIBASE_HOME/lib directory. Altibase.jar is a generic JDBC driver file. JDBC driver file used. Therefore, when interlocking with one Altibase DB or multiple Altibases with the same version, use the $ALTIBASE_HOME/lib/ Altibase.jar file.

It is necessary to check the Altibase JDBC Driver version to verify that the Altibase DB Server to be interlocked with the Altibase JDBC Driver is compatible.

To check the Altibase JDBC Driver version, execute the following command.

At this time, if the cm protocol version of the ALTIBASE DB server and the CMP of the ALTIBASE JDBC Driver are the same, they are compatible.

It is recommended that the user uses the ALTIBASE JDBC Driver file, which is the same as or higher than the version of ALTIBASE DB Server, because JDBC related bugs may have been fixed as the version was upgraded.

How to Set Up in JDBC Driver

The downloaded JDBC driver, Altibase.jar, can be added to the class-agh or placed in an appropriate directory on the web server.

If the user is developing using Eclipse, the user can add the ALTIBASE JDBC Driver to the project as follows.

Project – JRE System Library [DOCKI: J2SE-1.5]-Properties – Installed JREs – Click jre among the items – Click Edit – Add External JARs to add Altibase.jar, ALTIBASE JDBC Driver.



Setting up dataSource in SqlMapConfig file to link with ALTIBASE

The user can connect to ALTIBASE by specifying the property for ALTIBASE in the <transactionManager> tag of the SqlMapConfig file. At this time, the user can directly enter the property values in the SqlMapConfig file, or the user can create a separate properties file and load the property values written in this file for use.

The following is an example of defining properties for ALTIBASE in a properties file called db.properties, and reading these properties and using them in the SqlMapConfig file.

Ex) SimpleConnection db.properties file

The description of each value set in this file is as follows.

PropertyDescription
driverALTIBASE JDBC driver class name
urlConnection string information for connection with ALTIBASE Enter "jdbc:Altibase://IP:port_no/db_name"
usernameDatabase account
passwordDatabase password

Ex) SimpleConnection's SqlMapConfigExample.xml file

The driver, url, username, and password properties specified in db.properties are read and set in the JDBC.Driver, JDBC.ConnectionURL, JDBC.Username, and JDBC.password properties of the dataSource.

To execute the example SimpleConnection project above, Altibase.jar and ibatis-2.3.4.x.jar files are required.

Connection Using FailOver

FailOver is supported as of ALTIBASE 5.3.3. To use the FailOver function, the user can put FailOver-related properties in the part where the user writes the connection url of the dataSource. The following is an example of connecting to ALTIBASE using FailOver. Connection url part is defined in db.properties file.

Ex) FailOverSample's db.properties file

FailOver related properties that can be defined in the connection url specified in the above file are as follows.

PropertyDescription
AlternateServerIndicates the available servers to be connected when a failure occurs (IP Address1:Port1, IP Address2:Port2,...) and describes them.
ConnectionRetryCountIf there is a failure to connect to the available server, the number of attempts to connect is repeated
ConnectionRetryDelayTime to wait before attempting to connect again when the available server connection fails (in seconds)
LoadBalanceIf set to on, random selection is made including the default server and available servers when the first connection is attempted. If set to off, it connects to the default server when it tries to connect for the first time, and if it fails, it connects to the server described by AlternateServer.
SessionFailOverIndicates whether to perform STF (Service Time Fail-Over). on: STF, off: CTF CTF(Connection Time Fail-Over) refer to recognizing a failure at the time of DBMS connection and retrying the connection to another normal Server. STF(Service Time Fail-Over) means that it detects a failure during service, reconnects to the DBMS of another available node, restores the properties of the session, and allows the user application to perform the business logic again. (STF performs Fail-Over only for DB access, and failed transactions must be reprocessed by the user.)

In order to execute the above example FailOverSample project, Altibase.jar and ibatis-2.3.4.x.jar files are needed as in “Set dataSource in SqlMapConfig file to link with ALTIBASE”.

Connecting ALTIBASE 5 and Previous Versions at the Same Time

Starting with ALTIBASE 5, the ALTIBASE 5 version-specific JDBC Driver (Altibase5.jar) is provided so that one application can connect to ALTIBASE 5 and ALTIBASE 4 or ALTIBASE 3 simultaneously. By using this driver, the user can access two versions of ALTIBASE between ALTIBASE 5-ALTIBASE 4, or ALTIBASE 5-ALTIBASE 3, ALTIBASE 5.1.5-ALTIBASE 5.3.3.

In order to distinguish it from the existing Altibase.jar, Altibase5.jar for ALTIBASE 5 is required separately. In addition, in the part that is specified in the dataSource, the JDBC Driver class name should also specify Altibase5.jdbc.driver.AltibaseDriver for ALTIBASE 5 instead of the existing Altibase.jdbc.driver.AltibaseDriver.

In order to integrate with other versions of ALTIBASE in iBATIS, you need to create a separate SqlMapConfig file for each version and read each SqlMapConfig file in the application.

Please note that in this case, the program should load Altibase5.jdbc.driver.AltibaseDriver first and then Altibase.jdbc.driver.AltibaseDriver.

The following is an example of loading the drivers of two versions of ALTIBASE using Altibase.jar and Altibase5.jar files.

Ex) db.properties1 file of MultiVersionConneciton

Settings for ALTIBASE 5 version

Ex) db.properties2 file of MultiVersionConnection

Settings for ALTIBASE 5 and earlier

Ex) MultiVersionConneciton's SqlMapConfigExample1.xml file

Settings for ALTIBASE 5 version

Ex) MultiVersionConneciton's SqlMapConfigExample2.xml file

Setting for ALTIBASE 5 and earlier

Ex) PersonApp.java file of MultiVersionConnection

In the PersonApp.java example above, to load Altibase5.jdbc.driver.AltibaseDriver before Altibase.jdbc.driver.AltibaseDriver, read the SqlMapConfigExample1.xml file using Altibase5.jdbc.driver.AltibaseDriver as JDBC.Driver first. have. The driver for ALTIBASE5 must be loaded first.

In order to execute the MultiVersionConnection project included in the example, not only the ibatis-2.3.4.x.jar file used previously, but also Altibase.jar and Altibase5.jar files are needed. These files exist in the lib directory of the directory where ALTIBASE is installed ($ ALTIBASE_HOME). The user can use the Altibase5.jar file of the ALTIBASE 5 version and the Altibase.jar file of the previous version.

Calling Procedure/Function

When calling the stored procedure/function created in DB in iBATIS, set the information on the parameter defined in the stored procedure / function in the SqlMap file, and in the <procedure> tag, call the procedure/function applied to CallableStatement applied to the tag. Just define it.

The following is an example of calling the stored procedure/function.

Ex) ProcedureSample Procedure/Function creation statement

Ex) Procedure.xml(SqlMap) file of Procedure

Define the type and IN / OUT settings for the parameters of the procedure/function in the <paramaterMap> tag, and specify the id value of the <paramaterMap> tag in the parameterMap attribute in the <procedure> tag. Then, in the <procedure> tag, write a statement that calls Procedure / Function.

To execute the ProcedureSample example, the Altibase.jar and ibatis-2.3.4.x.jar files are required, as in “Configuring a dataSource in the SqlMapConfig file to link with ALTIBASE”.


  • No labels