OpenText Tempo Box, Content Server Edition 10.6.20 - Installation and Administration Guide English (SYNC100620-IGD-En-01)

OpenText™ Tempo™ Box, Content
Server Edition
Installation and Administration Guide
This guide explains the installation and configuration process of

the OpenText Tempo Box platform. Once configured, you can
access your OpenText Tempo Box content by entering the
OpenText Tempo Box URL in a Web browser, sync your Tempo
Box folder to your Windows® or Mac® computer, or access your
Tempo Box folder on your mobile phone or tablet.
SYNC100620-IGD-EN-01
OpenText™ Tempo™ Box, Content Server Edition
Installation and Administration Guide
Rev.: 2016-Mar-29
This documentation has been created for software version 10.6.20.
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 SA
40 Avenue Monterey , Luxembourg, Luxembourg L-2163
Tel: 35 2 264566 1
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: http://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2016 Open Text SA or Open Text ULC (in Canada). All Rights Reserved.
Trademarks owned by Open Text SA or Open Text ULC (in Canada).
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
1 OpenText Tempo Box Overview .............................................. 5
1.1 OpenText Tempo Box Architecture ..................................................... 8
2 OpenText Tempo Box Prerequisites ...................................... 11

2.1 Installing and Configuring Apache Tomcat ........................................ 12
2.2 Installing or Updating the Content Server Pulse Module for Content
Server 10.5.0 .................................................................................. 14
2.3 Configuring Content Server for OpenText Tempo Box ....................... 15
3 Installing OpenText Tempo Box ............................................. 17

3.1 Installing the Module for OpenText Tempo Box ................................. 17
3.2 Creating the Content Service Database ............................................ 18
3.3 Creating Tempo Box Folders ........................................................... 19
3.4 Updating Audit Interests for Tempo Box ............................................ 19
3.5 Installing and Configuring OpenText Directory Services (OTDS)
(Content Server 10.5.0 SP 1 Only) ................................................... 20
3.5.1 Configuring Content Web Services for Directory Services .................. 20
3.5.2 Installing OpenText Directory Services ............................................. 21
3.5.3 Adding and Configuring Users in OpenText Directory Services
using the Web Client ....................................................................... 22
3.6 Deploying the OpenText AppWorks Gateway .................................... 23
3.7 Installing the OpenText Tempo Box Bundle ...................................... 29
4 Installing OpenText Tempo Box (OpenText ECM

Everywhere Installed) .............................................................. 33
4.1 Upgrading the Content Service Module ............................................. 33
4.2 Updating the Database .................................................................... 35
4.3 Creating Tempo Box Folders ........................................................... 35
4.5 Upgrading the OpenText AppWorks Gateway ................................... 36
4.6 Installing the OpenText Tempo Box Bundle ...................................... 37
5 Upgrading OpenText Tempo Box .......................................... 41

5.1 Upgrading the Content Service Module ............................................. 42
5.2 Updating the Database .................................................................... 43
5.3 Verifying Your OpenText Tempo Box Settings ................................... 43
5.5 Upgrading the OpenText AppWorks Gateway ................................... 44
5.6 Updating the OpenText Tempo Box Bundle ...................................... 45
6 Uninstalling OpenText Tempo Box ........................................ 47
7 Configuring OpenText Tempo Box in Content Server ......... 49
OpenText Tempo Box, Content Server Edition – Installation and Administration Guide iii
Table of Contents
7.1 Configuring the Content Service Module ........................................... 49

7.2 Configuring Content Server (Enterprise) Integration ........................... 50
7.2.1 Enabling the Content Server Integration and Adding Folders .............. 53
7.2.2 Enabling Subscriptions to an Enterprise Folder ................................. 53
7.2.3 Inviting Users to Access an Enterprise Folder ................................... 54
7.3 Configuring External User Sharing ................................................... 55
7.4 Configuring Email Notifications ......................................................... 56
7.5 Configuring a Email Server for External Sharing and Email
Notifications .................................................................................... 58
7.6 Setting a Storage Limit .................................................................... 58
8 OpenText Tempo Box Client Management ........................... 61

8.1 Enabling Client Tracking .................................................................. 61
8.2 Monitoring Client Management ......................................................... 61
8.3 Wiping a Client ................................................................................ 62
9 OpenText Tempo Box Clients ................................................ 63

9.1 Distributing the OpenText Tempo Box Clients Over-the-Air ................ 63
9.2 Enabling Push Notification for Apple Devices .................................... 65
9.3 Enabling Push Notification for Android Devices ................................. 65
9.4 Configuring the Windows Desktop Client Push .................................. 66
10 Synchronizing Standard Users in OpenText Directory

Services .................................................................................... 69
10.1 Synchronizing Standard Users for Tempo Box from Active Directory
to Directory Services ....................................................................... 69
10.2 Consolidating Users from Active Directory to Content Server ............. 72
11 Migrating External Users into OpenText Directory

Services .................................................................................... 75
12 Deploying the AppWorks Gateway in a Cluster ................... 79
13 Configuring SSL on Apache Tomcat ..................................... 81

13.1 Creating the Java Keystore File ....................................................... 81
13.2 Creating a Certificate Signing Request (CSR) ................................... 82
13.3 Signing a CSR File Using Windows Certificate Services .................... 82
13.4 Importing the Certificate Chain Into the Keystore ............................... 83
13.5 Adding the Keystore to OpenText Tempo Box ................................... 84
14 Troubleshooting ...................................................................... 87
iv OpenText Tempo Box, Content Server Edition – Installation and Administration Guide
Chapter 1
OpenText Tempo Box Overview
OpenText Tempo Box offers secure file sharing and synchronization for the
Enterprise. It lets you access and collaborate on documents in your Tempo Box
folder regardless of your physical location. The content in your Tempo Box folder is
stored online and is accessible using desktop computers, smartphones and tablets, or
Web browsers. When the content is altered from any of these clients, the changes are
automatically and instantly synchronized with all other connected OpenText Tempo
Box clients.
The Tempo Box folder may be used as a regular folder, with the following
restrictions:
• Only Content Server Folders and Documents will sync with the various
OpenText Tempo Box clients. Adding unsupported items may cause errors and
unexpected behavior.
• Content Server users must not modify permissions on objects within the Tempo
Box folder using the desktop client.
• Objects moved in to the Tempo Box folder from other areas of Content Server
will be automatically synced. Objects moved out of the Tempo Box folder will be
deleted from all clients.
By default, your Content Server users can share content with other Content Server
users. However, you can also enable external sharing, which grants your Content
Server users that you select the ability to share content with users outside of your
company. External sharing is disabled by default. For details, see “Configuring
External User Sharing” on page 55.
Your Content Server users can also share content with colleagues in your company
who do not have a Content Server license. These users are referred to as Standard
users. For more information on the Tempo Box user types, see “OpenText Tempo
Box User Types” on page 7.
The OpenText Tempo Box platform requires the following components:
1. The Content Server Pulse and Content Service modules are installed in your
Content Server installation with the required databases and Tempo Box folders
created. With Content Server 16, the Content Server Pulse module is already
installed.
2. The OpenText AppWorks Gateway is deployed in your Apache® Tomcat™
installation. The AppWorks Gateway needs to connect to your Content Server
installation as well as to a production database such as Oracle® or Microsoft®
SQL Server®. You also need to configure AppWorks Gateway to authenticate
users using Content Server or OpenText™ Directory Services (OTDS).
OpenText Tempo Box, Content Server Edition – Installation and Administration Guide 5
Chapter 1 OpenText Tempo Box Overview
Important
You must deploy AppWorks Gateway 1.2.2. and not AppWorks Gateway
16. AppWorks Gateway 16 will not work with OpenText Tempo Box
10.6.20.
3. The OpenText Tempo Box bundle is installed and enabled in the AppWorks
Gateway. The bundle includes the applications, components, and services
required for OpenText Tempo Box.
Once the OpenText Tempo Box platform is installed and configured, your users will
be able to access their Tempo Box content from the available clients. They can access
their content by installing the OpenText Tempo Box client on their desktop
computer or by installing the OpenText Tempo app on their mobile device. When
your Content Server users are signing in to an OpenText Tempo Box client, their
Content Server credentials and the AppWorks Gateway URL are required. For
example, the AppWorks Gateway URL will have the following structure.
Client Server URL

Mobile and desktop client <https://AppWorks_Gateway:port>
Web client <https://AppWorks_Gateway:port>/
webaccess
Older versions of the OpenText Tempo Box app and desktop clients will not work
with OpenText Tempo Box 10.6.20.
The OpenText Tempo Box, Content Server Edition - Client Installation Guide (SYNC-
UQS) outlines the steps to install the OpenText Tempo Box clients. This guide is
available in the OpenText Knowledge Center (https://knowledge.opentext.com/
knowledge/cs.dll?func=ll&objId=24752394&objAction=browse&sort=name&
viewType=1).
There are three installation scenarios when installing or upgrading the OpenText
Tempo Box platform.
• New installation of OpenText Tempo Box. For details, see “Installing OpenText
Tempo Box “ on page 17.
• New installation of OpenText Tempo Box when OpenText ECM Everywhere is
already installed. For details, see “Installing OpenText Tempo Box (OpenText
ECM Everywhere Installed)“ on page 33.
• Upgrade of OpenText Tempo Box. For details, see “Upgrading OpenText Tempo
Box“ on page 41.
Before proceeding, make sure your system meets the OpenText Tempo Box
prerequisites. For details, see “OpenText Tempo Box Prerequisites“ on page 11.
OpenText Tempo Box Authentication Options

If you have Content Server 16 installed, you will be using OpenText Directory
Services (OTDS) for authentication. With Content Server 10.5, you can choose to
6 OpenText Tempo Box, Content Server Edition – Installation and Administration Guide
authenticate your users using Directory Services or Content Server when they sign
in to OpenText Tempo Box. The Directory Services authentication method offers the
following features, which are not available with Content Server authentication:
• Support for Standard users to have a Tempo Box folder. Standard users are
employees in your company who do not have Content Server licenses. For
information on configuring Standard users, see “Synchronizing Standard Users
in OpenText Directory Services“ on page 69.
• Specify runtime and user audiences in the AppWorks Gateway, which allows
you to display a feature in the specified runtime or to a specific user or group.
For example, you can choose to display the Favorites app to only the Marketing
department.
• Sync, add, and search for users in the AppWorks Gateway.
For more information on OpenText Directory Services, see OpenText Directory

Services - Installation and Administration Guide (OTDS-IWC) on the OpenText
Knowledge Center (https://knowledge.opentext.com/knowledge/llisapi.dll/open/
18985354).
OpenText Tempo Box User Types

OpenText Tempo Box supports the following types of users:
• Content Server users – users who are employees in your company who have a
Content Server license.
• Standard users – users who are employees in your company who do not have a
Content Server license. Standard users have access to the same Tempo Box
features as Content Server users. However, they cannot publish items from their
Tempo Box folder into Content Server or otherwise access Content Server.
With OpenText Tempo Box, Premium Edition, your Content Server users who
have Edit Permissions permission for an Enterprise folder will be able to share the
folder with Standard users. This is the only way Standard users can access the
content in an Enterprise folder.
Standard users are only supported with Content Server 10.5.0 SP 1 and Directory
Services 10.5.0 SP 1 with Patch 5 or higher, or Content Server 16.0.0 and Directory
Services 16.0.0. For more information, see “OpenText Tempo Box Prerequisites“
on page 11.
• External users – users who are not employees in your company. External users
need to receive a sharing invitation from a Content Server user or Standard user
in order to create a Tempo Box account and then access the content in the shared
folder. External users can only access content in shared folders. They cannot add
content outside of a shared folder. Also, External users cannot publish items
from their Tempo Box folder to Content Server or otherwise access Content
Server. External sharing is disabled by default and must be granted to Content
Server users or Standard users.
Chapter 1 OpenText Tempo Box Overview
1.1 OpenText Tempo Box Architecture

The OpenText Tempo Box architecture consists of the following components, where
the desktop and mobile clients are optional.
Desktop Client
Content Server
(Content Service module) Mobile Client
Apache Tomcat
(OpenText AppWorks Gateway)
Web Client
OpenText Directory
Active Directory/LDAP
Services
Figure 1-1: OpenText Tempo Box Architecture
Active Directory/LDAP
The Active Directory or LDAP server that contains your users. This is optional.
OpenText Directory Services
The OpenText Directory Services server that contains your users.
OpenText Content Server
The server hosting Content Server with the Content Server Pulse and Content
Service modules installed and configured.
Apache Tomcat
The server hosting Apache Tomcat with the AppWorks Gateway application
(Java) deployed and configured, and the OpenText Tempo Box bundle installed
and enabled.
Desktop Client
The desktop client syncs your Tempo Box content to a folder on your Windows
or Mac computer.
1.1. OpenText Tempo Box Architecture
Mobile Client
The OpenText Tempo app makes your Tempo Box content accessible from an
Apple® iPhone, iPad, or Android™ smartphone and tablet.
Web Client
Users can access their Tempo Box folder from a Web browser.
To better understand the flow outlined in Figure 1-1, when a Content Server user or
Standard user shares a folder with a new External user, it initiates a series of
processes in Content Server (shown with blue arrows in the following figure), as
well as a series of processes in Directory Services (shown with red arrows).
Figure 1-2: External Sharing Flowchart
Chapter 2
OpenText Tempo Box Prerequisites
The prerequisites for OpenText Tempo Box include the following:
• Content Server 16.0.0 or Content Server 10.5.0 SP 1. Ensure the latest patches for
Content Server are installed. For a list of required patches, refer to the Release
Notes on the OpenText Knowledge Center (https://knowledge.opentext.com/
knowledge/llisapi.dll?func=ll&objId=751264&objAction=browse&sort=name).
Important
Support for Standard users requires Content Server 16.0.0 or Content
Server 10.5.0 SP 1 with 2015–03 Update or later, as well as Directory
Services 16.0.0 or Directory Services 10.5.0 SP 1 with Patch 5 or later. For
more information on Standard users, see “OpenText Tempo Box User
Types” on page 7.
• A production database such as Oracle or Microsoft SQL Server.
• Apache Tomcat 7.x or 8.x and JDK 1.7.x or 1.8.x is needed for the AppWorks
Gateway. For more information, see “Installing and Configuring Apache
Tomcat” on page 12.
Note: OpenText strongly suggests installing the AppWorks Gateway on a

separate Tomcat installation from OpenText Directory Services.
• Content Server Pulse module. The Content Server Pulse module is already
installed in Content Server 16.0.0. However, with Content Server 10.5.0, you need
to download and install the module. For more information, see “Installing or
Updating the Content Server Pulse Module for Content Server 10.5.0”
on page 14.
• Additional Content Server configuration. For more information, see
“Configuring Content Server for OpenText Tempo Box” on page 15.
Table 2-1: Version Numbers for the Tempo Box 10.6.20 release
Content Content Tempo AppWork AppWork Desktop OpenText

Server Service Box s s Clients Tempo
Pulse module Bundle Gateway Gateway Mobile
module Add-on apps
Bundle
Content 16 (core 10.6.20 10.5.20 1.2.2 1.2.2 10.5.20 1.0.x
Server 16 module)
Content 10.5 10.5.20 10.5.20 1.2.2 1.2.2 10.5.20 1.0.x
Server
10.5
Chapter 2 OpenText Tempo Box Prerequisites
2.1 Installing and Configuring Apache Tomcat

