real time web analytics

Components Changes in StreamServe vs OpenText Exstream (Server-based) vs OpenText Exstream (Cloud Native)

OpenText Communications (formerly known as OpenText Exstream, StreamServe, HP Exstream, Exstream Software) has been on the market for more than 25 years. Throughout this time, it has continuously evolved to meet changing market demands and technological advancements. OpenText Communications (Exstream) Cloud Native is the name of the latest release. You can read more about it in our previous blog post. 

Overall, both in terms of components and architecture, this containerized release has seen significant changes compared to StreamServe and OpenText Exstream (server-based). This blog post provides an overview of the key component changes over the years.

Components Changes in StreamServe vs OpenText Exstream (server-based) vs OpenText Exstream (cloud native)

The above table outlines the evolution of components between StreamServe 5.6.2, OpenText Exstream (Server-based), and OpenText Communications, formerly Exstream, (Cloud Native), highlighting key changes in functionality and toolsets as the platforms transitioned to more modern, cloud-oriented architectures.

 

Templates: 

  • StreamServe 5.6.2: Relied on PageOut and StoryTeller for template creation.
  • Exstream (Server-based): Maintains compatibility with StreamServe’s  PageOut and StoryTeller, and Exstream Classics’s Exstream Designer and Design Manager, while introducing modern thin-client tools like Communications Designer. Please note: PageOut support is limited. Existing applications can be updated, but new ones can’t be created.
  • Exstream (Cloud Native): Doesn’t support any of the StreamServe-related tools, and support focuses on thin-client tools, like Communications Designer for enhanced design and flexibility, while still supporting classic desktop tools, like Exstream Designer/Design Manager. 

 

Engine

  • StreamServe 5.6.2: Powered by Communications Server.
  • Exstream (Server-based): Incorporates StreamServe’s Communication Server and Exstream Engine for expanded capabilities.
  • Exstream (Cloud Native): Operates solely on the Exstream Engine, optimized for cloud environments.

 

Version Control

  • StreamServe 5.6.2: Utilized external version control systems (e.g., CVS, SVN, etc.) for version control.
  • Exstream (Server-based): Upgraded to tools like Workshop and Common Asset Service (CAS) for improved asset management.
  • Exstream (Cloud Native): Features Design Asset Service (DAS) for robust cloud-based version control and design management.

 

Orchestration, Connectivity, and Delivery

  • StreamServe 5.6.2: Utilized the Communications Builder
  • Exstream (Server-based): Supported StreamServe’s `Communications Builder` and Exstream Classic’s `Communications Orchestrator`.
  • Exstream (Cloud Native): Streamlined into a unified `Orchestration` module for seamless connectivity and delivery.

 

Authoring

  • StreamServe 5.6.2: used Composition Center for on-demand letter development.
  • Exstream (Server-based): StreamServe Composition Center was replaced by StoryBoard. Content Author was added for the Exstream Classic engine.
  • Exstream (Cloud Native): Standardizes on Content Author as the primary on-demand letter development tool.

 

Interactive

  • StreamServe 5.6.2: Featured `AdHoc` for interactive document editing.
  • Exstream (Server-based): StreamServe’s Ad-hoc was upgraded to ReTouch. Empower Editor was added for the Exstream Classic engine.
  • Exstream (Cloud Native): Focuses exclusively on Empower Editor for interactive editing and collaboration.

 

Curious to learn more?

This blog post only provides a high-level overview. If you are curious to learn more, make sure to subscribe to our blog post as we will be posting more content related to this topic. Feel free to reach out to us for a free-of-charge consultation on recent product component changes and how they may impact your organization. 

 

Join OpenText professionals & get inside knowledge every week

Subscribe to our blog