Installing WebSphere 6.1, JAX-WS, EJB 3.0 and Updates

Introduction
System Requirements

What You Will Need

Installing WebSphere 6.1
Disabling the Windows System Service
Installing the WebSphere Update Installer
Applying WebSphere Update 6.1.0.13
Installing the Web Service Feature Pack
Applying Updates PK53084 Interim Fix and Web Service Feature Pack
Installing the EJB 3.0 Feature Pack
Profile Management & Augmentation

Augment a Profile
Create a New Profile

Resources
Feedback

1. Introduction

MyEclipse Blue Edition provides support for JavaEE technologies, like JAX-WS and EJB 3.0, that are available for WebSphere 6.1 in the form of feature packs but not installed out of the box. This guide will walk you through the process of not only installing WebSphere 6.1, but also the 2 feature packs and any updates currently available.

Due to the complexity of the process of installing not only these feature packs into WebSphere 6.1, but the updates that must be installed as well, we have tried to document all those steps for you in an easy-to-follow format below.

2. System Requirements

This tutorial was created with MyEclipse Blue Edition 6.1, WebSphere 6.1 and the associated Web Service and EJB Feature Packs (as well as 3 update packs) all on Windows Vista. If you are using a another version of MyEclipse Blue Edition (possibly newer), most of these screens and instructions should still be very similar.

If you are on Unix/Linux please see the appropriate WebSphere docs to guide you through the exact programs to launch that are synonymous with the ones outlined in this Windows tutorial. If there are comparable executables on Linux, the instructions, except for the directory paths, will be very similar and should be easily followed for your own needs.

NOTE: There is no WebSphere install for Mac, so it is not addressed here.

If you are using a newer version of MyEclipse and notice portions of this tutorial looking different than the screens you are seeing, please let us know and we will make sure to resolve any inconsistencies.

2.1 What You Will Need

This document looks fairly sizable because there are many steps covered in it and you will need a handful of different pieces of software to complete it. We will outline what we used below and potential alternatives that you might have access to:

WebSphere Application Server 6.1 Install (We used a ZIP, CD/DVD should work as well) - 518 MB
WebSphere Update Installer 6.1.0.13 (We used a ZIP, CD/DVD should work as well) - 75.8 MB
WebSphere Application Server 6.1.0.13 Update PAK (.PAK file) - 468 MB
WebSphere 6.1 Web Service Feature Pack (We used a ZIP, CD/DVD should work as well) - 585 MB
WebSphere 6.1 PK53084 Interim Fix PAK (.PAK file) - 7.7 MB
WebSphere 6.1 Web Service Feature Pack Fix PAK (.PAK file) - 47.5 MB
WebSphere 6.1 EJB 3.0 Feature Pack (We used a ZIP, CD/DVD should work as well) - 687 MB

These were all the installers, packs and PAKs used for this tutorial. If you are reading this tutorial at a later date and additional Feature Packs or update PAKs are available, you should make sure that none of the additional updates interfere with the functionality of the Feature Packs outlined in this document first. Chances are you would be fine to add any newer updates or Feature Packs though.

3. Installing WebSphere 6.1

Installing WebSphere 6.1 is a fairly straight forward process. If you downloaded it in the form of a ZIP file, go ahead and unzip it. If you got a CD or DVD with it on it, insert the disk.

If the startup installer app doesn't launch and you need to launch it manually the name of the executable is launchpad.exe, you can double-click it to run it:

After Launchpad starts you want to click the first option, to run the WebSphere Application Server installer:

NOTE: If for some reason the link doesn't work (for example on Vista due to security restrictions), you can close Launchpad and launch the WebSphere Application Server installer by going into the WAS directory, and running install.exe.

Once the installer has initialized itself and started up, you will see this screen:

For the most part, taking the defaults and simply "Nexting" your way through the installation is fine. On the Administrative Security portion of the wizard we do want to disable that feature by unchecking the box:

This tutorial is geared towards a development install of WebSphere Application Server, which is why we don't need the Administrative Security enabled.

After hitting Next here, you should be presented with a summary of the install actions to be performed and hitting Next again should begin the installer:

After the installer is done you can click Finish and then the First Steps console will open.

The frist thing to do with a new install of WebSphere Application Server is to click the Installation verification link off the First Steps console:

After clicking Installation verification, a console window will open up and WebSphere will be started, displaying it's startup log to the console window.

You are looking for verification success messages at the end of the console log before the installation is verified. This can take up to a few minutes to display on a slower machine, or within about a minute on a faster machine:

Once the installation has been verified, you can close the console window, and back on the First Steps console click Stop the server.

You can now close the First Steps console, your installation of WebSphere Application Server is complete.

4. Disabling the Windows System Service

By default, when WebSphere Application Server is installed, the installer adds a Windows System Service to your system that runs WebSphere on boot automatically. This is typically only necessary on a production server, but on a development machine, starting an entire application server on startup not only slows down your startup, but it will also conflict with managing WebSphere from inside MyEclipse Blue. Because of this, we want to disable this system service to make sure it doesn't start on bootup.

