Planning and Prerequisites Guide SDL WorldServer 11.5 Legal notice Copyright and trademark information relating to this product release. Copyright © 1998–2019 SDL Group. SDL Group means SDL PLC. and its subsidiaries and affiliates. All intellectual property rights contained herein are the sole and exclusive rights of SDL Group. All references to SDL or SDL Group shall mean SDL PLC. and its subsidiaries and affiliates details of which can be obtained upon written request. All rights reserved. Unless explicitly stated otherwise, all intellectual property rights including those in copyright in the content of this website and documentation are owned by or controlled for these purposes by SDL Group. Except as otherwise expressly permitted hereunder or in accordance with copyright legislation, the content of this site, and/or the documentation may not be copied, reproduced, republished, downloaded, posted, broadcast or transmitted in any way without the express written permission of SDL. WorldServer is a registered trademark of SDL Group. All other trademarks are the property of their respective owners. The names of other companies and products mentioned herein may be the trade- marks of their respective owners. Unless stated to the contrary, no association with any other company or product is intended or should be inferred. This product may include open source or similar third-party software. Although SDL Group takes all reasonable measures to provide accurate and comprehensive information about the product, this information is provided as-is and all warranties, conditions or other terms concerning the documentation whether express or implied by statute, common law or otherwise (including those relating to satisfactory quality and fitness for purposes) are excluded to the extent permitted by law. To the maximum extent permitted by law, SDL Group shall not be liable in contract, tort (including negligence or breach of statutory duty) or otherwise for any loss, injury, claim liability or damage of any kind or arising out of, or in connection with, the use or performance of the Software Documentation even if such losses and/or damages were foreseen, foreseeable or known, for: (a) loss of, damage to or corruption of data, (b) economic loss, (c) loss of actual or anticipated profits, (d) loss of business revenue, (e) loss of anticipated savings, (f) loss of business, (g) loss of opportunity, (h) loss of goodwill, or (i) any indirect, special, incidental or consequential loss or damage howsoever caused. All Third Party Software is licensed "as is." Licensor makes no warranties, express, implied, statutory or otherwise with respect to the Third Party Software, and expressly disclaims all implied warranties of non- infringement, merchantability and fitness for a particular purpose. In no event will Licensor be liable for any damages, including loss of data, lost profits, cost of cover or other special, incidental, consequential, direct, actual, general or indirect damages arising from the use of the Third Party Software or accompanying materials, however caused and on any theory of liability. This limitation will apply even if Licensor has been advised of the possibility of such damage. The parties acknowledge that this is a reasonable allocation of risk. Information in this documentation, including any URL and other Internet website references, is subject to change without notice. Without limiting the rights under copyright, no part of this may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of SDL Group. ii Planning and Prerequisites Contents 1 Environment overview and recommendations ........................ 1 2 Clustered mode planning ..................................... 5 3 System requirements ........................................ 9 Requirements for the application server . 10 Requirements for the database server . 11 Database size estimation . 12 Requirements for installing SDL Online Editor . 13 Prerequisites for installing the File Type Support (FTS) Server . 14 Supported browsers and recommendations for client machines . 15 4 Components supported in WorldServer ........................... 17 Content repository connectors . 18 Third-party tools . 18 Translation tools and terminology providers . 19 Interoperability standards . 19 Languages for translation . 19 Planning and Prerequisites iii iv Planning and Prerequisites 1 Environment overview and recommendations 1 Environment overview and recommendations WorldServer installations involve various components that you need to install on several different machines. Run your application servers and your database server on separate machines. A typical configuration deploys the database system on a single Linux or Windows server and the WorldServer application on one or more Linux or Windows servers. Typical deployments of WorldServer also contain multiple machines that serve as clients, servers, repositories, and databases, as shown in the following diagram: Hardware requirements depend on the amount of data and the operational load you expect on the system. WorldServer is CPU-intensive and database processing is input/output (I/O)-intensive. Thus, the application server should have adequate CPU power and the database server should have a fast disk subsystem and sufficient memory. 2 Planning and Prerequisites Environment overview and recommendations 1 Prepare for growth Most globalization needs grow over time; therefore, you should consider installing more powerful hardware than the initial requirements indicate. This gives you extra capacity and room for scalability expansion in the future. It is much harder to upgrade to new hardware after the system is in production mode than to anticipate future growth at the outset. The most important aspect of hardware configuration is the database server. WorldServer is a highly database-intensive application; the database system can never be too powerful. The database server should place more emphasis on its I/O subsystem and memory than on the CPU power. Oracle (the recommended database management system for large deployments) uses all the memory and I/O bandwidth it can get. SDL recommends a fast RAID array. You can achieve good performance on RAID 0+1 configurations. For the application server, CPU power is more important than I/O bandwidth. A baseline system consisting of at least a 2.8-3 GHz CPU can provide good performance. The general requirements for a server configuration are as follows: • Recommended configuration: 4 x CPU Cores at 2.0 GHz each with at least 16 GB RAM, running on Windows Server 2012 R2 (64-bit) or on Windows Server 2016, to support at least 4 File Type Support (FTS) Server processes. • Database servers: 4 x 4 CPU at 2.0 GHz with 16 GB RAM, as well as sufficient high speed storage and backup allocation. On the application server, you only need disk space for keeping system files, application files, temporary files, and uploaded documents. 20-30 GB of free disk space is sufficient. If the server has enough physical memory, any modern desktop-grade disk subsystem is adequate. For workflow-intensive installations, you should allocate one or more separate business processing (workflow engine) machines. If you use sophisticated workflows containing many automatic actions, you should separate the servers that run workflow processes from those that are used for user requests. When WorldServer processes a large project through a workflow, the workflow engine uses all the CPU it can get. If the workflow engine runs on the same server as other WorldServer functions, this might impact the performance of other user requests and cause slower user interface response time. A separate workflow server helps you maintain good user interface response tine while processing large project workflows. Dedicated vs. shared machines You should put WorldServer on a dedicated application server machine rather than on the same application server as other web-based applications. There is no way to restrict the amount of the CPU power given to web-based applications, which means that one application can starve the others. Because WorldServer is very processor-intensive, it can degrade the performance of other applications on the same machine. Similarly, you should also put the WorldServer database under a dedicated database server installation on a dedicated machine rather than having it share a database instance with other applications. Planning and Prerequisites 3 1 Environment overview and recommendations 4 Planning and Prerequisites 2 Clustered mode planning 2 Clustered mode planning WorldServer was designed to run in a clustered mode with multiple application servers accessing a shared database. Clustering provides almost linear scalability on the application server side as long as the database is powerful enough. For scalability, you should run a clustered application server configuration with each system having less CPU power, rather than a single application server on a powerful CPU system. As the demand grows, you can add server systems to accommodate possible growth in application load. A cluster setup provides many benefits over a stand-alone configuration: • Performance – Spreading the load across multiple machines can greatly improve the responsive- ness of the system and the overall user experience. • Redundancy – A WorldServer cluster does not have