Best practices cookbook for a new DevTest installation and verification 'out of the box', using Derby and ACL.

Document ID : KB000045156
Last Modified Date : 10/05/2018
Show Technical Document Details
Introduction:

Introduction: 

This cookbook documents the best practices when performing  a new DevTest installation and verification using the product 'out of the box' with Derby and ACL.

 

Background:  

A condensed listing of the important points to be concerned with when doing a new DevTest installation.  One should always follow the installation procedures provided in the online documentation.

 

Environment:  

All supported DevTest Releases and Platforms.

 

Instructions: 

·         Read the online documentation Release Notes section for the version you are going to be installing, and become familiar with the specific release to see which new features are available and which features may be end of life.

·         Ensure that you have a valid license.  The file-based license is valid for one year from the date of issue and will be renewed automatically as long as your support contract is up to date.  The license file is sent to an email address associated with the license for your company, so if you are not sure who will receive it, please call CA Support at 1-800-225-5224.

·         Make sure that you have downloaded the right version of the software. 

·         Read online documentation Installing section.  Verify all System Requirements to make sure you have the recommended memory and space requirements.

·         Decide whether this is going to be an upgrade in place (installing in the same folder as previous release) or a completely new install.  Recommendation is to always install to a new folder. In place upgrades are only supported for DevTest 9.0 or later.

·         Before doing an install, especially on UNIX or Linux, make sure you have enough space on the target machine. The installer will unpack to the /tmp folder and if not big enough, could get the following error:  java.io.IOException: No space left on device.

·         Install the software using the install wizard.  The license file is only associated with the Enterprise Dashboard and will be prompted for only when installing a new Enterprise Dashboard.  You only need 1 license file since it can be used on multiple machines.

·         Once the software is installed, DO NOT copy previous version local.properties, site.properties, dradis.properties (9.1.0 and later), logging.properties or lisa.properties files to your new install.    

o   If you need to change a property to a different value than that delivered in lisa.properties, update the local.properties or site.properties files.  These are delivered as templates, so copy _local.properties to local.properties and _site.properties to site.properties.  The lisa.properties file should never be modified.

o   Properties files are evaluated in the following order:

§  lisa.properties

§  site.properties take precedence over lisa.properties

§  local.properties takes precedence over site.properties and lisa.properties

§  Command line and vmoptions files takes precedence over all properties defined in any of the properties files.

 

Note: dradis.properties is only used when configuring the Enterprise Dashboard to use an external database.

         phoenix.properties used when needing to configure other than default values for the DevTest Portal.

         res-hub-config.properties used when wanting to configure a different Projects folder for the DevTest Portal.

 

 

·         If you are installing your components on different machines, make the appropriate updates to point to the correct Enterprise Dashboard in the site.properties file for where the Registry is running and the correct Registry in the local.properties file for where each Coordinator, Simulator and VSE is running.  The Broker must run on the same machine as the Registry.  You may also make the appropriate property updates in the .vmoptions files instead of the .properties files.

·       ​If you are using Derby, make sure the user that will start Enterprise Dashboard and Registry services, has the proper permissions on the $LISA_HOME/database folder.

·         Always follow this order when starting the DevTest components:

o   Enterprise Dashboard

o   Registry

o   Broker

o   Portal

o   These need be started after the Registry:

§  Coordinator, then Simulator

§  VSE

·         Verify all your DevTest components are up and running by:

o    For versions prior to 9.5.0:

§  Bring up Enterprise Dashboard URL http://<hostname or IP>:1506

§  Bring up DevTest Console URL http://<hostname or IP>:1505

·         Choose Server Console

·         View Coordinator, Simulator and VSE running

§  Bring up DevTest Portal URL http://<hostname or IP>:1507/devtest

o   For versions 9.5.0 and later

§  Bring up Enterprise Dashboard URL http://<hostname or IP>:1506

§  Bring up DevTest Portal URL http://<hostname or IP>:1507/devtest

 

 

Additional Information:

Is is considered a best practice to verify the product as installed out of the box before adding and external database or security/authentication configuration.

Please open a new case with CA Support if the installation cannot be verified after following the instructions here and in the product documentation.

Instructions:
Please Update This Required Field