System Requirements

This page describes the system requirements for the operating system, database, browser, and more. Review this page before you install .
dts105
This page describes the system requirements for the operating system, database, browser, and more. Review this page before you install
DevTest Solutions
.
2
Operating System Requirements
We do not support
DevTest
on operating systems for which the software vendor has discontinued support.
The following operating systems are supported:
  • Microsoft Windows
    • Windows Server 2012
    • Windows Server 2012 R2
    • Windows Server 2016
    • Windows 10
    Depending on the settings for Windows 9 and 10, you might have to start the installer executable as “Run as Administrator.”
  • Linux and UNIX
    (Server component support only)
    • Red Hat Enterprise Linux 6.9, 7.3, 7.4, 7.5, 7.7
    • Ubuntu 16.04.x LTS
    • SuSE Linux 11 SP4, 12 SP3
    • Oracle Solaris 11
    • IBM AIX 7.1
    • CentOS 7.5, 7.6
  • OS X 10.12, 10.13
We recommend a 64-bit operating system and JRE, especially for
DevTest Server
.
DevTest Server
JVM System Requirements
We recommend a 64-bit Java 8 for
DevTest Server
when requiring heap sizes above 1.3 GB.
Java JDK
Products composing
DevTest Solutions
are Java applications. An Oracle JRE is included with each operating system-specific installer (1.8.0_102 JRE including a
tools.jar
from the JDK) other than the generic UNIX installer. If you supply your own JVM, IBM JRE Version 8 is also supported.
The minimum supported Java version for
DevTest Workstation
,
DevTest Server
, and
VSE
is Java 8 update 60.
This requirement is a
DevTest
-side requirement only.
DevTest
running in a Java 8 virtual machine (VM) can be used to test applications on application servers running older or newer JREs.
The following table lists the support that is provided for various JDKs:
DevTest Workstation
DevTest Server
- Coordinator, Simulator, Registry
DevTest Server
-
VSE
DevTest
Java Agent (
Application Insight
)
Identity and Access Manager
Virtual Service Catalog
JDK 1.5
Not supported
Not supported
Not supported
Supported
Not supported
Not supported
JDK 1.6
Not supported
Not supported
Not supported
Supported
Not supported
Not supported
JDK 1.7
Not supported
Not supported
Not supported
Supported
Not supported
Not supported
JDK 1.8
Required for run time
Required for run time
Required for run time
Supported (WildFly 8.2 only)
Required for run time
Required for run time
DevTest
does not support IBM JRE Version 7, Oracle JRE 1.7, or OpenJDK.
Kerberos authentication is not supported on IBM JREs.
DevTest Workstation
cannot test web services and messaging backbones on different versions of Java.
The following information provides general guidance on JDK support in the
DevTest
Java Agent (
Application Insight
):
  • Application Insight
    supports systems that are based on JDK 1.5, JDK 1.6, JDK 1.7, and JDK 1.8 (WildFly 8.2 only).
  • Only JDKs from Oracle are fully supported.
/tmp Partition
When you install
DevTest
on Linux and UNIX operating systems, ensure that the
/tmp
partition has at least 2 GB of available free space.
This requirement is necessary because the installer unpacks the install in the
/tmp
partition.
If the partition does not have enough free space, you might receive the following message:
java.io.IOException: No space left on device
DevTest Locks Folder
The following folder in the LISA_HOME directory requires read/write permissions:
  • locks
In general, the rest of the LISA_HOME directory can be restricted with read-only permissions.
The lisatmp Folder
The following folder in the user home directory (on Linux, UNIX, and OS X) or Documents and Settings (on Windows) requires read/write permissions:
  • lisatmp_x.x (if it exists)