The AppWorks Gateway engine component is the single point of contact between all
clients and Content Server. It forwards all incoming operation requests, queues data
requests to reduce server load, and handles notifications to all registered client
applications.
The AppWorks Gateway engine can be located on the same server(s) as Content
Server or on a separate server. Communication between the AppWorks Gateway
engine and Content Server is done through HTTP or HTTPS. It does not require the
installation of Content Server Web services.

If your Content Server is behind a firewall and you want to provide access to mobile
devices, you need to run the AppWorks Gateway engine on a separate server. An
alternative is to locate the AppWorks Gateway engine in a DMZ environment where
the mobile devices and other clients can connect to the AppWorks Gateway engine.
You would then open firewall access for the AppWorks Gateway engine to connect
to Content Server.
The AppWorks Gateway engine is a standard Apache Tomcat Web application and
requires Apache Tomcat 7.x or 8.x and JDK 1.7.x or 1.8.x. If you have a previous
version of Apache Tomcat installed, you must uninstall your current version and
install Apache Tomcat 7.x or 8.x before installing AppWorks Gateway and OpenText
Tempo Box.
To configure Apache Tomcat:
1. Ensure you have Apache Tomcat 7.x or 8.x and JDK 1.7.x or 1.8.x installed.
2. Stop the Apache Tomcat service.
3. Navigate to the <Tomcat_Home>\bin folder.
4. Double-click Tomcat8w.exe and click the Java tab.
5. At the bottom of the Java Options list, type -XX:MaxPermSize=512m.
6. In the Maximum memory pool box, type 1024.
2.1. Installing and Configuring Apache Tomcat
7. Click OK.
8. Navigate to the <Tomcat_Home>\conf folder and open server.xml in a text

editor.
9. Locate the HTTP/1.1 connector and add a maxConnections attribute with a

large enough value to handle the expected number of clients. Each connected
client needs one connection for notifications. Collectively, the clients will need a
number of connections for sending data to the server. Our testing suggests that
this total should be multiplied by two to get the maxConnections value,
therefore if 1 GB is allocated to the Tomcat Java process, maxConnections can
be set to 12000.
The number of concurrent connections supportable depends on both
maxConnections and the memory available for Tomcat.
10. Add the maxThreads="2048" attribute.
11. To allow full UTF-8 support, add the useBodyEncodingForURI="true"

attribute. For example,
<Connector connectionTimeout="20000"
port="<8080>"
protocol="HTTP/1.1"
redirectPort="8443"
maxConnections="12000"
maxThreads="2048"
useBodyEncodingForURI="true"/>
12. Optional It is also recommended that you add the following attributes to the
HTTP/1.1 connector.
maxKeepAliveRequests="-1"
keepAliveTimeout="60000"
13. Comment out or remove the following tag.
<Listener SSLEngine="on"
className="org.apache.catalina.core.AprLifeCycleListener"/>
14. Save and close this file.
15. Restart the Apache Tomcat service.
16. To ensure a secure system, you need to configure SSL for Tomcat. For details,
see “Configuring SSL on Apache Tomcat“ on page 81.
2.2 Installing or Updating the Content Server Pulse

Module for Content Server 10.5.0
To install or update the Content Server Pulse module:
1. Do the following to install the Content Server Pulse module:
a. Download the module from the OpenText Knowledge Center (https://

knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=17581483&
objAction=browse).
Important
The Content Server Pulse module is a core module in Content Server
16.0.0.
Operating System Content Server Pulse Module for Content Server 10.5.0 SP 1
Windows 10.5.0_social64_win.exe
UNIX 10.5.0_social64_lnx.tar
10.5.0_social64_sol.tar
b. Do one of the following:
• For Windows, run the installation file and follow the instructions.
• For UNIX, navigate to the <Content_Server_Home> directory and run the
following command, where <x> is your operating system, either Linux®
or Oracle® Solaris:
tar -xvf <Content_Server_Pulse_Version>_<x>.tar
2.3. Configuring Content Server for OpenText Tempo Box
This places the necessary folder structure in the <Content_Server_Home>/

staging directory of the selected Content Server installation.
c. Sign in to the Content Server Administration page as an Admin user.
d. Scroll to the Modules Administration section and click the Install Modules
or Upgrade Modules link.
e. Scroll to the Installable Modules list. Select the Content Server Pulse and
Content Server Social Object check boxes and then click Install.
The server integrates the files from the <Content_Server_Home>/staging
folder into the installed <Content_Server_Home>/module folder.
f. After the files are integrated, you must restart the Content Server services
and then click the Continue link on the Restart Content Server page.
2. Download the latest patches for the Content Server Pulse module from the
OpenText Knowledge Center (https://knowledge.opentext.com/knowledge/
cs.dll?func=ll&objId=17582060&objAction=browse).
3. Stop the Content Server services.
4. Extract the downloaded patches to the <Content_Server_Home> folder.
5. Restart the Content Server services.
6. Optional By default, Content Server Pulse only generates events for Documents.
To generate events for Folders, do the following:
a. Sign in to the Content Server Administration page as an Admin user.

b. Click Pulse Administration and then Included Note Types.
c. Select the Folder check box and click Update.
2.3 Configuring Content Server for OpenText Tempo

Box
To configure Content Server for OpenText Tempo Box:
1. In the Server Configuration section, click the Configure Security Parameters

link.
2. In the Cookie Authentication Information section, do the following:
• Select the Enable X-Forwarded-For for Client IP mapping check box.

• In the Trusted Proxy Server List box, type the IP address of the machine that
your Apache Tomcat Web server is located.
3. In the Trusted Referring Websites section, type the IP address and port
number of the machine where your Apache Tomcat Web server is located. For
example,
<https://Apache_Tomcat_Host:port>
In a clustered environment, this must remain as the actual, single machine.

4. In the Trusted Cross Domains section, type the following:
tempo;<https://Apache_Tomcat_Host:port>/content/publish.html
In a clustered environment, this must remain as the actual, single machine.
5. Click Save Changes.
6. Restart the Content Server services and then click the Continue link on the
Restart Content Server page.
7. To return proper HTTP status messages, do the following:
a. Open Windows Explorer, navigate to <Content_Server_Home>\config and

open the opentext.ini file.
b. In the [general] section, add Set200Error=FALSE.
c. Add a [Client] section and add ErrorStatus=500.
d. Save and close the file.
e. Restart the Content Server services.
8. Optional If clustered, repeat these steps for all nodes.

9. You must now install the required components for OpenText Tempo Box. There
are three installation scenarios when installing or upgrading the OpenText
Tempo Box platform.
• New installation of OpenText Tempo Box. For details, see “Installing

OpenText Tempo Box “ on page 17.
• New installation of OpenText Tempo Box when OpenText ECM Everywhere
is already installed. For details, see “Installing OpenText Tempo Box
(OpenText ECM Everywhere Installed)“ on page 33.
• Upgrade of OpenText Tempo Box. For details, see “Upgrading OpenText
Tempo Box“ on page 41.
Chapter 3
Installing OpenText Tempo Box
The OpenText Tempo Box platform requires the Content Service module installed
and configured in Content Server and the AppWorks Gateway deployed in your
Apache Tomcat installation. Once deployed, the AppWorks Gateway needs to
connect to your Content Server installation as well as a production database such as
Oracle or Microsoft SQL Server. As a final step, you need to install the OpenText
Tempo Box applications, components, and services in the AppWorks Gateway.
3.1 Installing the Module for OpenText Tempo Box

To install the module for OpenText Tempo Box:
1. Ensure you have installed the prerequisite software and configured your
environment for OpenText Tempo Box. For more information, see “OpenText
Tempo Box Prerequisites“ on page 11.
2. Ensure the latest patches for Content Server are installed. For a list of required
patches, refer to the Release Notes on the OpenText Knowledge Center (https://
knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=751264&
objAction=browse&sort=name).
3. Download the Content Service module from the OpenText Knowledge Center
(https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=22598848&
objAction=browse&sort=name&viewType=1). For UNIX, save the file to the
<Content_Server_Home> directory.
Operating System Content Service Module for Content Server 16.0.0

Windows 10.6.20_content_service64_win.exe
UNIX 10.6.20_content_service64_lnx.tar
10.6.20_content_service64_sol.tar
Operating System Content Service Module for Content Server 10.5.0 SP 1

Windows content_service_10.5.20_win64.exe
UNIX content_service_10.5.20_lnx64.tar
content_service_10.5.20_sol64.tar
4. Do one of the following:
following command, where <content_service_module> is the filename of the
module for your Content Server installation:
Chapter 3 Installing OpenText Tempo Box
tar -xvf <content_service_module>.tar

5. Sign in to the Content Server Administration page as an Admin user.
6. Scroll to the Modules Administration section and click the Install Modules
link.
7. On the Install Modules page, scroll to the Installable Modules list. Select the
OpenText Content Service check box and then click Install.
The server integrates the files from the <Content_Server_Home>/staging folder
into the <Content_Server_Home>/module folder.
8. After the files are integrated, you must restart the Content Server services and
then click the Continue link on the Restart Content Server page.
9. If available, download any relevant Content Service module patches from the
llisapi.dll/open/24748720) and do the following:
a. Stop the Content Server services.

b. Extract the downloaded patches to the <Content_Server_Home> folder.
c. Restart the Content Server services.
10. Optional If clustered, repeat these steps for all nodes.
11. You must now create the Content Service database.
3.2 Creating the Content Service Database

To create the Content Service database:
1. In the Content Service Administration section, click the Content Service

Database Administration link.
2. Click the create link for every table listed on this page.
3. Click the Admin Home link to return to the Content Server Administration
page.
4. You must now create the Tempo Box folders.
3.3. Creating Tempo Box Folders
3.3 Creating Tempo Box Folders

You can create Tempo Box folders for all users in Content Server or only a list of
users.
To create the Tempo Box folders:
1. In the OpenText Tempo Box Administration section, click the OpenText

Tempo Box Maintenance link.
• To create a Tempo Box folder for all Content Server users, click Create next
to Create Tempo Box Folders for All Users. The operation status box will
indicate when the operation is complete.
• To create Tempo Box folders for specified users, in the Create Tempo Box
Folders for Specified Users box, type the user names of the Content Server
users for which you want to create folders, entered as a comma separated
list, and then click Create. The operation status box will indicate when the
operation is complete.
page.
4. Optional To automatically create a Tempo Box folder for new Content Server
users, do the following:
a. In the OpenText Tempo Box Administration section, click the OpenText

Tempo Box Configuration Settings link.
b. For the New Users Get Tempo Box Folders option, select Enabled.
c. Click OK.
d. Click the Admin Home link to return to the Content Server
Administration page.
5. You must now verify the audit interests for Tempo Box.
3.4 Updating Audit Interests for Tempo Box

To update audit interests for Tempo Box:
1. In the System Administration section, click the Administer Event Auditing

link.
2. Click the Set Auditing Interests link and verify that the following check boxes
are selected:
• Owner Changed by Tempo Box

• Tempo Box Sharing Disabled
• Tempo Box Sharing Enabled
• User Accepted Share Request

• User Invited to Share
• User Rejected Share Request
• User Subscribed to Tempo Box Share
• User Unsubscribed from Tempo Box Share
3. Click Set Interests and then click the Admin Home link.
4. If you already have OpenText Directory Services 10.5.0 SP 1, patch 4 or above

installed, the next step is to deploy the AppWorks Gateway. For details, see
“Deploying the OpenText AppWorks Gateway ” on page 23. If you do not
have OpenText Directory Services installed or you have an earlier version than
Directory Services 10.5.0 SP 1 installed, see “Installing and Configuring
OpenText Directory Services (OTDS) (Content Server 10.5.0 SP 1 Only)”
on page 20.
3.5 Installing and Configuring OpenText Directory

Services (OTDS) (Content Server 10.5.0 SP 1
Only)
The preferred method of authentication for Tempo Box is OpenText Directory
Services due to the additional features that Directory Services provides. For more
information on the authentication options, see “OpenText Tempo Box
Authentication Options” on page 6. With Content Server 10.5.0 SP 1, you need to
manually install Directory Services and alter your Content Server installation for
Directory Services authentication. With Content Server 16, the only authentication
method is Directory Services. Therefore, if you have Content Server 16 installed, you
can proceed to “Deploying the OpenText AppWorks Gateway ” on page 23.
3.5.1 Configuring Content Web Services for Directory

Services
To configure Content Web Services for Directory Services:
2. Copy the cws.war from your <Content_Server_HOME>/

webservices/java/webapps directory to your <TOMCAT_HOME>/webapps
directory. Tomcat will detect the new WAR file and automatically deploy it when
the Tomcat service starts again.
3. Configure Content Web Services to point to your Content Server installation.

Open the <TOMCAT_HOME>/webapps/cws/WEB-INF/web.xml file in a text
editor.
a. Locate the following lines:
3.5. Installing and Configuring OpenText Directory Services (OTDS) (Content Server 10.5.0
SP 1 Only)
<context-param>
<param-name>LivelinkServer</param-name>
<param-value>localhost</param-value>
</context-param>
Replace localhost with the fully-qualified domain name of the server that
hosts Content Server.
b. Locate the following lines:
<context-param>
<param-name>LivelinkServerPort</param-name>
<param-value>2099</param-value>
</context-param>
Replace the 2099 value with the port number of the server that hosts
Content Server.
4. Save and close this file.
5. Restart the Apache Tomcat service.
3.5.2 Installing OpenText Directory Services

To install OpenText Directory Services:
1. Download Directory Services (OTDS) 10.5.0 SP 1 with the latest patch from the
llisapi.dll/open/18985354).
During the installation of OTDS, be sure to save the otadmin@otds.admin
password.
2. You now need to create a Content Server resource in Directory Services and
configure the Directory Services Integration Administration in Content Server.
For information on completing these steps, see “Adding and Configuring Users
in OpenText Directory Services using the Web Client” on page 22.
For information on installing Directory Services or for complete instructions on
performing this step, see the OpenText Directory Services - Installation and
Administration Guide (OTDS-IWC) on the OpenText Knowledge Center (https://
objAction=browse&sort=name&viewType=1).
3.5.3 Adding and Configuring Users in OpenText Directory

Services using the Web Client
To add a new user partition:
1. In a browser, enter the URL of the Directory Services Web Client. For example,
https://<Domain_name>:8080/otds-admin/.
2. Enter the credentials of a Directory Services Admin user and click Sign In. For
example, type otadmin@otds.admin.
3. In the left pane, click Partitions, select Add and then New Non-synchronized
User Partition.
4. In the Name field, type the name of this partition. For example, “Content Server
Members”.
5. In the Description field, type the description of this partition. For example,
“This partition holds members that were created through Content Server”.
6. Click Save.
To add a Content Server resource in Directory Services:
1. In the left pane, click Resources and then click Add.

