You configure each proxy service for a specific gateway instance, so you must create the gateway instance
before you can configure any proxy services for it.
For an overview of proxy operation, see JAX-RPC handlers and proxy operation.
You can create
a new proxy service configuration through the command line, or through
the administrative console. To create a new proxy service configuration through
the administrative console, complete the following steps:
- 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 you want 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.
- Create
a new JAX-RPC handler configuration for the handler that sets the target
endpoint for this service.
- 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.
- Start the administrative console.
- In the navigation pane, click bus_nameinstance_name. The proxy
services collection form is displayed.
- Click New. The New proxy
service wizard is displayed.
- 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.
- Specify the proxy service name, proxy port point, service destinations and mediations.
Note: - 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 on 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 you 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 you must assign it
to a bus member; If you set the Request mediation or the Response
mediation property value to (none), you must also change
the corresponding bus member property value to (none). If you do not do this, no error message is displayed but
you cannot move on to the next wizard panel. If
you do not do this, the administrative 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.
- Select endpoint listeners for the inbound configuration of this
proxy service.
- Click Finish.
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.
Ensure that all service requesters append an
operationMode HTTP
query string parameter to the Web address for the proxy service. The value
of this parameter is either
oneway or
requestResponse,
and the default is
requestResponse. For example, if the Web
address of the proxy service is
http://host_name:port_number/wsgwsoaphttp1/soaphttpengine/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/wsgwsoaphttp1/soaphttpengine/your_bus/ProxyService/ProxyServiceInboundPort?operationMode=oneway