Posts tagged weblogic
Larry Ellison – Opening Keynote of Oracle Open World 2010 – announcing Exalogic, the cloud in a box.1
The first major keynote of this year’s Oracle Open World conference was last night – Larry Ellison announcing the Oracle Exalogic machine, the “cloud in a box”. A high end machine that is meant for consolidation (through virtualization) of many applications on a single piece of highly optimized infrastructure.
The Oracle JCA database adapter enables the communication between a web service and a database object, for instance a stored procedure. With the adapter configuration wizard, part of JDeveloper 11g, meta data is generated design time and used run-time to control the behaviour of the database adapter. In this hands-on we show how to set run-time the databaseÂ by overriding the design time selected database in the Oracle Service Bus 11g. (more…)
Starting WebLogic managed servers without providing username and password manually – SOA Suite 11g tip
After installing the Oracle SOA suite 11g, you will notice that you have to enter username and password for each managed server during startup and shutdown. This in contrary to the administration server where you don't need to enter username and password at startup. I was wondering if there was an easy way of skipping this manual step for the managed servers as well.
And yes, there is an easy and elegant way to prevent entering credentials every startup and shutdown. Just follow these steps:
1 Create a boot.properties file.
Create a plain text file called
boot.properties with the following content:
2 Place the boot.properties file in the security directory.
Save or copy this file in the
security directory under the managed server root directory. This directory was not created at installation time, so I had to create it myself. The server root directory is located at
3 Start the managed server.
The server will read the credentials from the
boot.properties file and in case of plain text username and More >
Last week we had some problems with the deployment of our ADF 11g applications on a stand alone WebLogic 11g (10.3.1) server. One of the issues that kept recurring during the deployment was a ClassCastException reffering to the ADFLogger class – that our application did not explicitly use. We got the impression that the ADF libraries that we rely on, somehow reference this internal class. The exception was just the first of potentially many indications of a WebLogic server lacking in ADF runtime readiness.
Here are some pointers as to the things that need to be ready in WLS 11g in order to ADF 11g application to be deployed and run:
One of the cool new things I learned about here at the ODTUG 2009 conference is the fast swap feature in WebLogic Server 10.3 and above. So far, Application Server features have had limit use in my little development world, but this is one that may have quite some value for me, as I am developing my web applications in JDeveloper and constantly deploying, running and testing them. This feature will considerably shorten those development cycles!
The fast swap feature makes it possible to have classes that are changed and recompiled in JDeveloper immediately redeployed on WLS, without actually redeploying the entire application. By setting a single configuration option in a configuration file and configuring the output path for the compiler in JDeveloper I can shorten most of the development-compile-deploy-test cycles by eliminating the deploy (and application restart) step.