Case Study Deploying Content Server 10.5 SP1 On Windows 2012 and SQL Server 2012

Product: OpenText Content Server
Version: 10.5 SP1

Task/Topic: Deployment
Audience: Administrators
Platform: Windows Server 2012, SQL Server 2012 SP1
Document ID: 500167
Updated: December 1, 2017
Case Study
Deploying OpenText Content Server
10.5 Service Pack 1 plus Update 2017-
12 on Windows 2012 and SQL Server
2012 SP1
Deploying Content Server 10.5 SP1 Update 2017-12
Contents
Summary ...................................................................................................................... 4
Case Study Scenario .................................................................................................. 5
New Hardware ................................................................................................. 5
End Goal .......................................................................................................... 5
Download Content Server 10.5 SP1 plus Update 2017-12 .................................... 6
Content Server 10.5 SP1 plus Update 2017-12 Requires a License .............. 7
Setup Folders in Advance of Installation .......................................................... 7
Database Set Up .............................................................................................. 8
Disable Virus Scanning .................................................................................... 8
Phase One: Setup IIS 8.0 ............................................................................................ 9
Phase Two: Install Content Server 10.5 SP1 plus Update 2017-12 ...................... 26
Run the Content Server 10.5 SP1 plus Update 2017-12 Installer ....................... 26
Phase Three: Configure Permissions ..................................................................... 30
Set the Content Server Services Permissions ............................................... 30
Phase Four: Configure Content Server 10.5 SP1 plus Update 2017-12 .............. 34
Database Set Up ............................................................................................ 37
Content Server 10.5 SP1 plus Update 2017-12 License Setup .......................... 42
Applying the License Files ............................................................................. 44
Install and Configure WebDAV ...................................................................... 48
Download the Optional Modules .......................................................................... 53
Install the Recycle Bin Module ....................................................................... 54
Install remaining Optional Modules ................................................................ 63
Phase Five - Install Language Packs (Optional) .................................................... 64
Install Optional Core Language Pack(s)............................................................... 64
Modular Language Packs .............................................................................. 71
Install Modular Language Packs .......................................................................... 74
Phase Six: Deploy Latest Patches .......................................................................... 80
Setup the Master System ..................................................................................... 80
Managing Patches ................................................................................................ 84
To View Available Patches: ............................................................................ 84
To View Staged Patches: ............................................................................... 88
To Install Patches: .......................................................................................... 88
To View Installed Patches: ............................................................................. 91
Create the Help Indexes ....................................................................................... 92
Backup the Environment ................................................................................ 94
Phase Seven: Post Installation Checks .................................................................. 95
Change Admin Server Password ................................................................... 95
Enable Admin Alerts ....................................................................................... 95
Additional Changes ........................................................................................ 95
Enable and configure Agents and Notifications ............................................. 95
The Information Company™ 2

Appendix A – Dynamic Thread Allocation .............................................................. 96

Dynamic Thread Allocation ............................................................................ 96
More Details ............................................................................................ 96
The Information Company™ 3

Summary
This document provides a technical overview of the steps for a first time installation
of OpenText™ Content Server 10.5 Service Pack 1 (SP1) plus Update 2017-12. It
is targeted for Content Server Administrators (the person or people responsible for
deploying, administering, and maintaining OTCS). This guide presumes that you
possess the following knowledge and skills:
• An understanding of Content Servers’ purpose within your organization and how
it will be used.
• Familiarity with each server operating system and any legacy products or
systems that will be integrated with OTCS.
• Web server administration skills.
• Database administration skills (or a database administrator to assist you).
Customers who are planning new deployment of OTCS 10.5 SP1 plus Update 2017-
12 when it is officially released can consider the option of a contract under a
statement of work to consult with our Services Groups.
DISCLAIMER:
This Case Study contains procedures and sample SQL code. All
procedures and sample code in this area is specific to the
scenario presented in the Case Study and delivered as is and is
for educational purposes only. It is presented as a guide to
supplement official OpenText 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.
Be sure to review the Overview of New Features for OpenText Content Server 10.5.
NOTE: This Case Study applies to the installation of OpenText

Content Server 10.5.SP1 plus Update 2017-12.
For OpenText Content Server 10.5 Plus Update 2014-09 or
earlier refer to:
Case Study - Deploying Content Server 10.5 on Windows 2008
R2 and SQL Server 2008
or
Case Study - Deploying Content Server 10.5 on Windows 2012
and SQL Server 2012
NOTE: For Windows 2012 R2, see:

Case Study – Deploying Content Server 10.5 SP1 on Windows
2012 R2 and SQL Server 2012 SP2
4
Case Study Scenario

New Hardware
The Windows 2012 server which will host OTCS will have the SQL 2012 Client Tools
installed. Connectivity between the OTCS server and the SQL Server 2012 SP1 plus
Update 2017-12 server will be tested in advance of installing OTCS.
The first stage in the installation procedure will be to install and configure Content
Server 10.5 SP1 plus Update 2017-12 on the new Windows 2012 server. The
database will be created on the new SQL Server 2012 SP1 plus Update 2017-12 64-
bit Server.
Figure 1
New Servers
End Goal
Deploy a new OpenText Content Server 10.5 SP1 plus Update 2017-12 environment
in a dual-server configuration with OTCS, Search Index and EFS on one server, and
the database and on the other.
Figure 2
Planned Deployment
5
Download Content Server 10.5 SP1 plus Update 2017-12

