Integrate Best Practice in my application

Hi.
I have developed a fusion application for my organization. It is based on pages and we don't have bounded task flows. I want to create bounded task flows with page fragments as a best practice, but without modifying the home page that has a menu bar which dinamycally loads up all the options from the data base. When I clic on an option from the menu bar I want to call a bounded task flow. For example I have an option security and inside I have sub-options.
The problem is that home page is in unbounded task flow and i can't call a bounded task flow with page fragments.
Thank you.

Ok i got it, but I have one problem. I have a commandNavigationItem (global link) and If I clic it then i see the corresponding taskflow, but If i clic on the menu items from the menu bar I go to a page and then clic on the commandNavigationItem i don't see the taskFlow, it stays in the page.
Edited by: Miguel Angel on 06/11/2012 03:57 PM

Similar Messages

Best Practice for Enterprise Application Integration

I would like to integrate a few corporate systems together by using Oracle Fusion Middleware. I suppose the integrated process is running in synchronous mode such that it also supports two phase commit.
In BPEL Process manager, there is a tool called "WSIF" which seems to be relevant to my requirement. I would like to know which tools should be best for my integration project and any suggestion on implementation.
Thanks in advance,
Samuel Wai

This has been answered repeatedly. WL allows you to cache JNDI context
          objects, ejb homes and remotes without any problems. (EJB remote interfaces
          must only be used by one thread at a time, but that requirement is provided
          by the EJB spec itself.)
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com
          +1.617.623.5782
          WebLogic Consulting Available
          "Geordie" <[email protected]> wrote in message
          news:3af9579f$[email protected]..
          >
          > I'm wondering what the best practice is for Servlet EJB integration in
          terms of
          > caching the home and remote objects. My understanding is that the Home
          object
          > is threadsafe and could therefore be cached as an attribute of the
          Servlet. This
          > would remove the need for a JNDI lookup for each request. Similarly
          caching the
          > ProxyObject would yield further savings. However, I have noticed that
          most examples
          > don't use either of these practices. Why not?
          >
          > Thanks in advance,
          > Geordie

Best Practice Needed: Global Application Properties...

Hi All,
When developing a web-based application that reads certain configurable parameters from .properties files, I usually put the appropriate code in a static block in the appropriate Java class, storing the property in a static final constant. For example, a DBConnection class might have a static block that reads the driver, username, and password from a properties file.
My question is, what are some "best practice" techniques for accessing and storing such parameters for use in an application? Are all global properties initialized in one class? at the same time? only when first needed?

over all, I would say that your approach is fine. Personally, I load properties through a single class, some thing like PropertyReader, and have the different classes initialize their static fields via a get method on that class, like getProperty("db.user"). I prefer to load them via a single class because I can place all of my IO trapping in one location, it is easier to implement new security measures and, if necessary, easier to support internationalization.
I initialize all properties once, at startup, into a Wrapper Object, typically ResourceBundle or Properties (although Hashtable or any some thing else would be suitable). I believe that it is best to initialize all properties at the same time, at startup because the costs of storing properties that may not be used is going to be less then the cost of making multiple IO calls to load properties on a need-by-need basis. In other words, you are almost always going to take a bigger performance hit by loading properties only when a request for that key is received, rather then just loading them all at once.

Best practices for creating application schema

All,
Can anyone recommend best practices (or pointer to a url) for creating application schema. A novice installer created a schema and the tablespace ran out of disk space in 2 days and the system came to a halt at a production site. The tablespace was created with one datafile and with MAXSIZE specified. I am looking for Do's and Dont's on production system.
Thanks for any help,
Vissu

I'm not sure that you can boil this down to a "Do's and Don'ts" list unless you want to get overly general...
For example, do make sure that you provision space appropriately. "Appropriately" however, is going to be radically different in different environments. Some shops set all their data files to autoextend in production and monitor utilization at the OS level. Other shops specify exact file sizes and monitor utilization at the Oracle level. Each approach has its own advantages and disadvantages, you just need to make sure that your application uses the same approach that every other application in the organization uses.
Do have an idea about the space utilization of the application, but don't go overboard. Running out of space in 2 days means someone failed to do a basic analysis. On the other hand, I've seen people spend way more time than they should making 5 year projections based on some relatively soft assumptions and getting worried about internal overheads that were much smaller than the error bars in their baseline estimates. Of course, the precision necessary also depends on the implications-- a 20% error in a multi-TB data warehouse is going to have a lot more impact than a 20% error in a 20 GB OLTP application.
Justin

