Where is the CONNECT source code repository?

https://github.com/CONNECT-Solution/CONNECT

Do I need to build CONNECT from source code?

You can Download CONNECT as a pre-compiled binary. 

Can CONNECT be used for Carequality implementation?

No

How do I configure my CONNECT TLS/SSL settings?

blah

Why is CONNECT throwing SAML exceptions?

blah

What are the different layers of CONNECT, and how are they used?

• Entity - Internal endpoints used to construct NwHin requests to be sent to an external Gateway via NwHin endpoints.
• NwHin - Endpoints that will be hit from an external gateway. This is the crossover point between the Initiating and Responding gateways. For the Initiating gateways, this will be an outbound request to another implementor. For the Responder, this will be an inbound request in which the gateway is expected to process and respond to the request by calling its Adapter.
• Adapter - Implementor specific components which will serve as the communication layers between CONNECT and the proprietary databases,architecture, and services of the implementor. These get called by CONNECT through the NwHin layer when the gateway in question is a responder to a request.

What are all these beans defined in the proxy property files for each service?

Each service may have a respective property file to configure a proxy to be used when communicating with a service. By default, there may be up to four pre-configured beans: NoOp, Java, Secured and Unsecured beans.

• NoOp - Will always return a successful invocation, or a blank response - depending on the expected context of the bean. Does not invoke any web services or call any methods.
• Java - Will use pure java calls to CONNECT code, can be substituted for any java class compiled with the CONNECT EAR, including custom Entity, NwHin, and Adapter implementations
• Secured - Will use a secured port to communicate to a given endpoint configured via the internalExchangeInfo.xml file.
• Unsecured - will use an unsecured port to communicate to a given endpoint configured via the internalExchangeInfo.xml file.

As an implementer, how do I configure my own Entity, NwHin, and Adapter processors?

Injection points into CONNECT are controlled by Spring Bean lookups. Injection can be done in one of 2 ways: Java or Webservices.

For Java injections, simply point the bean for the service you wish to replace in its respective property file to your custom implementation. For example, to change the Document Submission Adapter, the "adapterdocsubmission" alias inside the DocumentSubmissionProxyConfig.xml file would be changed to your custom bean. By default, there are example beans for most services with the "java" postfix - in this case "adapterdocsubmissionjava"

For webservice injections, the bean alias would be set to either the secure or unsecure beans already defined in the respective XML file. Instead of injecting a custom java class, the appropriate endpoint inside of the internalExchangeInfo.xml file must be changed to point to the URL of where your custom service is deployed. As an example, if we wanted to change the Document Submission Adapter endpoint, we would find the "adapterxdrsecured" service name (Or "adapterxdr" if you are using an unsecured service) and change its URL to point to the custom service. It should be noted that these custom services must implement their respective WSDLs

What is the difference between Standard and Passthrough Modes?

Passthrough does not invoke policy engine. 

What do I need to do if I only want some services deployed, and not others?

When building CONNECT, you may specify the appropriate maven profiles (DQ, PD, DS, DDS, admingui, etc.), which will compile and bundle the services into the resulting EAR file. Simply use the respective profiles only for the services you wish to deploy.

What is the Admin GUI, and how can I use it?

Admin GUI is meant to serve as an extension to CONNECT in order to manage the gateway, certificates, properties, and perform basic queries for information about the gateway. Admin GUI is also capable of serving a cross query client, as well as an interface for viewing Audit and Failure logs. Admin GUI may be deployed either on the same servlet container, as well as on a different server entirely (There may be some additional setup steps in order to configure your Admin GUI onto an external server).

A full user manual on the Admin GUI can be found here.