Transcript
Page 1: OpenSAP Fiori1 Week 02 Transcripts

openSAP Introduction to SAP Fiori UX

WEEK 2, UNIT 1

00:00:12 Hello and welcome. My name is Prakalp Phadnis.

00:00:15 I am a principal consultant in the Global Mobility Services SWAT team

00:00:19 and I am very happy to welcome you to this brand new session on Fiori at openSAP.

00:00:24 This week, the topic of our focus is deploying the components required for implementing Fiori

00:00:30 and some of the theory related to these activities.

00:00:34 In the previous sessions together with Elizabeth in week 1, you went through the UX, the user experience paradigm at SAP, the architecture,

00:00:43 and Bob Caswell took you through the RDS approach to knowledge sharing and implementation acceleration.

00:00:50 All of these are exciting topics for Fiori enthusiasts.

00:00:54 This week, unfortunately, the much more mundane topic of deployment.

00:00:59 But I hope that the exercises that we have designed will make it more exciting for you as we go along.

00:01:05 The slide you are looking at should be familiar to you.

00:01:10 Elizabeth took you through this in week 1.

00:01:12 Those who couldn't attend that session, please do take the time to familiarize yourselves with this slide.

00:01:18 It's a really good overview at a high level of what we are trying to achieve.

00:01:23 So the key message in this slide is, let's say, a one-minute architecture overview of how the Fiori applications are delivered

00:01:31 and what various layers that we are traversing and which components that we are using.

00:01:36 Starting at the very top, you see that there is a WebKit-enabled browser on either a desktop or a handheld device—it doesn't matter which—

00:01:45 which then goes through a proxy.

00:01:48 In some cases there is a hard requirement for this proxy to be an SAP Web dispatcher, but we'll get to that in a minute.

00:01:57 And then reach the SAP Gateway that we were...SAP NetWeaver Gateway 2.0, as it used to be called.

00:02:04 Now it's called the SAP front-end server, where the services are registered.

00:02:08 The front-end server, in turn, is responsible to call the correct OData services which are deployed on the back end.

00:02:15 And in some cases, the HANA XS engine is directly called from the Web dispatcher.

Page 2: OpenSAP Fiori1 Week 02 Transcripts

2

00:02:22 This is based on what kind of protocol is being used for that call and there is a routing logic in the Web dispatcher to handle that.

00:02:33 That's the reason for the dependency.

00:02:35 But we'll look into that a bit more as we go through the types of applications and so on.

00:02:40 So going past all this dry and theoretical stuff, what does it get you?

00:02:48 In the top section of the slide, I've tried to do sort of a guided procedure,

00:02:58 tried to get you to see this is what we have, it gets you this, and so on and so on.

00:03:02 So what does this theory get you?

00:03:04 Well it gets you this wonderful launchpad.

00:03:08 Now again, Elizabeth will have taken you through the launchpad and shown you the various applications in that launchpad.

00:03:17 But look at the transition. This dry architecture gives you such a wonderful UI

00:03:22 and in my opinion, this UI almost doesn't require any...there is no learning curve.

00:03:28 It's a clean user interface. It provides the information that you need

00:03:33 and you can almost begin to be effective in this UI from the word go.

00:03:39 So the question is: Okay, that's great. I like the UI. I now know what the architecture is or at least remember what the architecture is.

00:03:46 How to get here? How to really get here?

00:03:50 So let's take a few seconds. Before we go down to the next side, let's take a few seconds

00:03:56 to think about the composition of the apps themselves.

00:04:00 You will remember that I spoke about OData services in the architecture slides

00:04:05 and those of you who are inherently programmers, you will not need any explanation for that.

00:04:13 But for the wider audience, the OData service is what provides the data.

00:04:19 It's the meat on the bone, so to speak.

00:04:21 And naturally, this service lives where the data lives, and that's in the back-end system.

00:04:25 It's deployed as an add-on.

00:04:28 To our the participants looking at this or colleagues who are looking at this who are SAP Basis colleagues, they will immediately know what to do with this.

00:04:38 Each service is served with a UI component that matches it.

00:04:44 So some of the UI components are standardized across services

00:04:48 and others are specific for the app or the scenario.

00:04:52 And similar to the OData services add-ons, the UIs are also delivered as add-ons.

