SDLLiveContentArchitectUpgradeGuidesdl.ssl.cdn.sdlmedia.com › file › 635419658915346017BN.pdf · Author Acolumn for Authormetadata was added to the default baseline view in Publication

SDL LiveContent Architect Upgrade Guide

Product name Version number

SDL LiveContent Architect 10.0.0

December 2012

Notices

Copyright © 2001-2012 SDL plc. All rights reserved. No part of this documentation may be duplicated in whole or in part or

reproduced in any form without the express written permission of SDL plc.

This product may include open source or similar software designated: Apache Lucene, Apache Solr, Lucene Hunspell,

Jetty@Eclipse, Apache Ant, and DITAOpen Toolkit delivered under the Apache License, Eclipse Public License; 7-ZIP delivered

under the GNU LGLP License; Saxon 6.5 delivered under the Mozilla Public License; Korean(ko-aff-dic-0.4.1.zip) delivered

under Mozilla Public License; Dutch (OpenTaal 1.10G) and German (de-DE igerman98) delivered under GNU LGLP License;

French is delivered under "License: Opensource"; XulRunner delivered under the Mozilla Public License; GeckoFX delivered

under the Mozilla Public License; ThinkIdentity, IdentityServer license delivered under the MS-PL license.

LiveContent, LiveContent Architect, LiveContent Create, LiveContent Reach, and XPP are trademarks of SDL plc. 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.

Although SDL plc takes all reasonable measures to provide accurate and comprehensive information about the product, this

documentation 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.

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 document 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 plc.

II SDL LiveContent Architect Upgrade Guide

Contents

1 Release Notes for SDL LiveContent Architect ............................. 1SDL LiveContent Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 1

New third-party software support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 1

Batch metadata operations supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 2

Improved usability for SDL LiveContent Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 3

Importing data - DITA2Trisoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 4

Publication Manager baseline view includes Author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 4

Easier to clear search criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 4

SDLWorldServer integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 5

API changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 6

Authoring Bridge SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 7

Claims based authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 7

Review and collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 9

Validation XML configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 118

Changes to inputparameters.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 10

