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 ServicesA 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)
Business Logic ServicesIf 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.
ConclusionDo 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