hello and welcome to this course on process integration and process orchestration over the next couple of days and sessions i will be walking you through what is process integration what is process orchestration what is the difference between process integration and process orchestration and also be covering a lot of hands-on around various scenarios in in process integration and process orchestration the way this uh course has been structured uh is that uh we will walk you initially through a couple of slides uh that would be the theory uh while we have tried to curtail the theory to a mini as minimum as possible unfortunately there are few things that need to be explained theoretically uh before we can go and demonstrate and do hands-on in the system so so the first r or two or so would would include a theory understanding what is pi what is pi what is process orchestration how do the various components of pi work uh how the how do the various components of pi interact with each other and and so on so once we are done with with walking you through what the various components of pi is then we will look at each individual component of pi and then start uh using these components to to to work on the hands-on exercises okay so with that uh we'll kick start uh this exercise um where we are now going to walk through uh what is pi so at a very high level we are going to look at three important and essential components you know hey what is process integration right give you an introduction why is process integration uh needed uh in in the context of customers what role does pi what role does pi do we would also be looking at what are the various components of pi uh this is something that that you know by the end of this course you would you would remember even without having to look at theoretical slides but for you to start off with uh this is essential to understand what are the various components of bi and and you know which component is used when and and finally uh in in this session what we will do is we will wrap up with what are the architecture options of pi i'm sure a lot of you have heard about are wondering hey is this course process integration is this course process orchestration what is the difference between process integration and process orchestration is there any difference at all for that matter between process integration and process orchestration all of those questions would get answered when we look at the architecture options what are the architectures of pi uh what is a single stack pi what is a dual stack pi and so on uh rest assured the idea of this is uh to to make sure uh when you're done with this entire course you not only understand the theory behind pi but also are able to do sufficient amount of hands-on so with that said uh let's let's look at what is what is sap pi right uh sap process integration uh is is a part of the sap netweaver suit so people who are new to the sap landscape sap netweaver is is the overall underlying platform in which most of the sap components run so sap netweaver has multiple products in it one of the products is sap pi or sap process integration uh sap pi is is is fundamentally an enterprise application integration platform and what i mean by an eai platform is uh pi is used for integrating applications uh it could be a sap application it could be a non-sap application so sap pi is your is an eai enterprise application integration platform it is also called an enterprise service bus and esb sap pi enables you to integrate sap and non-sap applications now what do i mean by integrating sap and non-sap applications right so if you look at this image on this right right we have sap pi in the middle in the center and then you have multiple peripheral applications it could be an sap ecc 6.0 application it could be a third party payroll application it could be your mainframe applications you could have multiple other integration solutions involved now all of these applications can can technically talk to each other directly but the role of pi is to provide a much more governed and sophisticated means of of integrating applications so you might be wondering uh hey yes i understand pi is an integration platform uh but then what a value addition does pi do why you know what is the role of an eai landscape ai tool in a landscape so let me explain that with an ex example so let's take a case of let's say an sap ecc environment and sap environment i am not going to write sap out here let's take that this box is sap now there's a requirement where you know every day uh this sap system needs to send uh the you know employee data to a third party payroll system so this is this is one of the integration requirements that exist in a customer landscape and and the requirement is you know what uh ecc needs to create a file uh and that file need will be then picked up by this particular third party system through a patch program so if you're an if you're an app programmer if you're a java programmer you would say hey you know that's going to be very simple i would write a program in sap ecc that's now going to do whatever extraction of the data it needs from whatever sap tables and then i can create the file to basically what i can do is why do i need pi my ecc environment can directly integrate with this third party system by just writing an ab program or a java program or whatever programming that is required so let's say yes that's absolutely possible bi is not going to add any value here so similarly any any customer landscape is not just going to be one application any customer landscape will be multiples of hundreds of such applications and each application typically needs to talk to each other so today the example that we saw where ecc is going to send a file to a payroll system uh tomorrow there could be a requirement that this there's another requirement where some data needs to go from the system to the system from ecc to this system from this system to the system uh and so on and it need not be just one interface right there could be multiple interfaces multiple programs required so what's going to happen is as as the as the con the customers landscape becomes complicated as us things begin evolving you would end up with what is called as a spaghetti model like if you look at it i've kept it very simple but if you look at it if there are hundreds of such interfaces imagine a customer landscape where there are hundreds to thousands of such interfaces what's going to end up is you would end up with what is called as a spaghetti model and if you see this this is now beginning to resemble a spaghetti where data is is flowing all over and all across now can you imagine if this is how your your customers landscape is if this is how data is moving what what if one program needs to change what if this application is getting upgraded you would not know what are all the programs in your landscape that is sending data here you know it is it is eventually going to become a landscape that becomes much more complicated much difficult to upgrade much difficult to maintain because what you have is point-to-point connections that end up becoming what we call the spaghetti or multiple connections and with no structure associated to it what does pi do in this case right how does pi help so let me show that now let's assume that pi is sitting in the middle here and you have all these applications that we were talking about right just before all of these applications that are that we were talking about all of these applications are going to be here and now instead of all these applications talking directly to each other these applications are going to talk to pi and pi is going to then forward the message or you know translate the message connect to the system and so on so that way what you would end up with is not a spaghetti model but much more as you can see on this picture a much more beautiful picture even if there are hundreds of lines going out here it's going to be a much more evolved model much more uh supportable model where even if if this application is upgrading you would be able to say hey there are 10 interfaces that are running in pi connecting to these applications and do an impact analysis of that so the underlying idea of an enterprise application integration or enterprise service bus is is that it enables you to integrate all your applications in much more uh governed manner in much more a streamlined manner rather than just build point-to-point connections okay so let's go back to our slides as i was telling pi is used to integrate sap and non-sap applications and as you can see here you can have hundreds of applications that are connected to pi uh your your your application developers on the sap side need not worry about you know connectivity and stuff like that all they have to do is they write their programs that connect to pi and pi takes care of connecting to all the third party applications you you have a much more sophisticated and you have a much more cleaner architecture that way pi is used for both a to a and b to b integration what do i mean by a to a integration oops sorry i'll go back what do i mean by a to a integration right a to a integration is nothing but application to application integration just look at this box assume that these are all the applications within one particular customer's landscape right in that case all of these applications within the customers landscape talking to each other is called application to application integration what you see here this is a firewall basically if data has to flow over the internet what if you have another customer uh you know having a similar set of landscape similar set of applications and so on so if two different corporate entities have to talk to each other let's take the case of you know a conglomerate a big conglomerate uh like unilever right uh and let's take another conglomeratemate like walmart uh you know when walmart needs to purchase uh place a purchase order walmart is not gonna be picking up the phone and talking to to unilever directly walmart is going to trigger the purchase order electronically and walmart is going to do that through their middleware and obviously now the data has to go over the internet electronically to unilever so so this example where data is flowing across corporate entities over the internet that kind of integration is what is called b2b integration or business to business integration when the integration happens between multiple businesses that kind of integration is called b2b integrations a to a integrations just to summarize are integration that within happens within a corporate landscape uh what else about sap pi right sap pi runs on sap web application server so if you understand the architecture of sap netweaver all components on sap netweaver uses sap web application server and similarly pi also uses a sap web application server this is some a slide where i would be spending a lot of time on uh at least in the in the initial stages it might be a little overwhelming for people uh but rest assured uh as you start doing the hands-on you would start using all of these and and over probably the second or the third hands-on that you do you would have used all these components and you would have been you would start becoming extremely comfortable with these components but then it is important for you to understand how pis architecture how pi's components what are the various components of pi which is why this slide is is gonna be of multiple it's gonna be of importance okay so just give me a second i'm gonna do this do this okay so let's sorry go back yeah so we will start from the bottom left and then keep moving uh rightwards okay the first component of pi that i would like to talk about is what we call as the sld or the system landscape directly so if you're from a basis background or if you're from a solution manager background you would already be aware of what is system landscape directory or sld but for you know but for those who who have no background to it do not worry and sld is nothing but uh remember the underlying idea of pi that it is a central application that is going to integrate with multiple applications in the landscape so for pi it is essential to understand what all systems are in the landscape because eventually pi is connecting to multiple different systems right so the sld or system landscape directory is is a component of pi that tells pi what are all the systems that are there in the landscape in the customer's landscape when we talk about systems uh it could be your ecc system it could be a third party system it could be your [Music] sap portal system it could be a cloud system like people saw like success factors at the end of the days the system landscape directory or the sld provides information of what a customer's landscape is and as the name implies it is directory when we talk about directory it is like your yellow pages or where you have the listing of all the systems in the landscape so the idea behind sld is uh all systems in your landscape register themselves to the pi sld so pi understands what all systems are there in a particular customer's landscape and is able to then connect to them understands what are their products what are the software components that it has and so on so at this point uh what is essential for you to understand is sld is nothing but like a phone book that contains uh all the systems that in a customer's landscape register themselves on the sld so that pi can use that information uh when pi is exchanging messages with these systems so sld is equal to your telephone directory is equal to all the systems in your landscape okay good so we will move on to the next component this is what we call as the enterprise services repository uh it was also called integration repository in the previous releases of bi but we would use what is the newer term uh and it is the integration repository is now called the enterprise services repository uh enterprise services repository is the is the design time of pi so what i mean by design time is this is where we do all the uh design term work in pi uh any up because you're integrating uh applications you need and you're exchanging data between systems you need to tell hey system a is going to be send me data in a particular format and system b expects the data in a particular format so all that kind of definition that says what is the data format going to be what is the mapping going to be pi is not just integrating applications by connecting to each other but it also can translate data from one format to another so an sap system can send an idoc to pi and pi can then convert it into a into a flat file and send it to a third-party system so all that level of information where you're doing the design time work happens in the enterprise service repository uh integration directory is the component of pi where you're doing all the configuration what i mean by configuration is whatever work you've done in the enterprise servers repository those are all individual building blocks all those individual building blocks will get connected to with each other in the integration directory okay so this is what we call as the configuration time and the enterprise service repository is what we call as a design time so you design your development here you design your interfaces here you configure your interfaces here when i say configuring i if you need to connect to an ftp server you provide the ftp username password out here if you need to connect to an sap system you provide the sap systems username password out here and so on okay with that we would move to what is the the heart of pi uh which is the integration server the integration server is what we call as the runtime of pi okay when we say the runtime this is where the messages get processed this is where whatever is being sent to pi will get processed so the integration server is the runtime of pi and this in turn contains three essential components the central adapter engine the integration engine and the business process engine the central adapter engine is nothing but the connectivity layer it contains all the adapters it it so basically because pi needs to talk to multiple applications pi needs to support different types of connectivity options so that is done by the central adapter engine the integration engine is where the the main pipeline of pi gets executed and the business process engine is where a specific component of pi called ccbpm will execute okay okay so let me do one thing all right so let me just for the ease of use here i'll just say okay so we are back as we were saying the integration server is is the component which is the heart of pi which is the runtime of pi and this contains three different engines one is the central adapter engine where all the connectivity happens this adapter engine runs on the java stack of pi then you have the integration engine this this is where the pipeline opi gets executed and this runs on the ab stack and you have a specific component called business process engine that that is used for what we call as a cc bpm at this point this is sufficient this information is sufficient that business process engine is used for just ccppms okay uh i'm not going to go into uh these slides at this point we will revisit them uh subsequently but just to summarize before we go on to these two parts because that's been a lot of data that's been told your system landscape directory is is equivalent to the white pages or the telephone directory where all these systems in your landscape register on the sld the enterprise service repository is the design time of pi is is the component where you do your design time work your integration directory is where you configure the interfaces so this is your configuration time and the integration server is the run time enterprise service repository equal to design time integration directory equal to configuration time and integration server is equal to the runtime of pi and when we talk about runtime the integration server it has three components the central adapter engine that does most of the connectivity the integration engine that has the pipeline and the business process engine where the ccbpm will execute each of these engine does different actions each of these engines have are monitored differently so which brings us to these components the runtime workbench and the configuration and the monitoring these two are what is a part of the monitoring framework so if you obviously because pi is exchanging messages from one system to another system it is essential to be able to monitor what happened to a message uh did an idoc from sap get delivered to the downstream system did a file from a third-party system get delivered to sap all that amount of monitoring happens within these two components which is the runtime workbench and the pi monitoring okay so i'm not going to talk about uh the non-central adapter engine at this point in time we will revisit them probably closer to the end of this course when we are looking at the various architecture options of pi if you and finally if you look at the bottom of the screen you have an sap system you have a service provider you have service consumers what are all these these are all the various applications or the different types of applications that pi can connect to and that is that connectivity happens via either the integration engine or the adapter engine so pi can connect to an sap system it can connect to a third party system it could be a web service provider it could be a web service consumer it could connect to a file system a database system a james and so on okay so this is what at the end of the day is the heart of pi you will be using each of these components of pi extensively and when i say extensively this is where the development of pi happens this is where you would these are the components three components where you will do all your development these are the components where you will monitor your message see hey is my development okay is it working fine and this is where you would do the monitoring to see in the real run time what really happens okay and these are the various kinds of applications that pi can connect to okay so now that you saw various components of pi what are the various tools that you use to connect to to these what are the various tools that are used to connect to the components of pi right uh we will stop start from the bottom system landscape directory again i i will at this at the risk of being repetitive so that i'm just repeating it so again it registers yourself system landscape directory is your telephone directory is equivalent to your telephone directory it contains all the systems in your landscape because pi is connecting to those systems system landscape directory is accessed via a browser so you can use an internet explorer you can use your chrome you can use your firefox uh there are certain restrictions around which version of uh browser supports which version of pi but at the end of the day the client or the front-end tool that you use to connect to the system landscape directory is a browser the enterprise service repository is your design time of pi where you design your interfaces so and what are the tools that you use right sap provides three different tools that you can use you use a java based client called integration builder it is a java web start based client so in in 90 of the hands-on in 90 of the work that we do in this course we would be using the integration builder which is the java web-based web start client uh i will show you how to launch this do not worry at this point just remember that the enterprise service repository is launched using a java based java web start based client as long as you have java installed on your missions you will be able to launch the enterprise service repository uh you also have you can also use a browser based for just browsing through the enterprise source repository and you can also use an sap netweaver developer studio to to connect to the enterprise service repository the nwds is a newer feature that that you know all the work that you can do in the java web start is also supported in the netweaver developer studio but for this course we would predominantly be using the integration builder or the java web-based client the integration directory is typically accessed using the java web start again the java based client which is nothing but java web start the runtime components of pi be the adapter engine the integration engine or the business process engine is typically accessed using the sap gui and the runtime workbench basically your monitoring framework is accessed using the browser so this could again like i mentioned be any of the browsers there are certain compatibilities that you need to take care of but in principle most of the browsers are supported okay so what else is there in the pi component overview we'll now look at the enterprise service repository uh so within the enterprise service repository if you look at it these are the various types of objects that you would be building within the enterprise service repository at this point i'm not going to go into each of these objects uh i'll just at a very high briefly touch up on these objects and then we will when we are building them on the system you will be able to understand them but to give you an overview within the enterprise service repository which is which is what what is the enterprise service repository it is the design time of pi and it is accessed using either the java web start or netweaver developer studio or it can also be used access via web ui but typically in this course you're going to be using the java web start and the enterprise service repository contains various different types of objects you would create what we call as data types what we call as message interface or service interfaces there are different types of editors that are called scenario editors so you would have a data type editor you would have an xpath editor you would have a mapping editor all of these in the enterprise service repository because it is the design time of pi you would be building individual objects that are going to comprise your interface uh so all of these objects is what you would be designing and building in your enterprise service repository using different types of editors one another thing the enterprise service repository is dependent on the system landscape directory so what is the system landscape directory it is the sld which contains all the systems that are there in your landscape uh it is your it is your telephone directory of your lan of your of your of your customer landscape so but from a systems perspective so so the enterprise service repository reads what we call a software component version from the uh system landscape directory again do not worry about this this is just a theoretical information we will be seeing how the software components are created in the sld and how they are used within the enterprise service repository you can also connect to an sap system and import structures what we mean by structures is when you're exchanging messages between multiple systems there would be let's take the case of an sap system sap already has rfcs bapi's idocs all of that right so that is a predefined structure that sap provides so you can connect to to an sap backend and import all the sap structures into your enterprise service repository one another important stuff about pi or one another advantage of pi in the context of sap customers is sap provides content for the enterprise service repository that can be imported into the enterprise service repository so let me take an example what if you have an integration uh of an srm system between uh mm and assist system so these are two separate sap systems so what sap does is because both of them are standard sap systems sap and this system needs some kind of integration sap also provides the enterprise service repository content that you can just import into the esr and once you import into the esr all you need to do is just configure these interfaces so no real build or development of an interface interface is required similarly let's take the case of another sap product um let's take the case of sap ecc 6.0 that needs to now be integrated with let's say an sap cloud based uh solution like success factors success factors as you would all know is is sap's leading hr solutions so what if you need to now integrate sap ecc 6.0 with sap successfactors again both of these are sap products so what sap has done is sap provides you with enterprise service repository content that can just be imported directly into pi so that you know from an interface development perspective all you're doing is configuring those interfaces so what these kind of content that sap provides is called pre-delivered integration content so the idea of pre-delivered integration content is that sap is building the content you do not need to build anything in pi the only thing you would do is config import that content into the enterprise service repository and after you import it into the enterprise service repository you would just configure the interface in the integration directory okay again we've already touched upon it you use a browser based web ui you can use a netweaver developer studio uh which uses eclipse or you can use java web start to access it what is integration directory your integration directory as we had just touched upon a couple of minutes ago is your configuration time of pi so when we talk about configuration time all the objects that you build in the enterprise servers repository those objects will get used in the in the configuration time or in the integration directory and you have multiple configuration editors and wizards that can be used to define how an end to end interface is going to execute in the runtime in pi so i'm not going to go into each of these boxes we would look at them individually when we are building the interface but what you need to understand at this point in time is integration directory is your configuration time you have multiple wizards you have multiple editors that sap provides these are all of the shelf editors of the shell wizards that you would be using to do your configuration in pi okay so you what you use you use java based graphical tools that are started using java web start we will now touch upon you know just one concept uh called manage web service and basic web service so before we go into manage web servers and basic web servers what i want to explain is what is the concept of a web service web servers as the name implies is anything that is accessible over the web or over the internet or over the browser and that as it is a service has a request and a response so typically sap provides multiple web services and sap ecc pro environment provides multiple web services what you see here sap netweaver as application server or app application server you know you can always access a sap web service directly through a third-party web service client right you do not need to use pi for that and that kind of a web service is called a basic web service now typically what you would do is you you would not want to expose everything in ecc directly to a third-party system why remember the spaghetti model that we had talked upon if you start opening up point-to-point connections your entire landscape integration landscape is going to become a mess and which is why the pi comes into picture or the enterprise service runtime comes into picture and what you do here is uh you know you expose the web server that is there in ecc through pi and you know that becomes a managed web services so the third party systems instead of connecting directly to ecc will now connect via pi and then pi would in turn connect to ecc or it can make us a call to another third party system or to any other sap system and so on and those components are called the managed web servers one last thing that i wanted to touch upon in the pi components is the business process engine remember we had touched upon business process engine what was the business process engine it was used as the runtime of ccbpm okay so let's take this example we have business system one business system two and business system three what do i mean by business system business system is nothing but an end system right you have one end system one an end system two and an end system three and because any system and any it system in a landscape does some business functionality they are called business systems and what if the requirement is all these three systems will send messages to pi and then pi needs to combine all the three messages wait for three different messages from three different systems get these collect these messages combine them and then send them to a third fourth system right if you have to orchestrate a business process like this the competent that you use is called ccppm ccbpm stands for cross component business process management again do not worry about it we will be covering this in detail in our subsequent sections but ccbpm stands for cross-component business process management and the idea of a ccbpm is to enable you to orchestrate a business process in pi for stateful interactions and what do we mean by stateful interactions is when pi receives message one it knows that it has to wait for message two and message three it has to persist the message until all the three messages are received so that kind of uh persistence or that kind of uh of an interaction or a message orchestration has been pi is called a stateful interaction okay so so for to build such kind of business processor to build such kind of integration patterns in pi we use a component that is called ccbpm that is what is called the design time component and that ccbpm runs in the runtime on the business process engine and the ccbpm are built using a graphical modeler so there is an editor within the within the enterprise of service repository with which you design your cc bpm's okay uh the ccbpm is based on an industry standard called bpel uh you know ccbpm enables you to design and model your interfaces and so on will not spend more time here uh very finally this is something that is very important uh uh the next section of next 10 minutes is probably very very important because this is going to now touch upon a question that i asked at the beginning of the session saying hey is this course a process integration course or is this course a process orchestration course what is the difference between process integration and process orchestration those questions are now going to be answered in this session before that let's just talk about a little bit of the history of pi i'm not going all the way back to 2005 2004 when pi was launched but just when were the latest releases of pi launched pi 7.31 was launched in november 2011. ps 7.4 was launched in april 2013 and the latest version of pi is pi 7.5 which was released us late as november 2015 right with pi till pi 7.11 a lot of features were restricted when we you know there were a lot of restrictions on the product suit but with pi 7.31 and pi 7.4 what we brought about is a single stack execution of pi so what i mean by a single stack execution of pi is that previously pi's components needed mandatory uh pi installation required mandatory and abstract and a java stack so what do we mean by abstract in a java stack a pi installation would have an ab component and a pi installation would have a java component but with pi 7.31 we brought in a new psap introduced a new installation option for pi that was called a single stack or a java only pi what that meant is all the functionality that was being done on the abstract api was now possible on a java only pi which made the customer's life easy from a monitoring perspective from a hardware perspective and so on so what you need to understand is from pi 7.31 you have two installation options of pi you can have a dual stack installation a dual stack installation is an installation where you have both app and java combined together or you can do a single stack installation of pi which is nothing but a java only pi right and the java only installation of pi was called an advanced adapter engine aae it was also called adapter engine extended aex so the idea being that sap as we all know historically keeps changing the names of its components so so both of these components means one and the same adapter engine extended aex advanced adapter engine aae this is nothing but a single stack or a standalone installation of pi a dual stack installation of pi is just a bap and as a is a combination of both ab and java installation of pi okay so so far all we've been talking about is process integration i have not touched upon process orchestration as yet but i want to make sure that all of us understand that process integration is nothing but your enterprise application integration platform or eai platform from sap that enables you to integrate multiple sap and non-sap applications sap pi had mult has multiple components we had seen all those components beginning from system landscape directory to an enterprise service repository to the integration directory to the [Music] integration server right we had seen all of that and now what we are talking about is that from pi 7.31 sap introduced two installation options for pi one was a classical installation option that had both abstract and java stack the other was a single stack installation of pi where it was a java only so only a java stack was used and that was called an adapter engine extender and the or the advanced adapter engine and all of this just holds true for pi so what is process orchestration right so process orchestration is nothing but java only pi or a process sorry i'll correct myself so first what i would like to talk about is what is process orchestration in that case process orchestration is a combination of three separate sap products that have been bundled together and licensed and now sold as a single sap project product so process orchestration is nothing but a combination of aex adapter engine extended what is adapter engine extended it is your java only api right so process orchestration is a combination of your java only pi netweaver business process management and netweaver business rules management so these three products of sap were combined together licensed and frameworked as a single product called sappo okay so a process orchestration is nothing but a combination of three sap products a java only pi which is called aex sap business rules management and sap business process management so sap process orchestration is again does it have does sap process orchestration have an abstract the answer is no sap process orchestration is a java only product but it combines three different products right a single stack java only pi a business process management and a business rules management so to summarize what are the various architecture options of pi and po pi is nothing but process integration and process integration can be installed as a dual stack installation which is but an app and a java installation or a java only installation which was called an adapter engine extended or aex another evolution of process integration was called process orchestration where sap combined sap java only pi business rules management and business process management into a single product so a process integration is not process orchestration process integration and process orchestration are separate products from sap but process orchestration has all the features of process integration plus some additional additional features so you need to be aware that from a licensing perspective process orchestration has separate licensing process integration as separate licensing but from a features perspective process orchestration includes all the features of a java only pi and additional features of network business rules management and business process management okay so with that uh we come to the end of the first set of theory that we wanted now from this point on uh we will start doing much more hands-on where in the subsequent discussions what we would be doing is we would be uh looking at the system landscape directory or the sld we would be building some stuff on the sld and then we would be moving on to the enterprise service repository and the integration directory to summarize what we've looked at in the in the past 50 odd minutes uh we've looked at where at a very high level what is pros and for that i'll move on to the agenda slide so we can we can summarize it from there we had introduced you to pi pi is an enterprise application integration platform we had talked about why pi is important remember the the the spaghetti model that we spoke about where uh you have you know multiple systems talking to each other uh in a point-to-point connection will not will cause chaos and that's why pi is introduced as your enterprise application integration product then we looked at the various components of pi to summarize the various components the most critical ones system landscape directory it is your telephone directory all the systems in your landscape register themselves on the system landscape directory enterprise service repository it is your design time of pi enterprise service repository is the design time of pi where you design your interfaces it runs on the java stack it uses the java web start you can use the netweaver developer studio but for for this particular 90 of this course we will use the java web start integration directory is the configuration time of your pi server is that correct yes integration directory is the configuration time of your pi server where all the individual components that you build in the enterprise servers repository are combined together to form an end-to-end interface then you had the runtime of pi the runtime of pi is called the integration server which contains three comp components or three engines the adapter engine the integration engine and the business process engine okay and then uh we we we touched upon at a very high level each of these components what all do they contain uh we touched upon that and then we looked upon the architecture options of pi uh what is a single stack pi what is a dual stack pi and what is the difference between process integration and process orchestration okay with this we come to the end of our first session we will now move on to the next session to uh in the next uh slides where we would walk through the sld and then we will start building our first interface together okay awesome so i will see you in the next session soon