Blue Fish Development Group
701 Brazos St. #700
Austin, TX 78701
(512) 469-9300
Application monitoring should not only confirm that system components are running, but should make sure they are functioning properly. This paper discusses a strategy we employed for a complex Documentum based system.
Whether you’re a web developer or an administrator, understanding the publishing jobs in Documentum can help you create, automate, and refine the best features of your web content management solution. This article provides an introduction to the jobs used in the Documentum web publishing environment: what they are, recommended settings, and troubleshooting tips for some of the more common errors.
Learn to configure and customize Documentum’s email facilities to meet the needs of your organization.
Frequently, when setting up a distributed environment, questions arise about how Documentum handles the integrity of the data that is Replicated or Federated. For example, your system may rely on associations between objects. These associations can take many forms, dm_relations, attributes of ID datatype, locations, and attribute pointers for example. The question is, will these associations still be valid in all Docbases within your environment. This article will take you through several mini-scenarios of replication and describe how Documentum handles each scenario.
Documentum applications normally comprise of more components than just the Content Server and based on the needs of the application failover capability may be needed for all the components. This article, the second of a two part series, discusses the options for implementing failover in different components of a Documentum application. The first part of this series discussed how to provide failover capability for the Content Server using Microsoft Cluster service.
Documentum implementations frequently have a requirement to provide access to the documents from multiple distributed physical locations. In addition to their different physical location, these locations may vary in terms of: the types of actions they perform, their frequency of access, their network connectivity, the availability of support, and countless other potential issues.
This document attempts to outline the options available to someone who is developing a system with remote access requirements. In addition, it will provide a high-level framework for determining the architecture most appropriate for the system being developed.
Failover is the ability of a system to manage severe failures in a component that would normally lead to system shutdown by switching to an alternate standby component. This article, the first part of a two part series that discusses how to provide failover support at the eContent server layer using Microsoft Cluster Service. The second part of this series discusses the options available for providing failover support at each layer of a Documentum Solution.
This article discusses several approaches to updating the Documentum installation owner of a 5.2 Windows 2000 Docbase.
Learn to configure and use the embedded Verity Full Text Engine within Documentum.
The Documentum Content Server provides support for auditing events of interest which occur to objects in the Docbase and to application-specific entities. This article explores the features of the audit facility, how to configure it, and how to work around some of the problems using it with DFC.