Best practices desiging JSF applications

I have an intermediate level of knowledge on JSF but after completing a component for an application I'm still stumped about the best practices required when designing a Java Server Faces application.
The issue I faced mostly in the first iteration was Loading of dependant objects.
Wherever we needed to display an editable view of an object by way of a request parameter there was always the question at what point to load the entity?
For example, I have a page edit.jspx?itemId=21
In my faces config, I have a Backing bean which has a managed property:
<managed-property>
    <property-name>itemId</property-name>
    <property-class>java.lang.Integer</property-class>
    <value>#{param.itemId}</value>
</managed-property>My backing bean has the getters and setters for this property but at which point is it best to load the item with id of "itemId"?
It also gets a bit more complex when I depend on other injected properties for example an application scope manager class.
One thing I have learned is, that the order that you declare the managed-properties in the faces-config appears to be the order that they are injected - I can't make a definitive answer on this as that's just the way it works on Sun App Server 8.1 and JSF 1.1. But I'm still trying to work out when to undertake a simple load for dependant entities in a backing bean.
One appraoch I have looked at taking is introducing some "Loader" classes - basically a POJO that performs loads based on request param setting events:
    <managed-bean>
        <managed-bean-name>UserLoader</managed-bean-name>
        <managed-bean-class>testfaces.loader.UserLoader</managed-bean-class>
        <managed-bean-scope>request</managed-bean-scope>
        <managed-property>
            <property-name>invManager</property-name>
            <property-class>testfaces.aspect.InvestigationManager</property-class>
            <value>#{InvestigationManager}</value>
        </managed-property>
        <managed-property>
            <property-name>userId</property-name>
            <property-class>java.lang.Integer</property-class>
            <value>#{param.userId}</value>
        </managed-property>
    </managed-bean>
    <managed-bean>
        <managed-bean-name>ItemBean</managed-bean-name>
        <managed-bean-class>testfaces.jsf.bean.ItemBean</managed-bean-class>
        <managed-bean-scope>request</managed-bean-scope>
        <managed-property>
            <property-name>user</property-name>
            <property-class>org.ikeda.testfaces.model.UserEntity</property-class>
            <value>#{UserLoader.user}</value>
        </managed-property>
    </managed-bean>Ergo, each time I use the ItemBean in a JSP it will try and set the "user" property which is retrieved from the UserLoader provided the param.userId is set from the query string. Mind you this limits me to using only the request parameter (okay for Portlet integration) as there is no property called userId in the ItemBean - another workaround to work out!
Of course this kind of functionality can be rolled into the ItemBean, but it's amazing how much of a mess the Backing bean becomes when you encapsulate this logic into the backing bean.
What experiences has everyone else had with JSF and this kind of situation?
Does anyone know of any good resources about "designing" JSF applications (writing is one thing, designing is another)?
Regards,
Anthony

I have an intermediate level of knowledge on JSF but after completing a component for an application I'm still stumped about the best practices required when designing a Java Server Faces application.
The issue I faced mostly in the first iteration was Loading of dependant objects.
Wherever we needed to display an editable view of an object by way of a request parameter there was always the question at what point to load the entity?
For example, I have a page edit.jspx?itemId=21
In my faces config, I have a Backing bean which has a managed property:
<managed-property>
    <property-name>itemId</property-name>
    <property-class>java.lang.Integer</property-class>
    <value>#{param.itemId}</value>
