Hi again,

for the last couple of months my guys from SIT GmbH and Harbour Light have been working on an integration solution for Domino E-Mail into Adobe AEM. The Use Case is to enable E-Mail for intranet solutions of our customers, based on Adobe AEM. Our goal was to create an E-Mail Framework that would be extendible to other platforms (talking 'bout you, Exchange!) and that would be able to utilize a flexible UI to get adapted to the look and feel of our customers implementations easily.
And - we have done just that. The next screenshots show you a lightweight E-Mail Client that can be customized to any functional needs and esthetical requirements in a specific customer situation.

This Screenshot shows the inbox and the folder structure we have implemented.

Image:The voyage of IMPRISIS continues - IMPRISIS DA integrates Domino Mail with Adobe AEM

We also have fulltext search working:

Image:The voyage of IMPRISIS continues - IMPRISIS DA integrates Domino Mail with Adobe AEM

And finally, this is what an email can look like using IMPRISIS DA.

Image:The voyage of IMPRISIS continues - IMPRISIS DA integrates Domino Mail with Adobe AEM

In these Screen shots, we use a bootstrap theme as our basis for the UI but this can be changed to whatever framework is necessary. We deliver a JavaScript API that exposes the high-level functionality of the backend email services to the AEM components so any AEM component developer can alter the components or can create his/her own ones based on our APIs. The API also abstracts Single Sign On (SSO) headaches from the component developer as SSO can be configured centrally on an AEM instance using our IMPRISIS SSO Components and if needed our Secure Token Service IMPRISIS STS.

Right now, we are in beta with the E-Mail Services of IMPRISIS DA, next are Calendaring Services. Stay tuned !

Links & Resources:

[1] SIT GmbH
[2] Harbour Light Software Development Ltd.
Heiko Voigt   |   5 May 2015 14:15:00   |    Adobe  AEM  Domino  IMPRISIS    |  
  |   Next Document   |   Previous Document

Discussion for this entry is now closed.

Comments (0)

No Comments Found