Display Manager 13 - Altair Manager 13.0... · 2019-04-18 · Display Manager 13.0 Administrator’s Guide Remotely Visualize Your Datasets fo r Rapid Collaboration and Innovation

Display Manager 13.0

Administrator’s Guide

Remotely Visualize Your Datasets for Rapid Collaboration and Innovation

Display Manager 13.0 Administrator’s Guide

Display Manager 13.0 Administrator’s Guide Updated: October 8, 2015

Intellectual Property Rights Notice:

Copyrights, Trademarks, Trade Secrets, Patents & Third Party Software Licenses

Altair® PBS Works™

Enabling On-Demand Computing™

Copyright© 1994-2015 Altair Engineering Inc. All Rights Reserved.

Special Notice: Pre-release versions of Altair software are provided ‘as is’, without warranty of any kind. Usage is strictly limited to non-production purposes.

Display Manager™ 2007-2015; Compute Manager™ 2007-2015; PBS™ 1994-2015; PBS Professional® 1994-2015; PBS Application Services™ 2008-2015; PBS Analytics™ 2007-2015; and PBS Desktop™ 2007-2012; PBS Portal™ 2007-2011; e-BioChem ™ 2007-2013; e-Compute™ 2000-2007; e-Render™ 2006-2010; OpenPBS® 1994-2003 and Personal PBS® 2007-2012.

Other Altair software applications include:

Altair Simulation Cloud Suite: Simulation Manager™ 2003-2015; Compute Manager™ 2003-2015; Display Manager™ 2003–2015; and Process Manager™ 2003-2015.

Altair HyperWorks®: HyperMesh® 1990-2015; HyperCrash® 2001-2015; OptiStruct® 1996-2015; RADIOSS®1986-2015; HyperView® 1999-2015; HyperView Player® 2001-2015; HyperStudy® 1999-2015; HyperGraph® 1995-2015; MotionView® 1993-2015; MotionSolve® 2002-2015; HyperForm® 1998-2015; HyperXtrude® 1999- 2015; Process Manager™ 2003-2015; Templex™ 1990-2015; TextView™ 1996-2015; MediaView™ 1999-2015; TableView™ 2013-2015; BatchMesher™ 2003-2015; HyperMath® 2007-2015; HyperWeld® 2009-2015; HyperMold® 2009-2015; Manufacturing Solutions™ 2005-2015; solidThinking® 1993-2015; solidThinking Inspire® 2009-2015; solidThinking Evolve® 1993-2015; Durability Director™ 2009-2015; Suspension Director™ 2009-2015; AcuSolve® 1997-2015; AcuConsole® 2006-2015; SimLab® 2004-2015; Virtual Wind Tunnel™ 2012-2015; FEKO™ 1999-2015 and VisSim™ 1989-2015.

Altair Packaged Solution Offerings (PSOs) Copyright© 2008-2015 Automated Reporting Director™ 2008-2015; Impact Simulation Director™ 2010-2015; Model Mesher Director™ 2010-2015; Model Verification Director™ 2013-2015; and Squeak and Rattle Director™ 2012-2015.

Altair intellectual property rights are protected under U.S. and international laws and treaties. Additionally, Altair software is protected under patent #6,859,792 and other patents pending. All other marks are the property of their respective owners.ALTAIR ENGINEERING INC. Proprietary and Confidential. Contains Trade Secret Information. Not for use or disclosure outside of Altair and its licensed clients. Information contained in Altair software shall not be decompiled, disassembled, “unlocked”, reverse translated, reverse engineered, or publicly displayed or publicly performed in any manner. Usage of the software is only as explicitly permitted in the end user software license agreement.

ii


Copyright notice does not imply publication.

Third Party Licenses

Software Security Measures:

Altair Engineering Inc. and its subsidiaries and affiliates reserve the right to embed software security mechanisms in the Software for the purpose of detecting the installation and/or use of illegal copies of the Software. The Software may collect and transmit non-proprietary data about those illegal copies. Data collected will not include any customer data created by or used in connection with the Software and will not be provided to any third party, except as may be required by law or legal process or to enforce our rights with respect to the use of any illegal copies of the Software. By using the Software, each user consents to such detection and collection of data, as well as its transmission and use if an illegal copy of the Software is detected. No steps may be taken to avoid or detect the purpose of any such security mechanisms.

iii

http://www.altairhyperworks.com/ClientCenter3rdPartyLicense.aspx

http://www.altairhyperworks.com/ClientCenter3rdPartyLicense.aspx


Technical Support

This document is proprietary information of Altair Engineering, Inc.

Location Telephone EmailAustralia +1 800 174 396 [email protected] +86 21 6117 1666 [email protected] +33 1 4133 0992 [email protected] +49 7031 6208 22 [email protected] +91 80 66 29 4500

+1 800 425 0234 (Toll Free)[email protected]

Italy +39 800 905595 [email protected] +81 3 5396 2881 [email protected] +82 70 4050 9200 [email protected] +91 80 66 29 4500


North America +1 248 614 2425 [email protected] +49 7031 6208 22 [email protected] +46 46 460 2828 [email protected] +91 80 66 29 4500


South America +55 11 3884 0414 [email protected] +44 1926 468 600 [email protected]

iv

Contents

Introduction to Display Manager 1

Overview of the Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Prerequisites 3

Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Execution Host Requirements for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Execution Host Requirements for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Sample Configurations for Execution Hosts for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Sample Configurations for Execution Hosts for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Web Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Java Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Prerequisites for installing Display Manager Agent for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Prerequisites for installing Display Manager Agent for Windows . . . . . . . . . . . . . . . . . . . . . . . . . 8

Operating System Groups and User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Display Manager Deployment Options 11

Network Implementation of Display Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Distributed Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Single Host Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing Display Manager 15

Display Manager Installation on Linux 17

Starting the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Splash Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Altair Applications and Service Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Access Management Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

v

License Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Access Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Authentication Module for AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Authorization Module for AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

GPU Configuration for the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34GPU Configuration for the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Installation Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Display Manager Installation on Windows 39

Starting the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Splash Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Altair Applications and Service Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Access Management Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50License Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Access Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52


PBS Works Service User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Installation Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Display Manager Console Installation 61

Starting the Installer in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61License Agreement Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Altair Applications Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Display Manager Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Database Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Access Management Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

vi Contents

License Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Access Management Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66


GPU Configuration for the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68GPU Configuration for the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68PBS Works Super User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Pre-Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Installation Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Installing DM Execution Components for Linux 73

Display Manager Add-on Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Install Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Configure PBS and PAS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75GPU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Pre-Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Installing the Display Manager Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Choose Install Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79AMS Configuration for Display Manager Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Installation Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Installation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Install Display Manager Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84License Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85GPU Configuration for Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Pre-installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Unconfigure PBS and PAS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Installing DM Execution Components for Windows 89

Display Manager Add-on Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Starting the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Install Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Configure PBS and PAS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Pre-Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Installing the Display Manager Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Choose Install Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94AMS Configuration for Display Manager Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Installation Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Installation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Install Display Manager Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Contents vii

Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Pre-installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Unconfigure PBS and PAS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Uninstalling Display Manager 103

Configurations 107

PBS Applications and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Verifying Display Manager Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Access Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109PBS Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110GPU Configuration as PBS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111PAS Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111GPU Resource Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Display Manager Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Display Manager Router Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Changing the DM Router Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Display Manager Settings Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Client Configuration for Application Launch Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Setup the ALF Desktop Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Modify the ALF Client Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Starting, Stopping and Restarting 119

PBS Works Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Determine the PBS Works Portal Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Starting the PBS Works Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Stopping the PBS Works Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Restarting the PBS Works Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120DM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Determine the DM Router Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Starting DM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Stopping DM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Post Installation Administration 123

Network Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

viii Contents

Managing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Location of Application definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Main components of Display Manager Application Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 124Application specific for Linux and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Adding a New Application for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Adding a New Application for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Display Manager Specific Information for Application Definitions . . . . . . . . . . . . . . . . . . . . . . . . 128

Managing Graphical Node Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Modify the Cluster GPU Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Modify the Node GPU Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Configuring the Browser for Application Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Keyboard Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Troubleshooting 135

Quick Troubleshooting Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Resource Availability Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Resource Acquisition Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Only the display session is shown but not the application that was started . . . . . . . . . . 138Graphic Card Compatibility Issues with Display Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Contents ix

x Contents

1. Introduction to Display Manager

Display Manager is a platform for collaboration and remote visualization of applications and data. It enables high performance remote display of applications over the networks using a web browser. It fosters team work and communications by allowing to share the sessions among users.

Overview of the GuideThis guide describes how to install and configure Display Manager. The following topics are cov-ered in this guide:

• Prerequisites• Display Manager Deployment Options

1


• Installing Display Manager• Display Manager Installation on Linux• Display Manager Installation on Windows• Display Manager Console Installation• Installing DM Execution Components for Linux• Installing DM Execution Components for Windows• Uninstalling Display Manager• Configurations• Starting, Stopping and Restarting• Post Installation Administration• Troubleshooting

What’s NewHere’s a quick look at the latest features available in Display Manager 13.0:

• Redesigned framework for application launch and monitoring to enable tighter integra-tions and control.

• Display Manager can now control sessions and applications launched on Windows execu-tion hosts through the tight integration with Microsoft Remote Desktop Protocol (RDP) and HP Remote Graphics Software (RGS).

• Redesigned interface with PBS Application Services for improved robustness and light-weight application integration. The minimum amount of configuration edits to publish an application through Display Manager has been greatly reduced.

• Redesigned GPU resource management reduces the dependencies on the workload man-ager and the file system configuration.

• Greater control over session timeout. The waiting time can be customized based on site requirements. While waiting, the session can be aborted if it is taking too long to start.

• Improved web browser based client allows to dynamically resize remote Linux desktops to match the actual viewer window area.

• Now, when configured to do so, Display Manager will provide for the remote session tem-porary files to be copied in a permanent location when the session is terminated.

2 Introduction to Display Manager

2. Prerequisites

Minimum System Requirements

Execution Host Requirements for LinuxOperating System Any Linux distribution in the Red Hat Enterprise or SUSE Enterprise fam-

