If your database response file specifies EXECUTE_SCRIPTS=NO, you
must complete the database configuration process by manually running the generated
scripts.
Why and when to perform this task
Database configuration is a two-step process. The config_event_database script
first generates database-specific scripts for your environment; these generated
scripts then create the database and data sources. If your database response
file specifies EXECUTE_SCRIPTS=YES, the config_event_database performs
both steps automatically. However, if your database response file specifies EXECUTE_SCRIPTS=NO,
you must complete the database configuration by manually running the generated
scripts.
The default value in the sample database response file specifies EXECUTE_SCRIPTS=YES.
Unless you have changed this value in your customized response file, you do
not need to run the generated scripts manually.
To manually run the
generated scripts:
Steps for this task
- Go to the database-specific subdirectory containing the generated
scripts for creating the event database.
The scripts are placed
in one of the following directories, depending upon the database software
you are using:
- profile_path/event/dbscripts/cloudscape
- profile_path/event/dbscripts/db2
- profile_path/event/dbscripts/oracle
Replace profile_path with the path to the directory
containing the profile for the WebSphere Process Server runtime
environment in which you are configuring the event database.
- Run the generated database creation script for your operating system
and database software:
Type |
Operating system |
Database script |
Cloudscape |
Windows |
cr_event_cloudscape.bat |
Cloudscape |
Linux/UNIX |
cr_event_cloudscape.sh |
DB2 |
Windows |
cr_event_db2.bat |
DB2 |
Linux/UNIX |
cr_event_db2.sh |
Oracle |
Windows |
cr_event_oracle.bat |
Oracle |
Linux/UNIX |
cr_event_oracle.sh |
- Go to the database-specific subdirectory containing the generated
scripts for creating the JDBC data sources.
The scripts are
placed in one of the following directories, depending upon the database software
you are using:
- profile_path/event/dsscripts/db2
- profile_path/event/dsscripts/db2zos
- profile_path/event/dsscripts/cloudscape
- profile_path/event/dsscripts/oracle
Replace
profile_path with the path to the directory
containing the profile for the
WebSphere Process Server runtime
environment in which you are configuring the event database. If you are using
a database that is installed on another server, copy the entire folder (for
example, the
profile_path/event/dsscripts/db2 folder) of
generated database scripts over to that server. On the database server, open
a command prompt to the location of the copied scripts, and run the script
to create the database:
- Windows systems
- cr_event_db.bat server username
- Linux and UNIX systems
- cr_event_db.sh server username
The parameters are as follows:
- server
- Indicates that you are executing this command on the same computer as
the database
- username
- A valid user id for accessing the database.
- On the server where you originally generated the scripts, run the
generated JDBC configuration script for your operating system and database
software:
Type |
Operating system |
JDBC configuration script |
Cloudscape |
Windows |
cr_cloudscape_jdbc_provider.bat |
Cloudscape |
Linux/UNIX |
cr_cloudscape_jdbc_provider.sh |
DB2 |
Windows |
cr_db2_jdbc_provider.sh |
DB2 |
Linux/UNIX |
cr_db2_jdbc_provider.sh |
Oracle |
Windows |
cr_oracle_jdbc_provider.bat |
Oracle |
Linux/UNIX |
cr_oracle_jdbc_provider.sh |
Use the following command to run the JDBC configuration script:- Windows systems
- cr_db_jdbc_provider scope [server_name]
- Linux and UNIX systems
- cr_db_jdbc_provider.sh scope [server_name]
The parameters are as follows:
- scope
- The scope at which you want to configure the JDBC provider. The valid
values are cell, node, server,
or cluster.
- server_name
- The name of the WebSphere server where
you want to configure the JDBC provider, if scope is server. (If scope is cell, this parameter is ignored.
Note: You will be prompted to provide a user id and password
that is valid on the database server.
What to do next
After the event database is configured, you must restart the application
server.