deploying content server on windows 2008 64 bit and ie 8

Product:

Version:

Task/Topic:

Audience:

Platform:

Document ID:

Updated:

2010-04-19

Case Study

Deploying Content Server 9.7.1 on Microsoft® Windows Server 2008 x64 Edition

Open Text Content Server (formerly Livelink ECM – Enterprise Server)

9.7.1

Deployment

Administrators

Windows Server 2008 x64 Edition, SQL Server 2005

500060

Document Title

C h a m p i o n T o o l k i t D o c u m e n t w w w . o p e n t e x t . c o m

Case Study Deploying Content Server 9.7.1 on Microsoft® Windows Server 2008 x64 Edition

Contents Summary ...................................................................................................................... 1 Known Issues .............................................................................................................. 2 Case Study Scenario .................................................................................................. 4

The Production Environment .................................................................................. 4 End Goal ................................................................................................................. 4

Preinstallation Checklist ............................................................................................ 5 Review the Requirements for Content Server 9.7.1 ........................................ 5 Apply All Updates to Windows 2008 ................................................................ 5

Database Client ......................................................................................... 5 Index location ............................................................................................ 5 Internal or External Storage ....................................................................... 5

Phase One: Setup IIS 7 ............................................................................................... 6 Phase Two: Install Content Server 9.7.1 ................................................................. 16 Phase Three: Configure IIS 7 ................................................................................... 20 Phase Four: Configure Content Server 9.7.1 ......................................................... 26 Phase Five: Configure WebDAV .............................................................................. 33

Windows Vista Clients – Install WebDAV Extension for IIS 7 ........................ 48 Phase Six: Test Content Server ............................................................................... 53

Internet Explorer 6 Clients ............................................................................. 53 Internet Explorer 8 on Windows XP Clients. .................................................. 57 Internet Explorer 8 on Windows Vista Clients. ............................................... 62

Phase Seven: Applying the Latest Cumulative Patch ........................................... 72

Document Title Case Study Deploying Content Server 9.7.1 on Microsoft® Windows Server 2008 x64 Edition

Summary This document provides a technical overview of the steps for installing Content Server (formerly known as Livelink ECM – Enterprise Server) 9.7.1 on the Microsoft® Windows Server 2008 x64 Edition platform. This case study is not intended to replace the manuals distributed with the Content Server software, but rather to supplement the information in the official manuals. It is targeted for Livelink Administrators (the person or people responsible for deploying, administering, and maintaining Content Server). This guide presumes that you possess the following knowledge and skills:

• An understanding of Livelink's purpose within your organization and how it will be used

• Familiarity with the Windows Server 2008 x64 Edition operating system, specifically Internet Information Server (IIS) 7 and any legacy products or systems that will be integrated with Livelink

• Web server administration skills

• Database administration skills (or a database administrator to assist you)

Customers considering deploying Content Server 9.7.1 on Windows Server 2008 x64 Edition should review this document as well as the established documentation before proceeding with the installation.

Your environment may differ in the mix of optional modules, patches, database, and operating system platforms, as well as architecture. Information here is specific to this particular case study scenario.

Customers who are planning on moving their production environment to the Windows Server 2008 x 64 Edition platforms may also consider a contract under a statement of work to consult with our Services groups.

NOTE: In order to make the WebDAV component of Content Server compatible with Internet Explorer 8, a patch is required and is available on the Open Text Knowledge Center—pat09392.

NOTE: Both the Latin-1 and UTF-8 version of Content Server will work with Windows 2008 x64 Edition. If you are a new customer and this is your first deployment of Content Server, it is recommended that the UTF-8 version of Content Server 9.7.1 be deployed as opposed to the Latin-1 edition. Support for Latin-1 will end with 9.7.1, as the future version of Content Server (10.0) will be UTF-8 only. Switching from Latin-1 to UTF-8 will require a Conversion Tool, which is slated for release later this year.

C h a m p i o n T o o l k i t D o c u m e n t w w w . o p e n t e x t . c o m 1


