This document outlines some of the key components of support and
development for working with WebSphere Portal 6.0 server in
MyEclipse Blue Edition. Please note that WebSphere Portal 6.1 server is also
supported and its usage is similar to that shown here. The topics covered in this
overview assume that you have read the
overview for MyEclipse. This document builds ontop of that
overview and covers those aspects of Portlet development that are
specific to developers working with WebSphere Portal 6.0 server.
This tutorial was created with MyEclipse Blue Edition. However, if you notice that
portions of this tutorial appear different from the screens you
are seeing, please
let us know and we will make sure to
resolve any inconsistencies.
WebSphere Portal 6.0 Server Support
In MyEclipse Blue Edition server connectors have been
added that support WebSphere Portal 6.0 & 6.1 servers. Once you
configure WebSphere Portal server properly, it will be
available in the Servers view along side other servers.
The WebSphere Portal configuration is available through
connector preference page like other WebSphere Blue
connectors. There are a few new fields that are specific to
portal server users will need to pay attention to. The most
important are the portal server home directory and the portal
server specific profile along with the server name that specifies
the WebSphere_Portal server.
WebSphere Portal server requires a username/password to operate,
so those details must be provided in the Security section of the
WebSPhere portal connector.
Adding JSR 168 WebSphere Portal 6.0 support to a
In order to develop applications to be deployed to WebSphere
portal, you will need to add JSR 168 Portlet capabilities to your
webproject. You can add this support by invoking the
"Add JSR 168 Portlet Capabilities..." action enabled on
all MyEclipse Web Projects.
The Portlet capabilities wizard lets you select between 2
different portal engine runtimes. For WebSphere portal
server support you will need to select the "WebSphere Portal
6.0 JSR 168 API" item in the selection combo box.
Once the wizard completes, the project will be ready to support
new JSR 168 Portlet development that can also be deployed to
WebSphere Portal server. The last page of the "Add
Portlet Capabilities..." shows a message detailing what
types of WebSphere Portal application development that MyEclipse
6.5 Blue editon doesn't yet support.
For further information on how to enable additional JSR 168
click here to read the
WebSphere Portal Deployment Support
Once you have a portlet application configured for WebSphere
Portal 6.0 and also have added a few JSR 168 style portlets to
the project, you are ready to deploy them to WebSphere Portal
server. The only restriction on deployment is that the
portal server must be running (online) for portal engine
deployment to occur.
First during deployment the application is deployed as a normal
J2EE Web Application to the WebSphere AppServer that is runing
the portal engine. At the end of this "normal"
deployment, if MyEclipse detects that you have portlets support
added to your project, a special "WebSphere portal engine
deployment" will take place transparently.
The same thing occurs for undeployment, when you remove the J2EE
web application deployment if MyEclipse detects that your project
is a portlet project, it will "undeploy" all of the
portlets from the WebSphere Portal server.
WebSphere Portal Configuration Overview
Once you have properly deployed your project to WebSphere Portal
6.0 server you will be able to see the web application as being
deployed to the server under the "
Administration > WebSphere Portal > Portlet
managememt > Web Modules" page.
Any portlets that are defined in your web application will have
been registered with the portal server. So those portlets
will be available in the "Portlets palette" if you
search for them by name.
Once you have found them those portlets can be added to your
portal page by a simple drag and drop.
After the portlet is running on the portal server page, it acts
like a normal J2EE web application running on a server. If
the server is in debug mode, normal developmental features like
Java and JSP debugging, hot-swap and hot-sync debugging will be
In this section we want to provide you with additional links to
resources that supplement the topics covered in this overview.
While this is not an exhaustive list, we do make an effort to
point to the more popular links that should provide you with
diverse, high-quality information.
We would like to hear from you! If you liked this tutorial, has
some suggestions or even some corrections for us please let us
know. We track all user feedback about our learning material in
Please be sure to let us know which piece of MyEclipse material
you are commenting on so we can quickly pinpoint any issues that