In the 6.1.5 release the configuration and deployment process has been simplified and streamlined. This article discusses these changes.
You create server configurations to determine how and where your web applications are to be run. A single server configuration can support standalone and portlet targets and both local and remote machines. For example:
Note that one server configuration (WASCE) can support both local and remote or the IBM_WebSphere_Portal_6.0 configuration can support both standalone and portal.
Publishing and Exporting
To make these changes easier to understand, we've removed the general term "deployment" from the interface and documentation and instead we use two terms with unique meanings, "Publish" and "Export".
You "Publish" an application to test the web application on a development server. For example, right-click on a project and select "Publish Application":
to publish your application into your local WASCE development test environment.
You "Export" when it's time to place the web application in a production environment. You can export your application as:
- WebSphere Portlet Factory Application WAR
- WebSphere Portlet Factory Portlet WAR
- WebSphere Portlet Factory WAB for rich client
depending on your production server environment.
For example, right-click on a project and select Export and WebSphere Portlet Factory Portlet WAR to create and copy an application WAR to your remote production WebSphere Portal server.
See the WebSphere Portlet Factory 6.1.5 Information Center that installs with the product for more details.