Installation Guide SDL Studio GroupShare 2014

Document technical information

Format pdf
Size 3.9 MB
First found Jun 9, 2017

Document content analysis

Language
English
Type
not defined
Concepts
no text concepts found

Persons

Organizations

Places

Transcript

SDL Studio
GroupShare 2014
Installation Guide
Table of Contents
Chapter 1
Overview of The Installation Process
Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Other sources of information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Structure of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Pre-installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
About SDL GroupShare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
What the GroupShare installer program can install . . . . . . . . . . . . . . 1-4
System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Overview of Servers and Server Roles in GroupShare. . . . . . . . . . . . . . . . . . . . . . 1-6
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Computer sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Operating system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Database Size Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Third-Party Software Installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Chapter 2
Pre-Installation Configure IIS
Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Configure IIS 7.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Configure IIS 8 and IIS 8.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Chapter 3
Pre-Installation Configure Microsoft SQL Server
Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Supported Microsoft SQL Server installations. . . . . . . . . . . . . . . . . . . . 3-2
Overview of the process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Before You Start Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Database Server is installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Database Server has an appropriate user account . . . . . . . . . . . . .
The GroupShare installer can connect to the Database Server . . . . . . .
3-3
3-3
3-3
3-3
Preparing the Microsoft SQL Server Database Manually . . . . . . . . . . . . . . . . . . . . 3-5
Scrips for a first time install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Scripts for upgrading to GroupShare 2014 SP2 . . . . . . . . . . . . . . . . . . 3-5
Scripts for upgrading to GroupShare 2014 SP2 . . . . . . . . . . . . . . . . . . 3-5
GroupShare SP1 and GroupShare SP2 use different schema definitions only
for upgrading the TM database containers. To upgrade from GroupShare 2014 SP1 manually, upgrade any
existing database containers to the GroupShare 2014 SP2 format. For information on how to do this, see
the Scripts for upgrading Translation Memories to the 2014 SP2 format section below. . . . . . . . . . . . 3-6
Chapter 4
The Installation Procedure
Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Microsoft SQL Server Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Before You Start Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Prerequisites for Microsoft SQL Server installations . . . . . . . . . . . . . . 4-4
Microsoft .NET Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Microsoft WCF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Microsoft Message Queue (MSMQ) Server Core/MSMQ Service . . . 4-5
License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Recommendation: upgrade from TM Server 2009 versions . . . . . . . . 4-5
Create a user account for the server application . . . . . . . . . . . . . . . . . 4-5
When Installing over Multiple Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Order to run the installer on different computers . . . . . . . . . . . . . . . . 4-7
Windows domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Note on required Database Access Components . . . . . . . . . . . . . . . . 4-7
Before You Install the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
2
Install GroupShare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Choose products to install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Choose server roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Select database type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Checking prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Choose installation folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Choose folder for storing files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Parameters for email notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Parameters for email templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Services configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Website parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Message: The installer has detected that the website parameters.... . 4-20
Ready to install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Installing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
GroupShare Set Up: Microsoft SQL Server Configuration Phase . . . . . . . . . . . . . 4-23
Enter Database Server details for Microsoft SQL Server . . . . . . . . . . . 4-23
Database Service account details for Microsoft SQL Server . . . . . . . . 4-24
Configuring System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Administrative Login Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Install MultiTerm Administrator on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Chapter 5
Post-Installation Configure IIS
Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Enabling and Disabling Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Providing HTTPS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Get an X.509 certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
To enable HTTPS binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Run time settings on the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
To disable HTTP binding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Enable TCP Endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Chapter 6
Post-Installation Configure MultiTerm
Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Install MultiTerm Administrator on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Configure SDL MultiTerm Online-Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Upgrading from Earlier SDL MultiTerm Versions . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Move Termbase Data to a New Database Server . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3
Install MultiTerm Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Configure MultiTerm Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Configuring MultiTerm Online to use SSL . . . . . . . . . . . . . . . . . . . . . . 6-8
Troubleshoot Browser Connection to MultiTerm Online . . . . . . . . . . . . . . . . . . . 6-10
Where to Change SDL MultiTerm Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Chapter 7
Post-Installation Configure TM Server
Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Overview: Upgrading from Earlier SDL TM Server Versions. . . . . . . . . . . . . . . . . 7-2
Upgrading from TM Server 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Upgrading from TM Server 2011. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Use TMs Created by Previous SDL TM Server Versions . . . . . . . . . . . 7-3
Before you start: register database server with TM Server 2014 . . . . . 7-3
To register a pre-existing container with TM Server 2014 . . . . . . . . . . 7-4
Post-Upgrade: Check and Decommission Previous Versions. . . . . . . . . . . . . . . . 7-5
Chapter 8
Reference
Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
GroupShare program installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Log files and other program data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Registry keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Unpacked installation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
GroupShare use of UDP and TCP/IP ports . . . . . . . . . . . . . . . . . . . . . 8-2
Windows User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Installer created user accounts and groups . . . . . . . . . . . . . . . . . . . . . 8-4
Resources and access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
GroupShare User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
GroupShare logon information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Installer created GroupShare user accounts . . . . . . . . . . . . . . . . . . . . 8-6
GroupShare standard roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Import User Details into GroupShare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Running the User Import Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Importing from an LDAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Password Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4
Run Time Access to SDL GroupShare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
From a browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
From SDL Trados Studio or SDL MultiTerm . . . . . . . . . . . . . . . . . . . . 8-9
Run Time Access to SDL MultiTerm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
To open SDL MultiTerm Server from SDL MultiTerm Administrator. 8-10
To open SDL MultiTerm Online from a browser . . . . . . . . . . . . . . . . . 8-10
Digital Certificate Requirements..............................................................................8-11
Uninstallation and Re-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
To modify or uninstall GroupShare components. . . . . . . . . . . . . . . . . 8-12
Re-installing GroupShare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
5
Copyright
Installation Guide
SDL STUDIO GROUPSHARE INSTALLATION GUIDE
Copyright 2007–2014 SDL Group.
Nothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of 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 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 Studio GroupShare, SDL Studio GroupShare Console, SDL Trados Studio, SDL MultiTerm, SDL MultiTerm Online
and SDL MultiTerm Administrator are registered trademarks 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
Acknowledgments section. 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.
Acknowledgments
SDL Studio GroupShare includes open source or similar third-party software:
C
C
C
C
C
Sharpziplib and Spring.net distributed under GNU General Public License version 3 with restrictions
ICU distributed under IBM ICU License
Log4Net, Xalan and Xerces distributed under Apache License version 2.0
Wix distributed under Common Public License version 1.0
Nalpeiron Licensing Services distributed under license
This guide ships with SDL Studio GroupShare 2014.
November 2014
SDL GROUPSHARE 2014 INSTALLATION GUIDE
O V ERVI EW O F THE
IN S TALLATI ON P R OC ES S
An introduction to SDL GroupShare and an overview of the installation process.
Contents
C
About this Guide
C
Structure of this Guide
C
System Architecture
C
Overview of Servers and Server Roles in GroupShare
C
System Requirements
C
Database Size Requirements
C
Third-Party Software Installed
C
Installation Media
Chapter
1
Overview of The Installation Process
ABOUT THIS GUIDE
SDL Studio GroupShare contains the following components: TM Server, Project Server and
MultiTerm Server. This guide contains instructions for installing all these components.
Within the guide, SDL Studio GroupShare will be referred to in short form as GroupShare.
Intended audience
This guide contains information for whoever is responsible for installing, setting up and
maintaining GroupShare on a Microsoft SQL server (usually the GroupShare administrator).
To install GroupShare an Oracle server, see the GroupShare 2011 Installation Guide. GroupShare
2011 remains the active release for Oracle as GroupShare 2014 does not support Oracle database
back-ends.
You are assumed to be familiar with standard Windows administration practices, such as managing
a Windows user account.
Other sources of information
C
SDL GroupShare Online Help at
http://producthelp.sdl.com/SDL_Studio_Groupshare_2014/en/Index.htm
C
SDL Knowledge Base at kb.sdl.com
C
SDL Product Installation Guides
C
SDL MultiTerm Extract Tools Guide
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-2
1
Overview of The Installation Process
STRUCTURE OF THIS GUIDE
This chapter provides an overview of GroupShare and a description of the various components
installed by the installer.
Pre-installation
Chapter 2, Pre-Installation Configure IIS describes setting up IIS in preparation for installation.
Installation
Chapter 3, Pre-Installation Configure Microsoft SQL Server describes the steps you need to perform
prior to installing GroupShare on a Microsoft SQL server.
Chapter 4, The Installation Procedure describes the procedure to install GroupShare.
Post-installation
Chapter 5, Post-Installation Configure IIS describes optional modifications that you can make to IIS
after installation.
Chapter 6, Post-Installation Configure MultiTerm describes additional steps needed after installing
MultiTerm.
Chapter 7, Post-Installation Configure TM Server describes additional steps needed after installing
TM Server.
Reference
Chapter 8, Reference contains reference material.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-3
1
Overview of The Installation Process
ABOUT SDL GROUPSHARE
What the GroupShare installer program can install
The installer can install the following programs:
C
TM Server
C
MultiTerm Server, including SDL MultiTerm Online and MultiTerm Administrator
C
Project Server
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-4
1
Overview of The Installation Process
SYSTEM ARCHITECTURE
You can install the GroupShare components on one or more computers.
GroupShare Servers
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-5
1
Overview of The Installation Process
OVERVIEW OF SERVERS AND SERVER ROLES IN
GROUPSHARE
GroupShare consists of a number of servers. You can set up a multi-computer installation, that is
one that has different servers on different computers.
Example: different computers for the database and the GroupShare components
A common configuration is as follows:
C
One computer has the web site. This computer can be in the DMZ. All access to GroupShare
is through this computer.
C
A second computer has all the GroupShare components except the web site.
C
The database server is on a third computer.
D
NOTE
Installing different servers onto different computers enhances performance, and allows you to
scale up the system if and when performance requirements grow. Contact SDL Professional
Services for more information.
Servers
The available servers are as follows:
Web Server
All requests to an Application Server come through a Web Server. A computer performing the web
Server role needs Microsoft IIS installed and appropriately configured.
You can have one Web Server, which hosts all the GroupShare web services, or two: one to host the
TM Server and Project Server web sites, and another to host the SDL Anywhere WCF Router.
SDL MultiTerm Online Server
The SDL MultiTerm Online Server hosts the main MultiTerm Online web application. It allows
users to access MultiTerm Server from a browser.
The SDL MultiTerm Online Server requires Apache Tomcat to be installed and configured. See
Chapter 6, Post-Installation Configure MultiTerm.
Application Server
The Application Server hosts application services provided by Project Server, TM Server or
MultiTerm.
You can have one Application Server, which hosts all GroupShare applications, or two: one to host
TM Server and Project Server, and another to host MultiTerm.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-6
1
Overview of The Installation Process
The Application Server communicates with the Web Server using a TCP connection that is
configured during installation.
Database server
The database server hosts the database and provides the storage for translation memories and
termbases managed by GroupShare.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-7
1
Overview of The Installation Process
SYSTEM REQUIREMENTS
Single CPU and multi-CPU computers are supported, as are 32-bit and 64-bit operating systems.
Computer sizing
E
RECOMMENDATION
SDL recommends a recent mid-range server with an Intel Xeon CPU and 8 GB of RAM.
Large installations
A large TM Server installation is one that has more than 10 million translation units in all and one
or more translation memories with more than one million translation units.
A large MultiTerm installation is one that has more than one million entries in all and one or more
termbases with more than 250 000 entries.
For large installations, install the Application Server and the database server on separate computers.
For more help in configuring large installations, contact SDL Professional Services.
Operating system requirements
GroupShare runs on the following platforms:
C
Windows Server 2008 R2, with IIS 7.5
C
Windows Server 2012, with IIS 8.0
C
Windows Server 2012 R2, with IIS 8.5
Supported Database Servers
GroupShare supports the following SQL Server versions:
C SQL Server 2014
C SQL Server 2012
C SQL Server 2008
E
RECOMMENDATION
SDL recommends that you use the latest SP versions of SQL Server 2014, 2012 and 2008.
GroupShare may have performance issues if you use earlier versions of these SQL Server
releases. See, for example, http://support.microsoft.com/kb/957205).
If you plan to use SQL Express, make sure that you use the Advanced Services edition. For SQL
Express 2014, see http://msdn.microsoft.com/en-us/evalcenter/dn434042.aspx
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-8
1
Overview of The Installation Process
The GroupShare installation does not include Microsoft SQL Server. If you do not have access to a
full version of SQL Server, you can download the free SQL Server 2012 Express with Advanced Services
from http://microsoft.com/express/Database. This version includes the full text search engine option
which is required for completely supporting the Full Text Search option in MultiTerm.
SQL Server 2012 Express with Advanced Services has a limit of 10 GB data storage for each database.
If you need more data storage, upgrade to a full version of SQL Server. For more information, see the
next section, ”Database Size Requirements”.
For information on finding the right server hardware (including choice of RAID architecture),
contact SDL Professional Services.
D
NOTE
You cannot install GroupShare 2014 on an Oracle server as GroupShare 2014 does not support
Oracle database back-ends.
GroupShare 2011 remains the active release for Oracle. For information about installing
GroupShare 2011 on Oracle, see the GroupShare 2011 Installation Guide.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-9
1
Overview of The Installation Process
DATABASE SIZE REQUIREMENTS
A typical translation memory with character-based concordance searching disabled uses
approximately 4 KB per bilingual translation unit (TU), so a TM with a million TUs needs
approximately 4 GB of disk space.
If character-based concordance searching is activated, the TM needs more space. The amount
depends on the language: alphabetic writing systems need about 8 KB per TU.
E
RECOMMENDATION
SDL recommends that for alphabetic writing systems, you do not enable character-based
concordance on TMs with more than 100 000 TUs. Usually, therefore, you do not have
character-based concordance searching on server-based TMs.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-10
1
Overview of The Installation Process
THIRD-PARTY SOFTWARE INSTALLED
If the installer is online and the following software is not already installed, the installer installs it (32bit versions unless otherwise specified). See also section Chapter 4, Before You Start Installing.
Installed for all GroupShare components
Downloaded if missing
C
Windows Installer 4.5
C
.NET 4.5
Included in the installation package
C
Microsoft Visual C++ 2005 SP1 Runtime
C
Microsoft Visual C++ 2008 SP1 Runtime
C
Microsoft Visual C++ 2010 Runtime
C
Microsoft Management Console 3.0
C
Microsoft IIS URL Rewrite Module 2.0 (32-bit or 64-bit, depending on OS)
C
Microsoft Web Farm Framework 2.2 (32-bit or 64-bit, depending on OS)
C
Microsoft Application Request Routing 3.0 (32 or 64bit depending on OS).
GroupShare installs the three SQL Server components essential for GroupShare if your current SQL
Server version does not include these components:
C
Microsoft SQL Server 2012 Management Objects
C
Microsoft SQL Server Native Client
C
Microsoft SQL Server System CLR Types
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-11
1
Overview of The Installation Process
INSTALLATION MEDIA
When you purchase SDL software, you download the software from the Account section of the
Downloads section of the SDL Account at oos.sdl.com. Run the installer from the folder in which
you stored the downloaded files.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
1-12
1
P R E -INSTA LLA T ION
CO N F IG U RE I I S
Before installing GroupShare on the web server, make sure the
IIS features required for the GroupShare infrastructure are
installed on your system.
The information in this chapter is intended for users who are
familiar with IIS.
Contents
C
Configure IIS 7.5
C
Configure IIS 8 and IIS 8.5
Chapter
2
Pre-Installation Configure IIS
CONFIGURE IIS 7.5
To configure IIS 7.5 on Windows Server 2008 R2, open Server Manager, select Roles > Web Server
> Add Role Services. The Select Role Services dialog box is displayed:
Make sure the following IIS features are installed:
Web Server (IIS)
Common HTTP Features
C Static Content
C Default Document
Application Development
C ASP.NET
C .NET Extensibility
C ISAPI Extensions
C ISAPI Filters
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
2-2
2
Pre-Installation Configure IIS
Health and Diagnostics
C HTTP Logging
C Logging Tools
C Request Monitor
Security
C Request Filtering
For more information about configuring IIS 7.5, see the Microsoft IIS site:
learn.iis.net/page.aspx/130/understanding-setup-in-iis-70
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
2-3
2
Pre-Installation Configure IIS
CONFIGURE IIS 8 AND IIS 8.5
To configure IIS 8 on Windows Server 2012 or IIS 8.5 on Windows Server 2012 R2:
1
Open Server Manager > IIS group.
2
Click Manage and choose Add Roles and Features from the drop-down menu. The Add Roles
and Features wizard is displayed:
3
On the Server Roles page, expand Web Server (IIS) > Web Server and make sure the following
roles are installed:
Common HTTP Features
C Default Document
C Static Content
Health and Diagnostics
C HTTP Logging
C Logging Tools
C Request Monitor
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
2-4
2
Pre-Installation Configure IIS
Security
C Request Filtering
Application Development
C .NET Extensibility 4.5
C Application Initialization
C ASP.NET 4.5
C ISAPI Extensions
C ISAPI Filters
For more information about configuring IIS on Windows Server 2012, see the following links:
C IIS 8 on Windows Server 2012: www.iis.net/learn/get-started/whats-new-in-iis-8/installingiis-8-on-windows-server-2012
C IIS 8.5 on Windows Server 2012 R2: www.iis.net/learn/install/installing-iis-85/installingiis-85-on-windows-server-2012-r2
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
2-5
2
P R E -INSTA LLA T ION
CO N F IG U RE M I CR OSOF T S QL
SERVER
Perform these steps prior to installing SDL GroupShare on
Microsoft SQL Server.
Contents
C
Overview
C
Before You Start Installing
C
Preparing the Microsoft SQL Server Database Manually
Chapter
3
Pre-Installation Configure Microsoft SQL Server
OVERVIEW
This chapter describes the steps you must perform prior to installing GroupShare on Microsoft SQL
Server.
Supported Database Servers
GroupShare supports the following SQL Server versions:
C SQL Server 2014
C SQL Server 2012
C SQL Server 2008
SDL recommends that you use the latest SP versions of SQL Server 2014, 2012 and 2008. GroupShare
may have performance issues if you use earlier versions of these SQL Server releases. See, for
example, http://support.microsoft.com/kb/957205).
If you plan to use SQL Express, make sure that you use the Advanced Services edition. For SQL
Express 2012 SP1, see for instance www.msdn.microsoft.com/en-us/evalcenter/hh230763.aspx
Supported Microsoft SQL Server installations
Microsoft SQL Server supports the following components of GroupShare:
C
TM Server
C
MultiTerm Server
C
Project Server
Overview of the process
1
Prepare the database. See Before You Start Installing.
2
Install the standard prerequisites. See Prerequisites for Microsoft SQL Server installations.
3
Manually create the databases, users and run the scripts to set up the environment. See
Preparing the Microsoft SQL Server Database Manually.
D
NOTE
4
Install GroupShare. See Install GroupShare.
You only need to do this is you are planning to select the Use existing Microsoft SQL Server and
configure manually option during installation. Use this option for a locked down enterprise
installation with heavy usage requirements.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-2
3
Pre-Installation Configure Microsoft SQL Server
BEFORE YOU START INSTALLING
Ensure that the following items are addressed before you install TM Server:
The Database Server is installed
As part of the installation, you provide the details of an existing database server.
If upgrading from TM Server 2009 SP1 or SP2
The GroupShare installer does not delete data on the Database Server. It does, however, remove any
references that the Database Server had to an existing GroupShare Application Server. For more
information on upgrading from SP1 or SP2, see Overview: Upgrading from Earlier SDL TM Server
Versions.
The Database Server has an appropriate user account
At runtime, GroupShare needs a user account on the Database Server with the SQL Server privilege
dbcreator. This can be created automatically by the installer based on the options you select.
The GroupShare installer can connect to the Database Server
The installer will create the required databases and sets all permissions. To do this, it needs a user
account with the sql server role sysadmin. You can disable the account used for installation when
installation is complete. You may need this account later if you wish to re-install, repair or upgrade
this product.
If you are creating the databases by hand, either ensure the GroupShare installer has the SQL Server
privilege db_owner on each database, or run the sql installation scrips and give the service account
access to each database and the server privilege dbcreator.
E
RECOMMENDATION
C
Put the Database Server and the Application Server in the same Windows domain (or have a
suitable trust relationship set up), so that you can use Windows authentication.
C
The GroupShare installation does not include Microsoft SQL Server. If you do not have access
to a full version of SQL Server, you can download the free SQL Server 2012 Express with
Advanced Services from http://microsoft.com/express/Database. This version includes the
full text search engine option required for fully supporting Full Text Search in MultiTerm.
D
NOTE
SDL concurs with the Microsoft recommendation that where possible you should use Windows
authentication to access an SQL database server
If the Database Server is in a different and untrusted domain from the Application Server, or if
the Application Server is on a machine in a workgroup, you may need to use SQL authentication
rather than Windows authentication.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-3
3
Pre-Installation Configure Microsoft SQL Server
PREPARING THE MICROSOFT SQL SERVER
DATABASE MANUALLY
This section contains instructions for manually creating databases and the order in which scripts
should be run for this process.
You only need to do this is you are planning to select the Use existing Microsoft SQL Server and
configure manually option during installation. Use this option for a locked down enterprise
installation with heavy usage requirements.
D
NOTE
If you are using Windows Integrated Security, the login that you create on the database server
has to be the same Windows account that runs the services on the application server.
Scrips for a first time install
This table shows the order in which scripts should be run:
Script Name
Database
Name
Run this
script if
you are
installing
Project
Server
Enterprise2.Platform.Tables.svc.3.sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Programmability.svc.3
.sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Programmability.svc.
4.sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Tables.sts. 4.sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Programmability.sts.3
.sql
SDLSystem
yes
yes
yes
TMServer.Tables.2.sql
SDLSystem
yes
yes
ProjectServer.Tables.4.sql
SDLSystem
yes
ProjectServer.Programmability.4.sql
SDLSystem
yes
CreateSTSUsers.sql
SDLSystem
yes
InitializeMtMaster.sql
MTMaster
yes
SchemaVersion.sql
SDLSystem
yes
Run this
script if
you are
installing
TM
Server
Run this
script if you
are
installing
MultiTerm
Server
yes
yes
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-4
3
Pre-Installation Configure Microsoft SQL Server
Scripts for upgrading to GroupShare 2014 SP2
To upgrade from GroupShare 2011
Script Name
Database
Name
Run this
script if
you are
upgradin
g
Project
Server
Enterprise2.Platform.Programmability.svc.3
.sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Tables.svc.4.Upgrade.
sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Programmability.svc.
4.sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Programmability.sts.3
.sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Tables.sts.4.Upgrade.
sql
SDLSystem
yes
yes
yes
TMServer.Tables.3.Upgrade.sql
SDLSystem
yes
yes
ProjectServer.Tables.3.Upgrade.sql
SDLSystem
yes
ProjectServer.Tables.4.Upgrade.sql
SDLSystem
yes
ProjectServer.Programmability.4.sql
SDLSystem
yes
MtMaster.Tables.3.Upgrade.sql
MTMaster
yes
TermbasesSchema.3.Upgrade.sql
MTMaster
SchemaVersion.sql
SDLSystem
Run this
script if
you are
upgradin
g TM
Server
Run this
script if you
are
upgrading
MultiTerm
Server
yes
yes
yes
yes
yes
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-5
3
Pre-Installation Configure Microsoft SQL Server
To upgrade from GroupShare 2014
Run if
you
upgrade
TM
Server
Run if you
upgrade
MultiTerm
Server
Script Name
Database
Name
Run if you
upgrade
Project
Server
Enterprise2.Platform.Tables.svc.4.Upgrade.
sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Programmability.svc.
4.sql
SDLSystem
yes
yes
yes
Enterprise2.Platform.Tables.sts.4.Upgrade.
sql
SDLSystem
yes
yes
yes
ProjectServer.Tables.4.Upgrade.sql
SDLSystem
yes
ProjectServer.Programmability.4.sql
SDLSystem
yes
SchemaVersion.sql
SDLSystem
yes
yes
yes
To upgrade from GroupShare 2014 SP1
GroupShare SP1 and GroupShare SP2 use different schema definitions only for upgrading the TM
database containers. To upgrade from GroupShare 2014 SP1 manually, upgrade any existing
database containers to the GroupShare 2014 SP2 format. For information on how to do this, see the
Scripts for upgrading Translation Memories to the 2014 SP2 format section below.
D
NOTE
If you use the GroupShare installer, the TMs are upgraded automatically.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-6
3
Pre-Installation Configure Microsoft SQL Server
Scripts for upgrading Translation Memories to the 2014 SP2 format
For each TM container database that you want to upgrade manually, run the appropriate TMServer
SQL scripts from the SQLScripts folder under %Programdata%\Package
Cache\SDL\SDLStudioGroupShare2014_SP2\SQLScripts\SQLServer\
To upgrade TMs from GroupShare 2011
Run if you
upgrade
Project
Server
Run if you
upgrade
TM Server
Script Name
Database Name
TMServer-Upgrade-8.05-to8.06.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.06-to8.07.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.07-to8.08.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.08-to8.09.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.09-to8.10.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.10-to8.11.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.11-to8.12.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.12-to8.13.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.13-to8.14.mssql.sql
Name of your
database
containers
yes
Run if you
upgrade
MultiTerm
Server
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-7
3
Pre-Installation Configure Microsoft SQL Server
To upgrade TMs from GroupShare 2014
Run if you
upgrade
Project
Server
Run if
you
upgrade
TM
Server
Script Name
Database Name
TMServer-Upgrade-8.10-to8.11.mssql.sqll
Name of your
database
containers
yes
TMServer-Upgrade-8.11-to8.12.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.12-to8.13.mssql.sql
Name of your
database
containers
yes
TMServer-Upgrade-8.13-to8.14.mssql.sql
Name of your
database
containers
yes
Run if you
upgrade
MultiTerm
Server
To upgrade TMs from GroupShare 2014 SP1
TMServer-Upgrade-8.13-to8.14.mssql.sql
Name of your
database
containers
yes
Step 1: Create the following databases:
C
SDLSystem (required for Project, TM and MultiTerm Server)
C
MTMaster (required for MultiTerm server)
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-8
3
Pre-Installation Configure Microsoft SQL Server
Step 2: Create a login on the Microsoft SQL Server:
1
Add the server role ‘dbcreator’
2
Add user mappings (SDLSystem: ‘db_owner’ and MTMaster: ‘db_owner’)
Step 3: Run the scripts
1
Download the installer for GroupShare from the Downloads section of the SDL Account.
2
Double-click on the SDLStudioGroupShare.exe file to extract the binaries and scripts to the
default folder %Programdata%\Package Cache\SDL\SDL Studio
GroupShare2014_SP2\SQLScripts\SQLServer
D
NOTE
If TM Server or MultiTerm is required, the platform must be installed first.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-9
3
Pre-Installation Configure Microsoft SQL Server
3
GroupShare prompts you to accept the license agreement for.NET Framework 4.5 and install
this component if it is not already installed on your computer.
4
Leave the installer on the startup screen.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-10
3
Pre-Installation Configure Microsoft SQL Server
5
Run the required SQL scripts in the correct order (see table above).
6
After you have finished running the scripts and installing the other prerequisites, you
can return to the installer and finish the GroupShare installation process. See Install
GroupShare.
C On the Select Database Type page, select Use existing Microsoft SQL Server and configure
manually.
C When presented with the database configuration screens, enter the information for the
databases and users that you have created manually.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
3-11
3
TH E IN STALLATION
P R O C E D U RE
The procedure to install SDL GroupShare.
Contents
C
Overview
C
Information Needed Before You Start
C
Before You Start Installing
C
When Installing over Multiple Computers
C
Before You Install the Web Server
C
Install GroupShare
C
GroupShare Set Up: Microsoft SQL Server Configuration
Phase
C
Install MultiTerm Administrator on the Server
Chapter
4
The Installation Procedure
OVERVIEW
This chapter describes the installation of some or all the GroupShare components on the current
computer. It also describes some of the steps you need to perform prior to installing GroupShare.
Ensure that you have configured a database server with the latest SP versions of Microsoft SQL
Server 2008 or 2012 (preferably SQL Server 2012 or SQL Server 2012 Express with Advanced
Services)
Typically, but not necessarily, the Database Server is on another computer. Be aware that the installer
will need to make changes to the Database Server. You provide the location of the Database Server
to the installer as part of the installation process.
You can install GroupShare on a single computer, or install different components of the product on
separate computers.
Microsoft SQL Server Installations
Microsoft SQL Server installations support installing all three components of GroupShare: TM
Server, MultiTerm Server and Project Server.
Before installing GroupShare, ensure that you have performed the steps described in the beginning
of this chapter.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-2
4
The Installation Procedure
INFORMATION NEEDED BEFORE YOU START
During installation you will be asked to provide information that the installer needs. The
information needed depends on which of the following servers are installed on each computer. (See
also Chapter 1, Overview of Servers and Server Roles in GroupShare.) Hence, you should decide which
servers you install on each computer before you start.
You may need to provide the following information:
Web Server to Application Server link
C
If the Web Server and Application Server will be on different computers, provide the fully
qualified host name of the computer on which you will install the Application Server.
C
If you do not plan to use the default TCP port for Application Server (41000), provide the port
that you plan to use.
D
NOTE
Irrespective of which port the Application Server uses, if the Application Server is behind a
firewall, ensure that your firewall settings allow incoming TCP connections on this port.
Application Server to Database Server link and the application service user
C
Provide the SQL Server instance name that you will be using. This is often the same as the
host name of the Database Server, but may not be. Consult your database administrator.
C
Provide details of the user account that you will use for the application server service.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-3
4
The Installation Procedure
BEFORE YOU START INSTALLING
Before you run the installation procedure on any computer, check the following items.
Prerequisites for Microsoft SQL Server installations
Download the installer for GroupShare from your SDL Account.
If any of the following components are not already installed on your computer, the installer will try
to download them from the internet. If you are offline then you need to download and install them
before you start the installation:
C
.NET 4.5
C
Windows Installer 4.5
F
WARNING
If you are not online and these items are not installed, the installation will not succeed.
Microsoft .NET Framework
Microsoft.NET framework is needed on all GroupShare computers.
On computers using Windows Server 2012 and above, enable (rather than install) Microsoft .NET
Frameworks: In the Windows Server Manager, use the Add Features Wizard and select .NET
Framework 4.5.
D
NOTE
.Net 4.5 is a separate download and install on Windows Server 2008 R2.
Microsoft WCF
Microsoft WCF (Windows Communication Foundation) non-HTTP activation is needed on all
GroupShare computers.
In Windows Server 2008 R2, install the Application Server role. To do this, in the Window Server
Manager, use the Add Features Wizard: select Application Server and add TCP activation.
In Windows Server 2012, open the Add Roles and Features wizard. Under the Application Server
role > Windows Process Activation Service feature, enable Windows Process Activation Service
Support role service with the HTTP Activation and TCP Activation.
If you do not install WCF, you will get an error message similar to the one shown, which says:
‘The WCF Activation - Non-HTTP Activation Feature is not installed’.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-4
4
The Installation Procedure
Microsoft Message Queue (MSMQ) Server Core/MSMQ Service
The Microsoft Message Queue is a standard Windows component used for sending and receiving
messages. MSMQ is available from your Windows Features list and does not require a separate
license.
For information about installing MSMQ on different operating systems, see Install Message
Queuing on the Microsoft TechNet web site. GroupShare requires MSMQ for the Application Server
role.
License
You do not need a license to install GroupShare or to start it, but you need a separate license for each
application server. One license will cover all the GroupShare applications on a one server.
See the online Help on producthelp.sdl.com.
Operating systems
Ensure you are running one of the operating systems listed in Chapter 1, Overview of The
Installation Process.
Recommendation: do not install client software on GroupShare servers
The following client components of GroupShare should not be installed on the GroupShare server.
These products are:
C
SDL Trados Studio
C
SDL MultiTerm Desktop
Create a user account for the server application
The server application needs a Windows user account so that it can log on at run time. When you
install the server application, you will need to provide this user name.
Create a non-privileged user account. The GroupShare installer will give that account all the required
privileges.
Recommendation: use a Windows domain account
If you are in a Windows domain, create a domain wide user account for this purpose, not a local user
account. A domain wide account means you can use Windows authentication for the Database
Server and also means that at run time, GroupShare users will be able to use Windows domain
features. For example, they will be able to use Windows Active Directory to create another
GroupShare user.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-5
4
The Installation Procedure
E
RECOMMENDATION
SDL recommends that you set up the passwords for the server application user account and for
other service accounts so that they never expire. If the passwords expire (perhaps in accordance
with a security policy), then when they do so, the service will not work and diagnosis can be
difficult.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-6
4
The Installation Procedure
WHEN INSTALLING OVER MULTIPLE COMPUTERS
If you install different components of GroupShare on different computers, follow these guidelines.
Licenses
You need a separate license for each computer that runs an application server. You do not need an
SDL GroupShare license for the web server or database server.
Order to run the installer on different computers
To install GroupShare over multiple computers, run the installer separately on each computer.
When you run the installer, you choose the server roles that are to be installed on that computer.
When installing on multiple computers, it is usual to install the Application Servers before the Web
Server. However you can install the server roles in any order. You may need to restart services on the
Web Server after you install an Application Server.
D
NOTE
If you install the Web Server before you install the Application Server, and you enter incorrect
details in the Website parameters for the host name or port number, re-install the Web Server.
Windows domain
Ensure that all computers:
C
are in the same Windows domain, or are in a trust relationship.
C
use the same user account directory, typically Windows Active Directory.
Ensure that all GroupShare services in the configuration:
C
use the same name for the GroupShare web site.
C
run under the same Windows user account.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-7
4
The Installation Procedure
BEFORE YOU INSTALL THE WEB SERVER
Before you install the Web Server or SDL Anywhere, do the following:
C
Ensure that the web site name is registered in DNS.
C
Configure IIS. See Chapter 2, Pre-Installation Configure IIS. The installer will not complete
until IIS is configured appropriately.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-8
4
The Installation Procedure
INSTALL GROUPSHARE
Browse to the download folder and double-click the installation file. The installer extracts files in
preparation for the install.
D
NOTE
The extracted files are needed for the installation and also for uninstalling. If you delete these
files, you will need to download and extract them again to uninstall GroupShare.
The installer runs in two phases: installation and configuration. In the installation phase, you can
install GroupShare Web Server and Application Server. After installation has finished, the installer
proceeds to the configuration of the Database Server.
Fill in the pages in the order that they are displayed. Afterwards, you can go backwards and forwards
to change details as desired.
Note that depending on the options you choose, different pages are displayed. For example, the
Platform Website Parameters page is displayed only if you choose to install the Web Server (or SDL
Anywhere).
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-9
4
The Installation Procedure
Choose products to install
Select the GroupShare components:
C
SDL Project Server
D
NOTE
C
SDL TM Server
C
SDL MultiTerm Server
C If you select Project Server, TM Server is automatically selected also.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-10
4
The Installation Procedure
Choose server roles
On this page choose server roles for the current computer. The choice of server roles determines
which components are installed on the computer
D
NOTE
For more information about server roles, see Chapter 1, Overview of The Installation Process.
The available server roles are:
C
Application Server
D
NOTE
C
Web Server
C
SDL MultiTerm Online
The SDL GroupShare Console is automatically installed when this role is used.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-11
4
The Installation Procedure
Select database type
On this page select the database type and installation method.
C
Use existing Microsoft SQL Server and configure automatically - This option performs all the
configuration needed to run GroupShare against an existing SQL Server. Make sure you have
been given sufficient access. Use this option for an enterprise installation.
C
Use existing Microsoft SQL Server and configure manually - Select this option only if your DBA
has already pre-configured your SQL Server to run GroupShare by following the installation
instructions. Use this option for a locked-down enterprise installation.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-12
4
The Installation Procedure
Checking prerequisites
On this page the installer checks that you have all of the prerequisites installed. If one or more of the
prerequisites are missing, it will notify you of the missing prerequisites. You must then install these
prerequisites on the computer yourself. Once installed, return to the wizard and click Refresh. If all
of the prerequisites are installed, the Next button becomes active so that you can continue with the
installation.
D
NOTE
See Chapter 4, Prerequisites for Microsoft SQL Server installations for more information about
what prerequisites are needed.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-13
4
The Installation Procedure
Choose installation folder
On this page choose the folder under which to store the GroupShare program files. The default is:
C
(32-bit machines) %ProgramFiles%\SDL
C
(64-bit machines) %ProgramFiles(x86)%\SDL
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-14
4
The Installation Procedure
Choose folder for storing files
Here you can specify the folder where you want to save:
C
project files and project packages published to GroupShare from Studio
C
termbases imported/exported from SDL MultiTerm Online
C
translation memories imported/exported from TM Server
The GroupShare installer cannot check if network (UNC ) paths are valid. If you provide a UNC path
name, make sure that the folder you specify exists, and that the folder permissions allow to store files
in that location.
The default storage location is:
%ProgramData%\SDL\SDLServer1\FileStore
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-15
4
The Installation Procedure
Parameters for email notifications
This page is displayed if you choose to install the Application Server on the Choose Server Roles page.
GroupShare requires a working Simple Mail Transfer Protocol (SMTP) server in order to send out
notification emails when file assignments are created and edited in SDL Trados Studio 2014 and
later. Specify the settings for the SMTP server you want to use for sending email notifications.
You can change these settings at any time, from the GroupShare Console MMC snap-in.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-16
4
The Installation Procedure
Parameters for email templates
This page is displayed if you chose to install the Application Server on the Choose Server Roles page.
GroupShare uses a predefined email template which defines how the notification emails look like
and what information they contain. You can use your own email template to customize the email
notifications that GroupShare sends out when file assignments are created and edited in Studio 2014
and later. Specify what server address will be indicated for the assignments and where GroupShare
can find your customized email templates.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-17
4
The Installation Procedure
Services configuration
This page is displayed if you chose the Application Server role for this computer.
Provide the Windows user account that you have created for run time access. The installer creates
the local Windows group SDL Server Users and makes the specified account a member of that
group.
The installer assigns to the group those privileges that are required to run the server application. For
details on assigned privileges, see Chapter 8, Reference.
The Application service port must be the same port specified for the application service on the
Website parameters details.
D
NOTE
If the application server computer has a firewall, or is behind a firewall, ensure that the firewall
allows connections on the port that you specify.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-18
4
The Installation Procedure
Website parameters
This page is displayed if you are installing the SDL Web Server or SDL Anywhere on this computer.
Custom website location URI: specify the full URI (including any subfolders) where you want to
deploy the GroupShare website. If you leave this field empty, the GroupShare website is deployed
under the IIS website SDL Server.
Website host header: if the SDL Web Server is the only web site on this computer, you can leave this
field empty. However, if other web services on this computer use the same port, set a host header to
distinguish between them.
Website http port: Usually the default port number is satisfactory. However, you might need to
change it to accord with your company security policy. For example, you need to ensure that the
firewall does not block access to the specified port numbers.
Application Server Name and Port: Set the host name and TCP port of the Application Server. If you
have not yet installed the Application Server, enter the details that you plan to use for that server.
Host name: if you install the Application Server on this computer, enter localhost. If the
Application Server is on another computer, use the fully qualified name of that computer. The
default name is localhost.
TCP port: Ensure that the TCP Port number you specify here matches the one you specify for the
Application Server in the Platform Service Parameters page.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-19
4
The Installation Procedure
D
NOTE
The Web Server does not include a configuration screen to change these details after
installation. If you run the installer to completion with incorrect details for the Application
Server, or if you move the Application Server to another computer, re-install the Web Server.
Message: The installer has detected that the website parameters...
IIS already has a website running on this port. If you have just set up IIS as part of this installation,
click Yes and continue. If you have other web sites already running on this computer, click No to edit
the settings.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-20
4
The Installation Procedure
Ready to install
These pages allow you to review the items that are to be installed and change them before you go
ahead with the installation.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-21
4
The Installation Procedure
Installing Software
The installation program installs the components.
No reboot is required.
E
RECOMMENDATION
If you see a message similar to the one shown here, prompting you to reboot the computer, do
not do so.
Instead continue with the installation.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-22
4
The Installation Procedure
GROUPSHARE SET UP: MICROSOFT SQL SERVER
CONFIGURATION PHASE
After the installation wizard has installed the GroupShare Web Server and/or Application Server, it
prompts for the Database Server details. Follow these instructions if you selected a SQL Server
database type.
Enter Database Server details for Microsoft SQL Server
Complete this page with details of the Database Server, as follows:
Fill in the Server box with the name of an existing database server. When you click Next, the installer
program validates the name of the Database Server. At this stage, it does not attempt to connect to
the database.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-23
4
The Installation Procedure
Database Service account details for Microsoft SQL Server
Choose the appropriate authentication method.
If you choose Use Integrated Security (recommended), the application uses Windows authentication,
meaning that at run time the Application Server will use the service account details to log onto the
Database Server.
If you do not choose Use Integrated Security, the application will use SQL Server authentication at
run time. Be aware that in that case the password is not encrypted, and that the application does not
check password strength.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-24
4
The Installation Procedure
Configuring System
The installer displays a progress screen.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-25
4
The Installation Procedure
Administrative Login Required
The Administrator Login Required dialog box is displayed if the account you are logged in with does
not have sufficient user privileges to create the database.
Either restart the installation with a user account that has sufficient privileges on the Database
Server, or enter the details of an SQL account that has these privileges.
Note that this account is only used during the installation process.
If you now have given permissions to the installing account on the database, you could retry Use
Integrated Security.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-26
4
The Installation Procedure
INSTALL MULTITERM ADMINISTRATOR ON THE
SERVER
MultiTerm Administrator is installed automatically during the GroupShare installation if you
selected to install MultiTerm Server.
However, if you need to reinstall MultiTerm Administrator, only do so after you have installed
MultiTerm server. Install it into the server install location, usually %ProgramFiles%\SDL\SDL
Server\SDL Multiterm\Multiterm11.
D
F
NOTE
If you have to reinstall MultiTerm Administrator, ensure that you have the latest matching
standalone installer of MultiTerm Administrator.
WARNING
You must not install the MultiTerm Desktop client component on the server computer where
GroupShare is installed.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
4-27
4
P O S T- I NSTA LLATION
CO N F IG U RE I I S
After installation you can make additional changes to IIS.
It is assumed that the reader of this chapter is familiar with IIS.
Contents
C
Enabling and Disabling Endpoints
C
Providing HTTPS Services
C
Enable TCP Endpoints)
Chapter
5
Overview of The Installation Process
ENABLING AND DISABLING ENDPOINTS
You enable or disable endpoints to:
C
Enable or disable HTTP or HTTPS.
C
Enable or disable TCP connections.
To enable or disable endpoints in the GroupShare web site, edit the file
SDL\SDL Server\Web\Platform\web.config.
The GroupShare website has three services and each service has definitions for each endpoint for
that service (HTTPS, HTTP and, perhaps, TCP).
The general procedure to enable endpoints is to uncomment the lines for that endpoint in all the
GroupShare services. Find the endpoint definitions by looking for the associated comment line that
starts each definition, as follows:
User authentication service
Service tag:
C
<service name="Sdl.Enterprise2.Platform.Router.UserManagerRouter"
behaviorConfiguration="routerServiceBehavior">
Each endpoint definition is headed by one of the following comment lines:
C
<!-- Identity Router http endpoint -->
C
<!-- Identity Router https endpoint -->
Router service
Service tag:
C
<service name="Sdl.Enterprise2.Platform.Router.IssuedTokenRouter"
behaviorConfiguration="routerServiceBehavior">
Each endpoint definition is headed by one of the following comment lines:
C
<!-- Issued Token Router http endpoint -->
C
<!-- Issued Token Router https endpoint -->
C
<!-- Issued Token Router tcp endpoint -->
Discovery service
Service tag:
C
<service name="Sdl.Enterprise2.Platform.Router.DiscoveryService"
behaviorConfiguration="routerServiceBehavior">
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
5-2
1
Overview of The Installation Process
Each endpoint definition is headed by one of the following comment lines:
C
<!-- Discovery Service http endpoint -->
C
<!-- Discovery Service https endpoint -->
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
5-3
1
Overview of The Installation Process
PROVIDING HTTPS SERVICES
The default configuration for GroupShare is to use HTTP endpoints. You can set up IIS to support
HTTPS services. To do this:
1
Get an X.509 certificate.
2
Enable HTTPS binding.
E
RECOMMENDATION
If you enable HTTPS services, disable HTTP. If both HTTPS and HTTP connections are
available, GroupShare will work but the interaction is liable to be confusing for the user.
Get an X.509 certificate
The first step is to get an X.509 certificate from an established Certificate Authority (CA).
An X.509 certificate contains details such as the web site. It also certifies that the CA has publicly
committed that those details belong to you, and that they have not been tampered with.
For details on how to get a certificate, contact a trusted root CA. All browsers contain a list of trusted
root CAs. For example, in Internet Explorer, open Internet Options, click the Content tab, and then
Certificates > Trusted Root Certification Authorities.
To enable HTTPS binding
Edit the web config file
By default the installer configures the GroupShare web site to handle HTTP traffic on port 80.
Configure the website to support SSL by editing the file
SDL\SDL Server\Web\Platform\web.config.
Under each of the <services> tag you will see HTTPS endpoint definitions, commented out. The
endpoint definitions are headed by the appropriate comment line for the service, as follows. (See
also, Enabling and Disabling Endpoints.)
<!-- Issued Token Router https endpoint -->
<!-- Identity Router https endpoint -->
<!-- Discovery Service https endpoint -->
Each endpoint definition has two parts:
C
Https.....RequestReply allows client access via HTTPS.
C
Https....Metadata allows webervice querying via HTTPS.
Uncomment these endpoint definitions.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
5-4
1
Overview of The Installation Process
Edit the list of web sites in the Windows Server manager
From the Windows 2008 or Windows 2012 Server Manager, open the list of web sites, right-click the
web site that is going to provide the HTTPS service, and select Edit bindings. Add an HTTPS binding,
choosing the X.509 certificate that you obtained.
Run time settings on the client
Applying the settings described above enables a client-sever connection to be HTTPS. When you run
the client program (for example, SDL Trados Studio) and select a server, the client will allow you to
choose whether to use HTTPS for the new connection.
To disable HTTP binding
1. Comment out HTTP endpoints
For all three services listed in Enabling and Disabling Endpoints, comment out the endpoint
definition lines, that is, the definition lines headed by the following comments:
C
<!-- Identity Router http endpoint -->
C
<!-- Issued Token Router http endpoint -->
C
<!-- Discovery Service http endpoint -->
2. Edit router service behavior
Change the router service behavior to:
serviceMetadata httpGetEnabled="false".
The following extract shows the changed line in context:
<behaviors>
<serviceBehaviors>
<behavior name="routerServiceBehavior">
<serviceMetadata httpGetEnabled="false" />
<serviceDebug includeExceptionDetailInFaults="false" />
</behavior>
</serviceBehaviors>
</behaviors>
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
5-5
1
Overview of The Installation Process
ENABLE TCP ENDPOINTS
By default, GroupShare does not support TCP endpoints on IIS.
You normally use TCP endpoints if you have users on your LAN, because TCP endpoints enhance
client-server communication performance.
To enable the use of TCP endpoints, edit the file
SDL\SDL Server\Web\Platform\web.config and uncomment the TCP endpoint
definitions. These are headed by the following comment line:
<!-- Issued Token Router tcp endpoint -->
The endpoint definition has two parts:
C
Tcp....RequestReply allows client access via TCP.
C
Tcp....Metadata allows webervice querying via TCP.
Uncomment both of these parts. Also, make sure that the TCP bindings in IIS are enabled.
You do not need to modify the client.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
5-6
1
P O S T- I NSTA LLATION
CO N F IG U RE M U L TITER M
If you are not installing MultiTerm, you can skip this chapter.
If you are installing MultiTerm, you may need to configure it
after you install GroupShare.
Contents
C
Install MultiTerm Administrator on the Server
C
Configure SDL MultiTerm Online-Export
C
Upgrade From Earlier SDL MultiTerm Versions
C
Move Termbase Data to a New Database Server
C
Configure MultiTerm Online
C
Troubleshoot Browser Connection to MultiTerm Online
C
Where to Change SDL MultiTerm Settings
Chapter
6
Post-Installation Configure MultiTerm
INSTALL MULTITERM ADMINISTRATOR ON THE
SERVER
MultiTerm Administrator is installed automatically during the GroupShare installation if you
selected to install MultiTerm Server.
However, if you need to reinstall MultiTerm Administrator, only do so after you have installed
MultiTerm server. Install it into the server install location, usually %ProgramFiles%\SDL\SDL
Server\SDL Multiterm\Multiterm11.
D
F
NOTE
If you have to reinstall MultiTerm Administrator, ensure that you have the latest matching
standalone installer of MultiTerm Administrator.
WARNING
You must not install the MultiTerm Desktop client component on the server computer where
GroupShare is installed.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-2
6
Post-Installation Configure MultiTerm
CONFIGURE SDL MULTITERM ONLINE-EXPORT
The default folder for file transfers between MultiTerm Online and MultiTerm Server is:
%ProgramData%\SDL\SDLServer1\FileStore\MultiTerm
MultiTerm Online stores all imported files and exported files in this location.
You can specify a different folder from the SDL GroupShare Console > SDL Studio GroupShare tree
> Settings branch > File Storage section.
When you specify a network location in MultiTerm Server, ensure that the following accounts have
read-write access to this folder:
C
The user account that runs the SDL Application Service.
C
The user account that runs Apache Tomcat.
If you are working with a split installation scenario, make sure to create a network location to enable
import and export between MultiTerm Server and MultiTerm Online. The same read-write access
conditions as mentioned above apply.
D
NOTE
In previous versions of MultiTerm, this folder was specified in GroupShareConsole under
%WINDIR%\Temp\Transfer
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-3
6
Post-Installation Configure MultiTerm
UPGRADE FROM EARLIER SDL MULTITERM
VERSIONS
Upgrading from MultiTerm Server 2009
If you have server-based SDL MultiTerm 2009 termbases and you want to convert them to
MultiTerm 2014 (and later):
1
Run the MultiTerm Upgrade wizard available in SDL MultiTerm Console 2011. This converts
MultiTerm 2009 termbases to MultiTerm 2011.
2
Run the GroupShare installer. This automatically upgrades all MultiTerm termbases to
MultiTerm 2014.
D
NOTE
Use the Upgrade wizard only for server-based termbases. When you open a local termbase in
SDL MultiTerm, SDL MultiTerm automatically upgrades that termbase.
Deactivate your GroupShare 2011 license before upgrading to GroupShare 2014.
Upgrading from MultiTerm Server 2011
The SDL GroupShare 2014 installer automatically upgrades MultiTerm Server 2011 to MultiTerm
Server 2014. Run the installer on each computer, starting with the Application Server.
MultiTerm Server 2011 data is compatible with MultiTerm 2014.
D
NOTE
Deactivate your GroupShare 2011 license before upgrading to GroupShare 2014.
Before upgrading to GroupShare 2014, make sure that your GroupShare 2011 version is using
Cumulative Update patch 3 (or higher).
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-4
6
Post-Installation Configure MultiTerm
MOVE TERMBASE DATA TO A NEW DATABASE
SERVER
Overview
The following procedure moves termbase data to a different database server. It does not conserve
other MultiTerm data such as catalog objects:
1
Export the data from the existing termbase.
2
Create a termbase on the target database server.
3
Import the exported data into the new termbase.
D
NOTE
To upgrade a 2009 termbase, use the Upgrade wizard in SDL MultiTerm GroupShare. Upgrade
From Earlier SDL MultiTerm Versions.
Detailed procedure
Follow these steps:
1
From the Catalog view in MultiTerm select the termbase you are moving.
2
In the Navigation pane select Definition. From the Catalog menu select Save to save the
definition file (as a *.xdt file).
3
In the Navigation pane select Export and choose one of the Export definitions available in the
work pane.
4
From the Catalog menu select Process to export the termbase data using the Export Wizard.
5
Run the MultiTerm Administrator client and connect to the desired MultiTerm server. Use the
Create New Termbase Wizard to create a new termbase, using the definition file you saved in
step 2.
6
From the Catalog view in SDL MultiTerm select a new termbase.
7
In the Navigation pane select Import and choose one of the import definitions available in the
work pane.
8
From the Catalog menu select Process to import the termbase data using the Import Wizard.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-5
6
Post-Installation Configure MultiTerm
INSTALL MULTITERM ONLINE
SDL MultiTerm Online is a web server application that allows users to access MultiTerm Server over
the Internet, through a browser interface.
You can install MultiTerm Online on the same computer as the MultiTerm Server or on a different
computer.
To install MultiTerm Online, log in with Administrator privileges and do the following steps:
1
Install Java Runtime Environment (JRE), version 6 or higher.
On 64-bit systems, you need the 64-bit version of JRE. To get the 64-bit version of JRE ensure
you use a 64-bit browser when you navigate to the Sun JRE download site.
2
Install Apache Tomcat, Version 7. Apache Tomcat is not part of SDL installer.
On 64-bit systems, you need the 64-bit version of Apache Tomcat.
3
Run the SDL installer and select MultiTerm Online. Run the installer to completion.
4
Copy the MultiTerm.war file to the Webapps folder of the Tomcat installation directory.
This triggers the unpacking process. You do not need to restart the Tomcat service.
D
NOTE
MultiTerm.war is located in the Online folder under the MultiTerm Server installation
folder (usually %ProgramFiles%\SDL\SDL Server\SDL
MultiTerm\MultiTerm11\Online). GroupShare installs the *.war file alongside native
64-bit components, in the Program Files folder. All the other GroupShare and MultiTerm
components are installed in Program Files (x86) folder.
5
To specify the location and port number of the SDL Anywhere router, edit the properties
mtonline.router.location and mtonline.router.portNumber in the file
mtonline.properties, as described in the next section, Configure MultiTerm Online.
6
Run Configure Tomcat as an Administrator (usually you can find this from the Start menu
under Apache Tomcat) and click the Java tab.
C Add the following line in the Java Options box:
-Djava.library.path=MultiTermJNIConnectorPath
Here MultiTermJNIConectorPath is the folder which contains the file
SDL.MultiTerm.Client.JNIConnector.dll (usually
$ProgramFiles\SDL\SDL Server\SDL MultiTerm\MultiTerm11.)
Example:
-Djava.library.path=C:\Program Files\SDL\SDL Server\SDL
MultiTerm\MultiTerm11
C Add the following line:
-Dorg.apache.el.parser.SKIP_IDENTIFIER_CHECK=true
7
Restart the Tomcat service.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-6
6
Post-Installation Configure MultiTerm
CONFIGURE MULTITERM ONLINE
You can change most MultiTerm Online settings from MultiTerm Online, in the Administration
view:
See next section for information about using SSL in MultiTerm Online.
However, to change some settings, you need to edit the following file:
tomcatfolder\webapps\multiterm\WEB-INF\mtonline.properties
where tomcatfolder is the folder of the Apache Tomcat Server installation.
The following table lists these settings.
Setting
Description
mtonline.router.host
Specifies the name of the SDL Anywhere server.
Default is 127.0.0.1
“localhost” is not supported. Change the host value to the
full server name if SDL Anywhere server is configured to
run on https.
mtonline.router.path
Specifies any subfolders in the URL of the website where
the GroupShare server is deployed.
Default is empty, meaning that the Groupshare
administrator deployed the GroupShare server to a URL
which does not contain any subfolders.
mtonline.router.portNumber
Specifies the port number for the SDL Anywhere server
Default 80.
Change port number to 443 if SDL Anywhere is configured
to run on https. If SDL Anywhere is running on https on a
non-standard port, specify the port number here and add
https:// as a prefix to the server name mentioned above.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-7
6
Post-Installation Configure MultiTerm
mtonline.webservice.sessionTime Specifies the number of minutes that an inactive user
remains logged in to MultiTerm Online.
This setting overrides the setting in the <sessiontimeout> element in the file web.xml, in the same
folder as mtonline.properties.
Minimum is 2.
Default is 30.
mtonline.webservice.language
Specifies the MultiTerm Online user interface language.
Valid values are: en de fr.
Default is en.
mtonline.webservice.editEnabled Specifies whether the MultiTerm Online toolbar displays
Editing tools. Editing tools allow termbase entries to be
edited.
Default is true.
mtonline.webservice.supportAddr Specifies an email address or website for the Contact
ess
Support link.
Default is http://support.sdl.com.
mtonline.webservice.enableLinkP If true, MultiTerm Online will use any password included
assword
in a link URL. If false, MultiTerm Online will prompt for
the password.
Default is false.
mtonline.webservice.AutoselectA If true, when you log in to MultiTerm Online, all
llTermbases
termbases on the Select Termbases page are
automatically selected.
Default is false.
mtonline.webservice.displayVerb Specifies whether MultiTerm Online displays verbose
oseErrors
error messages.
This is primarily a support tool, not an end user tool.
Default is false.
mtonline.webservice.toggleFullF If True, the default display for editing termbase entries is
orm
to show all available fields. If false, only used fields are
displayed.
Default is false.
mtonline.webservice.publicHost
Specifies the external web address that the user will use to
access MultiTerm Online. Required if MultiTerm Online is
behind a reverse proxy.
Default is empty.
Configuring MultiTerm Online to use SSL
1
Using the Certificates MMC snap-in, export the SSL certificate (and its full certificate chain if
there is one) into a PKCS12 keystore (a PFX file in Windows). It is important to include the
Private Key for the certificate. The Export Certificate wizard will prompt for a password to use
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-8
6
Post-Installation Configure MultiTerm
to encrypt the keystore and this password will be used in the next step, so you may want to take
a copy.
2
Edit the conf\Server.xml file in the Tomcat installation folder, as follows:
C Uncomment the SSL HTTP connector definition.
C In the SSL HTTP connector definition, add the following parameters:
SSLEnabled="true"
keystoreFile=”<full pathname for the stored PKCS12 keystore file>”
keystorePass=”<password that you used to encrypt the file>"
keystoreType="PKCS12"
C If you chose Native option when you installed Tomcat, disable the APR
listener by commenting out the following line:
<Listener className="org.apache.catalina.core.AprLifecycleListener" />
If you do not do this, any attempt to access the MultiTerm logon page will
produce an HTTP 500 error with the detail: ssl_error_rx_record_too_long.
3
Restart Tomcat.
Example SSL HTTP connector definition
<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS"
SSLEnabled="true"
keystoreFile="C:\Program Files\Apache Software Foundation\SelfSSLCert.pfx"
keystorePass="MyPassword"
keystoreType="PKCS12" />
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-9
6
Post-Installation Configure MultiTerm
TROUBLESHOOT BROWSER CONNECTION TO
MULTITERM ONLINE
First, ensure that the database server, MultiTerm Server, SDL Anywhere and MultiTerm Online
components are in place.
E
RECOMMENDATION
SDL recommends that you create a sample termbase before checking the online connection.
If these are in place, check each step of the connection between a client browser and MultiTerm
Online, as follows:
1
In your browser, enter the MultiTerm Online URL, for example
http://servername:portnumber/multiterm/
where servername is the name of the MultiTerm Online Server and portnumber is the port
number that Tomcat listens on.
2
Log in to MultiTerm Online using the login for the guest user account:
User name guest. Password guest.
3
MultiTerm Online displays a list of available termbases; select the termbase that you created. If
the termbase page opens, all the connections between MultiTerm Online, MultiTerm Server
and the database server are working correctly.
Also, for diagnostic purposes, set mtonline.webservice.displayVerboseErrors=true
in the file mtonline.properties (as described in the section Configure MultiTerm Online), and
restart Tomcat server. The error messages are displayed in the browser.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-10
6
Post-Installation Configure MultiTerm
WHERE TO CHANGE SDL MULTITERM SETTINGS
To display and change MultiTerm server settings, use the SDL GroupShare Console, which is
installed on any GroupShare machine that includes the Application Server role.
To find the program search for SDL Studio GroupShare 2014 Console under Windows Start > All
Programs.
For more information, see the help installed with the SDL GroupShare Console.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
6-11
6
P O S T- I NSTA LLATION
CO N F IG U RE TM S ER VER
If you are not installing TM Server, you can skip this chapter.
If you are installing TM Server, you may need to configure it
after you have installed GroupShare.
If you are upgrading from TM Server 2007, contact Product
Support at http://www.sdl.com/en/languagetechnology/support.
Contents
C
Overview: Upgrading from Earlier SDL TM Server
Versions
C
Use Translation Memories Created by Previous SDL TM
Server Versions
C
Post-Upgrade: Check and Decommission Previous
Versions
Chapter
7
Post-Installation Configure TM Server
OVERVIEW: UPGRADING FROM EARLIER SDL TM
SERVER VERSIONS
Upgrading from TM Server 2009
TM Server 2009 data is not compatible with TM Server 2014. Upgrade TM Server 2009 to TM
Server 2011 before running the GroupShare 2014 installer. This will then automatically upgrade TM
Server 2011 data to TM Server 2014.
C
Upgrading from TM Server 2009 SP3 to TM Server 2011
The GroupShare 2011 installer upgrades TM Server 2009 SP3 to TM Server 2011 automatically. Run
the installer on each computer, starting with the application server.
C
Upgrading from TM Server 2009 SP1 or SP2 to TM Server 2011
If you are running TM Server 2009 SP1 or SP2, upgrade your software in the following sequence to
preserve existing data (translation memories and user details).
1. Upgrade from GroupShare 2009 to GroupShare 2011
Installing the software preserves the translation memories and user details from previous versions.
Uninstall SDL TM Server SP2 before you install TM Server 2011.
2. Register the existing translation memories
Follow the Use Translation Memories Created by Previous SDL TM Server Versions procedure below.
3. Import the details of existing TM Server users
Follow the procedure described in Chapter 8, Import User Details into GroupShare.
4. Post-Upgrade: check access and decommission previous versions
After the upgrade, check that your installation of SDL TM Server 2011 has all user details and can
access the translation memories, then decommission previous versions of the software.
Follow the procedure described in the Post-Upgrade: Check and Decommission Previous Versions
chapter.
5. Upgrade from GroupShare 2011 to GroupShare 2014
After upgrading to TM Server 2011, run the GroupShare 2014 installer to upgrade to TM Server
2014.
D
NOTE
Deactivate your GroupShare 2011 license before upgrading to GroupShare 2014.
Before upgrading to GroupShare 2014, make sure that your GroupShare 2011 version is using
Cumulative Update patch 3 (or higher).
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
7-2
7
Post-Installation Configure TM Server
Upgrading from TM Server 2011
The SDL GroupShare 2014 upgrades TM Server 2011 to TM Server 2014. Run the installer on each
computer, starting with the application server.
TM Server 2011 data is compatible with TM Server 2014.
D
NOTE
Deactivate your GroupShare 2011 license before upgrading to GroupShare 2014.
Before upgrading to GroupShare 2014, make sure that your GroupShare 2011 version is using
Cumulative Update patch 3 (or higher).
Use Translation Memories Created by Previous SDL TM Server Versions
Translation memories created by SDL TM Server 2011 are compatible with TM Server 2014,
In TM Server, translation memories are held in containers, so for TM Server 2014 to access
translation memories, you need to register the containers of those translation memories with TM
Server 2014.
D
NOTE
You do not register each translation memory separately; when you register a container that
contains translation memories, you thereby register all translation memories in the container.
Before you start: register database server with TM Server 2014
Containers are held by database servers and before you can register a container, you must register
the database server that holds the container.
To register a database server with TM Server 2014, complete the following steps:
1
In the Infrastructure view of GroupShare 2014, select the Servers tab and click Add.
D
NOTE
2
Only Administrators and members of any other role with View Infrastructure permission have
access to the Infrastructure view in GroupShare 2014 SP1 and later.
In the Add Server form that is displayed, provide a name and description for the database
server, and in the Server Name box enter the database instance name. Usually this is the same
as the database server hostname.
After you have completed this procedure, you can register any containers in that database server.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
7-3
7
Post-Installation Configure TM Server
To register a pre-existing container with TM Server 2014
Do the following steps:
1
Ensure you have registered the container’s database server, as described above.
2
In the Infrastructure view of GroupShare 2014, select the Containers tab and click Add.
D
NOTE
Only Administrators and members of any other role with View Infrastructure permission have
access to the Infrastructure view in GroupShare 2014 SP1 and later.
3
In the Add Container form that is displayed, provide a name and description for the container.
4
Enter the SQL Server database name (as displayed in your SQL Server management tool) in
the Database Name box .
When you have completed this procedure, TM Server 2014 inspects the container database and finds
all previously used translation memories that are in the container. It then registers these translation
memories so that they are ready for use with SDL TM Server 2014.
After you register containers with SDL TM Server 2014, you should not use the translation
memories with previous versions of SDL TM Server.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
7-4
7
Post-Installation Configure TM Server
POST-UPGRADE: CHECK AND DECOMMISSION
PREVIOUS VERSIONS
To check access to the user details and translation memories, log in to SDL GroupShare as an
administrator. For information on administrator log in, see Chapter 8, Reference.
For more information on viewing translation memories and user details after you have logged in, see
the GroupShare online help.
When you have confirmed that you have imported user details and that you can access translation
memory from a browser, check that you can do the same from SDL Trados Studio 2014 or SDL
MultiTerm as appropriate, then decommission your older versions of TM Server.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
7-5
7
REF E R EN CE
Reference information.
Contents
C
Configuration Information
C
Windows User Accounts
C
GroupShare User Accounts
C
Import User Details into GroupShare
C
Password Policies
C
Run Time Access to SDL GroupShare
C
Run Time Access to SDL MultiTerm
C
Digital Certificate Requirements
C
Uninstallation and Re-Installation
Chapter
8
Reference
CONFIGURATION INFORMATION
GroupShare program installation
By default, GroupShare programs are installed under:
C
%ProgramFiles%\SDL\ (32-bit machines)
C
%ProgramFiles(x86)%\SDL\ (64-bit machines)
D
NOTE
The MultiTerm.war file which is used by the Tomcat service is installed alongside native
64-bit components, under %ProgramFiles%\SDL\.
Log files and other program data
These files are installed under:
C
%ProgramData%\Package Cache\SDL\
Registry keys
The install creates and sets registry keys under:
C
HKEY_LOCAL_MACHINE\SOFTWARE\SDL\ (32-bit machines)
C
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SDL\ (64-bit machines)
Unpacked installation files
By default, the installer unpacks the installation files into folders under:
C
%ProgramData%\Package Cache\SDL\
D
NOTE
These files are needed for the installation and also for uninstalling. If you delete these files, you
will need to download and extract them again to uninstall GroupShare.
GroupShare use of UDP and TCP/IP ports
Ensure that any firewall allows access to and from these ports if these ports are used in your
configuration.
In ascending order, they are:
C
443
Standard HTTPS port.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-2
8
Reference
C
808
Windows port for TCP binding.
C
1434
UDP port used by SQL Server.
C
8080
Default Apache Tomcat port.
C
41000
Used by the GroupShare Application Server. This is set in the Windows Registry.
C
41234
Used by the GroupShare REST API.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-3
8
Reference
WINDOWS USER ACCOUNTS
Installer created user accounts and groups
Groups and privileges
The installer creates the Windows group, SDL Server Users.
The user account that runs SDL services has the privilege “Log on as a service”.
The user account that runs the SDL services also has rights to view and manage the message queues
that the Application Server creates for the MSMQ service. You can grant other users rights to
manage the message queue from Computer Management.
The Application Server creates the following default message queues under Private Queues:
C
sdl.servicebus
C
sdl.servicebus.error
C
sdl.servicebus.email.projectchange
C
sdl.servicebus.email. projectchange.error
User accounts
On the computer running SDL Anywhere or TM Website, the installer creates the user account
SDLWebUser and gives this account access to:
C
the Web Server program folder (usually under %programfiles%)
C
system32\inetsrv\config\, to access the file redirect.config.
Group assignment
When you install MultiTerm, the installer puts the MultiTerm user account into the group SDL
Server Users.
On the computer running SDL Anywhere or TM website, the installer puts the user account
SDLWebUser into the IIS_IUSRS group.
Resources and access
The following table shows access to resources for English language, 32-bit versions of Windows.
Other versions will have equivalent resource names.
Resource
Identity
Access level
HKEY_LOCAL_MACHINE\Software\SDL\Platform
Everyone
Full Control
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-4
8
Reference
Resource
Identity
Access level
C:\Windows\Temp
SDL Server Users
Full Control
SDL Server Users
Full Control
2
C:\Windows\System32\inetsrv\Config
SDL Server Users
Read Only
2
C:\Windows\System32\inetsrv\Config\redirection.config
SDL Server Users
Read Only
2
C:\Windows\System32\inetsrv\Config\applicationHost.config
SDL Server Users
Read Only
C:\ProgramData\All Users\Application Data\Microsoft\Crypto\
1,3
RSA\MachineKeys
SDL Server Users
Full Control
C:\Program files\SDL\SDL Server\Web
SDLWebUser
Full Control
C:\ProgramData\All Users\Application data\SDL
1
2
3
1
On some versions of Windows, ProgramData is called Documents and Settings.
IIS 7.5 only.
Only applies to the generated certificate file in this folder.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-5
8
Reference
GROUPSHARE USER ACCOUNTS
GroupShare logon information
The GroupShare server ensures that user credentials are valid across all its components. A user
account created in GroupShare is visible in MultiTerm Administrator, and can be made a user of a
termbase.
For more information about managing users in GroupShare, see the GroupShare online Help at
http://producthelp.sdl.com/SDL_Studio_GroupShare_2014/EN/index.htm
Permissions (access rights)
Permissions for termbases are managed in MultiTerm Administrator. However, the creating
termbase permission is managed in GroupShare.
Installer created GroupShare user accounts
When you install GroupShare, the installer creates the following GroupShare users:
C
System User (This is used by the server and is not for interactive users.)
C
System Administrator (User name: sa, Password: sa)
GroupShare standard roles
GroupShare groups together permissions into roles, which are then assigned to users. Depending
on what components of GroupShare you install, the following standard roles are automatically
created during installation:
C
Administrator
C
Power User
C
Translator
C
External Translator
C
Guest
C
Project Manager
For a list of the permissions allocated to each role, see the GroupShare online Help.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-6
8
Reference
IMPORT USER DETAILS INTO GROUPSHARE
GroupShare includes a utility program, User Import Tool. This imports user and organization details
into GroupShare from Windows Active Directory (or any other LDAP Server).
Running the User Import Tool
Run the User Import Tool on same computer as the Application Server and use the same user
account that you used to run the GroupShare installer.
The User Import Tool is in the same folder as GroupShare.
When you run the tool, it prompts you to import details from an LDAP Server such as Windows
Active Directory.
Importing from an LDAP Server
When you choose this option, the User Import Tool prompts you for a Windows domain and then
displays the list of users in that domain. You can use the standard shortcut keys to select users from
the list, as follows:
C Ctrl-click to select multiple users.
C Shift-click to select a range of users.
C Ctrl+A to select all users.
The tool prompts you to provide a GroupShare organization and roles for the imported users. The
tool imports the user details (name, description and encoded password), assigns the users to the
specified organization, and gives them the specified roles.
D
NOTE
You might find it useful to run the User Import Tool a number of times. Each time you run it,
you can assign to the users a different combination of organization and roles.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-7
8
Reference
PASSWORD POLICIES
Password policy with Windows authentication
If you choose Windows authentication, you get Windows password enforcement.
Password policy with SDL passwords
A password for a user in GroupShare must include at least one each of the following:
C
An uppercase letter
C
A lowercase letter
C
A digit
Password policy for custom accounts
Companies with a GroupShare custom authentication provider plug-in can use their corporate user
management system authentication to create custom user accounts and log into GroupShare.
The credentials for custom users are managed outside GroupShare. GroupShare does not impose
any format requirements for passwords created for custom users.
Password policy for service accounts
E
RECOMMENDATION
SDL recommends that the password for the server application user account, and for other
service accounts, should never expire. This is because, if the service password does expire, the
service will not work and diagnosis can be difficult.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-8
8
Reference
RUN TIME ACCESS TO SDL GROUPSHARE
From a browser
In a web browser, enter the computer name of the web server that you provided in the installation.
If you provided a host header in the installation, use that.
For example, enter:
C
http://www.example.com/sdltrados/groupshare if you have used a custom
location URI.
C
http://computername if you have not specified a custom location or a host
header.
GroupShare displays its start screen and prompts you for a user name and password. For more
information, see the online Help at
http://producthelp.sdl.com/SDL_Studio_GroupShare_2014/EN/index.htm
From SDL Trados Studio or SDL MultiTerm
In Windows, run the client application, Trados Studio or MultiTerm.
When the application starts, click File > Servers, and choose the action (Add, Edit or Check Server
Availability). Provide the connection details as required.
For further details, see the online help in SDL Trados Studio and in SDL MultiTerm on
producthelp.sdl.com.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-9
8
Reference
RUN TIME ACCESS TO SDL MULTITERM
To open SDL MultiTerm Server from SDL MultiTerm Administrator
In Windows, run the SDL MultiTerm Administrator. This is usually under Start > All Programs >
SDL > SDL MultiTerm ...
When the application starts, it displays the Connect to MultiTerm Server dialog box. Complete the
dialog box as required.
To open SDL MultiTerm Online from a browser
In a web browser, enter:
C
http://servername:portnumber/multiterm/
servername is the name of the computer that hosts the MultiTerm Online pages.
portnumber is the port number used to communicate with that computer.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-10
8
Reference
DIGITAL CERTIFICATE REQUIREMENTS
All SDL GroupShare and MultiTerm Online code and installer files are digitally signed. Make sure
your list of approved root certificates is up-to-date and includes the root certificate from the
Certification Authority that generates SDL's code signing certificate.
C
For computers with access to the Internet:
C Windows Vista or later - Go to https://www.digicert.com and add the new root certificate to
your Trusted Root Certification Authorities certificate store.
C Windows XP or earlier - Go to http://catalog.update.microsoft.com/v7/site/Home.aspx
and search for either root update or KB931125 to find the correct cumulative Root
Update package to install.
C
For computers in a locked down corporate environment without access to the Internet:
Follow the Root update package installation on disconnected environments instructions
available at http://support.microsoft.com/kb/931125. The root certificate updates are
available from http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB931125.
You can also download the specific root certificates directly from
https://www.digicert.com/digicert-root-certificates.htm and apply the certificates to each
locked down workstation manually or by group policy. At the time of writing, GroupShare
and MultiTerm Online require DigiCert Assured ID Root CA and DigiCert Assured ID
Code Signing CA-1.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-11
8
Reference
UNINSTALLATION AND RE-INSTALLATION
To modify or uninstall GroupShare components
Use the Windows control panel program Add or remove programs and choose GroupShare (not a
GroupShare component) to uninstall or modify GroupShare.
After uninstallation you can remove the GroupShare registry keys and the unpacked installation
files.
If you use Add or remove programs to modify GroupShare, you can add components to GroupShare,
but you cannot remove components.
Re-installing GroupShare
You can continue with the previous GroupShare database when you reinstall GroupShare.
If you want to re-use the previous database, ensure you use the same installation details. The
installation recognizes that a database already exists and uses it.
SDL GROUPSHARE 2014 SP2 INSTALLATION GUIDE
8-12
8
Copyright © 2014 SDL plc. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.
SDL enables global businesses to enrich their customers’ experience through the entire customer journey. SDL’s technology and services
help brands to predict what their customers want and engage with them across multiple languages, cultures, channels and devices.
SDL has over 1,500 enterprise customers, 400 partners and a global infrastructure of 70 offices in 38 countries. 42 out of the top 50
brands work with SDL. For more information, visit www.sdl.com.

Similar documents

×

Report this document