Portlet Factory, Version 6.1.2

---

 

Deploying to the IBM WebSphere Application Server JSR 168 and 286 Portlet container

If you are developing a portlet, you can use the JSR 168 and 286 container that ships with WebSphere® Application Server to run standalone portlets outside of the IBM® WebSphere Portal server environment.

1. Set up your JSR 168 container.

   1. If project is already deployed, uninstall the portlet and related development WARs from the WebSphere Application Server.
   2. Install the portlet WAR from the WebSphere Application Server Console.

      Provide a context name and accept all the defaults. You must deploy to server1, because WebSphere Portal security prevents the WebSphere_Portal instance from being a viable choice.

   3. From Enterprise Applications, select your web application and Detail Properties, click on Class loading, and update the class loader order setting to class loader first.
   4. From the console select Enterprise Applications > Your application name > Manage Modules > PA_your war name.war, and set classloading to PARENT_LAST on the module.
   5. Edit your project's .deployment/porletwar.excludes file and remove the reference to jdom.jar. You do this before building the production portlet war using the WebSphere Portlet Factory designer. Alternatively, you can add the jdom.jar to your deployed application and restart.
   6. Save the configuration.

2. Run the model.

   1. Manually enter the URL into browser. For example:

      http://host:port/context_name/portlet_name where

      host and port

      Use same value you provide when creating a WebSphere Application Server deployment configuration that is targeting server1.

      context_name

      Use the value you provided when installing the portlet WAR from WebSphere Application Server Console.

      portlet_name

      The value you used for the portlet name input in the Portlet Adapter builder.

   The model should load normally.

Parent topic: Overview: deployment

---

Library | Support |