00:04:58 And of course, you guessed right, these are delivered and deployed onto the front-end server.

00:05:04 So the SRAs or the OData service add-ons deployed on the back end, the UI add-ons

Page 3: OpenSAP Fiori1 Week 02 Transcripts

3

deployed on the front-end server.

00:05:14 And together they shake hands and once that happens, this is the picture that you are seeing on the screen,

00:05:22 the launchpad populated with tiles, as they're called, with data in them.

00:05:28 Where and what do these add-ons look like in the back end? How can you see them? What do you do?

00:05:35 Because of the breadth that this course is going to appeal to, some of this stuff is very basic.

00:05:41 Those of you who are SAP-proficient may not have that much to take away from it.

00:05:46 But for those who are not, this is...the add-ons are in the back-end system, are visible when you access a certain menu structure.

00:05:57 Let me go and show you that in a minute.

00:05:59 But the back-end components, the foundation components, are available to you there to view

00:06:06 and also the components for the services themselves.

00:06:11 Let me just jump out of this PowerPoint for a minute

00:06:15 and go log in...sorry, I am already logged in.

00:06:19 So now I hope what you're seeing is the SAP GUI when I'm already logged in.

00:06:27 This is, by the way, a similar system to the one that you're going to be using.

00:06:33 There should be no visible difference for you. Everything should be exactly the same.

00:06:40 You can click exactly where I'm clicking to go find this information.

00:06:44 So all I did was click on the System button, the menu item here.

00:06:49 Scroll down to Status, and that opens up a System Status window.

00:06:55 Click on the little magnifying glass (the proper term is Component information, by the way).

00:07:00 Click on the magnifying glass. That throws up another window

00:07:04 and here you see all the components—I am marking the column there—

00:07:09 their release level, the SP level, and some descriptive text about these components.

00:07:14 So let's take one example here. What can I show you?

00:07:18 This one right here, for example: SAP_GWFND.

00:07:23 The SAP Gateway Foundation. Self-explanatory.

00:07:26 If we scroll down a little bit, let's see if we can find some of those SRAs since we're talking about back-end component deployment.

00:07:36 Just a little bit more scrolling...

00:07:38 There. Here we go.

00:07:43 There it is. So all these here, the SRA001, 002, 003, and so on and so on,

00:07:51 these are all these OData services add-ons that have been deployed.

Page 4: OpenSAP Fiori1 Week 02 Transcripts

4

00:07:56 And each of them has a descriptive text. So although the name of the component may not be so intuitive,

00:08:04 you can see here 008 is, for example, Approve Travel Expenses. Just for example.

00:08:10 Now this is where you'll go and find this information in your system.

00:08:17 Going back to my presentation, if I can find it here.

00:08:22 So going back to my presentation and jumping one slide back.

00:08:26 Following the logic of the breadcrumbs or the guided procedure on top.

00:08:31 In the beginning, we had the architecture. That architecture gave you this as an end product, the launchpad and all the functionality within it.

00:08:38 Now to build this functionality, what we need is some of the basics like these SRAs.

00:08:46 And each of these back-end components have a handshake with a UI element to them, like I said in an earlier slide.

00:08:57 And let's go find these as well.

00:08:59 Now before we go there, you will see me do the same thing.

00:09:05 So I didn't change any systems. It's still being called ERP down here. You'll see that the client is the same.

00:09:11 That's because we're doing something called an embedded deployment. I'll come to that in a bit.

00:09:15 But our test system has both the back-end and the front-end components deployed in the same system.

00:09:26 Okay. So let me find those.

00:09:29 If I can do a little bit more scrolling here...there we are.

00:09:34 Perhaps mark this over here like this.

00:09:38 So here we have UI components. UI for ERP Central Applications.

00:09:45 The HANA Live content and Smart Business and so on.

00:09:49 These two deployed together—not necessarily on the same system—but these two deployed together shake hands

00:09:55 and give us what we need from our system to be able to use the launchpad.

00:10:05 Now going back to the presentation.

00:10:09 What I would like to highlight here just for one moment is that

00:10:16 we have a set of foundational components.

00:10:20 These are universal. Or rather, they are necessary for the Gateway to support its function as a front-end server.

00:10:29 And then there are some components which are generic.

00:10:34 So if I take you quickly back to this Status window here, I can show you that there was one which was called

