The first thing you have to do is to configure the Database Server. To do this:
Create the Monitor database (i.e. WFMDB)
Create the required TableSpaces in both the Monitor Database (WFMDB) and the EventQueue Database (FMCDB). BI Monitor allows you to control the distribution of the Monitor and the EventQueue Database tables and indexes into a number of TableSpaces that are up to 22 TableSpaces; 19 of them are created in the Monitor Database and three of them are created in the EventQueue Database. The database tables and indices are grouped and categorized so that each category can be assigned to a separate TableSpace.
This number is the maximum number of TableSpaces to which you can assign the database tables and indexes. This means you do not have to create all these TableSpaces, but you can create part of them. In this case, during the deployment steps, you can assign more than one group of tables or indices to the same TableSpace.
Refer to the section named Database Tables and Indexes Allocation with Multiple TableSpaces in this guide for details about the distribution of the Monitor and EventQueue database tables and indexes on multiple TableSpaces.
Adjust the Database authorizations for the User ID that will be used by the BI Monitor to access the database. The following are the required actions on the database that should be used in order to set the needed permissions for the given User ID:
DDL actions
ALTER TABLE
CREATE TABLE & DROP TABLE
CREATE TRIGGER & DROP TRIGGER
DML actions
SELECT
INSERT
UPDATE
DELETE
SELECT FROM SYSIBM.SYSTRIGGERS
SELECT FROM SYSIBM.SYSDUMMY1
Create the Monitor and EventQueue Database Tables by running the DDL files named monitorCreate.sql and eqCreate.sql respectively. These files are located in the <Monitor>/server/docs/ddl folder.
Before running, these files have to be edited in order to update them with the actual Schema and TableSpace name that you have created in the database. To do this:
Open each of these two files in any text editor.
Replace the variables named $TABLESPACE$ and $SCHEMA$ with the actual name of the TableSpace and Schema in each creation statement of the tables and indexes.
For example:
The original statement is:
CREATE TABLE "$SCHEMA$"."SCHEMA_HEADER"("VERSION" INTEGER NOT NULL) IN $TABLESPACE$$
The modified statement should be
CREATE TABLE "WFM"."SCHEMA_HEADER"("VERSION" INTEGER NOT NULL) IN AdminTablespace$
Save and close the file.
Important Notes:
The delimiter used in these files is the Dollar Sign ($). You must set this delimiter in the command that you will use to run these files specifically, otherwise the default DB2 delimiter (;) will be used and the script will fail to execute.
For distributed installation and deployment (where the Database server is located on a z/OS or an OS/390 machine while the WebSphere Application Server is installed and used from a different Windows, AIX or Solaris machine), You must make sure that the Database Client is installed on the client machine where the WebSphere Application Server is installed,and is properly configured and connected to the Database Server that exists on the Mainframe. Consult your database Administrator for information about configuring the DB2 database client to connect to the remote database.