Subscribe to a WSDL Offered as a JMS Data Source
Introspection properties are available for both JMS and HTTP ports.
• For HTTP ports and operations only, you can specify the timeout parameter in milliseconds, or type zero for no timeout, or leave the entry null for an operation where the port setting is to take precedence.
• For JMS ports:
— The Connector should be specified to ensure functionality of the JMS data source connection pools. JMS connectors should be installed by an administrator. See “Configuring TDV for Using a JMS Broker” in the TDV Administration Guide.
— The specified JMS Destination can be changed to take advantage of different queue destination aliases that offer the same service.
— Delivery Mode can be set to persistent so that messages are written to disk as a safeguard against broker failure. Non-persistent messages are not written to disk before acknowledgment of receipt.
— Message Expiry specifies the period of message validity in the broker queue. An entry of 0 specifies no expiration, while a null entry for an operation specifies that the port setting is to take precedence.
— Operations or messaging priority can be set to an integer of 1 through 9, where 9 is the highest priority.
— Default Timeout is a setting for the consuming client, and it can be set to some duration (in milliseconds). An entry of zero means no timeout, and a null entry specifies that the default takes precedence.
— Individual JMS operations under the port can be configured with a Message Type of Bytes or Text and with specific time-outs tailored to the operation.
If you need to review or change configurations for a Web service, open the Web service from Studio, click the Add/Remove Resources button, make required changes, and reintrospect the data source. For more details about introspection, refer the User Guide, Chapter Retrieving Data Source Metadata.