Page 5: OpenSAP Fiori1 Week 02 Transcripts

5

00:10:45 UI for ERP Central Applications. Generic UI.

00:10:49 And it's being used or reused. These UIs are being reused.

00:10:53 Here, for example, let's have a look at one of the ones which are specific

00:11:00 to the kind of module that one might be implementing.

00:11:03 For example, the one I've highlighted now is called UIX01HCM.

00:11:10 This UI component... you know, we're simplifying the whole thing,

00:11:14 the deployment, the maintenance and so on,

00:11:17 so this one add-on contains the UI for all the HCM scenarios.

00:11:23 The same applies for the next one. It's called Travel. All the travel scenarios are served by this one particular UI component.

00:11:34 Now where can you find these?

00:11:40 These components are downloaded for you.

00:11:44 You can do it in multiple ways.

00:11:49 But before we go to the actual place where you can go and find these components and download them,

00:11:54 I want to talk about something called the Solution Manager and Software Update Manager

00:12:02 and essentially the toolkit that we are recommending or even insisting should be used for deployment purposes.

00:12:11 The reason for this is because we are in a highly...not necessary volatile, but fast-moving area.

00:12:21 Fiori is evolving. There are a lot of changes being made.

00:12:25 And in that context, it is important to have a set of tools which

00:12:32 ensure that you're doing the right thing at the right time

00:12:36 and this is where this toolkit comes into play.

00:12:40 The Software Update Manager, for example, facilitates NetWeaver-based application system upgrades,

00:12:48 enhancement package updates,

00:12:50 and installation of Support Packages, for example, in a single harmonized UI.

00:12:58 While the Software Update Manager is shipped as a part of a toolset—again, you can go and download this—

00:13:05 it's independent of all the applications that we're talking about.

00:13:08 However, it supports the deployment, upgrade, and maintenance, as I mentioned.

00:13:13 You can get it from the Service Marketplace. In the next slide, I'm going to talk about the Service Marketplace for a bit.

00:13:21 But also, the Maintenance Optimizer transaction in SAP Solution Manager is an important point to discuss here

Page 6: OpenSAP Fiori1 Week 02 Transcripts

6

00:13:28 because we are generating the XML stack list through this transaction.

00:13:33 Again, those of you who are Basis colleagues, you will know this by heart,

00:13:36 but I need to mention it for the wider audience.

00:13:40 The Maintenance Optimizer transaction is a central point of access for these maintenance activities.

00:13:45 It supports, again, the installation of updates and upgrades

00:13:49 and it can essentially completely manage the maintenance activities for the entire solution.

00:13:55 There are some prerequisites to setting up the Maintenance Optimizer transaction.

00:13:58 That's not the scope of our work over here.

00:14:01 However, suffice for you to know that this is our recommendation of how you will deploy Fiori.

00:14:12 Maintenance Optimizer is centrally accessible from inside Solution Manager.

00:14:17 And there's a very simple URL for you to access for more information on this.

00:14:22 So all you need to do is go to service.sap.com/mopz.

00:14:28 So Maintenance Optimizer, that's the short form or the transaction code for that.

00:14:36 While on the previous slide, I said I'm going to talk about the Service Marketplace.

00:14:42 The Service Marketplace is the one place which gathers all information related to SAP products

00:14:49 and it's essentially a one-stop shop.

00:14:52 Here you go. You have a user, of course.

00:14:57 In the slide deck you're looking at now, I've drawn a little marker, if you will, or red box, on the top right-hand corner.

00:15:06 There is the information to either log in or register or even reset your password if you're coming in from the outside as a non-SAP employee.

00:15:16 Now, why am I saying this now? It's because when I show you this, I'll already be logged in and you won't see that part here.

00:15:23 So I just wanted to emphasize.

00:15:25 And you need a user, even with Solution Manager. When you create this stack list and when you ask for the downloads,

00:15:34 you need an authorized user with the right permissions to do that.

00:15:39 Usually, this S-user is not something you create yourself.

00:15:42 It's connected to the licenses that your employer has or your company has, and so on.

00:15:49 So make sure that's something that you have with you when and if you go down the path of implementing this.

00:15:57 So let's jump out again of the presentation and find the Service Marketplace.

00:16:03 Interestingly enough, it says Welcome Guest over here.

