Configuring WebSphere Business Events with installed universal test environment

You can configure WebSphere® Business Events with the installed universal test environment to run your J2C WebSphere Business Event applications.

Procedure

  1. Install the application as well as WebSphere Application Server v7 with feature packs.
  2. Install and configure WebSphere Business Events, either using the typical or the advanced installation options: For a typical installation, see: Installing WebSphere Business Events with a new instance of WebSphere Application Server (Typical option). For advanced installation, see: Installing WebSphere Business Events on an existing WebSphere Application Server instance, with these modifications:
    1. Install WebSphere Business Events using custom install and point to your existing Universal Test Environment installation. Disregard the steps that add feature packs to the server, since you have already installed the WebSphere Application Server during the installation of the application.
    2. Install Object Grid.
    3. Restart the unit test environment. The first line in the SystemOut.log indicates success; for example: WebSphere Platform 7 .....[WXDOG 7.0 cf50902.39719].
    4. Configure WebSphere Application Server. Follow the steps outlined here Configuring WebSphere Application Server. Step 1 asks you to navigate to the <install_dir>/config/was directory and edit the setenv script (setenv.bat on Windows, setenv.sh on Linux and UNIX). Add the following user environment variable WBE_WAS_HOME to point to your Universal Test Environment (<install_dir>SDP/runtimes/base_v7). Steps 10 and 11 involves creating a messaging topic space; after you run the configure_messaging.bat file and the install_app script, you notice some failures regarding the application wberuntimeear not being installed. To correct this problem, remove the messaging setup by typing using configure_messaging.bat -undo. Then run configure_messaging.bat again, and this time script completes without any errors.
    5. Create the repository database. Follow the steps outlined here: Creating the repository database
    6. Configuring your database manager. Follow the steps outlined here: Configuring your database manager. Step 4 asks you to create the database by running configure_db.bat; however, configure_db.bat file does not exist. This file is no longer in the WBE install package. Copy the SQL files for your database from the WebSphere Business Event <install_dir>\config\db directory, create a database either for derby or DB2® using the database tool provided for each following the instructions. From the Data perspective in your workspace, create a data design project and import the SQL files into the project. Connect to the database and run the SQL files against the database to create the tables and columns. Step 5 asks you to create a JDBC data source in the WebSphere Application Server Network Deployment Administrative Console. Although the step states that this is required for embedded Derby only, this step should be followed for all databases. In WebSphere Application Serve, before starting application by running wberuntimeear, create a JDBC provider and resource for your database. You need to point the JDBC provider to your database-specific jars. Make the JNDI name jdbc/repository. This is the default. Create a JAAS authentication and assign that to the resource.
    7. Restart the unit test environment.

Feedback