Isolate Sybase Control Center from other servers to avoid performance problems and overwriting Sybase environment variables.
Install Sybase Control Center on a dedicated system, particularly in a production environment.
Installing Sybase Control Center on a Windows or UNIX machine with another Sybase server can disable the pre-existing server. To check for the presence of other Sybase products that might be disabled by Sybase Control Center, look for a SYBASE_UA environment variable. SYBASE_UA is present on systems where certain Sybase servers are installed, including Adaptive Server Enterprise, Replication Server, Risk Analytics Platform, or RAP – The Trading Edition.
- Windows: If you find a SYBASE_UA environment variable on a Windows machine, do not install Sybase Control Center unless you remove the other server first. Installing Sybase Control Center disables Sybase products that are already installed.
- UNIX: If you find a SYBASE_UA environment variable on a UNIX machine, identify the directory in which the existing Sybase products are installed (sybase is the default) so you can install Sybase Control Center in a different directory. For example, if an existing /work/sybase directory contains Replication Server, you can install Sybase Control Center in /work/sybase_scc.
A Sybase Control Center server can monitor up to 15 resources (servers). To monitor more than 15 resources, install additional Sybase Control Center servers and distribute the resources among them. Install each Sybase Control Center server on a separate machine.
Warning! Do not install Sybase Control Center on a machine that is being used as a production server for any other product. Sybase Control Center collects and stores performance data for every server it monitors, using CPU cycles, network resources, and disk space in significant quantities. Running two (or more) servers on the same machine can result in unacceptable performance from all products.