Restarting Optiva

Under normal circumstances, it should not be necessary to restart any of the Optiva applications after you have changed their configurations. For example, when you update an authentication profile, a restart is triggered by the AppDomain, effectively restarting the application.

Some changes may not be detected automatically. In this scenario, you can force an application to restart. This ensures that the cache contains the correct configuration information.

When you update the properties of an existing database connection, the PLM Process Server retains the existing connection in the browser cache. The newly updated properties, such as user name and password, are not recognized until the application is restarted.

Normally, you should not have to restart the PLM Process Configuration application itself. One exception is when you use the application to test an Oracle database connection. Then, you manually update the configuration for the Oracle data source for the PLM Process Server.

If you test the Oracle connection again or another Oracle connection, PLM Process Configuration still uses the cached information. That cached information has the Oracle data source from the first test. This can only be resolved by restarting the PLM Process Configuration application.