The Entry Protocol Step (SOAP)

This step allows you to bridge protocols between the consuming application and the native service. For example, suppose you have a native service that is exposed over JMS and a consuming application that submits SOAP requests over HTTP. In this situation, you can configure the virtual service’s Entry Protocol step to accept HTTP requests and configure its Routing Protocols step to route the request to the Web service using JMS.

Besides using the Entry Protocol step to resolve protocol differences between the consumer and the native service, you might use this step to intentionally expose a virtual service over a particular protocol. For example, if you have a native service that is exposed over HTTP, you might expose the virtual service over JMS simply to gain the asynchronous-messaging and guaranteed-delivery benefits that one gains by using JMS as the message transport.

Note:

CentraSite supports HTTP version 1.1 only.

In this field...

Specify...

Protocol

The protocol (HTTP, HTTPS, or JMS) over which the virtual service will accept requests.

Note that you can select both HTTP and HTTPS if needed.

Important:

Before you deploy a service over HTTPS, ensure that the Integration Server on which the Integration Server is running has been configured for SSL. In addition, make sure you specify an HTTPS port in the Integration Server’s Ports Configuration page. (In the Integration Server Administrator, go to Solutions > Mediator > Administration > General and specify the port in the HTTPS Ports Configuration field.) For details on the Port Configuration page, see Administering webMethods Mediator.)

JMS Provider Alias

If you selected JMS, specify the Integration Server's JMS Trigger name. The alias must include the JNDI destination name and the JMS connection factory.

Format

The SOAP format (SOAP 1.1 or SOAP 1.2) of the requests that the virtual service will accept.