WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Manually running database configuration scripts

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

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=true, the config_event_database performs both steps automatically. However, if your database response file specifies EXECUTE_SCRIPTS=false, you must complete the database configuration by manually running the generated scripts.

The default value in the sample database response file specifies EXECUTE_SCRIPTS=true. 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

  1. 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 ESB run-time environment in which you are configuring the event database.

  2. 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
  3. 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 ESB run-time environment in which you are configuring the event database.

  4. 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 or cluster where you want to configure the JDBC provider, if scope is server or cluster. (If scope is cell or node, this parameter is ignored.

What to do next

After the event database is configured, you must restart the application server.


Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\doc\tcei_install_runDbScripts.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)