2. On the General page, in the Resource name field, type a name for this resource.
For example, “OTCS”. Click Next.
3. On the Synchronization page, select the User and group synchronization check
box. In the Synchronization connector list, select Content Server. Accept the
remaining default settings and click Next.
4. On the Connection Information page, enter the information for your Content
Server Web Services and click Test Connection. If the test was successful, click
Next. If the test was unsuccessful, make sure you enter the Content Server
Admin user password correctly and make sure you have Content Web Services
properly configured. For details, see “Configuring Content Web Services for
Directory Services” on page 20.
5. Click Save.
6. A resource identifier will appear. Copy this identifier.
To configure Directory Services authentication in Content Server:
1. Sign in to the Content Server Administration page.

2. In the Directory Services Integration Administration section, click Configure
Integration Settings.
3. Select the OTDS Authentication radio button.
4. In the OTDS Server URL field, type the URL of your Directory Services server.
3.6. Deploying the OpenText AppWorks Gateway
5. In the Resource Identifier field, paste the resource identifier that you copied in
step 6 of the previous procedure and then click Run Test.
6. If the test is successful, click Save and then restart the Content Server services.
To verify the activation and create an Access Role:
1. In Directory Services, click Verify Activation and then click OK. This creates a
link between Content Server and Directory Services. However, this does not
synchronize your Content Server users into Directory Services. To synchronize
your users, you must use the Content Server to Directory Services User
Migration Tool. This tool, and corresponding documentation is available in the
llisapi.dll?func=ll&objId=61575716&objAction=browse&viewType=1).
2. Once you’ve migrated your Content Server users into Directory Services, in the
left pane in Directory Services, click Access Roles, and then select Add.
3. In the Name field, type the name of this partition. For example, "Access to
Content Server".
4. In the Description field, type the description of this partition. For example,
"Default access role for Content Server".
5. Click Save.
6. Select Actions for your Content Server access role and then View Access Role
Details.
7. Click Add.
8. Search for “Content Server Members” or the name that you gave to the Content
Server Partition when you migrated your users.
9. Select the Content Server Members check box and then click Add Selected
Items to Access Role.
10. Click Close Dialog and then click Save.
3.6 Deploying the OpenText AppWorks Gateway

To deploy the OpenText AppWorks Gateway:
1. Download the AppWorks Gateway version 1.2.2 from AppWorks Developer

(https://developer.opentext.com/webaccess/#url=%2Fawd%2Fresources
%2Fdownloads&tab=501).
Important
AppWorks Gateway version 16 will not work with Tempo Box 10.6.20.

3. Optional The default Tomcat Web Management Application does not work with
the AppWorks Gateway. If you would like to use the default Tomcat Web
Management Application and you plan on uninstalling AppWorks Gateway at
a future time, you need to back up the ROOT webapp prior to installing the
AppWorks Gateway.
4. Extract the contents of the appworks_gateway_1.2.2.zip file to the root of the

Apache Tomcat folder. For example, <C:\\Program Files\Apache Software
Foundation\Tomcat 8.0>. You may need to overwrite some existing files.
5. Start the Apache Tomcat service. It may take a few minutes for the Tomcat
service to start completely.
Tip: Navigate to the <Tomcat_Home>\logs folder and open the

catalina.<yyyy-mm-dd>.log file. When you see a line beginning with
INFO: Server startup in <55278> ms, you will be able to begin
configuring the AppWorks Gateway.
6. In a browser, type <https://Apache_Tomcat_Host:port>/gateway to view

the AppWorks Gateway. The AppWorks Gateway and Content Server use the
same cookie, so be sure to open the AppWorks Gateway in a different browser
from Content Server to prevent issues.
7. In the Database Configuration section, from the Select Database Vendor list,
select a database and provide the required information. After the installation is
complete, you cannot change to another database.
When connecting to an Oracle database, you can choose either SID or Service
Name based on the configuration of your Oracle client. See Figure 3-1.
Figure 3-1: Selecting a database
For more information on connecting to an Oracle database, see Selecting Oracle

as your AppWorks Gateway Database (https://developer.opentext.com/
webaccess/#url=%2Fawd%2Fresources%2Farticles%2F1129456%2Fselecting
%2Boracle%2Bas%2Byour%2Bopentext%2Bappworks%2Bgateway
%2Bdatabase&tab=501).
For more information on connecting to a MySQL database, see Selecting
MySQL as your AppWorks Gateway Database (https://
developer.opentext.com/webaccess/#url=%2Fawd%2Fresources%2Farticles
%2F5693%2Fselecting%2Bmysql%2Bas%2Byour%2Bopentext%2Bappworks
%2Bgateway%2Bdatabase&tab=501).
The Embedded Derby option is not intended for production environments.
Caution
The Custom Connection String option is intended for experienced
database administrators only and must be used with caution.
8. Click Configure Database Connection.
9. In the OTDS Configuration section, from the Select OTDS Configuration list,
select Connect to existing OTDS service.
Important
The AppWorks Gateway requires OpenText Directory Services 10.5 or
higher. Earlier versions of Directory Services will not work.
10. Complete the required information.

OTDS server url requires the URL of the Tomcat server that is running
Directory Services.
OTDS Administrative account username and password require the credentials
for a Directory Services Admin user.
Password for new OTAG administrative user defines the AppWorks Gateway
administrative user account that will be created in Directory Services. The
default username and password are otag and otag respectively.
Resource Name and Gateway User Partition Name defines the name of the
AppWorks Gateway Resource and User Partition that will be created in
Directory Services. The default values are OTAG and otag respectively.
Figure 3-2: Connect to an existing Directory Services server
11. Click Save Changes. The configuration is complete when you are prompted to
sign in to the AppWorks Gateway again.

catalina.<yyyy-mm-dd>.log and gateway.log files to see the status of
the configuration. When you see INFO: Server startup in <55278> ms,
you will be able to sign into the AppWorks Gateway.
If you experience problems, see “How can I troubleshoot the AppWorks

Gateway?” on page 93.
12. You now need to add the otag partition to the Content Server resource in
Directory Services. To add this, do the following:
a. Sign into Directory Services Web Client as an admin user. For example,
https://<Domain_name>:8080/otds-admin/. Click Access Roles in the
left pane. Select Actions for your Conent Server access role and then View
Access Role Details.
b. Click Add.
c. Search for otag.
d. Select the otag check box and then click Add Selected Items to Access
Role.
e. Click Close Dialog and then click Save.
f. Click Resources in the left pane. Select Actions for Content Server and
select Consolidate.
g. Repeat steps a to f to add the Content Server Members to the OTAG access
role.
13. We now want to give a user who has system administrative permissions in
Content Server, namely the Directory Services admin user or the Content Server
admin user, administrative permissions in the AppWorks Gateway. To grant
this, do the following:
a. In the OpenText Directory Services Web Client, click Users & Groups in
the left pane.
b. Click the Groups tab.
c. Click Actions for otagadmins in the list of groups and then click Edit
Membership.
d. Click Add Member
e. Search for “otadmin@otds.admin”, which is the Directory Services admin
user.
f. Click the user in the search results and click Add Selected.
g. Click Close.
14. Sign in to the AppWorks Gateway as the OTAG administrative user. For
example,
Username = otag
Password = otag
The OTAG administrative user password may differ if you defined a different
password in the Password for new OTAG administrative user box.
15. In the left pane, click Settingsand then click General Settings.
16. In the Content Server URL box, type your Content Server URL. For example,
<https://Content_Server_Domain:port>/OTCS/cs.exe.
17. In the OTAG Server URL box, replace http://localhost:8080 with your
actual Apache Tomcat server. This URL is used by clients and providers to
reach the AppWorks Gateway server. It is also needed for links in external
invitations and for auto-configuration of the ContentServer trusted server. This
should be a URL that is reachable from Content Server and from off-site. If no
such URL exists, see “Troubleshooting“ on page 87.
18. Click Test Content Server URL and then click Save Changes.
Important
If the URL you are connecting to has Integrated Windows
Authentication enabled, you need to create a new application in the
Content Server IIS, which connects to the Content Server CGI directory
and have anonymous authentication enabled.
19. We now need to set the Trusted Server connection to Content Server. To make
this connection, do the following:
a. Sign out of the AppWorks Gateway. Because the otag user has Admin
permissions in the AppWorks Gateway, but not Content Server, we need to
sign into the AppWorks Gateway using the otadmin@otds.admin user
account.
b. Sign in to the AppWorks Gateway using the otadmin@otds.admin account.
c. In the left pane, click Trusted Servers.
d. Click the Select list and click ContentServer.
e. Click Generate Key and click Add New. This will make a trusted
connection between the AppWorks Gateway and Content Server. In a
clustered environment, you only need to do this once.
Important
After clicking Add New, if you were signed out of the AppWorks
Gateway, you do not have System administration rights privileges
in Content Server. Sign into Content Server and view the
permissions for the otadmin@otds.admin user.
Note: You will notice that this key matches the Shared Key in the
Content Service Notifier Settings page for the Content Service
module in Content Server. These two values must remain the same.
3.7. Installing the OpenText Tempo Box Bundle
20. Optional To deploy the AppWorks Gateway in a cluster, see “Deploying the
AppWorks Gateway in a Cluster“ on page 79.
21. Optional To allow your end users the option to choose a simpler process when
signing into the Tempo app on their mobile device, do the following:
a. In the left pane, click Settings.

b. Click the Advanced Settings link.
c. Select the Allow natave client "Keep me logged in" functionality box.
d. Click Save Changes.
When enabled, if your end users select the Keep me logged in option on the
sign in page of the Tempo mobile app, they will not be prompted to re-enter
their password in the future. The only exceptions are if the password expires or
it changes on the server.
22. Optional If you prefer, you can disable Directory Services single sign on. You
users will then be prompted to enter a user name and password when signing
in to the Tempo Box Web client. Directory Services may still be used for
password authentication. To disable Directory Services single sign on, do the
following:
a. In the left pane, click Settings.

b. Click the Advanced Settings link.
c. Select the OTDS SSO disabled box.
d. Click Update Settings.
23. You must now install the OpenText Tempo Box bundle in the AppWorks
Gateway.
3.7 Installing the OpenText Tempo Box Bundle

To install the OpenText Tempo Box bundle:
1. Download the AppWorks Add-ons bundle from the AppWorks Developer

Network (https://developer.opentext.com/webaccess/#url=%2Fawd
%2Fresources%2Fdownloads&tab=501).
2. Download the OpenText Tempo Box bundle from the OpenText Knowledge
Center (https://knowledge.opentext.com/knowledge/cs.dll?func=ll&
objId=22598848&objAction=browse&sort=name&viewType=1).
3. Sign in to the AppWorks Gateway as an OTAG Admin user.
4. In the left pane, click Install.
5. Click Browse and navigate to the AppWorks Add-ons bundle,

(ot_appworks_addons_1.2.x.otag) that you downloaded in step 1.
6. Click Next and follow the on-screen instructions to install the bundle.
7. Repeat steps 4 – 6 for the OpenText Tempo Box bundle
(tempobox_10.5.20.otag or after) that you downloaded in step 2.
8. In the left pane, click Applications and then click Enable for all of the
applications listed. When an application is disabled, users will not see the
application in the OpenText Tempo app on their Apple or Android devices.
9. In the left pane, click Components and then click Enable for all of the
components listed.
10. In the left pane, click Services and then click Enable for all of the services listed.
When a service is disabled, your users will not be able to access their content. If
the associated application is still enabled, users will see the application in the
OpenText Tempo app on their mobile device. However, it cannot be used.
11. Optional If you have OpenText™ Brava!™ Enterprise for Content Server installed
and you would like to use the Brava! features using the Tempo Box Web UI or
OpenText Tempo app, do the following:
a. Click Services.
b. Click for OTAG Reverse Proxy Service and click the Settings tab.
c. In the Allowed path patterns region, add the following paths.
<OT_HOME>/livelink.exe?func=brava.bravaviewer&nodeid=*
<OT_HOME>/livelink.exe?func=brava.*
For example,
OTCS/livelink.exe?func=brava.bravaviewer&nodeid=*
OTCS/livelink.exe?func=brava.*
d. In the Proxy Mappings region, add the following mapping and replace the
instances of localhost with your Content Server host.
<OT_HOME>=<localhost>/<OT_HOME>
img/brava=<localhost>/img/brava
For example,
OTCS=10.5.18.231/OTCS
img/brava=10.5.18.231/img/brava
e. Click Save Changes.
12. Click Services.
13. Click for Content Service.

14. Click the Settings link.
15. Select the Enable Tempo Box check box and then click Update Configuration.
16. In the Content Server user URL field, replace the current value with your IWA
enabled URL.
17. Click Update Configuration.

Your Content Server users can now access their Tempo Box content from any
Tempo Box client. For more on the Tempo Box clients, see “OpenText Tempo
Box Clients “ on page 63. When your Content Server users are adding a profile
in the Tempo Box desktop client or OpenText Tempo app, their Content Server
credentials and the OpenText AppWorks Gateway server URL are required.
Client Server URL

Mobile and desktop client <https://
OpenText_AppWorks_Gateway:port>
Web client <https://
OpenText_AppWorks_Gateway:port>/
webaccess
Important
Older versions of the desktop client and OpenText Tempo Box app will
not work with OpenText Tempo Box 10.6.20.
For details on installing and signing in to the OpenText Tempo Box clients, see
the OpenText Tempo Box, Content Server Edition - Client Installation Guide (SYNC-
UQS) on the OpenText Knowledge Center (https://knowledge.opentext.com/
viewType=1).
18. Optional You can now configure external sharing, email notifications, storage
limits, subscribing to Enterprise folders, and more. For details, see “Configuring
OpenText Tempo Box in Content Server“ on page 49.
Chapter 4
Installing OpenText Tempo Box (OpenText ECM
Everywhere Installed)
If you currently have OpenText ECM Everywhere 10.5.0 or above installed, these
instructions outline the steps required to install OpenText Tempo Box and maintain
access to your OpenText ECM Everywhere functionality. If you have an earlier
version of OpenText ECM Everywhere, these instructions do not apply to your
environment. Follow the installation instructions at “Installing OpenText Tempo Box
“ on page 17.
OpenText ECM Everywhere and OpenText Tempo Box use the same Content Server
module. Therefore, by installing OpenText Tempo Box 10.6.20, you are may be
upgrading the Content Server module of your OpenText ECM Everywhere
installation. However, further steps are required to fully upgrade your OpenText
ECM Everywhere installation. For more information, see OpenText ECM Everywhere -
Installation and Administration Guide (MOD-IGD) in the OpenText Knowledge Center
The instructions in this chapter will not alter your authentication method for
OpenText ECM Everywhere. If you are currently using Content Server
authentication and you want to give your Standard users a Tempo Box folder, you
need to alter your Content Server installation to use OpenText Directory Services.
For more information, see “Synchronizing Standard Users in OpenText Directory
Services“ on page 69. For information on Standard users and the other Tempo Box
user types, see “OpenText Tempo Box User Types” on page 7.
If you decide to switch from Content Server authentication to Directory Services

authentication, you need to migrate your Content Server users and any existing
External users into OpenText Directory Services. For details, see “Migrating External
Users into OpenText Directory Services“ on page 75.
4.1 Upgrading the Content Service Module

