Sharing Application Module view Instances

hi,
I read the sharing application module instances but I didn't understand the difference of Application level shared Application Module and session level shared Application Module.
Give the simple answer to this one.
Regards,
Ragu.

To summarize what the documentation says: Session-scoped shared app module would only be accessible to a single user (session), whereas application-scoped shared app module can be shared by all users.
John

Similar Messages

View Objects in the shared application module is not refreshing

Hi ,
I have view objects defined shared apps module. This view objects are used for creating lovs which won't change very frequently. I have set the AutoRefresh=true for this view objects. I do have a UI to update the underline table for these lovs. The view objects defined in the shared application module is not getting reflected even I add a new value in the database. Is there any way to refresh these lovs as soon as its added to db?
Thanks
Suneesh

I will explain my scenario ;
I have a view object(ViewA) where I have defined many LOVs for different attributes. Thes LOVs are using the shared application module's view object (shared_view1,shared_view2...etc) as List DataSource. Where exactly I need to set the auto refresh property=true. Currently I have set all of my shared apps view objects's(shared_view1,shared_view2...etc) autorefresh property=true.Do I need to use the autorefresh =true in the ViewA ?
What is the concept of autorefresh=true ? Wiill it refresh automatically the view object nexttime i am accessing the page after the db inserts ? Is there any time delay there ? if there is it something configurable ?
Thanks
Suneesh

LOV doesn't apply view critera working with shared application module.

Hi,
I have a shared application module to share lovs between applications.
These lovs have bind variables in the where clause and in view criterias.
When i use these shared lovs, if i select in the view accessor, more than one view criteria to be applied in the view accessor, all rows are selected, it seems that any view criteria are applied or they are applied with an OR operator, althougt in the view accesor indicate that they will be add with an AND operator.
thanks!

I also have a similar problem. View criteria dos not applied in LOV from shared AM. Workaround - in base VO view row implementation for base love attr setter add re-query for LOV view accessor:
ViewObject vo = getSharedAM_RefItem1_1().getViewObject();
vo.applyViewCriteria(vo.getViewCriteriaManager().getViewCriteria("RefItemViewCriteria"));JDeveloper 11.1.1.6 (Build JDEVADF_11.1.1.6.0_GENERIC_111205.1733.6192.1)
Edited by: VitalyCoder on 25.02.2013 10:53

Verifying a Shared Application Module

I have been looking at Shared Application Modules; I have created a small test application that utilizes a Shared Application Module. I would like to ensure that my implementation is OK, e.g., verify that only one instance of the Shared Application Modules is created. How can I do this?
In some forum, someone said that he tried to do this by “monitor the Application Pool “. How do I do this?
Thanks

You can test this from the AM tester. Enable Debugoutput to Console as described here.
IF you use a VO instance from a shared AM as an LOV you will see the LOV query being printed only once.
Also refer to http://www.oracle.com/technetwork/developer-tools/adf/learnmore/87-lov-using-shared-am-444769.pdf for the idea

Sharing application modules

Hi,
I have an application (ADF) running on Oracle AS. Lets call it Application A. This application comprises of about 10 projects (modules).
I am creating a new webservice that uses some of the application modules, view objects and entity objects of Application A. I will be deploying this webservice as a separate application on the same Oracle AS.
Is there someway for my webservice to use Application A's app modules, view objects and entity objects without physically including them in the webservice ear/war. This will help me keep my code in-sync.
Thanks.

Hi Frank,
We (colleague of Nilesh) unfortunately can't wait for 11g esp. because you can't give a release date.
The problem we are facing is that we see the same queries hitting the database over and over again. So caching these queries for a 'longer' period of time would save us a lot of round trips to the database.
The data we want to cache is releasable stable, the data we select is separated from the data we insert. So we can store the data over a longer period of time.
But as I understand it, there is no solution that would solve such a usecase? (Other then using a different framework/ building a custom solution)
Message was edited by:
Thijs Vonk

Combo LOV search on VO exposed on Shared Application Module