Login to OpenText My Support and visit the Content Server Software Downloads
area.
Expand the Download Content Server 10.5 SP1 plus Update 2017-12 section.
Figure 3
Click on Download for Content Server for your platform, in this case, Windows.
Figure 4
6
Content Server 10.5 SP1 plus Update 2017-12 Requires a License

For additional information on licensing for OpenText Content Server 10.5 SP1 plus
Update 2017-12, please review:
Content Server Licensing 10.5 FAQ
Setup Folders in Advance of Installation

Although Content Server will create a default installation folder, referred to as
OTHOME, (in this case c:\opentext) folders for the index and EFS will be setup in
advance. It is advisable to deploy the index outside of the OTHOME folder for three
reasons. When a sysreport is run for example, the report will include each and every
file found in the index if it exists in its default OTHOME folder. The second reason is
for ease of backup, and third in the event front end servers are going to be deployed,
when the Content Server instance is copied, it will not include the index as well.
NOTE: For the purposes of this case study the OTHOME folder of
c:\opentext will be used for simplicity. For real world deployments,
the best practice is to keep just the operating system on C:\ and
create other partitions like D:\ for applications.
Normally there is a D:\OPENTEXT folder created and then a
subdirectory for the OTHOME called “CS105”, and separate
subdirectories for index, efs, and upload also in D:\OPENTEXT
(but outside the OTHOME).
Ideally the structure would resemble:
x:\opentext
\CS105 (OTHOME)
\index
\efs
\upload
(where x: is the application drive, c: for this case study)
The following folders will be created on the new Windows 2012 Server:
C:\index
C:\upload
C:\efs
The following folder will be created on the new SQL 2012 SP1 Server to house the
OTCS database:
C:\data
The new hardware hostnames for the Windows 2012 Servers are:
columbia - Content Server 10.5 SP1 plus Update 2017-12
enterprise – SQL Server 2012 SP1
7
Database Set Up
Often the Database Administrator (DBA) are not going to share the sa account for
security reasons and will require the Content Server administrator to specify file
paths on their database servers where the files will be written.
If this is the case in your environment, contact the DBA in advance and request the
OTCS database new database user account (for example “OTCS”) which Content
Server will use to connect as to create the schema.
Disable Virus Scanning

Virus scanning must be turned off for certain folders. Detailed information can be
referenced here:
Configuring Antivirus Software for use with Content Server 10
This application note details the recommended configuration of anti-virus applications
for use with deployments of OpenText Content Server 10.5 SP1 plus Update 2017-
12. The objective of this document is to ensure that anti-virus applications are
configured in such a way that they have as little negative impact upon the
deployment as possible.
Next, IIS 8.0 will be configured.
8
Phase One: Setup IIS 8.0

The first step is to add the Web Server Role to Windows 2012.
1. Log in to the Console as Administrator. The Server Manager Dashboard will load
by default. Click on number two Add roles and features.
Figure 5
Server Manager Dashboard
2. This will launch the Add Roles and Features Wizard. Click Next.
Figure 6
9
3. Ensure Role-based or feature-based installation is selected. Click Next.
Figure 7
4. Ensure the local server is selected from the server pool. Click Next.
Figure 8
10
5. Select Web Server (IIS), this will open a new window.
Figure 9
6. Click Add Features.
Figure 10
11
NOTE: This document is not a manual for configuring IIS in

general. Only features required for Content Server 10.5 SP1 plus
Update 2017-12 are discussed here.
7. Click Next.
Figure 11
8. Expand the .NET Framework 3.5 Features (Installed) section.
Figure 12
12
9. Select HTTP Activation; click Add Features and Non-HTTP Activation.

Expand the .NET Framework 4.5 Features (Installed) section, and then expand
the WCF Services section. Select HTTP Activation and TCP Port Sharing.
Click Add Features and then click Next.
Figure 13
10. Click Next.
Figure 14
13
11. In the Common HTTP Features section, select Default Document, HTTP
Errors, Static Content and WebDAV Publishing.
Figure 15
12. In the Health and Diagnostics section, select HTTP Logging and Request
Monitor. In the Performance section, select Static Content Compression.
Figure 16
14
13. Expand the Application Development section, ensure .NET Extensibility 3.5
and .NET Extensibility 4.5 are selected, and then select CGI, ISAPI
Extensions, and ISAPI Filters.
Figure 17
14. In the Management Tools section, select IIS Management Console and expand
the expand the IIS 6 Management Console, and select IIS 6 Metabase
Compatibility, IIS 6 WMI Compatibility, and IIS 6 Scripting Tools to install all
backwards compatibility components, and then click Next.
Figure 18
15
15. Review the list of role services or features, and then click Install.
Figure 19
16. When the installation is completed, click Close.
Figure 20
16
17. Minimize the Server Manager.
Figure 21
18. Move the mouse to the upper right reveal the Start Menu, and select it.
Figure 22
17
19. Scroll to the bottom right. Right-click on Internet Information Services.
Figure 23
20. Select Pin to Taskbar.
Figure 24
18
21. Scroll to the left and click on Desktop.
Figure 25
22. From the taskbar click on the shortcut to Internet Information Services (IIS)
Manager. Expand the Server Name folder.
Figure 26
19
23. Click Cancel for now.
Figure 27
24. Expand the Sites folder, and click Default Web Site. Next, double-click on
Request Filtering.
Figure 28
20
25. Click on Edit Feature Settings.
Figure 29
26. Under the Request Limits section, change the value of Maximum allowed
content length (Bytes) from 30000000 to 2147483648 (30 million to 2 billion,
or 2 GBs).
Figure 30
21
27. Click OK.
Figure 31
28. In IIS Manager, in the Connections pane, expand Sites, and then click Default
Web Site. In the IIS section (of the Default Web Site Home pane), open
WebDAV Authoring Rules.
Figure 32
22
29. Click Add Authoring Rule in the Actions pane.
Figure 33
30. In the Add Authoring Rule dialog box, in the Allow access to section, click
Specified content, and then type “/” (forward slash) for the specified content. In
the Allow access to this content to section, click All users to specify that the
rule applies to all users. In the Permissions section, click Read and Source,
and then click OK.
Figure 34
23
31. Click WebDAV Settings in the Actions pane.
Figure 35
32. In the WebDAV Settings pane, in the Property Behavior section, set the Allow
Anonymous Property Queries and the Allow Property Queries with Infinite
Depth options to True. In the Actions pane, click Apply.
Figure 36
24
33. In the Actions pane, click WebDAV Authoring Rules once again. In the Actions
Pane, click Enable WebDAV.
Figure 37
The initial setup of IIS 8.0 is now complete
25
Phase Two: Install Content Server 10.5 SP1