To upgrade the Content Service module:
2. In Content Server 10.5.0 SP 1, ensure the latest patches for the Content Server
Pulse module are installed. For a list of required patches, refer to the Release
knowledge/cs.dll?func=ll&objId=17581483&objAction=browse).
Chapter 4 Installing OpenText Tempo Box (OpenText ECM Everywhere Installed)



6. Scroll to the Modules Administration section and click the Upgrade Modules
link.
7. On the Install Modules page, scroll to the Upgradable Modules list. Select the
OpenText Content Service check box and then click Upgrade.
into the installed <Content_Server_Home>/module folder.
9. If available, download any Content Service module patches from the OpenText
Knowledge Center (https://knowledge.opentext.com/knowledge/llisapi.dll/
open/24748720) and do the following:

10. Optional If clustered, repeat steps 1–9 for all nodes.
4.2. Updating the Database
11. You must now update the database.
4.2 Updating the Database

To update the database:
1. If applicable, in the OpenText Tempo Box Administration section, click the

Extra Upgrade Steps link and follow the on-screen instructions.
3. Verify that the status of each table is set to present, otherwise click the create or
update link.
page.
4.3 Creating Tempo Box Folders

You can create Tempo Box folders for all users in Content Server or only a list of
users.
To create the Tempo Box folders:

• To create a Tempo Box folder for all Content Server users, click Create next
to Create Tempo Box Folders for All Users. The operation status box will
indicate when the operation is complete.
• To create Tempo Box folders for specified users, in the Create Tempo Box
Folders for Specified Users box, type the user names of the Content Server
users for which you want to create folders, entered as a comma separated
list, and then click Create. The operation status box will indicate when the
operation is complete.
page.
4. Optional To automatically create a Tempo Box folder for new Content Server
a. In the OpenText Tempo Box Administration section, click the OpenText

b. For the New Users Get Tempo Box Folders option, select Enabled.
c. Click OK.
d. Click the Admin Home link to return to the Content Server
Administration page.
5. You must now verify the audit interests for Tempo Box.


link.
are selected:


“Deploying the OpenText AppWorks Gateway ” on page 23. If you do not have
OpenText Directory Services installed or you have an earlier version than
on page 20.
4.5 Upgrading the OpenText AppWorks Gateway

To upgrade the OpenText AppWorks Gateway:

Important
3. Navigate to the <Tomcat_Home>\webapps folder. Back up the gateway.war file

and delete the gateway folder.

service to start.

6. After the Tomcat service has completely started, you should be able to sign into
the AppWorks Gateway as before. In a browser, type <https://
Apache_Tomcat_Host:port>/gateway to view the AppWorks Gateway. The
AppWorks Gateway and Content Server Administration use the same cookie, so
be sure to open the AppWorks Gateway in a different browser from Content
Server to prevent issues.
7. The next step is to install the OpenText Tempo Box bundle.
4.6 Installing the OpenText Tempo Box Bundle

To install the OpenText Tempo Box bundle:

(ot_appworks_addons_1.2.x.otag) that you downloaded in step 1.
6. Click Next and follow the on-screen instructions to install the bundle.
(tempobox_10.5.20.otag or after) that you downloaded in step 2.
8. In the left pane, click Applications and then click Enable for all of the
applications listed. When an application is disabled, users will not see the
application in the OpenText Tempo app on their Apple or Android devices.
9. In the left pane, click Components and then click Enable for all of the
components listed.
10. In the left pane, click Services and then click Enable for all of the services listed.
When a service is disabled, your users will not be able to access their content. If
the associated application is still enabled, users will see the application in the
OpenText Tempo app on their mobile device. However, it cannot be used.
11. Optional If you have OpenText Brava! Enterprise for Content Server installed and
you would like to use the Brava! features using the Tempo Box Web UI or
a. Click Services.
For example,
For example,
OTCS=10.5.18.231/OTCS
12. Click Services.
13. Click for Content Service.
14. Click the Settings link.
15. Select the Enable Tempo Box check box and then click Update Configuration.
16. Click Update Configuration.

Your Content Server users can now access their Tempo Box content from any
Tempo Box client. For more on the Tempo Box clients, see “OpenText Tempo
Box Clients “ on page 63. When your Content Server users are adding a profile
in the Tempo Box desktop client or OpenText Tempo app, their Content Server
credentials and the OpenText AppWorks Gateway server URL are required.
Client Server URL

Mobile and desktop client <https://
OpenText_AppWorks_Gateway:port>
Client Server URL

Web client <https://
OpenText_AppWorks_Gateway:port>/
webaccess
Important
Older versions of the desktop client and OpenText Tempo Box app will
not work with OpenText Tempo Box 10.6.20.
For details on installing and signing in to the OpenText Tempo Box clients, see
the OpenText Tempo Box, Content Server Edition - Client Installation Guide (SYNC-
UQS) on the OpenText Knowledge Center (https://knowledge.opentext.com/
viewType=1).
17. Optional You can now configure external sharing, email notifications, storage
limits, subscribing to Enterprise folders, and more. For details, see “Configuring
OpenText Tempo Box in Content Server“ on page 49.
Chapter 5
Upgrading OpenText Tempo Box
Since OpenText Tempo Box version 10.5.0, the product now uses the AppWorks
Gateway engine as the middleware. If you are upgrading from a prior version, your
tracking information will be lost once you upgrade your Tempo Box installation.
Also, the required Content Server module has changed slightly. After you install the
module, now called the Content Service module, you will notice that some of the
OpenText Tempo Box settings have moved to the Content Service Administration
section. For example, the required tables for OpenText Tempo Box are now located
in the Content Service Administration section. The rest of the Tempo Box settings
still reside in the OpenText Tempo Box Administration section. Because the Tempo
Box settings are a part of the Content Service module, you do not need to alter the
Tempo Box settings before installing the Content Service module.
Caution
Do not delete the OpenText Tempo Box databases before reinstalling the
Content Service module because this will delete the Tempo Box folders for
your users. When you reinstall the Content Service module, the tables’
status remains set to present and users are able to access the full content of
their Tempo Box folders.
The instructions in this chapter will not alter your authentication method for
OpenText Tempo Box. If you are currently using Content Server authentication and
you want to give your Standard users a Tempo Box folder, you need to alter your
Content Server installation to use OpenText Directory Services. For more
information, see “Synchronizing Standard Users in OpenText Directory Services“
on page 69. For information on Standard users and the other Tempo Box user
types, see “OpenText Tempo Box User Types” on page 7.
If you decide to switch from Content Server authentication to Directory Services

authentication, you need to migrate your Content Server users and any existing
External users into OpenText Directory Services. For details, see “Migrating External
Users into OpenText Directory Services“ on page 75.
Chapter 5 Upgrading OpenText Tempo Box
5.1 Upgrading the Content Service Module

To upgrade the Content Service module:
2. In Content Server 10.5.0 SP 1, ensure the latest patches for the Content Server
Pulse module are installed. For a list of required patches, refer to the Release
knowledge/cs.dll?func=ll&objId=17581483&objAction=browse).



6. Scroll to the Modules Administration section and click the Upgrade Modules
link.
7. On the Install Modules page, scroll to the Upgradable Modules list. Select the
OpenText Content Service check box and then click Upgrade.
5.2. Updating the Database

into the installed <Content_Server_Home>/module folder.
9. If available, download any Content Service module patches from the OpenText
Knowledge Center (https://knowledge.opentext.com/knowledge/llisapi.dll/
open/24748720) and do the following:
10. Optional If clustered, repeat steps 1–9 for all nodes.
11. You must now update the database.
5.2 Updating the Database

To update the database:
1. If applicable, in the OpenText Tempo Box Administration section, click the

Extra Upgrade Steps link and follow the on-screen instructions.

3. Verify that the status of each table is set to present, otherwise click the create or
update link.
page.
5.3 Verifying Your OpenText Tempo Box Settings

To verify your OpenText Tempo Box settings:
1. In the Content Service Administration section, click Content Service Notifier

Settings and confirm the Shared Key and URIs are correct.
2. In the OpenText Tempo Box Administration section, click OpenText Tempo

Box Configuration Settings and confirm the settings.
3. If you have external sharing enabled, navigate to the Administer Object and
Usage Privileges page, in the System Administration section, and verify that
the restrictions you had previously configured for OpenText Tempo Box are set
correctly.


link.
are selected:


“Deploying the OpenText AppWorks Gateway ” on page 23. If you do not have
OpenText Directory Services installed or you have an earlier version than
on page 20.
5.5 Upgrading the OpenText AppWorks Gateway

To upgrade the OpenText AppWorks Gateway:
2. If you are upgrading from OpenText Tempo Box 10.5.0 or later, navigate to the
<Tomcat_Home>\webapps folder. Back up the gateway.war file and delete the
gateway folder.
If you are upgrading from OpenText Tempo Box 10.0.4, do the following:
a. In Windows Explorer, navigate to your Apache Tomcat folder.

b. In the webapps folder, delete the tempo.war file and tempo folder.
c. In the conf folder, delete the opentext.properties file.
d. You now need to install Directory Services, deploy the AppWorks
Gateway, and install the Tempo Box bundle. For details, see “Deploying the
5.6. Updating the OpenText Tempo Box Bundle
OpenText AppWorks Gateway ” on page 23 and “Installing the OpenText

Tempo Box Bundle” on page 29.

Important

service to start.

6. After the Tomcat service has completely started, you should be able to sign into
the AppWorks Gateway as before. In a browser, type <https://
OpenText_AppWorks_Gateway:port>/gateway to view the AppWorks
Gateway. The AppWorks Gateway and Content Server Administration pages
use the same cookie, so be sure to open the AppWorks Gateway in a different
browser from Content Server to prevent issues.
7. Optional To deploy the OpenText AppWorks Gateway in a cluster, see

“Deploying the AppWorks Gateway in a Cluster“ on page 79.
8. The next step is to update the OpenText Tempo Box bundle.
5.6 Updating the OpenText Tempo Box Bundle

To upgrade the OpenText Tempo Box bundle:


(ot_appworks_addons_1.2.2.otag) that you downloaded in step 1.
6. Click Next and follow the on-screen instructions to upgrade the components,
applications, and services.

(tempobox_10.5.20.otag or above) that you downloaded in step 2. The
previous settings you had for your applications, components, and services
should remain.
8. Optional If you have OpenText Brava! Enterprise for Content Server installed and
you would like to use the Brava! features using the Tempo Box Web UI or
a. Click Services.
For example,
For example,
OTCS=10.5.18.231/OTCS
Chapter 6
Uninstalling OpenText Tempo Box
If you want to uninstall OpenText Tempo Box with the intention of never installing
the module again, you need to archive the Tempo Box folders to preserve the
content for your users before uninstalling the OpenText Tempo Box module.
Archiving Tempo Box folders changes the object type to a regular folder and
renames the folder to OpenText Tempo Box (Archive)<timestamp>. In doing this, the
synchronization of content between clients is removed and all shared folder
connections that users have created are severed, which includes any content that is
shared with external users.
When you uninstall OpenText Tempo Box, the notification agent remains enabled.
To avoid potential errors relating to this, you should disable this scheduled activity
as outlined in the following procedure.
To uninstall OpenText Tempo Box:

2. In the Archive Tempo Box Folders for all users section, click Archive.
page.

Tempo Box Database Administration link.
5. Click the delete link for each table.
page.
7. Scroll to the Notification Administration section, and then click the Configure
Scheduled Activities link.
8. In the OpenText Tempo Box Notification Digest area, select the Disable radio
button.
9. Click Submit.
10. Scroll to the Module Administration section, and then click the Uninstall
Modules link.
11. Click Uninstall for OpenText Content Service.
12. Restart Content Server and then click the Continue link on the Restart Content
Server page.
Chapter 7
Configuring OpenText Tempo Box in Content
Server
The Content Service module provides the core sharing and syncing functionality.
When the module is installed, a custom type called a Tempo Box folder is added to
Content Server. Each user has a Tempo Box folder where their synchronized files
and folders are stored.
You can configure additional features such as granting chosen users the ability to
share folders with external users, enabling email notifications to inform your users
when they have a sharing request, allowing Content Server users to sync an
Enterprise folder to their Tempo Box folder, and setting a storage limit to the Tempo
Box folder.
7.1 Configuring the Content Service Module

To configure the Content Service module:

2. The URL in the OpenText Tempo Box Engine Location box should be set
during the AppWorks Gateway configuration process. Verify this value
matches the following example for your environment:
<https://OpenText_AppWorks_Gateway:port>
3. Tempo Box Folder Location specifies the location of the Tempo Box folder in
Content Server.
4. New Users Get Tempo Box Folders allows you to prevent Content Server from
automatically creating a Tempo Box folder for a user who is added into the
system.
5. External Sharing allows users to share folders with users outside of Content
Server when enabled. Before users can share folders with external users,
additional configuration is required. For details, see “Configuring External User
Sharing” on page 55.
6. The Set Permissions for External Sharing link in the Object and Usage
Privileges row allows you to assign users and groups the permission to share
folders with external users. For details, see “Configuring External User Sharing”
on page 55.
7. External Sharing Email Domain Blacklist prevents users from sharing with
external users at the domains added in this area. External users who have an
email address in the restricted domain and who have been sent share invitations
Chapter 7 Configuring OpenText Tempo Box in Content Server
prior to adding the domain can continue to access the files in the shared folder.
However, they will not be able to receive new share invitations.
8. Enable Publish Action grants users the ability to publish content from their
Tempo Box folder to a location in Content Server when enabled.
9. E-mail Notifications allows users to receive email notifications when enabled.

Before users can receive email notifications, additional configuration is
required. For details, see “Configuring Email Notifications” on page 56.
10. In the Maximum Folder Tree Size field, edit the maximum number of items
that can be stored in each users’ Tempo Box folder, including folders and shared
folders.
11. Date Synchronization allows users to preserve the original file system date for
files and folders when the content is added to the Tempo Box folder using the
OSX and Windows desktop clients. Existing content will not show the original
file system dates. When this option is not enabled, the create and modify dates
show the sync date of when the files and folders are synced to the Tempo Box
folder using the desktop client.
12. When Date synchronization is enabled, Display Synchronized Modified

Dates allows users to see the original file system dates for content added to the
Tempo Box folder using a desktop client in the Web and mobile clients as well.
When this setting is disabled, the existing Content Server modified date
displays in the Web and mobile clients.
13. Click OK.
14. Restart Content Server and then click the Continue link on the Restart Content
Server page.
7.2 Configuring Content Server (Enterprise)

Integration
Your Content Server users can sync any folder in the Enterprise Workspace to their
Tempo Box folder, making the folder content in the Enterprise Workspace available
from anywhere. If the Content Server user has read/write access to the Enterprise
folder then anytime they add, edit, copy, or remove files in the Enterprise folder
using a Tempo Box client, the action is synced to the folder in the Enterprise
Workspace.
Conditions to Sharing Enterprise Folders

In order to add an Enterprise Workspace folder to a user’s Tempo Box folder, the
following conditions must be met:
1. In the OpenText Tempo Box Administration area of the Content Server

