Overview

Troubleshooting is a long process of log analysis and knowing expected exception. Here are quick answers to common knowledge that may or may not solve the issue but provide a starting point to understanding the problems. If the issue is not found below, it may be found under CONNECT Community Forum.

...

Make sure your container server meets the minimum requirements and you have followed all of the setup instructions.

I deployed CONNECT again, and the deploy failed and it ran out of memory. Why?

This is a known issue with Spring / and Apache CXF. Remove the EAR deployment, restart the server, and redeploy.

...

How can we implement/Setup MPI?

Message Passing Interface Master Patient Index (MPI) is not part of CONNECT. There are several MPI's available like OpenMPI, MirthMatch, etc NextGen Connect Integration Engine, etc.

You will need to create an Adapter to connect to these MPIs. 

...

This error generally occurs when the saml.properties, signature.properties, and truststore.properties files in the configuration directory are either not found or the values in those files are incorrect/missing.

CONNECT failing to complete SSL Handshake?

Add the system property '-Djavax.net.debug=ssl' to your JVM. This property will output some pretty verbose logging but it's a good way to track the SSL handshake.

...

<datasource jta="true" jndi-name="<<jndi name>>" pool-name="<<data_source name>>" enabled="true" use-ccm="true">
    <connection-url>jdbc url</connection-url>
    <driver-class>com.mysql.jdbc.Driver</driver-class>
    <driver>mysql-connector-java-5.1.10.jar</driver>
    <security>
        <user-name>username</user-name>
        <password>password</password>
    </security>
    <validation>
        <check-valid-connection-sql>select 1</check-valid-connection-sql>
        <validate-on-match>false</validate-on-match>
        <background-validation>true</background-validation>
    	<background-validation-millis>10000</background-validation-millis>
	</validation>
</datasource>

SOAP Faults

Large Payload testing: "XDS MISSING DOCUMENT" from my submissions?

The payload did not convert correctcorrectly. It The payload should be in base64 encode format from file:///<file path location> .

For example:
your encode value should be simliar like this ZmlsZTovLy9jOi9sYXJnZXBheWxvYWQvb3V0Ym91bmQvdGVzdC50eHQ=

...

Make sure your GatewayPropDir property points to the nhinc property folder.

Validation tests are failing because of certificate path problems

The keystores were set up for you automatically. If this is the case, your gateway is using self-signed certificates. The Java keystore, gateway.jks, contains your gateway's certificate, which is known by the alias "gateway". This certificate has also been imported into the truststore, cacerts.jks, so that the gateway can make secured connections to itself. You may make secured connections to yourself when testing, so that your local gateway acts as both the requesting and responding gateway, and also at other times depending on your gateway configuration. If you want to send a message to a remote gateway, the same "gateway" certificate must be imported into the remote gateway's truststore.