The natural decision was to merge both solutions in Exstream 16.2. StreamServe classic and Exstream classic were merged into Exstream 16.2, but they still run there as two separate engines. Therefore, the challenge was to combine these two projects, even after they were both upgraded to Exstream 16.2.
First we updated Exstream application to version 16.2.1 to add new connectivity and transformation features and improve reliability by applying hotfixes. Then we updated StreamServe that the client was using to version 16.2 and adjusted it to new Exstream architecture by using Opentext Directory Services(OTDS) and Communications builder. After that the architecture was ready to use CAS as the central repository of external resources, so we rebuilt former Exstream part of the project to use all images from CAS browser. Finally, we integrated Exstream package into the solution as a Processing Engine.
This allowed us to set up a parallel process of documents generation. So the spool of previously created documents was generated using the existing Exstream package. Meanwhile other documents were generated by means of former StreamServe.
After implementing the new architecture, the client was able to use such new web applications as Workshop and Supervisor to let management interactively control the process of document distribution.