DevTest
CICS Agent
The
DevTest
CICS Agent supports the following CICS versions running under z/OS 2.1.x, 2.2.x, or 2.3.x: 4.2, 5.1, 5.2, 5.3, and 5.4
You can get the
DevTest
CICS Agent by opening a case with CA Support.
DevTest
LPAR Agent
The
DevTest
LPAR Agent supports the following z/OS versions: 2.1.x, 2.2.x, and 2.3.x
You can get the DevTest LPAR Agent by opening a case with CA Support.
Supplying Your Own JVM
The generic UNIX installer does not include a JRE. If you are using the generic UNIX installer, you
must
supply your own JVM.
Optionally, you can use this procedure with an installer for another platform to override the included JRE. See Using DevTest Workstation with Your Java Environment.
DevTest
supports IBM JRE Version 8.
DevTest
does not support IBM JRE Version 7, Oracle JRE 1.7, or OpenJDK.
If you use a Continuous Integration Server; for example, Jenkins or TeamCity, double verify that the JVM you have specified for your build has the proper JCE library installed. Some CIs use their own configuration of JVM location and do not use the
JAVA_HOME
system variable.
  • If your
    DevTest
    software is 32-bit, use Java x86 version.
  • If your
    DevTest
    software is 64-bit, use Java x64 version.
Installing and Configuring the Oracle JVM
Follow these steps:
  1. Download the Java SE Development Kit (JDK) 8 package for your platform from the Oracle website.
  2. Install JDK 8 for your operating system on the computer where you plan to install
    DevTest
    . If there is no
    java
    directory, create one (mkdir java).
    For example, install JDK 8 in \usr\java, which creates the usr\java\jdk1.8.0_102 directory (JDK_HOME).
  3. After you copy the jdk-8u65-
    platform
    . tar.gz file, enter this command:
    tar zxvf jdk-8u65-platform-x64.tar.gz
  4. Set environment variables:
    • Set the
      JDK_HOME
      environment variable to the directory where you installed JDK 8.
    • Set the
      JAVA_HOME
      environment variable to point to the
      JDK_HOME
      directory.
    For example:
    cd /usr/java/jdk1.8.0_102
    pwd
    export JAVA_HOME=$PWD
    export JDK_HOME=$PWD
  5. Extract the UnlimitedJCEPolicyJDK8 folder from the jce_policy-8.zip file. Move the following JAR files from this folder to the
    JDK_HOME\jre\lib\security
    directory:
    • local_policy.jar
    • US_export_policy.jar
    This action replaces the existing JAR files with the same names.
  6. Copy the
    tools.jar
    file from the
    JDK_HOME\lib
    directory to the
    JDK_HOME\jre\lib\ext
    directory.
    cd $JDK_HOME/jre/lib/ext
    cp $JDK_HOME/lib/tools.jar .
  7. If you are overriding the included JRE, perform the following steps after you install
    DevTest
    :
    1. Set the
      LISA_JAVA_HOME
      environment variable. For example:
      cd /usr/java/jdk1.8.0_102
      pwd
      export LISA_JAVA_HOME=$PWD
    2. Rename the
      jre
      directory under the
      DevTest
      installation directory to jre_default as described in Using DevTest Workstation with Your Java Environment.
You may get the following error when starting Enterprise Dashboard:
JVMJ9VM007E Command-line option unrecognized: ${LISA_MORE_VM_PROPS}
The JVM could not be started. The maximum heap size (-Xmx) might be too large or an antivirus or firewall tool could block the execution.
To correct the error, set the system environment variable
LISA_MORE_VM_PROPS
to
-Xmx512m
Installing and Configuring the IBM JVM
The IBM JRE has been certified only on the AIX operating system.
Follow these steps:
  1. Download the JVM for your platform from the IBM website.
  2. Install JDK 8 for your operating system on the computer where you plan to install
    DevTest
    . If there is no
    java
    directory, create one (mkdir java).
    For example, install JDK 8 in \usr\java, into the \usr\java\ibm_sdk80 directory (JDK_HOME).
  3. Copy the
    tools.jar
    file from the
    JDK_HOME\lib
    directory to the
    JDK_HOME\jre\lib\ext
    directory.
    cd $JDK_HOME/jre/lib/ext
    cp $JDK_HOME/lib/tools.jar .
  4. If you are overriding the included JRE, perform the following steps after you install
    DevTest
    :
    1. Set the
      LISA_JAVA_HOME
      environment variable. For example:
      cd $JDK_HOME
      pwd
      export LISA_JAVA_HOME=$PWD
    2. Rename the
      jre
      directory under the
      DevTest
      installation directory to jre_default as described in Using DevTest Workstation with Your Java Environment.