DISCLAIMER: All procedures and any sample code in this Case Study is specific to the scenario presented in the document and delivered as is, and is for educational purposes only. It is presented as a guide to supplement official Open Text product documentation. Procedures on deployments using other operating systems and database application platforms may differ in some areas. Deployments with additional optional modules may also add to the complexity.

Known Issues Open Text has conducted limited testing on the Windows Server 2008 SP2 x64 operating system for Content Server 9.7.1 and the modules in the Content Lifecycle Management bundle, including:

• Open Text Archive and Storage Services • Recycle Bin

• Imaging • WebDAV

• Directory Services • Web Forms

• eLink • Attribute Extensions

• Content Archiving • Doculink

• Livelink Explorer Professional • Activator for SAP Solutions

• Records Management • Forms

The testing performed against Content Server 9.7.1 deployed on Windows Server 2008 SP2 x64 operating system has revealed a number of issues. In Content Server 9.7.1 deployments, the following issues occur:

Knowledge Base Article Details

KBA 17581828 Enterprise Server - Unable to Install eLink Server on Microsoft Windows 2008 64-bit Operating System

KBA 17581374 Enterprise Server - Unable to Use Workflow Painter on Client Computer Running 64-bit Windows 2008 Server

KBA 17581830 Enterprise Server – "Double Escape Sequence" Error Message Appears When You Attempt View Page Containing Custom View


https://knowledge.opentext.com/go/17581828



Document Title



Open Text plans to resolve the known issues mentioned above in the Content Server 10 release. At their discretion, customers may engage Open Text Global Services to address these issues before the next release.

Document Title



Case Study Scenario

The Production Environment This is a new deployment of Content Server. There is a new server with Windows Server 2008 x64 Edition installed. In addition, SQL Server 2005 SP3 is also installed and configured. The database in this scenario is local. In the majority of situations, the database application will be on another physical server. In these cases, the SQL Client software (which matches the server version) must be installed, and connectivity to the database server verified in advance. Internet Information Server (IIS) 7.0 is not set up at this point.

End Goal Successful implementation of a UTF-8 Content Server 9.7.1 to run in IIS 7 on the 64-bit Windows Server 2008 x64 Edition SP2 platform. The system will be accessible from Windows XP clients with Internet Explorer 6 and Internet Explorer 8. The system will also be accessible from Windows Vista clients with Internet Explorer 8.

Document Title



Preinstallation Checklist

Review the Requirements for Content Server 9.7.1 The first step is to determine what the operating system and database requirements are for Content Server 9.7.1. Hardware requirements for Content Server, as a rule, match whatever the platform operating system specifications are.

Key items to ensure is sufficient RAM for Search and Indexing, as well as disk space to house the Index.

Visit the Open Text Knowledge Center to review the latest Release Notes and Install/Upgrade Guides for the Content Server 9.7.1 version.

Download the following:

• UTF-8 version of Content Server 9.7.1

• WebDAV Module version 3.6.1

• Latest cumulative patch for Content Server 9.7.1

• Patch 09391 and patch 09392 from the Open Text Knowledge Center.

Apply All Updates to Windows 2008 Download and apply any patches or service packs to Windows 2008 Server in advance of setting up and configuring IIS 7.

Database Client

The client database software (Oracle or SQL Server) is installed and configured, and connectivity to the database verified.

Index location

Initially, the Content Server index should not be located under the default or Content Server installation (OTHOME) folder. The index should reside in its own folder outside of the OTHOME tree and on a drive local to the Admin server (as opposed to a mapped drive or a SAN).

Internal or External Storage

Internal Storage is the term used when all content is housed within the database itself. External Storage is the term used when content is stored outside of the database (on a SAN for example).

In this scenario, the database application server—SQL Server 2005—is installed locally. Three directories have been created in advance on the system:

• C:\data - This folder will house the Content Server database files.

• C:\index - This folder will house the index folders.

• C:\efs - This folder will house content stored outside of the database.

Content Server will be installed to its’ default directory (C:\opentext). The first phase is to set up and configure Internet Information Server 7.0 (IIS7).

https://knowledge.opentext.com/knowledge/llisapi.dll


