Skip to main content

Overview Editor for bc4j.xcfg

By
This is used to customize the configuration settings for the application pool, connection pool, and transactions.

Select the Application Module, then select a configuration from the Configurations list.
You can specify a Default Configuration from the dropdown to use with selected application module. Edit the name of the configuration in Details.

Its having 3 tabs
1.Database and Scalability
2. Properties
3. Custom Properties

Database and Scalability Tab :

In Database and Scalability you can mention the JDBC data source definition for each application module.
You can choose to connect to a JDBC data source or to a JDBC URL.The default connection type is the default data source.
A data source is a vendor-independent encapsulation of a database server connection on the application server.
1. Data sources ( JNDI name) offer advantages over a JDBC URL connection because the data source can be tuned, reconfigured, or remapped without changing the deployed application.
2. JDBC URL connection type is useful for testing the application module in JDeveloper when you run Oracle ADF Model Tester or run the application in Integrated WebLogic Server.

You can mention Application module parameters that affect the behavior of the application module pool and whether application module instances holds onto JDBC connections that
they obtain from the connection pool after an instance is removed from the application module pool.
refer below image for such parameters.





Properties Tab :

You can use it customize the list of ADF Business Components project properties for the current configuration.
Click the Add Properties and Remove Properties button to customize the list.
Some properties below are labeled as advanced properties.
These generally allow you to create custom classes to implement core ADF Business Components functionality.
If you do not change these properties, ADF Business Components will use framework classes to implement this functionality, which is adequate for the large majority of users.




Custom Properties Tab  :

Use to customize the list of custom properties for the current configuration.



Comments

Post a Comment

Popular posts from this blog

Passivation and Activation in ADF (Application Module )

By
1. For performance reasons, ADF keeps a pool of application modules in memory. It tries to give each session the same application module as the session used during the last request; however, this might not be possible during peak load of your application. 2. In this case, ADF saves the application modules state in a database table so the application module can be used by another session. This is called passivation . 3. When the first session needs the application module again, its state is retrieved from the database process known as activation . 4. If you have made an error in your code and depend on some variable that is not persisted correctly when your application module state is stored, you will experience mysterious errors under high load.   Enable/Disable Application Module Pooling : Right-click on your application module, choose Configurations.By default, each application module has two configurations. Ensure that the one ending in …Local is selected and then c...
1 comment
Read more

Get modified rows from Entitiy Cache

By
To get the modified rows from entity cache we have getEntityState() method at EntityImpl class. Refer to my previous blog  Accessing EO impl methods from VO impl  where i am overriding the getEntityState() in EOimpl and calling it in VOImpl. We can use methods written or overridden in VOImpl class to AMImpl class. There are different states associated with an entity object. STATUS_UNMODIFIED STATUS_MODIFIED STATUS_NEW STATUS_DELETED STATUS_DEAD We have to check the state or row in our AmImpl class by using the VOImpl method and through this we can distinguish the rows present at vo. Add below code in AMImpl class along with my previous post. public void geCachedRowsCount(){         JobsVOImpl jobsVo = (JobsVOImpl)this.getJobsVO();         RowSetIterator iter = jobsVo.createRowSetIterator(null);             while(iter.hasNext()){             Row row = iter....
2 comments
Read more

The file store "WLS_DIAGNOSTICS" could not be opened

By
WLS_DIAGNOSTIC ERROR weblogic.store.PersistentStoreException: [Store:280073]The file store "WLS_DIAGNOSTICS" could not be opened because it contained a file with the invalid version 1. A file of version 2 was expected. When you get this error while running your application on internal weblogic server delete the following file WLS_DIAGNOSTICS000000.DAT search the file in following path C:\jdev_work\system11.1.1.5.37.60.13\DefaultDomain this file is in DefaultDomain folder of your jdev. and delete the WLS_DIAGNOSTICS000000.DAT file . and run your applicatuon
1 comment
Read more