Create a new gateway instance

Within each service integration bus we can create multiple gateway instances. We create web services gateway instances to partition the total set of gateway and proxy services into logical groups to allow simpler management. The gateway provides you with a single point of control, access and validation of web service requests, and we can use it to control which web services are available to different groups of web service users.

For a high-level task view of how you configure the web services gateway as part of an overall bus-enabled web services configuration, see Enable web services through the service integration bus.

Before we can work with the web services gateway you must Plan the bus-enabled web services installation, ensure that every stand-alone server or cluster that is to play a bus-enabled web services role is a member of a service integration bus (refer to Configure the members of a bus) and create a Service Data Objects (SDO) repository on every stand-alone server or cluster that is to play a bus-enabled web services role.

Bus destinations are already partitioned by the service integration bus, so each gateway instance is limited to gateway and proxy services within the same bus. However, gateway services can then map to target services that are available on other buses.

To create a new gateway instance...

1. Start the console.

2. In the navigation pane, click Service integration -> Buses -> bus_name -> [Additional Properties] Web service gateway instances. The gateway instances collection form is displayed.

3. Click New. The gateway instances settings form is displayed.

4. Type the following general properties:

   Name

   Type the name by which the gateway instance is known. This name must be unique, and it must follow the following syntax rules:

   • It must not start with "." (a period).

   • It must not start or end with a space.

   • It must not contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % '

   Description

   Type the (Optional) description of the gateway instance.

   Gateway namespace

   Type the namespace to use for the gateway services in exported WSDL documents. There is no fixed syntax for the gateway namespace, but whatever name you choose is likely to be more effective if it observes the following guidelines:

   • The name begins with urn:

     See the guidance on Internet standards for the syntax of Uniform Resource Names (URNs) at http://www.ietf.org/rfc/rfc2141.txt.

   • The name is globally unique.

   • The name reflects the company name.

   Default proxy WSDL URL

   Either leave this field blank if the supplied generic template WSDL file is to be used, or type the location (web address) of our own equivalent template WSDL file.

   A gateway service that runs in proxy mode has no actual target services and therefore no WSDL document that the gateway can use to configure the service invocation. A generic template WSDL file is used to configure the basic parameters for the invocation call. For more information, see JAX-RPC handlers and proxy operation.

   We can also override the default proxy WSDL file and supply an alternative WSDL file for an individual proxy service when you create a new proxy service configuration or modify an existing proxy service configuration.

5. Click OK.

Results

If the processing completes successfully, the list of gateway instances is updated to include the new gateway instance. Otherwise, an error message is displayed.

What to do next

We are now ready to create a gateway service or create a proxy service for this gateway instance.

Subtopics

• Modify an existing gateway instance
  Modify the configuration of an existing gateway instance.

• Delete gateway instances
  Use this task to delete gateway instances using the console.

Related information:

Web service gateway instances [Settings]