Administration page, you must enable the Content Server integration and add
the folder hierarchy to which you want to allow subscriptions. You do not need
7.2. Configuring Content Server (Enterprise) Integration
to add every folder in the hierarchy. When adding folders, choose a folder at the
top of the tree and all of its contents are added to the white list.
2. In the Enterprise Workspace, a user who has the Edit Permissions permission to
the Enterprise folder must enable subscriptions to the folder. This includes
administrators, as well as the folder owner.
When enabling subscriptions, you can choose to enable subscriptions to all of the
items down the tree for which you have the Edit Permissions permission. If you
enable subscriptions down the tree, end users will be able to selectively choose
which subfolders they want to subscribe to. By not enabling subscriptions down
the tree, end users are forced to subscribe to the root folder, which means that all
of the subfolders in the parent folder will sync to the end user’s desktop client.
After subscriptions are enabled, any new folders created within the current
folder will inherit the settings of its parent folder.
3. When the folder allows subscriptions, a user who has the Edit Permissions
permission for the Enterprise folder can share the folder and grant read/write or
read-only access to the folder. This includes administrators, as well as the folder
owner. If the folder owner grants a Content Server user read/write access when
the user currently has read-only access to the Enterprise folder, the additional
permissions are applied. However, if they try to grant read-only access to a
Content Server user who has permissions higher than See and See Contents, no
permissions will be altered and the user will continue to retain their higher
access level. To change the access level for a Content Server user who has read/
write access to a folder, a user who has Edit Permissions permission needs to edit
the user’s permissions at the folder location in the Enterprise Workspace. The
Edit Permissions permission is not granted when sharing a folder.
By sharing an Enterprise folder, the Content Server user will receive a sharing
invitation that they must accept before the Enterprise folder will sync to their
Tempo Box folder.
Content Server users can also add the Enterprise folder to their Tempo Box
folder if they can see the folder in the Enterprise Workspace.
Table 7-1: Folder Permission and Access in Tempo Box
Folder Permission in Content Server Access in Tempo Box

See Read-only access
See Contents Read-only access
Modify Read/write access
Add Items Read/write access
Reserve Read/write access
Delete Read/write access
Edit Permissions Read/write access with the ability to share
Enterprise folders
As with Content Server, your users need the Reserve permission in order to
reserve files in an Enterprise folder from their Tempo Box folder. Also, your
users require the Delete permission in order to delete files in an Enterprise folder
from their Tempo Box folder. If a Content Server user adds an Enterprise folder
to their Tempo Box folder, they may not have these permissions. To grant these
permissions, a user who has the Edit Permissions permission for the Enterprise
folder must edit the user’s permissions at the folder level in the Enterprise
Workspace.
Sharing Enterprise Folders with Standard Users

Sharing Enterprise folders with Standard users is only available if you have
OpenText Tempo Box, Premium Edition. When the Tempo Box Premium module is
installed in Content Server, then sharing Enterprise folders with Standard users
requires the same conditions as sharing Enterprise folders with Content Server
users. For details, see “Conditions to Sharing Enterprise Folders” on page 50.
When all of the conditions are met, a user who has the Edit Permissions permission
for an Enterprise folder can grant read/write or read-only access to the Enterprise
folder using the same process as sharing a Tempo Box folder. The Standard user will
then receive a sharing invitation that they must accept before the Enterprise folder
will sync to their Tempo Box folder. This is the only way in which Standard users
can access the content in an Enterprise folder.
For more information on Standard users, see “OpenText Tempo Box User Types”
on page 7.
Sharing Enterprise Containers with External Users

Sharing Enterprise folders with External users requires the same conditions as
sharing Enterprise folders with Content Server users. In addition, your Content
Server users also require the ability to share folders with External users. For more
information on sharing folders with External users, see “Configuring External User
Sharing” on page 55.
Important
The Content Server users to whom you give external sharing privileges can
grant External users full access to the Enterprise folder, which includes the
ability to add, edit and delete the items in the shared folder. Grant this
privilege to trusted Content Server users only. To share an Enterprise folder
with an External user, the Content Server user must also have Edit
Permissions permission to the Enterprise folder.
When these conditions are met, a user who has the Edit Permissions permission for an
Enterprise folder can share the Enterprise folder with an External user using the
same steps as sharing a Tempo Box folder. The External user will then receive an
email inviting them to register for an OpenText Tempo Box account or, if they
already have an account, a sharing invitation that they must accept before the
Enterprise folder will sync to their Tempo Box folder. This is the only way in which
External users can access the content in an Enterprise folder.
7.2. Configuring Content Server (Enterprise) Integration
7.2.1 Enabling the Content Server Integration and Adding

Folders
To enable the Content Server integration and add folders:
1. On the Content Server Administration page, click the Content Server

Integration link in the OpenText Tempo Box Administration area.
2. Click Enabled.
3. Click Browse Content Server.
4. Navigate to the Enterprise folder that you want to allow your users to access
from their Tempo Box folder and click the Select link.
5. Optional To add more folders, click and repeat steps 3 – 4.
6. Click OK.
7.2.2 Enabling Subscriptions to an Enterprise Folder

To enable subscriptions to an Enterprise folder:
1. Click the folder’s Functions icon, choose Properties, and then choose Tempo
Box.
2. Select the Allow Tempo Box Subscriptions check box. Only users with the Edit
Permissions permission can allow subscriptions to the folder. If you cannot select
this check box and you have the Edit Permissions permission, contact your
administrator.
If a folder has mandatory categories and attributes, a warning message will
appear stating that users will not be able to add new content from their Tempo
Box folders.
3. Optional Click to apply this setting to all subfolders for which you have the
Edit Permissions permission. If you do not select this icon, all users are forced to
subscribe to this folder instead of subfolders down the tree.
4. Click Update.
7.2.3 Inviting Users to Access an Enterprise Folder

To invite users to access an Enterprise folder:
1. Click the folder’s Functions icon and choose Tempo Box Participants.
Only users with the Edit Permissions permission to the Enterprise folder can
invite users to the folder. This includes administrators, as well as the folder
owner. All other users will see a read-only view of the list of participants.
Tip: Content Server users can add an Enterprise folder to their Tempo Box
folder if they can see the folder in the Enterprise Workspace.
2. Optional By default, when you invite a user to access an Enterprise folder, the
user is granted read-only permission. To grant the user read/write permission,
click and then click in the Invite Users area. The access level you
grant is applied to the items in the Enterprise folder for which you have the Edit
Permissions permission only.
If you grant a Content Server user read/write access when they currently have
read-only access to the Enterprise folder, the additional permissions are applied.
However, if you try to grant read-only access to a Content Server user who has
permissions higher than See and See Contents, no permissions will be altered and
the user will continue to retain their higher access level.
• Type the name of the user in the Enter Name box. If the user’s name does
not appear, contact your administrator.
• Type the email address of the External user in the Enter Name box. After
typing a valid email address, auto complete will display the email address of
the External user. If auto complete fails to display the email address, you do
not have permission to share folders with External users.
For more information on the types of users that Tempo Box supports, see
“OpenText Tempo Box User Types” on page 7.
4. Click the user’s name or email address.
5. Optional Repeat steps 2 – 4 for every user you want to invite.
6. Click OK when you have added all of the users. The users you have added will
be notified of the sharing request in their Tempo Box client.
7.3. Configuring External User Sharing
7.3 Configuring External User Sharing

By default, all Content Server users and Standard users who have a Tempo Box
folder can share their content with other Content Server users and Standard users.
However, you can also grant Content Server users and Standard users the ability to
share content with users outside of your company. These users are referred to as
External users. By default, external sharing is disabled. When you enable external
sharing, you need to select the Content Server users and Standard users to whom
you want to grant this privilege.
Caution
With this privilege, the selected users can grant External users with read/
write access to the content in their Tempo Box folder. Grant this privilege to
trusted users only.
When a Content Server user and Standard user shares a folder with a new External
user, it initiates a series of processes in Content Server (shown with blue arrows in
the following figure), as well as a series of processes in Directory Services (shown
with red arrows).
Figure 7-1: External Sharing Flowchart
To configure external user sharing:

3. In the External Sharing section, select Enabled.
Note: Disabling external sharing prevents external users from signing in

and accessing their Tempo Box folder from all clients. This does not delete
their account or Tempo Box content.
4. Click OK.
5. Select the OpenText Tempo Box Configuration Settings link again and then
click the Set Permissions for External Sharing link.
6. In the Usage Privileges area, click Edit Restrictions next to the OpenText
Tempo Box External Sharing usage type.
7. Add only the Content Server users for whom you want to grant the privilege of
sharing folders with external users.
Caution
Allowing users the ability to share folders with external users can
compromise security. Grant this feature to trusted users only.
8. Click Done.
page.
10. You must now setup an email server if you haven’t already done so. For details,
see “Configuring a Email Server for External Sharing and Email Notifications”
on page 58.
7.4 Configuring Email Notifications

There are three types of email notifications that an OpenText Tempo Box user can
receive:
• Shared folder invitations. An email message is sent immediately after the folder
owner shares the folder. By default, OpenText Tempo Box users will receive
notifications for shared folder invitations if an SMTP server is configured.
• Task announcements. When a colleague assigns a task in a shared folder, an
email message is sent immediately to the task assignee. Email messages are sent
to everyone in a share folder if the task is unassigned. The OpenText Tempo Box
user must enable this type of email notifications in the Settings of the OpenText
Tempo Box Web user interface. For details, see the OpenText Tempo Box Web
user interface online help.
• Activity for specific shared folders or for all shared folders, i.e. folders you have
shared and folders you have accepted through an invitation. The activity states
when someone creates, deletes, or adds a version to a file or folder in a shared
7.4. Configuring Email Notifications
folder. Email notifications are sent based on the settings in the Configure
Scheduled Activities page in Content Server. The OpenText Tempo Box user
must enable this type of email notification in the Settings of the OpenText
Tempo Box Web user interface. For details, see the OpenText Tempo Box Web
user interface online help.
To configure email notifications:

3. In the E-mail Notifications section, select Enabled.
4. Click OK.
page.
6. Optional An email notification of a shared folder invitation is sent immediately.

An email notification of shared folder activity and task announcements are sent
every hour by default. To adjust the duration of these notifications, do the
following:
a. In the Notification Administration section, click Configure Scheduled

Activities.
b. In the OpenText Tempo Box Notification Digest section, ensure Enabled
radio button is selected and then adjust the days, hours, and times of the
email notification activity.
c. Click Submit.
7. In order for your OpenText Tempo Box users to receive email notifications, they
must have an email address defined in their Content Server profile. From the
Enterprise menu, select Users & Groups and then view the profiles of your
Content Server users. Refer to the Content Server online help for details on
working with Users & Groups.
8. You must now set up an email server to send the email notifications. For details,
see “Configuring a Email Server for External Sharing and Email Notifications”
on page 58.
7.5 Configuring a Email Server for External Sharing

and Email Notifications
To configure an email server for external sharing and email notifications:
1. Sign in to the AppWorks Gateway.

2. In the left pane, click Settings and then Mail Settings.
3. In the SMTP: from address type the email address from which the external
sharing email invitation or update email is sent.
4. In the SMTP: host box, type the SMTP server.
5. Optional In the SMTP: use SSL check box to set SSL to true or false.
6. Optional In the SMTP: user name box, type the username of and SMTP user.
7. Optional In the SMTP: user password box, type the corresponding password of
the user you defined in step 6.
7.6 Setting a Storage Limit

By default, the size of each users’ Tempo Box folder is unlimited. However, you can
set a maximum size, in megabytes (MB). This limit applies to the total size for the
current versions of all content that the user owns in their Tempo Box folder.
Therefore, this value excludes items shared by other users, any synced Enteprise
folders and Tempo Social file libraries. When a user’s Tempo Box folder approaches
this limit, the will receive a warning message. If they exceed the limit, they will
receive an alert. The alert will continue to reappear until the combined size of all
items in their folder falls below the maximum. Users can continue to add, edit, and
sync files in their Tempo Box folder even after they exceed the limit.
The actual storage space for a user’s Tempo Box folder on the server could be higher
than the user’s Tempo Box limit because Content Server stores prior versions of the
Tempo Box folder items. The number of versions stored in Content Server can be
configured. For information on configuring the number of version stored in Content
Server, see the Content Server Admin Online Help.
To set a storage limit:
1. On the Content Server Administration page, click the OpenText Tempo Box
Storage Limits link in the OpenText Tempo Box Administration area.
2. Next to User Storage Limit, do one of the following:
• Click Unlimited to place no restrictions on the amount of content each user

can store in their Tempo Box folder.
• Next to MB, type a value that indicates the maximum permitted size, in
megabytes, of each user’s Tempo Box folder.
7.6. Setting a Storage Limit
3. Click OK.
page.
Chapter 8
OpenText Tempo Box Client Management
Using OpenText Tempo Box Client Management, you can see the clients that an
OpenText Tempo Box user has used to access their Tempo Box folder. You can also
wipe OpenText Tempo Box clients, which deletes all local copies of server data,
removes the stored username and password, and deletes the client id. The next time
a user attempts to access their Tempo Box folder, an error will display and access
will be rejected. If the wipe was accidental, the user can define a new client ID by
entering their OpenText Tempo Box credentials again. If the wipe was intentional,
you should wipe the client and change the password for the user whose devices you
wiped.
Client Management is now deployed through the AppWorks Gateway, therefore

upgrading from OpenText Tempo Box 10.0.4 will create a new tracking database.
For privacy reasons, client tracking is disabled by default. If you enable client
tracking, you can search for users by username and wipe their devices.
8.1 Enabling Client Tracking

To enable client tracking:
1. Sign in to the AppWorks Gateway as the OTAG administrative user.
2. In the left pane, click Settings and then click Advanced Settings.
3. Select the Client Tracking Enabled check box.
8.2 Monitoring Client Management

To monitor client management:
2. In the left pane, click Client Management.
3. In the Find clients for user box, type a username and then click Go. Client
tracking must be enabled in order to find the clients for a user. For details, see
“Enabling Client Tracking” on page 61.
You will see the username, device information, and connection times for every
client the user has used to access their account.
Chapter 8 OpenText Tempo Box Client Management
8.3 Wiping a Client

