Documentation

Services

SMPP binder HTTP Server Data Source Timer

Datasource service

Datasource services enables GnGSmS to connect to database engines,  the datasource service maintains a pool of database connections that can be used by SQL actions in the action tree.

GnGSmS services used JDBC to connect to the database engine, therefore it supports any database engine  that is supported by JDBC.

Driver Installation

Before you are able to connect to the database you have to install the database jdbc driver, the installation of the driver is as simple as copying the driver jar file to the GnGSmS "lib" directory.

Drivers

These are links to the download pages of the most common database engines:

Service Name
 The name of this service, it is better to have a unique name for each service in a GnGSmS configuration
Service Description
 A short description of the service
Disabled
 Enable or disable this service, if disabled the service will not start when you start the GnGSmS services
Connection Username
 The user name to use for connecting to the database server
Connection Password
 The password to use for connecting to the database server
Driver Class
 The JDBC driver class name, the driver class is specific to the Database engine used.

Example:

The Driver class for  MySQL is  com.mysql.jdbc.Driver

For Oracle it is oracle.jdbc.driver.OracleDriver

Important

You need to copy the database driver jar to the GnGSmS lib directory for the data source to be able to locate the driver class.

The data source service expects to find the Driver class in the GnGSmS classpath, any jar file under the lib directory us added automatically to the classpath

Note that you will need to restart GnGSmS after copying the driver to the lib directory for GnGSmS to find it
URL
 The format of the database URL varies cording to the database engine

Example

For MySQL the URL can look like jdbc:mysql://<host>/<databaseinstance>

For Oracle it is jdbc:oracle:thin:@<host>:<port>:<atabaseinstance>