Environment Setup

Unified UI internally relies on inter server communication. Therefore, if we consider the scenario of opening a HRM page from the Financial application, the request to open the HRM page flows through the Financial Management server and it internally processes the request and submits it to the HRM server. The HRM server sends the response back to the Financial server where the response is processed and sent back to the browser.

Unified UI Environment Setup Example Diagram. Starts with a browser request to open an HRM page that is routed to the Advantage Financial Management Server. Next, the request is forwarded from FIN to the Advantage HRM Server. HRM then sends a response to FIN and FIN processes the response, which is sent back to the browser to complete the process

For unified UI to work seamlessly, all applications hosted on different servers or ports should be accessible to each other. This is the basic requirement needed. Additionally, the application URLs need to be configured in the configuration file placed in <VLS_HOME>/VLS/bin/server_bootstrap.properties.

Overall, the goal of unified UI is to allow users to seamlessly navigate between applications, although which application URL the user should use should be based on the number of users registered on a particular application. In addition, there is no true single URL as the external facing applications such as Employee/ Manager/ Travel and Mobile have restricted functionalities. These applications serve only a subset of applications where pages are whitelisted. Please refer to the “Whitelisting of Application Metadata” section in this guide.

The following diagram explains the high-level deployment structure with respect to the usage of URLs for application access.

Diagram showing Unified Internal Application URLs and Unified External facing Application URLs. For Unified Internal Application URLs, users can use any of these application URLs within the organization's internal network to navigate between any of the following application functionalities: Administration, Financial, HRM, and PB. Administration functionalities get routed to Admin, Financial functionalities get routed to Admin and FIN, HRM functionalities get routed to Admin and HRM, and PB functionalities get routed to Admin and PB. For Unified External facing Application URLs, users can use any of these application URLs outside the organization's network to navigate between any of these application functionalities: Administration (Mobile app), Financial (Mobile/Travel), and HRM (Mobile/Employee/Manager). Mobile application and External facing applications are separate URLs. Users can use one mobile app URL while external facing apps have a different URL. Administration (Mobile app) functionalities route to Admin, Financial (Mobile/Travel) functionalities route to both Admin and FIN, and HRM (Mobile/Employee/Manager) functionalities route to both Admin and HRM. There are also some URLs that are common between both the internal and external facing applications. Finally, VSS routes to both VSS and VSS Common