pbs application services 13.0 administrator’s...

PBS Works is a division of

PBS Application Services 13.0

Administrator’s Guide

PBS Application Services 13.0 Administrator’s Guide

Updated: September 24, 2015.

Intellectual Property Rights Notice:

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

Altair® PBS Works™

Enabling On-Demand Computing™

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

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

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

Other Altair software applications include:

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

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

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

Altair intellectual property rights are protected under U.S. and international laws and treaties. Additionally, Altair software is protected under patent #6,859,792 and other patents pending. All other marks are the property of their respective owners.ALTAIR ENGINEERING INC. Proprietary and Confidential. Contains Trade Secret Information. Not for use or disclosure

Chapter 1

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 Licenses

Software Security Measures:

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

PBS Application Services Administrator’s Guide iii

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

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

Chapter 1

Technical Support

Table 1-1: Technical Support Contact Information

Location Telephone Email

Australia +1 800 174 396 [email protected]

China +86 21 6117 1666 [email protected]

France +33 1 4133 0992 [email protected]

Germany +49 7031 6208 22 [email protected]

India +91 80 66 29 4500 +1 800 425 0234 (Toll Free)

[email protected]

Italy +39 800 905595 [email protected]

Japan +81 3 5396 2881 [email protected]

Korea +82 70 4050 9200 [email protected]

Malaysia +91 80 66 29 4500 +1 800 425 0234 (Toll Free)

[email protected]

North America +1 248 614 2425 [email protected]

Russia +49 7031 6208 22 [email protected]

Scandinavia +46 46 460 2828 [email protected]

Singapore +91 80 66 29 4500 +1 800 425 0234 (Toll Free)

[email protected]

South America +55 11 3884 0414 [email protected]

UK +44 1926 468 600 [email protected]

iv PBS Application Services Administrator’s Guide

Table of Contents

1 PBS Application Services 11.1 Integration Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2.1 Supported Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.3.1 Minimum Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3.2 Minimum Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.3 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.4 Assumptions, Constraints, and Dependencies . . . . . . . . . . . . . . . . . . . . . . . 5

1.4 Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.5 Software Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.5.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.5.2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Pre-installation Planning 152.1 Upgrading from a previous release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 PBS Application Services default port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3 PBS Application Services staging directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.4 Access Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.5 SSL Communication with a Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.6 Installing PAS on a Separate Machine from the PBS Server . . . . . . . . . . . . . . 182.7 File Transfer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 Installing PAS GUI mode 213.1 Installing PBS Application Services and PAS Commands . . . . . . . . . . . . . . . . 22

3.1.1 Starting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.1.2 PBS Application Services installation instructions . . . . . . . . . . . . . . . . . . 233.1.3 License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.4 Install options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.1.5 PAS service user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

PBS Application Services Administrator’s Guide v

Table of Contents

3.1.6 PAS service user password - Windows only . . . . . . . . . . . . . . . . . . . . . . . 273.1.7 Staging directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.1.8 License server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.1.9 Installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.1.10 Pre-installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.1.11 Installation progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.1.12 Start PAS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.1.13 PAS client validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.1.14 Installation complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.1.15 Post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.2 Installing PAS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.2.1 Starting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.2.2 PAS Commands installation instructions . . . . . . . . . . . . . . . . . . . . . . . . . . 383.2.3 License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.2.4 Install options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.2.5 PAS server hostname/IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.2.6 Installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.2.7 Pre-installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.2.8 Installation progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.2.9 Installation complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.2.10 Post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4 Installing PAS console mode 474.1 Installing PBS Application Services and PAS Commands . . . . . . . . . . . . . . . . 48

4.1.1 Starting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.1.2 PBS Application Services installation instructions . . . . . . . . . . . . . . . . . . 494.1.3 License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.1.4 Install options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.1.5 PAS service user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.1.6 Staging directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.1.7 License server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.1.8 Installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.1.9 Pre-installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.1.10 Start PAS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.1.11 PAS client validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.1.12 Installation complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.1.13 Post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4.2 Installing PAS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.2.1 Starting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.2.2 PBS Application Services installation instructions . . . . . . . . . . . . . . . . . . 564.2.3 License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

vi PBS Application Services Administrator’s Guide

Table of Contents

4.2.4 Install options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.2.5 PAS server hostname/IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.2.6 PAS server port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.2.7 Installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.2.8 Pre-installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.2.9 Installation complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.2.10 Post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

5 Post-installation 615.1 Features and configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5.1.1 Application definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.1.2 Site configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.1.3 Server configuration file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.1.4 PAS configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.2 Installing PAS for the first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.2.1 Configure PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.2.2 Restart PAS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.3 Upgrading from a previous release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.3.1 Migrate application definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.3.2 Migrate site configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.3.3 Migrate server configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.3.4 Restart the PAS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.4 Updating search path for PAS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.5 Enabling job history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.6 Setting environment variable PAS_CONF_FILE . . . . . . . . . . . . . . . . . . . . . . . 655.7 Configuring SSL for communication with PAS Commands . . . . . . . . . . . . . . 665.8 Configuring password-less authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.9 Configuring PBS resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.10 Configuring the File Service Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.11 Verifying the installation of PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6 Configuring PBS Application Services 736.1 Configurable parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6.1.1 Standard configuration parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746.1.2 Advanced Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

6.2 Configuring PAS Server logging behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806.2.1 Remote file operations, job submission, and job status . . . . . . . . . . . . . . . 816.2.2 File upload/download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826.2.3 File operations (local and remote) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826.2.4 Job submission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826.2.5 Job submission and status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

PBS Application Services Administrator’s Guide vii

Table of Contents

