Introduction to SAP Process Orchestration

Srinivas Vanamala
A free video tutorial from Srinivas Vanamala
SAP Integration Architect
4.4 instructor rating • 11 courses • 43,730 students

Learn more from the full course

Beginner: Complete Basics of SAP PO (Process Orchestration)

Learn everything you need to know about SAP Process Orchestration tools and Integration Concepts

14:41:52 of on-demand video • Updated February 2021

  • Complete Understanding on Integration Concepts
  • Understand Concepts like XML, HTTP, Webservice, SOA and many others
  • Understand the SAP PO Architecture and Tools
  • Build Interface with SAP PO Tool
  • Introduction to SAP Process Orchestration and Process Integration
  • Understand the difference between PI and PO
  • AEX, NW BPM and NW BRM Introduction
  • Learn all the PO tool in detail
  • Complete Hands-on SLD,ESB, IR
  • Learn the testing tools like SOAPUI and PIMON
  • Complete Interface development from one FTP Location to another
English [Auto] Hello and welcome to broadcast Dotcom. This topic is all about getting started to learn and understand about what is the process of destruction. Well, this topic is like welcome to a special one you might be learning. This goes with previous understanding of Beric site Aldwych, another integration tool background. Or this might be your first introduction recipe integration to wherever you are. But I assume that you are a newbie. And first, I'm trying to understand this IT process of the situation. So I will arrange the topic from Rary. Basically, we have taken previous courses like XML, SSD xpac just to give it away, E.S.P LipService or WCT Eddi it is NetWeaver and all the other basics that we have been learning through in previous topics. Then learning Akpabio is like super easy for you. How could you bring these keywords with understanding that, you know these terms very well, having studied this topic with basics like why there is a need for integration and home SFP integration tool are used to solve integration challenges. This action will make you familiar with what is a simple and back home computer lessons, we will learn more about architecture than the actual books. Then let me give you a quick definition of what is a CPA, the CPA process participation. Hartville is a combo product provided basically it's actually a part of the primary purpose of this tool is to serve the integrations and as a people is a product like Microsoft Office. So remember, it is a product each to innocent people helps to address the specific needs of integration. And when we see a CPA as a product, it's a combination of three different things, like the test process integration, which is dominated by and business process management, which is a CPA and business rules management, which is BRM. Before thinking what is a CPA, then you need to understand that Bill is a product BIA's company and similarly BPM and BRM. He's a King Abdullah has been available for us to work. And he will cover everything under a CPA, but in the section that is just the basics and the introduction. Let me give you the floor of the topic that you learned in this section. First, we try to understand why there is actually a need for an indication of the challenges in integration and we learn about the simple process of destruction. I'll give you some background about previous releases of the CPA and how it evolved. And so we will try to understand what it is previously called us to look at components of this appeal. Finally, we will look at how a ship was positioned in the overall integration architecture. Really superexcited to start the journey of the CPA with you. So let's get started. Let's first understand what is the need for integration tools and how they are. Imagine a business process of you interested to buy an iPhone. First, you were logging into, let's say, Apple site and placed the order, Apple will receive the order and then it will place the parts order from its supplier to make that iPhone for you, then, once supported by Apple company, will build the iPhone. Finally, when the phone is ready, it is up to you. Well, I've explained the whole process in a simple words, but actually it's much more complex than we defined. But let's observe the business process and the systems involved. Well, ERP application can be used to store the order. Shopfloor and production floor might use a custom software to run the production line. The logistics system will make sure the delivery is done. Well, if you remember the topic that we discussed on Eddi and Pip, those were the data standards that can be used to exchange the business. Communication between the trading partners like Apple might be using Iida or PIP to exchange the communication between its supplier. So just to build one iPhone, there might be many data exchanges to happen between the systems, the need of integration is really important to make sure that business transactions are exchanged between one system to another and just to complete one business process and to end. Also, each system needs a different type of leader type or different connectivity to exchange the message, so the job of conversion of data connecting to systems and routing of messages is typically handled by the integration. Let me give you another view from an Israeli point of view, companies that follows Web based architecture where all their business processes are split into services. Now, just to complete one business process, all the services need to talk to each other. Right. And without the integration tool, all the services will start integrating with each other and thus it will complicate the entire landscape and will be difficult to sustain, obviously, in the longer run. Right. This does not mean it is a wrong concept. So should not be implemented. Do not have that assumption. OK, but understand that it does not speak about integration. You just say that when a company business process is split into loosely coupled services, then we say it's an I.T. architecture built on its own or service oriented architecture or service based architecture. Well, with the Enterprise Service Bus or ESB, we can solve the integration challenges and simplify the integration architecture, enterprise service bus or Legazpi helps to integrate all services and provide an integration platform to communicate in the previous diagram. All we need to solve the complexity was a single point of integration that actually can remove the dependency from each of the service to connect and to reuse. It's like asking all the services to come to USB and then ESB will decide what to do next with that request. This helps the company because now they can understand what is happening in the real time and how business processes are exchanging the messages. Lisp is like a single point of integration, and it removes the point to point connection between the services. It's like acting like a mediator between two services to talk to each other. So by now, you know, he be helped to integrate all the services together. We have actually discussed this topic previously and we have also discussed the ESB core principles in previous lessons. Let's give you a brief summary. ESB architecture has the following principles that we discussed. So any tool in the market who says is an ESB tool will follow these principles. And PayPal is not the only hospital. There are many other tools in the market. But for now, let me give you a brief summary of E.S.P principles. First, let's talk about orchestration. Well, orchestration means the tool should have the ability to connect to the system and exchange the message. Transformation means convert the data from one format to another format. Transportation actually means ability to connect system with different protocols like KSTP. So if TDB, Jamous and others, security means the message should be transferred in secured manner and no one should be able to sniff had the message packets. Governance means able to govern the entire business process, like we should have a monitoring tool, restart stopping capability locks, audit maintenance. Complete lifecycle of the application should be available. The business process management means obliged to define a business process and connect systems to service won't talk to it directly. They should use E.S.P to talk to each other and execute the business process. Well, these are the principles that integration tool or E.S.P tools has to follow. Let's look at the entire End-To-End integration diagram with Papu. Well, by Opio is an ESB tool, which means being or supports all the above core principles that we just discussed, TOPIA or P0 has this ability to connect to any system using different connectivity types like FPP HTP, so very busy and many others. It can convert data from one format to another format like CSFI to XML and many others. It can transport data in secured manner using certificates or an encrypted format. It provides the monitoring tools, deployment and entire application lifecycle tools to manage the integration. Also, it has the capability to run the business process. I know you might be confused. What is the difference between PI and beyond? I keep seeing Pioppi. Well, let's deep dive into what is PI and what is bew and understand where it belongs in the NetWeaver family. You might have seen this happen of a diagram previously in the it was topic, just to recap, the Supernet River is a technology platform that combines many tools and applications together. It actually forms an ecosystem and it solves challenges around people, process and information. Well, that's what we learned, right. So pure, pure will fall under the process. Section of the Pinatubo family bill, as I described previously, stands for process orchestration and Paea stands for process integration. P0 is a product and a combination of BI, BPM and BRM. That's why Pyo is called as a combo product. Right. And it has many tools in it. And Buia is the integration tool or the hospital, which actually has a collection of many tools inside to build the interface, monitor the interface and run the interfaces. So when you see, you know, Akpabio, you actually means, you know, API and even the BPM, including the BRM, really terms of deployment of the AZAPO. So when someone's SBP runs or NetWeaver. Right, a Seppo uses Java only server from the underlying SFP as applications server to run and it can be configured to use my database like Maxsted, Bjorklund, etc.. Let's try to understand in detail about the CPU. So here in this diagram, I'm showing you how the principle is described. I know there is a new word, A which stands for advanced adapter in an extended AICS is a new term being used instead of B.I because of its history. First, ASEP integration tool was called as EXI then that he named it to PI and after that SFP started adding new features like Advanced Adapter Engine, which was easy and then it improved. That is easy to know at this stage and 86 is actually the same thing. The major difference between PI and X is that can be installed on Java plus ABAB, but X is only Java only installation. So when someone says a box, then it actually means it's a job only box. So using AICS instead of PI help us to explain things in the right way. You'll always be confused when we refer to PR because we don't know by as Harborplace, Java or Pierres Java only, but with AICS now we can differentiate piesse Java only. Well, I have a separate section to talk about versus speech. That's a complete topic just to talk about. What are the internal architecture, how it is being deployed and why there's a difference between pure speech. So for now, let's give the definition of a Seppo as simple as as BPM, as BRM. Also remember whenever in the lesson when I say X, it is just Java only installation and Seppo also completely a Java only installation. Next, let's talk about each of these components and then understand benefit like what is AICS and its benefit, what is BPM and its benefits and then what is BRM? You can now visualize the ASX as the ESB tool, which actually helps to integrate all the application services together, and ASX will have some tools and components in it and then we'll go to that in the later section. But understand that it will help to connect systems and act as an integration tool. Also, ASX does not have the BPM capabilities. It is the BPM component that has the BPM capabilities. Well, let me ask you this. Can you define or explain what is it called the SAP process orchestration. Why it is called orchestration. What is the real meaning behind it? Well, let me try to explain it in very simple terms. Well, if you really know the answers, like why the process orchestration is used for this integration tool, then get the comments section and share your definition. Well, let me give you a simple definition that you can remember and use it anywhere. Well, I have shared this slide in the previous section during the Israelis and. Let me do a recap what Castro means, group of musicians playing different instruments, orchestration in general, English means arranging two or more things together to achieve the desired results within the context of service. Arranging two or more services together to achieve a desired result is called service orchestration. And in the context of ESB service, orchestration is a process of integrating two or more services together to automate a business process. And now the SAP process orchestration helps to combine all the subprocess together to fulfill a business process. So people actually have this AICS as an ESB and BPM to run the business process together. Is Caldas process orchestration simple enough? Let me now go through the history of S&P. I'll quickly give you a very high level perspective from where the pie started, so, you know the terms that was used previously, but I'm not so particular about the dates and the features. You know, it's added that it's a different section to it. But but I want to focus on what are the Virgin numbers and what it is called us just to help you understand the term that was used previously, the number one, two, three listing out here. One means let's look at the version of pie and the two will talk about version of BPM and be him. And three, we'll talk about the process orchestration version, OK, which actually a combination of a mix with people. So first, let's look at basic evolutionary history. There's a complete history of PI and the X and its previous releases. And I want to show you the names like Excite by any X, which is now so you can see the different version numbers and the ear. And actually the tool named first it was called XXXI, then it is called S.P.I, somewhere around thousand five. And then now it is called as X.. Next is a composite enthronement. Well, we haven't talked about C as of now. Right. Well, just to understand this new word, composite environment is actually an environment provided by keeping it. We were to develop BPM and other stuff will remember that BPM in previous version Lecci and was called a CBM between ABAB based and did not you see at all. It was just an builtin workflow feature of Xieng, mostly on the ABAB stack. And I understand that Xieng PR was developed using ABAB and Java, so Cbeyond was using a baps over to run the business process and it was very integrated inside the PR tool itself. Well, with Pyo or when the ATX was released, ABAB was completely removed from the its internal architecture. So you invent Ababa's remove the Cbeyond was also moved from the abstract and then it was moved to a Java style BPM, which is called us in WB and this N.W. BPM completely done on this composite environment which actually runs on Java Engine. But your composite environment is generally used to develop and deploy DBMS. That is a reason in context of N.W. BPM Composite Environment Alignment was available from 2007. It's just that it was used by API, which were Java only installation. Also understand that soon AP will go away from this dual stack to single step to support many features like cloud integration. So it is important for you to get familiar with the composite environment rather than the CBB. Next is the overview of AZAPO evolution and history. You can see the support of the NPA together. That way, the P.A. has a capability to deploy on Java only installation. So once the EPA has this capability of Java only installation, it didn't had ICBM's at all. And that's when the city came in and helped and provide this BPO feature to TOPIA. And now with a Seppo, it's a Java complete Java only installation. That's why it's officially said that P0 is a combination of B.I plus N.W., BPM and plus BRM and then BPM and BRM runs and developed using this composite enthronement. Now let's look at the duties of all the three components, like what are the benefits and what does it help to do, like a BMB item, just to make sure you completely understand this component. This is the diagram that actually shows the system that they used in the enterprise company. They will have like serum portal, DB, Hajat, Finance and many other systems in the landscape. And without DSB, they make a point to point connection and make the integration very, very complex. Well, we understood that AICS can help to integrate all the systems and exchange the messages. AICS plays the role of a middleman courier and a translator. Now let's look at the duties of AICS when he helps to rout the messages to decide to system one to one, one too many, many to one. It helps to transform or convert the data from one format to another format. It also provides a secure transaction between two systems. It has the ability to talk to a provider or consumer in the language of protocol. Well, also, the monitoring tools are provided to do an end to end monitoring for audit purposes. It also maintain the version of the code and provide easy to develop new government. That's basically the duties of a that's no understand the BPM. Let's look at how PMA used BPM stands for business process management. This is an example of a business process used to approve a travel budget. The business processes started when the to submit a request for travel approval. Well, let's imagine it's NSA people. They say people can send a message to a text and then he can calculate the price. Then based on the amount, if the amount is greater than 5000, it can send an email to the manager to approve the request. Or if the amount is less than 5000, it can send a signal back to a portal stating that request is approved. The process is completed when approval is sent back to people. Well, if you observed the process, her steps and each step has to perform some kind of operation. So you need to organize all the steps in a sequence so that a business process is completed. Well, BPM actually are used to lay out all the steps in a sequence and execute in the same order. And BP still uses the expert connectivity and routing purpose and BP just used to execute the steps in sequence. Let's look at the benefits of the BP well. BPM supports human centric and system centric process, which means BP can wait and take inputs from human to proceed further or automatically decide the next course of action in the process. Now with BP, we can see what happened with the request in to end as one process will being a fix and BP's separated means he can handle the connectivity and routing and BP handling the business process. We can quickly adapt to business changes, right. We can also monitor from when the message received. Still, what response is sent back, including what are the business steps executed in one dashboard? That's basically the end to end process monitoring. Let's now look at BRM, which stands for Business Rules Management. Berrima rules. Yes, business rules that we can define outside the BPM. So when you have a business rule that can change any time, those rules we know need to define or hard code inside the BPM with BRM, we can define these rules and then BPM can use it during the process execution. So if the rules are not matched, then BP will adapt to the changes accordingly, like the travel approval request process. Just we have seen we can have the entire business process and now the BLM can have only the rules of amont limit that requires manager approval. In the diagram I have highlighted with a box, it is the rule which can be defined in BRM and it can be changed any time without doing anything inside. The BPM is so powerful, right? So when a company decide to manager approval is required for amount less than 2000 or maybe say greater than 47000, then super easy to adopt as business changes, all we have to do is just to change the BRM and the BPM. We actually accept that. Right. So let's look at the benefit of the BRM when we are compelled to separate the logic and the data, the logic and BPM and the rule in the BRM. It actually provides a central repository for all the business rules, right? It can change by business themselves based on the company's direction. And organizations are able to automate the business decisions, which means organization can now make the decisions of changing the business rules by themselves. All the changes that we are doing in the BRM are basically Real-Time and no update to the BPM required or no redeployment of the people. Quite typical, right? Hope you have got a fair idea on what is being A and B and as you say, just let us go to the last topic on the positioning of the. You need to understand where boys position in the entire system architecture, well, there are generally three layers in the system architecture diagrams. The top layer is the presentation layer, the middle layer upon layer, which is the integration layer. And the third layer is the application layer on which the third party or the backend systems are not available and the services are enabled in those systems. Let's understand each of Virgilia, the presentation layer is nothing but the medium through which the user can communicate, like mobile system or in a browser, it can also be called and while wilier also using which they use to communicate and p0 is the integration layer which helps to transfer the data from presentation layer to service enable applications, which is the backend layer. BU provides the tools using which players can interact with each other and. We have seen has BPM to run business processes. We are import rules management. He for integration like connectivity, routing and the services that has been developed in API or can be maintained, discovered and managed in the Enterprise Service Repository. I know we haven't discussed about enterprise service repository, but if you refer to the style section or the lesson we have talked about Udai. So Enterprise Service Repository is nothing but the radio and these services can be published, searched and discovered by using what can be seen as an YellowPages for services. The service industry wide and all the services in the service industry can be exposed where the player to the presentation layer can call the services in the Beeliar. But in turns, it depends on the backend system to complete the service because the actual implementation of the service is in the back end system. Beeliar is just an abstract layer service to the backend services. You can think it like a medium to transfer or call the service from the player or from the integration layer. The bottom layer is a service enabled layer in which the services are enabled in the application, which can be used to complete a job. You can imagine as a web service in each of these application at the back end application could be an ERP shadow finance system which offers various services. And these services within the systems like ERP and Hajat is actually implementation of the logic. So understanding the positioning of people in the overall system architecture is very important when you're trying to build an interface and when you're trying to define even the architecture of the interfaces, you know where we should put what I do not be confused with the presentation layer, integration layer and the backend layer. So people use the integration layer. Right. I hope this will give you a solid understanding of where and how the bill is being laid out in the entire system architecture. Well, that's the end of this topic. If you have any questions regarding the topic of discussion or any clarification on this topic, please feel free to join the discussion in the forum where I can spend time to answer your question. You can always be just a supporter of the refugees dot com for any kind of questions without hesitation that I end this presentation and thanks for listening to a section of the Boston Globe understanding.