Page 7: OpenSAP Fiori1 Week 02 Transcripts

7

00:16:06 So it hasn't logged me on. But let's see if my single sign-on works.

00:16:11 Support Portal. Just an example. Let's go there.

00:16:22 Okay. A few minutes, a few seconds.

00:16:28 Okay. Excellent. My single sign-on worked. Here it says Prakalp Phadnis and so on.

00:16:32 Look at these breadcrumbs. I just wanted to show you a little bit of what it looks like in there.

00:16:38 Software Downloads. And then Installations and Upgrades. Let me just search for something really quick.

00:16:46 Let's say *fiori...Is that right? Yes...*. Enter.

00:16:52 And oh, look!

00:16:56 A number of hits. There are even a number of pages. 18 pages all in all.

00:17:01 So that's just a quick demo of the Service Marketplace.

00:17:09 Remember, you need an S-user, You can't see these...oh, what happened?

00:17:16 Okay, let me try again. You can't see these files if you don't have the licenses or the relevant authorizations.

00:17:24 In my case, being an employee, I can see a lot more than you probably would see.

00:17:30 Okay. All the components are downloaded from here.

00:17:35 Sorry, just one moment.

00:17:43 That's us back. Service Marketplace, yeah? Then that brings us to the end of this overview unit.

00:17:50 So what we did was we went quickly through the architecture that Elizabeth that covered with you in week 1.

00:17:55 We saw the results of having implemented all the required components, what kind of components they were, front-end, back-end.

00:18:03 We talked about where you can get these components, what you need to be able to download these components,

00:18:09 and we also talked about the recommendations that SAP has, or even directives that SAP has

00:18:15 for deploying these components—namely Update Manager and Solution Manager—for a successful deployment.

