# Web Service Attributes Editor: Quality of Service: Port Binding

In the Quality of Service 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:

Element | Description
--- | ---
Version Compatibility | A drop-down list of .NET/METRO version compatibility. By default, this list is disabled and the user must use .NET 3.0/METRO 1.0. To enable more recent versions of .NET, you must add the latest METRO library to your project classpath.
Optimize Transport of Binary Data (MTOM) | 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:hexBinary is optimally transmitted.
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 Service | Specifies security for all of the operations of a web service.
Security Mechanism | 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. 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.
Use Development Defaults | Select this option to import certificates into the GlassFish keystore and truststore, so that they can be used immediately for development. Because the default certificates are not in an appropriate format to be used in this context, this import is done for you, so that you do not need to do this manually yourself. In addition to importing certificates, a default user is created in the "file" realm, with username "wsitUser". In a production environment, you will probably want to provide your own certificates and user settings, however, in a development environment you may find these defaults useful.
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.
Disable Fast Infoset | Specifies that Fast Infoset is not used. Fast Infoset is useful for faster parsing, faster serializing, and smaller document sizes when compared with equivalent XML documents.

Related Topics

Developing Applications with NetBeans IDE,

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.