Most of the Meridian Enterprise Server configuration data is stored in a configuration database. This database can be hosted by the same database server that is used to host the other Meridian Enterprise Server data. This database is not created automatically during Meridian Enterprise Server installation. You must provide the configuration database connection parameters as a separate task described in this topic.
To view or edit existing configuration database connection parameters and Meridian Enterprise Server cluster configuration, see View And Edit the Connectivity Settings.
Errors can occur If the amount of disk space allowed for the configuration database is reduced or restricted. We highly recommend that you allow unlimited growth of the database, which is the default when the database is created by the task below and the scripts.
Notes about this Task
You will need the following information to complete this task:
-
The credentials of a domain account under which to run the Meridian Enterprise Server service.
-
The credentials of a domain account for the application pool under which the Meridian Enterprise Server web application will run.
-
The name of the server where Meridian Enterprise Server is installed and the number of the TCP port that it is listening to (if on a different server than the Meridian Enterprise Server web application).
-
For SQL Server, the connection parameters for a new or existing database. If you would prefer to create the database manually, an empty database with default parameters is sufficient. If you also want to create a Meridian Explorer repository database manually, use the script in SQL Server Database Creation Script.
-
For Oracle, the user name for a new or existing database. If you would prefer to create the database with a script instead, see Oracle Database Creation Script.
-
An existing database (SQL Server) or user (Oracle schema) can be used but we recommend that you can create a new database or user dedicated to the Meridian Enterprise Server configuration database and separate from any Meridian Explorer repositories.
In Meridian Enterprise Server 2021, before you can create an Oracle configuration database, you must first run the Oracle Database Creation Script and then run this SQL command as the user that you specified in the script:
CREATE TABLE BCLayerTranslationTable
(
ID INTEGER NOT NULL,
Name nvarchar2(255) NOT NULL,
Description nvarchar2(1024) NULL,
CONSTRAINT PK_BCLayerTranslationTable PRIMARY KEY (ID),
CONSTRAINT UK_TableName UNIQUE (Name)
)Create the Configuration Database
To create the configuration database:
-
Install the Meridian Enterprise Server software as described in Install Meridian Enterprise Server.
-
Set the credentials for the BC Enterprise Server service in the Services applet.
-
Set the credentials for the BCEnterprise application pool in IIS Manager.
-
Attempt to open the configuration page of the web application (http://<ServerName>/BCEnterprise/config.aspx).
The web application will attempt to connect to the configuration database. When this fails because the configuration database has not yet been created, the Configuration Database page appears.
-
Click options or type values for the database connection parameters using the descriptions in the following table.
-
Click Register.
The configuration database is created or connected using the parameters that you entered.
| Parameter | Description |
|---|---|
| Provider |
SQL Server or Oracle |
|
Server (SQL Server) or SID (Oracle) |
The name of the database server and/or instance where you want to create the configuration database. The names you must specify depend on the type of database server and the client configuration. For example: MyServer — SQL Server Standard or Enterprise MyServer\MyInstance — SQL Server Express or another edition that created a named instance when the software was installed. MyInstance — Oracle network alias for the database. This list includes the alias names found in all tnsnames.* files on the computer unless you have set in the Oracle client configuration the location of a specific tnsnames.ora file to be used. |
|
Type (SQL Server only) |
The authentication method to use to connect to the configuration database. |
|
User name |
The name of the user to connect to the configuration database. Note:
The account name should follow the Oracle rules described in Schema Object Names and Qualifiers. |
| Password | The password of the user to connect to the configuration database. |
|
Database (SQL Server only) |
To use an existing database:
To create a new database:
|
|
Primary path (SQL Server only) |
Type the path on the database server where to store the configuration data. |
|
Log path (SQL Server only) |
Type the path on the database server where to store the configuration database logs. |
