An important note about Moves and your Browser (IE11, Firefox and Chrome)There are several things to keep in mind about the Moves and Tomcat servers.the Browser that you are using. - If you have a problem with SyncMavenApps responding with either a “timeout” or a “no data received” error. These SyncMavenApps errors occur, in part, because, in some browsers, the browser response timeout defaults to 5 minutes. Currently, SyncMavenApps takes about 6 minutes to complete.
- If you are using Firefox: the following must be done:
- Update Firefox to version 31.0.
- The response timeout must be increased by doing the following:
- Open Firefox and enter about:config for the URL and click the “I’ll be careful, I promise!” button.
- Search for the Preference Name network.http.response.timeout.
- Change to default value of 300 to a new value of 3600.
- Restart Firefox.
- If you are using IE 11: update to the most current version. No other changes are needed. The response timeout default is 1 hour.
- If you are using Chrome: the response timeout defaults to 5 minutes and cannot be changed. Use either IE11 or Firefox
- There are 3 Server Tiers. These Server Tiers are TEST servers, QA servers and PRODUCTION servers. The servers within any Server Tier are NON-CLUSTERED Tomcat servers. This means that each individual server within any Server Tier should be thought of (relative to Moves) as an independent, stand alone server. This is different from what is currently being done with the OAS servers.
- There is NO CLUSTER management with the tomcat servers. What this means is that if Moves fails to deploy an application's war file, then human intervention is required to determine what has failed and how to recover from the failure. There is no automatic fail-over/role-back mechanism.
Moves uses the Tomcat manager to deploy an application's war file independently and directly to each Tomcat server within a Server Tier. This is different mechanism from what is currently being used with the OAS servers- .
|