Web Service Attributes Editor: Port Binding

See Also 

In the WSIT tab's Port Binding section, on the service side, you can configure MTMOM, reliable messaging, and interoperable security policy.

You can set the following options:

• Optimize Transport of Binary Data (MTOM). When you expand the MTOM section, you can select the MTOM checkbox. The MTOM feature is disabled in JAX-WS by default. It can be enabled on the client and server. Once enabled all the XML binary data, XML elements of type xs:base64Binary and xs:hexBianry is optimally transmitted. Currently MTOM works only with proxy port.
• Reliable Message Delivery. Specifies whether reliable messaging is enabled.
  • Deliver Messages In Exact Order. Specifies whether the Reliable Messaging protocol ensures that the application messages for a given message sequence are delivered to the endpoint application in the order indicated by the message numbers. This option increases the time to process application message sequences and may result in the degradation of Web service performance.
  • Advanced. Click the Advanced button to set the following options:
    • Flow Control. Specifies whether the Flow Control feature is enabled.
    • Maximum Flow Control Buffer Size. If Flow control is enabled, specifies the number of messages for a sequence that will be buffered. The default setting is 32.
    • Inactivity Timeout (ms). Specifies the time interval beyond which either source or destination may terminate any message sequence due to inactivity. The default setting is 600,000 milliseconds (10 minutes). A Web service endpoint will always terminate a sequence whose inactivity timeout has expired. To keep the sequence active, an inactive client will always send a stand- alone message with an AckRequested header to act as a heartbeat as the end Inactivity timeout interval approaches.
• Secure All Service Operations. Specifies WSIT security for all of the operations of a web service.
  • Secure All Service Operations. Select one of the options from the list. Most of the mechanisms are fully functional without further configuration, however, if you’d like to customize the mechanism, click Configure to specify the configuration for that mechanism. For details on each security mechanism, see About Security Mechanism Options for Web Services.

    The mechanisms that use STS require that an STS be specified in the Configuration dialog. If a security mechanism is selected that requires this, select the buttons to configure keystore, truststore, and validator options.

  • Act As Secure Token Service (STS).If you want to enable this web service to act as an STS, select this option. An STS contains a set of interfaces to be used for the issuance, exchange, and validation of security tokens.
• Allow TCP Transport. Specifies that the service supports TCP and works with both TCP and HTTP transport. TCP provides better performance when sending smaller messages. The performance enhancement is visible mostly in smaller messages because the overhead of sending messages over the HTTP protocol is eliminated.
• Allow Fast Infoset. Specifies that Fast Infoset is used for faster parsing, faster serializing, and smaller document sizes when compared with equivalent XML documents.