6.2.6 License checkout by PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.2.7 Applications (application definitions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.2.8 Dynamic Application Refresh Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.2.9 Metascheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6.3 Configuring PAS Commands logging behavior . . . . . . . . . . . . . . . . . . . . . . . . 856.3.1 Maximum log file size and rollover policy . . . . . . . . . . . . . . . . . . . . . . . . 86

6.4 Changing the Linux SSH Server or Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876.5 Configuring JVM Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7 Log files 897.1 PAS log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.2 PAS Commands log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.3 FSP file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907.4 Other log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

8 PAS service commands 918.1 Starting the PAS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8.1.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918.1.2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8.2 Stopping the PAS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928.2.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928.2.2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

8.3 Restarting the PAS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938.3.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938.3.2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

8.4 Determining the status of the PAS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948.4.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948.4.2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

9 Application Definitions 959.1 Overview of Application Definition Components . . . . . . . . . . . . . . . . . . . . . . 95

9.1.1 Application input file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969.1.2 Application converter file (HPCBP converter) . . . . . . . . . . . . . . . . . . . . . 969.1.3 Application runtime scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969.1.4 Site configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

9.2 Sample application definition PBSJobApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979.3 Administration of Application Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

9.3.1 Adding a new application definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989.3.2 Application definition validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989.3.3 Maintenance of existing application definitions. . . . . . . . . . . . . . . . . . . . . 98

9.4 Sitewide Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

viii PBS Application Services Administrator’s Guide

Chapter 1

9.4.1 Site configuration file content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009.4.2 Using site configuration information in an application definition . . . . . . 1039.4.3 Site configuration file backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039.4.4 Site configuration file validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

10 Reserved words 105

11 Uninstalling PAS GUI mode 10711.1 Starting the uninstaller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

11.1.1 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10711.1.2 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

11.2 Initiate the PAS uninstall process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10811.3 Uninstall PBS Application Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10911.4 Complete uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

12 Uninstalling PAS console mode 11112.1 Starting the uninstaller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11112.2 Initiate the PAS uninstall process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11212.3 Complete uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

PBS Application Services Administrator’s Guide ix

Chapter 1

13 Troubleshooting 11313.1 The package doesn’t match the OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11313.2 PBS Professional Server is not installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11313.3 Incompatible version of PBS Professional detected . . . . . . . . . . . . . . . . . . . . 11413.4 Staging Directory is blank. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11513.5 Could not detect “userid” (Linux/Unix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11513.6 Could not connect Windows AD/DNS Server (Windows) . . . . . . . . . . . . . . . 11513.7 Specified service user name does not exist (Windows) . . . . . . . . . . . . . . . . . 11613.8 Password is required to continue (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . 11613.9 PBS Professional installation appears to be incomplete . . . . . . . . . . . . . . . . . 11613.10 EIFL server ports in the default range is not available . . . . . . . . . . . . . . . . . . 11613.11 PAS server port is not free for installing PAS service . . . . . . . . . . . . . . . . . . 11713.12 Specified port # is not a valid value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11713.13 The PAS server IP/port number is blank. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11713.14 PAS Service was unable to start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11713.15 PAS Service was unable to install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11813.16 Installer not running as root/admin user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11813.17 Existing instance of Python found (Windows) . . . . . . . . . . . . . . . . . . . . . . . . 11813.18 License server information not provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11813.19 Manage Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11913.20 Out of Memory Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12113.21 IOException: No such file or directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12113.22 Job Fails with “Bad UID” exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12213.23 Job Fails with “Unknown Resource” exception . . . . . . . . . . . . . . . . . . . . . . . 12213.24 PAS Command connection error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

14 File Service Provider 12514.1 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12614.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

14.2.1 Minimum Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12614.3 Installation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12714.4 Integration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12714.5 Software Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

14.5.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12814.5.2 Linux/Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

14.6 FSP configurable parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13014.7 Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13114.8 Configuring FSP Server logging behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . 13214.9 Starting the FSP service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

14.9.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

x PBS Application Services Administrator’s Guide

Chapter 1

14.9.2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13314.10 Stopping the FSP service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

14.10.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13414.10.2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

14.11 Restarting the FSP service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13514.11.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13514.11.2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

14.12 Determining the status of the PAS service . . . . . . . . . . . . . . . . . . . . . . . . . . . 13614.12.1 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13614.12.2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

15 Installing FSP GUI mode 13715.1 Starting the installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13715.2 FSP installation instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13815.3 License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13915.4 FSP service user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14015.5 FSP service user password - Windows only . . . . . . . . . . . . . . . . . . . . . . . . . . 14115.6 Authentication and Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14215.7 Installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14315.8 Pre-installation summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14415.9 Installation progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14515.10 Start FSP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14615.11 FSP client validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14615.12 Installation complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14715.13 Post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

16 Installing FSP console mode 14916.1 Starting the installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14916.2 FSP installation instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15016.3 License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15016.4 FSP service user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15116.5 Authentication and Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15216.6 Installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15216.7 Pre-installation summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15316.8 Start FSP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15316.9 FSP client validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15416.10 Installation complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15416.11 Post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

17 Uninstalling FSP GUI mode 15517.1 Starting the uninstaller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

PBS Application Services Administrator’s Guide xi

Chapter 1

17.1.1 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15517.1.2 Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

17.2 Initiate the FSP uninstall process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15617.3 Uninstall FSP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15717.4 Complete uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

18 Uninstalling FSP console mode 15918.1 Starting the uninstaller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15918.2 Initiate the FSP uninstall process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16018.3 Complete uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Index 161

xii PBS Application Services Administrator’s Guide

Chapter 1

PBS Application ServicesToday, doing more with less is simply business as usual. Enterprises and institutions are plac-ing higher demands upon their high performance computing infrastructure – larger and more complex applications and dynamic end-user work loads. Optimizing end-user productivity and getting the most from limited resources and complex application work loads can seem to be an impossible challenge.

PBS Application Services (PAS) is a middleware component that communicates with the PBS Professional complex and the operating system, and provides services for the front end client applications such as graphical user interfaces. This middleware component is used as the pre-ferred method of communication between the integration of client applications and the PBS Professional complex. PBS Application Services allows users to quickly create application portals that boost productivity and accelerate innovation. Application administrators can use PBS Application Services to create custom, solver specific application definitions. Leverag-ing key industry standards like the Open Grid Forum High Performance Computing Basic Profile, PBS Application Services makes it easy to respond to dynamic changes to your users and applications.

Benefits of PBS Application Services:

• Stable WS-based application programming interface (API) for integration into bigger systems

• Streamlined APIs for integration of applications into PBS Professional for the indepen-dent software vendors

• Front end graphical user interface application building is made easier

• Independent software vendors and the community can define new application definitions and exchange them within the PBS Professional complex in a turn-key fashion

• Platform neutrality allowing PBS Application Services to run on Windows and Linux

PBS Application Services Administrator’s Guide 1

Chapter 1 PBS Application Services

platforms

• Customized application definition files can be shared across all supported platforms

• Transactional manner of operations (e.g. eliminates out of sync issues with resources not included in scheduling, etc.)

• Grid-friendly as it uses the same extensible markup language/web services (XML/WS) as large-scale grid solutions

• Easier integration into Enterprise SOA and business process management

• Standards-based implementation using Web Services, WS-Security, high performance computing basic profile (HPCBP)

PBS Application Services provides the following major groups of functionality:

• Installation and management of application definitions by administrators

• Site configuration such as billing accounts and MPROC by administrators

• User submission and management of PBS Professional jobs

• File operations services

1.1 Integration Architecture

Web Services (WS) are used as the underlying technology for communication between PBS Application Services and the front end client applications. The PBS Application Services component exposes all functionality supported by PBS Professional and is a neutral interface for the client applications to easily integrate with the PBS Professional complex.

PBS Application Services provides an integration layer built upon the service oriented archi-tecture (SOA) for easy integration of end user applications with the PBS Professional com-plex.

Client applications have access to PBS Application Services through the following ports:

Administration WS Port

• Administration of applications scheduled by PBS Professional

• Site configuration

• Application licensing management

2 PBS Application Services Administrator’s Guide

PBS Application Services Chapter 1

Application Job WS Port

• Application job submission, monitoring, and management

• Authentication and identity management

• Data management and staging

• Custom actions

HPCBP Job WS Port

• HPCBP job submission, monitoring, and management

• Ability to check attributes of BES container

File Operations WS Port

• Basic file operations

• File operations for running jobs, and expand options for staging user files

Figure 1-1:High Level Overview of PBS Application Services



1.2 Supported Platforms

The PBS Application Services Server is supported on the following platforms:

• Novell SUSE Linux Enterprise Server (SLES) 10.X, 11.X, and 12.x on x86_64

• Red Hat Enterprise Linux (RHEL) 5, 6, and 7 (server and desktop) on x86_64

• Windows Server 2008 on x86_64

• Windows Server 2008 R2 on x86_64


• CentOS 6 and 7 on x86_64

1.2.1 Supported Configuration

With versions of PAS prior to 13.0, the PBS Application Services Server and the PBS Profes-sional Server were required to be installed on the same host for job submission and monitor-ing.

With PAS 13.0, the PBS Application Services server and the PBS Professional Client are required to be installed on the same host for job submission and monitoring. In other words, the PAS server and the PBS Pro server can be located on different hosts. For further details see section 2.6, “Installing PAS on a Separate Machine from the PBS Server”, on page 18.

1.3 System Requirements

1.3.1 Minimum Hardware Requirements

Table 1-1: Minimum hardware rqmts

Hardware Requirement

CPU 1

Memory (Physical) 1 GB

Disk Space 2.8 GB



1.3.2 Minimum Software Requirements

To take full advantage of all the new features available with PBS Works 13.0, the cluster must be updated to PBS Professional 13.0, and PBS Application Services, Compute Manager, and Display Manager must be upgraded to 13.0.

It is not recommended but possible to run Compute and Display Manager 13.0.0 together with older versions of PAS and PBS Professional. However, certain features may not work or may show a degradation in performance and functionality. The currently supported versions are:

• Compute/Display Manager 12.x, 13.x

• PAS 12.x, 13.x

• PBS 12.x

On Linux systems, the Open SSH daemon using the SSH2 protocol is required.

PBS Application Services also includes three third party software packages. PBS Application Services will install and configure these three packages during installation:

• JRE 1.7 (Java Runtime Environment)

• Apache Tomcat 7.0x

• Python 2.5.x

Please note - Python 2.5.x must be installed on every execution node, and so is included with the PBS Professional execution node installation option. See section section 6.1.2, “Advanced Configuration Parameters”, on page 78.

1.3.3 Security

• Supported authentication using NIS and UNIX/Linux password security infrastructure

• Supported Windows NT LAN Manager (NTLM) authentication

• Supported High Performance Computing Basic Profile/Basic Execution Services (HPCBP/BES)-compatible Web Services Interoperability (WS-I), Web Services Archi-tecture (WS-A), and WS-security message format

1.3.4 Assumptions, Constraints, and Dependencies

• The PBS Application Services server and the PBS Professional server are required to be installed on the same host for job submission and monitoring.

• PBS Professional infrastructure for file staging: cp or passwordless rcp or scp

• Windows users username and password exactly match those in the UNIX/Linux security setup



1.4 Workflow

PBS Application Services Workflow:

1. The administrator/user creates a new application definition using HPCBP and PBS Application Services guidelines, or modifies an existing application definition.

2. The administrator uses PBS Application Services WSi for installation of the applica-tion definition.

3. The end user, via a front-end graphical user interface, obtains a list of available appli-cations.

4. The end user selects the application and provides the required and optional parame-ters.

5. Input data from the user is transformed into a JSDL-HPCBP format job description using the application definition documents for the specified application.

6. The JSDL-HPCBP job is converted to PBS Professional submission syntax in the PBS specific port and submitted to PBS Professional.

7. PBS Professional executes and terminates the job in an application specific way.



1.5 Software Organization

After a successful installation of PBS Application Services, two main directory structures are created: the PBS Application Services home directory (PAS_HOME) and the execution directory (PAS_EXEC). The location of these directories is platform dependent.

1.5.1 Windows

For a typical Windows x86_64 installation, PBS Application Services is installed in the fol-lowing location:

C:\Program Files\altair\pas\13.0

Files and directories installed at this location are:

Table 1-2: Directories

DirectoryTypes of files and

directories located here

_PBS Application Services_installation PAS installer directory

bin PAS framework directory

jre PAS framework directory

PAS PAS home and execution directories

(denoted by PAS_HOME & PAS_EXEC)

thirdparty PAS framework directory



The PBS Application Services home directory (PAS_HOME) and the execution directory (PAS_EXEC) can be determined by viewing the PBS Application Services configuration file located in:

C:\Program Files\altair\pas\13.0\PAS\pas.conf

The contents of the configuration file for a typical installation are:

1.5.1.1 PBS Application Services Home Directory

The typical location of the PBS Application Services Home directory is:

C:\Program Files\altair\pas\13.0\PAS\home

Directories located in the PBS Application Services Home directory are:

PAS_HOME=C:\Program Files\altair\pas\13.0\PAS\home

PAS_EXEC=C:\Program Files\altair\pas\13.0\PAS\exec

PAS_SERVER=localhost

PAS_PORT=17084

PAS_SSL_ENABLED=true

PAS_SSL_PORT=17443


Directory Description

conf PAS configuration files

config-private PAS configuration files used internally which are not avail-able for user modification

logs PAS log files

repository PAS specific files

applications Application definitions

includes Dynamic includes for the site configuration file.

invalid_applications PAS moves application definitions having invalid syntax to this location

pas-appmaker PAS Application Maker.

scripts Scripts for dynamic includes for site configuration file.



1.5.1.2 PBS Application Services Execution Directory

The typical location of the PBS Application Services Execution directory is:

C:\Program Files\altair\pas\13.0\PAS\exec

Directories located in the PBS Application Services Execution directory are:

schemas Schemas and WSDLs used by all PAS portals

temp Temporary files created by PAS during execution of web server operations



bin PAS binaries

AA Authentication and authorization

pas-server War file and PAS deployment directories of Tomcat server

eifl Infrastructure libraries

Windows Windows specific binaries - eifl server, Pro-cessRunner, unzip, zip

init PAS init script

lib Python scripts for application licensing

python Python scripts

pas-commands PAS Commands

bin PAS Commands python scripts

profiles PBSJobApp profile

src Python script files

pbs_spawn PAS python scripts

python Python library

scripts PAS python scripts





1.5.2 Linux

For a typical Linux/Unix installation, PBS Application Services is installed in the following location:

PBS Application Services home directory: /var/spool/pas

PBS Application Services execution directory: /opt/altair/pas/13.0/pas

PBS Application Services configuration and services directory: /etc

The PBS Application Services home directory (PAS_HOME) and the execution directory (PAS_EXEC) can be determined by viewing the PBS Application Services configuration file located in:

/etc/pas.conf


shared Platform specific shared libraries

Windows Windows shared libraries

unsupported Unsupported

actions-unix PBS hooks

aif2pas Python script for aif to pas conversion

pbs-hooks Unix actions

samples PBSJobSampleClient

PAS_HOME=/var/spool/pas

PAS_EXEC=/opt/altair/pas/13.0/pas


PAS_PORT=17084


PAS_SSL_PORT=17443





1.5.2.1 PBS Application Services Home Directory

The typical location of the PBS Application Services Home directory is:

/var/spool/pas

Directories located in the PBS Application Services Home directory



conf PAS configuration files

config-private PAS configuration files used internally which are not available for user modification

logs PAS log files

repository PAS specific files

applications Application definitions

includes Dynamic includes for the site configuration file.

invalid_applications PAS moves application definitions having invalid syntax to this location

pas-appmaker PAS Application Maker.

scripts Scripts for dynamic includes for site configu-ration file.

schemas Schemas and WSDLs used by all PAS portals

temp Temporary files created by PAS during execu-tion of web server operations



1.5.2.2 PBS Application Services Execution Directory

The typical location of the PBS Application Services Execution directory is:

/opt/altair/pas/13.0/pas

Directories located in the PBS Application Services Execution directory



_PBS Application Services_installation PAS installer directory

init_temp temporary files

jre Java Runtime Environment

pas PAS execution directory

bin PAS binaries

AA Authentication and authorization

pas-server War file and PAS deployment directories of Tomcat server

eifl Infrastructure libraries

Linux-i386 Platform specific binaries - eifl server, Pro-cessRunner, unzip, zip

Linux-x86_64 Platform specific binaries - eifl server, Pro-cessRunner, unzip, zip

Windows Platform specific binaries - eifl server, Pro-cessRunner, unzip, zip

init PAS init script

lib Python scripts for application licensing

python Python scripts

pas-commands PAS Commands

bin PAS Commands python scripts

profiles PBSJobApp profile

src Python script files

pbs_spawn PAS python scripts



1.5.2.3 PBS Application Services Configuration and Services Directory:

Files and directories located in the PBS Application Services Configuration and Services Directory are:

python Python library files

scripts PAS python scripts

shared Platform specific shared libraries

Windows Platform specific shared libraries

Linux-i386 Platform specific shared libraries

Linux-x86_64 Platform specific shared libraries

unsupported Unsupported

actions-unix PBS hooks

aif2pas Python script for aif to pas conversion

pbs-hooks Unix actions

samples PBSJobSampleClient

thirdparty PAS framework directory

Table 1-7:

Directory/File Name Types of files located here

/etc/init.d/pas PAS server script - start, stop, restart PAS

/etc/pas.conf PAS configuration file




Chapter 2

Pre-installation Planning

2.1 Upgrading from a previous release

If you are upgrading from a previous release of PBS Application Services, you must first migrate your existing application definitions, site configuration file, and server configuration file:

1. Stop the PBS Application Services service (see Chapter 8, "PAS service commands", on page 91).

2. Make a backup of the following files:

Prior to PBS Application Services 12.0

• application definitions stored in the <PAS_HOME>/applications directory

• site-config.xml stored in the <PAS_HOME>/conf directory

• server.conf file stored in the <PAS_HOME>/conf directory

PBS Application Services 12.0 and later

• application definitions stored in the <PAS_HOME>/repository/applica-tions directory

• site-config.xml stored in the <PAS_HOME>/repository directory

• server.conf file stored in the <PAS_HOME>/conf directory

3. Remove any old instances of PBS Application Services (see Chapter 11, "Uninstall-ing PAS GUI mode", on page 107 or Chapter 12, "Uninstalling PAS console mode", on page 111).


Chapter 2 Pre-installation Planning

2.2 PBS Application Services default port

The default port used to communicate with PBS Application Services is 17084. This port will be selected dynamically during installation. If port 17084 is not available, then the installa-tion process will increment the port number by one until an available port is found. If an available port is not found after 100 attempts, the installation process will request the admin-istrator to enter a port.

2.3 PBS Application Services staging directory

During the installation of the PBS Applications Service server, you will be prompted to enter a value for the PBS Application Service staging directory. The staging directory is where the necessary files are transferred after job submission (via a client for example, PBS Portals or Compute Manager), but prior to the portal submitting the job to PBS Application Services for transfer to PBS Professional for execution. This staging directory must exist for the installa-tion to complete successfully.

The default location of the staging directory for a typical installation of PBS Application Ser-vices is:

on Linux: /stage

on Window: C:\stage

However, you have the option to choose a custom stage directory during installation.

Following are considerations for selecting and creating the staging directory:

• As of PBS Application Services 11.1, the staging directory can be set to point to the user's home directory by using the variable $USER_HOME (for example: $USER_HOME/stage). However, this functionality is NOT supported by any release of Compute Man-ager prior to CM release 12.0.

• The stage area can grow quite large, depending on the size of the average job. Give care-ful consideration to the disk usage and disk capacity.

• The pathname for the staging directory should not contain spaces.

• PBS Application Services implements an automatic staging directory cleanup such that any data in the staging directory that is not generated by PBS Application Services is at risk of being purged without notice. It is recommended to select a staging directory where only PBS Application Services data files will be stored. Use of a directory that contains important data is not recommended.


Pre-installation Planning Chapter 2

2.4 Access Management Service

PAS incorporates Access Management Service (AMS), a centralized configuration system for authentication and authorization. Other PBS Works products such as Compute Manager and Display Manager are using AMS for authentication and authorization. For this release of PAS, AMS has been implemented to standardize security mechanisms across PBS Works products, and to improve security. AMS will continue to use the security mechanisms described in section 1.3.3, “Security”, on page 5.

After installation, PAS 13.0 Commands can be configured to use password-less or token-based authentication. This feature is available only on Linux platforms. For more informa-tion about configuring password-less authentication see section 5.8, “Configuring password-less authentication”, on page 67. By default, PAS Commands is configured to use username-password based authentication.

2.5 SSL Communication with a Client

A secure connection between PBS Application Services and a client, such as Compute Man-ager, is configured by default. This configuration is done through the server.xml file. The location of the file for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\exec\bin\pas-server\conf

on Linux: /opt/altair/pas/13.0/pas/bin/pas-server/conf

<Connector executor="tomcatThreadPool" port="17443" protocol="HTTP/1.1" SSLEnabled="true"

maxThreads="150" scheme="https" secure="true"

connectionTimeout="20000"

clientAuth="false" sslProtocol="TLS"

keystoreFile="conf/keystore"

keyAlias="aif-key" keystorePass="changeit"

/>



2.6 Installing PAS on a Separate Machine from the PBS Server

A new feature of PAS 13.0 is the ability to install PAS on a separate machine from the PBS Professional Server as a failover server. However, with this deployment option PAS 13.0 and the PBS Client must be installed on the same machine. In addition, PAS resources must be manually added to the PBS resource definition file after installing PAS. For more information about this post-installation task see section 5.9, “Configuring PBS resources”, on page 68.


Pre-installation Planning Chapter 2

2.7 File Transfer Service

A new feature of PAS 13.0 provides a mechanism for executing remote file operations on the PBS Professional execution hosts. This mechanism is called File Transfer Service or FSP. FSP removes the dependency upon PBS Professional for remote file operations and file trans-fers. Additionally, FSP increases the speed of Compute Manager file operations during job execution time. If you are interesting in utilizing FSP see Chapter 14, "File Service Provider", on page 125.


Chapter 3

Installing PAS GUI modeAs of the PBS Application Services 11.1 release, two installation options are available. The first option will install both the PBS Application Service server and the PAS Commands. The second option will install the PAS Commands only. PAS Commands are command-line scripts that allow users to access the power of PBS Professional without the use of a graphical user interface, while leveraging the capabilities of PBS Application Services and application definitions. For more information on how to use the PAS Commands see the PBS Application Services Commands User Guide.

See Chapter 13, "Troubleshooting", on page 113 for information pertaining to problems, warnings, or error conditions experienced while installing PAS.

A new feature of PAS 13.0 is the ability to install PAS and the PBS Professional Server on separate machines. However, this deployment option requires that PAS 13.0 and the PBS Cli-ent be installed on the same machine.


Chapter 3 Installing PAS GUI mode

3.1 Installing PBS Application Services and PAS Commands

Installation of this product requires:

• System administrator privileges (root or Windows Administrator)

• Existing installation of PBS Professional 11.3 or newer

• Installation of PAS on the same machine as the PBS Client when PAS is not being installed on the machine hosting the PBS Professional Server.

• Existing user account to register as the PBS Application Services Administrator account (default is pbsadmin)

• Removal of any old instances of PBS Application Services

• Removal of any instances of Python and Tomcat installed with previous versions of PBS Application Services

• PBS Application Services staging directory must exist prior to installation of this product

Please note - The first step in the installation process is the extraction of the installer to the %tmp% directory. There should be enough space in this directory to extract the installer (approximately 3 times the installation size). Also, while the installer is being extracted, noth-ing should be deleted from this directory.

To install PBS Application Services and PAS Commands, download the installer executable appropriate for your platform from the user area.

3.1.1 Starting the installer

Invoke the installer by running the installation binary on Linux/Unix platforms. For example:

./PBSAppSvcs_13.0_SLES-11_x86_64_20130521_1437.bin -i swing

Or by double-clicking the executable on Windows platforms:

PBSAppSvcs_13.0_Windows_x86_64_20130521_1437.exe


Installing PAS GUI mode Chapter 3

3.1.2 PBS Application Services installation instructions

Once the extraction process is complete, installation instructions will be displayed. Please read through the instructions before proceeding with the installation. At anytime during the installation process, you may click Previous to go back to a previous installation step. You may cancel the install at any time during the installation process by clicking Cancel. To con-tinue the installation process, click Next.



3.1.3 License Agreement

License agreement information will be displayed. Please read through the license agreement before proceeding with the installation. To accept the terms of the license agreement, click I accept the terms of the License Agreement, and click Next.



3.1.4 Install options

Choose to install the PBS Application Services server and the PAS Commands by selecting PAS Server and Commands (clear the PAS Commands Only check box if necessary), and then click Next.



3.1.5 PAS service user

Enter the user with whom the PBS Application Services service will be registered. The default is "pbsadmin".

On Windows platforms, this should be the PBS Administrative account as specified during the installation of PBS Professional.

On Linux/Unix platforms, this must be an existing account and can be a non-privileged user account that has been granted manager status for PBS Professional.

Once you have entered the user, click Next..



3.1.6 PAS service user password - Windows only

If you are installing PAS on a Windows platform, enter the PAS service user password. Click Next.



3.1.7 Staging directory

Enter a staging directory where user's job files will be staged prior to execution. This direc-tory must exist prior to the installation of PBS Application Services. You may select a custom stage directory by clicking Choose (please see the staging directory considerations below before choosing the location of the staging directory). Click Restore Default Folder to reset the directory to the default location. Select a staging directory for PBS Application Services and click Next.

Staging directory considerations:




• PBS Application Services implements an automatic staging directory cleanup such that any data in the staging directory that is not generated by PBS Application Services is at risk of being purged without notice. It is recommended to select a staging directory where only PBS Application Services data files will be stored. Use of a directory that contains important data is not recommended.


P 29

Chapter 3

ows platforms

BS Application Services Administrator’s Guide

Installing PAS GUI mode

Linux/Unix platforms Wind


3.1.8 License server

It is not mandatory to provide the license server at installation time. You may configure the license server information after installation of PAS (see the configurable parameter ALTAIR_LICENSE_PATH in section 6.1.2, “Advanced Configuration Parameters”, on page 78). Click Next.


P 31

Chapter 3

3

S tion Services in the default directory, or y re Default Folder. Once an installation l

ows platforms



.1.9 Installation location

pecify a location where PBS Application Services will be installed. You may install PBS Applicaou may select a custom directory by clicking Choose. To restore the default directory, click Restoocation is entered, click Next.


C

3 lication Services Administrator’s Guide

3

A lation. You may click Previous to go b

ows platforms

hapter 3 Installing PAS GUI mode

2 PBS App

.1.10 Pre-installation summary

pre-installation summary will be displayed. Review all your locations before initiating the instalack and make any changes. Install PBS Application Services by clicking Install.



3.1.11 Installation progress

The installation of PBS Application Services will be initiated. You can monitor the progres-sion of your installation via the installation progress toolbar.



3.1.12 Start PAS services

Once the installation is complete a message will be displayed asking if the PAS services should be started. Click Yes to start PBS Application Services. Click No to complete the installation without starting PBS Application Services. To manually start PBS Application Services see section 8.1, “Starting the PAS service”, on page 91.



3.1.13 PAS client validation

If the PAS service was started, then the PBS Application Services server will be contacted and the following message should be displayed. Click Next to continue the installation.


C


3

O yed. Click Done to complete the instal-l

3

P o configure PAS and to perform post-i

ows platforms


6 PBS App

.1.14 Installation complete

nce the installation of PBS Application Services is complete the installation details will be displaation

.1.15 Post-installation

lease proceed to the post-installation instructions (see Chapter 5, "Post-installation", on page 61) tnstallation tasks that must be completed before the PAS is ready for use.



3.2 Installing PAS Commands




To install PAS Commands, download the installer executable appropriate for your platform from the user area.



./PBSAppSvcs_13.0_SLES-11_x86_64_20130521_1437.bin -i swing


PBSAppSvcs_13.0_Windows_x86_64_20130521_1437.exe



3.2.2 PAS Commands installation instructions





Choose to install the PAS Commands by selecting PAS Commands Only (clear the PAS Server and Commands check box if necessary), and then click Next.



3.2.5 PAS server hostname/IP address

Enter the PBS Application Services server hostname or IP address, and the server port num-ber, and click Next. You may choose to accept the defaults by just clicking Next.


C


3

S or you may select a custom directory by c on location is entered, click Next.

ows platforms


2 PBS App

.2.6 Installation location

pecify a location where PAS Commands will be installed. You may install in the default directory,licking Choose. To restore the default directory, click Restore Default Folder. Once an installati


P 43

Chapter 3

3


ows platforms



.2.7 Pre-installation summary

pre-installation summary will be displayed. Review all your locations before initiating the instalack and make any changes. Install PAS Commands by clicking Install.



3.2.8 Installation progress

The installation of PAS Commands will be initiated. You can monitor the progression of your installation via the installation progress toolbar.


P 45

Chapter 3

3

O yed. Click Done to complete the instal-l

ows platforms



.2.9 Installation complete

nce the installation of PBS Application Services is complete the installation details will be displaation.



3.2.10 Post-installation

Please proceed to the post-installation instructions (see Chapter 5, "Post-installation", on page 61) to configure PAS and to perform post-installation tasks that must be completed before the PAS is ready for use.


Chapter 4

Installing PAS console modeAs of the PBS Application Services 11.1 release, two installation options are available. The first option will install both the PBS Application Service server and the PAS Commands. The second option will install the PAS Commands only. PAS Commands are command-line scripts that allow users to access the power of PBS Professional without the use of a graphical user interface, while leveraging the capabilities of PBS Application Services and application definitions. For more information on how to use the PAS Commands see the PBS Application Services Commands User Guide.

See Chapter 13, "Troubleshooting", on page 113 for information pertaining to problems, warning, or error conditions experienced while installing PAS.

A new feature of PAS 13.0 is the ability to install PAS and the PBS Professional Server on separate machines. However, with this deployment option PAS 13.0 and the PBS Client must be installed on the same machine.


Chapter 4 Installing PAS console mode

4.1 Installing PBS Application Services and PAS Commands


• System administrator privileges (root privileges)

• Existing installation of PBS Professional 11.3 or newer

• Installation of PAS on the same machine as the PBS Client when PAS is not being installed on the machine hosting the PBS Professional Server.

• Existing user account to register as the PBS Application Services Administrator account (default is pbsadmin)

• Removal of any old instances of PBS Application Services

• Removal of any instances of Python and Tomcat installed with previous versions of PBS Application Services

• PBS Application Services staging directory must exist prior to installation of this product

• Port 17084 must be opened for incoming TCP traffic


To install PBS Application Services and PAS Commands, download the installer executable appropriate for your platform from the user area.


Invoke the installer by running the installation binary. The installer will be extracted. This may take a few moments. For example:

./PBSAppSvcs_13.0_SLES-11_x86_64_20130521_1437.bin


Installing PAS console mode Chapter 4


The command line installer will launch and you will be prompted to either cancel or continue the installation. You may cancel the install at any time during the installation process by entering "quit" and pressing <Enter>. At anytime during the installation process, you may enter “back” and press <Enter> to go back to a previous installation step. To begin the installation process, press <Enter>.




Several pages of license agreement information will be displayed. Page through the license agreement by continuing to press <Enter> until you are prompted to accept the terms of the license agreement. To accept the terms of the license agreement enter "y" and press <Enter>.


Choose to install the PBS Application Services server and the PAS Commands by entering "1" and then pressing <Enter>.



4.1.5 PAS service user

Enter the user with whom the PBS Application Services service will be registered. The default is "pbsadmin". This must be an existing account and can be a non-privileged user account that has been granted manager status for PBS Professional. Once you have entered the user, press <Enter>.



4.1.6 Staging directory

Enter a staging directory where user's job files will be staged prior to execution. This direc-tory must exist prior to the installation of PBS Application Services. Once a staging directory has been entered, press <Enter>, or to accept the default staging directory, /stage, just press <Enter> (please see the note below before choosing the location of the staging directory).

Staging directory considerations:




• PBS Application Services implements an automatic staging directory cleanup such that any data in the staging directory that is not generated by PBS Application Services is at risk of being purged without notice. It is recommended to select a staging directory where only PBS Application Services data files will be stored. Use of a directory tha contains important data is not recommended.



4.1.7 License server

It is not mandatory to provide the license server at installation time. You may configure the license server information after installation of PAS (see the configurable parameter ALTAIR_LICENSE_PATH in section 6.1.2, “Advanced Configuration Parameters”, on page 78)

Click Next.

4.1.8 Installation location

Enter a directory where PBS Application Services will be installed and press <Enter>, or to accept the default directory, /opt/altair/pas/13.0, just press <Enter>.



4.1.9 Pre-installation summary

A pre-installation summary will be displayed. Review all your locations before initiating the installation. You may enter “back” and press <Enter> to go back and make any changes. Install PBS Application Services by pressing <Enter>.

4.1.10 Start PAS services

A message will be displayed indicating the installation has begun. Once the installation is complete a message will be displayed asking if the PAS services should be started. Enter "1" and press <Enter> to start PBS Application Services. Enter "2" and press <Enter> to com-plete the installation without starting PBS Application Services. To manually start PBS Application Services see section 8.1, “Starting the PAS service”, on page 91.



4.1.11 PAS client validation

If the PAS service was started, then the PBS Application Services server will be contacted and the message "PAS client was installed successfully (Server servername on port number portNum is up and running)" should be displayed. Press <Enter> to continue the installa-tion.

4.1.12 Installation complete

An installation complete message will be displayed indicating your installation is complete. Press <Enter> to complete the installation. Please logout and login again to complete the configuration for the PAS Commands prior to using PBS Application Services.





4.2 Installing PAS Commands


• System administrator privileges (root privileges)


To install PAS Commands, download the installer executable appropriate for your platform from the user area.



/PBSAppSvcs_13.0_SLES-11_x86_64_20130521_1437.bin








Choose to install the PAS Commands by entering "2" and then pressing <Enter>.



4.2.5 PAS server hostname/IP address

Enter the PBS Application Services server hostname or IP address and press <Enter>. You may choose to accept the defaults by just pressing <Enter>.

4.2.6 PAS server port

Enter the PBS Application Services server port number and press <Enter>. You may choose to accept the defaults by just pressing <Enter>.

4.2.7 Installation location

Enter a directory where PAS Commands will be installed and press <Enter>, or to accept the default directory, just press <Enter>.



4.2.8 Pre-installation summary

A pre-installation summary will be displayed. Review all your locations before initiating the installation. You may enter “back” and press <Enter> to go back and make any changes. Install PBS Application Services by pressing <Enter>.

4.2.9 Installation complete

An installation complete message will be displayed indicating your installation is complete. Press <Enter> to complete the installation. Please logout and login again to complete the configuration for the PAS Commands prior to using PBS Application Services.


Chapter 5

Post-installation

5.1 Features and configuration files

There are several configuration files and features that are installed with PAS.

5.1.1 Application definitions

Application definitions are a feature of PAS and are used to submit jobs using the power and flexibility of PAS. Application definitions are stored in the PAS application directory. The location of this directory for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\home\reposi-tory\applications

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

For an overview of application definitions see Chapter 9, "Application Definitions", on page 95.

Diving Into Application Definitions 13.0 explains what an application definition is and how to use an application definition. If you are installing PAS for the first time and are not familiar with application definitions, then Diving Into Application Definitions 13.0 is a good place to start. A set of tutorials is provided starting with how to create the simplest of application definitions and progressing to more advanced topics. Recipes are also available demonstrat-ing advanced techniques.

In addition, a sample application definition called PBSJobApp is provided out-of-the-box with PAS and is located in the PAS application directory.


Chapter 5 Post-installation

5.1.2 Site configuration file

A default site configuration file, site-config.xml, is installed in the PAS configuration directory. The location of this file for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\home\reposi-tory

on Unix/Linux: /var/spool/pas/repository

This file is a central repository for site specific information that can be used across all applica-tion definitions. The default site configuration file installed with PAS is basically a template. Initially, you may use the default site configuration file as is, but as you become accustomed to working with application definitions, you may choose to modify the site configuration file per your site’s needs. A tutorial and several recipes are available within Diving Into Applica-tion Definitions 13.0 showing several ways that the site configuration file can be used with an application definition. For an overview of the site configuration file see section 9.4, “Site-wide Settings”, on page 99.

5.1.3 Server configuration file

A server configuration file, server.conf, is also installed in the PAS configuration direc-tory. This file contains all configurable parameters available with PAS. Please review section 6.1, “Configurable parameters”, on page 74 for an explanation of each parameter.


Post-installation Chapter 5

5.1.4 PAS configuration file

A PAS configuration file, pas.conf,is installed by default in the following location:

on Linux: /etc/pas.conf

on Windows: C:\Program Files\altair\pas\13.0\PAS\pas.conf

This file contains:

• the location of the PAS home directory where application definitions, the site configura-tion file, PAS log files, and the server configuration file are stored.

• the execution directory where all binaries, scripts, and third party software are stored.

• the IP address and port number of the PAS server.

• a parameter for enabling or disabling HTTPS communication between the PAS server and PAS Commands.

• the default port for HTTPS communication between the PAS server and PAS Commands.

Linux

Windows




PAS_PORT=17084


PAS_SSL_PORT=17443

PAS_HOME=C:\Program Files\altair\pas\13.0\PAS\home

PAS_EXEC=C:\Program Files\altair\pas\13.0\PAS\exec


PAS_PORT=17084


PAS_SSL_PORT=17443



5.2 Installing PAS for the first time

5.2.1 Configure PAS

If you are installing PAS for the first time, the only configuration that is necessary before using PAS is to make changes to the configurable parameters stored in the server.conf file. Make any modifications that are necessary for your site's installation. For more infor-mation about configurable parameters available for PAS see section 6.1, “Configurable parameters”, on page 74.

5.2.2 Restart PAS service

Any configuration changes will require a restart of the PBS Application Services server (see Chapter 8, "PAS service commands", on page 91).

5.3 Upgrading from a previous release

If you are upgrading from a previous release of PBS Application Services to a new release, you must now migrate your existing application definitions, site configuration file, and server configuration file that were backed up during the pre-installation process (see section 2.1, “Upgrading from a previous release”, on page 15).

5.3.1 Migrate application definitions

Copy the backups of the application definitions to the new <PAS_HOME>/repository/applications directory.

5.3.2 Migrate site configuration file

Copy the backup of the site configuration file to the new <PAS_HOME>/repository directory.

5.3.3 Migrate server configuration file

Review and compare the new version of the server configuration file to the backup. Addi-tional parameters may have been added to the new server configuration file, or default values for configuration parameters may have changed. Make any modifications that are necessary for your site's installation. For more information about configurable parameters available for



PAS see section 6.1, “Configurable parameters”, on page 74.

5.3.4 Restart the PAS server

Any migration activities will require a restart of the PBS Application Services server (see Chapter 8, "PAS service commands", on page 91).

5.4 Updating search path for PAS Commands

On Linux platforms that are installing PBS Application Services version 11.1 or later, any user's of the PAS Commands will need to add <PAS_EXEC>/pas-commands/bin to their search path.

5.5 Enabling job history

As of PBS Application Services release 11.1, PBS Application Services does not automati-cally set the PBS Professional job_history_enable attribute to true. Therefore, to enable job history use the PBS Professional command:

qmgr -c 'set server job_history_enable=True'

5.6 Setting environment variable PAS_CONF_FILE

The environment variable, PAS_CONF_FILE, needs to be set for any nodes where PAS Com-mands are installed. This environment variable must be set to the absolute path of the PBS Application Services configuration file. The location of the configuration file for a typical installation of PBS Application Services is:

on Linux: /etc/pas.conf

on Windows: C:\Program Files\altair\pas\13.0\PAS\pas.conf



5.7 Configuring SSL for communication with PAS Commands

As of version 12.0.2, HTTPS communication between PAS Commands and the PAS server will be enabled by default. The default port number for HTTPS communication is 17433.

SSL must be enabled for both the PAS Client and the PAS Server. Therefore, the following parameters in the PAS configuration file (pas.conf) on the PAS Client and PAS Server machines must contain the same values, i.e., SSL must either be enabled or disabled on all machines and the SSL port number must match.

Communication over HTTPS can be disabled by modifying the configuration parameter PAS_SSL_ENABLED to "false" in the pas.conf file on all machines where PAS Com-mands is installed. Communication will then occur using the HTTP protocol.

It is also possible to configure a non-default SSL port for PAS Commands by changing the value of PAS_SSL_PORT on all machines where PAS Commands is installed.


PAS_SSL_PORT=<SSL_PORT>




PAS_PORT=17084

PAS_SSL_ENABLED=false

PAS_SSL_PORT=17445



5.8 Configuring password-less authentication

By default, PAS Commands employs username-password based authentication. With PAS 13.0, PAS Commands can be configured to use password-less (token-based) authentication. This feature is available only on Linux platforms. When password-less authentication is con-figured, user's no longer have to set a password before executing a PAS Command using the pas-passwd command.

If you have installed PAS Commands on multiple machines, you can configure password-less authentication for all machines, or a subset of those machines. This allows you to pick and choose where you want to employ password-less authentication.

To enable password-less authentication, add the following key-value pair to the pas.conf file on the machine where PAS Commands is installed.

PWDLESS_AUTH=true .

Password-less authentication can be disabled by removing the PWDLESS_AUTH=true key-value pair from the pas.conf file or by setting the value of PWDLESS_AUTH to false.




PAS_PORT=17084


PAS_SSL_PORT=17443

PWDLESS_AUTH=true




PAS_PORT=17084


PAS_SSL_PORT=17443

PWDLESS_AUTH=false



5.9 Configuring PBS resources

A new feature of PAS 13.0 is the ability to install PAS on a separate machine from the PBS Professional Server as a failover server. When PAS 13.0 is installed on a separate machine, resources required by PAS must be manually added to the PBS resource definition file. This file is located in the following directory on the machine where the PBS Professional server is installed (PBS_HOME is the location of the PBS working directories):

PBS_HOME/server_priv/resourcedef

Add these resource definitions to the resourcedef file and then restart the PBS Profes-sional server:

In addition, the PBS Professional flatuid attribute must be set to True. This attribute speci-fies whether, for each user, the username at the submission host must be the same as the one at the Server host. The username at the Server host must always be the same as the username at

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

pas_billing_accounts type=string_array

pas_policies type=string_array

pas_applications type=string_array

pas_applications_enabled type=string_array flag=h

pas_platform type=string_array flag=h

pas_candidate_hosts type=string_array

pas_operating_system type=string_array flag=h

pas_cpu_arch type=string_array flag=h

aif_billing_accounts type=string_array

aif_policies type=string_array

aif_applications type=string_array

aif_applications_enabled type=string_array flag=h

aif_platform type=string_array flag=h

aif_candidate_hosts type=string_array

aif_operating_system type=string_array flag=h

aif_cpu_arch type=string_array flag=h

# *********END OF AIF STATIC RESOURCES SECTION *************

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

ngpus type=long flag=nh

# *********** END OF DM STAT



the execution host. When flatuid is set to True, the Server assumes that UserA@host1 is the same as UserA@host2. Therefore, if flatuid is True, UserA@host2 can operate on UserA@host1’s job. Follow these steps to set flatuid to True:

1. At the command line, enter the command:

Qmgr: print server

2. If the attribute flatuid is equal to False or is not set (you do not see it in the output from the print server command), then set the value to True by issuing the command:

Qmgr: set server flatuid = True

For more information about installing PAS on a separate machine from the one hosting the PBS Professional server see section 2.6, “Installing PAS on a Separate Machine from the PBS Server”, on page 18.



5.10 Configuring the File Service Provider

File Service Provider or FSP is a mechanism for executing remote file operations on the PBS Professional execution hosts. FSP removes the dependency upon PBS Professional for remote file operations and file transfers. For more information about FSP see Chapter 14, "File Service Provider", on page 125.

By default, the use of FSP for file operations on the PBS Professional execution hosts is dis-abled. To use FSP to provide remote file operations, set the value of HTTP_FILE_TRANSFER_ENABLED to true in the server.conf file on the machine where the PAS Server is installed. The FSP port number, denoted by <FSP_PORT>, must be set to the port number that was specified during the installation of FSP.

To disable the use of the FSP for remote file operations, set the value of HTTP_FILE_TRANSFER_ENABLED to false.

Any change to the server.conf file requires a restart of the PAS server.

#Configuration to toggle HTTP based file transfer

HTTP_FILE_TRANSFER_ENABLED=true

#Default port for file service provider

FILE_SERVER_PORT=<FSP_PORT>

#Configuration to toggle HTTP based file transfer

HTTP_FILE_TRANSFER_ENABLED=false

#Default port for file service provider

FILE_SERVER_PORT=<FSP_PORT>



5.11 Verifying the installation of PAS

To verify that the installation was successful, the server is up and running, and PBS Applica-tion Services is properly integrated with PBS Professional, complete the following steps:

1. Determine if the PBS Application Services server is up and running by issuing the following command at the command prompt:

pas-ping

This command will return a message indicating the status of the PAS server

PAS server at <machine name> is up/down.

If the server is up and running then proceed to step 2. Otherwise, review the PBS Application Services log file for error messages.

2. Determine that PBS Application Services has successfully integrated with PBS Pro-fessional by issuing the following command at the command prompt.

pas-stat

This command displays the status of all jobs on the PBS Application Services server.

If this command returns a list of jobs and their corresponding status then proceed to step 3. Otherwise, review the PBS Application Services log file for error messages.

3. Submit a job.

Create a shell script called hello_world.sh and place the following code in that script:

Issue the following command at the command prompt:

If the job completes successfully, this command will create an output file containing the text 'Hello World'. Otherwise, review the PBS Application Services log file for error messages.

#!/bin/sh

echo 'Hello World'

pas-submit ApplicationId=PBSJobApp ApplicationName=PBSJobApp JOB_NAME=PBSJobApp_test MEMORY=10 NCPUS=1 JOB_SCRIPT=pbscp://hostname/job_script_pathname/hello_world.sh SUBMISSION_DIRECTORY=pbscp://hostname/submisson_dir_pathname


Chapter 6

Configuring PBS Application ServicesThe PBS Application Services Server has several configurable parameters. PBS Application Services stores its configuration data in a file called server.conf. The location of this file for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\home\conf

on Linux: /var/spool/pas/conf

All parameters are stored in key=value pairs. Spaces and tabs are preserved (as spaces) and providing quotes around values is optional. As spaces are preserved, do not use key = value (notice the space surrounding the =) unless spaces are intentional. Empty lines beginning with a comment symbol (ie. #) are ignored.


C ices


6

6

Default Value

the tracing the

server-log.xml

bled ults to e

false

r BS any

speci-ot be

eged S Pro-

pbsadmin

hapter 6 Configuring PBS Application Serv

4 PBS App

.1 Configurable parameters

.1.1 Standard configuration parameters

Table 6-1: Standard Configuration Parameters

Parameter Description

LOGGING_CONFIG_FILE_RELATIVE The PBS Application Services logging configuration file(Log4J) which is used to configure logging levels. SincePBS Application Services uses Log4J as its logging and API, you can access additional information on Log4J viaApache Log4J website at http://logging.apache.org/log4j

DEBUG The PBS Application Services debugging property. If enatrue, PBS Application Services will send intermittent resfiles stored in PAS_HOME/temp. This can be an effectivdebugging mechanism.

ADMIN_USER The PBS Application Services administration account (foexample, pbsadmin) that has complete control over the PApplication Services Server. This account is required forremote PBS Application Services administration tasks.

On Windows, this will be the same pbsadmin account as fied during the installation of PBS Professional and cannchanged.

On Linux, the administration account can be a non-priviluser account that has been granted manager status for PBfessional, and can be changed after installation.

P 75

ices Chapter 6

S uthori-yer.

Linux: UnixLogin

Windows: WindowsLogin

direc-n Ser-are , PBS

itting rofes-

job for m the wants g direc-ady to e, but

E_- using E/

any

Linux: /stage

Windows: C:/stage

http

Default Value


Configuring PBS Application Serv

LOGIN_MODULE_NAME The PBS Application Services authentication module. PBApplication Services uses the Java Authentication and Azation Service (JAAS) as its authentication abstraction la

STAGE_ROOT The PBS Application Services file staging location. Thistory must exist prior to the installation of PBS Applicatiovices. The staging directory is where the necessary files transferred after job submission (via a client for examplePortals or Compute Manager), but prior to the portal submthe job to PBS Application Services for transfer to PBS Psional for execution. When PBS Professional selects theexecution, the files are staged-in to the execution host frostaging directory. Upon job completion, any files the job to retain are staged-out by PBS Professional to the stagintory, and the client retrieves them from there when it is redo so. Customer written portals may choose to do the samare not required to do so.

As of PBS Application Services 11.1, the value of STAGROOT can be set to point to the user's home directory bythe variable $USER_HOME (for example: $USER_HOMstage). However, this functionality is NOT supported byrelease of Compute Manager prior to CM release 12.0.

FILE_TRANSFER_PROTOCOL The PBS Application Services file transfer mechanism.



C ices


ime. the y the e e never

14

This is BS

hed_-ral val-

server_dyn_res: '$FEATURE !"$PYTHON_PATH" "$LICSTATUS_PATH" --get-licenses -F $FEATURE'

oolean ar in

urces

ources line.

e added

false

Default Value


6 PBS App

FILE_EXPIRATION_TIME The PBS Application Services stage area file expiration tThat is, the age in days after which data is removed fromPBS Application Services staging directory (as defined bSTAGE_ROOT parameter) and its subdirectories with thexception of the profiles directory. Files in the profiles arremoved by PBS Application Services.

DYN_RES_PATTERN The PBS Application Services dynamic resource string. the pattern for creation of server_dyn_res records in the PScheduler configuration file (PBS_HOME/sched_priv/scconfig). The following elements are substituted with liteues defined by the PBS Application Services Server $FEATURE, $PYTHON_PATH.

PAS_SCHEDULING The PBS Application Services scheduling policy. This Battribute determines if PAS scheduler resources will appesched_config on PAS startup.

if PAS_SCHEDULING is set to true, PAS scheduler resowill be set in PBS sched_config in "resources:" line.

if PAS_SCHEDULING is set to false, PAS scheduler reswill be removed from PBS sched_config in "resources:"

The exception is PAS Dynamic licensing resources. Thosresources are now controlled by PAS_LICENSING (not or removed when we change PAS_SCHEDULING).



P 77

ices Chapter 6

S

S

false

17185

Default Value



HTTP_FILE_TRANSFER_ENABLED True enables the use of FSP for file operations on the PBMOMs.

False disables the use of FSP for file operations on the PBMOMs.

FILE_SERVER_PORT Port used by FSP.



C ices


6

T ppropriate for advanced configurations...

Default Value

ca-

y or ve re ry

as

$PBS_EXEC/bin/python

es on

on

<PAS_EXEC>/scripts/lic_status.py


8 PBS App

.1.2 Advanced Configuration Parameters

he PBS Application Services Server also has a few optional parameters available to you that are a

Table 6-2: Advanced Configuration Parameters


PYTHON_PATH The PBS Application Services Python binary. The PBS Applition Services require that each PBS execution host provide a standard Python binary. The full path to your systems Pythonbinary can be changed here.

The PBS Professional daemon pbs_mom will look for a binarcalled pbs_python in PBS_EXEC/bin. If using custom actionsany other operations that involve the pbs_mom accessing thispbs_python (aka python binary) there may be problems if thepython libraries are not located in the standard locations relatito PBS_EXEC/bin/pbs_python. If Python is installed elsewhea link to (Linux) or copy of (Windows) the actual python binamust exist as PBS_EXEC/bin/pbs_python.

As of PBS Professional 11.0 a Python distribution is includedpart of the pbs_mom installation.

LICSTATUS_PATH When the PBS Scheduler needs to know the number of licensavailable with which to run jobs submitted via PBS ApplicatiServices, it uses the lic_status.py utility to query the license server. This parameter can be configured to point to the locatiof lic_status.py. See the DYN_RES_PATTERN parameter above.

P 79

ices Chapter 6

Specified during the installa-tion of PBS Application Ser-vices

er. e

none

s ve

none

65536

Default Value



ALTAIR_LICENSE_PATH The location of the Altair license server. This is the license server from which PBS Application Services itself attempts topull license(s). Format: port@hostname.

FEATURE The application licensing feature, as known to the license servThe custom resource created for PBS Professional must be thsame as this feature name.

MAX_LIST_FILES_COUNT The number of files to be returned by the FileList API. Allowsites to impose limits on how many files are returned to improthe response time of CM remote file operations.

BUFFER_SIZE Maximum buffer size for file operations in bytes.

Table 6-2: Advanced Configuration Parameters


Chapter 6 Configuring PBS Application Services

6.2 Configuring PAS Server logging behavior

The PAS logging behavior can be defined in the file server-log.xml. The location of the file for a typical installation of PAS is:

on Windows : C:\Program Files\altair\pas\13.0\PAS\home\conf

on Linux : /var/spool/pas/conf

The default logging level is set to “info” providing informational messages that highlight the progress of the application at a coarse-grained level.

PAS allows logging to be configured for certain functional aspects of PAS, such as file opera-tions or job submission. These functional areas are defined by the <category> element. The existing categories in the server-log.xml are useful as a basic configuration, are more course-grained, and provide the default PAS logging.

To configure the level of logging, edit the server-log.xml file and set the <priority value> attribute of a particular <category> to one of the following values:

• off - has the highest possible rank and is intended to turn off logging.

• fatal- very severe error events that will presumably lead the application to abort.

• error- error events that might still allow the application to continue running.

• warn- potentially harmful situations.

• info - informational messages highlighting the progress of the application at a coarse-grained level.

• debug- fine-grained informational events that are most useful to debug an application.

• trace - finer-grained informational events than the DEBUG.

• all - the lowest possible rank and is intended to turn on all logging..

Another debugging option is to configure PAS to create job resource dump files. Setting the PAS configuration parameter DEBUG to false (see section 6.1, “Configurable parameters”, on page 74), writes job resource dump files to the location <PAS_HOME>/temp. PAS will then log a reference to the dump file in the PAS log file. For example:

The following sections describe categories that can be added to the server-log.xml file to troubleshoot non-default functional aspects of PAS:

<category name="category">

<priority value="<logging_level>" />

</category>

“Created job resources dump: <file name>”


Configuring PBS Application Services Chapter 6

6.2.1 Remote file operations, job submission, and job status

The logging for this category is relevant for the communication to and from the EIFL server

The following are examples of the type of messages that will be logged if debugging is enabled for this class:

Before a web service API call to the EIFL server

After an EIFL web service API call to the EIFL server

For a job status request, before the web service API call to the EIFL server

After an EIFL web service API call to the EIFL server

For the job submission request, after a web service API call to the EIFL server, on successful job submission:

For the job delete request, after a web service API call to the EIFL server:

For each operation, if an error occurs, the error code will be logged as returned by PBS

<category name="com.altair.gw.aif.pbs.ifl.implementations.PbsEiflWs">

<priority value="debug" />

</category>

“Success getting eifl server port <port>”

“Success returning from eifl.waitExit(), port is <port>”

“qstatJobs(): Success getting eifl server port <port>”

“qstatJobs(): Success returning from eifl.waitExit(), port is <port>”

"SubmitJob: returned job ID <jobId>”

“Deleted job ID: <jobId>”

“PbsEiflWs.java getErrorCode(): pbs error code is <pbsErrorCodeStr>”



6.2.2 File upload/download

6.2.3 File operations (local and remote)

6.2.4 Job submission

The following are examples of the type of messages that will be logged if debugging is enabled for this class:

Before job submission, PAS will record the job name and the resources requested.

Once the job is submitted, PAS will record the job id.

For job status requests, PAS will log any empty responses.

<category name="com.altair.gw.aif.servlets">


</category>

<category name="com.altair.gw.aif.fileop.implementation.FileOperations"> <priority value="debug" /></category>

<category name="com.altair.gw.aif.fileop.implementation.FileOperationsHelper"> <priority value="debug" /></category>

<category name="com.altair.gw.aif.wms.jobsubmission">


</category>

PbsJobFactory.getPbsJob():job name = <job name>, resourceList to String: <job resources>

“JobSubmit success. Job id: <jobId>”

"HpcpPbsAdapter.jobList(): qstat is empty"



6.2.5 Job submission and status

Enabling a debugging level for the “PbsJobsPortImpl” class also provides the ability to deter-mine the IP address of a client request for PAS job submission services.

For each job submission API call a log record is created having the API name, requesting user name, and remote host,. For example:

6.2.6 License checkout by PAS

6.2.7 Applications (application definitions)

6.2.8 Dynamic Application Refresh Script

<category name="com.altair.schemas.pbs._2007._03.portal.PbsJobsPortImpl">


</category>

<category name="com.altair.gw.aif.pbs.ifl.responses.JobsStatus_Response">


</category>

<category name=" com.altair.gw.aif.pbs.ifl.responses.PBSObjectStatus">


</category>

Entered getJobs(). User: <username>, client host: '<clientHost>'

<category name="com.altair.gw.pbs">


</category>

<category name="com.altair.gw.aif.converter">


</category>

<category name="com.altair.gw.aif.applications.utils.DynamicApplicationBuilder">


</category>



6.2.9 Metascheduling

To troubleshoot specific functional aspects of the Metascheduling version of PAS, enable debugging for the following classes/packages:

6.2.9.1 Basic Execution Service (BES) operations

All BES API operation calls will be logged. For example:

6.2.9.2 Vnode monitoring

Every time vnode details are requested, PAS will record the fact. For example: :

6.2.9.3 Job submission and status

In addition, the following debugging levels can be enabled for Metascheduling: section 6.2.1, “Remote file operations, job submission, and job status”, on page 81 and section 6.2.4, “Job submission”, on page 82.

<category name=" com.altair.schemas.aif._2010._07.bes_factory_wms. BESFactoryPortTypeImpl">


</category>

"CreateActivity: Job Submitted successfully."

<category name="com.altair.gw.aif.pbs.utils.monitoring">


</category>

“Getting VNode Details"

<category name="com.altair.gw.aif.pbs.ifl.responses.JobsStatus_Response">


</category>

<category name=" com.altair.gw.aif.pbs.ifl.responses.PBSObjectStatus">


</category>



6.3 Configuring PAS Commands logging behavior

PAS Commands log files and logging behavior configuration files are located on the machine where PAS Commands is installed.

The PAS Commands logging file is located at:

PAS_HOME/pas-commands/logs/pas-commands.log

The PAS Commands logging behavior is defined in the file PAS_HOME/pas-commands/conf/pas-commands-logging.conf.

If you have installed PAS Commands on multiple machines, you can configure logging behavior specifically for each machine.

The default logging level is set to “INFO” providing informational messages that highlight the progress of the application at a coarse-grained level.

To configure the level of logging, edit the pas-commands-logging.conf file and set the value of level to one of the following values:

• CRITICAL- very severe error events that will presumably lead the application to abort.

• DEBUG- fine-grained informational events that are most useful to debug an application.

• ERROR- error events that might still allow the application to continue running.

• INFO- informational messages highlighting the progress of the application at a coarse-grained level.

• WARNING- potentially harmful situations.

[logger_root]

handlers=file

level=INFO



6.3.1 Maximum log file size and rollover policy

By default, the maximum log file size is 10240000 bytes (10.24 MB). When a log file reaches this size, the log file will be backed up and a new log file will be created. The maximum num-ber of log files that are kept is 100,000.

To change the maximum size of the log file, change the value of the third parameter of args. to the appropriate value:

To change the maximum number of log files that are kept, change the value of the fourth parameter of args to the appropriate value:

[handler_file]

class=PasCommandsRotatingFileHandler.PasCommandsRotatingFileHandler

formatter=simple

args=('pas-commands.log','a',10240000,100000)

[handler_file]

class=PasCommandsRotatingFileHandler.PasCommandsRotatingFileHandler

formatter=simple

args=('pas-commands.log','a',10240000,100000)



6.4 Changing the Linux SSH Server or Port

This release of PAS incorporates Access Management Service (AMS), a centralized configu-ration system for authentication and authorization. For more information about AMS see sec-tion 2.4, “Access Management Service”, on page 17.

Authentication information is stored in the file AA_jaas.config. The location of the file for a typical installation of PAS is:

on Windows : C:\Program Files\altair\pas\13.0\PAS\home\conf\AAService-Home\config

on Linux : /var/spool/pas/conf/AAServiceHome/config

To change the SSH server or the SSH port, edit the AA_jaas.config file.

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

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

3. Restart the PAS service.

LoginModule {

com.altair.jaas.module.SSHUnixLoginModule Required

host="<SSH_SERVER>"

cache_ttl="60";

};

Super_User_Login {

com.altair.jaas.module.DatastoreLoginModule Required;

};

UnixLogin {

com.altair.jaas.module.JschLoginModule required;

};



6.5 Configuring JVM Performance

The Java Virtual Machine (JVM) heap size of PAS may need to be adjusted. Currently, the default JVM heap size is 1024 MB. If OutOfMemory errors or warnings are reported in the PAS log file, this value should be increased. It can be increased in multiples of 256 MB.

On Linux, the Java heap size default is stored in a script file called pas-server-start.sh. The location of this file for a typical installation of PAS is:

/opt/altair/pas/13.0/pas/scripts

The variable that needs to be changed is CATALINA_OPTS. Modify the JVM argument -Xmx1024m. Increase the "1024" value.

This is the area of pas-server-start.sh that will need to be modified (this file is too large to show in its entirety):

For Windows platforms, the same JVM argument, -Xmx1024m, in the following registry entry must be modified:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Pro-crun 2.0\PBSAppSvcs\Parameters\Java

The PAS service will need to be restarted for the changes to be reflected.

CATALINA_OPTS="-Dpass -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=128m -Djava.library.path=$PAS_EXEC/shared/$AIF_PLATFORM -Djava.security.auth.login.config=$PAS_HOME/conf/jaas.config -Dpas.exec=$PAS_EXEC -Dpas.eifl.port=18080 -Dpas.eifl.usebroker=true"


Chapter 7

Log files

7.1 PAS log file

The PBS Application Services log file, pas-server.log, contains a record of server activities and is useful for identifying issues and problems. The location of the log file for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\home\logs

on Unix/Linux: /var/spool/pas/logs

7.2 PAS Commands log file

The PAS Commands log file, pas-server.log, is used for identifying and resolving issues with PAS Commands. The log file is located on the machine where PAS Commands is installed, and its location for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\home\pas-com-mands\logs

on Unix/Linux: /var/spool/pas/pas-commands/logs/pas-commands.log


Chapter 7 Log files

7.3 FSP file

The FSP log file, fsp-server.log, contains a record of server activities and is useful for identifying issues and problems. The location of the log file for a typical installation of FSP is:

on Windows: C:\Program Files\altair\fsp\13.0\FSP\home\logs

on Unix/Linux: /var/spool/fsp/logs

7.4 Other log files

The PAS installation log file is located in:

<INSTALL_DIR>/_PBS Application Services_installation/Logs

The log files for the Apache Tomcat web server are located in:

<INSTALL_DIR>/pas/bin/pas-server/logs


Chapter 8

PAS service commands

8.1 Starting the PAS service

8.1.1 Windows

As the Windows Administrator open Windows Services:

1. Click Start

2. Click Control Panel

3. Double-click Administrative Tools

4. Double-click Services

5. Right-click on the service PBS Application Services.

6. Click the Start option.

Once the service is started, the status of the service will be displayed as Started.

8.1.2 Linux

As root, enter the following at the Linux command line prompt:

/etc/init.d/pas start


Chapter 8 PAS service commands

The following messages will be displayed:

8.2 Stopping the PAS service

8.2.1 Windows


1. Click Start





6. Click the Stop option.

8.2.2 Linux


/etc/init.d/pas stop


Starting PAS server

Using CATALINA_BASE: /opt/altair/pas/13.0/pas/bin/pas-server

Using CATALINA_HOME: /opt/altair/pas/13.0/thirdparty/Apache

Using CATALINA_TMPDIR: /opt/altair/pas/13.0/pas/bin/pas-server/temp

Using JRE_HOME: /opt/altair/pas/13.0/thirdparty/Java/jre1.7

Using CLASSPATH: /opt/altair/pas/13.0/thirdparty/Apache/bin/bootstrap.jar:/opt/altair/pas/13.0/thirdparty/Apache/bin/tomcat-juli.jar

PAS server started, pid: 30996

Stopping PAS server

PAS server stopped, was pid: 24604


PAS service commands Chapter 8

8.3 Restarting the PAS service

8.3.1 Windows


1. Click Start





6. Click the Restart option.


8.3.2 Linux


/etc/init.d/pas restart


Restarting PAS server

Stopping PAS server

PAS server stopped, was pid: 30996

Starting PAS server

Using CATALINA_BASE: /opt/altair/pas/13.0/pas/bin/pas-server

Using CATALINA_HOME: /opt/altair/pas/13.0/thirdparty/Apache

Using CATALINA_TMPDIR: /opt/altair/pas/13.0/pas/bin/pas-server/temp

Using JRE_HOME: /opt/altair/pas/13.0/thirdparty/Java/jre1.7

Using CLASSPATH: /opt/altair/pas/13.0/thirdparty/Apache/bin/bootstrap.jar:/opt/altair/pas/13.0/thirdparty/Apache/bin/tomcat-juli.jar

PAS server started, pid: 31221


Chapter 8 PAS service commands

8.4 Determining the status of the PAS service

8.4.1 Windows


1. Click Start




Scroll down the list of services until you find PBS Application Services.

The status of the service will be displayed as Started if PBS Application Services is running. The status of the service will not be displayed if PBS Application Services is not running..

8.4.2 Linux


/etc/init.d/pas status

If the service is running, the following messages will be displayed:

f the service is not running, the following messages will be displayed:

PAS server is running with pid: 31825

PAS server is not running.


Chapter 9

Application DefinitionsPBS Application Services requires a predefined set of instructions, called application defini-tions, 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 flexi-ble set of instructions that can be manipulated to allow for precise control over all aspects of application-specific parameters and job execution. These application definitions are stored in a central repository and will make PBS Professional aware of each of them upon server startup. The location of the application directory for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\home\reposi-tory\applications


9.1 Overview of Application Definition Components

An application definition is comprised of a set of Python scripts and two XML files which could include references to site wide configuration settings. A separate application definition with application-specific details is required for each application that will be integrated into PBS Application Services. Application definitions are compliant with the Open Grid Forum High Performance Computing Basic Profile (HPCBP), Business Process Execution Language (BPEL), and Job Submission Description Language (JSDL) standards.

For more comprehensive information about application definitions and their associated files see Diving Into Application Definitions 13.0.


Chapter 9 Application Definitions

9.1.1 Application input file

The application input file is where administrators can define the allowed arguments for a given application. This file is also used by graphical, web-based and even command-line tools to display these arguments to users for job submission.

The mandatory naming convention for the application input file is app-inp-applica-tionname.xml where "applicationname" is whatever name you choose to give your appli-cation.

9.1.2 Application converter file (HPCBP converter)

The application converter file is where administrators take the values received by the user via the input file and communicates this information to PBS Application Services and PBS Pro-fessional. This file allows the PBS Application Services administrator to configure the job submission environment.

The mandatory naming convention for the application converter file is app-conv-appli-cationname.xml where "applicationname" is whatever name you decide to give to your application.

9.1.3 Application runtime scripts

The application runtime scripts are what really get executed on the execution hosts. The run-time script, start.py, is what will be executed as the “job script”. This script file is respon-sible for executing the application associated with your application definition, using the information entered by the user (defined by the application input file), and converted (via the application converter file). Additional scripts can also be included that support and enhance the runtime script. Administrators can directly edit these runtime script(s), taking full advan-tage of Python to add further inspection and complexity to job submission and finally execu-tion of the application itself. This adds tremendous flexibility as nearly infinite possibilities for job control exist at this phase of job description.

For information about how to use runtime scripts see the tutorials “Enhancing your Applica-tion with Runtime Scripts” and “Executing Actions on a Running Job” and the Recipes sec-tion in Diving Into Application Definitions 13.0.

9.1.4 Site configuration file

The site configuration file, site-config.xml, is meant to make application definitions more portable by consolidating data that may change from cluster to cluster in a central loca-tion (see section 9.4, “Sitewide Settings”, on page 99 for more information pertaining to the


Application Definitions Chapter 9

site configuration file). It is where administrators can define things like policies, version, and path information for all the available applications, billing account information, etc. The data in this file is used by the application input and converter files. For information on how to ref-erence the site configuration file in an application definition see the tutorial “Allowing Multi-ple Versions of an Application”, and recipes “How to Configure and Use Billing Accounts” and “How to Configure and Use Site Policies” in Diving Into Application Definitions 13.0.

9.2 Sample application definition PBSJobApp

PBS Application Services provides a sample application definition, PBSJobApp, which is located in the application definition directory.

PBSJobApp is an example of how an administrator could create an application definition enabling users to use custom job scripts akin to the more common PBS Professional job script. PBSJobApp allows these job scripts to be written in any language by using its runtime script, start.py, to parse the first line (shebang line) to determine the correct interpreter to execute your job script against. PBSJobApp's versatility allows the following:

• extra arguments to be passed to the job script

• specification of advanced multi-node placement options

• the inclusion of additional files

This application definition in conjunction with the Diving Into Application Definitions 13.0 documentation will assist administrators to create and deploy application definitions.

9.3 Administration of Application Definitions

The PBS Application Services has a central location for keeping application definitions and will make PBS Professional aware of each of them upon server startup. The location of the application definition files for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\home\repos-itory\applications




9.3.1 Adding a new application definitions

Adding an application definition to the applications directory, followed by a restart of PBS Application Services, will expose your application definition to the user, as well as notify PBS Professional. Follow these steps to add an application definition:

• Navigate to the applications directory.

• Create a directory called appname (where appname is the name of the application).

• Place the application definition input file (applapp-inp-appname.xml) and the application definition converter file (app-conv-appname.xml) in the application directory.

• Create a subdirectory called runtime and navigate to that subdirectory.

• Place any runtime scripts into the runtime directory.

• Restart the PBS Application Services server.

9.3.2 Application definition validation

When the PBS Application Services server starts, it performs a validation of the existing application definitions. If application definitions fail to meet key criteria, they will be moved to an invalid application directory. The directory will be created if it does not exist. The loca-tion of this directory for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\home\repos-itory\invalid_applications

on Unix/Linux: /var/spool/pas/repository/invalid_applications

In addition, PBS Application Services will restore the site configuration file from the last valid backup - site-config.backup.

Error messages will be displayed in the PBS Application Services log file indicating why the application definition was invalid. Invalid application definitions can be retrieved from the invalid_applications directory and modified to meet the criteria necessary to be con-sidered valid. An invalid application definition will not prevent the PBS Application Services server from starting up.

9.3.3 Maintenance of existing application definitions

Existing application definitions can be modified or removed. To make PBS Application Ser-vices aware of the modification or the removal of an application definition, restart the PBS Application Services server.



9.3.3.1 Update an Application Definition

You can easily modify an existing application definition using your favorite XML editor. Fol-low these steps to modify an application definition:


• Edit and make any modifications necessary to the application definition files.

• Restart the PBS Application Services server:

9.3.3.2 Remove an Application Definition

Removing an application definition from PBS Application Services is also very simple. Sim-ply remove the application definition directory and restart PBS Application Services to remove your application definition from both PBS Application Services and PBS Profes-sional. Follow these steps to remove an application definition:


• Remove the application directory and all of its content including the runtime subdirec-tory and associated files.

• Restart the PBS Application Services server:

9.4 Sitewide Settings

PBS Application Services provides a central repository for site specific information such as executable paths, policies, and billing account information. This information is stored in a site configuration file, site-config.xml. By putting some site specific application infor-mation in the site-config.xml, application definitions can be made more portable and reusable among different PBS Professional complexes: for example, putting binaries locations and version availability information here, makes the rest of the application definition reusable on a different cluster just by modifying that cluster's site-config.xml. The location of this file for a typical installation of PBS Application Services is:

on Windows: C:\Program Files\altair\pas\13.0\PAS\home\reposi-tory

on Unix/Linux: /var/spool/pas/repository



9.4.1 Site configuration file content

This file can hold virtually any sort of information, since the information stored in the file can be referenced by any application definition XML file. Altair has included certain data in the site configuration file for the integration and support of other products from the PBS Profes-sional family. The example below shows a sample of the site configuration file with the sec-tions currently used by the PBS Professional product suite:

• Applications - This section holds application specific information.

• Application versions - For each application, you can insert site supported versions and for each version its binary pathname.

• Job projects (billing accounts) - This section is for integrating PBS Application Services with other products from Altair. Here you can list a set of strings to be used as “account-ing” information to be attached to jobs.

• Policies - Site policies are values that can be used in a site’s application definition XML files and/or as values available in job runtime environment (policies are included as envi-ronment variables for the jobs).


P 101

Chapter 9

9

A PBSJobApp, an application definition t ll need to be updated according to your s

<

<

s/site-config.xsd">

<


Application Definitions

.4.1.1 Initial site configuration file after installation of PAS

fter installation of PBS Application Services the site configuration file will contain references to hat is provided out-of-the-box. Placeholders for billing accounts and policies are provided, but wiite specifications.

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

SiteConfiguration xmlns="http://schemas.altair.com/pbs/2007/01/site-config"

xmlns:site-config="http://schemas.altair.com/pbs/2007/01/site-config"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://schemas.altair.com/pbs/2007/01/site-config ../schema

<Applications>

<Application id="PBSJobApp">

<ApplicationVersions/>

</Application>

</Applications>

<JobProjects id="BILLING_ACCOUNT"/>

<Policies/>

/SiteConfiguration>

C


9

H sions, billing accounts, and policies:

<

< g.xsd">

<

hapter 9 Application Definitions

02 PBS App

.4.1.2 Sample of a site configuration file

ere is an example of a site configuration file with modifications for site supported application ver

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

SiteConfiguration xmlns="http://schemas.altair.com/pbs/2007/01/site-config" xmlns:site-config="http://schemas.altair.com/pbs/2007/01/site-config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.altair.com/pbs/2007/01/site-config ../schemas/site-confi <Applications> <Application id="PBSJobApp"> <ApplicationVersions/> </Application> <Application id="Optistruct"> <ApplicationVersions> <ApplicationVersion> <Option>8.0</Option> <Executable>/opt/hyperworks/11.0/altair/scripts/optistruct</Executable> </ApplicationVersion> <ApplicationVersion> <Option>9.0</Option> <Executable>/sw/optistruct9/optistruct</Executable> </ApplicationVersion> </Application> </Applications> <JobProjects id="BILLING_ACCOUNT"> <Option>Company1</Option> <Option>Company2</Option> </JobProjects> <Policies> <Policy> <Option>MAX_CPUS</Option> <Value>4</Value> </Policy> <Policy> <Option>MPIPROCS</Option> <Value>4</Value> </Policy> </Policies>

/SiteConfiguration>


9.4.2 Using site configuration information in an application definition

For information on how to reference the site configuration file in an application definition see the tutorial “Allowing Multiple Versions of an Application”, and recipes “How to Configure and Use Billing Accounts” and “How to Configure and Use Site Policies” in Diving Into Application Definitions 13.0.

9.4.3 Site configuration file backup

Upon server start-up, PBS Application Services will validate the content of the site configura-tion file (section 9.4.4, “Site configuration file validation”, on page 104), and the content of application definitions (section 9.3.2, “Application definition validation”, on page 98):

If the content of both the site configuration file and application definitions is valid:

• The site configuration file will be backed up to a file called site-config.backup.

If the content of either the site configuration file or any application definition is invalid:

• The site configuration file will be backed up to a file called site-con-fig.YYYYMMDDMMSS where YYYYMMDDMMSS is the file cre-ation timestamp.

• The site configuration file will be restored from the last valid backup, site-con-fig.backup.

Up to five (5) backups will be maintained. All backup files will be maintained in the same directory as the site configuration file.



9.4.4 Site configuration file validation

Upon server startup, PBS Application Services validates the site configuration file. It is vali-dated against its XML schema. An XML schema defines the legal building blocks of a partic-ular XML document. An XML schema:

• defines elements that can appear in a document

• defines attributes that can appear in a document

• defines which elements are child elements

• defines the order of child elements

• defines the number of child elements

• defines whether an element is empty or can include text

• defines data types for elements and attributes

• defines default and fixed values for elements and attributes

The validation process also determines if the content of the site configuration file is well-formed (valid). The content is well-formed if the following criteria is met:

It must have a root element.

• XML elements must have a closing tag.

• XML tags are case sensitive.

• XML elements must be properly nested.

• XML attribute values must be quoted.


Chapter 10

Reserved wordsThe table below illustrates the reserved words used by PBS Application Services. The reserved words enable unification of application definitions and automatic rendering of GUIs based on these definitions.

The following list of reserved words are identified.

Table 10-1: PBS Application Services Reserved Words

Reserved Word Description

BILLING_ACCOUNT PBS Professional "account" attribute

CHUNK PBS Professional "requested chunks count" attribute

CPUTIME PBS Professional "cput" attribute

EXECUTABLE path to application executable

JOB_NAME PBS Professional "job_name" attribute

MASTER master file

MEMORY PBS Professional "mem" attribute

NCPUS PBS Professional "ncpus" attribute

PYTHON_PATH Python Interpreter

QUEUE PBS Professional "queue" attribute

SOFTWARE PBS Professional "software" attribute


Chapter 10 Reserved words

SUBMISSION_DIRECTORY job submission directory

VERSION application version

VMEMORY PBS Professional "vmem" attribute

WALLTIME PBS Professional "walltime" attribute

Table 10-1: PBS Application Services Reserved Words

Reserved Word Description


Chapter 11

Uninstalling PAS GUI modeStop the PAS service (see section 8.2, “Stopping the PAS service”, on page 92).

11.1 Starting the uninstaller

11.1.1 Linux

Navigate to the PBS Application Services execution directory. The execution directory for a typical installation of PAS is

/opt/altair/pas/13.0

Enter the following at the Linux/Unikx command line prompt (command must contain spaces with escape characters):

cd _PBS\ Application\ Services_installation

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

./Change\ PBS\ Application\ Services\ Installation -i swing

11.1.2 Windows

As the Windows Administrator navigate to Start > Control Panel > Programs and Fea-tures. Scroll down until you find the PBS Application Services application. Right-click the PBS Application Services application, and then click Uninstall/Change.


Chapter 11 Uninstalling PAS GUI mode

11.2 Initiate the PAS uninstall process

Click Next to start the uninstall process.


Uninstalling PAS GUI mode Chapter 11

11.3 Uninstall PBS Application Services

Click Uninstall to initiate the uninstallation process.


Chapter 11 Uninstalling PAS GUI mode

11.4 Complete uninstall

A message is displayed once the uninstall process is complete. Any items that could not be removed will be listed. Please take a moment to manually remove them. To complete the uninstall, click Done.


Chapter 12

Uninstalling PAS console modeStop the PAS service (see section 8.2, “Stopping the PAS service”, on page 92).


Navigate to the PBS Application Services execution directory. The execution directory for a typical installation of PAS is

/opt/altair/pas/13.0

Enter the following at the Linux/Unikx command line prompt (command must contain spaces with escape characters):

cd _PBS\ Application\ Services_installation


./Change\ PBS\ Application\ Services\ Installation


Chapter 12 Uninstalling PAS console mode

12.2 Initiate the PAS uninstall process

Press <ENTER> to start the uninstall process.


A message will be displayed indicating the uninstall has begun. Once the uninstall is com-plete a message is displayed indicating any items that could not be removed will be listed. Please take a moment to manually remove them..


Chapter 13

Troubleshooting

13.1 The package doesn’t match the OS

Question: I get a The package doesn’t match the OS error message, what do I do?

Answer: This error indicates that you are trying to use an installation binary or executable for a platform that does not match the operating system of the machine onto which you are trying to install PBS Application Services. For instance, you might have used the installation binary PBSAppSvcs_13.0_RHEL-6_x86_64_20130606_0725.bin to install PBS Application Ser-vices on a server that is running CentOS 6. Please download the installation binary/execut-able that matches your platform.

13.2 PBS Professional Server is not installed

Question: I get a PBS Professional Server is not installed warning message, what do I do?

Answer: The installation process has determined that PBS Professional is not installed. It is highly recommended to install PBS Professional prior to installing PBS Application Services. PBS Application Services can be installed without an existing installation of PBS Profes-sional, however some file operations functionality will not be available for jobs that are sub-mitted directly to PBS Professional via the command line.


Chapter 13 Troubleshooting

13.3 Incompatible version of PBS Professional detected

Question: I get an Incompatible version of PBS Professional error message, what do I do?

Answer: The installer has detected that you are installing PBS Application Services with an incompatible version of PBS Professional. Currently, PBS Professional 11.3 and greater is supported. The installation cannot continue and will abort. Make sure you have PBS Profes-sional version 11.3 or greater installed. Execute the following PBS Professional command from a command prompt and look for the pbs_version attribute to determine which version of PBS Professional is installed:

qstat -Bf Server: hwesuse113-01 server_state = Active server_host = hwesuse113-01.prog.altair.com scheduling = True total_jobs = 1 state_count = Transit:0 Queued:1 Held:0 Waiting:-1 Running:1 Exiting:0 Begu n:0 managers = pbsadmin@* default_queue = workq log_events = 511 mail_from = adm query_other_jobs = True resources_default.ncpus = 1 default_chunk.ncpus = 1 resources_assigned.mem = 0mb resources_assigned.ncpus = 1 resources_assigned.nodect = 1 scheduler_iteration = 600 FLicenses = 3333332 resv_enable = True node_fail_requeue = 310 max_array_size = 10000 pbs_license_info = 6200@trlicsrv03 pbs_license_min = 1 pbs_license_max = 2147483647 pbs_license_linger_time = 31536000 license_count = Avail_Global:3333321 Avail_Local:11 Used:1 High_Use:12 Avai l_Sockets:0 Unused_Sockets:0 pbs_version = PBSPro_11.3.0.121703 eligible_time_enable = False job_history_enable = True job_history_duration = 14:00:00 max_concurrent_provision = 5


Troubleshooting Chapter 13

13.4 Staging Directory is blank

Question: I get a Staging Directory is blank warning message, what do I do?

Answer: The staging directory is where the necessary files are transferred after job submis-sion, but prior to the portal submitting the job to PBS Application Services for transfer to PBS Professional for execution. This staging directory must exist for the installation to complete successfully. Please enter a pathname to an existing directory which will be designated as the PAS staging directory.

13.5 Could not detect “userid” (Linux/Unix)

Question: I get a Could not detect “userid” message, where “userid” is the PAS service user, what do I do?

Answer: This error condition will only occur on Linux/Unix platforms. The userid that was entered as the PAS service user is not an existing user account on the server where PAS is being installed. The PAS service user must be an existing account.

13.6 Could not connect Windows AD/DNS Server (Windows)

Question: I get a Could not connect Windows AD/DNS Server error message, what do I do?

Answer: On Windows platforms, the PAS installation process first checks the existence of the service account at the domain level. If it is unable to contact the Windows AD/DNS server, then this message will be displayed. Please verify that the AD/DNS server is up and running and that there are no network issues.

Secondly, if the service account does not exist at the domain level, then the installation pro-cess checks for its existence at the local level. If it does not exist at the local level, then the following message will be displayed Specified service user name does not exist - see section 13.7, “Specified service user name does not exist (Windows)”, on page 116



13.7 Specified service user name does not exist (Windows)

Question: I get a Specified service user name does not exist error message, what do I do?

Answer: The service account does not exist at either a domain or a local level for the userid entered. Verify that the service account has been created, or enter a different userid. Please refer to the information contained in section 6.1, “Configurable parameters”, on page 74 per-taining to the ADMIN_USER.

13.8 Password is required to continue (Windows)

Question: I get an Password is required to continue error message, what do I do?

Answer: You must enter the password of the PAS service user to proceed with the installa-tion.

13.9 PBS Professional installation appears to be incomplete

Question: I get a PBS Professional installation appears to be incomplete warning message, what do I do?

Answer: This error condition occurs when the <PBS_HOME>/server_priv/hooks directory is missing. This directory is created during the installation of PBS Professional. Please verify and correct the installation of PBS Professional. Once the issue is resolved, and an existing <PBS_HOME>/server_priv/hooks directory exists, copy the files located in <PAS_EXEC>/pas/unsupported/pbs-hooks to <PBS_HOME>/server_priv/hooks.

13.10 EIFL server ports in the default range is not available

Question: I get an EIFL server ports in the default range is not available error message, what do I do?



Answer: The EIFL server requires at least 50 ports within the range of 18080-18180. If less than 50 ports are available, then this error condition occurs. At least 50 ports must be freed within the default range to install PAS.

13.11 PAS server port is not free for installing PAS service

Question: I get a PAS server port is not free for installing PAS service error message, what do I do?

Answer: The default port used to communicate with PAS is 17084 (PAS release 11.1). As of the 12.0 release, the port will be selected dynamically during installation. If port 17084 is not available, then the installation process will increment the port number by one until an avail-able port is found. If an available port is not found after 100 attempts, the installation process will request the administrator to enter a port.

13.12 Specified port # is not a valid value

Question: I get a Specified port number is not a valid value error message, what do I do?

Answer: The installation process was unable to find an available port for PAS (see section 13.11, “PAS server port is not free for installing PAS service”, on page 117). Please enter a free port number to be used for communication with PAS within the range 1-65535.

13.13 The PAS server IP/port number is blank

Question: I get a PAS server IP/port number is blank error message, what do I do?

Answer: This error condition will only occur during installation of PAS Commands Only. The server name and port number where PAS is installed must be provided.

13.14 PAS Service was unable to start

Question: I get a PAS Service was unable to start error message, what do I do?

Answer: An error occurred while starting PAS. Review the PAS log file for errors (see Chap-ter 7, "Log files", on page 89) and contact system support.



13.15 PAS Service was unable to install

Question: I get a PAS Service was unable to install error message, what do I do?

Answer: An error occurred while installing PAS. Review the PAS installation log file for errors (see Chapter 7, "Log files", on page 89) and contact system support.

13.16 Installer not running as root/admin user

Question: I get an Installer not running as root/admin user error message, what do I do?

Answer: Ensure that you are installing PBS Application Services as root on Linux/Unix plat-forms or as an administrative user on Windows platforms.

13.17 Existing instance of Python found (Windows)

Question: I get an Existing instance of Python found error message, as shown below, what do I do?

Answer: On Windows platforms, uninstall the existing Python installation and restart the PBS Application Services installation.

13.18 License server information not provided

Question: I get a License server information not provided warning message, as shown below, what do I do?

Answer: You may install PBS Application Services without supplying a license server during installation time. You may later configure the license server. Please refer to the information contained in the section 6.1, “Configurable parameters”, on page 74 pertaining to the ALTAIR_LICENSE_PATH.



13.19 Manage Instances

Question: After launching the installer I get the following message:

What do I do?

Answer: An instance of PAS is still installed. You must uninstall any previously installed versions of PAS, before installing a new version of PAS.

To uninstall the existing instance of PAS, choose Modify an Existing Instance and click OK. The uninstallation process will initiate. Once the uninstall is complete, you will need to launch the installer a second time to install PAS.

If after uninstalling PAS this error persists, view the contents of the hidden file .com.zerog.registry.xml. On Linux/Unix platforms, this file will be located in the following directory:

/var

On Windows platforms, this file will be located in:

C:\Program Files\Zero G Registry



Whenever an Altair product is installed on a machine, the installation process appends infor-mation to this file. View the contents of this file for any existing installations of PAS. The following example shows an installation of PAS that is located at /opt/altair/pas2/12.1.

Navigate to the installation location and uninstall PAS - see Chapter 11, "Uninstalling PAS GUI mode", on page 107 or Chapter 12, "Uninstalling PAS console mode", on page 111.

If the installation location does not exist, or after launching the uninstall process, it is unable to complete successfully, edit the .com.zerog.registry.xml file. Remove all <prod-ucts> references of “PBS Application Services. For example:

Also remove any <component> references having the same installation location (loca-tion=”<INSTALL_LOC>”). For example:

<product name="PBS Application Services" id="c42daab7-1f0c-11b2-a949-8b152e999552" version="12.1.0.0" copyright="2012" info_url="" support_url="" location="/opt/altair/pas2/12.1" last_modified="2013-06-04 12:27:15">

<products>

<product name="PBS Application Services" ................. location="<INSTALL_LOC>"..................>

......

......

......

</product>

</products>

<components>

<component id=...........location="<INSTALL_LOC>/jre">

<component id=...........location="<INSTALL_LOC>/pas.conf.unix"/>

<component id=...........location="<INSTALL_LOC>/_PBS Application Services_installation/Change PBS Application Services Installation"/>

......

......

......

</component>

</components>



Launch the install process again. The Manage Instances message should not be displayed again.

13.20 Out of Memory Errors

Question: There are OutOfMemoryErrors in the PAS server log what do I do?

Answer: You may need to adjust the Java Virtual Machine (JVM) heap size of PAS. See sec-tion 6.5, “Configuring JVM Performance”, on page 88. Out of memory errors can indicate a underlying problem, therefore it is recommended to report these errors to PAS system support.

13.21 IOException: No such file or directory

Question: Our site has implemented load balancing for PBS Works. The following error is showing up in the PAS server log, what do I do?

ERROR gw.aif.pbs.admin.resources.ApplicationsResources (ApplicationsResources.java:210) - IOException java.io.IOException: No such file or directory

Answer: Edit the PAS server configuration file, server.conf, and add the following entry:

Restart the PAS service.

SERVER_ROLE_SECONDARY=true



13.22 Job Fails with “Bad UID” exception

Question: Our site has installed PAS on a separate machine from the one hosting the PBS Professional Server. When a user submits a job, the job fails with a “Bad UID for job execu-tion” exception. What do I do?

Answer: The PBS Professional flatuid attribute must be set to True. This attribute specifies whether, for each user, the username at the submission host must be the same as the one at the Server host. The username at the Server host must always be the same as the username at the execution host. When flatuid is set to True, the Server assumes that UserA@host1 is the same as UserA@host2. Therefore, if flatuid is True, UserA@host2 can operate on UserA@host1’s job. Follow these steps to set flatuid to True:

1. Log into the machine hosting the PBS Professional Server.

2. At the command line, enter the command:

Qmgr: print server

3. If the attribute flatuid is equal to False or is not set (you do not see it in the output from the print server command), then set the value to True by issuing the command:

Qmgr: set server flatuid = True

13.23 Job Fails with “Unknown Resource” exception

Question: Our site has installed PAS on a separate machine from the one hosting the PBS Professional Server. When a user submits a job, the job fails with a “Unknown resource Resource_List.xxxxxx” exception. What do I do?

Answer: Resources required by PAS have not been defined to PBS Professional. Add the required PAS resources to the PBS Professional resource definition file. For more informa-tion see section 5.9, “Configuring PBS resources”, on page 68.



13.24 PAS Command connection error

Question: Whenever a PAS Command is executed the following error message is displayed: "Connection error to PAS server: (1, 'error:100AE081:elliptic curve rou-tines:EC_GROUP_new_by_curve_name:unknown group')". What do I do?

Answer:

This issue is due to a bug in the version of OpenSSL installed at your site. More information about this bug can be found at https://www.centos.org/forums/viewtopic.php?f=14&t=43803. Updating OpenSSL solves this problem. Run the following command to update OpenSSL to the proper version:

If the OpenSSL developer’s package is also installed at the client's site, it should be upgraded as well. Run the following command to update the OpenSSL developer package:

rpm -Uvh openssl-1.0.1e-30.el6_6.5.x86_64.rpm --nodeps

rpm -Uvh openssl-devel-1.0.1e-30.el6_6.2.x86_64.rpm --nodeps


https://www.centos.org/forums/viewtopic.php?f=14&t=43803

Chapter 14

File Service ProviderFile Service Provider or FSP is a mechanism for executing remote file operations on the PBS Professional execution hosts. FSP removes the dependency upon PBS Professional for remote file operations and file transfers. Additionally, FSP increases the speed of Compute Manager file operations during job execution time by a factor of 1.5-3 depending upon the file operation.

The following operations are available using FSP:

• Create and delete a directory

• Compress and uncompress a file

• Copy, move, and delete a file

• Determine if a file exists

• Read, write, list, and search a file

• Replace data contained within a file

• Execute a script

• Upload and download a file


Chapter 14 File Service Provider

14.1 Supported Platforms

FSP is supported on the following platforms:

• Novell SUSE Linux Enterprise Server (SLES) 10.X, 11.X, and 12.x on x86_64

• Red Hat Enterprise Linux (RHEL) 5, 6, and 7 (server and desktop) on x86_64


• Windows Server 2008 R2 on x86_64


• CentOS 6 and 7 on x86_64

14.2 System Requirements

14.2.1 Minimum Hardware Requirements

Table 14-1: Minimum hardware rqmts

Hardware Requirement

CPU 1

Memory (Physical) 256 MB

Disk Space 600 MB


File Service Provider Chapter 14

14.3 Installation Considerations

It is necessary to install FSP on every PBS Professional execution host. The default port used for FPS is 17185. If port 17185 is not available, the installation process will request a port to be used for the FSP service. If the default port is changed during installation, then all instances of FSP must use the same port.

Once the FSP is installed, it will be started automatically during system start-up and the FSP service will run under root or the Windows Administrator account.

For information about installation procedures see Chapter 15, "Installing FSP GUI mode", on page 137 or Chapter 16, "Installing FSP console mode", on page 149.

14.4 Integration Considerations

To use FSP to provide remote file operations on the PBS Professional execution hosts, PAS 13.0 must be installed and configured to communicate with FSP. For more information about configuring PAS see section 5.10, “Configuring the File Service Provider”, on page 70.



14.5 Software Organization

The directory structure of FSP is similar to PAS with a HOME and EXEC directory:

14.5.1 Windows

The FSP home directory (FSP_HOME) and the execution directory (FSP_EXEC) can be determined by viewing the FSP configuration file located in:

C:Program Files\altair\fsp\13.0\FSP\init\fsp.conf


FSP_HOME=$USER_INSTALL_DIR$\fsp\home

FSP_EXEC=$USER_INSTALL_DIR$\fsp\exec

FSP_SERVER=$FSP_SERVER_IP_ADD$

FSP_PORT=$FSP_SERVER_PORT$



14.5.2 Linux/Unix

For a typical Linux/Unix installation, FSP is installed in the following location:

FSP home directory: /var/spool/fsp

FSP execution directory: /opt/altair/fsp/13.0/fsp

FSP configuration and services directory: /etc

The FSP home directory (FSP_HOME) and the execution directory (FSP_EXEC) can be determined by viewing the FSP configuration file located in:

/etc/fsp.conf


FSP_HOME=/var/spool/fsp

FSP_EXEC=/opt/altair/fsp/13.0/fsp

FSP_SERVER=localhost

FSP_PORT=17185


C


1

T d server.conf. The location of this f

A ng quotes around values is optional. As s intentional. Empty lines beginning with a

Default Value

config-ing and g4J via

og4j

server-log.xml

end his can

false

entica-ion

Linux: UnixLogin

Windows: WindowsLogin

hapter 14 File Service Provider

30 PBS App

4.6 FSP configurable parameters

he FSP Server has several configurable parameters. FSP stores its configuration data in a file calleile for a typical installation of FSP is:

on Windows: C:\Program Files\altair\fsp\13.0\FSP\home\conf

on Linux: /var/spool/fsp/conf

ll parameters are stored in key=value pairs. Spaces and tabs are preserved (as spaces) and providipaces are preserved, do not use key = value (notice the space surrounding the =) unless spaces are comment symbol (ie. #) are ignored.

Table 14-2: FSP configuration Parameters


LOGGING_CONFIG_FILE_RELATIVE The logging configuration file (Log4J) which is used to ure logging levels. Since the FSP uses Log4J as its loggtracing API, you can access additional information on Lothe Apache Log4J website at http://logging.apache.org/l

DEBUG The FSP debugging property. If enabled true, FSP will sintermittent results to files stored in FSP_HOME/temp. Tbe an effective debugging mechanism.

LOGIN_MODULE_NAME The FSP authentication module. FSP uses the Java Authtion and Authorization Service (JAAS) as its authenticatabstraction layer.


14.7 Log Files

The FSP log file, fsp-server.log, contains a record of server activities and is useful for identifying issues and problems. The location of the log file for a typical installation of FSP is:

on Windows: C:\Program Files\altair\fsp\13.0\FSP\home\logs

on Unix/Linux: /var/spool/fsp/logs



14.8 Configuring FSP Server logging behavior

The FSP logging behavior can be defined in the file server-log.xml. The location of the file for a typical installation of PAS is:

on Windows : \C:\Program Files\altair\fsp\13.0\FSP\home\conf

on Linux : /var/spool/fsp/conf

The default logging level is set to “info” providing informational messages that highlight the progress of the application at a coarse-grained level.

To configure the level of logging, edit the server-log.xml file and set the <priority value> attribute of <category name="com.altair.gw.fsp.*"> to one of the following values:

• off - has the highest possible rank and is intended to turn off logging.

• fatal- very severe error events that will presumably lead the application to abort.

• error- error events that might still allow the application to continue running.

• warn- potentially harmful situations.

• info - informational messages highlighting the progress of the application at a coarse-grained level.

• debug- fine-grained informational events that are most useful to debug an application.

• trace - finer-grained informational events than the DEBUG.

• all - the lowest possible rank and is intended to turn on all logging..

Another debugging option is to configure FSP to create job resource dump files. Setting the FSP configuration parameter DEBUG to false (see section , “All parameters are stored in key=value pairs. Spaces and tabs are preserved (as spaces) and providing quotes around val-ues is optional. As spaces are preserved, do not use key = value (notice the space surrounding the =) unless spaces are intentional. Empty lines beginning with a comment symbol (ie. #) are ignored.”, on page 130), writes job resource dump files to the location <FSP_HOME>/temp. FSP will then log a reference to the dump file in the FSP log file. For example:

<category name="com.altair.gw.fsp.*">

<priority value="<logging_level>" />

</category>

“Created job resources dump: <file name>”



14.9 Starting the FSP service

14.9.1 Windows


1. Click Start




5. Right-click on the service File Service Provider.

6. Click the Start option.


14.9.2 Linux


/etc/init.d/fsp start


Starting FSP server

Using CATALINA_BASE: /opt/altair/fsp/13.0/fsp/bin/fsp-server

Using CATALINA_HOME: /opt/altair/fsp/13.0/thirdparty/Apache

Using CATALINA_TMPDIR: /opt/altair/fsp/13.0/fsp/bin/fsp-server/temp

Using JRE_HOME: /opt/altair/fsp/13.0/thirdparty/Java/jre1.7

Using CLASSPATH: /opt/altair/fsp/13.0/thirdparty/Apache/bin/bootstrap.jar:/opt/altair/fsp/13.0/thirdparty/Apache/bin/tomcat-juli.jar

FSP server started, pid: 6832



14.10 Stopping the FSP service

14.10.1 Windows


1. Click Start





6. Click the Stop option.

14.10.2 Linux


/etc/init.d/fsp stop


Stopping FSP server

FSP server stopped, was pid: 17661



14.11 Restarting the FSP service

14.11.1 Windows


1. Click Start





6. Click the Restart option.


14.11.2 Linux


/etc/init.d/fsp restart


Restarting FSP server

Stopping FSP server

FSP server stopped, was pid: 6832

Starting FSP server

Using CATALINA_BASE: /opt/altair/fsp/13.0/fsp/bin/fsp-server

Using CATALINA_HOME: /opt/altair/fsp/13.0/thirdparty/Apache

Using CATALINA_TMPDIR: /opt/altair/fsp/13.0/fsp/bin/fsp-server/temp

Using JRE_HOME: /opt/altair/fsp/13.0/thirdparty/Java/jre1.7

Using CLASSPATH: /opt/altair/fsp/13.0/thirdparty/Apache/bin/bootstrap.jar:/opt/altair/fsp/13.0/thirdparty/Apache/bin/tomcat-juli.jar

FSP server started, pid: 7339



14.12 Determining the status of the PAS service

14.12.1 Windows


1. Click Start




Scroll down the list of services until you find File Service Provider.

The status of the service will be displayed as Started if FSP is running. The status of the ser-vice will not be displayed if FSP is not running..

14.12.2 Linux


/etc/init.d/fsp status

If the service is running, the following messages will be displayed:

f the service is not running, the following messages will be displayed:

FSP server is running with pid: 7339

FSP server is not running.


Chapter 15

Installing FSP GUI modePAS 13.0 provides a custom mechanism for executing remote file operations on the PBS Pro-fessional execution hosts. This mechanism is called File Service Provider or FSP. FSP removes the dependency upon PBS Professional for file transfers.



• Existing user account to install the FSP service (default is pbsadmin)


To install FSP, download the installer executable appropriate for your platform from the user area.

15.1 Starting the installer


./FileServiceProvider_13.0_SLES-11.bin -i swing


FileServiceProvider_13.0_Windows_x86_64.exe


Chapter 15 Installing FSP GUI mode

15.2 FSP installation instructions



Installing FSP GUI mode Chapter 15

15.3 License Agreement




15.4 FSP service user

Enter a user that exists on the machine where FSP is being installed. The FSP service user will be used to register the FSP service. The default is “pbsadmin”. Once you have entered the user, click Next..


Installing FSP GUI mode Chapter 15

15.5 FSP service user password - Windows only

If you are installing FSP on a Windows platform, enter the FSP service user password. Click Next.



15.6 Authentication and Authorization

AMS provides a centralized configuration system for authentication and authorization.

If you have previously installed a PBS Works product and want to use the previously installed instance of AMS, then click Yes and enter the AMS Server IP/Hostname and the AMS Server Port Number.

Otherwise to use SSH for authentication on Linux platforms, or Windows authentication for Windows platforms, click No.

Click Next.


P 143

Chapter 15

1

S may select a custom directory by click-i cation is entered, click Next.

ows platforms


Installing FSP GUI mode

5.7 Installation location

pecify a location where FSP will be installed. You may install FSP in the default directory, or young Choose. To restore the default directory, click Restore Default Folder. Once an installation lo


C


1


ows platforms

hapter 15 Installing FSP GUI mode

44 PBS App

5.8 Pre-installation summary

pre-installation summary will be displayed. Review all your locations before initiating the instalack and make any changes. Install FSP by clicking Install.


P 145

Chapter 15

1

T he installation progress toolbar.



5.9 Installation progress

he installation of FSP will be initiated. You can monitor the progression of your installation via t


15.10 Start FSP services

Once the installation is complete a message will be displayed asking if the FSP services should be started. Click Yes to start FSP services. Click No to complete the installation with-out starting FSP services. To manually start FSP see section 14.9, “Starting the FSP service”, on page 133.

15.11 FSP client validation

If the FSP service was started, then the FSP server will be contacted and the following mes-sage should be displayed. Click OK to continue the installation.


P 147

Chapter 15

1

O mplete the installation

1

P ce Provider", on page 70) to configure P

ows platforms



5.12 Installation complete

nce the installation of FSP is complete the installation details will be displayed. Click Done to co

5.13 Post-installation

lease proceed to the PAS post-installation instructions (see Chapter 5, "Configuring the File ServiAS to use the FSP.


Chapter 16

Installing FSP console modePAS 13.0 provides a custom mechanism for executing remote file operations on the PBS Pro-fessional execution hosts. This mechanism is called File Service Provider or FSP. FSP removes the dependency upon PBS Professional for file transfers.



• Existing user account to register as the FSP account (default is pbsadmin)t


16.1 Starting the installer


./FileServiceProvider_13.0_SLES-11.bin -i swing


Chapter 16 Installing FSP console mode

16.2 FSP installation instructions


16.3 License Agreement



Installing FSP console mode Chapter 16

16.4 FSP service user

Enter a user that exists on the machine where FSP is being installed. The FSP service user will be used to register the FSP service. The default is “pbsadmin”. Once you have entered the user, press <Enter>. .



16.5 Authentication and Authorization

AMS provides a centralized configuration system for authentication and authorization.

If you have previously installed a PBS Works product and want to use the previously installed instance of AMS, then enter “1” and enter the AMS Server IP/Hostname and the AMS Server Port Number.

Otherwise to use SSH for authentication on Linux platforms, or Windows authentication for Windows platforms, click enter “2”.

Press <Enter>.

16.6 Installation location

Enter a directory where FSP will be installed and press <Enter>, or to accept the default directory, /opt/altair/fsp/13.0, just press <Enter>.


Installing FSP console mode Chapter 16

16.7 Pre-installation summary

A pre-installation summary will be displayed. Review all your locations before initiating the installation. You may enter “back” and press <Enter> to go back and make any changes. Install FSP by pressing <Enter>.

16.8 Start FSP services

A message will be displayed indicating the installation has begun. Once the installation is complete a message will be displayed asking if the FSP services should be started. Enter "1" and press <Enter> to start FSP. Enter "2" and press <Enter> to complete the installation without starting FSP. To manually start FSP see section 14.9, “Starting the FSP service”, on page 133.



16.9 FSP client validation

If the FSP service was started, then the FSP server will be contacted and the message "FSP client was installed successfully (Server <servername> on port number <portmumber> is up and running)" should be displayed. Press <Enter> to continue the installation.

16.10 Installation complete

An installation complete message will be displayed indicating your installation is complete. Press <Enter> to complete the installation.

16.11 Post-installation

Please proceed to the PAS post-installation instructions (see Chapter 5, "Configuring the File Service Provider", on page 70) to configure PAS to use the FSP.


Chapter 17

Uninstalling FSP GUI modeStop the FSP service (see section 14.10, “Stopping the FSP service”, on page 134).


17.1.1 Linux

Navigate to the FSP execution directory. The execution directory for a typical installation of FSP is:

/opt/altair/fsp/13.0

Enter the following at the Linux/Unix command line prompt (command must contain spaces with escape characters):

cd _File\ service\ provider_installation


./Change\ File\ service\ provider\ Installation -i swing

17.1.2 Windows

As the Windows Administrator navigate to Start > Control Panel > Programs and Fea-tures. Scroll down until you find the File Service Provider application. Right-click the File Service Provider application, and then click Uninstall/Change.


Chapter 17 Uninstalling FSP GUI mode

17.2 Initiate the FSP uninstall process

Click Next to start the uninstall process.


Uninstalling FSP GUI mode Chapter 17

17.3 Uninstall FSP

Click Uninstall to initiate the uninstallation process.


Chapter 17 Uninstalling FSP GUI mode


A message is displayed once the uninstall process is complete. Any items that could not be removed will be listed. Please take a moment to manually remove them. To complete the uninstall, click Done.


Chapter 18

Uninstalling FSP console modeStop the FSP service (see section 14.10, “Stopping the FSP service”, on page 134).


Navigate to the FSP execution directory. The execution directory for a typical installation of FSP is:

/opt/altair/fsp/13.0

Enter the following at the Linux/Unix command line prompt (command must contain spaces with escape characters):

cd _File\ service\ provider_installation


./Change\ File\ service\ provider\ Installation -i swing


Chapter 18 Uninstalling FSP console mode

18.2 Initiate the FSP uninstall process

Press <ENTER> to start the uninstall process.


A message will be displayed indicating the uninstall has begun. Once the uninstall is com-plete a message is displayed indicating any items that could not be removed will be listed. Please take a moment to manually remove them..


IndexPPBSA service commands 93, 135

restarting web application 93, 135status of web application 93, 135

pbsworks-pbsa 93, 135

Rrestarting web application 93, 135

Sstatus of web 93, 135


Index


pbs application services 13.0 administrator’s...

Documents