PBS Works Admin Guide€¦ · PBS Works 13.2 Administrator’s Guide ii ... OptiStruct®...

PBS Works is a division of

PBS Works .

Administrator’s Guide

PBS Works 13.2 Administrator’s Guide

Intellectual Property Rights Notice: Copyrights, Trademarks, and Third Party Licenses

Updated: April 18, 2018.

Altair® PBS Works™ 13.2Enabling On-Demand Computing™Copyright© 1994-2017 Altair Engineering Inc. All Rights Reserved.

Altair PBS Works™: Compute Manager™ ©2012-2017; Display Manager™ ©2013-2017; PBS Pro™ ©1994-2017; PBSProfessional® ©1994-2017; PBS Application Services™ ©2008-2017; PBS Analytics™ ©2008-2016;PBS Desktop™ ©2008-2012; and e-Compute™ ©2000-2010.

HyperWorks® Products: HyperMesh® ©1990-2017; HyperCrash® ©2001-2017; OptiStruct® ©1996-2017; RADIOSS® ©1986-2017; HyperView® ©1999-2017; HyperView Player® ©2001-2017; HyperMath® ©2007-2017; HyperStudy® ©1999-2017; HyperGraph® ©1995-2017; MotionView® ©1993-2017; MotionSolve® ©2002-2017; HyperForm® ©1998-2017; HyperXtrude® ©1999- 2017; Process Manager™ ©2003-2016; Templex™ ©1990-2017; TextView™ ©1996-2017; MediaView™ ©1999-2017; TableView™ ©2013-2017; BatchMesher™ ©2003-2017; HyperWeld® ©2009-2017; HyperMold® ©2009-2017; Manufacturing Solutions™ ©2005-2017; solidThinking Inspire® 2017 ©2009-2017; solidThinking Evolve®2017 ©1993-2017; Durability Director™ ©2009-2017; Suspension Director™ ©2009-2017; AcuSolve® ©1997-2017; AcuConsole® ©2006-2017; SimLab® ©2004-2017; Virtual Wind Tunnel™ ©2012-2017; FEKO® (©1999-2014 Altair Development S.A. (Pty) Ltd.; ©2014-2017 Altair Engineering, Inc.); ConnectMe™ ©2014-2017; Click2Extrude™ Polymer 2017 ©1996-2017; Click2Extrude™ Metal 2017 ©1996-2017; Click2Form™ 2017 ©1998-2017.

Additional Altair Products: Multiscale Designer™ ©2011-2017; Flux v.12.2 ©1983-2017; InCa3D v.3.1©1996-2016; CDE v.2 ©2012-2016; Got-It v.3 ©2002-2016; WinProp v.14.5 ©2000-2017

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.

ii


Altair Packaged Solution Offerings (PSOs): Automated Reporting Director™ ©2008-2017; GeoMechanics Director ©2011-2017; Impact Simulation Director™ ©2010-2017; Model Mesher Director™ ©2010-2017; Model Verification Director™ ©2013-2017; NVH Director™ ©2010-2017; Squeak and Rattle Director™ ©2012-2017; Virtual Gauge Director™ ©2012-2017; Weight Analytics™ ©2013-2017; Weld Certification Director™ ©2014-2017; Multi-Disciplinary Optimization™ ©2012-2017.

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

Software products of solidThinking, Inc., a wholly owned subsidiary of Altair Engineering:solidThinking Inspire® 2017 ©2009-2017; solidThinking Evolve®2017 ©1993-2017; solidThinking Compose® 2017 ©2007-2017, solidThinking Activate® 2017 ©1989-2017, solidThinking Embed® 2017 ©1989-2017, solidThinking Embed® SE 2017 ©1989-2017; Click2Extrude™ Metal 2017 ©1996-2017; Click2Extrude™ Polymer 2017 ©1996-2017; Click2Cast® 4.0 ©2011-2017; Click2Form™ 2017 ©1998-2017; Envision® 4.0 ©2013-2017.

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. Copyright notice does not imply publication.

Third party software licenses

AcuConsole contains material licensed from Intelligent Light (www.ilight.com) andused by permission.

iii

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

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

http://www.ilight.com


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.

Technical Support

This document is proprietary information of Altair Engineering, Inc.

Location Telephone e-mail

China +86 (0)21 6117 1666 [email protected] +33 (0)1 4133 0992 [email protected] +49 (0)7031 6208 22 [email protected] +91 80 66 29 4500 [email protected] +39 800 905595 [email protected] +81 3 5396 2881 [email protected] +82 70 4050 9200 [email protected] America +1 248 614 2425 [email protected] +46 (0) 46 460 2828 [email protected] +44 (0)1926 468 600 [email protected]

iv

Contents

About this Guide xi

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiRelated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiDocument Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiAcronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Chapter 1: About PBS Works 1

Applications and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Compute Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Display Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Results Visualization Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Access Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Supported Product Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3System Requirements for CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Supported Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Hardware Requirements for CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

System Requirements for DM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Execution Host Requirements for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Execution Host Requirements for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Sample Configurations for Execution Hosts for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Sample Configurations for Execution Hosts for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Web Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Java Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

System Requirement for RVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Supported Server Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Supported Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Hardware Requirements for RVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9PBS Works Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Authentication and Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

v

Profile Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Options for Populating AMS with Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Software Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: Deployment Option 13

Deployment Options for PBS Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Option 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Option 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Option 3 - Recommended Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Network Implementation of Display Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Network Connections of Java Applet Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Network Connections of HTML5 Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Distributed Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Single Host Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Deployment Options for RVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Option 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22




Chapter 3: Prerequisites 27

Prerequisites for Installing PBS Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Prerequisites for Using CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Google Chrome Frame plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Prerequisites for Installing Display Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Prerequisites for Installing Display Manager Agent for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

vi Contents

Prerequisites for Installing Display Manager Agent for Windows . . . . . . . . . . . . . . . . . . . . . . . . . 30

Prerequisites for Installing RVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Prerequisites for using RVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Recommended Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Prerequisites for Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31SPN Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Configuring Client Browser for SSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 4: Installing PBS Works 33

Express Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Installing RVS on the Same Machine as CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35AMS Migration from Previous Versions of CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Configuration of PBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Manual Installation Configuration of PBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Manual Uninstallation Configuration of PBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installation Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Installing PBS Works Using the Express Installation Option . . . . . . . . . . . . . . . . . . . . . . . . . . 47Installing PBS Works Using the Custom Installation Option . . . . . . . . . . . . . . . . . . . . . . . . . . 49Installing RVS Using the Custom Installation Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 5: Starting, Stopping and Restarting 57

PBS Works Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Starting the PBS Works Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Stopping the PBS Works Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Restarting the PBS Works Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Determining the Status of the PBS Works Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

RVS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Starting RVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Determine the Status of RVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Stopping RVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Restarting RVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 6: Uninstall PBS Works 61

Starting the Uninstaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Contents vii

Chapter 7: Post-Installation Steps 65

Configuring the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Adding the License Server in Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Adding the License Server in the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Changing the AMS Administrator’s Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Migrating the AMS Datastore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Populating AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Logging into AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Adding Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Managing User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 8: PBS Works Advanced Configuration 79

Changing the Authentication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Changing Authentication to SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Changing the SSH Server or Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Changing Authentication to Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Changing Authentication to use the AMS Datastore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Connecting to a LDAP/AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Changing Authentication to NIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Changing the NIS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Changing Authentication to PAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring Administrative Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Improving File Operations Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Improving JVM Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Changing the Postgres Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Configuring the Postgres database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Changing the Database Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Changing the PBS Works Logging Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Changing the Logging Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Configuring Log File Size and Number of Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Configuring Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Configuring Language/Localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Configuring SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Creating a Tomcat Certificate Keystore File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Deploying a Customer Defined Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Configuring a Secure Open Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

viii Contents

Configuring a Secure Open Port with Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Enabling Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Disabling Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103SPN Verfication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103PBS Works Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 9: Troubleshooting 107

Single Sign-On (SSO) Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Glossary 111

Contents ix

x Contents

About this Guide

This document describes how to install, configure and administer PBS Works.

This chapter contains the following topics:• Audience• Related Documentation• Document Conventions• Acronyms

AudienceThis document is intended for administrators who perform the following tasks:

• Install and administer PBS Works products• Monitor the operation of PBS Works products• Troubleshoot PBS Works products

Related DocumentationThe other PBS Works related documents are as follows:

• PBS Works Release Notes• Compute Manager Administrator’s Guide• Display Manager Administrator’s Guide• Results Visualization Service Administrator’s Guide

Documentation can be found at the following URL:

http://www.pbsworks.com/SupportGT.aspx?d=PBS-Professional,-Documentation

xi

http://www.pbsworks.com/SupportGT.aspx?d=PBS-Professional,-Documentation


Document ConventionsThe following typographical conventions are used in this document:

PBS Works Home Directory

CONFIG_HOME is where the PBS Works configuration and log files are stored. The location of this directory is platform dependent. For more information see Software Organization on page 11.

For example:

config.properties is stored in CONFIG_HOME\services\cm\config

PBS Works Execution Directory

SERVER_HOME is where the PBS Works binaries are stored. The location of this directory is platform dependent. For more information see Software Organization on page 11.

For example:

PBSWorksService.bat is stored in SERVER_HOME\scripts\

RVS Installation Location

RVS SERVER_HOME is the location in a file system where RVS is installed. It is used when referencing a file that may need to be accessed or viewed by a systems administrator. For more information see Software Organization on page 11.

For example:

RVservice.bat is stored in SERVER_HOME\scripts\

Installation Location

<INSTALL_DIR> is the location in a file system where an Altair product is installed. It is used when referencing a file that may need to be accessed or viewed by a systems administrator. For example:

<INSTALL_DIR>/portal/config.xml

File Pathname

Names of a file or a directory are displayed as follows:

/home/user1/submission_dir/PBSJobApp/174.hwesuse113.oe

xii


Keyboard Inputs

Keyboard inputs, for example commands that are entered are displayed as follows:

./etc/init.d/pbsworks-pbsa start

Code Example and File Contents

Examples of programming code or the contents of a file are displayed as follows:

Parameters, Environment Variables, XML tags

Environment variables, XML tags, parameters, and references to a snippet of a file are displayed as follows:

Set the value of the MaxBackupIndex parameter to the maximum number of log files to keep.

UI Controls

User Interface controls such as command buttons, tab names, menu options, application fields, or items in a list are displayed as follows:

Click the Settings button.

Document References

References to an external document are displayed as follows:

For more information see the Compute Manager Administrator’s Guide.

Messages

Log file messages or messages returned from a command are displayed as follows:Please make sure PBSA engine and Monetdb Server are not running.

Notes

Information or notes that supplement or emphasize important points are displayed as follows:

if userInputs['ACCOUNT']:

job.attr_accounting_label =userInputs['ACCOUNT']

The default TOC type for a result file is set in the plugin_def.xml file

xiii


Tips

Tips that makes your work easier are displayed as follows:

Cautions

Cautions draw special attention to any action that could cause damage to the product or cause the loss of data. For example:

AcronymsThe following acronyms are used in this guide.

If you get an error during registration of the HyperView Player, right click on the shortcut and choose the Run as Administrator option from the context menu.

Do not turn the monitor off by unplugging it from the computer or wall socket. Severe damage to the monitor may result. Turn the monitor off before unplugging it.

Table 1. Acronyms

Term DefinitionAD Active DirectoryALM Altair License Management SystemAMD Advanced Micro DevicesAMS Access Management ServiceCAE Computer Aided EngineeringCentOS Community Enterprise Operating SystemCM Compute ManagerDER Distinguished Encoding RulesDM Display ManagerESR Extended Support ReleaseFEA Finite Element AnalysisGPU Graphics Processing UnitGUI Graphical User InterfaceHPC High Performance ComputingHVTRANS HyperviewTranslator

xiv


HWU HyperWorks UnitJRE Java Runtime EnvironmentJVM Java Virtual MachineLDAP Lightweight Directory Access ProtocolMBD Multi Body DynamicsMOM Machine Oriented MiniserverNIS Network Information SystemPAM Pluggable Authentication ModulesPAS PBS Application ServicePBS Portable Batch SystemPBSA PBS AnalyticsPEM Privacy Enhanced MailRAM Random Access MemoryRDP Remote Desktop ProtocolRDS Remote Display ServerRHEL Red Hat Enterprise LinuxRVS Results Visualization ServiceSLES SuSE Linux Enterprise ServerSPN Service Principal NamesSSH Secure Socket ShellSSL Secure Sockets LayerSSO Single Sign-OnUI User InterfaceXML eXtensible Markup Language

Table 1. Acronyms

Term Definition

xv


xvi

1. About PBS Works

Companies who have invested in high-performance computing (HPC) resources -- like clusters, supercomputers and cloud environments -- need these resources operating reliably around the clock. And just as importantly, the systems need to be easy to use, manage, and scale while still being cost-effective.

Altair’s PBS Works™ addresses these challenges with the most comprehensive suite of integrated HPC workload management products available from a single vendor. PBS Works simplifies and streamlines the management of HPC resources with powerful policy-based job scheduling, user-friendly web portals for job submission and remote visualization.

This chapter contains the following topics:• Applications and Services• Supported Product Configurations• System Requirements for CM• System Requirements for DM• System Requirement for RVS• Licensing• PBS Works Database• Authentication and Authorization• Software Organization

Applications and ServicesThe following applications and services can be installed as part of PBS Works:

Compute ManagerCompute Manager™ (CM) is a job submission and monitoring portal which enables users to run, monitor and manage workloads on distributed resources remotely. Compute Manager uses the High Performance Computing (HPC) workload management capability of Altair's PBS Applica-tion Services (PAS) and PBS Professional for efficient resource utilization, access to the cloud for job submission, and subsequent accounting.

1


CM provides a web-based user interface and with minimal configuration. Compute Manager automates the job submission process, allowing users to spend more time creating better models and simulations. End user productivity improves since there are no complicated commands to learn or complex scripts to create and maintain. PBS Application Services allows you to tailor Compute Manager to fit your applications and user preferences, making job submission simple and error free.

Display ManagerDisplay Manager (DM) 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. Authorized users can all view and control a single session without downloading any files. This vir-tual-team productivity feature can save the costs associated with expensive face-to-face meetings and eliminate the need for multiple users in different sites to download Big Data files.

Display Manager enables users to run graphics-intensive applications on their cluster while visual-izing those applications on their desktop. DM requires three components to be installed:

• web application - must be installed on the same machine as CM• router - must be installed on the same machine as CM• agent - must be installed on all PBS Professional MOMs

Results Visualization ServiceResults Visualization Service (RVS) provides features to access, process and visualize CAE results remotely, through a web browser, without installing any post-processing desktop applications. RVS is available as part of the PBS Works suite and after installation it is available through the Compute Manager web applications. CAE analysts can monitor simulations in real-time by tracking and visualizing relevant parameters from solver log files. Plots and animations can be created remotely without downloading huge raw results files from compute clusters or remote networks locations. A variety of Finite Element Analysis (FEA) and Multi Body Dynamics (MBD) solvers are supported.

For more information about Results Visualization Service see the Results Visualization Service Administrator’s Guide.

Access Management ServiceAccess Management Service (AMS) provides a centralized configuration system for authentication and authorization. With AMS administrators can manage users and groups, as well as access con-trol policies.