Changes to Database Upgrade Tool (DBUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 11

Change to ReqMetaDataExportForPublicationXMLForPubObject.xml . . . . . . . . . . . . ... 11

Changes to OnDocStore plugin for images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 11

Removed Admin.XMLTags.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 12

Changes to MetadataConfig.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 12

Fixed Issues in SDL LiveContent Architect 10.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 12

2 Upgrade Requirements ...................................................... 15Software and hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 15

Database layer software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 17

Configuring Microsoft SQL Server . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . ... 57

Creating a database . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . . . . . . . ... 58

Importing data from the SQL dumpfile . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . ... 60

Removing the database user and schema . . . . . . . . . . . . . ... . . . . . . . . . . . . . ... 59

Oracle database configuration requirements . . . . . . . . . . . . ... . . . . . . . . . . . . ... 62

Configuring Oracle RDBMS . . . . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . . . ... 22

Changing the SQLNET.AUTHENTICATION_SERVICES . . . . . ... . . . . . ... 63

Oracle versions configuration . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . ... 63

OracleDataAccessComponents 11. 2. 0. 1 32-bit . . . . . . . . . . ... . . . . . . . . . . ... 81

Third party component requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 39

Setting the MSDTC timeout . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . ... 41

Configuring . NET Framework and Microsoft Message Queuing (MSMQ) .... 41

Configuring IIS and ASP Web services . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . ... 42

IIISDL LiveContent Architect Upgrade Guide

Configuring Application Server Role . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . ... 43

Microsoft XML Parser 4. 0 Service Pack 3 . . . . . . . . . . . . . ... . . . . . . . . . . . . . ... 44

Microsoft . NETFramework 2. 0 SP2 . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . ... 44

Microsoft . NET Framework 3. 0 SP1 Visual C++ Redistributable . . . ... . . . ... 44

Microsoft Server . NETFramework 4. 0 . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . ... 44

Microsoft XML Parser 6. 0 Service Pack 2 . . . . . . . . . . . . . ... . . . . . . . . . . . . . ... 45

JavaDevelopmentKit 1. 6. 0_27 . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . ... 45

HTMLHelpWorkshop 1. 3 . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . ... 45

Antenna House XSL Formatter . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . ... 46

Configuration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 46

Requirements Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 48

Installer User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 50

3 Preparing for the upgrade - backing up the database .................. 51Backing up the project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 51

Backup the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 52

Backing up Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 52

Oracle RDBMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 53

4 Uninstalling .................................................................... 55

5 Configuring the database server ........................................... 57Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 57

Configuring Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 57

Creating a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 58

Removing the database user and schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 59

Importing data from the SQL dumpfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 60

Creating a new database user and schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 61

Oracle RDBMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 62

Oracle database configuration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 62

Changing the SQLNET.AUTHENTICATION_SERVICES . . . . . . . . . . . . . . . . . . ... 63

Oracle versions configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 63

Preparing the Oracle 10g environment . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . ... 63

Creating the Oracle 10g database . . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . ... 69

Importing the data . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . . . ... 80

Preparing the Oracle 11g environment . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . ... 75

Creating the Oracle 11g database . . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . ... 77

Oracle Data Access Components 11.2.0.1 32-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 81

Configuring the Oracle 11g client on Windows 2008 . . . . . . . . . . . . . . . . . . . . . . . ... 83

6 Upgrading the SDL LiveContent Architect server ....................... 85Configuring database connection strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 85

Creating and testing the connection for Microsoft SQL Server . . . . . . . . . . . . . . . ... 86

Creating and testing the connection for Oracle RDBMs . . . . . . . . . . . . . . . . . . . . . ... 87

Preparing for the server upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 89

Prerequisites for the server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 90

Enabling https on the IIS website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 90

inputparameters.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 93

Executing the InstallTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 100

IV SDL LiveContent Architect Upgrade Guide

Enabling network transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 147

Verifying the server after installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 102

7 Post upgrade tasks ......................................................... 103Completing the database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 103

Troubleshooting DatabaseUpgradeTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 104

Adding serverRuntime configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 104

The Administrator setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 105

Completing the Administrator setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 105

Adding the relying party entries for webUI and WCF Services . . . . . . . . . . . . . . . . . . ... 106

Removing the relying party entries for webUI and WCF Services . . . . . . . . . . . ... 108

Installing the SDL LiveContent Create license file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 108

Translation management configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 109

Integration requirements for SDL LiveContent Architect and SDL

WorldServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 110

Configuring the translation builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 112

Verifying URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 114

Enabling network transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 147

Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 115

Creating an account and connecting to the repository . . . . . . . . . . . . . . . . . . . . . . ... 116

Running a client tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 117

Rebuilding the full text index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 118

Validation XML configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 118

How-to references for advanced users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 119

Adding templates to the repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 119

Introduction to load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 123

Configuring asynchronous load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 131

Configuring a batch server for publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 137

Queued Component dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 139

For Windows 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 147

Enabling network transactions . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . ... 147

Firewall Configuration for MDTC . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . ... 148

Firewall configuration for Oracle RDBMs . . . . . . . . . . . . ... . . . . . . . . . . . . ... 149

SDL LiveContent Reach upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 154

Modifying the SETTITLE plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 154

8 Reference for the installation tools and files ............................ 155InstallTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 155

InstallTool overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 155

The InstallTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 156

Unimplemented features of the InstallTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 156

Database Upgrade Tool (DBUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 157

DatabaseUpgradeTool (DBUT) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 157

The DatabaseUpgradeTool (DBUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 158

Unimplemented features of the DatabaseUpgradeTool . . . . . . . . . . . . . . . . . . . . . ... 158

9 Installing desktop clients ................................................... 159Desktop client software and hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 159

Installing the Authoring Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 160

VSDL LiveContent Architect Upgrade Guide

Installing Publication Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 161

Installing Condition Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 161

Installing or upgrading SDL DITA2Trisoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... 162

VI SDL LiveContent Architect Upgrade Guide

Chapter 1

Release Notes for SDL LiveContentArchitect

New features, fixed and known issues in the SDL LiveContent Architect 10.0.0 release

are described.

SDL LiveContent ArchitectThe SDL Trisoft product name changed and is now SDL LiveContent Architect, part of a

SDL LiveContent product integration which includes SDL LiveContent Reach (formerly

known as SDL LiveContent DITA), and SDL LiveContent Create (formerly known as

SDL Xopus).

You may have the SDL LiveContent Architect product as a stand-alone with access to

SDL LiveContent Create, or you may have all products installed depending on your site

requirements.

New third-party software supportSupport for HTML browsers, SQLServer 2008, and Adobe FrameMaker has been

updated.

Multi-browser support

Browser support was expanded so users can access SDL LiveContent Architect on a

non-Microsoft platform such as Linux or on a portable device. The following browsers

are supported:

■ Internet Explorer 8


■ Chrome (latest version)

■ Firefox (latest version)

SQLServer 2008

Microsoft SQLServer 2008 Release 2 SP2

Microsoft SQLServer 2008 SP3

1SDL LiveContent Architect Upgrade Guide

Adobe FrameMaker

■ Adobe FrameMaker 10.0

■ Adobe FrameMaker support with DITA 1.2 DTDs

Batch metadata operations supportedSupport was added so that you can modify properties on multiple objects at the same time

(in batch).

You can:

■ Reassign multiple topics to a different person

■ Send multiple topics to a reviewer of choice

■ Reassign a different translator to multiple topics

■ Reassign a number of topics to a different tech writer

■ Change the status of multiple topics in Publication Manager

■ The user sees a list with all possible status transitions for the selectedobjects.

■ The status is always enabled, if an error occurs, the object appears in theerror list at the botton of the application.

■ Cancel a batch update

Note: Limitations:

■ The user sees a list with all possible status transitions for the selected objects. Thestatus is always enabled, if an error occurs, the object appears in the error list atthe bottom of the application.

■ The system checks if all objects are of the same object type. If not, it is notpossible to change the properties in batch. An appropriate error message isdisplayed to the user.

■ It is not possible to change the status for multiple topics if those topics havedifferent statuses. This has been done to prevent users from making invalid statustransitions.

Release Notes for SDL LiveContent Architect

2 SDL LiveContent Architect Upgrade Guide

Improved usability for SDL LiveContentCreate

Navigation in the SDL LiveContent Architect web client was improved so that it is more

intuitive where to click and which check boxes to select to check out a topic in SDL

LiveContent Create.

■ ACheck Out button was added to the SDL LiveContent Architect web client.

This button was renamed from Edit with Xopus to Check Out for consistency

with the terminology used in the desktop clients.

■ Clicking the Check Out button opens the latest version of the topic in thelanguage for the user in SDL LiveContent Create. If the object is released, the

user is prompted either to create a new version or a new branch.

■ Users can Check Out a topic that they already have checked out. When doing so,note the following:

■ Because the topic could already be open in another tab that does not havethe focus, the user is prompted that the object is checked out. Users areable to check out the topic from this dialog.

■ If a user has two copies of the same topic open in two different tabs, andthe user saves the topic twice, no special exception handling is included toprevent this. The topic is saved twice and the changes that were lastsubmitted are saved in the repository

■ When a user opens a topic from the inbox, the Check Out status in the listview is refreshed when the topic is checked in again.

■ The same icon and text used for the desktop client are used in the web client tomake the tools more consistent.

■ An Undo Check Out button was added to the top-level button bar to allow usersto close the topic without saving the changes they made.

■ The browser window closes.

■ The Quit icon was removed.

■ The Check In button:

■ Was removed for topics. Topics are always checked in from SDL

LiveContent Create unless Undo Check Out is selected . For other object

types such as images, this button is available.

■ The Save and Close button was replaced by a Check In button (icon andlabel are updated) which is available for objects other than topics.

■ Clicking Check In (available for objects other than topics) closes theobject in the browser.

The following OnDocStore plugin is no longer needed, as this plugin was used as a work-around and has been fixed.

<Plugin name="ISHREMOVEXOPUSNAMESPACE" handler="Ish Plugins. CDocRemoveXMLNode" logrun="no" ishcondition="ISHType in (’ISHMasterDoc’, ’ISHModule’, ’ISHLibrary’) and EDT=’EDTXML’"><Description>Remove the namespace that was inserted by Xopus (should befixed in Xopus 4.2.3 or higher)</Description><Parameters><Param



eter name="OnNodeXPath">/ *[namespace::*[local-name() = ’a’]]/namespace::*[local-name() = ’a’]</Parameter></Parameters></Plugin>

Importing data - DITA2TrisoftA new DITA2Trisoft tool is available for importing DITA files from your filesystem into

the SDL LiveContent Architect repository.

Refer to the SDL LiveContent Architect DITA2Trisoft User Guide for information about

importing files using DITA2Trisoft.

Publication Manager baseline view includesAuthor

A column for Author metadata was added to the default baseline view in Publication

Manager.

The metadata field contains the name of the original author (FAUTHOR ).

Easier to clear search criteriaAReset button was added in the Search pane of the Browse Repository window.

The Reset button allows you to clear all search terms so that you don't have to manually

remove all text from the metadata search pane.

This Reset search option is available on the Search tab in the Browse Repository window.

The option is not available for search from the web client at this time.



SDL WorldServer integrationSDLWorldServer excels in tight on-premise integrations with content management

systems via AIS. It allows Content Management System users and Translation

Management System users to access the same content without forcing either group to do

a specific hand-off to the other.

The user experience has improved for creating and exporting translation jobs; the number

of clicks needed to export translation packages has been greatly reduced. Where users

had to use the Translation Statistics Report to export files and had to repeat this process

for every language, they now can create a Translation Job and select a number of

languages all at once. Once the Translation Job is created, users can export the files that

need to be translated to the file system of the SDL LiveContent Architect server then send

them to the SDLWorldServer server. For importing files, the same process as before is

followed.

Note: The current integration is with SDLWorldServer v10.1 and v10.2.

Starting the translation process

■ The technical writer releases objects in SDL LiveContent Architect

■ ATranslation Coordinator creates a translation job. He specifies the sourceand target languages, and he selects a translation template.

Note: ATranslation Template is the name for a project type defined in SDLWorldServer. A project type in SDLWorldServer defines the source locale,

default workflow and workflows for every target locale. When a user sends the

translation job to SDLWorldServer, the connector creates a project in SDL

WorldServer using the specified project type.

■ The Translation Coordinator adds publications and/or other items to thetranslation job.

■ When the job is sent to translation; the Translation Coordinator clicks thebutton Send to translation the SDLWorldServer Connector takes over, and it

automatically:

■ Creates the target stubs in SDL LiveContent Architect for the objects

you selected (~push translations),

■ Extracts the content from the objects in SDL LiveContent Architect,

■ Moves the objects into In translation status, and

■ Creates the project in SDLWorldServer and uploads the files.

In the first release of the SDLWorldServer connector, a translation job cannot be

restarted. You must create a new translation job so that you can track it separately.

Importing translated files

At regular intervals, the SDLWorldServer connector queries SDLWorldServer for all

files that are translated and are ready to be imported in SDL LiveContent Architect;



the SDLWorldServer Connector does not wait until all files in a Translation Job are

translated. Every task is imported separately.

The SDLWorldServer Connector changes the status of the imported files to a

Translated status so there is no need to do this manually anymore.

Mapping language codes

You can map language-locale pairs. This is needed because in SDL LiveContent

Architect you may have 2-digit codes whereas SDLWorldServer codes such as fr-fr

are used.

Workflow in SDLWorldServer

There is no need to modify the workflow in SDLWorldServer. Tasks that are

completed are picked-up by the SDLWorldServer connector automatically. SDL

WorldServer can analyze SDL LiveContent Architect translation packages without

any additional steps.

Limitations

■ The SDLWorldServer connector only accepts files in the source language; it

does not support pre-translated files from SDL LiveContent Architect.

■ You cannot send draft files for translation.

■ You cannot delete projects in SDLWorldServer. You can only cancel or

complete projects. Project are automatically cancelled in SDLWorldServer if

the user cancels a translation job in SDL LiveContent Architect.

API changesThe web services has been migrated to Windows Communication Foundation (WCF)

services in order to support the claims-based authentication.

■ The new WCFWeb Services API deprecates the previous ASMXAPI, but SDLcontinues to support the ASMXAPI in this release.

■ TheASMXAPI will not be supported in the next release and as a result, customersusing the ASMXAPI should start to consider upgrading to the newAPI.

Desupported APIs:

■ application25.Authenticate

NewAPIs:

■ LOV

■ Revisions

■ Settings

Changed APIs:

■ DocumentObject: new methods for retrieving BLOBs in DocumentObject 2.5 nolonger resolve reusable objects



Authoring Bridge SDKRefer to the new SDL LiveContent Architect Authoring Bridge SDK guide for information

about the Authoring Bridge SDK.

■ The primary goal of the SDK is to expose the functions and features of theAuthoring Bridge API to speed-up development of new tools or to make it easierto integrate XML authoring tools with SDL LiveContent Architect.

■ By using this SDK, you can write connectors so authoring tools have access to theobjects in an SDL LiveContent Architect repository. The SDK also provides C#

code samples for the typical repository operations such as view, check out, check

in, and so on, but they do not demonstrate every possible use of the Authoring

Bridge API.

Claims based authenticationClaims-based Authentication is available for all SDL LiveContent products, relying on

the SAML and WS-Federation standards.

Claims-based Authentication is the process of authenticating a user based on a set of

claims about its identity contained in a trusted token which:

■ addresses privacy and other compliance concerns by requesting less specific, lesspersonal information about people, and by trusting other parties or systems todo the proof-of-identity check.

■ allows for cross-domain single sign-on and removes the need for content providersto maintain user names and passwords. Identity providers (IdPs) supply userinformation, while service providers (SPs) consume this information and obtainaccess to secure content.

■ addresses integration of different systems by allowing communications usingopen standards and by providing a platform for developing more specializedidentity connectors between systems.

This provides the following to users:

■ Single sign-on for all SDL LiveContent products

■ Seamless front-end authentication

■ Enables SDL LiveContent applications to be part of a larger SSO realm

■ All API integrations employ the same security model

■ Moves identities authentication from all applications, and security and passwordpolicies from the applications.

■ Integrates with identity providers like AD (through ADFS or a SAML compliantSTS)

■ Provides configuration flexibility

■ Support on-premise, hybrid, or cloud scenarios

■ Provide commonality in configuration in security across SDL LiveContent

products



■ Maintain stand-alone capability for all products

■ All products are still be capable of being stand-alone (internal users /groups)

■ Insures backward compatability for existing customers / custom tools /integrations

Prerequisites include that you, the customer:

■ provide an Identity Provider (Active Directory, Open LDAP)

■ provide a STS which can talk SAML and WS-Federation

■ ADFS - a free STS from Microsoft for Active Directory

■ are responsible for insuring high availability of IDP / STS

■ are responsible for identity management and security policies

Architecture



Review and collaborationWhen using SDL LiveContent Reach you now can display comments across different

versions of a topic, filter comments, sort so you only see relevant threads, respond to

comments, search for comments, modify the document from SDL LiveContent Reach in

SDL LiveContent Create and report on comments and topics.

Note: If you are currently using SDL LiveContent Reach, know that you must republishyour content to enable the new features.

Functionality: Commenting

■ Targeted commenting in both LiveContent Architect and LiveContent Reach -allowing you to comment down to the element level

■ Technical writers can see comments in Publication Manager

■ Technical writers can see all comments on re-used content, or across versionsof the same content

■ Users can comment anytime on any content (including released content)

■ Users can move comments through a configurable list of statuses

■ Users can see commenting activity in analytics

■ Users can get a list of all comments for all publications or a given publication

Functionality: Collaboration

■ Allows in-context editing of content (in-context within the delivery platform)

■ Allows you to open and close a review cycle based on dates

■ You can manually send a URL in an email to notify reviewers of theavailability of the document

■ Collaborator can browse, navigate, or search to find content, and then modifyit in-context

■ You can upload images, insert re-used content, and perform other coreauthoring tasks

■ Administrators can control who can edit content based on SDL LiveContent

Architect permissions and workflow



Validation XML configuration filesAs part of the introduction of the Settings API 2.5, a schema was made for all

configuration XML files.

■ Configuration files received a version number

<InfoShareStatesversion="1.0">...</InfoShareStates>

■ Configuration files are validated against this schema when they are submittedthrough the user interface (UI). The rest of the application assumes that theconfiguration files in the database are valid.

Resubmit the legacy configuration XML files using the Web Client, Settings tab. The

configuration file is validated and some corrections are made. For example, a @version

attribute with the value, 1.0 is added. If there are validation errors when resubmitting the

configuration files, remove all statuses in the status definitions with value "Not found

as LOV Value".

<Status Elm="..." value="Not found as LOV Value"/>

Changes to inputparameters.xmlThe inputparameters. xml file has changed and new parameters have been added.

New values for the <validation> element

■ certificateinstalled

■ certificatevalidationmode

■ wstrustbindingtype

Parmameters that were removed

■ TrisoftXopus merged into InfoShareAuthor

Parameters that need to be modified

■ baseurl must be set always to use the https binding

Parameters that were added

Refer to the SDL LiveContent Architect Information Portal publication for

descriptions, explanations, and examples of the parameters.

■ infosharestswebappname

■ servicecertificatesubjectname

■ servicecertificatevalidationmode

■ issuercertificatethumbprint

■ issuercertificatethumbprint

■ issuercertificatevalidationmode

■ issuerwstrustbindingtype



■ issueractorusername

■ issueractorpassword

■ issuerwstrustendpointurl

■ issuerwstrustmexurl

■ issuerwsfederationendpointurl

■ serviceusername

■ servicepassword

■ localservicehostname

Changes to Database Upgrade Tool (DBUT)A new option was added to the maintenance section of the Database Upgrade Tool to

assist administrators when configuring an ADFS instance.

Option 8 was added to the maintenance part of the database upgrade tool to help

administrators when setting up an ADFS instance. This is because, in the database dump

delivered on the CD, users are not included anymore. This option helps to add an external

id to the admin user so you can run DBUT and login afterwards.

Change toReqMetaDataExportForPublicationXMLForPubObject.xml

The FMAPID ishfield has been added to the configuration settings in theReqMetaDataExportForPublicationXMLForPubObject.xml file.

Added: <ishfield name='FMAPID' level='lng'/> (logical id of a publication).

Changes to OnDocStore plugin for imagesThe OnDocStore plugin code has been modified to improve support for images.

The parameter ExtractXPath was changed from:

<Parameter name="ExtractXPath">(//*[contains(@class,’ topic/image’)][@href!=’-dita-use-conref-target’or not(@conref)][not(ancestor: : *[@conref])][not(ancestor-or-self: : *[@scope and @scope!= ’’][position()=1]/@scope=’external’)]/@href)</Parameter>

to:

<Parameter name="ExtractXPath">(//*[contains(@class,’ topic/image ’)][@href!=’-dita-use- conref- target’ ornot(@conref)][not(ancestor::*[@conref])]



[not(ancestor-or- self::* [@scope and @scope!=’’][position()=1]/@scope=’external’)]/ @href) |(//*[contains(@class,’ topic/ object’)][not(ancestor::*[@conref])][not(contains(@data,’:’))]/@data) | (//*[contains(@class,’ topic/ param ’) and (@name= ’movie’ or @name= ’src’ or @name= ’URL’)][not(ancestor::*[@conref])][not(contains(@value,’:’))]/@value)</Parameter>

Removed Admin.XMLTags.xmlThe Admin.XMLTags.xml configuration file is removed completely.

Changes to MetadataConfig.xmlThe MetadataConfig. xml configuration file contains all of the forms and fieldsrequired for managing Translation Jobs.

Changes were made to the MetadataConfig.xml file to provide for new or improved

translation job functionality in this release.

Fixed Issues in SDL LiveContent Architect10.0.0

Issues that were fixed in SDL LiveContent Architect version 10.0.0 are described.

Issue: Push translation fails

Description: Push Translation fails when generating mixed language file:Generating mixed language file failed: Object variable or Withblock variable not set. See eventdata for more details.

Resolution: Fixed.

PreTranslation issues causing crash which is blocking full pushtranslation

PreTranslation crashes the Translation Management attempt. Fallback is to provide

the source language in the target language file. Related to Mantis ticket numbers:

1873, 3480, 5410, 6808, 6809, 6832, 6844

Resolution: Fixed.

Issue: Unpredictable caching

Description: Unpredictable caching causes out-of-date, or newly created values to not

function properly across multiple web and application servers.

Resolution: Fixed. Single server-side cache strategy which provides for faster

responses with accurate data, and clear instructions on what to restart if you adapt

system changes on one or more machines.



Issue: Synchronization of metadata when server and client are installed in a different

time zones

Description: The server returns a local date/time without adding the time zone offset.

The client therefore assumes that the server uses the same time zone offset as the

client. This leads to client tools not refreshing metadata or client tools refreshing

metadata too frequently.

Resolution: Fixed. A web service was created to retrieve the time zone information

from the server.

Bookmark button does not appear

The bookmark functionality is unavailable; the button does not appear when I insert a

reference.

Resolution: Fixed. This functionality has been restored; tested and verified for insert

hyperlink, insert conref, insert variable, and anchorref support.

When two users refresh the same baseline, Publication Manager crashes

Concurrent baseline editing in Publication Manager results in an application crash;

when two users refresh the same baseline, Publication Manager crashes.

Resolution: Fixed.

Freezing a baseline that is shared between multiple publications crashes Publication

Manager

Problem occurred with a baseline shared by 53 publications. The Publication Manager

code had trouble with an a endless loop in the code and eventually a stack overflow

caused the crash.

Resolution: Fixed.

Loss of Connector functionality as a result of using the Change function in the

FrameMaker element catalog

API client was blocked because of an access violation. The exception was cached and

not rethrown. When the exception is rethrown FrameMaker crashes.

Resolution: Fixed. The exception handling to rethrow exceptions was changed and the

code that caused the FrameMaker crash was removed.

Cannot check out a read-only topic in FrameMaker

When you double-click a topicref, the topic is opened in Read-only mode. But you

cannot check out using the SDL Trisoft menu option; it doesn't work, no error, nothing

happens.

Resolution: Fixed.

Compare PDF only includes the new image in compare mode for changed images

When building a compare PDF output using a topic which includes some text

changes and a reference to the same images (with different versions), the image

change is not available in the rendered output.

Resolution: Fixed.





Chapter 2

Upgrade RequirementsFollow these procedures and check the upgrade requirements only if you are upgrading

an existing SDL LiveContent Architect installation.

Software and hardware requirementsBefore you install or upgrade the server, you must check the software and hardware

requirements and complete the pre-installation tasks. The pre-installation tasks ensure

you do not encounter issues when installing and configuring the necessary SDL

LiveContent Architect software components.

Before starting an SDL LiveContent Architect installation, check the hardware, basic

operating system setup, and third party software as required and qualified with for version

of SDL LiveContent Architect. Focus on the preparation steps which should be verified

or executed before installing SDL LiveContent Architect.

Hardware

The performance of SDL LiveContent Architect depends primarily on the CPU power

and the I/O characteristics of the hardware. High CPU power is needed to allow the

system to make calculations on-the-fly, for example, for publishing. The I/O

performance largely influences the system’s speed to gather and assemble information

from the database to serve user requests. SDL LiveContent Architect imposes no

specific requirements for data storage, as it holds generic versions that become

specific versions by calculation on a user's request.

Know that the hardware required for a specific SDL LiveContent Architect

implementation depends on the specific requirements and settings of the project (for

example, the number of concurrent users). The exact definition of the hardware

requirements is typically done at the beginning of the project.

Database

The system requires one of the following:

■ AUNIX-based SDL LiveContent Architect database server running Oracle:

■ Oracle RDBMs 10.2



■ AMicrosoft Windows SDL LiveContent Architect database server running Oracle

or MS SQL Server, Standard or Enterprise edition:



■ SQLServer2008 SP3

■ SQLServer2008 R2 SP2

■ SQLServer2005 SP4

The SQLServer files, tested with this version of SDL LiveContent Architect, can

be retrieved online from SDL upon request.

Also note the following requirements for the database server:

■ It is important that the system has enough storage available to host your data.

■ To be able to execute database transactions, the Microsoft Distributed TransactionCoordinator (MSDTC) settings of the database server have to match the ones onthe application server. All servers require a reboot before these settings becomeactive.

The database server may be on any platform supported by the database vendor. Hardware

and platform requirements for the database server should be obtained from the database

vendor. The specifications supplied by SDL LiveContent Architect should be checked

against the specifications supplied by the database vendor for the current hardware on

which it is installed.

Web and Application layer

Server operating system (OS) supported for this release is Microsoft Windows 2008

Server Release 2 64-bit (x64).

The server can be on a single system however for performance reasons, it is advised

to scale and have redundancy over multiple servers. The SDL LiveContent Architect

SystemArchitecture document helps you determine the setup. Due to the many setup

variations, you may want to contact the SDL LiveContent Architect support team to

discuss your specific setup.

The minimum server configuration: A recent dual core Xeon® 2.0 GHz system(s)

containing 4 GB of RAM or more. Virtualized environments are supported if they are

guaranteed to behave like a Windows OS installed on a physical machine. If

performance is, or becomes an issue, you are advised to use physical servers.

The recommended server configuration: A Quad Core Xeon® Processor E5640 2.66

GHz system containing 12MB Level 3 cache and 8GB of RAM, with dual port Gigabit

ethernet, and a smart array RAID controller with 256MB memory.

Storage demands: The consumers of storage are the actual installed SDL LiveContent

Architect software components, the full-text-index collection, exported, and published

content. Considering a normal documentation project, with an initial database

reservation of 100 GB, the server should have at least 50 GB. The typical setup is two

servers, one handling the synchronous operations and one server handling the

asynchronous/background operations. Initially you can start with one server handling

all operations; we suggest a dual CPU server. A second server can be added quite

easily afterwards if load needs to be reduced on the primary server.

Upgrade Requirements


Database layer software

Either Microsoft SQL Server or Oracle RDBM is required to host a SDL LiveContent

Architect database.

The SDL LiveContent Architect database can reside on a database server that runs

Microsoft SQL Server or Oracle. One of the following is sufficient as a database layer:

■ AUNIX-based SDL LiveContent Architect DB Server running Oracle:



■ AMicrosoft Windows SDL LiveContent Architect DB Server running Oracle or

MSSQL Server, Standard or Enterprise edition:



■ Microsoft SQL Server 2005

■ Microsoft SQL Server 2008

Only one of these is required to host a SDL LiveContent Architect database. Check the

matching section of your chosen database RDBMs system for explicit version, service

pack and patch numbers.

Note: The software requirements as specified in this document could be changedwithout prior notice.

Hardware and platform requirements for the database server should be obtained from

the database vendor. The SDL LiveContent Architect database server may be on any

platform supported by the database vendor.

Microsoft SQL Server

Database setup on a Microsoft server requires configuration of the server and creation of

the database.

Configuring Microsoft SQL Server

Database setup is done on the Microsoft SQL server.

Be certain to read the pre-installation notes for SQL Server provided in this

documentation.

The SQL Server installation has to be an AccentSensitive, CaseInsensitive,

Unicode-ready installation.



■ If you are doing a fresh SQL Server installation make sure that in the Databaseengine Collation settings, Accent-sensitive is selected and Case-sensitive is notselected.

■ The typical SDL LiveContent Architect collation is

SQL_Latin1_General_CP1_CI_AS (not the often mistaken collation

Latin1_General_CI_AS). Depending on the SQL Server version, the collation

SQL_Latin1_General_CP1_CI_AS is also displayed as Dictionary order,

caseinsensitive, for use with 1252 Character Set.

■ You can check the collation name by issuing a query in SQLServer ManagementStudio connected to your server.

■ To access the SQL Server Management Studio click Start All

Programs > Microsoft SQL Server > SQL Server Management Studio

■ Click New Query then enter:

select Server Property(’Collation’)

■ Click Execute.

■ Verify that the result shows an Accent-sensitive (AS), Case-insensitive(CI) collation name. For more information refer to Collations in the SQL

Server help files.

Authentication based on named SQL Server login ID and on Windows accounts is

recommended.

■ Check or modify this in SQL Server Management Studio, right-click onServerName then click Properties, select Security in the left pane.

■ In the Server authentication pane on the right, select SQL Server and WindowsAuthentication Mode.

SQL Server Agent is part of the SQL Server software.

■ Check that this Windows Service is set to automatically start upon server reboot.Check Start > Control Panel > System and Security > Administrative Tools

then double-click on Services.

■ Verify that SQL Server Agent start up type is Automatic.

To execute database transactions, the Microsoft Distributed Transaction Coordinator

(MSDTC) settings of the database server have to match the ones on the application server.

All servers require a reboot before these settings become active.

Creating a database

Create a database for the SDL LiveContent Architect data collection.

Procedure

1. Open SQL Server Management Studio.

Result: The Microsoft SQL Server Management Studio window displays.

2. Right-click on Databases then click New Database…

3. Enter a database name.

4. Click Options in the left pane.



5. In the Collation field, select: SQL_Latin1_General_CP1_CI_AS

6. In the Recovery model field, select: Full

Note: The Full Recovery model uses database backups and transaction log backupsto provide complete protection against media failure. If one or more data files are

damaged, media recovery can restore all committed transactions. In-process

transactions are rolled back. It provides you with the ability to recover the database to

the point of failure or to a specific point in time. To guarantee this degree of

recovery, all operations, including bulk operations such as SELECT INTO, CREATE

INDEX, and bulk loading data, are fully logged. The recovery model may be set to

Simple to avoid a fast growing transaction log files, but note that this reduces the

number of points-in-time for recovery.

7. In the Compatibility level field:

■ If installing on SQL Server 2005 enter: SQL Server 2005 (90)


8. Click OK.

9. In the originalMicrosoft SQLServer Management Studio window, open Databases

and right-click on the database you created.

10. Click Properties.

Result: A Database Properties window displays for your database.

11. Click Files in the left pane.

12. Change or ensure the following data in the Database Properties window:

■ In the field, Owner, enter: sa

■ Logical name: dbname_Data (for example InfoShare_Data) where the file

type equals Rows Data. Set File Name to dbname.mdf

■ Logical name dbname_Log (for example InfoShare_Log) where the file type

equals Log. Set File Name to dbname_Log.ldf

13. Click OK.

Importing data from the SQL dumpfile

Import the sample SDL LiveContent Architect database dump to validate the

configuration and for training purposes.

Procedure

1. In the SQL Server Management Studio window, under Databases, right-click on

the database you created.

2. Click Tasks > Restore > Database.

3. In the Restore Database window, select From Device then select the latest available

dump provided on the installation CD in:

■ for SQLserver 2005:\Database\Dump\SQLServer2005




Note: If the SQL server 2008 dump is not provided, you can use the SQLserver 2005 dump on the SQL 2008 server.

a. Click the ellipsis button next to the From Device field.

b. Click Add in the resulting Specify Backup window.

c. Locate and select the backup file.

d. Click OK.

e. Verify that the correct file is selected in the Specify Backup window, then

click OK.

4. In the Restore Database window, select Restore next to the database filename in the

lower pane then click Options in the left pane.

5. Select Overwrite the existing database.

6. Click OK.

Result: The database is restored.

7. After restoring the database, use SQL Server Management Studio to check the

recovery model and verify that Full is selected for the Recovery model.

Removing the database user and schema

To ensure successful creation of a new database user and schema, delete the user and

schema that was created when importing the sample data.

About this task

A database user in SQL Server exists on two levels, as an account on the SQL Server

level and as an account on your database. Depending on the kind of initial database setup

dump you received, you could have problems creating your new database user. Therefore,

you should delete the InfoShare database designated user (by default named isource)

and schema.

Note: The user listed within the created database part is to be removed and not thegeneral SQL Server part listed under Security > Logins.

Procedure

1. In the SQL Server Management Studio window, under Databases, locate and open

the tree under the database you created.

2. Open Security > Schemas.

3. Right-click on isource then click Delete.

Result: A Delete Object window displays.



Note: The isource user may not exist under Schemas. If it does not exist, skip thisand the next step; continue to the step to open Security > Users.

4. Click OK to confirm the removal.

5. Open Security > Users.




Oracle RDBMs

The installation makes use of the Oracle Database Configuration Assistant (DBCA) and

command line programs to create and set up the database. This allows for anyone with a

mixture of Windows and UNIX knowledge to be able to set up an environment on any

Oracle hosting machine.

The configuration procedure refers to a Windows environment when noting system

variables and file paths.

This procedure guides a knowledgeable person through the configuration so that no

important steps are forgotten. However, it does not provide an explanations, or all the

options for each step.

Note: The default database name is ISH.

Oracle database configuration requirements

The users who can configure Oracle must have permissions and access as required and be

familiar with Oracle and Microsoft environments.

All implicit steps that must be done were considered for inclusion in these procedures.

The procedures were written for administrators who have knowledge of the Oracle and

Microsoft environments.

Please be sure that you satisfy the following before beginning:

■ ADBA role is required for a database migration.

■ A server reboot is required after Oracle installation to make sure that all Oracleenvironment settings are available to you.

■ Settings should be NLSCHARACTERSET=UTF8,NLS_LENGTH_SEMANTICS=CHAR andNLS_NCHAR_CHARACTERSET=AL16UTF16



Also note:

■ Executed actions should be done in the same command window so settings whichare shell specific, for example, ORACLE_SID or ORACLE_HOME areavailable.

■ All paths are examples only. Paths are system specific, so make sure that all filepaths are valid and contain the correct file(s), and beware of read-only flagson files.

■ The default database name is ISH and is used in examples in the procedures.

Configuring Oracle RDBMS

Database setup may be done on a Oracle RDBMS 10.2 or Oracle RDBMS 11.2.

NLS CHARACTERSET=UTF8, NLS_LENGTH_SEMANTICS=CHAR and

NLS_NCHAR_CHARACTERSET=AL16UTF16 settings are recommended.




Changing the SQLNET.AUTHENTICATION_SERVICES

A freshly installed Oracle database sometimes results in ORA-12638 errors. If you are

running a dedicated SDL LiveContent Architect Oracle server, you can resolve problems

by altering the SQLNET.AUTHENTICATION_SERVICES setting.

Note: If you are not running a dedicated SDL LiveContent Architect Oracle server,contact your Oracle DBA.

1. OpenOracle file\network\admin\sqlnet.ora

2. Change the value of parameter SQLNET.AUTHENTICATION_SERVICES to

(none). This setting is instead of (NTS).

Oracle versions configuration

Procedures for configuring Oracle RDBMS 10g and Oracle RDBMS 11g is described.

Refer to the procedure for using the required Oracle RDBMs version 10.2.0.2 (or higher)

or Oracle RDBMs version 11.2.0.1 (or higher).

Oracle 10g configuration

Oracle 10.2.0.2 or higher is required. The procedure guides a knowledgeable person

through the configuration so that all important steps are completed.

Preparing the Oracle 10g environment



To prepare your environment, you must copy and edit the delivered Oracle 10g files, and

activate the listener service.

About this task

To begin, copy the files delivered on the installation CD.

Procedure

1. Locate the\Database\Dump\Oracle\Oracle102.Admin folder on the installationCD.

Result: The folder contains the ISH Admin folder structure and files such as:

■ pfile\initISH.ora (default pfile)

■ create\crdbs.sql (create the database)

■ create\crtbs.sql (create tablespaces)

2. If it does not exist, create a C:\oracle\ admin directory.

3. Copy the the ISH folder to the C:\oracle\ admin directory.

Configuring the parameters file

Edit the file (PFILE) that contains information about the database parameters.

Procedure

1. Open for editing, the initISH.ora parameters that you copied into C:\oracle\admin\ISH\pfilewhen preparing the system.

2. Define the following in the file:

■ the database identifier

■ the location of the database

■ the database instance

■ directories for the control files

■ directories to store trace and alert files

Note: Refer to the documentation within the file about these parameters.

3. Because Oracle expects the parameters file to be in (on Windows) C:\oracle\product\10.2.0\db_1\databaseor (onUNIX/Linux)$ORACLE_HOME/dbsyoumust create a link.

To do this, create a text file named initISH.ora in C:\oracle\ product\10.2.0\ db_1\ database or $ORACLE_HOME/ dbs and add the following to the file'scontents:

IFILE=C:\oracle\admin\ISH\pfile\initISH.ora



Note: The path in the step above is an example and should reflect your Oraclehome directory.

Configuring the database creation files

Configure the files that are used to create the Oracle database and tablespaces.

Before you begin

The Oracle DBA should edit these files.

Review the steps and sample files below before editing to be sure you have the

information necessary to properly configure the database creation files.

Procedure

1. Open and edit the file used to create the database: C:\oracle\ admin\ ISH\create\ crdbs.sql file. A sample of the file's contents is:

CREATE DATABASE ISHCONTROLFILE REUSEMAXINSTANCES 16MAXLOGFILES 32MAXDATAFILES 128CHARACTER SET UTF8DATAFILE’C:\Oracle\OraData\ISH\sys_ISH.dbf’SIZE 240M REUSE AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCAL

SYSAUX DATAFILE ’C:\Oracle\ OraData\ ISH\ sysaux_ISH.dbf’

SIZE 70M REUSE AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDDEFAULT TEMPORARY TABLESPACE "isrc_temp" TEMPFILE’C:\Oracle\OraData\ISH\temp01.dbf’SIZE 20M REUSE AUTOEXTEND ON NEXT 500K MAXSIZE UNLIMITEDUNDO TABLESPACE "isrc_rollback" DATAFILE ’C:\Oracle\ OraData\ISH\rollback01.dbf’SIZE 100M REUSE AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDLOGFILEGROUP 1 (’C:\Oracle\ OraData\ ISH\ redoISH1.log’) SIZE 32M,GROUP 2 (’C:\Oracle\ OraData\ ISH\ redoISH2.log’) SIZE 32M,GROUP 3 (’C:\Oracle\ OraData\ ISH\ redoISH3.log’) SIZE 32M

2. Open and edit the file used to create the database tables: C:\oracle\ admin\ ISH\create\ crtbs.sql file. Make sure the paths are correct for the datafiles, and resizethe datafiles as noted below:

DATAFILE SIZE

DATA_M1.DBF 32M

DATA_S1.DBF 32M



DATAFILE SIZE

INDEX_M1.DBF 64M

INDEX_S1.DBF 128M

PAGE_M1.DBF 64M

ROLLBACK01.DBF 128M

TMPDATA1.DBF 64M

SYS_ISH.DBF 256M

3. Optional, if not already specified: Add extra datafiles to your static size files which

increase (auto growth) in size when necessary until they reach your disk limit. If not

specified already, add the datafiles noted below with AUTOEXTEND ON and a

maxsize of 1M.

To TABLESPACE Add DATAFILE

ISRC_DATA_M DATA_M2.DBF

ISRC_DATA_S DATA_S2.DBF

ISRC_INDEX_M INDEX_M2.DBF

ISRC_INDEX_S INDEX_S2.DBF

ISRC_PAGE PAGE_M2.DBF

A sample of the delivered file's contents is:

CREATE TABLESPACE "ISRC_TEMPDATA"DATAFILE ’C:\Oracle\ OraData\ ISH\ Tmpdata1.dbf’ SIZE 10MAUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTO

/CREATE TABLESPACE "ISRC_DATA_S"DATAFILE ’C:\Oracle\ OraData\ ISH\ Data_S1.dbf’ SIZE 20MAUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISRC_DATA_M"DATAFILE ’C:\Oracle\ OraData\ ISH\ Data_M1.dbf’ SIZE 20MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISRC_INDEX_S"DATAFILE ’C:\Oracle\ OraData\ ISH\ Index_S1.dbf’ SIZE 20MAUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITED



EXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISRC_INDEX_M"DATAFILE ’C:\Oracle\ OraData\ ISH\ Index_M1.dbf’ SIZE 20MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISH_DATA_M"DATAFILE ’C:\Oracle\ OraData\ ISH\ ISH_DATA_M1. dbf’ SIZE 20MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISH_INDEX_M"DATAFILE ’C:\Oracle\ OraData\ ISH\ ISH_INDEX_M1. dbf’ SIZE 20MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISRC_PAGE"DATAFILE ’C:\Oracle\ OraData\ ISH\ Page_M1.dbf’ SIZE 50MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/

Activating the Oracle Listener service

You must start the Oracle listener service so incoming client connection requests are

received and sent to the database server.

Procedure

1. Open a command prompt window and set the ORACLE_HOME variable.

For example, in the command prompt window, enter: set oracle_home=c:\oracle\product\11.2.0\dbhome_1

2. In the same command prompt window, enter lsnrctl start.

Result: This ensures that an OracleOraDb<nn>g_home1TNSListener serviceexists in the Services Control Panel. Where <nn> is the Oracle versionnumber.

For example:

■ OracleOraDb10g_home1TNSListener




3. Go to Start > Programs > Administrative Tools > Services and locate the

OracleOraDb<nn>g_home1TNSListener service and make sure it is set to

Automatic.

4. Restart the OracleOraDb<nn>g_home1TNSListener service.

If your database and application server are not able to communicate with each other,

it is typically because the two-way communication is blocked by a firewall or security

settings are not matching. Refer to the topic about security and firewall configuration

for more information.

Creating the Oracle 10g database

You must create the Oracle database instance for the SDL LiveContent Architect

repository.

Before you begin

All commands should be entered in the same command window to ensure that all

necessary environment variables are set throughout the process.

Procedure

1. At a command prompt, set the ORACLE_SID and ORACLE_HOME variables. For

example:

Set ORACLE_SID= ISH

Note: The ORACLE_SID value is the SERVICE NAME value in the tnsnames.orafile. In this example it is ISH.

SetORACLE_HOME=C:\oracle\product\10.2.0\db_1\

Note: The ORACLE_HOME value is the location of the Oracle software. In thisexample it is C:\oracle\product\10.2.0\db_1\.

2. To create the database instance, at the same command prompt where you set the

variables above, as one statement (that is, enter it on a single line) type:

ORADIM -NEW -SID Oracle_SID -STARTMODE AUTO –PFILEOracle_home\database\initISH.ora

where:

■ Oracle_SID is the value you set for the ORACLE_SID in the previous step.

■ Oracle_home is the value you set for ORACLE_HOME in the previous step.

For example:



ORADIM -NEW -SID ISH -STARTMODE AUTO –PFILE C:\oracle\product\10.2.0\db_1\database\initISH.ora

3. Create the new password file by executing the following command as one statement:

ORAPWD FILE=Oracle_home\ database\ pwdISH.ora PASSWORD= CHANGE_ON_INSTALL

where Oracle_home is the value you set for ORACLE_HOME in a previous step. Forexample:

ORAPWDFILE=C:\oracle\product\10.2.0\db_1\database\pwdISH.ora PASSWORD= CHANGE_ON_INSTALL

4. Create the database folder,C:\oracle\ OraData\ ISH. This is the place where the data

is stored.

Result: The directory is required and not created by Oracle. Make sure thatall paths exist.

5. Create the database and data files:

a. Start SQLPLUS /NOLOG from the same command prompt window (where

all variables are set):

SQLPLUS / NOLOG

b. The indented lines below are commands which should be executed in server

manager.

Important: You must make sure that all files are in the correct locations asnoted in the commands. Read through the next sequence and adjust the paths

to match the ones on your system.

Tip: To ensure that all commands are accurately executed, you can paste thecommands below into a text editor, edit the necessary paths for your

environment, then copy each command and paste it at the command prompt to

execute it.

SET TERMOUT ONSET ECHO ONSPOOLC:\oracle\admin\ISH\create\dbadmin1.logCONNECT SYS/ CHANGE_ON_INSTALL AS SYSDBASTARTUP NOMOUNT PFILE=’C:\oracle\ product\ 10.2.0\db_1\database\initISH.ora’@C:\oracle\admin\ISH\create\crdbs.sql@C:\oracle\admin\ISH\create\crtbs.sql



@C:\oracle\product\10.2.0\db_1\rdbms\admin\catalog.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\catexp.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\catblock.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\catproc.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\catoctk.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\owminst.plb;@C:\oracle\product\10.2.0\db_1\rdbms\admin\dbmspool.sql@C:\oracle\product\10.2.0\db_1\rdbms\admin\prvtpool.plb@C:\oracle\product\10.2.0\db_1\RDBMS\ADMIN\xaview.sqlDROP public SYNONYM dbms_shared_pool;CREATE public SYNONYM dbms_shared_pool FOR sys. dbms_shared_pool;GRANT execute ON dbms_shared_pool TO public;CONNECT SYSTEM/ MANAGER@C:\oracle\product\10.2.0\db_1\sqlplus\admin\pupbld.sql;@C:\oracle\product\10.2.0\db_1\sqlplus\admin\help\hlpbld.sql helpus.sql;CONNECT SYS/ CHANGE_ON_INSTALL AS SYSDBA@C:\oracle\product\10.2.0\db_1\rdbms\admin\utlrp.sql;SHUTDOWNSTARTUP

SPOOL OFF



Creating the designated ISOURCE database user

You must create the ISOURCE designated database user for the new database.

Procedure

1. Optionally, copy theCD_Package/Applications/TriDK/Database/Oracle/create/ isrcuser.i to a temporary location on your server.

Makesure that the\Applications\TriDK\Database\Oracle\create\isrcuser.i file path in the command below is to the full file path of the file either on theCD or, if copied to your system, to the temporary location on your system.

The example below is specific for Windows. Be sure to modify the path and command

for your environment.

2. Open a Command Prompt Window as Administrator and set the following variables:

Set ORACLE_SID=ISH

Set ORACLE_HOME=C:\oracle\product\10.2.0\db_1\

or


Note: All commands must be entered in the same window, ensuring that everyenvironment variable set, is available throughout the process. The next steps presume

that you use the same shell with these variables set correctly.

3. Make sure that the folder C:\oracle\ admin\ ISH\ create exists before continuing.

Note: If the folder is missing the error SP2-0606: Cannot create SPOOL file"C:\oracle\admin\ISH\create\dbadmin2.log, is displayed when issuing the command

below.

4. Start SQLPLUS /NOLOG from the same window:

SQLPLUS /NOLOG

5. At a command prompt where the variables for ORACLE_SID and ORACLE_HOME

are set, type:

SPOOLC:\oracle\admin\ISH\create\dbadmin2.logCONNECT SYS/ CHANGE_ON_INSTALL AS SYSDBA@CD_Package\Applications\TriDK\Database\Oracle\create/isrcuser.iCONNECT ISOURCE/ isource@?/RDBMS/ADMIN/catdbsyn.sqlSPOOL OFF;



Importing the data

Import the sample data to validate the configuration and for training purposes.

Procedure

1. Edit the\Database\Dump\Oracle\import\ISOURCE.Rows.par file and edit theparameters for your system and environment. Make sure that the location of the dump files,connect strings, log files and other parameters are correct.

You may typically edit the following parameters:

■ FILE=..\export\export.ISOURCE.Ora<num>.ISH.dmpwhichpointsto the dump file you want to import. For example:

..\export\export.ISOURCE.Oracle10.2.InfoShareEmpty.dmp

■ LOG=import.ISOURCE.Rows.logwhich points to a logfile to which the imp.exe writes log information.

■ USERID=ISOURCE/ ISOURCE@ISH. WORLDwhich is the user account that isused to import the dump file.

2. In the same\Database\Dump\Oracle\import\ISOURCE.Rows.par file checkthe parameters to do a user to user (ISOURCE to ISOURCE) import of the data from the dmpfile. For example:

The file contains FROMUSER= ISOURCE and TOUSER=ISOURCE. The dump file(FROMUSER) contains an ISOURCE schema and the database (TOUSER) has a ISOURCEschema created by the isrcuser.i script.

3. At command prompt, go to the \ Database\ Dump\ Oracle\ import folder andimport the data by entering the following command:

imp parfile=import. ISOURCE. Rows.par

Removing the designated ISOURCE database user

This procedure can be used if the import fails and you want to remove the the ISOURCE

user and all the objects it owns.

Procedure

1. Start SQLPLUS /NOLOG from a shell where the ORACLE_SID and

ORACLE_HOME variables are set correctly; at a command prompt type:

CONNECT SYS/ CHANGE_ON_INSTALL AS SYSDBADROP USER ISOURCE CASCADE;

2. Recreate the ISOURCE user.



Validating the database

The newly imported Oracle database needs some packages, triggers and more to be

(re-)compiled for the database to be valid.

Procedure


ORACLE_HOME variables are set correctly, at a command prompt type:

SQLPLUS / NOLOG

2. Enter the following statements to validate the database. Do not use a script file.

CONNECT SYS/ CHANGE_ON_INSTALL AS SYSDBA@?/rdbms/admin/utlrp;

Result: All objects in the database should be valid.

Importing the data


Procedure














The SDL LiveContent Architect database is created using the Oracle Database

Configuration Assistant. Oracle version 11.2.0.1 or higher is required.

When installing with Database Configuration Assistant, SDL LiveContent Architect uses

a template with SPFile and without specification for the NLS_LENGTH_SEMATICS.

The database is created with NLS_LENGTH_SEMATICS = BYTE.

The SDL LiveContent Architect requested setting is NLS_LENGTH_SEMATICS =

CHAR. To correct this, SDL LiveContent Architect recommends executing the

DatabaseUpgradeTool after each creation or update of the Oracle database. The

DatabaseUpgradeTool checks and corrects the NLS_LENGTH_SEMATICS to CHAR

using a statement such as:

alter system set nls_length_semantics= char scope= both;


To prepare your environment for the Oracle configuration, you must first copy the

template file to your server.

About this task

From: \Database\Dump\Oracle\Oracle112.Admin\DBCATemplates\SDL-

Trisoft.InfoShare-Database-Template.dbt

To: C:\Oracle\product\11.2.0\dbhome_1\assistants\dbca\

templates on the server




Procedure





For example:







Automatic.








repository. This is the place where the data is stored.

Procedure

1. Create the database folder,C:\oracle\OraData\ ISH.

The directory is required and not created by Oracle. Make sure that all paths exist.

2. Start the Database Configuration Assistant.

3. Click Next.

4. Select Create a Database then click Next.

5. Select the SDL-Trisoft. InfoShare-Database-Template then clickNext.

6. Enter the Global Database Name and SID then click Next.

For example:

■ Global Database Name: ISH.global.SDL.corp

■ SID: ISH

7. Optionally, select the Configure Enterprise Manager and Configure Database

Control for local management then click Next.

Result:

Optionally you are prompted with:

Configuring database with Database Control requires a listener to be configured in the current Oracle home. You need torun Netca to configure a listener before you can proceed.Otherwise you may choose to continue without Database Control configuration

If prompted to do so, add the listener service:

■ Start the Netca Oracle program as the Administrator user

■ Select the default values: Listener configuration – add – LISTENER – port1521)

■ At a command prompt, type lsnrctl start

■ This ensures an OracleOraDb11g_home1TNSListener service exists in theServices Control Panel.

■ At the same command prompt type: lsnrctl reload



■

Go to Start > Programs > Administrative Tools > Services and locate the

OracleOraDb11g_ home1TNSListener service. Make sure that is set to

Automatic then restart it.

Note: If your database and application server are not able to communicatewith each other, it is typically because the two-way communication is blocked

by a firewall or security settings are not matching. Refer to the topic about

security and firewall configuration for more information.

■ Continue with the Database Configuration Assistant wizard.

8. Select either Use Different Administrative Passwords or Use the Same

Administrative Password for All Accounts then enter a Password and Confirm the

password.

This password is requested later. SDL is not able to assist you if you do not know the

password so it is advised to record and store the password in a secure place.

9. Click Next.

10. For storage locations choose either:

■ Use Database File Locations from Template which points to

%ORACLE_BASE%/oradata/DB_UNIQUE_NAME.

Tip: DB_UNIQUE_NAME is a DBCA File Location Variable.

■ Use Common Location for All Database Files where you must specify a path.

For example: C:\Oracle\ OraData

Note: Be sure the path exists!

11. Click Next.

12. Optionally, you can change the recovery configuration in the next window.

13. Click Next.

14. Leave the Database Components as specified by the template; click Next.

15. In the next window, optionally, you can lower the default amount of memory. By

default DBCA detects the amount of memory and takes 80% of this. If you change

this, specify at least 1GB of memory.

Leave the Character Sets, and Connection Mode parameters as specified by the

template.



Note: The template specifies that the character set as UTF8 however, the UI showsAL32UTF8. Know that the Database Configuration Assistant creates the database

with the required correct character set. Explicitly changing the character set to UTF8

is possible by deactivating Show recommended character sets only then choosing

UTF8, but this is unnecessary.

16. Click Next.

17. Leave all settings as specified in the next window and click Next.

18. Click Finish.

19. Click OK.

Result: The database is created.



Procedure






Set ORACLE_SID=ISH


or






below.




SQLPLUS /NOLOG


are set, type:


Importing the data


Procedure
















Procedure








Procedure



SQLPLUS / NOLOG




Oracle Data Access Components 11.2.0.1 32-bit

This is required if you use Oracle RDBMs to host your database.

About this task

The Oracle Data Access Components 11.2.0.1 or ODAC – 32 bit is required if you use

Oracle RDBMs to host your database. It must be installed as the Administrator user. More

information can be found in the Oracle documentation.

The version tested with this version of SDL LiveContent Architect can be retrieved upon

request at SDL. The necessary files are part of the Oracle Database 11g Release 2 Client

(11.2.0.1.0) for Microsoft Windows (32-bit): win32_11gR2_client.zip

The package provides three parts:

■ Oracle Provider for OLE DB

■ Oracle Data Provider for .NET 2.0

■ Oracle Services for Microsoft Transaction Server



Procedure

1. In the Select Installation Type window, click Custom.

Note: The Select Installation Type window is displayed after the Welcome screenwhen you launch the Oracle.

2. Click Next.

Result: Select Product Languages window displays.

Preferably leave only English as selected Product Languages.

3. Click Next.

Result: Specify Installation Location window displays.

4. Enter the following in the fields as note.

■ Oracle Base: C:\Oracle

■ SoftwareLocation:C:\Oracle\product\11.2.0\client_1

5. Click Next.

Result: The Available Products Components window displays.

6. Select:

■ Oracle Net



■ Oracle Data Provider for .NET

7. Click Next.

8. Accept the suggested port number by clicking Next.

Make certain that your fire wall settings match this.

9. Addanentry in theC:\Oracle\product\11.2.0\client_1\network\admin\tnsnames.ora file that identifies the location of the Oracle database.

If you do not know how to add entries to this file, contact your Oracle database

administrator.

Third party component requirements

Third party components for the SDL LiveContent Architect application, web, and batch

servers are described.



Software compatibility

Information about third party or client software is packaged, configured and tested for

this version software release.

The following information includes:

■ The SDL LiveContent Architect client tools versions which should be used with

this release of the server side components.

■ The Third Party software which is configured or integrated in this release of theserver side components.

■ The Third Party software such as the operating systems, databases, and runtimeswhich are quality assurance tested.

Attention:While versions other than those listed may work, know that they arenot quality assured so if a problem is encountered customer support will only

accept the issue if it is reproducible for the listed versions.

Restriction: The relation between the SDL LiveContent Architect Authoring Bridgeand the XML editors is not specified below. Installation packages for SDL LiveContent

Architect Authoring Bridge are not always available for all xml editors.

Note: The names, trademarks, designs, logos, service marks, intellectual property, etc. ofthe products shown are exclusive property of their respective owners.

■ Windows 2008 Server Release 2 (64-bit)

■ Oracle RDBM 10.2

■ Oracle RDBM 11.2

■ Microsoft SQLServer2005 SP4

■ Microsoft SQLServer2008 SP3

■ Microsoft SQLServer2008 R2 SP2

■ Java Runtime 1.6.0_27 (32-bit)

■ Java Development Kit 1.6.0_27 (64-bit)

Microsoft Windows 2008 Server

Additional installation and configuration requisites are described for the SDL LiveContent

Architect product installation.

The SDL LiveContent Architect software must be installed on a Microsoft Windows 2008

Server Release 2 64-bit (x64).

Note: PowerShell v2 is required and should be installed by default on a Windows2008R2 system.



Setting the MSDTC timeout

The default timeout for the Microsoft Distributed Transaction Coordinator is 60 seconds.

For some of the queued components this might not be sufficient to complete the whole

transaction. The transaction timeout should be set to a higher value, for example 3600

seconds.

About this task

Note: This must be done on the database server, and all SDL LiveContent Architectservers

Procedure

1. Go to Start > Administrative Tools > Component Services.

2. Double-click on Computers in the middle pane.

3. Right-click onMy Computer in the middle pane then select Properties.

4. Click the Options tab and set the Transaction timeout to a higher value such as

3600 seconds.

5. Click OK.

6. Go to Start > Administrative Tools > Services.

7. Restart the Distributed Transaction Coordinator Service


(MSDTC) settings of the database server have to match the ones on the application

server. All servers require a reboot before these settings become active.

Note: IfMessage Queuing is already installed, this prompts that the MessageQueuing service will be restarted.

Configuring .NET Framework and Microsoft Message Queuing (MSMQ)

It is required that the .NET Framework and Microsoft Message Queuing be installed.

Before you begin

This is an optional component during a Windows installation, and is not installed by

default during operating system setup.

Procedure

1. Click Start > Control Panel > Programs and Features then on the left side of the

window, select Turn windows features on or off.

2. In the (left side) Server Manager pane, click Features.

3. Click Add Features in the right pane.

Result: A Select Features window is displayed.



4. Open the .NET Framework <version> Features tree node and select the .NET

Framework <version> option.

5. OpenMessage Queuing > Message Queuing Services tree node and select the

Message Queuing Services option.

If the feature(s) are greyed and already installed (the Next button is not available)

skip the next steps and instead, click Cancel.

6. Click Next.

7. Click Install.

Configuring IIS and ASP Web services

It is required that the Web Services (IIS, ASP) be installed.

Before you begin



Procedure



2. In the (left side) Server Manager pane, click Roles.

3. Click Add Roles (upper right).

Result:

If prompted with Before You Begin, click Next.

A Select Server Roles window is displayed.

4. In the Select Server Roles window, check the box for theWeb Server (IIS) role.

5. Click Next.

6. Under Role Services in the right pane, click Add Role Service.

7. Under Common HTTP features select:

■ Static Content

■ Default Document

■ Directory Browsing

■ HTTP Errors

8. Under Application Development select:

■ ASP .NET

■ .NET Extensibility

■ ASP

■ ISAPI Extensions

■ ISAPI Filters



9. At this point you can also add compression for static content; needed to compress the

JavaScript files required for SDL LiveContent Create in both, SDL LiveContent

Reach and SDL LiveContent Architect: Under Performance select Static Content

Compression.

10. Under Health and Diagnostics select:

■ HTTP Logging

■ Request Monitor

11. UnderManagement Tools select:

■ IIS Management Console

12. Select IIS 6 Management Compatibility.

All options under IIS 6 Management Compatibility should be selected.

13. Click Next.

14. Click Install.

Configuring Application Server Role

It is required that the Application Server Role is installed.

Before you begin



Procedure



2. In the Server Manager window, right-click Roles then click Add Roles.

Result:

If prompted with Before You Begin, click Next.

An Add Roles Wizard window is displayed.

3. Select Server Roles in the left pane.

Result: The Select Server Roles window is displayed.

If the feature(s) are greyed and already installed (the Next button is not available)

skip the remaining steps and instead, click Cancel.

4. Select the Application Server role.

5. Select Role Services under Application Server in the left pane.

6. Open the Distributed Transactions tree.

7. Select the Incoming Remote Transactions and Outgoing Remote Transactions.

8. Click Next.

9. Click Install.



Microsoft XML Parser 4.0 Service Pack 3

It is required that the Microsoft XML Parser be installed.

About this task

The Microsoft XML Parser 4.0 Service Pack 3, or MSXML4SP3, must be installed for

use with this version of SDL LiveContent Architect.

Microsoft .NET Framework 2.0 SP2

It is required that the Microsoft .NET Framework 2.0 SP2 be installed.

About this task

The corresponding updates for Microsoft Windows 2008 R2 are deployed via the full

.NET Framework 3.5 Service Pack 1. Version 3.5 of the .NET Framework uses the

Common Language Runtime of version 2.0.

The .NET Framework 2.0 SP2 can only be installed by installing the .NET Framework

3.5 SP1 package. All ASP.NET components must be hosted using .NET version

2.0.50727.

Verify the ASP.NET version on Default Web Site:

Procedure

1. Click Start > Administrative Tools > Internet Information Services Manager

2. In the left pane, navigate down Local computer > Sites > Default Web

Site > Aspnet_client > System_web

3. Verify that at this location there is a folder named 2_0_50727.

Microsoft .NET Framework 3.0 SP1 Visual C++ Redistributable

It is required that the Microsoft .NET Framework 3.0 SP1 Visual C++ Redistributable be

installed

About this task

Both the 32-Bit and 64-Bit version of Microsoft .NET Framework 2008 3.0 Service Pack

1 Microsoft Visual C++ Redistributable must be installed for this version of SDL

LiveContent Architect.

The NETFramework2008_3.0_ServicePack1_MicrosoftVisual

C++Redistributable_(vcredist_x86).exe and NETFramework2008_

3.0_ServicePack1_MicrosoftVisual C++Redistributable_(vcredist_x64).exe tested

with this version of SDL LiveContent Architect can be retrieved online from SDL upon

request.

Microsoft Server .NET Framework 4.0

It is required that the Microsoft .NET Framework 4.0 be installed.

If the component is not installed, InstallTool errors with a notice such as:



RegAsm.exe - .NET Framework Initialization Error

The NET Framework tested with this version of SDL LiveContent Architect can be

retrieved online from SDL upon request. (NET

Framework2010_4.0.30319_dotNetF40_Full_x86_x64.exe)

Attention: Do not take the install package for .Net Framework 4.0 Client Profile.

Prerequisites for publishing engine

These software packages are required on the server that handles SDL LiveContent

Architect publishing.

Microsoft XML Parser 6.0 Service Pack 2

Only required for SDL LiveContent Architect publishing engine.

About this task

You need to install these components if you use the SDL LiveContent Architect

Publishing engine. Both the 32-Bit and 64-Bit version of Microsoft XML 6.0 Parser SP2

must be installed.

Note: For Windows 2008R2, both versions may already be installed. To check, verifythe existence of the file msxml6.dll in these folders:

■ C:\windows\system32

■ C:\Windows\syswow64

Java Development Kit 1.6.0_27

Only required for the SDL LiveContent Architect Publishing engine.

The 64-Bit version of the Java Development Kit 1.6.0_27 must be installed.

When you install JDK you only need the Development Tools. (Source Code and Public

JRE is not required.)

Java files tested with this version of SDL LiveContent Architect can be retrieved online

from SDL upon request.

HTML Help Workshop 1.3

Only required for the SDL LiveContent Architect Publishing engine.

On a 64-bit operating system the default installation path is C:\Program Files

(x86)\HTML Help Workshop

The htmlhelp.exe file tested with this version of SDL LiveContent Architect can be



retrieved online from SDL upon request.

Antenna House XSL Formatter

Required if you use the SDL LiveContent Architect Publishing engine and the Antenna

House XSL Formatter software by Antenna House to render your output.

To allow the proper rendering of non-Western language such as Thai or the East Asian

languages, you must have the specialized fonts available. SDL LiveContent Architect

expects that all available complex script, right-to-left and East Asian language support are

available.

The file tested with this version of SDL LiveContent Architect was Antenna House XSL

Formatter 6.0 and can be retrieved online from SDL upon request.

Note: You may use a later version of Antenna House XSL Formatter; check with yourSDL customer support representative if you have any questions.

Configuration requirements

After installation, some components need to be configured to conform to SDL

LiveContent Architect requirements.

It is expected that a designated operating system user will run all SDL LiveContent

Architect related components.

Note: A designated operating system user is also known as a Service Account.

It is recommended that you do a system reboot to ensure that all installed components

finish their installation.

Establishing a dedicated system user on Windows 2008

The SDL LiveContent Architect components need a dedicated OS user. This user should

belong to the local administrator group.

Before you begin

It is expected that a designated operating system user will run all SDL LiveContent

Architect related components. This separate user allows you to change user settings with

little interaction with the rest of the system.

Note: A designated operating system user is also known as a Service Account.

About this task

ADomain user is required when using Windows Authentication or ADFS as an STS. Ask

your Active Directory system administrator to create a Service account.



Procedure

1. Create the local Infoshare system user:

Note: If you have to configure multiple servers, you can create a domain user andmake the user the local Administrator on each of the target machines as noted here.

a. Click Start > Administrative Tools > Server Manager

b. Open Configuration > Local Users and Groups then select Users.

c. Open the Action menu and select New user.

d. Enter InfoShare as the User name.

e. Enter a Full name and Description

f. Enter a Password. Enter the password again in the Confirm password field.

g. Select User cannot change password and Password never expires.

h. Click Create.

i. Make the InfoShare user a local Administrator by adding the user to the local

(or domain) Administrator group.

Note: This is necessary because Microsoft requires some registry keys to bewrite-enabled for transactions and more. The services, Message Queues,

Indexing and Component Services Server Applications all run within this

user's context.

2. Set the regional options:

a. Login on your system as the InfoShare user to validate the user account.

b. Click Control Panel > Clock, Language and Region.

c. Click Region and Language.

d. In the Region and Language window under the Formats tab, select the

language (or leave the default) in the Format field.

e. Set the following Date and time formats.

Important: The date and time format must be set as described below. If theformat is not in the select list (the list depends on the language selected),

to modify the format, click the appropriate: Additional Settings > Time

and/or Additional Settings > Date.

■ Short date: dd/MM/yyyy

■ Long date: ddddd d MMMM yyyy

■ Short time: HH:mm:ss

■ Long time: HH:mm:ss

Click OK to activate the settings.



3. Allow the InfoShare user to run services (if not done, it can cause service startup

failure):

a. As an administrator, open Start > Administrative Tools > Local Security

Policy on your server.

b. Open Local Policies then click User Rights Assignment.

c. Select Log on as a service click Add User or Group and add the InfoShare

user created above.

d. Click OK to activate the settings.

e. Open the File menu and select Exit to close the window.

Changing the Local Group Policy on Windows 2008

Set the group policy so that Windows 2008 does not forcefully unload the registry.

About this task

A new User Profile Service functionality built into the OS by default forces the unload of

the user profile on Windows 2008 when the user logs off. This results in, for instance, a

COM+ application to stop working on Windows Server 2008 when the identity user logs

off and the COM+ application can no longer read registry keys in the profile of the

identity user. The policy setting Do not forcefully unload the user registry at user

logoff counters the default behavior of Windows 2008. When enabled, Windows 2008

does not forcefully unload the registry and waits until no other processes are using the user

registry before it unloads it.

Procedure

1. As an Administrator user, click Start then in the Run field type gpedit.msc.

Result: A Local Group Policy Editor window displays.

2. Click Local Computer Policy > Computer Configuration > Administrative

Templates > System > User Profiles

3. In the right pane, double-click on Do not forcefully unload the user registry at user

logoff.

4. In the resulting window, click in the radio button Enabled.

5. Click OK.

Result:

Requirements Checklist

Use this checklist to make sure that all the necessary pre-installation requirements are

met before installing SDL LiveContent Architect software.

The noted hardware requirements (HW) are for the supported hardware for this release.



Layer Type Requirement Completed?

DB HW Hardware requirements are

checked and verified as being

supported

DB SW The database engine is one of the

supported versions including the

exact service pack

DB SW SQL Server installation has a

Case Insensitive default collation

App/Web HW Hardware requirements are

checked and verified as being

supported

App/Web Env The designated database user

(isource) has minimal system adm

inistrator rights

App/Web Env The designated app/web service

account for SDL LiveContent

Architect (InfoShare) is a local

administrator and is a domain user

when using ADFS

App/Web Env The designated app/web user

(InfoShare) has the correct

regional options set

(dd/MM/yyyy)

App/Web Env Do not forcefully unload the user

registry at user logoff is enabled

(Windows 2008)

App/Web SW Windows 2008 Release 2 64bit

installed

App/Web SW Web Services IIS/ASP is installed

App/Web SW Microsoft Message Queuing

(MSMQ) is installed

App/Web SW Application Role is installed

App/Web SW Microsoft Xml Parse 4.0 SP2 is

installed

App/Web SW Microsoft .NET Framework 3.5.1

is installed

App/Web SW Microsoft .NET Framework 4.0 is

installed



Layer Type Requirement Completed?

App/Web SW If Oracle is used as RDBMs, the

Oracle Data Access Components

11.2.0.1 is installed

App/Web SW If Oracle is used as RDBMs, the

Oracle Client Configuration is

configured

App/Web SW If publishing to JAVA help files is

chosen, and Java Help 2.0.0.5 is

installed

App/Web SW Java Development Kit 1.6.0_27 is

installed

App/Web SW If publishing to CHM files is

chosen, Microsoft HTML Help

Workshop 1.3 is installed

App/Web SW If publishing to PDF files is

chosen, a XSL-FO renderer such

as Antenna XSL Formatter is

installed

Installer User Requirements

The users who can install SDL LiveContent Architect must have permissions and access

as required.

An administrator user who has authorized access on the machines to be installed can

install the SDL LiveContent Architect software. The user must be able to:

■ logon to the machine and have full access to the file system

■ alter the registry

■ have full access to the Services, Message Queuing, Indexing, Internet InformationServices and Component Services

A database administrator must set up the SDL LiveContent Architect database. The user

must be able to:

■ create a database

■ run scripts to set up the database



Chapter 3

Preparing for the upgrade - backingup the database

You should always make a complete backup of the SDL LiveContent Architect

environment before upgrading so you can restore to the current environment if necessary.

Note:

■ Before beginning the upgrade it is recommended that you warn all users that thesystem will be temporarily unavailable.

■ No updates should be allowed beyond this point in time.

■ You should plan to copy the whole of the SDL LiveContent Architect environment

to a secure destination.

■ The whole of the SDL LiveContent Architect environment includes all SDL

LiveContent Architect websites, SDL LiveContent Architect website components,

the Full Text Collection, the database backup(s), and the SDL LiveContent

Architect registry keys.

■ Identify and plan to backup any custom files and information in the same way.

Backing up the projectThis backup operation makes a copy of everything installed and generated in this project.

About this task

This does a backup of the business components and used configuration and makes a full

copy of:

■ the Full Text Collection

■ all Publish Service, Import Service, Export Service generated data

■ all generated logging

Note: This backup can take a lot of time. You can do an initial clean up of all data thatneeds no backup or do a manual backup of the necessary files and settings.


Procedure

1. Login to the Windows 2008 system as the Administrator user or a user with Adminis

trator privileges (a user in the Administrator group).

2. In Windows Explorer, go to C:\IShCD\yyyymmdd.CD.InfoShare<version_num>\ProjectName.IT\__InstallTool

3. Locate and double-click on InstallTool. exe.

4. Select the backup option.

5. Select the project that you want to backup and a location where you can safely store

everything.

Backup the databaseFollow the procedure to backup the Microsoft SQL Server 2005, Microsoft SQL Server

2008, or Oracle RDBMs 10.2 database based on your current configuration

Note: The complexity of the Oracle backup is much greatger than that of the SQLServer. The the SQL Server algorithm is described by its Windows UI. The Oracle

procedure is explained by command line tools so that it is valid for both a Windows and

UNIX environment).

Backing up Microsoft SQL Server

Follow this procedure to backup your SQLServer.

Procedure


2. Open the Databases folder.

3. Right click on your database

4. Select Tasks > Back Up.

5. Backup type should be Full.

6. Enter a Name for the backup.

It is recommended that you use the format: yyyymmdd.projectname.bak to name thebackup.

7. Ensure that Backup set will expire: After 0 days

8. In the Destination pane at the bottom of the window, click Add.

9. Add a destination folder such as: yyyymmdd.projectname\SQLServer\ Dump.

10. Click Options in the left pane and verify that the information is accurate:

■ Backup to the existing media set.

■ Append to the existing backup set.

Preparing for the upgrade - backing up the database


■ Verify backup when finished.

■ SQLServer 2008 only: Set backup compression: Use the default serversetting

(This field is not available for SQLServer 2005.)

11. Click OK.

Result: The backup of the database starts.

Oracle RDBMs

The description makes use of command line programs so that a person with a mixture of

Windows and UNIX knowledge can follow the procedure on any Oracle hosting machine.




The procedure includes suggestions about how to do the steps. It is out of scope of this

document to give a step-by-step explanation on basic Oracle maintenance. An Oracle

DBA can choose any option desired, as long as an exact restoration of the SDL

LiveContent Architect environment can be made.

Note:

■ The description refers to a Windows environment concerning system variablesand file paths.

■ The default database name is ISH.

Backing up the closed data files

You can make a copy of closed data files. This is a valid option if you are not planning to

change the location of the files, character set or the Oracle version.

Procedure

1. Open a command line window and set the ORACLE_SID and ORACLE_HOME

environment variables. For example, on Windows:

set ORACLE_SID= ISHsetORACLE_HOME=C:\Oracle\Product\<version>\db_1

2. Start SQLPLUS /NOLOG:

SQLPLUS / NOLOG

3. Force a database to close by typing the following. The goal is to do this quickly

enough so that no-one can make a connection and alter the database.



shutdown abortstartup openshutdown normal

Result: All pending connections are closed by force. The startup open checksthe database and the shutdown normal closes all database files.

Exporting the database

A full database export is more difficult but allows you take a version, character set, and

location independent backup.

Procedure

1. Navigatetothefile\Database\Dump\Oracle\export\export.par.

2. Edit the export.par file to ensure the correct tnsnames entry and location of database logand dump file.

3. In a command prompt window, go to the directory where the export.par file islocated and issue the following command:

exp parfile=export. par

Result: A dumpfile is exported.



Chapter 4

UninstallingRemoval of all items of the installed environment is required before starting an upgrade.

About this task

All items which were installed and in the installplan.xml are removed from your system.

Items which are not be removed are:

■ the Full Text Collection

■ all PublishService, ImportService, ExportService generated data

■ all generated logging

■ files which changed after the initial installation (such as configuration files)

Procedure

1. Login to your Windows system as the Administrator user or a user with

Administrator privileges (a user in the Administrator group).

2. In Windows Explorer, go to the location where the previous installation software is

located, or to the CD that was used to install the current environment, to access the

correct version of the tool for uninstalling the software. Go to:

C:\IShCD\yyyymmdd.CD.InfoShare<version_num>\ProjectName.IT\__InstallTool


4. Select the uninstall option.

5. Select the project that you want to remove.


Uninstalling


Chapter 5

Configuring the database serverThe SDL LiveContent Architect database can reside on an SQL or Oracle database server.

Oracle setup is more complex than an SQL server setup. This is because the SQL Server

installation/configuration is explained using a Windows user interface.

Note: If you have the choice and are not an Oracle DBA, we advise that you install onan SQL Server platform.

Microsoft SQL ServerDatabase setup on a Microsoft server requires configuration of the server and creation of

the database.

Configuring Microsoft SQL Server

Database setup is done on the Microsoft SQL server.

Be certain to read the pre-installation notes for SQL Server provided in this

documentation.

The SQL Server installation has to be an AccentSensitive, CaseInsensitive,

Unicode-ready installation.


■ If you are doing a fresh SQL Server installation make sure that in the Databaseengine Collation settings, Accent-sensitive is selected and Case-sensitive is notselected.

■ The typical SDL LiveContent Architect collation is

SQL_Latin1_General_CP1_CI_AS (not the often mistaken collation

Latin1_General_CI_AS). Depending on the SQL Server version, the collation

SQL_Latin1_General_CP1_CI_AS is also displayed as Dictionary order,

caseinsensitive, for use with 1252 Character Set.

■ You can check the collation name by issuing a query in SQLServer ManagementStudio connected to your server.

■ To access the SQL Server Management Studio click Start All

Programs > Microsoft SQL Server > SQL Server Management Studio

■ Click New Query then enter:

select Server Property(’Collation’)

■ Click Execute.

■ Verify that the result shows an Accent-sensitive (AS), Case-insensitive(CI) collation name. For more information refer to Collations in the SQL

Server help files.

Authentication based on named SQL Server login ID and on Windows accounts is

recommended.

■ Check or modify this in SQL Server Management Studio, right-click onServerName then click Properties, select Security in the left pane.

■ In the Server authentication pane on the right, select SQL Server and WindowsAuthentication Mode.

SQL Server Agent is part of the SQL Server software.

■ Check that this Windows Service is set to automatically start upon server reboot.Check Start > Control Panel > System and Security > Administrative Tools

then double-click on Services.

■ Verify that SQL Server Agent start up type is Automatic.




Creating a database

Create a database for the SDL LiveContent Architect data collection.

Procedure


Result: The Microsoft SQL Server Management Studio window displays.

2. Right-click on Databases then click New Database…

3. Enter a database name.

Configuring the database server


4. Click Options in the left pane.

5. In the Collation field, select: SQL_Latin1_General_CP1_CI_AS

6. In the Recovery model field, select: Full

Note: The Full Recovery model uses database backups and transaction log backupsto provide complete protection against media failure. If one or more data files are

damaged, media recovery can restore all committed transactions. In-process

transactions are rolled back. It provides you with the ability to recover the database to

the point of failure or to a specific point in time. To guarantee this degree of

recovery, all operations, including bulk operations such as SELECT INTO, CREATE

INDEX, and bulk loading data, are fully logged. The recovery model may be set to

Simple to avoid a fast growing transaction log files, but note that this reduces the

number of points-in-time for recovery.

7. In the Compatibility level field:



8. Click OK.

9. In the originalMicrosoft SQLServer Management Studio window, open Databases

and right-click on the database you created.

10. Click Properties.

Result: A Database Properties window displays for your database.

11. Click Files in the left pane.

12. Change or ensure the following data in the Database Properties window:

■ In the field, Owner, enter: sa

■ Logical name: dbname_Data (for example InfoShare_Data) where the file

type equals Rows Data. Set File Name to dbname.mdf

■ Logical name dbname_Log (for example InfoShare_Log) where the file type

equals Log. Set File Name to dbname_Log.ldf

13. Click OK.

Removing the database user and schema

To ensure successful creation of a new database user and schema, delete the user and

schema that was created when importing the sample data.

About this task

A database user in SQL Server exists on two levels, as an account on the SQL Server

level and as an account on your database. Depending on the kind of initial database setup

dump you received, you could have problems creating your new database user. Therefore,

you should delete the InfoShare database designated user (by default named isource)

and schema.



Note: The user listed within the created database part is to be removed and not thegeneral SQL Server part listed under Security > Logins.

Procedure

1. In the SQL Server Management Studio window, under Databases, locate and open

the tree under the database you created.

2. Open Security > Schemas.



Note: The isource user may not exist under Schemas. If it does not exist, skip thisand the next step; continue to the step to open Security > Users.


5. Open Security > Users.




Importing data from the SQL dumpfileImport the sample SDL LiveContent Architect database dump to validate the

configuration and for training purposes.

Procedure

1. In the SQL Server Management Studio window, under Databases, right-click on

the database you created.

2. Click Tasks > Restore > Database.

3. In the Restore Database window, select From Device then select the latest available

dump provided on the installation CD in:



Note: If the SQL server 2008 dump is not provided, you can use the SQLserver 2005 dump on the SQL 2008 server.

a. Click the ellipsis button next to the From Device field.

b. Click Add in the resulting Specify Backup window.

c. Locate and select the backup file.



d. Click OK.

e. Verify that the correct file is selected in the Specify Backup window, then

click OK.

4. In the Restore Database window, select Restore next to the database filename in the

lower pane then click Options in the left pane.

5. Select Overwrite the existing database.

6. Click OK.

Result: The database is restored.

7. After restoring the database, use SQL Server Management Studio to check the

recovery model and verify that Full is selected for the Recovery model.

Creating a new database user and schemaAdd a new user to connect to the newly created database.

Procedure

1. On the database server, open the SQL Server Management Studio.

2. In the left pane under the server name open Security.

3. Right-click on Logins then select New Login…

Result: A Login - New window displays.

4. In the Login name field, enter isource.

5. SQL Server Authentication should be selected. Enter a Password and Confirm

password for SQL Server Authentication.

By default the password is isource, however the password may be one of your choice.

Note: If you change the password, SDL is not able to assist you if you do not knowthe password so it is advised to store the password in a secure place.

6. Depending on your local password policy, you can enforce password policy and

password expiration. When both are enabled, keep in mind to change the connect

string of isource at password expiration time.

7. Use the drop down list to select the Default database; select your newly created

database.

No other changes are required for the General information.

8. In the Login - New window, click Server Roles in the left pane.

9. Select (check the boxes next to) public and sysadmin in the right pane.

Result: This allows the SDL LiveContent Architect DatabaseUpgradeTool

(DBUT) to fully execute all necessary tasks to update your database with new

releases. This is strongly advised.

10. In the Login - New window, click User Mapping in the left pane.



11. Select (check the boxes next to) the newly created database in the upper right pane.

12. In the bottom pane, select (check the boxes next to) db_owner and public.

13. In the Login - New window, click Status in the left pane.

14. Verify that Grant is selected for Permission to connect to the database engine and

that Enabled is selected for Login.

15. Click OK.

16. Click File > Exit.

Oracle RDBMsThe installation makes use of the Oracle Database Configuration Assistant (DBCA) and

command line programs to create and set up the database. This allows for anyone with a

mixture of Windows and UNIX knowledge to be able to set up an environment on any

Oracle hosting machine.

The configuration procedure refers to a Windows environment when noting system

variables and file paths.




Note: The default database name is ISH.

Oracle database configuration requirements

The users who can configure Oracle must have permissions and access as required and be

familiar with Oracle and Microsoft environments.

All implicit steps that must be done were considered for inclusion in these procedures.

The procedures were written for administrators who have knowledge of the Oracle and

Microsoft environments.

Please be sure that you satisfy the following before beginning:

■ ADBA role is required for a database migration.

■ A server reboot is required after Oracle installation to make sure that all Oracleenvironment settings are available to you.

■ Settings should be NLSCHARACTERSET=UTF8,NLS_LENGTH_SEMANTICS=CHAR andNLS_NCHAR_CHARACTERSET=AL16UTF16



Also note:

■ Executed actions should be done in the same command window so settings whichare shell specific, for example, ORACLE_SID or ORACLE_HOME areavailable.

■ All paths are examples only. Paths are system specific, so make sure that all filepaths are valid and contain the correct file(s), and beware of read-only flagson files.

■ The default database name is ISH and is used in examples in the procedures.

Changing the SQLNET.AUTHENTICATION_SERVICES

A freshly installed Oracle database sometimes results in ORA-12638 errors. If you are

running a dedicated SDL LiveContent Architect Oracle server, you can resolve problems

by altering the SQLNET.AUTHENTICATION_SERVICES setting.

Note: If you are not running a dedicated SDL LiveContent Architect Oracle server,contact your Oracle DBA.

1. OpenOracle file\network\admin\sqlnet.ora

2. Change the value of parameter SQLNET.AUTHENTICATION_SERVICES to

(none). This setting is instead of (NTS).

Oracle versions configuration

Procedures for configuring Oracle RDBMS 10g and Oracle RDBMS 11g is described.

Refer to the procedure for using the required Oracle RDBMs version 10.2.0.2 (or higher)

or Oracle RDBMs version 11.2.0.1 (or higher).


Oracle 10.2.0.2 or higher is required. The procedure guides a knowledgeable person

through the configuration so that all important steps are completed.


To prepare your environment, you must copy and edit the delivered Oracle 10g files, and

activate the listener service.

About this task

To begin, copy the files delivered on the installation CD.



Procedure

1. Locate the\Database\Dump\Oracle\Oracle102.Admin folder on the installationCD.

Result: The folder contains the ISH Admin folder structure and files such as:

■ pfile\initISH.ora (default pfile)

■ create\crdbs.sql (create the database)

■ create\crtbs.sql (create tablespaces)

2. If it does not exist, create a C:\oracle\ admin directory.

3. Copy the the ISH folder to the C:\oracle\ admin directory.

Configuring the parameters file

Edit the file (PFILE) that contains information about the database parameters.

Procedure

1. Open for editing, the initISH.ora parameters that you copied into C:\oracle\admin\ISH\pfilewhen preparing the system.

2. Define the following in the file:

■ the database identifier

■ the location of the database

■ the database instance

■ directories for the control files

■ directories to store trace and alert files

Note: Refer to the documentation within the file about these parameters.

3. Because Oracle expects the parameters file to be in (on Windows) C:\oracle\product\10.2.0\db_1\databaseor (onUNIX/Linux)$ORACLE_HOME/dbsyoumust create a link.

To do this, create a text file named initISH.ora in C:\oracle\ product\10.2.0\ db_1\ database or $ORACLE_HOME/ dbs and add the following to the file'scontents:

IFILE=C:\oracle\admin\ISH\pfile\initISH.ora

Note: The path in the step above is an example and should reflect your Oraclehome directory.

Configuring the database creation files

Configure the files that are used to create the Oracle database and tablespaces.



Before you begin

The Oracle DBA should edit these files.

Review the steps and sample files below before editing to be sure you have the

information necessary to properly configure the database creation files.

Procedure

1. Open and edit the file used to create the database: C:\oracle\ admin\ ISH\create\ crdbs.sql file. A sample of the file's contents is:

CREATE DATABASE ISHCONTROLFILE REUSEMAXINSTANCES 16MAXLOGFILES 32MAXDATAFILES 128CHARACTER SET UTF8DATAFILE’C:\Oracle\OraData\ISH\sys_ISH.dbf’SIZE 240M REUSE AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCAL

SYSAUX DATAFILE ’C:\Oracle\ OraData\ ISH\ sysaux_ISH.dbf’

SIZE 70M REUSE AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDDEFAULT TEMPORARY TABLESPACE "isrc_temp" TEMPFILE’C:\Oracle\OraData\ISH\temp01.dbf’SIZE 20M REUSE AUTOEXTEND ON NEXT 500K MAXSIZE UNLIMITEDUNDO TABLESPACE "isrc_rollback" DATAFILE ’C:\Oracle\ OraData\ISH\rollback01.dbf’SIZE 100M REUSE AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDLOGFILEGROUP 1 (’C:\Oracle\ OraData\ ISH\ redoISH1.log’) SIZE 32M,GROUP 2 (’C:\Oracle\ OraData\ ISH\ redoISH2.log’) SIZE 32M,GROUP 3 (’C:\Oracle\ OraData\ ISH\ redoISH3.log’) SIZE 32M

2. Open and edit the file used to create the database tables: C:\oracle\ admin\ ISH\create\ crtbs.sql file. Make sure the paths are correct for the datafiles, and resizethe datafiles as noted below:

DATAFILE SIZE

DATA_M1.DBF 32M

DATA_S1.DBF 32M

INDEX_M1.DBF 64M

INDEX_S1.DBF 128M

PAGE_M1.DBF 64M

ROLLBACK01.DBF 128M

TMPDATA1.DBF 64M

SYS_ISH.DBF 256M



3. Optional, if not already specified: Add extra datafiles to your static size files which

increase (auto growth) in size when necessary until they reach your disk limit. If not

specified already, add the datafiles noted below with AUTOEXTEND ON and a

maxsize of 1M.

To TABLESPACE Add DATAFILE

ISRC_DATA_M DATA_M2.DBF

ISRC_DATA_S DATA_S2.DBF

ISRC_INDEX_M INDEX_M2.DBF

ISRC_INDEX_S INDEX_S2.DBF

ISRC_PAGE PAGE_M2.DBF

A sample of the delivered file's contents is:

CREATE TABLESPACE "ISRC_TEMPDATA"DATAFILE ’C:\Oracle\ OraData\ ISH\ Tmpdata1.dbf’ SIZE 10MAUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTO

/CREATE TABLESPACE "ISRC_DATA_S"DATAFILE ’C:\Oracle\ OraData\ ISH\ Data_S1.dbf’ SIZE 20MAUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISRC_DATA_M"DATAFILE ’C:\Oracle\ OraData\ ISH\ Data_M1.dbf’ SIZE 20MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISRC_INDEX_S"DATAFILE ’C:\Oracle\ OraData\ ISH\ Index_S1.dbf’ SIZE 20MAUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISRC_INDEX_M"DATAFILE ’C:\Oracle\ OraData\ ISH\ Index_M1.dbf’ SIZE 20MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISH_DATA_M"



DATAFILE ’C:\Oracle\ OraData\ ISH\ ISH_DATA_M1. dbf’ SIZE 20MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISH_INDEX_M"DATAFILE ’C:\Oracle\ OraData\ ISH\ ISH_INDEX_M1. dbf’ SIZE 20MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/CREATE TABLESPACE "ISRC_PAGE"DATAFILE ’C:\Oracle\ OraData\ ISH\ Page_M1.dbf’ SIZE 50MAUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITEDEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOBLOCKSIZE 16k

/

Editing the tnsnames.ora database connection file

Edit the Oracle configuration file that defines the information for connection to the

database server and database instance for the SDL LiveContent Architect repository.

About this task

The Oracle tnsnames.ora file must be modified on the Oracle database server and on systemsthat communicate with the Oracle database server.

Note: If the Oracle database server and client software was installed on the samesystem, you must edit the tnsnames.ora file under each instance of Oracle_home.

Procedure

1. Login to the server as an administrator user.

2. Open theOracle_home\network\admin\tnsnames.ora file for editing.

If the file does not exist create an empty text document named tnsnames.ora in thedirectory above.

3. Add the following to the file. Make sure that it is left-aligned (that is, no leading

whitespace on the first line)

net_service_name =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)

(HOST = hostname)(PORT = 1521))



)(CONNECT_DATA =

(SERVICE_NAME = service_name)))

