Enabling hot deployment of code on WebLogic Server

Developers need a quick turn around time for making changes in development and debugging etc. WebLogic server has the ability of hot deploying code without needing to redeploy the application. This works particularly well when running the Integrated WebLogic Server.

To enable the functionality locate your weblogic-application.xml file that will be in your application. If using JDeveloper you’ll find it in your Application Resources panel usually on the left and it will be in the folder Descriptors->META-INF.

Double click this and you should see the Fast Swap panel.
Expand this panel and tick Enable Class Redefinition.

You should end up with the following in your file:


Rebuild and redeploy your application and you will now have the ability to update your code and have it automatically pushed to the server. You will see the message “Redefined all recompiled classes that are loaded in the debuggee process.” in your logging panel when it pushes the files to the server. (Note, because JDeveloper doesn’t support automatic building of code you have to explicitly run “Make” on the files you have changed.

“Development Lifecycle for Taskflows in WebCenter Portal” whitepaper guidance notes

Whilst following the white paper from Oracle on the “Development lifecycle in Oracle WebCenter Portal” I came across a significant issue for new users of WebCenter which was a missing project for the tutorial.

It stated in the introduction that there are applications shipped with the whitepaper but I couldn’t find them and neither could Oracle Support. To get going in the meantime I created my own “GenericWebService” project that satisfied the requirements of the tutorial. This is available here.

Alternatively, follow the steps below to create it yourself.

Missing connection.xml file
Section 3a: Create a Web Service Proxy Facade – On page 28 the whitepaper says to update the connection.xml file with the contents in yellow in the page above. However, for my application that I had created I didn’t have a connection.xml file for some reason. To resolve this I closed the GenericServiceConsumer application, went to the GenericServiceConsumer\.adf\META-INF folder and created a new file called connection.xml. On re-opening the GenericServiceConsumer project the file was then available and I could paste the conents below into it.

<?xml version = '1.0' encoding = 'UTF-8'?>
<References xmlns="http://xmlns.oracle.com/adf/jndi">
  <Reference name="GenericUserWebServiceConnection"
             manageInOracleEnterpriseManager="true" deployable="true" xmlns="">
    <Factory className="oracle.adf.model.connection.webservice.api.WebServiceConnectionFactory"/>
      <XmlRefAddr addrType="WebServiceConnection">
          <wsconnection description="http://localhost:7101/GenericWebService-UserWebService-context-root/UserServiceWS?WSDL"

Nullpointer Exception
I also had a nullpointer exception thrown when I first started up the taskflow in the JSF page. This was probably because of the home made web service project that I created above. It wasn’t a SOAP based web service and therefore the URL was wrong in the connection.xml file.

You will notice that mine above contains the URL http://localhost:7101/GenericWebService-UserWebService-context-root/UserServiceWS?WSDL whereas the whitepaper’s URL is http://localhost:8888/GenericWebService-UserWebService-context-root/UserServiceSoap12HttpPort?WSDL

Proxy Server pitfalls with JDeveloper!

If you are using JDeveloper with a proxy server then you may already be familiar that you need to go into Tools->Preferences->Web Browser and Proxy to setup your proxy server. For me this is required so that I can download extensions into JDeveloper.

I then began to have issues when I was trying to setup my JDeveloper connection to my VM application server that hosts WebCenter. I filled all of the details out correctly however, the connection test output returned failure when testing JSR-160. See output below.

Testing JSR-160 Runtime … failed.
Cannot establish connection.
Testing JSR-160 DomainRuntime … skipped.
Testing JSR-88 … skipped.
Testing JSR-88-LOCAL … skipped.
Testing JNDI … skipped.
Testing JSR-160 Edit … skipped.
Testing HTTP … success.
Testing Server MBeans Model … skipped.

This issue was down to the proxy server settings. I attempted to configure the proxy settings in JDeveloper to ignore my VM, so it didn’t go through the proxy server, I tried disabling the proxy server. Neither of these worked.

What I needed to do was disable the proxy server settings in JDeveloper and then restart it! Only once I had restarted did the disabling of the proxy work.

The downside of JDeveloper here, is I now need to turn the proxy settings on whenever I need to download/check the extensions but then disable it whenever I need to deploy to my VM Application Server!

What do all the ADF/JDeveloper configuration files do?

One thing that is particularly overwhelming when starting out with WebCenter is the number of configuration files used. My background is from working on JSF based applications, particularly Richfaces. Some of the files are common but a lot aren’t and the question in my mind so often was, “What on earth is this file doing?”

This post covers a number of useful links that I have come across during my reading that explain the purpose of all the diffent configuration files.

What configuration files should I know about?

Configuration files touched when manually migrating a project.

Web User Interface Configuration

ADF Meta Files

More Files

Files affected when developing and why

Customising WebCenter Portal Spaces

This post is aimed at providing a summary of what is required and what is available when developers want to customise their WebCenter Portal: Spaces application (Renamed to WebCenter Portal from It doesn’t go into detail, however, does provide useful links to the Oracle documentation on where to go for further details.

There are a couple of options available to developers if they want to customise Spaces within WebCenter.

  • Browser – If adding spaces, tweaking/selecting templates customising portals, spaces and pages with respect to content.
  • JDeveloper – If you want to deploy additional shared libraries, include custom code or tasksflows. You can also edit skins, page templates and navigations in JDeveloper too.
  • In order to customise any Spaces in JDeveloper you’ll need to download the DesignWebCenterSpaces project available here for version This consists of a JDeveloper application which contains two projects “WebCenterSpacesExtensionLibrary” and “WebCenterSpacesResources”.

    WebCenterSpacesExtensionLibrary (
    On the Weblogic server there is already an empty extended.spaces.webapp.war and the WebCenterSpacesExtensionLibrary project in this application allows the developer to add and build a new extended.spaces.webapp.war.

    WebCenterSpacesExtensionLibrary (
    There is a zip file in this page that you’ll need for customising skins and page templates. Search for DesignWebCenterSpaces_11. download that and open the application in JDeveloper to get going.

    This project essentially contains a weblogic.xml that you can insert the shared library declarations into.

    Creating your own extended.spaces.webapp.war informs WebCenter Portal: Spaces that you are deploying customisations that the server needs to make available.

    Important Note – It is best practice to deploy your extended.spaces.webapp.war in addition to the one that comes with the server. As long as the version in the Manifest.MF file in the war is greater then this will take precedence. Keeping the original ensures that if needed you can go back to the base configuration.

    This project contains resource customisations, e.g. custom skins, page templates, page styles, navigations etc. It provides a single project that enables the developer to customise the look and feel of Spaces and allows you to make these changes from within JDeveloper. As a starting point you can export your existing application to get it’s templates and then make incremental changes to that rather than trying to start from scratch.

    How to enable iterative development in JDeveloper (Hot Deploy)

    Hot Deploy, FastSwap or interative development can be enabled easily on your WebCenter project in JDeveloper.

  • In JDeveloper click on the menu button just above your Project panel on the left hand side, select Application Properties…
  • Expand the Run list item and select “WebCenter Portal”
  • You should see the screen below. Just click on “Enable Iteractive Development” if it is not already checked, and click OK.

    Interative Development Configuration Dialog

    Interative Development Configuration Dialog

    This will enable the hot deploy of changes to JSPX, CSS etc. saving you the time to redeploy and restart the server. There is a performance hit, but for development purposes this is perfect because the performance hit is negligable during development and prevent the time wasted from server restarts.

    Getting to grips with Oracle WebCenter Portal

    I have the task of getting to grips with Oracle WebCenter Portal applications. The product I am working on provides a number of customisations to “WebCenter Portal: Spaces” that have since been rebranded as “WebCenter Portals” from version onwards.

    To get up an running the quickly I came across a VirtualBox image for another Oracle product, however, that VM is configurable to start up a WebCenter Spaces server with JDeveloper pre-installed which is exactly what I needed.

    Using the Oracle VM I am progressing through the tutorials on Oracle Fusion Middleware. The VM is based on the code, so I am sticking with those tutorials for now.

    Tutorial 1
    This tutorial introduces the WebCenter Portal. Using JDeveloper it shows how to create a new Portal application and how to deliver content from the UCM server. Topics covered are initial setup, creating a new portal, adding pages, customising the look of those pages by introducing page templates and skins.

    Tutorial 2
    This tutorial looks like the most suitable next step for anyone developing new custom portal/portal producer applications. It builds upon the previous tutorial and explains in much more detail the concepts and technology behind the scenes.

    Tutorial 3
    This tutorial looks more like a tutorial for front end administration of WebCenter Portals. It seems to cover page template customisations, skinning (CSS), building new pages and wiring them together.

    This blog, certainly in the short term will contain posts on any parts of these tutorials that weren’t obvious to me, or tips on using the VM in these tutorials to help anyone else get to grips with this stack.

    Iterative WebCenter Development and JRebel

    It is possible to develop on the WebCenter platform iteteratively out of the box, however, there are some limitations. The tutorial that Oracle provides here explains a little about what is possible. Essentially, this includes making changes to existing pages (JSPX files, templates, CSS etc), however, it doesn’t do so well at everything else.

    One product that I have used in the past that helps greatly with iterative development is JRebel.

    Relying on WebLogics JVM hotswap or FastSwap will get you so far, i.e. JSP, Servlet, EJB support classes however, JRebel will take it a step further and include JPA and CDI changes. It also supports numerous frameworks too, including Spring, Hibernate, Guice etc.

    Creating a WebCenter Portal Application & Customising a page template

    This post follows on from the previous one which is part of a series of explaining any non-obvious parts of the Oracle Tutorial.

    I am using the Virtual Box development environment which makes things a lot easier because everything for WebCenter is pre-installed and configured. This can be found here.

    In this post I will be following this tutorial.

    This part of the tutorial is essentially all in JDeveloper and goes through setting up your first project. Section 3 is just a case of following the steps, there is nothing here that I feel is worth commenting on further.

    Important note from this article is that when creating a new page template you also need to create a Page Definition as well. A page definition file is an XML file that specifies ADF bindings, page parameters, and permission settings. Various mappings and bindings used by pages and page templates are also specified. In this case, the myTemplatePageDef.xml file specifies the task flow for navigation rendering of the site, as well as parameters defining site structure paths.

    The Application Sources folder is primarily a repository for page definition files, like the myTemplatePageDef.xml file, as well as for source code in a project.

    Missing Step
    In Step 3, item 12 there is a missing step on this page. The page shows the new template that has been created, however, it is not available. You first need to make it available before being able to select it in the Configuration tab.

    To do this select the “Hidden” template, click the Edit menu and then select “Show”. This will make the template available and then it can be selected in the Configuration tab in the next step.

    Also, on the step when we need to select the Default skin. I didn’t have an drop down to select from. This was because although my skin was available the default skin wasn’t. Making this available enabled the drop down. (You can enable this by clicking on “Skins” in the “Look and Layout” menu on the left and selecting the skin, clicking the Edit menu and selecting “Show”.

    How to develop portals for Oracle Web Center

    This is going to be the first in a series of articles explaining how to get up and running with developing Oracle WebCenter Portal: Spaces.

    Note the name has changed from onwards. “WebCenter Portal: Spaces” has become just “WebCenter Portal”.

    The article will be going through the tutorials that Oracle provide here: but I will attempt to explain what I needed to do when the instructions aren’t all that clear to a newbie.

    Step 6, item 4 of this article isn’t particularly helpful. It instructs the reader to upload the content into WebCenter Content. This is in fact the new name for Oracle UCM. The pre-built server that I am using only has a UCM instance, so this needs to be running for this tutorial.

    What I did here was in UCM.

  • – Login to your UCM server as user: weblogic and password: welcome1
  • – Go to Browse Content on the left hand side. Then expand Contribution Folders.
  • – Select the Contribution Folders and then click “New Item” on the right then “New Folder” to create “About Us”. I then repeated this for the other folders.
  • – Next I then selected the folder and clicked “New Item” then “New Content”. I clicked the browse button to upload the file from the expanded zip file selected a file and then gave it the same title as the file name. Saved this then repeated the process for all the other files and folders.
  • For Step 7 I didn’t do anything as it seemed to be explaining what we’d need to do but not at this point. (Following through the rest of the tutorial you do not need to do this step now)

    The next post will cover anything I did/discovered in the next section “Creating a WebCenter Portal Application