Introduction

JS7 - Self-Test provides a number of test cases for health status checks, inventory status checks, performance tests etc.

FEATURE AVAILABILITY STARTING FROM RELEASE 2.8.1

Prerequisites

Before importing Self-Test to a JS7 environment, users should check that an Agent with the name self-test-agent eixsts.

Any existing Agent can be used. Agents can be assigned Alias Names that allow the same Agent to act under differnt names.

From any page in JOC Cockpit users can click the wheel icon for administrative tasks and select the Manage Controllers/Agents page.

The page offers to manage Agents. Users should use the three dots action menu of a Standalone Agent and select the Edit operation like this:

This brings forward a popup window to manage Agent properties. Click the icon for Alias Names to add a new entry with the name self-test-agent. Then use the Submit button to apply changes.

Download

Self-Test ships from two archive files that are available for download and that can be operated for JS7 using Unix and Windows.

Import

The archive files can be imported to JOC Cockpit, see JS7 - Inventory Export and Import.

Users should first import the self-test-user.zip archive, then the self-test.zip archive.

Importing Self-Test-User

• Hitting the Import button in the Configuration->Inventory view brings forward the below popup window.
• Users select the downloaded self-test-user.zip archive file for import.
• Self-Test-User will be imported to the /Self-Test-User inventory folder. Users can optionally use the Folder input field to specify a folder hierarchy, for example /Users/myself will import to the /Users/myself/Self-Test-User folder.
• The Overwrite check box should be handled with consideration as it will overwrite existing user objects with the same name.
  
  

Importing Self-Test

If the /Self-Test folder exists from a previous import, then users should remove the folder before import.

• Hitting the Import button in the Configuration->Inventory view brings forward the below popup window.
• Users select the downloaded self-test.zip archive file for import.
• Self-Test will be imported to the /Self-Test inventory folder. Users can optionally use the Folder input field to specify a folder hierarchy, for example /Users/myself will import to the /Users/myself/Self-Test folder.

Deployment

Deploying Self-Test-User

After import of objects to the /Self-Test-User folder, objects are in draft status and must be deployed.

Users can click the three dots action menu of the /Self-Test-User folder like this:

From the action menu select the Deploy operation.

Deploying Self-Test

The proceeding is similar to deploying objects from the /Self-Test-User folder.

After import of objects to the /Self-Test folder, the objects are in draft status and must be deployed.

Users can click the three dots action menu of the /Self-Test folder and select the Deploy operation.

Adjustments of User Configuration

Job Resource: Self-Test-AuthenticationSettings

The job resource is located in the /Self-Test-User folder and hold authentication settings for Self-Test job to access the JS7 REST Web Service API.

A number of options are available for authentication:

• js7.api-server.url
  • If JOC Cockpit and Agent are located on the same server then the localhost host name can be used.
  • If JOC Cockpit is operated for HTTP then this protocol can be used.
  • Users should check for which port JOC Cockpit is operated (default: 4446).
• js7.api-server.username, js7.api-server.password
  • Users must specify an account and password for authentication with JOC Cockpit.
  • By default the root account is available with the root password that might have changed after initial login.
    
    

When using the HTTPS protocol, then additional settings for keystore and truststore are required.

For details about authentication settings see JS7 - JITL Common Authentication.

Schedules

The /Self-Test-User folder includes sub-folders for test areas such as Daily-Plan-Checks, Health-Checks etc.

The sub-folders include schedules that can be used to parameterize test cases.