SDL Translation Management System
Installation Guide
Legal Notice
Copyright and trademark information relating to this product release
Copyright © 2000 – 2017, SDL Group.
SDL Group means SDL PLC. and its subsidiaries and affiliates. All intellectual property rights contained herein are the sole and exclusive rights of SDL Group. All references to SDL or SDL Group shall mean SDL PLC. and its subsidiaries and affiliates details of which can be obtained upon written request.
All rights reserved. Unless explicitly stated otherwise, all intellectual property rights including those in copyright in the content of this website and documentation are owned by or controlled for these purposes by SDL Group. Except as otherwise expressly permitted hereunder or in accordance with copyright legislation, the content of this site, and/or the documentation may not be copied, reproduced, republished, downloaded, posted, broadcast or transmitted in any way without the express written permission of SDL.
SDL TMS is a registered trademark of SDL Group. All other trademarks are the property of their respective owners. The names of other companies and products mentioned herein may be the trademarks of their respective owners. Unless stated to the contrary, no association with any other company or product is intended or should be inferred.
This product may include open source or similar third-party software, details of which can be found by clicking the following link: Acknowledgments.
Although SDL Group takes all reasonable measures to provide accurate and comprehensive information about the product, this information is provided as-is and all warranties, conditions or other terms concerning the documentation whether express or implied by statute, common law or otherwise (including those relating to satisfactory quality and fitness for purposes) are excluded to the extent permitted by law.
To the maximum extent permitted by law, SDL Group shall not be liable in contract, tort (including negligence or breach of statutory duty) or otherwise for any loss, injury, claim liability or damage of any kind or arising out of, or in connection with, the use or performance of the Software Documentation even if such losses and/or damages were foreseen, foreseeable or known, for: (a) loss of, damage to or corruption of data, (b) economic loss, (c) loss of actual or anticipated profits, (d) loss of business revenue, (e) loss of anticipated savings, (f) loss of business, (g) loss of opportunity, (h) loss of goodwill, or (i) any indirect, special, incidental or consequential loss or damage howsoever caused.
All Third Party Software is licensed "as is." Licensor makes no warranties, express, implied, statutory or otherwise with respect to the Third Party Software, and expressly disclaims all implied warranties of non- infringement, merchantability and fitness for a particular purpose. In no event will Licensor be liable for any damages, including loss of data, lost profits, cost of cover or other special, incidental, consequential, direct, actual, general or indirect damages arising from the use of the Third Party Software or accompanying materials, however caused and on any theory of liability. This limitation will apply even if Licensor has been advised of the possibility of such damage. The parties acknowledge that this is a reasonable allocation of risk.
Information in this documentation, including any URL and other Internet 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.
SDL TMS 11.3 Installation Guide Page 1
Table of Contents
1 Overview ...... 3 1.1 About this Guide ...... 3 1.2 Recommended Setup ...... 3 1.3 Software and Hardware Requirements ...... 3 1.3.1 SDL TMS Server ...... 3 1.3.2 Database Server ...... 3 1.4 Overview of the SDL TMS Installation Process ...... 4
2 Installation Step 1 – Server Preparation ...... 5 2.1 About Server Preparation ...... 5 2.2 User Accounts ...... 5 2.2.1 Local Administrator Accounts ...... 5 2.2.2 SDL TMS Domain Account ...... 5 2.3 Prepare the SDL TMS Server ...... 6 2.3.1 Install prerequisites components ...... 7 2.4 Prepare the Database server ...... 9 2.4.1 Configure SQL Server 2008, 2012 or 2014 to Enable Remote Connections using TCP/IP ...... 9
3 Installation Step 2 – Install SDL TMS ...... 11 3.1 About Installing SDL TMS ...... 11 3.2 Installation Files ...... 11 3.3 Install SDL TMS 2007 SP1 ...... 12 3.3.1 Start the Installation ...... 12 3.3.2 Installing SDL TMS 2007...... 13 3.4 Install latest Service Pack ...... 19 3.4.1 Database Deployment Wizard ...... 19 3.5 Verify the Installation...... 20 3.5.1 Log in to SDL TMS ...... 20
Appendix A ...... 21 Acknowledgments ...... 21
SDL TMS 11.3 Installation Guide Page 2 1 Overview
1.1 About this Guide This guide describes how to install SDL Translation Management System (SDL TMS) as of version 11.0. It describes the system requirements for installing SDL TMS and provides information on how to configure the system before installation, outlining pre-installation steps and giving step-by-step instructions for installing SDL TMS and its component products.
1.2 Recommended Setup We recommend a two - computer setup, having the SDL TMS core components installed on one server computer and the database server installed on a separate server computer.
1.3 Software and Hardware Requirements
1.3.1 SDL TMS Server For the computer on which the SDL TMS server components are installed, the recommended specifications are as follows: Processor 4 CPU cores
RAM 8 GB
Hard Disk We recommend dedicating at least 8 GB of space. Most of the deployments require significantly more space, since this space is used by the content that is being translated. Typical production environments have 60+ GB of space allocated for the solution and the data (out of which the solution is about 1 GB).
Operating Microsoft Windows Server 2008 R2 (Standard Edition or above) / System Microsoft Windows Server 2012 (Standard Edition or above) /
1.3.2 Database Server For the computer on which the database is installed, the recommended specifications are: Processor 4 CPU cores
RAM 8 GB
Hard Disk RAID 5 Array for SQL Logs & Data. Size requirements will depend on usage.
Operating Microsoft Windows Server 2008 R2 (Standard Edition or above) / System Microsoft Windows Server 2012 (Standard Edition or above)
Database Microsoft SQL Server 2008 / 2012 (Standard Edition or above) Server Microsoft SQL Server 2014 (Standard Edition or above)
SDL TMS 11.3 Installation Guide Page 3 1.4 Overview of the SDL TMS Installation Process The following diagram gives an overview of the steps you will take when installing SDL TMS. Each of the steps has their own chapter within this guide.
• Install Microsoft Windows Server 2008 or 2012 Step 1: Server Preparation Components • Install and Configure Microsoft SQL Server 2008, 2012 or 2014 • Apply Updates and Patches
• Install pre-requisites • Run the SDL TMS installer Step 2: Install SDL TMS • Install Service Packs • Verify the installation
SDL TMS 11.3 Installation Guide Page 4 2 Installation Step 1 – Server Preparation
2.1 About Server Preparation If you are installing SDL TMS for the first time, prepare both the server computer where you intend to install SDL TMS and the computer you intend to use as the database server. If you are not installing SDL TMS for the first time, you can proceed to Installation Step 2 – Install SDL TMS.
2.2 User Accounts To install and run SDL TMS, the following user accounts are required: • Local administrator account • A domain account (required permissions listed in 2.2.2 SDL TMS Domain Account).
2.2.1 Local Administrator Accounts Local administrator accounts are required for both the SDL TMS server and the database server, in order to perform installation and configuration. In this guide, the local administrator account is referred to as
2.2.2 SDL TMS Domain Account Create or nominate a domain account for SDL TMS to run as. We recommend that this account does not have password change enforced. In this guide, the SDL TMS domain account is referred to as
Note: For the installation, this domain account needs administrator rights on the server computer where you are installing SDL TMS. After installation, you can remove this account from the local administrator group. Additionally, as part of the installation routine, the SDL TMS installer adds
SDL TMS 11.3 Installation Guide Page 5
Important: The User Account Control (UAC) needs to be set to “Never notify”.
2.3 Prepare the SDL TMS Server To prepare the server where SDL TMS Server will be installed, all required prerequisites have to be installed (see 2.3.1).
Note: For the SDL TMS server, we recommend using a separate partition for all SDL TMS Application and Data files. This partition must be at least 32 GB in size but, depending on the scale of your deployment, you may need to increase this size.
SDL TMS 11.3 Installation Guide Page 6
2.3.1 Install prerequisites components In order to have SDL TMS running properly, there is a list of prerequisites which are required to be installed on the server, as follows:
1. Microsoft .Net Framework 3.5 2. Microsoft .Net Framework 4.5.2 3. Microsoft Internet Information Server (IIS) 4. Microsoft Message Queue (MSMQ) 5. Microsoft MSXML 4.0 Parser 6. Microsoft System CLR Types for SQL Server 2012 7. Microsoft System CLR Types for SQL Server 2012 x64 8. Microsoft SQL Server 2012 Management Objects 9. Microsoft SQL Server 2012 Management Objects x64 10. Microsoft SQL Server 2012 Native Client x64 11. Microsoft SQL Server Compact 4.0 ENU x64 12. Microsoft Visual C++ 2005 x86 Redistributable 13. Microsoft Visual C++ 2008 x86 Redistributable 14. Microsoft Visual C++ 2010 x86 Redistributable
The installation files you find on FTP (for details, see 3.2 Installation Files) contain SDL TMS Prerequisites.exe which lets you install all the components from the above list.
SDL TMS 11.3 Installation Guide Page 7
In case each component was installed successfully, if you double click again the SDL TMS Prerequisites Installer.exe, it should display the screenshot below:
SDL TMS 11.3 Installation Guide Page 8
2.4 Prepare the Database server Configure SQL Server 2008, 2012 or 2014 to Enable Remote Connections using TCP/IP. For details, see 2.4.1. Allow Extended Stored Procedures (necessary for the SDL TMS 2007 installer to create the database user).
2.4.1 Configure SQL Server 2008, 2012 or 2014 to Enable Remote Connections using TCP/IP Once Microsoft SQL Server 2008, 2012 or 2014 has been installed, in addition to any configuration you may do when following the manufacturer's guidelines, you must also configure the installation to enable remote connections using TCP/IP. 1. Go to Start > All Programs > Microsoft SQL Server 2008 / 2012 / 2014> Configuration Tools > SQL Server Configuration Manager. The SQL Server Configuration Manager window is displayed. 2. Click the Surface Area Configuration for Services and Connections link. The Surface Area Configuration for Services and Connections dialog box is displayed.
3. In the navigation tree on the left hand side, select SQL Native Client Configuration. 4. On the right hand side TCP/IP and named pipes are marked as enabled. 5. To enable Ole Automation, open SQL Server 2008 / 2012 / 2014 Management Studio, right-click the server node in the object explorer and choose Facets from the context menu. 6. Within the View Facets window select “Surface Area Configuration” from the Facet drop down list.
SDL TMS 11.3 Installation Guide Page 9
In the list of properties for this facet, set “OleAutomationEnabled” to “True”, ONLY REQUIRED DURING INSTALLATION.
SDL TMS 11.3 Installation Guide Page 10
3 Installation Step 2 – Install SDL TMS
3.1 About Installing SDL TMS Installing SDL TMS is a cumulative process. First you run the TMS 2007 SP1 installer and then you apply all of the later updates and service packs to the installation using separate installers. Note: The installers will perform the database creation and setup.
When you install SDL TMS, the SDL TMS website is installed as the default website on your SDL TMS server and any existing websites are overwritten. SDL recommends that the first time you install SDL TMS, you do so on a clean server.
3.2 Installation Files The TMS installation files are located on ftp://sdlpatches:[email protected]/SDL%20TMS/ in the appropriate sub-folder. You will find an ISO image that you need to download. This ISO contains the following files: - SDL TMS Database_11.x.xxxxx.x.exe - SDLTMS 11.x.xxxxx.x.exe - SDL TMS Installation Guide.pdf (this file) - Sdl.ContentCollector.msi - Sdl.Nexus.msi - Sdl.Sjp.msi - Sdl.Tms.Passolo.2011.msi - Sdl.Tms.Passolo.2015.msi - Sdl.Tms.Sdk.msi - SDLNexus.jar - TMS2007SP1 - For Fresh Installs. This folder contains: o Data1.cab o ISScript1050.msi o jre-1_5_0_12-windows-i586-p.exe o Readme.txt o SDLTMS2007.msi o setup.exe o setup.isn o TradosCompatibility1.msi - Content Transfer API. This folder contains: o SDL TMS CTA Overview.pdf o Sdl.Tms.Cta.chm o Sdl.Tms.Cta.dll o sdl.tms.cta.doc.jar o sdl.tms.cta.jar - Sdl.Tms.Prerequisites.Installer.exe
SDL TMS 11.3 Installation Guide Page 11
- SDLUnicodeFont.msi - ApiDiffs.zip
Note: Any hotfix, patch or service pack released after the publication of this guide will also need to be installed. You can download these from the SDL TMS FTP site. Login details for this site can be obtained from your SDL representative.
3.3 Install SDL TMS 2007 SP1 This section describes how to install SDL TMS 2007 SP1. All components are installed on the same server.
3.3.1 Start the Installation 1. TradosCompatibility1.msi - Trados 2007 Compatibility pack - required for the legacy T2007 filters. 2. ISScript1050.Msi - Installshield scripting - required for the TMS 2007 Installation. 3. jre-1_5_0_12-windows-i586-p.exe - optional – this is required for TMS 2007/2011 Legacy INX filter 4. setup.exe - TMS 2007 Installation program
5. Login to the SDL TMS server as
SDL TMS 11.3 Installation Guide Page 12
3.3.2 Installing SDL TMS 2007 1. Click Next. The Installation Name screen is displayed.
2. Enter the name by which SDL TMS server and the Database server will identify SDL TMS (the name of the computer is provided by default). This is essential for effective communication between the servers and it is also useful if you use a shared database server to identify specific SDL TMS installations.
Note: As this name uniquely identifies your installation and will be used in e – mails, we recommend that you use a name that will be familiar to your users, a company name, for example.
Do not use spaces or punctuation in the name.
3. Click Next. The Select Features page is displayed.
SDL TMS 11.3 Installation Guide Page 13
4. Do not change the default selections on this page. Click Next. The Choose Destination Location page is displayed.
This page is where you choose the location for the SDL TMS application files. The default destination folder location follows Microsoft standards by installing files into the Program Files (x86) folder on the C:\ drive. However, we recommend that you install all your SDL TMS files to the separate partition you created earlier (see 2.3 Prepare the SDL TMS Server) under an SDL TMS subdirectory (for example: W:\SDL TMS\). This helps you identify easily SDL TMS program files and makes the process of backing up your files easier. Click Browse to select the default destination folder. Once the installation is complete, do not attempt to move files from this location, as this will cause SDL TMS to fail. If you need to move the SDL TMS files, uninstall the application and then reinstall it to the required location.
5. Click Next when you have finished. The Website location page is displayed. The default destination folder location follows Microsoft standards by installing web files to the Inetpub folder on the C:\ drive. However, we recommend that you install them to the separate partition you created for the SDL TMS installation files (for example: W:\SDL TMS\Website). This helps you identify SDL TMS website files easily and may facilitate your backup procedures. Click Browse to select the default destination folder.
SDL TMS 11.3 Installation Guide Page 14
6. Click Next when you finish. The System User screen is displayed.
7. Complete the Domain, User and Password boxes by entering the relevant details for the domain account you want the SDL TMS system to run as (
9. Under Database Server, click Browse to view a list of database servers. Select the server on which you installed and configured Microsoft SQL Server. Alternatively, enter the name of the database server associated with the installation. Under Connect Using, select Windows authentication.
Note: If you use Windows authentication, you must be logged in with an account having permissions to access the database server and permissions to install on this computer.
SDL TMS 11.3 Installation Guide Page 15
10. When you finish, click Next. The Database Details screen is displayed. SDL recommends that you accept the default settings on this page. However, you can change any of the settings if you need to.
11. Click Next. The Start Copying Files page is displayed.
SDL TMS 11.3 Installation Guide Page 16
12. Check the summary of the installation settings and click Next to begin the install.
Summary of the Installation Settings
Installation Name Identifies the SDL TMS server instance
Selected Features SDL Translation Management System, SDL TMS Broker System
Destination Folder W:\SDL TMS\ (for example) Website Location W:\SDL TMS\Website
Windows User Account < TMS_DOMAIN_User >
Database Server
Database Server Login
Database Details:
Database Name
Data File D:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\DEV_SDL TMS_DATA.MDF (for example) Data File Size 250 Mb
Log File D:\Microsoft SQL Server\MSSQL.1\MSSQL\log\DEV_SDL TMS_DATA.MDF (for example) Log File Size 100 Mb
13. Observe and ignore the following error:
SDL TMS 11.3 Installation Guide Page 17
14. When the installation is complete the InstallShield Wizard Complete page is displayed.
SDL TMS 11.3 Installation Guide Page 18
15. When the installer finishes, there is more step to do. Open IIS Manager and configure both SDL TMS Application Pools to run in 32bit process mode. If there is an additional website called “Default Web Site”, delete it, and just leave “SDLTMS".
3.4 Install latest Service Pack
Install the latest Service Pack available (standard name format: SDLTMS 11.x.xxxxx.x.exe). When you are running the installers, you must continue to use the same values that you used when completing the SDL TMS installer pages. After running each file, log in to SDL TMS to verify the installation and check the log files produced by the installers. The log files can be found here
3.4.1 Database Deployment Wizard SDL TMS 2007 SP4 introduces a new methodology for deploying database changes. As part of the installation, the Database Deployment Wizard will run. When the application runs, click the “Go” button to make the necessary changes to upgrade the database. The Database Deployment Wizard will only run on the primary server; this installation step will be skipped on secondary servers (assuming that the patch has successfully installed on at least one server).
SDL TMS 11.3 Installation Guide Page 19
3.5 Verify the Installation
3.5.1 Log in to SDL TMS Now that the installation is complete you can verify the installation. To log on to SDL TMS: 1. Launch the web browser on the SDL TMS server and navigate to http://localhost/. Note: You may need to disable your pop-up blocker when you open SDL TMS.
2. When prompted for a username and password, use the system administrator values you entered in the SDL TMS Administration account screen when you installed SDL TMS. If a new window is created and the SDL TMS Login screen appears, you have successfully installed SDL TMS.
SDL TMS 11.3 Installation Guide Page 20
Appendix A
Acknowledgments This appendix contains the list of free third party libraries used in SDL TMS, as follows: - AlphaFS – AlphaFS is an Open Source library that provides a namespace (Alphaleonis.Win32.Filesystem) containing a number of classes. Most notable are replications of the System.IO.File, System.IO.Directory and System.IO.Path, all with support for the extended-length paths (up to 32000 chars), recursive file enumerations, native backups and manipulations with advanced flags and options. They also contain extensions to these, and there are many more features for several functions. - AngularJS – AngularJS is a toolset for building the framework most suited to your application development. It is fully extensible and works well with other libraries. Features can be modified or replaced to suit your unique development workflow and feature needs. - ANTLR – ANTLR is a powerful parser generator that you can use to read, process, execute, or translate structured text or binary files. - Ascender – The font library available at Font Squirrel is your best resource for FREE, hand-picked, high-quality, commercial-use fonts - AutoMapper – AutoMapper is a convention-based object-object mapper in .NET. - CAPICOM – CAPICOM can be used to digitally sign data, sign code, verify digital signatures, envelop data for privacy, hash data, encrypt/decrypt data and more. - Common Service Locator – The Common Service Locator library contains a shared interface for service location which application and framework developers can reference. The library provides an abstraction over IoC containers and service locators. Using the library allows an application to indirectly access the capabilities without relying on hard references. The hope is that using this library, third-party applications and frameworks can begin to leverage IoC/Service Location without tying themselves down to a specific implementation. - Dapper – A high performance Micro-ORM supporting SQL Server, MySQL, Sqlite, SqlCE, Firebird etc. - Entity Framework – Entity Framework is Microsoft's recommended data access technology for new applications. - Flexcel – 100% managed code Excel file manipulation engine; Excel &PDF report generation for .NET, .NET Compact Framework. - Fluent Assertions – A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit test. - Glimpse – Glimpse is a web debugging and diagnostics tool used to gain a better understanding of what is happening inside of your ASP.NET 4.0 application. - Glimpse ASP NET – Glimpse is a web debugging and diagnostics tool used to gain a better understanding of what is happening inside of your ASP.NET 4.0 application - Glimpse Mvc4 – Glimpse is a web debugging and diagnostics tool used to gain a better understanding of what is happening inside of your ASP.NET MVC 4.0 application. - Globalize – JavaScript globalization and localization. Formats and parses strings, dates and numbers in over 350 cultures. - globalize.TypeScript.DefinitelyTyped – TypeScript Definitions (d.ts) for globalize.
SDL TMS 11.3 Installation Guide Page 21
- gudusoft.sqlparser.dll – Provides the class gudusoft.gsqlparser.TGSqlParserr necessary to create a SQL Parser and the classes a SQL Parser uses internally to handle different SQL dialects. - ICSharpCode Zip Lib – #ziplib (SharpZipLib, formerly NZipLib) is a Zip, GZip, Tar and BZip2 library written entirely in C# for the .NET platform. It is implemented as an assembly (installable in the GAC), and thus can easily be incorporated into other projects (in any .NET language). - jasmine.TypeScript.DefinitelyTyped – TypeScript Definitions (d.ts) for jasmine. - Jasmine-JS – Jasmine is a behavior-driven development framework for testing JavaScript code. - Jasmine.Test – DOM-less simple JavaScript testing framework. - jQuery – jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript. - jquery.datatables – DataTables is a plug-in for the jQuery Javascript library. It is a highly flexible tool, based upon the foundations of progressive enhancement, which will add advanced interaction controls to any HTML table. - jquery.dataTables.columnFilter – DataTables is a plug-in for the jQuery Javascript library. It is a highly flexible tool, based upon the foundations of progressive enhancement, which will add advanced interaction controls to any HTML table. - jquery.TypeScript.DefinitelyTyped – TypeScript Definitions (d.ts) for jquery. - jQuery UI – jQuery UI is a set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library. - jQuery.UI.Combined – jQuery UI is a set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library. - jQuery Validation – This jQuery plugin makes simple clientside form validation trivial, while offering lots of option for customization. That makes a good choice if you're building something new from scratch, but also when you're trying to integrate it into an existing application with lots of existing markup. The plugin comes bundled with a useful set of validation methods, including URL and email validation, while providing an API to write your own methods. - jsTree – jsTree is jquery plugin, that provides interactive trees. It is absolutely free, open source and distributed under the MIT license. jsTree is easily extendable, themable and configurable, it supports HTML & JSON data sources and AJAX loading. - Knockout JavaScript library – Knockout is a JavaScript library that helps you to create rich, responsive display and editor user interfaces with a clean underlying data model. Any time you have sections of UI that update dynamically (e.g., changing depending on the user’s actions or when an external data source changes), KO can help you implement it more simply and maintainably. - knockout.TypeScript.DefinitelyTyped - TypeScript Definitions (d.ts) for knockout. - knockout.validation.typeScript.DefinitelyTyped – TypeScript Definitions (d.ts) for knockout. - Knockoutjs - A JavaScript MVVM library to help you create rich, dynamic user interfaces with clean maintainable code. - KnockoutJS.Validation – A validation plugin for KnockoutJS. - Korzh – Ad- hoc query builder is a useful addition to WebForms and the MVC web- app that requires some functionality for advanced searching and/or filtering.
SDL TMS 11.3 Installation Guide Page 22
- Linq.js – Linq to Objects for JavaScript. - linq.js-jQuery – Linq to Objects for JavaScript. This version is plugin integrated with jQuery. - linq.TypeScript.DefinitelyTyped - TypeScript Definitions (d.ts) for linq. Generated based off the DefinitelyTyped repository. - Microsoft ASP.NET MVC – This package contains the runtime assemblies for ASP.NET MVC. ASP.NET MVC gives you a powerful, patterns-based way to build dynamic websites that enables a clean separation of concerns and that gives you full control over markup. - Microsoft ASP.NET Razor – This package contains the runtime assemblies for ASP.NET Web Pages. ASP.NET Web Pages and the new Razor syntax provide a fast, terse, clean and lightweight way to combine server code with HTML to create dynamic web content. - Microsoft ASP.NET Web Optimization – ASP.NET Optimization introduces a way to bundle and optimize CSS and JavaScript files. - Microsoft ASP.NET Web API 2.2 – This package contains everything you need to host ASP.NET Web API on IIS. ASP.NET Web API is a framework that makes it easy to build HTTP services that reach a broad range of clients, including browsers and mobile devices. ASP.NET Web API is an ideal platform for building RESTful applications on the .NET Framework. SDL uses the Web API client libraries, core libraries, the API for OData 4.0, and the Web host. - Microsoft ASP.NET Web Pages – This package contains the runtime assemblies for ASP.NET Web Pages. ASP.NET Web Pages and the new Razor syntax provide a fast, terse, clean and lightweight way to combine server code with HTML to create dynamic web content. - Microsoft BCL Build Components – This package provides build infrastructure components so that projects referencing specific Microsoft packages can successfully build. Do not directly reference this package unless you receive a build warning that instructs you to add a reference. - Microsoft BCL Portability Pack – This packages enables projects targeting down-level platforms to use some of the types added in later versions. - Microsoft Data UnitTesting - Part of Visual Studio, the Microsoft.VisualStudio.TestTools.UnitTesting namespace supplies classes that provide unit testing support. - Microsoft Enterprise Library – Microsoft Enterprise Library is a collection of application blocks designed to assist developers with common enterprise development challenges. Application blocks are a type of guidance, provided as source code that can be used "as is," extended, or modified by developers for use in their development projects. - Microsoft jQuery Unobtrusive Ajax – jQuery plugin that unobtrusively sets up jQuery Ajax. - Microsoft jQuery Unobtrusive Validation – jQuery plugin that unobtrusively sets up jQuery.Validation. - Microsoft HTTP Client Libraries – This package includes HttpClient for sending requests over HTTP, as well as HttpRequestMessage and HttpResponseMessage for processing HTTP messages. This package is not supported in Visual Studio 2010, and is only required for projects targeting .NET Framework 4.5, Windows 8, or Windows Phone 8.1 when consuming a library that uses this package.
SDL TMS 11.3 Installation Guide Page 23
- Microsoft Web Administration - The Microsoft.Web.Administration namespace contains classes that a developer can use to administer IIS Manager. With the classes in this namespace, an administrator can read and write configuration information to ApplicationHost.config, Web.config, and Administration.config files. For more details, see: http://blogs.msdn.com/b/carlosag/archive/2006/04/17/microsoftwebadministration.asp x. - Microsoft Web Infrastructure – This package contains the Microsoft.Web.Infrastructure assembly that lets you dynamically register HTTP modules at run time. - Modernizr – Modernizr is a JavaScript library that detects HTML5 and CSS3 features in the user's browser. - MOQ – Moq is the most popular and friendly mocking framework for .NET. - Mvc.JQuery.Datatables – Strongly type html helpers for rendering jquery.datatables tables from IQueryables. - Newtonsoft.Json – Json.NET is a popular high-performance JSON framework for .NET. - Q – A library for making and composing asynchronous promises in JavaScript. - Q.TypeScript.DefinitelyTyped – TypeScript Definitions (d.ts) for q. Generated based off the DefinitelyTyped repository [git commit: 13308a020d67ad90337790d51f635747e307161c]. http://github.com/DefinitelyTyped. - RequireJS – RequireJS is a JavaScript file and module loader. It is optimized for in- browser use, but it can be used in other JavaScript environments. - requirejs.TypeScript.DefinitelyTyped - RequireJS is a JavaScript file and module loader. It is optimized for in-browser use, but it can be used in other JavaScript environments. - ScriptUtils(ASPForm x64) – This installation package contains ScriptUtilities libraries. - Stimulsoft – This all-in-one solution is a comprehensive platform that includes a complete set of tools to build reports under JavaScript, ASP.NET, ASP.NET MVC, WPF, Silverlight, WinRT, HTML5, Windows Forms, PHP, Java, and Flex. - StructureMap – StructureMap is a Dependency Injection / Inversion of Control tool for .Net that can be used to improve the architectural qualities of an object oriented system by reducing the mechanical costs of good design techniques. - structuremap.automocking – Test utility to instantiate a class by creating mocks for each of its dependencies. - T4Toolbox – T4 Toolbox extends the code generation functionality of the T4 text templates in Visual Studio 2015. - Telerik – Telerik UI for ASP.NET MVC is a suite of products containing Kendo UI Professional and server wrappers for Microsoft's ASP.NET MVC framework. - Text plugin for RequireJS – A RequireJS/AMD loader plugin for loading text resources. - WebGrease – Web Grease is a suite of tools for optimizing javascript, css files and images. - Wix – The WiX toolset builds Windows installation packages from XML source code. The tool-set integrates seamlessly into build processes. - XMLDiffPatch – Generates difference files based on the comparison of two XML documents. This code is based on a very old .Net 1.0 example project.
SDL TMS 11.3 Installation Guide Page 24 SDL (LSE:SDL) is the global innovator in language translation technology, services and content management. With more than 20 years of experience, SDL delivers transformative business results by enabling powerfully nuanced digital experiences with customers around the world.
Are you in the know? Find out why 79 out of the top 100 global brands use SDL at SDL.com and follow us on Twitter, LinkedIn and Facebook.
Copyright © 2017 SDL plc. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.