Creating a New Enterprise Gateway Process

Contents

Overview

This topic describes how to use the createinstance script to create a new Enterprise Gateway process instance from your Enterprise Gateway installation. This feature is optional. You can use it to specify the location of your Enterprise Gateway configuration files to keep them separate from your Enterprise Gateway executables, which makes them easier to maintain.

For example, this enables you to use dedicated Enterprise Gateway processes for high value services and to avoid potential downtime due to lower value services. This makes Enterprise Gateway upgrades and maintenance much easier. In addition to isolating services into different Enterprise Gateway processes, you could also use this feature to create dedicated Enterprise Gateway processes for specific Enterprise Gateway users or user groups.

Running the Createinstance Command

Run the following command in your Enterprise Gateway installation:
Windows INSTALL_DIR\Win32\bin\createinstance
UNIX\Linux INSTALL_DIR/posix/bin/createinstance

Specifying Parameters
You can specify the following parameters to the createinstance command:
-n Specifies the service ID name for the new process instance (for example, my_gateway). This parameter is required.
-d Specifies the directory containing the configuration files for the new process instance. Defaults to the service ID specified using -n (for example, INSTALL_DIR\Win32\bin\my_gateway).
-s Specifies the external services port for the new process instance. Defaults to 8080.
-m Specifies the management services port for the new process instance. Defaults to 8090.
-u Specifies a unique user ID to run the process instance as.
-i Creates an init.d script for the new service instance (starts at boot time).
-I Creates an init.d script for an existing service instance (starts at boot time).
--debug Enables debugging for the createinstance script.
-help Displays help text and exits.

Starting the New Enterprise Gateway Service

When the createinstance script completes, it outputs the location where the configuration files for the new Enterprise Gateway service have been successfully installed and the command to use to execute the process. On Windows, a startinstance.bat file is created in the win32\bin directory of your Enterprise Gateway installation. You can pass this script the location of the newly created Enterprise Gateway configuration, for example: 

startinstance C:\my_gateway

On UNIX, the startinstance script is created in your in the posix\bin directory of your Enterprise Gateway installation. To run this script from any directory, you can add the location of the startinstance script or .bat file to your PATH environment variable.

Connecting to the New Enterprise Gateway Service

When the new Enterprise Gateway service has started, you can test the connection to it using the following URL: 

http://hostname:service-ID/healthcheck:services_port

You can use the Policy Studio to connect to the new Enterprise Gateway service on the following address: 

http://hostname:service-ID:management-port

Further Information
If you encounter any problems with creating a new Enterprise Gateway process, please contact the Oracle Support Team with your queries.