Content Manager Enterprise Studio 25.1 Enterprise Studio

# Adding a Workgroup Server

1. Ensure that the new workgroup server has the required Content Manager software installed
2. Right click Workgroup Servers and then click New Workgroup Server.

   The New Content Manager Workgroup Server dialog box appears.

   - Server name - type or select the computer hosting the workgroup server
   - TCP
     - Port - select the port to use for TCP communication, 1137 by default
     - IP Address - the server network interface to use for TCP binding. The default value is all available interfaces.
   - HTTP
     - Port - select the port to use for HTTP communication, 80 by default
     - IP Address - the server network interface to use for HTTP binding. The default value is all available interfaces.
   - HTTPS
     - Port - select the port to use for HTTPS communication, 443 by default
     - Certificate - select the server certificate to use for HTTPS communication. From the drop-down list, select from the certificates installed in the Personal certificate store of the Local Computer account. You will need to import the your server certificate to this store to make it available in this list.
     - IP Address - the server network interface to use for HTTPS binding. The default value is all available interfaces.

   NOTE: Content Manager supports having two different login names for the same Content Manager user. This allows the presentation of one set of credentials, e.g. on a remotely located PC, based on Active Directory Federated Services (ADFS), then use another set of credentials when connecting from an office PC that is logged into a trusted organization domain.

   NOTE: If a reverse HTTP proxy is deployed between the client and the Workgroup Server, it is important to enable persistent sessions (also known as “sticky sessions”) on the reverse proxy. This means that once an HTTP session is initiated between the client and a back-end server, subsequent HTTP messages from the client are routed to the same back-end server.

   NOTE: For customers deploying Active Directory Federation Services Web Application Proxy (AD FS WAP) as a reverse proxy between the client and the Workgroup Server, Content Manager supports both AD FS WAP pre-authentication and AD FS WAP pass-through authentication. To use AD FS WAP pre-authentication, the pre-authentication type must be set to Web and MSOFBA, when publishing the Content Manager service in the AD FS WAP management tool.

   - Can process events - select for this workgroup server to also process events as described in Processors and events.

     See also Configuring event processing.

   - Publish available datasets to clients - on by default - available datasets will be published to clients only after they have authenticated. Users that have not authenticated will not be able to get a list of all available datasets on the Workgroup Server. If this option is disabled, when a user attempts to open a new dataset they will be warned that the dataset list is unavailable for this Workgroup Server.
   - Use HTTPS to deploy to this server - select this option to allow Content Manager Enterprise Studio to deploy the configuration to a Workgroup Server that is not domain-joined, for example, a Containerized Workgroup Server.
   - Redirect client database requests to Content Manager Workgroup Server - optional - computer hosting a workgroup server on the same LAN as the database.

     TIP: When running Content Manager over a wide area network (WAN), this option enables the client to communicate directly to a local workgroup server to add or extract documents and a remote workgroup server for searching.

     Administrators should use this option if it significantly improves performance when searching from clients. As there are many factors influencing performance over a network, this may not work for every organization.

   - Use a cache for documents accessed via this server - select this option to cache the documents that are actively requested by a client connecting to this Workgroup Server.

     If this option is not selected, the Workgroup Server will write the document to the cache, but delete it after approximately 30 minutes.

     It is recommended that you use caching on any Workgroup Server that is on a different computer from the central store.

     - Set a maximum size for the document cache (Megabytes) - set the maximum size limit for the document cache. The maximum size that can be set here is 2000000000MB

       A separate Workgroup Server process checks for documents that can be deleted from the cache. This removes documents from the cache if they no longer exist in the central document store.

       Even with this purge process, there is still a chance that the size limit is reached.

       In this case, the Workgroup Server will check for the documents in the cache that have not been accessed the longest and deletes enough so that the cache is within the size limit.

   - SharePoint server farm - you can allocate the process SharePoint Integration only to workgroup servers that are part of a SharePoint Server farm.

     See Configuring event processing.

     - Not On A Sharepoint Farm - this server is not part of a SharePoint Server farm
     - SharePoint Farm <number> - the SharePoint Server farm this Workgroup Server is a part of
3. Click OK.

Related information

Copyright 2008-2025 Open Text
Version 25.1 | Last updated October 2024
Contact

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to hprmdocumentation@microfocus.com.

We appreciate your feedback!

Product: Content Manager Enterprise Studio 25.1

Topic Title: Adding a Workgroup Server