Posts tagged weblogic server
Production redeployment is a facility in WebLogic that provides the ability to temporarily have multiple versions of the same web application of web service active at the same time.
Sometimes, changes in application functionality require redeployment of the application. In the theoretical case of instantaneous responses from applications, we could argue that the roll out of a new version of an application is akin to the flip-of-the-switch: request A is handled by version X, the switch is flipped to bring version X+1 live and the next request B is taken care of by the new version. This, however, is not the reality. Requests take longer to process than no time at all. Besides, requests live in the context of a session – this applies to database as well as application server. This means that replacing version X with a new version X+1 in a throw-the-switch manner would not only potentially interrupt pending non-zero duration requests but would also – and far more harmfully – destroy all pending sessions. This would definitely not constitute zero-downtime application upgrade.
One of the perhaps somewhat counterintuitive challenges with at least the initial stages of adopting Fusion Middleware is the fact that there is too little work in terms of administration.
On the one hand, Fusion Middleware administration entails quite a bit, starting with WebLogic Server
and typically extending to one or more FMW components:
all of which the administrator – or rather the administration team – needs to deal to with. Typically even around the clock to ensure the availability required by the business.
On the other hand, the actual workload for FMW administration for a small number of applications, services and processes does not justify a dedicated resource. This proves a serious problem for many organizations: 24/7 availability requires 3 FTE while the effort is on average less 0.5 FTE.
Organizations can adopt several strategies to address this challenge, as is illustrated in the next picture.
Years ago, when I worked as an Application Support Analyst for a big triple-A Bank, I got acquainted with the BEA product stack.
One of those products was BEA Tuxedo, at that time at the release of 6. I worked at a settlements project, and Tuxedo was used for as distributed transaction processing, to process settlements an clearing messageg from the bank to an international Clearing an Settlements Project, called CLS. It used the SWIFT network to connect; CLSÂ was an international and timezone independent settlements and clearance platform to overcome timezone and bankrupt issues, and prevent a domino effect when an important bank in the chain becomes bankrupt.
Tuxedo is a transaction processing system or transaction-oriented middleware, or enterprise application server for a variety of systems and programming languages.
Tuxedo was designed for high availability and to provideÂ scalable applications to support a lotÂ transactions per second on commonly available distributed systems. It was developed and designed by AT&TÂ if that required online transaction processing (OLTP) capabilities.
Tuxedo is aÂ message routing and queuing system. Requests are sent to named services More >
As you probably already know, ADF Business Components can very easily be exposed through a WebService interface. An Application Module can be configured with a Service Interface, ordinary ViewObjects and custom methods can be exposed in that interface and deployment is relatively straightforward. In minutes, a WebService can be published that exposes operations based on regular ADF BC functionality. This may well give us the fastest way to provide data services on top of a relational database. Several excellent articles have been published on the ADF BC service interface, for example by Steve Muench and Andrejus Baranovskis.
The blog-article you are reading is created as the result of my research and investigations around an article I hope to publish in Oracle Magazine later in 2011. It is adamant for this article that readers can get the example to work with the smallest number of instructions possible – both to make their life easy and to save on words. The article describes a BPM process that interacts with the HR schema of an Oracle RDBMS as one of its activities. The focus in the article will be on BPM, not on exposing data services for the HR schema. The WebService should More >
In a recent article I described the interaction between JavaServer Faces (1.2) and Spring Framework (2.5.x): http://technology.amis.nl/blog/6655/spring-a-surprise-on-a-jsf-developer-how-spring-beans-can-become-jsf-managed-beans. I created a JDeveloper 11g web application that I ran on the integrated WebLogic Server 11g (10..3.2). In this article I will explain the configuration steps I had to go through for making JDeveloper and WebLogic run my simple JSF/Spring application.
1. Create a new generic JDeveloper application; set the project name and add the JSF library
2. Install the JDeveloper Spring extension through the Check for Updates facility under Help in the main menu