Each person who needs to work with Author-it must have the Author-it program files installed on their computer. You must ensure this step is completed on each client computer.
You can install Author-it on any number of computers. The license defines how many users have access to Author-it at any one time.
After you have prepared the installation on your server, you are ready to install Author-it onto your client computers.
To Install Author-it on the Client Computers:1) Close all other Windows programs. This lets Author-it update essential components which are shared by other programs.
2) Run the Author-it Setup program to begin the installation process. The setup confirmation screen opens. Choose Next to continue.
3) Choose I Agree to accept the End User License, then choose Next to continue.
4) The Setup Wizard shows you the location where Author-it will be installed on the computer. Use the suggested settings, or browse to another location.
Select how Author-it will be installed for people using this computer then choose Next to continue:
Choose Just me to make the installation of Author-it available to you only
5) When you have completed all of the required steps choose Next to begin the installation process. Progress is shown as the components are installed.
Upgrading from a Previous Version of Author-it
Please read this procedure carefully before attempting to upgrade your existing version of Author-it. With any update, we recommend that you maintain accurate backups of your data before installing the software, and that you always test it in a separate environment before changing your production environment.
Refer also to these topics for detailed information: Upgrade Matrix - READ ME before upgrading
Minimum Server Requirements for Author-it (on page 13)
Minimum Computer Requirements - Client (see "Minimum Computer Requirements" on page 14)
Hardware and Software Recommendations for Installations (on page 15).
First determine if you are performing a major upgrade or a minor upgrade
Refer to the release notes for this software upgrade to determine any specific upgrade instructions. The release notes will clarify if the upgrade requires more procedures than normal.
A minor upgrade is from one release to a closely related release, for example from release 5.5.2 to
5.5.3.
A major upgrade is from primary release to primary release, for example from 5.xx to 6.xx What is the difference in procedure?
With a minor upgrade you can simply follow normal Windows software upgrade procedures: close the Author-it software, run the installation file, follow normal installation prompts, and on
completion re-open the Author-it software to check that it is functional. With a major upgrade, you also need to
Backup all your libraries, graphics, templates, and any other supporting files before the upgrade. When you run an upgrade, files that you have modified (such as publishing templates) should not be overwritten, while files that have not been modified should be overwritten. If using SQL Server, the library will not be backed up automatically. If the SQL database is less than 2GB in size, you are strongly advised to export it to JET first, or follow your normal backup procedure prior to upgrading the Library. Note that JET databases have a 2GB size limitation, so only SQL databases that are smaller than 2GB can be exported to JET.
Install the software into a test environment before updating your production software.
Upgrade the Library (the software will prompt you to do this when you log into Author-it Administrator).
Re-assign a license file.
To obtain upgrade software:1) Log into My Author-it and navigate to software downloads > Author-it for Windows Software> download files.
2) Save the appropriate file.
To perform a minor upgrade:1) Close Author-it.
2) Run the upgrade file and follow instructions, as for any other Windows software.
3) Open Author-it and check the software version to ensure that the upgrade was successful (Click the Help button> About Author-it....), then check the Author-it functionality.
4) After checking the upgrade, make the file available to all appropriate users so that they can also upgrade their installations.
To perform a major upgrade:1) Ensure that all users are logged out of your library, then backup all your libraries, graphics, templates, and any other supporting files before you begin.
If using SQL Server, you can backup your library by exporting it to JET provided the library is under 2GB, otherwise have your SQL Server administrator back it up for you.
2) Install Author-it into a test environment.
3) Using Author-it Administrator, open your existing test library. Author-it will prompt to upgrade your library. Choose Yes to continue (see Upgrading Libraries from earlier builds)
4) Progress is displayed while your library is upgraded. This can take some time depending on the size of your database and specifications of your computer. Do not interrupt this upgrade. Any problems are listed in the Log file while the library is being upgraded. The log file can be opened later from the \Author-it 5\Logs folder.
5) If you are using a JET database library, then we recommend that you compact your library to improve efficiency.
Additional Steps for Your Installation
The following topics provide additional information and options for your installation.
Backups
We strongly recommend stringent daily backup procedures for your Author-it data files, especially the Library database/s.
When you upgrade an earlier JET Library database so you can work with it using Author-it 5, a copy of that earlier database is automatically created before the upgrade. Otherwise, Author-it has no internal backup procedures.
There are many good backup tools available - contact your regular software and hardware supplier.
Changing Relative File Paths
The following step should be completed by the library administrator. This step is required if the Data folders are moved in a way that breaks the relative file paths (that is, the templates folder is moved out of your Data folder).
Let's look at how the paths are created. In this example, the two parts to the path are combined by Author-it to point to a Word template located on the server: \\[server
name]\Data\Libraries\Templates\Word Templates\Acme.dot
Library path: \\[server name]\Data\LibrariesRelative file paths
If you change the relative positions of the Library database and the Templates directory from Author-it's default file directory structure, you may also need to change settings in several Author-it objects (usually object templates). These settings point to files whose location is always specified
relative to the position of the Library file that you are working with.
SQL Server
If you are using a SQL Server database, the locations of files are specified relative to the Library path directory specified in the Summary section of the Author-it Administrator. Think of this as your base directory. This path points to the Libraries folder in your Data folder.
To Change File Paths:1) Start the Author-it program and log in to your Library.
You'll need to log in as a User who has sufficient permissions to edit object templates. 2) Open the object templates for these types of object, and change their relative paths if necessary:
Book object: Print tab - update the Word template field, Web tab - update the Frameset
template and Additional files (if they are used).
Index object: Web tab - update the fields in each of the sub-tab template fields (Plain HTML,
HTML Help, JavaHelp, and Oracle Help).
Table of Contents object: Web tab - update the fields in each of the sub-tab template fields
(Plain HTML, HTML Help, JavaHelp, and Oracle Help).
Media object: Web tab - update the fields for the HTML template and Additional files (if they
are used).
Customizing Each User's Styles Toolbar
For each Library, each user can customize the Styles toolbar in the Topic Editor, and assign
keystrokes to styles. You can also copy an existing user's customized styles, but only from within the same Library.
For more information see the Using Author-it Guide topic for Customizing the Styles Toolbar.
Options for Assigning a License to the Library
Before opening your library for the first time you will need to assign the license. License allocation is completed in the Author-it Administrator.
There are two License Models to choose from. In most cases you will use the option to assign the license file to your library. The license file is allocated to your primary, or main, library, and license tokens can then be allocated to any secondary libraries created from your main library.
1) Load the License File: use this option when you assign the license (see "Step 4 - Loading the License File Against Your Library" on page 38) to your primary, or source library.
-or-
2) Use an Author-it License Library: use this option to allocate license tokens from your primary library to any secondary libraries (for example, if you create a sandpit library). Tokens are automatically allocated to Target and Offline libraries when they are created.
In addition, you have the option to allocate License tokens for specific users or groups. This allows you to reserve tokens for users, or alternatively restrict token use.
Reserving tokens (Optional)
Tokens can be reserved for specific users or groups ensuring they have access to required
functionality needed to complete a project. This is done by allocating a minimum number of tokens to the group or user. The tokens can also be reserved for a specific time period using the start and finish dates.
Restricting tokens (Optional)
You can restrict the number of tokens that will be made available for groups or users. This is useful when you want to restrict the functionality for users or groups, for example, restricting which groups or users have access to Localization Manager.
Use an Author-it License Library
Once you have assigned the license to your primary library you can assign tokens to a secondary library, for example when you are working in test or sandpit libraries.
Note: Tokens for Target and Offline libraries are automatically assigned to the libraries when they are
created. When Offline libraries are checked in the tokens are returned to the primary library.
To Assign License Tokens to Secondary Libraries:1) Open your secondary library using Author-it Administrator.
2) Choose Security > Update Licenses.... The Update License window opens. Choose the option to
3) The library allocation window opens. Choose Find Library... then select the library you are
assigning tokens to. Choose OK.
4) The pathway to the library is added to the Update License window. Choose Next to complete the licensing update.
5) When the Licensing has been successfully updated Close the licensing window.
Assigning License Tokens to Users
Using Author-it's License Assignment Configuration you can reserve licenses for users, groups, or other libraries. For example, you can reserve licenses for a specific time period (days, weeks, etc) for a selected group of users, ensuring they have full access to resources needed to complete a special project.
Note: This step is optional. You only need to assign licenses when you want to reserve or restrict the
available licenses for certain users, groups or libraries.
To Assign Licenses:1) Open the library using Author-it Administrator.
2) Choose Security > Allocate Licenses.... The License Allocation window opens. 3) Select the License Token then right-click and choose New.... The License Assignment
User: assigns the token allocation to an individual user. Select the user from the drop-down list.
Group: assigns the token allocation to a group. Any users assigned to that group can use the
token. Select the Group from the drop-down list.
Note: Options in the drop-down lists for the user names and groups are populated from the
Author-it Administrator's Users and Groups.
Library: assigns the token allocation to a library. Select a Library from the Name drop-down
list, or choose the browse button to open the New Related Library window. Choose the browse button and select the library.
5) Select the Minimum and Maximum number of tokens you are assigning to this configuration.
To reserve tokens select the minimum number of tokens that will be made available.
Individual users have one token assigned, while groups and libraries can have multiple tokens assigned.
To restrict tokens select the maximum number of tokens that will be made available. As an
example, selecting 1 token will restrict usage of the functionality, while selecting 0 tokens will remove the functionality for the selected user or group.
6) Select the start and finish dates for the time period the tokens will be assigned in this configuration.
Publishing to PDF and Microsoft Word 2007 and 2010
The following tables show the settings required for publishing using specific operating systems (either 32-bit or 64-bit) and versions of Microsoft Word.
Note:
When publishing using Author-it Live, ensure the settings for Client and Live are completed: Desktop System32 (publishing folder) and Desktop SysWOW64 (publishing folder) [ReadMore (see "Author-it Live: Publishing to Word on Server 2008" on page 60)]
Add registry key and Enable Word macros [Read More (see "Author-it Client and Live: Publishing to Word 2010 (64-bit)" on page 61)]
For Word 2007 publishing, you need to type in personal details for the Microsoft Office Installation, in Word Options > Popular > Personalize Your Copy of Microsoft Office. Without these details, Word 2007 publishing fails, with an error message "Document cannot be opened by Word: Line 1080 error, Bad parameter".Builds Author-it 5.4 and Author-it Live 5.4 and later
Server Operating System
Word 2007 Word 2010 (32-bit) Word 2010 (64-bit)
Microsoft Server 2003
Client No Action No Action Does not apply
Live Publishing Server
No Action No Action Does not apply
Microsoft Server 2008 (32-bit)
Client No Action No Action Does not apply
Live Publishing Server
Desktop System32 (publishing folder)
Desktop System32 (publishing folder)
Does not apply
Microsoft Server 2008 (64-bit) (R2)
Client No Action No Action Enable Word macros
Live Publishing Server Desktop SysWOW64 (publishing folder) Desktop SysWOW64 (publishing folder)
Enable Word macros Desktop System32 (publishing folder)
Builds Author-it 5.4 and later
Desktop Operating System
Word 2007 Word 2010 (32-bit) Word 2010 (64-bit)
Microsoft Windows 7 (32-bit)
Client No Action No Action Does not apply
Microsoft Windows 7 (64-bit)
Client No Action No Action Enable Word macros
Microsoft Vista (32-bit)
Client No Action No Action Does not apply
Microsoft Vista (64-bit)
Client No Action No Action Enable Word macros
Builds Author-it 5.3.530.7964 and Author-it Live 5.3.510.7936 and earlier
Server Operating System
Word 2007 Word 2010 (32-bit) Word 2010 (64-bit)
Microsoft Server 2003
Client No Action No Action Does not apply
Live Publishing Server
No Action No Action Does not apply
Microsoft Server 2008 (32-bit)
Client No Action No Action Does not apply
Live Publishing
Desktop System32 (publishing folder)
Desktop System32 (publishing folder)
Server Operating System
Word 2007 Word 2010 (32-bit) Word 2010 (64-bit)
Live Publishing Server Desktop SysWOW64 (publishing folder) Desktop SysWOW64 (publishing folder) Registry key Macros enabled
Desktop System32 (publishing folder)
Builds Author-it 5.3.5307964 and earlier
Desktop Operating System
Word 2007 Word 2010 (32-bit) Word 2010 (64-bit)
Microsoft Windows 7 (32-bit)
Client No Action No Action Does not apply
Microsoft Windows 7 (64-bit)
Client No Action No Action Registry key Enable Word macros
Microsoft Vista (32-bit)
Client No Action No Action Does not apply
Microsoft Vista (64-bit)
Client No Action No Action Registry key Enable Word macros
Author-it Live: Publishing to Word on Server 2008
Description:
When publishing to Microsoft Word or PDF, an additional folder is required by Windows Server 2008 (32-bit), Server 2008 (64-bit), or Server 2008 R2 (64-bit). If this folder does not exist on the server the publishing job can fail with the following error shown in the publishing log.
'Document cannot be opened by word. Error: Object variable or With block variable not set. Publishing finish (Finished 11:44:03 AM)
Publishing job failed.'
Author-it's recommended solution:
To enable publishing to complete successfully, create a "Desktop" folder in the location specified for your server operating system:
For Windows Server 2008 (32-bit):C:\Windows\System32\config\systemprofile
For Windows Server 2008 (64-bit) or Server 2008 R2 (64-bit) and Office 2010 (32-bit):C:\Windows\SysWOW64\config\systemprofile
For Windows Server 2008 (64-bit) or Server 2008 R2 (64-bit) and Office 2010 (64-bit):Personal Details requirement for Author-it Publishing to Word 2007
For Word 2007 publishing, you need to manually type in personal details for the Microsoft Office Installation, in Word Options > Popular > Personalize Your Copy of Microsoft Office.
Note: Without these details, Word 2007 publishing fails, with an error message "Document cannot
be opened by Word: Line 1080 error, Bad parameter".
Author-it Client and Live: Publishing to Word 2010 (64-bit)
Description:
Microsoft Word 2010 64-bit requires an additional registry key when publishing to Word or PDF using Author-it Client 5.3.530.7964 (and earlier) and Author-it Live 5.3.510.7936 (and earlier). If the
registry key does not exist on the server or computer used for publishing, the following error may be displayed:
'Object reference not set to an instance of an object.'
Author-it's recommended solution:
To publish to Word or PDF with Microsoft Word 2010 64-bit add the following registry key and
enable macros in Word's Trust Center.
To Add the Registry Key:1) Add the following registry key and value to the computer running Author-it, or the publishing server if using Author-it Live, or both:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Word \Security
2) Add a string value under this called "Level" with the data set to "1".
Setting Up Author-it Using an Application Server
Note: This step is optional, and only required if using Author-it in an Application Server environment.
Windows Terminal Services, Citrix MetaFrame and Citrix Presentation Server allow applications to be distributed over a wide area and used on many different operating systems. The Citrix products even allow Author-it to be run on Macintosh or Unix computers.
Put simply, many instances of Author-it run on an Application Server, which sends information to the Client computers for them to display on screen. The Client computers in return send mouse click, key stroke and clipboard information back to the Application Server.
Working with an Application Server creates additional installation requirements:
Each Client computer should see the Library and external files (HTML templates etc) at the same location
Each Client computer must publish to their own publishing folder
Each Client computer must maintain their own dictionaries
Each Client computer must create their own separate log files when importing and publishing These requirements are best addressed using a login script.Note: Before Author-it is installed on the Application Server, the File Server and Database Server
should be installed and running.
User Login Script
All users opening an Author-it session from a Client Computer working through an Application Server