Agile methodology is a collection of innovative, user-centered approaches to system development. It tries to define an overall system plan quickly, develop and release software quickly, and then continuously revise the software to add additional features. After the downsides of the traditional software development approaches were identified (too many documentations, all requirements must be known at the beginning of a project,…) it became obvious that we needed another approach. And that’s how Agile was created.

Facebook is the biggest social networking website intended to connect friends, family, and business associates. With over 800 million users and counting, application developers are in need of user information integration with the biggest social network. That means using Facebook user data as the primary authentication mechanism in their applications and/or reading user data from Facebook so the user doesn’t have to fill out annoying registration forms.

Establishing production environment is the final, but probably the most important step in the application’s life cycle. Production environment for ADF application implies application server, but also various settings and resources. As each version of ADF becomes more demanding, it is necessary to follow certain procedures in establishing ADF production environment. This blog will describe the procedure of installation of ADF 11.1.2.1.0 on WebLogic 10.3.5.

If you are looking for a solution that offers a bridge between business and IT as well as improvement of enterprise performance by driving operational excellence and business agility, you should consider implementing  BPM (Business Process Management). Furthermore, if you aren’t afraid of a little bit of Java coding, you might pay attention to jBPM (Java Business Process Management).

We have been using Oracle ADF Framework to develop applications since the version 10g. ADF Task Flow was introduced in version 11. In 10g version we can only use one large task flow for navigation between pages (like in JSF application).
How to switch to the ADF Task Flow after we have somehow got used to control execution of action in pageDef files or managed-beans and how much they have helped us in the work, read below.

The development of application solutions in modern environments sooner or later will point up to the following dilemma: independently develop functionality or use the functionalities environment already provides. Developing application solution in ADF technology has proven to be in need for better control of session management. It seemed illogical to develop our own solution for functionality that has already been implemented in WebLogic. It was time to look into JMX.

In the past decade, investments in IT solutions based on Java technology have been counted in billions, and it is certain that in the coming years this trend will not be changed. If we consider that the major players in the IT market have recognized Java as the “de-facto” standard for enterprise scale product development, that Oracle got Java in the recent acquisition of SUN, that IBM made a huge investment in WebSphere middleware, and that Java middleware is the fastest-growing business of JBoss, it sounds unreasonable to start with development of new solutions and not think about Java as a candidate platform for development. So what about Java development on enterprise scale level? Are there any available “add-ons” (frameworks) that can help us in development process?

The question is often how many application modules to create, a single big one or several small ones.

While developing ADF KickStart application, we have made the right decision about the number of application modules, but it turned out that they do not need to be root application modules. We are supposed to nest within a root application module.

Why and how we performed nesting, read below.

In almost all web applications we encounter the need to keep certain data in the session scope, and to store and access data that last through the whole user session.

The most common practice is keeping user data (roles, rights, and any additional data) accessible from the time of login until system logout. To avoid the repeated retrieval of such data, we usually store them in session scope variables and use them when necessary.