ilies which contains GLIBC 2.3.2 or laterGraphics • Only NVIDIA and [AMD] ATI cards are supported.

• For Linux, install the 3D adapter drivers provided by the manufacturer.• Full 3D acceleration or Pixel Buffer support should be enabled by the

Linux drivers.GPU cores and GPU memory

Specific to the applications used.

CPU cores and Physical memory


Others • For running Display Manager sessions, X Server and application on local display must be configured and working. X Server must be config-ured to export True Color (24 bit or 32 bit) visuals.

• Use Virtual Private Networking or secured channels for communication between clients and Display Manager server if encryption is required.

• The execution host must be able to access and run the applications avail-able through Display Manager.

3


Execution Host Requirements for Windows

Sample Configurations for Execution Hosts for LinuxHere are some sample execution host configurations on which Display Manager has been tested for Linux.

Operating System Windows Server 2007, 2008 R2 and 2012Graphics Only NVIDIA and [AMD] ATI cards are supported.CPU cores and Physical memory


Others • Use Virtual Private Networking or secured channels for communication between clients and Display Manager server if encryption is required.

• The execution host must be able to access and run the applications avail-able through Display Manager.

If Remote Desktop Protocol (RDP) is in use, then ensure that the latest updates and patches are installed. Refer Remote Desktop Protocol (RDP) 8.0 update for Windows 7 and Windows Server 2008 R2 for more infor-mation.

Graphics Card Model Processor OS RAM

System 1 NVIDIA Quadro FX 5500

2 x AMD® Opetron® CPU 2220 (4 cores total)

RHEL WS R4 (Nahant Update 6)

4 GB

System 2 NVIDIA Quadro 600

2 x Intel® Xeon® CPU E31280 @ 3.50GHz (8 cores total)

RHEL Client R 5.1 (Tikanga)

32GB


2 x Intel® Xeon® CPU X5675 @3.07GHz(12 cores total)

Cent OS 5.5 48GB


2 x Intel® Xeon® CPU X5675 @3.07GHz (12 cores total)

Cent OS 5.5 48GB

4 Prerequisites

https://support.microsoft.com/en-us/kb/2592687

https://support.microsoft.com/en-us/kb/2592687


Sample Configurations for Execution Hosts for WindowsHere are some sample execution host configurations on which Display Manager has been tested for Windows.

System 5 NVIDIA (2) Quadro 4000

2 x Intel® Xeon® CPU E5620 @ 2.40GHz(8 cores total)

Cent OS 5.5 32GB


2 x Intel® Xeon® CPU E5620 @ 2.40GHz (8 cores total)

RHEL Server R 6.3 (Santiago)

24GB


Intel® Xeon® CPU E5620 @ 2.40GHz (4 cores)

RHEL 5 4GB

System 8 [AMD] ATI Device 6809

Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz (4 core)

Cent OS 6.4 32GB

System 9 NVIDIA Quadro K4000, NVIDIA Quadro 2000


SLES 11 SP3 32GB

System 10 NVIDIA Quadro K5000


SLES 11 SP3 32GB



Intel(R) Pentuim(R) CPU 3.00GHz (2 core)

Windows 2008 R2 4GB


Intel(R) i7 CPU 2.20GHz (4 core)

Windows 2012 R2 8GB


Intel(R) i7 CPU 2.20GHz (4 core)

Windows 2012 R2 8GB


Prerequisites 5


Web Server Requirements

Web Client Requirements

Java RequirementJava Extensions are required on the browsers. Java Runtime Environment (JRE) should be avail-able on the Web Client.

Download the latest JRE version from https://java.com/en/download/.

For information about installing Java, refer to http://www.java.com/en/download/help/down-load_options.xml.

To enable Java, refer to http://www.java.com/en/download/help/enable_browser.xml.

To enable NPAPI in Chrome, refer to https://java.com/en/download/faq/chrome.xml#npapi-chrome.

Operating System • Windows Server 2007, 2008 R2 and 2012• Red Hat Enterprise Linux version 5 and later• SUSE Linux Enterprise Server version 10 and later

CPU Intel(R) Xeon(R) CPU X5675 @ 3.07GHz or fasterPhysical Memory 8GB or higher

CPU Pentium 4/Xeon, 2.0 GHz or fasterRAM 2 GB or higherSupported Browsers On Windows:

• Mozilla Firefox ESR (Extended Support Release) 24, 31, and 40• Google Chrome 40 and 41• Microsoft Internet Explorer 8, 9, 10, and 11On Linux:• Mozilla Firefox ESR 31Note: Java Extensions are required on the browsers.

6 Prerequisites

https://www.mozilla.org/en-US/firefox/organizations/

https://java.com/en/download/

http://www.java.com/en/download/help/download_options.xml

http://www.java.com/en/download/help/enable_browser.xml

https://www.mozilla.org/en-US/firefox/organizations/

https://java.com/en/download/faq/chrome.xml#npapichrome


For troubleshooting the Java installation, refer to http://www.java.com/en/download/help/trouble-shoot_java.xml.

Prerequisites for installing Display Manager Agent for LinuxThe following prerequisites have to be met to allow the Display Manager Agent (DM Agent) to configure ngpus on PBS MOMs (Machine Oriented Miniservers).

Configuring GPU Resources

A custom resource called ngpus has to be configured for Display Manager sessions. This can be adjusted any time.

The ngpus setting limits the number of concurrent display sessions that can utilize the GPU on the host. When more concurrent sessions are using the same GPU, the display session performance will be affected.

Apart from configuring GPUs, performance can be improved by increasing host memory, network performance and CPU cores.

Configuration of PBS Server

PBS Server should have been configured using either the PBS Works 13.0 installer or the PBS Works 13.0 Display Manager add-on installer to make sure that ngpus are configured as a custom resource.

The PBS Works 13.0 installer will perform the following:• Install the DM components• Define a new custom resource called ngpus• Set the custom resource at each execution host

The PBS Works 13.0 Display Manager add-on installer will perform the following:• Configure PBS and PAS Server• Installing the Display Manager Router• Install Display Manager Agent• Unconfigure PBS and PAS Servers

PBS Privileges

For the Display Manager Add-on installer to set the custom resource at each execution host, the root user of all execution hosts must be granted operator access. Prior to starting the DM Add-on installer, issue the following command to grant this access:

Prerequisites 7

http://www.java.com/en/download/help/troubleshoot_java.xml


qmgr: s s operators+=root@*

If this access is not granted, then you will manually have to set the custom resource by issuing a qmgr set command for each execution host after installation of DM. For example:e.g. set node <node> resources_available.ngpus = 4

After applying such a setting, every user named root from any host on any network will be able to operate on jobs from other users. To prevent misuse, restrict the above setting to the sub domain containing the execution hosts or list them one by one.

After installing Display Manager components, you can remove the root user of the PBS MOMs from the operators list on the PBS server using the command: qmgr: s s operators-=root@*

Prerequisite Resource Libraries for DM Agent

If the following libraries must be installed before attempting to install DM. If they are not, they can be installed using the appropriate system tools (e.g. RPM, YUM, YAST etc.).

Prerequisites for installing Display Manager Agent for WindowsConfiguration of PBS Server

PBS Server should have been configured using either the PBS Works 13.0 installer or the PBS Works 13.0 Display Manager add-on installer.

The PBS Works 13.0 installer will Install the DM components.

The PBS Works 13.0 Display Manager add-on installer will perform the following:

libc.so.6()(64bit)

libc.so.6(GLIBC_2.2.5)(64bit)

libc.so.6(GLIBC_2.3)(64bit)

libcrypt.so.1()(64bit)

libdl.so.2()(64bit)

libdl.so.2(GLIBC_2.2.5)(64bit)

libGL.so.1()(64bit)

libGLU.so.1()(64bit)

libICE.so.6()(64bit)

libm.so.6()(64bit)

libm.so.6(GLIBC_2.2.5)(64bit)

libpam.so.0()(64bit)

libpthread.so.0()(64bit)

libpthread.so.0(GLIBC_2.2.5)(64bit)

libpthread.so.0(GLIBC_2.3.2)(64bit)

libSM.so.6()(64bit)

libX11.so.6()(64bit)

libXaw.so.7()(64bit)

libXcursor.so.1()(64bit)

libXext.so.6()(64bit)

libXmu.so.6()(64bit)

libXt.so.6()(64bit)

libXv.so.1()(64bit)

libz.so.1()(64bit)

8 Prerequisites


• Configure PBS and PAS Server• Installing the Display Manager Router• Install Display Manager Agent• Unconfigure PBS and PAS Servers

Prerequisites 9


Operating System Groups and User RequirementsDisplay Manager requires the following user accounts to be defined on the hosts it is installed on.

1. An existing user who will become the PBS Works portal administrator. The portal admin-istrator can define policies and manage resources.

2. An existing user who will be the database administrator.

During installation, the credentials of these users will be required.

10 Prerequisites

3. Display Manager Deployment Options

Network Implementation of Display ManagerThe network connections for Display Manager components is shown below:

When a user double-clicks an application icon in Display Manager (DM), the remote application is started and the following sequence of events are initiated.

1. The DM Application sends the request to the DM Web Service.2. The DM Web Service interfaces with PAS to submit an interactive job.

11


3. The interactive job script updates DM Web Service with the Remote Display Server (RDS) information.

4. DM Web Service responds to DM Web Application with the RDS information. The DM Web Application transfers the information to Client Viewer.

5. Client Viewer connects to the Display Server directly. If the Display Server is not reachable, then it tries to connect to Display Server through configured Display Router.

Virtual Private Networking or secured channels for communication between clients and Display Manager Server can be used if encryption is required. Only the users currently logged in into DM that have a valid session ID are allowed to connect to the DM router.

The ports for the Display Manager portal (application server, port 8086 by default) and the Display Manager Router (port 9500 by default) should be open through the firewall or gateway for clients to connect. The port information for these two components is displayed in the installation sum-mary. Installation Summary shows this information for Display Manager application server and Installation Complete shows the screen for the Display Router installation summary.