Phase One: Setup IIS 7 The first step is to add the Web Server Role to Windows 2008 x64.

If you are using the default Start Menu (Figure 1):

From the Console, click Start, Administrative Tools, and then Server Manager.

Figure 1- Default Start Menu

If you are using the Classic Start Menu (Figure 2):

Click Start, Programs, Administrative Tools, and then Server Manager.

Figure2- Classic Start Menu



The Server Manager in Windows Server® 2008 replaces the older management consoles, such as: Configure Your Server and Manage Your Server. In the Server Manager, you configure your server for deployment by installing logical software packages known as roles, role services, and features.

1. From the Server Manager Roles Summary area, click Add Roles.

Figure 3

2. This launches the Add Roles Wizard. Click Next.

Figure 4



3. Select Web Server (IIS).

Figure 5

4. Click Add Required Features.

Figure 6



5. Click Next.

Figure 7

6. Click Next.

Figure 8



7. Under the Application Development area, select CGI, ISAPI Extensions, and ISAPI Filters.

Figure 9

8. Scroll down to the Management Tools area and select IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility, and IIS 6 Scripting Tools to install all backwards compatibility components.

Figure 10

C h a m p i o n T o o l k i t D o c u m e n t w w w . o p e n t e x t . c o m 1 0


Click Next.

NOTE: This document is not a manual for configuring IIS in general, only features required for Content Server.

NOTE: In the event Enterprise Web Services is going to be installed, then select .NET Extensibility as well.

9. Review the list of role services or features, and click Install.

Figure 11



10. When the installation is complete, click Close.

Figure 12

Launch the Internet Information Services Manager.

If you are using the default Start Menu:

From the Console, click Start, Administrative Tools, and then Internet Information Services (IIS) Manager.

If you are using the Classic Start Menu:

Click Start, Programs, Administrative Tools, and then Internet Information Services (IIS) Manager.



Figure 13

11. Click the plus sign (+) sign beside the server name, and then click on Application Pools (Figure 14).

Figure 14

12. Click Add Application Pool. Enter a meaningful name, for instance, Content Server. From the .NET Framework version drop-down list, select No Managed Code. Click OK.

Figure 15



13. Select the Content Server Application Pool. Next click Advanced Settings.

Figure 16

14. In the Enable 32-Bit Applications drop-down menu, select TRUE. Click OK.

Figure 17

15. Click on the plus sign (+) beside Sites, and click Default Web Site. Double-click MIME Types.

Figure 18



16. Click Add.

Figure 19

17. In the File name extension box, type .properties, and in the MIME type box application/octet-stream, and then click OK.

Figure 20

The initial setup of IIS 7 is complete. Next, Content Server will be installed.



Phase Two: Install Content Server 9.7.1 If this is a new deployment, download Content Server 9.7.1 UTF-8 for Windows from the Open Text Knowledge Center. It is recommended that the UTF-8 version of Content Server 9.7.1 be deployed as opposed to the Latin-1 edition. Support for Latin-1 will end with 9.7.1, as the future version of Content Server (10.0) will be UTF-8 only. Switching from Latin-1 to UTF-8 will require a Conversion Tool, which is slated for release later this year. If there is an existing deployment of Content Server 9.7.1, download a version of Content Server 9.7.1 that matches your deployment.

1. Double-click on the executable to initialize the setup. Click Run.

Figure 21

2. The Setup Wizard launches. Click Next.

Figure 22



3. Select the check box for the License Agreement, and click Next.

Figure 23

4. Select Install a new instance, and click Next.

Figure 24

5. Accept the default path C:\OPENTEXT, and click Next.

Figure 25



6. The defaults for Service Name, DNS Name, HTTP Server Name, and HTTP Port Number are fine; click Next.

Figure 26

7. The default for the URL Prefix /img/ is fine; click Next.

Figure 27

8. Accept the default ports, and click Next.

Figure 28



9. Click Next to commence Installation.

Figure 29

10. Once the installation is complete, click Next to start the services and open the Mapping file.

Figure 30

