A stand-alone configuration has a single node running an
application server and one daemon server in a single z/OS® system
or LPAR. When you use a DB2® database you must make considerable
changes to the response file, and you must set up and configure the
database. If you want to quickly set up a stand-alone configuration
for evaluation or demonstration purposes, you might prefer to use
a Derby database instead.
Before you begin
Before you configure
WebSphere® ESB, you must complete
the following tasks:
Procedure
- Stop the server.
- Increase the OMVS time limit to allow the product configuration
script time to complete. In an MVS™ console
enter the following command:
SETOMVS MAXCPUTIME=86400
- Access the USS command shell, then switch to the administrator
user ID. For example:
su wsadmin
- Change directory to the application server bin directory. For example:
cd /WebSphere/V6R1/AppServer/bin
- Run thezWESBConfig.sh configuration script with
the absolute path of your edited response file. For example:
zWESBConfig.sh -augment -response /working_directory_path/standAloneProfileDB2.rsp
Where working_directory_path is the location of the standAloneProfileDB2.rsp file that you have
edited.
- Wait for the configuration to run.
When the script has finished running, review the messages that are
written to the console. If the script has run successfully, no error
messages are displayed and the informational messages state augmenting profile(s) complete.
- Back up the data sets that contain the stand-alone server
configuration.
Results
The stand-alone server has now been augmented with
WebSphere ESB functions and
the DDL scripts that you need to run to create the database objects
have been generated.
What to do next
You can now run the DDL scripts to create the DB2 database
objects. See
Create and
configure the DB2 database objects.