You may get the following error when starting Enterprise Dashboard:
JVMJ9VM007E Command-line option unrecognized: ${LISA_MORE_VM_PROPS}
The JVM could not be started. The maximum heap size (-Xmx) might be too large or an antivirus or firewall tool could block the execution.
To correct the error, set the system environment variable
LISA_MORE_VM_PROPS
to
-Xmx512m
DevTest Server Requirements
Application Test
and
Service Virtualization
require the registry in
DevTest Server
.
The minimum requirements for
DevTest Server
are:
  • CPU:
    2 GHz or faster, 8 cores minimum
  • RAM:
    8 GB available
  • Disk Space:
    50 GB
  • Database:
    See Database Requirements. The registry database can reside on a different system and must have at least 500 GB of available storage.
For load and performance testing, the following resources are recommended:
  • 250 virtual users for each simulator
  • 1 processor core and 2-GB available RAM for each simulator
Example for 4000 concurrent virtual users: 16 simulators; 16 processor core; 32-GB available RAM (for
DevTest
)
For each data center:
  • 1 test registry and 1 coordinator
  • 1 processor core/process = 2 processor cores
  • 2 GB available RAM/each = 4-GB available RAM (for
    DevTest
    )
A basic
DevTest Server
configuration has one enterprise dashboard, one registry, and one portal, which are required for all products.
Application Test
requires one coordinator server and one simulator server.
Service Virtualization
requires one virtual server environment. The
Application Insight
feature requires one broker. Only one enterprise dashboard server is required for any given configuration.
The requirements that are listed here are intended as a guideline. For large load environments, we recommend contacting Professional Services to assist with developing a load generation environment to suit your needs.
DevTest Workstation for Application Test Requirements
The minimum requirements for
DevTest Workstation
are:
  • CPU:
    2 GHz or faster, 2 cores minimum
  • RAM:
    4 GB available
  • Disk Space:
    4-GB free space
Service Virtualization Requirements
The
Service Virtualization
component,
VSE
, is required for maintaining a virtualization environment.
VSE
is a server-level service and can coexist with a registry that has a coordinator and a simulator that is attached to it. The simulator and coordinator are not mandatory to run
VSE
.
The following requirements are baseline requirements only:
  • CPU:
    2 GHz or faster, two cores minimum
  • RAM:
    Minimum 8 GB available RAM for VSE, in addition to the RAM requirement for
    DevTest Workstation
    ,
    DevTest Server
    , or
    Application Insight
  • Disk Space:
    50 GB of free space
By default, the
DevTest
Java Agent uses the same database schema as the registry. However, you can configure the agent and the registry to use different database schemas.
Application Insight Requirements
The minimum requirements for
Application Insight
are as follows:
  • CPU:
    2 GHz or faster, 8 cores minimum
  • RAM:
    8 GB available
  • Disk Space:
    50 GB of local available disk storage
Identity and Access Manager Requirements
The minimum requirements for Identity and Access Manager are as follows. These requirements are in addition to the requirements for
DevTest Workstation
,
DevTest Server
, or
Application Insight
.
  • CPU:
    2 GHz or faster, 8 cores minimum
  • RAM:
    512-MB available RAM
  • Disk Space:
    1 GB of free space
  • Database:
    Requires its own unique database and must have at least 25 GB of storage
Virtual Service Catalog Requirements
The minimum requirements for Virtual Service Catalog are as follows. These requirements are in addition to the requirements for
DevTest Workstation
,
DevTest Server
, or
Application Insight
.
  • CPU:
    2 GHz or faster, 4 cores minimum
  • RAM:
    4-GB available RAM
  • Disk Space:
    15 GB of free space
    If you are indexing many virtual services or virtual services with large operations, More disk space is required.
