Issue : Fiori Launchpad URL

[Former Member]

Hi All,

Kindly help me to resolve the below issue :

http://host:port/8000/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html

On accessing the above URL with the credentials , it results with error in the below screen shot.

However, if I mention the Client details as below , say Client parameter, it opens-up.

http://host:port/8000/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=120

Let me know where I have to maintain the Default client for each system.

Regards,

Nagaraj

[nageshcaparthy · Accepted solution]

Hi Nagraj,

Can you try to check if the client is maintained in the SICF path of Fiori launchpad. If not try to maintain and then test the services.

Regards,

Nagesh

[Former Member · Accepted solution]

Hi Nagesh,

I have checked but I didn't get the exact part where to be maintained.

Can you please suggest exactly where the Default client has to be maintained in SICF for Fiori Launchpad ?

Regards,

Nagaraj

[former_member182967 · Accepted solution]

Hi Niagara,

Please set login/system_client = 120 in SAP DEFAULT profile and restart AP to take into effect.

Then retry.

Regards,

Ning

[Former Member · Accepted solution]

Hi Ning ,

In Quality System, they have maintained the said parameter with exact client.

But still same issue persists, only after adding the parameter sap-client=300 in URL it opens-up.

Regards,

Nagaraj

[former_member182967 · Accepted solution]

Hi Nagraj,

Perform the following things:

1. Login to the ABAP front-end server.
2. Access the activity using the following navigation options: Transaction Code SICF
3. Choose Execute. The Maintain Service window displays.
4. Double - click on the node /sap/bc/ui5_ui5/ui2/ushell.
5. Choose the Error Pages Tab.
6. Choose System Logon and then choose the Configuration button beside.
7. Select Client in Select Display area and retry.

Regards,

Ning

[Former Member · Accepted solution]

Hi Ning,

Thanks for your kind reply, I have noticed that in Quality, it is 120 ( Development Client Number ) and chosen as " Define Service Specific settings ".

Actually, Quality system client number is " 300 ".

So I need suggestion from you that, is there any option to capture in Transport Request to maintain the Client or have to open the Quality System and change to 300 or choose " Use Global Settings ".

If we prefer " Use Global Settings " , by default they maintained in RZ10 , client number as 300 in Default Profile.

Regards,

Nagaraj

[former_member182967 · Accepted solution]

Hi Nagraj,

This can not be included into TR, as I know.

Depend on you, I prefer to set default client in DEFAULT.PFL.

A kindly remind: please consider to use Fiori Launchpad with cache buster (Cache Buster for SAP Fiori - User Interface Add-On for SAP NetWeaver - SAP Library)

If the problem is solved now, please kindly close this thread.

Regards,

Ning

[Former Member · Accepted solution]

Hi Ning,

Our BASIS team suggests there is some restriction in opening the client QAS.

So he suggests to alternate way, I'm looking for the same.

Once the issue is closed, let you know.

Regards,

Nagaraj

[Former Member · Accepted solution]

Hi,

I hope this helps!

The default client is defined in the service maintenance.

Transaction /IWFND/MAINT_SERVICE on the gateway system.

Here you'll find the service model that is used in a Fiori application.

When you click this, you'll find a system alias linked to this service (bottom right of screen), this alias is linked to an RFC (doubble click alias) that is defined in transaction SM59. Here you'll find the client in the logon & security tab page.

(If you only have one Gateway server for multiple backend system (DEV, QAS, PRD) you can use host routing to link a different system alias.)

Grant points if useful.

Jonathan

[Former Member · Accepted solution]

Hi Jonathan,

Thanks for your reply.

There is no client specified in Logon & Security tab as shown below.

However, I'm trying in other way, will keep posting once it is done by EOD.

Regards,

Nagaraj

[Former Member · Accepted solution]

That is because you are using an embeded gateway if i'm not mistaken.

If no client is specified in the system it will take the default client of the backend system.

You can either add the client in the RFC of the screeenshot, or you can use the URL parameter ?sap-client=200 for example.

Normally this is how you use a gateway:

External -> Webdispatcher depending on port used to access the webdispatcher -> development and acceptance hub or production hub.

then depending on the backend system you want to reach, you access the development/acceptance hub with a different host.

This host is then linked in the service maintenance with a system alias that points to either the development backend or the acceptance backend.

Please note that is this setup the gateway server is a stand alone instance and not embeded in the backend.

If you have an embeded gateway you simply have to use a different URL to target the acceptance backend system.

E1 Port 1 => WD1 => HUB Dev Host AA => DEV

E1 Port 2 => WD1 => HUB Dev Host BB => ACC

E1 Port 3 => WD1 => HUB Prod => PRD

This is the way it should be setup normally .

Embeded gateway

E1 Port 1 => Gateway component in DEV with destination local (RFC NONE)

E1 Port 2 => Gateway component in ACC with destination local (RFC NONE)

E1 Port 3 => Gateway component in PRD with destination local (RFC NONE)

[karthikarjun]

Hi Nagaraj- Is the Fiori component install in your GW system? If yes check the client number.

Regards,

Karthik A

[Former Member]

Hi Karthik ,

Thanks for your kind attention. Issue has been resolved.

Regards,

Nagaraj

[saqib_dastgeer2]

Hi Nagaraj

Kindly let us know , how you resolve this issue

[Former Member]

Hi Saqib,

As  per the below procedure suggested by Mr.Ning Tong...

1. Login to the ABAP front-end server.
2. Access the activity using the following navigation options: Transaction Code SICF
3. Choose Execute. The Maintain Service window displays.
4. Double - click on the node /sap/bc/ui5_ui5/ui2/ushell.
5. Choose the Error Pages Tab.
6. Choose System Logon and then choose the Configuration button beside.
7. Select Client in Select Display area and retry.

Regards,

Nagaraj