Enabling Science. IDBS Products HARDWARE REQUIREMENTS. ID Business Solutions

Transcription

1 Enabling Science IDBS Products HARDWARE REQUIREMENTS ID Business Solutions IDBS 2016

2 Information in this document is subject to change without notice. The software described in this document is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of those agreements. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and recording for any purpose other than the purchaser s personal use without the written permission of IDBS. The names of actual companies and products mentioned in this document may be trademarks of their respective owners. IDBS accepts no responsibility or liability for any errors or inaccuracies that may appear in this documentation. Copyright 2016 IDBS Date of issue: 3 January 2017

3 Contents Introduction... 4 ActivityBase Suite... 5 Client Tier... 5 Application Tier... 5 Data Tier... 6 E-WorkBook... 7 Client Tier... 7 Desktop Clients Only... 7 Web Clients... 7 Application Tier... 8 Desktop Clients Only... 8 Web Clients... 8 Spreadsheets... 9 Web Chemistry... 9 Data Tier E-WorkBook Inventory Client Tier Application Tier Data Tier Inforsense for E-WorkBook Client Tier Application Server Tier ActivityMart Data Tier InforSense Suite Client Tier Application Tier Data Tier (for ClinicalSense) BioMolecular Hub InforSense Application Server Tier BioMolecular Hub Data Tier... 18

4 Introduction This document summarises the levels of support that IDBS currently provides for its products running on different hardware environments. IDBS products fall into three categories: Desktop products that install and run locally on a client PC. 3-tier products (e.g. E-WorkBook, BioBook, InforSense/ClinicalSense, ActivityBase) that require client PCs, an Application Server and Database Servers. Multiple Data Tier servers (e.g. ActivityMart). The recommended hardware specifications for IDBS products are provided on the following pages. Note: references to CPU cores apply to both physical and virtual CPU cores.

5 ActivityBase Suite Below is the recommended hardware platform for running the following products and their utilities: ActivityBase, ActivityBase XE, Object Manager, Protocol Transfer Assistant, HTS File Assistant, Start File Assistant, Selection Assistant, StructureLoad, IDBSMAC, SARgen, SARview and XLfit. All product versions are those compatible with ActivityBase 8.x unless specifically noted. Client Tier Display Intel Core 2 Duo 2GHz or better. For XE 7.7 and above, a quad-core CPU or better is recommended to take advantage of multi-core support. 4 GB for 32-bit Operating Systems, 8 GB or above for 64-bit Operating Systems when using 64-bit XE client. 1 GB is sufficient to install all IDBS client and desktop products. For XE 7.7 and above, a minimum of 2 GB disk space after installation is recommended to take advantage of local file access on the client machine during an XE session. An IDBS product requiring an Oracle client install and/or Microsoft Office applications to be installed will largely determine hard drive space needs. Consult Oracle and/or Microsoft documentation for advice. WXGA or WSXGA minimum (that is approximately 1280 x 768 to 1440 x 900 pixels). Graphics adapter Capable of driving the display to medium (16-bit) colour settings or above. 256 colours are not recommended. IDBS desktop/client products either use, or may in the future use, 3D data visualisation techniques using OpenGL. A graphics adapter with at least 32 MB of memory is essential at the minimum display resolution and 64 MB is helpful to maintain performance in interacting with 3D data visualisation. Note that you should consider the resolution and colour needs of any other applications or document/image viewing tools that you may use in conjunction with our products. Normal font size is recommended. Application Tier Intel Xeon Quad Core 2.27GHz or higher. 8 GB or higher. 1 GB is sufficient to install all application server products and pre-requisites.

6 Data Tier Seek Oracle expert advice. IDBS Chemistry support: The Oracle implementation will largely dictate the specification required. However if you install and use IDBS Chemistry system with Oracle, some additional constraints need to be considered: ActivityBase supports x86 32 and 64-bit Intel Pentium 4, 3 GHz or equivalent up to and including current multi-core CPUs. Sun UltraSPARC hardware (natively 64-bit). Maximum supported by your hardware and operating system. Seek IDBS advice for your implementation.

