Pipeline Pilot Server Installation Guide
Total Page:16
File Type:pdf, Size:1020Kb
SERVER INSTALLATION GUIDE PIPELINE PILOT SERVER 2016 Copyright Notice ©2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with BIOVIA Pipeline Pilot Server." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Pipeline Pilot Server 2016 Post-Install Checklist 27 Installation 5 Pipeline Pilot Server Home Page 30 Quick Install Tips 5 Administration Portal 31 BIOVIA License Files 5 Chapter 7: Deployment Options 32 Additional Information 5 Load Balancing Deployments 32 Chapter 2: Getting Started 6 Load Balancing Features 32 Overview 6 Pre-configuration Steps 32 Deployment Options 6 Configuration Steps 32 Managing Multiple Installations 6 Grid Engine Installation 34 Side-by-side installations 6 Grid Engine setup 34 Protocol database compatibility 7 Grid Engine requirements 34 Port management 7 Setting the User Account for Running Xvfb Sharing an XMLDB with Multiple Servers 7 on Grid Cluster Nodes 34 Moving/Migrating an Installation 8 Chapter 8: Uninstalling Pipeline Pilot 36 Best practices for moving directories 8 Uninstalling from a Windows Server 36 Pre-Install Checklist 10 Uninstall from a Linux Server 37 Chapter 3: Pipeline Pilot Services 12 Appendix A: Unattended Installation on Shutting down Services on Windows 13 Linux 39 Shutting down Apache on Linux 14 Setting Required Pre-Installation Environment Variables 39 Chapter 4: Installing Pipeline Pilot on Windows 15 Installation Environment Variables 40 Windows Server Installation 15 Package names. 40 Windows Guidelines 16 Installation Command Example 42 Windows Requirements for Load Balancing 16 Appendix B: Configuring Apache as a Load Balancer and Reverse Proxy 44 Local job temporary directory 16 HTTP Requests 44 Impersonation on Windows 17 SSL Requests 45 Chapter 5: Installing Pipeline Pilot on Linux 18 Appendix C: Installing Separately Licensed Pre-Installation Checklist for Linux 18 Collections 46 Linux Guidelines 20 Materials Studio Collection 46 Installation paths 20 Windows (upgrade) 46 Red Hat Linux 20 Windows (new installation) 46 Local authentication and SELinux 20 Linux (upgrade) 47 Distributed file system and NFS Linux (new installation) 47 configuration 20 Appendix D: Required Linux RPMs 48 NFS Settings 21 Red Hat Enterprise Linux 7 48 NFS Cache Settings 21 Red Hat Enterprise Linux 6 49 Clock synchronization 21 SUSE Linux Enterprise 11 50 Possible interaction with /usr/sbin/tmpwatch 22 Installing Pipeline Pilot on Linux 22 Post-Install Checklist for Linux 23 Linux Checklist 23 Server Configuration Checklist 24 Testing Client software on Linux 26 Chapter 6: Post-Installation 27 Chapter 1: Pipeline Pilot Server 2016 Installation Quick Install Tips To install Pipeline Pilot on your Windows or Linux server 1. Shut Down Apache. 2. Review Pre-Install Checklist and perform all recommended pre-installation tasks. 3. Follow the instructions for Windows Server Installation or Linux Server Installation. 4. You might need to perform additional tasks on your server to ensure your installation runs properly. For details, see Post-Install Checklist. BIOVIA License Files To install any BIOVIA Pipeline Pilot Server software and collections, you need a valid license file. Instructions are included with the license file activating a new license. Note that the Thomson Reuters and Materials Studio collections require a separate license. See Appendix C Installing Separately Licensed Collections. Additional Information For information about supported hardware and software, see the Pipeline Pilot System Requirements document. For details about advanced server deployments, see the Pipeline Pilot Deployment Guide. To install Pipeline Pilot Client, see the Pipeline Pilot Client Guide. For details about installing R Software, see the R Software Installation and Configuration Guide. For more information about BIOVIA Pipeline Pilot Server 2016 and other Pipeline Pilot software products, visit https://community.3dsbiovia.com/. Pipeline Pilot Server 2016 Installation | Page 5 Chapter 2: Getting Started Overview Upfront planning is critical to a successful enterprise deployment. See the Pipeline Pilot Deployment Guide, then use the pre-installation checklists and related information in this chapter to plan your deployment. The checklists apply to most deployments. If you have any questions, contact [email protected]. IMPORTANT! Pipeline Pilot Server 2016 requires Pipeline Pilot Client 2016. Users must upgrade their client in order to access the Server. Some applications and collections must be upgraded separately (e.g., Insight and Insight for Excel). Before installing Pipeline Pilot, ensure that you have access to these separate installers that are compatible with this version of the server. BIOVIA Draw does not upgrade automatically when you upgrade from an earlier version of Pipeline Pilot Server. You will need to upgrade BIOVIA Draw automatically. A separate license file is required for the Thomson Reuters and Materials Studio collections. See Appendix C: Installing Separately Licensed Collections. Deployment Options There are several advanced options for deploying Pipeline Pilot including: Workstation Standalone Web Farm (Load balancing) Clustering (Linux only) Distributed grid computing (Linux only) Note: For more information, see Chapter 7: Deployment Options Managing Multiple Installations Pipeline Pilot supports side-by-side installations of existing and new products. You can run BIOVIA Pipeline Pilot Server 2016 and previous Pipeline Pilot Server 9.x versions on the same machine. With side-by-side installations, the installer can copy components and protocols from an existing protocol database (XMLDB) into the new installation. You can also upgrade an existing installation to the latest version. Side-by-side installations To run different versions side-by-side, each version needs to be installed in a unique path or drive on your server. They cannot all reside in the same directory or subdirectories. You also need to run side-by- side versions of the clients that correspond to each server installation, assuming they are mutually incompatible versions. Getting Started | Page 6 On a Windows server, the default paths are: Version Default install path Pipeline Pilot Server 2016 C:\Program Files\BIOVIA\PPS Pipeline Pilot Server 9.5 C:\Program Files\BIOVIA\PPS Pipeline Pilot Server 9.0, 9.1, and 9.2 C:\Program Files\Accelrys\AEP Pipeline Pilot Server 8.x C:\Program Files\Accelrys\PPS Pipeline Pilot Server 7.5 C:\Program Files\Accelrys\SES Pipeline Pilot 7.0 and earlier versions: C:\Program Files\SciTegic (or "SciTegic 7.0" if this location already contains an installation) Protocol database compatibility The Pipeline Pilot Client (Pro Client) supports connecting to multiple XMLDBs through the Network tab. The 2016, 9.x and 8.x clients can connect to databases of previous software versions, but can only save files on the current database. Port management The following port numbers used by Pipeline PIlot: Type Default Port HTTP 9944 HTTPS 9943 Tomcat Shutdown 9945 Tomcat HTTP 9946 Derby 9947 You can have side-by-side installations of Pipeline Pilot 2016 on the same server where Pipeline Pilot 9.5 and earlier versions are installed. Each installation requires unique ports. If the default ports listed above are already in use for 2016, 9.1, 9.0, 8.5, or an earlier version of Pipeline Pilot Server, use alternate port numbers. Sharing an XMLDB with Multiple Servers Pipeline Pilot Pro clients running at multiple sites can access the same protocols and components if they share the same protocol database (XMLDB). To provide this functionality, the computational servers that process protocol jobs at each site need to communicate with one server that operates as the XMLDB for all the other servers. Clients are only aware of the computational server where they run protocols. They have no information about the machine hosting the XMLDB. See Moving/Migrating an Installation for more information about XMLDB. Page 7 | Pipeline Pilot Server • Server Installation Guide Moving/Migrating an Installation On Windows, you can move/migrate your server location by uninstalling Pipeline Pilot and transferring the XMLDB to the new server. After uninstalling, some files remain intact, making it possible for you to relocate existing data to a server re-installation. Specifically, your XMLDB remains intact in the <pps_ install> folder, so you can easily move/migrate it to a new location. Best practices for moving directories Note: <pps_install> is the name of your Pipeline Pilot