🚀 Add to Chrome – It’s Free - YouTube Summarizer
Category: N/A
No summary available.
00:00
hello everyone thank you so much for joining this is day four of oricle integration session and in this session we are going to create our first AB driven integration so in previous session we already done with creating the scheduled Integrations and where we
00:16
added few parameters to the schedule Integrations so now this in this session we will we will have to create Aben integration but before going to cover that creating ABD integration uh I just have to cover few points so that it will help us when we will go for creating the
00:31
uh AB driven integration so for that first we will cover that adapters which we already discussed but just for brief here we will discuss on that part and then we will go for connection that uh the adapters we are going to use while creating the connections and there is one point is like connection roles so
00:49
what what is connection roles and why we are using that connections roles while creating the connections for a specific adapters that we are going to discuss and then we'll create our connections and then we'll create create our Integrations so we'll check that why we require connection while creating
01:04
Integrations for when we are going to create up integration we'll see one by one so as we already discussed earlier that adapter is something that which is going to Define that which third party system we are going to connect so as OIC is a middleware application so in case
01:21
of OIC whatever application it can be it can be Oracle Fusion application or it can be Oracle EBS or it can be Oracle database Bas or ATP database anything every system is uh third party system in front of OIC so when we are going to
01:38
create integration so in that integration there can be two situations that the one situation can be that we have to invoke that third party system and another situation can be that our that third party system is going to trigger our integration so when we are
01:54
saying that trigger our integration it means that our integration will having the flexibility that that uh that can be provided to the system so that they can invoke our integration so most of the time in our Integrations so just like in sedule integration when we are creating
02:09
schedule integration we have one end point that's called schedule right the starting end point at the very first end point that schedule and points help that schedule Integrations to initiate or to execute the start the execution so when we'll go for abs integration I will I
02:24
will show you that in AB D integration we are not going to get any end point in that canvas so that's that's the reason we require minimum one connection to AB integration so that's also we will we will cover in the session only so that we'll get to know that the use of that
02:40
connection over there so now like now it's time for connection so obvious like for each and every in adapters that adapters we are not going to directly use in OIC adapter is something that they are just going to tell us that which thir part system we
02:56
are going to connect but how we will connect to the thir system that will be defined in connection so while creating the connections we have to use the adapter so that that connection can identify which third party system we are going to connect and what is the connectivity details like the we have to
03:13
provide the user password only to connect with that or do we have any VPN or any agents required for that connection or any firewall or any wh listing and all it's required to to connect with the third party system so everything is going to Define in the connection only so so connection helps
03:30
integration to connect with that to connect with that external system or any third party system and in connection we are using adapters that is going to Define that that connection is going to connect with which third party system for example we have to connect Oracle
03:46
database so that's why we will create connection Oracle database connection but while creating the connection we have to select that adapters as Oracle databas same as we have Oracle Erp Cloud adapter Oracle HCM Cloud adapters we have ATP adapters that helps to connect
04:02
with that database or that that connect with that system so that's we are going to create so once we will go for creating the connections while creating the connection mly like it will ask you to select roles of that connections so type of connection is something
04:17
different than the roles of connection so when we are saying the types of connection so whatever adapters you will select that type will be for that connection for example I selected adapter as a ATP adapter so our type of that connection will be AIC type
04:32
connection but while creating the connection it will ask you three options for the roles you can see the one is trigger another one is invoke and the last one is trigger and invoke so there is differences between Trigger and invoke so in any integration there will
04:49
be only one trigger connection so when we are saying that trigger connection so that trigger connection is going to help to initiate the integration or the trigger connection will help integration to execute so for example we created our integration and that integration we want
05:06
to execute on a specific time so we need something in our integration so that that integration can be a started that's why in schedule integration we have sedule end point and that sedule end point obvious we are going to use SED over there in case of ab integration or
05:24
in generation three we are saying that application integration so that application integration here you can even you can see in that screenshot also right so once we will go to create integration we will be able to see so this is the screenshot when we are created AB integration and that AB
05:39
integration doesn't have any any end point in this canvas so like how integration will start at this point that's why we require trigger connection trigger connection is something that is going to help integration to a start so in our case we are going to use
05:56
uh rest connection rest connection as a trigger connect Trier Ro connection so that when our integration will be completed that our integration will be considered as a rest end point so one of the reason when we are using AB driven integration to expose our OIC as a risk
06:14
services so most of the time like if you heard about that we have one bbcs page or any third party system having their web pages and all and from the web pages they want to execute our OIC then how it will be possible to execute our o from
06:31
their system so using that ABD integration it's possible so while creating we will create ABD integration and while creating AB integration we will select rest end point as a a rest connection as a trigger end point so that our integration will be exposed as
06:47
a rest API and obvious like app D integration provide flexibilities to add the request perod in integration add the response perod in our Integrations so when we are saying that request pad of that integration it is something that
07:03
when we will run the integration so what value we are going to pass that value is known as request payload and when that integration will be executed and what value we are going to expect from that integration so that unstructured values like just like it can be xmls or Json so
07:20
most of the time we are going to use Json format only because that Json is too much easy than XML to identify to to just create the payloads and all and in our example also we are going we will use Json only so when we are creating
07:37
integration in a such a way that while running the integration we have to pass some values that values is known as request payad and when integration will be executed and in once that integration will be completed we are going to expect some values in return that that values
07:52
is known as response payload so it is same like apis so any of the API rest API soap API or of web services you you executed or you worked on earlier so while executing that API you are going to pass some values right and in
08:08
response they are returning some value so that kind of things we can configure in our OIC and that's why we required at least one trigger connection so I will show you that one also so in our OIC or in our Integrations when we added trigger connections so as I told you one
08:24
point that in our integration there will be only one trigger connection we cannot have more than one trigger Connection in OIC this is the point related to trigger connection if you will move to the next the second role type is invoke so when we are saying that invoke connection so
08:40
all these adapters we will use while creating the connections so when we want to invoke third party system or any Legacy system or external system from OIC for example here you in the screenshot only you can see this is our integration we created from integration
08:57
only we want to invoke the ATP data datase to insert few data so from OIC only we are going to invoke ATP Services right so that's why it that's why OIC provide ATP connect ATP adapter so we created Connection by using ATP adapters
09:14
and that connection we are going to use in our integration so in in this type like in the case when we use this connection that connection is considered as a invoke connection so if suppose we will create trigger connection and we want to use the trigger connection here so it will not be possible to use a
09:30
trigger connection here because in a integration there will be only one trigger connection and that trigger connection will be used in very first of that integration or that the first as a first end point only so that using that trigger connection trigger connection we can initiate our
09:46
integration or we can start our integration in our integration we can have multiple uh multiple invoke connections so invoke connection is simply that when from OIC when we have to to call any external system using
10:03
risk services or using web services or by using that connections available or adapters available in the system so that kind of things it will be considered as a invo so the calling that ATP and point is one example another can be that from
10:18
OIC we are going to call the VIP report of fusion right and we want to call the VIP report data into OIC so that's why we have soap web services so that it will return the vi data so that soap web services when you want to execute from OIC that will be considered as a invoke
10:36
that we are going to invoke that soap we services from OIC at the time we will create soap connection as a invoke Ro type connection and yes in last we have the third role type that is trigger and invoke so just like trigger the trigger
10:53
connection we can use only in a starting of the integration in connection we can use only in between the integration not from a starting in and it can be in last of that integration it can be in midle of integration anywhere so for example
11:08
you want to create a connection that that connection can be used as a trigger also or that connection also you can use to invoke any apis so at the time you will create that connection as a trigger and invoke Ro type so that that is specific connection can be used as a
11:26
trigger to that integration or that can be used to in invoke that connection invoke that services so that all we are going to use one example yeah one example for trigger and invoke will be one example for trigger and invoke will
11:42
be that we have rest API to create AP invoices so we are going to create one rest connection that rest connection we we provided that URL for orle Fusion where we want to create the AP invoices and we want that a specific single
11:59
connection only to trigger our integration and two to invoke that AP invoice rest API so at the time we will create that connection as a trigger and invoke so that that connection we can use as a trigger to that integration and
12:15
also we will use that we can use that connections to invoke the rest API of Oracle fuser so at the time we will use this kind of rules so in OIC we have total three roles for connection that Ro is trigger invoke and Trigger and invoke
12:33
so the basic differences between Trigger and invoke is in integ in a single integration there can be only one trigger connection used but in a single integration there can be multiple invoke Ro type connection we can use that can
12:48
be that in our integration we can use uh soap trigger soap invoke connection we can use rest inv connection we can use ATP connections to to insert data into database table we can use ATP uh we can use uh FTP invoke connections to insert
13:04
file or place file over file server to get the file from file server that kind of things we are going to work so it's all about or connections role so once
13:20
we uh yes that's why I told you right so that's why I've given one example that we have one rest API that rest API is going to to create AP invoices in Oracle Fusion application and our our point is to create integration that we want to create one integration that integration
13:37
will take some values uh while running that integration and B on that value it will create AP invoices in system so as is as uh like as I told you that for invoking that RIS API to create invoices infusion we requir risk connection so that connection we are going to use in
13:54
OIC as an invoke that's fine right same connection we can expose or we can use use to initiate our integration to start our integration to use as a trigger of that connection so in this time there is no need to create two separate connections so we will create only one
14:10
single connection and that rule we will provide to the connection as trigger and invoke this trigger and invoke so that that a specific connection can be used to initiate our integration just by adding as a trigger end point or can be used as a invoking the rest API as a
14:26
invoke end point or in between anywhere so that's we are going to work on so the same example here you can see I just taken one example to create a rist connection so in this rest connection we given this Fusion URL this is the fusion application URL and here we provided the
14:43
user ID and password for that so the same connection we can use in our OIC to invoke the rest API of Oracle Fusion just providing the resource URL here here in that integration only and the same connection we can use to initiate our integration so that kind of things
15:00
we can we can work in in OIC so now let's let's move to that OIC instance where I will show you that how we can create connection and obvious before going to create connection so if you will see let me open this instance twice so that I can just show you the
15:15
comparison between rest and so so here you can see I'm going to create the rest uh create that schedule integration so I'm just going to give access I will delet it l so this isle I selected so when selecting any schedule
15:30
kind of integration that schedule integration is by default providing us Endo that end point is nam as schedule Endo this is trigger Endo right so this is the trigger Endo using this Endo this schedule integration is going to execute
15:46
going to start the same way if we will go and will try to create AB driven integration here that is application type integration xx03 or 02 so once we will try to create so this in this type
16:01
we are not able to see any end point here so that's the basic differences in schedule integration and the ABD integration and now that how our ABD will integration will execute right so without any end point that o integration
16:17
will not be executed that's why we have to add at least one trigger Connection in AB integration so if you will see another differences is this is our schedule integration and in the schedule Integra if you want to add another connection what we can do we can just navigate to
16:33
the right hand side and this is the the the point where we will click and we will be able to see all the connections available here so as this is our s integation and it's having already one trigger connection trigger and point
16:48
added so it will not allow you to select any of the trigger connections so here you can see whatever connection is there right you are able to see the connection all these connections are either invoke type connection invoke Ro connection or trigger and invoke connection any of the
17:04
connection if you want I can I can just show you that one too so the connection is mscore FTP Co n right so let me search this one go back to the connection so you can see right this one
17:21
this one Ms FTP andore con this is the same connection right here so the role for this connection you can see that invoke connection right so this connection having role as invoke you can see here another connection if you will see so for example let me see any trigger inte
17:38
connection this is the trigger connection right XX restore trigger Co n right this connection you will not be able to find here if I will search XXX
17:53
ER right you will not be able to find the connection here why this connection go type is connection Ro type is trigger and in our integration we cannot have trigger integration after the Endo is added after theer end point added so the
18:11
same way if this this connection I will search in this app driven integration we will be able to see that connection here me this one right so if you I will click here this one you can see that connection we
18:26
will be able to find xxxr right here you can see XX race trigger con we are able to see here but the same connection we are not able to see here why this the features of trigger connection that in our integration we can have only one
18:42
trigger connection but the condition is in schedule integration we cannot have trigger connection why because that it's the trigger connection is something that can be used to initiate the integration or to a starting of the integration only but in the schedule ation it's already
18:59
there that schedule end point to start this integration that's why this connection we are not able to see over there you can take any of the examples for example here you can see Fox ATP con this is trigger and invoke connection so
19:15
this trigger and invoke connection can be find both places so this trigger and invoke connection you can find here to that FAS you can see right FAS ATP con so as as this connection role type is trigger
19:31
and invoke trigger and invoke both that's why we are able to find this connection here to at a trigger point and the same connection you will be able to find here too you can see fos ATP connection to
19:47
use as a invoke so like we are done with the basics of trigger and invoke or trigger and Trigger or invoke and Trigger and invoke so when more thing to identify here you can see in the sched
20:02
integration when we created this integration the connection type you will see right here it's the circular it and if you will move your cursor here you will be able to see that invokes message right are you able to see that proper message as invoke so it seems It's it is saying that whatever connection you will
20:18
be able to see here that connection having the role as invoke and obvious the third connection role that is trigger and invoke also contain invoke so that's why here we are able to see all this things so the same way if we will move to that AB driven integration
20:34
as if this integration doesn't have any end point that's why it's showing the icon and once you will move your cursor here it will show you that trigger it means that this integration need first trigger connection then after it will allow you to add another rest another
20:50
that invoke connection so that's the basic differences so let's move to that integration and give we create one connection here
21:06
so here I already created one rest connection let me delete this one so now here I have to create connection to create the connection we just have to go to the create so here you can see you are also able to find
21:22
the one tab that is adapter but this is just we are using to check that ad connection or check the details of that adapter and all to use this adapter obvious we have to go to the connection and in the connection we have to create
21:37
one connection and while creating the connection whatever adapters available in the system it will list down all the adapters here and you have to select any of the adapters for which you want to create the connection so right now I want to create a connection for rest
21:52
type because I want to expose our ABD integration as a rest API so for that I will select here as a rest you can see this is the rest adapter so once I will select this rest adapter it's asking to give the name and
22:11
obvious identifier will come automatically so I will give the name as F this is the rest connection so I will use rest to name and I will just use c n
22:27
instead of that only you can can also mention the role for that connection so this connection we are going to create as a trigger so I will use TR R icore c2n so by looking for the name only anyone can identify this is the r trigger type connection so now here
22:44
identify itcs automatically and now rooll here we have to select as a trigger so I will select the trigger connection roll here and now I will click on create so this is the page where we are going to create connection as a trigger role by selecting the connection type as
23:01
rest another way in the another scen I'm just going to create one more connection I will go back and here I will select the connection as rest
23:17
again and I will give the name as so instead of yes I will use invoke IV right so this is separate name I will select the r type as invoke I will show you the differences that's why I'm just going to create all this s single one
23:33
only so just recreated here so now we have this is our trigger connection Ro this is our invoke connection Ro and now let me add one more so I will just make aate of thison
24:06
so let me go to the design connection here and now again I will select one more connection adapter will be rest only and here I will select the instead of in in invoke I will use 3core invoke
24:21
so this connection will select as a type as trigger and invoke that is selected right so now I will click on create so now you are able to see that we have three connections Page open here right the first one is trigger so when we are
24:37
using the trigger the trigger is doesn't asking that URL and all so just asking that the security so by default that Security is coming like o 2.0 so I will select the basic authentication so that just we can directly provide the ID
24:53
password for this y instance and we can invoke our integration I will I will explain this Point ler right so here you can see it's not asking here we connected the connection as a trigger and it not asking the URL right anywhere that which web services which rest web
25:09
services you are going to call it's not asking right so why it's not asking because we are created this connection as a trigger and you know that trigger connection will only be used to initiate the not to invoke any API right that's why it's not asking any URL for that
25:25
rest API so now here I will move to the another page and here in the page I selected the role as invoke and when we are saying that invoke it means that using this connection we are going to invoke rest API we are going to call any rest API for any third party system
25:43
obvious when we want to invoke any rest API for any system we need to provide the URL we need to provide the ID password for that that API or web services which we want to access using this RIS connection that's why here you can see it's asking the connection
25:58
URL so in this step if we want to connect with that Oracle Fusion application so here we have to provide the Oracle Fusion URL and then here we have to provide the ID password for that URL so as earlier I used that one that's
26:14
why it's showing that ID password here so here we have to provide the URL so let me check that do I have any URL or not so let me see that this is a fusion URL just for testing purpose I'm using I'm not show that ID password is same or
26:29
not so here you can see and now for accessing this rest API this URL for this rest API what kind of connection they allow they allow connection that that the the open AP API or that they having different security
26:45
and all or just that this is a rest based API so I will select this rest based API so whatever rest API available in the system related to Oracle transactions or any third party system most of the time like we know that that is going going to be rest API so you will select that connection type as a
27:01
rest API based URL so why because we know that this is fusion fusion URL so then why we use that Fusion URL here so for example if we will search any of the API so R API to create AP invoice for
27:19
example in Oracle Fusion so here you can see orle provided that the web services to invoke the rest API so this is the resource URL so by conting this resource URL with that
27:35
Fusion you Fusion uh host or Fusion URL it will be considered as a complete URL so once I will copy this Fusion URL so this will be the Oracle Fusion rest API to create AP invoice this is the this is the rest web services so that's why what
27:53
we are going to do this is the host of that URL or host for that web services this rest API so this host we provided here in this connection we provided this rest here in the connection or remaining part this part right so when we will use
28:09
this connection in our OIC so we will provide remaining this part while adding this connection in OIC so once we will create transaction we will I will explain you that part two so this is the URL I given and for this URL to access
28:24
this URL which user ID password required that's why we use use here user and password and always for selecting the user and password we have the the security type policies which we are going to use so what kind of security they added to access their services to access their system so here you can
28:42
select that your services and obviously like you are not the owner of this API or owner of the system so you will not be aware about that which Securities policies you have to select so if you are going to invoke any third party system just like any GST service
28:58
provider URL or any external service URL so then you will get that URL user password you have to ask that which kind of security it is having so if it is having basic authentication obvious we will go so all the Oracle Fusion web services available that the rest API
29:14
having the security as a basic authentication so just you have to provide the user and password so this this is the point we added here so if you will see as this is the public Gateway only so we are just don't want to do anything so here we
29:30
have private endpoint also connectivity agent also so this private Gateway and connectivity agent will used when our Fusion application having their security added just like VPN so without VPN you cannot access your Fusion application at the time you required agent to connect
29:47
here in the connection so we will create one connection where we will use agent so that we will also learn about the agents and all in upcoming days so now here we are done with the providing the URL details providing the ID password to access this URL this is the rest
30:02
connection and if you will see connection status is in Drive d right now and the percentage you will able to see it's 8 percentage or something just whenever you started initiated providing any values it's moving bit percentage right so now this is our third connection which connection having the
30:19
role type as a trigger and invoke so now trigger and invoke will ask you all the information connective information same as the invoke why trigger is going to have less information and invoke is having more
30:35
than more information that's why whatever is the maximum information required for the connection so when you will create that trigger and rooll connection it will ask you that the the the more information which is having so obvious in that while creating invoke
30:50
type connection we have to Prov provide the URL we have to provide the user ID and password so the same way when you will create connection as a triggered and work you have to provide the URL type you have to provide the connection URL and ID and password for that so let
31:06
me use the same URL here too now so this is our first connection so for making the connection as 100% so just you have to go and test so as this trigger Type R connection doesn't require any URL any ID password and any
31:23
user for that that's why automatically when you created it's moved to the configuration status so remember you can use Connection in your OIC only when your connection status will be in configur stus so just here I will save this connection it's already
31:39
100% because it doesn't require any credentials and now once we save you just go back so this we created as a trigger
31:56
right so this one uh the is one yeah this one three connection right so we we this three connection is in
32:13
right now dra status let me save again here you can see it's in graph status so we have to test so now once we click on test so it's it got tested and once it tested it changed the status to 100% And now status of this integration is draft so
32:29
just you have to save again so once you will save your connection your connection status will be changed to configure so now once your connection will be in configur status then only you will be able to use your connection in OIC integration so now our first connection as a trigger done we will go
32:45
for another connection that is invoke type connection invoke R type connection so now here we already provided the URL ID and password so just we have to click on test to check that everything is fine or not and now here we will click on save to
33:01
change the status from draft to configure remember when we are passing the user ID and password here it's not going to check the user ID password in the system it's just validating that we are providing the user ID password or not so it will validate the user password run time and it will this R API
33:19
from OIC so that's why if we will provide inv valid one it but user ID should be correct so now we done saved again so connection status is in configure right now so we'll go back so let me add the filter here also
33:35
for asore R so these two connections having the status as configure you can see the first two connection the last one is trigger and invoke so this is trigger and invoke again here we provided all these things the configure process is 8%
33:53
only so just I have to test so once we will test so this will be tested successfully and then status will be changed to 100% And now status is in dra I will click on save so once we will save the connection status
34:08
will be changed to configure and when status is in configure it means that connection is ready to use just go back you can see our all this connection best connection all this rest connection is
34:24
added here and all these rest connections are in config status so now we have to go back to the integration and again same if you will want you want to search here so if I will click here and if I will search our
34:44
integration just providing the same name so whatever connection having that invoke or trigger and invoke type role it will display here you can see the connection fos having the type S invoke okay so here you can see we have the
35:00
connection created so in connection page we are able to search the connection with this name right when we are searching we are able to see only these three connection when integration when we are searching the connection with the same name we are not able to see and we are able to see the old connection which we already deleted so why we are saying
35:17
able to see here just because before creating the connection we already open this integration canvas and it's not loaded to the connection page to check the connection and to load the connection again we have to go back to the integration so just
35:34
discarded this is our xx01 that schedule integration so let me edit the integration again and here you can see and now if I will search that one sorry so now here we will be able to see that connection
35:50
creat you can see we are able to see this two connection here out of three so out of three we are able to see two connections the but two connection is invoke type connection trigger and invoke type connection but trigger connection we are not able to see so it's it's quite clear that we are
36:07
not able to see the Trier whole type connection because this is sched integration and theed integration already having the trigger and point which is s that's why we are not able to see this trigger and point trigger connection here right and here we are able to see the tri and invoke
36:23
connection why because this having the invoke capability too so that's why given because the same connection we can use as a trigger we can use as a invoke tool so now move to that AB integration again we have to go back to load the connection here so now once you will
36:39
open this integration again you will be able to search the connection so here I will click on this invoke connection trigger connection type so here you can see here we are able to see the connection and the
36:55
connection we are able to see we are able to see the trigger connection and we are able to see Trigger and invoke but invoke Ro type connection we are not able to see so why we are not able to see invoke R type connection because this is AB D integration and ab D integration require at least one trigger
37:12
connection first so that this can be started and it can process further so the same way here this schedule is already the trigger and point that's why it's able to see the invoke connection so the same way when we will add the trigger connection here then only it
37:27
will allow you to show the invoke connection so that's why it's not showing the invoke type connection which is there this one F restore IV con and you should not be confused that what is FAS that f is the short name of
37:44
fox Oracle app solution so in your project so whenever you will work any of the project each and every project having their own naming convention they use the same naming convention for creating the connection creating the the lookup to create the integration to
38:00
create the database connectivity and all these things right so that's why we try to follow the same sequence so here this is our end point right so I will not use this xx0 Z2 name so I use just the name just for that showing that integration so I will remove this
38:16
connection this uh sorry this integration also I will remove this set integration to which we already created in our previous session
38:32
so because I don't want to use any any that name which which is not in correct format so that it it will make a wrong impact so so here you can see this is xx01 this is not deleted from here because the page is not loaded so once
38:48
you will load the page it will be removed because we already loaded deleted right so yeah so now let me delete all this step now here we have to create AB driv integration so I will just click on create I will select the application
39:04
give the name FAS s underscore I will give the name in int 00 I will give the five this 5005 is integration code so in your project integration code be based on your integration for example for
39:19
creating AP invoices there will be separate code for creating the purchase requistion there will be different code for creating that that the p to payment G load and all for each and every integration will have separate identifier and that identifier you can
39:35
use here in in while creating your integration so that it can be easy to identify so now fos 005 and what kind of task the integration is going to perform it's going to display the log message so I will use that or just first app
39:51
integration so this is first AB integration I'm just going to give name like that only and here we we already discussed the version and all so this version we will cover in upcoming session so I'm not going to pick on that part so here again I will select new packages so earlier we already created
40:08
one package that F.C SC means that schedule integration so I will use f. AP so now you like you can see we are not able to see any package with that AP name right so when we will pass AP here so what it will do it will create package with this name
40:24
that fos do AP so uh I will just give the brief description that is this is our first app driven that is application integration now click on
40:41
create so when we create on create so our integration page is here and we don't have any end point that's why we first created connection so that that connection we can use in our integration to initiate our integration so for adding the connection your integration
40:57
you have two way the one way is that just click on the plus icon select the connection here or another way just click on this trigger uh icon here and you can select the connection here so which connection we created we created connection as fascore risk TR con so
41:13
this Tron is something that trigger connections I will use the connection here so remember when I will drag this trigger connection here so our integration will have one trigger and point trigger connection so this connection you will not be able to find after once we will add the connection
41:28
here right so I will show you that too so let me add the connection here just select the connection drop here it's not problem okay let me create by
41:46
clicking plus icon here so I will select this is the same connection right fos rest trigger con I will select here so when giving the naming good naming conven it's really too much important why because if you will see once I will click here I'm able to see
42:01
too many connections available right and right if you will use any any invalid name and all that which is not in correct format it will be difficult to identify you can see that xx7 add addore 7 PPN Des prg you are not able to identify the connection roles types and
42:18
all using that connection right so that's why we will provide naming convention in a such way only so we give so here you can see this is asking the name name name of the Endo so if you remember when we created a schedule endpoint that schedule endpoint having their own name as schedule if we added
42:34
when we added the logger Endo log for loger Endo we have to provide the name so same as as this is our first end point we are going to add here as a trigger so we have to provide the name to that end point so what I will give I will give name as a start so this a
42:50
start it means that this is going to start our integration even instead of a start you can also use trigger so I'm going to use a start so always I prefer that a start only a start and what kind of endo it is this is rest connection endpoint right so that's why I will use
43:06
a start r s rest so even you can use aore rest too so I will just use a start rest so now this is description about the end point I don't want to provide anything because it's not mandatory and I will not give anything like
43:21
that so just click on continue so this is something that uh we cover later it's related to that while invoking this integration we have to pass few values and that values we can configure here so that that we we are going to cover
43:38
later so continue so just just for brief I'm going to give you here so this is something that option if you will see this is the rest API this rest API for creating the invoice you can see that
43:54
the 11 11 13 18 05 SL invoice the same API you will find for this is for post method the same API you will find for different method so just like where is invoice let me show you that one table
44:09
somewhere update invoice right so you can see here delete an invoice if you will select here you will be able to see that same API having the the URL here right so that kind of things you can achieve
44:26
using this this by adding The Tick here we will cover this in upcoming session and you can see the same API but the method is different that method that is delete so if you will go for
44:43
update so here you can see the same API but having that method as patch so that kind of things we can achieve our integration using this way right so that is known as multiple verb for that API right so I will just click on continue
44:59
so our end point is ready given the name as a start rest so now once you will go next so it will ask you that the what this endpoint relative URL is going to do so for example I told you this is that Ur this is the relative URI or URI
45:15
we can say to create or to update the invoices right so this is not the complete rest API to update the invoice to make this complete rest API so we have to concate the Fus URL so in that way this Fusion URL we
45:31
already given in that end point we already given in the rest API right while creating the rest connection so remaining thing right this point this is called as URI URI of that rest rest API so the same way when we are creating connection creating AB integration and
45:49
selecting the rest as a trigger connection it means that we are going to create AB integration and we are going to expose that AB integration as a rest API so when we are going to expose our integration as a rest API so what will
46:04
be the URI for that rest API that resource URI for that rest API or that end point for that rest API so the same way here this having that the invoice as resource URI or the end point so same way we can use here so let me give the
46:21
point as app driven first integration so where it will display I will show you once I will run this integration right so make sure that let me make a note of this endpoint so
46:36
that you can be validate so this is the resource URI be given URI and point right so now here you can see this is the method they are asking to select so this method as we are going to create
46:53
as a use this connection as a trigger so this method will be for our this integration so this integration if any other system will invoke our integration then what kind of method they will use just like for invoking this API we have to use patch method so the same way for
47:08
invoking our integration what kind of method they will use they will means the third system we will use so that we have to select so obvious there are slight differences between all these methods most of the time while creating our integration we will select post so when
47:24
we are saying we will will select post so when you will use post you will get option to configure the request payload or you will get option to configure the response payload so if you not select the post here suppose we are going to use gate only so you can see the request
47:42
payload is hidden you cannot add the request P to this integration it means that when you will run this integration or any other third party will run your integration they will not be able to pass any value as a request fail and as get method is just
47:58
used to retrieve the data so the same way this integration will only return the data that's why here we have enable this option that receive the response so whoever will call our integration They will receive the response so we have option to add the response but we don't
48:14
have option to add the request why because we selected the method as get so the same way if you will select your method as put so it will give options so just like when we are using put it means that we can pass some value BAS that value we can perform some operation that API can perform some some operation and
48:31
it will return some data so that's why when we are using put we are able to see the option as request and response Bo so generally we're creating integration so we are going to create integration in a generic way that they can retrieve the data they can perform operations and all
48:48
so that's why we are just going to select method as post and obviously if you want to add the parameters or request pill or response P you can make a t here else you can escape so as this is our first integration I will not select anything that request and response we go next here one more option
49:05
we have that is review parameters so I will show you that what is this review parameter and how it works in in our upcoming Integrations right so now here you can see we have few more configuration set up that configure header request configure response request so all this we are going to
49:21
escape so we will get to know or we will learn all this when we will invoke any rest AP to perform transaction from OIC so at the time I will explain this point now I'm going to escape everything here just selected the method and post I will click on
49:37
continue so as we have not selected any of the method to configure payload configure parameters and all we are not getting any option further it's just directly moving to the last page which is the review page where we can check our apis and all our endpoint details so
49:53
you can once you will explain this endpoint summary you you will be able to see that whatever you said so I said that end point as this one method at post just click on finish so now once you click on the
50:09
Finish you can see by default this the this a stop end point added so why this a stop end point added this a stop end point it means that this integration is not going to return any value which is correct right while adding this end point we have not selected response
50:24
belad part so that's why when this integration will be executed it will not return any values okay so this is our Tri point we added now if you will go to the connection again you can see the connection icon got Chang and this icon is for invoke you can see right invoke
50:40
message you are able to see once you will click here now you will not be able to find your trigger integ trigger connection if I will search F andore race you will not be able to find the trigger connection so you can see we have option
50:55
as trigger and invoke or invoke so this trigger you are able to see here which is mentioning in use that this connection is already in use you cannot use this connection you can see right when we are clicking here try to directag we are not able to drag but if you select this connection we are able to drag this connection here right so
51:13
that's that's the connection roles over there so now here we added now same as schedule integration which we worked on let me add few log messages then in in next integration we will add parameters to the log message so so that kind of things we will work so for adding the
51:29
log message again I will go to the connection that ation I will select the logger here so I will drag here this end point where we will get the plus icon so this is the endpoint R right so it's able to see that logger one here so in the
51:45
integration if you will see at the time while adding this one we added the end point name as start RIS that's why we are able to see the start rest here right so now I will change the name logger one as a logger uncore message and I will make it to save and
52:01
now here we have to display the message we want to display so I want to display the messages this is our first app driven
52:19
application integration whatever message you will provide in the single coures starting and ending that will be considered as a fixed value and the same value we you will be able to use or you will be able to see this value will not be changed so
52:35
for changing the value we have to use variables and all right so we are not going to check that one too so here this is done so now I'm just going to click outside so that the value can be fixed here now you can see this integration we
52:52
added this end point everything is fine but again we are getting one error here and you know that the why we are getting this error so we are getting this error because it's mandatory to have a minimum one business identified to each and every integration this integration we
53:08
created but we didn't added any business identifier to this integration so once we have to add we will add winess identifier error will be resolved so I will click here even for checking the error message or error name you can click here to check the error message so again once you will click here you will
53:24
be able to see the same message that business identifier missing that is primary business identifier is missing so I will go here and here I will select any this is the identifier and we have to select the value so obvious as this is not schedule parameters a schedule
53:41
integration which will have the a start date a start time as a variable so if you will expand here you will be able to see some values that some values is like the this is the method which we selected as a post this is the UR U which we
53:57
selected this is this is this is the the resource URI and this is the complete path so whatever things you will use you will map here the same you will be able to see in the the integration monitoring dashboard so let me go and use the
54:12
method only so I will drag the method here and then you can CH change the identifier name so by default it's say thatp request matter so I will change the name here I will give the name as de in method let me use in _ method so just
54:28
I will click outside so that this variable can be fixed and once we added the identifier that error go got removed and our integration is in configur status but the next is unsaved changes so we have to save the changes so just save the changes here so once we click
54:46
on Save and everything is fine our integration status got changed to configure and like you know that whenever our integration is in configur status we will be able to activate this integration and we can run easily so again I will click on this power button
55:03
and I will select the tring label so as I already explained that what is the difference between all this tracing label so I will just click on debug so that every time we can see the log messages and we'll click on activate even we are able to see few parameters here that enable payload validation this
55:20
is the new features provided in Generation 3 that that using this this end point we can validate the the payload which we are going to pass to that integration but right now we are not using any payloads we will skip that one this will allow you to run your
55:35
integration with the same instance again and again if you want so I don't want to run this integration again so I will just click this activate so all these things you can do from monitoring dashboard we'll cover in upcoming session so now our integration is activated so it's in process so just
55:51
once you will reload it will be change the status to activate right so now the same way like when we are running this any schedule integration we just have to click on three Dot and we are clicking on run so the same way you have to click on this three Dot and you have to click on this
56:07
run button so once you will click here it will open the page where you will run the ination now you can see if you remember
56:22
while creating the endpoint we given this resource URL or URI to the end point as AB driven SL first insation and same you are able to see here that AB driven SL first and this is the same as that standard API available in the
56:38
market that is equal see the invoices right here right so now I told you when we are creating AB integration remember this point when we are creating AB integration and selecting the rest end point as a trigger it means that we are exposing our AB integration as a API so
56:57
here you can see this is the the complete URI the URI for this rest API for our integration and the same way then when we added that the rest can the fusion host here so the same way we have to add
57:14
the OIC host here in this before this one so that it will be considered as a complete rest API I will I will show you that how we can execute to in upcoming session so this is that one which added and if you remember while configuring the rest end point we selected the
57:30
method at post so that's why you are able to see post here in our integration we have not added any request payload any response payload that's why you are not able to see in the body anything to pass here we don't have any parameters to that integration that's why you are not able to see anything here we have
57:47
not configured any headers we have not configured any integration property that's why we don't have anything right so we just created one simple integration and we have to run that one when you can see in the response you will not able to find anything in the response so here for running the integration we just have to click on
58:02
this run button so once you will click on the Run button it will start the integration with the help of the trigger end point we added just like in SED integration we have schedule end point so you can see this integration
58:18
completed successfully for again we will for make sure we will REM again so that L message can be La so now you can see this is the end point RIS be added with the help of this end point our integration got triggered the triggered by this end point and all these are the
58:34
MPP these all the the activity of the log activity of our integration so once you will click here you will be able to see all the details to that integration that URL the method the integration name and all so you can see message start started processing so once you will
58:51
click on this I icon you will able to see the properties of your integration property of this have driven integration so you can see what kind of property is there the property is method that method is post the same method we mapped as a business
59:06
identifier remember in business identifier we map the same method so this post it will display over there in the monitoring dashboard I will see I will CH show you and you can see this is the URI and this URI you can see this is the complete URI and this URI is
59:22
something your rest API for this integration so most of the time if you remember from vvcs page we are executing our integration so from vbcs page they are executing integration using this rest API only so it means that this integration will be exposed as a rest
59:39
API and this is the URL of that rest API the complete URL and for that URL you can see this is the resource URI we added this one and these are the this is the integration short name this is the integration version and these are the
59:54
flow that this is saying that integration having rest flow and these are the from API right this is our YC instance URL so the same way we are adding the fusion host URI right URL so I will explain this you more when we
00:09
will check this one by running from any other applications and all so now you can see the same way we have relative URI that relative URI the end point we added the path so this is the path of that our integration by making this one
00:24
it will make full and by adding that YC instance URL so this is the brief info about the metad data or that the details of this integration so now we added one loger in our integration so you can see we given the endpoint name of this loger is logger _ message and once you will
00:41
click on this end point you will be able to see the same message which we passed that hi there is our this is our first AB application integration so this is the different integration we created so we added the business identifier to so for checking
00:58
that one what we have to do we have to navigate to the monitoring dashboard so this is the one option that you can manually move to the monitoring dashboard another option is when you will run that integration you will be able to see the track instance page right so once you will click on this track instance this integration will be
01:14
moved directly to the instance monitoring dashboard and here you can see this is our integration in the monitoring dashboard of instance and you can see the time taken like 4 minutes ago it's taken 99 millisecond to execute a status is success and in our
01:30
integration we added only one business identifier that's the primary identifier that's why the primary identifier we able to see and we given the identifier name as inore method so this is the business identifier name in method and what value we M we map the value as a
01:46
integration method that is post in this integration we will have only one identifier that's why the business remaining business identifier we are not able to see here and again if you want to see the log message of this instance here in the last you can see the I icon
02:01
once you will click on this I icon same activity you are able to see here and this is the instance that instance ID for this integation so earlier in Generation 3 it was it was numeric and in Generation 3 it's alpha numeric so that's all about that AB
02:19
integration so in next session we will create one ABS integration where there the same way by create in sched integration we pass through values to add the sum of the two number so in AB also we will pass through values and we check that how we can pass the value
02:35
while running the ab integration so that's we are going to cover in upcoming session so we already done done with creating the a integration So yeah thank you so much everyone for for joining and
02:51
be there in the session and yes if you have any other question queries and you want to ask platform is open for you you can ask it