Friday, February 15, 2008

Deploying BlazeDS to Weblogic 10.0

The BlazeDS is a free and open source J2EE application that provides data services to Adobe Flex and AIR applications. I’ve deployed it to Weblogic 10.0 server. I thought somebody else would be interested to do the same. Here is how.

In case you need to install Weblogic 10.0, the developers copy is available for free at http://commerce.bea.com/products/weblogicplatform/weblogic_prod_fam.jsp.

I have it installed on my Windows XP at D:\bea10 folder.

I have created a new domain for my BlazeDS applications. It is easy to do, see http://edocs.bea.com/common/docs100/confgwiz/index.html for details.

In my case, the domain name is blazeds and it is located in D:\bea10\user_projects\domains\blazeds folder on my computer. The domain name and the folders names can be difference, I just mentioned them so it is easier to follow the examples..

Once the Weblogic server is installed and a domain is ready, the BlazeDS applications can be deployed.

A copy of BlazeDS is available at http://labs.adobe.com/technologies/blazeds/. I downloaded the latest version - blazeds_b1_020108.zip and unzipped it to D:\java\blazeds_b1_020108.

There are three WAR files provided in BlazeDS distribution: blazeds.war, ds-console.war, and samples.war. Copy them to autodeploy folder of your Weblogic domain. In my case it is D:\bea10\user_projects\domains\blazeds\autodeploy.

Start the Weblogic servert. If you run it on Windows, simply click on Start -> All Programms -> BEA Products -> User Projects –> blazeds (or your domain name) -> Start Admin Server.

If everything ok, the Weblogic server log window will appear on the desktop:


Now is a good time to verify that the BlazeDS applications were deployed successfully. It is easy to do by checking the status of the applications in the Weblogic Admin console and scanning the log files for errors.

My server is configured with HTTP port 7001. My Weblogic console URL is http://localhost:7001/console. The console application asks for the admin’s name and password. Just want to remind that they were specified during the domain configuration step. Once you logged in, select Deployments in the Domain Structures window. You should see these applications deployed

I also like to check the log files for errors. The BlazeDS log file is created in

D:\bea10\user_projects\domains\blazeds\servers\AdminServer\logs folder and it is called blazeds.log. I could not find any errors in the log, which is a good sign.

Now the BlazeDS is ready. Open examples URL: http://localhost:7001/samples/. You should see a page

The BlazeDS samples use the database that is provided in the BlazeDS distribution. To start the database, open a command prompt window, navigate to \blazeds_b1_020108\sampledb folder and run startdb.bat:

Now lets test drive the BlazeDS. Navigate to the BlazeDS Test Drive page

http://localhost:7001/samples/testdrive.htm and follow the sample instructions. All sample applications worked nicely in my case. I’ve got data via HTTPService, Web Services, Java Remoting mechanism just fine.


I verified blazeds.log and AdminServer.log files for errors and could not find any. Everything run just fine.

I hope you found this post helpful. Please submit any comments or questions. I will be glad to help.



3 comments:

cc said...

Hi,

I am trying to set up blazeDS on a remote weblogic server, and I am not sure how to configure the compiler (-services) and server settings (root folder) to make it work. I keep getting errors about invalid root folder, or the web server cannot be connected. I would appreciate any pointers you can give me. Thanks a lot!

Christina

cx113 said...

that's cool, i love it
big thank you

ven512 said...

Hi,

Does this works for weblogic 9.2..?

Thanks in Advance.

-Venkat