The old OpenText Documentum Webtop versions (older than 6.8.2) were using Content Transfer Applet, and clients have been complaining about the Content Transfer Applet for many years due to issues supporting Java versions on client machines as well as the inherent security problems with Applets. While the Webtop 6.8.2 version and higher removes the Applet, users are still required to install a browser extension as well as a native exe installation that utilizes Java.
This technical blog describes the installation steps and troubleshooting guide for Documentum Webtop Native Client plugin 16.4.
It is the first Wednesday of November, a special day because today is our team lunch. Recently I have been working on a project to introduce an enterprise content management system to manage plant-specific documents. A multitude of installation, configuration and implementation tasks have to be done.
In this blog post I would like to express my personal experiences about Captiva from OpenText. It happens very often that neither users nor IT specialists know exactly what is behind this “software tool”.
I have also heard the sentence “It’s just scanning” more often and exactly for this reason, it is time to illuminate the mystery Captiva Capture. In simple words I try in this article to tell something about the software itself and about the daily tasks and problems. Maybe it is then comprehensible, why I find this area with the activities connected with it insanely exciting and that thereby more hides itself, than only scanning.
The use of public cloud platforms such as Amazon Web Services (AWS) for the implementation of OpenText Documentum-based ECM environments is often viewed critically. There is quite a list of points in favour of its use. In fact, it depends on the scope of the environment to be built, what data is processed there and how deeply AWS is to be integrated into the own network. This blog post should help to find answers to these questions and to show a first basic environment on the AWS platform.
OpenText Documentum is a full-fledged and mature server-based Document Management System which is accepted e.g. by the FDA and therefore widespread in pharmaceutical companies.
Compared with cloud computing technologies that are very strong in providing elastic (scalable) services OpenText Documentum products could be regarded as inflexible and monolithic / layered applications. Although they seem to be the exact opposite of the flexible Microservice architecture approach used for cloud native application design, there are ways to combine OpenText Documentum products with cloud computing technologies. read more
From 1997 to 2007 I was employed at Documentum in Munich and was responsible for the technical sales issues for Central & Eastern Europe, Middle East and South Africa. I witnessed the birth of the fme – Documentum partnership in 1998 at close quarters. With fme Documentum had found the ideal partner to realize projects in Germany. Since then I have always followed the development and international growth of fme. That’s why I’m all the more pleased I joined the fme in 2015 and am now responsible for content management and cloud business as a board member of fme AG.
At fme we are proud that this year marks the 20th anniversary of our partnership with Documentum, now part of OpenText. It is a success story with countless successful client projects, a world renowned product that has been certified for more than 10 years, extensive platform and industry-specific process know-how and a great team of highly specialized employees.
This blog article looks at OpenText’s Documentum REST API and provides insight into its technology, basic functionality and extensibility capabilities. Here I report from my own experiences and I am happy if I can help other “techies” like me a little with it 😉
What is the “Documentum Rest API”?
In principle, the term Documentum REST API refers to a web interface introduced with Documentum 7 that allows access to objects and functions of OpenText Documentum. This is based on Spring-Boot, is delivered as a WAR file and must be installed on an application server – e.g. Apache Tomcat. This interface can be used to write customized clients, apps, or plug-ins of other systems.