ADMINISTRATION GUIDE XECUTE Version: 2.0 March 2019 Legal Information Software Copyright Notice Customer Care Introduction This guide provides details on the installation, upgrade, administration and maintenance of the RPM XECUTE. XECUTE consists of following installations: XECUTE Service l Windows service to be installed on the EPF application server XECUTE Config l Desktop utility to upload and configure XECUTE site data and manage system settings. XECUTE l Desktop application to schedule an XECUTE site. XECUTE+AR (iOS) and XECUTE Mobile (Android) l Mobile companion apps to view an XECUTE site. XECUTE+AR is available on the Apple App Store® for iPhone® and iPad® devices. XECUTE Mobile is available on the Google Play™ store for compatible devices. Please see the Mobile Requirements section for more information. Prerequisites XECUTE is an Enterprise service that has been designed to work in conjunction with EPF. XECUTE 2.0 requires EPF OMI and Model Repository version 2.2 or later. Please refer to the EPF Administration Guide for EPF setup instructions. Client Hardware requirements System requirements for XECUTE and XECUTE Config client applications. 2 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Component Minimum Recommended Operating Windows 7 Professional (64-bit) Windows 10 Professional system SP1 (64-bit) Processor Intel i7 dual core Intel i7 quad physical core or better (PassMark - CPUMark score 13000 or higher) Memory 16 GB 32 GB Screen 1600 x 900 1920 x 1080, True Colour (32 resolution bit), 96dpi Graphics cards NVIDIA Quadro K2000 (1GB Video NVIDIA Quadro K2200 (4GB RAM) or equivalent Video RAM) or better (PassMark - G3D Mark score 3400 or higher) Mobile Requirements XECUTE+AR is a companion mobile app available to Apple iPhone and iPad devices iOS 8.0 or later. XECUTE+AR is designed to connect to the XECUTE Mobile Service to view active sites, or it can be run offline using the demonstration site included with the app. Augmented Reality (AR) functionality requires iOS 11 or later, and is supported on the iPhone SE, iPhone 6s, iPad (2017 model), iPad Pro or later editions of these devices. XECUTE Mobile is the companion mobile app for devices running Android 7.0 or later. XECUTE Mobile offers the same functionality as XECUTE+AR, but does not support augmented reality. Please contact RPMGlobal for more information. XECUTE Server XECUTE supports multiple deployment options, depending on the scale of the deployment and the technological maturity of the site. Options for a single-server deployment and a separate application and database server deployment are described below. The deployment patterns described here are intended for the final production environment. RPM strongly recommends that at least two separate environments are created for the project: l QA: Quality Assurance / Test environment: Used during the project for testing purposes prior to go-live, and after the project for testing of future upgrades, issue analysis and res- olution testing. 3 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved l Production: The live production environment commissioned during the final phase of the project. The separation of QA and Production environments involves the use of separate application serv- ers, separate SQL instances and, ideally separate SQL server host machines. Separation of the QA and Production environments ensures that any issues that occur during test- ing and deployment do not affect live production systems. RPM recommends that the QA environment be as similar as possible to the Production envir- onment to ensure that any potential issues are discovered early in the project, allowing adequate time for resolution prior to scheduled “Go-Live” deployment in the Production environment. Single-server deployment The single-server deployment is the simplest XECUTE deployment option. Single-server System Requirements Component Minimum Recommended Operating System Windows Server 2012 R2 Windows Server 2016 Database Microsoft SQL Server 2012 Microsoft SQL Server 2016 Standard SP2 Standard SP2 Processor Intel XEON quad physical Intel XEON Octa Core with core with hyper-threading (8 hyper-threading (16 logical logical cores). 2.2 GHz+ cores). 3 GHz+ Memory 32 GB 64 GB Database Space 2 TB* 2 TB* Note: * Storage space is for databases only. Model Repository requires additional space for storage of model files. Depending on usage, RPM suggests a minimum of 2 terabytes on an enterprise grade SAN. RPM recommends separate partitions for SQL data files, log files and backup. Typical production topology EPF and XECUTE services are not restricted to using a single SQL server. There are multiple options for physical server locations; the specific option is determined during implementation. 4 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Separate Database Server Deployment The separate database server deployment provides for the application and database server infra- structure to be physically separated and independently managed and scaled. This deployment option provides for targeted scalability. XECUTE Application Server System Requirements Component Minimum Recommended Operating System Windows Server 2012 R2 Windows Server 2016 Processor Intel XEON quad core with Intel XEON Octa core with hyper-threading (8 logical hyper-threading (16 logical cores). 2.2 GHz+ cores). 3 GHz+ Application Storage 3 GB 3 GB Memory 32 GB 64 GB 5 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved EPF Application Server System Requirements Component Minimum Recommended Operating System Windows Server 2012 R2 Windows Server 2016 Processor Intel i7 dual core CPU with hyper-threading (4 logical cores) Application Storage 3 GB Memory 16 GB Database Server System Requirements Component Minimum Recommended Operating System Windows Server 2012 R2 Windows Server 2016 Database Microsoft SQL Server 2012 Microsoft SQL Server 2016 Standard SP2 Standard SP2 Processor Intel dual core CPU quad physical core or better (PassMark - CPUMark score 9000 or higher) Memory 16 GB Database Space 2 TB* 2 TB* Note: * Storage space is for databases only. Model Repository requires additional space for storage of model files. Depending on usage, RPM suggests a minimum of 2 terabytes (RAID 5 + stripping). RPM recommends separate partitions for SQL data files, log files and backup. 6 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Installation Guide Application Server Pre-Installation Configuration The following must be installed / configured on the application server prior to installing any applic- ation components: 1. Microsoft .NET 4.6.2. 2. Microsoft Distributed Transaction Coordinator service must be running and configured cor- rectly (please see section titled “Microsoft Distributed Transaction Coordinator”). Note: Access to the databases must be provided via Microsoft SQL Server Man- agement Studio. Where remote desktop access to the database server is not per- mitted, RPM recommends that SQL Server Management Studio be installed on the Application Server. Database Server Pre-Installation Configuration Microsoft Distributed Transaction Coordinator service must be running and configured correctly (please see section titled “Microsoft Distributed Transaction Coordinator”). The database server should be configured as shown in the table below: 7 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Configuration Property Setting Server Collation Latin1_General_CI_AS Memory allocation Dependent on available memory and other applications, but at least 2GB Automatic Processor Affinity Mask True Automatic IO Affinity mask True Server Authentication Mixed Mode (SQL Server and Win- dows) Remote Connections True FILESTREAM for Transact-SQL access Must be enabled for EPF Model Repository FILESTREAM for file I/O streaming access Must be enabled for EPF Model Repository. The default setting should be used in the Windows Share Name box. It must not be blank. Allow remote clients access to FILESTREAM Must be enabled for EPF Model data Repository. Installation Account To install the software, a user account must be provided for use by the RPM implementation team during the installation process. The account should conform to the general user account man- agement policy of the client organisation. The installation account must have the following permissions on the application server: l Local administration rights l Permission to install software The installation account must have the following permissions on the database server: l SQL ‘sysadmin’ rights if the databases have not been pre-installed; OR l SQL ‘dbo’ rights on each of the pre-installed databases if this has been done 8 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Ideally, SQL Server Management Studio should be installed and available for use by the install- ation account. This can be on the application server, or on the database server if the installation account is given local user rights on the database server. Service Account A domain service account must be created to be used as the start-up account for the XECUTE service. The account must satisfy the following requirements: l It must be a domain-level account (not a local system account) l Password never expires l Don’t require password change at next logon l Disallow interactive logon (recommended) l Given the Logon as a service right in the local group policy settings on the application server l Given write permissions to the “%programdata%\RungePincockMinarco” and "%programdata%\RPMGlobal" folders (including subfolders and files)