WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Creating a new proxy service configuration through the command line

Use this task to set the gateway to act purely as a proxy for your service, and use JAX-RPC handlers to set the endpoints for incoming request messages for the service.

Before you begin

The command described in this topic is run using the AdminTask object of the wsadmin scripting client.

This command is only valid when run against WebSphere Application Server Version 6 application servers. Do not run it against earlier versions.

Command-line help is provided with each of the service integration technologies commands:
  • For a list of all the available gateway commands, plus a brief description of each, enter the following command:
    wsadmin> $AdminTask help WSGateway
  • For detailed help on a given command, enter the following command:
    wsadmin> $AdminTask help command_name

For additional details of the command properties, see the related reference topic.

Purpose

This command creates a new ProxyService object with an associated InboundService object, and a TargetService object with an associated OutboundService object.

You then use a service integration technologies command to add any InboundPort objects that are associated with the InboundService object. For more information see the worked example at the end of this topic.

Command name
createWSGWProxyService
Target
ObjectName of the gateway instance within which the proxy service is created.
Result
ObjectName of the created ProxyService object.

The command creates the proxy request destination and corresponding reply destination. The proxy request destination is configured to update the reply path to add the proxy reply destination. If a destination with the specified or default names already exists, the command fails.

If a gateway service or proxy service with the same name already exists, the command fails.

If you specify the name of the proxy request destination, the proxy service destination and port destinations are created with names derived from the proxy request destination name. Otherwise, the proxy service destination and port destinations are created with names derived from the proxy service name. The proxy service destination name is created by adding "ProxyService" to the proxy request destination or proxy service name. Each proxy port destination is then named after the proxy service destination, followed by a colon (":"), followed by the port name, followed by "Port". If a destination with any of these names already exists, the command fails.

Either specify the node and server, or specify the cluster. If there is no messaging engine defined for the specified node and server or cluster, the command fails.

The command creates an OutboundService object, with the same name as the proxy service. This new outbound service uses the created destinations, the supplied localization, and either the default proxy WSDL location for the gateway instance or (if specified) the location of the proxy WSDL file. The new outbound service is associated with the ProxyService object.

The proxy WSDL must have only a single service element. If there are multiple ports within the single service element, an outbound port object is created for each one.

The proxy WSDL should never come from UDDI, so only a Web address is supported for the default and overridden proxy WSDL location.

The command uses the proxy destination to create an InboundService object with the same name as the proxy service, and uses the default or specified proxy WSDL location as the template WSDL location.

Required Parameters

name
The proxy service name.

Conditional Parameters

node
The node in which the destinations is localized.
server
The server in which the destinations is localized.
cluster
The cluster in which the destinations is localized.

Optional Parameters

requestDestination
The name of the proxy request destination.
replyDestination
The name of the proxy reply destination.
wsdlLocation
The location of the proxy WSDL file. This is a Web address.

Example

set proxyService [$AdminTask createWSGWProxyService $wsgw {-name "MyProxyService" -node "MyNode" -server "server1"}]
The following is a minimal example of a sequence of commands to create a fully-functional proxy service with inbound and outbound SOAP over HTTP protocol attachments:
  1. Create the proxy service, where wsgw is the gateway instance:
    set proxyService [$AdminTask createWSGWProxyService $wsgw {-name "ProxyService" -node "MyNode" -server "server1"}]
  2. Get the inbound service for the gateway service, where busName is the name of the service integration bus:
    set inServiceName [$AdminConfig showAttribute $proxyService "inboundServiceName"]
    set inService [$AdminConfig getid /SIBus:$busName/SIBWSInboundService:$inServiceName/]
  3. Add a SOAP over HTTP port, where the SOAP over HTTP 1 endpoint listener is already configured:
    set inPort [$AdminTask addSIBWSInboundPort $inPort {-name "SOAPHTTPPort" -endpointListener "soaphttp1" -node "MyNode" -server "server1"}]
  4. Complete the configuration of the inbound and outbound services and ports. For example, apply JAX-RPC handlers or WS-Security.
Related concepts
JAX-RPC handlers and proxy operation
Related tasks
Working with proxy services
Creating a new proxy service configuration
Modifying an existing proxy service configuration
Related information
Proxy services settings

Reference topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\ref\rwsg_cli_proxy_new.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)