...
As an implementer, how do I configure my own Entity, NwHin, and Adapter processors?
( Insert your java class into the bean properties, or if it is a webservice you want CONNECT to consume, change the endpoint to point to your service in the internalExchangeInfo)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 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?
...
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?
(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)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).