Distributed Deployment

12 Display Manager Deployment Options


In this deployment, all the applications - Compute Manager, Display Manager, the Database, Access Management Service, Display Manager Router, PBS and PAS servers can be in one system (System A).

DM Components and MOM (Machine Oriented Miniserver) should be in systems B1, B2, B3, B4, and so on.

The distributed deployment options are:• CM and DM on same machine as PAS/PBS• CM and DM on separate machine from PAS/PBS• CM and DM on machine 1, PAS on machine 2, PBS on machine 3

The DM components are the Remote Display Server and the DM Router. These components use TurboVNC and VirtualGL technology.

To install and configure the DM components use the Display Manager Add-on Installer.

Single Host Deployment In this deployment option, all the following components are installed in a single system.

Enterprise Foundation• Access Management Services• Database

Display Manager Deployment Options 13


Applications• Compute Manager• Display Manager

Other Components• Display Manager Router• PBS and PAS Servers• PBS MOM• Display Manager Agent

14 Display Manager Deployment Options

4. Installing Display Manager

This guide covers the information relevant to Display Manager. More information regarding the other products available in the PBS Works Suite installer is available in the PBS Works Administra-tor’s Guide.

Display Manager is available as part of the PBS Works 13.0 Installer. In this installer, Compute Manager, Results Visualization Service, Display Manager, Display Manager Router, Display Man-ager Agent and PBS Customizations are available. Use this installer for a Single Host Deployment option.

For a single host deployment use the PBS Works 13.0 installer to install DM. When you install DM, Computer Manager is automatically installed.

For a distributed deployment use the PBS Works 13.0 installer to install DM and then use the DM Add-On installer to configure PBS and PAS servers, install Display Manager Router and Display Manager Agent.

Separate installers are available in the Altair download area for Windows and Linux operating sys-tems. The installer walks you through the installation process, requesting installation and configu-ration information along the way. Once the installation is complete, Display Manager is ready for use.

The Display Manager Add-on Installer is available to install the execution components of Dis-play Manager Router, Display Manager Agent and PBS Customizations. Use this installer to com-plete the installation for a distributed deployment option.

This guide provides a step by step description of: 1. Installing Display Manager using the PBS Works Installer.

a. Display Manager Installation on Linuxb. Display Manager Installation on Windowsc. Display Manager Console Installation (applies to both)

2. Display Manager Add-on installer to install execution components of Configure PBS and PAS Server, Installing the Display Manager Router, Install Display Manager Agent, and Unconfigure PBS and PAS Servers.

3. Uninstalling Display Manager

15


16 Installing Display Manager

5. Display Manager Installation on Linux

Display Manager is installed using the PBS Works Installer. The installation package can be obtained using your usual Altair support channels.

Starting the Installer

Start the installer by executing the following command: ./PBS_Works_13.0_Linux_x86_64.bin

[root@localhost PBS Works 13.0 Installer]# ./PBS_Works_13.0_Linux_x86_64.bin

Preparing to install...

Extracting the JRE from the installer archive...

Unpacking the JRE...

Extracting the installation resources from the installer archive...

Configuring the installer for this system's environment...

Launching installer...

The graphical launcher will work only if running the installer from within an X graphic environment or if proper redirection (e.g. "set DISPLAY=myhost:0.0") is set for the running shell.

17


Splash ScreenAfter extracting the files, the installation will proceed by displaying the splash screen.

18 Display Manager Installation on Linux


IntroductionThe Introduction screen provides information on navigating the installer using the Next and Pre-vious buttons and specifies the Prerequisites for Installation.



License AgreementTo continue with the installation, please scroll down to read the license agreement and accept it.



Installation TypeTo install Compute Manager and Display Manager using windows authentication on Windows, SSH on Linux, using local authorization with a new database, choose Express Install.

Custom Install enables you to specify all options available in the installer. In this guide, all the options specific to installing Display Manager are described in detail using the custom Install option.



Altair Applications and Service SelectionSelect the Display Manager option to install:

1. Display Manager Application2. Display Manager Router3. Compute Manager (Prerequisite for Display Manager)

If the installer detects PBS and PAS servers in the target system, it will configure them for Display Manager. If PBS MOM is detected, it will install the DM Agent components.

If PBS and PAS servers are installed on the target system, the installer will inform that they will be restarted during installation.



Database ConfigurationIn this screen, a New Database can be created or the application can reuse a database installed ear-lier using the same PBS Works installer. In the example below, the database will be created in the local host. The installer can create a non-admin user on the server where the database is installed, (with username pbsworksuser) who will become the owner (Super User) of the database.



You can also provide the credentials of an existing OS user who will become the database Super User.



If the application is pointed to an existing database from a previous installation using the PBS Works installer, provide the credentials of the database super user.



Access Management Service ConfigurationAccess Management Service (AMS) can be installed on the target system to implement Authoriza-tion and Authentication rules for applications.



An existing instance of AMS can be used by providing the Hostname or IP Address and the port at which the AMS instance is running.



Installation FolderChoose the installation folder on the target system. The default location is: /opt/altair/pbsworks/13.0



License Server ConfigurationProvide the license server location information. More than one location can be provided by sepa-rating them with a colon (:).



Access Management ServiceAMS (Access Management Service) is used to implement authentication and authorization rules for the users of Display Manager application. The following options are available for AMS.

Authentication Module for AMS The portal (PBS Works) and services can be configured to use the following authentication mech-anisms:

SSH (Secure Shell): All the users will be authenticated against a SSH server provided by the administrator during installation.



Access Management Service: All the users will be authenticated against a datastore and managed using the AMS console.



Authorization Module for AMSThe authorization module is used by AMS to query group memberships and user details. AMS supports two authorization modules: Active Directory and AMS.

Active Directory

If you choose to use Active Directory, provide the details of the LDAP compatible server.



Access Management Service

If you choose Access Management Service, no further inputs are required by the installer. Use the AMS console for authorizing users through the local datastore.



GPU Configuration for the ServerIf PBS is detected on the target system, the installer will ask you for the number of GPUs available in the cluster to configure the PBS Server.



GPU Configuration for the NodeIf the installer detects PBS MOM on the target system, it will prompt you to enter the number of GPUs available and use the information to configure PBS MOM.



Installation SummaryThis screen summarizes all your choices before beginning the installation.



Installation ProgressDuring installation, the billboards are displayed based on the installation options you selected.

On completion, the installer will provide the details of the Installation Directory, Host, Port and the link to login to the portal.

Bookmark the link and make it available to the users of the portal.




6. Display Manager Installation on Windows


Starting the InstallerLocate the installer executable in Windows Explorer, right click and choose the Run as adminis-trator option from the context menu as shown below.

Splash ScreenThe installer will extract the required files.

39


After extracting the files, the installation will proceed by displaying the splash screen.

40 Display Manager Installation on Windows


IntroductionThe Introduction screen provides information on navigating the installer using the Next and Pre-vious buttons and specifies the Prerequisites for Installation.



License AgreementTo continue with the installation, please scroll down to read the license agreement and accept it.



Installation TypeTo install Compute Manager and Display Manager using windows authentication on Windows, SSH on Linux, using local authorization with a new database, choose Express Install.

Custom Install enables you to specify all options available in the installer. In this guide, all the options specific to installing Display Manager are described in detail using the custom Install option.

Altair Applications and Service SelectionSelect the Display Manager option to install:

1. Display Manager Application2. Display Manager Router



3. Compute Manager (Prerequisite for Display Manager)

If the installer detects PBS and PAS servers in the target system, it will configure them for Display Manager. If PBS MOM is detected, it will install the DM Agent components.

If PBS and PAS servers are installed on the target system, the installer will inform that they will be restarted during installation.



Database ConfigurationIn this screen, a New Database can be created or an Existing Database installed earlier with the PBS Works installer can be reused. In the example below, the database will be created in the local-host. The installer can create a non-admin user, (with username pbsworksuser) who will become the owner (Super User) of the database.



You can also provide the credentials of an existing OS user who will become the database Super User.



If the application is pointed to an existing database from a previous installation using the PBS Works installer, provide the credentials of the database super user.



Access Management Service ConfigurationAccess Management Service (AMS) can be installed on the target system to implement Authoriza-tion and Authentication rules for applications.



An existing instance of AMS can be used by providing the Hostname or IP Address and the port at which the AMS instance is running.



Installation FolderChoose the installation folder on the target system. The default location is: C:\altair\pbsworks\13.0



License Server ConfigurationProvide the license server location information. More than one location can be provided by sepa-rating them with a semicolon (;).



Access Management ServiceAMS (Access Management Service) is used to implement authentication and authorization rules for the users of Display Manager application.


SSH (Secure Shell): All the users will be authenticated against a SSH server provided by the administrator during installation.



Windows: Windows credentials can be used to authenticate users.



Access Management Service: All the users will be authenticated against a datastore managed by AMS.



Authorization Module for AMSThe authorization module is used by AMS to query group memberships and user details. AMS supports two authorization modules: Active Directory and AMS.

Active Directory

If you choose to use Active Directory, provide the details of the LDAP compatible server.




If you choose Access Management Service, no further inputs are required by the installer. Users will be authorized through a Local Datastore.



PBS Works Service User ConfigurationTo run PBS Works service, provide the credentials of a user in the target system



Installation SummaryThis screen summarizes all your choices before beginning the installation.



Installation ProgressDuring installation, the billboards are displayed based on the installation options you selected.


Bookmark the link and make it available to the users of the portal.




7. Display Manager Console Installation


The installation steps in the console mode are identical to the steps in the GUI mode. In this chap-ter, screenshots of the console mode installation on Linux is displayed. Windows specific informa-tion is included wherever required.

Starting the Installer in Console ModeTo start the installer in console mode navigate to the location of the installer and type the name of the installer followed by -i console.

In the Linux terminal, enter the following command:./PBS_Works_13.0_Linux_x86_64.bin -i console