where:

■ net_service_name is an alias that is used for a connect descriptor. For example:

ISH.WORLD =

■ hostname is the ip address or name of the database server. For example:

(HOST = devserver01)

or

(HOST = 127. 0.0.1)

■ SID is a combination of the db_name and db_domain values in theC:\oracle\admin\ISH\pfile\PFILE\initISH.orafile.Forexample:

SERVICE_NAME = ISH. ORASERVER. DOMAIN. NAME

where ISH is the db_name value and ORASERVER.DOMAIN.NAME is the

db_domain value in the initISH.ora file.

4. Save and exit the file.




Procedure





For example:







Automatic.








repository.

Before you begin

All commands should be entered in the same command window to ensure that all

necessary environment variables are set throughout the process.

Procedure

1. At a command prompt, set the ORACLE_SID and ORACLE_HOME variables. For

example:

Set ORACLE_SID= ISH

Note: The ORACLE_SID value is the SERVICE NAME value in the tnsnames.orafile. In this example it is ISH.

SetORACLE_HOME=C:\oracle\product\10.2.0\db_1\

Note: The ORACLE_HOME value is the location of the Oracle software. In thisexample it is C:\oracle\product\10.2.0\db_1\.

2. To create the database instance, at the same command prompt where you set the

variables above, as one statement (that is, enter it on a single line) type:

ORADIM -NEW -SID Oracle_SID -STARTMODE AUTO –PFILEOracle_home\database\initISH.ora

where:

■ Oracle_SID is the value you set for the ORACLE_SID in the previous step.

■ Oracle_home is the value you set for ORACLE_HOME in the previous step.

For example:



ORADIM -NEW -SID ISH -STARTMODE AUTO –PFILE C:\oracle\product\10.2.0\db_1\database\initISH.ora

3. Create the new password file by executing the following command as one statement:

ORAPWD FILE=Oracle_home\ database\ pwdISH.ora PASSWORD= CHANGE_ON_INSTALL

where Oracle_home is the value you set for ORACLE_HOME in a previous step. Forexample:

ORAPWDFILE=C:\oracle\product\10.2.0\db_1\database\pwdISH.ora PASSWORD= CHANGE_ON_INSTALL

4. Create the database folder,C:\oracle\ OraData\ ISH. This is the place where the data

is stored.

Result: The directory is required and not created by Oracle. Make sure thatall paths exist.

5. Create the database and data files:

a. Start SQLPLUS /NOLOG from the same command prompt window (where

all variables are set):

SQLPLUS / NOLOG

b. The indented lines below are commands which should be executed in server

manager.

Important: You must make sure that all files are in the correct locations asnoted in the commands. Read through the next sequence and adjust the paths

to match the ones on your system.

Tip: To ensure that all commands are accurately executed, you can paste thecommands below into a text editor, edit the necessary paths for your

environment, then copy each command and paste it at the command prompt to

execute it.

SET TERMOUT ONSET ECHO ONSPOOLC:\oracle\admin\ISH\create\dbadmin1.logCONNECT SYS/ CHANGE_ON_INSTALL AS SYSDBASTARTUP NOMOUNT PFILE=’C:\oracle\ product\ 10.2.0\db_1\database\initISH.ora’@C:\oracle\admin\ISH\create\crdbs.sql@C:\oracle\admin\ISH\create\crtbs.sql



@C:\oracle\product\10.2.0\db_1\rdbms\admin\catalog.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\catexp.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\catblock.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\catproc.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\catoctk.sql;@C:\oracle\product\10.2.0\db_1\rdbms\admin\owminst.plb;@C:\oracle\product\10.2.0\db_1\rdbms\admin\dbmspool.sql@C:\oracle\product\10.2.0\db_1\rdbms\admin\prvtpool.plb@C:\oracle\product\10.2.0\db_1\RDBMS\ADMIN\xaview.sqlDROP public SYNONYM dbms_shared_pool;CREATE public SYNONYM dbms_shared_pool FOR sys. dbms_shared_pool;GRANT execute ON dbms_shared_pool TO public;CONNECT SYSTEM/ MANAGER@C:\oracle\product\10.2.0\db_1\sqlplus\admin\pupbld.sql;@C:\oracle\product\10.2.0\db_1\sqlplus\admin\help\hlpbld.sql helpus.sql;CONNECT SYS/ CHANGE_ON_INSTALL AS SYSDBA@C:\oracle\product\10.2.0\db_1\rdbms\admin\utlrp.sql;SHUTDOWNSTARTUP

SPOOL OFF





Procedure






Set ORACLE_SID=ISH


or






below.


SQLPLUS /NOLOG


are set, type:


Resizing the data files

Enter a short description of your task here (optional).



Before you begin

Enter the prerequisites here (optional).

About this task

Procedure

1. Enter your first step here.

Result: Enter the result of your step here (optional).

Example:

Enter an example that illustrates the current task (optional).

What to do next

Enter the tasks the user should do after finishing this task (optional).

Importing the data


Procedure
















Procedure








Procedure



SQLPLUS / NOLOG




Importing the data


Procedure









2. In thesame\Database\Dump\Oracle\import\ISOURCE.Rows.par file checkthe parameters to do a user to user (ISOURCE to ISOURCE) import of the data from the dmpfile. For example:





The SDL LiveContent Architect database is created using the Oracle Database

Configuration Assistant. Oracle version 11.2.0.1 or higher is required.

When installing with Database Configuration Assistant, SDL LiveContent Architect uses

a template with SPFile and without specification for the NLS_LENGTH_SEMATICS.

The database is created with NLS_LENGTH_SEMATICS = BYTE.

The SDL LiveContent Architect requested setting is NLS_LENGTH_SEMATICS =

CHAR. To correct this, SDL LiveContent Architect recommends executing the

DatabaseUpgradeTool after each creation or update of the Oracle database. The

DatabaseUpgradeTool checks and corrects the NLS_LENGTH_SEMATICS to CHAR

using a statement such as:

alter system set nls_length_semantics= char scope= both;


To prepare your environment for the Oracle configuration, you must first copy the

template file to your server.

About this task

From: \Database\Dump\Oracle\Oracle112.Admin\DBCATemplates\SDL-

Trisoft.InfoShare-Database-Template.dbt

To: C:\Oracle\product\11.2.0\dbhome_1\assistants\dbca\

templates on the server




About this task





Procedure









)(CONNECT_DATA =


where:


ISH.WORLD =



or

(HOST = 127. 0.0.1)











Procedure





For example:





Automatic.








repository. This is the place where the data is stored.

Procedure

1. Create the database folder,C:\oracle\OraData\ ISH.

The directory is required and not created by Oracle. Make sure that all paths exist.

2. Start the Database Configuration Assistant.

3. Click Next.

4. Select Create a Database then click Next.

5. Select the SDL-Trisoft. InfoShare-Database-Template then clickNext.

6. Enter the Global Database Name and SID then click Next.

For example:

■ Global Database Name: ISH.global.SDL.corp

■ SID: ISH

7. Optionally, select the Configure Enterprise Manager and Configure Database

Control for local management then click Next.

Result:



Optionally you are prompted with:

Configuring database with Database Control requires a listener to be configured in the current Oracle home. You need torun Netca to configure a listener before you can proceed.Otherwise you may choose to continue without Database Control configuration

If prompted to do so, add the listener service:

■ Start the Netca Oracle program as the Administrator user

■ Select the default values: Listener configuration – add – LISTENER – port1521)

■ At a command prompt, type lsnrctl start

■ This ensures an OracleOraDb11g_home1TNSListener service exists in theServices Control Panel.

■ At the same command prompt type: lsnrctl reload

■

Go to Start > Programs > Administrative Tools > Services and locate the

OracleOraDb11g_ home1TNSListener service. Make sure that is set to

Automatic then restart it.

Note: If your database and application server are not able to communicatewith each other, it is typically because the two-way communication is blocked

by a firewall or security settings are not matching. Refer to the topic about

security and firewall configuration for more information.

■ Continue with the Database Configuration Assistant wizard.

8. Select either Use Different Administrative Passwords or Use the Same

Administrative Password for All Accounts then enter a Password and Confirm the

password.

This password is requested later. SDL is not able to assist you if you do not know the

password so it is advised to record and store the password in a secure place.

9. Click Next.

10. For storage locations choose either:

■ Use Database File Locations from Template which points to

%ORACLE_BASE%/oradata/DB_UNIQUE_NAME.

Tip: DB_UNIQUE_NAME is a DBCA File Location Variable.

■ Use Common Location for All Database Files where you must specify a path.

For example: C:\Oracle\ OraData

Note: Be sure the path exists!

11. Click Next.



12. Optionally, you can change the recovery configuration in the next window.

13. Click Next.

14. Leave the Database Components as specified by the template; click Next.

15. In the next window, optionally, you can lower the default amount of memory. By

default DBCA detects the amount of memory and takes 80% of this. If you change

this, specify at least 1GB of memory.

Leave the Character Sets, and Connection Mode parameters as specified by the

template.

Note: The template specifies that the character set as UTF8 however, the UI showsAL32UTF8. Know that the Database Configuration Assistant creates the database

with the required correct character set. Explicitly changing the character set to UTF8

is possible by deactivating Show recommended character sets only then choosing

UTF8, but this is unnecessary.

16. Click Next.

17. Leave all settings as specified in the next window and click Next.

18. Click Finish.

19. Click OK.

Result: The database is created.



Procedure






Set ORACLE_SID=ISH


or








below.


SQLPLUS /NOLOG


are set, type:


Importing the data


Procedure
















Procedure








Procedure



SQLPLUS / NOLOG




Oracle Data Access Components 11.2.0.1 32-bit

This is required if you use Oracle RDBMs to host your database.

About this task

The Oracle Data Access Components 11.2.0.1 or ODAC – 32 bit is required if you use

Oracle RDBMs to host your database. It must be installed as the Administrator user. More

information can be found in the Oracle documentation.



The version tested with this version of SDL LiveContent Architect can be retrieved upon

request at SDL. The necessary files are part of the Oracle Database 11g Release 2 Client

(11.2.0.1.0) for Microsoft Windows (32-bit): win32_11gR2_client.zip

The package provides three parts:


■ Oracle Data Provider for .NET 2.0


Procedure

1. In the Select Installation Type window, click Custom.

Note: The Select Installation Type window is displayed after the Welcome screenwhen you launch the Oracle.

2. Click Next.

Result: Select Product Languages window displays.

Preferably leave only English as selected Product Languages.

3. Click Next.

Result: Specify Installation Location window displays.

4. Enter the following in the fields as note.

■ Oracle Base: C:\Oracle

■ SoftwareLocation:C:\Oracle\product\11.2.0\client_1

5. Click Next.

Result: The Available Products Components window displays.

6. Select:

■ Oracle Net



■ Oracle Data Provider for .NET

7. Click Next.

8. Accept the suggested port number by clicking Next.

Make certain that your fire wall settings match this.

9. Addanentry in theC:\Oracle\product\11.2.0\client_1\network\admin\tnsnames.ora file that identifies the location of the Oracle database.

If you do not know how to add entries to this file, contact your Oracle database

administrator.



Configuring the Oracle 11g client on Windows2008

If installing on a Windows 2008 system you must configure it to use the Oracle11g

libraries.

If you install an Oracle11g (client) on your application server to allow the COM+

components access your Oracle Server, for Windows 2008 you must configure the system

so it does not use the default OCI 8 libraries but instead uses the Oracle11g libraries.

You can do this by requesting theMTxOCI_Oracle11g_amd64. reg file online from SDL

LiveContent Architect. The file's contents are shown below.

Place the file in your Oracle home directory then double-click on it.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI]"_Oracle9i_OracleOciLib"="oci.dll""_Oracle10g_OracleOciLib"="oci.dll""OracleOciLib"="oci.dll""_Oracle9i_OracleSqlLib"="orasql9.dll""_Oracle10g_OracleSqlLib"="orasql10.dll""OracleSqlLib"="orasql11.dll""_Oracle9i_OracleXaLib"="oraclient9.dll""_Oracle10g_OracleXaLib"="oraclient10.dll""OracleXaLib"="oraclient11.dll"[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSDTC\MTxOCI]"_Original_OracleOciLib"="oci.dll""OracleOciLib"="oci.dll""_Original_OracleSqlLib"="SQLLib80.dll""OracleSqlLib"="orasql11.dll""_Original_OracleXaLib"="xa80.dll""OracleXaLib"="oraclient11.dll"