Hello,
My Jdev version 11.1.1.6. Technology stack is ADF BC and ADF faces.
I have a generic lookup table that provides static list of values for many pages. Most lookup types have short list of values i.e. 15-20 and are implemented as selectOneChoice but some are 100+ and are implemented as Combo LOVs.
This lookup VO has been exposed on Application level Shared Application Module and all LOVs are implemented on data model side.
The problem is with Combo LOV search functionality. If I try to search on column, putting X%, it returns all values and I noticed that no query is sent to database which means it has all the data already cached on application server and returning all rows from there.
If I change the LOV's Base VO [i.e. lookupVO] to regular [non-shared] then it perfectly searches as per entered criteria and returns correct rows.
Do I need to set something on VO (or some where) to return filtered records from memory?
My BC objects extends custom framework extn classes. Can something be done in custom framework etxn classes affecting only where it is required and not affecting other VOs [non-shared] functionality?
Please help.
Thanks,
Jai

Pratap,
Thank you for the response.
The reason I need to use new xxCO on the page is this.
Seeded page CheckoutLinesPG.
It has advanced table on it where every column has it's one external region.
The new LOV region xxRN is put on a page also under this table new column.
1. When a requester (seeded region on the seeded page) is changed then my xxLOV should reflect the change and be populated according to what is selected in the Requester LOV.
2. When one-time address is added (another seeded region on the seeded page) my xxLOV should be disabled, when one time address taken out - enabled again.
So xxCO should apply to the whole page.
The VO behind advanced table PoRequisitionLinesVO is extended with 2 additional attributes and will substitute, the new xxVO is under xxAM data model.
All works fine with my methods in the seeded RequisitionAM which I get a handle to in the xxCO. But I don;t know how to get the handle to the xxAM if I put my methods there.
Thanks,
Anatoliy
P.S. just fyi - I know it is not the recommended approach but what I did for now I put all calls into the controller - in the controller I can get a handle to root AM, through that I am getting a handle to xxVO which (!) is substituted during runtime with my xxVO. But if you can figure out how to get a handle to xxAM in my case it will be great.
Edited by: asmirnov on Mar 24, 2009 2:04 PM

Question about shared application modules

Hello,
I read the part in the developer guide but I still have some questions.
1) The dev guide states that shared app modules use a different configuration.
I assume this is the <appmod>Shared configuration?
2) Where is this defined? Can this be changed?
3) I understand there are two type of ‘scopes’ session and application. I’m using application for static lists, but I do not understand what the session scope is for? Is there any reason to use this scope over a normal application module?
4) We have a system which uses VPD in an ‘odd’ way. We use it to set the current working year. Because the data is bound to years. Is it possible to use a session scoped shared module for this? And when I changed the current year (Context being set via the app module) to refresh all the session scoped shared module’s views?
-Anton

Anton,
Yes, you can jump aroundd as you like.
You just can't use view links between VO's based on different db schema tables.
Nesting AM's doesn't help there, the DB connection of the top-level AM will be used.
Why don't you create synomyms for the tables in the other schema?
Steven Davelaar,
JHeadstart Team.

Shared applications modules

Hi,
I've been reading the section about shared AM in the developer's guide, however I found explanations rather incomplete.
I would like to know how to do the following:
1. Use a shared AM from the user interface, a.k.a. have a data control referring to an application or session scoped shared AM. I am aware that I can change the configuration name in the DataBindings.cpx file, however there are no ways to specify the instance name as defined in the "Model" project Business Components properties.
2. Use a shared AM from another AM, a.k.a. define a nested AM as a reference to an application or session scoped shared AM. Inspecting the source xml file for an AM definition, I see that nested AM are defined as AM usages, a.k.a. like a shared AM definition is an AM usage. So, if I specify the usage name of a shared AM and change the "SharedScope" to be "1" (session) or "2" (application), will it work as I expect it?
3. Use a shared AM from code. In this case, I would like to known how to retrieve an instance of a shared AM from its instance name wherever my code is located. I may be in an EntityObject, ViewObject or elsewhere.
4. How do I create dynamically a shared AM instance? Either as a nested AM from a root AM or from scratch (if that is possible).
Shared AM looks like an extremely nice feature, let us exploit them! :-)
Thanx!
Olivier

