Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Central HUB and HR Renewal (ESS / MSS via Suite Pagebuilder)

Hi Gurus!

We are currently in the process of upgradring our system landscape - with a SAP Gateway deployed as a Central Hub. The first thing we are going to do is to upgrade our Manager Self Service. Today we use the portal, but in the future we only want to use the Suite Page Builder Application - providing access to Manager Self Service in SAPUI5.  - Later - when the Launchpad is merged with NWBC HTML into a combined launchpad - we might consider this. But until then  -we will skip our portal, and only use the suite page builder.

As of now - we have done some prototyping - on our sandbox environment - where the gateway was installed on the server server (local gateway).

But now that gateway has been deployed as a central hub - i want to be sure that we a on the right track - with our architectural considerations - regarding  deployment and distribution of our users.

As I understand it:

We have to access the suite-page-builder application (The UI5 application) from the Central Hub Gateway - ie this Netweaver Server has its Webserver exposed and serves the html pages to our end users.  And then the masterdata is off course served as ODATA to the UI5 applications - all running on the central hub - and reading data from the backend server (our HR Server).

The Pagebuilder therefore also has to be configured on the central hub system, as well as the pfcg roles, the launchpad (lpd_cust) customizing. 

As a result of this- we will have to create all our users with login details and role assignment on the central hub right?

Is the above approach the right one?

Best regards


Not all apps in above list are UI5 apps. gateway server hosts only UI5 apps.

Webdynpro apps use server side technology, so they have to be in the backend itself.

1 View this answer in context
Not what you were looking for? View more on this topic or Ask a question