Chapter 6

Upgrading the SDL LiveContentArchitect server

You must install and configure the application and web server to use the SDL LiveContent

Architect application and connect to the repository. The SDL LiveContent Architect

server installation is automated however, certain changes and options must be made

before the installation can become operational.

Configuring database connection stringsUse the Microsoft Universal Data Link tool to create and test a connection string.

An SQL Server oriented environment makes use of the standard available Microsoft OLE

DB Provider for SQL Server.

An Oracle oriented environment needs to make use of Oracle Provider for OLE DB.

The introduction of Unicode requires the use of this provider together with the Enhanced

Oracle Services for Microsoft Transaction Server.


Creating and testing the connection for MicrosoftSQL Server

An SQL Server oriented environment makes use of the Microsoft OLE DB Provider for

SQL Server.

Procedure

1. Create a new text document in your installation directory (C:\InfoShare) and name it

connection.udl

Note:

■ Be sure that the file extension is .udl. If required, change your WindowsExplorer settings to recognize the file extension. You have created a UniversalData Link file, which has a wizard-like program associated to createconnection strings.

■ Ensure that the filename was not appended with a .txt filename extension. Iffilename extensions are not visible, modify the Windows Tools > FolderOptions > View and make certain Hide extensions for known file types isnot selected!

2. Start the associated program fromWindows Explorer by double-clicking on

C:\InfoShare\connection.udl.

3. Click on the Provider tab then selectMicrosoft OLE DB Provider for SQL Server.

4. Click Next.

5. Under the Connection tab, in the first field, select or enter the SQL database server

name.

6. In the second field, click in the box for Use a specific username and password.

a. Enter isource in the User name field.

b. Enter the password for the isource user in the Password field.

The default password is isource. If you did not use the default password, be

sure to enter the password used when you created the new user. The password

was specified for the isource user when configuring the Microsoft SQL

server.

c. Check in the box for Allow saving password.

7. In the third field, click in the box for Select the database on the server and specify

the name of the database.

This is the name specified when you created the database. The database name was

specified when configuring the Microsoft SQL server.

8. Test the connection by clicking Test Connection.

Result: If the connection is valid, a message is displayed verifying that theconnection is good.

9. Click OK to acknowledge.

This saves the password plain text in the UDL file. If the connect string does not

contain the password variable, no valid connections can be made with this connection

string.

Upgrading the SDL LiveContent Architect server


Creating and testing the connection for OracleRDBMs

An Oracle oriented environment makes use of Oracle Provider for OLE DB in Oracle

11g.

Before you begin

You must have a valid tnsnames.ora file in place to create and test the connection. If this

has not been done, refer to the procedure for editing the tnsnames.ora database connection

file.

Procedure

1. Create a new text document in your installation directory (C:\InfoShare) and name it

connection.udl

Note:

■ Be sure that the file extension is .udl. If required, change your WindowsExplorer settings to recognize the file extension. You have created a UniversalData Link file, which has a wizard-like program associated to createconnection strings.

■ Ensure that the filename was not appended with a .txt filename extension. Iffilename extensions are not visible, modify the Windows Tools > FolderOptions > View and make certain Hide extensions for known file types isnot selected!

2. Start the associated program by executing the command:

%WINDIR%\SysWOW64\cmd.exe /c START C:\InfoShare\connection.udl

The command window launched from SysWOW64 ensures that the 32-bit database

provider in the wizard screen is found.

3. Click on the Provider tab then select Oracle Provider for OLE DB.

4. Click Next.

5. Under the Connection tab, in the first field, select or enter the data source. For

example: ISH.WORLD.

The data source is the net_service_name entry in the Oracle_home\ network\admin\tnsnames.ora file.

6. In the second field, click in the box for Use a specific username and password.

a. Enter isource in the User name field.

b. Enter the password for the isource user in the Password field.

The default password is isource. If you did not use the default password, be

sure to enter the password used when you created the new user. The password

was specified for the isource user when configuring the Oracle server.

c. Check in the box for Allow saving password.



7. Test the connection by clicking Test Connection.

Result: If the connection is valid, a message is displayed verifying that theconnection is good.

8. Click OK to acknowledge.

Result: This saves the password plain text in the UDL file. If the connectstring does not contain the password variable, no valid connections can be

made with this connection string.




About this task