11. The Mapping file references are used to create the virtual directories in IIS 7. Minimize this window. Click Finish to complete the Setup Wizard.

Figure 31



Phase Three: Configure IIS 7 The next step is to set up and configure the virtual directories in IIS 7 for Content Server 9.7.1. Return to IIS 7 Manager by maximizing its window.

1. Right-click on the Default Web Site, and then click Add Virtual Directory.

Figure 32

2. Using the Mapping file as a reference, set up the img virtual directory first as illustrated in Figure 33.

Figure 33



3. Next, right-click Default Web Site once again, and click Add Application.

Figure 34

4. Once again, using the Mappings file as a reference set up the livelink virtual directory as illustrated in Figure 35. Click Select.

Figure 35

5. In the Application Pool drop-down list, select the Content Server application pool and click OK, and then click OK once again.

Figure 36



6. On the IIS Manager page, click on the Server name.

Figure 37

7. Next, double-click the ISAPI and CGI Restrictions icon.

Figure 38

8. Right-click in the middle of the pane, and click Add.

Figure 39



9. Navigate to the c:\opentext\cgi\ folder, and then from the drop-down list on the bottom right, select All files (*.*).

Figure 40

10. Select the livelink.exe file. Select Allow extension path to execute.

Figure 41

11. Repeat the process once more for the llview.exe file, and for the llisapi.dll file.

Figure 42

The description fields can be left blank, or you can enter a meaningful name.



12. When complete, the livelink.exe, llview.exe and llisapi.dll files should be listed as Allowed.

Figure 43

13. Click Default Web Site, and then double-click Handler Mappings.

Figure 44

14. Click Edit Feature Permissions.

Figure 45

15. Select the Execute check box as illustrated in Figure 46. Click OK.

Figure 46



16. The .exe and .dll extensions are now enabled for the Default Web Site. The final configuration of Content Server can now proceed.

Figure 47



Phase Four: Configure Content Server 9.7.1 The next phase is to complete the setup of Content Server 9.7.1. The system passwords, database, External File Store, and index will be set up and configured.

1. Launch Content Server for the first time by doing one of the following:


From the Console, click Start, All Programs, Livelink Enterprise Server 9.7.1 (livelink), and then Livelink Administration.


Click Start, Programs, Livelink Enterprise Server 9.7.1 (livelink), and then Livelink Administration.

Since this is the first time Content Server has been launched, the Configure Server Parameters page loads (Figure 48). Enter a new password in the Administrator Password and Verify Password boxes, and then scroll down to the bottom of the page.

Figure 48

NOTE: There are several Server Parameters options available on the Configure Server Parameters page. Only the bare minimal are addressed in this Case Study. Please refer to your user documentation for more details on the other parameters.



2. In the License Key area, enter your company name, and then select the expiration date of the license, the number of users, and finally, the License Key itself. All of the information must match that which was issued in order for the key to work. When complete, click Save Changes.

Figure 49

3. The Database Administration page loads next. Click Create New Database.

Figure 50

4. Since the database platform is SQL Server 2005, the appropriate selection is made. Click Continue.

Figure 51



5. Enter the credentials for connecting to the database server as “sa,” then click Log-in.

Figure 52

6. Next, click the link to the Microsoft SQL Server Maintenance page.

Figure 53



7. Click Create a New Microsoft SQL Server Database.

Figure 54

8. Give the database a name, and create the database file in the data folder created earlier. The file sizes are for illustrative purposes only. Create the log file in the same folder as the database. When complete, click Create Database.

Figure 55



9. Click Create a New User.

Figure 56

10. Create a user name that Content Server will use to access its own database. Select the new database from the drop-down list, and click Create User.

Figure 57

11. Click Return to previous page.

Figure 58



12. Since there will be an External File Store, select External Document Storage, and enter the path to the folder created earlier to house the EFS—c:\efs. Click Create Tables when complete. This may take some time to complete.

Figure 59

13. Once the database tables are created (this may take a few moments) the screen in figure 60 will load. Enter the password for the Livelink Administrator (‘livelink’ by default) and click Log-in.

Figure 60

