Download SDL Documentation Center

Planning and Prerequisites
SDL WorldServer 10.4.3
Documentation Notice
Copyright and trademark information relating to this product release
Copyright © 1998-2014 SDL Group.
SDL Group means SDL PLC. and its subsidiaries. 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/or its subsidiaries 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.
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 trademarks 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, details of which can be found by clicking the following
link: “Acknowledgments ” on page 43.
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.
Information in this documentation, including any URL and other Internet Web site 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.
November 2014
II
Planning and Prerequisites
Contents
1
About the SDL WorldServer Planning and Prerequisites Guide ....... 1
SDL WorldServer Documentation and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2
Best Practices for WorldServer Environments ............................ 5
WorldServer Components and System Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Clustered Mode Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3
Platform Infrastructure ....................................................... 13
WorldServer Application Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Size Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FTS Server Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
Components Supported in WorldServer ................................. 23
Translatable Document Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Content Repository Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Third-Party Tools Included with WorldServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Desktop Translation Workbenches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Interoperability Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Languages for Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
13
16
18
20
23
25
26
26
27
28
28
Configuration Options ....................................................... 35
Live Translation Memory Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Differences Between Live TM Mode and Non-Live Mode . . . . . . . . . . . . . . . . . . . . . . . . . 36
6
Platform Support Changes History ........................................ 39
Release Feature List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Planning and Prerequisites
III
IV
Planning and Prerequisites
Chapter 1
About the SDL WorldServer Planning
and Prerequisites Guide
Welcome to SDL Language Technologies and WorldServer™. SDL WorldServer is a
translation management system that provides advanced linguistic technology, process
automation, content repository integration and management services. Aligned with SDL
Studio™, WorldServer provides consistent analysis and reporting of translation projects
for localization managers, project managers, translators and reviewers.
Scope
The SDL WorldServer Planning and Prerequisites Guide provides conceptual information
for planning a WorldServer installation. It describes the environment requirements and
options for the WorldServer platform, infrastructure, and supported components.
SDL WorldServer Documentation and
Resources
The SDL WorldServer documentation set includes multiple separate deliverables. Some
of these documents are installed with WorldServer.
The following publications are available from the SDL Knowledgebase, in the Product
Documentation/SDL_WorldServer folder.
Planning and Prerequisites
1
About the SDL WorldServer Planning and Prerequisites Guide
Administrator Guide
Information on setting up and administering WorldServer in your environment.
Administrator Tutorial - Configuring SDL WorldServer
The process of performing an initial configuration of WorldServer.
Basic Operations Guide
Basic system administration and troubleshooting information for installed WorldServer
systems.
Browser Workbench User Guide
Information on embedded translation tool for brief reviews or edits.
Installation and Upgrade Guide
Instructions for installing or upgrading WorldServer and its components in your
environment.
Planning and Prerequisites Guide
Conceptual information for planning a WorldServer installation or upgrade, including
environment requirements and options for the WorldServer platform, infrastructure,
and supported components.
SDK Web Services Developer Guide
Reference guide for programmers who need to add Web Services to WorldServer.
Software Development Kit (SDK) User Guide
Reference guide for programmers to understand the APIs that extend WorldServer
functionality and integrate WorldServer with other custom or third-party applications.
Translation Memory Mode Concepts Guide
Information for project managers that need to understand the Studio-aligned translation
memory mode.
User Guide
Information for general WorldServer users: project managers, translators, and
reviewers.
WorldServer and Studio Integration Guide
Information for translators, reviewers, and project managers that use SDL Studio with
WorldServer.
The following WorldServer documentation resources are also available:
2
Planning and Prerequisites
About the SDL WorldServer Planning and Prerequisites Guide
WorldServer Release Notes
Where: The Knowledgebase SDL WorldServer/Release Notes folder. Also available
from the WorldServer FTP site: Walthamftp.sdl.com/ dist/ product/
worldserver/<releasenumber>/
Information on enhancements and changes in the most recent release. Also contains
late-breaking information about known issues and issues fixed in this release.
SDL Glossary
Where: http://producthelp.sdl.com/glossary/en/glossary.htm
An alphabetical list of terms related to WorldServer and other SDL products.
Transport Online Help
Context-sensitive help is available for most pages in TransPort from the More Info...
link. A full web help system is available from the Help link at the top of each page.
All Language Technologies online help documentation is also available from the
following web page: “http://www.sdl.com/support/language-technologyproducts/trados-online-product-help.html”http://www.sdl.com/
support/language-technology-products/trados-online-product-hel
p.html/
WorldServer Online Help
Context-sensitive help is available for most pages in WorldServer from the More
Info... link. A full web help system is available from the Help link at the top of each
page.
Planning and Prerequisites
3
About the SDL WorldServer Planning and Prerequisites Guide
4
Planning and Prerequisites
Chapter 2
Best Practices for WorldServer
Environments
As you plan your WorldServer environment, consider the hardware and software system
components you will need for your translation management processes.
WorldServer Components and System
Recommendations
The WorldServer installation involves several different components potentially residing
on several different machines.
SDL recommends that you run application and database servers on separate computers. 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 contain various machines that serve as clients,
servers, repositories, and databases.
Planning and Prerequisites
5
Best Practices for WorldServer Environments
Hardware requirements depend on the amount of data and the operational load expected
on the system. As a rule of thumb, the WorldServer application is CPU-intensive and
database processing is I/O intensive. Thus, the application server should have adequate
CPU power and the database server should have a fast disk subsystem and a lot of memory.
6
Planning and Prerequisites
Best Practices for WorldServer Environments
Prepare for Growth
Because most globalization needs grow over time, SDL recommends that you install
more powerful hardware than initial requirements would 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 it is to anticipate that future
growth at the outset.
The most important aspect of hardware configuration is the database server. WorldServer
is a very database-intensive application. The database system can never be too powerful.
The database server should have more emphasis on its I/O subsystem and memory than on
CPU power. Oracle (the recommended DBMS for large deployments) uses all the
memory and I/O bandwidth it can get. SDL recommends a fast RAID array. Good
performance is achieved on RAID0+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.
General guidance for minimal server configuration is as follows:
■
Smaller implementations: 2 x CPU Cores at 2.0 GHz each with at least 4 GB
RAM, running on Windows Server 2012 R2 (64bit)
■
Larger implementations: 4 x CPU Cores at 2.0 GHz each with at least 8 GB RAM
■
Database servers: 2 x 4 CPU at 2.0 GHz with 32 GB of RAM, as well as direct
connected/fibre channel connected SAN Storage (750 GB) plus 500 GB backup.
On the application server, disk space is only needed 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 will
be 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, we recommend that you separate servers running workflow
processes from those exposed for user requests. When WorldServer processes a large
project through a workflow, the workflow engine will take all the CPU it can get. If the
workflow engine runs on the same server as other WorldServer functions, this might
impact performance of other user requests and cause slower user interface response. A
separate workflow server helps to maintain good user interface response while processing
large project workflows. See Setting Up Clustered Workflow and Background Processing
Engines later in this document.
Planning and Prerequisites
7
Best Practices for WorldServer Environments
Dedicated Versus Shared Machines
SDL strongly recommends putting the WorldServer application on a dedicated application
server machine rather than under the same application server as other Web-based
applications.
In particular, there is no way to throttle the amount of the CPU given to Web-based
applications, which means that one application can “starve” the other applications. Since
WorldServer is very processor-intensive, it can degrade the performance of other
applications on the same machine.
Similarly, SDL generally recommends putting the WorldServer database under a dedicated
database server installation on a dedicated machine rather than sharing a database
instance with other applications.
Clustered Mode Planning
SDL designed WorldServer 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 power is sufficient. For scalability, SDL
recommends running 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.
Cluster setup provides many benefits over standalone configuration:
■
Performance – Spreading the load across multiple machines can greatly improve
responsiveness of the system and overall user experience.
■
Redundancy – A WorldServer cluster does not have any single point of failure
(except for the database). If a node in the cluster goes down, the service continues
uninterrupted, by switching requests to other nodes. WorldServer is a stateless
application—the user state is kept either in the database or on the client—and if a
node goes down, another node can continue the user session without a need to
login again and without any data loss.
■
High availability – Because taking down a node does not interrupt the service,
hardware maintenance can be performed one node at a time without service
interruption.
■
Specialization – The cluster can be specialized, based on your particular needs.
For example, if your process involves a lot of automatic processing, extra hardware
can be allocated for automatic task processing. If you experience a lot of user
interaction, then additional hardware can be used to boost user interface serving
(front-end) machines.
Clustering can include multiple WorldServer instances on a single machine (vertical
clustering) or multiple instances spread across different machines (horizontal clustering).
A mix of vertical and horizontal clustering is possible. SDL recommends putting no
more than two WorldServer instances per CPU. For example, a dual CPU box should not
run more than four WorldServer instances, or performance might degrade.
8
Planning and Prerequisites
Best Practices for WorldServer Environments
SDL does not provide any software to implement a cluster. You can build a cluster using
a Tomcat application server by simply installing multiple Tomcat instances and managing
them separately. You can use the Apache Web server load balancer plug-in in this
configuration. Commercial application servers like WebSphere have built-in facilities for
creating and maintaining a cluster. You can stop and start nodes, upgrade them at the
same time, and monitor their performance. WebSphere also has load balancing facilities
to spread the load across the nodes.
Clustered WorldServer deployments are designed to handle thousands of assets, translation
memory of millions of words, and multiple projects going through WorldServer at the
same time. They require more server and respository capacity, and usually include load
balancing capabilities and multiple machines.
Planning and Prerequisites
9
Best Practices for WorldServer Environments
In a cluster some configuration parameters must be shared across all the nodes while
others can be configured differently to allow for node specialization. Shared parameters
include:
■
Database – All instances must connect to the same database instance using the
same credentials (user/password)
■
Temporary directory – All instances must point to the same shared filesystem
for temporary directory (temp_file_path property in
general.properties).
■
RCS directory – If built-in version control is in use, the RCS directory must also
be located on a shared filesystem.
■
Additional configuration files (Translation memory, Terminology database,
sentence breaking, and import/export properties files) must be the same across all
instances.
Other configuration parameters can be configured differently between the nodes:
10
■
Log file location and log level – Each node can have a separate log file.
■
Number of workflow engines – Each node can run zero or more workflow
engines depending on its role in the cluster.
Planning and Prerequisites
Best Practices for WorldServer Environments
■
Whether rules engine is on or off – Each node may or may not run a rules
engine thread.
■
Notification engine – Each node may or may not run a notification engine.
Setting Up Clustered Workflow and Background
Processing Engines
In a generic WorldServer setup, a single WorldServer instance is used for the following
purposes:
■
It serves the application GUI that users interact with to create new projects,
upload translation kits, edit new documents, modify workflows, and so on.
■
It serves the workflow engine that executes the defined workflows.
■
It serves the background processing engine for any jobs that are submitted for
background processing.
In a larger installation, to improve performance, we recommend that you separate these
activities, assigning them to one or more machines. Specifically, we recommend that you
create one or more dedicated WorldServer application machines, one or more dedicated
business processing (workflow engine) machines, and one or more background processing
machines.
The primary benefit of this split is that you can provide adequate response times for each
of the WorldServer tasks. Workflows, for example, may consume large amounts of CPU.
When the workflow engine is on the same machine as the WorldServer application,
performance degradation on the application server can result. Similarly, if your
organization submits large jobs for background processing, response time can degrade.
Separating the WorldServer application, the workflow engine, and the background
processing engine allows you to eliminate this sort of resource contention.
In addition, separating the activities allows you to independently scale the resources
assigned to each. For example, you might start with three machines, each dedicated to
one of the three main activity areas. As more background processing occurs, you might add
more machines dedicated just to that one area.
Planning and Prerequisites
11
Best Practices for WorldServer Environments
Controlling Application Access
There is no specific setting to turn off the application portion of WorldServer. In particular,
you are likely to want the ability to log onto the WorldServer instances of worfklow and
background-processing machines to monitor jobs, configure logging settings, and so on.
The best way to ensure that these machines are not used as general-purpose WorldServer
application machines is to simply not give your users access to them. For example, if you
have inserted a load balancer in front of the WorldServer application machines, do not
include the dedicated engines in the list of machines over which you balance end-user
requests.
12
Planning and Prerequisites
Chapter 3
Platform Infrastructure
The WorldServer platform consists of the central application server, a Relational Database
Management System (RDBMS), and appropriate database clients and a File Type Support
(FTS) server for processing translation assets.
WorldServer Application Machine
Requirements
The central machine in any WorldServer deployment is the WorldServer Application
Server. This is the machine that manages all of the WorldServer processes, including the
workflow, translation memory, and document publishing.
Note: Products listed as supported have been qualified by SDL as part of each release.
We recommend that customers review with their product (application server, database and
operating system) providers or internal IT group as to whether an update would be
appropriate for their deployment and environment.
The following sections document the list of supported configurations for the WorldServer
application machine.
Supported Application Servers
■
Tomcat™ 7.0.53 (included with WorldServer) patched with tcnative-1.dll 1.1.30
or later
■
IBM® WebSphere® Application Server 7 or later
Planning and Prerequisites
13
Platform Infrastructure
Supported Application Server Operating Systems
Note: On 64-bit systems, a complete 64-bit infrastructure is recommended, including
Tomcat and Java versions.
■
Microsoft® Windows® Server 2012 R2 support (64-bit) standard and enterprise
editions
■
Microsoft Windows Server 2008 R2 support (64-bit) standard and enterprise
editions
■
32-bit x86 English Windows Server 2003, standard and enterprise editions
■
32-bit x86 Japanese Windows Server 2003, standard and enterprise editions
■
32-bit x86 Red Hat® Enterprise Linux® 4
■
32-bit and 64-bit Red Hat Enterprise Linux 5
■
32-bit and 64-bit Red Hat Enterprise Linux 6
Note: Platform Virtualization You can choose to deploy WorldServer in a virtualized
environment (such as VMware) with the following understandings:
■
WorldServer must support the environment in a non-virtualized form.
■
The platform vendor states that it supports the virtualized form of the environment.
■
You follow product vendor recommendations on use, configuration, and
maintenance of all products in a virtual environment.
■
Database resources are sufficient and consistently available at all times.
■
SDL's policy is to defer to system behavior and performance on a physical
machine, should problems arise.
Supported Application Server Java Versions
14
■
64-bit Java™ Standard Edition 7, update 25
■
32-bit Java™ Standard Edition 7, update 25
Planning and Prerequisites
Platform Infrastructure
Database Clients
If your database server resides on a different machine from the WorldServer application
server, the WorldServer application server machine needs to have the database client
installed for that database server.
Also, if you create the WorldServer database yourself (rather than letting the WorldServer
installer create it), and your database server is on a different machine from WorldServer,
you will need the Oracle or SQL Server client on the machine from which you create the
database, since database creation requires a management utility (like SQL Plus for Oracle
or iSQL for SQL Server).
Recommended Hardware for Application Server
SDL recommends that your WorldServer application server machine meet the following
minimum specifications:
■
Microsoft Windows servers:
■
Minimum 2 GHz processor (dual processor 3 GHz or better is
recommended)
■
Minimum of 2 GB RAM (4 GB or better is recommended)
■
Minimum of 100 MB space on disk before installing WorldServer (200
MB or better is recommended), plus additional space for your documents
(assets) if they are being stored on this machine
or
■
Red Hat® Enterprise Linux® servers:
■
Minimum 1 GHz processor (dual processor 3 GHz is recommended)
■
Minimum of 1 GB RAM (4 GB is recommended)
■
Minimum of 100 MB space on disk before installing WorldServer (200
MB is recommended) plus additional space for your documents (assets) if
they are being stored on this machine
Note: The monitor used for working with WorldServer should have a screen resolution
of 1024 x 768 pixels or higher.
Planning and Prerequisites
15
Platform Infrastructure
Database Server Requirements
WorldServer stores information about your WorldServer installation (for example, your
workflow definitions, translation memory, terminology database, and users) in a Relational
Database Management System (RDBMS).
The WorldServer database can reside on the same machine as the WorldServer server.
However, we recommend that you install the database server on a dedicated computer, and
that you locate applications and the content management system on other machines.
This section documents the supported configurations for the back-end WorldServer
database server.
Note: Products listed as supported have been qualified by SDL as part of each release.
We recommend that customers review with their product (application server, database and
operating system) providers or internal IT group as to whether an update would be
appropriate for their deployment and environment.
Supported Relational Database Management
Systems
SDL tests the compatibility of WorldServer with the following relational database
management systems:
■
Microsoft® SQL Server™ 2012 R2
■
Microsoft SQL Server 2008 R2 SP2
■
Microsoft SQL Server 2005 R2 SP2
■
32-bit and 64-bit English Microsoft SQL 2008 Server, standard and enterprise
editions
■
32-bit and 64-bit Oracle™ 10g Release 2 (10.2.0.2 and higher), standard and
enterprise editions
■
32-bit and 64-bit Oracle 11g Release 1 and Release 2, standard and enterprise
editions
Note: WorldServer does not support case-sensitive SQL Server. To use WorldServer
with SQL Server, you must configure SQL Server to be case-insensitive. The same
case-sensitivity restriction applies to Enterprise and Standard Editions, and to both 32-bit
and 64-bit versions of the SQL Server RDBMS.
Note: On 64-bit systems, a complete 64-bit infrastructure is recommended, including
Tomcat and Java versions.
16
Planning and Prerequisites
Platform Infrastructure
Note: As of the 11.0 version, SDL will no longer provide support for Microsoft SQL
Server 2005 and Microsoft Windows 2003 in WorldServer. Also, as of the 11.0 version,
only one installer will be provided: setup_64.exe.
Supported RDBMS Operating Systems
■
English Windows 2003
■
English Windows 2008
■
English Windows 2008 R2
■
English Windows Server 2012 R2
■
Linux
Note: Microsoft SQL Server is only supported on the Microsoft Windows platforms.
Recommended Hardware for Database Server
SDL recommends that your WorldServer database machine meet the following minimum
specifications:
■
Microsoft Windows servers:
■
Minimum 1 GHz processor (dual processor 3 GHz or better is
recommended)
■
Minimum of 2 GB RAM (8 GB or better is recommended)
■
SCSI RAID Disk Array with a minimum of 100 GB free disk space (250
GB or better is recommended).
or
■
RedHat Enterprise Linux servers:
■
Minimum 1 GHz processor (dual processor 3 GHz is recommended)
■
Minimum of 2 GB RAM (8 GB is recommended)
■
SCSI RAID Disk Array with a minimum of 100 GB free disk space (250
GB is recommended).
Planning and Prerequisites
17
Platform Infrastructure
Database Size Estimation
SDL designed WorldServer to handle extremely large amounts of data. However, it is
essential to estimate the amount of content a WorldServer installation will be required to
handle and to provide adequate hardware including storage capacity. Estimation of storage
requirements depends on the type of data to be used, the number of target languages
supported, typical user activity patterns, total system load in terms of how many projects
are turned around within a particular time frame, and many other factors.
Areas in WorldServer that can require a large amount of storage space include:
■
Translation memory (TM)
■
Terminology database (TD)
■
Segmented documents
Translation Memory
Translation memory size can be measured in either words or entries, where an entry
usually contains a single sentence. The average English sentence contains 15 to 20 words.
An analysis by SDL of customer translation memories confirmed this range with the
average word count being 17 words per sentence. If a translation memory size is measured
in the number of entries, the number of words is calculated using the following formula:
TMwords = 17 * TMentries
To estimate disk space required for a translation memory, the total translation memory
size in thousands of entries should be multiplied by a space factor that needs to be
calculated experimentally and is database dependent.
If you do not have any existing translation memories, the future translation memory size
can be estimated from the number of words that you expect to translate, using the formula
above.
Customers using the Studio file types introduced in WorldServer, and processed by the
FTS server, should expect that their translation memory size will increase over TMs
created with legacy WorldServer filters. This size increase should be covered by the
formula change described in the CONTENT entry for “Estimate Guidance” on page 19.
18
Planning and Prerequisites
Platform Infrastructure
Terminology Database
Terminology database (TD or termbase) size is measured in number of entries. Entries
usually contain one source term and one or more target terms. In most cases there is a one
to one correspondence, but a terminology database entry might contain several target
terms in each of several languages.
Segmented Documents
WorldServer segments all content into textual and markup elements. Usually, segmentation
is done on a sentence level; each sentence becomes a separate segment. WorldServer
stores this data in the application database and uses it as the internal document
representation. Each content asset (file) becomes a separate segmented document structure.
The size of this structure directly corresponds to the size of the document and the amount
of textual content it contains. The estimating factor in the final formula is based on
markup language formats (HTML, SGML, XML, and so on). For binary data formats
(DOC, PPT) the space factor is much smaller because most of the binary data deals with
formatting and does not get loaded into WorldServer.
Overhead
In addition to the three biggest storage contributors described above, there is also the
overhead of keeping all other WorldServer data, including users, projects, workflows, and
so on. This overhead is difficult to estimate because it is very dependent on the particular
usage pattern. However, SDL finds that 1 GB of space is more than enough to cover the
overhead for most WorldServer installations.
Estimate Guidance
Customers have used the following formula for estimating SQL Server database sizes for
WorldServer 9.x and earlier versions. Take your own environment and data into account
when you think about your own database needs.
Where:
■
TOTAL SPACE
Total space required for the database, in gigabytes (GB)
■
LANGS
Number of languages supported by the installation
■
TM
Expected translation memory size, in thousands of entries
Planning and Prerequisites
19
Platform Infrastructure
■
TD
Expected terminology database size, in thousands of entries
■
CONTENT
Total translatable content size, in megabytes (MB)
Customers using the studio file types introduced in WorldServer and processed by
the FTS server should expect that they will need more database space. Studio
file types may require up to three times the CONTENT space required for assets proces
sed by legacy WorldServer filters.
Note: Some files and assets that are processed with Studio file types may actually
require less storage space than when filtered with legacy filters (such as Microsoft
Word documents).
FTS Server Prerequisites
The FTS Server must be installed on a Microsoft Windows computer. The FTS launcher
runs as a Windows Service process. Individual FTS Servers run as Windows processes.
The FTS Server can communicate with WorldServer installations on Windows, Solaris or
Linux operating systems.
FTS System Requirements
It is important to understand the following requirements before you download and install
the FTS Server files.
■
Minimum operating system — Microsoft Windows Server 2003 Standard Edition
(32-bit Windows operating system).
■
(Recommended) Separate machine to host the FTS Server.
You can have multiple FTS Servers connected to your WorldServer installation.
The servers can share a single Windows computer. SDL recommends that you
install FTS Servers on a separate computer from WorldServer, but in lower-demand
installations a single FTS Server can reside on the same computer as a Windows
installation of WorldServer.
■
.NET Framework 4.0 (provided).
■
Shared directories for WorldServer and the FTS Server, supporting the shared file
system connection and the FTS Server log.
These are defined in the WorldServer general.properties file, with the
name ftsserver_shared_directory and are required as an entry for the FTS
server installation process.
Note: As of the 11.0 version, SDL will no longer provide support for Microsoft SQL
Server 2005 and Microsoft Windows 2003 in WorldServer. Also, as of the 11.0 version,
only one installer will be provided: setup_64.exe. FTS Server is a 32-bit application and
runs in 32-bit mode when running on a 64-bit machine.
20
Planning and Prerequisites
Platform Infrastructure
Note: When using the File Type Support server in WorldServer, it is important to note
that the default operating system cultures, default .NET cultures, and user defined cultures
determine which cultures are available. The version of Windows on which the File Type
Support server is installed also plays a role in which of the .NET culture codes are
available. Not all versions of Windows have all .NET cultures available. For example,
Windows Server 2003 does not support a number of cultures; such as, English (India),
English (Malaysia), etc. The same is true for some locales in WorldServer that have never
been supported by .NET. You can map these WorldServer locales with .NET cultures in
exchange.properties.
When deploying WorldServer and FTS in a mixed Unix/Windows environment and
using NFS, Windows Active Directory must be configured with Identity Management for
Unix. This enables you to map Windows user names to Linux user names.
All WorldServer and FTS Server Service 'run-as' users must have read/write access to:
■
The directory paths in UNC format for AIS file system mounts in WorldServer
■
The UNC path defined in general.properties to 'ftsserver_shared_directory' (Example: //servername/ pathname)
■
The UNC path defined in general.properties to WorldServer's 'temp_file_path' (Example: //servername/ pathname)
Databases Supported
The FTS Server uses the WorldServer database, and therefore works with the two
databases that WorldServer supports:
■
Microsoft SQL Server
■
Oracle
Note: Database clients are not required on the computer that runs the FTS server.
Planning and Prerequisites
21
Platform Infrastructure
Microsoft Office File Types
To process Rich Text Format (RTF) file types, you must install Microsoft Word 2007 or
Microsoft Word 2003 with the Office 2007 compatibility pack on the computer that runs
the FTS server.
22
Planning and Prerequisites
Chapter 4
Components Supported in
WorldServer
WorldServer is a robust enterprise-level application that interoperates with many different
components for managing translating projects and assets.
WorldServer includes support for many document formats, repository connectors,
third-party tools, servers, browsers, and applications. It complies with many industry
standards and supports over 300 different languages.
Note: Products listed as supported have been qualified by SDL as part of each release.
We recommend that customers review with their product (application server, database and
operating system) providers or internal IT group as to whether an update would be
appropriate for their deployment and environment.
Translatable Document Formats
WorldServer includes support for reading from and writing to documents in the following
formats.
Note: Starting with WorldServer 2011, new installations include support for Studio file
types, and all file type processing is handled by the File Type Support (FTS) Server. See the
FTS Server Prerequisites section of this guide for more information on supporting file
types.
Planning and Prerequisites
23
Components Supported in WorldServer
Supported Document Formats
24
■
Adobe FrameMaker (version 8.x-12.x, MIF files)
■
Adobe InCopy (CS4-CS6 ICML, InDesign CC files)
■
Adobe InDesign (CS4-CS6 IDML files)
■
Delimited Text (CSV files)
■
HTML 4 (ASCX, ASP, ASPX, HHC, HHK, HTM, HTML, INC, JSP, PHP,
Javascript files)
■
HTML 5 (.HTM, .HTML, .JSP, .ASP, .ASPX, .ASCX, .INC, .PHP, .HHK, .HHC)
■
Microsoft .NET Resources XML (RESX files)
■
Microsoft Excel 2000-2003 (XLS, XLT files)
■
Microsoft Excel 2007-2013 (XLSX, XLTX, XLSM files)
■
Microsoft PowerPoint 2007-2013 (PPTX, PPSX, POTX, PPSM , POTM, PPTM
files)
■
Microsoft PowerPoint XP-2003 (PPT, POT, PPS files)
■
Microsoft Word 2000-2003 (DOC, DOT, RTF files)
■
Microsoft Word 2007-2013 (DOCX, DOTX, DOCM, DOTM files)
■
OpenDocument Studio File Types (ODP, OTP, ODS, OTS, ODM, ODT, OTT
files)
■
QuarkXPress Export (TAG, XTG files)
■
Rich Text Format (RTF files)
■
Text (TXT files)
■
XHTML 1.1 (XHTML files)
■
XML, XSL files (Any XML and Custom XML file types), as well as Legacy
XML file types.
■
OASIS DITA XML (DITA files)
■
OASIS DocBook 4.5 XML (XML files)
■
W3C ITS Compliant XML (XML files)
Planning and Prerequisites
Components Supported in WorldServer
Content Repository Connectors
WorldServer connects to one or more content repositories to get access to the content that
needs to be translated. In most cases, WorldServer connects to an existing content
management system or source control system to access the content.
The WorldServer team has qualified connectors for the listed content repositories.
Qualified Content Repository Connectors
■
Perforce Software Configuration Management (SCM) system 2009.1 - 2014.
■
Microsoft SQL Server 2012 R2
■
Microsoft SQL Server 2008 R2 64-bit
■
Oracle 10g 32-bit
■
Oracle 11g 32-bit and 64-bit
■
SDL LiveContent Architect
■
SDL Trisoft 2011
■
SDL Tridion 2011
■
SDL Tridion 2013
Note: As of the 11.0 version, SDL will no longer provide support for Microsoft SQL
Server 2005 and Microsoft Windows 2003 in WorldServer. Also, as of the 11.0 version,
only one installer will be provided: setup_64.exe.
Other Content Repositories
SDL WorldServer is capable of connecting to virtually any other content repository,
through the use of the WorldServer SDK and associated web services. For more
information on other content repository integrations not listed, contact “SDL Professional
Services”, or review the corresponding SDK guides, documentation and samples.
Planning and Prerequisites
25
Components Supported in WorldServer
Third-Party Tools Included with WorldServer
WorldServer includes several third-party tools.
The following tools are located in the 3rdparty subdirectory of the distribution kit:
■
Apache Tomcat version 7.0.53 patched with tcnative-1.dll 1.1.30
WorldServer 10.4 also includes:
■
Sun JS2E Software Development Kit 1.7 for Windows deployments using the
WorldServer installer (Tomcat only)
■
Java Deployment Toolkit
■
JasperReports Server 5.2, under license from Jaspersoft
Browser Requirements
Most interactions with WorldServer are through a Web browser. WorldServer provides a
browser-based interface to perform nearly all tasks including:
■
Defining workflows
■
Managing users and permissions
■
Translating content
This section documents the supported Web browser configurations for WorldServer.
Supported Web Browsers
26
■
Microsoft Internet Explorer 10
■
Microsoft Internet Explorer 9.0
■
Mozilla® Firefox® 17 ESR (Extended Support Release)
■
Google™ Chrome™ 27 or later. Given the rapid update cycle of this browser, you
may find issues due to changes in browser behaviour. These will be addressed if
logged through the appropriate support channels.
Planning and Prerequisites
Components Supported in WorldServer
Supported Web Browser Java Versions
■
64-bit Sun Java ™ Runtime Environment 1.7
■
32-bit Sun Java ™ Runtime Environment 1.7
Recommended Hardware for Client
SDL recommends that your WorldServer client browser machine meet the following
specifications:
■
■
Microsoft Windows clients:
■
A minimum of 1 GHz processor
■
A minimum of 256 MB RAM
■
A high-speed network connection
Apple Mac OS clients:
■
A minimum of 1 GHz processor
■
A minimum of 256 MB RAM
■
A high-speed network connection
Note: The monitor used for working with WorldServer should have a screen resolution
of 1024 x 768 pixels or higher.
Desktop Translation Workbenches
WorldServer can export and import standard XLIFF allowing interactions with many
different desktop translation workbenches. SDL also provides the following direct
translation tool integrations:
■
SDL Trados Studio 2014
■
SDL Trados Studio 2011
■
SDL Trados Studio 2009
Note: Support for Desktop Workbench is no longer provided.
Planning and Prerequisites
27
Components Supported in WorldServer
Supported Interoperability Standards
■
XML Localization Interchange File Format (XLIFF) 1.2
■
Translation Memory eXchange (TMX) 1.2
■
Translation Memory eXchange (TMX) 1.3
■
Translation Memory eXchange (TMX) 1.4
Note: WorldServer is certified to be TMX 1.4 Level 1 compliant in terms of
import and export.
■
TBX 1j
Supported Languages for Translation
This section documents the languages that can be used during the translation process.
Note: Many translation tools require that you specify a locale as well as a base language.
For example, you cannot simply use “Dutch” as a source or target language, you must
specify “Dutch (Belgium)”.
28
Languages - “A”
Languages - “B” and “C”
Languages - “D” to “E”
Afar
Balante
Danish
Afrikaans
Bamanankan
Dari (Afghanistan)
Albanian
Banda
Divehi
Alsatian (France)
Baoule
Dutch
American Indian (Mexico)
Bashkir (Russia)
Dutch (Belgium)
Amharic
Basque
Dutch (Netherlands)
Arabic
Belarusian
Dzongkha
Arabic (Algeria)
Bemba
Edo
Arabic (Bahrain)
Bengali
Efik
Arabic (Egypt)
Bikolano
English
Arabic (Iraq)
Bislama
English (Australia)
Arabic (Jordan)
Bosnian (Cyrillic)
English (Belize)
Arabic (Kuwait)
Bosnian (Latin)
English (Canada)
Arabic (Lebanon)
Breton (France)
English (Caribbean)
Arabic (Libya)
Bulgarian
English (Hong Kong)
Planning and Prerequisites
Components Supported in WorldServer
Languages - “A”
Languages - “B” and “C”
Languages - “D” to “E”
Arabic (Morocco)
Burmese
English (India)
Arabic (Oman)
Cakchiquel
English (Indonesia)
Arabic (Qatar)
Catalan
English (Ireland)
Arabic (Saudi Arabia)
Chamorro
English (Jamaica)
Arabic (Syria)
Cherokee
English (Malaysia)
Arabic (Tunisia)
Chinese
English (New Zealand)
Arabic (U.A.E.)
Chinese (Hong Kong)
English (Philippines)
Arabic (Yemen)
Chinese (Macau)
English (Singapore)
Armenian
Chinese (PRC)
English (South Africa)
Assamese
Chinese (Singapore)
English (Trinidad)
Aymara
Chinese (Taiwan)
English (United Kingdom)
Azeri (Cyrillic)
Chuukese
English (United States)
Azeri (Latin)
Comorian
English (Zimbabwe)
Crioulo (Portuguese Creole) Estonian
Croatian
Ewe
Croatian (Latin) (Bosnia
and Herzegovina)
Czech
Languages - “F”
Languages - “G” and “H”
Languages - “I” to “K”
Faeroese
Gaelic (Ireland)
Iban
Fang
Gaelic (Scotland)
Ibibio
Fante
Galician
Icelandic
Farsi
Georgian
Igbo
Fijian
German
Ilocano
Filipino
German (Austria)
Indonesian
Finnish
German (Germany)
Inuktitut
Fon
German (Liechtenstein)
Inuktitut (Syllabics)
(Canada)
French
German (Luxembourg)
Inupiaq
French (Belgium)
German (Switzerland)
Italian
French (Cameroon)
Greek
Italian (Italy)
Planning and Prerequisites
29
Components Supported in WorldServer
Languages - “F”
Languages - “G” and “H”
Languages - “I” to “K”
French (Canada)
Greenlandic
Italian (Switzerland)
French (Cote d'Ivoire)
Guarani
Japanese
French (France)
Gujarati
Javanese
French (Haiti)
Gusii
K'iche (Guatemala)
French (Luxembourg)
Haitian
Kannada
French (Mali)
Hausa
Kanuri
French (Monaco)
Hawaiian
Kashmiri
French (Morocco)
Hebrew
Kashmiri (South Asia)
French (Reunion)
Hiligaynon
Kazakh
French (Senegal)
Hindi
Kekchi
French (Switzerland)
Hindi (Fiji)
Khmer
French (West Indies)
Hmong
Kikongo
French (Zaire)
Hungarian
Kirghiz
French Antillean (Patois)
Kiribati
Frisian (Netherlands)
Kiwai
Fulfulde
Konkani
Futa
Korean
Korean (Johab)
Kosraean
Kpelle
Krio
Kuna
30
Languages “L” to “M”
Languages - “N” to “Q”
Languages - “R” to “Sp”
Lao
Navajo
Rabinal Achi
Latin
Ndebele (Sindebele)
Rarotongan
Latvian
Neomelanesian (Tok Pisin)
Rhaeto-Romanic
Lingala
Nepali
Romanian
Lithuanian
Nepali (India)
Romanian (Moldova)
Lithuanian (Classic)
Niue
Rotuman
Lower Sorbian (Germany)
Nivacle
Rundi
Luganda
North Sotho (Sepedi)
Russian
Planning and Prerequisites
Components Supported in WorldServer
Languages “L” to “M”
Languages - “N” to “Q”
Languages - “R” to “Sp”
Luxembourgish
(Luxembourg)
Norwegian
Russian (Moldova)
Macedonian
Norwegian (Bokmal)
Rwanda
Macedonian (FYROM)
Norwegian (Nynorsk)
Sami (Inari) (Finland)
Makua
Nyanja
Sami (Lule) (Norway)
Malagasy
Occitan (France)
Sami (Lule) (Sweden)
Malay
Oriya
Sami (Northern) (Finland)
Malay (Brunei Darussalam) Oromo
Sami (Northern) (Sweden)
Malay (Malaysia)
Palauan
Sami (Skolt) (Finland)
Malayalam
Pampangan
Sami (Southern) (Norway)
Maltese
Pangasinan
Sami (Southern) (Sweden)
Mam
Papiamentu
Sami Lappish
Mandinka
Pashto
Sanskrit
Manipuri
Pocomchi
Serbian (Cyrillic)
Maori (New Zealand)
Pohnpeian
Serbian (Cyrillic) (Bosnia
and Herzegovina)
Mapudungun (Chile)
Polish
Serbian (Cyrillic)
(Montenegro)
Marathi
Portuguese
Serbian (Cyrillic) (Serbia)
Marshallese
Portuguese (Brazil)
Serbian (Latin) (Bosnia and
Herzegovina)
Mauritian (French Creole)
Portuguese (Portugal)
Serbian (Latin)
(Montenegro)
Maya
Punjabi
Serbian (Latin)
Mbundu (Ovimbundu)
Quechua (Bolivia)
Serbian (Latin)
(Montenegro)
Mende
Quechua (Peru)
Serbian (Latin) (Serbia)
Mohawk
Quiche
Seychellese (French Creole)
Mohawk (Canada)
Quichua (Ecuador)
Shona
Mongolian
Sindhi
Mongolian (Traditional
Mongolian) (People's
Republic of China)
Sindhi (Pakistan)
Moore (Mossi)
Sinhalese
Planning and Prerequisites
31
Components Supported in WorldServer
Languages “L” to “M”
Languages - “N” to “Q”
Motu (Hiri Motu)
Languages - “R” to “Sp”
Slovak
Slovenian
Solomonese
Somali
Sorbian
South Sotho (Sesotho)
Spanish
Spanish (Argentina)
Spanish (Bolivia)
Spanish (Castilian)
Spanish (Chile)
Spanish (United States)
32
Languages - “Sp” to “Sy”
Languages - “T”
Languages - “U” to “Z”
Spanish (Colombia)
Tagalog
Upper Sorbian (Germany)
Spanish (Costa Rica)
Tajik
Ukrainian
Spanish (Dominican
Republic)
Tamazight
Urdu
Spanish (Ecuador)
Tamazight (Latin)
Urdu (India)
Spanish (El Salvador)
Tamil
Uyghur (People's Republic
of China)
Spanish (Guatemala)
Tatar
Uzbek
Spanish (Honduras)
Telugu
Uzbek (Cyrillic)
Spanish (International Sort) Thai
Uzbek (Latin)
Spanish (Mexico)
Tibetan
Venda
Spanish (Modern Sort)
Tigrigna (Eritrea)
Vietnamese
Spanish (Nicaragua)
Tigrigna (Ethiopic)
Waray
Spanish (Panama)
Tsonga
Welsh
Spanish (Paraguay)
Tswana
Wolof
Spanish (Peru)
Turkish
Xhosa
Spanish (Puerto Rico)
Turkmen
Yapese
Spanish (United States
Tuvaluan
Yi
Planning and Prerequisites
Components Supported in WorldServer
Languages - “Sp” to “Sy”
Languages - “T”
Languages - “U” to “Z”
Spanish (Uruguay)
Twi
Yiddish
Spanish (Venezuela)
Tzotzil
Yoruba
Sranan
Yupik
Sutu
Zulu
Swahili
Swati
Swedish
Swedish (Finland)
Syriac
Planning and Prerequisites
33
Components Supported in WorldServer
34
Planning and Prerequisites
Chapter 5
Configuration Options
Every WorldServer installation has its own unique configuration. You should consider
which of the available options works for your environment. These options include such
things as Live Translation Memory (TM) mode.
Live Translation Memory Mode
WorldServer translation memories (TMs) can be configured to operate in live mode. In
live TM mode, entries are added to the translation memory constantly during the
translation process, and status is tracked to distinguish different types of entries.
Translation memories are updated whenever the segmented asset cache is updated. Any
operation that updates the segmented asset cache will update the translation memory (for
example, saves to the Asset Interface System, uploads from desktop translation tools,
and so on).
Note: SDL recommends enabling live TM mode, which is disabled by default.
In addition to enabling real-time sharing of translation memory, live translation memory
makes it possible to effectively update projects by restarting tasks without losing work.
The combination of live translation memory mode and segment status makes it possible for
translations to go into translation memory as soon as possible for the benefit of all
translators. At the same time translators can distinguish between translations that have
been through a review process and those that might have just been added.
As translators work, the source and target text are copied from the segment cache to
translation memory. Segment translation status (of Pending Review, Reviewed, Rejected,
or no status) determines if a segment is added to or updated in the translation memory
and what translation status the corresponding entry should have.
Planning and Prerequisites
35
Configuration Options
Differences Between Live TM Mode and
Non-Live Mode
The following table summarizes some of the behavior differences between live translation
memory mode and non-live mode.
36
Area
Live Mode On
TM Update
Whenever segment cache is On explicit calls to update
touched.
TM. (Note that all entries
added to TM are set to
Reviewed.)
Browser Workbench
No Save and Update TM
button.
XLZ Import
No Update the translation Has an Update the
memory using imported
translation memory using
assets check box.
imported assets check box
as in previous versions of
WorldServer.
Import of other translation
kit formats (besides XLZ)
Segments with a none status are set to Pending
Review.
Planning and Prerequisites
Live Mode Off
Has a Save and Update
TM button as in previous
WorldServer versions.
No special behavior.
Configuration Options
Area
Live Mode On
User type permissions and
ACL privileges
Same as in previous
The following user type
permissions are meaningless versions of WorldServer.
and hidden:
■
Can save asset and
update TM
■
Can modify TM
during Upload
Live Mode Off
If a user that has only Read
ACL privilege for a TM
opens an asset in the
Browser Workbench, the
workbench does not present
a Save button, and issues
this message:
WARNING: You do not
have permission to
update
translation memory
"<TM>". Write permission
is required when using Live
Translation Memory.
Please, contact your
WorldServer Administrator.
For the user to be able to
work in the Browser
Workbench in Live TM
mode, the administrator
must give that user Write
ACL privilege for that TM.
Logging
Anytime WSAssetTransl- No special behavior.
ation. saveTranslationToTm() is called, a
warning is logged with a
stack trace.
Leverage
TM entry translation status
affects segment status.
TM entry translation status
does not affect segment
status unless Segment Asset
automatic action is used
with Set Translation
Statuses? and Maximum
Translation Status
for 100% Matches arguments set to Yes and Pending.
Planning and Prerequisites
37
Configuration Options
38
Planning and Prerequisites
Chapter 6
Platform Support Changes History
The SDL WorldServer development team continually improves the capabilities of the
WorldServer environment, and expands support for industry-standard platforms and tools.
The SDL WorldServer development team continually improves the capabilities of the
WorldServer environment, and expands support for industry-standard platforms and tools.
The following summary of platform changes is provided for reference only, and should
not be used as a definitive list of all the features and changes in any one WorldServer
release.
Release Feature List
Changes for WorldServer 10.4.3
■
Embedded Content Processors enable WorldServer filters to process multiple
custom XML Content Types using default settings.
■
Added Microsoft Windows Server 2012 R2 as a supported operating system. The
supported Tomcat version has been upgraded to 7.0.55. Oracle® and Microsoft®
SQL Server drivers were updated to the latest available version. Also, support for
MultiTerm 2014 SP2 has been added.
■
Enhanced compatibility with SDL Trados Studio: the timeout interval of the
return package is now editable and the default value is now 900 seconds. When a
WorldServer Translation Provider is set to Live, TMs in both WorldServer and
SDL Trados Studio update accordingly in the case of segments with tags contained
in a package. The Core Components have been aligned with those available in
SDL Trados Studio 2014 SP2.
■
Updated and improved filters: Adobe® InDesign® Cloud version 10, Adobe
FrameMaker 12, multiple custom XML Content Types.
Planning and Prerequisites
39
Platform Support Changes History
Changes for WorldServer 10.4.2
■
Added Microsoft Windows Server 2012 as a supported operating system
■
Added SQL Server 2012 as a supported database management system
■
Added Perforce 2014 as a supported qualified content repository connector
■
Better compatibility with Studio in terms of TM edits display. Both solutions now
use the same Core Components (March 2014 edition)
■
Several website security enhancements
■
The supported Tomcat version has been upgraded to 7.0.53, patched with
tcnative-1.dll 1.1.30
■
The supported MultiTerm Server version has been upgraded to the 2014 SP1
version
Changes for WorldServer 10.4.1
■
Implemented Multi-Criteria search, saved searches, multi-criteria error handling
■
Offline/Online Studio Package Translation Memory (TM) selectable from the
interface
■
Upgraded HTML 4, HTML 5, PPTX and Java Resources filters to match SDL
Trados Studio's File Types
■
BrowserWorkbench (BWB) issues fixed
Changes for WorldServer 10.4
40
■
Added support for Tomcat 7 and Java 7, Jasper 5.2 (Java 6, Tomcat 6 and Jasper
4.x are no longer supported), Internet Explorer 10, .NET 4.0, Google Chrome and
Mozilla Firefox 17
■
Improved Studio integration with better translation package and export penalties
and other miscellaneous improvements
■
Added reports Dashboard on Home page
■
New design of the login page
■
Improved FTS server with .NET 4.0 and the upgrade of filters (HTML4 filter
improved, HTML5 filter added)
■
Improved Search features with the use of the "and" logical operator, enabling
multi-criteria searches and saved searches.
Planning and Prerequisites
Platform Support Changes History
Changes for WorldServer 10.3
■
WorldServer/Studio integration improvements including live TM/segment updates
■
Japanese localization of user interface, guides and help
■
File type support enhancements including support for Microsoft Office 2013
■
Usability enhancements such as the option to reset passwords
■
Security enhancements including the option to disable the Jasper Reports Server
Heartbeat.
Changes for WorldServer 10.2.1
■
WebSphere 7
■
Red Hat Enterprise Linux 6
■
German localization of user interface (updates)
■
German localization of guides
■
Chinese localization of user interface (updates)
■
Chinese localization of guides
Changes for WorldServer 10.2
■
Regulated Industry Labeling Support (Pharma 1.0)
■
Integration with MultiTerm Server 2011
■
Browser support updates
■
Internet Explorer 9
■
Mozilla Firefox 10 ESR
■
TM Attribute Penalty Support for Studio Filters
■
Import .SDLXLIFF/TTX into TMs
Planning and Prerequisites
41
Platform Support Changes History
Changes for WorldServer 10.1
■
German Localization of User Interface
■
Chinese Localization of User Interface
■
JasperReports based Report Center (replaces ScopeServer)
■
SDL Tridion 2011 Connector
■
End of Life – Support for TTX files
■
SDL BeGlobal TouchPoint support via SDL GlobalConnect
■
Infrastructure Updates
■
Java 6
■
Apache Tomcat 6
■
Oracle 11g 64bit support
■
MS SQL Server 2008 support (32bit and 64bit)
■
MS Windows Server 2008 support (32bit and 64 bit)
Changes for WorldServer 10.0
■
Added Studio-Aligned Translation Memory Mode
■
Extended Studio file type support to the Studio file types listed in the Translatable
Document Formats section of this guide.
■
File Type Support (FTS) Server Information
■
Ad Hoc Job Clean-up
■
Bulk User Management updates
Changes for WorldServer 9.4
42
■
Added File Type Support (FTS) server to provide file segmentation compatibility
across SDL product lines
■
Added early evaluation support for seven Studio file types, including Adobe
FrameMaker, Microsoft Word 200-2003, and five XML flavors
■
Added support for Java 1.5
■
Added browser client support for Microsoft Internet Explorer 8.0
Planning and Prerequisites
Platform Support Changes History
Changes for WorldServer 9.3
■
Updated support for SDL Trados Studio 2009
■
Added support for Oracle 11
■
Added support for Firefox 3.5
■
Added support for Perforce 2009.1
■
Added support for InDesign CS3 and CS4
Changes for WorldServer 9.2
■
Added support for SDL Trados Studio 2009
■
Added integration with SDL Global Authoring Management System (AuthorAssistant™)
■
Added SDK library of supported components
■
Added support for SDL Enterprise Translation Server
Changes for WorldServer 9.1
■
Added support for Tomcat Application Server 5.5.27
■
Added support for all languages officially supported by Java 1.4, as both source
and target languages
■
Added AIS connector for SDL Trisoft Component Content Management Server
■
Added automatic actions for converting Microsoft Office files between Office
2003 and Office 2007 (OpenXML) file formats
■
Added translation memory search option for finding and deleting duplicate entries
Acknowledgments
SDL WorldServer includes open source or similar third-party software.
“JasperReports Server”
JasperReports Server is a stand-alone and embeddable reporting server. It provides
reporting and analytics that can be embedded into a web or mobile application as well
as operate as a central information hub for the enterprise by delivering mission critical
information on a real-time or scheduled basis to the browser, mobile device, printer, or
email inbox in a variety of file formats. JasperReports Server is optimized to share,
secure, and centrally manage your Jaspersoft reports and analytic views.
Planning and Prerequisites
43