Hello, in this video, I will show you what is if a standard configuration which you should do for any EDF application. So, I have created documentation and you will find this documentation in this course resource. I will go with you during this documentation and I will show you what is standard configuration huge which you should do before you deploy your application in the production you should have some standard in wave while you do following any diff application. So, application structure should have two project one for model which has a business component can access decision scope and another one for view controller for JSF pages and bag bean and task flow and any third party library and so on. And you should not do in dependency between both of this project otherwise you will fail with MVC Ok application configuration. As I told you the application session, you can sit in application session to be 15 for example, and the maximum should be 45 minutes as I told you listen one hour, unless the customer asked you to sit it for more than an hour, you should make some configuration in application module.

I will go on this later. meds you can apply meds if you want otherwise, don't apply the emergency relief application unless the customer asked you for this meds feature. Sure template and CSS and images and as I show you during this course, you should create your template and CSS and images and icons, which will be used when you already publication in one library. And you should deploy this library in WebLogic as a shared library as it Before the most important thing now, which is the model configuration, which is application module for the polling. So, first option you should do is application module is to check lazy loading. This is will increase the performance of Kook query the view query as a former security for application.

So, you should open your application module here for the general tuning chick customize runtime and this is a lazy loading. I try to run both ADF application in both way I found the lazy loading is a best way for increasing performance. So, you can do this it should works in the application module. Second thing is application Boolean query configuration and this would be depending on the concurrent user, which you will use your ADF application. So, let us go to the configuration open here here initial bone size, what is this initial port size? initial boot size was the number of application would you should be initially created on the first access.

So, the first access what is the initial boot size is recommended to be 10% more Zen's estimated number of concurrent users. So, if for example, if a zero if your ADF application will be accessed during the day from 10 concurrent user, so, you can set this initial boot size to be 11. Second thing is maximum bolt size, maximum boot size is a number of maxima application viewed instance in support can be created and you can see this Is 20 or 30% more than what you sit in the initial building size? reference pool size. This is a number of active application modules in this tent recommended to be the same as estimated number of concurrent three years or so, this is the number of active application would you innocence. So, of course, if you want number of activation, in essence would be same like what this number of users This is the configuration is very important to avoid in passivation and activation mode.

So, for example, if you're a if application would be used for 50 user, you should see this reference boot size to be 50. Or if you want to increase it, you can increase it because currently it is by default it is 10 so 10 because in the development Okay, maybe you want to developer will use it, but if there are too many users will use your ETF application And you didn't set this number correctly you you you some user will be entering specification mode at some at any stage. So, this is a reference booth size should be sent set to be same like an estimated number of concurrent users minimum available size which is five wins it to zero it's allowed to release all application units and after an ideal time I would happen this is would be helped to reserve database connection with Okay Is it is it 204 distance this environment in your system you may see it to a high value but lizanne referenced site size This is a minimum variable size.

So, reference size for example, if you see 250 you can see this minimal size to be for example, 20 listen what it is in reference to boot size, maximum available size by default is 25. This is the maximum number of application module in essence of Torah the Buddhist clean up you can keep it as it is, idle innocence time out by default is 600 application is is considered inactive 10 minutes of in active So, this is in second. So, this is a after 10 minutes of inactive This is for the stresses in your system usage is something close to the web session time out to prevent investigation and activation. So, if you set your session timeout to be 45 minutes this will be 45 minutes, by default is 10 minutes, but you shouldn't carry carries this idea in essence timeout This is I just about by by by default this 10 minutes, you can set it as the same as use it your session timeout.

So, if it is 30 you should set this to be 30 minutes. So, it means 30 minutes multiply by 660 So, your reserve value is here bowling interval 600 a bowl is cleaned up every 10 minutes This is okay you can keep it as it is as I told you if a customer wants at a fabrication station claim to be more than one hour, so, you can set the configuration in application module like I show you in Mexican active age, maybe five hour time to live minus one in new condition Boolean true and disconnected it will make it is one here as a barbarian Bertie. This is Maxie Active Time To Live You can add any, any other property you want to override it. Like I mentioned here. This is force application module pooling. This is the most most important part that you can configure your pooling size depending on the number of concurrent users.

The default configuration was coming with ADF application is for development. But once you go for board action, you should care about session timeout, which the customer is asked if the customer didn't ask leave it is as it is 15 which is nice. And you just focus on the reference booth size and initial maximum booth size as I mentioned in this documentation, and this will be the mini ones the number of concurrent user which will use your ADF application for the view object in any view object if As the user interface somehow to the best division, the user will get a lot of error and exception on this in the view object, you mark Enza include or transit value in the best of it state. So in your specific state include or transit vary by default this is not ticked. So let's just open it was a view object here.

Okay. And you can go for tuning as you can see pacifism state, you can check include all transient values. And even if you have a programmatic view object if you define programmatic the object does this in the programmatic view object as well. This is just to avoid is the best division and to make use of it if application can handled a number of users concurrent users. Just be sure that you configure your application module pooling very well. So that to avoid any reservation to be entered and hopefully your customer will not ask you to enter session type with more than one hour because it may be sometimes can cause an issue for any user ViewController configuration you can use alter your oil responsive templates, you can use this responsive tivity because at the time if a customer asks you if this template can be responsible not you should be ready to have it for task flow.

I prefer not to use in your region or just if unless zero in your usable things and you need it you can use it because sometimes jeez if has some restrictions and what is you develop Is GS f itself. So for my site from my perspective, I use only GS if, if I really need it in ADF application. As I show you before the code library, you should have your own code somewhere, you should generate a jar file and deploy this as a library in some way vertical shared library, so that you will no need to write a lot of code because you will have your own code now in a library. So you can, you can create a shared library for your code. This is the way how you can deploy your application and you can check shirt library as I showed you before. And you should check the auto generate in the WebLogic under the deployment, and you can deploy your application from the console or from terms of bridesmaids or manager or from side by side deployment.

As I show you the data source. This is a way how you can carry the data source but the most Important thing after you carry to the source, you should sit in maximum capacity, because by default, it will be 15. That does go to the console. So if you define the data source here like HR, this, if you go to here in the connection pooling, you'll find the maximum capacity is 15. In your production, you can't keep this in 15. Because if you have 2030 use are using zero application.

The application will there is no capacity for the visible data source and user will get an error. So you have to increase this. I always get maybe 100 depending on the number of users, you will use it so I can just save it. I said it maybe 100 if I know the routine user will use it. I said it for 100 if you see 20 user make it 200 initiative. So you have to increase this maximum capacity otherwise your application will get the user will get an error can't find a connection, a capacity.

This is the what I mentioned here is the maximum chemist, I set it to 114 user using my application. This is you will find this documentation in the Course Resources. This is a good reference for you to know how you can configure your application module pooling for best practice how you can avoid the Pacific Ocean and this is a standard you wish you should follow in your native application you will develop so see you like a civic