Communication Requirements
Ensure that your firewall allows
DevTest Solutions
to send and receive network transmissions. The functionality that
DevTest Solutions
provides requires access to network resources and does not work properly when blocked by a firewall. Authorize
DevTest Solutions
applications.
All DevTest server components must have access to the External Database the Registry is connecting to. Each DevTest server component communicates directly with the database to record their actions. Any restriction to the flow of this data has adverse effects.
Communications to and from the
DevTest
ports must be opened in any relevant firewall. See the following pages:
Database Requirements
The following components store information in a database:
  • DevTest Server
    :
    The database is used for report results, which can be exported to other formats as needed. The database is also used for access control (ACL).
  • VSE
    :
    The database is used for usage counts and legacy service images.
  • Application Insight
    :
    The database is used for paths, including request and response data, SQL statements, and application logs. The database is also used for tickets.
  • Identity and Access Manager:
    The database is used for user data, roles, permissions, and session information. This database is required even if you opt to manage your users through LDAP. For more information, see Identity and Access Manager.
  • Enterprise Dashboard:
    The database is used for the
    DevTest Solutions
    Usage Audit Report data, other registry information, historical event logs, and metrics.
    Enterprise Dashboard requires its own unique large database. The database can reside on a different system and must have at least 50 GB of storage. All DevTest server components must have access to the External Database the Registry is connecting to. Each DevTest server component communicates directly with the database to record their actions. Any restriction to the flow of this data has adverse effects.
By default, these components use an Apache Derby database that is included with
DevTest
. This database is adequate only for small deployments that do not require load and performance testing, and is not supported. For all other scenarios, configure
DevTest
to use an external database.
To ensure correct performance when using an external database, the database server and
DevTest
server should have high network bandwidth and low latency.
When run in a distributed configuration,
DevTest
depends on server components having a high-bandwidth, low-latency connection to a well-maintained, enterprise-class database.
All
DevTest
server components communicate directly with the database to record their actions. Any restriction to the flow of this data has adverse effects.
To ensure that your
DevTest
functions correctly, no
DevTest
server components should have a Round Trip Time (RTT) of greater than 20 ms to the database host. If the network latency exceeds this 20-ms value, you can expect performance problems.
If you are upgrading from an older version of DevTest and reusing the database, the database user must have permissions to modify the schema. This permission is required for any necessary schema and data changes when migrating between the old and new versions.
The following external databases are supported:
  • IBM DB2 9.8, 10.1, and 10.5
    The code page of the database must be 1208. In addition, the page size must be at least 8 KB for the
    DevTest
    registry, 16 KB for Enterprise Dashboard, and 16 KB for IAM. IBM DB2 9.8 is supported as a result of being integrated into IBM DB2 10.1.
  • MySQL 5.5, 5.6, and 5.7
    The MySQL database must provide collation and characters set supporting UTF-8; double-byte characters are stored in the ACL and reporting tables. The default code page for the database must be UTF-8; it is not enough only to define your database as UTF-8.
  • Oracle 11g Release 2
    and
    12c Release 2
    The character set must be Unicode set. For the initial creation of the database, the Oracle user must have DBA privileges, including the
    CREATE VIEW
    system privilege. Oracle must be installed with UTF-8 encoding. UTF-8 is the only encoding we have tested and is the only encoding we support.
  • Microsoft SQL Server 2008 R2, 2012, 2014, and 2016
    The reporting database, that is, lisadb.reporting must have the database user set to en-US as default language. If this user is set with any other language, JASPER report rendering issues might occur.
  • PostgreSQL 11.1, 10.6, and 9.6.11
    The PostgreSQL database must provide collation and characters set supporting UTF-8, that is, the default encoding that we support and tested.
    You must use lowercase table names for PostgreSQL to work.
