5 Starting and Stopping Domain Web Servers

This chapter describes how to start and stop Domain Web servers:

• Starting the Domain Web Server

• Stopping the Domain Web Server

• Setting Up Security for the Domain Web Server

Starting the Domain Web Server

The Domain Web server provides Processing Servers and Signaling Servers with HTTP access to the domain configuration and the OSGi bundles for the domain.

It is a Web server that gives HTTP access to the domain configuration, and performs no other functions. The domain configuration must have been created so it can be accessed using the Domain Web server, see Chapter 6, "Managing Domains".

Note:

The Domain Web server is intended for test and evaluation purposes only. In production deployments, the domain configuration should be accessed using a shared file system.

To start the Domain Web server:

1. Open a command line shell.

   Note:

   You must be logged in as a user that has read privileges on the file-system where the domain configuration resides.

2. Change directory to:

   Oracle_home/axia/admin_console

   Where Oracle_home is the Oracle Home directory you defined when you installed the product.

3. Enter:

   ./host.sh directory

   Replace directory with the path to the domain configuration directory.

4. If HTTPS is enabled, enter the keystore password.

5. If Basic Authentication is enabled, enter the user name and password combination to use for HTTP Basic Authentication.

When the Domain Web server is started, Processing Servers and Signaling Servers can access the domain configuration over HTTP or HTTPS.

The port is defined in the property org.eclipse.equinox.http.jetty.http.port. Default value is 9000. See Appendix A, "System Administrator's Reference".

Stopping the Domain Web Server

The recommended way to stop the Domain Web server is to kill the process in which it is running. Refer to the documentation for your operating system for more information.

Setting Up Security for the Domain Web Server

The Domain Web server must be started by a user that has read privileges to the Domain Configuration directory. See Chapter 1, "Configuring Security".