If your database response file specifies EXECUTE_SCRIPTS=false,
you must complete the database configuration process by manually running the
generated scripts.
Why and when to perform this task
To run the scripts manually:
Steps for this task
- Go to the profile_path/event/dbscripts/db2zos
directory.
Replace profile_path with the path to the directory
containing the profile for the WebSphere ESB run-time environment
in which you are configuring the event database.
- Use the SQL Processor Using File Input (SPUFI) to load and run
the generated DDL scripts. Run the scripts in the following order:
- $WAS_HOME/event/dbscripts/db2zos/ddl/cr_db.db2
- $WAS_HOME/event/dbscripts/db2zos/ddl/cr_db_catalog.db2
- $WAS_HOME/event/dbscripts/db2zos/ddl/cr_tbl.db2
- $WAS_HOME/event/dbscripts/db2zos/ddl/cr_tbl_catalog.db2
- $WAS_HOME/event/dbscripts/db2zos/ddl/ins_metadata.db2
- $WAS_HOME/event/dbscripts/db2zos/ddl/catalogSeed.db2
- Go to the profile_path/event/dsscripts/db2zos
directory.
Replace profile_path with the path to the directory
containing the profile for the WebSphere ESB run-time environment
in which you are configuring the event database.
- Run the $WAS_HOME/event/dsscripts/cr_db2zos_jdbc_provider script
to create the event data source. Specify the scope at which the
JDBC provider is to be configured:
cr_db2zos_jdbc_provider scope [server_name]
What to do next
After the event database is configured, you must restart the application
server.