14. The Install Modules page loads next. Scroll down to the bottom of the page, and click Continue. Do not install any of the Installable modules at this point. WebDAV will be set up after the Index is set up. For eLink, and CAP Connector, please refer to the standard documentation.

Figure 61



15. Next the setup page for the Enterprise Data Source folder appears. This is where the data flow and index partition will reside. By default, it is created under the Content Server installation folder. It is recommended that the indexes be housed outside on the Content Server folder structure. Since a root folder was created earlier to house the Index, modify the paths and direct them to the new location (c:\index). When complete, click Create Processes.

Figure 62

16. When setup has completed successfully, click Continue. The Content Server and database setup is complete.

Figure 63

17. Next the WebDAV module will be installed and configured. Click Admin Home.

Figure 64



Phase Five: Configure WebDAV The next phase is to complete the setup of WebDAV. The module will be installed, configured in IIS, and tested. The version of WebDAV that ships with Content Server 9.7.1 will not be installed. Instead the latest version WebDAV 3.6.1 will be installed. Locate and run the installer for WebDAV 3.6.1 downloaded earlier from the Knowledge Center. Allow it to download into the Administrator download folder or one of your choosing.

Once the download is complete, some cleanup and preparation of the Content Server folder will be done first.

1. Right-click the Start button and click Explore. Navigate to the C:\OPENTEXT folder.

Figure 65



2. Create a new folder called patch.

Figure 66

3. Select and delete the weblink360 folder.

Figure 67



4. Next double-click the staging folder to open it.

Figure 68

5. Select and delete the webdav_3_6_0 folder.

Figure 69



6. Open the folder where WEBDAV_3.6.1_WIN.exe was downloaded to. Double click WEBDAV_3.6.1_WIN.exe.

Figure 70

7. Click Run.

Figure 71



8. Click Next.

Figure 72

9. Click Next.

Figure 73

10. Click Finish.

Figure 74



11. On the Admin page, click Show As Tabs. This will present a compact view of the Administration sections available.

Figure 75

12. Click in the Module Administration area, and click Install Modules.

Figure 76



13. Select the check box for Livelink WebDAV, and click Install. You may be asked to log on again.

Figure 77



14. Accept the default name, and click Continue.

Figure 78

15. DO NOT click Continue again. CLOSE this browser window.

Figure 79

NOTE: The WebDAV installer was not initially designed to set up on Internet Information Server 7. It was designed for Internet Information Server 6. The ISAPI filter installed will be removed. Two patches will be applied next to update the WebDAV installer for IIS7. The ISAPI filter will then be reinstalled automatically.

16. Click Start, Run and type services.msc. This shortcut will launch the Services control panel. Select the Livelink Server service and stop it. The two WebDAV patches will now be applied

Figure 80



17. Extract pat09391 first.

Figure 81

18. Move the module and weblink361 folders over to the c:\OPENTEXT\ folder, and replace all the files.

Figure 82



19. Next, move the pat09391.txt file into the c:\OPENTEXT\patch\ folder.

Figure 83

20. Next extract pat09392.

Figure 84

21. Open the module folder. Delete the webdav_3_6_0 folder, since we are patching 3.6.1.

Figure 85



22. Move up one level, then copy the module and support folders over to the C:\OPENTEXT\ folder, and overwrite any files.

Figure 86

23. Next move the pat09392.txt file to the c:\OPENTEXT\patch\ folder.

Figure 87

24. Next, start the Livelink Server service.

Figure 88



25. Launch Content Server by doing one of the following:


From the Console, click Start, All Programs, Livelink Enterprise Server 9.7.1 (livelink), and then Livelink Administration.


Click Start, Programs, Livelink Enterprise Server 9.7.1 (livelink), and then Livelink Administration.

26. Log on, and click Show as Tabs.

Figure 89

27. Select the WebDAV Administration section, and click Configure Web Server.

Figure 90

28. Click Configure Local Web Server.

Figure 91



29. Click Run the Installer.

Figure 92

30. Click Run.

Figure 93

31. Click Run.

Figure 94



32. Click Next.

Figure 95