In Windows command prompt, enter the following command:PBS_Works_13.0_Windows_x86_64.exe -i console

Type next and previous to navigate the screens. To exit the installer, type quit. Type the number of your choice and press Enter to select the choice. To make multiple choices, enter the numbers of your choices separated by commas.

The Introduction screen is displayed. Press the Enter key to continue.[root@localhost PBS WORKS 13.0 Installer]# ./PBS_Works_13.0_Linux_x86_64.bin -i console



Unpacking the JRE...




===================================================================================

PBS Works Suite (created with InstallAnywhere)

-----------------------------------------------------------------------------------

61


Preparing CONSOLE Mode Installation...

===================================================================================

Introduction

------------

PBS Works Suite 13.0 installer will guide you through the installation.

It is strongly recommended that you quit all programs before continuing with

this installation.

Use the ''Enter" key to go to the next step and type "Back" to navigate to the

previous installation step. You may cancel this installation at any time by

using Ctrl-C.

Pre-requisites for Installation:

1. Minimum hard disk space of 4 GB

2. Minimum RAM of 4 GB

3. A non-admin User name and password to act as owner of PBSWorks Database

4. An User name and password of the user who would be acting as Portal

Administrator. This user should be existing on the authentication server.

5. An existing user in case you choose Enterprise data store to query user

details for authorization.

PRESS <ENTER> TO CONTINUE:

License Agreement ScreensThe License Agreement is displayed in a series of screens, please press Enter to scroll down and read it. To continue with the installation, press Y to accept it. PRESS <ENTER> TO CONTINUE:

counterparts, all of which together shall constitute one and the same instrument. Execu-tion. Copies of this Agreement executed via origin signatures, facsimile or email shall be deemed binding on the parties.

DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N) : Y

62 Display Manager Console Installation


Installation TypeChoose the Custom Installation option by typing 2 and pressing Enter.===============================================================================

Installation Type

-----------------

Please choose the type of installation that you would like to go ahead with. A

small description for the installation types is as below:

Express Install - Installs Compute Manager and Display Manager applications,

Results Visualization Service is not installed, uses windows authentication on

windows and ssh on Linux, uses local authorization, installs a new DB and

creates a default DB user.

Custom Install - Provides option to the users to configure the installation.

->1- Express Install

2- Custom Install

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:: 2

Altair Applications SelectionChoose the Applications option by typing 1 and pressing Enter.===============================================================================

Altair Applications and Service

-------------------------------

Please specify your installation options.

->1- Applications

2- Service: Results Visualization Service




Display Manager SelectionTo install Display Manager, type 2 and press Enter.===============================================================================

Applications

------------

Please select the applications you would like to install.

->1- Compute Manager

2- Display Manager(Compute Manager will be installed as a pre-requisite)

ENTER A COMMA-SEPARATED LIST OF NUMBERS REPRESENTING THE DESIRED CHOICES, OR

PRESS <ENTER> TO ACCEPT THE DEFAULT: 2

If the installer detects PBS and PAS servers in the target system, it will configure the servers for DM. If PBS MOM is also detected, it will install the DM Components. If the PBS and PAS servers are not detected, the Add On installer has to be run on PBS server, PAS server and the PBS MOMs for completing the DM installation.

Database Configuration ScreenIn this screen, a New Database can be created or the application can be pointed to the address of an Existing Database. Type 1 and press Enter to create a new database in the localhost. The installer can create a non-admin user, (with username pbsworksuser) who will become the owner (Super User) of the database.===============================================================================

Database Configuration

----------------------

The selected options need access to the PBS Works Database.

Please choose to install a new database or use an existing database.

->1- New Database

2- Existing Database


If you want to use an existing database, type 2, press Enter and provide the hostname/ip address, the port of the database and the credentials of the database super user.



Access Management Service ConfigurationAccess Management Service (AMS) can be installed on the target system to implement Authoriza-tion and Authentication rules for applications. Type 1 and press Enter to install a new instance of AMS in the target system.===============================================================================

Access Management Service Configuration

---------------------------------------

Please choose to install Access Management Service or use an existing instance

of the service.

->1- Install Access Management Service

2- Use an Existing Instance


Type 2 and press Enter to use an existing instance of AMS by providing the Hostname or IP Address and the port at which the AMS instance is running.

Installation FolderPress Enter to accept the default installation folder location.

In Linux, the default location is : /opt/altair/pbsworks/13.0

In Windows, the default location is: C:\altair\pbsworks\13.0===============================================================================

Installation Folder

-------------------

Please choose a destination folder for this installation.

Where would you like to install?

Default Install Folder: /opt/altair/pbsworks/13.0

ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT :

If you wish to install to a another location, type the absolute path of the location and press Enter.



License Server ConfigurationType the license server location information. More than one location can be provided by separat-ing them with a colon (:) on Linux and a semicolon (;) on Windows.===============================================================================

License Server Configuration

----------------------------

"Applications" requires access to the Altair License Server to function. Please

provide the license server location.

You can provide multiple license server locations seperated by a colon.

License Servers (e.g: [email protected]:6200@lmxserver): (Default: ): [email protected]:6200@licsvr

Access Management Service ConfigurationAMS (Access Management Service) is used to implement authentication and authorization rules for the users of Display Manager application. The following options are available for AMS.


SSH (Secure Shell): All the users will be authenticated against a SSH server provided by the administrator during installation. Type 1 and press Enter to use SSH authentication.===============================================================================

Access Management Service: Authentication Module

------------------------------------------------

Access Management Service provides Authentication and Authorization services

for all Altair Products. It also helps create policies that define access

permissions to all the product features and services.

The next set of screens will guide you through the installation of Access

Management Service.

Please specify the module to be used for authentication.

->1- SSH

2- Access Management Service




On choosing SSH, provide the Hostname or IP address of the SSH server, or press Enter to use the localhost.===============================================================================

Access Manager : SSH Server Hostname/IP Address

-----------------------------------------------

Access Manager is a service to create policies that define access permissions

to product features and servers. It also provide Authentication and

Authorization services for all Altair products.

The next set of screens will guide you through the installation of Access

Manager. On Linux, SSH based authentication is supported. Please provide SSH

Server.

Hostname or IP Address (Default: localhost): sshsvr

Access Management Service: All the users will be authenticated against a datastore managed by AMS. Type 2 and press Enter to use AMS.

Authorization Module for AMSThe authorization module is used by AMS to query group memberships and user details. AMS supports two authorization modules: Active Directory and AMS===============================================================================

Access Manager: Authorization Module

------------------------------------

You can manage your users and groups using either of the following:

1. Windows Active Directory Server or any LDAP compatible server.

2. Altair's Access Management Service

1- Active Directory (LDAP)

->2- Access Manager Service


Type 2 and press Enter to use AMS based authorization.



Type 1 and press Enter to use Active Directory, provide the details of the LDAP compatible server in the next screens.

GPU Configuration for the ServerIf PBS is detected on the target system, the installer will ask you for the number of GPUs available in the cluster to configure the PBS Server===============================================================================

Display Manager: GPU Configuration for Server

---------------------------------------------

Provide the maximum number of GPUs available for the server

Available GPUs on the Cluster: (Default: 1): 2

GPU Configuration for the NodeIf PBS MOM is detected on the target system, the installer will ask you for the number of GPUs available in the node.===============================================================================

Display Manager: GPU Configuration for Node

---------------------------------------------

Available GPUs on the Node: (Default: 1): 2

PBS Works Super User Configuration===============================================================================

PBS Works Suite: Super User Configuration

-----------------------------------------

Please provide the username for the PBS Works Suite Super User. This user will

be the PBS Works portal Administrator and must exist on the authentication

server.

You have chosen AMS based authentication.

Portal Administrator User Name: (Default: ): pbsworksuser



Pre-Installation Summary

After entering all the required information, a summary of all the chosen options is displayed. You can navigate to earlier screens and change your choices by typing previous or back. No changes are made to the server till the choices are confirmed in this screen.===============================================================================


------------------------

Please Review the Following Before Continuing:

Install Folder:

/opt/altair/pbsworks/13.0

Product Name:

PBS Works Suite 13.0

Installation Host:

localhost.localdomain

Applications/Service selected for installation:

Applications

Application Server Port:

8086

Database Host:

localhost

Database Port:

6767

DM Router Port:

9500

For the Windows installation, the credentials of a user has to be provided for the PBS Works Service. This information is not required for Linux.



Database Super User:

pbsworksuser

Portal Admin User:

pbsworksuser

Disk Space Information (for Installation Target):

Required: 818.78 MegaBytes

Available: 10,166.8 MegaBytes

PRESS <ENTER> TO CONTINUE:

Press the Enter key to start the installation process with your selected options.

Installation ProgressDuring installation, the following information is displayed.===============================================================================

Installing ...

------------------------

[===============|===============|===============|===============|===============]

[...............|...............|...............|...............|...............]

===============================================================================

PBS Works Suite Installation Complete

--------------------------------------

Congratulations! PBS Works Suite has been successfully installed to:

Install Directory : /opt.altair/pbsworks/13.0

Host : localhost.localdomain

Port : 8086

To login, proceed to

http://localhost.localdomain.8086/pbsworks

Press "Done to quite the installer.

PRESS <ENTER> TO EXIT THE INSTALLER:



=================================================================================

Restart Required!

------------------

System needs to be restarted for changes to take effect.

Would you like to restart now?

->1. Yes

2. No

ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: 1


In Linux, restarting the system is advised if DM Agent is installed. It is only required to restart X server to enable the DM Agent component access to the GPU.

Bookmark the link and make it available to the users of the portal




8. Installing DM Execution Components for Linux

This section provides the step by step procedure to install the Display Manager execution compo-nents (i.e Display Manager Agent and Display Manager Router) and configure PAS and PBS.

The DM Add-on installer should be used to complete the DM installation, if the PBS Works Suite installer does not detect PBS, PAS servers and PBS MOM on the target system. This is required for a distributed deployment option.

