This section details:
To install Univiewer Web Console, the administrator must deploy the univiewer_webconsole_<version>_all_os.war file on a servlet engine (Tomcat supported).
To deploy the Univiewer Web Console, follow the steps described below, in sequence:
For example, if Tomcat is used to run Univiewer Web Console, this will be done automatically (described below).
If you have not already installed a servlet engine, Tomcat can be installed.
The minimum configuration required for Tomcat is:
To access the Tomcat Web Application Manager, launch a Web browser and enter the URL corresponding to the Tomcat Web application manager servlet. For instance: http://localhost:8080/manager/html
At the bottom of the window, in the Deploy frame, a new application can be declared
The Univiewer Web Console application is displayed in the list. Click the name of the application to start it.
The following topics detail how to configure Univiewer Web Console. They are not mandatory.
The Univiewer Web Console web.xml file is located in the WEB-INF subdirectory in the univiewer_webconsole application in Tomcat.
The Univiewer Web Console configuration can be modified before starting the Univiewer Web Console application but this is not mandatory. The configuration file can be set at the beginning of the web.xml file:
<display-name>Univiewer Web Console 6.x</display-name>
<description>Univiewer Web Console 6.x</description>
- <!-- you can uncomment the next context param named "config" if you don't want the default configuration file to be considered (You can fill in the param-value tag in this manner => <param-value>D:\my\path\my_UVC_config.properties</param-value> )
-->
- <!--
<context-param>
<param-name>config</param-name>
<param-value>ENTER_YOUR_PATH_FOR_FILE_UVC_config.properties</param-value>
<description>Configuration file</description>
</context-param>
-->
Univiewer Web Console uses the Apache log4j library. The two configuration files: UVC_Config.properties and log4j.xml files are located by default in the WEB-INF/conf subdirectory.
If these files are to be modified, it is best to modify the web.xml file (enter the full path of these files) and to move them outside the UVC installation to avoid losing the modifications in the event of an upgrade of Univiewer Web Console.
The Univiewer Web Console can include a refresh policy for security information variables in the web.xml file located in the WEB-INF subdirectory.
If this variable is set, then the security caches managed by Univiewer Web Console are regularly refreshed according to the period defined; otherwise the security caches will not be refreshed.
To set the security cache refresh interval, add the following 6 lines to the web.xml file:
<context-param>
<param-name>security.cache.retention</param-name>
<param-value>600</param-value>
<description> Refresh period for the security file. Default is after the restart of the server<description></context-param>
</context-param>
By enabling it by default it will update the cache with the specified time. As a result, it may have an impact on Univiewer Console's performance.
The HTTPS (SSL) mode can be enabled (in Tomcat or in another application server) in order to encrypt all incoming and outgoing data.
This is especially useful if traffic must be routed through the Internet without using a VPN.
For Tomcat, the configuration is described in its official documentation, refer to http://tomcat.apache.org/tomcat-4.0-doc/ssl-howto.html
If https protocol is used memory requirements will double.
The https configuration required for Tomcat should be:
The load balancing is based on the usage of HAPROXY (http://www.haproxy.org). It is an Open Source software commonly used for this kind of need in IT. HAPROXY is installed in frontend and accepts all connections targeting a Univiewer Web Console installation on several Tomcat servers. HAPROXY balances connections from the user interface to one of the Tomcat servers according to several algorithms such as Round-robin, Weight, Number of sessions, etc.
For more information please contact your Automic support.
To upgrade the Univiewer Web Console, the user can deploy the new version of the univiewer_webconsole_<version>_all_os.war file on the servlet engine.
If the two configuration files have been modified (UVC_config.properties and log4j.xml, located by default in WEB-INF/conf), refer to section: Update Univiewer Web Console web.xml.
Keep the same name for the deployed Web Application so that the URL given to the end users will be the same. This also allows for saved bookmarks and user preferences to be kept (for example in "C:\Users\<user>\univiewer_console\localhost_8080").
From the Tomcat manager:
If the Univiewer Web Console configuration has been modified (using ssl mode for example), save the contents of the WEB-INF/conf sub-directory as it is overwritten with the upgrade in Tomcat. It must be recopied once the upgrade has completed.
If you have a new version of Univiewer Web Console, it is recommended to deploy it with the same name as the previous version. You will not have to communicate a new URL to your end users: they will get the new version automatically when they launch Univiewer Console and they will keep their bookmarks and preferences.
Refer also to section: Deploy Univiewer Web Console with Tomcat.
As of version 6.10.41, documentation new updates are posted on the Broadcom Techdocs Portal.
Look for Dollar Universe.