7 E-WorkBook Below are the recommended minimum hardware platforms for running the following products and their utilities: E-WorkBook, E-WorkBook Enterprise (BioBook), E-WorkBook Chemistry (ChemBook) and Asset Hub. All product versions are those compatible with E-WorkBook Suite 10.x unless specifically noted. Client Tier Desktop Clients Only The following specification applies to PCs running the Desktop Client only: Display Graphics Adapter Intel Core 2 Duo 2GHz or better. 4 GB or more. 1 GB is sufficient to install all IDBS and Desktop Client products. XGA or WXGA minimum (that is 1024 x 768 or 1280 x 800 pixels). SXGA (1280 x 1024 pixels) or higher is recommended. Capable of driving the display to medium (16-bit) colour settings or above. 256 colours are not recommended. IDBS desktop/client products either use, or may in the future use, 3D data visualisation techniques using OpenGL. A Graphics adapter with at least 6 MB of memory is essential at the minimum display resolution and 16 MB is helpful to maintain performance in interacting with 3D data visualisation. Note that you should consider the resolution and colour needs of any other applications or document/image viewing tools that you may use in conjunction with our products. Normal font size is recommended. Web Clients For devices running the Web Client, the following minima are recommended: Display Intel Core 2 Duo 2GHz or better. 1 GB or more. 200 MB required to install ancillary components (such as External Editor Integration and Send to E-WorkBook feature). XGA or WXGA minimum (that is 1024 x 768 or 1280 x 800 pixels). Web client users intending to run the Spreadsheet Designer (E-WorkBook 10 only) should refer to the Desktop Client specifications.

8 Application Tier There is a range of sizing options for this tier, which depend on three main factors: The number of concurrent, active users of E-WorkBook; The proportion of users of the Web Client as against the Desktop Client; and Whether Web Spreadsheets are used. Usage characteristics will also affect required sizing, but these vary considerably between deployments, and are therefore complex to take into account. For this reason, the specifications below are conservative, assuming heavy usage. Furthermore, the and specifications refer to the total compute resources required in this tier, whether in a single server or spread across a multi-node cluster of servers. refers to the maximum storage required to install the IDBS software and pre-requisites on each Application Server. Desktop Clients Only In deployments primarily using the Desktop Client, the demands on the Application Server are comparatively modest, since the majority of the processing takes place in the Client and Data Tiers. Application Server Small (up to 100 users) Medium (up to 750 users) Large (up to 1,500 users) 4 cores 12 cores 24 cores 6 GB 16 GB 32 GB 5 GB 5 GB 5 GB Network Single 1 GbE Single 1 GbE Two 1 GbE For very large deployments (in excess of 1,000 concurrent users), please consult IDBS. Note that for very small deployments (fewer than 25 concurrent users), it is possible to combine the Application and Database tiers on same server. Web Clients Deployments with a significant number of active Web Clients entail a much greater demand upon the Application Servers, requiring correspondingly higher specifications for the total server resources required. Application Server Small (up to 150 users) Medium (up to 750 users) Large (up to 1,500 users) 8 cores 40 cores 80 cores 48 GB 240 GB 480GB 5 GB 5 GB 5 GB Network Single 1 GbE per server Single 1 GbE per server Two 1 GbE per server

