WebSphere Portal on z/OS

Chapter 6. Portlet development and deployment 233

Not to worry, at this stage there were undoubtedly missing JAR files and since we

would work with only half of the project, the Web application WAR, we decided to

filter them out by selecting Filter Tasks->On selected resource only as seen in

Figure 6-43.

Figure 6-43 Filter tasks option

Our next step was to create the Portlet Application project in Application

Developer by switching to a Portlet perspective, then right-clicking in the

Navigator frame and selecting New -> Project -> Portlet application project

as seen in Figure 6-44 on page 234.

234 WebSphere Portal on z/OS

Figure 6-44 Creating a Portlet application project

Figure 6-45 on page 235 shows the settings we provided to define our Portlet

project which we decided to call TraderPortlet. After entering the project’s

settings we clicked on Finish since we did not want Application Developer to add

portlets for us, because we will use the TraderWeb.war Web application as our

base for a portlet.

Chapter 6. Portlet development and deployment 235

Figure 6-45 Define the Portlet project

After clicking on Finish, Application Developer creates and populates the project

for us as shown in Figure 6-46 on page 236.

236 WebSphere Portal on z/OS

Figure 6-46 TraderPortlet project

Next we added TraderWeb.war to the project by clicking on the TraderPortlet

project name and selecting File -> Import -> WAR file, as shown in Figure 6-47

on page 237.

Chapter 6. Portlet development and deployment 237

Figure 6-47 Import WAR

Figure 6-48 on page 238 shows the location of the WAR file and the options we

set for the import.