2 About PBS Works


Supported Product ConfigurationsThe currently supported PBS Works Suite product configurations are:

System Requirements for CM

Supported PlatformsCompute Manager is supported on the following platforms:

Windows 64bit• Windows Server 2008 R2• Windows Server 2012 • Windows Server 2012 R2

Linux 64bit • Red Hat Enterprise Linux 5, 6, and 7• Cent OS 5, 6 and 7• Suse Linux Enterprise Server 11 and 12

Supported BrowsersWindows

• Firefox 45.3 ESR (Only Extended Support Release is supported. Please refer to https://www.mozilla.org/en-US/firefox/organizations/)

• Google Chrome 45.x and 46.x• Internet Explorer 11

Linux • Firefox 45.3 ESR (Only Extended Support Release is supported. Please refer to https://

www.mozilla.org/en-US/firefox/organizations/)

PBS Works PAS PBS Professional13.1 13.1.x 13.x

13.2 13.2 13.1.314.2.1

About PBS Works 3

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





• Google Chrome 45.x and 46.x

OSX • Safari 8.x and 9.x

Hardware Requirements for CM Please review the following hardware requirements for Compute Manager.

System Requirements for DM

Execution Host Requirements for Linux

Table 1. Hardware requirements for CM and DM

Hardware Minimum Requirement RecommendedCPU 2 CPU cores with a minimum

speed of 2.5 GHz4 CPU cores with a minimum speed of 2.5 GHz

Memory (Physical) 2 GB 8 GBDisk Space 2 GB 4 GB

Operating System Any Linux distribution in the Red Hat Enterprise or SUSE Enterprise fam-ilies which contains GLIBC 2.3.2 or later

Graphics • 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.

4 About PBS Works


Execution Host Requirements for Windows

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.

Operating System Windows Server 2008 R2, 2012 and 2012 R2Graphics 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.

About PBS Works 5

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

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


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

Graphics Card Model Processor OS RAMSystem 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

System 3 NVIDIA Quadro FX 3800

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

Cent OS 5.5 48GB

System 4 NVIDIA Quadro FX 3800

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

Cent OS 5.5 48GB

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

6 About PBS Works


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

Web Server Requirements

Web Client Requirements

Graphics Card Model Processor OS RAMSystem 1 NVIDIA Quadro

FX 1400Intel(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

Operating System • Windows Server 2008 R2, 2012 and 2012 R2• 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) 45.3, 32-bit• Google Chrome 45.x and 46.x• Microsoft Internet Explorer 11On Linux:• Mozilla Firefox ESR 45.3, 32-bitNote: Java Extensions are required on the browsers.

About PBS Works 7


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.

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

System Requirement for RVS

Supported Server Platforms• Architecture: Only the 64-bit (x86_64) platforms are supported

Supported Operating Systems• Windows Server 2012 R2• Red Hat Enterprise Linux version 6.X• SUSE Linux Enterprise Server version 11.0 and later• CentOS version 6.X and later

Supported Browsers• Internet Explorer version 11 and later• Mozilla Firefox ESR (Extended Support Release) version 38.0 and later• Google Chrome: version 43.0 and later

NPAPI plugins (HyperView Player Plugin for RVS) are not supported from Chrome version 44.0 and Mozilla Firefox ESR 45.

8 About PBS Works

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

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





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





Hardware Requirements for RVS Please review the following hardware requirements for Results Visualization Service.

LicensingFor users to log into any of the PBS Works products, PBS Works must have access to an activated and running Altair License Management System (ALM) that allows a PBS Works product to draw license units. During the installation of PBS Works, you will be prompted to supply information about the license server (port and hostname/IP address). You may supply the information at this time, or PBS Works can be configured with this information post-installation.

The following HyperWorks Units (HWUs) are drawn for Computer Manager:• 2 HWUs are checked out at CM/DM server startup and stay locked all the time.• 1 additional HWU per concurrently logged in user is required.

The following HyperWorks Units (HWUs) are drawn for Results Visualization Service. These units are checked out only during the server-side operation for extracting the information from job result files. There is no license draw while displaying this information in the browser.

• 10 HWUs for a RVS plot• 6 HWUs for a RVS animation

PBS Works DatabasePostgres will be installed by the PBS Works installer. The installer creates a database super user, “pbsworksuser”, if one is not supplied during installation.

The PBS Works database is installed and configured to use port 6767. If this port is not available during installation, then the PBS Works installer will increment the port number and try again. This will continue until a free port is found, or until 100 consecutive ports are refused at which point the installer will ask for a port.

Table 2. Hardware requirements for RVS

Hardware Minimum Requirement RecommendedCPU Dual Core Processor @ 2 GHz Quad Core Processor @ 2.5 GHzMemory (Physical) 4 GB 16 GB

About PBS Works 9


Authentication and Authorization

AuthenticationAuthentication is the process of verifying the identity of an entity who attempts to access a PBS Works application. During installation, PBS Works products can be configured to use below Authentication modules:

• Windows based• SSH based• Active Directory• AMS data store

The AMS datastore is an internal repository automatically installed with PBS Works. It is used for storing users, groups, and access policies. If authentication is performed against the AMS data-store, then the datastore must be populated with users and/or groups before users can log into the CM web application.

AuthorizationAuthorization is the process of specifying the access permissions for that identity. Access policies are defined through AMS. Computer Manager and Display Manager supports specific authoriza-tion policies. By default, users who login to CM have authorization to access:

• all PAS servers• all applications installed on the PAS servers

AMS can be used to change this default authorization. Use AMS to control things, such as:• who can register a PAS server• which applications are available for job submission• who can browse local or remote files• which modules are available for the users

Profile SharingJob submission profiles are customized shortcuts for submitting jobs with CM. If multiple jobs are submitted to the same application with the same arguments, it makes sense to create a profile that has these arguments pre-populated. Job submission profiles can be shared among users and groups, however to share job submission profiles, users and groups must be added to AMS.

10 About PBS Works


Options for Populating AMS with Users and GroupsThere are two options available for populating AMS with users and groups:

• During installation of PBS Works products, there is an option to connect AMS to a Win-dows Active Directory (AD), or a Lightweight Directory Access Protocol (LDAP) compat-ible server. AMS will automatically be populated with those users and groups stored in the LDAP/AD. However, adding and deleting users via the AMS console is restricted when an LDAP/AD is being used. AMS can only be used to define access policies.

• Populate AMS with users and groups using the AMS console.

Software OrganizationAfter a successful installation of PBS Works, two main directory structures are created. The loca-tion of these directories is platform dependent.

PBS Works home directory (CONFIG_HOME)

This is where the PBS Works configuration and log files are stored.

The default location for CONFIG_HOME is:

on Windows: C:\altair\pbsworks\13.2\home

on Linux: /var/spool/pbsworks/13.2/home

PBS Works execution directory (SERVER_HOME)

This is where the PBS Works binaries are stored.

The default location for SERVER_HOME is:

on Windows: C:\altair\pbsworks\13.2\exec

on Linux: /opt/altair/pbsworks/13.2/exec

RVS execution directory (RVS SERVER_HOME)

This is where the RVS binaries, configuration, and log files are stored.

The default location for RVS SERVER_HOME is:

on Windows: C:\altair\rvs\13.2\exec

on Linux: /opt/altair/rvs/13.2/exec

About PBS Works 11


12 About PBS Works

2. Deployment Option

Depending on which installation option is chosen, Express Installation on page 34 or Custom Installation on page 35, you can choose to install some or all PBS Works applications or services.

When you install CM or DM, an instance of AMS will also be installed, as well as a database instance.

If DM is being installed, the PBS Works installer always installs the DM web application and router. If the installer detects a PBS Professional MOM (execution host) on the machine where DM is being installed, then the DM agent will also be installed.

If a MOM is not detected, then the DM agent will have to be installed separately on the MOM(s). The installation of the DM agent will require the use of a separate installer and instructions for it’s installation on the MOM(s) can be found in the Display Manager Administrator’s Guide.

If you are installing DM onto a machine where PBS Professional and PBS Application Services are already installed, then the installer will perform some configuration of both in support of DM. Otherwise, if DM is being installed onto a machine that does not host PBS Professional and PBS Application Services, then a separate DM installer must be used to configure the PBS Professional and PAS Servers. Instructions for these activities can be found in the Display Manager Administra-tor’s Guide.

This chapter contains the following topics:• Deployment Options for PBS Works• Network Implementation of Display Manager• Deployment Options for RVS

13


Deployment Options for PBS Works

Option 1This option installs all applications and services onto a single machine that hosts all PBS Works applications and services, as well as the PBS Professional Server and MOM, PBS Application Ser-vices, and the DM agent.

Advantages• Costs are reduced since a single hardware is sufficient• Maintenance cost is reduced since a single hardware is used.

Disadvantages• Performance can be slow as all the services are running on a single machine.• Adequate computing hardware resources are required.• Not suitable for heavy usage load. • High dependency on the single server's performance

14 Deployment Option


Option 2This option deploys all applications and services, except the DM agent component, on a single machine that hosts the PBS Professional Server. The execution host(s) are installed on separate machines from the PBS Professional Server, therefore the DM agent will have to be installed sepa-rately on the MOMs. The installation of the DM agent will require the use of a separate installer and instructions for it’s installation on the MOMs can be found in the Display Manager Adminis-trator’s Guide.

Advantages

Similar to Option 1 although execution resources are off loaded to separate machine(s).

Disadvantages• Similar to Option 1.• Installation of the DM agent will have to be done as a separate step.

Deployment Option 15


Option 3 - Recommended ConfigurationThis option deploys all applications, except the DM agent component, on a single machine with the PBS Professional and PAS Servers hosted on a separate machine. Since DM is being installed on a machine that is not hosting the PBS Professional and PAS servers, then a separate DM installer must be used to configure the PBS Professional and PAS Servers, as well as installing the DM agents on the MOMs. Instructions for these activities can be found in the Display Manager Administrator’s Guide.

Advantages• Improved performance as the services are running on different machines.• Distributed environment reduces computing hardware resources per machine.

Disadvantages• Installation of the DM agent will have to be done as a separate step.• Configuration of PBS Professional and PAS will have to done as a separate step.• Increased investment and maintenance costs.



Network Implementation of Display ManagerThere are two options for viewing a remote session:

• Legacy Java Applet Viewer• HTML5 Viewer

The network connections for viewing remote session is provided in the following sections:• Network Connections of Java Applet Viewer• Network Connections of HTML5 Viewer

Network Connections of Java Applet ViewerThe network connections for Display Manager components of Java Applet Viewer 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.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.



Network Connections of HTML5 ViewerThe network connections for Display Manager components of HTML5 Viewer 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.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.

Virtual Private Networking or secured channels for communication between clients and Display Manager Server can be used if encryption is required.



The port for the Display Manager portal (application server, port 8086 by default) should be open through the firewall or gateway for clients to connect. Installation Summary shows the port infor-mation for Display Manager application server.

Distributed Deployment

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, see “Display Manager Add-on Installer” in Display Manager Administrator’s Guide.

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

Enterprise Foundation• Access Management Services• Database

Applications• Compute Manager• Display Manager

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



Deployment Options for RVS

Option 1This option deploys all applications and services on a single machine.

Advantages• In this deployment option, there is no file copy from the PAS staging directory to the

machine hosting RVS, therefore the performance is better. • Costs are reduced since a single hardware is sufficient• Maintenance cost is reduced since a single hardware is used.

Disadvantages• Performance can be slow as all the services are running on a single machine.• Adequate computing hardware resources are required.• Not suitable for heavy usage load. • High dependency on the single server's performance



Option 2 This option deploys RVS on the same machine as PBS Professional and PBS Application Services, while Compute Manager is hosted on a separate machine.

Advantages• This deployment option provides better performance since there is no file copy required

from the PAS staging directory to the machine hosting RVS.

Disadvantages• High availability of computing resources on the PBS head node is required. • High dependency since RVS performance affects PBS server.



Option 3This option deploys RVS on the same machine as HyperWorks. PBS Professional and PBS Applica-tion Services, and Compute Manager are hosted on a separate machine.

Advantages• This option provides better performance as the services are running on different machines.• There is low dependency between RVS and other applications.

Disadvantages• If the result files are not directly accessible, they are moved over the network resulting in

slower response time. This can be improved by mounting the PAS staging directory.• High investment and maintenance costs.



Option 4This option deploys RVS on the same machine as HyperWorks. PBS Professional and PBS Applica-tion Services are hosted on a single machine, while Compute Manager is hosted on a separate machine.

Advantages• Distributed environment reduces dependency.• Better performance as the services are running on three different machines.

Disadvantages• If the result files are not directly accessible, they are moved over the network resulting in

slower response time. This can be improved by making the PAS staging directory directly accessible to Server-C.

• High investment and maintenance costs.


3. Prerequisites

This chapter contains the following topics:• Prerequisites for Installing PBS Works• Prerequisites for Using CM• Prerequisites for Installing Display Manager• Prerequisites for Installing RVS• Prerequisites for Single Sign-On

Prerequisites for Installing PBS Works• System administrator privileges • Existence of the following users before beginning the installation

- The PBS Work superuser (CM only) - This user must be a pre-existing user on the machine where PBS Work is being installed. This user will be responsible for adminis-tering the CM web applications, for example adding PAS servers to CM.

- The PBS Works service user (Windows platforms only) - This user will be used to reg-ister the PBS Works service. This user must exist on the authentication server.

• Removal of any old instances of PBS Works applications and services - CM, DM, AMS, and RVS

• Adherence to the minimum system requirements (see System Requirements for CM on page 3).

27


Prerequisites for Using CMTo take full advantage of all the new features available with PBS Works 13.2, the HPC system must be updated to one of the supported PBS Works product configurations. See Supported Product Configurations on page 3.

Google Chrome Frame plug-inInternet Explorer versions 8, 9, 10, and 11 do not natively support the multi-file upload mecha-nisms for local files nor the file upload progress meter in Compute Manager. It has been observed that many times installing the Chromium projects Google Chrome Frame plug-in on Windows XP, Vista and Windows 7 has provided indirect support for this. However, this configuration has not formally been tested, so it is not fully supported by Altair. Please use the Chromium projects at your own discretion.

Prerequisites for Installing Display ManagerThe following prerequisites have to be met to allow the Display Manager Agent (DM Agent) to configure ngpus on PBS MOMs (Machine Oriented Miniservers). The term ngpus refers to a sin-gle custom consumable resource to represent all GPU devices on an execution host. Refer to the PBS Professional Administrator's Guide for more information.

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

28 Prerequisites


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

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

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:

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 29


Prerequisites for Installing Display Manager Agent for WindowsConfiguration of PBS Server

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

The PBS Works 13.2 installer will Install the DM components.

The PBS Works 13.2 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

Prerequisites for Installing RVS • Altair HyperWorks 12.0 - 110 must be installed.

- The HyperWorks installation should not be in /root or any user’s home directory.- HyperWorks should be installed in a location where all users have read and execute

permissions.- Refer to the HyperWorks installation guide for more details on how to install it.- Installation of RVS must be performed as root or an Administrative user.

• Compute Manager must be installed and the service should be up and running.

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)

