Configuring a Database Server for 1Integrate's repository

1Integrate requires access to an database server to store configuration data such as rule or session definitions, and conformance results. This is referred to as the "1Integrate repository".

By default, 1Integrate will use a H2 database as the Repository. This will store the 1Integrate metadata and entities on the same file system as the 1Integrate installation.

     Warning: This is intended for local, development work and will enable you to get started quickly. Do not use the default H2 database in production environments. See the following database options for recommended repository servers.

Supported Database Servers

The following additional Database Servers are supported:

  • Oracle Enterprise

  • PostgreSQL

  • Microsoft SQL Server

     Note: Please refer to the relevant product documentation when installing your chosen database server.

Creating the repository

You will need to create a database and user (Oracle only requires a User) for your 1Integrate repository on your selected server.

     Note: When deploying 1Integrate to multiple servers, one database user is required per environment.

Oracle

Using Oracle, 1Integrate requires a database user. The setup should be performed as recommended by your Database Administrator who must grant the user access to the database and at least the following permissions:

  • create session

  • create sequence

  • create table

Microsoft SQL Server Database

Using SQL Server Database, you will need a Database and a User that can access that database.

The setup should be performed as recommended by your Database Administrator who must grant the user access to the database and at least the following permissions:

  • create sequence

  • create table

     Note: Microsoft SQL server supports two methods of authenticating users, but these will differ depending on your operating system:

  • Windows: SQL Server authentication and Integrated Windows Authentication

  • Linux: SQL Server authentication

Create a PostgreSQL User

Create a user that can access that database with the default properties. This will ensure the user has all required privileges. Alternatively the set up should be performed as recommended by your Database Administrator who must grant the user access to the database and at least the following permissions:

  • create sequence

  • create table