File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Websphere and the fly likes WebSphere and DB2 architecture Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WebSphere and DB2 architecture" Watch "WebSphere and DB2 architecture" New topic

WebSphere and DB2 architecture

Sharon whipple
Ranch Hand

Joined: Jul 31, 2003
Posts: 294
Hi guys
I used to work with Oracle tools
bc4J as the Business Components
Oc4J as the application server
Jsp/ servlets
Struts as the application framework implementing MVC

Recently due to business changes, we need to build a replacement for the previous application using IBM technologies, and if the pilot will work, we will convert the application.
The technologies we are going to use are:
WebSphere portal as the web server,
Portlets as the web interface.

I�m overwhelmed of the new technologies out there (Hibernate,Spring Ejb3) and I will be glad if you can explain what should we use for framework and Business Components.

Thank you
Sharon Whipple
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper

Joined: Aug 26, 2006
Posts: 4968

There are certainly alot of choices out there.

First of all, IBM provides a Struts wrapper for the portal, so you can port your existing Struts to have a portlet interface with just a little bit of work.

With IBM, the focus going forward really seems to be JSF in the portal world, so, I always go with JSF for new, complex portlet interfaces.

Remember, not every portlet is a framework portlet. Using the JSR168 API alone to deliver content is just fine. On that topic, here are a few other JSR168 portlet developement best practices for WebSphere, and any other portal server such as liferay or JetSpeed2 for that matter:

Best Practices for Portlet Development

The delivery of content to portlets should be services out as much as possible, whether that is leveraging the actual IBM PortletService capabilities, or having the portlets interact with a web service to access data. The web service can then be implemented just about any way you like, as it is hidden from the portlet. Hibernate/Spring/EJB2.x, it doesn't matter if the portlet/client only interacts with an interface.

Those are just some ideas. Let me know what you think.

-Cameron McKenzie
[ April 22, 2007: Message edited by: Cameron W. McKenzie ]
I agree. Here's the link:
subject: WebSphere and DB2 architecture
jQuery in Action, 3rd edition