Altair Panopticon Visualization Server Installation and Reference Help - Setting Up Panopticon Visualization Server on Windows

NOTE	To support Python Transform, the following files are included in the installation zip file: · start_Python_connectivity.sh · start_Python_connectivity.bat · pyro.py Refer to Python Integration for more information.

2. Create the AppData folder (i.e., vizserverdata) and ensure that the user account Local Service running Tomcat has read/write and execute permissions to this folder.

Example: c:\vizserverdata

3. Specify the license type that will be used. Use either of the following license types:

· Volume License file (DatawatchLicense.xml) that must be copied to the designated AppData folder, or

· Altair Units license. Refer to Using Altair Units License in the Panopticon Visualization Server for more information.

· Hosted Altair Units license. Refer to Using the Hosted Altair Units License in the Panopticon Visualization Server for more information.

4. Copy the extracted panopticon.xml file into the Tomcat config folder (\Apache Software Foundation\Tomcat 9.0\conf\Catalina\localhost). This file contains the following information:

NOTE	Update this file if the path of the environment variable DatawatchVDDAppData is different from c:\vizserverdata or the data folder created in step 2.

5. Copy the panopticon.war file into the Tomcat webapps folder (\Apache Software Foundation\Tomcat 9.0\webapps).

6. For a basic install using the Tomcat inbuilt XML file user directory, copy the provided tomcat-users_example.xml and overwrite the existing tomcat-users.xml file which is available in the Tomcat config folder (\Apache Software Foundation\Tomcat 9.0\conf).

The provided tomcat-users_example.xml contains the following roles and users:

NOTE

In Panopticon 2020.0 and onwards, the Administrators.txt and AdministratorGroup.txt files are no longer used to authorize administrator users. The function provided by these files has been replaced by a set of properties in Panopticon.properties:

access.administrator.groups=admin

access.default.roles=VIEWER

access.designer.groups=designer

access.viewer.groups=user

The access.default.roles property defines the default roles assigned to any user accessing the server, defaulting to VIEWER. The administration (access.administrator.groups property) and content creation (access.designer.groups property) on the server are mapped by default to groups named "admin" and "designer".

For more complex authentication and user directory options, see section [3] Authentication.

7. You can also opt to install Java data connector’s dependencies, and JDBC driver JAR files as required.

NOTE

· Before proceeding to step 8, ensure the Tomcat temp folder (e.g., (\Apache Software Foundation\Tomcat 9.0\temp) is available.

· You can opt to choose a different temp folder with the CATALINA_TMPDIR environment variable. For example:

Variable	Value
CATALINA_TMPDIR	C:\tomcat\dev\temp

8. Start Tomcat to deploy the .war file.

The panopticon folder is extracted in the Tomcat webapps folder:

Also, the .repository, CacheData, Datatables, JavaScriptConfiguration, Schedule, Sounds, Statistic, Themes, Token, and UserData folders are generated in the AppData folder (c:\vizservdata) along with the DefaultSettings.xml, Panopticon.properties and Parameters.json files.

9. Increase the Java heap size of Tomcat.

10. You should now be able to log on to the Panopticon Visualization Server using the following:

[Host Name]:[Port]/[Name of your application]

For example:

http://localhost:8080/panopticon

The more advanced configuration options are also discussed in this document.

NOTE

The Panopticon Visualization Server supports different user roles. To have full access to all the services, the user is required to have an ADMINISTRATOR and DESIGNER roles.

For example, logging on using the ADMINISTRATOR role added in step 6 (i.e., admin/admin), will display:

All of the available user specific folders in the authentication method used are displayed.

However, logging on with a DESIGNER role (i.e., designer/designer) will only display:

The allowed features available for the DESIGNER role is extensively discussed in the Web Authoring Guide.

For more information on how to set up the user groups and map them to the user roles, refer to Supported Roles in the Panopticon Visualization Server.