Systemic Qualities Implemented in the FTP Binding Component

These are the systemic qualities implemented in FTP Binding Components.

• Transport Security

  • Explicit SSL - FTP/TLS (RFC 2228 + RFC 4217)

  • Implicit SSL - FTP on SSLSocket

• Connection Pooling

• Numerous QoS

  • Password Handling

    Security often interacts with various external systems, protocols, and implementations. Security can be authorization, authentication, or encryption. This initiative provides a common mechanism for components that handle authorization and authentication using user names and passwords.

  • Usability Enhancement of WSDL Extensibility Element Editor

  • Component Logging Systemic Quality

  • Application Variable and Application Configuration

  • Runtime Monitoring (MBean)

    Users can monitor the component and the application during runtime. After deploying and starting the server, it provides datapoints like endpoint statistics, component statistics and also measures performance.

  • Re-Delivery

  • Throttling

    Throttling settings can be used to limit the number of concurrent messages sent over the NMR.

  • Normalized Message Properties

    Normalized Message properties (or NM properties) are commonly used to specify metadata associated with the message content. Some standard NM properties defined in JBI specifications are: javax.jbi.security.subject and javax.jbi.messaging.protocol.type.

    • Getting/Setting transport context properties (for example, http headers in the coming HTTP request, file names read by the File Binding Component)

    • Getting/Setting protocol specific headers or context properties (SOAP headers)

    • Getting/Setting additional message meta-data (for example, unique message identifier, endpoint name associated with a message)

    • Dynamic configurations (for example, dynamically overwrite the statically configured file name to write to at runtime)

  • FTP Binding Component Defined Normalized Message Properties

    FTP Binding Component supports the unique message ID, that is, org.glassfish.openesb.messaging.messageid.

    Unique Message ID can be used, for example, to correlate messages while responding to a request.

    FTP Binding Component provides out-of-box request or response correlating using a UUID for every message.

  • Dynamic Addressing based on FTP Binding Component Normalized Message Properties

    FTP Binding Component can derive binding information from Normalized Message properties from a message. It applies this information to the static binding obtained from WSDL. It derives the endpoint while the message is processed or routed. This is called Dynamic Addressing.

    • For Inbound: Normalized Message properties will be populated and attached to the message if and only if AllowDynamicEndpoint == true.

    • For Outbound: Normalized Message properties will be used to overwrite static binding if and only if: AllowDynamicEndpoint == true and org.glassfish.openesb.ftp.use.dynamic.endpoint == true

    Dynamic Addressing can be of as a per message (outbound) endpoint binding (for example, to an external system).

    ---

    Note –

    This is a different mechanism from the JBI Dynamic Endpoint Reference (EPR).

    ---