A stand-alone configuration is the simplest configuration
type in WebSphere® ESB for z/OS®. A stand-alone configuration has a single node running an application
server and one daemon server in a single z/OS® system or LPAR. Use
a Derby database only for a test system. Use a DB2® database
for a production system.
Before you begin
Before you can configure
WebSphere ESB, you must complete
the following tasks:
Procedure
- Run the zWESBConfig.sh configuration script with
the absolute path of your edited response file. For example:
zWESBConfig.sh -augment -response /working_directory_path/standAloneProfile.rsp
Where working_directory_path is the location of the standAloneProfile.rsp file that you have
edited.For more information about the command, see zWESBConfig.sh script.
- 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.
- Start the server. See Starting stand-alone servers for more information.
- Verify that WebSphere ESB information
appears in the administrative console:
- Open the administrative console by opening a browser
window and typing the URL of the server that you want to view. For example:
http://server_name.domain_name:port_number/admin
- Log in to the administrative console.
- Verify that you can see WebSphere ESB on the Welcome
page. You can click on WebSphere ESB for more information.
- Navigate around the administrative console to check
applications and messaging engines are started.
- Back up the data sets that contain the stand-alone server
configuration.
What to do next
You can now deploy applications to the stand-alone server.