33. Click Yes.

Figure 96



34. Click Yes.

Figure 97

35. Click OK. The WebDAV Extension for IIS 7 is for Windows Vista Clients only. This will be dealt with in the next section.

Figure 98

36. The installer will restart the Web Server. Click Finish.

Figure 99



37. Click Admin Home.

Figure 100

WebDAV setup and configuration is now complete. If there are Windows Vista clients in your environment, follow the procedure below to install and configure the WebDAV Extension for IIS7. Otherwise, move on to Phase Six, where the system will be tested.

Windows Vista Clients – Install WebDAV Extension for IIS 7 For compatibility with Windows Vista clients, the IIS 7 Web server must be configured to “Enable WebDAV at the Root”. For more information on this feature see Section 2.2 of the Configuring the Web Server of the WebDAV ECM – Installation and Administration Guide.

Versions of IIS that precede IIS 7 (including 5.1, 6.0, and 6.1) ship with this functionality already pre-installed and configured. For IIS 7 to include this functionality, a Web server extension called WebDAV Extension for IIS 7 must be installed and configured.

This section describes the steps for installing and configuring the WebDAV Extension for IIS 7. The WebDAV Extension for Windows Server 2008 x64 SP2 is available from Microsoft at:

http://go.microsoft.com/?linkid=9655651

1. Download the webdav_x64_75.msi file into your download folder. Run the executable.

Figure 101


http://go.microsoft.com/?linkid=9655651


2. Accept the License Agreement and click Install.

Figure 102

3. Upon completion click Finish.

Figure 103

4. Open the IIS Manager. In the Connections pane, expand the Sites node in the tree, and then click on the Web server site (Default Web Site). Double-click the WebDAV Authoring Rules feature.

Figure 104



5. When the WebDAV Authoring Rules page appears, if Enable WebDAV is shown in the Alerts pane, then click Enable WebDAV. If Disable WebDAV is shown in the Actions pane then WebDAV is already enabled.

Figure 105

6. Click Add Authoring Rule in the Actions pane.

Figure 106



7. When the Add Authoring Rule dialog box appears, click Specified content and type “/” for the specified content. Choose All users to specify that the rule applies to all users. Select Read, and Source for the permissions and then click the OK button.

Figure 107

8. Click the WebDAV Settings in the Actions pane.

Figure 108



9. When the WebDAV Settings page appears, set the Allow Anonymous Property Queries behavior to True. Set the Allow Property Queries with Infinite Depth behavior to True. Click Apply in the Actions pane.

Figure 109

The server is now ready for the Windows Vista clients.



Phase Six: Test Content Server The next phase is to test the setup of WebDAV. This will be completed from a client machine. The llisapi.dll will be used for this test. WebDAV functionality will be tested as well as the Workflow Map. An error message will be deliberately generated in the Workflow Map to ensure any errors generated reach the end user.

Ensure that the Windows clients all have Java installed, which is available at www.java.com.

NOTE: In a Windows environment, with IIS as the default Web server, the use of livelink.exe in the URL is not common practice. Instead the use of llisapi.dll is employed in order to enhance performance. Requests to Content Server are handed off to the Web server itself, which avoids tying up one of the Content Server threads (for instance, while downloading or uploading a large file). For Further information, see: Livelink™: CGI • EXE versus LLISAPI.dll versus Servlet Discussed

Internet Explorer 6 Clients 1. From a client machine, enter the URL to the Content Server, and use the

llisapi.dll to log on. The performance is superior to using livelink.exe.

Figure 110

2. A Drag & Drop tab should appear. Click on the tab.

Figure 111


https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/744073/2120338/2120999/6849437/Application_Note_-_Livelink_CGi_EXE_versus_LLISAPI.dll_versus_Servlet_Discussed_%28Ver_2_Updated_Mar_2008%29.pdf?nodeid=14182433&vernum=-2

https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/744073/2120338/2120999/6849437/Application_Note_-_Livelink_CGi_EXE_versus_LLISAPI.dll_versus_Servlet_Discussed_%28Ver_2_Updated_Mar_2008%29.pdf?nodeid=14182433&vernum=-2


