My webMethods Server 10.11 | My webMethods Server Webhelp | Administering My webMethods Server | System Administrator Functions | My webMethods Server Configuration | Deploying My webMethods Server Components | Modifying the Polling Interval
 
Modifying the Polling Interval
If your organization is developing multiple portlets, this installation method may be more convenient than manually installing portlets one at a time. The default file system location for the Deploy folder is:
Software AG_directory \MWS\server\serverName\deploy
Note:
Polling can be turned on or off by modifying the PhaseProvider.xml configuration file on the server's file system. Use the following instructions to modify the polling interval.
*To modify the polling interval
1. At a command line prompt, type the following command to move to the server’s bin directory:
cd Software AG_directory\MWS\bin
2. Retrieve the phaseProvider.xml file from the My webMethods Server database, using the getconfig command, as follows:
mws getconfig phaseProvider.xml
3. Navigate to the following location:
Software AG_directory \MWS\server\serverName\config
4. Open the phaseProvider.xml configuration file in a text editor or equivalent XML editing facility. Locate the following XML fragment:
<Phase name="deploySync" enabled="true"
class="com.webmethods.portal.system.init.impl.MasterServerPhase">
<PhaseInfo name="startTimedSyncDeploy" enabled="true"
class="com.webmethods.portal.bizPolicy.biz.install.impl.
SyncDeployService" interval="5" />
</Phase>
5. To turn polling off, change the enabled attribute from true to false.
6. To change the polling interval, modify the interval attribute to the desired value. The default setting is 5 seconds.
Note:
This setting will not have an impact on overall performance
7. Save the file.
8. Deploy the revised file to the My webMethods Server database, using the putconfig command, as follows:
mws putconfig phaseProvider.xml
9. Delete the file from the \serverName\config directory.
If you do not delete the file, this server instance will continue to use the local version of the configuration file.
10. Restart your server instance.