Publishing to the IBM WebSphere Application Server JSR 168 and JSR 286 Portlet containersAdded by IBM on August 31, 2010 | Version 1 (Original)
|If you are developing a portlet, you can use the JSR 168 and JSR 286 containers that ship with WebSphere® Application Server to run standalone portlets outside of the IBM® WebSphere Portal server environment.
If you are developing a portlet, you can use the JSR 168 and JSR 286 containers that ship with WebSphere® Application Server to run standalone portlets outside of the IBM® WebSphere Portal server environment.
Follow these steps to set up your JSR 168 and JSR 286 container.
- Edit your project's .deployment/excludes/portletwar.excludes file and remove the reference to jdom.jar. If you already installed the production war to the server, you can add the jdom.jar to your published application and restart.
- Export the Portlet War for your project
- If the project has already been published from the WebSphere Portlet Factory, uninstall the portlet and related development WARs from the WebSphere Application Server.
- Logon to the WebSphere Application Server Console and install the portlet WAR. Provide a context name and accept all the defaults. You must publish to server1, because WebSphere Portal security prevents the WebSphere_Portal instance from being a viable choice.
- When web application has finished installing, choose Manage Applications and choose your application. In theDetail Properties section, click Class loading and update detection. Verify that the WAR class loader policy is set to Class loader for each WAR file in your application. In the Modules section, click Manage Modules and the WebSphere Portlet Factory module and change the class loader order setting so that class loader is first.
- Save the configuration.
- Start the web application in the WebSphere Application Server Console.
- Open WebSphere Portlet Factory and run the model.
- Manually enter the URL into browser. For example:
where host and port use same value you provide when creating a WebSphere Application Server server configuration that is targeting server1. For context_name use the value you provided when installing the portlet WAR from WebSphere Application Server Console. For portlet_name enter the value you used for the portlet name input in the Portlet Adapter builder.
The model should load normally.
Excluding files from a published WAR: wpf7
WebSphere Portlet Factory provides two mechanisms you can use to exclude one or more project files from a published WAR.
JAR files in a WAR: wpf7
The creation of a development or production WAR with IBM WebSphere Portlet Factory includes a number of JAR files from the associated project.
web.xml processing and templates: wpf7
You can modify the web.xml
file and templates to customize feature sets, set properties, or to update servlet definitions and mappings.
Parent topic: Publishing a project: wpf7