In my previous blog (Fiori: technical installation and configuration of one app from A – Z) I was wondering how I could setup SAP FIORI apps from scratch.

I described all the technical steps how to come to one working App.

I installed SAP and added patches and add-ons and performed the configuration manually.

This helped me understand all the technical steps that are needed and gave me an indication of the timelines.

Now I want to find out how this would go if I take the complete preconfigured solution that is available in the CAL (Cloud Appliance Library).

This solution on the CAL is the perfect way to test a solution quickly.

It has the advantage that you do not have to install it manually yourself.

Of course this preconfigured out of the box version has a big disadvantage: you cannot make the basic choices yourself (hostname, SID, instance number, version/patchlevel).

But for me this test with the SAP CAL is just a learning experience to see how the procedure is done and how fast I can deploy a working solution via CAL.

Prerequisites

Your company has to have a test and demo license

You have to register your S-user account at the CAL (https://cal.sap.com/)

You have to have an AWS account

Fortunately my company has such a test and demo license.

And I already have an AWS account because I already perform SAP test installations there.

To give an idea: the SAP ECC system I used for the previous Fiori system had 7.5 GB RAM and 600 GB storage and costed around 50 dollar per month (I turn it off when I did not use it to save costs).

Initial setup

Steps to perform in CAL

Go to the CAL start page at: https://cal.sap.com/

You see that there are solutions that are free and there are solutions that you have to buy.

CAL start.JPG

Search for Fiori in the right corner.

One Solution is available:

CAL Fiori.JPG

When we Click in the “Create Instance”, the process starts.

In step 1 the name is given and you can choose the AWS region in which the new systems will be deployed.

step1.JPG

In step 2 the size of the AWS instances can be chosen.

You see that two SAP systems will be created: one SAP Netweaver Gateway 2.0 and one ERP 6 Ehp6 system.

At the bottom you can see that the port numbers are predefined and cannot be changed.

Step2.JPG

In step 3 you give the master password.

step3.JPG

In step 4 we can configure the systems to be removed automatically after a number of days.

This might be good for a course or just to make sure the costs will not get to high.

In this case I choose to set it to manual to make sure it will not be removed automatically.

Step4.JPG

In step 5 you can calculate the estimate costs.

With the instance types I choose (the smallest) I see that it will costs 1.53 dollar per hour.

I will make sure I shutdown the systems when I do not use them.

Remark: There will be extra costs if there is a lot of data transferred to/from the servers.

Step5.JPG

Step 6 is the summary. With the Finish-button the deployment will start.

Step6.JPG

We see that the instances will be created in about 1 hour.

Activate instance.JPG

In the CAL we see that the deployment is running:

Activating2.JPG

And after one hours it is active:

Activated3.JPG

Check in AWS

Login to the AWS console to check if the new systems are really created and ready:

inAWS.JPG

Both the ERP and the Netweaver Gateway are up and running and ready for login.

Check the SAP systems

First we logon to the systems.

We know the ip addresses from the AWS console and we know that the instancenumber is 00 for both systems.

ERPreadyforlogin.JPGGatewayreadyforlogin.JPG

What I did next was check if the configuration for Fiori was really allready done.

I will not show all screenprints because this will make this blog too big.

Check the following pdf for the Fiori configuration for this specific CAL deployment.

But I can confirm that the following configuration was all done in the system:

  • SICF: Relevant services
  • SPAM: Patch level
  • SM59: trusted RFC  from Gateway to ERP and from ERP to Gateway
  • SPRO: SAP NetWeaver > Gateway > Odata Channel > Configuration > Connection Settings > SAP NetWeaver Gateway to SAP System > Manage SAP System Aliases
  • SPRO: SAP NetWeaver > Gateway > Odata Channel > Configuration > Connection Settings > Activate or Deactivate SAP NetWeaver Gateway
  • /IWFND/MAINT_SERVICE: Gateway and UI5 Services
  • SMICM: ICM port

Test Fiori

Our first test is the Fiori launchpad.

The hostname of the Netweaver Gateway was already configured: cigw1.dummy.nodomain

I added this hostname in my local Windows hostfile to be able to reach the system by this full qualified domainname.

The configured secure port is 44300.

So the URL for Fiori Launchpad is:

https://cigw1.dummy.nodomain:44300/sap/bc/ui5_ui5/ui2/launchpage/admin/admin.html?sap-client=001&sap-language=EN

Use user BPINST with master password that we filled in during setup in CAL

FioriLauchpad.JPG

After login:

FioriLauchpad2.JPG

When we click on Customer Invoices:

FioriLauchpad3.JPG

Some preconfigured URLs that I successfully tested:

Sales Representatives Applications

  • Change Sales Orders: /sap/bc/ui5_ui5/sap/ui5_sd_so_mon/index.html
  • Create Sales Orders: /sap/bc/ui5_ui5/sap/ui5_sd_so_cr/index.html
  • Customer Invoices: /sap/bc/ui5_ui5/sap/ui5_sd_inv_mon/index.html
  • Track Sales Orders: /sap/bc/ui5_ui5/sap/ui5_sd_so_mon/index.html

Purchasing Agent Applications

  • Order From Requisitions: /sap/bc/ui5_ui5/sap/ui5_mm_popr_cr /index.html
  • Track Purchase Orders: /sap/bc/ui5_ui5/sap/ui5_mm_po_tr/index.html

With these tests I have a good feeling the deployed systems technically work.

I decided to end the test and remove the systems.

Remove systems

From the CAL I terminated the Fiori instance.

TerminateCAL.JPG

In AWS we see that the systems are being shutdown automatically:

TerminateAWS.JPG

After 20 minutes the instance in CAL and the systems in AWS were deleted.

With this excersise I learned how easy it was to setup a complete working Fiori environment in AWS via the SAP CAL.

When I need a demo or test environment, this is a really good option.

When I need a production environment for a customer I will install it manually to be able to choose the SID, hostnames etc myself. 

Best Regards,

Marco

To report this post you need to login first.

13 Comments

You must be Logged on to comment or reply to a post.

  1. Masayuki Sekihara

    Has someone tested the new launchpad?

    launchpad:

    https://<host>.<domain>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/Fiorilaunchpad.html?sap-client=<client>&sap-language=EN

    launchpad designer:

    https://<host>.<domain>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?sap-client=<Client>?scope=CUST

    (0) 
    1. M. Stitselaar Post author

      Hi Massayuki,

      With this preconfigured installation this new launchpad was not yet available.

      When I installed the Fiori system manually I used the latest version of ERP Ehp7 and patchlevel and then I used the url to new launchpad.

      I only did some small basic tests, but I did not had any issues.

      Regards, Marco

      (0) 
      1. Anil Bavaraju

        Marco,

        I am using the AWS trail, and i am not seeing the new launchpad, please let me know if you applied the patch to get the new launchpad?

        -Anil

        (0) 
  2. Sudhanshu Garg

    Hi Marco,

    Thanks for creating this blog. Its very informative & good for quick Fiori demo purposes.

    I started following the steps and fulfills all the below mentioned prerequisites but couldn’t see any entries under “Activated By” & “Operations” column to proceed further in the second step. My company has production & non production license for SAP Fiori and heading towards POCs first. So is there any extra step need to be followed to locate an entry in the mentioned columns? I would appreciate your inputs on this.

    Prerequisites

    Your company has to have a test and demo license

    You have to register your S-user account at the CAL (https://cal.sap.com/)

    You have to have an AWS account

    Thanks,

    Sudhanshu

    (0) 
    1. M. Stitselaar Post author

      Hi Sudhanshu,

      I think the issue is that your AWS account is not yet configured for your CAL userID.

      For me this was already done because I experimented also with other systems.

      Can you contact a colleague who has administrator authorisations?

      I will also ask mine to ask him how this can be done if it is not yet setup.

      Regards, Marco

      (0) 
      1. Sudhanshu Garg

        Hi Marco,

        Thanks for your inputs. I have forwarded the request to admin person as per your response. In the meanwhile please update in case you here from your contact person.

        Thanks,

        Sudhanshu

        (0) 
        1. M. Stitselaar Post author

          Hi Sudhanshu,

          I found out from my colleague who has administrator rights that he did connect the CAL user to the AWS account.

          It looks like this:

          CAL user AWS connect.png

          So you need to know your AWS Access key and Secret Key.

          Best regards, Marco

          (0) 
  3. Sudhanshu Garg

    Many Thanks to you Marco for your timely inputs. I have forwarded it to my Admin person & yet to receive a response.

    Thanks Again.

    Sudhanshu

    (0) 
  4. Manoj Ramasamy

    Thanks for your support.

    Can I know how to get test and demo license for individual  ( I am trying to install and explore it )

    Prerequisites

    Your company has to have a test and demo license

    You have to register your S-user account at the CAL (https://cal.sap.com/)

    You have to have an AWS account

    (0) 
  5. Prashant Bhat

    Hi,

    As far as I know any solution on SAP CAL comes with a 30 day expiry period. What if we want to install it permanaetly on AWS? 

    Kindly revert

    (0) 
  6. Ian Wyatt

    Hi,

    It seems that this solution that been removed from the CAL and replaced by a S/4 demo solution. We, like most SAP customers, do not have S/4 installed and have no plans to migrate. However I need to investigate some Fiori apps that have been released for an ECC backend and therefore would very much like to have access to this solution through the CAL. Does anyone know how we could get SAP to make this available again?

    Regards,

    Ian

     

    (0) 

Leave a Reply