Procedure









)(CONNECT_DATA =


where:


ISH.WORLD =





or

(HOST = 127. 0.0.1)






Preparing for the server upgradeA complete SDL LiveContent Architect database has to be available to install or upgrade

a SDL LiveContent Architect server.

About this task

Note: The install tool makes no changes to your database.

Procedure

1. Extract the SDL LiveContent Architect archive to a temporary folder on the server.

Note that Windows path depths are limited to 260 characters so it is suggest to extract

the archive to a short directory path such as C:\IShCD\

2. Locate the InputParameters. xml file from the previous installation in the folder withthe name that uses the format:

C:\IShCDs\yyyymmdd.CD.InfoShare.ver.num.ProjectName.IT\__InstallTool\

This is the file that was edited for your current environment and installation.

3. Copy the file to the new installation folder with the name:

C:\IShCDs\yyyymmdd.CD.InfoShare.ver.num.ProjectName.IT\__InstallTool\

Result: This makes accessible to the install tool, the inputparameters.xml filewith the customized information for your environment.

4. Open the file in an ascii editor (for instance, NotePad) and make certain all<currentvalue> items in the file are correct for this installation. For instance, all UDLfile, check paths, and so on are correct and that the resulting file is a well-formed xml file.

If you cannot access an InputParameters. xml file that has been edited for yourenvironment, refer to the information for the InputParameters. xml file to makenecessary edits before upgrading and using the install tool.



Prerequisites for the server installation

Check the prerequisites before using the install tool to ensure a successful installation.

Before using the install tool, be sure that the following prerequisites are satisfied:

■ You are installing on a SDL LiveContent Architect server that has no instances of

SDL LiveContent Architect (or SDL Trisoft) installed. Make certain that any

SDL COM+Applications and all Virtual Directories are removed.

■ You have a designated InfoShare operating system user with the regional optionsand Log OnAs Service configured as specified in the pre-installation tasks forestablishing a dedicated system user (Service Account).

■ The Microsoft Distributed Transaction Timeout settings are specified as noted inthe as specified in the pre-installation tasks.

■ If using STS, obtain and install the certificate before installing SDL LiveContent

Architect.

Enabling https on the IIS website

SDL LiveContent Architect requires that https is enabled on the IIS website that is used

for SDL LiveContent Architect.

Before you begin

Follow this procedure on the main SDL LiveContent Architect server. After installing the

certificate, you must bind the website to https (included in the last step below).

About this task

Before you can enable https on the SDL LiveContent Architect website you must first

install a SSL certificate on the server. There are several ways to request and install a

certificate:

■ You can buy a certificate from a commercial certificate authority, for example,Verisign. These commercial CAs have online how-to help pages that guide youthrough the process of requesting a certificate and installing it.

■ When your company has an internal Certificate Authority, you can requestcertificates yourself, or through your IT staff.

■ Use the Create Domain Certificate in IIS. To do this follow the procedurebelow.

Procedure

1. Request and install the certificate.

a. In Internet Information Services (IIS) Manager, open:

ComputerName > Server Certificates.

b. In the right Actions pane, click Create Domain Certificate.



Result: A Create Certificate window displays.

c. Add the necessary information to the fields in Create Certificate:

■ Common name: Enter the complete domain name of the URL to beused for this SDL LiveContent Architect. For example:techdoccms.sdl.com

■ Organization: enter your company name. For example: SDL

■ Organizational unit: Enter the name of the department that isrequesting the certificate. For example: SDL IT

■ City, State & Country: Enter the city, state & country where thecompany is located.

d. Click Next.

An Online Certificate Authority window displays.



e. Specify Online Certificate Authority that you want to use by clicking Select

to the right of the field.

Note: If the list for Certificate Authority is empty you cannot continue andyou have to ask your IT department for instruction on how to continue.

f. Enter a Friendly Name. The Friendly Name is a more user-friendly name

for the certificate and is shown in several programs such as IIS.

Result:

You should see the requested certificate appearing in the IIS Server

Certificates list and you can now use it.

g. Click Finish .

2. Bind the website to https:

a. Right-click on the IIS Website that is going to be used for SDL LiveContent

Architect.

b. Select Edit Bindings.

c. Click Add.

■ In the Type field select https.

■ In the SSL certificate field select the certificate that you requestedand installed.

d. Click OK.



inputparameters.xml

The inputparameters.xml file stores key parameters that are used by the SDL LiveContent

Architect installer. It is imperative that this file accurately reflects your environment for

the install tool to be successful.

Overview

Note: If using STS, obtain and install the certificate before modifying theinputparameters.xml file.

Each parameter in this configuration file has the following syntax:

<param name="parameter"><currentvalue>value</currentvalue><defaultvalue>example_value</defaultvalue><description>description_of_how_used</description><validate>if_validated</validate>

</param>

The XML elements perform the following functions:

<currentvalue>

Contains the value that is used by the SDL LiveContent Architect installer.

<defaultvalue>

Currently contains a suggested value as an example.

<description>

A description of how the current value of the parameter is used.

<validate>

Whether the value of the parameter is validated. If the element is empty, no validation

takes place. The <validate> values are provided and should not be modified.

Note: If using STS, obtain and install the certificate before modifying theinputparameters.xml file.

Parameters

The parameters in the inputparameters.xml file that you must define for your installation

are described.

Note: To obtain the required connectstring parameter:

■ In a text editor such as Notepad, open the connection.udl file you created in theinstallation directory (C:\InfoShare)

■ Find the line that begins Provider= such as: For Oracle:



Provider=OraOLEDB.Oracle.1;Password=isource-password;Persist Security Info= True;User ID= isource;Data Source=data_source_name

For MSSQL:

Provider=SQLOLEDB.1;Password=isource-password;PersistSecurity Info= True;User ID= isource;Initial Catalog= database;Data Source= server-name

■ Copy the line and paste in the inputparameters. xml file for the connectstringparameter.

osuser

The user name for the designated operating system account.

ospassword

The password for the designated operating system account. This password must be set

to never expire.

projectsuffix

A suffix that specifies the particular instance of SDL LiveContent Architect if you are

installing more than one instance of SDL LiveContent Architect on a server.

connectstring

The connection string for the instance of the database application.

databasetype

The type of database application that is used. The following values are valid:

■ oracle

■ sqlserver

apppath

The root directory for the SDL LiveContent Architect installation.

By default, this is set to C:\InfoShare.

webpath

The root directory for the Web site.

By default, this is set to C:\InfoShare.

datapath

The directory in which the data directory is created. This directory is where all data

exported from SDL LiveContent Architect is stored.

By default, this parameter is set to C:\InfoShare.

workspacepath

The temporary directory that is used to store installation files.

By default, this parameter is set to C:\InfoShare\ _Workspace.



infoshareauthorwebappname

The name for the web client application.

By default, this parameter is set to InfoShareAuthor.

infosharewswebappname

The name for the web services application.

By default, this parameter is set to InfoShareWS.

infosharestswebappname

Specify the name of the SDL LiveContent Architect Secure Token Service (STS) web

site.

Follow the same patterns as with infoshareauthorwebappname andinfosharewswebappname

Note: There is no default value for this parameter.

websitename

The name of the Web Site, in which all virtual directories are created.

By default it is set to Default Web Site.

baseurl

Specify the base URL that is used to access the SDL LiveContent Architect web client

This URL must specify the https:// secure protocol.

The best practice is that the HTTPS binding on IIS has a certificate that matches itsCommon Name with this host name.

localservicehostname

The host name for the local address.

This specifies the hostname with which communication within the SDL LiveContent

Architect box happens.

It can be localhost or the node's machine name.

ps_fo_processor

The fully qualified file name of the XSL-FO processor, for example, C:\ProgramFiles\AntennaHouse\AHFormatterV51\AHFCmd.exe.

ps_htmlhelp_processor

The fully qualified file name of the HTMLHelp processor, for example, C:\ProgramFiles (x86)\HTML Help Workshop\hhc.exe

Note: Do not use environment variables or quotation marks.

ps_java_home

The path to the JAVA HOME directory.




ps_webworks_automap_application

The fully qualified path and filename of WebWorks.


solrlucene_service_port

The port that is used by the SolrLucene service. This port must be unique for each

instance of SDL LiveContent Architect that is installed on a server.

solrlucene_stop_port

The port that is used to stop the SolrLucene service. This port must be unique for each

instance of SDL LiveContent Architect that is installed on a server.

servicecertificatesubjectname

Specify the Common Name (CN) of the subject of the service certificate.

With the typical SDL LiveContent Architect setup, the service certificate is the SSL

certificate of the IIS website where a typical SDL LiveContent Architect setup is going

to be installed.

■ Open Internet Information Services (IIS)Manager > Servername > Server Certificates

■ Right-click on the certificate of the IIS website that is going to be used forSDL LiveContent Architect then click View.

■ Click on the details tab then click on the Subject field. In the bottom pane you

see the details of the subject field.

■ Select the whole value then press CTRL + C on your keyboard to copy it ontothe clipboard.

■ Paste it in the servicecertificatesubjectname/ currentvalue of theinputparameters.xml file.

■ Remove the space characters before and after the equal sign and replace thenew line character with a comma space.

For example, the preceding Subject would be represented as CN=Servername.mycompany.com, OU=My Organizational Unit, O=My Company, L=MyCity, S=My State or Province, C=XX in theservicecertificatesubjectname parameter.

servicecertificatevalidationmode

Specify the validation mode of the service certificate.



Specify the level of validation used to verify the service certificate

(servicecertificatesubjectname):

■ ChainTrust Validates the certificate using a trust chain (it validates the

certificate, the CA(s) and checks if the certificate is not revoked using the

CRL or OCSP).

■ PeerTrust Verifies if the certificate is in the TrustedPeople certificate store of

the computer.

■ PeerOrChainTrust Verifies if the certificate is valid by either a ChainTrust or

PeerTrust validation.

■ None The Certificate is not validated, it is always valid.

issuercertificatethumbprint

Specify the thumbprint of the signing certificate on the configured STS.

(issuerwstrustendpointurl and issuerwsfederationendpointurl)

You can configure SDL LiveContent Architect to either use the SDL LiveContent

Architect STS (aka InfoShareSTS) or use another STS such as Microsoft ADFS 2.0.

Do one of the following depending on if you use SDL LiveContent Architect STS or

ADFS:

SDL LiveContent Architect STS

SDL LiveContent Architect STS uses the same certificate as the one that is used on

IIS Website on which SDL LiveContent Architect is going to be installed. So the

thumbprint of the signing certificate is the one of the IIS website certificate.

■ Open Internet Information Services (IIS) Man-ager > Servername > Server Certificates

■ Right-click on the certificate of the IIS website that is going to be used forSDL LiveContent Architect then click View.

■ Click on the details tab then click on the Thumbprint field.

In the bottom pane you see the details of the Thumbprint field.

■ Select the value then press CTRL + C on your keyboard to copy it onto theclipboard.

■ Paste it in the issuercertificatethumbprint/ currentvalue of theinputparameters.xml file.

■ Change all the letters to uppercase and remove all spaces and controlcharacters.

Tip: It may be prudent to type everything over so you are sure you do not

miss a control character.



ADFS 2.0

Note: If you do not have access to the ADFS server, ask someone who has access to

obtain the thumbprint of the token signing certificates.

■ Open AD FS 2.0 Management > Service > Certificates then right-click on

the Primary Token- signing certificate and choose View certificate.

■ Click on the details tab then select the Thumbprint field.

■ Select the value and press CTRL + C on your keyboard to copy it on theclipboard.

■ Paste it in the issuercertificatethumbprint/ currentvalue of theinputparameters. xml file.

■ change all the letters to uppercase and remove all spaces and controlcharacters.

Tip: It may be prudent to type everything over so you are sure you do not

miss a control character.

Note: For example, if the initial Thumbprint value was formatted such as:

" e2 9e 9c dd 03 cb 20 66 52 30 e3 8a 05 8a 68 d6 a4 a5 2a bf"

You would specify this value for the issuercertificatethumbprint parameter

as:

"E29E9CDD03CB20665230E38A058A68D6A4A52ABF"

issuercertificatevalidationmode

Specify the validation mode of the issuer certificate.

Specify the level of validation used to verify the issuer certificate

(issuercertificatethumbprint):

■ ChainTrust Validates the certificate using a trust chain (it validates the

certificate, the CA(s) and checks if the certificate is not revoked using the

CRL or OCSP).

■ PeerTrust Verifies if the certificate is in the TrustedPeople certificate store of

the computer

■ PeerOrChainTrust Verifies if the certificate is valid by either a ChainTrust or

PeerTrust validation.

■ None The Certificate is not validated, it is always valid.

issuerwstrustbindingtype

Specify the binding type for the issuerwsfederationendpointurl parameter.

Based on the authentication mode supported by the server specified in theissuerwstrustendpointurl parameter, specify one of the following values:

■ When authenticating with SDL LiveContent Architect STS, specify

UserNameMixed. This value is specified when username/password

authentication is expected.

■ When authenticating with AD FS 2.0 STS, specify WindowsMixed This value

is specified when Windows authentication is expected.



Note:When WindowsMixed is specified, values specified for theissueractorusername and issueractorpassword parameters areignored.

■ When authenticating with some other STS, specify the value based on therequirements for that STS and IDP (ID (identity) Provider).

issueractorusername

When delegating, specify the username of the actor.

■ When authenticating with SDL LiveContent Architect STS, specifyInfoShareActor.

■ When authenticating with AD FS 2.0 STS, leave this field empty.

■ When authenticating with some other STS, specify the value based on therequirements for that STS and IDP.

issueractorpassword

When delegating, specify the password of the actor.

■ When authenticating with SDL LiveContent Architect STS, specify the

password defined for the InfoShareActor user.

■ When authenticating with AD FS 2.0 STS, leave this field empty.


issuerwstrustendpointurl

Specify the endpoint of the STS for the Active Profile.

■ When authenticating with SDL LiveContent Architect STS, specify:baseurl/infosharestswebappname/issue/wstrust/mixed/username

where baseurl and infosharestswebappname are the values specified forthe baseurl and infosharestswebappname parameters.

■ When authenticating with AD FS 2.0 STS, specify: https://adfshost/adfs/services/trust/13/windowsmixed andmake sure that thisADFSendpoint is enabled. To do this:

■ Open AD FS 2.0 Management

■ Go to AD FS 2.0 > Service > Endpoints.

■ Makecertain that /adfs/ serices/ trust/ 13/windowsmixed is enabled.




issuerwsfederationendpointurl

Specify the endpoint of the STS for the Passive Profile.

■ When authenticating with SDLLiveContentArchitect STS, specify: baseurl/infosharestswebappname/wsissue/wsfed

where baseurl and infosharestswebappname are the values specified forthe baseurl and infosharestswebappname parameters.

■ When authenticating with AD FS 2.0 STS, specify: https://adfshost/adfs/ls/


issuerwstrustmexurl

This is the metadata address (Mex) of the STS for the active profile. It is used when

generating proxy classes. Example:

InfoShareSTS: baseurl/infosharestswebappname/issue/wstrust/mex

ADFS: https://adfshost/adfs/services/trust/mex

Other: Value based on specific STS

serviceusername

Specify the username of the service user inside the SDL LiveContent Architect user

repository. The service user is required for the “translation builder” on page 112.

servicepassword

Specify the password of the service user defined in the SDL LiveContent Architect

user repository

Executing the InstallToolUse the SDL LiveContent Architect InstallTool to install and merge all standard and

customer specific project files.

Procedure

1. Login to your Windows system as a SDL LiveContent Architect user with the

Administrator user role.

2. In Windows Explorer, go toC:\IShCD\yyyymmdd.CD.InfoShare<version_num>\ProjectName.IT\__InstallTool


4. Select the Install option by entering the number 2.

5. Hit enter to respond to all questions; the default options should be sufficient.

Result:

All standard and customer specific project files are merged and installed. All required

services are up and running (the Crawler, SolrLucene, IISAdmin, W3SVC).



Enabling network transactionsThe Microsoft Distributed Transaction Coordinator must allow network transactions. This

must be done on all SDL LiveContent Architect servers; application, database, and batch

servers.

About this task

By default, the security configuration for the Microsoft Distributed Transaction

Coordinator is set to not allow network transactions. To enable network transactions:

Procedure

1. Login to the system as the administrator user or a user with administrative privileges

(a user in the administrator group).

2. Click Start > Administrative tools > Component services.

3. In the left pane open Component Services > Computers > My

Computer > Distributed Transaction Coordinator.

4. Right-click on Local DTC and select Properties.

5. Click on the Security tab in the Local DTC Properties window.

6. The following should be checked (others should not be checked):

■ Network DTC

■ Allow Remote Clients

■ Allow Inbound

■ Allow Outbound

■ NoAuthentication Required

■ Enable XATransactions

■ Enable SNA LU 6.2 Transactions

■ The DTC Login Account, Account field should read: NTAuthority\NetworkService

7. If you made changes, click Apply.

If no changes were made, the Apply button is inactive. Continue to the next step.

8. Click OK.



Verifying the server after installingA basic list of what you must do to ensure that your SDL LiveContent Architect

environment works within parameters.

Procedure

1. Open theconfiguration file\Author\Configuration\InfoShareConfig.xmlina text editor.

2. This file should be accurate and need no edits however, the file binds background

tasks to batch servers and also includes possible options for the handlers, so be sure to

verify:

■ All file and folders paths are valid.

■ All Queue paths contain valid machine names so that asynchronous requestcan be forwarded to other designated servers.

■ All URLs are valid and accessible by the designated user.



Chapter 7

Post upgrade tasksAfter you complete the upgrade of your SDL LiveContent Architect server, you should

complete a number of post-installation tasks. The post-installation tasks help you to verify

the installation and configure the components that you have just installed.

Completing the database configurationThe DBUT tool, for all supported database engines, does an overall verification of the

database and updates database objects such as views, indexes, packages and stored

procedures and modifies metadata structures

Before you begin

■ SystemAdministrator rights for the isource database user.

■ An available and complete SDL LiveContent Architect database (up and running).

■ An available, full and correctly installed SDL LiveContent Architect server. The

installation ensures that the upgrade files and connections are in place to allow a

successful upgrade.

■ Exclusive access to the SDL LiveContent Architect database for the

DatabaseUpgradeTool. If necessary, stop all components and services, especially

InfoShare Crawler on all servers.

Procedure

1. Login to the server as a Windows user with the Administrator user role.

2. In Windows Explorer, in the SDL LiveContent Architect installation directory, open:\App\Setup\DBUgradeTool\

3. Locate and double-click on DBUpgradeTool. exe

4. Optional, for ADFS only

Use the Database Upgrade Tool to configure the FishExternalID of the administrator

user with a value such as domain\ username, for the user who is to login in thesystem as the administrator. To do this:

■ Run Database Upgrade Tool, choose option 1: Maintenance

■ Choose option 8: Append an user's externalid for initial STS logon

■ Choose installation then complete the appropriate value for the SDL

LiveContent Architect admin user.


5. Select the DatabaseUpgrade option.

6. Hit the Enter key to respond to all questions; the default options are sufficient for the

following questions:

■ Select your recently installed project (thereby selecting the database locationand user, upgrade script paths, version and so on).

■ Default for the application.

■ Enter a valid InfoShare administrator user account.

Result: The result is an upgrade from an older or same version to theinstalled version when applicable.

Troubleshooting DatabaseUpgradeTool

If the DBUT suddenly dies, it results in a hanging database upgrade logged in to the

database. All other attempts to upgrade will fail since only one upgrade process is

permitted to run at a time.

To force an undo of a hanging update, execute DBUT then select

Maintenance > Terminate and your current project.

If you see errors when executing the tool contact SDL LiveContent Architect or

preferably, use the SDL LiveContent Architect Issue Tracking system, or email

[email protected]

The information you must provide when contacting SDL LiveContent Architect for

support is:

■ A screenshot of the failed execution of DatabaseUpgradeTool

■ Thelogfile:\App\Setup\DBUpgradeTool\DBUpgradeTool.log

Adding serverRuntime configurationAdd serverRuntime configuration to the servers applicationHost.config file to ensure that

the compression/caching of files work properly.

About this task

Follow this procedure after running the Database Upgrade (DBUT) tool.

Procedure

1. Open Internet Information Services (IIS) Manager -

Computername > Sites > Live Content Architect web site

> Configuration Editor.

2. On the top of the Configuration Editor open the select list next to From and select

ApplicationHost.Config (location path = Live Content Architect web

site).

Post upgrade tasks


3. In the Section: menu on the left side:

■ select system.webServer/ serverRuntime

■ set to: frequentHitThreshold=1 frequentHitTimePeriod=23:59:59

4. Click Apply in the right pane.

The Administrator setupNeeds to be done only if you did not receive a fully prepared database dump-backup file,

otherwise this is done and configured.

Note:

■ This is the responsibility of a functional administrator not of a technicaladministrator.

■ The configurations handled in this section are all managed through the Authorwebsite Settings tab.

■ The delivered configuration files are available in web\ Author\ EnterViaUI or,for your customer specific files, in \ CustomerSpecificFiles\ Websites\Author\EnterViaUI

Completing the Administrator setup

Needs to be done only if you did not receive a fully prepared database dump-backup file,

otherwise this is done and configured.

About this task

Procedure

1. Login to the SDL LiveContent Architect web client as an administrator user.

2. Select the Settings tab.

3. To configure each of the following:

a. Go to the place as noted in the To configure, go to column in the table below,

under the Settings tab.

b. Delete the contents of the textbox.

c. Copy the contents of the file indicated in the Copy from column to the

textbox. When you copy, ensure that there are no leading empty lines.

The files are located on the server in the SDL LiveContent Architect_home

directoryin\Web\Author\EnterViaUI

Post upgrade tasks


To configure, go to: Copy the contentsfrom:

On the top menu bar,click:

XML Inbox Settings Admin.XMLInbox

Configuration.xml

Save

XML Plugin Settings Admin.XMLPlugin

Config.xml

Save

XML Status Settings Admin.XMLStatus

Configuration.xml

Save

XMLTranslation

Settings

Admin.

XMLTranslationconfiguration.

xml

Save

XMLChangeTracker

Settings

Admin.XMLChange

TrackerConfig.xml

Save

Adding the relying party entries for webUIand WCF Services

After the SDL LiveContent Architect installation you have to create the Relying Party

Trust for the website and the WCF services on the ADFS 2.0 Server. This is required to

allow logins to SDL LiveContent Architect.

About this task

These post-installation steps have to be done when you are using ADFS as STS. If you

are using InfoShareSTS as STS do not follow these steps.

Doing this manually can be error prone, therefore SDL provides you a powershell script

that creates the Relying Party Trust and does the configuration. To execute the script do

the following:

Post upgrade tasks


Procedure

1. The ADFS server needs the service certifcate that is used by the SDL LiveContent

Architect WCF Services.

This is the same value as the certificate whose subjectname is used in the

inputparameters parameter servicecertificatesubjectname. With the typical SDL

LiveContent Architect setup, this WCF Service certificate is the same as the IIS

Website Certificate for SSL.

a. Open Internet Information Services (IIS)

Manager > Servername > Server Certificates.

b. Right-click on the certificate of the IIS website that is going to be used for

SDL LiveContent Architect then click View.

c. Click on the Details tab then click Copy to File and export the certificate to

the file system (private key not necessary).

2. Copy the PowerShell scripts which are created in the directory \ InfoShare\ App\Setup\STS\ADFS\Scripts\ scripts to a temporary directory on theADFS 2.0 servertogether with the certificate you exported in the previous step.

3. Login into the ADFS Server and open a administrative PowerShell command line;

right-click on the PowerShell shortcut and choose Run as administrator.

4. Set the powershell execution policy to Unrestricted.

Note: The scripts provided are not signed because they are generated during theSDL LiveContent Architect installation. To execute unsigned scripts in powershell

you must set the execution policy to Unrestricted.

■ To check if powershell's execution policy is already set to unrestricted, executethe command:

Get-ExecutionPolicy

■ If the output of this command shows something other than Unrestricted,execute the command:

Set-ExecutionPolicy Unrestricted

5. Change the working directory of the command prompt by executing the command:

cd \path\to\ADFS\Scripts

6. Before running the script, load the ADFS PowerShell module by issuing the

command:

Add-PSSnapin Microsoft.Adfs.PowerShell

7. Execute the command:

.\SDL.LiveContent.Architect-ADFSv2.0-RP-Install.ps1 "\path\to\IISwebserver\cerFile.cer"

Result: Now if you open AD FS 2.0 Management you should see two new

Relying Party entries with the baseurls you use for the SDL LiveContent

Architect instance.

Post upgrade tasks


Removing the relying party entries for webUI andWCF Services

If you want to remove the Relying Party entries, for instance because SDL LiveContent

Architect is moved to another server or the url has changed, follow the steps below.

Procedure

1. Check if the Uninstall script for the Relying Party entries is on the ADFS server. If

not, copy it from the SDL LiveContent Architect application server directory

\InfoShare\App\Setup\STS\ADFS\Scripts\.

2. Login into the ADFS Server and open a administrative PowerShell command line;

right-click on the PowerShell shortcut and choose Run as administrator.

3. Before running the script, load the ADFS PowerShell module by issuing the

command:

Add-PSSnapin Microsoft.Adfs.PowerShell

4. Execute the command:

.\SDL.LiveContent.Architect-ADFSv2.0-RP-UnInstall.ps1

Result: Now if you open AD FS 2.0 Management you should see that the twoRelying Party entries are removed.

Installing the SDL LiveContent Createlicense file

After completing the SDL LiveContent Architect installation, install the SDL LiveContent

Create license file (which is obtained from SDL Technical Services) before you to gain

access to SDL LiveContent Create.

Note: SDL LiveContent Create is installed automatically when you install SDLLiveContent Architect.

You must copy the SDL LiveContent Create license file into the installation directory on

the SDL LiveContent Architect Web server. Typically, this location is:

C:\Infoshare\Web\Author\ASP\Editors\Xopus\license\

Post upgrade tasks


Translation management configurationThe configuration files for translation management are described. The files reside on the

SDL LiveContent Architect server.

You can modify the files and parameters noted below to configure or customize translation

management for your needs.

Application configuration for TranslationBuilder

Location: \Infoshare\App\TranslationBuilder\Bin\

Filename: translationbuilder.exe.config

■ DefaultLogLocation - the folder where the log files are created. This value isinitialized from install parameters.

■ MaxObjectsInOnePushTranslation - maximum number of objects in a singlepush translation. The default value is 1000.

■ MaxTranslationJobItemsCreatedInOneCall - maximum number of itemscreated in a single transaction. The default value is 10000.

■ DeleteJobsAfterHours - number of hours after which the completed/cancelledjob is deleted. Default value is 2160.

■ JobProcessingTimeoutMinutes - number of minutes that job can be processedby a single step without updating the job lease before it is considered dead.Default value is 60.

■ Username - the name of the user to access SDL LiveContent Architect. This

value is initialized from install parameters

■ Password - the password of the user to access SDL LiveContent Architect.

This value is initialized from install parameters.

■ JobPollingIntervalSeconds - number of seconds that the jobs are polled forprocessing. Default value is 300.

■ PendingJobPollingIntervalSeconds - number of seconds the jobs that arepending the push translations are polled for processing. Default value is 900.

Application configuration for TranslationOrganizer

Location: \Infoshare\App\TranslationOrganizer\Bin\

Filename: TranslationOrganizer.exe.config

Note:Most parameters have default values (as noted) however, if using SDLWorldServer, take note of the values that must be set manually ; they are highlighted

in bold type below.

■ DefaultLogLocation- the folder where the log files will be created. This valueis initialized from install parameters.

■ WorldServerUri - the base URI for WorldServer WS. This value has to be setmanually. If you are not configuring for use with SDLWorldServer, leave

this blank.

■ WorldServerUserName - the user name to access WorldServer WS. Thisvalue has to be set manually. If you are not configuring for use with SDL

WorldServer, leave this blank.

Post upgrade tasks


■ WorldServerPassword - the password to access WorldServer WS. This valuehas to be set manually. If you are not configuring for use with SDL

WorldServer, leave this blank.

■ DumpFolder - the folder where the temporary files are created. This value isinitialized from install parameters.

■ ExternalJobMaxTotalUncompressedSizeBytes - max total size of the singletranslation job. Default value is 5242880.

■ MaxTranslationJobItemsUpdatedInOneCall - max number of items updated ina single transaction. Default value is 100.

■ JobPollingIntervalSeconds - number of seconds that the jobs are polled forprocessing. Default value is 300.

■ PendingJobPollingIntervalSeconds - number of seconds the jobs that arepending translation are polled for processing. Default value is 900.

■ SystemTaskIntervalSeconds - the minimal interval that system tasks (forexample, template synchronisation) are run. Default value is 600.

■ AttemptsBeforeFailOnRetrieval - number of attempts the update of singlecontent object fails before the job is moved to failed status.

■ RetriesOnTimeout - number of times the single external call can fail and beretried before the job is moved to failed status. Default value is 3.

■ UpdateLeasedByPerNumberOfItems - number of items that have to beupdated before the translation job is updated. Default value is 100.

■

■ Language mappings for SDLWorldServer:

<LanguageMappings><Mappings><add Trisoft Language="en" World Server LocaleId="1145"/><add Trisoft Language="fr" World Server LocaleId="1146"/><add Trisoft Language="nl" World Server LocaleId="1147"/><add Trisoft Language="fo" World Server LocaleId="1161"/>

</Mappings></LanguageMappings>

Integration requirements for SDL LiveContentArchitect and SDL WorldServer

The following are items that will help you better understand the integration of SDL

LiveContent Architect and SDLWorldServer and considerations when configuring

translation and workflow.

Post upgrade tasks


SDL LiveContent Architect

Required for SDL LiveContent Architect integration:

■ Languages are defined as described for source and pivot languages (see relatedtopic). For example:

The following example defines a source language of English with target languages

for German, Spanish, French, Italian and Chinese. The second group indicates

that Chinese can be used as source language (pivot) for translating to Japanese and

Korean.

<GenerationScheme><FromLanguage ref= "en">

<ToLanguage ref="de"/><ToLanguage ref="es"/><ToLanguage ref="fr"/><ToLanguage ref="it"/><ToLanguage ref="zh"/>

</FromLanguage><FromLanguage ref= "zh">

<ToLanguage ref="ja"/><ToLanguage ref="ko"/>

</FromLanguage></GenerationScheme>

■ Translation templates come from SDLWorldServer and are automatically pushed

to SDL LiveContent Architect by TranslationOrganizer.

■ SDL LiveContent Architect uses UTF-16 for the content.

■ Workflow: Ready for translation > In Translation > Translated; these statustransitions should be configured for the TRANSLATORSERVICE role.

■ For TRANSLATORSERVICE, the user must have the roleTRANSLATORSERVICE.

Note: TranslationBuilder starts automatically. TranslationOrganizer has to beconfigured before the initial (first) start. Start TranslationOrganizer manually or change

it to start automatically later using the Services option in the Control Panel. (The

WorldServer URI, login and password is required.) The services are:

■ Trisoft InfoShare TranslationBuilder

■ Trisoft InfoShare TranslationOrganizer

Defining and configuring the TRANSLATORSERIVCE role and the status transition

are described in: Configuring the translation builder.

SDL WorldServer

Required for SDLWorldServer integration:

Post upgrade tasks


■ A dedicated user in SDLWorldServer: This is the user that is used by Translation

Organizer to logon to SDLWorldServer. This is the parameter

WorldServerUserName in the configuration file.

■ SDL LiveContent Architect mount configured to use UTF-16: Refer to the SDL

WorldServer manuals for the further details.

■ Locales, Workflows, Project Types, whatever is required by WorldServer to gothrough the translation process: Refer to the SDL WorldServer manuals for the

further details.

■ The last step in a workflow should be Save step. Refer to the SDLWorldServer

manuals for the further details about how to configure the workflow in SDL

WorldServer. For example:

■ Asset path normalizer: This is optional custom component that can beimplemented separately and installed in SDLWorldServer to force SDL

WorldServer TM to consider the file name when doing match. Refer to the SDL

WorldServer manuals for the further details.

Configuring the translation builder

Follow these steps to configure the translation builder including adding the

TRANSLATORSERVICE role, creating a user ServiceUser, and adding the status

transitions.

Procedure

1. Create a TRANSLATORSERVICE role:

a. In the web client, click the Settings tab.

b. Click User Roles in the left pane.

c. Click New in the toolbar in the right pane to display the User Role Properties

window.

d. In the User Role Properties window:

■ Enter TRANSLATORSERVICE in the Name field

■ Enter TRANSLATORSERVICE has to be uppercase in theDescription field

■ Ensure that the checkbox next to Active is checked.

Post upgrade tasks


e. Click OK.

2. Create a user ServiceUser with user role TRANSLATORSERVICE:


b. Click Users in the left pane.

c. Click New in the toolbar in the right pane to display the User Properties

window.

d. In the User Properties window:

■ Enter ServiceUser in the User Name field

■ Enter the Language from the select menu.

■ In the Roles field, select TRANSLATORSERVICE, Translator, andAdministrator from the select menu.

■ Select the User Groups for this user from the select menu.

■ Select Internal in the Type field.

■ Enter Domain\ ServiceUser in the External Id field.

Note: This ServiceUser needs to be a user which is created withinthe domain and has permission to run the service'Translationorganizer'. It can be any name on the domain,ServiceUser is only an example.

■ Ensure that the checkbox next to Active is checked.

■ Click OK.

3. Add status transitions:


b. Click Status Transitions in the left pane.

c. Click Add in the bottom right pane to display the Add Status Transitions

window.

d. In the Add Status Transitions window, add the following transitions:

From Status To Status User Role

To be translated In translation TRANSLATORSERV

ICE

In translation Translated TRANSLATORSERV

ICE

Post upgrade tasks


Verifying URLsIf your environment includes reverse proxy servers, after you install SDL LiveContent

Architect, you need to check that certain URLs are accessible.

Procedure

1. Using Windows Internet Explorer, ensure that you can reach the following URLs:

■ BaseURL/InfoShareWS/Application.asmx?wsdl

■ BaseURL/InfoShareWS/Application.asmx?disco

where BaseURL is the value specified for the baseurl parameter, and InfoShareWS isthe value specified for the infosharewswebappname parameter. These parameters are setin the inputparameter. xml file that is used by the SDLLiveContentArchitect

installer.

2. If you cannot access the URLs, verify that the reverse proxy servers are correctly

configured. See the documentation for the reverse proxy servers.

Enabling network transactionsThe Microsoft Distributed Transaction Coordinator must allow network transactions. This


servers.

About this task



Procedure









■ Network DTC


■ Allow Inbound

■ Allow Outbound



Post upgrade tasks






8. Click OK.

Verifying the installationFollow these procedures to test and verify the critical parts of the new SDL LiveContent

Architect installation.

About this task

In general the following should never result in an error and cause no harm on a production

system. Testing more complex setups, such as the batch servers is out-of-scope.

Procedure

1. Log in into the SDL LiveContent Architect Web client as an existing user.

For example, go to http://servername/InfoShareAuthor and login using an existinglogin name and password, or the admin name and password.

2. Test the inbox by selecting the Inbox tab then select one of the inbox tabs in the left

pane.

Result: Test is successful if the inbox is displayed in the right pane in a tableformat.

3. Create a folder in the repository:

a. Select the Repository tab.

b. Create a folder by clicking the New Folder icon in the upper left pane.

c. Enter a name.

d. Click Ok.

Result:

Test is successful if the folder is created (shown in the left pane). Remove the folder

after verifying using the Delete Folder button in the upper left pane.

4. Test publishing; if a publication is not available, skip this test.

a. Select the Repository tab.

b. Locate a publication (traverse the left pane) and select the publication (in the

right pane).

c. Select an output type in the bottom pane.

Post upgrade tasks


d. Click Publish.

Result: A confirmation window is displayed.

e. Click OK in the confirmation window.

The publication output status (bottom right pane of the search window)

changes to Queued.

Result: Test is successful if the output status changes to Draft; refresh theview to confirm that the status changes to Draft.

5. Execute a full text search:

a. Select the Search tab.

b. Enter a term in the Search term field.

Be sure to enter a word that you know exists in your topics. For example,

enter the search word: the.

c. Click Search.

Result: Test is successful if search results are displayed in the right pane.

6. Verify web services, synchronization, and network availability by starting the Client

Tools such as Publication Manager, Condition Manager or Authoring Bridge.

Result:

Test is successful if you can view the repository through the client tools and can view

or preview a topic in the repository.

7. Verify requested customizations to your system such as PDF stylesheets, extra

metadata, or extra development for integration with other systems (such as SDL-TMS,

PLMs, SingleSignOns).

Ask your SDL LiveContent Architect administrator or documentation manager what

customizations, if any, were requested.

Creating an account and connecting to therepository

Before you can use SDL LiveContent Architect you must create a user account and

configure the connection to the repository.

Before you begin

You need the following information to create the account and connect to the repository:

■ Name of the SDL LiveContent Architect application server

■ URL of the SDL LiveContent Architect web services. For example:http://example.com/InfoShareWS/

■ URL of the SDL LiveContent Architect web client.

Procedure

1. Perform one of the following actions:

Post upgrade tasks


Application Action

Publication Manager Click Tools > Accounts.

XML authoring tool Click SDLTrisoft > Accounts.

Result: The repository window is displayed.

2. Click Add.

3. Enter an Account Name and the URL of the SDL LiveContent ArchitectWeb

Service.

4. Click Next.

5. If necessary, select the Authentication Method.

6. Enter the username and password.

Check Remember password if you do not want to enter the information each time

you use the application.

7. Click Next.

Result: SDL LiveContent Architect validates the account and synchronizes

files.

Running a client tool

When started, the client tools verify availability of the synchronization website and web

services.

Before you begin

■ A desktop client workstation must be installed with the client tools. If not done,refer to the section for installing desktop clients.

■ The client tool must be configured with a user login and account.

■ To fully test the client, the database should contain data.

Procedure

1. If necesssary, create an account and connection to the repository.

2. Start a client tool such as Publication Manager, Condition Manager or Authoring

Bridge from the Start menu or desktop shortcut.

Result:

If you can view and access the repository through the client tool, and can view or

preview a topic in the repository then web services, synchronization, and network

availability have been successfully verified.

Post upgrade tasks


Rebuilding the full text indexYou can rebuild the full text index when, or if it is no longer synchronized with the

current database.

Before you begin

■ You must be a member of the system administration user group.

■ You must have full access to the application server.

■ The crawler service must be running.

Note: It is recommended that you rebuild the index outside regular business hours asthe initialization uses database resources. In addition, the index may take a while to

rebuild depending on the size of the repository.

Procedure

1. On the application server, open the \ InfoShare\ App<projectsuffix>\Crawler\Configuration folder.

2. Execute the StartDataFolderCleanup. bat file to remove the existing index.

3. Execute the StartReindex. bat file to rebuild it based on the exiting repository andproject.

Validation XML configuration filesAs part of the introduction of the Settings API 2.5, a schema was made for all

configuration XML files.

■ Configuration files received a version number

<InfoShareStatesversion="1.0">...</InfoShareStates>

■ Configuration files are validated against this schema when they are submittedthrough the user interface (UI). The rest of the application assumes that theconfiguration files in the database are valid.

Resubmit the legacy configuration XML files using the Web Client, Settings tab. The

configuration file is validated and some corrections are made. For example, a @version

attribute with the value, 1.0 is added. If there are validation errors when resubmitting the

configuration files, remove all statuses in the status definitions with value "Not found

as LOV Value".

<Status Elm="..." value="Not found as LOV Value"/>

Post upgrade tasks


How-to references for advanced usersAdvanced procedures for configuring the system for administrators who have had SDL

LiveContent Architect training are described.

Adding templates to the repository

You can add map, topic, graphic, or publication templates to your repository and make

them available to users when creating new objects.

When working in SDL LiveContent Architect you can create new objects by clicking the

New button in your editor or by creating a reference in Publication Manager. When

creating a new object, the Select Template window displays with a list of available

templates. The templates that are listed, are located in the repository under

System > Editor templates.

Adding the bookmap template

You can add the bookmap template to the SDL LiveContent Architect repository for users

to apply when creating a bookmap.

Before you begin


■ You must have permission to edit and store objects in the SDL LiveContentArchitect repository.

Procedure

1. Login to the SDL LiveContent Architect web client.

2. To add a value to the LOV:

a. Select the Settings tab.

b. Select Lists of Values (LOV) in the left pane.

c. From the Available List of Values, selectMaster type.

d. Click Get Values.

e. Click Add.

f. In the Add Value window add the name of the template in the Name field.

For example, enter Book Map.

g. Optionally, add a Description which explains the proper use of the template.

h. Click OK.

3. Create the BookMap template:

a. In the SDL LiveContent Architect web, select the Repository tab.

b. Open System > Editor template then selectMaps.

c. Click the New icon in the top right pane.

Post upgrade tasks


d. Enter the Bookmap in the Title field and select Bookmap from the list in the

Content Type field.

e. Click Next.

f. Click Next in the Add Master Document Version window.

g. Click Browse next to the File field in the Add Master Document Language

window.

h. Select the \InfoShare\Web\Author\EnterViaUI\System\EditorTemplates\ Maps\Bookmap.dita file.

The file is located on your SDL LiveContent Architect application server. If

you are on a client system, copy the file locally so you can select it.

4. Release the Bookmap template so users can select it.


b. Open System > Editor template then selectMaps.

c. Select the Bookmap in the upper right pane.

d. Select the version and language in the bottom right pane.

e. Click Properties from the menu on the bottom right.

f. In theMaster Document Languages Properties window, select Released

from the Status list.

g. ClickModify.

Adding a topic template

You can add a topic template to the SDL LiveContent Architect repository for users to

apply when creating topics.

Before you begin



Procedure


2. To add a value to the LOV:

a. Select the Settings tab.

b. Select Lists of Values (LOV) in the left pane.

c. From the Available List of Values, selectModule type.

d. Click Get Values.

e. Click Add.

f. In the Add Value window add the name of the template in the Name field.

For example, if adding the DITA specialize Learning Plan template, enter

Learning Plan.

Post upgrade tasks


g. Optionally, add a Description which explains the proper use of the template.

h. Click OK.

3. Create the topic template:


b. Open System > Editor template then select Topics.

c. Click the New icon in the top right pane.

d. Enter the the name of the template in the Title field and select Topic from the

list in the Content Type field.

e. Click Next.

f. Click Next in the Add Master Document Version window.

g. Click Browse next to the File field in the Add Master Document Language

window.

h. Select the template file to add.

4. Release the template so users can select it.


b. Open System > Editor template then select Topic .

c. Select the template you added in the upper right pane.

d. Select the version and language in the bottom right pane.

e. Click Properties from the menu on the bottom right.

f. In the Document Languages Properties window, select Released from the

Status list.

g. ClickModify.

Adding a graphic template

You can add the template to create new illustrations in the client tools.

Before you begin



Procedure


2. Create an empty graphic template:

a. Open System --> Editor template then select Illustrations.

If the Illustrations folder does not exist, create one by clicking on the New

Folder icon in the upper left pane.

b. Click the New icon in the upper right pane.

c. Enter the name of this graphic in the Title field.

Post upgrade tasks


d. Select or enter other optional information if necessary, then click Next in this

and the next, add language, window.

e. Select the Resolution from the list.

f. Verify that the Format matches the type of template file you have.

g. Click Browse next to the File field in theAdd Illustration Document Language

window.

h. Select the file to use as a template.

Note: For example, SDL LiveContent Architect delivers an empty templatefile on the application server that can be used as a template for png graphics:\InfoShare\Web\Author\EnterViaUI\System\Editor Templates\Illustrations\EmptyGraphic.png

3. Release the template so users can select it.

a. Under the Repository tab in the SDL LiveContent Architectweb client, open

System --> Editor template then select Illustrations.

b. In the upper right pane, select the template you added.

c. Select the version and language in the bottom right pane

d. Click Properties from the menu on the bottom right

e. In the Illustration Document Language Properties window, select Released

from the Status list.

f. ClickModify.

Adding a publication template

You add publication templates that you configure with output type(s), conditions or other

options which can then automatically be available for new publications that use the

template.

Before you begin


Procedure

1. Login to SDL LiveContent Architect Publication Manager.

2. Click Publication > New

Result: A Select Template window displays.

3. Select New Publication.

4. Click Next.

5. Open the System > Editor Templates folder then select Publications.

6. Click Next in the bottom right pane.

7. Enter the Title for this publication template.

Post upgrade tasks


8. Complete other optional fields if needed.

9. Click OK.

10. The new publication is opened in Publication Manager.

11. Click the Output tab to Add and configure output formats that are to be available for

publications based on this template.

12. Optionally, click the Conditions and/or Variables tab to add conditions or variables

that are to be used by publications based on this template.

13. Click Publication > Close.

Introduction to load balancing

You can configure your systems to balance work loads so that the main, or a single server

is not handling all requests.

Consider balancing work loads on your systems for instance, to divide work for user

requests that are expected to be handled immediately from those that take longer and can

be run as background tasks. The division of work loads among several servers can be

accomplished by rerouting queue requests from a main server to batch servers

(asynchronous work load balancing), or by using direct network connections to secondary

servers (network load balancing).

To distribute work loads, you install multiple servers. Each is installed the same, as a

SDL LiveContent Architect application and web server.

■ For asynchronous work load balancing, the additional SDL LiveContent Architect

servers are configured to handle requests through a main SDL LiveContent

Architect server. The main SDL LiveContent Architect server is the one to which

users connect and make work requests. The main server reroutes the request to

another server.

■ For network load balancing, users connect directly to the additional server fortheir work requests. These secondary servers can be used for example, for workrequests to import legacy data or files that have been translated from an outsidesource.

Using separate servers for background processes

Complex tasks that needs to be executed in the background can be executed on (a)

separate server(s).

The difference between synchronous and a background processes are:

■ Synchronous task: a process for which the user waits until the action is completed.

■ Background task: complex tasks that needs to be executed but for which users donot want to wait until it has finished (e.g. publishing very large publications). Abackground process is said to run asynchronously.

Since performance is mostly measured on the synchronous tasks, SDL LiveContent

Architect can be configured to execute background tasks on dedicated servers (batch

servers).

The following diagram illustrates how background processes can be separated:

Post upgrade tasks


Asynchronous load balancing

With asynchronous load balancing, you install a server that handles specific requests, for

example, requests to publish or requests for translation.

The diagram below shows a configuration of two servers that balance the load using

asynchronous load balancing.

Post upgrade tasks


For example, assume you want Batch server1 to handle publishing requests:

■ The user connects to the main server and sends a request to publish.

■ The request is put on the publish queue.

■ The main server checks the resident InfoShareConfig. xml file to determinewhere the publish queue is located (which server handles the request).

Post upgrade tasks


■ The main server's InfoShareConfig. xml file specifies that the publish queueis on the Batch Server.

■ The main server sends the request to the Batch Server as indicated in theInfoShareConfig.xml file.

■ The incoming request is received on the Batch Server; the Batch Server checksthe resident InfoShareConfig. xml file and notes that the queue is local andthat the request is to be handled locally.

■ The Batch Server processes the publishing request.

When configuring for asynchronous load balancing:

■ The main server (the server to which users connect) must be configured to forwardthe request to the (batch) server designated to process the request.

■ The batch server must be configured to accept requests from the main server. Thismay include ensuring that message queuing (messages to the batch server) is notblocked by security settings.

■ The batch server must be configured to handle the request locally.

■ You must redirect full text indexing (FTI). Full index indexing may be on themain server or there may be another server that handles it. The Batch Server mustknow where FTI is handled.

■ Disable the crawler service on the Batch Server and redirect full textindexing (FTI) to the FTI server (configured in the registry.)

■ Modify the server handling FTI to accept requests from other servers.

Network load balancing

Network load balancing requires installation of additional servers to which users or

processes connect directly.

You can use network load balancing to handle requests directly, such as when importing

legacy files or for translation import and export. In this case, the tool connects directly to

the additional server and does not go through a main server. The server interactsdirectly with the database and stores the files in the repository.

Recall that in the SDL LiveContent Architect network, there is a (or multiple) main

server(s) to which users connect, batch servers to which the main server(s) can send work

requests, servers that may directly handle work such as discussed here, and the full text

index server. So when interacting directly with a SDL LiveContent Architect server, you

always must redirect full text indexing to the server which is designated to do this task.

Related tasks

■ “Redirecting full text indexing” on page 136

Asynchronous and network load balancing

You may configure your systems to do load balancing using both asynchronous and

network load balancing.

When you configure your systems for load balancing, you must redirect full text indexing

(FTI) from all servers to the server that handles FTI.

Post upgrade tasks


The graphic below is an example showing:

■ asynchronous load balancing to redirect requests from the Main server to Batchserver1 and Batch server2

■ network load balancing to import legacy files directly on Server 3

■ network load balancing to import translated files directly on Server 4

■ network load balancing to handle FTI on Server 5

Note in the graphic above that:

■ The Main server is that to which users connect and make requests.

■ Batch server1 and Batch server2 are servers to which the Main server redirectswork requests depending on the configuration made for load balancing.

■ Server 3 and Server 4 are servers to which requests are made directly from toolssuch as for legacy import.

■ Server 5 is being used solely for full text indexing.

Note that in addition to the asynchronous and network load balancing described thus far,

on the main server you can configure a QCdispatcher to handle requests. The

QCdispatcher option allows you to specify, depending on message payload (label,

priority...), to which server the request is forwarded.

Prerequisites for load balancing

The prerequisites you need to know and check to help ensure successful configuration for

asynchronous load balancing is explained.

Asynchronous load balancing involves sharing queues among servers. The following

refers to queues when describing asynchronous load balancing.

Post upgrade tasks


SDLLiveContent Architect Version Management

All machines running within one multi-machine setup must be running the same

configuration and the same SDL LiveContent Architect software version. If not, some

message routes may give different results than others.

Security

Security on one computer is easy using the designated system or domain user

(typically the username is InfoShare). To minimize possible access rights issues, you

are advised to start with the domain user and make it a local administrator on each

enabled SDL LiveContent Architect server.

Sharing private queues over multiple servers can mean that you must create the same

named local designated administrator with the same password on all the involved

servers. In general security read/write permission of the Microsoft Message Queues is

the most difficult piece to configure.

COM+ Server Application Names

The name for the COM+ Server applications is used by Microsoft Queued

Components to automatically generate queue names when the queued flag is checked.

The SDL LiveContent Architect InstallTool uses Trisoft-InfoShare-Author and

Trisoft-InfoShare-EndUser for names.

Note that the names do not contain spaces. A problem can arise if the queue name has

a white space in it because the MSMQQueueInfo object does not accept queue

names with whitespace(s) in them. If you have white spaces in queue names, you

should uninstall your DLLs and COM+ application and reinstall using a COM+

Application name without whitespaces. This way, the newly created queues

are generated without white spaces and will function properly.

Configuration Parameters

All parameters on the Main server should match the ones of the batch server. If they

do not match, you see different behaviors depending on the server that executes

the message.

Important to note is:

■ Although forced by InstallTool, the TriDKApp in the registry should beexactly the same. This is because the context containing the user informationis part of the message, and it needs to be validated by the InfoShareAuthorentry in the registry on the asynchronous batch server.

■ DTDs and catalogs have to be available.

Operating System

Windows extra security changes since some ports, which were open by default on

Windows 2000, are closed here by default. If you specify machine names to indicate

the location of other queues, the name resolution of the other machines need to be

guaranteed by DNS or host file.

Private Queues

Private transactional queues are only guaranteed to be transactional on the same

machine. When a message is sent to a local transactional queue, MSMQ guarantees

that there is enough storage available to handle the message on the local queue. When

Post upgrade tasks


MSMQ forwards this message to the local queue of another machine, it may fail

without response or retry.

If the message arrives, it is executed within a transaction once more. Only the actual

crossing of the message can go wrong. SDL LiveContent Architect uses very small

message (of about 4MB or less) so they have a very low rate of failure on today's

machines.

Plan for batch and network load balancing

Before configuring for load balancing, consider the actions and processes in your work

load and the SDL LiveContent Architect servers available among which you can share the

load.

When planning for asynchronous and network load balancing, create tables or lists as

shown in the examples below.

Asynchronous load balancing

The following is an example that describes a possible setup of three (3) servers and how

they can interact with one another. This shows a plan for asynchronous load balancing for

the Actions listed in the first column.

Other columns are:

■ Main server: This is the main SDL LiveContent Architect server to which users

connect making the request for the action in the first column. The rows under this

column show to which server the request is to be forwarded, showing how the

load is to be shared among the other servers.

Use the information to make the necessary modifications in the residentInfoShareConfig.xml file.

■ Batch Server1: This is an additional SDL LiveContent Architect server which is

to be used for the actions that the Main server is to foward to Batch Server1. Verify

that the resident InfoShareConfig. xml file specifies that the processing for

the action (as described in the first column) is Local.

■ Batch Server2 This is an additional SDL LiveContent Architect server which is

to be used for the actions that the Main server is to foward to Batch Server2. Verify

that the resident InfoShareConfig. xml file specifies that the processing for

the action (as described in the first column) is Local.

Action Main server Batch Server1 Batch Server2

Translation Management Batch Server1 Local

PublishService Batch Server2 Local

Notify Rendition Server Batch Server1 Local

Status Transition Plugins Batch Server1 Local

Push Translations Batch Server1 Local

Inbox Export (using Zip files) Batch Server1 Local

Post upgrade tasks


Action Main server Batch Server1 Batch Server2

Update Full Text Retrival Index Batch Server2 Local

The example shows, users connect to the Main server and:

■ When a request for translation management, rendering, status transition, pushtranslation, or inbox exports are made, the Main server forwards it to BatchServer1.

■ When a request for publishing or updating the full text retrieval index is made, theMain server forwards it to Batch Server2.

The advantage of this setup is a split in the load where the:

■ The Main server handles all requests where a user expects an immediate response.

■ Batch Server1 handles all change requests where the user does not expectimmediate result.

■ Batch Server2 server handles all non-transactional request, so all read-onlyoperation such as export and publish are handled on this machine.

QCdispatcher load balancing

When planning for load balancing, also consider configuring a QCdispatcher for

distributing a work load among several servers.

For example, when a request to publish is made to the main server, it can be forwarded to

a QCdispatcher queue. When the request message arrives on the QCdispatcher publishing

queue, a Microsoft Message Queuing Trigger is fired. The rule that is attached to the

Trigger launches the QCdispatcher component.

When QCdispatcher is launched, it checks the configuration file to see to which servers it

can send the request message then it does one of the following:

■ chooses a random queue of batchservers to which to send the message

■ counts the messages that are on the batchservers' queues and send the new requestto a queue with the lowest number of messages

Action Main server moved the request to:

Translation Management Batch Server1

PublishService Batch Server1 —or— Batch Server2

Notify Rendition Server Batch Server1

Status Transition Plugins Batch Server1

Push Translations Batch Server1 —or— Batch Server2

Inbox Export (using Zip files) Batch Server1

Update Full Text Retrival Index Batch Server2

In this case, publishing and push translations may be sent to Batch server1 or Batch

server2 depending on the availability and work load on the queues for each server.

Post upgrade tasks


Network load balancing

The following shows an additional action that can be shared using network load balancing.

In this example, the import of files, for example, importing legacy data using

DITA2Trisoft tool, makes the request (connects) directly to Batch Server2 and does not

go through the main server.

Action Server

Import Dita2Trisoft Batch Server2

Configuring asynchronous load balancing

To configure for asynchronous load balancing, you must direct requests to other, batch

servers, allow the batch servers to accept requests, disable the crawler on the batch

servers, and redirect full text indexing.

Private and public queue configuration

This is a configuration for scaling many-to-one so one or multiple servers can forward

messages to one server only.

If you have multiple SDL LiveContent Architect machines, make sure that the Message

Queue is available for all machines. The techniques and configuration of queues when

using multiple servers is described.

Requirements: A fully operational SDL LiveContent Architect server, verified by

executing actions such as state transition, folder creation, update admin section, and

translation management.

There are two advanced solutions. Make sure that you consistently alter all queue settings

for all machines:

■ Public Queues within a Domain: Security and setup are easier than when usingprivate queues. This is the Microsoft preferred way.

■ Private Queues: Generally used on a single SDL LiveContent Architect server,

however you can configure private queues to be used over multiple SDL

LiveContent Architect servers. Although not advised, you can share private

queues across multiple servers within one domain.

Specifying the queue format name

The syntax and ways to specify a public or private queue location is described.

The AddressSpecification of a computer can be specified using two forms in MSMQ:

■ as the network protocol followed by the network address of the target computer

■ as the operating system (OS) protocol followed by any string (supported by theunderlying operating system) that identifies the target computer

Pubic queues example:

Post upgrade tasks


DIRECT=AddressSpecification\QueueNameDIRECT=Protocol:ComputerAddress$\QueueNameDIRECT=OS:ComputerName\QueueName

Private queues example:

DIRECT=AddressSpecification\PRIVATE$\QueueNameDIRECT=Protocol:ComputerAddress\PRIVATE$\QueueNameDIRECT=OS:ComputerName\PRIVATE$\QueueName

DIRECT format names should be used to send messages whenever routing,

authentication, and encryption by Message Queuing are not needed. When Message

Queuing detects a direct format name for a remote public queue or for a local or remote

private queue, it does not contact the directory service. Message Queuing uses the

information provided by the format name to send messages directly to their destination.

The maximum length allowed for the computer name in the address specification is 256

Unicode characters and queue names longer than 124 Unicode characters are not

supported. Using names longer than 64 Unicode characters for public queue names may

cause a slight reduction in performance.

Configuration of shared queues in InfoShareConfig.xml

When configuring for asynchronous load balancing, you configure shared queues in theInfoShareConfig.xml file.

To pass a work request from the main server to another server, you must modify theInfoShareConfig. xml file on the servers. The file is located in<drive-letter>:\Infoshare\App<project-suffix>\Author\Configuration\.

For example, a typical entry in \ InfoShareConfig. xml file is:

<label name= ’CREATETRANSLATIONS’><handler><project>ISAuthor</project><component>CTranslationMgmt</component><asynchronousprocessing>yes</asynchronousprocessing>

</handler></label>

This entry is used when a create translation request is made to the main server. A correctly

specified <queuespecification> entry can be used to point to the queue of the localserver, or to pass the request to another server.

To pass the request to another SDL LiveContent Architect server, you modify the file as

shown in the example below.

<label name= ’CREATETRANSLATIONS’><handler>

Post upgrade tasks


<queuespecification>FormatName=DIRECT=TCP:145.4.3.122\PRIVATE$\ISHAuthor

</queuespecification><project> ISAuthor </project><component> CTranslation Mgmt</component><asynchronousprocessing>yes</asynchronousprocessing>

</handler></label>

The <queuespecification> points to an existing queued components queue on theother server. In this case, when the request is made to the main server, it is passed to theserver and queue specified in the <queuespecification>.

To use private queues of another machine, you can modify the file as shown below.


<queuespecification>FormatName=DIRECT=OS:PC2-XML\PRIVATE$\TrisoftOCEAuthor

</queuespecification><project> ISAuthor </project><component> CTranslation Mgmt</component><asynchronousprocessing>yes</asynchronousprocessing>

</handler></label>

To point to the local server, you can modify the file as shown below. You can do this on

the batch server to which the request is passed, where it is to be handled locally. For

instance, if the main server passes a create translation request to Batch server2, Batch

server2's InfoShareConfig. xml file must indicate that the request is to be handledlocally.

You can modify the file by using commenting arrows  for the queuespecification

or by completely removing the queueuspecification element and contents so the entry

reads, for example:


<project> ISAuthor </project><component> CTranslation Mgmt</component><asynchronousprocessing>yes</asynchronousprocessing>

</handler></label>

Post upgrade tasks


Configuring the batch server to accept messages from the mainserver

On the batch servers (additional server handling messages from the main server) you

must trigger a COM+ server application on the batch server to pick up the arriving

messages for background tasks.

About this task

Background tasks are communicated by messages. Arriving messages do not

automatically trigger the Microsoft COM+ engine to start the Trisoft-InfoShare-Author

COM+ server application so the messages are stored onto a queue until someone starts the

application.

An application is started many times a day (up to once every minute if required) by a

synchronous request coming from a script like the Maintenance vbscriptWakeUpIshComponents. vbs or from a web request.

Procedure

1. On the Windows server, go to Computer Management > Configuration > Task

Scheduler > Task Scheduler Library

2. Click Create a Basic Task (right pane).

3. In the Name field, enter Trisoft Wakeup Components.

4. Optionally, enter a description in the Description field such as: This scheduled

task is triggered every 5 minutes to start the

Trisoft-InfoShare-Author COM+ server application.

5. Click Next.

Result: Trigger is selected in the right pane, and the Task Trigger windowdisplays.

6. Click the radio button next to when you want the task to start; it is recommended that

you click Daily.

7. Click Next.

Result: Daily is selected in the right pane under Trigger, and the Dailywindow displays.

8. Enter the start date and time and number of days for reoccurance. It is recommended

that this task reoccur every 1 day.

9. Click Next.

Result: Action is selected in the right pane and the Action window displays.

10. Click in the radio button to Start a program.

11. Click Next.

Result: Start a program is selected in the right pane and the Start aProgram window displays.

12. Browse to the WakeUpIshComponents. vbs script in the \ App\ Maintenance\WakeUpIshComponents folder.

Post upgrade tasks


13. Click Next.

Result: Finish is selected in the right pane and the Summary windowdisplays.

14. In the Summary window:

a. Check the box for Open the Properties dialog for this task when I click

Finish.

15. In the Property window:

a. Change the user to the system service user account.

b. Select Run whether user is logged on or not.

c. Open the Triggers tab and edit it to Repeat task every: 5 minutes for a

duration of 1 day. Be sure the Enabled checkbox is checked.

d. Click OK.

If required, enter the password of the SDL LiveContent Architect system service user.

Message queuing security configuration

If no messages arrive at the batch server, the message delivery from one server (main) to

the batch server may be blocked by security settings.

Before you begin

The settings described must be available on the application servers handling the incoming

request if they are running Windows 2008.

About this task

Messages are only transactional within the scope of one machine. Message Queuing uses

the anonymous user to send messages to remote queues. This option is disabled by

default on Windows 2008 so delivery of messages across machines is not guaranteed by

Microsoft using the anonymous user. Allow the anonymous user to act with the Everyone

permissions to remedy this issue.

Procedure

1. Login to the target (batch/asynchronous) server as the administrator user or a user

with administrative privileges (a user in the administrator group).

2. Open the Local Security Settings by entering secpol.msc at a command prompt.

3. Open Local Policies > Security Options.

Result: The Local Security Settings window is displayed with the LocalSecurity Setting tab selected.

4. Double-click on Network access: Let Everyone permissions apply to anonymous

user in the right pane.

5. Select Enabled.

6. Click OK.

Post upgrade tasks


7. Click File > Exit to close the Local Security Settings window.

8. Reboot the server.

Redirecting full text indexing

Redirect full text indexing when configuring batch servers, or when the local machine

does not have full text indexing (FTI). This can be done on a main server if FTI is handled

on a different server, for batch servers when configuring asynchronous load balancing,

or when configuring network load balancing.

About this task

The configuration for full text indexing (FTI) is handled by the Crawler and SolrLucene

entries in the registry.

A default configuration is installed that connects to the localhost (127.0.0.1) port 8080.

For example:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Trisoft\TriDK\TridkApp\InfoShareAuthor]"CrawlerIndexEngineType"="ApacheSolrLucene""SolrLuceneBaseUrl"="http://127.0.0.1:8080/solr""SolrLuceneHTTPTimeout"="180""SolrLuceneHTTPRetries"="5"

