Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web services - Bus enabled web services > Enable web services through the service integration bus > Configure web services for a service integration bus > Work with the web services gateway

Create a new proxy service configuration

We can set the web services gateway to act purely as a proxy for your service, then use JAX-RPC handler lists to set the endpoints for incoming request messages for the service.

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.

You configure each proxy service for a specific gateway instance, so create the gateway instance before you can configure any proxy services for it.

Decide which method to use to configure these resources. You can create a new proxy service by using the admin console as described in this task, or by using the createWSGWProxyService command.

When you create a new proxy service configuration, the gateway takes no action with regard to that service other than to invoke it. When you configure a proxy service, you also configure a JAX-RPC handler list that uses the javax.xml.rpc.service.endpoint.address to set the target endpoint for the service. You then attach the handler list to the inbound port for the proxy service.

A proxy service configuration has no actual target services and therefore no WSDL that the gateway can use to configure the service invocation. A generic proxy WSDL file is used to configure the basic parameters for the invocation call (for example which binding to use), but you can override the default by supplying your own equivalent generic proxy WSDL file. If the JAX-RPC handler list is not deployed, then the gateway attempts to send all requests to the fake web address specified in the <soap:target address> tag in the proxy WSDL file.

For more detailed information, see JAX-RPC handlers and proxy operation.

To create a new proxy service configuration by using the admin console, complete the following steps:

Procedure

1. Create a JAX-RPC handler that uses the javax.xml.rpc.service.endpoint.address to set the target endpoint for the service. It is up to you to decide how to establish the target endpoint, and to create and configure the javax.xml.rpc.service.endpoint.address JAX-RPC handler. For information about creating JAX-RPC handlers, see the IBM developerWorks article A developer introduction to JAX-RPC, Part 2: Mine the JAX-RPC specification to improve web service interoperability.

2. Create a new JAX-RPC handler configuration for the handler that sets the target endpoint for this service.

3. Create a new JAX-RPC handler list, select the handler that sets the target endpoint for this service and add it to the handler list.

4. Start the admin console.

5. In the navigation pane, click Service integration -> Buses -> bus_name -> [Additional Properties] Web service gateway instances -> instance_name -> Proxy Services . The proxy services collection form is displayed.

6. Click New. The New proxy service wizard is displayed.

7. Use the wizard to create the new proxy service configuration by completing the following steps. For more information about the properties that you set with the wizard, see Proxy services settings.
   1. Specify the proxy service name, proxy port point, service destinations and mediations.

      • Choose a proxy service name that is unique across all gateway and proxy services within the current gateway instance. If you enter a name that is not unique, an error message is displayed.
      • The proxy port point is the point at which the proxy port destination is to be located.
      • You need not provide proxy destination names. If you leave either of these fields blank, a default name is generated for you when the wizard completes its operation. The default names are not displayed in the panel. They are constructed as follows:
        • The request destination name is the same as the proxy service name. For example: myProxyService.
        • The reply destination name is the same as the request destination name, followed by "Reply". For example: myProxyServiceReply.

      • The lists of available mediations contain all mediations that are currently deployed to this service integration bus. If we have created a mediation and deployed it to the bus, then it is available for selection in both these lists. If you do not want to use a mediation with this proxy service, select none from either or both selection lists.
      • Bus members are application servers or clusters that are added to this bus. The Request mediation bus member and the Response mediation bus member properties define the bus members to which the corresponding mediation is assigned. If you select a mediation, then assign it to a bus member; If you set the Request mediation or the Response mediation property value to (none), also change the corresponding bus member property value to (none).

        If you do not do this, the admin console displays an error message.

      • A generic proxy WSDL file is used to configure the basic parameters for the invocation call (for example which binding to use), but you can override the default by typing the location of your replacement generic WSDL file in the Proxy WSDL override URL field.

   2. Select endpoint listeners for the inbound configuration of this proxy service.

      See Endpoint listeners and inbound ports: Entry points to the service integration bus.

8. Click Finish.

Results

If the processing completes successfully, the list of proxy services for this gateway instance is updated to include the new proxy service. Otherwise, an error message is displayed.

What to do next

Ensure that all service requesters append an operationMode query string parameter to the address for the proxy service. The value of this parameter is either oneway or requestResponse, and the default is requestResponse. For example:

• For HTTP operation, if the web address of the proxy service is

  http://host_name:port_number/wsgwsoap//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  1/soap//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  engine
  /your_bus/ProxyService/ProxyServiceInboundPort
  

  then requesting clients indicate that they are sending a one-way request by using the following URL:

  http://host_name:port_number/wsgwsoap//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  1/soap//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  engine
  /your_bus/ProxyService/ProxyServiceInboundPort?operationMode=oneway
  

• For JMS operation, if the JMS address of the proxy service is

  jms:/queue?destination=jndi_queue&connectionFactory=
  jndi_factory&targetService=your_bus/ProxyService/ProxyServiceInboundPort
  

  then requesting clients indicate that they are sending a one-way request by using the following URL:

  jms:/queue?destination=jndi_queue&connectionFactory=
  jndi_factory&targetService=
  your_bus/ProxyService/ProxyServiceInboundPort&operationMode=oneway
  

• Modify an existing proxy service configuration

  Modify the configuration details for a proxy service.

• Delete proxy service configurations

  Use this task to delete proxy service configurations using the admin console.

JAX-RPC handlers and proxy operation

Related

deleteWSGWProxyService command
createWSGWProxyService command
Proxy services [Settings]

+

Search Tips   |   Advanced Search