9 Spreadsheets Those deployments using Web Spreadsheets will additionally require Spreadsheet Server resources (E- WorkBook 10 only and above). Important Notes: 1. The specifications given below are conservative, and assume large spreadsheets, which place disproportionate demands upon the servers upon which they run. If this does not apply, fewer resources may be used. 2. There is a significant increase in the total server resources required where Asset Hub is deployed. 3. As with the other E-WorkBook specifications above, they may be distributed across as many or as few actual servers as suits the target environment, depending on organisational infrastructure standards. IDBS guidance to customers is to scale up, rather than out first, specifying a smaller number of more powerful servers (within the bounds of reasonable cost, naturally), whilst maintaining the appropriate level of fault tolerance through redundancy. This is due to the non-linear nature of Spreadsheet Server scaling. 4. The number of users refers to concurrent and active, rather than total users. 5. refers to the maximum storage required to install the IDBS software and pre-requisites on each Application Server. Without Asset Hub: Spreadsheet Server Small (up to 150 users) Medium (up to 750 users) Large (up to 1,500 users) 36 cores 180 cores 360 cores 72 GB 360 GB 720 GB 1 GB 1 GB 1 GB Network Minimum Single 1 GbE Minimum Two 1 GbE Minimum Four 1 GbE With Asset Hub: Spreadsheet Server Small (up to 150 users) Medium (up to 750 users) Large (up to 1,500 users) 72 cores 360 cores 720 cores 144 GB 720 GB 1,440 GB 1 GB 1 GB 1 GB Network Minimum Single 1 GbE Minimum Two 1 GbE Minimum Four 1 GbE Web Chemistry Those deployments using Chemistry in the Web will additionally require Web Chemistry Server resources (E- WorkBook 10.1 only and above). The deployment of the Web Chemistry Server will depend not only on the number of concurrent users but the number of molecules or reactions stored in the system.

10 After first installation, the number of molecules and reactions stored in the database will initially be zero and only increase over time. This means the initial deployment will be relatively modest, so the following conversative specifications are suggested: Web Chemistry Server Initial Deployment 4 cores 2 GB 1 GB Note: the memory allocation refers to the maximum memory pool configured to the WebChemistryServer process. As the number of concurrent users, molecules and reactions in the database increases, the specification of the server can be adjusted appropriately. For example, memory and disk space requirement on the Web server will increase with the chemical structure count due to caching. Please refer to the following ChemAxon documentation here for a further discussion on the hardware requirements for the JChem Base component, which the Web Chemistry Server is based upon. Data Tier As with the Application Tier, there is a range of sizing options for this tier. However, these depend primarily on the number of concurrent, active users. Again, usage characteristics will also affect required sizing, but these vary considerably between deployments, and are therefore complex to take into account. For this reason, the specifications below are conservative, assuming heavy usage. Should lighter usage be expected, these may be adjusted downward. Database Server Small (up to 150 users) Medium (up to 750 users) Large (up to 1,500 users) 8 cores 16 cores 32 cores 1 48 GB 224 GB 448 GB GB or more 1 TB or more 2 TB or more Network Single 1 GbE Two 1 GbE Four 1 GbE 1 This core count may be split across more than one Database server, using Oracle s RAC technology. 2 Includes storage capacity for the database itself, as well as the Oracle installation files.

11 E-WorkBook Inventory Below is the recommended hardware platform for running the following products and their utilities: E-WorkBook Inventory Client Tier Please refer to E-WorkBook section relating to web client requirements. Application Tier The following section provides starting guidelines to the sizing of the application tier and data tier hardware based on application profiling that has been performed at IDBS. As the application is profiled using general user scenarios and data structures/sizes, it is highly recommended that the application is profiled and monitored under production deployment with more representative user workflows and data structures/sizes. For the application tier, the key factors that influence hardware resource requirements are as follows: CPU - number of concurrent users and total inventory data size. - total inventory data size. Disk Storage - total inventory data size. Application Server 20 Concurrent 50 Concurrent 100 Concurrent 150 Concurrent 250 Concurrent 6 cores 14 cores 26 cores 40 cores 62 cores 16 GB 24 GB 40 GB 54 GB 68 GB 1250 GB 2500 GB 5000 GB 7500 GB GB Note that if a MongoDB replica set secondary node is deployed on the E-WorkBook Inventory server, additional disk storage needs to be provisioned for the MongoDB data (equivalent to the primary MongoDB server disk storage requirements). The above table provides a general guideline for the typical levels of concurrent user and inventory data size combinations. Please contact IDBS Support for concurrent user and inventory data size combinations that are not listed above.

