+

Search Tips   |   Advanced Search

Web service gateway instances [Settings]

A web services gateway allows us to configure specific endpoint listeners and deploy gateway and proxy services to those listeners.

To view this page in the console, click the following path:

  • Service integration -> Buses -> bus_name -> [Additional Properties] Web service gateway instances -> instance_name.

    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. We can also map multiple target services to a single gateway service, and configure proxy services.

    We create web services gateway instances to partition the total set of gateway and proxy services into logical groups to allow simpler management. Note that 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.


    Configuration tab

    The Configuration tab shows configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.


    General Properties

    Name

    The name of the web services gateway instance.

    This name must be unique, and it must obey 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: \ / , # $ @ : ; " * ? < > | = + & % '

    Required Data type
    Yes Custom

    Description

    An optional description of the web services gateway instance.

    Required Data type
    No Text area

    Gateway namespace

    The namespace assigned to this gateway for use in WSDL generation.

    This is used as the namespace 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.

    Required Data type
    Yes Custom

    Default proxy WSDL URL

    The URL of the default proxy WSDL description for use with proxy services.

    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 creating or modify a proxy service configuration.

    Required Data type
    No String


    Additional Properties

    Gateway services

    A gateway service provides the configuration of the web service enablement of a service destination, along with the information that maps to one or more target destinations.

    Proxy services

    A proxy service provides the configuration of the web service enablement of a service destination that is able to act as a proxy for a variety of providers.


    Related tasks

  • Create a new gateway instance

  • Modify an existing gateway instance


    Related information:

  • Administrative console buttons

  • Administrative console preference settings Reference topic