Installing › Preinstallation › Planning Your DevTest System

Planning Your DevTest System

In order to successfully install DevTest Solutions, consider the following decision points prior to the installation:

• What supported operating system do you plan to use?
• Are you performing a shared or local installation?
• Is the installation targeted for workstation or server use?
• Which enterprise database do you plan to use?

  If the installation is a permanent installation or you intend to use it in an environment that is generally available, the supplied Derby database is not supported.

• Do you plan to install the Demo Server?

  The demo server is supplied separately from the product installer.

Before beginning an installation, the license file (devtestlic.xml) must be available and present on your target system.

Additional considerations regarding the ideal layout of the various services and processes within the target systems:

• The Enterprise Dashboard must be reachable by the registry, but it does not need to be local to the registry. The Enterprise Dashboard requires its own database instance.
• The registry and the coordinator should reside on the same machine, wherever possible.
• The simulators should be on the same network segment as the coordinator, if practicable.
• The registry, coordinator, simulators, and any virtual service environments require high-performance database access. Performance data is recorded directly to the database by these components. CA recommends that the database be present within the same data center. Databases hosted within a virtual machine are not recommended for general availability use.

For more information about database requirements, see Database System Requirements.

Before you begin planning your DevTest system, review the Release Notes for the release you install. If you are migrating a system, review the Migration Guide.

Part of planning a DevTest system is deciding how many DevTest Servers to install and what processes or services to run on each host computer containing a DevTest Server.

When you download the DevTest Solutions installers, you can select one of three products, all of which point to the same installers. DevTest Components depicts graphically these three products with product-specific UIs and processes and the common UI and processes shared by all products. About DevTest Server Components describes the purpose of each process and where you can find more details.

Example Relationships in a Distributed System introduces major concepts concerning what processes you can run on each host in a distributed system. The Post-Installation section addresses topics that can help you tailor your distributed system; specifically:

• Running components on different systems
• Calculate simulator instances
• Load and performance server sizing

Another aspect of planning is designing naming conventions for your project directory structure.

You can use the JRE that comes with DevTest or you can install your own. For more information, see Using DevTest Workstation with your Java environment.