What is the data transfer latency?

What is... This is a short answer and question category.Explanation: The BAM Server collects events from the audit trail database that occurred 30 seconds in the past. This delay ensures that late arriving audit trail events are collected.

Function: On high load environments where Process Engine handles large volumes of workflows simultaneourly (> 100 concurrent WF events) the Content Server takes more than some second to complete the transaction.
Default latency is 30 second. On high load environments the latency up to 300 seconds and more.
–higher latency = longer delay for update the report data in the dashboard–

Relevant products: Business Activity Monitor, Content Server, xCP, Process Engine

additional information:server step size

What is... This is a short answer and question category.What is the GAP-filler?

Explanation: The gap-filler-feature is part of the Content Server and stores data between the Content Server and the Business Activity Monitor (BAM) database.

Function: The Content Server continuously writes audited data into the audit trail table regardless of whether the Business Acitvity Monitor Server monitors the data.
If the BAM database goes offline the gap-filler-feature stores the data and fills the backlogged data into the BAM Server after a preconfigured period.
Default period is 5 Minutes. There is no numeric imitation to the period time accept the BAM memory size.

Relevant products: Business Activity Monitor, Content Server, xCP

Understanding Accelerated Content Service (ACS)

The Accelerated Content Services is a lightweight server that handles read and write content operations for web‑based client applications (Webtop, Taskspace or D2). ACS server is not available to handle content read and write requests for users on Desktop client applications.The ACS server runs in the Java method server.
By default ACS caching is disabled (Distributed Configuration Guide 6.5 ). To enables ACS caching set the acs.cache.enabled property to true.

There is one ACS server for each Content Server host installation. It communicates with one Content Server for each repository in the host installation. The ACS server is installed automatically when the first repository on the installation is configured.
If additional repositories are added to the installation, the ACS server’s configuration information is updated so that the server can communicate with the primary Content Server for the new repository.

These are the acs.properties file and acs config objects. Each ACS server has one acs.properties file and at least one acs config object. The file is created when the ACS server is installed. The acs config object is created when a repository is configured. The acs config object resides in a repository. Each repository served by an ACS server must have an acs config object for that ACS server. ACS config objects can be modified only through Documentum Administrator, located here Administration -> Distributed Content Configuration -> ACS Servers.

An ACS server cannot access content in other types of storage areas. Nor can it directly access encrypted or compressed content or virtual documents or XML documents. If an ACS server receives a request for a document that it cannot access, the request is forwarded to its associated Content Server, which will service the request and send the result back to the ACS.

ACS servers by default are configured in push mode for communications with a Documentum Message Services (DMS*1) server. They cannot be run in pull mode.
A Branch Office Caching Services (BOCS) server can communicate with a DMS server in either push or pull mode.

UCF*2 provides support for distributed content by providing integration with ACS and BOCS. Both these technologies providen performance optimizations when content is distributed across different repositories in distant network locations.


*1A DMS server is a message routing server. It runs in the application server. Although part of the Content Server product, DMS is packaged separately, with its own installer and is installed on a host that is different from the Content Server host. It is not installed with Content Server.

*2 Unified Client Facilities (UCF) is a proprietary, lightweight client-server application used for managing content transfer between Documentum repositories and UCF-enabled clients. UCF is a remote content transfer application, and is available in the productivity layer in Java (remote mode only) and .NET.

References

  • EMC® Documentum® Documentum Administrator, Version 6.5, User Guide
  • EMC® Documentum® Content Server, Version 6.5, Distributed Configuration Guide
  • EMC® Documentum® Documentum Foundation Services, Version 6.5 SP2, Development Guide

short tutorial: use adaptors in Forms Builder

xCP 1.x compatible

 Example: the last five active users

This list was dynamically created with the data source adaptor for the application Forms Builder.

First you must create a global or template adaptor. Use the data source adaptor to create a DQL or SQL – Query and include dynamical information from external data source.

The following query returns the last logged in users

select user_name, last_login_utc_time  from dm_user WHERE user_os_name not like 'dm%' AND user_name = SUBSTR( default_folder,2,20)ORDER BY last_login_utc_time DESC ENABLE(RETURN_TOP 5)

ReadOnlyTable

Make sure that you are working in the  “Design view” and insert a ReadOnlyTable. The table has a lot of properties, please label the table and select the “Special” tab.

Select your individual adaptor as external data source.

The individual adapter named “hpe_top5_users” and is a global adapter, available for all form templates.

Remember: the output data was created as an indivudual complex type. The output type called “data” and the group named “item”. The individual items are  the result values of the query: user_name and last_login_utc_time.

The output data is sortable. You can relabel the columns and set the visibility and the width of the rows.

ListBox

The individual adapter named “hpe_top5_users” and is a global adapter, available for all form templates.

The ListBox functionality is very similar to the ReadOnlyTable. The adaptor must be specified for every individual ListBox in the “Data & Storage” tab.

The login-time as unique value is not recommend, because it is not an identifier. The query should be extended with one unique id, for example the r_object_id.

In the ListBox only one value is available. Please select one of the result values of the query.

 

This figure displays the special tab for the ListBox property. The adaptor will be exectuted when the form initializes.