Skip to end of metadata
Go to start of metadata

Among the various ways to start and shutdown the WebLogic server instance, the following describes how to start and stop the script (script or batch) fil in $DOMAIN_HOME/bin.

The script file has the separate start/stop script files for each management server and each managed server for each domain.

  • Management Server - startWebLogic.cmd / stopWebLogic.cmd
  • Managed Server - startManagedWebLogic.cmd / stopManagedWebLogic.cmd


Run startWebLogic.cmd to start the management server of the domain. The following is an example of the message format when the operation is completed normally.


Run stopWebLogic.cmd to shutdown the management server of the domain. The following is an example of the message format when the shutdown is completed normally.

In case of a shutdown, it is possible to guarantee the normal termination only by the execution result of the shutdown script file.

If the related process still exists despite the normal shutdown in the message, the log of the WebLogic server instance should be checked and corrected.

JDBC Driver Settings

To create a JDBC data source, the relevant JDBC driver must be set in WebLogic. This section describes overall information about JDBC Driver settings.

How to get the Altibase JDBC Driver

The Altibase JDBC driver is provided as a single file called Altibase.jar.

It is provided with the Altibase Server package by default, so it can be obtained in the $ALTIBASE_HOME/lib directory of the operating system account where Altibase is installed.

Altibase.jar, as well as Altibase5.jar files, exist from the ALTIBASE 5 version. Altibase5.jar is used to link ALTIBASE 5 and lower versions together.

Therefore, in a normal situation where only one ALTIBASE server or multiple ALTIBASE servers of the same version are linked, the file $ ALTIBASE_HOME/lib/Altibase.jar can be used.

The latest ALTIBASE JDBC driver can be found on

How to check the Altibase JDBC Driver Version

In order to determine whether the Altibase Server and the Altibase JDBC Driver are compatible, the version of the Altibase Server and Altibase JDBC Driver must be compared to check whether the CM (Communication) protocol matches.

The method to check the version of the Altibase server is as follows.


The method to check the version of the Altibase JDBC Driver is as follows.

Here, if the "cm protocol version" of the Altibase server matches the "CMP" of the Altibase JDBC driver, compatibility is possible.

Generally, the Altibase JDBC driver file included in the Altibase server package is used for compatibility, but it is recommended to use the latest compatible Altibase JDBC drive file whenever possible.

How to set the JDBC Driver to be used in WebLogic

To use a specific JDBC driver in WebLogic, the relevant files must be added to the CLASSPATH of the domain management server.

It cant be set up in two ways. It is irrelevant to select either method, but after setting, the user must restart the management server of the domain.

For reference, all the examples are for setting ALTIBASE 5 and ALTIBASE of different versions at the same time. When integrating ALTIBASE of the same version, only one JDBC driver needs to be set.

  1. The JDBC driver-related files are located in $ DOMAIN_HOME / lib.

After placing JDBC driver-related files in $DOMAIN_HOME/lib, the default library path of each domain, when the management server of the domain is started, the files are automatically added to the CLASSPATH with the following message.

  1. Add JDBC driver-related files directly to CLASSPATH of startWebLogic.cmd file.

Open the startWebLogic.cmd file which is the management server of each domain, and add the JDBC driver-related file directly to the CLASSPATH item and restart it.





  • No labels