On Windows XP you can simply click on the Start Menu, then Control Panel and then Administrative Tools and Services to find the list of system services. On Vista, you can open the Start Menu and immediately type "Services" into the filter box to find the link:

After bringing up the Services dialog, you want to scroll down and look for the service named IBM WebSphere Application Server V6.1 and likely the computer node name after that. After selecting the service, you can right-click and select Properties or double-click the entry to bring up it's service properties.

On the service properties dialog, you want to set the Startup type to Disabled (You can also set the type to Manual if you like):

NOTE: At this point if the service is still running, you can click Stop from this screen to stop it.

Now you can hit OK and continue following the tutorial. WebSphere Application Server is installed, verified and the service disabled. You are ready for the next steps.

5. Installing the WebSphere Update Installer

WebSphere Application Server updates are installed by using the WebSphere Update Installer to install PAK files that represent updates for the server.

To install the WebSphere Update Installer, either unzip the ZIP file you received or insert the CD or DVD in your computer. If the installer does not autostart for you, you may need to drill down to find it. If the root contents of your CD, DVD or directory looks like this:

You will want to drill down into the UpdateInstaller directory and find the installer.exe file, then double click to run it:

After running install.exe the welcome screen for the WebSphere Update Installer will popup:

You can "Next" your way through the installer, selecting most all the defaults if you like. On the last page of the wizard, the installer asks you if you want to launch the WebSphere Update Installer, but we haven't downloaded the PAK files yet to install, so uncheck that and click Finish for now:

We will actually run the Update Installer twice through out this tutorial, first to apply the WebSphere Application Server 6.1.0.0 -> 6.1.0.13 patch, and then again to apply two separate patches (Interim patch and Web Service Feature Pack patch).

Now the WebSphere Update Installer is installed, we are ready to continue to the next part of the tutorial.

6. Applying WebSphere Update 6.1.0.13

This is the first update we will apply to WebSphere Application Server; it will update the server from version 6.1.0.0 to 6.1.0.13.

To apply this PAK file, as with any other PAK file, we have to download it, and move the PAK file into the maintenance directory of the WebSphere Update Installer. In our case, since we installed the Updater Installer into the C:\Program Files\IBM\WebSphere\UpdateInstaller directory, the directory we want to place PAK files is:

Once we drop the update PAK file ( 6.1.0-WS-WAS-WinX32-FP0000013.pak) into that maintenance directory, we run the Update Installer by double-clicking the update.exe file in that directory, or running it from the Start Menu:

IMPORTANT NOTE : Because of the revised permission control on Windows Vista, if you have installed WebSphere Application Server to your C:\Program Files directory, you are encouraged to right-click on the Update Installer windows shortcut, and select Run as Admnistrator to ensure the update doesn't fail due to permission problems:

After launching the Update Installer and hitting Next you will be asked for the installation directory of WebSphere Application Server. By default the Update Installer should have found it and is showing it to you, but double check to make sure it's correct.

After hitting Next again you will be prompted if you want to Install or Uninstall a maintenence package, in this case we want the default which is Install. After hitting Next you will be asked for the directory containing your maintenance package files (PAK files), and as you remember we used the /maintenance directory under the Update Installer's install directory, which by default should be chosen and displayed to you:

After correcting the directory or confirming the default, the Update Installer will show you the update packs it has found and ask you to confirm/select the ones you want to install. In our case you should only have 1 update pack listed:

Hit Next, and the installer will verify the action you are about to perform and ask you to confirm it, go ahead and click Next again and the update process will begin:

NOTE: Given the size of the update package being applied, on a fast machine this can take 2-5 mins, on a slower machine it could take up to 10 mins or more to run.

Once the update is done applying the Update Installer will confirm that the process is complete:

WebSphere Application Server is now upgraded to 6.1.0.13 and you are now ready to move onto the next portion of the tutorial.

IMPORTANT NOTE : If the update process fails at any point, you can try and re-run the Update Installer, it will automatically attempt to recover the failed update. If recovery fails it is possible that a server resource is locked due to a hung server process or running server. Be sure the server is stopped and you even may want to reboot your computer before trying to recover the update process to make sure all open file handles are closed.

7. Installing the Web Service Feature Pack

Now that WebSphere is properly updated to the latest version, we are ready to install the Web Services Feature Pack, which will add support for the Java EE Web Service Specification: JAX-WS.

The Web Service Feature Pack is installed by way of a stand alone installer contained inside the ZIP or CD/DVD you have to install it from. Either unzip the ZIP file or put the CD/DVD into your computer, then find and run the installer.exe file if the installer doesn't automatically start. You might have a subdirectory named WEBSV you need to look in to find it:

