Liferay POC (draft)

1.

Liferay POC (draft)
28 June 2023
v 0.3
Confidential | Authorized

2.

POC
Demonstrate that we can enable quick integration of disparate portals and experiences with the goal of
enabling fast recombination of services that comprise our evolving services portfolio.
OSS, T0/T1/T2 uplifts, MS, A&PS, GreenLake, Partners
Demonstrate that Liferay can be used to provide a thin integration layer (e.g. landing page mash-ups) for
the new portal.
Demonstrate that a reverse-proxy pattern could be used for integrations beyond the landing page.
Identify risks and areas for further investigation
TBD: customer representation, UX consistency, performance, SSO, maintainability, CDP compatibility
4 week timebox
Confidential | Authorized
2

3.

POC Landing Page
What type of search
experience would be
useful for POC?
reverse proxy
domain
Authenticated
page
liferay-poc.hpe.com/services
HPESC header
Lightning Out
Component?
CEP
Salesforce
SA20
Card links to
DCM in HPESC?
PRP widget?
Out of scope for
POC
SNow widget?
Landing Page
HPESC backend
HOC
PRP
Other Portals?
Confidential | Authorized
3

4.

POC integration
Salesforce (CEP) Pages:
internal.support.hpe.com
support.hpe.com
User Agent (Browser)
Home Page
Search Page
Case Mgmt Pages
Header/Footer
Etc
IAM-Facing
Portal
Apache
DWF
Proxy
UID-Facing
Portal
Apache
Liferay Pages:
Public landing page
Authenticated landing page
SA2.0 Pages:
Portal Gateway
Doc Display
SWD Detail
Service Credits
Etc
Feature Apps
Confidential | Authorized
4

5.

POC Scope
Is
Is Not
Creation of landing page in Liferay that incorporates widgets from existing portals:
HPESC/CEP, HPESC/SA20, PRP (?), others?
Like for like replacement of functionality in SF Communities UI with equivalent functionality in
Liferay-hosted UI.
SSO integration and demonstration that identity tokens can be passed from Liferay to other
portals.
User onboarding flow, email verification flow, Single Logout
Reverse proxy integration to expose native functionality from other portals: HPESC, PRP,
others
Re-implementation of existing HPESC pages
Experimentation with Lightning Out in Liferay pages, investigation of OOTB Liferay-Salesforce
plug-ins
Guarantee that Lightning Out will go GA on timeline that meets our needs
Identification of changes needed in HPESC to enable Liferay (APIs, session management, SSO,
request routing, etc.)
Changes to business logic or data models in SFDC or SA2.0, except where needed to support
the new landing pages (e.g. new APIs for remote data access)
Intended to identify risks or areas (functional and non-functional) that may cause problems
during implementation or production
Solving problems that are identified
Intended to contribute to informed decision making for integrated PSE, HPESC, Services
Experience, and Partner Experience technology choices and design
Investigation of other alternatives to Liferay. Have Adam and Arnaud been looking at other
options?
Performance comparison with communities-based implementation on a few key use cases
(login? case list? SW search? Doc display?)
Performance or scalability testing
Understand Liferay deployment models (on-prem, SaaS) and implications for HA, DR, CDP,
SEL, dev/test environments, etc.
Integration with SMART pipelines
Addressing the problem of HPE employee licenses for Salesforce CEP
Confidential | Authorized
5

6.

Key POC activities / deliverables
Implementation of authenticated and public Liferay landing pages combining elements from HPESC/CEP
and HPESC/SA20:
HPESC H/F, cases-awaiting-action widget (?), Search widget (?).
At least one Lightning Out component and native Grommet component on page
Link-outs from Liferay landing pages to HPESC functionality: DCM, Doc Display, etc.
Do we want to include other portals: PRP, SNow/HOC, OpsRamp?
Integration of IAM login flow and SSO for Liferay landing pages and portal integrations
Common domain for Liferay and HPESC pages
Identification of components with non-standard relationships to Salesforce or HPESC (VA, DI
Dashboards), and investigation of their integration into Liferay.
Report out
Demo
Findings
Recommendation
Confidential | Authorized
6

7.

Resources and prioritization
1.
2.
3.
4.
Identify the people to be involved
Agree when POC will kick off and end
Define specific functionality and pages for POC implementation
Determine if any commitments (analysis or dev) need to be re-prioritized
Confidential | Authorized
7

8.

Backup
Confidential | Authorized
2023 Hewlett Packard Enterprise Development LP

9.

GLCP considerations
Not part of POC, but we probably need to understand how Liferay would fit GLCP plans.
-aaS support experience in GLCP: we assume UX must be similar across GLCP and HPESC.
Have been looking at Lightning Everywhere.
Can Liferay support LWC widgets? Can Liferay export UI widgets, e.g. into GLCP?
Liferay and MSP experience? Think through PRP vs. GLCP MSP experiences.
Confidential | Authorized
9