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

Modifying an existing inbound service configuration

Modify the configuration details for an existing 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 first associate it with a service destination, then you configure one or more ports (each with an associated endpoint listener) 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.

To list the inbound services, and to view and modify their configuration details, complete the following steps:

  1. Start the administrative console.
  2. In the navigation pane, click Service integration > Buses > [Content Pane] bus_name > Inbound Services. A list of all the inbound services is displayed in an inbound services collection form.
  3. Click the name of an inbound service in the list. The current settings for this inbound service are displayed.
  4. Optional: Click Reload template WSDL to reload the template WSDL file for this inbound service.
    Note:
    • When you create a new inbound service, a copy of the template WSDL file for the service is loaded into a locally-maintained repository. If you change the template WSDL file, you must update the local copy.
    • When you click Reload template WSDL, you launch the command that is described in Refreshing the inbound service WSDL file through the command line. For the command to complete successfully, the conditions must be met that are described in that topic.
    • If the bus needs to pass messages through an authenticating proxy server to retrieve WSDL documents, then you cannot use the Reload template WSDL option and you must launch the refresh WSDL command from the command line. For more information see the corresponding troubleshooting tip.
  5. Modify the general properties. For information about each of these properties, see Inbound services settings.
    Note:
    • When you change an inbound service name, the system looks up all objects that refer to it and updates the name.
    • The template WSDL is the service-specific WSDL file that you create to describe this inbound service. For information on how to create a WSDL file, see Developing a WSDL file.
    • Although logically the template WSDL name and namespace are only required if there is more than one service in the WSDL, the fields that you use to set them are coded within the administrative console as compulsory fields. They are filled in for you by default, so if they are not logically required for your service you should leave the default values. If you remove the value from either field, the administrative console treats the empty field as an error.
    • If you select the option to Enable operation-level security then you must also complete, for this inbound service, the steps described in Password-protecting a Web service operation.
  6. Modify the additional properties.
    1. Modify the inbound ports that are associated with this inbound service. For information about the properties of inbound ports, see Inbound ports settings.
      Note:
      • An inbound port describes the Web service enablement of a service destination on a specific endpoint listener, with associated configuration.
      • Each inbound port is associated with an endpoint listener, and you can control which groups of users can access a particular inbound service by making the service available only through specific endpoint listeners. For more information see Endpoint listeners and inbound ports - entry points to the service integration bus.
      • You can use a JAX-RPC handler list to monitor activity at the port, and take appropriate action (for example logging, or re-routing) depending upon the sender and content of each message that passes through the port. For more information see SIBWS and JAX-RPC handlers.
      • You can use WS-Security to set the levels of security to be applied to messages. The security level can be set independently for request and response messages. For more information see Service integration technologies and WS-Security.
    2. Modify the UDDI publication properties that are used to publish this inbound service to one or more UDDI registries. For information about the UDDI publication properties, see UDDI Publication settings and UDDI registries - Web service directories that can be referenced by service integration technologies.
    3. Modify the custom properties, if any, that you have set for this inbound service. These custom properties are name and value pairs that you can use to set internal system configuration properties. In each pair, the name is a property key and the value is a string value.
    4. Use the publish WSDL files property to export the template WSDL for this inbound service to a ZIP file.

      As a technology preview, the exported ZIP file incudes a version of the WSDL file that has no ports (bindings) defined. This non-bound WSDL is intended for use by your colleagues preparing to deploy an inbound service. It gives you a convenient way of sharing information on the planned deployment details for the service among your team. When you finally deploy the inbound service, the associated WSDL must be complete (that is, it must include the binding information).

      The non-bound WSDL file is always published in the exported ZIP file for the inbound service, along with the bound WSDL file if the inbound service has any ports defined. The ZIP file, named inbound_service_name.zip, therefore always contains the following files:
      • bus_name.inbound_service_nameNonBound.wsdl (this file contains the non-bound service, port and binding for the inbound service).
      • bus_name.inbound_service_namePortTypes.wsdl (this file contains the port type definition for the inbound service).
      If the inbound service has one or more ports, then the ZIP file additionally contains the following files:
      • bus_name.inbound_service_nameService.wsdl (this file contains the service and port elements for the inbound service).
      • bus_name.inbound_service_nameBindings.wsdl (this file contains the binding elements that correspond to the ports for the inbound service).

      If there is an error generating the WSDL then an error page is returned.

  7. Apply the changes.
If the processing completes successfully, the list of inbound services for this service integration bus is redisplayed. Otherwise, an error message is displayed.
Related concepts
Non-bound WSDL
Related tasks
Creating a new inbound service configuration
Deleting inbound services configurations
Publishing a Web service to a UDDI registry
Related reference
Creating a new inbound service configuration through the command line
Refreshing the inbound service WSDL file through the command line
Publishing to UDDI the inbound service WSDL file through the command line
Removing from UDDI the inbound service WSDL file through the command line
Related information
Inbound Services settings
Inbound Ports settings

Task 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\tasks\tjw_in_config.html

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