Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Version: 9.7.1
Task/Topic: Deployment
Audience: Administrators
Platform: Windows Server 2008 x64 Edition, SQL Server 2005
Document ID: 500060
Updated: 2010-04-19
Case Study
Deploying Content Server 9.7.1 on
Microsoft® Windows Server 2008 x64
Edition
Document Title
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
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: 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.
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:
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:
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.
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.
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.
Figure 1-
Default Start Menu
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
Figure 4
Figure 5
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
Click Next.
Figure 11
Figure 12
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
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.
Figure 21
Figure 22
3. Select the check box for the License Agreement, and click Next.
Figure 23
Figure 24
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
Figure 28
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
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
Figure 37
Figure 38
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
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
Figure 48
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
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
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
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
Figure 65
Figure 66
Figure 67
Figure 68
Figure 69
Figure 70
7. Click Run.
Figure 71
8. Click Next.
Figure 72
9. Click Next.
Figure 73
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
Figure 78
Figure 79
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
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
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
Figure 87
Figure 88
Figure 89
27. Select the WebDAV Administration section, and click Configure Web Server.
Figure 90
Figure 91
Figure 92
Figure 93
Figure 94
Figure 95
Figure 96
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
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.
Figure 101
Figure 102
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
Figure 105
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
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
Figure 110
Figure 111
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.
Figure 114
Figure 115
7. Click the Functions menu for the new Workflow Map, and click Edit.
Figure 116
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
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
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
17. Enter a name for the Workflow Map, and click Add.
Figure 125
18. Click the Functions menu for the new Workflow Map, and click Edit.
Figure 126
Figure 127
20. 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 128
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
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
Figure 138
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
36. 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 143
37. 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.
38. From the Add Item drop-down menu, click on Workflow Map.
Figure 144
39. Enter a name for the Workflow Map, and click Add.
Figure 145
40. Click the Functions menu for the new Workflow Map, and click Edit.
Figure 146
Figure 147
42. 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 148
The setup of Content Server 9.7.1 is complete. Next the latest cumulative patch will
be applied.
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
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
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.
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.
www.opentext.com 79