00:18:21 In the next unit (that's also me, by the way), we will cover the prerequisites

00:18:27 and we will look at SAP Notes, a very important topic.

00:18:34 And we will look at where to go...again, I want to show you the background of where to go

00:18:40 and where to find information, because that's almost more important than just giving you the information.

00:18:46 So thank you for your attention and see you next week.

Page 8: OpenSAP Fiori1 Week 02 Transcripts

8

WEEK 2, UNIT 2

00:00:13 Hello and welcome to week 2, unit 2 “Validating the Prerequisites”.

00:00:17 This is going to be the shortest section you are going to see in this course.

00:00.23 Why, because there is really only very little to say and even less to show.

00:00:28 However, I decided to dedicate a unit to this topic as we have experienced that many challenges can be mitigated just by having done some of the preparation work prior to starting execution.

00:00:42 And because Fiori is such a fast moving topic (I mentioned this also in unit 1), there are improvements and additions in almost every quarter.

00:00:51 And it's vital that you spend some time on 1) determining the prerequisites and 2) ensuring that all the relevant notes are applied.

00:01:01 This helps, you know, mitigating any unknown behavior that you might be experiencing.

00:01:06 So SAP is providing the foundation to make the start as easy as possible by gathering all the relevant information in an easily accessible and equally easily referenced documentation.

00:01:19 And to reach this documentation, the only URL you are going to need is help.sap.com/fiori.

00:01:27 And all the necessary information is collected here and any further links or any further additional material that may need referencing is also identified over here: help.sap.com/fiori.

00:01:39 Now in order to find the prerequisites for your particular scenario, what you need to do is access the prerequisite list, which is published on this slide.

00:01:51 And I have a hyperlink in the presentation over here, I have already clicked on it.

00:01:57 So let me switch the view to Internet Explorer and show you the Prerequisites section.

00:02:08 Now, on the Help Portal, when you click on the “prerequisite” link, it will take you directly to the Installation section.

00:02:16 If you were to access this otherwise, just click on the installation topic, and that will throw up these subtopics where “prerequisites” is the second main subtopic.

00:02:27 And the prerequisites are listed in a logical order: They address databases, so either HANA –

00:02:34 prerequisites for, if you're running on HANA, prerequisites if you're running on any other database,

00:02:41 prerequisites based on...for the front-end server, the back-end server, which version of these servers so if you're on NetWeaver 7.31 or 7.40,

00:02:51 which SP you're on, what SP you need minimum, what SPS and versions you need for the ERP if you're deploying those scenarios.

00:03:02 SRM, CRM, and so on – you see them listed down here.

00:03:08 Now going back to the presentation. The second topic that we wanted to talk about or I said I'd like to talk about is SAP Notes.

00:03:16 And SAP Notes, again, are collected in the same place.

00:03:22 They're are also gathered under a title, let me, I have a link on the left-hand side again.

Page 9: OpenSAP Fiori1 Week 02 Transcripts

9

00:03:30 It's called “release notes”, check the release notes. So I've clicked on this link and it will take you...

00:03:37 In this particular case, look away from the fact that it says “Transactional Apps” and “Fact Sheets” – they apply, the concept of notes applies to all types of applications.

00:03:47 And here all the notes are gathered together for you.

00:03:51 The central SAP Notes, they give you sort of an entry point if you will.

00:03:58 And they usually reference other notes so let's look at one by just clicking on it.

00:04:03 This particular one applies to the front-end server and it's about, it's a general information note for the UI and infrastructure components.

00:04:12 So there's that note, it's come up. And they always follow the same format:

00:04:18 some symptoms, the reasons, the prerequisites, what solutions are being offered and additional details.

00:04:26 And then look at this section here – additional needed notes – you have a number of notes that are referenced.

00:04:31 Always look through these and make sure that you're up-to-date and up to speed in your system.

00:04:40 Like I promised, shorter section, shortest unit.

00:04:44 And in the next unit, we're going to talk about deploying back-end components. So see you soon!

Page 10: OpenSAP Fiori1 Week 02 Transcripts

10

WEEK 2, UNIT 3

00:00:12 Hi and welcome to unit 3 of week 2: Back-End Server Components Installation Overview.

00:00:19 I am happy to see that after two units there is still interest to follow this essentially dry and tough topic.

00:00:26 If you remember back to our earlier units, as well as Elizabeth’s units,

00:00:30 we spoke about the architecture of how the components are designed to be a handshake

00:00:36 between the back-end components and the front-end components,

00:00:39 where both depend on their respective foundation components as well.

00:00:42 So in this unit we will look at the back-end components, where to find them, and how to deploy them.

00:00:49 Before we go any further, let's have a quick look at the types of Fiori applications available to us today.

00:00:55 There are essentially three types of applications: the transactional applications, the fact sheets, and the analytical applications.

00:01:02 The types of applications being deployed dictate what kind of components to be deployed

00:01:09 and the back-end system that is required to deploy these components.

00:01:14 Talking about each of these types a little bit. Transactional applications are essentially task-oriented.

00:01:20 The name itself says, you know, a transaction.

00:01:22 So you are executing a specific action. For example, you are entering your time in your time sheet

00:01:29 or maybe you're a manager and you are approving leave requests or time sheets.

00:01:33 Usually these transactional applications are provided in archives called SRAs

00:01:40 and these archives, at the moment at least, are numbered from 1 to 20 or 21.

00:01:46 With the exception of three of them, for some reason. And these are called...these have names that start with GBHCM or GBAPP.

00:01:55 And let's stop there for a moment. I will jump into the SAP GUI and let's see these names.

00:02:04 I expect now that you're familiar with where we are in the GUI. So I'll just click on the magnifying glass and scroll down in this component list.

00:02:14 And there you see them. Let me scroll back up a little bit.

00:02:18 So we get both types of names there.

00:02:21 This is what I was talking about. SRA001, SRA002, and so on.

00:02:25 And then GBAPP and GBHCM.

00:02:29 So that's the naming anomaly, let's call it like that, in this particular case.

00:02:39 So. Transactional applications. Now moving on.

Page 11: OpenSAP Fiori1 Week 02 Transcripts

11

00:02:42 Let's have a look at what fact sheets are.

00:02:45 Fact sheets make contextual data come alive.

00:02:48 They allow the user to review data at an overview level,

00:02:52 drill down into some details, and then finally navigate to a system in order to execute a specific action.

00:02:59 Fact sheets require both the ABAP stack as well as SAP HANA.

00:03:04 They require the Web Dispatcher.

00:03:07 And they use something called search models,

00:03:11 and these models are delivered as a part of the prerequisites enhancement pack for these type of applications.

00:03:20 The next type is analytical applications.

00:03:24 A little bit confusing—sometimes they are called smart business applications,

00:03:27 and in some other documents you may see them as analytical applications. Essentially the same thing.

00:03:32 They require and only run on the HANA platform.

00:03:37 They use something called a two-tier architecture. It's also called HANA Live,

00:03:43 where we are using something called virtual data models (VDMs).

00:03:49 And again, require the SAP Web Dispatcher.

00:03:52 These give the users a role-based insight into real-time operations for the business.

00:03:59 They collect and display key figures directly in the browser.

00:04:02 They provide real-time information on large data volumes

00:04:08 and a simplified front end for enterprise control.

00:04:14 This slide most of you will see and remember from earlier units.

00:04:20 While we have covered most of the salient points in this unit about app types,

00:04:24 there are always more details. There are updated details that are relevant, and more important information that needs to be discovered.

00:04:31 And all this can be found at help.sap.com/fiori.

00:04:37 Clicking on this link takes you to this page in the Help Portal.

00:04:45 Click on the text which says SAP Fiori App Types and Database Requirements.

00:04:50 And that gives you all the current requirements and all the current app types and an explanation of each of these app types,

00:04:58 including the architecture.

00:05:04 And then finally, at the end of this section, perhaps the most important slide.

00:05:10 Again, this may be a little bit of a repeat, but it just goes to show how important this

Page 12: OpenSAP Fiori1 Week 02 Transcripts

12

recommendation is.

00:05:16 We are clearly recommending to use deployment tools like Solution Manager (Maintenance Optimizer transaction) and the Software Update Manager

00:05:25 and the HANA Lifecycle Manager to manage and deploy Fiori to your target landscape.

00:05:31 In some cases—in some cases only— you may have to use the transactions SPAM or SAINT

00:05:38 to add new Support Packages or updates to your existing Support Packages.

00:05:43 Yes, the Basis colleagues will tell you, these are actual transactions in SAP—I'm not just making them up—

00:05:49 SPAM standing for Support Package Manger and SAINT for Add-On Installation Tool.

00:05:55 And you can see that the titles on the menus here in the graphic also reflect that description.

00:06:04 And in some special cases, you can manage the entire deployment of a Fiori application

00:06:13 using these transactions, but that is really not the recommended approach.

00:06:20 To recap at the end of this session, we have looked at the back-end components based on app types,

00:06:29 we have looked at where to find them, we have looked at where to go for more information.

00:06:34 We have seen what kinds of tools and transactions are required to deploy these components,

00:06:39 and we've also had a look at the help pages.

00:06:41 In the next unit, we will repeat this exercise, but at that time focusing on the front-end components.

00:06:47 See you soon.

Page 13: OpenSAP Fiori1 Week 02 Transcripts

13

WEEK 2, UNIT 4

00:00:12 Hello and welcome to week 2 unit 4: an exercise to familiarize yourself with deploying add-ons to the back-end server.

00:00:20 In the previous unit, we looked at the back-end components installation overview, and now it's time to get some hands-on experience if you so choose.

00:00:28 This is an optional exercise, as are all the exercises we have designed for you,

00:00:32 which means that there is no impact on your final score if you choose not to do it.

00:00:37 Let me spend a few minutes describing the structure of the task at hand as I envision it.

00:00:43 The task of deploying an add-on onto the back end is a straightforward activity if you are a specialized SAP Basis consultant,

00:00:50 and sometimes even then it's difficult.

00:00:53 But most of us are not Basis consultants, so don’t worry if you are not successful in deploying the add-on to your personal cloud instance.

00:01:00 We have prepared the groundwork to account for most of the possibilities, but cannot account for all of them.

00:01:06 On the other hand, if you are successful in deploying the add-on,

00:01:10 then please don't walk away from this exercise thinking Aha, that was a piece of cake, because it's really not.

00:01:16 For the purposes of this arena, we've tried to simplify the process as much as possible to give you a taste of what is required.

00:01:23 In this exercise, I would like to guide you through the end-to-end process of downloading, deploying,

00:01:30 and then identifying the recently deployed add-on and it's new version.

00:01:36 You will create a user on the Service Marketplace, find the add-on that we have chosen,

00:01:40 load it into the queue of your back-end system, run through the deployment process,

00:01:45 and finally view the change in the system status window that we've seen earlier.

00:01:51 In the how-to guide, linked both in the slide as well as at the bottom of your screen,

00:01:57 you will find detailed instructions for setting up the system and executing this exercise.

00:02:02 You can also use the forum for support and discussions.

00:02:06 Have fun.

Page 14: OpenSAP Fiori1 Week 02 Transcripts

14

WEEK 2, UNIT 5

00:00:12 Hello and welcome to week 2, unit 5: Front-End Server Installation Overview.

00:00:18 Again, I'm happy that you are with us and you're finding these units interesting.

00:00:24 Let us do a quick recap on what we have covered.

00:00:26 So far, we have visited the following topics in these units:

00:00:31 the deployment of SAP Fiori-related components from a high level,

00:00:35 the prerequisites that you need, where to find updated information,

00:00:40 the deployment process, the tools that you require during the deployment process,

00:00:45 and how to deploy back-end components.

00:00:48 Now let us look at the required components and the process of deploying them for the front-end system.

00:00:56 You will all remember me talking about the Service Marketplace

00:00:59 and the downloads section in the Service Marketplace contains all the necessary media for all the components, including the front-end components.

00:01:08 So you may recall also that I talked about SAP focusing on simplifying the deployment process of Fiori.

00:01:15 As opposed to a one-on-one relationship between the front-end components and the OData service components,

00:01:23 we now have UI bundles that serve multiple back-end services.

00:01:28 For transactional applications, the UI applications are collected under the title FIORI ERP APPLICATIONS X1 1.0.

00:01:40 For fact-sheet-based applications, it is a little different,

00:01:44 and these are collected under the title UI FOR EHP7 FOR SAP ERP 6.0.

00:01:53 For analytical applications, the common search term that you will use—or you can use—is SAP SMART BUSINESS 1.0 FOR ERP.

00:02:03 Of course when you change the type of application that you're deploying, the corresponding back-end connotation will also change.

00:02:12 For example, if you are deploying a CRM-based Smart Business application,

00:02:18 then your search term may look something like SAP Smart Business 1.0 for SAP CRM.

00:02:27 In the earlier units, the emphasis I expressed on using the Toolkit also applies here.

00:02:34 Please use the Software Update Manager and the Maintenance Optimizer transaction in Solution Manager

00:02:40 to manage your deployment and to manage all your installation tasks.

00:02:44 As always, in some special cases, the deployment of the components can directly happen in the SAINT or the SPAM transactions.

00:02:53 This brings us to the end of this unit.

Page 15: OpenSAP Fiori1 Week 02 Transcripts

15

00:02:56 Here in this unit, we looked at the front-end component deployment, the app types, and the components based on these app types.

00:03:05 We saw where to find the required information and which tools and transactions are required to deploy these as well.

00:03:11 The difference in this unit from the rest of the units is that I have not repeated the visit to the help pages.

00:03:18 However, I am certain that you are now completely comfortable with the help pages and there is no need to repeat this topic further.

00:03:25 In the next unit, we will repeat this exercise, but a little differently

00:03:29 because we will focus on the HANA-based scenarios.

00:03:33 See you soon.

Page 16: OpenSAP Fiori1 Week 02 Transcripts

16

WEEK 2, UNIT 6

00:00:12 Hi and welcome to week 2 unit 6: an exercise to familiarize yourself with deploying add-ons to the front-end server.

00:00:20 In the previous unit, we looked at the front-end server components installation overview,

00:00:25 and now it is your time to get some hands-on experience if you choose.

00:00:30 This is an optional exercise, as are all the exercises we have designed for you,

00:00:34 which means that there is no impact on your final score if you choose not to do the exercise.

00:00:40 Because the previous exercise and this one are very similar

00:00:44 in the sense that we will repeat almost all the steps from when you deployed the back-end components,

00:00:49 I don't want to spend too much of your time introducing the exercise itself.

00:00:54 However, in this exercise, I would like to guide you through the end-to-end process of downloading, deploying, and then identifying

00:01:02 the recently deployed add-on and it's version level.

00:01:05 You will log in to the Service Marketplace—

00:01:07 remember we already created a user together—

00:01:10 find the add-on we have chosen, load it into the queue, run the deployment,

00:01:15 and verify the change in the system status window.

00:01:19 In the how-to guide, linked both in the slide as well as at the bottom of your screen,

00:01:25 you will find detailed instructions for setting up the system and executing this exercise.

00:01:30 You can also use the forum for support and discussions.

00:01:34 Have fun.

Page 17: OpenSAP Fiori1 Week 02 Transcripts

17

WEEK 2, UNIT 7

00:00:12 Hi, and welcome to week 2, unit 7: SAP Fiori UX on SAP HANA – Deployment Overview.

00:00:19 This week, we've covered various deployment topics already

00:00:22 and you may be wondering why I've chosen to address the HANA-based Fiori scenario separately.

00:00:27 Walking through this unit should highlight the differences between what we've seen so far

00:00:33 and why the HANA-based scenarios are different in terms of deployment.

00:00:38 In these HANA-based scenarios, we are introducing the HANA XS Engine,

00:00:45 the virtual data models (or VDMs, as they are referred to in short), and the HANA studio.

00:00:51 The HANA studio is an integrated development environment (or ID for short) which hosts the HANA lifecycle manager.

00:00:57 And this plays an important role in this context.

00:01:00 The Web dispatcher also plays an important role in this architecture

00:01:03 and last but not least, the deployment tools in themselves are different.

00:01:08 Clicking on the link in the presentation will take you to the help pages

00:01:14 and on these pages, you will see the entire composition described in detail. Please do have a look.

00:01:22 The HANA lifecycle management tool, at the time of recording this, is on SPS 07

00:01:29 and is now capable of installing and upgrading all the HANA platform software components,

00:01:34 for example, the HANA studio, the database, the host agent, and so on.

00:01:40 It has improved batch processing capabilities, so configuration files and command line options.

00:01:46 And it has improved logging and error handling.

00:01:48 The new HANA lifecycle manager installer is contained in this.

00:01:56 Essentially, there are three ways to work with the HANA lifecycle manager.

00:02:00 You can either use a config file that you prepare up front,

00:02:05 work in a terminal window with user interaction or in a terminal window without user interaction,

00:02:10 and through a GUI (graphical user interface).

00:02:14 The GUI is a fairly standard SAP UI with guided procedures, radio buttons, and checkboxes.

00:02:20 In those cases where one may be running an interactive session in a terminal window,

00:02:26 those checkmarks in the GUI would correspond to values entered as comma-separated values.

00:02:35 The HANA lifecycle manager is a tool with which you can maintain your HANA systems.

00:02:41 Currently, I am limited to showing you only the screenshot and the path which you will follow in

Page 18: OpenSAP Fiori1 Week 02 Transcripts

18

the tool.

00:02:48 And I understand that the screenshot may not be completely clear.

00:02:51 However, this is the view from the HANA studio of the lifecycle management tool.

00:02:59 And let me talk to the numbers in this screenshot, which are meant to show how to navigate within the tool itself.

00:03:07 Number 1, right-click on the system that you have in your studio.

00:03:14 That opens a context menu. In that context menu, number 2, is the lifecycle management menu item.

00:03:22 Clicking on that gives us number 3, which is the HANA lifecycle manager itself within this user interface

00:03:31 where you will then be able to update your HANA system, manage additional HANA components in the system.

00:03:37 You will be able to integrate the HANA system in your landscape and administer these systems as you would otherwise.

00:03:46 Now that brings us to the end of this unit.

00:03:52 Here we've seen some of the salient features as to why the tools that we're using to deploy HANA

00:03:59 are significantly different than the toolset we talked about earlier in this week.

00:04:04 In the next unit, you will look at an exercise based on the HANA studio. See you soon.

Page 19: OpenSAP Fiori1 Week 02 Transcripts

19

WEEK 2, UNIT 8

00:00:12 Hi and welcome to week 2, unit 8: the exercise on HANA studio.

00:00:18 This is an optional exercise, as are all the exercises we have designed for you,

00:00:22 which means that there is no impact on your final score if you choose not to do it.

00:00:28 In this exercise, I would like to guide you through the end-to-end process of downloading, installing, and connecting the HANA studio to the back-end system.

00:00:36 In the how-to guide, linked in the slide as well as at the bottom of your screen,

00:00:41 you will find detailed instructions for setting up the system and executing this exercise.

00:00:47 You can also use the forums for support and discussions.

00:00:50 Have fun.

Page 20: OpenSAP Fiori1 Week 02 Transcripts

www.sap.com

© 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.


Top Related