HP Exstream vs Opentext Exstream

Approximate Reading Time:  4 Minutes 44 Seconds

Since the time (August 2016), it’s been a common buzz across the Customer Communication Management (CCM) industry on what the acquisition of Exstream from HP to Opentext is bringing up the changes to the CCM industry across the customers, consultants, competitive companies and analysts.,

I am going to write down on how the changes went across pertaining to Exstream since it’s association with HP and Opentext, will talk about how and what are the changes brought down to the industry, will try to understand if the changes are healthier and what is the resulting feedback across the CCM industry on the changes went by, what the pulse people feel across, and future thoughts/take away from Opentext now on.

Here are the release versions on Extream from opentext since the acquisition: – 16.0, 16.1, 16.2,16.3,16.4 and now the latest 16.4 update1 where it was with the version numbers 9, 9.x when the product was engaged with HP. The point here is not to mention the difference in the numbers between 9 and 16.1, it is more on the landscape of the Exstream between 9.x and 16.x. Coming to that lines, the very common perception across the customers and consultants is “oh is it changed from 9.x to 16.x, that means lot of features must have been  added between the versions 9.x to 16.x”. To explain in detail on the profound reasons between 9.x to 16.x is, opentext across the platforms maintains a common major release version, so in order to bring the Exstream to the same level though there are not new features added with Exstream(HP’s) of 9.x, it is rebranded with opentext and released with the version label 16.x. There comes the talk between the classic Exstream(HP’s) and opentext Exstream.

To talk on the high level or on the business model level, the recent mantra was from multi-channel to Omni-channel when Exstream was associated with HP. But soon it has engaged with opentext, the main mantra is engage anywhere, integrate anywhere and deploy anywhere. As the mantra says, it can be said that opentext is changing the landscape of the products from one version to another version from 16.x to 16.4.,

Now, coming to the few salient features: –

Directory Services: –

The Directory Services module called Opentext Directory Services is not only a repository of user and group identity information for Opentext applications, it helps the organizations in saving time and administrative overhead and enables to maintain user information in one directory for use by opentext applications. In essence, Opentext Exstream uses OTDS for a single sign on identity management even either have any other Opentext applications across your enterprise OR if your organization maintains several Enterprise server systems, they can all use the same central user directory by means of Windows server Active Directory (AD) or Lightweight Directory Access Protocol (LDAP).

Exstream as a suite of products

Opentext Exstream now is not a single product that have Exstream Design Manager, Designer and running modules, it is a platform or a suite that comprises the native opentext Customer Communication Management(CCM) tools called Streamserve, Powerdocs and Exstream. With this combination of three products under the banner of Exstream, we can understand on the efficiency of the core product Exstream as a singleton. Keeping aside the individual capabilities of these products aside, Opentext have started leveraging the capabilities of each product along with others. For instance, Exstream as a singleton is very good at the design aspects and is very known for its throughout. But Communications server, a module from CCE(Communications Center Enterprise) formerly Streamserve is having a very good capacity in the orchestration beating down the Extream’s native Command center. So, these combinedly forms a very robustic product by using Exstream’s design and Communication Server’s orchestration by letting to call/configure the Exstream engine with in the Communication Server. Not only that, with this suite of Exstream, Exstream is able to extend the document generation capabilities across different platform. In essence, Salesforce can integrate with Exstream under the product of Powerdocs to generate the correspondence then and there.  SAP is able to do so by using the Streamserve capabilities under the name of Document Presentment of SAP.

Electronic output test simulators: –

With HP Exstream, when a designer wants to test the electronic outputs with related to how the outputs like HTML email or web would appear in other devices by using device preview simulators like Mobile test., The same way if wanted to see how the emails appear with different mail boxes we shall be using something like litmus., But now, with Opentext Exstream, these test facilitators are provided with the installation software package itself.

 

Patrick Kehoe Christian Askland

And needless to say, as the above-mentioned points are mostly on the product technical aspect, it was Patrick Kehoe who was the product manager for Exstream, HP and it is now Christian Askland for Exstream, Opentext.

 


Author Bio

Ragavarao Yenuga has total experience of 10 years.  With 10+ years of experience on Opentext/HP Exstream and 2+ years on Opentext ECM, CCM ecosystem with products of Exstream, Content server, xPresssion

 

 


 

Disclaimer: This disclaimer informs readers that the views, thoughts, and opinions expressed in the text belong solely to the author, and not necessarily to the author’s employer, organization, committee or other group or individual.



2 Comments

Leave a Reply