Last Wednesday the OpenText Enterprise World took place – the purely digital version. The “real” version, which was supposed to happen last week in Prague, was transformed in light of the COVID19 situation.
I “attended” the show and the official part is just over. Let me give you a short overview of the most important topics, as well as the news around OpenText Documentum.
Mark Barrenechea’s (CIO and CTO of OpenText) key note revolved around two catchwords. One was “Resilient Enterprise”, which covers several aspects. OpenText have acquired several companies that deal with IT security products and have integrated their products into their portfolio. In addition, “resilient” also refers to the ability of companies to continue to function in today’s world with Remote Work – with the help of OpenText products.
At the end of August I was able to attend the BoxWorks conference in San Francisco, subtitled “The Future of Work”. I have to admit, I went there with only a little pre-knowledge and with the history (baggage?) of being a long-time Documentum consultant.
Let me start with a quick summary of the highlights:
Box Feed (available as Beta)
Box feeds allow you to get a stream of activities happening in the shared folders which the user can access. This is a nice collaboration function as are you are seeing the content of your coworkers directly in the stream. This has been missing for a while and Box is now delivering a first iteration with the possibility for you to comment on the documents.
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.
Interesting announcement from Alfresco. They started an aggressive > swap out program against Documentum pushing the fear that Documentum is going away or going south soon. First of all, Alfresco is a really good ECM platform – fme has been an Alfresco partner for many years. There might be good reasons for the one or the other company to decide to change their ECM platform within the next weeks or months, but it should have nothing to do with the OpenText acquisition. Fear has always been a bad advisor. Documentum is not going away any time soon, or why do you think OpenText payed 1,6 billion USD? They have to keep up the flow of maintenance money for quite some years to make the deal work.