Client and FMC

  1. I receive a 'Response: No appropriate protocol (protocol is disabled or cipher suites are inappropriate). Server might require mutual SSL authentication' message when trying to connect to and FMS server from FMC.

    Ensure that the client side java java.security file entry for jdk.tls.disabledAlgorithms does not include the required protocol. For FMC revisions prior to 5.4.2 build 7 the required transport protocol is TLSv1.

    Ensure that the FMS server private certificate for the relevant listener is valid and has not expired.

  2. I get the following SAXParseException when trying to send a message.

    \
    \2019-04-30 13:30:04,637 WARNING com.flame.client.as4.AS4ClientAPI <init>() \
    \  - Preparing message for sending to host https://ebis-int.open-grid-europe.com/ibis/as4/sync 
    \2019-04-30 13:30:04,637 INFO com.flame.client.as4.api.Client createEnvelope() \
    \  - Creating Envelope with messageID 'AS4-16A6E0248DC-D7C8C@undefined' 
    \2019-04-30 13:30:04,669 INFO com.flame.client.as4.api.Client createPayload() \
    \  - Creating Payload for messageID 'AS4-16A6E0248DC-D7C8C@undefined' 
    \[Fatal Error] :1:1: Content is not allowed in prolog.
    \ERROR:  'Content is not allowed in prolog.'
    \2019-04-30 13:30:04,675 SEVERE com.flame.client.as4.api.Client transmit() \
    \  - org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog. 
    \
    \          

    Ensure that all arguments are correctly set when invoking the AS4 light client. Eg. ensure that arguments such as '-ag' are followed by a value which in this case would be the Agreement Reference.

  3. When trying to send a message with the client process I get an unknown connection issue message.

    Try to connect to the remote FMS server using openssl or telnet on port 443. If no log messages appear at the remote FMS then the remote server is not listening on port 443. Ensure that no other process such as a web server is listening on port 443 on the remote server. Also ensure that the user starting up FMS has permissions to bind to port 443.

  4. I can't start the client because the Java command cannot be found!

    Ensure Java is installed and setup correctly. Open a console and type java -version it should return version 1.8.0 or higher.