Configuration Manager (CM) Considerations

Edit online

Refer to the following considerations when configuring CM:

  • Configure an engine with only one CM. If you use more than one CM, the engine accepts only the CM configuration with a higher version number than its own and with the engine name defined at the first connection.
  • If you configure CM to use a port already in use by another application, CM will not start.
  • If you upgrade CM from version 3.2 to version 3.3.01 or later, information about Configuration Manager from version 3.2 is maintained in the new installation to allow the CM from version 3.2 to continue to work for both engines. If you want to change the url used to connect to the server in version 3.3.01 or later, click the Advanced menu. Then select the SSO Configuration to modify. Modify the value in the Default Landing Page field. You must also delete the default.app.url property defined in the adapter on the Properties tab; otherwise, the property overrides the value defined in the SSO Configuration.
  • When you access CM with a browser, a session time-out occurs, if the session is idle for 30 minutes. The Monitoring screen is periodically refreshed, which prevents a session time-out. If the Monitoring screen is displayed as the active application and is not minimized, it does not time out. If you select Monitoring and then minimize the application, a time-out occurs. After a time-out, you may have to login to CM again. Enforce desktop security to prevent unauthorized access to CM.
  • When you configure a node in a netmap, complete all required fields before you copy a policy or add a new policy. Otherwise, an error message is generated.
  • When you configure an adapter, complete all required fields before you copy or create a netmap. Otherwise, an error message is generated.
  • If you are using Mozilla Firefox, do not open two login sessions on a computer; otherwise, the second login page is blank.
  • If you use Mozilla Firefox as your browser and you clear the cache while using CM, restart the browser. Otherwise, it may display unpredictable results.
  • If you use Mozilla Firefox as your browser and you upgrade Secure Proxy, clear the cache before you use CM. Otherwise, it may display unpredictable results.
  • If you do not store the certificate in the trusted store and you are using Mozilla Firefox, you receive an error message. Adding the CM certificate to the trusted store prevents this error.