To redirect full text indexing on a secondary server to the FTI server:

Procedure

1. On the secondary server, alter SolrLuceneBaseUrlto the URL for SolrLucene on thefull text indexing (FTI) server.

Example: For example, where 10.98.124.5: 8080 is the FTI server's URL forSolrLucene, modify the secondary (for example, the batch) server's registry to read:

[HKEY_LOCAL_MACHINE\SOFTWARE\Trisoft\TriDK\TridkApp\InfoShareAuthor]"SolrLuceneBaseUrl"="http://10.98.124.5:8080/solr"

Result: Full text indexing is now directed to the server as specified in theregistry for SolrLuceneBaseUrl.

2. Reboot the secondary server or, at minimum, a recycle is required for the application

pool and COM+ server application.

3. To allow incoming requests on the FTI server from other servers, add the secondary

servers IPs, or server IP range to the FIT server, in the \ App\ Utilities\SolrLucene\Jetty\etc\jetty-ipaccess.xml file'swhite list.

Example: For example, to allow incoming requests on the FTI server fromother servers as identified by the IP address 127.0.0.1 and IP range

10.98.0-255.0-255:

Example: On the FTI server modify jetty-ipaccess. xml to read:

Post upgrade tasks


<Set name= "white"><Array type= "String">

<Item>127.0.0.1</Item><Item>10.98.0-255.0-255</Item>

</Array></Set>�

4. Disable the crawler service on the secondary server (the server that has been

redirected to the FTI server):

■ Click Control Panel > Administrative Tools > Services

■ Double-click on the service named, Trisoft InfoShare<project_name>Crawler One.

For example: Trisoft InfoShareDita Crawler One

There may be more than one service. If so, follow the procedure for each.

■ Under the General tab, set the Startup type to Disabled.

5. Restart the TrisoftSolrLucene Windows service on the secondary server.

Configuring a batch server for publishing

If you want a separate server to handle publish requests, you can configure a batch server

to handle the output requests.

Before you begin

■ Install identical batch and main servers with the same suffix.

■ Use the same inputparameters. xml file on the servers.

■ Make certain that the batch and main servers connect to the same database.

Procedure

1. On the main server:

a. Edit theC:\InfoShare\App<suffix>\Author\Configuration\InfoShareConfig.xml file.

b. Search for <label name="EXPORTFORPUBLICATION">

c. Insert the queuespecification line highlighted below but changeBatchServerComputerName to the batch server's hostname.

<label name="EXPORTFORPUBLICATION"> <handler>

<handler><queuespecification>FormatName=DIRECT=OS:BatchServerComputerName\PRIVATE$\Trisoft-InfoShare-Author</queuespecification>

<project>PublishService</project>

<component>CExport4Pub</component>

Post upgrade tasks


2. On the batch server:

a. Open the Start > Run menu and enter secpol.msc.

Result: A Local Security Settingss window is displayed.

b. Browse to Local Policies > Security Options.

c. Select the Network access: Let Everyone permissions apply to anonymous

users and enable it

d. Close the security settings window.

e. Open: Administrative Tools > Task Scheduler .

f. Click Action > Create Basic Task.

g. In the Name field, enter Architect Wakeup Component.

h. In the Description field, enter Task to publish from the main server then

click Next.

i. Select Daily for the task trigger then click Next.

j. Make sure that Recur every is set to 1 day then click Next.

k. Select Start a Program then click Next.

l. ClickBrowse and select:C:\Infoshare\ App<suffix>\ Maintenance\

WakeUpIshComponents\WakeUpIshComponents. vbs then clickNext.

Where <suffix> is the application project name (if specified).

m. Select the Radio button Open the Properties dialog for this task when I

click Finish then click Finish.

n. Right-click on Architect Wakeup Component then select Properties.

o. In the Properties window under the General tab, select Run whether the

user is logged on or not.

p. Click Change User or Group.

q. Login if necessary then if a domain user, click Locations then select the

domain, otherwise leave the machine name in the location field.

r. Enter the user name in the lower field, that is indicated in the

inputparameters. xml file for osuser, then clickCheck Names.

The name is automatically found and populates the field.

s. Click OK.

t. Open the Triggers tab then click Edit.

u. Select Repeat task every and set to 5 minutes.

v. Click OK to exit.

3. Disable both Trisoft InfoShare Crawler services on the batch server.

Post upgrade tasks


4. Reboot the batch server.

5. To verify, publish a publication from the web client and check that the request is

processed on the batch server instead of the primary server. The name of the batch

server is indicated in the window when published, for example, the batch server name

is circled in the graphic below.

Queued Component dispatcher

This is a queue configuration for a many-to-many (server) forwarding.

The QCDispatcher can decide depending on message payload (label, priority...) to which

server the message is forwarded. Complex tasks that needs to be executed in the

background can be executed on separate batchservers using the Queued Component

dispatcher (QCdispatcher). This is an optional configuration procedure that you can do at

any time, when needed.

Introduction and overview

The default, out-of-the-box SDL LiveContent Architect can be configured to use a batch

server for background tasks. To reduce the amount of time to process requests, add a

batchserver for a single event type.

You can configure one batchserver for one event type, for example, the event,

EXPORTFORPUBLICATION. If you have many requests, a single batchserver is

sometimes not sufficient. When the batchserver has many queued requests, it can take

time before all requests can be processed. The procedure to add a second batchserver for

a single event type is described using the Queued Component dispatcher (QCdispatcher).

Note: The procedures that follow must be done on the SDL LiveContent Architectserver. The procedure is for installing on a Windows 2008 R2 server. This is the supported

OS for this release.

With the default scenario, you modify InfoShareConfig.xml to send events (for example

of type EXPORTFORPUBLICATION) to a batchserver using the queuespecificationelement. Refer to the example below of the default configuration:

Post upgrade tasks


<label name= "EXPORTFORPUBLICATION"><handler>

<queuespecification>FormatName=DIRECT=OS:batchServer\private$\trisoft-infoshare-author</queuespecification>

When using QCdispatcher the InfoShareConfig.xml reads:

<label name= "EXPORTFORPUBLICATION"><handler>

<queuespecification>FormatName=DIRECT=OS: Main Server\ private$\trisoft- infoshare- publishing </queuespecification>

For example, in this case when requesting a publication, the request message is not put on

the queue of the batchserver but it is put on a different queue of the main server. When

the request message arrives on this Trisoft-infoshare-publishing queue, a Microsoft

Message Queuing Trigger is fired. The rule that is attached to this Trigger launches the

QCdispatcher component.

When QCdispatcher is launched, it checks the configuration file to see to which servers it

can send the request message then it does one of the following:

■ chooses a random queue of batchservers to which to send the message

■ counts the messages that are on the batchservers' queues and send the new requestto a queue with the lowest number of messages

An example of this configuration is:

<eventGroup name= "publishing" dispatchType= "count"><serverQueues><serverQueue path="Format Name:DIRECT=OS:pubbatchserver1\private$\trisoft-infoshare-author"/><serverQueue path="Format Name:DIRECT=OS:pubbatchserver2\private$\trisoft-infoshare-author"/></serverQueues>

</eventGroup>

The batch server

The batch server must be installed exactly like the main server (use the same service

account, same inputparameters.xml, etc.)

If the batch server is dedicated for publishing or other batch tasks, you can disable the

crawler and SolrLucene services on the batch server. This saves about 300 MB of memory

and some CPU time. Stop the SDL LiveContent Architect crawlers and SolrLucene

services on the batch server and set their startup type toManual.

Post upgrade tasks


Note: The SDL LiveContent Architect crawlers may be named Trisoft in the list ofprocesses or tasks.

If the batch server is also used as a second main server, then you can configure both the

main and the batch server so that the Solr/Lucene database on the main server can be

accessed by the batch server, and that the batch server's search requests are sent to the

main server.

Installing the message queuing triggers

Install the Message Queuing Triggers component as a prerequisite to installing the SDL

LiveContent Architect QCDispatcher component.

Procedure

1. Click Start > Administrative Tools > Server Manager.

Result: The Server Manager window is displayed.

2. Click Features in the left pane.

3. Click Add Features in the upper right.

Result: A Select Features window is displayed.

4. OpenMessage Queuing > Message Queuing Services then click the checkbox for

Message Queuing Triggers.

5. Click Next.

6. Click Install.

7. Click Close.

Installing the SDL LiveContent Architect QCDispatchercomponent

The InstallTool installs the QCDispatcher component. However, if the components are

not correctly installed, you can install the components from the CD.

Procedure

1. Register the QCDispatcher component, Trisoft.Utilities.COMQUtilities.dll

At an administrative command prompt, go to the C:\InfoShare\ AppCore\Utilities\ QCDispatcher directory and execute the following commands:

regasm Trisoft. Utilities. COMQUtilities. dll / tlbgacutil / i Trisoft. Utilities. COMQUtilities. dll

Post upgrade tasks


Note: regasm and gacutil are on the CD package in\Applications\Utilities\InstallTools\NET\2.0

2. Add the registered component to the Trisoft-InfoShare-Author com+ application

a. Click Start > All Programs > Administrative Tools.

b. In the right pane, open Component Services > Computers > My Computer

> Com+Applications > Trisoft-InfoShare-Author > Components.

c. Right click on Components > New Component

Result: AWelcome to the Com+Component Install Wizard windowis displayed.

d. Click Next then click Install New component.

Result: A Select New Component window is displayed.

e. BrowsetoC:\InfoShare\AppCore\Utilities\QCDispatcher

f. SelectTrisoft.Utilities.COMQUtilities. tlb.

g. Click Next.

h. Click Finish.

3. Add the values and value data as described below to the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Trisoft\Tridk\TridkApp\InfoShareAuthor<SUFFIX>]

Note: The <SUFFIX> is the projectsuffix parameter in the inputparamters.xml file.If there is only one installation on the server, the projectsuffix may be empty (which

is the default) and in that case, there is no <SUFFIX> in the value data or in theregistry keys.

Specify the location of the log file

Value QCDispatcherLogFile

Value Data \Data<SUFFIX>\logs\QCdispatcher.log

Example C:\InfoShare\Data<SUFFIX>\Logs\QCdispatcher.log

Specify the location of the configuration file

Value QCDispatcherConfigurationFile

Value Data \App<SUFFIX>\Author\Configuration\QCdispatcher

Config.xml

Example C:\InfoShare\App<SUFFIX>\Author\Configuration\

QCdispatcherConfig.xml

Post upgrade tasks


Specify the log level

Value QCDispatcherLogLevel

Value Data Verbose

Note If desired, this can be set to Exception when using in

production.

Creating the MSMQ Trigger rule(s)

Create message queuing trigger rules for the process(es).

About this task

Note: In the procedure that follows, references to <SUFFIX> is the projectsuffixparameter in the inputparamters. xmlfile. If blank in the xml file, ignore <SUFFIX>in the step.

Procedure

1. Click Start > Administrative Tools > Computer Management

Result: A Computer Management window is displayed.

2. Open Services and Applications > Message Queuing > Triggers Message

Queuing > Triggers

3. Right-click on Rules.

4. Click New > Rule.

