WebSphere® Portlet Factory Designer automatic synchronization of war files on local and remote development systems.
This feature keeps you from having to publish your project each time you make a change. When a change is made to your project the update will automatically be updated on the server.
Some changes to your project will require a republish, for example adding a Portlet Adaptor Builder.
There are two ways to setup Automatic synchronization in WebSphere Portlet Factory:
Determining the location of your published application
- Automatic synchronization is set up in the WebSphere Portlet Factory Project Properties dialog.
- Right click your project and select properties
- Select WebSphere Portlet Factory Project Properties
- Chose a Synchronize Mode to indicate how you want copy the development WAR file. Choose Direct to specify a file location or http to use the default installedapps directory.
- If you chose the Direct synchronize mode, In the Development WAR Location field, enter the location of the war file for your published project. See below on how to determine the location of your project war file.
- The first time you publish a project, if your Application Server is local, the location for automatic synchronization is created for you. If your Application server is remote, you will be prompted for the Published application location. You can select HTTP to use the default installedapps directory and the http protocal to update the project. To use Direct synchronize you will need to create a mapped drive to the published application or use a UNC path.
- On a locally installed application server WebSphere Portlet Factory will detect the location of your published application when you first publish it.
- On a remotely installed application server you can find the installed application in the following location. AppServerInstallationDir/profileFolder/InstalledApps/cellName For Example: For IBM Mashup Center it would be IBM\Mashup Center\2.09_7\mm_profile\installedApps\ktuttleT60Node01Cell For IBM® WebSphere Application Server only install it would be websphere\AppServer\profiles\AppSrv01\installedApps\pfsles9was7Cell01
The following caveats apply when you choose to auto-synchronize WAR files:
- The automatic synchronization feature is intended as a convenience for development use only. You should not use automatic synchronization to place a WAR file in a production environment.
- The WebSphere Portal server you are publishing to must be running.
- You do have to develop a project on WebSphere to Export it to a production WebSphere server. For example, for convenience sake you might develop a portlet on Tomcat or IBM WebSphere Application Server CE and choose Publish Application of the portlet WAR file to WebSphere Portal.
- When automatic synchronization is enabled, you must not manually un-install and republish a WAR file. Doing so will result in problems with the WAR file and WebSphere Portlet Factory publishing logic. You can, however, un-install a WAR file using the server Admin tool.
Parent topic: WAR interactions at project creation