# Installation Guide

# Appendix A: Installation Best Practices

Depending on the nature of your enterprise system and your supporting environment, you can make choices during the installation of ALSM that can optimize its performance.

The ALSM installer allows you to install all ALSM components into a single container. This installation scenario is useful for demonstrations and for learning how to use the product. However this scenario might not scale successfully for a number of reasons.

As with any software, you want to use resources efficiently. Therefore, you might want to separate some of the ALSM components and install them on different machines and/or in different containers. For example, depending on what your service level monitoring requirements are, it may be best to put the service level management components into their own environment. This will lessen the impact on memory resources by dividing processes across CPUs/ environments.

Your logging demands also impact system performance. For example, if you log all messages, rather than, say, only messages that generate exceptions, you might want to install exception management components into their own environment.

Finally, if you install all components into a single container and then run into memory problems, it will be hard to diagnose which part of the system is causing the problem. Memory and CPU usage will vary depending on the number of services, correlations, operations in your system, as well as what you configured ALSM to do.

To install different components into different containers, note that you will need to run the installer multiple times. For example, if you want to install a sphere in one container, exception management components into another, and service level management components into a third container, you will run the installer three times.

If you are considering installing all components in a single environment for anything other than demonstrations/training purposes, please consult with BEA Technical Support.