Dependency of backend, frontend and SAPUI5 version, core library and launchpad

[markus_deuter]

Hi developers and admins,

I have one question about SAPUI5 and infrastructure.

We started developing first SAPUI5 apps on a ERP ECC6.0 EHP8 as frontend and backend machine. So I started the gateway (750/SP3) and configured the SAP Launchpad on our ABAP AS. First test apps are running very well.

Now I was on a SAP training and came back a little bit confused. I have understood, that we can run apps in principle standalone by using index.html or via launchpad by component.js. Our local SAPUI5 lib on ABAP AS is version 1.36.10.

By using index.html I am able to use different bootstrap core libs, like this:

(1) src="https://sapui5.hana.ondemand.com/resources/sap-ui-core.js"
- or -
(2) src="https://sapui5.hana.ondemand.com/1.42.6/resources/sap-ui-core.js"
- or -
(3) src="http://(our servername):8000/sap/public/bc/ui5_ui5/1/resources/sap-ui-core.js"
- or- 
(4) src="../../resources/sap-ui-core.js"

Of course, only one path can be set by index.html. 🙂

(1) is a direct use of the latest SAPUI5 version

(2) is use of a specific version 1.42.6 from SAP

(3) is using the lib 1.32.10 from our local server

(4) is using the lib relative to SAP Launchpad node

This last version is of course ideal for transporting trough a 3-systems-landscape and was my personal favourite. But then I recognized, that version 1.36.10 is buggy and old. 😞

Then I switched, using the version by src=(2), like described above.

But then I recognized, that If I want to use local SAP Launchpad, I always have to use the local SAPUI5 version, right ?

Or is it possible to redirect SAPUI5 core library loading of our local SAP Launchpad e.g. to a new SAPUI5 lib from internet ?

Another way would be to use a url to index.html within Launchpad, but I think, this prevents to have a common look & feel, which is configured in LPAD by a customer theme, isn't it ? Index.html settings will overwrite LPAD settings, right ?

I'm asking because I want to use a special UI5 component, which is buggy but fixed in a new release. In correspondence with my server administration, I have now the information, that I have to update my SAP ERP to a new patchlevel to get a new SAPUI5 version according to SAP note 2217489 and 2118663.

If this is true, why can I use index.html with a link to the SAP internet sources ?

Can I also set parameter "src" in Components.js ?

Where can I see the dependencies of UI5 version, frontend and backend and patch levels ?

I'm confused ... please explain ... thank you very much.

Best regards,
Markus

[junwu]

when you run in flp, your index.html is no use.

[junwu]

if you run your app with your index.html, you are not running your app in flp. do you understand that?

BTW, lpd_cust is no use anymore.

[markus_deuter]

Yes, you are right, I understand ... I had described this already by saying

>> ....that we can run apps in principle standalone by using index.html or via launchpad by component.js.

> lpd_cust is no use anymore.

What does it mean ? Is there another way to configure ? I have this information from SAP training and from the book "SAP Fiori" & "SAPUI5", Rheinwerk publishing. Keep in mind that I have no HANA engine. I'm still on ECC6.08.

Best regards,
Markus

[markus_deuter]

Hi Jun Wu,

thank you for answering.

> flp is the index.html

Which index.html are you talking about ? Currently I start apps only by using Components.js using transaction LPD_CUST.

Or do you talk about index.html which starts LPD itself ? In my case, this is FioriLaunchpad.html. But there is no bootstrap configuration.

> you have no chance to choose which version to use.

Yes, I agree, but you can use direct URL to index.html of the app in special scenarios, isn't it ? But this should not be a preferred way ...

Best regards

Markus

[junwu]

flp is the index.html, which decide which version of ui5 lib is loaded.

if you run your app in flp, you have no chance to choose which version to use.