Follow Us on Twitter

Extending your WebLogic standalone environment with ADF runtime libraries

by Ian Hoogeboom on January 6, 2010 · 3 comments

When setting up your WebLogic platform with domains and servers in a production environment, you don’t want to extend the AdminServer with ADF or even deploy applications in it. In larger (clustered) systems, the AdminServer could not even be present on the same machine. You can start (of may have started) with a clean WebLogic install, creating an AdminServer and, for production of course, a separate WebLogic server. This makes ADF configuration a bit harder than just plain ‘next, next, next, Norwegian’.

Lots of detailed guides are available on how to do this, I even recommend reading more detailed information on all kinds of SOA subjects at the Java / Oracle SOA blog of my colleague.

Below, I have briefly described how to extend your existing or newly created WebLogic environment with the ADF run-time libraries.

Installing the ADF software for extending the WebLogic Domain

When running one of the following ‘installers’, you only place the ADF run-time libraries in the middleware home, but the WebLogic domains are not extended automatically:

  • Soa Suite and Repository Creation Utility (rcu);
  • Oracle Application Developer;
  • JDeveloper (de-select JDeveloper Studio).
Oracle Application Developer

Oracle Application Developer

JDeveloper Installer

JDeveloper Installer

You need to run the Fusion Middleware Configuration Wizard when you want to really extend your domain including the existing WebLogic servers within that domain.

Extending an existing WebLogic Domain or new Server through Fusion Middleware Configuration Wizard

So, you still need to actually extend the domain and existing servers by running the Fusion Middleware Configuration Wizard (middleware_home/wlserver_10.3/common/bin/config.sh).

While you extend the domain, you can also select servers or create new servers as targets where ADF should be deployed.

Since version 11.1.1.0 (or WLS 10.3.2) ADF is now called Oracle JRF, so don’t get confused if you can not find ‘ADF’, but see Oracle JRF instead.

With this utility, you can also add Enterprise Manager now, or extend your domain with it later.

Fusion Middleware Configuration Wizard

Fusion Middleware Configuration Wizard

Select Oracle JRF to extend you domain with it.

Setup extra domain options

Setup Extra Domain Options

You can create a new Managed Server now or add only the ADF Deployments and ADF Services to the extsiting ones.

Setup targets for JRF

Setup targets for JRF

By default, the AdminServer gets all the ADF stuff, but I have clear it all for the AdminServer and added the Libraries for the new or existing target. I don’t want the extra applications.

Setup JRF Services For Targets

Setup JRF Services Targets

Also for the Startup/Shutdown classes, I have removed them from the AdminServer and selected them all for the new or existing target.

Extending an existing WebLogic Server on an already ADF enabled Domain through Enterprise Manager

If your Domain was already extended with ADF, but an existing server was not, you can apply the JRF template to it.

You need to go to the Enterprise Manager for this (http://ip:port/em), go to the WebLogic Domain, open the domain/server-tree and select the server without ADF.

In the detail screen, you will find a ‘Apply JRF Template’ button. If you press this button, this server will be extended with the ADF libraries and some example application will be deployed.

Applying JRF Template

Applying JRF Template

Oracle Enterprise Manager

If you did not install the Oracle Enterprise Manager when extending your WebLogic domain, you can add it also through the Fusion Middleware Configuration Wizard.

Installing Oracle Enterprise Manager

Installing Oracle Enterprise Manager

Creating a new WebLogic domain

With the Fusion Middleware Configuration Wizard, you can also create new domains, including the ADF runtime libraries and Oracle Enterprise Manager, after you placed the ADF runtime libraries with one of the ADF ‘installers’ (see Extending the WebLogic Domain).

Tip Developing ADF applications

If an application is developed with JDeveloper, it can be tested with an internal WebLogic server, fully loaded and pre-installed with ADF run-time libraries and other goodies which are not present in a standalone WebLogic environment.

When having troubles deploying an ADF application (wrapped in an EAR), try to deploy an empty ADF application. If this works, add some functionality and try again. Try to figure out the differences, this can be much faster troubleshooting when trying to solve deployment issues with a larger application packed with functionality, libs and jars).

Also try to pack the EAR/WAR with no ADF libraries selected in JDeveloper under application properties WEB-INF/lib (war level) and Application Libraries (EAR level). Lots of stuff is available in WebLogic when its extended with the ADF libraries.

Extending your WebLogic standalone environment with ADF runtime libraries, 4.5 out of 5 based on 4 ratings
Ratings:
VN:F [1.9.22_1171]
Rating: 4.5/5 (4 votes cast)

{ 2 comments… read them below or add one }

Mr. Anderson May 12, 2011 at 10:22 pm

Unfortunate this is by hand, is there any to do thos across many managed servers in a domain in a scripted fashion?

Reply

Patrick October 1, 2013 at 9:58 am

@Mr Anderson,
To script this accress many managed servers, use:
applyJRF(target=’my_cluster’, domainDir=’/fmw/domains/my_domain’)

Reply

Leave a Comment

 

{ 1 trackback }

Previous post:

Next post:

About Whitehorses
Company profile
Services
Technology

Whitehorses website

Home page
Whitebooks
Jobs

Follow us
Blog post RSS
Comment RSS
Twitter