Create an inbound service. An inbound service is a Web interface
to a service that is provided internally (that is, a service provided by your
own organization and hosted in a location that is directly available through
a service integration bus destination). To configure a locally-hosted service
as an inbound service, you associate it with a service destination, and with
one or more endpoint listeners through which service requests and responses
are passed to the service. You can also choose to have the local service made
available through one or more UDDI registries.
Before you begin
You must also create a template WSDL file that describes
the service, and make the WSDL available at a URL or through a UDDI registry.
For information on how to create a WSDL file, see Developing a WSDL file.
You can create
an inbound service through the administrative console as described in this
task, or you can
create
an inbound service through the command line.
Note: If the bus needs
to pass messages through an authenticating proxy server to retrieve WSDL documents,
then you cannot use the administrative console for this task and you must
create your new inbound service through the command line. For more information
see
the
corresponding troubleshooting tip.
Why and when to perform this task
Web service requests and
responses to an inbound service can be sent across any binding (for example
SOAP over HTTP or SOAP over JMS) that is available to the bus. Each available
binding type is represented by an inbound port, and each inbound port is associated
with a binding-specific endpoint listener.
You can control and monitor
access to your inbound services in the following ways:
- You can control which groups of users can access a particular inbound
Web service by making the service available only through specific endpoint
listeners.
- You can associate JAX-RPC handler lists with ports, so that the handlers
can monitor activity at the port, and take appropriate action depending upon
the sender and content of each message that passes through the port.
- You can set the level of security to be applied to messages (the WS-Security
configuration and bindings). The security level can be set independently for
request and response messages.
To create a new inbound service through the administrative console,
complete the following steps:
Steps for this task
- Start the administrative console.
- In the navigation pane, click bus_name. The inbound
services collection form is displayed.
- Click New. The New inbound
service wizard is displayed.
- Use the wizard to create the new inbound service configuration
by completing the following steps. For more information about the properties
that you set with the wizard, see Inbound
services settings.
- Select the service destination and template WSDL location.
Note: The template WSDL is the service-specific WSDL file that you have
created to describe this inbound service.
- Select the service from the template WSDL.
Note: - This option is needed in case there is more than one service in the template
WSDL. The field is filled in for you by default. If there is only one service
in the WSDL, accept the default.
- Specify the name of the inbound service and select the endpoint
listeners.
Note: - You need not supply a name for the inbound service. If you choose not
to supply a name, a default name is created. The default name is derived from
the service destination name, with characters that are invalid for names filtered
out.
- An inbound port is automatically created for each endpoint listener that
you select. Each inbound port is created without a template port, JAX-RPC
handler list or security settings and is given a default name that relates
to the endpoint listener selected. For an overview of the relationship between
endpoint listeners and inbound ports, see Endpoint listeners and inbound ports - entry points to the
service integration bus.
- Define any UDDI publication properties.
- Click Finish.
If the processing completes successfully, the list of inbound services
for this service integration bus is updated to include the new inbound service.
Otherwise, an error message is displayed.
If you want to secure your new inbound service, or apply any JAX-RPC handler
lists to the ports for the service, or publish the service to more
UDDI registries, use the administrative console to modify your inbound service configuration.