FMS Version History

• Version: 5.4.3 Release 1 pre-release

  1. Server - Improved warning log message for 'Referenced partner not found'.

  2. Server - Migrate from log4j to log4j2.

  3. Server Partner Configuration ConnectionConfiguration.partnerIdentifier.organisation - added optional organisation element.

  4. Server Partner Configuration ConnectionConfiguration.partnerIdentifier.address - added optional address element.

  5. Server Partner Configuration ConnectionConfiguration.partnerIdentifier.phone - added optional phone element.

  6. Server Partner Configuration ConnectionConfiguration.partnerIdentifier.email - added optional email element.

  7. Server Partner Configuration ConnectionConfiguration.partnerIdentifier.email - added optional email element.

  8. FMC - Bug fixes and improved certificate export functionality for both DER and PEM formats.

  Version: 5.4.2 Release 8

  1. 5.4.2-8 p-mode search caching fix (unreproducible).

  2. documentation - general editorial updates,

  3. FMC - soften TLS protocol - default to TLSv1.2.

  Version: 5.4.2 Release 7

  1. FMC - add html directory to doc and include support jars including webservices-rt to the management console build distributions.

  2. FMC - general improvements including keystore management.

  3. documentation - general editorial updates including reference to new directory structures,

  Version: 5.4.2 Release 6

  1. Server - improved logging.

  2. fmsconf - TLS_ARG now defaults to an empty string.

  3. Server - fixed insert into request query syntax error. This occured in previous versions if the interfaceConfig.databaseConfig.enabled property is set to true resulting in failed inbound message processing.

  4. Server - corrected audit log tables /home/fms/schema/postgresq/databaseAudit.sql to match latest database schema.

  5. Server - updated comments in /home/fms/schema/postgresq/databaseCreation.sql.

  6. Server - updated comments in /home/fms/schema/postgresq/databaseConfig.sql.

  7. Server - updated comments in /home/fms/schema/postgresq/fms.sql.

  8. Console - improved error response messages.

  9. Server - implemented listening on all IP address when the configuration interfaceConfig.listener.Properties.HOST property is set to '*'.

  10. Server - Configurable ConnectionConfiguration.partnerIdentifier.mailBox implemented as described in the Section called Partner Identifier Configuration in the Chapter called Configuring FMS.

      Used for alternate messsage delivered directory based on the partnerIdentifier definition in the server configuration.

  11. Server - Configurable ConnectionConfiguration.interfaceConfig.deliveredContentDir with similar functionality as the ConnectionConfiguration.partnerIdentifier.mailBox configuration setting.

      Used for alternate messsage delivered directory based on the interfaceConfig definition in the server configuration.

  12. Server - Support for TLSv1.3 ConnectionConfiguration.interfaceConfig.listener.Properties.ENABLED_SSL_PROTOCOLS if supported by the java runtime.

  13. FMC Management Console - support for exporting certificates in PEM and DER (binary) format.

  14. FMC Management Console - improved display of certificate details.

  Version: 5.4.2 Release 5

  1. Server - added command line option '-D53' to revert to the FMS version 5.3 deliveredContentDir format as follows

     \fms_installation_dir/<cc:deliveredContentDir>/toPartner.URLtoPath()/conversationID/messageID \

     instead of the FMS version 5.4 deliveredContentDir format as follows

     \fms_installation_dir/<cc:deliveredContentDir>/fromPartner.URLtoPath()/toPartner.URLtoPath()/messageID \

  Version: 5.4.2 Release 4

  1. Server - fix missing sun/security/validator/KeyStores.class message on FMS server startup after upgrading Java^TM 8 release 212 or earlier to a later version. This resulting in FMS server not starting up.

     Also see 5 for details on circumventing this problem with previous versions of the FMS server.

  2. Server - fix incorrect log message Unable to load interface 'HTTP - AS4': NullPointerException while reading FMS Licence. This was caused by incorrect or unresolvable listener HOST property in the Administration interfaceConfig section.

  3. Server - Various logging improvements - display stack trace only when FMS LOGGING_LEVEL is set to TRACE as set in the server main.conf settings.

  Version: 5.4.2 Release 3

  1. Server - Include fmsas4lc in the debian and ubuntu distribution.

  2. Server - New log message 'Using default p-mode' in debug log level, if no p-mode match was found and DEFAULT_PMODE is set in the package configuration properties.

  3. Server - Change log level from debug to info for 'Setting session pmode' log message

  4. Server - Fixed configuration schema path. No longer needs to be terminated with a path separator.

  Version: 5.4.2 Release 2

  1. Server - Fixed metadata.fmd <fmd:Location> from relative to absolute path. Was broken in 5.4.2 Release 1.

  2. Server - Fixed configuration delivered-content path. Was broken in 5.4.2 Release 1.

  3. Server - enhanced file move capabilities both within and across file systems including versioning (backups) for duplicates.

  4. Server - all logging messages for received messages saved now show normalised and absolute path.

  5. Server - fixed an issue where a SOAP fault indicating an internal server error was returned with an HTTP 500 error on receiving an empty payload. This caused the following error in the server logs

     com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.lang.NegativeArraySizeException

     and SEVERE com.sun.xml.messaging.saaj.soap.AttachmentPartImpl getRawContentBytes() - SAAJ0577: Exception while trying to get the Raw content for this attachment sent to stderr.

  6. Console - provided management console support for local PKCS12 keystores.

  7. server - fixed support for PKCS12 keystores.

  8. server - renamed fmsdaemon.deb to fmsdaemon to avoid confusion with debian and ubuntu install packages.

  9. server - removed inadvertent log message displaying certificate alias names introduced in version 5.4.2 release 1.

  10. server - database table for storing any payload URL associated with a message implemented.

  11. server - database table for storing partner_agreements associated with a message implemented.

  12. server - updated bouncy castle libraries.

  13. server - fixed permission changes on directory /home/fms during installation.

  14. server - fixed unnecessary call to savelog in server startup.

  15. server - fixed ConversionPattern for dest3 in log4j.profile.as4.

  16. server - clear previous session logging details such as ID, FROM and TO.

  17. fmsconf - __FMS_Admin_DeleteCert command extended with optional result argument.

  18. fmsconf - __FMS_Admin_GetCert command extended to return the full certificate detail if the optional full argument is provided.

  Version: 5.4.2 Release 1

  1. Server - Optional partner mailBox (inbox/outbox) for local/remote partners or the other way around for inbound/outbound messages implemented in schema/FMS/ConnectionConfiguration-1_0.xsd. Used for alternate delivered directory based on partnerIdentifier.

  2. Server - added command line option '-w' to not write a new configuration in case of updates.

  3. Server - Message payloads are now correctly moved from temp to destination across file systems.

  4. client - New '-z' command line option for compressing payloads. If included on the command line then payloads will be compressed overriding the p-mode setting.

  5. client - The "mimeType" (non compressed payloads), "schema" and "characterset" properties may now be set in the pmode businessInfo.PayloadProfile.mimeType, businessInfo.PayloadProfile.schemaFile and/or the businessInfo.PayloadProfile.CharacterSet settings where these will be used if not included in the properties passed in the '-a' command line argument. The appropriate businessInfo.PayloadProfile will be matched on the "content-id" property that SHOULD be included in any properties passed in the '-a' command line argument. Eg. the following illustrates a typical pmode businessInfo.PayloadProfile configuration

     \ \ <pmode:PayloadProfile> \ <pmode:ContentID>sbdh-order</pmode:ContentID> \ <pmode:mimeType>application/xml</pmode:mimeType> \ <pmode:schemaFile>testSbdh.xsd</pmode:schemaFile> \ <pmode:CharacterSet>utf-8</pmode:CharacterSet> \ <pmode:maxSize>0</pmode:maxSize> \ <pmode:usage>expected</pmode:usage> \ </pmode:PayloadProfile> \ \

  6. Server - table insert SQL statements now include the attributes being inserted. This to permit table attribute extension without affecting internal code.

  7. Server - ConnectionConfiguration.partnerIdentifier.errorEndpointURL endpoint is now supported as follows

     This endpoint indicates the address to which to send ebMS errors generated on the receiving MSH that receives a message that caused an error. This is typically the endpoint address of the MSH sending the message that caused an error on the receiving side. It will only be used if the asResponse is set to true and if the FMS connection interface database is configured. If ConnectionConfiguration.partnerIdentifier.errorEndpointURL is not set the P-Mode.errorHandling.receiverErrorsTo setting will be used. This element was ignored prior to FMS version 5.4.2.

  8. Server - P-Mode Error handling endpoints are now supported as follows

     1. P-Mode.errorHandling.asResponse

        This boolean parameter indicates whether (if true) errors generated from receiving a message in error are sent over the back-channel of the underlying protocol associated with the message in error, or as a callback message in the case that the FMS connection interface is configured with a database connection. All error signals will be sent back on the backchannel if no database connection is configured. SOAP Faults are always sent back to the remote partner on the back channel. This element was ignored prior to FMS 5.4.2.

     2. P-Mode.errorHandling.receiverErrorsTo

        This endpoint indicates the address to which to send ebMS errors generated by the MSH that receives a message in error. This is typically the endpoint address of the MSH sending the message that caused an error. It will only be used if asResponse is set to true and if the FMS connection interface database is configured. This endpoint is overriden by the optional connection configuration partnerId errorEndpointURL if configured. This element was ignored prior to FMS version 5.4.2.

  9. Server - Receipt acknowledgement triggers have been extended with the following available arguments

     1. SERVICE.

     2. ACTION.

     3. SENDER_IDENTIFIER.

     4. SENDER_ROLE.

     5. RECIPIENT_IDENTIFIER.

     6. RECIPIENT_ROLE.

     7. SUBMITTED.

     8. CONVERSATION_ID.

     9. PATH.

  10. Server - Improved message file saving permitting across filesystem saving of payloads, receipts and other signals between MESSAGE_TMP_DIR and delivered-content directories.

  11. Server - interfaceConfig.deliveredContent directory structure changed from

      ../delivered-content/initiatingParty/message-id

      to

      ../delivered-content/initiatingParty/respondingParty/message-id

      where the partner strings have any preceding URI elements removed to ensure a consistent directory structure. Eg.

      http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/defaultFrom

      is transformed to just

      defaultFrom

  12. Server - connection configuration deliveredContent directory support for absolute paths for both *nix and Windows operating systems.

  13. Server - Use the responding (local) partner keystore for determining the private decryption key. This permits the use of multiple private keys each associated with a separate initiating (remote) partner.

  14. Server - Use the initiating (remote) partner keystore for determining the key to sign a receipt signal response for a received user message. This permits the use of multiple private keys where remote partners can then be issued with separate public keys as associated with their respective keystores. Note that keystores can be shared across partners permitting a single keystore with a single private/public key across any number of remote and local partners.

  15. Server - The listener.aliasRef.alias value is now used to determine the SSL private key alias in the associated listener keystore if set. If not set (empty) then the SSL private key will default to the first private key located in the keystore.

  16. Server - Listener activation now picks up the correct interface properties from the server configuration including the following.

      1. <prop:entry prop:key="SSL_PROVIDER">SunJSSE</prop:entry>.

      2. <prop:entry prop:key="SSL_NEED_CLIENT_AUTH">true</prop:entry>.

      3. <prop:entry prop:key="SSL_VERSION">TLSv1</prop:entry>.

  17. Server - Listening sockets are now closed down when shutting the server down and when closing and reloading interfaces from the management console.

  18. Server - Logging now includes the thread id.

  19. Server - Inbound messages using security setting keyReferenceType="IssuerSerialNumber" comparison on certificate issuer improved and is now based on RFC 3280 compliant comparison.

  20. Client - improved usage message for the '-h' host command line option when using a TCP IPv6 address.

  21. Server - A Receipt for a user message that could not be signed due to the private certificate alias being incorrectly configured on the server and as associated with the remote (previously local) partner configuration resulted in an EBMS:0102 error returned to the initiating party. The server now logs the error and responds with a SOAP fault indicating a server side problem to the client.

  22. FMC - improved support for TCP IPv6 addresses when connecting to a server.

  23. fmsconf - general improvements and no longer requires certificates if the server admin listener SSL_NEED_CLIENT_AUTH property is set to false.

  24. Server - Implement multiple private certificates for signing outbound messages by locating the private signing certificate using the initiating (remote) partner aliasRef alias in the initiating partner keystore for signing receipts.

      If the certificate alias could not be located in the initiating partner keystore search the responding (local) partner keystore using the responding partner aliasRef alias.

      Previously only the responding partner keystore was searched permitting only a single private signing certificate for outbound receipts.

  25. Server - Use the responding (local) partner keystore for locating the private certificate for decrypting inbound messages and not the listener keystore. If not located then try the listener keystore as previously done.

  26. Server - Verify signature for inbound user message by searching the responding (local) partner keystore for a match. If not found search the listener keystore. If not found fail.

  27. Server - Improved default configuration and p-mode creation on startup. Now based on default properties

  28. Windows install - include send.bat and sample XML payload

  29. Server - Fixed receiving message with unknown encryption key and unknown partner results NPE.

  30. Server - Fixed error if pmode:queueMessages is missing from the configuration.

  31. Server - Logging for Linux changed as follows

      1. /var/log/fms/debug.log renamed to /var/log/fms/fms.log. General FMS server logs. Configured in /etc/fms/log4j.properties.as4.

      2. /var/log/fms/out.log renamed to /var/log/fms/fms-stdout.log. Configured in /etc/fms/fmsdaemon (ubuntu, debian) or /etc/fms/fms.conf (RedHat, CentOS).

      3. /var/log/fms/err.log renamed to /var/log/fms/fms-webservices.log. Detailed webservices soap and security logs. Configured as java.util.logging.FileHandler in /etc/fms/logging.properties

      4. /var/log/fms/err.log renamed to /var/log/fms/fms-stderr.log. General webservices soap and security logs. Configured in /etc/fms/logging.properties (java.util.logging.ConsoleHandler aka stderr) and /etc/fms/fmsdaemon (ubuntu, debian) or /etc/fms/fms.conf (RedHat, CentOS).

      5. /var/log/fms/error.log. Removed from log4j.properties.as4. Can be re-configured as dest3 in /etc/fms/log4j.properties.as4

  32. Server logging configurations for Linux are now as follows

      1. /etc/fms/log4j.properties.as4. FMS Server general logging configuration.

      2. /etc/fms/logging.properties. FMS Server Webservices logging configuration.

  33. FMC Logging

      1. /etc/fms/log4j.properties.mc. FMC logging configuration (goes to stdout).

  34. FMC - Fixed error not displaying cc:interfaceConfig. Due to invalid setting for cc:interfaceConfig.Optimisations.retryFrequency = 300000

  35. Fixed java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.impl.SOAPTextImpl cannot be cast to javax.xml.soap.SOAPElement due to tabs or spaces in security encryption <xenc:CipherReference...> element of an encrypted incoming user message.

  Version: 5.4.1 Release 3

  1. client - improved logging

  2. client - move atTime to before preparing message to be sent

  3. client - optional '-messageFile soapFile.out' command line option to save outbound soap envelopes

  4. client - fmsclient.as4.jar '-d' command line switch sets 'ALL' for logging.properties but no longer 'OFF' if not set. This so logging can be configured in logging.properties using 'java -Djava.util.logging.config.file=/home/fms/trigger/logging.properties'.

  5. server - messages are now saved with thread_id in the case of no DB connections as follows as per directory setting in main.conf

     <entry key="HTTP_REQUEST_STORAGE_DIRECTORY">/home/fms/http_requests/ </entry>

     \ \ OUTGOING-01112017-074737.582-13_sig.dat \ INCOMING-01112017-074737.253-13_um.dat \ \

     where '-13_' indicates the thread id. This to ensure uniqueness in filenames

  6. server - fixed FMS_ARGS in /etc/fms/fms.conf

  7. client - the following attachment partproperties set on the '-a' command line option are removed from the part properties for compressed payloads.

     1. partProperties.remove("mimetype");

     2. partProperties.remove("description");

     This as the following duplicate properties are added when the payload is compressed

     MimeType, Description, CompressionType

     resulting in duplicate part properties.

  8. server - Default properties updated to use latest signing and encryption algorithms.

  9. server - Default configuration generation updated to use default properties.

  10. server - Improved logging

  Version: 5.4.1 Release 2

  1. client - atTime '-at msecs' now works when timeouts are not set.

  2. server - improve debug logging, and throw certificate error reason to be used in response if certificate validation failed due to a problem with the root certificate.

  3. server - remove call to undocumented jdk.nashorn.internal.ir.debug.ObjectSizeCalculator as that causes errors (com.flame.shared.exceptions.PackingException: Unhandled exception Exception: Internal Server Error) with later versions of java (1.8.0_131...)

  Version: 5.4.1 Release 1

  1. client - new '-batch batchArgs.txt' command line option

     The new optional command line option '-batch file' permits multiple messages to multiple locations during a single session. Each line contains separate client arguments for separate messages.

     Invoke fmsclient.as4.jar as follows when using the new '-batch' command line option

     \ \ java -jar fmsclient.as4.jar -batch batchArgs.txt -k ./fmstestcerts -ksp changeit -d \ \

     where batchArgs.txt contain lines with fmsclient.as4.jar arguments for each separate message. Lines starting with a '#' character are ignored.

  2. Improved logging - includes detail when compressing and securing messages.

  Version: 5.4.0 Release 4

  1. server - further improvements to large payload (up to 1.8GB) handling. Includes updates to webservices-rt including saaj-impl-1.3.28, mimepull to 1.9.1 and org.jvnet.staxex to 1.7.8

  2. server and client - removed NLs surrounding <wsse:Security> ... </wsse:Security> tags - this in an attempt improve .NET interoperability.

  3. server and client - HTTP_BAD_REQUEST (400) Responses eg. SOAP faults no longer blocked.

  4. client - Improved truststore private key retrieval logging

  Version: 5.4.0 Release 3

  1. server - further improvements to large payload (up to 1.8GB) handling. Includes updates to webservices-rt including saaj-impl-1.3.28, mimepull to 1.9.1 and org.jvnet.staxex to 1.7.8

  2. Also includes changes to removing NLs from encryption CipherValue element. SignatureValue still contains NLs.

  3. Externalised setting of -Dsaaj.mime.optimization=true -Dsaaj.use.mimepull=true -Dsaaj.lazy.mime.optimization=true. These java args must now be set on FMS startup

  Version: 5.4.0 Release 2

  1. server - large payload (up to 1.8GB) handling. Includes updates to webservices-rt including saaj-impl-1.3.28, mimepull to 1.9.1 and org.jvnet.staxex to 1.7.8

  2. server - ubuntu and debian package fixes and improvements.

  3. server - logging improvements.

  Version: 5.4.0 Release 1

  1. server - xmlsec 2.0.7 based webservices server

  2. server - optimisation if certificate matches entry in keystore

  3. server - fixed problem with saving inbound binary compressed attachments

  4. server - fixed activation problem with java-1.8 on some VMs

  Version 5.3.4 Release 2

  1. client - Certificate chain validation for validating incoming signing certs implemented.

  2. client - Support for separation of ssl trust store (default java cacerts) from key store by default.

     New optional '-st sslTruststore' and '-stsp sslTruststorePass' command line options to set the ssl truststore to an alternate truststore. Set '-st' to the same as the keystore location for pre 5.3.4-2 behavior.

  3. client - Command line option '-u' now works as expected. Ie. SSL support is not loaded if set.

  4. client - Certificate chain validation for validating incoming ssl certs implemented.

  5. client - Return code 3 in case of SSL certificate error.

  6. client - Implemented '-noSystemExit' command line option. If set then program return status will be sent to stdout instead of the invoking shell.

  7. client - Copyright notice now goes to stderr.

  Version 5.3.4 Release1

  1. client - Dynamic p-mode support for setting initiating and responding partner p-mode settings. Includes setting partner.party@type and partner.role on the command line.

  2. client - New command line args include -toType, -toRole, -fromType, -fromRole.

     Use these command line options when any of '-from' or '-to' do not match what is in the p-mode. Used to override p-mode settings particularly when dynamic p-modes are required without having to create new p-mode files.

  Version 5.3.3 Release 17

  1. client - migrate to java 1.8.

  2. client - further encryption support for gcm encryption algorithms.

  3. client - support for EncryptedKey.EncryptionMethod.DigestMethod

  4. client - support for key encryption method "http://www.w3.org/2009/xmlenc11#rsa-oaep"

  5. client - fixed part properties usage example by escaping the first colon.

  6. client - improved error trapping on non-existing attachments.

  7. client - added stack trace on null pointer exceptions (return code 6).

  Version 5.3.3 Release 16

  1. client - fixed spec in URL instantiation. Was set to path instead of the full spec as returned by url.getFile()

  2. client - no need to override URLConnection() if connectTimeout and responseTimeout is not set.

  3. client - allow pmode:party/@pmode:type and pmode:party/@type. Fixed regression pmode:party/@type since 5.3.3-13

  4. client - allow pmode:service/@pmode:type and pmode:service/@type. Fixed regression pmode:service/@type since 5.3.3-13

  5. client - implemented underlying encryption support for gcm algorithms. Only available with java 1.8.

  6. client - improved logging.

  Version 5.3.3 Release 15

  1. client - log for message transmit time (based on com.flame.client.as4 logger) when '-d' command line option is used.

  2. client - set return code to TIMEOUT (4) on read or connect timeout.

  3. client - set return code to CONNECTION_EXCEPTION (2) on failing to establish a connection.

  Version 5.3.3 Release 14

  1. client - Improved error message when failing to connect to remote host. Eg. 'network unavailable'

  2. client - New command line options

     -at <Send Time> - Send message at current time + time in milliseconds or at specified future date in format yyyy-MM-dd'T'HH:mm:ss.SSS eg. 2100-01-01T00:00:00:000

     -t <Timeout> - Connection timeout in milliseconds. Defaults to 30000.

     -T <Timeout> - Response timeout in milliseconds. Defaults to 30000.

     Set both -t and -T to 0 to disable timeouts.

  Version 5.3.3 Release 13

  1. client - New command line option '-X' for dumping security providers.

  2. client - Unused command line option '-pr' removed.

  3. client - Command line option '-r refToMessageId' now also works for user messages.

  4. client - New repeatable command line option '-mp' for setting MessageProperties.

  5. client - messageID '-m messageID' now functions as expected.

  6. client - Use of p-mode.id and agreementref now optional if not defined in the p-mode.

  7. client - Only default pmode:party/@type to "string" if party is not a URI - also see RFC 2396

  Version 5.3.3 Release 12

  1. client - Improvements to SSL context handling.

  2. client - Internal improvements and bug fixes.

  Version 5.3.3 Release 11

  1. client - Added 400 response code as SOAPFault (even though it's against SOAP 1.2 over HTTP) - also see https://java.net/jira/browse/SAAJ-74 and https://issues.jboss.org/browse/WFLY-3966

  2. client - Strip path from attached payload files as appears in Content-Disposition

  3. client - Internal improvements and bug fixes.

  Version 5.3.3 Release 10

  1. client - fixed bug saving payload attachments

  Version 5.3.3 Release 9

  1. client - remove schema from part properties.

  Version 5.3.3 Release 8

  1. client - bug fix for '-service' and '-serviceType' command line options when sending messages with attached payloads

  Version 5.3.3 Release 6 and 7

  1. client - debug flag now sets security config dumpMessage='true' for inbound messages.

  2. client - attachment filename can now be either a filename or external payload pointed to by a url which will be retrieved

  3. client - remove filename,content-id,mimetype,description and encoding from part properties

  4. client - do not gzip payload if the payload is already compressed as per gzip sig bytes ID1 and ID2 from RFC 1952. Requires <pmode:useCompression>true</pmode:useCompression> in the p-mode.

  Version 5.3.3 Release 4 and 5

  1. client - Internal improvements including bug fixes for partner type.

  Version 5.3.3 Release 3

  1. client - Internal improvements and bug fixes.

  Version 5.3.3 Release 2

  1. client - Do not with an empty messageID

  Version 5.3.3 Release 1

  1. client - First release of fmsclient.as4.jar based on sas4client.jar

  Version: 5.3.2 Release 19

  1. server - dynamic partner support - create initiating partner from the 'from' party field in message if it does not exist. Note no @type as yet.

  2. server - fixed NRR receipts not being signed for incoming signed messages from unknown remote partners

  3. server - fix retrieving private key for the local partner - was set to attempting to obtain private key using the remote partner alias.

  4. server - fixed debug message output

  5. server - Certificate chain validation for validating incoming SSL certificates implemented. Requires root CA certificate either in the truststore or in cacerts.

  6. FIXES for CA certs

  Version: 5.3.2 Release 18

  1. fmsconf - updated usage

  2. server - improved checking on service, action, agreementref and mpc if these are empty strings

  3. server - Dynamic p-modes. Set p-mode to packagerConfig.Properties.DEFAULT_PMODE if no p-mode match. If no DEFAULT_PMODE property match then no match.

  4. server - improved logging

  5. server - now validates sign certificates against issuer CA as well.

  Version: 5.3.2 Release 17

  1. Server - webservice-rt.jar

     1. Support for Java^TM 8.

     2. Support for AES_GCM_BLOCK_ENCRYPTION_128, AES_GCM_BLOCK_ENCRYPTION_192, AES_GCM_BLOCK_ENCRYPTION_256 with Java^TM 8.

     3. Improved logging.

     4. Attachment "Content-Transfer-Encoding" changed from base64 to binary.

  2. Server - RESPONSE_SENT trigger improvements. This trigger fires after writing final response for incoming user message. It may be used for implementing twoWay MEPs.

  3. Server - improved logging for cert handling - now shows keystore used.

  4. Server - partner identification now done prior to the security processing. This requires that <eb:Messaging> -> <eb:UserMessage> -> <eb:PartyInfo> not be encrypted as per 5.1.6 of the AS4 Profile and as recommended in 7.4 of the core spec.

  5. Server - Locate the private decryption and signature verification key in the local partner keystore if not found in the connection keystore. The connection private key is used for SSL so the private decryption and signature verification key can now be separate.

  6. Server - Return EBMS:0303 on failure to un-compress a compressed incoming attachment.

  7. Server - mark message as failed in case of internal Exception (Session.run())

  8. Server - improved logging (include class and method name in TRACE mode)

  9. Server - improved checking for non-existant messageID

  10. Server - SignatureKeyCallback.AliasPrivKeyCertRequest - improved logging and set keystore referred to by initiatingParty (was respondingParty) as required when separating keystores based on partners.

  11. Server - Trigger position RESPONSE_SENT include path

  12. Server - if a test message with service set to 'http://.../service' and action set to'http://.../test' then process complete message and now also creates a receipt if specified in the p-mode, but do not writePayload. e-SENS requirement

  13. Server - throw packingException on missing MimeType PayloadInfo PartProperty - Compressed payload requirement from section 3.1 of the AS4-Profile.

  14. Server - metadata.fmd support for PartInfo/PartProperties/Property/@name="CharacterSet". Added MimeCharacterSet to schema/FMS/FMSMetadataDocument-1_0.xsd - not written to metadata.fmd as yet

  15. Server - throw PackingException with ValueNotRecognized (EBMS:0001) on invalid character set (eb:PartInfo/eb:PartProperties/eb:Property/@name="CharacterSet") for a compressed xml SWA payload. Also see Section 3.1 of the AS4 Profile.

  16. Server - Admin protocal command for __FMS_Admin_ReloadLicence. Also reloads connections.

  17. Server - Fixed logging and management console viewing and updating of license details

  18. Schema - FMSMetadataDocument-1_0.xsd support for the following Eg. metatdata.fmd may now include

      \ \<fmd:MessagePayloads> \ <fmd:Payload> \ <fmd:MimeContentID>xmlpayload@minder</fmd:MimeContentID> \ <fmd:MimeContentType>application/xml</fmd:MimeContentType> \ <fmd:MimeCharacterSet>utf-16</fmd:MimeCharacterSet> <!-- optional --> \ <fmd:Location>/home/fms/delivered-content/flame-c2/703131/6622e78c@mindertestbed.org/attachment-0</fmd:Location> \ </fmd:Payload> \ \

  19. Schema - FMSMetadataDocument-1_0.xsd support for the following

      1. metadata.fmd support for eb:CollaborationInfo/eb:AgreementRef Eg. metatdata.fmd may now include

         <fmd:AgreementRef>test-agreement</fmd:AgreementRef>

      2. metadata.fmd support for

         eb:MessageInfo/eb:Timestamp

         Eg. metadata.fmd now includes

         <fmd:Timestamp>2016-02-12T12:30:22.552Z</fmd:MessageID>

  20. fmsconf implemented.

  Version: 5.3.2 Release 16

  1. Server - Close SSL socket bugfix for 5.3.2-14 and 5.3.2-15

  2. Fixed non-blocking server mode as reported for 5.3.2-15 (hanging sockets) - 5.3.2-16

  Version: 5.3.2 Release 15

  1. Server - Fixed NPE bugfix for 5.3.2-14 on returning a response when attempting to fire RESPONSE_SENT trigger. Occurs when pulling from non-existing MPC or pushing to an non-existing p-mode.

  Version: 5.3.2 Release 14

  1. message.message_type - OTHER=7 for soap faults

  2. Server - much improved log messages - TRACE will generate huge logs including stack traces on error conditions, DEBUG is useful for debugging and recommended in a running test environment and INFO appropriate for a long running production server.

  3. Server - SSL protocol property

     \ \ <prop:entry prop:key="ENABLED_SSL_PROTOCOLS">TLSv1.2</prop:entry> \ \

  4. Server - improved socket connection threading and handling - new LISTENER_COUNT property with default set to 5 plus the value of LISTENER_COUNT. Used for number of listeners.

     \ \ <prop:entry prop:key="LISTENER_COUNT">5</prop:entry> \ \

  5. Server delivery directory and file handling improvements

     User Messages

     \ \fms_installation_dir/<cc:deliveredContentDir>/toPartner.URLtoPath()/conversationID/messageID/fromPartner.URLtoPath()-action.[xml|soap] \ \

     Meta file delivery to

     \ \fms_installation_dir/<cc:deliveredContentDir>/toPartner.URLtoPath()/conversationID/messageID/metadata.fmd \ \

     Receipts

     \ \fms_installation_dir/<cc:deliveredContentDir>/fromPartner.URLtoPath()/message_id/receipt.soap \ \

     Meta file delivery to

     \ \fms_installation_dir/<cc:deliveredContentDir>/fromPartner.URLtoPath()/message_id/metadata.fmd \ \

  6. Server message storage directory improvements (used if no db)

     user messages to fms_installation_dir/HTTP_REQUEST_STORAGE_DIRECTORY/[INCOMING|OUTGOING]-mmddyyyy-hhmmss.SSS_um.dat (no mime messages so no attachments) signal messages to fms_installation_dir/HTTP_REQUEST_STORAGE_DIRECTORY/[INCOMING|OUTGOING]-mmddyyyy-hhmmss.SSS_sig.dat

  7. Server interfaceConfig acls implemented for AS4 listeners.

  8. Server RECEIVE trigger argument 10 now contains PATH indicating full path name of delivered messages and metadata.

     Requires change to ConnectionConfiguration.xml triggers as follows

     Change

     \ \<tg:Trigger> \ <tg:identifier>ReceiveMessage</tg:identifier> \ <tg:enabled>true</tg:enabled> \ <tg:type>SynchronousExecutable</tg:type> \ <tg:location>RECEIVE</tg:location> \ <tg:instruction>./trigger/Receive.sh %1$s %2$s %3$s %4$s %5$s %6$s %7$s %8$s %9$s</tg:instruction> \ <tg:providedArguments>action</tg:providedArguments> \ <tg:providedArguments>conversationID</tg:providedArguments> \ <tg:providedArguments>event</tg:providedArguments> \ <tg:providedArguments>messageID</tg:providedArguments> \ <tg:providedArguments>MPC</tg:providedArguments> \ <tg:providedArguments>processingMode</tg:providedArguments> \ <tg:providedArguments>recipientIdentifier</tg:providedArguments> \ <tg:providedArguments>senderIdentifier</tg:providedArguments> \ <tg:providedArguments>service</tg:providedArguments> \ <tg:executionType>External</tg:executionType> \</tg:Trigger> \ \

     to

     \ \<tg:Trigger> \ <tg:identifier>ReceiveMessage</tg:identifier> \ <tg:enabled>true</tg:enabled> \ <tg:type>SynchronousExecutable</tg:type> \ <tg:location>RECEIVE</tg:location> \ <tg:instruction>./trigger/Receive.sh %1$s %2$s %3$s %4$s %5$s %6$s %7$s %8$s %9$s %10$s</tg:instruction> \ <tg:providedArguments>action</tg:providedArguments> \ <tg:providedArguments>conversationID</tg:providedArguments> \ <tg:providedArguments>event</tg:providedArguments> \ <tg:providedArguments>messageID</tg:providedArguments> \ <tg:providedArguments>MPC</tg:providedArguments> \ <tg:providedArguments>processingMode</tg:providedArguments> \ <tg:providedArguments>recipientIdentifier</tg:providedArguments> \ <tg:providedArguments>senderIdentifier</tg:providedArguments> \ <tg:providedArguments>service</tg:providedArguments> \ <tg:providedArguments>path</tg:providedArguments> \ <tg:executionType>External</tg:executionType> \</tg:Trigger> \ \

  9. Server returns HTTP CODE 400 regression fixed - this bug crept in with the -14 build updates. May cause the pulling partner to drop the associated EBMS response message

     eg. EBMS:0006:EmptyMessagePartitionChannel.

  10. Server now returns 200.

  Version: 5.3.2 Release 13

  1. server - provide support for absolute URIs as per RFC 2616 (http://tools.ietf.org/html/rfc2616#section-9.5)

  2. server - improved usage message

  3. rpm package - include Envelope directory

  Version: 5.3.2 Release 12

  1. server and as4 client - Java^TM 7 compatibility, tweak on socket close

  2. server - Java^TM 1.6.0_31 problem with attachments - Changed saaj.lazy.contentlength from true to false

  Version: 5.3.2 Release 11

  1. Server - messageid suffix configured as $host gives wrong host - fixed

  2. Server - Locate the private decryption and signature verification key in the local partner keystore if not found in the connection keystore.

  3. SSL key customisation - ConnectionConfiguration.xml

     Change

     \ \ <cc:listener cc:packagerConfigID="AS4-PackageManager"> \ <cc:name>AS4</cc:name> \ <cc:className>com.flame.connection.impl.ebXML.AS4.RemoteIn</cc:className> \ <cc:aliasRef cc:keystoreID="default"> \ <cc:alias>fmsrns</cc:alias> \ <cc:password>fmsrns</cc:password> \ </cc:aliasRef> \ \

     to

     \ \ <cc:listener cc:packagerConfigID="AS4-PackageManager"> \ <cc:name>AS4</cc:name> \ <cc:className>com.flame.connection.impl.ebXML.AS4.RemoteIn</cc:className> \ <cc:aliasRef cc:keystoreID="flamessl"> \ <cc:alias>flamessl</cc:alias> \ <cc:password>fmsrns</cc:password> \ </cc:aliasRef> \ \

     and add the following

     \ \ <cc:keystoreRef cc:ID="flamessl"> \ <cc:name>ssl_certs</cc:name> \ <cc:type>JKS</cc:type> \ <cc:pass>changeit</cc:pass> \ </cc:keystoreRef> \ \

  4. Server - Implement signing messages and NRR (non repudiation receipts) with separate signing cert instead of the partner SSL cert

     Gen the new private key into a separate keystore as follows - required to avoid java.security.InvalidKeyException: Not an RSA key: DSA when do the default keytool -genkey ???

     \ \keytool -genkeypair -keyalg RSA -sigalg MD5withRSA -alias flamesign -keypass fmsrns \ \ -keystore sign_certs -storepass changeit \ \

     Then set the partner and keystore as follows

     \ \<cc:partnerIdentifier cc:value="flame" cc:type="string"> \ <cc:endpointURL>https://localhost:6444/AS4</cc:endpointURL> \ <cc:partnerType>LOCAL_PARTNER</cc:partnerType> \ <cc:username>flame</cc:username> \ <cc:password>flame</cc:password> \ <cc:aliasRef cc:keystoreID="flamesign"> \ <cc:alias>flamesign</cc:alias> \ <cc:password>fmsrns</cc:password> \ </cc:aliasRef> \ \ <cc:keystoreRef cc:ID="flamesign"> \ <cc:name>sign_certs</cc:name> \ <cc:type>JKS</cc:type> \ <cc:pass>changeit</cc:pass> \ </cc:keystoreRef> \ \

  5. Server and client swa 11 encryption compliant transform fix (metro webservices jars), and wsse:mustUndertand = "true" instead of "1"

  6. Server - the messageid suffix not included for errors - fixed 5.3.2-11

  7. Client - Softened up service and action - can now be set via the command line

  8. Client - fix schema option for attachments, set via the '-a schema:location;...' command line option per attachment

  9. Client - '-suffix' command line option to set the messageid suffix

  10. Client - new exception that can be used for invalid arguments

  11. Client - Allow escape characters to escape required characters such as ':' in the '-a' attachment key value pairs

  Version: 5.3.2 Release 9

  1. Server - NPE on storing invalid messagees

  2. Update FMS server p-mode search algorithm

     1. Using the optional @pmode attribute in the agreementref - if set but does not match return EBMS:0010

     2. combination of to/from/service/action - if to/from/service/action are set but no match goto next step

     3. combination of to/from/agreementref - if to/from/agreementref set but no match goto next step

     4. Just agreementref - if agreementref set but no match then return EBMS:0010.

     5. combination of from/MPC for pulls - if from/MPC set but no match then return EBMS:0010. and finally

     6. just MPC for pulls

  3. New configuration properties

     \ \<prop:entry \ \prop:key="EBXML_SOAP_EXTENSION_NS">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/</prop:entry> \<prop:entry \ \prop:key="DEFAULT_INITIATOR_ROLE">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/initiator</prop:entry> \<prop:entry \ \prop:key="DEFAULT_RESPONDER_ROLE">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/responder</prop:entry> \<prop:entry \ \prop:key="DEFAULT_SERVICE">http://docs.oasis-open.org/ebxml-msg/as4/200902/service</prop:entry> \<prop:entry \ \prop:key="DEFAULT_ACTION">http://docs.oasis-open.org/ebxml-msg/as4/200902/action</prop:entry> \<prop:entry \ \prop:key="ONEWAY_MEP">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/oneWay</prop:entry> \<prop:entry \ \prop:key="TWOWAY_MEP">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/twoWay</prop:entry> \<prop:entry \ \prop:key="PUSH_MEP">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/push</prop:entry> \<prop:entry \ \prop:key="PULL_MEP">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/pull</prop:entry> \<prop:entry \ \prop:key="PUSH_PUSH_MEP">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/pushAndPush</prop:entry> \<prop:entry \ \prop:key="PUSH_PULL_MEP">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/pushAndPull</prop:entry> \<prop:entry \ \prop:key="PULL_PUSH_MEP">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/pullAndPush</prop:entry> \<prop:entry \ \prop:key="SYNC_MEP">http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/sync</prop:entry> \ \

  Version: 5.3.2 Release 9

  1. Client - create attachment directory if it does not exist. Was broken for default case.

  2. Client - fixed ignoring of suffix - caused light client to be non RFC 2822 compliant for MessageId

  3. Client - attachment part properties are not included in PartInfo from the p-mode or from the '-a' command line option - done

  4. Client - Allow pmode:ID to be set to an empty string eg. <pmode:ProcessingMode pmode:ID="" xmlns:tg="http://fms.flame.business/FMS/schema/Trigger" xmlns:pmode="http://fms.flame.business/FMS/schema/ProcessingMode"> if empty do not include @pmode in CollaborationInfo.AgreementRef

  Version: 5.3.2 Release 7

  1. Server - table message add column event - provides missing event from old configuration table

  2. Server -table dispatch add column retry_threshold - provides missing retry_threshold from old configuration table

  3. Server -table dispatch add column retry_interval - provides missing retry_interval from old configuration table

  4. Server -index dispatch_attempt_dispatch_id_idx - missing index - used for DatabaseHandler.isMessageRetriable

  5. Server Configuration - Security Encryption Certificate - make it minOccurs="0" - done 5.3.2-6

  6. Server - add event to message table (was originally in configuration which now no longer exists). - done 5.3.2-6

  7. Server - remove journal trace logs - done

  8. Server - customise the prefix/suffix for messageid - done

  9. server - toRole incorrect - set to fromRole - fixed problem xpath on the as4client

  10. Server - SID, FROM and TO log4j settings are not reset on new connections made to the server - these must be cleared. - fixed 5.3.2-7

  11. Server - MessageId for empty MPC messages are wrong - contain the to party instead of the from party. Also if the party is a url then characters to the right of the @ do not conform to RFC 2822 - need to only get the last bit or use host - fixed 5.3.2-7

  12. Server - Receipt message ids have $to instead of $from - fixed

  Version: 4.3.0 Release 1

  1. Server - Added message direction to PullMessagesForMPC query to prevent incorrect messages being sent to pull requester (Incorrect private key for message error)

  2. Server - All interfaces now have access to all p-modes.

  3. Server - Log error when service is not found.

  4. Server - Removed configuration limit on listeners.

  5. Server - Fixed bug during dispatch update when transaction is locked.

  6. Server - Fixed configuration refresh not refreshing listener configuration.

  7. Server - Fixed endpoint/MPC in partner identifier references.

  8. Server - Fixed incorrect connection path being printed on bind.

  9. Server - Fixed message transaction locking.

  10. Server - Fixed null P-Mode message referring to old interface association.

  11. Server - Fixed possible null pointer when no packagers exist.

  12. Server - Fixed server classpath after BC library update.

  13. Server - Fixed synchronous reliable messaging with and without receipts.

  14. Server - Implemented auto pull features in processing modes.

  15. Server - Implemented service and action property searching for Rosettanet.

  16. Server - Implemented service mapping location using service identifier rather than associated service mapping

  17. Server - First write messages to temp directory before moving to delivered-content directory.

  18. Server - Fixed potential for duplicated http response send.

  19. Server - Adjusted service names to UBL and PIDX.

  20. Console - Added FMC drag and drop transfer handlers.

  21. Console - Confirm whether the administrator wants to refresh the connections on save.

  22. Console - Added splashscreen to jar load.

  23. Console - Improved administrator connection error message.

  24. Console - Fixed handling of modified nodes on exit.

  25. Console - Moved location of the help dialog to be on the left if there is no space on the right.

  26. Console - Set modality type for the wizard dialog.

  27. Console - Paste now appends Copy Of in front of pasted node.

  28. Console - Adjusted paste to insert nodes at an index.

  29. Console - Adjusted properties so it uses old properties when resaving.

  30. Console - Implement shortcuts for management console

  31. Console - Adjusted transport and payload security levels to be MIME and SOAP security levels respectively.

  32. Console - Adjusted wizard to run without a connection to a server.

  33. Console - Fixed P-Mode duplication copy-of-copy-of issue.

  34. Console - Fixed clone bugs.

  35. Console - Fixed cloning of P-Mode conversationID.

  36. Console - Fixed help file referencing.

  37. Console - Fixed tree not modifying the correct nodes.

  38. Console - Fixed null variables causing XML parse failure when saving.

  39. Console - Fixed null pointer for null outgoing connection.

  40. Console - Fixed partnerIdentifier modification causing null pointer when handler node is not selected.

  41. Console - Fixed template re-assignment issue when going back to beginning without changing template types.

  42. Console - Fixed unmodified tree method, forward scan on handler node first, then backward to root.

  43. Console - Implemented undo editor, resets all edits with each new panel that is opened.

  44. Console - Implemented administrator MOTD command.

  45. Console - Implemented Tree Drag and Drop.

  46. Console - Implemented multiple administrator connections.

  47. Console - Implemented report graphs (Messages/Minute over Time, Messages/Minute meter, Message Times, Message Composition)

  48. Console - Implemented report message search queries.

  49. Console - Implemented empty file handlers for easy access (cached).

  50. Console - Implemented imports of configurations to an administration connection.

  51. Console - Implemented reports node for message queries with menu accessors.

  52. Console - Implemented unified wizard dialog.

  53. Console - Moved Quit from File menu and About from Help menu for Mac OS X

  54. Console - Moved content identifier in PayloadProfile to below schema selection.

  Version: 4.2.7 Release 1

  1. System - Upgraded compiler to Java 1.6

  2. Server - Implement extended protocol for the administration connection to the server. This to enable multiple concurrent connections from the FMC to FMS servers.

  3. Server - Removed all connection restrictions. Licensing restrictions are implemented at the partner level.

  4. Console - Deprecated Configuration Editor and replaced it with FMC.

  5. Console - Implemented authentication for the administration connection.

• Version: 4.2.6 Release 18

  1. Server - Implemented FMSMetadataDocument to be deposited in the delivered content directory.

  2. Server - Added application client correlation code for correlation of sequenceID and sequenceNum from client properties.

  3. Server - Implemented WS-ReliableMessaging

  4. Server - Implemented configurable Trigger system which can invoke a system executable or log a custom message when trigger location is encountered.

  5. Server - Implemented custom HTTP compression as well as client compression for slower connections.

  6. Server - ebXML - Implemented UsernameToken authentication.

  7. Server - Implemented database pooling and queuing system.

  8. Server - Implemented system network optimisations and prioritizing of TCP/IP packets.

  9. Server - Adapted protocolListener to allow handles with sub handles in the format https://host:port/handle/subhandle

  10. Server - Added log message to log time/size/bandwidth after upload/download.

  11. Server - Adjusted storage of messages to indicate the direction (Incoming or Outgoing).

  12. Server - Added thread names for logging purposes.

  13. Configuration - Fixed memory leaks after opening popup panels.

  14. Configuration - Tightened up GUI controls and consistancy.

  15. Configuration - Added configurable tooltips with HTML ToolTip viewer to FMC.

  16. Many other bug fixes and enchancements.

• Version: 4.1.3 Release: 1

  1. Server - Implemented Processing Modes (P-Mode).

• Version: 4.1.2 Release: 10

  1. Server - Include message content in SOAP Body and implement namespace separation for WSS encryption and signatures.

  2. Server - Library update to fix external namespace bug in SOAP Envelope when marshalling complex XML objects.

• Version: 4.1.2 Release: 9

  1. Server - Adjusted Database connection handling to abort connection instantiation if database connection fails unless in INIT mode so as to generate the connection specific settings.

  2. Server - Adjusted destinationAddress usage.

  3. Server - Updated transmission message for pull requests.

  4. Server - Added MPC attribute value to UserMessage.

  5. Server - Adjusted exception handling for unknown MPC

  6. Server - Allowed all interfaces to be instantiated during INIT mode to allow for non enabled connection specific configuration entries to be populated during first init to prevent confusion during initial configuration.

  7. Server - Rethrow SQL exception during connection should failure occur for underlying layer to handle.

  8. Server - ebXML Package Manager - Adjusted so that a client specified CPA in a Test environment will not be cached.

  9. Server - ebXML Package Manager - Removed Production environment check when checking for Override Client CPA.

  10. Server - ebXML Package Manager - Adjusted CPA TTL to be in seconds instead of milliseconds.

  11. Server - ebXML Package Manager - Removed Production environment check when checking for Override Client CPA.

  12. Server - ebXML Package Manager - Added null checks when recipient is unknown but error message must be generated.

  13. Client - Implemented new exit status code handling.

  14. Client - Added -q for a single messageID query instead of using -Q for testing multiple messageIDs from the messageID temp store file.

  15. Client - Added EMPTY_MESSAGE_PARTITION_CHANNEL exit code for PullRequest errors.

  16. Client - Removed RosettaNet specific PIP references.

  17. Configuration - Adjusted alignment of buttons in button panel, adjusted alignment of administration menu bar, added administration version to menu About.

  18. Configuration - Changed CPA config Override Client CPA in Production to Override Client CPA, removed defunct CPA registry URL field.

  19. Configuration - Set usage to only display Production and Test, admin connections are fixed as Usage: Admin.

  20. Configuration - Adjusted admin console colours for better readability, recalled last viewed configuration on reload.

  21. Administration - Added server log level notification on new admin connection to adjust gui controls.

  22. Administration - Fixed menu options availability when disconnected.

• Version: 4.1.2 Release: 4

  1. Server - Added readMimeMultiPart from ebMS connections to PackageManager, unsynchronized some methods to prevent deadlock.

  2. Server - Added better logging for pullrequests.

  3. Server - Adjusted readHTTPBoundary finishing check to only check if the line ends with boundary + "--" rather than more explicit equals.

• Version: 4.1.2 Release: 3

  1. All - Implemented Pull Requests.

  2. Server - Added findPartnerIdentifierByEndpoint method for use with PullRequests.

  3. Client - Fixed required argument checking arrays.

• Version: 4.1.2 Release: 2

  1. Server - Adjusted ebXML.RemoteOut to use custom Socket instead of HttpsURLConnection due to synchronous transmission problems.

  2. Server - Shifted message construction around, took Receipt, Error and PullRequest construction out of createV3Envelope and placed construction code into createV3Receipt, createV3Error and createV3PullRequest respectively, renamed createV3Envelope to createV3Request.

  3. All - Added PartnerType enum for PartnerIdentifiers one of {LOCAL_PARTNER, REMOTE_PARTNER, PULL_PARTNER}.

• Version: 4.1.1 Release: 3

  1. All - Renamed Packing to Package and PIP to Schema.

  2. All - Renamed PipMapping and PIPEntry to SchemaMapping and SchemaEntry.

  3. Administration - Added expiry date to Licence check.

  4. Server - Rebuilt with new Metro Webservices libraries.

• Version: 4.1.1 Release: 1

  1. Configuration - Centered Connection Config arrow between buttons, Added delayed draw of watermark when resizing or moving to prevent 100% CPU usage due to downscaling of watermark image during continuous resize.

  2. Server - Implemented chained EntityResolver as well as deeper search mechanisms for the location of XML Schemas.