Managers

You can find the links to the Javadoc API documentation for all the Galasa Managers on the overview page.

Managers provided with the current Galasa distribution¶

CICS TS Managers¶

CICS TS Manager: Provides configuration information for pre-existing CICS TS servers. Drives provisioning services from other managers, e.g. z/OS PT.
CICS TS Resource Manager: Provides management of CICS resources including CICS Bundles, JVM servers, and JVM profiles.
CECI Manager: Provides CECI 3270 interaction - initially supporting containers and link programs.
CEDA Manager: Provides CEDA 3270 interaction for creating, installing, and managing CICS resource definitions.
CEMT Manager: Provides CEMT 3270 interaction for inquiring, setting, and managing CICS resources at runtime.

IMS TM Managers¶

IMS TM Manager: Provides configuration information for pre-existing IMS TM systems. Drives provisioning services from other managers, e.g. z/OS 3270 Manager.

Cloud Managers¶

Docker Manager: Enables containers to run on infrastructure Docker engines - either for testing directly or for assisting the testing process.
Kubernetes Manager: Provisions Kubernetes namespaces for tests (or Managers) to use.
OpenStack Manager: Provisions Linux images on servers within OpenStack. This Manager currently supports only Linux and provides the servers via the Linux Manager.

Communications Managers¶

HTTP Client Manager: Provides a common setup of HTTP client operations for the test (or a Manager) to use.
IP Network Manager: Provides configuration information for IP-based servers.
MQ Manager: Provides the ability to connect to an existing Queue Manager and enables applications to read and write one or more messages to and from a queue.

Core Managers¶

Artifact Manager: Provides access to resources within a test bundle. It also provides templating services.
Core Manager: The Core Manager provides tests with access to some of the core features within the Galasa Framework. The Core Manager is always initialised and included in a test run and contributes the logger, stored artefact root and test property annotations.
Text Scan Manager: Provides utility text scanning routines for searching and validating text content in logs, batch job outputs, and other text sources.

Database Managers¶

DB2 Manager: Provides connectivity to DB2 databases and enables tests to execute SQL statements, manage schemas, and retrieve query results.

Language Managers¶

Java Manager: Provides access to Java installations and manages Java-related resources for testing Java applications.
Java Ubuntu Manager: Provides Java installations on Ubuntu Linux images with automatic download, extraction, and configuration.
Java Windows Manager: Provides Java installations on Windows images with automatic download, extraction, and configuration.

Windows Managers¶

Windows Manager: Provides access to Windows images, enabling tests to connect to Windows systems, execute commands, and manage Windows-based resources.

Logging Managers¶

ElasticLog Manager: Exports test results to ElasticSearch, which can be subsequently used within Kibana dashboards.

Ecosystem Managers¶

Galasa Ecosystem Manager: Deploys an entire Galasa Ecosystem to Kubernetes to enable integration testing against Galasa.

Test Tool Managers¶

JMeter Manager: Configures and runs JMeter testing via Docker containers.
SDV Manager: Create an automated test in Galasa and use the SDV Manager to record the security used during your test.
Selenium Manager: Allows tests to drive Web Browser testing using Selenium.

Unix Managers¶

Linux Manager: Connect to a Linux image and run commands on that image via the command shell. Drive provisioning of images by using other Managers, for example, the OpenStack Manager. The Linux Manager depends on the IP Network Manager to provide the IP connection to the Linux image.

Workflow Managers¶

GitHub Manager: Use the GitHub Manager to help analyze test results. Identify test classes and test methods that have failed as the result of a known problem which is documented in an open GitHub issue, avoiding spending time investigating the cause of a failure of which the reason is known.

z/OS Managers¶

RSE API Manager: Provides tests and Managers with access to RSE API functions.
z/OS 3270 Manager: Provides tests and Managers with a 3270 client.
z/OS Batch z/OS MF Manager: Provides the default implementation of the z/OS Batch Manager using z/OS MF. Can only be used via the z/OS Batch Manager interface.
z/OS Batch RSE API Manager: Provides an implementation of the z/OS Batch Manager using the RSE API. Can only be used via the z/OS Batch Manager interface.
z/OS Console oeconsol Manager: Provides an implementation of the z/OS Console by using the z/OS UNIX oeconsol command. Can only be used via the z/OS Console Manager interface.
z/OS Console z/OS MF Manager: Provides the default implementation of the z/OS Console by using z/OS MF. Can only be used via the z/OS Console Manager interface.
z/OS File RSE API Manager: Provides an implementation of the z/OS File Manager by using RSE API. Can only be used via the z/OS File Manager interface.
z/OS File z/OS MF Manager: Provides the default implementation of the z/OS File Manager using z/OS MF. Can only be used via the z/OS File Manager interface.
z/OS Manager: Provides tests and Managers with access to z/OS images, sysplexes and log information. Additionally, the z/OS Manager contributes annotations which allow you to run batch jobs, issue console commands, transfer files and securely access z/OS systems via TSO or UNIX commands.
z/OS MF Manager: Provides tests and Managers with access to z/OS MF functions.
z/OS Program Manager: Compiles test programs from source embedded in the Galasa test bundle at test start. The executable load module is then available for use in the test.
z/OS TSO Command SSH Manager: Provides the default implementation of the z/OS TSO Command Manager using SSH. Can only be used via the z/OS TSO Command Manager interface.
z/OS UNIX Command SSH Manager: Provides the default implementation of the z/OS UNIX Command Manager using SSH. Can only be used via the z/OS UNIX Command Manager interface.