Table of Contents |
---|
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 and follow our deployment instructions as a pre-compiled binary.
Can CONNECT be used for Carequality implementation?
...
Why is CONNECT throwing SAML exceptions?
blah
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?
( Insert your java class into the bean properties, or if its an endpoint, change the endpoint to point to your service in the internalExchangeInfo)
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, 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?
(Insert details about how you can use it to invoke cross query clients, configure the properties of CONNECT, and view failure/event logs. Mention it does not need to be on the same server)