Installation Guides › Implementation Guide › Architectural Considerations › Implementation Considerations › Determine if Virtualization is to be Used

Determine if Virtualization is to be Used

Will SOA Security Manager be implemented to a virtual environment?

Consider the following before implementing SOA Security Manager to a virtual environment:

• Be sure to review the CA policy on virtualization.
• Be sure to:
  • Understand the virtual environment and the performance overhead the host system can impose on applications.
  • Tune the virtual environment to eliminate as much as the performance overhead as possible.

    Note: For more information about performance tuning the virtual environment, see the vendor–specific documentation.

• Be sure to size the CPU, disk space, and memory available to the virtual environment. Use the system requirements detailed in each SOA Security Manager installation guide to determine how many components to deploy to the entire system.
• Be aware of issues associated with clock synchronization and multiple operating systems. Unsynchronized clocks can result in unexpected SOA Security Manager behavior.
• When considering where to deploy components:
  • We recommend deploying Policy Servers to the virtual environment. We recommend that Policy Servers have their own Ethernet port. A dedicated port helps to prevent SOA Security Manager from missing requests because it is competing with other virtual hosts for available bandwidth.
  • We recommend deploying Web Agents to virtualized web servers.
  • We recommend deploying all SOA Security Manager data stores to physical hardware and operating systems. Directory servers and databases can become very resource dependent. If deployed to the virtualized environment, this dependency can result in performance degradation.