</managed-property>My backing bean has the getters and setters for this property but at which point is it best to load the item with id of "itemId"?
It also gets a bit more complex when I depend on other injected properties for example an application scope manager class.
One thing I have learned is, that the order that you declare the managed-properties in the faces-config appears to be the order that they are injected - I can't make a definitive answer on this as that's just the way it works on Sun App Server 8.1 and JSF 1.1. But I'm still trying to work out when to undertake a simple load for dependant entities in a backing bean.
One appraoch I have looked at taking is introducing some "Loader" classes - basically a POJO that performs loads based on request param setting events:
    <managed-bean>
        <managed-bean-name>UserLoader</managed-bean-name>
        <managed-bean-class>testfaces.loader.UserLoader</managed-bean-class>
        <managed-bean-scope>request</managed-bean-scope>
        <managed-property>
            <property-name>invManager</property-name>
            <property-class>testfaces.aspect.InvestigationManager</property-class>
            <value>#{InvestigationManager}</value>
        </managed-property>
        <managed-property>
            <property-name>userId</property-name>
            <property-class>java.lang.Integer</property-class>
            <value>#{param.userId}</value>
        </managed-property>
    </managed-bean>
    <managed-bean>
        <managed-bean-name>ItemBean</managed-bean-name>
        <managed-bean-class>testfaces.jsf.bean.ItemBean</managed-bean-class>
        <managed-bean-scope>request</managed-bean-scope>
        <managed-property>
            <property-name>user</property-name>
            <property-class>org.ikeda.testfaces.model.UserEntity</property-class>
            <value>#{UserLoader.user}</value>
        </managed-property>
    </managed-bean>Ergo, each time I use the ItemBean in a JSP it will try and set the "user" property which is retrieved from the UserLoader provided the param.userId is set from the query string. Mind you this limits me to using only the request parameter (okay for Portlet integration) as there is no property called userId in the ItemBean - another workaround to work out!
Of course this kind of functionality can be rolled into the ItemBean, but it's amazing how much of a mess the Backing bean becomes when you encapsulate this logic into the backing bean.
What experiences has everyone else had with JSF and this kind of situation?
Does anyone know of any good resources about "designing" JSF applications (writing is one thing, designing is another)?
Regards,
Anthony

Best practice documentation of application

Hello listers, I need to come up with a proposal for a standard on how we want (to force) our developers to document there code and all the neat stuff there are building. Is there a best practice for Oracle and if so can some direct me to the URL. Thanks Ronald

Hi,
There are a lot of such links available in the oracle site. Some of them are
http://otn.oracle.com/docs/products/oracle8i/doc_library/817_doc/server.817/a76992/sql.htm
http://otn.oracle.com/tech/pl_sql/content.html
You can search for more in the oracle site for "Best Practices" or "Coding Standards". You can also search in
"www.google.com" for external articles.
Thanks,
Sharmila

What is the best practice with Jclient application

Hi all:
If we have some oracle Jclient(bc4j+swing) solution application system , how to co-work with Oracle workflow ?
what is the best solution to integrate these technology ?

There are a few PDF documents about the Workflow Java API. Try to locate "Oracle Workflow and Java Technical White Paper" for 2.6.2 version.
However, please note that Workflow PL/SQL API is far richer and more flexible that its JAVA equivalent.
Also, take into account the different ways workflow engine executes an activity, if the underyling code is written in Java or PL/SQL. If you select the Java API to implement workflow activities, then 2 scripts must be running at all times so that workflows proceed. These are the Java Function Activity Agent and the Workflow Background Engine. Details are included in the above document.
Our experience has shown that:
1) Implementation of workflow activities via Java API is slower and more complex than PL/SQL API, because java classes are considered as external prcoedures.
2) Not all PL/SQL procedures are included in Java API.
3) For workflows with high throughput, the Java Function Activity Agent becomes a bottleneck.
Please note that Oracle has announced several months ago the OW4J (Oracle Workflow for Java). Check a beta version at OTN, together with some features and specs. However, a final version is still pending.

Best practice for calling application module methods and plsql code

