on me about to six years okay so let's start with the things right so how it is okay so maybe you know we're housing background or not so I'll be giving a brief idea on data ever us in flow and then we'll jump into the a Venetia party right okay so why we need and it have it hurts right what is the purpose of data warehouse right so you know that that ever house is a data base right which we store the data of the business right so any idea on the warehousing what is a warehouse on other than Prasoon as he worked on ETL so i'm sure and hopefully calm any idea where houses like you know you use it for more analytical purposes mmm yeah it's like data gathered from multiple sources and it is structured in such a way that it will be more useful for the reporting you know right hello buy it right yeah that's correct okay so you know that right that every us is a database which will be storing the current data and the historical data and it gives us reporting and analysis purpose okay so when we compare with the normal databases the data of size will be more and it is huge we'll be having huge volume of data which we will be showing it and as as we know that ETL will take the data from multiple types of sources right any kind of source format the data can be so it will be input for my ETL process okay and ETL will perform extraction transformation loading Pat and then we will be loading into the data warehouse right and once the data is available in the data warehouse the reporting teams will try to read the data and then it will show the reports to the end-user okay so in this platform in this warehousing database in platform will be having two areas right one is ETL friend another one is a reporting right so we will be working another ETL part we will be preparing the data warehouse with the help of any of these ETL tools right so we will be working on the ignition back here okay so other equal tools and other reporting tools right I have listed here okay so in terms of data passing application flows right so any of the tools you're working with the data flow will not be changed it will be the same right but but what is the difference here is you are seeing some kind of salient features for a be sure when we are comparing with the other ETL tools okay so this thing will be differing right in terms of futures right which are available in the Abney show when compared to other atl tools okay so as you are ever off bit on the warehousing right I will not be expending more on this now I'm go right we can go with the ambition part so here we can discuss the basics once again when we started our sessions okay so we'll go with the average of friend so happening show what is happening show right I'm not sure it's a ETL tool and it is a latin word from the beginning right so from the beginning onwards this tool is giving ETL solutions for many kinds right and we have listed out many domains different domains right what we have like banking telecom incidents healthcare electrical science retail right so we have multiple domains we have right so among all these domains right so we will be having more projects from financial services right like banking sector telecom incidence right all these are having more projects on this trend right and will be having a few projects on health care systems al Turkish Airlines and detail big al macro track so they have a different domains right what we have data right and we'll be using average of per se right so a bonito is a ETL tool and it is a us-based company right so where the guys will be working in this tool for creating and developing on the develop and elephant part of the ETL tool and supporting to the vendors it's a button to the vendors okay so it started in 1996 the tool was direct on 1996 and from mm right around 2000 onwards so we have so many projects coming upon this ETL tool and we have more projects now and it is a cost here ETL tool among all the ETL tools right so even it is it is coming up with the package right so like repository the client and server right everything is provided by ETL nashoni right and performance wise this is the topmost ETL tool right so where wherever you work with the millions of records the data volumes okay you'll be finding that the performance is far better than any other ETL tool so F nature is a specifically right so stands alone as a single point of right ETL tool with respect to the performance okay so this performance is due to the pathogen techniques right which makes this tool very strong right so the way we have parallel techniques in a variety of tools also right so account to the architecture and according to the futures available in the Abney show it stands the different than compared to the other ETL tools okay that's why the performance is topmost here okay and current version is 3.2 version which we are using okay but as a part of planning program you'll be getting 2.10 version right for your practice purpose okay and but I will be covering the latest futures right whichever you want to work right now whenever you started working on this ab initio 8 here right so we'll be covering all the topics which we will be working currently but for practical things you will be getting two point one zero poojas available in 2.10 is similar in the 3.2 but we'll be learning additional things right which are missing in the 2.10 but which are required for the current developments okay any questions till now yeah okay so in that case okay we'll start understanding the about architecture for it so how the architecture will be right at what kind of working nature we'll be doing it right within the app initial level okay so we have a transfer model right as it as I said it's a pencil model so client is agde which is graphical development environment and certain component is cooperating system right so this is my GT right graphical elephant environment which is existing on the Windows environment okay it will not change right it is harder is existing on the Windows environment and this is the front-end interface for a developer right so whenever you started working on a GD right so what you are what are you going to do using the GD means okay you're going to DJ in the graphs you're going to execute the gap and we are going to check the status of the graph right so all these three points right will be performing using this GD right so like in terms of like suppose a informatica right so in the eating there in the retail right if you want to perform these three steps right so you will be doing using different you'll be using these three steps using different tools right but here will be doing it in a single window right so it is a simplest way it is the simplest way to do the activity is using the GD okay so we here the graph is nothing but it's a collection of components well graph is nothing but it's a collection of components so we'll be choosing the components as per the requirements and will be defining the properties and then we'll be building the graphs right so the graph is created and it will be saved with the extension dot NP right so that will be saved like a not MP extension right and the relevant dot and P will have a dot cases file right so which is nothing but it is a shell script right it will be created automatically whenever you save the graph right that means every graph is having a dot case H which will be created automatically right when may save the graph okay and where are you going to save all these graphs and dot here such files right so that means nothing but it is it is nothing but it is available on the UNIX mission right so your server come brain the corporate system is available on the UNIX mission right now cooperating system is available on the UNIX mission okay it is being connected to multiple CPUs the corporate system is counter to multiple CPUs right so the UNIX mission here it is called as a host mission right it is called as a host mission so the host mission contains the corporate system server component right so it's internally linked with multiple CPUs right depends upon your application you might be having 12 city you 16 CPUs right depends on application wise then this is called as a host mission where you are going to store your input files output files interment files right everything you will be saving here itself right along with the graphs and the dot cases files which I explained now right that means there is there is no physical location in the GD 2 story rafts right everything will be stored in the host level ok so your server content is existing in the host right so GD is only purposefully used for designing the graphs right and modifying the graphs but now physically they will get saved in the hosts mission and the seller competent is physically available in the host it's been available so whenever you trigger to run the graph right so running the DAP will be handled by the coding system and the CPUs right so these cooperating system is meant for taking taking care of excitation process whenever you run the graph okay so within the GD I'll be having the connection details towards my hosts mission right so this is a UNIX which has a right so this unique server access right so we have to fill the details of the unique server within the GD to connect to this mission okay so that only the GD and the host T is having the relation linkage right so whenever you turn the graph right whenever you run the graph so what are the steps it is being involved with right so that is nothing but its anatomy of running a job right so whenever you run the job whenever you run the graph right so what happens is the you will you triggered the graph from the GD and it will create one process right that means the initial request will be going to the host Nothe which is called as host transcreation right so this is all the steps are will like a background process right whenever you trigger the job what happens so the host will receive this request right and then this request will be given to the processing nodes right it is given to the processing nodes that is nothing but the CPUs right so these are called as agent process creation right each and every CPU will have one process created and within the agents the components right so how many components you are using in the graph so each and every component will create one process okay so this process creation will be happen in the agent level and it will be executed that is component execution and it will be terminated right the components will be terminated once the job is completed so that means the agent will understand that all the components got executed within that agent level and then agent will be terminating right by sending back the request to the host right that means the control is back through the host okay and from the host again the request will be sent to the GD that is nothing but it is a host termination ok so this way the the running of the graph will be happen at the background level right and you will be able to see the output within the GD itself right so the resolution part is mainly handled with the help of the corporate systems are our component okay so any questions here no no it's clear okay now this one I'm fine okay fine yeah so this is the communication right how it is happening between the Gd and the host G right so that's what we discussed till now so you will be having the connection right in the GD to connect to this first mission right so whenever you join to any client to work with right so you will be given access to this host mission that it is your UNIX mission and you'll be given access to the GD lessons right will be activated with your ID okay so whenever you log in to this host mission you'll be having a home path right that means the root directory is home followed by the developer ID right so this is my home path let's say that right okay so now I'll be introducing one more component right from the architecture level that is thing but eme okay that is nothing but M so here eme is here me is a repository right DM is a repository that is Enterprise meta endowment Enterprise meta environment which is a separate software from the apt issue okay so that means here whenever you work with the amateur yes ETL tool projects right everywhere you'll be using the eme as a repository right there is nothing like will be using the third-party tools right as a depository okay so the repository is always eme only right so this is installed on the different unique server right this is existing on the different UNIX server so sometimes in some of the projects right so we observe that right so this eme and this host mission right how she is a different unit server right so in this scenario I am Telling that host is at one unit server and eme is existing on the different unit server right they said two different unique servers right but sometimes you might be saying that the same UNIX server is serving like as a host I say eme but in those situations right so we face some problems with the performance right and they migrated this eme right to the different unit server so that the battery will not be existing on the different same unit server right so you will not face any problem okay so that means eeehm is a completely it's a repository where you store the code right and it is also a version controlling tool by default right it's a version control in tool so here I will be storing all my code admission code right in this eme okay so from the eme only I will be migrated in the code into the respect to higher internments right so whenever you do the life cycle whenever you see the life cycle of the Abney show right or any kind of PT L or anything you can see here right so we have direct meant track right so we have SAT u8e production right so we have different environments available right in our paid housing so you will moving the code from one location to another location right and finally it will be in the production so as a part of a venetian skill set so you can work as a ETL developer with the within the development environment and you can work like a Support Analyst in the production support right so both the responsibilities right we'll be there in different projects right as a support we'll be working the support analyst also right so we can have more opportunities our memories friend okay and now like whenever you see this yummy so yummy is existing on the unique server right so we have the root directory which is a projects right which is a projects so this is constant in the eme that means to any client to any client to any project you're working with right any domain so this projects root projects is a common directory right it's a root directory for every application but the rest of the folders will be changing as per your client right so they will be creating their own subdirectories right so they create some directory structure like this right and this complete complete path is called as project path okay it's complete path is called as a project path so I'm using the technology as project this is not about your your project which are you working with right but project is an aperture technology which is called as a directory structures in the eme to store your code right to story of code that means this is called as a project path and in this last sub Dietary and in this last subdirectory we'll be having a set of subtitles right like this these are again constant okay this have this a constant again in any application you work with so MPs will store the graphs right MP folder and run folder will store the dot case it files right so this way each and every folder is having an importance right so where the respective objects will be saved right into these locations okay so this is existing in the project path right so whenever I started working on this project right so I'll be creating my own environment first right I'll be creating my own environment that means I'll be creating a sandbox in my hosts mission right in my in my host mission I'll be creating a sandbox so how do you create it means whenever you perform a check or crosses a sandbox will be created right that is within your home path within your home path the complete path of the eme project path will be copied into your home path right so now this complete path is called as a sandbox and it is nothing but it is a working environment for a project right and it is working in normal for a project okay so every user will have their own sandbox ok any any questions here so far so good okay so a sandbox will be created so in this is my place right where I'll be storing my code initially right so from the Giri from the GD whenever you create anything it will be saved under my sandbox right so this is my sandbox path right so when I created a graph right a graph will be saved under MP extension right under MP extension and this is my problem right so initially the code will be stored in the code will be stored in the sandbox right but later once the development and testing is completed it will be stored in the emé okay so whenever you want to store it in the emé you have to perform check-in process right so how to do check-in checkout we'll see later but check out is getting the objects from Amy to the sandbox and check-in means taking the updates from your sandbox to eme okay so you'll be seeing this check-in checkout process you can do either from the gde or from the host machine right so if you are doing from the gde you'll have an options right how to perform check-in checkout but if you are doing from the host machine we should use the commands but AB nature commands to do this checking check out okay so we'll have other commands also to interact with eme so basically like every user will be creating the graphs initially in their sandbox and then they will perform a check in right so whenever you do check out the check out will always try to bring the objects which are missing in your sandbox but they are present in the in okay but they are present in the eme right that means the missing objects in your sandbox with respect to the eme project that is one thing and the updates also right you have any graph modified in the in the emmys having the latest version okay and you are holding the old version in your sandbox right so then it will overwrite the existing object which is existing in your sandbox level right the sandbox is not a but not a person controlling tool but eme is a version hundred into right in the sandbox we will not maintain multiple versions right you'll have only one version it can be older version or it can be latest version right let's say that right I did not do check out for the last ten days right so from last ten days they are ten graphs which are created as a new and then they are available in the evening and we have our five graphs right which are modified right in the eme so whenever you check out after 10 days right you'll get all those ten graphs into your sandbox and then also your objects your five objects which are updated right those are also will be coming out right that means into your sandbox they will get updated so your sandbox will be up-to-date in sync with eme right suppose say if you are trying to modify the existing object in your sandbox right suppose say you're not trying to modify the existing ball object in the sandbox at that time you have to lock it okay you have to lock it that means we are going with the scenario right have it have it is like this okay they are to developers like a and B right so they created a dot MP and beta or MP and it is existing in their own sandbox is right so developer a is having they don't hanboks B is having its own sandbox right and once the rap is to be checked in into the eme they will perform a check-in and eme will have both the objects with two different questions right and now when you go for modification right suppose now they want to modify it so the the developer a want to modify both the graphs error MB and beta or MP right but as per the initial step step number one right he is having only error MB right so beta MP is not present in the sandbox right but whenever he perform a check out as his new object existing in the eme it will be copied into is sandbox so now the sandbox of a will have both the graphs error ambient be rat MP we can lock the graphs right we can lock the graphs so locking is required to modify in any object which is present in the eme right an object which is existing in the eme if you want to modify it if you want to modify it you have to lock it right so once it is loved you can modify it and then you can save it okay yeah yeah tell me hello hello yeah yeah so if buzz if same person is working on the same yeah two different persons are working on the same project after they check oh good hello yeah yeah tell me a new young hey yeah you're right Abel your audible word so that this it's if it's like yeah well so do % then check in on the same graph I two at a time no that is not that is not and that is not possible right so suppose you created a graph right you created a graph and then you checked in right okay and that's what like you know in the locking is required to avoid you just to modify at the same time right so multiple you just cannot modify at the same time okay that is where we are locking it right so without locking even we cannot edit the graph without locking you cannot eight the graph as well right so once you logged it and modified it right and it will be saved into your sandbox but whenever you perform chicken it will be available in the eme right and then in the eme you can see new versions right so both the graphs are modified right so why not one version a dot MP is having a new version with 191 and the two not one B dot MP is having a new version 234 right so we have two versions available in the eme right so now this the person B right the person B ok initially created bidder and B right so he is trying to lock it he want to modify something on the same graph right he is having this MP right in the sandbox first as he created it so but he cannot lock it he is unable to lock it why because this is the older version when you compare with the eme version right so the version which is existing in beta for a beta Ram be right in the in the B user right what is the version number it will be two not fun okay it will be two not fun right so 234 is been created by this new developer a so he did not do any check out right he tried to lock it so the older version cannot be known hello [Music] able to hear me hello oh you can hear right so what is the problem here and the other like I'm in the same mode right I did not change anything so one see you are not able to hear me hello pum say hello Kumar hello yeah I hear you like 4 to 3 minutes it was not audible V&V will not hear you okay fine fine yeah there is some problem in to your end I think right so the Sunni is able to hear yeah okay fine what I'm saying here is right so the a user a has modified two graphs right and he checked in so that these versions are available in the ami right so you have created 191 and 234 versions in the eme right by it is user okay and now the user B want to modify the grabby wrote MP right but beta MP in his sandbox is Ola version so whenever he tried to lock it he cannot lock it right why because it is the older version it will pop up a window stating that the version is available it's not in sync with the eme version so in order to modify any graph which is present in the eme okay it should be the same version the latest version of the eme should be available near sandbox right then only you can modify it if not you cannot modify this graph right so you'll be will be performing a check out and he will get aired or MP updated inner MD will be the error MP will be added up and beta MP will be the latest version it will be updated okay so this way he can he will modify it right this change I thought is not a one-time process it will be the regular process hello Vamsi hello okay okay fine that's really questions for you okay actually like the examples wise right we want a little more maybe somewhat advanced actually because we had a bit of understanding already okay yeah because we want to work in a real time like how oh well the examples because for us it's more important to have the real-time examples really good one yeah we have it anyhow like as we are given the real times in Arizona right so all the assignments will be right so once you come read things right so we'll be having more and more and how many classes overall one month okay and it's like wanna one and a half hour session organization okay okay fine then we'll meet in the actual sessions and then like that I need is what I need is right so you need to work on the guidelines right whatever I am giving to you so by the time you complete the course right you'll be able to will you be discovering the topics on the whole or you will explain them in a like pregnant