To wipe a client:
2. In the left pane, click Client Management.
3. In the Find clients for user box, type the username of a user and then click Go.
Client tracking must be enabled in order to find the clients for a user. For more
information, see “Enabling Client Tracking” on page 61.
You will see the operating systems, client versions, and connection times for
every client the user has used to access their account.
4. Click the Wipe link for the client for which you want to remove server data.
5. Click Wipe to confirm the action. The wipe status changes to Pending. The next
time the user attempts to access their account using the client ID you wiped, the
client wipe will take place. At that point, the status of the wipe changes from
Pending to Complete. To prevent the user from creating a new client ID and
accessing their content, you should now change the user’s password in Content
Server. For details, see the Content Server Online Help.
Chapter 9
OpenText Tempo Box Clients
OpenText Tempo Box offers three types of clients to access your Tempo Box folder:
desktop clients for your Windows and Mac computer, apps for mobile phones and
tablets, and a Web client using a Web browser. The desktop and mobile clients
require that an application is installed in order to access the Tempo Box content. The
Web client does not require an installer.
OpenText Tempo apps are available for the Apple iPhone and Apple iPad, and
Android devices.
• The OpenText Tempo app for iPhone and iPad devices is only available from the
Apple App Store (https://itunes.apple.com/ca/app/opentext-tempo/id781547141?
mt=8).
• The OpenText Tempo app for Android devices is available from Google Play
(https://play.google.com/store/apps/details?id=com.opentext.m.tempo).
You can also download the app from the OpenText Knowledge Center (https://
objAction=browse&sort=name&viewType=1) and deploy it to your Content
Server end users from your local server.
Important
Older versions of the OpenText Tempo Box app will not work with
OpenText Tempo Box 10.6.20.
For details on installing and signing in to the OpenText Tempo app, see the
OpenText Tempo Box, Content Server Edition - Client Installation Guide (SYNC-UQS) on
the OpenText Knowledge Center (https://knowledge.opentext.com/knowledge/
cs.dll?func=ll&objId=24752394&objAction=browse&sort=name&viewType=1).
9.1 Distributing the OpenText Tempo Box Clients

Over-the-Air
The easiest way for your users to install the clients is by setting up an over-the-air
deployment environment. Once configured, your users can follow the instructions in
the OpenText Tempo Box, Content Server Edition - Client Installation Guide (SYNC-UQS)
that is available in the OpenText Knowledge Center (https://
To distribute the OpenText Tempo Box clients, you can download the clients to your
Apache Tomcat server and create an over-the-air deployment environment.
Chapter 9 OpenText Tempo Box Clients
The OpenText Tempo app for iPhone and iPad devices is only available from the
Apple App Store (https://itunes.apple.com/ca/app/opentext-tempo/id781547141?
mt=8).
To distribute the OpenText Tempo Box clients over-the-air:
1. Navigate to the <Tomcat_Home>\webapps folder.

• Create a folder called tempo_clients.

• If you are updating from a previous version, backup the clients that are
currently in the tempo_clients folder.
3. Download the following clients from the OpenText Knowledge Center (https://
objAction=browse&sort=name&viewType=1):
Table 9-1: Download the OpenText Tempo Box Clients
OpenText Tempo Download Location

Box Client
Windows Desktop opentext_tempo_box_<xx>_<yy>.exe
Client where <xx> is the language and <yy> is the 32–bit or 64–bit
version of the installer.
Mac Desktop Client OpenText Tempo Box.dmg
Android App opentext_tempo_android.apk
The Windows Desktop client, Mac Desktop client, Android App, and iOS App
have not changed for Tempo Box 10.6.20. Therefore, your users can continue to
use the 10.5.20 version of the clients and apps.
4. Place the OpenText Tempo Box clients in the <Tomcat_Home>\webapps

\tempo_clients folder.
Note: Ensure the names of the installers match the filenames and paths in
the tempo.clients.properties file in the <Tomcat_Home>\conf folder.
Also, verify that the correct version of the tempo.clients.properties
file was copied to this folder. For example. open this file and verify the
current Android client version.
#Current Android Client Version

AndroidClientVersionForDownload=10.5.20
If this version is incorrect, navigate to <Tomcat_Home>\webapps\content

\WEB-INF\ folder. Copy the tempo.clients.properties file and paste it
in the <Tomcat_Home>\conf folder.
5. Create a backup of the tempo.clients.properties file and tempo_clients

folder.
9.2. Enabling Push Notification for Apple Devices
For details on installing the OpenText Tempo Box clients, see the OpenText
Tempo Box, Content Server Edition - Client Installation Guide (SYNC-UQS) on the
cs.dll?func=ll&objId=24752394&objAction=browse&sort=name&viewType=1).
9.2 Enabling Push Notification for Apple Devices

In environments that include iPhone or iPad devices, the AppWorks Gateway server
must be able to access the Apple Push Notification Service (APNS). The following
locations must be accessible from the server hosting the AppWorks Gateway server:
• gateway.push.apple.com, port 2195
• feedback.push.apple.com, port 2196
To establish a TLS session with APNs, an Entrust Secure CA root certificate must be
installed on the provider’s server. If the server is running OS X, this root certificate is
already in the keychain. On other systems, the certificate might not be available. You
can download this certificate from the Entrust SSL Certificates website at http://
www.entrust.net/.
Making the aforementioned locations available may include making modifications

to host-based, network-level firewall egress rules or both. For assistance, contact the
IT administrator responsible for firewall configuration and network perimeter
security.
9.3 Enabling Push Notification for Android Devices

In environments that include Android devices, the AppWorks Gateway server must
be able to access the Google Cloud Messaging (GCM) service. If your organization
has a firewall that restricts the traffic to or from the Internet, you need to configure it
to allow connectivity with GCM in order for your Android devices to receive
messages. The ports to open are: 5228, 5229, and 5230. GCM typically only uses 5228,
but it sometimes uses 5229 and 5230. GCM doesn't provide specific IPs, so you
should allow your firewall to accept outgoing connections to all IP addresses
contained in the IP blocks listed in Google's ASN of 15169.
Making the aforementioned locations available may include making modifications

to host-based, network-level firewall egress rules or both. For assistance, contact the
IT administrator responsible for firewall configuration and network perimeter
security.
Chapter 9 OpenText Tempo Box Clients
9.4 Configuring the Windows Desktop Client Push

To simplify the process for your users to install or update the OpenText Tempo Box
Windows desktop client, these instructions explain how to silently install or update
the client on your users’ systems. The first time a new user starts OpenText Tempo
Box, they are prompted for their OpenText Tempo Box user name and password.
The OpenText Tempo Box URL is automatically pre-populated.
Notes
• Microsoft C++ Redistributable package and Microsoft .NET 4 Framework
must be installed on your users’ computers before the Windows desktop
client can be installed.
• The Windows Desktop Client Push is intended for new installations of
OpenText Tempo Box Update 4 or above. If your users have manually
installed a previous version of the Windows desktop client, they will see two
instances of the client at the default location of C:\Program Files
\OpenText. Instruct your users to uninstall the OpenText Tempo client and
keep the OpenText Tempo Box client.
To configure the Windows desktop client push:
1. Download the Windows desktop client from the OpenText Knowledge Center
Note: You must create groups of users if you need to deploy both the 32
and 64– bit installers, or if you need to deploy the client in different
languages.
2. Extract the .msi file from the executable file.
3. If you want to customize the default OpenText Tempo Box settings, do the
following:
a. Download and install Microsoft Orca.

b. In Orca, open the .msi file.
c. From the Transform menu, select New Transform.
d. In the Tables column, click Property.
e. In the Property column, locate the following properties and edit the
associated values:
• PushSettings allows the desktop client push to run. Double-click the

Value field and replace False with True.
• TempoServer reflects your URL. Double-click the Value field and
replace http://localhost:8080 with <https://
OpenText_AppWorks_Gateway:port>.
9.4. Configuring the Windows Desktop Client Push
• TempoFolderLocation reflects the location of your users’ Tempo Box

folder. The folder is placed in your users’ My Documents folder when
this value is set to Default.
• StartTempoOnStartup runs OpenText Tempo Box when the user signs
in, if this value is set to True.
• ShowTempoNotifications displays notifications relating to the sync
status of the users’ Tempo Box folder, if this value is set to True.
f. From the Transform menu, select Generate Transform and save the file.
This generates a Windows Installer Transform file (.mst)
4. Deploy the .msi file from step 2 or the .mst file you created in step 3.
5. Once deployed, your users will be prompted to enter their user name and
password upon starting OpenText Tempo Box.
Chapter 10
Synchronizing Standard Users in OpenText
Directory Services
Content Server 16.0.0 uses OpenText Directory Services when authenticating users.
With Directory Services, you can provide the employees at your company who do
not have Content Server licenses with their own Tempo Box folder. These users are
referred to as Standard users. This will allow Standard users the ability to sync and
share files with Content Server users, as well as other Standard users. For more
information on Standard users, see “OpenText Tempo Box User Types” on page 7.
Important
Support for Standard users requires Content Server 16.0.0 or Content Server
10.5.0 with the 2015–03 Update or later, as well as Directory Services 16.0.0 or
Directory Services 10.5.0 SP 1 Patch 5 or later.
10.1 Synchronizing Standard Users for Tempo Box

from Active Directory to Directory Services
To synchronize Standard Users from Active Directory to Directory Services:
1. In a browser, enter the URL of the Directory Services Web Client. For example,
https://<Domain_name>:8002/otds-admin/.
2. Enter the credentials of an Directory Services Admin user and click Sign In. For
example, type otadmin@otds.admin.
3. In the left pane, click User Partitions and select New Synchronized User
Partition.
4. On the Connection Information page, enter the IP address, port, and
encryption method of your Active Directory server. Click Test Connection
before proceeding. Click Next.
5. On the Authentication page, enter the user name and password of an Active
Directory admin user. Click Test Authentication before proceeding. Click Next.
6. On the General page, type a name for your user partition. For example,
“Standard User Partition”. Make sure the Start importing users and groups
automatically check box is selected. Click Next.
7. On the Server Settings page, select the server type and naming context. Click
Verify Settings before proceeding. Click Next.
8. On the Group Locations page, click Edit for the Group Locations.
9. Select the group(s) that you want to import into Directory Services and click
Save.
Chapter 10 Synchronizing Standard Users in OpenText Directory Services
10. Select the Import users from matched groups check box.
11. Click Test Filter and Locations. If the test results are correct, click OK and then
click Next.
12. On the User Locations page, click Edit for the User Locations.
13. Select the group(s) that you want to import into Directory Services and click
Save.
14. Click Test Filter and Locations. If the test results are correct, click OK and then
click Next.
15. On the User Mappings page, locate the following Directory Services Attributes.
Click the attributes and set the mappings as shown below.
oTDepartment
OTDS Attribute: oTDepartment
Active Directory Attribute: cn
Format: Tempo Box Standard Users
oTType
OTDS Attribute: oTType
Format: ExternalUser
10.1. Synchronizing Standard Users for Tempo Box from Active Directory to Directory
Services
Click Test Mappings. You may receive a warning that some of the attributes are
not set. This is ok. Click OK. If the mapping is successful, click Next.
16. On the Group Mappings page, locate the following Directory Services
Attributes. Click the attributes and set the mappings as shown below.
oTType
Format: ExternalGroup
17. On the Monitoring page, accept the default settings and click Test Search. If the
test was successful, click Next.
18. On the Scheduler page, accept the default setting or add a schedule to perform
a full sync. Click Next.
19. On the Notifications/Search page, accept the default settings and click Test
Search. If the search setting is successful, click Next.
20. On the Extended Functionality page, accept the default settings and click Test
Attributes. If the test is successful, click OK.
21. Click Save.
Chapter 10 Synchronizing Standard Users in OpenText Directory Services
10.2 Consolidating Users from Active Directory to

Content Server
To consolidate users from Active Directory to Content Server:
1. Click Access Roles in the left pane. Click Actions for Access to Content Server
and then click View Access Role Details.
2. Click Add and then select the check box for the Active Directory partition
(Standard User Partition) you defined previously. Click Add Selected Items to
Access Role and then click Close Dialog. Click Save.
3. Click Resources in the left pane. Click Actions for Content Server. Select
Consolidate and then click Consolidate.
4. Ensure that your Content Server resource has the proper mappings. Click
Resources in the left pane. For Content Server resource, click Actions and then
Properties. Click User Attribute Mappings and verify the following user
attribute mappings:
Type
Resource Attribute: Type
Format: %s
GroupID
Resource Attribute: GroupID
OTDS Attribute: oTDepartment
Format: %s
10.2. Consolidating Users from Active Directory to Content Server
5. Sign into Content Server as an admin user and view the list of users that are
now available.
Chapter 11
Migrating External Users into OpenText Directory
Services
If you choose to connect to your existing OpenText Directory Services installation to

authenticate users, you will need to follow these instructions to migrate any existing
external Tempo Box users. This includes Tempo Box users who were sent a sharing
request and created an account, as well as those who have not created an account.
For complete information on the Migration Tool, see OpenText Content Server to
OpenText Directory Services User Migration Tool - Installation, Configuration, and User
Guide (OTDS-CGD) in the OpenText Knowledge Center (https://
objAction=browse&viewType=1).
Important
These steps assume you are already using Directory Services as your Content
Server authentication method.
To migrate external users into OpenText Directory Services:

1. Ensure the latest patches for the Content Service module are installed. For a list
of required patches, refer to the Release Notes on the OpenText Knowledge
2. Ensure the latest patches for Directory Services are installed. For a list of
required patches, refer to the Release Notes on the OpenText Knowledge Center
(https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&
objId=18982571&objAction=browse&sort=name) and follow the installation
instructions that are available in the same folder.
3. Download the Content Server to OTDS User Migration Tool 10.5.3 from
llisapi.dll?func=ll&objId=61575716&objAction=browse&viewType=1).
4. Extract the contents of the zip file and double-click OTDS.CS.Tools.exe. The
zip file also contains configuration files that you can choose to edit before
running the installer. For more information on the configuration files, see the
OpenText Content Server to OpenText Directory Services User Migration Tool -
Installation, Configuration, and User Guide (OTDS-CGD) in the OpenText
Knowledge Center (https://knowledge.opentext.com/knowledge/llisapi.dll?
func=ll&objId=61575716&objAction=browse&viewType=1).
5. On the Before You Begin page, make sure you know the stated information
before proceeding and then click Next.
6. On the Data Provider page, choose the type of your Content Server database
and then click Next.
Chapter 11 Migrating External Users into OpenText Directory Services
7. On the Content Server Database page, provide the connection and

authentication information for your Content Server database:
a. In the SQL/Oracle server name field, type the name of the server.
b. In the Database name field, type the name of the database.
c. In the SQL/Oracle user name field, type the name of the SQL or Oracle
admin user name.
d. In the Database user name field, type the name of the user authorized to
access the database.
e. In the Password field, type the password for the SQL or Oracle admin user.
f. Click the Test Connection button. After you have successfully tested the
database connection, click Next.
8. On the Directory Services Server page, type the name of the Directory Services
server, along with the user name and password of an Directory Services admin
user who has the ability to create user partitions. Click Test Connection. After
you have successfully tested the Directory Services connection, click Next.
9. On the Migration Type Configuration page, do the following:
a. Select Content Server users and groups.

b. Select Tempo external users and groups.
c. Click Next.
10. On the New Non-Synchronized User Partition page, do the following:
a. In the Name of new non-synchronized user partition field, type otag.

b. Click Next. A dialog will appear asking if you want to migrate users and
groups into this user partition.
c. Click Yes.
11. On the New Content Server Resource page, do the following:
a. Type the name of your Content Server resource. For example, OTCS.
b. Click Next. A dialog should appear stating, “A resource with the name
already exists. Do you want to continue without resource creation?”
c. Click Yes.
12. On the Connection Information page, do the following:
a. Edit the Member Service WSDL value to show cws. For example,
http://<server-name>:8080/cws/services/MemberService?wsdl
Do not use localhost.

b. The Security Clearance WSDL field is only used if RM Security clearance is
being used with Directory Services. You can ignore this field.
c. Edit the Authentication Service WSDL value to show ot-authws. For
example,
http://<server-name>:8080/ot-authws/services/Authentication?
wsdl
Do not use localhost.