Display Manager Add-on InstallerThe DM Add-on installer is available through your usual Altair support channels.

To start the installer, type the name of the installer executable in the Linux console as shown below.[root@localhost PBS Works 13.0 Installer]# ./PBS_Works_13.0_DMA_Linux_x86_64.bin



Unpacking JRE...




The graphical launcher will work only if running the installer from within an X graphic environment or if proper redirection (e.g. "set DISPLAY=myhost:0.0") is set for the running shell.

73


The installer provides a notification that the PBS and PAS Servers might require to be restarted. It is advisable to run the installer when critical jobs are not running.

Choose No to exit and run the installer at a more suitable time. On choosing Yes, the Introduc-tion and License screens are displayed. On agreeing to the License, the available installation options are displayed.

Install OptionsThe Display Manager Add-On installer provides the following four install options.


The rest of this chapter explains the details for each of these options available in the installer.

74 Installing DM Execution Components for Linux


Configure PBS and PAS ServerThis option performs the following configurations:

• Creates and configures interactive work queue (iworkq)• Configures ngpus• Installs interactive application definition



GPU Configuration

Provide the available GPUs on the cluster to configure the PBS interactive queue.




Review the summary of choices made before proceeding with the installation.

On clicking the Install button, the installation progress is displayed along with the splash screens and the installation complete message is shown.



Installing the Display Manager RouterThis option installs the DM router.



Choose Install Folder



AMS Configuration for Display Manager Router

Provide the Hostname or IP Address of the Access Management Service Server for authenticating connections to the DM Router.



Installation Progress

The installation progress is shown along with the DM billboard.



Installation Complete

On successful completion the message below is displayed.



Install Display Manager AgentThis option installs the DM Agent and configures GPUs for the node.



Installation Folder



License Server Configuration

Enter the location of the license server. You can provide multiple server locations separated by colon (:)



GPU Configuration for Node

Enter the number of GPUs available on the node.



Pre-installation Summary

Review the summary of your choices before proceeding to install.

The DM billboards and file copy progress is displayed during installation. On completing installa-tion, a message is displayed. It is recommended to restart the system on completing the installa-tion.



Unconfigure PBS and PAS ServersThis option performs the following unconfigurations:

• Deletes the interactive queue• Unconfigures GPUs as a custom resource• Uninstalls interactive application definition

On choosing the Unconfigure PBS and PAS Server option, the following message is displayed.

While unconfiguration is in progress, splash screen is displayed and the process is completed.


9. Installing DM Execution Components for Windows

This section provides the step by step procedure to install the Display Manager execution compo-nents (i.e Display Manager Agent and Display Manager Router) and configure PAS and PBS.

The DM Add-on installer should be used to complete the Display Manager installation, if the PBS Works Suite installer does not detect PBS, PAS servers and PBS MOM on the target system. This is required for a distributed deployment option.

Display Manager Add-on InstallerThe DM Add-on installer is available through your usual Altair support channels.

Starting the InstallerLocate the installer executable in Windows Explorer, right click and choose the Run as adminis-trator option from the context menu as shown below.

89


The installer provides a notification that the PBS and PAS Servers might require to be restarted. It is advisable to run the installer when critical jobs are not running.

Choose No to exit and run the installer at a more suitable time. On choosing Yes, the Introduc-tion and License screens are displayed. On agreeing to the License, the available installation options are displayed.

Install OptionsThe Display Manager Add-On installer provides the following four install options.


The rest of this chapter explains the details for each of these options available in the installer.

90 Installing DM Execution Components for Windows


Configure PBS and PAS ServerThis option performs the following configurations:

• Creates and configures interactive work queue (iworkq)• Installs interactive application definition




Review the summary of choices made before proceeding with the installation.

On clicking the Install button, the installation progress is displayed along with the splash screens and the installation complete message is shown.



Installing the Display Manager RouterThis option installs the Display Manager router.



Choose Install Folder



AMS Configuration for Display Manager Router

Provide the Hostname or IP Address of the Access Management Service Server for authenticating connections to the DM Router.



Installation Progress

The installation progress is shown along with the Display Manager billboard.



Installation Complete

On successful completion the message below is displayed.



Install Display Manager AgentThis option installs the Display Manager Agent.



Installation Folder



Pre-installation Summary

Review the summary of your choices before proceeding to install.

The Display Manager billboards and file copy progress is displayed during installation. On com-pleting installation, a message is displayed. It is recommended to restart the system on completing the installation.



Unconfigure PBS and PAS ServersThis option performs the following unconfigurations:

• Deletes the interactive queue• Uninstalls interactive application definition

On choosing the Unconfigure PBS and PAS Server option, the following message is displayed.

While unconfiguration is in progress, splash screen is displayed and the process is completed.




10. Uninstalling Display Manager

In Linux, navigate to the _PBS Works Suite_installation directory in the location where the DM application is installed. Run the following command:

./Change\ PBS\ Works\ Suite\ Installation

[root@localhost _PBS Works Suite_installation]# ./Change\ PBS\ Works\ Suite\ Installation

In Windows, navigate to the _PBS Works Suite_ installation folder in the location where DM is installed. Right click on the Change PBS Works Suite Installation executable and select the Run as administrator option from the context menu as shown below.

The steps from this point onwards to uninstall Display Manager is identical on Windows and Linux platform. In this section, the example screenshots are based on the Linux version.

103


The Installer launches in Maintenance Mode. Select Uninstall Product and click on the Next but-ton.

In the next screen, click on the Uninstall button.

104 Uninstalling Display Manager


Confirm your choice in the alert box.

The uninstall process will begin and the progress will be shown

Uninstalling Display Manager 105


A confirmation message will be displayed. Click on Done to exit the installer.

106 Uninstalling Display Manager

11. Configurations

On successful installation, the PBS Works portal will be ready for use. Here is a list of configura-tions the installer takes care of:

• PBS Applications and Services• Verifying Display Manager Configurations• Database• Access Management Service• PBS Server Configurations• GPU Configuration as PBS resource• PAS Server Configurations• GPU Resource Configuration• Display Manager Agent Configuration• Display Manager Router Configuration• Display Manager Settings Configuration• Client Configuration for Application Launch Framework

PBS Applications and ServicesFollowing are the configurations made by the installer based on the inputs provided during instal-lation.

File What gets updatedLinux: /etc/pbsworks.confWindows: %SystemRoot%\System32\Driv-ers\etc\pbsworks.conf

Installation Home

<Install Folder>/thirdparty/apache/tomcat/conf/server.xml

Control Ports

<Install Folder>/binaries/framework/data/factoryset-tings.xml

LMX License Location

107


Verifying Display Manager ConfigurationsYou can use the information to configure DM without reinstalling it. In the PAS server, you can configure the PBS server location and port in the dmrest.properties file. You can configure the DM Router host and port in the dmviewer.properties file located in the PAS server.

DatabasePostgres will be silently installed by PBSWorks Suite installer without any input from user.

The following databases will be created based on the choice of applications.

<Install Folder>/config/AA/AA_Client.properties Access Management Service HostAccess Management Service Port

<Install Folder>/config/platform.xml Default LocaleLinux: /etc/init.d/pbsworks

Windows: <Install Folder>\scripts\PBSWorksSer-vice.bat

Application Service Startup Scripts

Linux: /etc/init.d/pbsworks

Windows: <Install Folder>\scripts\pbsworksdb.bat

Database Service Scripts

Postgres version 9.4.4Install Location <Install Folder>/thirdparty/postgresPostgres Home <Install Folder>/thirdparty/postgresPort The default port is 6767. If this port is not available, the installer tries to

find a free port in next 100 ports. If it is unable to find a free port, the installer will request you to provide a suitable port number. Port details will be shown in the summary page before installation

File What gets updated

108 Configurations


If you choose to create a new user during installation, the installer will create a user with username as pbsworksuser.

Configurations:

Following files will be updated by the installer:

**The port by default will be 6767. The installer will search for next 100 ports if 6767 is not avail-able. If there is not free port even after searching for 100 ports, you will be asked to provide a port that's available.


Configurations Files

The installer modifies the following files based on the inputs given during the installation.

Product Database Super User/PasswordCompute Manager pbsworksdb Provided by the user during installation.Display Manager pbsworksdb Provided by the user during installation.

File What gets updated<Install Folder>\ \services\dm\config\spring-con-fig.xml

Database HostDatabase Port**Database User NameEncrypted Database Password

AMS Version RC 8.8Install Location <Install Folder>/binaries/framework/webappsAAService Home <Install Folder>/config/AAServiceHome

File What gets updated<Install Folder>/config/AA_ServiceHome/config/AA_jaas.config

Authentication Details based on the mode selected

Configurations 109


Here is a brief description of what these files are meant for:• <Install Folder>/config/AA_ServiceHome/config

- AA_jaas.config: This file contains the authentication module and its related settings- log4j.properties: This file contains the settings for Access Management Service log

settings- AA_Service.properties: This file contains the settings for time out and the mode of

authorization.- Datastore/Datastore.properties: This contains the settings of LDAP or Domain con-

troller when you choose Enterprise mode authorization• <Install Folder>/config/AA_ServiceHome/applications

- cm/cmActions.xml: The actions that Compute Manager administrators can perform through Access Management Service is defined in this file.

• <Install Folder>/config/AA_ServiceHome/resources

- AA_Groups.xml: This file holds the information about groups. CM administrators are defined in this file under the group "CMAdmin"

- AA_Users.xml: This file holds the details of the users when a local datastore is chosen as Authorization mode.

PBS Server ConfigurationsBelow are the configurations made to PBS by the installer (applicable for Linux cluster).

Verifying the Interactive Queue Configuration

The installer creates a queue called iworkq and configures it with ngpus provided during installa-tion. You can verify the configuration with the following command:zeethon:/var/spool/pas/config-private # qmgr -c "p q iworkq"

#

# Create queues and set their attributes.

#

#

<Install Folder>/config/AA_ServiceHome/config/AA_Service.properties

Authorization Mode