30 Prerequisites


• adherence to the minimum system requirements (see System Requirement for RVS on page 8).

Prerequisites for using RVS • Configuration of Compute Manager is necessary after installation of RVS to register RVS

with CM. Please see the “Configurations on Compute Manager” section of the Results Visualization Service Administrator’s Guide.

• The RVS URL (http://<RVSHost>:Port ) must be directly accessible from the connecting web clients, unless RVS is configured to route traffic through Compute Manager. See “Enabling RVS traffic through CM” in the Compute Manager Administrator’s Guide for more information.

Recommended RequirementsTo avoid copying result files from job execution host to RVS, all execution hosts job scratch direc-tories should be directly accessible from RVS. For more information, refer to the section “Making Job Directories Available to RVS” in the Results Visualization Service Administrator’s Guide.

To avoid file copies, the file location should be directly accessible to RVS. The PAS staging direc-tory and job output directories (such as user’s home or project directories) should be mounted on RVS.

In some situations the above setup is not possible. Therefore, to use an efficient file copying sys-tem, password-less authentication must be configured among all hosts.

Prerequisites for Single Sign-OnSingle Sign-On (SSO) for the application allows the users to log in to the installed applications without providing the username and password. The user will be allowed to log in using their domain credentials, i.e., the username and password that they use to login to their client system.

By default SSO is disabled. The easy and recommended way to enable SSO is during the installa-tion. Refer to Installing PBS Works Using the Custom Installation Option on page 49 for more information.

You can also enable SSO manually after the installation. Refer to Enabling Single Sign-On on page 101 for more information.

You cannot enable SSO using Express Installation option.

Prerequisites 31


The following tasks have to be performed for SSO to work:• SPN Registration• Configuring Client Browser for SSO

SPN RegistrationPerform the Execute Registering an SPN steps provided at http://spnego.sourceforge.net/spne-go_tomcat.html for SPN registration.

Configuring Client Browser for SSOYou have to configure client browser for SSO to work. Refer to https://ping.force.com/Support/PingFederate/Integrations/How-to-configure-supported-browsers-for-Kerberos-NTLM for the steps to configure client browser.

The above link also provides the list of supported browsers for SSO.

32 Prerequisites

http://spnego.sourceforge.net/spnego_tomcat.html

http://spnego.sourceforge.net/spnego_tomcat.html

https://ping.force.com/Support/PingFederate/Integrations/How-to-configure-supported-browsers-for-Kerberos-NTLM

https://ping.force.com/Support/PingFederate/Integrations/How-to-configure-supported-browsers-for-Kerberos-NTLM

4. Installing PBS Works

Installation is similar to the installation of other PBS Works products. A binary or executable needs to be downloaded from the PBS Works user area and executed. The installer will walk you through the installation process.

Typically, the PBS Works service is installed and configured to use port 8086. If this port is not available during installation, then the PBS Works installer will increment the port number and try again. This will continue until a free port is found, or until 100 consecutive ports are refused at which point the installer will ask for a port.

This chapter contains the following topics:• Express Installation• Custom Installation• Installing RVS on the Same Machine as CM• AMS Migration from Previous Versions of CM• Configuration of PBS• Installation Information• Installation Check List• Installing PBS Works Using the Express Installation Option• Installing PBS Works Using the Custom Installation Option• Installing RVS Using the Custom Installation Option

33


Express Installation

The Express installation option installs both CM and DM. Additionally, AMS and a database instance (port 6767) are installed. If a MOM is detected, then the DM agent is installed.

SSH protocol is used for authentication on Linux/Unix platforms, and Windows protocol on Win-dows platforms.

Authorization services are performed through AMS.

The installation directory will be:on Windows: C:\altair\pbsworks\13.2on Unix/Linux: /opt/altair/pbsworks/13.2

For DM, the number of GPUS available in the cluster defaults to one (1). This information will be used to configure the PBS Professional Server. The number of GPUS on the execution hosts defaults to one (1). This information will be used to configure the PBS MOM.

The database administrator defaults to “pbsworksuser” and the default AMS administrator user name is “amadmin”.

For Installation steps, see Installing PBS Works Using the Express Installation Option.

The Express option is recommended for installations where both Com-pute Manager and Display Manager are being installed on the same machine as PBS Professional and PBS Application Services.

34 Installing PBS Works


Custom InstallationThe Custom option provides more flexibility during installation. You can choose what applications to install, where to install, type of authentication and authorization to use, and you can install the PBS Works application on a separate machine from PAS and PBS.

The following PBS Works products can be installed with the custom installation option:• CM only• CM and DM• RVS

The installation of any of these PBS Works products also installs AMS and a database instance (port 6767).

If DM is installed and a MOM is detected, then the DM agent is installed.

If credentials are not provided for the database administrator during installation, then the data-base administrator defaults to “pbsworksuser”. The default AMS administrator username is “amadmin”.

For Installation steps, see Installing PBS Works Using the Custom Installation Option.

Installing RVS on the Same Machine as CMCurrently, the Custom option of the PBS Works installer does not support installing RVS at the same time as CM (typically RVS is installed on a separate machine). If you are installing RVS on the same machine as CM, then you need to install RVS in a separate location from CM. Addition-ally, RVS should be installed with its own database. Do not connect to an existing PBS Works data-base.

For RVS Installation, see Installing RVS Using the Custom Installation Option.

AMS Migration from Previous Versions of CMIf you are currently running a previous version of Compute Manager, and would like to migrate the AMS datastore to avoid having to re-enter users, groups, and authorization policies into AMS, then prior to uninstalling CM, copy and save the following files:<INSTALL_DIR>/config/AAServiceHome/applications/cm/cmPolicy.xml

<INSTALL_DIR>/config/AAServiceHome/resources/AA_Users.xml

<INSTALL_DIR>/config/AAServiceHome/resources/AA_Groups.xml

Installing PBS Works 35


where <INSTALL_DIR> is the directory where the previous version of Compute Manager is installed.

Configuration of PBSThe PBS Works installer provides an option to automatically or manually configure the PBS Server with a new custom resource called ngpus and a new queue called iworkq and restart at the time of Installation and Uninstallation.

Manual Installation Configuration of PBSIf you opted for manual configuration of PBS during installation, follow the steps below:

1. Stop the PBS server:/etc/init.d/pbs stop

2. Edit the file /var/spool/PBS/sched_priv/sched_config and add ngpus to the resources line.For example: resources: "ncpus, mem, arch, host, vnode, netwins, aoe, ngpus"

3. Edit the file /var/spool/PBS/server_priv/resourcedef and add the custom resource ngpus as below:ngpus type=long flag=nh

4. Start the PBS Server/etc/init.d/pbs start

5. Add a queue to the complex: create queue iworkq

set queue iworkq queue_type = Execution

set queue iworkq Priority = 150

set queue iworkq max_queued_res.ngpus = [o:PBS_ALL=<MAX_NO_GPUS_IN_CLUSTER>]

set queue iworkq resources_max.ngpus = 1

set queue iworkq resources_min.ngpus = 1

set queue iworkq enabled = True

set queue iworkq started = True

6. If the machine where you are installing PBS Works is also a graphical execution host, then set the ngpus count:qmgr -c "set node <NODE_NAME> resources_available.ngpus=<NO_GPUS_ON_NODE>"



Manual Uninstallation Configuration of PBSDuring uninstallation, if you opt for an automatic uninstallation, the PBS ngpus resources and the iworkq queue will be removed and the PBS server will be restarted.

To skip this, manually restart the PBS server and perform the following steps:1. Remove the DM entries:

If ngpus is not used by any other application other than Display Manager, remove ngpus from the "resources:" line of PBS_HOME/sched_priv/sched_config and the line containing the ngpus resource from PBS_HOME/server_priv/resourcedef.

2. Delete iworkq:qmgr -c "delete queue iworkq"

3. On each GPU node, unset resources_available.ngpus using the command:qmgr -c "unset node <NODE_NAME> resources_available.ngpus"

4. Restart the PBS Server.

Installation InformationThe following table contains a list of installation details that you may be required to enter during the installation process. This information will vary depending upon the installation option chosen (Express or Custom), and the applications you have chosen to install.

Table 1. Installation Information

Name DescriptionLicense Server A license server is required to login to all of the PBS Works products.

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

It is not mandatory to provide the license server at installation time. You will however be required to configure the license server informa-tion prior to logging into any of the PBS Works products.Example: [email protected]: 6200@linuxserver



Super User This user will have privileges for administering the PBS Works applica-tions, for example adding PAS servers to CM.

On Linux, this user must be a pre-existing user on the machine where PBS Works is being installed.

On Windows:If the machine where PBS Works is being installed is a part of a domain, then specify a domain user that exists on the machine.

If the machine where PBS Works is being installed is not part of a domain, then specify a local user that exists on the machine.

Service User (applicable only for Windows)

This user will be used to register the PBS Works service. This user must exist on the authentication server.

Database A database instance is installed when you install any of the PBS Works products. You can choose to install a new database or connect to an existing database.

Existing DatabaseIf you have already installed a PBS Works product and want to connect to its database, choose this option.

You will be asked to provide the hostname, port, and database admin-istrator and password of the existing database.

Note: If you are installing RVS on the same machine as CM, do not connect to the existing PBS Works database. RVS should be installed with its own database.

New DatabaseIf you want to create a new database for the PBS Works product(s) that you are installing, choose this option.

A non-administrative user is required to own the database as an administrator. You can provide this user’s credentials, or you can let the installer create a database administrator.


Name Description



Access Management Service AMS provides a centralized configuration system for authentication and authorization. You can choose to install a new AMS instance or connect to an existing instance.

Use an Existing InstanceIf you have previously installed a PBS Works product and want to use the previously installed instance of AMS, choose this option.

You will be asked to enter the hostname and port where AMS is installed.

Install Access Management Service If you want to install a new instance of AMS, choose this option.

Installation Location The location where the selected applications will be installed. These components can be installed to the default location, or another loca-tion locally.

If you are installing RVS on the same machine as CM, choose a sepa-rate installation location. Do not install RVS in the same location as CM.

Two main directory structures CONFIG_HOME and SERVER_HOME are created during installation. For more information see Software Orga-nization on page 11.

Authentication During installation, PBS Works can be configured to use either Win-dows based or SSH based authentication, or it can be configured to authenticate against the AMS datastore.

If SSH is chosen, then a SSH server hostname/IP address is required. The default is localhost, however you may connect to any Linux server for authentication.

If you have chosen to authenticate against the AMS datastore, then the datastore must be populated prior to users logging into any of the PBS Works applications


Name Description



Authorization Authorization is performed against the AMS datastore. The AMS data-store can be populated with users and groups via a connection to a Windows AD, or any LDAP compatible server. Or it can be populated by using AMS to add users, groups, and authorization policies.

If you choose to use an LDAP/AD for authorization, then you will be prompted to enter the information necessary to connect to the LDAP/AD.

GPU Configuration for the PBS Server (for DM only)

If DM is being installed and a PBS Professional Server is detected by the installer on the machine where DM is being installed, you will be asked for the number of GPUs available in the cluster.

This information will be used to configure the PBS Professional Server.GPU Configuration for the PBS MOM (for DM only)

If DM is being installed and a PBS MOM is detected by the installer on the machine where DM is being installed, you will be asked for the number of GPUs available on the execution node.

This information will be used to configure the PBS MOM.Hyperworks Installation Location

HyperWorks must be installed on the same machine as RVS. Specify the installation location of HyperWorks.

PBS Application Service Server

Enter the hostname/IP address and port of the PAS server.

Configuration of PBS During the installation of DM, a new custom resource called ngpus is configured, a new queue called iworkq is created, and PBS is restarted. You can choose to perform this configuration manually after the installation completes or you can choose to allow the installer to make these changes for you.

This is applicable only for Linux installation.Single Sign-On You can enable Single Sign-On (SSO) for the application. With SSO

enabled, users will be logged in using their domain credentials, i.e., the username and password they use to login to their client system.

By default, SSO is disabled.

For more information see Prerequisites for Single Sign-On on page 31.

Service Principal Names (SPN) Domain Server

If you choose to enable SSO, then you must specify the SPN domain server and its corresponding details.


Name Description



Installation Check ListUse the following check list to verify that all pre-installation steps are complete before installing any of the PBS Works products.

Table 2. Pre-Installation Check List for all PBS Works Products

Task CompletePrevious Version of PBS Works

1. The AMS repository is backed up.2. Old instance of CM, DM, and RVS are removed.

Express Installation (installs CM and DM)1. Installation location is ______________________________________.

If you are installing RVS on the same machine as CM, choose a separate installation location. Do not install RVS in the same location as CM.The following installation folder is created:- CONFIG_HOME - This is where the PBS Works configuration and log

files are stored. The default location for CONFIG_HOME is:on Windows: C:\altair\pbsworks\13.2\homeon Linux: /var/spool/pbsworks/13.2/home

- SERVER_HOME - This is where the PBS Works binaries are stored. The default location for SERVER_HOME is:

on Windows: C:\altair\pbsworks\13.2\execon Linux: /opt/altair/pbsworks/13.2/exec

- RVS SERVER_HOME - This is where the RVS binaries, configuration, and log files are stored. RVS default installation folder is:

on Windows: C:\altair\rvs\13.2\execon Linux: /opt/altair/rvs/13.2/exec

2. License server is installed and running.- License server is _________________.

3. PBS Works Superuser is _________________________.4. PBS Works Service User (Windows only) is

______________________.



Custom Installation (installs CM, CM and DM, or RVS)1. Configuration of PBS Server is chosen:

Auto Configuration or Manual Configuration2. Installation location is ______________________________________.

If you are installing RVS on the same machine as CM, choose a separate installation location. Do not install RVS in the same location as CM.The following installation folder is created:- CONFIG_HOME - This is where the PBS Works configuration and log

files are stored. The default location for CONFIG_HOME is:on Windows: C:\altair\pbsworks\13.2\homeon Linux: /var/spool/pbsworks/13.2/home

- SERVER_HOME - This is where the PBS Works binaries are stored. The default location for SERVER_HOME is:

on Windows: C:\altair\pbsworks\13.2\execon Linux: /opt/altair/pbsworks/13.2/exec

- RVS SERVER_HOME - This is where the RVS binaries, configuration, and log files are stored. RVS default installation folder is:

on Windows: C:\altair\rvs\13.2\execon Linux: /opt/altair/rvs/13.2/exec

3. License server is installed and running.- License server is _____________________________.

4. AMS Configuration is chosen:Connecting to an existing instance of AMS:- AMS hostname or IP address is _______________________.- AMS port number is _______________________.ORInstalling a new instance of AMS.

5. Enable Single Sign-On (SSO) is chosen:


Task Complete



6. SPN registered for Single Sign-OnSPN Domain Server details:- Domain Server is _________________________.- Domain Username is _________________________.- Domain User Password is _________________________.

7. Authentication method is chosen:SSH is installed and running:- SSH server is _________________________.OR- Windows AD is installed and running.OR- AMS - AMS must be populated after the installation of PBS Works.

8. Method for populating AMS is chosen:Manually populate AMS using AMS console.ORConnect AMS to an AD/LDAP:- Domain URL is _________________________.- Domain component is _________________________.- AD Username is _________________________.- AD User Password is _________________________.- Group Container is _________________________.- User Container is _________________________.


Task Complete



Use the following check list to verify that all pre-installation steps are complete before installing Compute Manager.

9. Database Configuration is chosen:Connecting to an existing database:- Database hostname or IP address is _______________________.- Database port number is _______________________.- Database superuser is _______________________.- Database superuser password is _______________________.ORInstalling a new database:Optional:- Credentials of database superuser _________________.

10. Number of GPUs available in the Cluster ______________________.11. Number of GPUs available on the Execution Host _______________.12. PBS Works Superuser is _________________________.13. PBS Works Service User (Windows only) is

______________________.

Table 3. Pre-Installation Check List for CM

Task Complete1. Deployment option chosen.2. Hardware requirements meet at least the minimum requirements.3. Google Chrome Frame plug-in is installed and configured (optional).4. PBS Application Services 13.2 is installed.


Task Complete



Use the following check list to verify that all pre-installation steps are complete before installing Display Manager.

Table 4. Pre-Installation Check List for DM

Task Complete1. Deployment option chosen.2. Hardware requirements meet at least the minimum requirements.

PBS Professional Server3. Number of GPUs available on the PBS Professional cluster is

__________.Execution hosts (MOMs)

1. Operating system is any Linux distribution in the Red Hat Enterprise or SuSE Enterprise families which contains GLIBC 2.3.2 or later.

2. Video cards are either nVidia or ATI cards. 3. Linux proprietary drivers provided by the manufacturer of your 3D

adapters are installed.4. The video card drivers that are shipped with Linux provide full 3D

acceleration or pixel buffer support.5. GPU core/memory6. CPU core/memory7. X Server and applications on local display are configured and working.8. X Server is configured to export True Color (24 bit or 32 bit) visuals.9. Virtual Private Networking or secured channels for communication

between the Web Clients and the Display Manager server are being used if encryption is required.

10. The execution host is able to access and run the applications available through Display Manager.

11. Number of GPUs available on the execution host is _____________.Web Client

1. CPU is a Pentium 4/Xeon, 2.0 GHz or faster.2. Physical Memory is 2GB or higher.



Use the following check list to verify that all pre-installation steps are complete before installing Results Visualization Service.

3. Java Extensions have been enabled for the browser.4. JRE (Java Runtime Environment) is installed and available on the Web

Client. For more information on installing and troubleshooting your Java installation, refer to the following link:http://www.java.com/en/download/help/troubleshoot_java.xml

Table 5. Pre-Installation Check List for RVS

Task Complete1. Deployment option chosen.2. Hardware requirements meet at least the minimum requirements.3. Google Chrome Frame plug-in is installed and configured (optional).

Table 4. Pre-Installation Check List for DM

Task Complete






Installing PBS Works Using the Express Installation OptionTo ensure a successful installation, review the Prerequisites for Installing PBS Works on page 27.

Follow these steps to install CM and DM using the Express installation option:

1. Start the installer:Invoke the installer by executing the following command on Linux/Unix platforms:./PBS_Works_13.2_Linux_x86_64__YYYYMMDD_MMSS.bin -i swing

Or by double-clicking the executable on Windows platforms:PBS_Works_13.2_Windows_x86_64_YYYYMMDD_MMSS.exe

After extracting the files, the installation will proceed by displaying the splash screen fol-lowed by an Introduction dialog box. Read through the instructions before proceeding with the installation.

2. To continue the installation process, click Next.

License agreement information will be displayed. Read through the License Agreement before proceeding with the installation.

3. To accept the terms of the license agreement, select I accept the terms of the License Agreement, and click Next.

4. Select the Express Install option and click Next to install both CM and DM.

5. Choose an installation directory and click Next.

During the installation, the following directory structures are created:- Binaries Install Location - This is where the PBS Works binaries are stored.

The default location isOn Linux: /opt/altair/pbsworks/13.2/execOn Windows: C:\altair\pbsworks\13.2\execBinaries install location is referred as SERVER_HOME.

- Config Install Location - This is where the PBS Works configuration and log files are stored.

At anytime during the installation process, you may click Previous to go back to a previous installation step.To cancel the installation process, click Cancel.



The default location isOn Linux: /var/spool/pbsworks/13.2/homeOn Windows: C:\altair\pbsworks\13.2\homeBinaries install location is referred as CONFIG_HOME.

6. Enter the License Servers details and click Next.

7. Enter a user id that will be the PBS Works portal administrator and click Next.

This user will have privileges for administering the PBS Works applications, for example adding PAS servers to CM.

These components can be installed to the default location or another location locally.

It is not mandatory to provide the license server at installation time. You will however be required to configure the license server information prior to starting any of the PBS Works products. For more information see Configuring the License Server on page 66.

On Linux:This user must be a pre-existing user on the machine where PBS Works is being installed.On Windows:If the machine where PBS Works is being installed is a part of a domain, then specify a domain user that exists on the machine.If the machine where PBS Works is being installed is not part of a domain, then specify a local user that exists on the machine.

If the user does not exist, you can choose to select:- OK to continue the installation. You will need to configure the portal administrator once installation is complete. For more information see Configuring Administrative Users on page 87.- BACK to enter another user.



8. Enter a user id and password that will be used to register the PBS Works service. Click Next.

9. Click Install to initiate installation, if the installation specifications are correct. Click Pre-vious to go back, if the specifications are incorrect.

You can monitor the progression of your installation via the installation progress toolbar.

Once the installation is complete, the PBS Works service will be started and the installation details will be displayed.

10. Click Done to complete the installation.

Installing PBS Works Using the Custom Installation OptionTo ensure a successful installation, review the Prerequisites for Installing PBS Works on page 27.

Follow these steps to install PBS Works products using the Custom installation option:

1. Start the installer:Invoke the installer by executing the following command on Linux/Unix platforms:./PBS_Works_13.2_Linux_x86_64__YYYYMMDD_MMSS.bin -i swing

Or by double-clicking the executable on Windows platforms:PBS_Works_13.2_Windows_x86_64_YYYYMMDD_MMSS.exe



This user must exist on the authentication server.

If the DM Agent is installed, you will be advised to restart the system. Click Yes to restart the system.






4. Select the Custom Install option and click Next.

5. Choose any one of the following applications to install:- Compute Manager- Display Manager (Compute Manager will be installed as a prerequisite)- Service: Results Visualization ServiceFor RVS Installation steps, see Installing RVS Using the Custom Installation Option.

6. Click Next.

If DM is being installed, then you will be advised that the PBS and PAS servers will be restarted during the DM installation process. Choose- Yes to continue the installation.- No to discontinue the installation.

7. Choose one of the following options for configuring the PBS server:- Auto Configuration

PBS Professional will be configured. This will create a new interactive work queue, add custom resource to resourcedef and sched_config files. PBS server will be restarted.

- Manual Configuration

Manually configure the PBS Professional. Perform the steps in Manual Installation Configuration of PBS after the installation.

8. Choose an installation directory and click Next.


The default location isOn Linux: /opt/altair/pbsworks/13.2/execOn Windows: C:\altair\pbsworks\13.2\execBinaries install location is referred as SERVER_HOME.




The default location isOn Linux: /var/spool/pbsworks/13.2/homeOn Windows: C:\altair\pbsworks\13.2\homeBinaries install location is referred as CONFIG_HOME.


10. Choose one of the following options to configure AMS:- Use an Existing Instance

If you have previously installed a PBS Works product and want to use the previously installed instance of AMS, choose this option. You will be asked to enter the hostname and port where AMS is installed.

- Install Access Management Service

If you want to install a new instance of AMS, choose this option.

11. Choose one of the following options to configure Single Sign-On (SSO):- Yes

Enable Single Sign-On (SSO) for the application. With SSO enabled, users will be logged in using their domain credentials, i.e., the username and password they use to login to their client system.

Service Principal Names (SPN) has to be set for SSO to work. Refer to Prerequisites for Single Sign-On on page 31 for more information.

- No


It is not mandatory to provide the license server at installation time. You will however be required to configure the license server information prior to starting any of the PBS Works products. For more information see Configuring the License Server on page 66.

In Windows installation, SPN registration is verified once you enable SSO.



SSO is not enabled. You can perform the SSO configuration manually after installation. Refer to Enabling Single Sign-On on page 101 for more information.

12. Enter the SPN domain server details and click Next.

13. Choose the appropriate authentication protocol and click Next.

PBS Works can be configured to use either Windows based or SSH based authentication, or it can be configured to authenticate against the AMS datastore.

If SSH is chosen, then a SSH server hostname/IP address is required. The default is local-host, however you may connect to any Linux server for authentication.

If you have chosen to authenticate against the AMS datastore, then the datastore must be populated prior to users logging into the CM and DM web applications.

14. Choose the appropriate authorization mechanism, enter any necessary information, and click Next.

Authorization is performed against the AMS datastore. The AMS datastore can be popu-lated with users and groups via a connection to a Windows AD, or any LDAP compatible server. Or it can be populated by using the AMS console to add users, groups, and authori-zation policies.

If you choose to use an LDAP/AD for authorization, then you will be prompted to enter the information necessary to connect to the LDAP/AD.

15. Choose one of the following options for configuring the database:- Existing Database

If you have already installed a PBS Works product and want to connect to its database, choose this option.

If you are installing RVS on the same machine as CM, do not connect to the existing PBS Works database. RVS should be installed with its own database.

You will be asked to provide the hostname, port, and database administrator and pass-word of the existing database.

- New Database

If you want to create a new database for the PBS Works product(s) that you are install-ing, choose this option.

A non-administrative user is required to own the database as a administrator. You can provide this user’s credentials, or you can let the installer create a database administra-tor.



16. If a PBS Server is detected on the machine where PBS Works is being installed, enter the number of GPUs available in the cluster to configure the PBS Server for DM. Click Next.

17. If a PBS execution host is detected on the machine where PBS Works is being installed, enter the number of GPUs available in the node on the execution host to configure the PBS MOM for DM. Click Next.

18. Enter a user id that will be the PBS Works portal administrator and click Next.

This user will have privileges for administering the PBS Works applications, for example adding PAS servers to CM.

19. Enter a user id and password that will be used to register the PBS Works service. Click Next.

20. If the installation specifications are correct, click Install to start the installation. Otherwise, click Previous and make any necessary corrections.


Once the installation is complete, the PBS Works service will be started and the installation details will be displayed.

If the machine where PBS Works is being installed is a part of a domain, then specify a domain user that exists on the machine.If the machine where PBS Works is being installed is not part of a domain, then specify a local user that exists on the machine.

If the user does not exist, you can choose to select:- OK to continue the installation. You will need to configure the portal administrator once installation is complete. For more information see “Configuring Administrative Users” in the PBS Works Adminsitrator's Guide.- BACK to enter another user.

This user must exist on the authentication server.




Installing RVS Using the Custom Installation OptionResults Visualization (RVS) is a service, available through a plug-in, which provides necessary fea-tures to access, process and visualize CAE results through an easy and intuitive graphical user interface, embedded directly into the web browser. In the current release, these features are acces-sible through the Compute Manager web interface. The Results Visualization Service must be installed to use the plug-in with Compute Manager.

CM should be installed and its service should be up and running prior to installing RVS.

To ensure a successful installation, review the Prerequisites for Installing RVS on page 30.

Follow these steps to install PBS Works products using the Custom installation option:

1. Start the installer:Invoke the installer by executing the following command on Linux/Unix platforms:./PBS_Works_13.2.0_Linux_x86_64__YYYYMMDD_MMSS.bin -i swing

Or by double-clicking the executable on Windows platforms:PBS_Works_13.2.0_Windows_x86_64_YYYYMMDD_MMSS.exe


RVS should be installed with its own database. Do not connect to an existing PBS Works database.








4. Select the Custom Install option and click Next.

5. Choose Service: Results Visualization Service to install the Results Visualization Ser-vice. Click Next.

6. Choose New Database option to create a new instance of a database for RVS.

A non-administrative user is required to own the database as a administrator. You can pro-vide this user’s credentials, or you can let the installer create a database administrator. Do not connect to an existing database.

7. Specify a location where RVS will be installed.

If you are installing RVS on a separate machine from CM, then you may use the default location.


The default location is

If RVS is being installed on the same machine as CM, and CM has already been installed, then Manage Instance dialog box will be dis-played.Choose the Install a New Instance option. When prompted for an instal-lation location for RVS, do not select the default location. Installing into the default location will overwrite the instance of CM that has already been installed. Instead, install RVS into a separate location than CM.

Do not install RVS to the same location as CM. Installing RVS to the same location as CM overwrites the previous installation.



On Linux: /opt/altair/rvs/13.2/execOn Windows: C:\altair\rvs\13.2\execBinaries install location is referred as SERVER_HOME.


The default location isOn Linux: /var/spool/rvs/13.2/homeOn Windows: C:\altair\rvs\13.2\homeBinaries install location is referred as CONFIG_HOME.


9. Specify the installation location of HyperWorks. To select a directory click Choose. To restore the default directory, click Restore Default Folder.

10. Enter the hostname/IP address and port of the PAS server.

11. If the installation specifications are correct, click Install to start the installation. Otherwise, click Previous and make any necessary corrections.


Once the installation is complete, the PBS Works Results Visualization Service will be started and the installation details will be displayed.



It is not mandatory to provide the license server at installation time. You will however be required to configure the license server information prior to starting any of the PBS Works products. For more information see Configuring the License Server.



5. Starting, Stopping and Restarting

PBS Works Portal

Starting the PBS Works ServiceLinux

At the Linux command line prompt enter:/etc/init.d/pbsworks start

Windows

1. Navigate to Control Panel -> Administrative Tools -> Services.

2. Right-click PBSWorks Service

3. Select Start.

Stopping the PBS Works ServiceLinux

At the Linux command line prompt enter:/etc/init.d/pbsworks stop

Windows



3. Select Stop.

Restarting the PBS Works ServiceLinux

At the Linux command line prompt enter:/etc/init.d/pbsworks restart

57


Windows



3. Select Restart.

Determining the Status of the PBS Works ServiceLinux

At the Linux command line prompt enter:/etc/init.d/pbsworks status

Windows


2. View the Status column of the PBSWorks Service to determine the status of the service.

RVS ServiceAdministrator privileges are required to start, stop and restart RVS.

Starting RVSAt the Windows command line enter:

RVS SERVER_HOME/scripts/RVservice.bat start

At the Linux command prompt enter:./etc/init.d/rvs start

Determine the Status of RVSAt the Windows command line enter

RVS SERVER_HOME/scripts/RVservice.bat status

At the Linux command prompt enter:./etc/init.d/rvs status

58 Starting, Stopping and Restarting


Stopping RVSAt the Windows command line enter

RVS SERVER_HOME/scripts/RVservice.bat stop

At the Linux command prompt enter:./etc/init.d/rvservices stop

Restarting RVSAt the Windows command line enter

RVS SERVER_HOME/scripts/RVservice.bat restart

At the Linux command prompt enter:/etc/init.d/rvs restart

To start and stop RVS from the service management console in Windows, use Results Visualization Service. On Linux, use the rvs service.

Starting, Stopping and Restarting 59


60 Starting, Stopping and Restarting

6. Uninstall PBS Works

Prior to uninstalling, stop the PBS Works service. Refer Starting, Stopping and Restarting for more information.

Starting the Uninstaller

Follow the instructions as documented below for uninstalling CM/DM.

To uninstall RVS, you will have to navigate to the directory where RVS has been installed to per-form the uninstall of RVS (follow the same set of instructions for uninstalling, but just execute the uninstall script that is located in the RVS installation directory).

In Linux:

1. Navigate to the PBS Works installation directory. The installation directory for a typical installation of PBS Works is/opt/altair/pbsworks/13.2

2. Enter the following at the Linux/Unix command line prompt (command must contain spaces with escape characters):cd _PBS\ Works\ Suite_installation

3. Execute the uninstall script by entering the following command at the Linux/Unix com-mand line prompt (command must contain spaces with escape characters)

If you have installed RVS on the same machine as CM, then two separate uninstall processes will have to be performed to remove CM/DM and RVS.

61


./Change\ PBS\ Works\ Suite\ Installation -i swing

In Windows:

1. Navigate to the _PBS Works Suite_ installation folder in the location where PBS Works 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.

1. The Installer launches in Maintenance Mode. Select Uninstall Product and click on the Next button.

When you are uninstalling the DM in Linux, you can choose to update the servers automatically and restart them or you can manually update the servers and restart them. If you opted for manual configuration, perform the steps in Manual Uninstallation Configuration of PBS.

Confirm your choice for removing the CONFIG_HOME folder i.e., /var/spool/pbsworks/13.2/home

62 Uninstall PBS Works


2. In the next screen, click on the Uninstall button.

3. Click OK to Uninstall PBS Works Suite.

The uninstall process will begin and the progress will be shown.

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

Confirm your choice for removing the CONFIG_HOME folder i.e., C:\altair\pbsworks\13.2\home

Uninstall PBS Works 63


64 Uninstall PBS Works

7. Post-Installation Steps

Once the installation of a PBS Works product is complete, the following post-installation steps are required. Changes will effect all PBS Works products installed on the machine where the modifi-cation is being made.

1. Configuring the License Server when a license server was not supplied during installation.2. Changing the AMS Administrator’s Password.3. Setting up authentication, authorization and profile sharing by performing one of the fol-

lowing steps:- Migrating the AMS Datastore. - Populating AMS for authentication, authorization and profile sharing.

Post-installation steps related to a specific PBS Works product can be found in the product’s respective Administrator’s Guide.

Once all post-installation steps are complete, use any of the supported browsers to login to PBS Works through the URL:

http://<hostname>:<port>/pbsworks

Refer to PBS Works Advanced Configuration on page 79 for other advanced configuration options for the PBS Works suite of products.

65


Configuring the License Server A license server must be configured during the installation of PBS Works, you will be prompted to supply information about the license server (port and hostname/IP address). You may supply the information at this time, or PBS Works can be configured with this information post-installation.

You can configure the license servers after installation in console mode or in the application.

Adding the License Server in ConsoleThe license server information is stored in the adminSettings.xml file.

The location of this file for a typical installation of a PBS Works product is:

on Windows: CONFIG_HOME\binaries\framework\data

on Linux: CONFIG_HOME/binaries/framework/data

Change the port and hostname of the XML element <value> to the port and hostname of the license server in the format port@hostname.

The PBS Works service must be restarted for these changes to take effect.

You must have administrative privileges to configure the Compute Man-ager license server.

Separate multiple server details with a colon (:) in Linux and with a semi-colon ( ; ) in Windows.

<Category name="License Server">

<Setting name="Location" preference="true">

<value>6200@trlicsrv03</value>

<class>com.altair.awpf.services.preferences.model.StringPreference</class>

<displayName>Server Location</displayName>

<isEnforced>true</isEnforced>

<private>false</private>

</Setting>

</Category>

66 Post-Installation Steps


Adding the License Server in the ApplicationYou can update the license server in the application as follows:

1. Click the Settings button . 2. Click Settings > License Server.3. Enter the details of the license server. You can provide multiple license server details.

4. Click the Apply. 5. Click OK.6. Restart the PBS Works service.

Separate multiple server details with a colon ( : ) in Linux and with a semicolon ( ; ) in Windows.

Post-Installation Steps 67


Changing the AMS Administrator’s Password Once a PBS Works product is installed, changing the AMS administrator password from the default of "adminadmin" to a secure site-specific password is highly recommended.

To change the AMS administrator password:

1. Navigate to the following directory:

on Windows: SERVER_HOME\binaries\common\ams

on Linux: SERVER_HOME/binaries/common/ams

2. Issue the following command to change the AMS administrator password:

SERVER_HOME/thirdparty/java/bin/java -jar AccessManagerInstallation.jar update-admin-password <oldpassword> <newpassword>

3. Encrypt the new password by issuing the following command (this command will output the password in its encrypted format):

SERVER_HOME/thirdparty/java/bin/java -jar AccessManagerInstallation.jar encrypt <newpassword>

4. Edit the file following file:

on Windows: SERVER_HOME\services\cm\config\authzlogin.properties

on Linux: SERVER_HOME/services/cm/config/authzlogin.properties

5. Change <ENCRYPTED_AMS_PASSWORD> to the encrypted format of the new password.

password=<ENCRYPTED_AMS_PASSWORD>

6. Restart the PBS Works service.



Migrating the AMS DatastoreMigrating the AMS datastore from your previous version of CM avoids having to re-enter users, groups, and authorization policies into AMS. To migrate the AMS datastore from your previous version of CM to 13.2, you will need to merge the previous version of the AMS datastore files with the 13.2 versions.

The previous version of the AMS datastore files should have been saved prior to installing a PBS Works 13.2 product. For more information see AMS Migration from Previous Versions of CM on page 35.

The files that will need to be merged are those that were saved prior to installing PBS Works 13.2 and the following files that are located in the PBS Works installation 13.2 directory:

• CONFIG_HOME/AMS/AAServiceHome/applications/cm/cmPolicy.xml

• CONFIG_HOME/AMS/AAServiceHome/resources/AA_Users.xml • CONFIG_HOME/AMS/AAServiceHome/resources/AA_Groups.xml

After installing PBS Works 13.2, follow these instructions for merging the files:

1. Copy all <user></user> tags from the previous version of AA_Users.xml to the 13.2 version of AA_Users.xml, except the users amadmin and portal_admin. Do not overwrite these users in the 13.2 version of AA_Users.xml:

The user amadmin is the AMS administrator and the user portal_admin is the PBS Works portal administrator entered during installation.

The xmllint command line tool may have to be used to reformat the XML files in a more readable format. Use the following command:xmllint --format <file_name> > temp_file

<?xml version="1.0" encoding="UTF-8"?><users>

<user userName="amadmin">

<password>fnGbROpp3kCV65tCw52RBcsUmMnJfhuMnkgfm23UAQs=</password>

</user>

<user userName="<portal_admin">

<password>9z1WNgdMqjh42kPr7gGhbbKKlzVOWfeeVvQX00fRVc0=</password>

</user>

</users>



2. Copy all <group></group> tags from the previous version of AA_Groups.xml to the 13.2 ver-sion of AA_Groups.xml, but do not overwrite the altairadmin group in the 13.2 version of AA_Groups.xml:

3. As the PBS Works portal administrator, log into Compute Manager.

4. Add all previous PBS Professional servers. It is VERY important to add a server with the same CM server name that was used for the previous CM release. You can determine those names by viewing the previous version of the cmPolicy.xml file, and searching for the tag Resource name="CM/Server”. You will see something similar to:

where pbsworks1 and pbsworks2 are the CM server names.

5. Once all servers have been added, copy the previous version of the cmPolicy.xmlfile to the location of the 13.2 version.


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<groups>

<group name="altairadmin" privilegeType="TRUE">

<user>portal_admin</user>

</group>

</groups>

<Resource name="CM/Server">

<Resource name="CM/Server/pbsworks1">

<Resource name="CM/Server">

<Resource name="CM/Server/pbsworks2">



Populating AMS AMS must be populated with users and groups when any of the following conditions are met:

• AMS was chosen as the mechanism for authentication and is not connected to a LDAP/AD• your site wants to use the profile sharing functionality of CM• your site wants to define user or group access policies

For more information about authentication, authorization, or profile sharing see Authentication and Authorization on page 10.

Populating AMS requires the following steps:1. Logging into AMS.2. Adding Users and Groups when AMS is not connected to a LDAP/AD.

Logging into AMS To log into AMS, enter the following in the address bar of any supported browsers.

<PBS_WORKS_HOSTNAME:PORT>/pbsworks/ui/ams/

For more information about supported browsers see Supported Browsers on page 3.

The AMS login page will open in the browser as shown below:

Use the PBS Works portal administrator credentials to log into AMS. These credentials are speci-fied during the installation of PBS Works.



Adding Users and Groups

Managing User Accounts

Use the Users tab to manage user accounts added to AMS using the AMS console or through a connection to an LDAP/AD.

The Status Messages area provides information on the latest actions performed.

The Filter Records field above a column’s title can be used to filter the information displayed.

Use the Delete button located in the same row as the user to delete a user.

Users cannot be added or deleted when AMS is connected to an LDAP/AD.



Click Add New to add a new user. Enter the user account information. The required fields are marked with an asterisk (*). Click Save to create the new user account.



Select a user in the list to view details of the user account.

Click the Edit tab to edit the user account details.

Once all updates to the user account information are complete, click Save.



Managing User Groups

Click the Groups tab to manage groups added to AMS using the AMS console or through a con-nection to an LDAP/AD.

The Status Messages area provides information on the latest actions performed.

The Filter Records field above a column’s title can be used to filter the information displayed.

Use the Delete button located in the same row as the group to delete a group.

User Groups cannot be added or deleted when AMS is connected to an LDAP/AD.



Click Add New to add a new group. Enter the group information. The required fields are marked with an asterisk (*). Click Save to create the new group.

Select a group in the list to view details of the group account.



Click the Edit tab to edit members of a group.

Select a user from the Available Users list and click to add the user to the group.

Select a user from the Users in the group list and click to remove the user from the group.

You can set administrator privileges for a group by enabling the Set Admin Privilege check box.

Once all updates are complete, click Save.


8. PBS Works Advanced Configuration

This chapter contains advanced configuration options for the PBS Works suite of products. Changes to the default settings associated with any of the following topics will effect all PBS Works applications installed on the machine where the modification is being made. For an overview of PBS Works configuration files see PBS Works Configuration Files.

• Changing the Authentication Method• Configuring Administrative Users• Improving File Operations Performance• Improving JVM Performance• Changing the Postgres Database• Changing the Database Password• Changing the PBS Works Logging Behavior• Configuring Session Timeout• Configuring Language/Localization• Configuring SSL• Enabling Single Sign-On• Disabling Single Sign-On• PBS Works Configuration Files

79


Changing the Authentication MethodDuring installation, PBS Works can be configured to use either Windows based or SSH based authentication, or it can be configured to use the AMS datastore for authentication.

Authentication information is stored in the file AA_jaas.config. The location of the file for a typi-cal installation of PBS Works is:

on Windows: CONFIG_HOME\AMS\AAServiceHome\config

on Linux: CONFIG_HOME/AMS/AAServiceHome/config

PBS Works supports the following methods for authentication:• SSH• Windows• AMS datastore• NIS• PAM

Sample configuration files for all authentication methods are stored in the AAServiceHome direc-tory. Administrators can use these configuration files for:

• Changing Authentication to SSH• Changing the SSH Server or Port• Changing Authentication to Windows• Changing Authentication to use the AMS Datastore• Changing Authentication to NIS• Changing the NIS Server• Changing Authentication to PAM

PAM and NIS have not been fully tested - use these authentication meth-ods with caution.

80 PBS Works Advanced Configuration


Changing Authentication to SSHBy default, SSH uses port 22, although you may configure SSH to use another port. If SSH is cur-rently being used for authentication, and you want to change the SSH server or port number, then follow the instructions for Changing the SSH Server or Port.

Follow these instructions to change the authentication method to SSH:

1. Back up the existing AA_jaas.config.

2. Copy the sample configuration file AA_jaas.config.ssh to AA_jaas.config.

3. Update the SSH server and port by following the instructions for Changing the SSH Server or Port.


Changing the SSH Server or PortFollow these instructions to change the SSH server or the SSH port:

1. Edit the AA_jaas.config file.

2. Replace <SSH_SERVER> with the new SSH server IP address or hostname.

3. Replace <PORT> with the new port number.


LoginModule {

com.altair.jaas.module.SSHUnixLoginModule Required

host="<SSH_SERVER>"

port="<PORT>"

cache_ttl="60"

debug=false;

};

Super_User_Login {

com.altair.jaas.module.DatastoreLoginModule Required;

};

PBS Works Advanced Configuration 81


Changing Authentication to WindowsFollow these instructions to change the authentication method to Windows:


2. Copy the sample configuration file AA_jaas.config.win to AA_jaas.config.


Changing Authentication to use the AMS DatastoreFollow these instructions to change the authentication method to use the AMS datastore:


2. Copy the sample configuration file AA_jaas.config.ds to AA_jaas.config.

3. If you wish to populate the AMS datastore with information stored in a Windows Active Directory (AD), or a Lightweight Directory Access Protocol (LDAP) compatible server, then provide the necessary information to connect to the LDAP/AD by following the instructions for Connecting to a LDAP/AD. Otherwise, users and groups will have to added to the AMS datastore. For more information see Populating AMS on page 71.


Connecting to a LDAP/AD

LDAP/AD information is stored in the Datastore.properties file. The location of the file for a typical installation of PBS Works is:

on Windows: CONFIG_HOME\AMS\AAServiceHome\config\Datastore

on Linux: CONFIG_HOME/AMS/AAServiceHome/config/Datastore

Replace all LDAP attributes with the appropriate values of your site’s LDAP/AD attributes.

Check with Altair support for valid values for these attributes



Table 1. LDAP/AD Attributes

LDAP Attribute Description Examplecom.altair.aaservice.ldap.depart-mentId

Name of the department in which the user works

Computational Fluid Dynamics

com.altair.aaservice.ldap.domain Domain Name of AD example.organization.comcom.altair.aaservice.ldap.TitleId The user's job title Systems Engineercom.altair.aaservice.ldap.domain-component

Domain Components DC=example, DC=organization, DC=com

com.altair.aaservice.ldap.firstNa-meID

Given name of user Sam

com.altair.aaservice.ldap.Coun-tryId

Denotes the group's country in a 3 digit code which is based on ISO standard 3166.

840 denotes USA

com.altair.aaser-vice.ldap.domainuser.password

Encrypted password of the user

com.altair.aaser-vice.ldap.domainuser.id

User identifier ssmith

com.altair.aaservice.ldap.url Valid LDAP/AD URL to connect

ldap://192.168.5.38:389/

com.altair.aaservice.ldap.Loca-tionId

l

com.altair.aaservice.ldap.Man-agerId

Contains the distin-guished name of the user who is the user's manager

CN=John,OU=DIREC-TORS,DC=acmethecom-pany,DC=com

java.naming.factory.ini-tial=com.sun.jndi.ldap.LdapCtx-Factory

Java naming factory Do not change this attribute

com.altair.aaservice.ldap.com-manNameAttributeId

The name that represents an object, used to per-form searches

Sam Smith

com.altair.aaservice.ldap.Tele-phoneNoId

Primary telephone num-ber of user

+1 210 000 1234

com.altair.aaservice.ldap.roleAt-tributeID

ID for Role attribute in AD

memberOf

com.altair.aaservice.ldap.lastNam-eID

Surname of user Smith



com.altair.aaservice.ldap.emaiId Email id of user [email protected]

sAMAccountName

com.altair.aaservice.ldap.group-container

Semicolon (;) separated list of groups the user belongs to

OU=Distribution Groups,OU=Groups,DC=example,DC=Organization,DC=com”;“OU=Distribution Groups2,OU=Groups,DC=example,DC=Organization,DC=com,CN=Mentors,OU=Technol-ogy,DC=acmethecom-pany,DC=com

com.altair.aaservice.ldap.groupO-bjectClass

Object class for Group in AD

group

com.altair.aaservice.ldap.usercon-tainer

User Container in AD “CN=Users,DC=example,DC=Organization,DC=com”;“ OU=NoScrSvr,OU=MKTG,DC=example,DC=Organization,DC=com”

com.altair.aaservice.ldap.userOb-jectClass

Object Class for User in AD

user

com.altair.aaservice.ldap.member-AttributeID

ID for Member attribute in AD

member

com.altair.aaservice.ldap.recon-nectTimeInSeconds

Reconnect time in sec-onds in case of network issues

10

Table 1. LDAP/AD Attributes

LDAP Attribute Description Example



com.altair.aaservice.ldap.departmentId=<ID for Department Attribute in AD>

com.altair.aaservice.ldap.domain=<Domain Name of AD>

com.altair.aaservice.ldap.TitleId=<ID for Title attribute in AD>

com.altair.aaservice.ldap.domaincomponent=<Domain Component of AD>

com.altair.aaservice.ldap.firstNameID=<ID for First Name attribute in AD>

com.altair.aaservice.ldap.CountryId=<ID for Country attribute in AD>

com.altair.aaservice.ldap.domainuser.password=<Encrypted password of the user>

com.altair.aaservice.ldap.domainuser.id=<Existing user id>

com.altair.aaservice.ldap.url=<Valid LDAP/AD URL to connect>

com.altair.aaservice.ldap.LocationId=<ID for Location Attribute in AD>

com.altair.aaservice.ldap.ManagerId=<ID for Manager Attribute in AD>

java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory

com.altair.aaservice.ldap.commanNameAttributeId=<ID for Common Name in AD>

com.altair.aaservice.ldap.TelephoneNoId=<ID for Telephone Number in AD>

com.altair.aaservice.ldap.roleAttributeID=<ID for role attribute in AD>

com.altair.aaservice.ldap.lastNameID=<ID for Last name attribute in AD>

com.altair.aaservice.ldap.emaiId=<ID for Email attribute in AD>

com.altair.aaservice.ldap.uidAttrName=<ID for User Id attribute in AD>

com.altair.aaservice.ldap.groupcontainer=<Group Container in AD>

com.altair.aaservice.ldap.groupObjectClass=<Object Class for Group in AD>

com.altair.aaservice.ldap.usercontainer=<User Container in AD>

com.altair.aaservice.ldap.userObjectClass=<Object Class for User in AD>

com.altair.aaservice.ldap.memberAttributeID=<ID for Member attribute in AD>

com.altair.aaservice.ldap.reconnectTimeInSeconds= <Reconnect time in seconds>



Changing Authentication to NISFollow these instructions to change the authentication method to NIS:


2. Copy the sample configuration file AA_jaas.config.nis to AA_jaas.config.

3. Download the nis-1_2_1.zip file from http://www.oracle.com/technetwork/java/javase-business/downloads/java-archive-downloads-java-plat-419418.html.

4. Extract the file nis-1_2_1.zip to a directory called <EXTRACTED_LOC>.

5. Copy the jar files nis.jar and providerutil.jar from <EXTRACTED_LOC>/lib to SERVER_HOME/binaries/common where SERVER_HOME is the location where PBS Works was installed.

6. Update the NIS server by following the instructions for Changing the NIS Server.


Changing the NIS ServerFollow these instructions to change the NIS server:

1. Edit the AA_jaas.config file.

2. Replace <NIS_USER_URL> and <NIS_GROUP_URL> with the appropriate values for your site’s NIS server. For example:

user.provider.url="nis://NISServerHostName/NISDomain/user"

group.provider.url="nis://NISServerHostName/NISDomain/system/group"

LoginModule {

com.sun.security.auth.module.JndiLoginModule Required

strongDebug="false"

user.provider.url="<NIS_USER_URL>"

group.provider.url="<NIS_GROUP_URL>"

tryFirstPass="false"

useFirstPass="false"

storePass="true"

clearPass="true"

debug="true"

java.naming.factory.initial=com.sun.jndi.nis.NISCtxFactory;

};


http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-java-plat-419418.html

http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-java-plat-419418.html


Changing Authentication to PAMFollow these instructions to change the authentication method to PAM:


2. Copy the sample configuration file AA_jaas.config.pam to AA_jaas.config.

3. Download the jaas-pam-0.2-src.tar.gz from http://sourceforge.net/projects/jaas-pam/files/latest/download.

4. Extract the contents of the jaas-pam-0.2-src.tar.gz file to a directory called <EXTRACT-ED_LOC>.

5. Set the environment variable JAVA_HOME to the following, where SERVER_HOME is the installa-tion directory of PBS Works:

export JAVA_HOME=SERVER_HOME/thirdparty/java

6. Navigate to the directory <EXTRACTED_LOC>/jaas-pam-0.2/src/java.

7. Compile the JAAS PAM Java classes by issuing the following commands:

$JAVA_HOME/bin/javac -encoding ISO-8859-1 ch/odi/jaaspam/*.java

$JAVA_HOME/bin/javac -encoding ISO-8859-1 ch/odi/pam/*.java

8. Create a jar file from the compiled Java classes by issuing the following command:

jar cvf <jar_file_name> ch/odi/jaaspam/*.class ch/odi/pam/*.class

9. Copy the generated jar file to SERVER_HOME/binaries/common.


Configuring Administrative UsersDuring the installation of PBS Works, the installation process prompts for a userid that will be used to administer the PBS Works portal. This user will be responsible for administering the CM web application, for example adding PAS servers to CM. The installation process adds this admin-istrator to a group called altairadmin. To add or remove PBS Works portal administrators, simply add or remove users from this group using AMS. For more information about adding users to AMS see Adding Users and Groups on page 72.


http://sourceforge.net/projects/jaas-pam/files/latest/download

http://sourceforge.net/projects/jaas-pam/files/latest/download


Improving File Operations PerformanceWhen a job is running and a user views or downloads a file from the job’s execution directory, PBS Works asks PAS for the contents of the file in chunks. By default, PBS Works asks for 8 MB of con-tent at a time, therefore a 100 MB file results in 100/8 number of calls to PAS.

To improve the performance of these calls to PAS, this default can be set to a higher value (16, 32, 64, etc.). For example, increasing the default from 8 MB to 16 MB, halves the number of calls to PAS. Increasing the value of this default may have an adverse affect on memory (RAM). If the default is set to 32 MB and 10 users are simultaneously downloading the file, potentially 32*10 MB of RAM could be required just for downloads. This can result in an OutOfMemory exception, therefore take careful consideration when determining the optimal value for this argument.

This default is stored in a script file called server-start.sh on Linux and PBSWorksService.bat on Windows. The location of this file for a typical installation of PBS Works is:

on Windows: SERVER_HOME\scripts

on Linux: SERVER_HOME/scripts

The argument that needs to be modified is the JVM argument -DAIF_FILECHUNK_SIZE_MB.

This is the area of the server-start.sh file that needs to be modified:

This is the area of the PBSWorksService.bat file that needs to be modified:


echo "Setting CM Paramters"

if [ "$HWE_CM" == "INSTALLED" ] ; then

JAVA_OPTS="$JAVA_OPTS -DAIF_WSDL_LOCATION=file:///$HWE_INSTALLATION_DIRECTORY/services/cm/config/wsdl/"

JAVA_OPTS="$JAVA_OPTS -DAIF_FILECHUNK_SIZE_MB=8"

fi

"%EXECUTABLE%" //US//%SERVICE_NAME% --Environment "HWE_INSTALLATION_DIRECTORY=%HWE_INSTALLA-TION_DIRECTORY%#PATH='%PATH%'" --JvmOptions "-Xmx1024m;-Djava.security.auth.login.con-fig=%HWE_INSTALLATION_DIRECTORY%/config/login.config;-DHWE_INSTALLATION_DIRECTORY=%HWE_INSTALLATION_DIRECTORY%;-DAIF_WSDL_LOCATION="file:///"%HWE_INSTALLATION_DIRECTORY%"/services/cm/config/wsdl/";-Dderby.system.home=%HWE_INSTALLA-TION_DIRECTORY%/binaries/framework/data/datastore;-Dderby.infolog.append=true;-Djava.proto-col.handler.pkgs=com.altair.common.filetransfer;-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%/endorsed;-DAIF_FI-LECHUNK_SIZE_MB=8" --StartMode jvm --StopMode jvm



Improving JVM PerformanceTo sustain a large number of concurrent users (over 30), the Java Virtual Machine (JVM) heap size may need to be adjusted. Currently, the default JVM heap size is 1024 MB. If OutOfMemory errors or warnings are reported in the PBS Works log files, this value should be increased. It can be increased in multiples of 256 MB.

The Java heap size default is stored in a script file called server-start.sh on Linux and PBSWorks-Service.bat on Windows. The location of this file for a typical installation of PBS Works is:

on Windows: SERVER_HOME\scripts

on Linux: SERVER_HOME/scripts

The JVM argument that needs to be modified is the -Xmx1024m argument. Increase the 1024 value.

This is the area of the server-start.sh file that needs to be modified:

This is the area of the PBSWorksService.bat file that needs to be modified:


CATALINA_OPTS="-Xmx1024m -D${prodid}"

CATALINA_OPTS="$CATALINA_OPTS -Djava.security.auth.login.config=$HWE_INSTALLATION_DIRECTORY/config/login.config"

CATALINA_OPTS="$CATALINA_OPTS -Djava.protocol.handler.pkgs=com.altair.common.filetransfer"

export CATALINA_OPTS

set CATALINA_OPTS= "-Xmx1024m"

set CATALINA_OPTS="-Djava.security.auth.login.config=%HWE_INSTALLATION_DIRECTORY%/config/login.config"

set CATALINA_HOME=%TOMCAT_HOME%



Changing the Postgres DatabasePBS Works uses Postgres which is bundled with the PBS Works installer. PBS Works can be changed to point to a different Postgres database by updating the spring-config.xml file. The location of the file for a typical installation of PBS Works is:

on Windows: SERVER_HOME\services\cm\config

on Linux: SERVER_HOME/services/cm/config

Configuring the Postgres databaseFollow these instructions to point PBS Works to a different Postgres database:

1. Edit the spring-config.xml file.

2. Change the following values for the datasource properties:


<bean id="cmdataSource" destroy-method="close" class="com.altair.custom.datasource.EncryptBa-sicDataSource">

<property name="driverClassName" value="org.postgresql.Driver" />

<property name="url" value="jdbc:postgresql://<HOST>:<PORT>/<DB_NAME>"/>

<property name="username" value="<DB_USER>" />

<property name="password" value="<DB_PASSWORD>" />

<property name="maxActive" value="8" />

<property name="maxIdle" value="1" />

<property name="maxWait" value="-1" />

</bean>

Table 2. Datasource properties

Datasource Property DescriptionHOST The hostname or IP address of the server where Postgres is installed.PORT The port configured for Postgres.DB_NAME The Postgres database name.DB_USER The Postgres user name which PBS Works will use to connect to the data-

base.DB_PASSWORD The encrypted password for the Postgres user name. For more informa-

tion about encrypting the password see Changing the Database Pass-word.



Changing the Database PasswordIf the Postgres database password is changed (via passwd, yppasswd, etc.), then PBS Works will need to be updated with the new password.

The Postgres database password is stored in the spring-config.xml file. The location of the file for a typical installation of PBS Works is:

on Windows: SERVER_HOME\services\cm\config

on Linux: SERVER_HOME/services/cm/config

Follow these direction to change the database password:

1. Navigate to the following directory:

on Windows: SERVER_HOME\binaries\common\ams

on Linux: SERVER_HOME/binaries/common/ams

2. Encrypt the new password by issuing the following command (this command will output the password in its encrypted format):

SERVER_HOME/thirdparty/java/bin/java -jar AccessManagerInstallation.jar encrypt <newpassword>)

3. Edit the spring-config.xml file.

4. Change <DB_PASSWORD> to the encrypted format of the new password.


<bean id="cmdataSource" destroy-method="close" class="com.altair.custom.datasource.EncryptBa-sicDataSource">

<property name="driverClassName" value="org.postgresql.Driver" />

<property name="url" value="jdbc:postgresql://<HOST>:<PORT>/<DB_NAME>"/>

<property name="username" value="<DB_USER>" />

<property name="password" value="<DB_PASSWORD>" />

<property name="maxActive" value="8" />

<property name="maxIdle" value="1" />

<property name="maxWait" value="-1" />

</bean>



Changing the PBS Works Logging BehaviorBy default, the PBS Works logging behavior is as follows:

• The logging level is set to INFO designating coarse-grained informational messages. • Backup copies of the logs files are kept.

The PBS Works logging behavior for the installed applications can be defined in the log4j.proper-ties file. The location of the file for a typical installation of PBS Works is:

on Windows: CONFIG_HOME\services\<Application Name>\config

on Linux: CONFIG_HOME/services/<Applicaiton Name>/config

For example, the location of the log4j.properties for CM is:

on Windows: CONFIG_HOME\services\cm\config

on Linux: CONFIG_HOME/services/cm/config

Changing the Logging LevelThe logging levels available for PBS Works are:

Follow these instructions to change the logging behavior of PBS Works:

1. Edit the log4j.properties file.

2. Change the value of log4j.rootLogger to the appropriate logging level:

Table 3. PBS Works logging levels

Logging Level Description

OFF The highest possible ranking and is intended to turn off logging.FATAL Designates very severe error events that will presumably lead the application to abort.ERROR Designates error events that might still allow the application to continue running.WARN Designates potentially harmful situations.INFO Designates informational messages that highlight the progress of the application at

coarse-grained level.DEBUG Designates fine-grained informational events that are useful for debugging.TRACE Designates finer-grained informational events than the DEBUG.ALL Designates the lowest possible rank and is intended to turn on all logging.



log4j.rootLogger=INFO, frameworkRollingFile


Configuring Log File Size and Number of BackupsThe default value of maximum log file size and the number of backups is different for each of the applications that is installed.

By default, for CM application the maximum log file size is 10MB and the number of log files that are backed up is 30.

Follow these instructions to change the maximum log file size and the number of backups:

1. Edit the log4j.properties file and

2. Set the values of maxFileSize and maxBackupIndex:

log4j.appender.cmActivityLogAppender.maxFileSize=10MB

log4j.appender.cmActivityLogAppender.maxBackupIndex=30


Configuring Session TimeoutBy default, a PBS Works application session expires when the user has not requested or refreshed a page for 120 minutes (2 hours). The session timeout value is stored in the file platform.conf. The location of this file for a typical installation of PBS Works is:

on Windows: CONFIG_HOME\framework\config

on Linux: CONFIG_HOME/framework/config

Follow these instructions to change the session timeout value:

1. Edit the platform.conf file.

2. Change the value of sessiontimeout to the appropriate timeout value in minutes.

sessiontimeout=120




Configuring Language/LocalizationLocalization and language settings are stored in the platform.xml file. Currently, PBS Works sup-ports:

• English• Chinese

The location of this file for a typical installation of PBS Works is:

on Windows: CONFIG_HOME\framework\config

on Linux: CONFIG_HOME/framwork/config

Follow these instructions to change the session timeout value:

1. Edit the platform.xml.

2. Change the value of the <default> element to the proper language option. For example, to switch from a default of English to Chinese you would change <default>en_US</default> to <default>zh_CN</default>.


<locale>

<default>zh_CN</default>

<availableLocales>

<localename>en_US</localename>

<localename>ja_JP</localename>

<localename>zh_CN</localename>

</availableLocales>

</locale>



Configuring SSL SSL (Secure Sockets Layer) is a protocol that provides security for communications between client and server by implementing encrypted data and certificate-based authentication. The advantage of SSL is added security for your users. By default, communication over SSL is disabled. The follow-ing sections describe how to enable SSL.

Typically, the PBS Works service is installed and configured to use port 8086. If this port is not available during installation, then the PBS Works installer will increment the port number and try again. This will continue until a free port is found, or until 100 consecutive ports are refused at which point the installer will ask for a port. The following instructions assume that PBS Works is configured to use port 8086. If your installation of PBS Works is using a different port, then these instructions will need to be modified accordingly, that is, references to port 8086 must be changed to the correct port).

Follow these instructions to enable SSL:

1. Enter the following command at the Linux command line prompt to determine if the envi-ronment variable JAVA_HOME is set properly:

echo $JAVA_HOME

2. Set the value of JAVA_HOME to SERVER_HOME/thirdparty/java by entering the following command:

export JAVA_HOME=SERVER_HOME/thirdparty/java

3. A security certificate is necessary for SSL encryption. Two options are available for provid-ing a security certificate: - Creating a Tomcat Certificate Keystore File- Deploying a Customer Defined Certificate

4. There are two options for configuring SSL:- Configuring a Secure Open Port- Configuring a Secure Open Port with Redirection



Creating a Tomcat Certificate Keystore FileIn order to implement SSL, a web server must have an associated Certificate for each external interface (IP address) that accepts secure connections.

Follow these instructions to create a Tomcat Certificate keystore file:

1. Enter the following command at the Linux command line prompt to create the Certificate:

$JAVA_HOME/bin/keytool -keystore SERVER_HOME/thirdparty/apache/tomcat/conf/key-store -genkey -alias PBSWorks -keyalg RSA

2. When prompted, enter a keystore password. The default password used by Tomcat is "changeit" (all lower case), although a custom password can be provided. You will also need to specify the custom password in the server.xml configuration file, as described later.

3. When prompted, enter general information about this Certificate, such as company and contact name. This information will be displayed to users who attempt to access a PBS Works application, so make sure that the information provided here matches what they will expect.

4. When prompted, enter a key password, which is the password specifically for this Certifi-cate (as opposed to any other Certificates stored in the same keystore file). You MUST use the same password here as was used for the keystore password itself. This is a restriction of the Tomcat implementation. The keytool prompt will tell you that pressing the ENTER key does this for you automatically.)

If everything was successful, you now have a keystore file in the SERVER_HOME/thirdparty/apache/tomcat/conf directory with a Certificate that can be used by your server.



Deploying a Customer Defined CertificateYou may deploy an existing Certificate rather than creating a new Certificate. However, to deploy an existing Certificate you must have a working installation of the OpenSSL software and be able to execute openssl from the command line.

Follow these instructions to deploy a customer defined Certificate:

1. Convert the Certificate to a Distinguished Encoding Rules (DER) format using openssl by issuing the following command at the Linux command line prompt:

openssl pkcs8 -topk8 -nocrypt -in <input.crt> -inform PEM -out <output.crt> -out-form DER

where <input.crt> is the PEM certificate and <output.crt> is the end result of the conver-sion, a DER certificate.

2. Convert the key to a Distinguished Encoding Rules (DER) format using openssl by issuing the following command at the Linux command line prompt:

openssl x509 -in <input.key> -inform PEM -out <output.key> -outform DER

where <input.key> is the PEM key and <output.key> is the end result of the conversion, a DER key.

3. Import these files into the Java KeyStore by issuing the following command at the Linux command line prompt

$JAVA_HOME/bin/keytool -import -alias PBSWorks -keystore SERVER_HOME/thirdparty/apache/tomcat/conf/keystore -file <output.crt>


Configuring a Secure Open PortThis option enables secure access to PBS Works over port 8443. PBS Works runs as a normal user - pbsworksuser. The pbsworksuser does not have permission to use privileged ports (443), there-fore a non-privileged port (8443) is used. With this option, access to PBS Works is only available through port 8443, with no redirection from the default http port of 8086.

If you have enabled SSL using the Configuring a Secure Open Port with Redirection option, then please back out those changes prior to completing the following steps.

Follow these instructions to configure the secure public port (8443):

1. Edit the Tomcat server configuration file SERVER_HOME/thirdparty/apache/tomcat/conf/server.xml.

2. Comment out the following http connector:

<Connector connectionTimeout="20000" port="8086" protocol="HTTP/1.1" redirect-Port="8443"/>

After commenting out the http connector it should look like the following:

3. Paste the following block of XML:

The value of keystorePass should be set to the password specified during the creation of the keystore. Replace SERVER_HOME with the pathname to the PBS Works installation direc-tory.

After the following block of XML:



<Connector

port="8443" maxThreads="200"

scheme="https" secure="true" SSLEnabled="true"

keystoreFile="SERVER_HOME/thirdparty/apache/tomcat/conf/keystore" keystorePass="changeit"

clientAuth="false" sslProtocol="TLS"/>


4. Edit the CONFIG_HOME/AMS/AA/AA_Client.properties file to configure AMS to communi-cate with PBS Works over https:

Replace the following lines of the file:

with these lines:


The restart command will return this message:

PBSWorks started, pid: <PID>, port:8086 [OK]

Disregard the reference to port 8086 - this is a known issue. PBS Works will now be config-ured to use the secure https port 8443.

6. Navigate to https://<HOSTNAME>:8443/pbsworks using a supported web browser.

7. Accept the certificate when you are prompted by the browser.

8. Login to the PBS Works portal.

java.authWsdl=http://<hostname>:8086/AAService/AuthzUserPort?wsdl

java.authEndpoint=http://<hostname>:8086/AAService/AuthzUserPort

java.adminWsdl=http://<hostname>:8086/AAService/AuthzAdminModulePort?wsdl

java.adminEndpoint=http://<hostname>:8086/AAService/AuthzAdminModulePort

java.authnWsdl=http://<hostname>:8086/AAService/AuthNPort?wsdl

java.authnEndpoint=http://<hostname>:8086/AAService/AuthNPort

java.authWsdl=https://<hostname>:8443/AAService/AuthzUserPort?wsdl

java.authEndpoint=https://<hostname>:8443/AAService/AuthzUserPort

java.adminWsdl=https://<hostname>:8443/AAService/AuthzAdminModulePort?wsdl

java.adminEndpoint=https://<hostname>:8443/AAService/AuthzAdminModulePort

java.authnWsdl=https://<hostname>:8443/AAService/AuthNPort?wsdl

java.authnEndpoint=https://<hostname>:8443/AAService/AuthNPort



Configuring a Secure Open Port with RedirectionThis option enables secure access to PBS Works over port 8443, while keeping the http port 8086 open. With this option, users are redirected to the secure connection from the http port. PBS Works runs as a normal user - pbsworksuser. The pbsworksuser does not have permission to use privileged ports (443), therefore a non-privileged port (8443) is used.

If you have enabled SSL using the Configuring a Secure Open Port option, then please back out those changes prior to completing the following steps:

Follow these instructions to configure the secure public port (8443):

1. Edit the Tomcat server configuration file SERVER_HOME/thirdparty/apache/tomcat/conf/server.xml.

2. Paste the following block of XML:

3. After the following XML:

The value of keystorePass should be set to the password specified during the creation of the keystore. Replace SERVER_HOME with the pathname to the PBS Works installation direc-tory.

4. Edit the SERVER_HOME/binaries/framework/webapps/pbsworks/WEB-INF/web.xml file to set up redirection from http://HOSTNAME:8086/pbsworks to https://HOSTNAME:8443/pbsworks.

<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150"

scheme="https" secure="true"

clientAuth="false" sslProtocol="TLS"

keystoreFile="SERVER_HOME/thirdparty/apache/tomcat/conf/keystore" keyAlias="PBSWorks" keystorePass="changeit" />




5. Paste the following block of code:

After the following block of XML:


The restart command will return this message:

PBSWorks started, pid: <PID>, port:8086 [OK]

Disregard the reference to port 8086 - this is a known issue. PBS Works will now be config-ured to use the secure https port 8443.

7. Navigate to https://<HOSTNAME>:8443/pbsworks using a supported web browser.

8. Accept the certificate when you are prompted by the browser.

9. Login to the PBS Works portal through either of the following URLs:- https://<HOSTNAME>:8443/pbsworks - logs in through the secured connection- http://<HOSTNAME>:8086/pbsworks - redirects the user to the secure connection

Enabling Single Sign-OnSingle Sign-On (SSO) for the application allows the users to log in using their domain credentials, i.e., the username and password that they use to login to their client system.

To ensure SSO is enabled successfully, review the Prerequisites for Single Sign-On on page 31.

Follow the steps to enable SSO:1. Verify if SPN is registered using the steps mentioned in SPN Verfication before you enable

SSO.

<security-constraint>

<web-resource-collection>

<web-resource-name>Altair PBSWorks</web-resource-name>

<url-pattern>/*</url-pattern>

</web-resource-collection>

<user-data-constraint>

<transport-guarantee>CONFIDENTIAL</transport-guarantee>

</user-data-constraint>

</security-constraint>

<session-config>

<session-timeout>120</session-timeout>

</session-config>



2. Edit the platform.xml located in the directory:on Windows: CONFIG_HOME\framework\configon Linux: CONFIG_HOME/framework/config

3. Change the SSO value to true.<sso>false<sso>

By default, the SSO option is set to False.

4. Edit the Krb5.conf file located in the directory CONFIG_HOME\AMS\AAServiceHome\config.Replace the $ALTAIR_SPM_SSO_DOMAIN$ with the domain name against which the users must be authenticated in the server.

To find the domain name of the server in Windows: i. Right-click on My Computer and select Properties.The following is an example of the domain name of the computer:

To find the domain name of the server in Linux: i. At the Linux command prompt enter: dnsdomainsname

5. Edit the web.xml file location in the directory CONFIG_HOME\framework\tomcat\conf\spnegoUpdate the key spnego.preauth.username with value of userid used for SPN registration. For SPN registration refer to SPN Registration.

6. Update the key spnego.preauth.password with value of the above user password.

7. Execute the following steps in Windows:i. At the Windows command line prompt, navigate to SERVER_HOME\scripts

If you enable SSO, then Auto Register and Use CM Credential options will be disabled.

Enter the values in the uppercase.

To configure client browsers, refer to Configuring Client Browser for SSO.



ii. Enter PBSWorksService removeiii. Enter PBSWorksService installiv. Enter PBSWorksService.bat start


Disabling Single Sign-OnFollow the steps to disable Single Sign-On:

1. Edit the platform.xml located in the directory:on Windows: CONFIG_HOME\framework\configon Linux: CONFIG_HOME/framework/config

2. Change the SSO value to false.<sso>true<sso>

3. Execute the following steps in Windows:i. At the Windows command line prompt, navigate to SERVER_HOME\scriptsii. Enter PBSWorksService removeiii. Enter PBSWorksService installiv. Enter PBSWorksService.bat start


SPN VerficationThe PBS Works installer provides a batch file to verify SPN registration. The VerifySPN batch file is located at SERVER_HOME\scripts\

To verify SPN registration, perform the following steps:1. At the Windows command line, navigate to SERVER_HOME\scripts\2. Enter VerifySPN.bat <Host Name of the Server>



The following is an example of the message that is displayed:

In the above example tr-lap471 is the host name of the server.

To verify the SPN registration in Linux server, execute the VerifySPN.bat command on any domain connected to windows host by passing the hostname of the Linux server.

During Windows installation, if you enable SSO then SPN registration is verified by the installer automatically using the batch file.



PBS Works Configuration FilesThe files in the table below can be modified to customize PBS Works. These files are located in the PBS Works installation directory. By default, PBS Works products are installed in the following directory.

on Windows: <INSTALL_DIR> is C:\altair\pbsworks\13.2

on Linux: <INSTALL_DIR> is /opt/altair/pbsworks/13.2

Two main directory structures CONFIG_HOME and SERVER_HOME are created during installation. For more information see Software Organization on page 11.

Table 5. PBS Works Configuration Files

File Name CustomizationCONFIG_HOME/AMS/AAServiceHome/config/AA_-jaas.configCONFIG_HOME/AMS/AAServiceHome/config/AA_-jaas.config.sshCONFIG_HOME/AMS/AAServiceHome/config/AA_-jaas.config.winCONFIG_HOME/AMS/AAServiceHome/config/AA_-jaas.config.dsCONFIG_HOME/AMS/AAServiceHome/config/Datstore/Datastore.properties.CONFIG_HOME/AMS/AAServiceHome/config/AA_-jaas.config.nisCONFIG_HOME/AMS/AAServiceHome/config/AA_-jaas.config.pam

Changing the Authentication Method

SERVER_HOME/services/cm/config/spring-con-fig.xml

• Changing the Postgres Database• Changing the Database Password

CONFIG_HOME\services\<Application Name>\config Changing the PBS Works Logging Behavior

CONFIG_HOME/config/platform.xml • Configuring Language/Localization• Enabling Single Sign-On• Disabling Single Sign-On

SERVER_HOME/thirdparty/apache/tomcat/conf/server.xml

Configuring SSL

CONFIG_HOME/config/platform.conf Configuring Session Timeout



on Windows: SERVER_HOME\scripts\PBSWorksSer-vice.bat on Linux: SERVER_HOME/scripts/server-start.sh

Improving File Operations Perfor-mance

on Windows: SERVER_HOME\scripts\PBSWorksSer-vice.bat on Linux: SERVER_HOME/scripts/server-start.sh

Improving JVM Performance

SERVER_HOME\scripts\VerifySPN.bat SPN Verfication

Table 5. PBS Works Configuration Files

File Name Customization


9. Troubleshooting

Single Sign-On (SSO) ErrorsThe following section provides the list of SSO errors with the possible causes and the resolution.

Summary: GSSException: Failure unspecified at GSS-API level (Mechanism level: Checksum failed) with root cause java.security.GeneralSecurityException: Checksum failed

Possible Causes: • SPN not registered properly• Incorrect user credentials in web.xml

Resolution: • Use the tool to verify SPN. For more information on the tool see SPN Verfication on

page 103.• Check for a miss-typed password or wrong password in web.xml.

Summary: Pop up on browser asking for user credentials

Possible Causes: • The client and server not on same domain• The browser is not configured for Single Sign-On • The browser configured for SSO but the hostname of the server could be wrong or mis-

typed• Non-Domain user might be logged into client machine who is trying to access the

PBSWorks • Browser in private browsing mode

Resolution: • Enter the domain user credentials on the pop up window• Configure browser for SSO. Refer section Prerequisites for Single Sign-On on page 31 to

configure browser

107


• Check for a miss-typed hostname while configuring SSO on browser• Enter the domain user credentials on the pop up window• Use the application in normal mode or if user likes to continue in private browsing then

provide the username and password once

Summary: Pop up on browser asking for user credentials again and again even after providing valid credentials

Possible Cause:• Domain value krb5.conf file is not in uppercase

Troubleshoot:• Change the domain values in krb5.conf file to UPPERCASE. This is a known issue (AMS-

232).

Summary: On Linux logging in as non-domain user (root) on same client and server

Possible Causes: • Property spnego.allow.localhost set to true in web.xml

Resolution: • Change the property spnego.allow.localhost to false in web.xml at location

SERVER_HOME\thirdparty\apache\tomcat\conf

Summary: Cannot get kdc for realm

Possible Causes: • Domain name configured in krb5.conf could be wrong

Resolution: • Check [libdefaults] and [realms] section of krb5.conf for domain name typos

108 Troubleshooting


Summary: javax.security.auth.login.LoginException: null (68)

Possible Causes: • Domain name configured in krb5.conf could be wrong

Resolution: • Check [libdefaults] and [realms] section of krb5.conf for domain name typos

Summary: Windows 2012 issue firewall settings

Possible Causes: • Windows firewall is enabled on server machine and not allowing to access portal outside

on other machines

Resolution: • Disable firewall on Server machine.• Add Exception in firewall on server machine.

Troubleshooting 109


110 Troubleshooting

Glossary

Account. An account is an arbitrary character string, which may have meaning to one or more hosts in the batch system. Frequently, an account is used as a grouping for charging for the use of resources.

Accounting Log. The PBS Professional accounting log is a text file containing information about a cluster's HPC job activity.

Administrator. A person who administers a product (CM, DM, RVS, PAS, PBSA, or PBS), per-forming functions such as downloading, installing, upgrading, configuring, or managing the product. Administrator is distinguished from "site administrator", although often these are the same person.

Access Management Service, AMS. A centralized configuration system for authentication and authorization.

Application Definition. A predefined set of instructions to describe your application parameters to users, store their responses, and prepare those responses for job execution via PBS Professional. An application definition provides a flexible set of instructions that can be manipulated to allow for precise control over all aspects of application-specific parameters and job execution.

Chart. A charts is a visual representation of data. Charts are used to ease understanding of large quantities of data and the relationships between parts of the data.

Cluster. A relatively homogeneous set of systems that are used as if they are a single machine.

Commands, PBSA Commands, PAS Commands. A set of command-line commands. PBSA Commands are commands that assist with the configuration of PBSA. PAS Commands provide job submission, monitoring, as well as file operations capabilities from the command-line.

Complex. A PBS complex consists of the machines running one primary server+Scheduler (plus, optionally, a secondary backup server+Scheduler) and all the machines on which the MoMs (attached to this server+Scheduler) are running. A complex can be a heterogeneous mix of system architectures, and can include one or more clusters.

Consumable resource. A consumable resource is a resource that is reduced or taken up by being used. Examples of consumable resources are memory or CPUs.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

111


CPU. Has two meanings, one from a hardware viewpoint, and one from a software viewpoint: • A core. The part of a processor that carries out computational tasks. Some systems present

virtual cores, for example in hyperthreading.• Resource required to execute a program thread. PBS schedules jobs according, in part, to

the number of threads, giving each thread a core on which to execute. The resource used by PBS to track CPUs is called "ncpus". The number of CPUs available for use defaults to the number of cores reported by the OS. When a job requests one CPU, it is requesting one core on which to run.

Custom group. Custom groups are specific to PBS Analytics, and are an alternative for tracking usage of HPC resources at a project level for sites running versions of PBS Professional prior to 11.2.

Custom resource. A resource that is not defined in PBS as shipped. Custom resources are created by the PBS administrator or by PBS for some systems.

Daily Parsing. A PBSA activity where information from the PBS Professional accounting logs is parsed, and then loaded into a database. Once the PBS Professional accounting logs have been parsed for the first time (see Initial Parsing), daily parsing is scheduled by default to occur at 1:00 am, and will parse any newly generated accounting logs.

Dashboard. A dashboard is a visual display of the most important information needed to achieve one or more objectives; consolidated and arranged on a single screen so the information can be monitored at a glance.

Dimension. A field or variable that is displayed on a PBSA chart. Dimensions are the independent variable (often denoted by the x-axis) whose variation does not depend on another variable. Examples are users, software, servers, and nodes. PBSA requires that Dimensions be displayed on the x-axis or z-axis (in the case of a three dimensional chart).

Demonstration Database. A database that is loaded with demonstration data. An installation option is available that installs PBSA with a demonstration database, so that all out-of-the box charts, dashboards, and slideshows can be viewed, and all key features of PBSA can be accessed and evaluated.

Execution host. A computer which runs PBS jobs. An execution host is a system with a single operating system (OS) image, a unified virtual memory space, one or more CPUs and one or more IP addresses. Systems like Linux clusters, which contain separate computational units each with their own OS, are collections of hosts. Systems such as the SGI ICE are also collections of hosts. The SGI Altix 4700 is a single execution host.

112 Glossary of Terms


An execution host can be comprised of one or more vnodes. For example, the SGI Altix 4700, while being a single execution host, can contain multiple vnodes, where each vnode is a blade. On the SGI ICE, each blade is treated as a vnode. See Vnode.

File Service Provider, FSP. A PAS mechanism for executing remote file operations on the PBS Professional execution hosts. It removes the dependency upon PBS Professional for remote file operations and file transfers.

Finished Jobs. Jobs whose execution is done, for any reason:• Jobs which finished execution successfully and exited • Jobs terminated by PBS while running • Jobs whose execution failed because of system or network failure • Jobs which were deleted before they could start execution

Fully Qualified Domain Name, FQDN. The complete domain name for a specific computer, or host, on the Internet. The FQDN consists of two parts: the hostname and the domain name.

Furnishing Server. The server from which the job is pulled when peer scheduling is implemented.

Group. A collection of system users. A user must be a member of at least one group, and can be a member of more than one group.

Head Node. Machine where the PBS Server is installed.

High Performance Computing, HPC. High Performance Computing (HPC) most generally refers to the practice of aggregating computing power in a way that delivers much higher perfor-mance than one could get out of a typical desktop computer or workstation in order to solve large problems in science, engineering, or business.

Holiday. A non-working day usually associated with a special day of celebration.

Host. A machine running an operating system. A host can be made up of one or more vnodes.

Initial Parsing. A PBSA activity where information from the PBS Professional accounting logs is parsed, and then loaded into a database. Initial parsing is when the accounting logs are parsed for the first time after installation and configuration of PBSA is complete. Initial parsing may take anywhere from several hours to several days depending upon the amount of data stored in the PBS Professional accounting log(s), number of processors, and amount of available RAM.

Job or Batch job. A unit of work managed by PBS. A job is a related set of tasks, created and sub-mitted by the user. The user specifies the resources required by the job, and the processes that make up the job. When the user submits a job to PBS, the user is handing off these tasks to PBS to

Glossary of Terms 113


manage. PBS then schedules the job to be run, and manages the running of the job, treating the tasks as parts of a whole. A job is usually composed of a set of directives and a shell script.

Job ID, Job identifier. When a job is successfully submitted to PBS, PBS returns a unique identi-fier for the job. Format: sequence_number[.server][@new server]

Job State. A job exists in one of the possible states throughout its existence within the PBS system. For example, a job can be queued, running, or exiting.

License Server. A centralized computer software system which provides access tokens, or keys, to client computers in order to enable licensed software to run on them.

Measure. A field or variable that is displayed on a PBSA chart. Measures are the dependent vari-able (often denoted by the y-axis) whose value changes dependent on the other variables. Exam-ples are total numbers of jobs, average memory used, and total CPU walltime. Measures are displayed on the y-axis. The PBSA Web Application refers to Measures as Values.

MoM. The daemon which runs on an execution host, managing the jobs on that host. MoM is the informal name for the process called pbs_mom. One MoM runs on each execution host.

MoM runs each job when it receives a copy of the job from the server. MoM creates a new session that is as identical to the user's login session as possible. For example under UNIX, if the user's login shell is csh, then MoM creates a session in which .login is run as well as .cshrc. MoM returns the job's output to the user when directed to do so by the server.

MoM is a reverse-engineered acronym that stands for "Machine Oriented Mini-server".

Mother Superior. Mother Superior is the MoM on the head or first host of a multihost job. Mother Superior controls the job, communicates with the server, and controls and consolidates resource usage information. When a job is to run on more than one execution host, the job is sent to the MoM on the primary execution host, which then starts the job.

Node. No longer used. See Execution Host.

Nodeclass. A custom resource that groups or classifies PBS Professional nodes. PBSA automati-cally assign a nodeclass based on cores and memory when node information is added to PBSA via the pbsa-config-nodes command.

Node Details. A map of your site's PBS Professional cluster, that is each PBS Professional server and its associated execution hosts. This information is stored in a configuration file, and is used by PBSA to provide HPC resource usage statistics.

Non-consumable resource. A non-consumable resource is a resource that is not reduced or taken up by being used. Examples of non-consumable resources are Boolean resources and walltime.



Non-Prime Time Hours. Non-working hours.

Owner, Job owner. The user who submitted a specific job to PBS.

Parsing. A PBSA activity where information from the PBS Professional accounting logs is parsed, and then loaded into a database.

PAS_EXEC.The path containing PAS executables. The path under which PAS executables are installed on the local system. The location of this directory is platform dependent.

PAS_HOME. The path containing PAS configuration and log files. The path under which PAS configuration and log files are installed on the local system. The location of this directory is plat-form dependent.

PBS Analytics, PBSA. A job accounting and reporting solution that provides PBS Works adminis-trators with advanced analytics to support data-driven planning and decision making. Data from multiple PBS Professional servers can be consolidated, providing a global view of your HPC usage for chargeback, capacity planning, troubleshooting and project management.

PBS Application Services, PAS. A middleware component that communicates with the PBS Pro-fessional complex and the operating system, and provides services for the front end client applica-tions such as graphical user interfaces.

PBS Professional. A workload management system consisting of a server, a Scheduler, and any number of execution hosts each managed by a MoM. PBS accepts batch jobs from users, and schedules them on execution hosts according to the policy chosen by the site. PBS manages the jobs and their output according to site-specified policy.

PBS Works. PBS Works is a suite of products for comprehensive, secure workload management for high-performance computing (HPC) environments.

PBS_EXEC. The path containing PBS executables. The path under which PBS executables are installed on the local system.

PBS_HOME. The path containing PBS files. The path under which PBS files are installed on the local system.

PBSA Data Collector, Data Collector. A software component of PBSA, installed on execution hosts, responsible for making the PBS Professional accounting logs accessible to the PBSA engine.

PBSA Engine, PBSA Web Application. A software component of PBSA that consists of web ser-vices, a database, and an analytics engine responsible for the analysis and visualization of HPC resources.



PBSA Hook. A mechanism for adding a custom resource to PBSA.

PBSA Parser, Parser. A software component of PBSA that is responsible for parsing the PBS Pro-fessional accounting logs and loading this information into the PBSA database.

PBSWORKS_EXEC. The path containing PBS Works executables. The path under which PBS Works executables are installed on the local system. The location of this directory is platform dependent.

PBSWORKS_HOME. The path containing PBS Works configuration and log files. The path under which PBS Works configuration and log files are installed on the local system. The location of this directory is platform dependent.

Peer scheduling. A feature allowing different PBS complexes to automatically run each others' jobs. This way jobs can be dynamically load-balanced across the complexes. Each complex involved in peer scheduling is called a peer.

Prime Time Hours. Working hours.

Project. In PBS, a project is a way to group jobs independently of users and groups. A project is a tag that identifies a set of jobs. Each job's project attribute specifies the job's project.

Queue. A queue is a named container for jobs at a server. There are two types of queues in PBS: routing queues and execution queues. A routing queue is a queue used to move jobs to other queues including those that exist on other PBS servers. A job must reside in an execution queue to be eligible to run and remains in an execution queue during the time it is running. In spite of the name, jobs in a queue need not be processed in queue order (first-come first-served or FIFO).

Resource. A resource can be something used by a job, such as CPUs, memory, high-speed switches, scratch space, licenses, or time, or it can be an arbitrary item defined for another pur-pose. PBS has built-in resources, and allows custom-defined resources.

Scheduler. The PBS scheduler is the daemon which implements the site's job scheduling policy controlling when and where each job is run. The scheduler is the process called pbs_sched.

Scheduling. The process of selecting which jobs to run when and where, according to a predeter-mined policy. Sites balance competing needs and goals on the system(s) to maximize efficient use of resources (both computer time and people time).

Server. The central PBS daemon, which does the following:• Handles PBS commands • Receives and creates batch jobs• Sends jobs for execution



The server is the process called pbs_server. Each PBS complex has one primary server, and if the complex is configured for failover, a secondary server. The server contains a licensing client which communicates with the licensing server for licensing PBS jobs.

Server Configuration File. A file containing all configurable parameters available with PAS.

Service User. Windows platforms only. The user under which the CM or PAS Windows service is registered.

Site Configuration File. A central repository for site specific information that can be used across all application definitions.

User. Has two meanings:• A person who submits jobs to PBS, as differentiated from Operators, Managers and

administrators.• A system user, identified by a unique character string (the user name) and by a unique

number (the user ID). Any person using the system has a username and user ID.

User ID, UID. A unique numeric identifier assigned to each user.

Values. The PBSA Web Application refers to Measures as Values. Values are the dependent vari-able (often denoted by the y-axis) whose value changes dependent on the other variables. Exam-ples are total numbers of jobs, average memory used, and total CPU walltime. Values are displayed on the y-axis.

Vnode. A virtual node, or vnode, is an abstract object representing a set of resources which form a usable part of an execution host. This could be an entire host, or a nodeboard or a blade. A single host can be made up of multiple vnodes. Each vnode can be managed and scheduled inde-pendently. Each vnode in a complex must have a unique name. Vnodes can share resources, such as node-locked licenses.


PBS Works Admin Guide€¦ · PBS Works 13.2 Administrator’s Guide ii ... OptiStruct®...

Documents

Transcript of PBS Works Admin Guide€¦ · PBS Works 13.2 Administrator’s Guide ii ... OptiStruct®...