User’s Guide — LinkFixer Advanced

Requirements

OpenText Versions: 10.0–10.5

OpenText Modules: Web Services must be installed, enabled and correctly configured.

Operating Systems: Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2012.

Introduction

There are two ways to move files into OpenText while preserving the integrity of the links contained in the files. The two options are to use the LinkFixer Advanced Move/Rename process, or to use the LinkFixer Advanced Inoculate and Cure processes.

One option is to use the LinkFixer Advanced Move/Rename process to move the files into OpenText. This will automatically preserve the links during the migration. In many cases this is the simplest and fastest way to move files into OpenText. Moving the files and fixing the links in the files is accomplished in a single step.

If you wish to use LinkFixer Advanced to move the files into OpenText, use the procedures described in the following section and in the “Move and Rename” sections of this User’s guide.

There are other utilities for moving files into OpenText, but they will not protect and preserve your links. If you wish to use some other utility to move and rename files and folders, your second option is to use the LinkFixer Advanced Inoculate process before the migration and the Cure process after the migration. Using this method, links will be temporarily broken during the migration, but will be repaired by the Cure process. The steps of the Inoculate and Cure method are outlined in one of the following sections of this Appendix.

Note: Regardless of which method you decide to use to move folders and files into OpenText, you will need to perform the first step below — connecting LinkFixer Advanced to the OpenText server.

Moving Files into OpenText Using LinkFixer Advanced

Connecting LinkFixer Advanced to the OpenText server

In order for LinkFixer Advanced to be able “see” folders and files in OpenText, you must first provide LinkFixer Advanced with the information it needs to connect to the OpenText content server and Web Services module. Check with your IT manager to ensure that the Web Services module is installed and activated.

Important: If you have more than one OpenText server, be sure to map each OpenText site that contains files that LinkFixer Advanced will need to access.

The procedure you use to connect to OpenText server is the same regardless what operating system your computer is running. This procedure is outlined below.

Mapping the Network Location

If your OpenText site has not already been mapped in the LinkFixer Advanced “Network Locations” screen, do the following:

1. Launch LinkFixer Advanced (if it is not already running).
2. Select the “Network Locations” button on the ribbon menu.
3. Select {Add Open Text}.
4. Fill in the server URL, the name of the content server, and the name of the Web Services module. It is possible that the default values for Content Server and Web Services will work with your server. If not, you will need to ask your IT manager for the data.
5. Select the link format you want LinkFixer Advanced to use when it fixes links within files. The drop-down selection menu provides several of the most frequently used formats. Click {Customize} if you wish to specify a link format that is not available in the drop-down menu. The most commonly used format is selected by default. If you are uncertain, please contact your IT manager.
6. Specify the type of authentication to use.

Note: Unless your OpenText user authentication information is exactly the same as your log-in and password for the computer you are using to run LinkFixer Advanced, you will need to select “Use different credentials for authentication” and enter your OpenText credentials (user name and password).

1. Click the “Test” button to test the settings you entered above. If the connection test is successful, you will be able to use the LinkFixer Advanced “Select Parent Files” screen to select folders and files for processing. If the connection test is not successful, carefully note and correct the resulting error messages.

Important: You must successfully connect to the OpenText content server and Web Services module (“les-services”) in order for LinkFixer Advanced to be able to access and process files in OpenText. The most common connection issues occur when web services (les-services) are not installed, not correctly configured, or have been renamed to a file name other than “les-services”. Please ensure that you have “les-services” configured as a virtual directory in IIS, that you are using a 32-bit version of ASP.net, and that the version of ASP and .NET used by IIS is the same version as is used by les-services.

For further details on setting up web services, please contact OpenText support. Enabling web services for LiveLink (version 9.7) is also possible but is somewhat more complicated. Please refer to the following OpenText technical bulletin for instructions on enabling web services for LiveLink:

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=15628200&objAction

=WikiView&vernum=10

Scanning Files

From the “Home” screen, select {Scan}, and step through the process of scanning all the files you intend to move to the OpenText site.

Move/Rename Files

From the “Home” screen, select “{Move/Rename}”.

Move/Rename Options

On the “Move/Rename Options” screen, ensure that the option “Automatically correct slash orientation in links” is checked. This causes LinkFixer Advanced to automatically change Windows file system backslashes to hyperlink (https://) forward slashes.

Move and Rename Rules

Create as many rules as necessary to specify the files you want to move into OpenText, using the “Define Rename Rule” screen as shown below.

For more details on creating rename rules, please refer to the Move/Rename section of “Chapter 6 — What Do You Want LinkFixer Advanced to Do?” of this User’s guide.

Preview Files to be Moved/Renamed

Review the listed files to be sure they are complete and correct.

Perform Move/Rename

Click the {Run} button to perform the Move/Rename function.

Then review the Move/Rename Summary report for details of the process.

Using Inoculate and Cure when Migrating Files into OpenText

If you choose to use a different software tool to do your migration, then you’ll need to Inoculate the files first, using the procedures described in the “Results Summary” section. Once you have successfully inoculated your files, you may use any techniques and/or software utilities you wish to move the inoculated files into the new directory structure in OpenText. Then use the procedures described in the “The Cure“ sections of this User’s guide to restore the links in the files you moved into OpenText.

Important Note: Before using Cure in OpenText, we strongly recommend that you temporarily disable the synchronization feature in OpenText Explorer or Enterprise Connect (or both). We have found that automatic synchronization of files by these utilities can cause errors during the Cure process.

To summarize, the migration to OpenText using LinkFixer Advanced’s Inoculate and Cure processes consists of these four steps:

Connect to the OpenText, as explained and illustrated in the previous section.

Prepare the files for the migration using the LinkFixer Advanced Inoculate process.

Move the files into OpenText by any means you choose.

Re-link the files using the LinkFixer Advanced Cure process.

Versioning in OpenText

One widely used feature of OpenText is its ability to track and store successive versions of documents. LinkFixer Advanced has been designed to work with this feature of OpenText. If version control is enabled in OpenText, LinkFixer Advanced features that write changes to OpenText files (Inoculate, Cure, Move/Rename and Modify Links) will cause a new version to be created in OpenText. OpenText will create this new version of the file with the current date and time of the modification, and with the “Modified By” field populated with the name of the user who is running LinkFixer Advanced.

On-going Link Maintenance

The best solution for broken links is to keep all files within OpenText inoculated using LinkFixer Advanced. When broken links do occur, they can then be easily repaired using the LinkFixer Advanced Cure process.