WAR interactions during deployment to production

Portlet Factory, Version 6.1.2

WAR interactions during deployment to production

For a standalone web application deployment to a production server, run an Ant script to create the deployment WAR. You then copy the WAR to a production server and deploy the WAR. For application deployment, you either rebuild the WAR from IBM® WebSphere Portlet Factory Designer (recommended) using menu commands, or run the script to create a deployment WAR. You can then copy the WAR to a production server and deploy it.
It is not possible to synchronize the deployed production WAR from your project. To update a deployed production WAR, rebuild the WAR and then redeploy the WAR to a production server, or update the deployed WAR using the rebuilt WAR.
Note: If you use your Portal tools to remove a deployed portlet WAR file, and you then attempt to redeploy the WAR again using WebSphere Portlet Factory, problems will result because some portals (such as WebSphere) leave remnants of the removed WAR file on the server. These remnants can conflict with the redeployed portlet WAR. As a result, you might need to modify your portlet root directory properties in the Create Portlet Factory Project Wizard to correctly point to the newly deployed portlet.
Note: WebSphere Portal versions are not always identical. As a result, problems can occur if you develop an application using one version of a portal and deploy that application to another version of the portal. Make sure that the version of the portal that you develop and build an application with is the same version that you deploy against.
Parent topic: Deployment configurations for widgets

Library | Support |