plus Update 2017-12
Run the Content Server 10.5 SP1 plus Update 2017-12

Installer
1. Double-click on the executable to initialize the setup and click Run.
Figure 38
2. The Setup Wizard opens. Click Next.
Figure 39
3. Select the check box for the License Agreement, and click Next.
Figure 40
26
4. Accept the default path C:\OPENTEXT, and click Next.
Figure 41
5. The defaults for Service Name, DNS Name, HTTP Server Name, and HTTP
Port Number do not need to be changed; click Next.
Figure 42
6. Select the Web Server platform, and click Next.
Figure 43
27
7. Accept the default CGI Mapping and URL Prefix, and click Next.
Figure 44
8. Accept the default port numbers, and click Next.
Figure 45
9. Select the Web Server platform for the Content Server Web Service, and click
Next.
Figure 46
28
10. Accept the default Web Service mappings, and click Next.
Figure 47
11. Click Next to start the Installation.
Figure 48
12. Once the installation is complete, uncheck all the boxes. Click Finish to
complete the Setup Wizard.
Figure 49
29
Phase Three: Configure Permissions

Set the Content Server Services Permissions
Create the OTCS user on both Windows 2012 servers. Assign full permissions to the
OPENTEXT and Index folders. For the EFS folder, set it up as a share (e.g.
\\<servername>\efs) and ensure the OTCS user has full permissions to the
upload folder and the EFS folder.
1. Close the Internet Information Services Manager. Move the mouse to the
upper-right corner of the screen to reveal the Start Menu, and click on Start.
Figure 50
2. Click Administrative Tools.
Figure 51
30
3. Right-click Services and select Pin to Taskbar.
Figure 52
4. Click on the new shortcut to Services in the taskbar to open it. Locate the
Content Server Service, right-click and select Properties.
Figure 53
31
5. Select the account for Content Server to run as, enter and confirm the password
for the account and click Apply and OK.
Figure 54
6. Click OK.
Figure 55
32
7. Repeat steps 4 and 5 for the Content Server Admin service.
Figure 56
For the purposes of this Case Study, the Content Server Cluster Agent service will be
left running under the Local System Account. To secure this service and the other
OTCS services, see the NOTE below. This new service is part of the Cluster Patch
Deployment system which is discussed later in this document.
NOTE: Administrators need to ensure that OpenText Extended

ECM deployments are operating under system accounts that use
the least privileges required to run the applications that form the
Extended ECM Suite. This ensures that:
• the deployment is more stable as it is unable to inadvertently
interact with system resources that are not required by the
application; and
• the deployment is more secure as it cannot be used to gain
unwanted access to resources outside those required by the
application.
OpenText recommends that administrators of Content Server 10.5
SP1 plus Update 2017-12 deployment follow the guidelines in this
document.
Configuring for Least Privilege: OpenText Content

Server 10.5
33
Phase Four: Configure Content Server 10.5

SP1 plus Update 2017-12
The next phase is to complete the setup of Content Server 10.5 SP1 plus Update
2017-12. The system passwords, database, External File Store, and index will be set
up and configured.
1. Start the three OTCS services for the first time.
Figure 57
2. Move the mouse to the upper right to reveal the Start Menu, click Start.
Figure 58
34
NOTE: Windows 2012 Server comes equipped with variants of

the Internet Explorer 10 web browser. One is the “Metro” Internet
Explorer 10 app which is launched by applications from the
Windows Start Screen, for use with touch interfaces on mobile
devices for example. The other variant is the traditional desktop
version of Internet Explorer 10. Currently the “Metro IE 10 app” is
unsupported.
To open Content Server for the first time, do the following:

3. From the Start Menu, right-click to bring up the All apps link, click on it.
Figure 59
4. Locate the Content Server Administration App – click on it.
Figure 60
35
5. This will open the regular IE 10 browser.
Figure 61
6. Since this is the first time OTCS has been started, the Configure Server
Parameters page appears (Figure 62). Enter a new password in the
Administrator Password and Verify Password fields, and then scroll down to
the bottom of the page, enter in the location of the Upload Directory, then click
Save Changes.
Figure 62
36
NOTE: There are several Server Parameters options available on