12 Data Tier For the data tier, the key factors that influence hardware resource requirements are as follow: CPU - total inventory data size. - total inventory data size. Disk Storage - total inventory data size. Database Server 20 Concurrent 50 Concurrent 100 Concurrent 150 Concurrent 250 Concurrent 2 cores 2 cores 4 cores 4 cores 6 cores 26 GB 50 GB 100 GB 150 GB 200 GB 250 GB 500 GB 1000 GB 1500 GB 2000 GB

13 Inforsense for E-WorkBook Below is the recommended hardware platform for running the InforSense for E-WorkBook Below is the minimum recommended hardware platform 3 for running the following products and their utilities: InforSense Suite for E-WorkBook. All product versions are those compatible with the InforSense for E-WorkBook Suite 1.x unless specifically noted. Client Tier Display x86 32-bit or 64-bit Intel Core 2 Duo 2GHz+ or equivalent, up to and including current quad core CPUs. 4 GB or above. 1 GB is sufficient for Java Webstart to install the InforSense Workflow Builder client. Minimum SXGA or WSXGA resolution (1280 x 1024 or 1440 x 900 pixels). Graphics Adapter Capable of driving the display to medium (16-bit) colour settings or above. 256 colours are not recommended. IDBS desktop/client products either use, or may in the future use, 3D data visualisation techniques using OpenGL. A Graphics adapter with at least 6 MB of memory is essential at the minimum display resolution and 16 MB of memory is helpful to maintain performance in interacting with 3D data visualisation. Note that you should consider the resolution and colour needs of any other applications or document/image viewing tools that you may use in conjunction with our products. Normal font size is recommended. Application Server Tier x86 64-bit Intel Core 2 Quad 2Ghz+ per core. 6 CPU cores are required when installing with the default number of concurrent workflow tasks of 4. Each additional workflow executor configured should be allocated an additional 1 CPU core as a minimum. The exact CPU requirement will depend on the data set sizes and workflows that are typically processed by the application. It is highly recommended that the InforSense application server is installed on a dedicated hardware server separate to that of the E-WorkBook server, and connected with a high speed low latency Gigabit network link. 3 It is recommended that more accurate hardware sizing is established by profiling the typical data sizes and/or typical workflows that will be processed within the application.

14 Maximum supported by your hardware for 64 bit platforms. 4 GB memory is required when installing using the default memory settings and the default number of concurrent workflow tasks. This will typically support approximately 3-4 concurrent users and up to a maximum of 4 concurrent workflow tasks. Each additional concurrent user added to the system will require an additional 150 MB of memory allocated to the server heap size setting. Each additional concurrent workflow executor configured will require an additional 600 MB of memory (based on the default executor memory setting). The exact memory requirement will depend on the data set sizes and workflows that are typically processed by the application. 10 GB storage space is recommended per user as a typical guideline; however, the exact disk space requirement will depend on the data set sizes that are typically processed by the application. Seek IDBS advice for your implementation.

15 ActivityMart Below is the recommended hardware platform for running ActivityMart. The compatible ActivityMart version is 3.x. Data Tier ActivityMart can be installed on one or two servers. Seek Oracle expert advice for server processor power to ensure adequate and reliable performance of the Oracle database(s). x86 32bit or 64 bit Intel Pentium 4, 3 GHz or equivalent up to and including current multi-core CPUs. Sun UltraSPARC hardware (natively 64bit). Maximum supported by your hardware and operating system but minimum recommendation is 1 GB. There should be sufficient disk capacity to allow for the ActivityMart to grow over time. As a rough estimate, the Staging Area and ActivityMart will each require the same amount of space as the source ActivityBase database takes up. Seek IDBS advice for your implementation.

