Creating Databases

To start creating a new database connection, press the Create button in the Databases section and follow the required steps.

Identification
Name	Enter a name for the new database. The name must be unique.
Description	Optionally enter a description for the new database. The description can only be viewed by administrators in JMap Admin.

Connection parameters
Driver	Select the driver for the database system you wish to connect to.You can add new drivers by creating new configuration files in the JMAP_HOME/conf/db directory on the server.
Host	(Depending on the selected driver) The name or TCP/IP address of the database server.
Port	(Depending on the selected driver) The TCP/IP port of the database server.
Database	(Depending on the selected driver) The name of the database to access, as defined in the database server.
Folder	(Depending on the selected driver) The path to the database folder.
Connection string configuration - Advanced	(Only for Oracle driver) Advanced configuration allows you to configure the connection string by writing it directly to the wizard. This is a more flexible way to configure the string under certain circumstances.
Extra parameters	In some rare cases, database systems may require additional parameters. They can be entered in this field.
Username	Enter a username for the database connection. The authentication of domain users is not supported; you must make sure your database allows database authentication.
Password	Enter a password for the database connection.

Connections
Number of connections	Enter the initial size of the pool of connections. This determines how many connections to the database will be kept open.
Maximum connections	Enter the maximum number of connections allowed for this pool. It must be equal to or greater than the initial number of connections. If the pool needs to be increased, new database connections will be created automatically until the maximum value is reached. After a certain period of time, additional connections are automatically closed, and the connection pool returns to its initial size. The maximum value can be disabled by unselecting the check box, allowing the pool to increase without restriction.

Advanced parameters

The following advanced parameters usually don’t need to be modified.

Additional parameters	In some rare cases, database systems may require additional parameters. They can be entered in this field.
Validation query	JMap uses a query validation mechanism to validate database connections. This query is used to test the connection each time a query needs to be executed. If the validation query fails, which typically means that the connection to the database is broken, JMap Server will try to establish a new connection automatically. This mechanism ensures the database connections are always working. The query must be valid and very quick to execute. In order to reduce the impact on performance, make sure you minimize the number of returned records (zero is perfect) and use indexed fields in the WHERE clause. Default queries are provided. They normally don’t need to be changed.
Connection timeout	The connection inactivity timeout is used to close and reopen connections that are inactive for a long period. This mechanism ensures that the database system does not close inactive connections. Make sure that this value is lesser than the connection timeout of your database system. A default value of 2 hours is appropriate most of the time.
Connection wait timeout	Sets the wait timeout value for database operations. This parameter can be lowered to prevent slowdowns or deadlocks in situations where the database server is taking too long to respond, or increased to allow longer wait periods so that queries with long processing time can be successfully executed. The default value is 60 sec. Enable this option to specify a different value for this connection.
Connection type	Specify the connection type to create. Generic connections are all created with the same user information (username and password) defined earlier. From the perspective of the database system, it is as if the same user performed all queries. This type of connection is used most of the time. Identified connections are created on the fly for each user connected to JMap Server. The same connection is reused during the session for each user. From the perspective of the database management system, each query is done by the user who is connected to JMap Server. This connection mode is useful in environments where security is managed at the database level. In order for the identified connection mode to work, it is required that JMap and the database system share the same list of users. This can be the case when the Oracle user manager module is used to manage users.