Why OpenText Documentum products and Cloud Computing are complementary

Why OpenText Documentum products and Cloud Computing are complementary!

by Jörg Friedrich |
Aug 17, 2018 |
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. Here are some examples to give you an idea of how to achieve more flexibility by breaking either the OpenText Documentum base installation or business logic into smaller services.

Infrastructure Services

A classic OpenText Documentum Content Server installation could be split into four services / Linux containers:
  • The Docbroker
  • The repository services
  • The Java Method Server (serverapps.ear)
  • The Accelerated Content Services (acs.ear)
It is obvious that the Docbroker does not have to deal with much traffic and does not need any load balancing. Thus one or two instances at most could be sufficient (complemented with according health check monitoring) to provide a robust fail over. For the repository services, the Java Method Server and the Accelerated Content Services, two instances each are sufficient to provide a quite robust service. However, at some point you might want to perform a data migration into your repository with many documents for example. In this situation, you might think of hiring our highly skilled content migration team. During the migration period, especially with systems utilizing the Java Method Server heavily, exactly this service would become a bottleneck. All other server components would be able to handle all migration tasks. And here things become interesting: If you had used the service architecture as described earlier and you had been utilizing an orchestration tool, you would have been able to request two additional Java Method Server instances on-demand within minutes. The orchestration tool automatically creates two more instances, which are automatically proxied via a service end point. All upcoming migration requests are then spread over all existing instances, providing a good migration experience. Once the migration is finished, you can scale down the number of instances.

Business Logic Services

If you are using OpenText Documentum D2 e.g. and have potentially “heavyweight” logical services like watermarking, you can create real services (Microservices) and connect them to service discovery tools with load balancing/fail over aware clients (e.g. the Netflix OSS – Eureka, Ribbon, Hystrix). With this option, the watermarking service becomes scalable and flexible for any upcoming future needs and can be placed or moved to dedicated computing resources as needed. If at a certain point this service is identified as a bottleneck, you may instruct your orchestration tool to create additional instances of the same service. If there is a one-time event like a submission to an authority, you may also instruct your orchestration tool to create additional instances of the same service, but you are able to downscale the service after the specific event has finished in order to efficiently use your hardware resources.

Conclusion

Do not fear to use the best of both worlds! We will support you in combining both technologies and providing best results to you!
  • Analyze your existing OpenText Documentum infrastructure architecture
  • Analyze your existing OpenText Documentum software architecture
  • Create a roadmap with you on how to make your OpenText Documentum stack cloud computing-ready
  • Create best practices on how to create future components inside your existing OpenText Documentum stack to make them elastic and to comply with the concepts of cloud computing
  • Move application logic (where applicable) into elastic Microservices
We are looking forward to sharing our expertise with you!

More from this category

AWS Sumerian as Quality Training – Digital Learning in the Enterprise

Digital learning is an exciting and at the same time very dynamic area where technologies are constantly evolving. There is an increasing need for companies to integrate this new way of learning...

My journey through Life Sciences

Within these years of learning, I was established in the company’s IT department and made some excursions to purchasing, sales and production control departments. I was taught that IT links...

Keep Talking: Why Communication Is the Key to a Successful Project

When an investment in IT solutions doesn’t live up to expectations, this can often be attributed to lack of effective communications and the establishment of a formalized communication plan. If the...

Veeva R&D Summit Puts Focus on Innovation and Best Practices

As a Veeva Migration Services partner, fme was a key sponsor of the summit and we were excited to be part of this growing industry event. During both days of the summit, sessions were separated into...

Updates from the OpenText Enterprise World Conference in Toronto

On top of that, there are additional challenges as a result of mergers and acquisitions. Once they come together, companies are forced to consolidate documents and data from different systems and...

A master plan: why master data management is key to successful migration projects

»Master data management is the method that an organization uses to define and manage its critical data in order to achieve a single source of truth across the enterprise.« The importance of master...

Checklist for a Successful OpenText Documentum D2 Implementation

After all, the sheer volume of content can be overwhelming and the potential to change business processes that developed over time can be a contentious point in any organization. This planning...

Lost in translation: Why complex EDMS projects often miss the mark

Typically, teams or committees are created across different business units and geographies, each with different goals and expectations. The result can be a budget blow-out, failure to harmonize on...

Quality in migration projects – “a life necessity” in the Life Sciences industry: Interview with Markus Schneider

Jens Dahl: Markus, you have been working in the area of ECM in the Life Science and Pharmaceutical industry for more than 20 years. You know many platforms, applications, client environments and of...

Getting an Edge with Your Box Migration So It’s Efficient, Fast and Focused

It’s all about how to transition data fast and securely with minimal downtime or disruption to the organization and employees. But that’s much easier said than done in most environments – especially...