OpenText Archive Center 16.2 - Installation Guide for Windows (Integrated Archive Installer) English (AR160200-00-IGW-En-03) (1)

May 14, 2018 | Author: Юрий Лагутин | Category: Transport Layer Security, Port (Computer Networking), Oracle Database, File System, I Pv6


Comments



Description

OpenText™ Archive CenterInstallation Guide for Windows (Integrated Archive Installer) This guide describes the setup of OpenText Archive Center 16 EP2 with the integrated Archive Center Installer on Windows systems. Use this guide for fast and easy installation of Archive Center 16 EP2. AR160200-00-IGW-EN-03 OpenText™ Archive Center Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 Rev.: 2017-Nov-06 This documentation has been created for software version 16.2. It is also valid for subsequent software versions as long as no new document version is shipped with the product or is published at https://knowledge.opentext.com. Open Text Corporation 275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1 Tel: +1-519-888-7111 Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440 Fax: +1-519-888-0677 Support: https://support.opentext.com For more information, visit https://www.opentext.com Copyright © 2017 Open Text. All Rights Reserved. Trademarks owned by Open Text. Disclaimer No Warranties and Limitation of Liability Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication. Table of Contents PRE About OpenText Archive Center v 1 Prerequisites for Archive Center ............................................. 9 1.1 Configuring basic settings ................................................................ 10 1.1.1 Hardware and software recommendations ........................................ 10 1.1.2 Network recommendations and restrictions ....................................... 11 1.1.3 Testing network environment ........................................................... 12 1.1.4 Optimizing system for network applications ....................................... 12 1.1.5 Checking computer name ................................................................ 13 1.1.6 Disabling disk cache of hard disk ..................................................... 13 1.2 Installing Java ................................................................................. 14 1.3 Setting up Apache Tomcat ............................................................... 14 1.3.1 Installing Tomcat ............................................................................. 14 1.3.2 Configuring Tomcat options ............................................................. 15 1.3.3 Configuring the Cookie Processor component ................................... 15 1.3.4 Configuring the Tomcat user ............................................................ 16 1.3.5 Configuring the connector and securing Tomcat ................................ 17 1.4 Setting up Directory Services ........................................................... 19 1.4.1 Configuring OTDS ........................................................................... 19 1.4.2 Scenario-specific settings ................................................................ 21 2 Setting up the database .......................................................... 23 2.1 Setting up Microsoft SQL Server or Azure SQL Database .................. 23 2.1.1 Database characteristics ................................................................. 23 2.1.2 Testing the database ....................................................................... 25 2.2 Setting up Oracle Database ............................................................. 26 2.2.1 Database characteristics ................................................................. 27 2.2.2 Remote DB on Oracle RAC ............................................................. 27 2.2.3 Testing the database ....................................................................... 28 3 Installing Archive Center ........................................................ 31 3.1 Running the Archive Center Installer ................................................ 31 3.2 Folder settings ................................................................................ 38 3.3 Troubleshooting .............................................................................. 39 4 Configuring Archive Center .................................................... 43 4.1 Signing in to Archive Server in Administration Client .......................... 43 4.2 Changing the dsadmin password ..................................................... 43 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) iii AR160200-00-IGW-EN-03 Table of Contents 4.3 Changing the password of the database user .................................... 44 4.3.1 Oracle Database only: Checking the expiry date of the password ....... 44 4.4 Configuring the ports for the SAP gateway ........................................ 45 4.5 Configuring different internal and external hostname ......................... 45 4.6 Configuring certificate authentication for Archive Center Proxy ........... 46 5 Appendix: Setting up the database in Microsoft SQL Server ....................................................................................... 47 5.1 Configuring network connectivity ...................................................... 47 5.2 Creating the SQL Server login ......................................................... 49 5.3 Creating the database ..................................................................... 49 5.4 Rights for database users before and after installation ....................... 50 6 Appendix: Setting up the database in Oracle Database ...... 53 6.1 Setting up Oracle Database server ................................................... 54 6.1.1 Creating the Oracle Listener ............................................................ 54 6.1.2 Creating the test database ............................................................... 54 6.1.3 Creating the database user .............................................................. 58 6.1.4 Configuring the Oracle Listener ........................................................ 59 6.1.5 Configuring Oracle TNS Service Names ........................................... 59 6.2 Rights for database users before and after installation ....................... 60 7 Appendix: Special commands ............................................... 63 7.1 Starting and stopping Archive Server with SQL Server ...................... 63 7.2 Starting and stopping Archive Server with Oracle Database ............... 64 GLS Glossary 67 iv OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 Preface About OpenText Archive Center OpenText Archive Center is a lean, easy-to-install, easy-to-maintain archiving solution based on the well-established core component Archive Server. It offers basic metadata handling using a CMIS interface and supports various data sources, for example, SAP systems and file archiving. Note: Archive Center 16 EP2 can be used with or without the services provided by the Application Layer. In the latter case, Archive Center continues the feature set of previous Archive Server versions (10.5.0 and before). This guide describes scenarios that use the Application Layer and web clients explicitly. For more information, see also OpenText Archive Center - Administration Guide (AR-ACN). Archive Center OpenText™ Archive Center Administration is a web-based, easy-to-use client Administration included in Archive Center. OpenText Archive Center customers, called tenants, administrate the archiving of content and documents from their system to Archive Center. The archiving activities are defined and controlled by specific collections. • Collections support different scenarios, like File Share or archiving from SAP systems, using data sources. The Collections administration provides the following features: • Creation, configuration, and administration of collections. • Collection-specific holds (freezing) of archiving to protect all currently archived documents from modification and deletion. • Collection-specific data volume usage statistics. • Rules define actions when a certain condition is met (for example, add tags to documents). • Retentions can be specified and, using tagging rules, applied to documents automatically. • Statistics provide information about the total data volume usage on the Archive Center. • Server provides information about the tenant and the related Archive Server administration and allows the business administrator to create new system keys for encryption. DPs Archive Center uses Document Pipelines (and their “DocTools”) to import documents in various scenarios. The Archive Center Installer provides the base OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) v AR160200-00-IGW-EN-03 About OpenText Archive Center package “OpenText Document Pipeline Base” and a pipeline for document import using CMIS (“OpenText Document Pipeline for Archive Center CMIS”) by default. For more information, see also OpenText Document Pipelines - Overview and Import Interfaces (AR-CDP). Access OpenText™ Archive Center Access is a web-based, easy-to-use client included in Archive Center, which allows access to the archive independently from the archiving application. This can, for example, be important in case of impending litigation. Using the Archive Center Administration client, collections can be put on hold to protect all currently archived documents from modification and deletion. Existing metadata of archived documents can be searched and all relevant documents can be exported. My Archive OpenText™ My Archive, similar to Access, is an easy-to-use web client that allows access to the archive. In contrast, it allows individual users to access their archived documents. Users can view, search, and download the documents only if they have appropriate rights. Proxy OpenText™ Archive Center Proxy is an easy to set up and maintain client, which securely connects the customer’s network with the cloud-based Archive Center and also provides caching functionality. For more information, see OpenText Archive Center Proxy - Installation and Configuration Guide (ARPRX-IGD). Related documentation Product docu- The following documentation is available for Archive Center on OpenText My mentation Support (https://knowledge.opentext.com/docs): • OpenText Archive Center - Administration Guide (AR-ACN) This guide describes all configuration-related and administration-related aspects of OpenText™ Archive Center. • OpenText Archive Center - Scenario Configuration Guide (AR-CGD) This guide describes the setup of scenarios for Archive Center, including prerequisites and the usage of the applications OpenText™ Archive Center Administration and OpenText™ Archive Center Access. • OpenText Archive Center - Cluster Installation Guide (AR-ICLU) This guide describes how to set up Archive Center as a highly-available and data-secure active-active cluster. • OpenText Archive Center Proxy - Installation and Configuration Guide (ARPRX-IGD) This guide describes the installation and usage of OpenText Archive Center Proxy. • OpenText Archive Center Administration - Online Help (ARBA-H-AGD), OpenText Archive Center Access - Online Help (ARAC-H-AGD), OpenText My Archive - Online Help (ARMA-H-UGD) Online help is available for Archive Center Administration, Archive Center Access, and for My Archive. vi OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 About OpenText Archive Center • OpenText Archive Center - Update Installation Guide (Windows) (AR-DWZ) This guide describes the installation of the latest “patch collection” for Archive Center, called Update 16.2.1. Note: Update 16.2.1 delivers new features and fixes for Archive Center. In this documentation we assume that Update 16.2.1 is installed. • OpenText Document Pipelines - Overview and Import Interfaces (AR-CDP) This guide describes concepts, tools, and scenarios of OpenText™ Document Pipeline and gives detailed information on the standard DocTools. Release Notes The Release Notes describe the following aspects in detail: • The software supported by the product. • Requirements. • Restrictions. • Important dependencies. • Last-minute changes regarding the documentation. • Identification codes of the current documentation. The Release Notes are continually updated. The latest version of the Archive Center Release Notes is available on OpenText My Support (https:// knowledge.opentext.com/knowledge/llisapi.dll/Open/52712069). OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) vii AR160200-00-IGW-EN-03 Chapter 1 Prerequisites for Archive Center 3rd-party The following software has to be installed on the computer before you install the software Archive Center components. For the latest information, see the Release Notes on My Support (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/52712069). Operating system Archive Center requires Microsoft Windows Server 2012 R2 or Windows Server 2016. Microsoft Visual C++ Archive Center requires a Microsoft Visual C++ package: Visual C++ 2008 SP1 Redistributable Package (x64) (https://www.microsoft.com/downloads/en/ details.aspx?familyid=BA9257CA-337F-4B40-8C14-157CFDFFEE4E). .NET Framework 4.5.1 OpenText™ Administration Client requires .NET Framework 4.5.1. Verify that the “.NET Framework 4.5” feature is enabled in the Windows Server Manager. Note: The Archive Center Installer does not check for this requirement. Database Archive Center requires Microsoft® SQL Server®, Microsoft® Azure® SQL Database, or Oracle® Database. For information about the supported versions, see the Release Notes on My Support (https://knowledge.opentext.com/ knowledge/llisapi.dll/Overview/67816615). The database can be installed locally or on a remote system. Java Archive Center requires Java™ Runtime Environment 8 Update 72 or later. Application server Archive Center requires Apache® Tomcat™ 8.5.8 or later. General Do the following to ensure a successful installation of Archive Center: settings Administrative rights To install Archive Center, you must have administrative rights and the “Log on as a service” privilege. Run secpol.msc and add the user or group in Local Policies > User Rights Assignment > Log on as a service. Tomcat must be run by a dedicated user (not LocalSystem!). This user must be a member of the local Administrators group. For more information, see “Configuring the Tomcat user” on page 16. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 9 AR160200-00-IGW-EN-03 Chapter 1 Prerequisites for Archive Center Basic settings See “Configuring basic settings” on page 10 for recommended settings. OpenText™ Directory Services Directory Services (OTDS) can either be installed locally or remotely, and you can either use an existing instance or install a new one. Depending on which landscape you want to use, the installation paths differ. For more information, see “Setting up Directory Services” on page 19. Conventions The following variables are conventions for this documentation: • The installation folder for Archive Center is called <OT install AC>. The default value is C:\Program Files\OpenText. • The folder for configuration data is called <OT config AC>. The default value is C:\ProgramData\OpenText\Archive Server 16.2.0\ config. Procedure • “Setting up Microsoft SQL Server or Azure SQL Database” on page 23 • “Setting up Oracle Database” on page 26 • “Installing Java” on page 14 • “Setting up Apache Tomcat” on page 14 • “Setting up Directory Services” on page 19 1.1 Configuring basic settings Do the following to avoid problems during installation or runtime. 1.1.1 Hardware and software recommendations Paging space The amount of paging space should be about the same as the amount of RAM. Prerequisites for hard disk systems • Enterprise-ready disk arrays are used. • High-performance and random access to data and file system metadata (for example, directory structures) is provided. • Multi-threaded access is provided. • Standard file system calls (read, write, stat, delete, etc.) always return results comparable to locally attached hard disks. • Disks are protected against data loss by backup or similar technologies. Hard disk layout Most disks for Archive Center must be mirrored with RAID 1, and there must be at least three independent disks. The secure operation of the database requires one disk for the database and two separate disks for the log files. Archive Center stores all documents temporarily on hard disk. This disk must be protected by RAID 5 or RAID 1. 10 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 1.1. Configuring basic settings For the disk layout of an Oracle Database, see the Oracle documentation (http:// www.oracle.com/pls/db112/homepage). For the disk layout of a Microsoft SQL Server database, see the following MSDN entries: • SQL Server Best Practices (http://msdn.microsoft.com/en-us/sqlserver/ bb671432.aspx) • Disk Partition Alignment Best Practices for SQL Server (http:// msdn.microsoft.com/en-us/library/dd758814%28SQL.100%29.aspx) Unwanted frag- Be aware that the file system may fragment disk partitions in an undesirable mentation manner, depending on the used type of file system. This can lead to incorrect free space detection, causing attempts to write data to the file system to fail, resulting in a “no space left on device” message. Schedule regular defragmentation, in particular for the partitions holding caches and volumes. 1.1.2 Network recommendations and restrictions Static ports SQL Server must use static ports. Dynamic ports will not work. Ports to open Archive Center requires the following ports, which must be configured in the firewall: RPC Tools and administration interface: 4020, 4027, 4030, 4032, 4033, 4034 TCP HTTP/HTTPS ports for Tomcat as defined in the server.xml file (default: 8080, 8090) Enforcing In mixed IPv4/IPv6 environments, you may need to enforce preferred usage of one protocol of the protocols. To enforce IPv4 or IPv6: 1. Open the window to edit the system environment variables. Tip: In the Start menu, search for edit the system environment variables. 2. Create a system variable named AS_PREF_IP and then enter a Value of 4 or 6, depending on the protocol to be preferred. Related Topics • “Optimizing system for network applications” on page 12 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 11 AR160200-00-IGW-EN-03 Chapter 1 Prerequisites for Archive Center 1.1.3 Testing network environment Test the connections between Archive Server and your leading application on <server name> (ensure that lookup and reverse lookup are working in your network): ping <server name> and on <server name> ping <archive server name> Do the same for the connection to the Enterprise Scan, if you use the mass scanning scenario. Make sure that lookup and reverse lookup are working. If you are using a remote database, do the same for the database server. 1.1.4 Optimizing system for network applications When a task requests a port, the operating system by default assigns any port between 1024 and 65535. If, for example, Tomcat is configured to run on port 8080, it can happen that Windows assigns this port to some other application before Tomcat starts. Do the following to avoid this situation. To configure the dynamic port range: 1. Start a command prompt with Run as administrator (elevated command prompt) and enter the following to avoid running out of ports. Note: These commands set the minimum port number to 8091 (by default, Archive Server uses port 8090 for HTTPS). If your system requires a different setting, for example, because an application needs a certain port above 8091, change the commands correspondingly, where num = 65535 − start. For IPv4 netsh int ipv4 set dynamicport tcp start=8091 num=57444 netsh int ipv4 set dynamicport udp start=8091 num=57444 For IPv6 netsh int ipv6 set dynamicport tcp start=8091 num=57444 netsh int ipv6 set dynamicport udp start=8091 num=57444 2. Use following commands to verify the result of the previous step (for IPv6, replace IPv4 accordingly): >netsh int ipv4 show dynamicportrange tcp Protocol tcp Dynamic Port Range --------------------------------- Start Port : 8091 Number of Ports : 57444 and >netsh int ipv4 show dynamicportrange udp Protocol udp Dynamic Port Range 12 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 1.1. Configuring basic settings --------------------------------- Start Port : 8091 Number of Ports : 57444 Configure the processor scheduling for background processes to optimize the performance. To adjust for best performance of background processes: 1. Press WINDOWS LOGO+PAUSE to open Control Panel > System. 2. Click Advanced system settings > Advanced. In the Performance area, click Settings and select the Advanced tab. 3. From Processor scheduling, select Background services. Click OK. 1.1.5 Checking computer name Important Ensure that the name of the computer hosting Archive Center does not contain any underscores (“_”). To check the computer name: • Press WINDOWS LOGO+PAUSE to open Control Panel > System. If the name contains underscores (“_”), see the procedure below. To change the name of the computer: 1. Click Advanced System Settings > Computer Name > Change. 2. Enter the computer name and the domain. 3. Click OK. You will be asked for credentials and you must restart the computer. 1.1.6 Disabling disk cache of hard disk To avoid loss of data, you must disable the Windows disk caching. To disable disk caching: 1. Open Device Manager > Disk Drives > Properties of the drive > Policies. 2. Select the Quick removal check box. 3. Close all the applications opened before, such as Computer Management. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 13 AR160200-00-IGW-EN-03 Chapter 1 Prerequisites for Archive Center 1.2 Installing Java To install Java: 1. Download Java (JDK or JRE) version 8 Update 72 or later for Windows (64-bit) from the Oracle website (http://www.oracle.com/technetwork/java/javase/ downloads/index.html). Note: Oracle only offers the latest version over the above link. When Java 8 is no longer available, you can get it from the Oracle Support pages (https://support.oracle.com/epmos/faces/DocumentDisplay?id=1439822.1). OpenText recommends running Archive Center with the current JDK update version to avoid security and stability issues. 2. Run the installation file and follow the instructions. Note: You must install the JRE. The JDK alone is not sufficient. 3. For known issues concerning the installation of Java and troubleshooting information, see also this article in the OpenText Knowledge Base (https:// knowledge.opentext.com/knowledge/cs.dll/kcs/kbarticle/view/KB2851395). 1.3 Setting up Apache Tomcat OpenText recommends that you perform the following steps to install and configure Tomcat: 1. Install Tomcat. 2. Configure Java options to optimize performance and further Tomcat components. 3. Configure the Tomcat user and the Tomcat connectors. 1.3.1 Installing Tomcat To install Tomcat: 1. Download the Windows Service Installer for the Tomcat software version 8.5.8 or later from https://tomcat.apache.org/download-80.cgi. 2. Run apache-tomcat-<version>.exe to install the Tomcat software. Notes • Do not use the ZIP file to install Tomcat. • Do not select the Native support because the used version of OpenSSL is incompatible with Archive Center. 14 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 1.3. Setting up Apache Tomcat Tip: In the Choose Components window of the Apache Tomcat Setup, select a Normal type of install. 1.3.2 Configuring Tomcat options For optimal performance, change the following Java settings for Tomcat. To configure Java options: 1. Start the Configure Tomcat tool or run tomcat8w.exe in the <Tomcat_home> \bin folder. 2. Click the Java tab. 3. In the Initial memory pool box, specify at least 512 MB. Note: For optimal performance, set Initial memory pool and Maximum memory pool to the same value. 4. In the Maximum memory pool box, the value you enter should be proportional to the number of users Directory Services will manage. OpenText recommends entering a minimum value for Maximum memory pool as follows: • If your number of users is 25,000 users or less, enter a minimum value of 1024 MB • If your number of users is 25,000 to 50,000 users, enter a minimum value of 2048 MB • If your number of users is 50,000 to 100,000+ users, enter a minimum value of 4096 MB 5. Click OK. 6. Open the <Tomcat_home>\conf\logging.properties file in an editor. 7. In the line starting with .handlers = ..., remove the entry java. util.logging.ConsoleHandler and save the file. 1.3.3 Configuring the Cookie Processor component Configure an option in the context.xml file to avoid issues with the Cookie Processor component of Tomcat. This avoids authentication problems with Archive Center Proxy when trying to sign in. Note: This step is only required if Archive Center must support OpenText Archive Center Proxy. On Archive Center Proxy, no configuration changes are required. To configure the Cookie Processor component: 1. In the <Tomcat_home>\conf folder, open the context.xml in an editor. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 15 AR160200-00-IGW-EN-03 Chapter 1 Prerequisites for Archive Center 2. Add the following line within the <Context> element: <CookieProcessor className="org.apache.tomcat.util.http. LegacyCookieProcessor" /> Example: ... <Context> <!-- Default set of monitored resources. If one of these changes, the --> <!-- web application will be reloaded. --> <WatchedResource>WEB-INF/web.xml</WatchedResource> <WatchedResource>${catalina.base}/conf/web.xml</ WatchedResource> <CookieProcessor className="org.apache.tomcat.util.http.LegacyCookieProcessor" /> <!-- Uncomment this to disable session persistence across Tomcat restarts --> <!-- <Manager pathname="" /> --> </Context> 3. Save the context.xml file and restart Tomcat. 1.3.4 Configuring the Tomcat user Admin rights The user running Tomcat must be a member of the local Administrators group. During the installation of Archive Center, Tomcat must be allowed to write to the C: \ProgramData folder. To add the Tomcat user to the local Administrators group: 1. Log on as a user with administrative rights and run lusrmgr.msc. 2. In the console tree, select Groups, and then open the Properties of the Administrators group. 3. Click Add, browse for the Tomcat user, and then click OK twice. Tomcat user You must run Tomcat with a user. Do not use the local system account. To set the user for Tomcat: 1. Start the Monitor Tomcat tool (tomcat8w.exe). 2. Click the Log On tab and select This account. 3. Enter the name and password of the user to run the Tomcat service. 16 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 1.3. Setting up Apache Tomcat Use the <domain>\<user> notation. The <user>@<domain> notation can lead to connection errors when running the Archive Center Installer. 1.3.5 Configuring the connector and securing Tomcat To use secure connections with TLS (Transport Layer Security; often also referred to as SSL, Secure Sockets Layer), add a connector for HTTPS in the Tomcat configuration. You may have to open ports on your routers when adding ports for SSL/TLS. Automatically redirect clients that access a page with a security constraint requiring SSL/TLS. Important When enabling SSL/TLS, OpenText recommends using a server certificate from a Certificate Authority. The root certificate must be trusted by the JRE or JDK and correctly imported into the truststore (for example, <JRE_HOME> \lib\security\cacerts or <JDK_HOME>\jdk8\jre\lib\security \cacerts). For information about enabling SSL/TLS, see the Tomcat SSL Configuration HOW-TO (https://tomcat.apache.org/tomcat-8.0-doc/ssl-howto.html). To configure Tomcat for SSL/TLS: 1. From the <Tomcat_home>\conf folder, open server.xml in an editor. 2. Ensure that APR Listener is commented out, for example: <!-- <Listener className="org.apache.catalina. core.AprLifecycleListener" SSLEngine="on" /> --> 3. After the line <Service name="Catalina">, define an HTTP connector port according to the example. Example: <!-- Define a HTTP/1.1 Connector on port 8080 --> <Connector port="8080" protocol="HTTP/1.1" redirectPort="8090" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" /> Notes • Keep the default value for protocol (HTTP/1.1). • Keep the default value for disableUploadTimeout (true). • Keep the default value for enableLookups (false). OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 17 AR160200-00-IGW-EN-03 Chapter 1 Prerequisites for Archive Center 4. After the line <Service name="Catalina">, define an SSL connector port. Ensure that the redirectPort from the previous step matches the SSL connector port, as shown in the following example. Example: <!-- Define a SSL HTTP/1.1 Connector on port 8090 --> <Connector port="8090" SSLEnabled="true" scheme="https" secure="true" sslProtocol="TLS" sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1" protocol="HTTP/1.1" acceptCount="100" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" algorithm="SunX509" clientAuth="false" disableUploadTimeout="true" enableLookups="false" keystoreFile="<path to keystore file>" keystorePass="<password for the keystore>" keyAlias="<yourKeyalias>" keystoreType="<pkcs12 OR jks>" /> Notes • If you want installations of Archive Center Proxy to use a certificate to authenticate against Archive Center (rather than user and password), set clientAuth to want. • Keep the default value for protocol (HTTP/1.1). Do not use protocol="org.apache.coyote. http11.Http11AprProtocol". • Keep the default value for disableUploadTimeout (true). • Keep the default value for enableLookups (false). 5. Save the file and restart Tomcat. Further For more information, see the Tomcat SSL Configuration HOW-TO (https:// information tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html). 18 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 1.4. Setting up Directory Services 1.4 Setting up Directory Services Depending on which landscape you want to use, see the corresponding item below. See “Configuring OTDS” on page 19 for information related to all scenarios. See “Scenario-specific settings” on page 21 for further important information for your scenario. • Local, new installation of OTDS The Archive Center Installer can install all components, including OTDS, in one go. This scenario is described in this guide. • Remote, new installation of OTDS First install OTDS on the remote computer. For more information, see OpenText Directory Services - Installation and Administration Guide (OTDS-IWC). Afterwards, install Archive Center. When asked by the Archive Center Installer (Step 10), enter the credentials of the OTDS connection. The Archive Center Installer will create the resource automatically. • Local, existing installation of OTDS The Archive Center Installer will use the existing local installation of OTDS. When asked by the Archive Center Installer (Step 10), enter the credentials of the OTDS connection. Do not use localhost as the Server name but the fully- qualified name. The Archive Center Installer will create the resource automatically. • Remote, existing installation of OTDS When asked by the Archive Center Installer (Step 10), enter the credentials of the OTDS connection. The Archive Center Installer will create the resource automatically. Related Topics • “Prerequisites for Archive Center“ on page 9 • “Configuring Tomcat options” on page 15 1.4.1 Configuring OTDS The following settings are required to use OTDS successfully in all scenarios: Partition, groups, and users User information from Active Directory must be mapped to OTDS. OTDS provides a connector to push changes of user information to Archive Center. The connector is configured through the (synchronized) resource; see Resource on page 20 below. For more information, see Section 3.5 “Synchronized User Partitions” in OpenText Directory Services - Installation and Administration Guide (OTDS-IWC). Further, Archive Center requires the following technical partition, groups, and users. The Archive Center Installer takes care of these settings automatically. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 19 AR160200-00-IGW-EN-03 Chapter 1 Prerequisites for Archive Center • A non-synchronized partition named, for example, OTInternal. This partition must be added to the access role of Archive Center. The technical users for the Application Layer will be added to this partition when creating tenants, for example, ba.tenant@OTInternal. • A user named system.cmis within the OTInternal partition. The password should never expire. You do not need to remember the password as system. cmis is only used as a technical user for the Application Layer (Archive Center CMIS). • A group called $PushConnector with an assigned user called, for example, pushconnector. • The access role of Archive Center requires the Include Groups from OUs setting. For more information, see Section 6.7 “Including/excluding groups from organizational units” in OpenText Directory Services - Installation and Administration Guide (OTDS-IWC). Resource Archive Center is represented in OTDS by a resource (a unique name and an identifier). The Archive Center Installer takes care of creating the resource automatically. For more information, see Section 5.2.2 “Creating a synchronized resource” in OpenText Directory Services - Installation and Administration Guide (OTDS-IWC). Impersonation right Directory Services requires the “impersonate user” right. The Archive Center Installer sets this right automatically. For more information, see Section 5.3 “Configuring access to your resources” in OpenText Directory Services - Installation and Administration Guide (OTDS-IWC). Attribute mapping configuration The OTDS user attribute mapping and group attribute mapping depend on the scenario. See “Scenario-specific settings” on page 21. For more information, see also Section 5.2.1.3 “Using resource attribute mappings” in OpenText Directory Services - Installation and Administration Guide (OTDS-IWC). ACLs The CMIS ACLs must be based on OTDS user IDs (not on the user name). Names of users and groups are treated case-insensitive in OTDS, while CMIS allows for case-sensitive names. If the ACLs are based on the user name it can happen that permissions are not mapped correctly, because CMIS distinguishes between, for example, access.default@OTInternal and access. default@otinternal. 20 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 1.4. Setting up Directory Services 1.4.2 Scenario-specific settings To run Archive Center scenarios, Directory Services is mandatory. In particular, OTDS is used for the following scenarios: FILE SHARE Use Directory Services to let file share users be able to access their files using a CMIS interface. File share users are mapped to Directory Services users. Attribute mapping configuration The oTExternalSID field must include objectSID, in the %s format. MY ARCHIVE Use Directory Services to let users have web access to their archived documents through My Archive. You must allow the corresponding Directory Services users to access Archive Center by adding them to the access role of Archive Center. My Archive users must be members of the OTDS group OTInternal \<tenant>_UG, either directly or through another group membership. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 21 AR160200-00-IGW-EN-03 Chapter 2 Setting up the database Archive Center supports Microsoft SQL Server, Azure SQL Database, and Oracle Database. The database can be installed locally or remotely. 2.1 Setting up Microsoft SQL Server or Azure SQL Database Adhere to the following: • You can either use an existing database or create a new database. The database can reside on the computer on which Archive Center is installed or on a dedicated database server. • The Microsoft SQL Server or Client software has to be installed beforehand. For remote database servers, the database and database user must have been created. • If you use a local installation of SQL Server, the Archive Center Installer will create the database and the user. • For mandatory characteristics of the database for Archive Center, see “Database characteristics” on page 23. • SQL Server must use static ports. Dynamic ports will not work. For more information, see “Configuring network connectivity” on page 47. For a detailed instruction how to install an example SQL Server database for Archive Center, see “Appendix: Setting up the database in Microsoft SQL Server“ on page 47. Using a remote database Named Named instances are supported for remote databases and require a static TCP port. instances 2.1.1 Database characteristics Observe the following requirements and recommendations for the Archive Center database: • Database collation SQL_Latin1_General_CP1_CS_AS (code page 1252) is recommended. • OpenText recommends that the sort order of the database collation is case- sensitive unless other products require a case-insensitive database. For the following options, the respective settings are required: OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 23 AR160200-00-IGW-EN-03 Chapter 2 Setting up the database AZURE SQL DATABASE • Auto Close must be False. • Auto Create Statistics must be True. • Auto Shrink must be False. • Auto Update Statistics must be True. • Close Cursor On Commit Enabled must be False. • ANSI NULL Default must be True. • ANSI NULLS Enabled must be True. • ANSI Padding Enabled must be True. • ANSI Warnings Enabled must be True. • Arithmetic Abort Enabled must be True. • Concatenate Null Yields Null must be True. • Numeric Round-Abort must be False. • Quoted Identifiers Enabled must be True. SQL SERVER • Recovery model must be Full. • Auto Close must be False. • Auto Create Statistics must be True. • Auto Shrink must be False. • Auto Update Statistics must be True. • Close Cursor On Commit Enabled must be False. • ANSI NULL Default must be True. • ANSI NULLS Enabled must be True. • ANSI Padding Enabled must be True. • ANSI Warnings Enabled must be True. • Arithmetic Abort Enabled must be True. • Concatenate Null Yields Null must be True. • Numeric Round-Abort must be False. • Quoted Identifiers Enabled must be True. • Page Verify must be CHECKSUM or TORN_PAGE_DETECTION. Note: CHECKSUM protection can catch more errors but is also more resource intensive than TORN_PAGE_DETECTION. For details, see the Microsoft website (http://msdn.microsoft.com/en-us/library/ aa337525.aspx). • SQL Server must be configured to support at least 200 concurrent connections (default: unlimited). This value depends on the web server configuration value for the maximum number of supported threads. For Apache Tomcat, this is the maxThreads connector parameter. Set the database processes parameter to maxThreads + 50. • There must be two non-default file groups for Archive Center data and index, respectively. • The database user provided for Archive Center must be the dbo of the database; see below for details. 24 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 2.1. Setting up Microsoft SQL Server or Azure SQL Database Permissions for During the installation of Archive Center with a local instance of SQL Server, the creating and database user is created as database owner with the full scope of assigned running the Archive Center administration permissions. However, technical users who run an Archive Center database database on a regular basis do not need the full scope of administration permissions that are required for creating a database. Following security considerations, the permissions of the database account used by Archive Center can be reduced after successful installation. For more information, see “Rights for database users before and after installation” on page 50. 2.1.2 Testing the database In case the database already exists, verify that the database has all the required features. Run the StPreSchemaCreateMSSQL.sql check script in a command window (do not use Powershell). You can find the script in the Schema and Pre- upgrade checks for Archive Center 16.2.zip file, which is available on My Support (https://knowledge.opentext.com/knowledge/cs.dll/Overview/68246636). To test the database: 1. Prerequisites for Azure SQL Database: a. Install Microsoft Command Line Utilities for SQL Server, available from the Microsoft website (https://www.microsoft.com/en-us/download/ details.aspx?id=53591), which require the Microsoft ODBC Driver for SQL Server (https://www.microsoft.com/en-us/download/details.aspx? id=53339). b. Ensure that the options described in “Database characteristics” on page 23 are configured. For example, run the following commands: ALTER DATABASE <database> SET ANSI_NULLS on, ANSI_NULL_DEFAULT on, ANSI_WARNINGS on, QUOTED_IDENTIFIER on, ANSI_PADDING on, ARITHABORT on GO 2. Process the script as follows: sqlcmd -U <user> -P <passwd> -d <database> -S <database server> \<instance>,<port> ‑i StPreSchemaCreateMSSQL.sql ‑v fgd='<data file group>' fgi='<index file group>' Azure SQL Database Leave <data file group> and <index file group> empty in case of Azure SQL Database: sqlcmd -U <user> -P <passwd> -d <database> ‑S <database server>\<instance>,<port> ‑i StPreSchemaCreateMSSQL.sql ‑v fgd='' fgi='' OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 25 AR160200-00-IGW-EN-03 Chapter 2 Setting up the database Example 2-1: Testing the database We assume that you process this script on the database server. The following example shows default values for <instance> and <port>: sqlcmd -U acdbuser -P acdbpassword -d AC -S localhost \MSSQLSERVER,1433 ‑i StPreSchemaCreateMSSQL.sql ‑v fgd='AC_DATA' fgi='AC_INDEX' In this example, <database server>\<instance> is assumed to be MYSERVER\MYINSTANCE, with the non-default port 15050: sqlcmd -U ecr -P ecr -d ECR -S MYSERVER\MYINSTANCE,15050 ‑i StPreSchemaCreateMSSQL.sql ‑v fgd='ECR_DATA' fgi='ECR_INDEX' 3. The script shows the affected rows per tested feature (lines starting with “(0 rows affected)”, for example). The script must not yield any messages beginning with FATAL:. If you do not get any FATAL: messages, the configuration of connection and user is correct. 2.2 Setting up Oracle Database You can either use an existing database or create a new database. The database can reside on the computer on which Archive Server is installed or on a dedicated database server. The Oracle server or client software has to be installed beforehand. A database and a database user must have been created. For mandatory settings of the database for Archive Center, see “Database characteristics” on page 27. For a detailed instruction how to install an example database for Archive Center, see “Appendix: Setting up the database in Oracle Database“ on page 53. Important To be able to connect to Oracle Database, additional client software is required: Either install the Oracle Instant Client for Windows or the Oracle Full Client for Windows. This is true even if the Oracle Database resides on the same host. The bin folder of the client software must occur in the PATH variable before the bin folder of the server software. 26 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 2.2. Setting up Oracle Database 2.2.1 Database characteristics The following requirements for Archive Server database are mandatory. • The database character set must be AL32UTF8. To verify, execute select value from nls_database_parameters where parameter='NLS_CHARACTERSET'; • The national character set must be AL16UTF16 (Unicode UTF-16 Universal character set). To verify, execute select value from nls_database_parameters where parameter='NLS_NCHAR_CHARACTERSET'; • The ARCHIVELOG mode must be set. To verify, execute select log_mode from v$database; • The database must be configured to support at least 200 processes. To verify, execute select value from v$parameter where name = 'processes'; This value depends on the web server configuration value for the maximum number of supported threads. For Tomcat, this is the maxThreads connector parameter. Set the database processes parameter to maxThreads + 50. • There must be at least two non-default tablespaces with a block size of 8 KB for the Archive Center data and index, respectively. These tablespaces must not be named data and index. To verify, execute select tablespace_name, block_size from dba_tablespaces; • The database user provided for Archive Center must have the system and object privileges listed in “Creating the database user” on page 58. • The listener must be configured to support TCP/IP. 2.2.2 Remote DB on Oracle RAC In case of a remote database that resides on an Oracle Real Application Cluster (RAC), you must adapt the tnsnames.ora file. To use a remote database with Oracle RAC: 1. Open the tnsnames.ora file in an editor. 2. Extend tnsnames.ora to include a TNS service name that points to the cluster host and the SID of the cluster. Example: RACLINUX = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = rac-cluster01.example.com) OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 27 AR160200-00-IGW-EN-03 Chapter 2 Setting up the database (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = ORCL) ) ) 3. Before starting the Archive Server setup, ensure that at least one dedicated node is running. 4. During the Archive Server setup, enter the following database parameters: • Enter the TNS service name from Step 2. • As database server, use the cluster host name, not the name of a dedicated node. • As Oracle SID, use the SID of the cluster, not the SID of the instance running on a dedicated node. 2.2.3 Testing the database To verify that the database has all the required features, run the StPreSchemaCreateOracle.sql check script in a command window (do not use Powershell). You can find the script in the Schema and Pre-upgrade checks for AC 16.zip file, which is available on My Support (https://knowledge.opentext.com/ knowledge/cs.dll/Overview/62940896). Important Ensure that the owner of the Apache Tomcat process has at least read access on the $ORACLE_HOME\network\admin\tnsnames.ora file. To test the database: 1. Connect to the database. Example: sqlplus ecr/ecr@ecr_<db_host> 2. To test the characteristics of the database, enter: @StPreSchemaCreateOracle.sql You are prompted for the data and index tablespace names. 3. The script must not yield any messages beginning with FATAL:. If you do not get any FATAL: messages, the configuration of connection and user is correct. Testing Oracle RAC In case of Oracle RAC, enter a RAC node as the database server and SID, and the RAC service as the service. 28 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 2.2. Setting up Oracle Database Example: [oracle@racnode1 ~]$ sqlplus ecr/ecr@ORCL SQL*Plus: Release 12.1.0.2.0 Production on Fri Aug 18 13:27:40 2017 Copyright (c) 1982, 2014, Oracle. All rights reserved. Last Successful login time: Fri Aug 18 2017 13:26:39 -04:00 Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options SQL> @/tmp/StPreSchemaCreateOracle.sql Please enter data tablespace: USERS Please enter index tablespace: USERS WARNING: Cannot determine archive log mode of database - please ensure it is set to ARCHIVELOG WARNING: Cannot determine number of processes - please ensure it is 200 at the least. INFO: user=ECR INFO: database server=racnode2 INFO: service=ORCL INFO: oracle sid=ORCL2 Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 29 AR160200-00-IGW-EN-03 Chapter 3 Installing Archive Center Archive Center comes with an integrated installer (“Archive Center Installer”), which performs the following tasks: 1. Checking prerequisites: Java and Tomcat correctly installed and configured. 2. Asking for input parameters. 3. Shutting down Tomcat. 4. Installing and configuring components. 5. Starting Tomcat. 6. Starting OpenText Administration Client or, if a “default tenant” was created during installation, starting Archive Center Administration in a browser. Related Topics • “Prerequisites for Archive Center“ on page 9 Background • “About OpenText Archive Center“ on page v 3.1 Running the Archive Center Installer When all prerequisites are met, you can start the installation. Oracle RAC Ensure to avoid switches to another database node while running the setup. During installation, switches do not happen transparently for Archive Center. The installation can fail in this case. To install Archive Center: 1. Download the self-extracting installer file (ArchiveCenterInstaller_16.2.0. exe) from OpenText My Support (https://knowledge.opentext.com/knowledge/ llisapi.dll/Open/52699338). 2. Log on to the server as a user with administrator rights. Remote setup If you want to run the installer using Microsoft Remote Desktop (Terminal Service Client), you must use the /admin option when establishing the remote session. 3. Run ArchiveCenterInstaller_16.2.0.exe. The Archive Center Installer starts. 4. Accept the License Agreement. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 31 AR160200-00-IGW-EN-03 Chapter 3 Installing Archive Center 5. The Archive Center Installer checks the prerequisites. When all checks have finished successfully, click Next. 6. On the Archive Center page, enter the following: External host name Name of the computer that will host Archive Center (default: name of the local host). Enter a fully-qualified host name. Archive Center operating mode Depending on the scenario, select one of the following: Multi tenant Archive Center is installed in a cloud infrastructure, usually within the company’s network. Archiving (write) and read requests for different tenants are separated entirely. To use Archive Center with more than one tenant, Archive Center Proxy is required. Note: Ensure that encryption is configured properly. For more information, see “Configuring collections” in OpenText Archive Center - Scenario Configuration Guide (AR-CGD). Single tenant Archive Center is installed on a dedicated server within the company’s network. Only one tenant is used, meaning that write and read requests are not separated. Archive Center Proxy is only required in certain 32 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 3.1. Running the Archive Center Installer scenarios (for example, when running a cluster and using CMIS/CMIS DP). For corresponding default values, see Section 1.2 “Operation mode” in OpenText Archive Center - Scenario Configuration Guide (AR-CGD). Create a default tenant If selected, the Archive Center Installer creates a tenant ready to be used called “default”. In “multi tenant” mode, you can safely select this option. You can create more tenants afterwards, for example, for production systems. In “single tenant” mode, only one tenant is possible. Archive Center Installer creates the “default” tenant automatically. 7. On the Application Server page, enter the following: Note: Depending on your system, some settings may not be changeable. For example, if only one instance of Tomcat is installed, the Archive Center Installer automatically uses its settings. Select Tomcat Select the instance of Tomcat to be used (if applicable). Tomcat HTTP port Select the HTTP port configured for Tomcat; default: 8080 (if applicable). Allowed values are 1 to 65534. Tomcat HTTPS port Select the HTTPS (SSL/TLS) port configured for Tomcat; default: 8090 (if applicable). Allowed values are 1 to 65534. Windows Service user Enter the name of the Tomcat service user (if applicable). Ensure that the <domain>\<user> notation is used. The <user>@<domain> notation can lead to connection errors. Windows Service user password Enter the password of the Tomcat service user. 8. On the Database System page, select the database system to be used. If you use an installation of Microsoft SQL Server on the same computer, you can additionally let the installer create the database for Archive Center. Otherwise (Oracle Database or remote SQL Server), the database must exist already. 9. On the Database Parameter page, do the following, depending on your database installation: SQL SERVER • Local database OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 33 AR160200-00-IGW-EN-03 Chapter 3 Installing Archive Center Port Enter the port configured for the database; default: 1433. Super user (sa) Enter the password of the database’s sa user. password Database user Enter the name of the user who will be created for the Archive Center database. Database user password Create and enter a password for the new database user and confirm it. • Remote database Server name Enter the name of the computer hosting the database. Port Enter the port configured for the database or leave blank to use the default port (1433). Instance Enter the instance name of the SQL Server (default: MSSQLSERVER). Database name Enter the name of the database. Important The database must exist. Database user Enter the name of the database user. Database password Enter the password of the database user. Data filegroup Enter the name of the data filegroup. Index filegroup Enter the name of the index filegroup. • Azure SQL Database Server name Enter the name of the computer hosting the database, for example: myexample.database.windows.net Port Enter 1433. Instance Enter MSSQLSERVER. Database name Enter the name of the database. Important The database must exist. Database user Enter the name of the database user. Database password Enter the password of the database user. Data filegroup Leave empty. Index filegroup Leave empty. 34 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 3.1. Running the Archive Center Installer ORACLE DATABASE Server name Enter the name of the computer hosting the database. If the database is an Oracle RAC, enter the name of the RAC cluster. Important Do not enter localhost, even if the database resides on the same computer. Instead, enter the actual hostname. Port Enter the port configured for the database; default: 1521. Database name Enter the name of the database. Important The database must exist. Database user Enter the name of the database user. Password Enter the password of the database user. Service name Enter the TNS service as configured by the Oracle Net Configuration Assistant (NetCA); default: ecr_<db server>. If the database is a remote Oracle RAC, enter the TNS service name configured in “Remote DB on Oracle RAC” on page 27. Oracle SID Enter the system identifier for the database; default: ECR. If the database is an Oracle RAC, enter the ORACLE_SID of the node specified as the Server name (not the abstract SID of the RAC). Data file group Enter the name of the data file group. Index file group Enter the name of the index file group. Local TNS admin Enter the folder where the Oracle net configuration files are located; default: $ORACLE_HOME/network/ admin. Important Only local paths are supported. UNC paths or mapped network drives will not work. Local Oracle home Enter the folder of the Oracle installation. If you use Oracle client, enter the folder of the Oracle client installation. If you use Oracle instant client, enter the location to which the Oracle instant client package was extracted. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 35 AR160200-00-IGW-EN-03 Chapter 3 Installing Archive Center Note: Archive Center Installer tries to connect to the remote database for 30 seconds. In case of incorrect entries for server name, instance, or port, the title bar shows “(Not Responding)” and you have to wait for the result of the connection test. 10. On the Directory Services page, do one of the following: • To install a new, local instance of OTDS, select the corresponding option and choose a password for the OTDS administrator ([email protected]). • To use an existing installation of OTDS, select the corresponding option and specify the connection credentials. Enter the OTDS server URL in the form <protocol>://<hostname>.<domain>:<port>, for example: https:// otdsserver.example.com:8090 Do not add any characters after <port>. For example, https:// otdsserver.example.com:8090/ will fail. 11. On the Folders page, you can change default parameters if required, for example, installation folders. For details, see “Folder settings” on page 38. Important Do not use the default folders for production systems. Plan carefully where to locate the files for the database and for temporary storage as these may become very big. Installation folder for OTDS If you change the Installation folder to another partition than C:, ensure that the new partition supports the 8.3 format. For more information, see “Enabling 8.3 format” on page 40. 12. Click Install to start the installation. If you selected to create a default tenant, the OpenText Archive Center Administration page is started in a browser window after the installation has finished. Otherwise, OpenText Administration Client is started. You can sign in using the credentials given in the summary shown in the next step for first testing. 13. Click Next. If an installation fails In case of an error during installation, click Close. To find out which setup caused the error, see the %temp%\OpenText\ Installer_<date>_<time>_.log file. See also “Troubleshooting” on page 39. The Summary page informs you about the following: • After installation, the password of the dsadmin user (superuser of Archive Center) initially is the empty string. For security reasons, set the password as 36 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 3.1. Running the Archive Center Installer soon as possible. Although signing in as dsadmin into Administration Client is not possible, dsadmin is still used by other components. Important Immediately set the password of the dsadmin user (using Administration Client). For more information, see “Changing the dsadmin password” on page 43. Changing the password of dsadmin is also required when using OTDS. • Local SQL Server only: A database named AC<n> was created in SQL Server with a user named acadmin. • Archive Center was started automatically (that is the Apache Tomcat and Archive Spawner processes). Tip: In a command window, verify the status of the Archive Spawner process by running the following commands: > <OT install AC>\bin\profile.bat > spawncmd status where <OT install AC> by default is C:\Program Files\OpenText\ Archive Server 16.2.0. • If you want to store the summary information for future reference, click Save Summary. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 37 AR160200-00-IGW-EN-03 Chapter 3 Installing Archive Center 14. The notification server needs to be restarted manually. Open a command window and enter the following: spawncmd restart notifSrvr Continue with the configuration as described in “Configuring Archive Center“ on page 43. Creating tenant Before users can sign in to Archive Center Administration, their tenant group must exist. In the multi tenant operation mode, Archive Center Installer can create a tenant for demonstration purposes. In the single tenant operation mode, no tenant should have been created. You must create the tenants in Administration Client: Users and Groups > System > New Tenant. For more information, see Section 9.7 “Creating tenants” in OpenText Archive Center - Administration Guide (AR-ACN). Related Topics • “Setting up Apache Tomcat” on page 14 • “Setting up Directory Services” on page 19 3.2 Folder settings You can specify the following on the Folders page: No overlapping folders All installation and configuration folders must be distinct. For example, you cannot use one folder for the exports and for the search index. Installation folder Folder where Archive Center is installed. Configuration folder Folder where configuration data is stored. DB data files Folder for the database’s data (MDF) files (local database only). DB index files Folder for the database’s index (NDF) files (local database only). DB log files Folder for the database’s log (LDF) files (local database only). DB primary file group Folder for the database’s primary filegroup (local database only). Document Pipeline folder Folder where documents are saved temporarily. Export folder Folder in which the My Archive and Archive Center Access web clients save files when their export function is used. 38 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 3.3. Troubleshooting Important Depending on the scenario and usage, the exported files or their number can become very big. Ensure that you provide enough disk space for the export directory. You can also change the folder location later using the Directory for the generated EDRM-XML files configuration variable (internal name: AS.AS.BIZ_EXPORT_DIRECTORY). Search index folder Folder in which the search index for the My Archive and Archive Center Access web apps is stored. Important Depending on the scenario and usage, the index can become very big. Ensure that you provide enough disk space. You can also change the folder location later using the ES_DATA_DIRECTORY configuration variable in the <OT config AC>\AS.Setup file. Buffer volumes Folder in which the default disk volumes for buffers are created. Important Do not use the default folder (%ProgramData%\OpenText\buffervols) for production systems. For more information about prerequisites for hard disk systems, see Section 5.2 “Configuring disk volumes” in OpenText Archive Center - Administration Guide (AR-ACN). 3.3 Troubleshooting • Retrying installation If for some reason the Archive Center installation failed, you usually cannot rerun the installation because changes made to the file system and the database, for example, cannot be revoked automatically. Before trying to run the installer again, do the following. To clean up the system after a failed installation: 1. Stop the Apache Tomcat and Archive Spawner services. 2. Remove each of the following setups by clicking Control Panel > Uninstall a program, if applicable: OpenText Administration Client, OpenText Archive Center CMIS, OpenText Archive Monitoring Server, OpenText Archive Center, OpenText Directory Services, OpenText Document Pipeline Base, Document Pipeline Info, OpenText File Archiving OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 39 AR160200-00-IGW-EN-03 Chapter 3 Installing Archive Center 3. Delete the database AC on SQL Server. • In case of a local database, additionally remove the database user (acadmin). • In case of a remote database, recreate an empty database (for example, AC). The database user (for example, acadmin) must still exist. 4. Delete the following folders. If you changed the default path, delete the folder accordingly: Installation folder (C:\Program Files\OpenText), Configuration folder (C:\ProgramData\OpenText) Note: Local OTDS installations are always located in C:\ProgramData\ OpenText. Delete this folder even if you changed the default path. 5. To clean up the Tomcat installation, delete all files and folders that were not present in the original Tomcat instance. In particular, the Archive Center Installer placed files in the following folders: <Tomcat_home>\conf\ Catalina\localhost, <Tomcat_home>\webapps, and <Tomcat_home>\work \Catalina\localhost. 6. Open the window to edit the system environment variables and delete all System variables that start with ECM_. Further, remove the entry for the Archive Spawner in the Path variable (default: C:\Program Files\Common Files\Open Text\Spawner\bin;). Tip: Press WINDOWS + PAUSE to open the System item in Control Panel, and then click Advanced system settings. • Enabling 8.3 format Directory Services must be installed on a drive or partition that supports the 8.3 format. Trying to install OTDS on a partition that does not support 8.3 format will lead to an error. By default, C: supports 8.3 format. To check whether a partition supports the 8.3 format: • Open a command window and run the following command to check the drive <drive>: FSUTIL.EXE 8dot3name query <drive> For example, FSUTIL.EXE 8dot3name query C: always yields The volume state for Disable8dot3 is 0 (8dot3 name creation is enabled). The registry state of NtfsDisable8dot3NameCreation is 2, the default (Volume level setting). Based on the above two settings, 8dot3 name creation is enabled on C:. To enable 8.3 format for a partition: • To enable 8.3 format for the drive <drive>, run: 40 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 3.3. Troubleshooting FSUTIL.EXE 8dot3name set <drive> 0 Related Topics • “Prerequisites for Archive Center“ on page 9 • “Configuring basic settings” on page 10 • “Setting up Directory Services” on page 19 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 41 AR160200-00-IGW-EN-03 Chapter 4 Configuring Archive Center Although Archive Center is ready to be used after a successful installation, you must perform some additional configurations. In particular, you can change passwords for security reasons. Further configuration for the Application Layer To use the Application Layer and the web apps of Archive Center, several additional steps are required. For example, you must create tenants. For more information, see OpenText Archive Center - Scenario Configuration Guide (AR-CGD). 4.1 Signing in to Archive Server in Administration Client To authenticate against Archive Server using Directory Services, start Administration Client and sign in as user [email protected]. Note: To administer users, groups, and tenants, you use the Directory Services web client, which is accessible under <protocol>://<host>:<port>/otds- admin. For more information about working with OTDS, see OpenText Directory Services - Installation and Administration Guide (OTDS-IWC). 4.2 Changing the dsadmin password The initial password of the dsadmin superuser is not set. You must assign a password as soon as possible. Note: Although signing in as dsadmin into Administration Client is not possible when OTDS is used, dsadmin is still used by other components. To set the password of the dsadmin user: 1. Sign in to Administration Client as an OTDS user with administrator rights (for example, [email protected]). 2. In the console tree, open the Archive Server > System > Users and Groups node, and in the result pane, select the Users tab. 3. Open the Properties of the dsadmin user and change the password. 4. Restart the Apache Tomcat and Archive Spawner services for the changes to take effect. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 43 AR160200-00-IGW-EN-03 Chapter 4 Configuring Archive Center 4.3 Changing the password of the database user The login (DBLOGIN) and password (DBPASSWORD) of the database user are encrypted and stored in the setup file DBS.Setup. If you change the password of the database user, you must also change the corresponding entry as described below. To change the DB user password: 1. Start Administration Client and sign in to Archive Server. 2. In the console tree, expand the Archive Server node. 3. Create a secure password. Note: Characters allowed within a password are all printable ASCII characters except: “;”, “'” and “"”. 4. Select the Configuration object in the console tree and search for the User password of database configuration variable (internal name: AS.DBS.DBPASSWORD). 5. Open the Properties of the User password of database configuration variable and enter the new password. 6. Click OK. The password is automatically stored and encrypted. 7. Change the password in the database application. 8. Restart the Apache Tomcat and Archive Spawner services for the changes to take effect. 4.3.1 Oracle Database only: Checking the expiry date of the password You can check the expiry date of the user password. Run an SQL statement as follows: Example: sqlplus ecr/ecr@ecr_<local_host> select username,account_status,expiry_date from user_users; Note: With Oracle 11, the default password policy changed. Now, by default a user password expires after 180 days. If you do not want your password to expire, consult your local database administrator to modify your profile accordingly. Further See also the Oracle information about security (http://www.oracle.com/technetwork/ information database/security/overview/index.html). 44 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 4.4. Configuring the ports for the SAP gateway 4.4 Configuring the ports for the SAP gateway For the SAP Document Pipeline to function, the gateway ports need to be configured in Windows. To configure the ports for the SAP gateway: • Open the C:\Windows\System32\drivers\etc\services file in an editor and add the following lines. Depending on the gateway instances you use, you do not need to add all 100 lines: sapgw00 3300/tcp #SAP Gateway sapgw01 3301/tcp #SAP Gateway ... ... ... sapgw99 3399/tcp #SAP Gateway 4.5 Configuring different internal and external hostname If in a cloud environment the internal and external name of the Archive Center host diverge, do the following. To configure diverging internal and external hostnames: 1. Start Administration Client and connect to Archive Center (Archive Center). 2. Select the Configuration object in the console tree and search for my_host. 3. Open the Properties of the External Archive Server Host Name configuration variable (internal name: AS.DS.MY_HOST_NAME). As Value, specify the fully qualified external hostname, for example: externalhost.domain1.example.com 4. Open the Properties of the Alias Archive Server Host Name(s) configuration variable (internal name: AS.DS.MY_HOST_ALIASES). As Value, specify a comma-separated list containing the internal hostname, external hostname, and the fully qualified external hostname, for example: internalhost,externalhost,externalhost.domain1.example.com Note: Changes to these settings do not take effect until the application server is restarted. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 45 AR160200-00-IGW-EN-03 Chapter 4 Configuring Archive Center 4.6 Configuring certificate authentication for Archive Center Proxy Before Archive Center Proxy can be installed using the Authenticate with SSL Client Certificate option, you must change a configuration variable in Archive Center. To accept SSL/TLS client certificates for authentication: 1. Start OpenText Administration Client and connect to Archive Center (Archive Center). 2. Select the Configuration object in the console tree and search for accept ssl. 3. Open the Properties of the Accept SSL client certificates for authentication configuration variable (internal name: AS.AS.BIZ_ACCEPT_SSL_CLIENT_CERTIFICATE). 4. Set the Value to on, and then click OK. Configuring Further, you must configure Tomcat to request a client certificate by setting Tomcat clientAuth="want" for the SSL/TLS connector in the server.xml file. For more information, see “Configuring the connector and securing Tomcat” on page 17. 46 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 Chapter 5 Appendix: Setting up the database in Microsoft SQL Server This chapter provides an example for the setup of Microsoft SQL Server. It does not cover Azure SQL Database. Settings to be considered during installation of SQL Server Collation tab Using a case-sensitive (CS) and accent-sensitive (AS) database is recommended unless other products require a case-insensitive database. The collation of this database should be the same as the collation of SQL Server’s tempdb for technical reasons. Therefore, OpenText recommends selecting a case-sensitive and accent-sensitive server collation for maximum performance and compatibility. For example, select SQL_Latin1_General_CP1_CS_AS. Authentication Mode On the Database Engine Configuration page, select the Account Provisioning tab, and then enable SQL Server Authentication as Authentication Mode (for example, as mixed mode). Enter and confirm the password for the sa logon. 5.1 Configuring network connectivity Enable SQL Server to be connected via TCP/IP using SQL Server Configuration Manager. The SQL Server must use static ports. Dynamic ports will not work. To configure network connectivity: 1. Start SQL Server Configuration Manager. 2. Expand SQL Server Network Configuration > Protocols for MSSQLSERVER. 3. Double-click TCP/IP. If it is not enabled yet, enable it. On the IP Addresses tab, scroll down to the IPAll area and ensure that TCP Dynamic Ports is blank, and that TCP Port is set to the SQL Server port (default: 1433). OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 47 AR160200-00-IGW-EN-03 Chapter 5 Appendix: Setting up the database in Microsoft SQL Server 4. If the Shared Memory protocol is enabled, disable it. 5. Analogously, enable TCP/IP and disable Shared Memory for the client protocols of SQL Native Client [11.0] Configuration and SQL Native Client 11.0 Configuration (32 bit). 6. If you had to change anything in the previous steps: Expand SQL Server Configuration Manager (Local) > SQL Server Services, right-click SQL Server (MSSQLSERVER), and then click Restart. SQL Server is now ready to be connected using TCP/IP. 48 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 5.2. Creating the SQL Server login 5.2 Creating the SQL Server login In the SQL Server Management Studio (Security > Logins), create a new login (for example, ecr). Select the SQL Server Authentication option. Clear the Enforce Password policy option. 5.3 Creating the database 1. In the SQL Server Management Studio, connect to the database engine as sa. 2. Select New Database. 3. Under General, enter a database name (for example, ECR) and the owner of the database (for example, ecr). 4. Under Filegroups, create one filegroup for data and one for index (for example, ECR_DATA and ECR_INDEX). 5. Create the database files for the data and the index filegroups: a. Add two files for the data and index filegroups created before: Choose a logical name for the files (for example, ECR_DATA_1 and ECR_INDEX_1, respectively). Choose the respective filegroup (in the example, select the ECR_DATA filegroup for the ECR_DATA_1 file and the ECR_INDEX filegroup for the ECR_INDEX_1 file). Choose a path where the files are to be located. The files will be created in the folder you enter. The folder must exist. b. Choose a path for the primary filegroup and the transaction log (named <database name> and <database name>_log, respectively. Important Do not use the default locations in the SQL Server installation folder. The transaction log should be located on an empty disk without any other files. Specify a suitable initial size and enable unrestricted autogrowth for each of the files: Example: Logical Name File Type Filegroup Initial Size Autogrowth (MB) ECR Rows Data PRIMARY 50 By 1 MB ECR_log Log n/a 100 By 10 % ECR_DATA_1 Rows Data ECR_DATA 100 By 100 MB ECR_INDEX_1 Rows Data ECR_INDEX 100 By 100 MB OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 49 AR160200-00-IGW-EN-03 Chapter 5 Appendix: Setting up the database in Microsoft SQL Server c. Click Options and set the following: i. Select SQL_Latin1_General_CP1_CS_AS as the collation. Note: CS (case-sensitive) and AS (accent-sensitive) are recommended. ii. Set the following options to True: Auto Create Statistics, Auto Update Statistics, ANSI NULL Default, ANSI NULLS Enabled, ANSI Padding Enabled, ANSI Warnings Enabled, Arithmetic Abort Enabled, Concatenate Null Yields Null, Quoted Identifiers Enabled iii. Set the following options to False: Auto Close, Auto Shrink, Close Cursor On Commit Enabled, Numeric Round-Abort iv. Set Page Verify to CHECKSUM or TORN_PAGE_DETECTION. Note: CHECKSUM protection can catch more errors but is also more resource intensive than TORN_PAGE_DETECTION. For details, see the Microsoft website (http://msdn.microsoft.com/en- us/library/aa337525.aspx). d. Click OK to create the database. 6. Under Security > Login, select the Properties of the user created before (for example, ecr). Select the database created before (for example, ECR) as the default database and click OK. 5.4 Rights for database users before and after installation Permissions for During the installation of Archive Center with a local instance of SQL Server, the creating and database user is created as database owner with the full scope of assigned running the Archive Center administration permissions. However, technical users who run an Archive Center database database on a regular basis do not need the full scope of administration permissions that are required for creating a database. Following security considerations, the permissions of the database account used by Archive Center can be reduced after successful installation. Database permissions/roles required for running a database schema • db_datareader • db_datawriter • public • Permission to execute stored procedures Recommendation: execute permission on the schema 50 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 5.4. Rights for database users before and after installation To downgrade the database permissions: 1. Transfer the ownership to a new database user. Example: USE [ECR] CREATE LOGIN ecrowner WITH PASSWORD='ecrowner', DEFAULT_DATABASE=ECR, CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF; ALTER AUTHORIZATION ON DATABASE::ECR TO ecrowner; GO 2. Map the existing login to the new database user with restricted permissions. Example: USE [ECR]; CREATE USER [ecr] FOR LOGIN [ecr]; EXEC sp_addrolemember 'db_datawriter', 'ecr'; EXEC sp_addrolemember 'db_datareader', 'ecr'; GRANT EXECUTE ON SCHEMA::[dbo] TO [ecr]; GO Restricted Instead of downgrading the database permission, you can create a new login for a permissions new database user with restricted permissions. After that, change the Archive Center database access configuration to the new database account. To create a new database account: 1. Create a new login and database user. Example: USE [ECR]; CREATE LOGIN ecrdb WITH PASSWORD='ecrdb', DEFAULT_DATABASE=ECR, CHECK_EXPIRATION=OFF,CHECK_POLICY=OFF; CREATE USER [ecrdb] FOR LOGIN [ecrdb] WITH_DEFAULT_SCHEMA=[dbo]; EXEC sp_addrolemember 'db_datawriter', 'ecrdb'; EXEC sp_addrolemember 'db_datareader', 'ecrdb'; GRANT EXECUTE ON SCHEMA::[dbo] TO [ecrdb]; GO 2. Configure the Archive Center database access: a. Start Administration Client and sign in to Archive Server. b. Change the AS.DBS.DBLOGIN and AS.DBS.DBPASSWORD parameters to reflect the new database login. For more information, see “Changing the password of the database user” on page 44. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 51 AR160200-00-IGW-EN-03 Chapter 5 Appendix: Setting up the database in Microsoft SQL Server Note: Changing DBLOGIN involves the same steps as when changing DBPASSWORD. 52 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 Chapter 6 Appendix: Setting up the database in Oracle Database Local database To set up a test database, you have to perform the following procedures on the database server: 1. Set the language. 2. Install the Oracle server software and relevant patches. 3. Create the Oracle listener. 4. Create the database. 5. Create the database user. 6. Configure the Oracle listener. 7. Configure the TNS service names. Remote In addition, if the database is located on a different server than Archive Center, you database have to perform the following procedures on the Archive Server computer: 1. Install the Oracle Client software and relevant patches. 2. Configure the network service names or copy the tnsnames.ora and sqlnet. ora files from the database server to the Archive Server computer. Language settings To start the Oracle Installer or tools in English, ensure that the current regional setting parameter is English (United States). To set the regional options: 1. In Control Panel, click Regional and Language Options > Formats. 2. In the Formats drop-down list, select English (United States). OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 53 AR160200-00-IGW-EN-03 Chapter 6 Appendix: Setting up the database in Oracle Database 6.1 Setting up Oracle Database server 6.1.1 Creating the Oracle Listener 1. To start the Net Configuration Assistant, from the Start menu, click Oracle - <Oracle installation name> > Configuration and Migration Tools > Net Configuration Assistant. The path depends on the Oracle version and installation name you specified during installation. 2. Welcome: Select Listener configuration and click Next. 3. Listener Configuration, Listener: Select Add and click Next. 4. Listener Configuration, Listener Name: Type a name for the Oracle listener, for example, LISTENER, and click Next. 5. Listener Configuration, Select Protocols: Add TCP to the selected protocols and click Next. 6. Listener Configuration, TCP/IP Protocol: Use the standard TCP port number 1521 and click Next. Note: If you enter a different port here, you will need the port number during the installation of Archive Center. 7. Listener Configuration, More Listeners: Select No and click Next. 8. Listener Configuration Complete: Click Next. 9. Welcome: Click Finish. The listener is created and started. 6.1.2 Creating the test database Note: If the Oracle software is already installed, ensure that the Oracle Enterprise Manager Console DB is installed before you create a new database. Prerequisites The disks used for the database must fulfil the following prerequisites: • The volumes of the disks must not be compressed. • Avoid the use of RAID 5 for redo logs and archived redo logs. Important The database must not be installed on a computer that works as primary or backup domain controller. 54 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 6.1. Setting up Oracle Database server To create the database with Oracle 11.2: The following shows how to create a TEST database with the Oracle 11.2 Database Configuration Assistant. This very simple test database will have the following characteristics: • All database files are located in one directory. Thus, as a prerequisite, create a directory in which you want all database files to be created (for example, d: \dbdata). • Redo log file groups consist always of two members. 1. To start the Database Configuration Assistant, from the Start menu, click Oracle–OraDb11g_home1 > Configuration and Migration Tools > Database Configuration Assistant. The path depends on the Oracle installation name you specified during installation. 2. Welcome: Click Next. The number of steps shown in the dialog headers may vary between 11 and 12, but there are always 11 steps processed. 3. Step 1 of 11: Operations: Select Create a Database and click Next. 4. Step 2 of 11: Database Templates: Select Custom Database and click Next. 5. Step 3 of 11: Database Identification: Type a Global Database Name (for example, ECR). The SID is set automatically. Click Next. 6. Step 4 of 11: Management Options: • In the Enterprise Manager pane, select Configure Enterprise Manager and Configure Database Control for local management. • In the Automatic Maintenance Tasks pane, clear Enable automatic maintenance tasks. Click Next. 7. Step 5 of 11: Database Credentials: Feel free to set the passwords according to your company standards. Click Next. 8. Step 6 of 11: Storage Options: • For storage type, select File System • For storage location, select Use Common Location for All database Files and enter the respective directory (directory must exist). Click Next. 9. Step 7 of 11: Recovery Configuration: OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 55 AR160200-00-IGW-EN-03 Chapter 6 Appendix: Setting up the database in Oracle Database a. Clear Specify Fast Recovery Area. b. Select Enable Archiving. c. Click Edit Archive Mode Parameters. d. Enter one or more directories on dedicated disks as archive log destinations. e. Click OK and then click Next. 10. Step 8 of 11: Database Content: a. Clear Oracle Text. b. Select at least Enterprise Manager Repository. c. Click Standard Database Components and clear all options. Ignore warning and click OK. d. Click Custom Scripts and select No Scripts to run. e. Click Next. 11. Step 9 of 11: Initialization Parameters: a. Click Memory and select Typical. Memory Size 500 MB. Note: This is the minimum for a test system; a reasonable value for a productive database will be substantially larger. Select Use Automatic Memory Management. b. Click Sizing: For the block size, select 8192 bytes. For processes, select at least 200. c. Click Character Sets and do the following: • Database Character Set: Select Use Unicode (AL32UTF8). • National Character Set: Select AL16UTF16 – Unicode UTF-16 Universal character set. d. Click Connection Mode and select Dedicated Server Mode. Click Next. 12. Step 10 of 11: Database Storage: a. Expand the Storage tree listing. b. Click Controlfile to check that there are at least two control files. c. Create the tablespace ECR_DATA: i. Click Tablespaces. ii. Click Create. iii. On the General tab, set the following: 56 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 6.1. Setting up Oracle Database server • As name, enter ECR_DATA. • As file name, enter ECR_DATA_1.dbf . • Accept the shown directory. • As Size, enter 500 MB. Note: This is the size for a test system; a reasonable value for a productive database will be several GB. • As status, select Online. • As type, select Permanent. iv. On the Storage tab, set the following: • Extent Management: Select locally managed. Select Automatic Allocation. • Segment Space Management: Select Automatic. • Enable logging: Select yes. • Block size: Select default. v. Click Create. d. Create the tablespace ECR_INDEX. Proceed as for the tablespace ECR_DATA in Step 12.c, but enter a different name (for example, ECR_INDEX) and file name (for example, ECR_INDEX_1.dbf). e. Configure the data files of the table spaces: i. Expand the Datafiles tree listing. ii. Click the entry for ECR_DATA, for example, ECR_DATA_1.dbf. iii. Select the Storage tab and set the following: • Enable the Automatically extend datafile when full (AUTOEXTEND) option and set the increment to 500 M Bytes. • As maximum size, select Unlimited. iv. Select the entry for ECR_INDEX, for example, ECR_INDEX_1.dbf. v. Click the Storage tab and set the following: • Enable the Automatically extend datafile when full (AUTOEXTEND) option and set the increment to 500 M Bytes. • As maximum size, select Unlimited. f. Configure the redo log groups: OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 57 AR160200-00-IGW-EN-03 Chapter 6 Appendix: Setting up the database in Oracle Database i. Expand the Redo Log Groups. ii. Click redo log group 1. iii. Set the File Size to 100 M Bytes. iv. Verify the directory for the first redo log member. v. Add at least one other file to the redo log members. This file must be located on a separate disk (if you are using a SAN (Storage Area Network) or something comparable you can omit this point). vi. Repeat the definition (steps 12.f.ii to 12.f.v) for the redo log groups 2 and 3. g. Click Next. 13. Step 11 of 11: Creation Options: Select Create Database, click Finish and confirm with OK. The database creation may take some time. 14. Database Configurations Assistant: Note the database control URL displayed, and click Exit. The database is now created and started. 6.1.3 Creating the database user 1. Start SQL*Plus. set ORACLE_SID=ECR sqlplus "sys/<password> as sysdba" 2. Enter the following SQL commands: create user ecr identified by ecr; grant create sequence to ecr; grant create table to ecr; grant create view to ecr; grant create session to ecr; grant create procedure to ecr; grant execute on DBMS_SQL to ecr; alter user ecr default tablespace ecr_data; alter user ecr quota unlimited on ecr_data; alter user ecr quota unlimited on ecr_index; exit Using a role to grant the rights indirectly is not sufficient as stored procedures will not have the rights. For more information, see also “Rights for database users before and after installation” on page 60. 58 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 6.1. Setting up Oracle Database server 6.1.4 Configuring the Oracle Listener 1. To start the Net Manager, from the Start menu, click Oracle – <Oracle installation name> > Configuration and Migration Tools > Net Manager. The path depends on the Oracle installation name you specified during installation. 2. If the location of the net configuration files is the default location, the existing configuration has been loaded. If you use a nonstandard location, click File > Open Network Configuration to edit the listener configuration. Enter the according name of the directory containing the listener.ora file, and then click OK. 3. Expand Oracle Net Configuration > Local > Listeners and click the name of the existing listener, for example, LISTENER. Select Listening Locations. There should be at least the following two addresses: • TCP/IP with your host and the port (default: 1521) • IPC with key ORACLE_SID (default ECR) 4. Select Database Services and click Add Database. 5. Enter the global database name (for example, ECR), the Oracle home directory (for example, E:\software\ora102) and the SID (for example, ECR). 6. Click File > Save Network Configuration to save the listener configuration to the listener.ora file. 7. To make your changes effective, you have to restart the listener. Open a command prompt and enter lsnrctl stop lsnrctl start Or stop and start the respective service: Oracle< <your oracle installation key> >TNSListener The listener is now configured and ready for use. 6.1.5 Configuring Oracle TNS Service Names To use SQL*Plus with Net Services Names and for some components of Archive Center, you need to configure the tnsnames.ora file. 1. To start the Net Manager, from the Start menu, click Oracle – <Oracle installation name> > Configuration and Migration Tools > Net Manager. The path depends on the Oracle installation name you specified during installation. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 59 AR160200-00-IGW-EN-03 Chapter 6 Appendix: Setting up the database in Oracle Database 2. If the location of the net configuration files is the default location, the existing configuration has been loaded. If you use a nonstandard location, click File > Open Network Configuration to edit the Net Service Name configuration. Enter the according name of the directory containing the tnsnames.ora file, and then click OK. 3. Expand Oracle Net Configuration > Local and click Service Naming. 4. Click Edit and then click Create. 5. Page 1 of 5, Welcome: Enter the net service name (for example, ECR_<localhost>) and click Next. 6. Page 2 of 5, Protocol: Select TCP/IP (Internet Protocol) and click Next. 7. Page 3 of 5, Protocol Settings: Enter the database host name and the configured port of the Oracle listener and click Next. 8. Page 4 of 5, Service: Enter the configured service name of the database (for example, ECR). Choose Dedicated server as the Connection Type and click Next. 9. Page 5 of 5, Test: Click Finish. 10. Expand Oracle Net Configuration > Local and click Service Naming. 11. Select the just created service ECR_<localhost>. An address configuration is displayed showing Address 1. Click + to add another address. 12. Select IPC as protocol and the ORACLE_SID of the database just created as Key Name. 13. Click File > Save Network Configuration to save the Net Service Name configuration to the tnsnames.ora file. 6.2 Rights for database users before and after installation Technical database users who run an Archive Center database on a regular basis do not need the full scope of administration privileges that are required for creating a database. Administration privileges required for creating a database schema create user ecr identified by ecr; grant create sequence to ecr; grant create table to ecr; grant create view to ecr; grant create session to ecr; grant create procedure to ecr; grant execute on DBMS_SQL to ecr; 60 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 6.2. Rights for database users before and after installation alter user ecr default tablespace ecr_data; alter user ecr quota unlimited on ecr_data; alter user ecr quota unlimited on ecr_index; exit Note: Using a role to grant the rights indirectly is not sufficient as stored procedures will not have the rights. Administration privileges required for running a database schema We assume that the same database user is used to create and to run the database schema. grant create session to ecr; grant create sequence to ecr; alter user ecr quota unlimited on ecr_data; Notes • The CREATE SEQUENCE privilege is required only to adjust the Archive Center sequences. You do not need specific privileges to delete Archive Center sequences. However, grant create sequence to ecr; is required to create a new Archive Center sequence. • If you use a different user to run the database than its owner (the user who created the database), the user running the database needs additional rights. Assign the missing “object privileges” by running a corresponding grant all command, for example. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 61 AR160200-00-IGW-EN-03 Chapter 7 Appendix: Special commands In the following, you can find information about the starting and stopping of Archive Center, including the database. 7.1 Starting and stopping Archive Server with SQL Server To start Archive Center: 1. Use the Microsoft SQL Server Management Studio to start the SQL Server service. 2. From the Control Panel, open Administrative Tools > Services. 3. Select Apache Tomcat and click Start. 4. Select Archive Spawner and click Start. To stop Archive Center: 1. Open the Services window as described above. 2. Select Archive Spawner and click Stop. 3. Select Apache Tomcat and click Stop. To stop the SQL Server database: • Use the Microsoft SQL Server Management Studio to stop the SQL Server service. To set the startup type of Archive Server to manual: 1. Use Microsoft SQL Server Configuration Manager to change the startup type of the SQL Server service. 2. Open the Services window as described above. 3. Double-click Archive Spawner, set the startup type to Manual, and click OK. 4. Double-click Apache Tomcat, set the startup type to Manual, and click OK. To disable Archive Center: 1. Use Microsoft SQL Server Configuration Manager to change the startup type of the SQL Server service. 2. Open the Services window as described above. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 63 AR160200-00-IGW-EN-03 Chapter 7 Appendix: Special commands 3. Select Archive Spawner, click Startup, set the startup type to Disabled, and click OK. 4. Select Apache Tomcat, click Startup, set the startup type to Disabled, and click OK. 7.2 Starting and stopping Archive Server with Oracle Database To start Archive Server: 1. From the Control Panel, open Administrative Tools > Services. 2. Select Oracle<Ora_Home>TNSListener and click Start. Select Oracle<Ora_Home>Agent and click Start. Select OracleService<SID> and click Start. 3. Select Apache Tomcat and click Start. 4. Select Archive Spawner and click Start. To stop Archive Center: 1. Open the Services window as described above. 2. Select Archive Spawner and click Stop. 3. Select Apache Tomcat and click Stop. To stop the Oracle Database: 1. Open the Services window as described above. 2. Select Oracle<Ora_Home>Agent and click Stop. Select OracleService<SID> and click Stop. To set the startup type of Archive Center to manual: 1. Open the Services window as described above. 2. Double-click Archive Spawner, set Startup type to Manual, and click OK. 3. Repeat the previous step for the following services: Apache Tomcat Oracle<Ora_Home>Agent OracleService<DatabaseInstance> To disable Archive Center: 1. Open the Services window as described above. 2. Double-click Archive Spawner, set Startup type to Disabled, and click OK. 3. Repeat the previous step for the following services: 64 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03 7.2. Starting and stopping Archive Server with Oracle Database Apache Tomcat Oracle<Ora_Home>Agent OracleService<DatabaseInstance> OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 65 AR160200-00-IGW-EN-03 Glossary Application Layer The Application Layer provides the extended functionality of OpenText Archive Center and offers additional services for multi-tenant, integrated archiving. Using the OpenText Archive Center Administration web client, you can set up archiving scenarios involving SAP or file systems (CIFS). Archive Box If enabled for a File Share data source, all folders and documents below the specified path are archived and replaced by a single folder shortcut. This option is intended for documents, and optionally folders, that need to be archived but are no longer in daily use. Thus, the required disk space on the file server, including the total number of files, can be reduced. This is in contrast to the shortcut scenario where every file is replaced by an individual link. (Extended Archive Center feature) CMIS See Content Management Interoperability Services (CMIS). Collection Controls and defines all archiving activities and is mapped to a tenant-specific logical archive. (Extended Archive Center feature) See Also Data source. Content Management Interoperability Services (CMIS) An open standard that allows different content management systems to inter- operate over the Internet. CMIS defines an abstraction layer for controlling diverse document management systems and repositories using web protocols. Data source Specifies the origin and properties of the documents that are archived by a collection. (Extended Archive Center feature) Hold Logical archives can be put on hold, which means that its documents and components cannot be changed or deleted. Adding further documents to the archive is still possible. In Administration Client, logical archives on hold are indicated by a check mark in the On Hold column of the Original Archives list and by an entry in the archive's Properties dialog box. See Also Retention. OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) 67 AR160200-00-IGW-EN-03 Glossary Logical archive Logical area on the Archive Center in which documents are stored. The Archive Center can contain many logical archives. Each logical archive can be configured to represent a different archiving strategy appropriate to the types of documents archived exclusively there. An archive can consist of one or more pools. Each pool is assigned its own exclusive set of volumes which make up the actual storage capacity of that archive. Retention Time frame during which it is impossible to delete or modify a document to facilitate compliance with regulations and meet the demands of lifecycle management. Retention is defined per logical archive and can be either fixed (“hardware retention”; i.e. propagated to the storage system) or variable (“software retention”; i.e. handled by the leading application). Using the Application Layer, retention periods can also be assigned to documents using rules. Tenant A tenant consists of a defined user group for a customer. Tenants are entirely delimited from one another. In Archive Server a tenant is defined by a user group with an associated, dedicated policy. (Extended Archive Center feature) 68 OpenText Archive Center – Installation Guide for Windows (Integrated Archive Installer) AR160200-00-IGW-EN-03
Copyright © 2024 DOKUMEN.SITE Inc.