d. In the User name and password fields, provide the username and password
of your Content Server admin user.
e. Verify that Default Group states DefaultGroup.
f. Click Test Connection.
g. After you have successfully tested the connection, click Migrate.
13. On the Migration Status page, ensure there are no errors in the migration
process. Click Next.
14. On the Resource Activation page, click Finish. There is no need to update the
resource identifier or verify activation.
15. Sign in to the OpenText Directory Services Web Client as an admin user.
16. In the left pane, click Resources.
17. Click Actions for the Content Server resource and then select Consolidate.
To verify the migration:
1. Navigate to the folder from which you ran the Migration Tool. The Migration
Tool generates a otds.cs.tools.log file which records the successes and
failures of the migration.
2. In the OpenText Directory Services Web Client, click User & Groups. Verify the
migrated users and groups were added to the otag partition.
Chapter 12
Deploying the AppWorks Gateway in a Cluster
You can deploy and configure additional AppWorks Gateway servers to use an
existing AppWorks Gateway database. Any application, service, or component that
is installed on one node in the cluster is automatically installed on all of the other
nodes. All settings changes are also propagated to all of the nodes. You do not need
to perform any manual steps on any other node or restart the Apache Tomcat
service. However, you must restart the Apache Tomcat service if you change any of
the following settings in the AppWorks Gateway Advanced Settings page:
• Changes to the Back-channel stale connection cleanup period (s) will only take
effect when the current period elapses or when the Apache Tomcat servers are
restarted.
• Updates to the Cluster Key are not generally necessary and may require that all
nodes be restarted.
• Changes to the OTAG token cleanup interval (s) and the OTAG token session
timeout (s) will only take effect once the current interval elapses or when the
Apache Tomcat servers are restarted.
• Changes to the Temporary Directory Path should be done when the servers are
off-line, because some services may lose temporary data. Changing the
Temporary Directory Path may leave old temporary files in the former location.
The Temporary Directory Path location must exist on disk before changing the
path in the AppWorks Gateway. The default location is C:\Apache Software
Foundation\Tomcat 8.0\tmp.
• Changes to the Temporary file cleanup interval (s) will only take effect when the
current interval elapses or when the Apache Tomcat servers are restarted.
Note: In most cases, you should not change advanced settings.
Clients that are connected to one node can also switch to another node and continue
functioning.
All nodes must be on the same subnet. They must also be mutually accessible using
the User Datagram Protocol (UDP) and through the Transmission Control Procotol
(TCP) on port 4000. UDP is used for cluster node discovery and TCP on port 4000 is
used for intra-cluster communication.
To deploy AppWorks Gateway in a cluster:
1. Ensure you have Apache Tomcat 7.x or 8.x and JDK 1.7.x or 1.8.x installed on
each node.
2. Stop the Apache Tomcat service on each node.
Chapter 12 Deploying the AppWorks Gateway in a Cluster

Important
4. Extract the contents of the appworks_gateway_1.2.2.zip file into the root of

the Apache Tomcat folder on each node. For example, C:\Program Files
\Apache Software Foundation\Tomcat 8.0.
5. On each node, copy the <Tomcat_Home>/conf/opentext.properties file from

the original node to the <Tomcat_Home>/conf folder on each of the other nodes.
6. Configure a load-balancer in front of the AppWorks Gateway nodes. When

complete, sign in to the AppWorks Gateway, click Settings, and edit the OTAG
Server URL to point to the load-balancer's address.
Note: Repeat this procedure at any time to add nodes to the cluster. They
must also be added to the load-balancer.
Chapter 13
Configuring SSL on Apache Tomcat
OpenText strongly recommends using SSL to increase security of the system. This
section explains how to configure SSL on Apache Tomcat to allow OpenText Tempo
Box to work with the HTTPS protocol.
13.1 Creating the Java Keystore File

To create the Java keystore file:
1. On your local file system, create a folder into which you will create the keystore.
For example, C:\new-keystore. If you do not do this, the keytool utility will
create the keystore in the root directory of the user running the tool.
2. Open a Command Prompt window and navigate to <JAVA_HOME>/bin where

you will find the keytool.exe utility.
3. Run the following command:
keytool.exe -genkey -alias <tomcat> -keyalg RSA -keystore <C:

\new-keystore\keystore.jks>
Note: This is one single continuous line.
The name of the -alias is not important and does not have to be tomcat. Make
sure the aliases you create in this keystore are the same throughout this process
unless otherwise stated.
The name of the -keystore is also not important and does not have to be
keystore.jks
The tool will ask you a series of questions about the keystore including a
keystore password.
The main question of relevance is the following question.
What is your first and last name?
The required input is the fully qualified name of the server you wish to deploy
it on. For example, tempo.company.net.
Note: Make sure you record the keystore password because you will need
it later in this chapter.
4. Enter all the other requested parameters. When completed, the command
prompt returns.
Chapter 13 Configuring SSL on Apache Tomcat
You now have a functioning keystore called keystore.jks for your required host,
which is located in the C:\new-keystore folder. Next, you need to generate a
Certificate Signing Request (CSR) that you can submit to your Certificate Authority
(CA) for signing.
13.2 Creating a Certificate Signing Request (CSR)

To create a Certificate Signing Request (CSR):
• In the Command Prompt window you used in the previous section, run the
following command:
keytool.exe -certreq -keyalg RSA -alias <tomcat> -file <C:\new-

keystore\certreq.csr> -keystore <C:\new-keystore\keystore.jks>
Notes
• This is one single continuous line.
• You must enter the keystore password that you set when creating the
keystore in the previous section.
When complete, you should have a CSR file called certreq.csr , which is
located in the C:\new-keystore folder.
This CSR file now needs to be submitted to your signing authority for signing. After
it has been signed, you should receive both the signed certificate for your server and
also the ROOT certificate from the Certificate Authority (CA) that was used to sign
the new certificate. If the CA uses intermediate chain certificates, you will also need
these as well.
Important
It is crucial that you have the full chain of certificates used to sign your new
certificate. Without the complete chain, SSL communication will fail.
13.3 Signing a CSR File Using Windows Certificate

Services
If you have access to a local Windows Certificate Services system, you can use this to
sign the CSR file that you created in the previous section. This process can be used if
you are building an internal system and do not have access to an external CA, such
as VeriSign.
To sign a CSR file using Windows Certificate Services:
1. In a text editor, open the certreq.csr file that you created in the previous
section.
2. Navigate to the browser interface of the Windows Certificate Services Server.

For example, https://domain_name/certsrv/.
13.4. Importing the Certificate Chain Into the Keystore
3. Click the Request a certificate link.
4. Click the advanced certificate request link.
5. Click the second link for base-64 encoding. For example, the Submit a
certificate request by using a base-64–encoded CMC or PKCS #10 file link.
6. Copy and paste the entire contents of the CSR file from your text editor into the
Saved Request box.
7. In the Certificate Template list, click Subordinate Certification Authority.
8. Click Submit. You should then get an option to download the newly signed
certificate in DER format.
9. Download the certificate to a suitable location on your file system and open it.
You now have your signed certificate. Next, you need to export the ROOT
certificate used to sign it.
10. In the certificate dialog box, click the Certification Path tab. You should see the
chain of certificates.
11. Select the root certificate and click View Certificate. The root certificate opens.
12. For the root certificate, click the Details tab.
13. Choose the Copy to File option. This will launch the Export Certificate Wizard.
14. Export the certificate in DER format to the same location where you saved the
server certificate, which is the C:\new-keystore folder.
You should now have the following:

• A created keystore for your server.
• A server certificate signed by your CA.
• The root certificate from the CA that was used to sign your certificate.
13.4 Importing the Certificate Chain Into the Keystore

You now need to add your certificate chain into your keystore. This has to be done
in a specific order to ensure the SSL chain is correct.
To import the root signing certificate into the keystore:
1. In the same Command Prompt window that you used in the previous sections,
run the following command:
keytool.exe -import -alias rootCA -keystore <C:\new-keystore

\keystore.jks> -trustcacerts -file <C:\new-keystore\rootca.cer>
Notes
• You will need to enter the keystore password.
In this example, the root certificate used to sign the server certificate is named
rootCA.cer.
The -alias rootCA is a unique alias in the keystore.
The location of the keystore is C:\new-keystore\keystore.jks.
2. The keytool will ask if you want to import the certificate. Choose Yes.
Now that you have the Root certificate in the keystore, you can add the signed
server certificate.
To import the signed server certificate into the keystore:
1. In the same Command Prompt window that you used in the previous sections,
run the following command:
keytool.exe -import -alias <tomcat> -keystore <C:\new-keystore

\keystore.jks> -file <C:\new-keystore\rootca.cer>
Notes
• You will need to enter the keystore password.
In this example, the name of the server certificate signed by the CA is

newcert.cer.
The -alias <tomcat> is the same alias in the keystore used to create the CSR.
The location of the keystore is C:\new-keystore\keystore.jks.
2. You should now have a new keystore that contains the signed server certificate
and the chain of certificates used to sign it. You can check the contents of the
keystore using keytool. For example,
keytool.exe -list C:\new-keystore\keystore.jks
This will list the certificates in your keystore.
13.5 Adding the Keystore to OpenText Tempo Box

The chain of certificates from the new keystore needs to be added to the internal
Content Server keystore so that the Content Service module can communicate via
SSL to the OpenText AppWorks Gateway Engine. You do this with the keytool
utility on Content Server. The Content Server keystore resides in:
<Content_Server_Home>/jre/lib/security
The keystore is called cacerts.
By following these steps, your Tomcat server can still run in normal mode at the
same time on port 8080 with HTTP.
13.5. Adding the Keystore to OpenText Tempo Box
To add the new keystore to OpenText Tempo Box:
1. Stop the Tomcat server.
2. Open the server.xml file located in the <TOMCAT_HOME>\conf directory in a

text editor.
3. Locate the <Connector> element with port="<8443>" as seen below. Ensure the
line is uncommented and add the two highlighted lines.
<Connector port="<8443>"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="true" disableUploadTimeout="true"
acceptCount="100" debug="0" scheme="https"
secure="true" clientAuth="false" sslProtocol="TLS"
keystoreFile="C:\new-keystore\keystore.jks"
keystorePass="<keystore_password>"/>
4. Save and close the file, and then restart the Tomcat server.
5. Check the setting by entering the following URL in your Web browser:
https://<Apache_Tomcat_Host>:<8443>
6. Copy the signed server certificate and the root certificate to Content Server.
7. From a command prompt, navigate to the keytool binary. For example,
<Content_Server_Home>/jre/keytool.exe
8. Import the root certificate by running the following command:
keytool.exe -import -trustcacerts -alias rootCA -file C:

\rootca.cer -keystore c:\opentext\jre\lib\security\cacerts
The -alias rootCA is a unique alias chosen to import the root certificate into.
The -file C:\rootca.cer parameter is the location of the Root certificate used
to sign the OpenText Tempo Box server certificate.
9. Choose Yes to import it when prompted.
10. Import the server certificate by running the following command:
keytool.exe -import -trustcacerts -alias tomcat -file C:

\certnew.cer -keystore c:\opentext\jre\lib\security\cacerts
The —alias tomcat is a unique alias chosen to import the Tomcat certificate.
The -file C:\certnew.cer parameter is the location of the OpenText Tempo
Box server certificate.
11. Choose Yes to import the certificate when prompted.
12. Check using keytool that the new certificates are in place. This will list the
certificates in your keystore. For example,
keytool.exe -list C:\opentext\jre\lib\security\cacerts

\certnew.cer
13. Import the certificate used to identify the Content Server machine into the
default Java keystore on the Tomcat machine, that is, the instance of Java that is
used to run Tomcat. This is generally the instance stated in the PATH variable.
For example, C:\Program Files (x86)\java\jre7\lib\security\cacerts.
This is needed so that Tomcat will accept the certificate offered by Content
Server.
Chapter 14
Troubleshooting
The following FAQs cover basic troubleshooting information.
When Content Server is configured with OpenText Directory

Services authentication, OpenText Tempo Box cannot log into
the Content Server at all.
OpenText Tempo Box will work with an Directory Services-enabled Content Server
under the following conditions:
1. Make sure you are running Tomcat 7.x or 8.x.

2. Make sure Tomcat is using JDK 1.7.x or 1.8.x.
3. Make sure that Content Server is configured to use Directory Services. Also, you
need to made sure to add the otag partition to the Content Server resource in
Directory Services.
When I try to access the OpenText Tempo Box Web Client, an

error appears saying “OpenText Tempo Box” is not enabled on
this server.
To resolve this problem, you need to enable Tempo Box in the AppWorks Gateway.
Do the following:

2. In the left pane, click Services.
3.
Locate Content Service and click the Settings icon .
4. Click the Settings tab.
5. Select the Enable Tempo Box check box.
I have Brava! Enterprise for Content Server installed yet I don’t

have Brava! as an option for my documents in the Tempo Box
Web UI or in the Tempo app.
If you have Brava! Enterprise for Content Server installed and you would like to use
the Brava! features for your documents in your Tempo Box folder, you need to
update the proxy mappings in AppWorks Gateway and verify the Brava! license is
assigned in Content Server. To update the mappings, do the following:
Chapter 14 Troubleshooting
2. Click Services.
3.
Click for OTAG Reverse Proxy Service and click the Settings tab.
4. In the Allowed path patterns region, add the following paths.
For example,
5. In the Proxy Mappings region, replace the instances of localhost with your
Content Server host and port number.
For example,
OTCS=10.5.18.231/OTCS
7. In the Tempo Box Web User Interface, sign in and navigate to a document.
8.
Point to the item’s function menu and then click Brava!. If Brava! is not
available, you may not have a Brava! license for the selected file type. Verify the
Brava! licenses in Content Server.
I want to use Content Server to authenticate users.

Content Server 16 only supports Directory Services to authenticate users. For users
with Content Server 10.5, do the following:
1. After deploying the AppWorks Gateway, open a browser, type <https://

OpenText_AppWorks_Gateway:port>/gateway to view the OpenText
AppWorks Gateway Admin page. The AppWorks Gateway and Content Server
use the same cookie, so be sure to open the AppWorks Gateway in a different
browser from Content Server to prevent issues.
2. From the Choose Your Database list, select a database and provide the required
information.
The Embedded Derby option is not intended for production environments.
The Custom Connection String option is intended for experienced database
Administrators only and must be used with caution.
3. Click Save Changes. The configuration is complete when you are prompted to
sign in to the AppWorks Gateway again.
4. Sign in to the AppWorks Gateway as the OTAG administrative user. For
example,
Username = otag
Password = otag
The OTAG administrative user password may differ if you defined a different
password in the Password for new OTAG administrative user box when
5. In the left pane, click Settings.
6. In the Content Server URL box, type your Content Server URL. For example,
<https://Content_Server_Domain:port>/OTCS/cs.exe
7. In the OTAG Server URL box, replace http://localhost:8080 with your

actual Apache Tomcat server. This should be a URL that can be reached both
from Content Server and from off-site.
8. Click Test Content Server URL and then click Save Changes.
9. Sign out of the AppWorks Gateway.

