Creating an SQL Server database

Create a Microsoft SQL Server database before installing Application Engine.

About this task

Tip: If you need to know which database versions are supported for your installation, use this IBM Support page to generate a software compatibility report.

Procedure

  1. To configure XA transactions for SQL Server, see Configuring XA Transactions.
    Note that Windows Authentication is not supported.
  2. To create the Application Engine database, run the following command on your local or remote database server:
    create database APP_ENGINE_DB_NAME;
    
    where APP_ENGINE_DB_NAME is the database name for the Application Engine database, for example, AAEDB
    Note: The database must be created by the database administrator who can then assign these roles to the database users.
  3. Create the users and schemas for the SQL Server databases.
    1. If you haven't already done it, create an SQL Server login account for the database user of your database.
      Note: The SQL Server login that is created must not have SYSADMIN privileges. If the login user has SYSADMIN privileges, the specified schema value is ignored for database connections by SQL Server because the sysadmin user's default schema is always dbo.
      For example, if sqluser is the database username and secret1 is the password, run the following command:
      USE MASTER
      GO
      CREATE LOGIN sqluser WITH PASSWORD='secret1'
      GO
      
    2. If you haven't already done it, update the master database to grant permission for XA transactions for the login account.
      For example, if sqluser is the database username, run the following command to update the master database (where login_account is the same login account that you used in the previous step):
      USE MASTER
      GO
      CREATE USER sqluser FOR LOGIN login_account WITH DEFAULT_SCHEMA=sqluser
      GO
      EXEC sp_addrolemember N'SqlJDBCXAUser', N'sqluser';
      GO
    3. For the database that you created, set the default schema for the SQL Server login. In SQL Server, the default schema name that is associated with a user must be the same as the username. You must create an ordinary database user and assign the required rights to the user instead of using a super user, such as sa or the user who created the database. This is because the default schema for the super user is dbo and you cannot change this.
      For example, if app_engine_user is the database username, run the following command:
      USE APP_ENGINE_DB_NAME
      GO
      CREATE USER app_engine_user FOR LOGIN login_account WITH DEFAULT_SCHEMA=app_engine_user
      GO
      EXEC sp_addrolemember 'db_ddladmin', 'app_engine_user';
      EXEC sp_addrolemember 'db_datareader', 'app_engine_user';
      EXEC sp_addrolemember 'db_datawriter', 'app_engine_user';
      GO
    Restriction: For all database users, note the following restrictions:
    • You cannot assign the user to the system administrator (SYSADMIN) role.
    • You must map the user to the master database with the SqlJDBCXAUser role.
  4. If IBM Business Automation Application data persistence is enabled, it needs one object store from IBM FileNet® Content Manager. You can either reuse the existing one and specify it for the object_store_name parameter or create one named something like AEOS, which stands for application engine object store.
    • To create the databases for IBM FileNet Content Manager, create a database for the Content Platform Engine Global Configuration Database (GCD) and one database for the content stores. For more information, see Preparing the databases.
    • To create one object store for Business Automation Application data persistence but not reuse the existing one, you must create one database, such as one named AEOSDB. For more information, see Creating a Content Platform Engine database for SQL Server.
  5. Optional: To use your own JDBC driver, complete the following steps.
    1. Package your JDBC files into a compressed file and use the sc_drivers_url configuration parameter to download them from an accessible web server. Follow the steps in Optional: Preparing customized versions of JDBC drivers and ICCSAP libraries.
    2. Add the customized JDBC driver information to the configuration parameters. Set application_engine_configuration.use_custom_jdbc_drivers to true in the configuration parameters. See Application Engine configuration parameters.

What to do next

To protect the configuration data you are going to enter, see Creating secrets to protect sensitive configuration data.