The schema is automatically created in the external database when the registry starts for the first time. Before the schema is created, ensure that the
DevTest
user has DBA privileges. After the schema is created, you can remove the DBA privileges from the user.
If your security policy does not permit this approach, the database administrator can manually create the schema. The DDL files in the
LISA_HOME\database
directory contain SQL statements that can serve as the basis for manually creating the schema. Provide this information to the database administrator.
For more information about the configuration of an external database, see Database Administration.
DevTest requires three schemas. Each Registry, Enterprise Dashboard, and Identity and Access Manager must have its own unique schema. Do not point multiple registries at the same database schema.
For load and performance testing, tune the external database to ensure that it can support the amount of data storage that
DevTest
requires.
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. We recommend that the database is present within the same data center. Databases that are hosted within a virtual machine are not recommended for general availability use.
DDL Files
The
LISA_HOME\database
directory contains the following DDL files for
DevTest
:
  • db2.ddl
  • derby.ddl
  • mysql.ddl
  • oracle.ddl
  • sqlserver.ddl
  • postgresql.ddl
The
LISA_HOME\database
directory contains the following DDL files for the Enterprise Dashboard:
  • db2_enterprisedashboard.ddl
  • derby_enterprisedashboard.ddl
  • mysql_enterprisedashboard.ddl
  • oracle_enterprisedashboard.ddl
  • sqlserver_enterprisedashboard.ddl
  • postgresql_drop_enterprisedashboard.ddl
For information about
Application Insight
, see Java Agent Database Schema
.
Network Requirements
DevTest
Solutions rely on good network communication being available always, and is dependent upon network performance.
  • Any server component must not have a network latency to the database that exceeds 20 ms.
  • Any server component must not have a network latency to the Registry that exceeds 20 ms.
    Reliability and performance issues are expected when the network latency exceeds 20 ms. If the Workstation round trip time exceeds 100 ms, any form of deployment through Workstation is not supported.
Name Resolution
DevTest
Solutions require that hostname resolution work correctly always, in both a forward and reverse direction. A name resolution to an IP address must function correctly, and resolving that IP address must generate the original host.
Network Address Translation
DevTest
Solutions is communicated through ActiveMQ, with messages containing network endpoint information. So you cannot use
DevTest
Solutions through network address translation (NAT).
Virtual IP or Network Address Changes
DevTest
Solutions do not support the use of Virtual IP or any installation where the network address might change during the lifetime of a server component (Registry, DevTest Portal, Broker, Coordinator, Simulator, or Virtual Service Environment).
Supported Browsers
DevTest
includes the following web-based portals, consoles, and dashboards:
  • Enterprise Dashboard (http://
    hostname
    :1506/)
  • DevTest
    Portal (http://
    hostname
    :1507/devtest)
  • Forward Cars Demo Server (/
    hostname
    :3434/cars-app)
  • Demo Server (http://
    hostname
    :8080/lisabank/)
  • Identity and Access Manager (https://
    hostname
    :51111)
  • Virtual Service Catalog (https://
    hostname
    :51110)
DevTest
Portal requires HTML 5. Therefore, the latest internet browser technology is required to use the new web-based UI. The following internet browser versions support HTML 5:
  • Google Chrome 64
  • Mozilla Firefox 58
  • Apple Safari 11 (Mac)
  • Microsoft Internet Explorer 11
    Some versions of Internet Explorer 11 handle cookies in a way that is not compatible with the
    DevTest
    Enterprise Dashboard. If you experience issues accessing the Enterprise Dashboard, upgrade Internet Explorer to the latest version or use another browser.
DevTest
Portal provides content to browsers with WebSockets. Any browser that you use must support WebSockets for successfully using
DevTest
Portal. Any firewall or reverse-proxy that you use must also permit the use of WebSockets. If they do not, we recommend that you access
DevTest
Portal with HTTPS to allow WebSocket connectivity.
The recommended screen resolution for viewing
DevTest
Portal is 1024 x 768.
Browser support for recording Selenium Integration tests is limited to Mozilla Firefox 42 through 47. After you import these tests to
DevTest
, running the test cases has been verified on Google Chrome, Mozilla Firefox 42 and 43, Apple Safari 7.0 (Mac), and Internet Explorer 10 and 11. Safari is not supported on Windows.
DevTest uses Selenium Library 2.53.0, which might not be fully compatible with the latest driver. Use a driver version that is compatible with Selenium API 2.53.0 (usually an older release version). Some newer web browsers might be unsupported.
Supported Languages
DevTest Solutions
supports the following languages:
  • English
  • Japanese
  • French
The use of Korean characters is not supported.