Thank you for your answer Blaise.
I agree that creating shared AM dynamically seem to contradict their purpose, but I'm really looking to know how things work and where I can push that feature.
I hope you found out how we can access shared AM with code as it seems to me that the feature is completely underexploited.
What if I'd like to "cache" other stuff at the AM level?
What if I'd like to access a shared AM from another AM to access shared data?
What if I'd like to show in my UI a drop-down with cached lookup data and I can't use the LOV feature?
I can think of plenty of scenarios where I would use it.
Thanx!
Olivier

Defining Application module

I need to get the exact points on how to define the Application Module.
I feel AM as the definition for initializing or grouping set of EOs VOs etc.
So what are the points in doing this grouping?
In some cases common EOs and VOs are used for different functionality.
Is such cases what is the best way of defining AM, define several AMs or do all functions in one AM?
Is there a big performance issue too on this decision?
Please explain.
Thanks.

Hi,
I suggest you begin by reading chapters 9 and 10 from the Developer's Guide:
"Implementing Business Services with Application Modules" http://download.oracle.com/docs/cd/E17904_01/web.1111/b31974/bcservices.htm
"Sharing Application Module View Instances" http://download.oracle.com/docs/cd/E17904_01/web.1111/b31974/bclookups.htm

Misbehavior when LOV is mapped from Shared AM's view object.

Hi,
I found a misbehavior when i try to map a LOV from a Shared AM, whereas it is working fine when i map the LOV from a normal AM.
Let me tell you the details about the sample i created to simulate it.
JDeveloper version - 11.1.1.4.0
Sample Application - Based on HR Schema
Functionality requirement:
Screen has a Select one choice, which should list out all the employees from EMP_DETAILS_VIEW, a view of HR schema, without only one employee.
Sample App Details:
1. Created a Shared Application Module, say "SharedSupplierAM" (i.e. Said the scope of the AM as Application Level)
2. Created a view object “EMP_DETAILS_VIEW” with a bind variable "bind_Emp_Id" and a view criteria "NotSaidEmployeeVC". View criteria's where clause is framed as ( (EMPLOYEE_ID Does not equal :bind_Emp_Id ) ) 3. Shuttled an instance of "EMP_DETAILS_VIEW" into SharedSupplierAM.
4. Created another application module, say "ConsumerAM" (It is not a shared AM).
5. Created a BaseViewObject, say "BaseVO", with an attribute "Employee", to which EMP_DETAILS_VIEW from SharedSupplierAM is mapped as LOV.
6. In the View accessor, shuttled the view criteria NotSaidEmployeeVC and hard coded the value "100" for the bind variable bind_Emp_Id.
7. Shuttled an instance of BaseVo into Consumer AM.
Expected functionality:
LOV should not display the Employee whose id is 100.
Issue:
When i run the AM tester, create a row, it displays all the employees irrespective of the view criteria's where clause i framed, whereas when i map the LOV from normal AM (i.e. not a Shared AM), it displays the employees based on the view criteria's where clause !!.
NOTE:
1. Instead of hard coding the value 100 in the view accessor, If you keep another attribute in the BaseVO, say emp_id, and refer it for the bind variable bind_Emp_id, for the first creation of row alone, it is misbehaving. Once a selection from LOV is made, for further creation of rows, it is displaying the proper list.
2. When i repeat all the above said process but map the LOV from normal AM (i.e. not a Shared AM), everything works fine.
Question:
1. Why this inconsistency?
2. Is it a bug or do i've to change my approach of mapping a LOV when it comes from Shared AM?
Thanks in Advance.
Raguraman
Edited by: Raguraman on May 2, 2011 12:54 AM

Thanks to Jobinesh.
I got answer from Jobinesh, which i specified below so that it will be useful for others.
In case of shared AM as the same VO is being shared by multiple users and the query cannot be dirtied at runtime, so applying VC at run time doesn't have any effect/supported. All the VCs need to be applied on the AM where the ViewObject usage is defined, and pass the bind parameter value while defining ViewAccessor as you did in the sample.
Also note that if one attribute(e.g: LoggedInEmpId) drives value for LOV defined on another one, then the first needs to be added in to Dependencies list for the second one using your VO editor and keep autosubmit=true for the driving one, set partialTrigger to refresh LOV
Raguraman

