Working in non-GUI mode

Many of the actions can be performed in non-GUI mode by using the command line, Ant, or REST interfaces.

The table below gives an overview of the actions that can be alternatively performed by using a non-GUI interface.

Table 1. Available actions and their associated interfaces
Actions	Command line	Ant tasks	REST services, grouped by resource type
Running tests	RunTests	GHTester
Managing test results	GHTesterCmd command delete-all-results delete-all-results-keeping
Managing environments	GHTesterCmd command lock-environment unlock-environment	lockEnvironment unlockEnvironment	Environments Look up a URL for an environment Environment Get a specific environment Update the environment tags Delete an environment Environment lock Retrieve information on the existing lock, if any. Create an exclusive lock on an environment. Release an environment lock
Managing scenarios	GHTesterCmd command start-scenario stop-sceanrio	startScenario stopScenario	Scenarios Get a list of all scenarios Scenario Get a specific scenario Start a scenario Scenario instance (Running scenario) Stop a scenario
Managing stubs	GHTesterCmd command publish-stubs start-stub stop-stub	publishStubs startStub stopStub	Stub definitions Get a list of all stub definitions Stub definition Get a specific stub definition Start stub Stub definition configuration Get a specific stub definition configuration Stub instances Get a list of all stub instances Stub instance Get a specific stub instance (to determine its state) Stop a stub

Availability of the various interfaces

Command line: Both the RunTests and GHTesterCmd commands are supplied with IBM Rational Integration Tester. For more information on the commands, see Command-line interfaces.
Ant: Support for the environment, scenario and stub Ant tasks is supplied with IBM Rational Integration Tester and as an installation option for IBM Rational Integration Tester Platform Pack. Support for the GHTester Ant task is supplied only with IBM Rational Integration Tester. For more information on the Ant tasks, see Ant tasks.
REST: The REST interfaces described here are just a set of specifications, so no client is provided. However REST calls must be made to an instance of IBM Rational Test Control Panel. For more information on the REST services, see REST Services.

Note: Domain-level security is supported only by Rational Test Control Panel 8.5.1.1 or later. By default, domain-level security is not enabled.

If domain-level security is enabled, a security token must be specified.

For the command-line, use the securityToken option.
For Ant tasks, use the securityToken attribute.
For the REST APIs, use the X-Jazz-Session Authorization header. For more details, see REST and Domain level security.

For information on how to create a security token, see Creating and assigning security tokens.

Feedback