the Configure Server Parameters page. Only the settings required
for this procedure are addressed in this Case Study. Please refer
to the Content Server Administration Guide documentation for
more details on the other parameters.
7. The Select Default Metadata Language page appears.
Figure 63
8. From the drop-down menu, click English (United States) – en US and then click
Continue.
Figure 64
Database Set Up
Often the Database Administrator (DBA) are not going to share the sa account for
security reasons and will require the Content Server administrator to specify file
paths on their database servers where the files will be written.
If this is the case in your environment, contact the DBA in advance and request the
OTCS database new database user account (for example “OTCS”) which Content
Server will use to connect as to create the schema.
9. The Database Administration page appears; click the Create New Database
link.
Figure 65
37
10. Because the database platform is SQL Server 2012 SP1, click Microsoft SQL
Server, and then click Continue.
Figure 66
11. Enter the credentials for connecting to the database server using the “sa,”
account, and then click Log-in.
Figure 67
12. Next, click the Microsoft SQL Server Maintenance link.
Figure 68
38
13. Click Create a New Microsoft SQL Server Database.
Figure 69
14. Enter a database 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. Then click Create Database.
Figure 70
15. Click Create a New User.
Figure 71
16. Create a user name that OTCS will use to access its database - OTCS. Select
the new database from the drop-down list and click Create User.
39
Figure 72
17. Click Return to previous page link.
Figure 73
18. Since there is going to be an External File Store (EFS) select the External
Document Storage checkbox and enter the path to the EFS into the field below
it. Click Create Tables. This may take some time to complete.
Figure 74
40
19. Once the database tables are created the Administration page login page
appears (figure 75). Enter the password for the Content Server Administrator
(‘livelink’ by default) and then click Log-in.
Figure 75
20. The Install Modules page then appears. Do not install any of the installable
modules at this point. At the bottom of the page, click Continue.
Figure 76
21. On the Enterprise Data Source setup page, ensure the Base Directory
information contained here is correct. The default settings here are
c:/OPENTEXT/index/enterprise/. Since the index folder is off the root of C
drive, we will adjust the paths to read \\columbia\index\enterprise and
click Create Processes. This is where the data flow and Search Index partition
will reside.
Figure 77
41
22. When setup completes successfully, click Continue.
Figure 78
Content Server 10.5 SP1 plus Update 2017-12 License

Setup
Next, the License Setup page will load. A System Fingerprint will have been
generated. In order to activate your copy of OpenText Content Server 10.5 SP1 plus
Update 2017-12, a license is required. In order to obtain a license, click on the link
adjacent to Product Activation.
For those who have the WebReports module as part of their deployment, a separate
License File is required. The License File for Content Server must be applied first,
then the WebReports License File.
Figure 79
42
23. This will open a new browser tab/window displaying entitlements for all your
accounts. If this server is going to be your production environment, click on the
for the Non-production License Type if this is a development or test
environment. Otherwise select the Production License Type if this is your
production environment.
Figure 80
24. Your new license key will be generated.
Figure 81
25. Click Download File. Click OK.
Figure 82
26. Your License Key (Non-production in this example) is now listed as Active.
Figure 83
43
Applying the License Files

Once your License Files (two if you are using WebReports) has been received from
OpenText, retain the License Files in a safe place. The following procedure will
illustrate how to activate your system.
27. From the Server Configuration section click on Manage Licenses.
Figure 84
28. Click on the License Management section.
Figure 85
44
29. Click on the Browse button.
Figure 86
30. Locate the Content Server License File downloaded earlier, click Open.
Figure 87
31. The License File details will be displayed. Review the contents and then click on
Apply License File.
Figure 88
45
32. The Status will change from Unlicensed to Valid. Note that the WebReports
Module now appears on the page as Unlicensed. Click on License
Management.
Figure 89
33. Locate the WebReports License File downloaded earlier, click Open.
Figure 90
34. The License File details will be displayed. Review the contents and then click on
Apply License File.
Figure 91
46
35. The Status will change from Unlicensed to Valid. Click on Show Details to
expand the Module License Overview. Click on Continue.
Figure 92
36. Restart the Content Server Service.
Figure 93
The system has now been activated.
47
The initial “vanilla” (basic) setup of OTCS 10.5 SP1 plus Update 2017-12, the
database, EFS and index is now complete. Once the Congratulations page
appears, click the Admin Home link to proceed to the next procedure in the setup
process
Figure 94
Install and Configure WebDAV

