Creating the database and tables after stand-alone profile creation or augmentation

If you postponed creating the database and its tables while configuring WSRR, you or your database administrator must create the database and its tables manually. You do this using scripts that the Profile Management Tool generates during profile creation or augmentation. These instructions assume that you configure a single database.

About this task

attention You must create the database using the UTF-8 code set. No other code sets will function correctly.

Procedure

Go to the directories containing the table creation scripts and copy the scripts to your database server. By default, the location is: profile_root/dbscripts/WSRR/db_type The variable db_type represents the supported database product. See the Creating the WSRR database manually topic under related links for more information on database creation scripts, but note that many of the tasks described in these topics have been completed for you by the profile creation.
Use your standard database definition tools, native commands, and procedures to configure the database for WSRR, activity logging, and service integration bus. Run the script files in the order shown.
1. Run the following scripts to configure the database for WSRR, activity logging, and service integration bus:
  1. createWsrrDb.sql to configure the database for WSRR.
  2. createActDb.sql to configure the database for activity logging.
  3. createSibDb.sql to configure the database for the service integration bus.
2. DB2® and DB2 Express® only: createWsrrTablespace.sql to create the WSRR Tablespaces.
3. Run the following scripts to create tables for WSRR, activity logging, and service integration bus:
  1. createWsrrSchema.sql to create the WSRR schema.
  2. createWsrrTables1.sql to create the WSRR tables.
  3. createWsrrProcs.sql to create the WSRR stored procedures.
  4. createWsrrTables2.sql to create additional WSRR tables.
  5. createActSchema.sql to create the activity logging schema.
  6. createActTables.sql to create the activity logging tables.
  7. createSibSchema.sql to create the service integration bus schema.
  8. createSibTables.sql to create the service integration bus tables.

What to do next

After the tables are successfully created , before starting the server, be sure the database is running even if it is installed locally. Then start the server from the profile's First steps console to ensure there are no errors. You can check the SystemOut.log and SystemErr.log files for errors. These files are found in the following location:

profile_root/logs/server_name.