<Install Folder>/config/AA_ServiceHome/config/ Datastore/Datastore.properties

Datastore settings

File What gets updated

110 Configurations


# Create and define queue iworkq

#

create queue iworkq

set queue iworkq queue_type = Execution

set queue iworkq Priority = 150

set queue iworkq max_queued_res.ngpus = [o:PBS_ALL=32*]

set queue iworkq resources_max.ngpus = 1

set queue iworkq resources_min.ngpus = 1

set queue iworkq enabled = True

set queue iworkq started = True

*32 is the GPU count provided during the installation. This is the count of GPUs avail-able on the cluster

GPU Configuration as PBS resourceresourcedef

An entry will be made to resourcedef under PBS_HOME/server_priv/.

You can verify the resourcedef configuration as below:zeethon:/var/spool/PBS/server_priv # grep -A3 "DM STATIC" resourcedef

# *********** BEGINNING OF DM STATIC RESOURCES SECTION.DO NOT EDIT BY HAND ******

ngpus type=long flag=nh

# *********** END OF DM STATIC RESOURCES SECTION.DO NOT EDIT BY HAND ************

sched_config

An entry will be made in PBS_HOME/sched_priv/sched_config as below:

zeethon:/var/spool/PBS/sched_priv # grep ngpu sched_config

resources: "ncpus, mem, arch, host, vnode, netwins, aoe, ngpus"

PAS Server ConfigurationsInteractive Application Definition:

An application definition will be installed in PAS_HOME/repository/applications folder and ijob.conf will be updated to point to the Display Manager server.

GPU Resource ConfigurationGPU will be configured as a resource in PAS Server by making the following entries to aif_re-sources_definitions.txt and resource_type.xml files in PAS_HOME/config-private/ directory.

Configurations 111


zeethon:/var/spool/pas/config-private # grep -A2 "DM STATIC" aif_resources_defini-tions.txt

# *********** BEGINNING OF DM STATIC RESOURCES SECTION.DO NOT EDIT BY HAND ******

ngpus type=long flag=nh

# *********** END OF DM STATIC RESOURCES SECTION.DO NOT EDIT BY HAND **

zeethon:/var/spool/pas/config-private # grep -A2 -B1 ngpus resource-type.xml

<JOB_RESOURCE>

<WMS_NAME>ngpus</WMS_NAME>

<WMS_TYPE>chunk</WMS_TYPE>

</JOB_RESOURCE>

Display Manager Agent ConfigurationThe installer configures GPUs.

GPU Node Configuration

You can verify the GPU configuration as below:zeethon:~ # pbsnodes -a

Mom = zeethon.pbsworks.com

Port = 15002

ntype = PBS

state = free

pcpus = 1

resources_available.arch = linux

resources_available.host = zeethon

resources_available.mem = 3903096kb

resources_available.ncpus = 1

resources_available.ngpus = 2*

resources_available.vnode = zeethon

resources_assigned.accelerator_memory = 0kb

resources_assigned.mem = 0kb

resources_assigned.naccelerators = 0

resources_assigned.ncpus = 0

resources_assigned.netwins = 0

resources_assigned.ngpus = 0

resources_assigned.vmem = 0kb

resv_enable = True

sharing = default_shared

112 Configurations


*This is the value provided during the installation process.

Display Manager Router ConfigurationThe only file that will be updated is the /etc/dmrouter.conf with the installation path.

Changing the DM Router PortsTo change the DM Router ports, follow the steps below:

1. Edit the router port entry in the routingservice.properties file located in the <Install Folder>/dmrouter/config/ directory.

2. Edit the AMS or CM URL entry in the AA_Client.properties file located in the <Install Folder>/dmrouter/AA/config/ directory.

3. Edit the router port entry in the dmrest.properties file located in the <Install Folder>/services/dm/config/ directory.

Configurations 113


Display Manager Settings ConfigurationThe settings for Display Manager can be modified in adminSettings.xml located at <Install Folder>\services\dm\data\.

The following settings can be modified in the adminSettings.xml:

Settings Name Definitionmaxstarttimeout The maximum wait time for the display session to start. The possible

values are 30 seconds, 1 minute and 5 minute. By default it is set to 1 minute. A Session Timer dialog box is displayed showing the wait time for the session to start. If the session is not started within the specified wait time, then the session is aborted. You can also abort the session while the timer is running.

eststartuptimeout This is a soft timeout which triggers the startup dialog box to appear informing that the session is taking long time to start. By default, the value is set to 10 seconds.

displaygeo DM synchronizes the browser window size with the session viewer size.resizedesktop The resize desktop option allows you to resize the window viewer that

is imbedded in the browser. By default, this option is enabled.viewerwindow Enable this option to launch the display session in a new independent

applet window, instead of the browser window.copybackfiles Specify a location for the staged out job. After running the session, the

files used in the session are copied to this location.

If a DM session fails to start, this option can be used to download the files and examine the reasons for failure.

sessionaction Your sessions are retained even after you log out. This enables you to resume the work you were doing when you log in again. However, this value sets a time limit to specify how long the sessions should be retained after you log out.

By default, the sessions will be terminated after 5 years.view This is used to persist the ID of session in view; basically to connect

back the user to the last viewed session.

114 Configurations


To change Display Manager settings in the application, follow the steps:1. Click the settings icon, and choose the Settings option from the drop down menu as

shown below:

A Settings dialog box will be displayed.

The Settings dialog box can be used to set session save options, update license server infor-mation, set Display Manager preferences and Application Launch Framework client loca-tion.

The factorySettings.xml available in the location <Install Folder>\services\dm\data\ has the default factory settings.

Once a category has been selected and updates have been made, click Apply to apply the changes. To cancel any changes made, and close the Settings dialog box, click Cancel. To apply any changes made, and close the Settings dialog box, click OK. To restore any defaults, click Restore Defaults.

Configurations 115


2. Click Display Manager and update the preferences.

Client Configuration for Application Launch FrameworkDisplay Manager has the capability to launch session like RDP and RGS using the Application Launch Framework. The ALF client has to be configured, so that it can open the remote sessions.

Setup the ALF Desktop Component1. The ALF desktop component is available at http://<host>:<port>/pbsworks/ui/frame-