Next the WebDAV module will be installed and configured.
37. In the Content Server Administration page, click the Show As Tabs link.
Figure 95
38. In the Module Administration section and select Install Modules. At the bottom
of the page, select Content Server WebDAV, and then click Install.
Figure 96
39. The Configure Virtual Directory appears with the default virtual directory name
specified. Click Continue.
48
Figure 97
40. Since the web server is IIS 7.5, it is not necessary to change any of the default
settings. Click Run the Installer.
Figure 98
41. In the File Download – Security Warning dialog box, click Run.
Figure 99
42. The install wizard opens. Click Next.
Figure 100
49
43. Click Yes when prompted to configure WebDAV.
Figure 101
44. Click Yes when prompted to update the IIS virtual mappings and ISAPI filter
information.
Figure 102
45. When complete, this process will restart the Web server.
Figure 103
46. Click Finish to close the installation wizard.
Figure 104
50
47. Return to the Configure Local Web Server page and click the Continue link.
Figure 105
48. It is necessary to restart the Content Server (OTCS) service at this point. Do
not click Continue. Open the Windows Services dialogue box and restart the
Content Server (OTCS) service.
Figure 106
49. Once the service has restarted, return to the Restart Content Server page and
click the Continue link.
Figure 107
51
50. The Install Modules page appears. Click Continue.
Figure 108
51. The Content Server Administration page appears. From a client computer, (for
example, a Microsoft Windows XP client computer) open Internet Explorer and
navigate to the Content Server login URL (in this example,
http://hal9000/OTCS/llisapi.dll).
Figure 109
52. Login to the Enterprise workspace. Test WebDAV to ensure it is working. There
is no longer a Drag and Drop tab. To access WebDAV in Content Server 10.5
SP1 plus Update 2017-12, a click the WebDav button available at the top right of
the browse view pane.
Figure 110
52
53. A WebDAV pane now appears below the browse view folder list. Drag a test file
into the WebDAV area. Once the file appears in the WebDAV pane, click
Continue.
Figure 111
Return to the Content Server Administration page.
Download the Optional Modules

Open a new browser window and download all the Content Server 10.5 SP1 plus
Update 2017-12 versions of the optional modules installed on the 10.0.0 system.
Based on the preliminary analysis, they are as follows:
Optional Module Version
Forms 10.5.0
Forms Workflow 10.5.0
Forms Workflow Painter 10.5.0
Recycle Bin 10.5.0
Web Forms 10.5.0
Visit the download section of My Support to acquire the install executable file for each
module, and review the install guides for each one. Some modules may require
schema to be created from the user interface after installation. We will walk through
the installation of the Recycle Bin module next.
When you enable a module that requires the installation of other modules, Content
Server automatically selects the required modules if they have been installed on the
operating system. Content Server can install as many as nine modules at once, but if
you want to install the modules one at a time, install the required modules first.
53
Install the Recycle Bin Module

The first step for installing the Recycle Bin module is the removal of the Document
Undelete module which is included as a core module in Content Server.
54. Go to the Module Administration section and select Uninstall Modules.
Figure 112
55. Click on the Uninstall button adjacent to the Content Server Document Undelete
module.
Figure 113
56. Click OK.
Figure 114
54
Figure 115
58. Click Continue.
Figure 116
59. Click OK.
Figure 117
Locate and run the installer for the Recycle Bin module. This will launch the
installation wizard.
55
60. Click Next.
Figure 118
61. Select the checkbox to accept the License Agreement and click Next.
Figure 119
62. Click Next.
Figure 120
56
63. Click Install.
Figure 121
64. Click Finish when complete.
Figure 122
65. Go to the Module Administration section and select Install Modules.
Figure 123
57
66. Select the OpenText Recycle Bin module and click Install.
Figure 124
Figure 125
58
68. Click Continue.
Figure 126
69. Click Continue.
Figure 127
70. Next scroll down and click on to the new Recycle Bin section on the Content
Server Administration page. When the section opens click on Database
Administration.
Figure 128
59
71. In order to add the Recycle Bin schema, click on each create link under the
Action section.
Figure 129
72. When complete, click Admin Home.
Figure 130
73. Next click on Configure Recycle Bin.
Figure 131
60
74. Next select the objects you want Recycle Bin to retain in the event of deletion. In
this example Recycle All is selected.
Figure 132
75. Next scroll down to the bottom of the page and select from the various options.
Figure 133
61
76. In this example, Yes was selected for both Enable “Recycle Bin” Menu Item
and Enable “Recycle Bin – Today” Menu Item options. For Access Restricted
To, the Admin and Owner Only option was selected. Click Update when
complete.
Figure 134
Figure 135
78. Click Continue.
Figure 136
62
Install remaining Optional Modules

Now install and configure any additional modules. Review and follow the install
guides for each of them. You can install up to nine modules at the same time.
NOTE: New modules that unique to Content Server 10.5 SP1 plus
Update 2017-12 should NOT be installed at this time. These
modules will be part of a separate post-upgrade project which will
be implemented once the production environment has been
upgraded.
Optional Module Version
Forms 10.5.0
Forms Workflow 10.5.0
Forms Workflow Painter 10.5.0
Web Forms 10.5.0
63
Phase Five - Install Language Packs (Optional)
Install Optional Core Language Pack(s)

To meet the requirement for the production system to be bilingual (offering both
English and French), it is necessary to apply the French language pack.
NOTE: By design, Language Packs can be installed, upgraded or

updated to a later (higher) version, and enabled or disabled, but
not uninstalled.
1. Download the core Language Pack file from OpenText My Support. In this
example, the core French language pack for Windows, from the Update 2017-12
section.
Figure 137
NOTE: If the system was on Update 2014-09 for example, then

the Update 2014-09 core French language pack would be
downloaded instead. Match language pack level to the installed
patch level.
64
2. Extract the zip file to a folder outside of the opentext folder.
Figure 138
3. Once extracted, copy the langpkgstaging folder, and paste it in the opentext
folder, replacing the existing langpkgstaging folder.
Figure 139
NOTE: Deploying the Language Pack deliverable into the Content

Server Staging folder will prevent OTCS from starting.
65
4. In the Languages section of the Content Server Administration page, click

Install Language Packs.
Figure 140
5. Choose the Install checkbox for the language pack, and then click Install.
Figure 141
The language package installs.
Figure 142
66
6. Once complete, do not click Continue. Restart the Content Server Service first.
Figure 143
7. Click Admin Home. Restart the Content Server Service.
Figure 144
8. Click Continue.
Figure 145
67
NOTE: Once installed, a language pack must be enabled in the

Configure Languages section in order for it to be applied to the
entire system.
9. Click Continue.
Figure 146
Configure Languages.
Figure 147
11. Choose the Enabled checkbox for the language, click Apply, and then click OK.
Figure 148
NOTE: The language label (in this case French) can be changed
by clicking the Edit icon and changing the description (to
“Français,” for example)
68
Administer Date/Time.
Figure 149
You can use the form to specify the date format that you want users to use to input
dates (Input date format), and that you want Content Server to use to display short
and long dates (Short Display and Long Display date formats). Use Time Zone Offset
to override server time. In this example, the defaults are used. See Admin Help for
more details on these settings.
13. Click OK, and then restart the Content Server service. Close the browser.
Figure 150
14. Do not click Continue. Restart the Content Server Service first.
Figure 151
69
15. Restart the Content Server Service.
Figure 152
16. Click Continue, and then close the browser.
Figure 153
17. Open the browser and return to Content Server. The Log-in screen will load and
the new language is available. Test the cookie by clicking French. To change
back, click English.
Figure 154
70
Modular Language Packs

Once a core language pack is installed, it is necessary to apply the corresponding
modular language packs for your optional modules.
When downloading optional modules, check if the module has a modular language
pack. Since the production server in this scenario offers bilingual services in English
and French, we will download the French modular language pack.
The example below illustrates how to check for required Modular Language Packs.
View Installed Language Packs.
Figure 155
71
19. From the list, the French language (_fr) is installed across all the core modules.
However, the optional modules Form and Forms Workflow have no
corresponding language pack. For the optional module Forms Workflow Painter it
states “No languages installed”, meaning there is no language pack
required for this optional module.
Figure 156
20. Below is an illustration of the Forms module download area. Open the Forms
10.5.0 folder.
Figure 157 –
The contents of the Forms
10.0.0 download folder
72
21. Below is an illustration of both the module download, and the French modular
language pack for the Forms module. In figure 158, the contents of the download
folder for the Forms module are illustrated.
Figure 158–
22. The English subfolder, as illustrated in figure 159, has a set of subfolders by
operating system type. The installer for the Forms module for Windows is located
here. This must be run to set up the module in the staging folder. In this case,
10.5.0_FORMS64_WIN.exe is selected.
Figure 159
23. Go up one level of the Forms 10.5 folder, where there are subfolders for the
modular language packs. Since the production server in this example offers the
French language, only the French modular language pack will be downloaded.
Figure 160–
73
24. Within the French folder are a set of subfolders by operating system type. We will
select the Windows version – forms_langpack_10.5.0_win_win_fr.zip.
Figure 161
Visit the download section of My Support to acquire the install executables.

For Forms, Forms Workflow, and Forms Workflow Painter, there is a single install
executable. There is a separate one for Webforms.
Download and install all the optional modules, according to the individual
documentation for each module.
Install Modular Language Packs

The example below illustrates the installation of the Forms Modular Language Pack.
NOTE: optional modules language packs can only be installed

after the corresponding core language pack has been installed
and the language has been enabled.
In the Languages section of the Content Server Administration page, click View
Installed Language Packs.
Figure 162
74
25. From the list, the French language (_fr) is installed across all the core modules.
However, the optional modules Form and Forms Workflow have no
corresponding language pack. For the optional module Forms Workflow Painter,
it states “No languages installed”, meaning there is no language pack
required for this optional module.
Figure 163
26. Extract the Modular language to a folder outside of the Content Server
installation folder. The extracted package creates a folder called
langpkgstaging.
Figure 164
NOTE: Deploying the Language Pack deliverable into the Content

Server Staging folder will prevent OTCS from starting.
75
27. Copy the langpkgstaging folder to the clipboard, paste it to the langpkgstaging
folder under the root install folder for Content Server (in this example
c:\opentext), overwriting the contents of the original langpkgstaging folder.
Figure 165
Install Language Packs.
Figure 166
29. A list of Installable Module Language Packs appears.
Figure 167
76
30. Choose the individual Modular Language Packs, and click Install.
Figure 168
The Modular language packs installs.
Figure 169
31. Once complete, a summary page appears, do not click Continue. Restart your
Content Server service first.
Figure 170
77
32. Return to the browser window, and click Continue.
Figure 171
33. Click Admin Home.
Figure 172
View Installed Language Packs.
Figure 173
78
The Forms and Forms Workflow optional modules now have the French Modular
language pack applied.
Figure 174
NOTE: The above procedure must be repeated for all optional

modules which have Modular language packs
NOTE: OpenText requires that you delete and recreate the Help
Data Source Folder whenever you add or remove language
packs, or when the system default locale is modified.
See Appendix for details.
79
Phase Six: Deploy Latest Patches

Now that the Content Server 10.5 SP1 plus Update 2017-12 has been built, and the
Cluster Agent is connected, it is time to configure the new Cluster Management Patch
Deployment System. Before using this new tool, there is a one-time configuration
setup to perform.
Setup the Master System

1. On the Content Server Administration page, click on the Server
Configuration section, and then click on Cluster Management.
Figure 175
2. Click on Manage Cluster Settings.
Figure 176
80
3. The URL for the manifest is available via the online help. From the top of the
page click on the ? and select For this Page.
Figure 177
4. A list of the latest URLs for the Manifest will be displayed in the Help window.
Figure 178
5. On the Configure Deployment Settings page, type the URL for updating the
manifest into the Update URL.
Figure 179
81
6. Click Check URL to validate the manifest URL.
Figure 180
7. You will also need to specify the master system. Click Browse.
Figure 181
8. On the Cluster Agents page, click the + icon beside the desired Host. In the
example below we have our new Content Server. Click OK.
Figure 182
82
9. The staging folder for the patches will be provided automatically. This location
can be changed at your discretion.
Figure 183
10. Select the checkbox for Automatically download and stage patches when
selected (Note: Requires and internet connection and valid My Support
account.). Click Save Settings.
Figure 184
11. Click Yes to confirm.
Figure 185
83
Managing Patches
Cluster Management lists available and staged patches, setting them up for
installation to Content Server. When accessing Managing Patches, the Master
System Analysis will run, but it can be skipped if the system has been recently
validated. Managing Patches has three separate tabs:
• Available Patches, lists the available patches on the OpenText My Support
for download.
• Staged Patches, lists patches can be deployed.
• Installed Patches, lists the installed patches.
To View Available Patches:

12. Under the Server Configuration section of the Content Server Administration
page, click on Cluster Management, then click the Manage Updates link.
Figure 186
13. Click Continue.
Figure 187
84
14. The system will now be analyzed.
Figure 188
15. View the report, click OK when complete.
Figure 189
16. A page will load listing the available patches for download. Below is an example
of available patches.
Figure 190
85
17. Click on the Details link on each patch to view information on what the patch
addresses. Click Close when complete.
Figure 191
Next the patches will be downloaded and applied.

18. Click on the top checkbox to select all the patches, then click the Download link.
Figure 192
86
19. Click OK after reviewing the Confirm Download Package window.
Figure 193
20. Login with your OpenText My Support credentials and click OK.
Figure 194
21. Downloads will commence.
Figure 195
87
To View Staged Patches:

22. Click the Staged Patches tab and refresh the page in your browser. The patches
we downloaded will now be listed for installation.
Figure 196
To Install Patches:
23. Click on the top check box to select all the patches to install. Click the Deploy
button.
Figure 197
1.
88
24. Click OK
Figure 198
25. The patches will be deployed and the Content Server Service restarted in the
background.
Figure 199
89
The system will automatically update the master system information when complete.
Figure 200
26. Click OK.
Figure 201
27. Click OK again.
Figure 202
90
To View Installed Patches:

28. The system will automatically update and produce the latest status report. Click
on the Installed link.
Figure 203
29. The patches recently installed will be listed. Clicking on the Details link will
reveal all the information about the patch. Click Admin Home.
Figure 204
91
Create the Help Indexes

With the optional modules, language pack(s) and Hotfixes now applied, the help file
data source folders can now be created.
1. Return to the Content Server System page. Click Show as Tabs on the admin
page to only show the sections. Go to the Search Administration section and click
on Open the System Object Volume.
Figure 205
2. Click on the Add Item menu, click Admin Help Data Source.
Figure 206
3. Enter in the path to the location where you want to create the Admin Help Data
Source (in this case \\columbia\index\adminhelp\) in the Base
Directory field. Click Create Processes.
Figure 207
92
4. Click Continue to confirm.
Figure 208
5. From the Add Item menu, click User Help Data Source.
Figure 209
6. Enter the path to the location where you want to create the User Help Data
Source (in this case, \\columbia\index\help\) in the Base Directory field.
Click Create Processes.
Figure 210
93
7. Click Continue to confirm.
Figure 211
8. Click Admin Home.
Figure 212
Backup the Environment

Make a complete backup of both new servers; this will be the snapshot to revert to
prior to upgrading production. Figure 213 illustrates the current state of the test
environment.
Figure 213
94
Phase Seven: Post Installation Checks

Change Admin Server Password
Although optional, best practices for securing the system call for the Admin server
password to be changed from the default value of “livelink” to a secret value. Record
and store the secret value in a secure place.
Enable Admin Alerts

This is a reminder that Administrator Alerts (email notifications) should be re-enabled
if they were disabled earlier.
Additional Changes
If you had changes to the search configuration that you want to implement with
Content Server 10.5 SP1 plus Update 2017-12, the system is now configured and
ready. Note that trying to make some changes earlier in the process might not work
as expected. For example, there are some settings that cannot be changed correctly
until after the Admin Server resync.
In addition:
Enable and configure Agents and Notifications

If this is the production server, Agents and Notification will need to be setup and
configured.
Once this step has been performed and verified that it is working, see the Post –
Installation/Upgrade Testing for Open Text Content Server 10.5 Checklist.
This document lists the tests that should be performed, and that must be passed, to
ensure a working Content Server 10.5 SP1 plus Update 2017-12 installation. The
tests described in this document cover all basic functionality.
95
Appendix A – Dynamic Thread Allocation

Dynamic Thread Allocation
Dynamic Thread Allocation was introduced in Content Server 10 with the intent to
provide a performance enhancement. The idea of dynamic thread allocation is to only
allocate the defined minimum number of Content Server threads on initial start-up in
order to conserve server resources. The threads allocated on start-up then become
available to service user requests to Content Server. If a user request arrives to
Content Server, and all available threads are saturated, Content Server will spawn a
new thread to service the request. Content Server will only spawn up to the defined
maximum number of threads before resorting to queuing user requests.
After analyzing the behaviour of Content Server 10 with this new model, it was
determined that due to the design of Content Server, the benefits of this
enhancement were not often realized. As a result, OpenText recommends that the
minimum and maximum number of Content Server threads are set to the same value.
Please note that this may increase start-up time of Content Server.
More Details
When a Content Server thread is created, the thread loads all of the modules and
patches into memory. This process can take up to a minute on larger systems. The
threads also maintain their own Oscript objects in memory, where various data is
cached (e.g., facet, column and category definitions), so they are expensive to
destroy and recreate.
The side effect of this is an artificial demand on the server for the maximum number
of threads, once the minimum number of threads have been saturated.
If a user sends a request to Content Server, and Content Server needs to spawn a
new thread to service the request, the processing of the user's request will be
delayed until the new thread has been created.
If the delay is perceived by the user to be excessive, the user may retry the request,
creating yet another demand for a thread from Content Server. This can happen
multiple times by multiple users, resulting in a large number of requests for new
threads. Ultimately, Content Server will be required to create the maximum number of
threads to try to service the large number of pending user requests.
For this reason, it has been determined that allocating the maximum number of
threads on start-up is much preferred over the above scenario.
As a result, OpenText recommends that the "min" and "max" settings, found within
the [llserver] section of the <OTHOME>/config/opentext.ini file, are set to
the same value.
Determining the number of threads to deploy to a specific environment is dependent
on many different factors. The OpenText Global Services department can assist you
in this assessment through a sizing and scaling exercise.
96
About OpenText
OpenText enables the digital world, creating a better way for organizations to work with information, on premises or in the
cloud. For more information about OpenText (NASDAQ: OTEX, TSX: OTC) visit opentext.com.
Connect with us:
OpenText CEO Mark Barrenechea’s blog

Twitter | LinkedIn | Facebook
97
www.opentext.com/contact
Copyright © 2017 Open Text SA or Open Text ULC (in Canada).
All rights reserved. Trademarks owned by Open Text SA or Open Text ULC (in Canada).

Case Study Deploying Content Server 10.5 SP1 On Windows 2012 and SQL Server 2012

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Case Study Deploying Content Server 10.5 SP1 On Windows 2012 and SQL Server 2012

Hochgeladen von

Copyright:

Verfügbare Formate

Product: OpenText Content Server

Version: 10.5 SP1

The Information Company™ 2

Appendix A – Dynamic Thread Allocation .............................................................. 96

The Information Company™ 3

NOTE: This Case Study applies to the installation of OpenText

NOTE: For Windows 2012 R2, see:

Case Study Scenario

Download Content Server 10.5 SP1 plus Update 2017-12

Content Server 10.5 SP1 plus Update 2017-12 Requires a License

Setup Folders in Advance of Installation

(where x: is the application drive, c: for this case study)

Disable Virus Scanning

Next, IIS 8.0 will be configured.

Phase One: Setup IIS 8.0

3. Ensure Role-based or feature-based installation is selected. Click Next.

5. Select Web Server (IIS), this will open a new window.

6. Click Add Features.

NOTE: This document is not a manual for configuring IIS in

8. Expand the .NET Framework 3.5 Features (Installed) section.

9. Select HTTP Activation; click Add Features and Non-HTTP Activation.

10. Click Next.

16. When the installation is completed, click Close.

17. Minimize the Server Manager.

19. Scroll to the bottom right. Right-click on Internet Information Services.

20. Select Pin to Taskbar.

21. Scroll to the left and click on Desktop.

23. Click Cancel for now.

25. Click on Edit Feature Settings.

27. Click OK.

29. Click Add Authoring Rule in the Actions pane.

31. Click WebDAV Settings in the Actions pane.

The initial setup of IIS 8.0 is now complete

Phase Two: Install Content Server 10.5 SP1

Run the Content Server 10.5 SP1 plus Update 2017-12

2. The Setup Wizard opens. Click Next.

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

6. Select the Web Server platform, and click Next.

8. Accept the default port numbers, and click Next.

11. Click Next to start the Installation.

Phase Three: Configure Permissions

2. Click Administrative Tools.

3. Right-click Services and select Pin to Taskbar.

7. Repeat steps 4 and 5 for the Content Server Admin service.

NOTE: Administrators need to ensure that OpenText Extended

Configuring for Least Privilege: OpenText Content

Phase Four: Configure Content Server 10.5

NOTE: Windows 2012 Server comes equipped with variants of

To open Content Server for the first time, do the following:

4. Locate the Content Server Administration App – click on it.

5. This will open the regular IE 10 browser.

NOTE: There are several Server Parameters options available on

7. The Select Default Metadata Language page appears.

12. Next, click the Microsoft SQL Server Maintenance link.

13. Click Create a New Microsoft SQL Server Database.

15. Click Create a New User.

17. Click Return to previous page link.

22. When setup completes successfully, click Continue.

Content Server 10.5 SP1 plus Update 2017-12 License

24. Your new license key will be generated.

25. Click Download File. Click OK.

Applying the License Files

28. Click on the License Management section.