Version History
| Version | Date | Modified By | Description of Modification |
|---|---|---|---|
| 0.1 | 12/14/2018 | Paul Tambellini | Initial version |
| Table of Contents |
|---|
Overview
Admin GUI can be deployed on a remote server separate from where the CONNECT ear is deployed. Most services within the Admin GUI have been coverted to use webservices to interact with the CONNECT ear allowing Admin GUI to interact over the internet and does not have to be included on the same server as CONNECT ear. This process has mostly been done in CONNECT 5.2.
- On two different machines, start the application server. Both servers must have the mysql-connector-java jar deployed because the Admin GUI will have to write login information to where the Admin GUI war is deployed and all other services will write to the database that is deployed on the server containing the CONNECT ear.
- On one machine, deploy the 5.2 or above CONNECT ear because most of the web services have decoupled from the CONNECT ear in 5.2.
- On another machine, deploy the 5.2 or above Admin GUI war because most of the web services have decoupled from the CONNECT ear in 5.2.
- Update exchangeInfo.xml in the properties directory of the server which hosts the CONNECT ear. Change every URL from localhost to the ip address of machine which represents the localhost. In order for Exchange Manager to be viewed by the Admin GUI, exchangeInfo.xml has to be pointed to the ip address of the CONNECT ear server. This must be done because when the Admin GUI looks upon the CONNECT ear server the exchangeinfo services will be pointed to the localhost which the Admin GUI will view as its own localhost and not the ip address where the information is currently being stored.
- Update exchangeInfo.xml and internalExchangeInfo.xml in the properties directory of the server which hosts the CONNECT Admin GUI. Change localhost to the ip address of where the CONNECT ear is located. ExchangeInfo.xml is pointed to the ip address of the CONNECT ear server in order to ping the services. InternalExchangeInfo.xml has to be pointed to where the CONNECT ear is located to have the web services be able to interact. This must be done because when the Admin GUI looks upon the CONNECT ear server the internalexchangeinfo services and the exchangeinfo services will be pointed to the localhost which the Admin GUI will view as its own localhost and not the ip address where the information is currently being stored.Test Data Loader will have to be converted to a web service. Currently, Test Data Loader writes to the database where the Admin GUI war resides.
- User Management which includes login information and account creation will not be converted to a web service at the moment but should be determined if any vulnerabilities exist.
...