work/alf/alf.zip (eg., http://dm-02:8086/pbsworks/ui/framework/alf/alf.zip)2. Download the ALF zip and extract to the default install location on windows. The default

install location is C:\altair\pbsworks\13.0The folder structure and the files in the alf folder after extracting the ALF zip file in the default location would be:- config- java.zip- libs- logs- launchmgr.bat- README.txt

116 Configurations


3. Extract the java.zip in the C:\altair\pbsworks\13.0\alf path.

Modify the ALF Client LocationIf you extract the ALF client in a different location, then you have to modify the ALF client loca-tion in the application as follows:

1. Click the Settings icon, and choose the Settings option from the drop down menu as shown below:

A Settings dialog box will be displayed.

The ALF desktop component install location (C:\altair\pbsworks\13.0\alf) will match the ALF Client Location preference in Application Launch Framework. If you modify the default location, then the ALF desktop component install location must be mod-ified.

Configurations 117


2. Click Application Launch Framework and update the ALF Client Location.

118 Configurations

12. Starting, Stopping and Restarting

PBS Works Portal

Determine the PBS Works Portal Status---------------------------------------------------------------------------------------

zeethon:/etc/init.d # /etc/init.d/pbsworks status

PBS Works 13.0 (pid 18908) is running

You can access the portal using link http://zeethon.pbsworks.com:8086/pbsworks

---------------------------------------------------------------------------------------

Starting the PBS Works PortalOn Windows:

1. Click Start, choose Run and type services.msc to open the Services Management Con-sole.

2. Select the PBSWorks Service in the list of services. Click the Start link to start the service.

119


On Linux:zeethon:/etc/init.d # /etc/init.d/pbsworks start

Stopping the PBS Works PortalOn Windows:

From the services console select the PBSWorks Service and click the Stop link.

On Linux:zeethon:/etc/init.d # /etc/init.d/pbsworks stop

Restarting the PBS Works PortalOn Windows:

From the services console select the PBSWorks Service and click the Restart link.

120 Starting, Stopping and Restarting


On Linux:

From the terminal window with root privilege, type the following command to restart the service:

zeethon: /etc/init.d # /etc/init.d/pbsworks restart

DM Router

Determine the DM Router Statuszeethon:/etc/init.d # /etc/init.d/dmrouter status

dmrouter is running with pid: 18860

Starting DM Routerzeethon:/etc/init.d # /etc/init.d/dmrouter start

Starting dmrouter

dmrouter started, pid: 29252

Stopping DM Routerzeethon:/etc/init.d # /etc/init.d/dmrouter stop

Stopping dmrouter

dmrouter stopped, was pid: 18860

Starting, Stopping and Restarting 121


122 Starting, Stopping and Restarting

13. Post Installation Administration

This section describes the post installation administration procedures.

Network Ports The Display Manager Application server and the Display Manager Router server should be able to communicate to the web browser through the firewall or gateway. Ensure the ports for the Display Manager application server (port 8086 by default) and the Display Manager Router (port 9500 by default) are able to communicate through the firewall or gateway. The port information for these two components is displayed in the installation summaries. Installation Summary shows this information for Display Manager application server and Install Complete shows the screen for the Display Router installation summary.

Managing ApplicationsThe applications available in Display Manager are deployed as PAS Application definitions. Appli-cation definitions are a predefined set of instructions to describe application parameters, store responses and prepare responses for job execution.

In this section we describe the application definition details specific to Display Manager. More comprehensive information regarding Application Definitions is available in the PBS Application Services Administrator's Guide and the Diving Into Application Definitions Guide.

Location of Application definitionsWhen PAS server starts up, it scans the application definitions stored in a central repository to list the applications as resources available for PBS Professional.

Windows: C:\Program Files\altair\pas\13.0\PAS\home\repository\applications

Linux: /var/spool/pas/repository/applications

123


Main components of Display Manager Application DefinitionsA Display Manager Application Definition consists of the following components:

• An Application input file (e.g.app-inp-GlxSpheres.xml). The valid arguments for the application is specified in this file.

• The Application converter file (app-conv-GlxSpheres.xml). The values received through the input file are converted and communicated to the PAS and PBS through this file. The Job submission environment is configured in this file.

• The Application action file (e.g. app-actions-GlxSpheres.xml) The custom actions defined in this file enable Display Manager to communicate to PAS to perform actions on the interactive job while it is running.

• The Site Configuration file (site-config.xml). The information stored in this file can be referenced by any application definition. Applications, Application versions, Job projects and policies are some common settings that can be defined in the site configuration file.

Application specific for Linux and WindowsWriting a DM specific application definition is a bit more complex than writing simple applica-tions definitions. We recommend a simple procedure of copying and modifying the GLXSpheres application definition which is available as part of the Display Manager installation. A description of the important points to keep in mind while creating DM specific applications is covered in the next section.

Adding a New Application for LinuxThe steps to add a new application to Display Manager:

1. In the application definitions directory, copy the GlxSpheres application definition directory and rename it to the name of the application. In this example, let's assume we are adding HyperView to Display Manager. Run the following command. cp -rp GlxSpheres HyperView

2. Rename the GlxSpheres application definition files to the name of the application.mv app-actions-GlxSpheres.xml app-actions-HyperView.xml

mv app-conv-GlxSpheres.xml app-conv-HyperView.xml

mv app-inp-GlxSpheres.xml app-inp-HyperView.xml

3. Edit the app-inp-AppName file (e.g. app-inp-HyperView.xml).

124 Post Installation Administration


i. Change the <ApplicationId>GlxSpheres</ApplicationId> entry to the application name.e.g. <ApplicationId>HyperView</ApplicationId>

ii. Change the <ApplicationName>GlxSpheres</ApplicationName> entry to the application name.e.g. <ApplicationName>HyperView</ApplicationName>

iii. Locate the VERSION category. In the xpath1 value, update the Application@id to the AppNamee.g.<ArgumentChoice>

<ArgumentStringEnumerated>

<Name>VERSION</NAME>

<Description> Version of the interactive application you selected to start</Description>

<DisplayName>Version</DisplayName>

<xi:include href="site-config.xml" pointer="xpath1 (//Application[@id='HyperView']/ApplicationVersions//Option)" />


</ArgumentChoice>

4. Open the app-actions-AppName file (e.g. app-actions-HyperView.xml) and change the <ApplicationId>GlxSpheres</ApplicationId> entry to the application name as described in step 3.i.

5. Open the app-conv-AppName file (e.g. app-conv-HyperView.xml) and make the changes described in step 3.i and step 3.ii. Set the required environment for the application.

You can set the ALTAIR_LICENSE_PATH, NCPUS, ngpus, MEMORY etc according to the requirements for the application.

(e.g. <jsdl-hpcp:Environment name="ALTAIR_LICENSE_PATH">6200@licsrv</jsdl-hpcp:Environment>

6. Restart the PAS services for these changes to take effect. Alternatively, you can remove the time stamp from the directory and wait for the services to pick up the updated files.

7. In the site-config.xml file located in the application definitions directory, add an entry for the application in the <Applications> section.

e.g.<Application id="HyperView">

<ApplicationVersions>

<ApplicationVersion>



<Option>12.0</Option>

<Executable>/altair/hw/12.0/altair/scripts/hv</Executable>

</ApplicationVersion>

</ApplicationVersions>

</Application>

Example to define multiple executable versions of the application definition:<Application id="HyperView">










</ApplicationVersions></Application>

8. Once PAS picks up the new application definitions, the application will be available in Dis-play Manager.

Adding a New Application for WindowsThe steps to add a new application to Display Manager:

1. In the application definitions directory, copy the Notepad application definition directory and rename it to the name of the application. In this example, let's assume we are adding HyperView to Display Manager. Run the following command. copy Notepad HyperView

2. Rename the Notepad application definition files to the name of the application.rename app-actions-Notepad.xml to app-actions-HyperView.xml

rename app-conv-Notepad.xml to app-conv-HyperView.xml

rename app-inp-Notepad.xml to app-inp-HyperView.xml

3. Edit the app-inp-AppName file (e.g. app-inp-HyperView.xml).

You can also define multiple executable versions for the application defi-nition.



i. Change the <ApplicationId>Notepad</ApplicationId> entry to the application name.e.g. <ApplicationId>HyperView</ApplicationId>

ii. Change the <ApplicationName>Notepad</ApplicationName> entry to the application name.e.g. <ApplicationName>HyperView</ApplicationName>

iii. Locate the VERSION category. In the xpath1 value, update the Application@id to the AppNamee.g.<ArgumentChoice>





<xi:include href="site-config.xml" pointer="xpath1 (//Application[@id='HyperView']/ApplicationVersions//Option)" />


</ArgumentChoice>

4. Open the app-actions-AppName file (e.g. app-actions-HyperView.xml) and change the <ApplicationId>Notepad</ApplicationId> entry to the application name as described in step 3.i.

5. Open the app-conv-AppName file (e.g. app-conv-HyperView.xml) and make the changes described in step 3.i and step 3.ii. Set the required environment for the application.

You can set the ALTAIR_LICENSE_PATH, NCPUS, MEMORY etc according to the requirements for the application.

(e.g. <jsdl-hpcp:Environment name="ALTAIR_LICENSE_PATH">6200@licsrv</jsdl-hpcp:Environment>

6. Restart the PAS services for these changes to take effect. Alternatively, you can remove the time stamp from the directory and wait for the services to pick up the updated files.

7. In the site-config.xml file located in the application definitions directory, add an entry for the application in the <Applications> section.

e.g.<Application id="HyperView">








</ApplicationVersions>

</Application>

Example to define multiple executable versions of the application definition:<Application id="HyperView">










</ApplicationVersions></Application>

8. Once PAS picks up the new application definitions, the application will be available in Dis-play Manager.

Display Manager Specific Information for Application DefinitionsAny app that should be shown in Display Manager should contain the following <Interactive> tag in its app-inp-AppName application definition.

<ApplicationId>Application</ApplicationId>

<ApplicationName>Name of the Application</ApplicationName>

<Interactive>true</Interactive>

You can also define multiple executable versions for the application defi-nition.



The <Interactive> tag should be set to true. PAS will scan an application definition for the <Interactive> tag and identify it as a DM application. Only these applications are filtered and dis-played in the DM UI.

Display Manager should contain the following <ArgumentChoice> declared in its app-inp-AppName application definition.

<ArgumentChoice>

<ArgumentString>

<Name>JOB_NAME</Name>

<Description>The name of the Job.</Description>

<DisplayName>Job Name</DisplayName>

<InputRequired>true</InputRequired>

</ArgumentString>

</ArgumentChoice>

Multiple versions of an application is derived from the PAS reserved keyword defined in the VER-SION section. This refers to the site-config.xml used by PAS.<ArgumentChoice>





<xi:include href="site-config.xml" xpointer="xpath1(//Applica-tion[@id='HyperView']/ApplicationVersions//Options)" />


</ArgumentChoice>

Application Specific Configurations for Display Geometry, Number of CPUs, Memory and GPUs can be defined in the app-input-AppName.xml

If this section is not included, Display Manager will not be aware of the interactive application.

The FeatureEnabled option for GPU, controls the request for GPUs. For 2D applications set it to false and a request for GPUs will not be made for the application. FeatureEnabled option has to be set to true for 3D applications.



The following new application specific configuration for Display Manager can be defined in the app-input-AppName.xml file:

• Arguments - this can be used if multiple number of variables has to be specified for the submitted job. The variables should be separated by ‘\n’.

<ArgumentChoice>

<ArgumentString>

<Name>DM_APP_ARGS</Name>

<Description>'\n' separated args</Description>

<DisplayName>Arguments</DisplayName>

<InputRequired>false</InputRequired>

</ArgumentString>

</ArgumentChoice>

• Environment - this can be used to pass other environment related variables. The variables should be separated by ‘\n’.

<ArgumentChoice>

<ArgumentString>

<Name>DM_APP_ENVS</Name>

<Description>'\n' separated envs</Description>

<DisplayName>Environments</DisplayName>


</ArgumentString>

</ArgumentChoice>

• WorkDirectory - use this argument to create a working directory for the jobs that are sub-mitted.

<ArgumentChoice>

<ArgumentString>

<Name>DM_APP_WDIR</Name>

<Description>Working dir</Description>

<DisplayName>Working Dir</DisplayName>


</ArgumentString>

</ArgumentChoice>

• Copy back files - use this argument to create a backup of the files that are submitted for the jobs in the stageout directory.

<ArgumentChoice>

The arguments mentioned above is disabled by default. Enable them by setting the InputRequired field to true.



<ArgumentBooleanWithDescription>

<Name>COPY_BACK_FILES</Name>

<Description>Should job file(s) be staged out</Description>

<DisplayName>Copy back files</DisplayName>

<InputRequired>true</InputRequired>

<FeatureEnabled>false</FeatureEnabled>

<RefreshOnUpdate>true</RefreshOnUpdate>

</ArgumentBooleanWithDescription>

</ArgumentChoice>

In the app-conv-AppName application definition file, the following section determines which jobs are displayed in Display Manager.<jsdl-hpcp:Environment name="DM_JOB">True</jsdl-hpcp:Environment>

If this is set to False, apart from the interactive Display Manager jobs, all the other jobs belonging to the user will be displayed. Ensure that this is set to True.

Application specific Environment values like ALTAIR_LICENSE_PATH, VERSION, NCPUS, ngpus, MEMORY etc. can be defined here.

Managing Graphical Node LimitsThe installer configures all the node and cluster limits for the GPUs. Follow the below procedure in situations where these limits might change (e.g. a node going down or being removed, adding new graphical nodes post install, etc.)

Modify the Cluster GPU LimitAn attribute that controls this limit is defined for the PBS queue (iworkq) that exclusively handles interactive job requests for a PBS server.

The Copy_Back_Files arguments is disabled by default. Enable this field by setting the FeatureEnabled option to true. This options will be dis-played while submitting a job in Compute Manager. You can also change this option in the Display Manager Settings.

In the app-actions-AppName application definition file, apart from chang-ing the <ApplicationID>, no other changes are recommended.



For example,

set queue iworkq max_queued_res.ngpus = [o:PBS_ALL=5]

The numerical value "5" is the available GPU limit for the cluster. This is the cumulative number of all the GPUs available in the cluster managed by the PBS server. Change this value to accommo-date any changes in the limit due to addition or removal of Graphical nodes or Graphic devices in nodes.

Modify the Node GPU LimitAn attribute that controls this limit is defined for every Graphical node configured in the cluster.

For example,

set node v03 resources_available.ngpus = 2

The numerical value "2" is the available GPU limit for the node v03, this is the cumulative number of all the graphical devices available in a particular node. This value will need to be changed to accommodate any changes to the limit due to addition or removal of Graphical devices to the node.

Refer to the Troubleshooting section for fixing any known issues during setup.

Configuring the Browser for Application ShortcutsSeveral applications like HyperMesh and HyperView use the mouse scroll wheel for critical opera-tions like rotating a model or zooming in and out. For a consistent and smooth application experi-ence, these shortcuts must not be intercepted by the web browser.

In Mozilla Firefox, open the configurations section by typing about:config in the address bar. Set the value of the parameter mousewheel.with_controlkey.action to 0.

In Internet Explorer in Windows,

1. Go to Start > Run and type gpedit.msc

2. Navigate to User Configuration > Windows Components > Internet Explorer

3. On the right hand side page double click to open Turn off page-zooming functionality. Click on enabled.

4. Restart Internet Explorer.



Keyboard ConfigurationKeyboard entries for the certain characters like @ # [ ] { } do not work in OS X using JRE 7. These keys will work when using JRE 6. Currently, if you are using OS X, please use JRE 6 to work on Display Manager.

Reset these option after using Display Manager to return to your normal browsing experience.




14. Troubleshooting

Quick Troubleshooting ChecklistOn completing the installation the services relevant to Display Manager should be up and run-ning. This quick troubleshooting section assumes services like vncrouter, dmagent, application services, PAS and PBS with PBS-P are running and configured

Checklist for the Web Client:

1. Verify that Java is enabled and working in the web browser. To solve Java related issues, refer to the Java troubleshooting document at: http://www.java.com/en/download/help/trouble-shoot_java.xml

Checklist for the Execution node (or Graphics node):

2. Make sure that all the DM components are able to communicate with each other. Hostname resolution should be consistent with DM needs and information entered during installation.

3. As a prerequisite, the execution node should be set up to run VNC server successfully for the user. Run the following command:

/opt/TurboVNC/bin/vncserver -noauth

Browse to: http://$host:$vncwebport (e.g. http://v01:5801),

Replace v01 with the VNC server host name and 5801 (5800 + display #) with the http port of the VNC server.

If you don't see the virtual desktop, please forward the ~/.vnc folder to the support team for further investigation.

4. As another prerequisite, X server must be configured and running.

Verify if X server is running for display:0 (usually with process name Xorg or X). In case it is not running, reconfigure X server with /usr/bin/nvidia-xconfig --use-display-device=NONE --enable-all-gpus --keyboard=us

This will overwrite existing configurations and configure the X server with all available GPUs.

5. Access to X server must be granted for the user. (The DM Installer will do this)

135




Run the following command in a terminal window in the remote desktop session created in Step 1

/opt/VirtualGL/bin/glxinfo -display :0 -c

the command should output a list of visuals and complete with no errors.

6. Does the Graphics driver support VirtualGL?

To verify, use the command:

glxinfo -display :0

Look for visuals with a class of "tc", a buffer size of 24 or 32, a caveat of "None", and drwtyp "P" in the right-most column. direct rendering: Yes

OpenGL version string: "should state vendor driver version here"

e.g., 3.3.0 NVIDIA 260.19.36 and not a software renderer like mesa. Latest vendor drivers are recommended

7. Is VirtualGL configured and functional. (Pre-requisite)

Run the following command in a terminal window in the remote desktop session created in Step 1

/opt/VirtualGL/bin/vglrun -d :0.0 -sp /opt/VirtualGL/bin/glxspheres64".

If GLXSpheres starts, then VirtualGL is properly configured. If not, a detailed investigation is required by the support team.

8. Check for errors for the DM appdef in the PAS logs.

9. Verify that the pbs_mom logs do not report any error related to the DM jobs associated with the DM sessions. i.e. errors related to file transfers.

10. Verify that PBS Pro jobs submitted as DM ends up running on the expected host(s) without errors. For example, when debugging problems related to the execution host dmhost1, verify that a job like:

qsub -l select=1:ncpus=1:mem=8gb:ngpus=1:host=dmhost1 -Wsandbox=PRIVATE -I

is correctly running and does not generate any errors in any PBS Pro logs, most importantly in the related pbs_mom logs. Tune the resource requests to match the actual ones DM uses when generating this jobs. PBS Pro job history will help identify the correct values: qstat -fx <jid of failed dm job>.

136 Troubleshooting


Resource Availability Error Graphical resources are not available at this time

This error message is shown when there are no available graphical resources to schedule the sub-mitted job.

Level: Production & Admin.

Occurrence: Frequent.

What to look for:

Verify whether all the configured graphical resources in the cluster are occupied. Each interactive job will occupy a GPU, switch to Compute Manger monitoring page or run qstat command on PBS the head node to know the list of running interactive jobs at a given time.

1. If the number of running interactive jobs is equal to the total number of available GPU's configured in the cluster, then the user has to wait until one of them gets finished for the error message to disappear.

2. Another cause might be due to PAS/PBS errors which are not in the scope of this docu-ment, however refer to relevant guides to provide a fix for the identified problem.

Resource Acquisition ErrorExecution host information not available on time

This error message is shown when the DM web service did not get an update from the PBS job script of an interactive job about the execution node information within a time period after being successfully scheduled.

Level: Admin.


What to look for:1. The job script of the interactive job (/var/spool/pas/applications/interactiveApp/run-

time/ iJobStart.py) uses certain environments that are prefixed with PAS, but with the older versions of PAS installation same variables are prefixed with AIF. The references need to be changed to match the current PAS installation.

2. Another cause might be due to PAS/PBS errors which are not in the scope of this docu-ment, however refer to relevant guides to provide a fix for the identified problem.

Troubleshooting 137


Only the display session is shown but not the application that was startedAfter starting an application, you might notice that the display session was shown but not the application. Generally it happens when the user doesn't have access to the 3D X server.

Level: Admin.


What to look for:1. Check whether the user has access to the 3D X server.

a. Open a terminal and run "xdpyinfo -display :0" or "/opt/VirtualGL/bin/glxinfo -display :0 -c"

"unable to open display :0" means the user doesn't have permission to access the 3D X Server, verify whether VGL server is configured correctly (http://www.virtualgl.org/vgldoc/2_2_1/#hd005001) or the user doesn't belong to the vglusers group.

2. Check whether the X is configured correctly.Verify whether X Server is configured to export True Color (24 bit or 32 bit) visuals. (eg., use "/usr/bin/nvidia-xconfig --use-display-device=NONE --enable-all-gpus --key-board=us" to configure X server for nVidia devices)

3. Check whether the application is configured correctly.Refer to the Managing Applications section of this guide.

Graphic Card Compatibility Issues with Display ManagerUse the drivers provided by the manufacturer of the graphic card. If the manufacturer of your 3D adapter provides proprietary drivers for Linux, then it is recommended that you install these. Many of the drivers that ship with Linux do not provide full 3D acceleration or Pbuffer (pixel buf-fer) support.

Level: Admin.


What to look for:

Inspect the output of /opt/VirtualGL/bin/glxinfo -display :0 -c for the below.

138 Troubleshooting

http://www.virtualgl.org/vgldoc/2_2_1/#hd005001

http://www.virtualgl.org/vgldoc/2_2_1/#hd005001


1. Look at the OpenGL renderer string and make sure it doesn't contain any variant of mesa or software

2. Direct Rendering is Yes3. Look for visuals with a class of tc, a buffer size of 24 or 32, a caveat of None, and have a P in

the right-most column.

Here is an example output for the command:

[root@dmsystem-linux ~]# /opt/VirtualGL/bin/glxinfo -display :0

name of display: :0

display: :0 screen: 0

direct rendering: Yes

server glx vendor string: NVIDIA Corporation

server glx version string: 1.4

server glx extensions:

GLX_ARB_context_flush_control, GLX_ARB_create_context,

GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness,

GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age,

GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,

GLX_EXT_framebuffer_sRGB, GLX_EXT_stereo_tree, GLX_EXT_swap_control,

GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap,

GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer,

GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer,

GLX_NV_multisample_coverage, GLX_NV_swap_group, GLX_NV_video_capture,

GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control,

GLX_SGI_video_sync

client glx vendor string: NVIDIA Corporation

client glx version string: 1.4

client glx extensions:



GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample,

Troubleshooting 139


GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,

GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float,

GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree,

GLX_EXT_swap_control, GLX_EXT_swap_control_tear,

GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,

GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap,

GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_present_video,

GLX_NV_swap_group, GLX_NV_video_capture, GLX_NV_video_out,

GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control,

GLX_SGI_video_sync

GLX version: 1.4

GLX extensions:



GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample,

GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,

GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB,

GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear,

GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,

GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap,

GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_swap_group,

GLX_NV_video_capture, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,

GLX_SGI_swap_control, GLX_SGI_video_sync

140 Troubleshooting

Documents

Display Manager 13 - Altair Manager 13.0... · 2019-04-18 · Display Manager 13.0 Administrator’s Guide Remotely Visualize Your Datasets fo r Rapid Collaboration and Innovation