Software AG Products 10.5 | Using CentraSite | Runtime Governance | Virtual Service Asset Management | Managing Virtual Service Assets through CentraSite Control | Virtual SOAP Service Management | Configuring Virtual Services | Configuring the Entry Protocol Step
 
Configuring the Entry Protocol Step
The Entry Protocol step specifies the protocol (HTTP, HTTPS or JMS) and SOAP format (1.1 or 1.2) of the requests that the Virtual Service will accept.
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.
*To configure the Entry Protocol step
1. In CentraSite Control, go to Asset Catalog > Browse.
2. In the displayed list of asset types, select Virtual Service.
3. In the Assets pane, right-click the Virtual Service you want to configure, and click Details.
The Virtual Service Details page is displayed.
4. In the Processing Steps tab, click Entry Protocol.
5. In the Entry Protocol tab, specify the protocol (HTTP, HTTPS, or JMS) for the Virtual Service to accept requests, and click OK.
Note:CentraSite supports HTTP version 1.1 only.
Field
Description
Protocol
Select the protocol over which the Virtual Service will accept requests. The possible options are: HTTP, HTTPS, JMS.
Note that you can select both HTTP and HTTPS if required.
Important:
Before you deploy a Virtual 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 have selected the JMS option, specify the Integration Server's JMS Trigger name. The alias must include the JNDI destination name and the JMS connection factory.
Format
Select the SOAP format (SOAP 1.1 or SOAP 1.2) of the requests that the Virtual Service will accept.