16 InforSense Suite Below is the minimum recommended hardware platform 4 for running the following products and their utilities: InforSense and ClinicalSense. All product versions are those compatible with InforSense Suite 5.1.x unless specifically noted. Client Tier Display x86 32bit Intel Core 2 Duo 2GHz+ or equivalent, up to and including current quad core CPUs. x86 32bit Intel Core 2 Quad 2GHz+ or equivalent, if Omics Workbench is installed. 2 GB or above. 4 GB, if Omics Workbench is installed. 1 GB is sufficient for Java Webstart to install the InforSense Workflow Builder client. For the InforSense Portal and ClinicalSense Client, disk space requirement is dependent on the selected internet browser requirements. Please consult the hardware requirements of the relevant internet browser used. Minimum SXGA or WSXGA resolution (1280 x 1024 or 1440 x 900 pixels). Graphics Adapter Capable of driving your display to medium (16bit) colour settings or above. 256 colours are not recommended. IDBS desktop/client products either use, or may in the future use, 3D data visualisation techniques using OpenGL. A Graphics adapter with at least 6 MB of memory is essential at the minimum display resolution and 16 MB of memory is helpful to maintain performance in interacting with 3D data visualisation. Note that you should consider the resolution and colour needs of any other applications or document/image viewing tools that you may use in conjunction with our products. Normal font size is recommended. Application Tier x86 64-bit Intel Core 2 Quad 2Ghz+ per core is recommended. However, please refer to the IDBS Software Platform Support document for 32-bit and 64-bit OS support. 2 CPU cores are recommended per concurrent user as a typical guideline; however, the exact CPU requirement will depend on the data set sizes and workflows that are typically processed by the application. It is recommended that the InforSense/ClinicalSense application is installed on a dedicated hardware server. 4 It is recommended that more accurate hardware sizing is established by profiling the typical data sizes and/or typical workflows that will be processed within the application.

17 Maximum supported by your hardware for 64-bit platforms. 3 GB is the maximum amount of memory available to a 32-bit Windows operating system. 1 GB memory is recommended per concurrent user as a typical guideline; however, the exact memory requirement will depend on the data set sizes and workflows that are typically processed by the application. 20 GB storage space is recommended per user as a typical guideline; however, the exact disk space requirement will depend on the data set sizes that are typically processed by the application. Seek IDBS advice for your implementation. Data Tier (for ClinicalSense) Seek Oracle expert advice. x86 64-bit Intel Core 2 Quad 2Ghz+ per core is recommended. However, please refer to the IDBS Software Platform Support document for 32-bit and 64-bit OS support. It is recommended that the ClinicalSense Oracle data tier is installed on a dedicated hardware server with fast gigabit low latency network connection to the InforSense/ClinicalSense server. Maximum supported by your hardware and operating system. Seek IDBS advice for your implementation.

18 BioMolecular Hub Below is the recommended hardware platform for running the following products and their utilities: BioMolecular Hub. All product versions are those compatible with BioMolecular Hub 1.x unless specifically noted. InforSense Application Server Tier 5 x86 64-bit Intel Core 2 Quad 2Ghz+ per core is recommended. However, please refer to the IDBS Software Platform Support document for 32-bit and 64-bit OS support. Maximum supported by your hardware for 64-bit platforms; 4 GB as a general guideline if InforSense/ClinicalSense functionalities are not required 6. 3 GB is the maximum amount of memory available to a 32-bit Windows operating system. Seek IDBS advice for your implementation. The data storage area of the BioMolecular Hub is required to be accessible by the InforSense application server either through a local storage disk or network SAN storage connected via a high speed/bandwidth channel. BioMolecular Hub Data Tier Seek Oracle expert advice. x86 64-bit Intel Core 2 Quad 2Ghz+ per core is recommended. However, please refer to the IDBS Software Platform Support document for 32-bit and 64-bit OS support. It is recommended that the BioMolecular Hub Oracle data tier is installed on a dedicated hardware server with fast gigabit low latency network connection to the InforSense server 7. Maximum supported by your hardware and operating system. Seek IDBS advice for your implementation. 5 The BioMolecular Hub application is installed within an InforSense application server. 6 Please also consult the InforSense hardware requirement section if InforSense and ClinicalSense functionalities are also utilised. 7 The BioMolecular Hub Oracle Database can coexist on the same server instance as the ClinicalSense Oracle Database.