IMPORTANT NOTE : Because of the revised permission control on Windows Vista, if you have installed WebSphere Application Server to your C:\Program Files directory, you are encouraged to right-click on the installe.exe executable, and select Run as Admnistrator to ensure the update doesn't fail due to permission problems.

After running the installer you will be presented with the welcome screen:

You can "Next" your way through the screens of the installation wizard, agreeing to the license, confirming your WebSphere Application Server directory installation path and then the wizard will begin installing the Web Service Feature Pack:

After the installation is complete, the wizard will give you a summary of everything that was installed:

and after clicking Finish the Profile Management tool will open automatically for you. We don't need to do anything with it at this moment, so you can go ahead and close it.

You have now completed adding the Web Service Feature Pack to your WebSphere install. You are ready to continue on to the next section.

8. Applying Updates PK53084 Interim Fix and Web Service Feature Pack

Now that we have updated WebSphere and added the Web Service Feature Pack, we need to apply two updates for the Web Service Feature Pack that are available:

6.1.0.9-WS-WASWebSvc-IFPK53084.pak
6.1.0-WS-WASWebSvc-WinX32-FP0000013.pak

Both of these files, because they are PAK files, must be copied or moved into the /maintenance directory that we used for Step 6:

And as we did before with the WebSphere update, we now want to run the Update Installer again by launching it from the Start Menu.

As before we "Next" our way through this wizard, confirming the WebSphere install to upgrade and so on. When we reach the page showing us a list of updates to apply, there are two listed:

At this point you can only select the 6.1.0.9-WS-WASWebSvc-IFPK53084.pak and apply it, so go ahead and select only that 1 patch and apply it first:

After it is done, click Relaunch (or Finish, then manually restart the Update Installer) and walk your way back through the wizard to the point where the only remaining update is listed, and select it:

Now the updater will run and apply that last update to WebSphere:

Once that has applied, you can click Finish, you are all done updating the Web Service Pack Feature and are ready to move on to the next step.

9. Installing the EJB 3.0 Feature Pack

The last step for our Tutorial is to install the EJB 3.0 Feature Pack for WebSphere Application Server 6.1. Installation of this pack will work identically to how installation of the Web Service Feature Pack went, more specifically, you either unzip the ZIP file you have for it and run the install.exe or insert the CD/DVD in your computer and do the same (if the installer doesn't automatically startup for you). The installer may be contained inside of a directory named EJB 3.0:

After running the installer you will see a familiar welcome screen as we have with the other installers:

From here things should be quite familiar. We can "Next" our way through this wizard, confirming the WebSphere installation location and eventually agreeing the summary screen which will start the install process:

After the installation has completed, the wizard will show you a summary of the installation as we have seen so far:

You can now click Finish. That will close the EJB 3.0 Feature Pack installer but will automatically open the Profile Management tool. We are going to cover Profile augmentation in the next section. So you can leave the Profile Management tool open and continue to the next section, or close it and reopen it at a later date to continue.

10. Profile Management & Augmentation

Now that all the updates and feature packs have been installed correctly into WebSphere 6.1 you have two choices to begin working with the new technologies:

Create a new profile based on the feature packs
Augment an existing profile to add support for one of the feature packs

NOTE: At the time of this writing it does not seem possible to expose an EJB 3.0 bean as a JAX-WS web service as defined in the Java EE 5 specification for profiles with both the EJB 3.0 and JAX-WS feature packs installed. IBM should likely fix this in a future update.

10.1 Augment a Profile

If you choose to Augment an existing profile, you want to launch the Profile Management Tool from the Start Menu:

and select the Augment option when asked:

At that point you will be asked to select the profile you wish to Augment:

After selecting the profile and clicking Next, you will be prompted to select the augmentation you would like to apply to the profile:

NOTE: At the time of this writing there seems to be a bug with WebSphere 6.1 such that existing profiles can only be augmented with the EJB 3.0 feature pack and not the JAX-WS feature pack. The only way to get JAX-WS support is to create a new profile based on that feature pack.

After selecting the augmentation you wish to make and clicking Next, WebSphere will make the necessary changes (it may take a few minutes).

10.2 Create a New Profile

If you choose to create a new profile, you will want to launch the Profile Management Tool from the Start Menu:

and when prompted, click to Create a new profile:

On the following screen you will be prompted to select the features you would like to base the new profile on:

NOTE: At the time of this writing, you cannot augment an EJB 3.0 profile with JAX-WS, in order to create a profile that uses both feature packs, you must create a JAX-WS profile first, then augment it with the EJB 3.0 feature pack immediately after.

This process, as expected, will generate a new profile for WebSphere based on the platform technology selected. You can now use the profile or augment it further with additional features if desired.

11. Resources

In this section we want to provide you with additional links to resources that supplement the topics covered in this tutorial. 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.

12. Feedback

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 our Documentation Forum. Please be sure to let us know which piece of MyEclipse material you are commenting on so we can quickly pinpoint any issues that arise.