Communications Protocols Enhancements
MIME multi-part messaging ECS handles multi-part MIME messages. It can break the multi-part messages apart or keep them together and can hand them off to Delta either way.
Business framework support (SOAP, ebXML, BizTalk, etc.) When integrated with Delta, ECS can seamlessly handle any current or future business framework and track all related attachments.
HTTP/S Server and HTTP listeners ECS 4.0 installs with an HTTP server and supports the ability to define HTTP listeners. For each listener, multiple HTTP paths can be defined and each of these paths are input channels in ECS. ECS' use of an HTTP server and listeners allows it to fully support Web services which expose the core services of ECS for the purpose of application-to-application processing.
Input/output ports Input/output ports are generic input channels and output queues that are not associated with any protocol. Input and output ports exist to hold and forward data and to tie channels and queues together, eliminating the need to write the data to a file system as an intermediary step.
New security protocol support ECS 4.0 supports IETF EDI-INT AS2 as well as "AS3," an industry proposed security protocol.
AS2 Merlin A new Tools|AS2 Merlin menu selection has been added to the ECS Management Console. Choosing this displays a series of merlin screens for easily setting up AS2 communications (including an HTTP input channel and/or output queue, TPM records, certificate designations, and so on) between your ECS server and a trading partner's AS2 server.
User-defined session limits A new option under Tools|Advanced Options has been added to the Management Console, letting you specify the maximum number of communications sessions that can be simultaneously open for each communications protocol used in ECS (e.g. HTTP, FTP, or SMTP). The default limit is 32 sessions, but you can change this value as needed.
Use implicit TLS There is a new Use implicit TLS option for FTP input channels and output queues. When this option is selected in conjunction with the Use secure FTP option for a channel or queue, ECS will attempt to exchange data with the target FTP server via an implicitly secured SSL/TLS connection (FTPS). When deselected, ECS will attempt to communicate with the target server via an explicitly secured connection (AUTH SSL or AUTH TLS).
Client certificate verification There is a new Use client certificate check box on the Options pages in the FTP input channel and output queue configuration windows. You should select this option and choose a client certificate from the corresponding drop-down list if the FTP server referenced by that channel or queue verifies client certificates as part of the SSL/TLS negotiation process.
AUTH LOGIN

SMTP output queues have been updated to support the AUTH LOGIN login/authentication method (used by Microsoft Exchange and other SMTP servers) in addition to the AUTH PLAIN login method supported in prior ECS releases.