3. Once it loads, the screen should appear exactly as illustrated in figure 112.

Figure 112

4. Test WebDAV by dragging a file from the local system and dropping it in the empty pane. The file should appear in the pane. When complete, click Continue.

Figure 113

Try opening the file, deleting the file and then adding the file back in, WebDAV testing is complete. Next the Workflow Map will be tested.



5. From the Add Item drop-down menu, click on Workflow Map.

Figure 114

6. Enter a name for the Workflow Map, and click Add.

Figure 115

7. Click the Functions menu for the new Workflow Map, and click Edit.

Figure 116



8. Add a couple of items in the map.

Figure 117

9. Drag the second item on top of the first. This will generate an error message, which confirms that Workflow Maps and any error messages generated are working properly and appear to the user.

Figure 118



Internet Explorer 8 on Windows XP Clients. For Internet Explorer 8 (IE 8) ensure that the Windows clients all have Java installed, which is available at www.java.com. Do the following steps to confirm IE 8 operability.

10. Enter the URL to the Content Server, and use the llisapi.dll to log on. The performance is superior to using livelink.exe.

Figure 119

11. Log on to Content Server. A Drag & Drop tab should appear. Click on the tab.

Figure 120



12. An ActiveX Control will need to be downloaded. Click on the yellow bar to install.

Figure 121

13. Click Yes.

Figure 122

14. Once it loads, the screen should appear exactly as illustrated in figure 123.

Figure 123



15. Test WebDAV by dragging a file from the local system and dropping it in the empty pane. The file should appear in the pane. When complete, click Continue. Try opening the file, and deleting the file. When complete, add the file back, and then click Continue.

16. From the Add Item drop-down menu, click Workflow Map.

Figure 124


Figure 125




Figure 126


Figure 127




Figure 128



Internet Explorer 8 on Windows Vista Clients. For Internet Explorer 8 (IE 8) ensure that the Windows Vista clients all have Java installed, which is available at www.java.com. Do the following steps to confirm IE 8 on Windows Vista operability.

21. Enter the URL to the Content Server, and use the llisapi.dll to log on. The performance is superior to using livelink.exe.

Figure 129

22. Log on to Content Server. From the Tools dropdown menu in Internet Explorer, select Internet Options.

Figure 130



23. Click the Security tab, and then select Trusted Sites.

Figure 131

24. Click Sites. If you are using https, then clear the Require server verification (https:) for all sites in this zone check box. Click Add to add Content server to the Trusted Zone. Click Close to complete.

Figure 132



25. Click Custom Level.

Figure 133

26. Scroll down to the Miscellaneous area. Scroll within this section until the Launching programs and files in an IFRAME setting are reached. Select Enable. Click OK.

Figure 134



27. Click Yes, and then click OK to return to the Content Server page.

Figure 135

28. From the Enterprise drop-down menu, click Properties, and then WebDAV.

Figure 136

29. Highlight the WebDAV URL: and press CTRL+C to copy it to the clipboard.

Figure 137



30. Minimize the browser window. Double-click on Computer.

Figure 138

31. Click Map network drive.

Figure 139



32. Paste the WebDAV URL from the clipboard into the Folder: box, and then click Finish.

Figure 140

33. Enter the Content Server Admin credentials. Click OK. The contents of WebDAV will now appear as a mapped drive. In this example, drive Z.

Figure 141



34. Test WebDAV by dragging a file from the local system and dropping it into the mapped drive. The file should appear in the pane. When complete, try opening the file, and deleting the file. When complete, add the file back.

35. Maximize the browser window and return to the Enterprise workspace. Click on the Drag & Drop tab. The screen should appear as illustrated below.

Figure 142


Figure 143




Try opening the file, and deleting the file. When complete, add the file back, and then click Continue.

38. From the Add Item drop-down menu, click on Workflow Map.

Figure 144


Figure 145




Figure 146


Figure 147




Figure 148

The setup of Content Server 9.7.1 is complete. Next the latest cumulative patch will be applied.