In my application I am experiencing problems with connection pooling, I seem to be using a lot of connections in my application when only a few users are using the system. As part of our application we need to call database procedures for business logic.
Our backing beans, call methods on the application module which in turn call a database procedure. For instance in the backing bean we have code like this to call the application module method.
// Calling Module to generate new examination/test.
CIGAppModuleImpl appMod = (CIGAppModuleImpl)Configuration.createRootApplicationModule("ky.gov.exam.model.CIGAppModule", "CIGAppModuleLocal");
String testId = appMod.createTest( userId, examId, centerId).toString();
AdfFacesContext.getCurrentInstance().getPageFlowScope().put("tid",testId);
// Close the call
System.out.println("Calling releaseRootApplicationModule remove");
Configuration.releaseRootApplicationModule(appMod, true);
System.out.println("Completed releaseRootApplicationModule remove");
return returnResult;
In the application module method we have the following code.
System.out.println("CIGAppModuleImpl: Call the database and use the value from the iterator");
CallableStatement cs = null;
try{
cs = getDBTransaction().createCallableStatement("begin ? := macilap.user_admin.new_test_init(?,?,?); end;", 0);
cs.registerOutParameter(1, Types.NUMERIC);
cs.setString(2, p_userId);
cs.setString(3, p_examId);
cs.setString(4, p_centerId);
cs.executeUpdate();
returnResult=cs.getInt(1);
System.out.println("CIGAppModuleImpl.createTest: Return Result is " + returnResult);
}catch (SQLException se){
throw new JboException(se);
finally {
if (cs != null) {
try {
cs.close();
catch (SQLException s) {
throw new JboException(s);
I have read in one of Steve Muench presentations (Oracle Fusion Applications Team' Best Practises) that calling the createRootApplicationModule method is a bad idea, and to call the method via the binding interface.
I am assuming calling the createRootApplicationModule uses much more resources and database connections that calling the method through the binding interface such as
BindingContainer bindings = getBindings();
OperationBinding ob = bindings.getOperationBinding("customMethod");
Object result = ob.execute()
Is this the case? Also is using getDBTransaction().createCallableStatement the best way of calling database procedures. Would it be better to expose plsql packages as webservices and then call them from the applicationModule. Is this more efficient?
Regards
Orlando

Thanks Shay, this is now working.
I successfully got the binding to the application method in the pagedef.
I used the following code in my backing bean.
package view.backing;
import oracle.binding.BindingContainer;
import oracle.binding.OperationBinding;
public class Testdatabase {
private DCBindingContainer bindingContainer;
public void setBindingContainer (DCBindingContainer bc) {this.bindingContainer = bc;}
public DCBindingContainer getBindingContainer() {return bindingContainer;}
public static String validateUser()
// Calling Module to validate user and return user role details.
System.out.println("Getting Binding Container from Home Backing Bean");
BindingContainer bindings = BindingContext.getCurrent().getCurrentBindingsEntry();
System.out.println("Obtain binding");
OperationBinding operationBinding = bindings.getOperationBinding("calldatabase");
System.out.println("Set username parameter");
operationBinding.getParamsMap().put("p_userId",userId);
System.out.println("Set password parameter");
operationBinding.getParamsMap().put("p_testId",examId);
Object result = operationBinding.execute();
System.out.println("Obtain result");
String userRole = result.toString();
System.out.println("Result is "+userRole);
}

Best practice for adding application to $env:Path in PowerShell?

I'm trying to figure out the best way to add a program to PS's path. When I look at $env:Path, I see tons of different entries pointing to various programs on the system that seem to have been added by their installers. This would suggest that I could just
add another entry pointing to the .exe I want to have available in the path, but if I do this every time I want to have an application available at the shell my path is going to get hideously cluttered.
In bash, I would normally make a bin directory within my home directory, add it to the path at startup in my .bashrc, and then make symlinks in that directory for anything I wanted available. This keeps the path clean and easy to manage. Is there a way to
do something like this in PS, or is the standard solution just to add a new entry to the path for every application you want until it's like a million miles long and unreadable? Putting symlinks or shortcuts in directories already in the path hasn't worked
so far.

I'm trying to figure out the best way to add a program to PS's path. When I look at $env:Path, I see tons of different entries pointing to various programs on the system that seem to have been added by their installers. This would suggest that I could just
add another entry pointing to the .exe I want to have available in the path, but if I do this every time I want to have an application available at the shell my path is going to get hideously cluttered.
In bash, I would normally make a bin directory within my home directory, add it to the path at startup in my .bashrc, and then make symlinks in that directory for anything I wanted available. This keeps the path clean and easy to manage. Is there a way to
do something like this in PS, or is the standard solution just to add a new entry to the path for every application you want until it's like a million miles long and unreadable? Putting symlinks or shortcuts in directories already in the path hasn't worked
so far.
You can't put symlinks in a folder to a folder but you must put a link or shortcut to the executable. Links to folders are not scanned. Only the root folder in the path is scanned. No programs wil lever be found through the path if it is in the
current folder in a PowerShell session.
You can quickly alter the patch for the current session like this:
$env:path+='c:\myprogramfolder'
When you exit PowerShell it will not reamian. It will only change the PowerShell process path for that PowerShell session.
¯\_(ツ)_/¯

Best practices for Air application distribution

I am going to need to develop an AIR application. I am a bit confused how I will deliver updated version it when something has been changed. Will the users have to reinstall it every time I let them know that there is a newer version available? A reason I am asking is that with a web based applications I dont have that problem, every time I export newer version it becomes available immediately.
Thanks

Look at this article http://www.adobe.com/devnet/air/articles/air_update_framework.html
Etienne

What is best practice for...

What is best practice for deploying applications through the IPCU to 10 ipads?
I'm looking for a complete step-by-step of the best way to do this.
Thanks in advance!

Just place a modem into any console port. Ideally you use a terminal server, but is not always really needed.

New paper available on the Forms OTN page (Best practices...)

This is a great paper about "Best practices when Developing Applications with Forms 10gR2"
http://www.oracle.com/technology/products/forms/pdf/BESTPRACTICES10GR2.pdf
Very interesting.
Francois

hi
thx franco
Kris

Where is Forms Best Practices guide?

I'm looking for
Best practices when Developing Applications with Forms 10gR2
which is listed on the documentation tab, here:
http://www.oracle.com/technetwork/developer-tools/forms/documentation/techlisting10gr2-087608.html
But the link:
http://www.oracle.com/technetwork/developer-tools/forms/documentation/ssLINK/164049
gets a 404 error.
Looking through the forums threads and googling, I find references to its being located here:
http://www.oracle.com/technology/products/forms/pdf/BESTPRACTICES10GR2.pdf
but that redirects back to the home page.
Anyone know where I can find it?
Thanks,
Rebeccah

I believe the doc for which you are search is here:
http://www.oracle.com/technetwork/developer-tools/developer-suite/bestpractices10gr2-164049-fi.pdf
I have requested that the Forms OTN page be corrected to point to this url. Thank you for bringing it to our attention.

Best Practices for Configuration Manager

What all links/ documents are available that summarize the best practices for Configuration Manager?
Applications and Packages
Software Updates
Operating System Deployment
Hardware/Software Inventory

Hi,
I think this may help you
system center 2012 configuration manager best practices
SCCM 2012 task-sequence best practices
SCCM 2012 best practices for deploying application
Configuration Manager 2012 Implementation and Administration
Regards, Ibrahim Hamdy

Best-practice on versioning a soa suite-application

Hi everyone,
I recently organised a seminar for customers concerning the Soa Suite Stack and one of the interesting questions asked that day was a versioning-question.
Let's say we've build a bpel/esb application interacting with different external and internal webservices and we've deployed this application to our production environment and we need to change an internal web service.
How can we add versioning to this heterogenous system in a consistent way? I know you can tell esb which version of the bpel process it needs to use, but what about the custom and external webservices that we've integrated with?
My 2 cents: You need to add a versioning-tag to you custom web services that you need to manage yourself, and use this versioning tag in the services your integrating with.
Could somebody point me out what best practice is, or what Oracle's development team is working out regarding versioning systems for SOA-applications?

Marc,
Are you saying versioning isn't supported in ESB now? I thought that ESB already uses the versioning tag from bpel when you're integrating bpel and esb?
During the development of my demo I've seen that the version-tag was used when invoking the bpel process through a soa service.

Integrate Best Practice in my application

Similar Messages

Maybe you are looking for