editor.
12. Locate the <GlobalNamingResources> section and add the following:
<GlobalNamingResources>
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and
saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
<Resource auth="Container"
factory="com.opentext.otag.auth.CSIdentityServiceFactory"
name="otag/IdentityService"
type="com.opentext.otag.auth.IdentityService"/>
</GlobalNamingResources>
Note: By adding this section, Content Server users with administrative

permissions can sign into the AppWorks Gateway.
13. Save and close this file, and then start the Apache Tomcat service. It may take a
few minutes for the Tomcat service to start.

14. Sign in to the AppWorks Gateway as a user who has Admin permissions on
Content Server.
15. In the left pane, click Trusted Servers.
16. Click the Select list and click ContentServer.
17. Click Generate Key and click Add New. This will make a trusted connection
between the AppWorks Gateway and Content Server. In a clustered
environment, you only need to do this once.
Important
After clicking Add New, if you were signed out of the AppWorks
Gateway, you do not have System administration rights privileges in
Content Server. Make sure you perform these steps by signing into the
AppWorks Gateway as a user who has this permission in Content
Server.
Note: You will notice that this key matches the Shared Key in the Content
Service Notifier Settings page for the Content Service module in Content
Server. These two values must remain the same.
When two users with same login name are added to two different
Directory Services partitions, authentication fails. Why?
The usernames in every partition in Directory Services must be unique. For example,
if you have two users with the username jsmith in different partitions, jsmith@otag
and jsmith@csusers, this must change to jsmith@otag and jsmith1@csusers.
How do I deploy OpenText Tempo Box with clustered servers?

A typical deployment of OpenText Tempo Box will require multiple Content Server
installations for every AppWorks Gateway server. As the AppWorks Gateway can
only be configured with a single Content Server URL, this needs to point to the load
balanced URL if deploying with a Content Server cluster. On the Content Server
side, the Java notification component on each node must be configured to point to
the AppWorks Gateway. This is the case in all deployment scenarios.
My Windows client is not getting file change notifications

If the Windows client is not reflecting changes made from other OpenText Tempo
Box clients, this is normally due to a notification configuration failure. Verify the
following:
1. Ensure that the shared key matches.

a. Sign in to the Content Server Administration page and select Content
Service Notifier Settings in the Content Service Administration section.
b. Sign in to the AppWorks Gateway and select Trusted Servers. Compare the
ContentServer value with the Shared Key value on the Content Service
Notifier Settings page in the previous step.
2. Ensure that the destination protocol, host, and port are set correctly on all nodes
if in a clustered environment. If the engines are clustered, these should all be
lists representing the various nodes in the engine cluster.
b. Verify the path in the Destination section.
3. If SSL is required between the Content Server module and AppWorks Gateway,
and if the SSL certificate is not signed by a trusted authority (trusted by both
Content Server and AppWorks Gateway) the certificate must be manually added
to both machines, as well as their respective JVMs. To determine whether SSL is
the problem, first configure the notifications to use regular HTTP and test before
forcing HTTPS.
I am not receiving email notifications

In order to receive email notifications for shared folders, the following criteria must
be met:
• On the Content Server Administration page and select OpenText Tempo Box
Configuration Settings in the OpenText Tempo Box Administration section.
Make sure E-mail Notifications is Enabled.
• On the Content Server Administration page and select Configure Scheduled
Activities in the Notification Administration section. In the OpenText Tempo
Box Notification Digest, make sure the status is Enabled and review the
duration of email notifications. This setting only affects the duration of shared
folder activity email notifications.
• In Content Server, the OpenText Tempo Box user needs to have an email address
defined for their profile.
• On the AppWorks Gateway Mail Settings page, a valid SMTP host must be
defined.
• In the OpenText Tempo Box Web client settings, the OpenText Tempo Box user
needs to indicate the type of email notifications they want to receive. Sharing
request notifications are sent by default. For more information, refer to the
OpenText Tempo Box Web client online help.
• If you are using Directory Services authentication, verify the following settings in
your Directory Services configuration:
• The connection parameters should use cws URLs instead on les-services
URLs.
• The Group attribute mapping in the Content Server resource is Type=oTType.
• The User attribute mapping in the Content Server resource is Type=oTType.
Notes
• Users can receive notifications for select, specific shared folders or for all
shared folders, that is, folders you have shared and folders you have
accepted through an invitation. All preferences can be set in the Tempo Box
Web UI.
• Users only receive notifications on shared folders, not un-shared folders.
• Users will not receive email notifications for activity which they initiated,
only activity within the share that other users performed.
How do I allow OpenText Tempo Box to accept large files in

Internet Explorer?
In order to allow OpenText Tempo Box to accept large files, you need to do the
following:
1. Open IIS.
2. Click your Content Server application.
3. In the Management section, click Configuration Editor.
4. Navigate to system.webServer > security > requestFiltering.
5. Add or edit the value of requestLimits.maxAllowedContentLength. For
example, setting the value to 2147483648 will accept files that are up to 2 GB in
size. Files larger than 2 GB cannot be added to your Tempo Box folder,
regardless if this value is higher.
6. Click Apply.
I am having trouble with large numbers of concurrent uploads

It has been noted that Content Server may have trouble with large numbers of
concurrent uploads with the default IIS configuration. It is recommended that you
increase the MaxConcurrentRequestsPerCPU setting in IIS. It is also recommended
that you increase the maxAllowedContentLength to 2147483648 bytes.
I am receiving an "out of memory" error when trying to install the

OpenText Tempo Box bundle
If you receive this error, make sure you are connecting to an Oracle or Microsoft
SQL Server database and not the Embedded Derby database. You can also add the -
XX:MaxPermSize=512m option to the list of Java options in the Apache Tomcat Java
settings, and set the initial and maximum memory pool to 256 and 1024 respectively.
My AppWorks Gateway server URL is not reachable from Content

Server and from off-site
If there is no such URL, do the following:

Content Server.
2. Click Settings.
3. In the OTAG Server URL box, type the desired public URL.
5. Click Trusted Servers.
7. Click Generate Key and click Add New.
How do I configure Application Request Routing (ARR) in IIS for

Tempo Box?
Information on this is available in the OpenText Knowledge Center (https://
objAction=ArticleView&viewType=1).
How can I troubleshoot the AppWorks Gateway?

The AppWorks Gateway provides information in the gateway.log file which is
located in the <Tomcat_Home>\logs directory. Information is also available in the
default Catalina logs such as catalina_<date>_.log and localhost-
access_logs.<date>.txt.
For debugging, first check the Catalina log for errors, and if necessary check the
localhost-access_logs.<date>.txt in Tomcat as they record each request. This
allows you to confirm timing and response codes for each request when nothing
appears in the logs.
Commonly reported issues revolve around OpenText Directory Services

configuration. On the initial AppWorks Gateway configuration, there is a chance
that the Directory Services configuration will fail either due to port conflicts,
memory issues, failure to communicate with an external Directory Services (firewall
blocking request, mistyped config info) or resource conflicts with existing Directory
Services data. The Catalina logs will show exceptions in Directory Services
configuration. For more information, review the Directory Services logs which can
provide additional information. These logs can be found on the Tomcat server used
to host your Directory Services installation. Errors relating to port conflicts and
resource name conflicts will be clearly indicated in the logs. Other error cases may
require further investigation.
Beyond initial configuration of the AppWorks Gateway, there are very few error
scenarios that would be indicated in the logs. The primary issue that can occur
relates to authentication errors. If the user has entered a correct password, but
cannot authenticate, these issues will not be captured in the log files. The following
steps are recommended to troubleshoot authentication errors.
1. Double check that the credentials and server URL were typed correctly. This is
often the problem.
2. Try connecting using a different client.
3. Try using the fully qualified name. For example. <username>@otag for internally
created users, <username>@<domain> for Directory Services synced users.
4. Log in to Directory Services and check that the user’s account hasn’t expired or
been locked.
5. Add a new user in the AppWorks Gateway. Then sign in to Directory Services
and verify that the new user was added to the otag User Partition.
6. If you were using Content Server auth and you changed to Directory Services
auth, make sure you have removed the following entry in the
<GlobalNamingResources> of the Tomcat server.xml file.
saved"
7. Make sure that the shared key matches in Content Server and AppWorks
Gateway match.

b. Sign in to the AppWorks Gateway and select Trusted Servers. Compare the
ContentServer value with the Shared Key value on the Content Service
Notifier Settings page in the previous step.
If the shared key values do not match, generate a new key in the AppWorks
Gateway. On the Trusted Servers page, click Refresh Key and then click the
check mark.
External users are unable to delete items from a share folder

In Content Server 10.5, if the OpenText Recycle Bin or OpenText Document Undelete
modules are installed after the Content Service module, external users and standard
users will not be able to delete items from a shared folder. To allow these users the
ability to delete items, do the following:
1. On the Content Server Administration page, click the OpenText Tempo Box
Maintenance link in the OpenText Tempo Box Administration area.
2. In the Permissions row, click Add.
I‘m having difficulties signing into AppWorks Gateway and
creating a trusted server with Content Server 10.5.0 SP 1 when
using CSDS
If you choose to use Content Server Directory Services when authenticating your
1. Make sure you have the following patch installed in Content Server.
# Patch PAT100000517 created at Tue Sep 11 09:30:37 2012

#
# Issue: LPG-669
# Module: Livelink DS 10.0.0
# Version: Content Server 10.0.0 64-bit for Windows
#
# Description: Cannot authenticate external users from Active
Directory using OTE with Directory Services

editor.
4. Locate the <GlobalNamingResources> section and add the following:
saved"
5. Save and close this file, and then start the Apache Tomcat service. It may take a
few minutes for the Tomcat service to start.

Content Server and the AppWorks Gateway. For example, the Content Server
Admin user.
7. In the left pane, click Trusted Servers.
9. Click Generate Key and click Add New. This will make a trusted connection
between the AppWorks Gateway and Content Server. In order to set a trusted
server, you must sign into the AppWorks Gateway as a Content Server Admin
user.
After clicking Add New, if you were signed out of the AppWorks Gateway, you
do not have System administration rights privileges in Content Server. Make
sure you perform these steps by signing into the AppWorks Gateway as a user
who has this permission in Content Server.
Note: You will notice that this key matches the Shared Key in the Content
Service Notifier Settings page for the Content Service module in Content
Server. These two values must remain the same.
External users are not able to create an account or sign in to

Tempo Box
If you are trying to share a folder with an external user and the external user is
unable to access Tempo Box, verify the following information:
2. Click User Management and add a user.
3. Sign in to the OpenText Directory Services Web Client.
4. In the otag User Partition, verify that the user you added in the AppWorks
Gateway was added to this partition.
5. If you were previously using CS authentication, navigate to the server.xml in

the <Tomcat_Home>\conf folder and verify that the highlighted section is
commented out or removed.
saved"
I have installed Tempo Box on a DMZ and Directory Services on
an internal server. When I access the Tempo Box URL, it is
redirecting to a Directory Services URL where the Directory
Services URL can't be accessed from outside an internal
network.
The reverse proxy feature of the AppWorks Gateway can be used to configure access
to Directory Services, without exposing it externally.
2. In the left pane, click Proxy.
3. In the Proxy Mappings section, add the following mappings:
otdsws=<servername:8443>/otdsws
otds-v2=<servername:8443>/otds-v2
ot-authws=<servername:8443>/ot-authws
Be sure to replace “servername:8443” with your Directory Services server

address.
4. Click Save.
5. In the Allowed path patterns section, add the following mappings:
otdsws/*
otds-v2/*
ot-authws/*
6. Click Save.
7. In the left pane, click Settings.
8. On the General Settings page, in the OTDS url box, enter the AppWorks
Gateway URL rather than your existing external Directory Services installation.
The Directory Services Reverse Proxy will route all Directory Services calls
through this URL to your external Directory Services server.

OpenText Tempo Box, Content Server Edition 10.6.20 - Installation and Administration Guide English (SYNC100620-IGD-En-01)

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

OpenText Tempo Box, Content Server Edition 10.6.20 - Installation and Administration Guide English (SYNC100620-IGD-En-01)

Загружено:

Авторское право:

Доступные форматы

OpenText™ Tempo™ Box, Content

Installation and Administration Guide

This guide explains the installation and configuration process of

40 Avenue Monterey , Luxembourg, Luxembourg L-2163

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

No Warranties and Limitation of Liability

2 OpenText Tempo Box Prerequisites ...................................... 11

3 Installing OpenText Tempo Box ............................................. 17

4 Installing OpenText Tempo Box (OpenText ECM

5 Upgrading OpenText Tempo Box .......................................... 41

6 Uninstalling OpenText Tempo Box ........................................ 47

7 Configuring OpenText Tempo Box in Content Server ......... 49

7.1 Configuring the Content Service Module ........................................... 49

8 OpenText Tempo Box Client Management ........................... 61

9 OpenText Tempo Box Clients ................................................ 63

10 Synchronizing Standard Users in OpenText Directory

11 Migrating External Users into OpenText Directory

12 Deploying the AppWorks Gateway in a Cluster ................... 79

13 Configuring SSL on Apache Tomcat ..................................... 81

The OpenText Tempo Box platform requires the following components:

Client Server URL

OpenText Tempo Box Authentication Options

For more information on OpenText Directory Services, see OpenText Directory

OpenText Tempo Box User Types

1.1 OpenText Tempo Box Architecture

Figure 1-1: OpenText Tempo Box Architecture

Figure 1-2: External Sharing Flowchart

The prerequisites for OpenText Tempo Box include the following:

Note: OpenText strongly suggests installing the AppWorks Gateway on a

Content Content Tempo AppWork AppWork Desktop OpenText

2.1 Installing and Configuring Apache Tomcat

Note: OpenText strongly suggests installing the AppWorks Gateway on a

To configure Apache Tomcat:

2. Stop the Apache Tomcat service.

3. Navigate to the <Tomcat_Home>\bin folder.

4. Double-click Tomcat8w.exe and click the Java tab.

5. At the bottom of the Java Options list, type -XX:MaxPermSize=512m.

6. In the Maximum memory pool box, type 1024.

8. Navigate to the <Tomcat_Home>\conf folder and open server.xml in a text

9. Locate the HTTP/1.1 connector and add a maxConnections attribute with a

10. Add the maxThreads="2048" attribute.

11. To allow full UTF-8 support, add the useBodyEncodingForURI="true"

13. Comment out or remove the following tag.

14. Save and close this file.

15. Restart the Apache Tomcat service.

2.2 Installing or Updating the Content Server Pulse

1. Do the following to install the Content Server Pulse module:

a. Download the module from the OpenText Knowledge Center (https://

b. Do one of the following:

This places the necessary folder structure in the <Content_Server_Home>/

3. Stop the Content Server services.

4. Extract the downloaded patches to the <Content_Server_Home> folder.

5. Restart the Content Server services.

a. Sign in to the Content Server Administration page as an Admin user.

2.3 Configuring Content Server for OpenText Tempo

1. In the Server Configuration section, click the Configure Security Parameters

2. In the Cookie Authentication Information section, do the following:

• Select the Enable X-Forwarded-For for Client IP mapping check box.

In a clustered environment, this must remain as the actual, single machine.

In a clustered environment, this must remain as the actual, single machine.

5. Click Save Changes.

7. To return proper HTTP status messages, do the following:

a. Open Windows Explorer, navigate to <Content_Server_Home>\config and