Phase Seven: Applying the Latest Cumulative Patch The final phase is applying the latest cumulative patch to Content Server. In order to do this, a complete backup must be made. The backup will include the following:

• The Database

• The External File Store (EFS)

• The Index

• The Application Folder (C:\OPENTEXT\)

The backup must be a snapshot of all the above elements from the same time frame.

Once the backup is complete, extract the latest cumulative patch downloaded earlier from the Open Text Knowledge Center into a temporary folder outside of Content Server.

Once complete, the Livelink Server services must be stopped, as well as the Web Server service.

1. Click Start, Run and type services.msc. This shortcut will launch the Services control panel. Select the Livelink Admin service and stop it. Next select the Livelink Server service and stop it.

Figure 149



2. Scroll down to the bottom of the Services list and select the World Wide Web Publishing Service and stop it. Minimize this window when complete.

Figure 150

3. Next open two Windows Explorer windows. Open the first window (Window A) with the temporary folder where the cumulative patch was extracted, and then open another window (Windows B) with the Application Folder—C:\OPENTEXT\.

Figure 151



4. In the temporary folder containing the latest cumulative patch, select and delete the iss6cgi folder. This section of the patch is not relevant for ISS7.

Figure 152

5. Next open the module folder in the temporary patch directory, and in Window B, open the module folder in the C:\OPENTEXT\folder. Compare the lists of modules in the patch versus the modules installed on the system.

Figure 153



6. From this comparison, the only module contained in the patch that is not installed on the system is uniteatlas_9_5_0. This folder will be deleted, as there is no need to patch a module that is not installed.

Figure 154

7. Select all the modules in the patch folder and move and replace the folders under the modules folder in the C:\OPENTEXT\ folder.

Figure 155



8. Next, move up one level in both windows. Window A will be open on the extracted patch. Window B will be open on the root level of the application folder (C:\OPENTEXT). Select all of the folders except for the cumulative patch file (09-2009.pat in this example) and the MANIFEST file and move them to the application root, replacing all relevant files and folders.

Figure 156

9. The system is now patched. There is one more item to deploy.

Figure 157



10. In the application Window B, open the c:\OPENTEXT\patch\ folder. Move the cumulative .pat file (in this example, 09-2009.pat) into the application patch folder. The MANIFEST file can be retained for record purposes, or disposed of.

Figure 158

11. Close both windows and return to the Services window. Start the World Wide Web Publishing Service, then the Livelink Admin service, and the Livelink Server service.

Figure 159


Document Title


12. Return to a Windows client and repeat the tests in Phase Six.

Figure 160

If any new optional modules are installed at a later time, the cumulative patch will need to be reapplied. The setup of Content Server is complete.


Document Title

Sales Americas Europe Asia/Pacific www.opentext.com

[email protected] North America Sales

1-800-499-6544 International Sales

+800-4996-5440

United States 100 Tri-State Int’l Parkway

Lincolnshire, IL USA 60069

Phone: 847-267-9330 Fax: 847-267-9332

Germany Technopark 2

Werner-von-Siemens-Ring 20 D-85630 Grasbrunn

Germany Phone: +49 89 4629 0 Fax: +49 89 4629 1199

United Kingdom Grosvenor House

Horseshoe Crescent Beaconsfield, Buckinghamshire

United Kingdom HP9 1LJ Phone: +44 1494 679700

Fax: +44 1494 679707

Australia Level 23

100 Miller St. North Sydney

NSW 2060 Australia

Phone: +61-2-9026-3400 Fax: +61-2-9026-3455

If you are an Open Text partner or customer, visit online.opentext.com for more information about this and other Open Text solutions.

Open Text is a publicly traded company on the NASDAQ (OTEX) and the TSX (OTC). © Copyright 2009 by Open Text Corporation. Open Text, Livelink, Livelink ECM, and Great Minds Working Together are trademarks or registered trademarks of Open Text Corporation. All other trademarks or

registered trademarks are the property of their respective owners. All rights reserved.

w w w . o p e n t e x t . c o m 7 9


deploying content server on windows 2008 64 bit and ie 8

Documents