Summary

A system administrator asks:

1. Within the WebSphere Application server (WAS) environment, it is possible to restart an Enterprise Application as a "warm deploy" even across a network deployment?  This helps support multiple applications within one WAS server environment.

2,. When does Process Commander require a complete restart, including JVM re-initialization?

Suggested Approach

Having more than one application deployed on multiple app servers and then trying to balance across many servers increases your performance tuning challenges.  In addition, without a full restart you have static items hanging around in JVM memory that may degrade performance. 

When you restart Process Commander, you ordinarily need to do a full JVM restart, not just a system start and stop, to clean up the memory optimally.  In addition, the native DLL library that Process Commander uses for performance and tuning measurements (in a Windows environment) can provide more granular measurements after full JVM restarts. 

However, unlike traditional J2EE applications that may require full restarts and even full redeployments in order to exploit code changes, there are many changes you can make, such as .rule updates within the Process Commander application -- without affecting the application server.  For such changes, there is no need to restart Process Commander or to do a JVM stop and start.