5. For publishing, set the Rule Name to

QCdispatcher-Trisoft-InfoShare<SUFFIX>-Publishing

6. Click Next.

7. Leave the Condition field empty in the Define conditions for the rule pane.

8. Click Next.

9. Specify a COM component:

a. Set Component ProgID to Trisoft.Utilities.COMQUtilities.QCDispatcher

b. SetMethod name to DispatchSingleMessage

10. Click Parameters.

11. Specify the parameters:

a. From the parameter drop down list, select String literal.

b. Set the Literal value to InfoShareAuthor<SUFFIX>.

c. Click Add.

d. Do the same for the second parameter but set the Literal value to Publishing

for publishing events, then click Add.

Post upgrade tasks


e. Add a third and forth parameter by selecting from the parameter drop down

list:

■ Queue format name (as string)

■ Message Lookup ID (as variant)

f. Verify that the parameters are in the following order. If not, select the

parameter then use the Up and Down buttons on the right, to reorder the list to

appear in this order:

■ "InfoShareAuthor"

■ "Publishing"



12. Click OK.

13. Click Finish.

14. If needed, follow these steps to create the trigger rule for translation.

Note:

Rule Name: QCdispatcher-Trisoft-InfoShare<SUFFIX>-Translation

Parameters:■ "InfoShareAuthor"

■ "Translation"



Creating Transactional Queues

Create the two transactional queues as described.

About this task

In the procedure that follows, references to <SUFFIX> is the projectsuffix parameter in

the inputparamters. xml file. If this is not indicated in the xml file, ignore <SUFFIX> in thestep.

Procedure

1. Click Start > Administrative Tools > Computer Management.

Result: A Computer Management window is displayed

2. OpenServices and Applications > Message Queuing

3. Right-click on Private Queues.

4. Click New > Private Queue

Result: a New Private Queue window is displayed.

Post upgrade tasks


5. In the Queue Name field enter:

trisoft-infoshare<SUFFIX>-publishing

Make certain that transactional box is checked.

6. Click OK.

7. Add a second queue; in the Queue Name field enter:

trisoft-infoshare<SUFFIX>-translations

Make certain that transactional box is checked.

8. Click OK.

9. Create the MSMQ Triggers trigger

a. Right click onMessage Queuing > Private Queues

> trisoft-infoshare<SUFFIX>-publishing > Triggers then choose New

Trigger

b. In the Trigger Name field, enter

QCdispatcherTrigger-Trisoft-InfoShare<SUFFIX>-Publishing and check

Serialized.

Leave the Enabled box checked also.

c. Click Next.

d. With QCdispatcher-Trisoft-InfoShare<SUFFIX>-Publishing rule selected in the

left pane, click Attach.

The rule is moved to the right pane under Attached Rules.

e. Click Finish.

10. Give the SDL LiveContent Architect service account (eg: infoshare), Administrators

(local) and MSMQ Triggers (local) full control for these queues.

a. Right-click on the queue, click Properties.

b. Click on the Security tab.

c. Click on the username.

d. Add all permissions for the user, click Allow to check all permissions then

click Apply and OK.

11. If needed for adding translation queues, follow the two steps above but note that the

Trigger Name should be entered as

QCdispatcherTrigger-Trisoft-InfoShare<SUFFIX>-Translation

Configuring

Add the queue(s) and configure the system so that the event(s) go to the desired queue.

About this task

In the procedure that follows, references to <SUFFIX> is the projectsuffix parameter in

the inputparamters. xml file. If blank in the xml file, ignore <SUFFIX> in the step.

Post upgrade tasks


Procedure

1. Open\InfoShare\App<SUFFIX>\Author\Configuration\QCdispatcherConfig. xml and complete the trisoft-infoshare-author queues of thebatchserver that you want to use for publishing and for translations. For example:

<eventGroups><eventGroup name= "publishing" dispatchType= "count">

<serverQueues><serverQueuepath="FormatName:DIRECT=OS:BatchServer1\private$\trisoft- infoshare- author" /><serverQueue path="Format Name:DIRECT=OS: Batch Server2\ private$\trisoft- infoshare- author" />

</serverQueues></eventGroup><eventGroup name= "translation" dispatchType= "random"><serverQueues><serverQueue path="Format Name:DIRECT=OS: BatchServer3\private$\trisoft-infoshare-author"/><serverQueue path="Format Name:DIRECT=OS: BatchServer4\private$\trisoft-infoshare-author"/></serverQueues></eventGroup>

</eventGroups>

2. · Change InfoShareConfig. xmlso that events of type EXPORTFORPUBLICATIONare sent to the dispatcher queue.

[�]<label name= "EXPORTFORPUBLICATION">

<handler><queuespecification>FormatName=DIRECT=OS: Main Server\ private$\ trisoft- infoshare<suffix>-publishing </queuespecification>

[�]

Testing the QCdispatcher

After installing QCdispatcher, test that it operates as expected.

About this task

The batchservers should be set up as a normal batchserver; such as wakeUpComponents

scheduled task should be running and Network access: Let Everyone permissions

apply to anonymous user should be in place. Also when you install SDL LiveContent

Architect on the batchservers ensure that the application name (the suffix) is the same as

that which is on the main server.

Post upgrade tasks


Procedure

1. On the publishing batchserver(s), in Administrative Tools > Component Services

disable the Trisoft-InfoShare-Author COM+ application .

2. On the main server shutdown the Message Queuing Triggers service.

3. Publish one publication. Verify that you see one message on the

trisoft-infoshare-publishing queue.

4. Start the Message Queuing Triggers service. Verify that the message is not on the

queue anymore.

5. Check the batchservers and verify that there is one message.

6. Enable and start the Trisoft-InfoShare-Author COM+ application. Verify that the

publish request is processed by the batchserver.

For Windows 2008

Information for how-to for Windows 2008 were executed previously during the

installation; for example during Operating System installation time or when using the

SDL LiveContent Architect InstallTool. This information can be referenced if you must

execute or reconfigure these steps manually.

Security and Firewall

When there is a transaction problem, it is usually because the database and application

server are not able to communicate with each other.

After an installation, test transactions by creating a new temporary repository folder.

When there is a transaction problem the typical message is New transaction cannot

enlist in the specified transaction coordinator. This is typicallybecause the two-way communication is blocked by a firewall, or security settings do notmatch.

Check all SDL LiveContent Architect and database servers for security settings described

in this section.

Enabling network transactions

The Microsoft Distributed Transaction Coordinator must allow network transactions. This


servers.

About this task



Post upgrade tasks


Procedure









■ Network DTC


■ Allow Inbound

■ Allow Outbound







8. Click OK.

Firewall Configuration for MDTC

You can enable the built-in rule to allow distributed transactions in the Windows Firewall.

Procedure

1. Login to the system as the administrator user or a user with administrative privileges.

2. Click Start > Control Panel > Windows Firewall

3. In the left pane, click Allow a program or feature through Windows Firewall.

Result: The Allowed Programs window displays.

4. In the Allowed Programs window select (check the box next to) Distributed

Transaction Coordinator.

5. Click OK.

Result: The changes are saved.

Post upgrade tasks


Firewall configuration for Oracle RDBMs

A firewall configuration must be done when using Oracle RDBMs

Procedure

1. Click Control Panel > Windows Firewall.

2. In the left pane, click Advanced Settings.

3. In the left pane, right-click on Inbound Rules then select New Rule.

4. Select Port then click Next.

5. In the Specify Local Ports field, select TCP and enter 1521; then click Next.

6. Select Allow the Connection then click Next.

7. SelectWhenApplies matching your network environment setup, typically values

Domain and Private.

8. Click Next.

9. Enter the Name: Listener

10. Click Finish.

11. Repeat these steps but when specifying the local port, enter 1526.

12. Create a New Rule on Inbound and Outbound Rules using these settings:

What Protocol Port Direction

Listener TCP 1521 IN/OUT

Listener TCP 1526 IN/OUT

.NET Transactions Maximum Timeout

If the logging of .NET based programs returns a cannot access or timeout error, it usually

means that the timeout setting was reached and exceeded.

About this task

If the logging of .NET based programs returns an error (as listed in the examples below)

it usually means that the transaction timeout was reached without program completion.

Example .NET program error:

■ System.ObjectDisposedException: Cannot access a disposed object

■ Transaction timeout

■ The transaction has aborted

If the maximum timeout setting in machine.config setting is not specified, the defaultis 10 minutes. This cannot be overridden in code. It is designed to be used by theSystemAdministrator to limit transaction timeouts. If the app.config timeout or the

timeout specified in the program's source code exceeds the maximum timeout in themachine.config, the timeout is adjusted down to the maximum timeout value.

Post upgrade tasks


Procedure



2. Openthe%WINDIR%\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config file.

3. At the bottom of the configuration section, just before the closing tag add:

<configuration>[...]<system.transactions><machine Settings maxTimeout="01:00:00" />

</system.transactions></configuration>

4. Save the file then open the %WINDIR%\ Microsoft.NET\ Framework\v4.0.30319\CONFIG\machine.configfile.

5. At the bottom of the configuration section, just before the closing tag add the same:

<configuration>[...]<system.transactions><machine Settings maxTimeout="01:00:00" />

</system.transactions></configuration>

6. Save the file and restart the application.

7. If possible restart the server.

Throttling the number of parallel executed messages (queuelisteners)

The number of maximum concurrent players for the queue listeners may be defined.

Procedure



2. Click Start > Control Panel > Administrative Tools > Component Services.

3. Select the properties of the COM+ server applications.

4. Click on the Queuing tab.

5. Set the number ofMaximum concurrent players to 4 unless instructed to do

otherwise by an SDL consultant.

Post upgrade tasks


Disabling friendly HTTP error messages on client and server

You can make error messages visible that are obscured by the high security settings on

Internet Explorer 8 and Internet Information Server 7.x.

About this task

By default Internet Explorer 8 and Internet Information Server 7.x come with high

security settings which results in obscuring actual error messages with more general

messages such as, HTTP 500 - Server Error or An error occurred on the

server when processing the URL. Please contact the systemadministrator. To make the actual error message visible follow the procedure below.

Procedure

1. Login to the web server as the administrator user or a user with administrative

privileges (a user in the administrator group).

2. Open a command prompt window.

3. Set the web server asp scriptErrorSentToBrowser to true in the command prompt

window by executing the following (enter on one line):

%windir%\ system32\ inetsrv\ appcmd.exe set config-section:system.webServer/asp-scriptErrorSentToBrowser:true

4. Close the dialog.

Result: The setting should become active immediately.

5. Login to the client and open an Internet Explorer window.

6. Click Tools > Internet Options Internet Options.

7. Click the Advanced tab.

8. Deselect the Show friendly HTTP error messages options.

9. Click OK.

Enable InfoShareAppPool32Bit on virtual directories

Most of the server code is running 32-bit. As such, websites should run in 32-bit mode.

About this task

By default the InfoShareAuthor and InfoShareWS virtual directory is hosted by the IIS

DefaultAppPool using the credentials provided by the Network Services identity.

To run websites in 32-bit mode to match the 32-bit server code, create an Application

Pool which is 32-bit enabled.

Post upgrade tasks


Procedure

1. Login to the web server as the administrator user or a user with administrative

privileges (a user in the administrator group).

2. Create a new application pool:

a. Click Start > Administrative tools > Internet Information Services (IIS)

manager.

b. Navigate to, and right-click onApplication Pools.

c. Click AddApplication Pool.

d. In the Name field, enter InfoShareAppPool32Bit.

e. Select the .NET Framework version.

f. Select Integrated as theManaged pipeline mode.

g. Select Start application pool immediately.

3. Set the application pool identity to the designated InfoShare user:

a. Right-click on InfoShareAppPool32Bit.

b. Select Advanced Settings.

c. Set Enable 32-Bit Applications to True.

d. Set Identity to the designated InfoShare user.

e. In the Set Credentials window, enter the Infoshare user name and password.

f. Click OK.

g. In the Application Pool Identity window, click the radio button next to

Custom account.

h. Click OK.

4. Enable the application pool on virtual directory InfoShareWS:


manager.

b. SelectManage Application > Advanced Settings.

c. Set Application Pool to InfoShareAppPool32Bit.

d. Click OK.

5. Enable the application pool on virtual directory InfoShareAuthor:


manager.

b. Navigate to Sites Default Web Site and right-click on InfoShareAuhorDita.

c. SelectManage Application > Advanced Settings.

Post upgrade tasks


d. Set Application Pool to InfoShareAppPool32Bit.

e. Click OK.

Changing Startup Type of the SDL LiveContent Architectservices

When both the database and SDL LiveContent Architect components are installed on the

same server, the Startup Type of every SDL LiveContent Architect service should be

changed to Automatic (Delayed Start).

About this task

Note: Database and SDL LiveContent Architect components installation on one serveris not a recommended configuration.

Procedure

1. Login to the server as the administrator user or a user with administrative privileges


2. Click Start > Administrative tools > Services.

3. Right-click on the Trisoft InfoShare Crawler One service.

4. Select Properties.

5. Click the General tab.

6. In the Startup Type field selectAutomatic (Delayed Start).

7. Click OK.

Troubleshooting the crawler service

If the crawler service does not run after the installation, you can unregister and register

the crawler service to fix this issue.

Procedure

1. Login into the server as an Administrator user.

2. Run the following bat scripts:

<INFOSHARE>\App\Crawler\Configuration\UnregisterAllCrawlers.bat

<INFOSHARE>\App\Crawler\Configuration\RegisterThisCrawler.bat

Troubleshooting the install tool

Error when running the install tool: RegAsm.exe - .NET Framework Initialization Error

If the Microsoft Server .Net 4.0 is not installed you get errors from InstallTool such as:

RegAsm.exe - .NET Framework Initialization Error

Post upgrade tasks


The NETFramework2010_4.0.30319_(dotNetF40_Full_x86_x64).exe tested with thisversion of SDL LiveContent Architect can be retrieved online from SDL upon request.

SDL LiveContent Reach upgradeSDL LiveContent Reach has added features.

If you were using SDL LiveContent 5.2 or earlier and upgraded to the lastest version of

SDL LiveContent Reach, you must republish your documents to your SDL LiveContent

Reach server to use the new review and edit features of the product

Modifying the SETTITLE pluginModify the SETTITLE plugin to fix a recurring issue with titles that are overwritten after

importing when using DITA2Trisoft.

The SETTITLE plugin is, by default, configured to copy the value from the metadatafield

FTITLE into the title element, overwriting anything that is in the title.

<Plugin name="SETTITLE" handler="Ish StdPlugins. CDoc SetXMLNode"ishcondition= "ISHType in (’ISHMasterDoc’, ’ISHModule’, ’ISHLibrary’) and EDT= ’EDTXML’ and VERSION= ’1’ and CurrentAction= ’Create’"><Description>Set title for new objects using the metadata title</Description><Parameters><Parameter name="OnNodeXPath">(/ * [contains(@class,’ map/ map’)] [title]) | (/ * [contains(@class,’ topic/ topic ’)] [title])</Parameter><Parameter name="NodeType">node</Parameter><Parameter name="NodeName">title</Parameter><Parameter name="Overwrite Existing">Yes</Parameter><Parameter name="Value"> <Value type="Meta DataField"> <Parameter name="Meta DataField">FTITLE</Parameter>

<Parameter name="Meta DataField Level">logical</Parameter> </Value> </Parameter></Parameters></Plugin>

Set <Parameter name="OverwriteExisting">Yes</Parameter> from Yes to No:

<Parameter name="OverwriteExisting">No</Parameter>

Post upgrade tasks


Chapter 8

Reference for the installation toolsand files

The following describe the tools and files used during a SDL LiveContent Architect

installation for your information and reference.

InstallToolInstallTool is a command line driven application which allows you to install SDL

LiveContent Architect, including customer-specific files and components.

InstallTool overview

InstallTool logs all installation actions and keeps an installation history which allows you

to rollback.

InstallTool was developed to:

■ reduce the time needed to install InfoShare

■ eliminate the most common mistakes when installing InfoShare

■ provide reproducible installations over DEV, QA and PROD

■ provide a framework for system integrators to deploy a customer-specific SDL

LiveContent Architect application

■ make it easier to have multiple SDL LiveContent Architect applications on one

server

Training is available on how to build and maintain the InstallTool package. Note that the

Generate InstallPlan option cannot take into account all variations of all possible setups or

all possible options. Manual actions on the InstallPlan may be required to describe your

installation. InstallTool is only available to generate the initial file.

Executing the program consists of starting InstallTool and following the instructions. The

InfoShare Database should be up and all Microsoft components and Third Party Software

should be installed.


The InstallTool

The InstallTool package contains three parts described herein.

The InstallTool package contains:

The root of your CD location

This is folder on your file system using the SDL LiveContent Architect official

structure containing the raw data.

InstallPlan.xml

The InstallPlan is generated by SDL LiveContent Architect or an integrator. It

describes the installation. That is, it describes every install action such as the source

and target folder for every file, COM+Applications and their content, Virtual

Directories, Registry structures, Services and so on.

An install plan is built of two types of building blocks:

■ file elements (from-to copy statements)

■ webapp/commapp/registry/serviceapp (system change statements)

These building blocks are in the following three groups:

■ Core (e.g. a DLL can only be installed once)

■ Standard (the SDL LiveContent Architect standard DITA delivery)

■ Customer Specific (your customised/project files overwriting the Standard/DITA files

Note that if you add files to the CD, you must regenerate the install plan otherwise it

does not contain extra file elements.

InputParameters.xml

This file contains a list of variables which require a value assignment from the system

administrator. The main goal is to centrally define global settings such as AppPath,

WebPath, DataPath, ProjectName, Designated OSUser, database ConnectString, and

so on.

The file contains the prompts displayed in a graphical user interface of an install

program. All these values are inserted in the necessary places during the installation.

The InputParameters file needs to assign a value for ALL variables used somewhere in

the InstallPlan.xml or in files which use variables on the CD.

Unimplemented features of the InstallTool

InstallTool must know about all SDL LiveContent Architect options, features, and

environment changes that are impossible however, some operations are not automated.

For reasons of security and complexity, the following operations are not automated:

■ Installing SQL Server or Oracle.

■ Running scripts on an existing database.

■ Creating the designated operating system user.

■ Changing the transaction timeout settings.

Reference for the installation tools and files


■ Delta upgrading of environments (only full (un)install).

■ Checking the availability of correct Microsoft components.

There are some additional, manual configurations or edits that need to be done included

in the procedure for installing or upgrading.

Database Upgrade Tool (DBUT)Database Upgrade Tool (DBUT) allows automated database upgrading.

DatabaseUpgradeTool (DBUT) overview

The DBUT allows upgrading using a DatabaseUpgradeTool, similar to InstallTool.

The tool can handle statements from the Upgrade such as:

■ Oracle RDBMs 10.2 indexes, views, packages for TriDK, EventMonitor, andInfoShare Common

■ Microsoft SQL Server 2005/2008 indexes, views, stored procedures and functionsfor TriDK, EventMonitor and InfoShare Common

■ TriDK Xml Setup and small TriDK Migration code

Several projects have indicated that there are less and less database administrator (DBA)

people involved in upgrades. The manual upgrades by non-DBApeople are error-prone.

To reduce upgrading risks and allow better database upgrade logging SDL LiveContent

Architect grouped them together in one tool, developed to:

■ reduce the time needed to upgrade the SDL LiveContent Architect database

■ eliminate the most common mistakes when upgrading

■ provide reproducible installations for DEV, QA and PROD

■ have one log file holding all database upgrade information, the

DBUpgradeTool.log, which can be used for troubleshooting or reporting issues.

DatabaseUpgradeTool should NOT be used:

■ to handle customer specific upgrades and/or information

■ by integrators or customers to handle their upgrades

Executing the program consists of starting DatabaseUpgradeTool and following the

instructions.

The InfoShare Database should be up, and all database satellites and services should be

down to allow exclusive access for the tool, to the database.

In a Windows 2008 environment, the program should be executed with Run as

administrator.



The DatabaseUpgradeTool (DBUT)

The DBUT tool has three requisites described herein.

The DatabaseUpgradeTool determines the current version of the database then runs the

necessary sql scripts and TriDK XML scripts to upgrade the SDL LiveContent Architect

database to the SDL LiveContent Architect version that is installed. The

DatabaseUpgradeTool package requires:

A running database

To allow upgrading of the database, the database must be operational

(up-and-running).

Note: Automatic upgrading is only supported starting from SDL LiveContentArchitect version 3.5.4. If your database is an earlier version, you must apply the

necessary Upgrade Walkthrough documents to upgrade to 3.5.4. Contact SDL

LiveContent Architect support if you do not have the necessary Walkthrough

documents to upgrade.

A server installed by the SDLLiveContent Architect InstallTool

InstallTool makes no changes to your database. However upon installation, it verifies

that a connection can be made given the current connectstring. The results ofan installation are verified entries for:

■ database name, location, user name and password

■ application, data and website paths with strict folder structures and contents

■ project name and SDL LiveContent Architect version

ATrisoft.Setup.DBUpgradeTool.Plan.xml

This file is created by SDL LiveContent Architect and describes the complete upgrade

order and is part of every SDL LiveContent Architect version.

Warning: Do not make changes to this file.

Unimplemented features of theDatabaseUpgradeTool

DatabaseUpgradeTool must know about all SDL LiveContent Architect options, features,

and environment changes however, some operations are not automated.

For reasons of security and complexity, the following operations are not automated:

■ Advanced isource permission checking

■ Changing the transaction timeout settings

■ Checking the availability of correct Microsoft components



Chapter 9

Installing desktop clientsYou can install the desktop clients with the Authoring Bridge, Publication Manager, and

Condition Manager based on the role and responsibilities of the user. The desktop clients

must have the same (matching and compatible) version of the SDL LiveContent

Architect client tool software installed, as the software installed on the server.

Desktop client software and hardwareThe desktop client systems (hardware and operating systems) and third party software

which has been tested and approved for use with SDL LiveContent Architect version are

listed.

Editors:

■ FrameMaker 9

■ FrameMaker 10

■ XMetaL 5.5

■ XMetaL 6.0

■ Arbortext 5.3

■ Arbortext 5.4

■ SDL LiveContent Create (version delivered with SDL LiveContent Architect)

Web Browsers:



■ Chrome (latest version)

■ FireFox (latest version)

Note: The browser must be configured:

■ to allow cookies.

■ to allow pop-up windows for SDL LiveContent Create when the application is

called from the SDL LiveContent Architect web client.

Client System (hardware and operating systems):


■ Windows XP (x86)

■ Windows Vista (x86)

■ Windows Vista (x64)

■ Windows 7 (x86)

■ Windows 7 (x64)

Installing the Authoring BridgeThe authoring bridge is used to access the repository using an authoring tool.

Before you begin

Before installing the Authoring Bridge, please make sure that:

■ The correct version of the .NET runtime framework is installed.

■ Any previous version of the Authoring Bridge are uninstalled first.

Note: If using XMetaL on Windows 7, you must uninstall XMetaL beforeuninstalling the Authoring Bridge.

■ When using XMetaL, ensure that Full Control permissions are granted to the Usergroup on the C:\Program Files (x86)\XMetaL and sub directories, even for userswho are defined as Local Administrator on the client PC.

About this task

You install the Authoring Bridge msi package for the xml editor software that you are

using. This is any editor that is qualified with the installed version of SDL LiveContent

Architect such as XMetaL, Arbortext Editor, or Framemaker.

Procedure

1. Double click the Authoring Bridge install package then click the Next button.

2. Enter the location where you want to install, or accept the default location.

3. You are prompted to install the Authoring Bridge for yourself, or for anyone who may

use the computer. Choose an option then click Next.

Result: The installation begins.

4. Click the Close button to exit the installation.

Note:

■ When a user launches the authoring tool after the installation, the user accountmust exist or the user cannot connect to the repository. Make certain that theuser account exists.

■ Make certain that the user has full access to the directory where the editorsoftware is installed. This can be an issue for certain editors and versions ofWindows software.

Installing desktop clients


Installing Publication ManagerThe publication manager is used to create, modify, check the status of, and produce

publications in various formats.

Before you begin

Before installing Publication Manager, you must:

■ Install the correct version of the .NET runtime framework.

■ Uninstall any previous version of the Publication Manager.

Procedure

1. Double click PublicationManagerx.x.x.msi

2. Click Next.

3. Click Next again.

4. You are prompted to install the Publication Manager for yourself, for anyone who

may use the computer. Choose an option then click Next.

5. Click Next to start the installation.

6. Click Close to exit the installation.

Installing Condition ManagerThe condition manager is used to create and manage conditions for your publications.

Before you begin

Before installing the Condition Manager tool, please make sure that:

■ All server side Condition Manager components are installed.

■ The .NET runtime framework is installed.

Procedure

1. Double click on the Condition Manager install package, ConditionManager<xx>.msi

2. Click Run.

3. Click Next to start the installation process.

4. If required, select the Enable Synchronization option then click Next.

The synchronization option enables SDL LiveContent Architect to synchronize the

set of conditions with definitions from another system, for example, such as product

configurators. Note that the synchronization process needs to be configured separately.

The option during install only makes the menu items available in the application.

5. You are prompted to install the Condition Manager for yourself or for anyone who

may use the computer. Choose an option then click Next .

Result: The installation begins.

6. When the installation is complete, click Close to exit.



Installing or upgrading SDL DITA2TrisoftYou can install DITA2Trisoft without closing other applications or restarting your system.

If you upgrade DITA2Trisoft, you do not need to uninstall the existing version.

Before you begin

The Microsoft .NET Framework 2.0 Service Pack 2 or later and Microsoft .NET

Framework 3.5.x must be installed.

Procedure

1. Click the .msi file.

Result: The installation program starts.

2. Click Next.

3. Specify installation information:

a. In the Folder field, specify the directory where the application will be

installed.

By default, the application is installed to C:\Program Files\Trisoft\

DITA2Trisoft\10.1.

b. In the Install SDLTrisoft2DITA for yourself, or for anyone who uses this

computer area, click either Everyone or Just me.

c. Click Next.

4. In the Confirm Installation window, click Next.

5. When the installation is completed, click Close.

Results

The following files are written to the directory where you installed DITA2Trisoft:

■ ResolutionList.xml

■ DITA2Trisoft.xsl

■ DITA2Trisoft executable file

■ .dll files

The documentation is written to the help subdirectory.

Documents

SDLLiveContentArchitectUpgradeGuidesdl.ssl.cdn.sdlmedia.com › file › 635419658915346017BN.pdf · Author Acolumn for Authormetadata was added to the default baseline view in Publication