How to programmatically call remote application module - JDev 10.1.3.3.0

Hi,
I've an ADF web application (10.1.3.3.0) deployed onto an OAS server. I'd like to be able to access view objects via the application module of this web app from a simple java class on another server.
I've created a simple class to query a local application module (included in the same project as the simple class). This works fine but I'm not sure how to change this to access an application module when it's remote on another server. Can anyone assist?
Here is my sample code for querying a local application module/view object:
    public static void main(String[] args) {
        ApplicationModule applicationModule =
            Configuration.createRootApplicationModule("com.almac.model.common",
                                                      "AppModuleLocal");
        try {
            ViewObject eventList = applicationModule.findViewObject("SipEventsView1");
            eventList.executeQuery();
            while (eventList.hasNext()) {
                Row event = eventList.next();
                System.out.println("Event Name: " + event.getAttribute("EveName"));
        } catch (JboException e) {
            System.out.println(e.getMessage());
        } finally {
            Configuration.releaseRootApplicationModule(applicationModule, true);
    }Thanks,
Paul.

You can expose an AM as an EJB or Web service to expose them for remote access:
http://download.oracle.com/docs/cd/B32110_01/web.1013/b25947/web_services.htm#CJAEEICB

Transaction Management for Nested Application Module

Hi
I'm using Jdev 11.1.2.0
I am having nested Application Module. In that I want to separate view object data need to commit without commit the root application module view object.
Is it possible. Kindly reply me.

No, the root application module controls the transaction of all need application modules. A commit will commit all changes together. You have to use different root application modules for this.
Timo

Application module configurations

Hi
When I right click on an application module and choose Configurations... there are two configurations for a given application model (for example AppModuleLocale and AppModuleShared) in the manage configurations dialog. I couldn't find anything about the usages and differences of these two configurations on the net. Would you please tell me about this?
Cheers,
Ferez

These are the two configurations which are created by default by the framework. The 'local' configuration is for normal use as a web application with multiple users accessing the application. The 'shared' configuration is a special use case where the application module is shared by multiple other application modules, e.g. when the data accessible via the shared application module is quasi static in nature. This kind of application module is often used for look up data.
If you check the 'Pooling and Scability' parameters of the two configurations, you'll notice the difference in the 'MaxPoolSize' parameter. For 'shared' application modules this parameter is set to 1, as there are no changes in the data expected and the same application module can be used for all queries.
Timo

Remotable Application Module

Hello,
i try to make an existing application module remotable:
Application Module Editor -> Remote -> EJB Session Bean -> Local Configurations -> Edit -> Application Module -> Middle Tier Server Type
In the Middle Tier Server Type select-box i can't select something else than Local. In Help Content you have also remote types like Oracle9i EJB or WebLogic EJB. How can i choose Oracle9i EJB as Middle Tier Server Type?
JDeveloper Version: 10.1.2.0.0 (Build 1811)
Application: ADF Toy Store, (http://www.oracle.com/technology/products/jdev/collateral/papers/10g/adftoystore.html)
Daniel.

Hi,
If you have developed custom methods in your Business Components (on your application module, view object, or view row), and you have specified in the respective wizard that those methods should be exported to your client, then depending on your remoteable deployment platform, JDeveloper will generate the client stubs for those methods when you generate your deployment profiles for the app module.
On the Remoteable page of the App Module wizard, you can specify to have that client stub code generated to a new project, or to an existing client project. By default, they will be generated to a new project named something like deploymentplatformClient.jpr.
Basically, the only thing you need to be aware of for those files is that they get included with your client code when you deploy your client project. They must be available to your client code at runtime in the deployment environment.
So, the easiest thing to do is to add these generated files to your client project. When you create a deployment profile for your client project, just make sure to include them.

About application module

Hi,
I want to call executeWithParams method in one of application modules view object..
what is the syntax?

ADFBC problem with bind variables

Sharing Application Module view Instances

Similar Messages

Maybe you are looking for