Admin

Here, the user can perform some admin related activities, such as setting up projects, LDAP server settings, setting up servers, controllers, GIT settings, data retention policy, access control, agent info, and NetHavoc. In the subsequent sections, description of these are provided.

Projects

Projects enable easy organization and management of individual users of the NetStorm.

A Project, in essence, is a self-contained entity that can perform all of its work without affecting the work of another user. Project and subproject can be added from user management GUI and used in scenario and analyze GUI.

Following things need to be ensured in Project Administration window:

  • Make sure sorting is done on every column.
  • Make sure all check boxes are enabled.
  • Project name should not have spaces in between.
  • A project should have at least one subproject.
  • A project can have multiple subprojects.
  • Name of project and subproject can be same.
  • Multiple projects can’t be deleted at a time.
  • A subproject can’t be deleted without deleting the project to which it belongs.

This section describes the following tasks:

  • Add project/subproject
  • Delete project/subproject
  • Delete Forcefully project/subproject
  • Rename project
  • Rename subproject

Adding a Project/Subproject

Admin user needs to follow the below mentioned steps for adding a project/sub project:

  1. Login to NetStorm as an admin user and click the Projects option under the Admin menu on the tool bar. The NetStorm – Project Administration window is displayed with a list of projects.

14

  1. Enter the Project name and sub-project name and click Add. The project and sub-project is added in the list.

15

 NoteIf user provides an existing Project name, system flashes an alert message “Record with same key (proj, sub_proj) already exists in the Project. Please enter different value of key”.

Deleting a User Project/Subproject

Admin user needs to follow the below mentioned steps for deleting a project/sub project:

  1. Select the project/sub-project that needs to be deleted and click the Delete button. A confirmation message is displayed as shown below:

16

  1. Click OK. The project/sub-project is deleted.
 NoteUsing the Delete button, the Admin user can delete only those projects/sub- projects that do not contain Scenarios and Scripts.

Delete Forcefully a User Project/Subproject

Delete forcefully functionality is used to delete a project/sub-project that contains Scenarios and Scripts. Such projects cannot be deleted using the Delete button. Admin user needs to use the Delete Forcefully button for deleting such projects.

Admin user needs to follow the below-mentioned steps for deleting a project/sub project that contains Scenarios and Scripts:

  1. Select the project/sub-project that needs to be deleted and click the Delete Forcefully button. A confirmation message is displayed.

16

  1. Click OK. The project/sub-project is deleted.
 NoteIf the admin user selects more than one record to delete, system generates an alert message” Select only one record and try again”.

Rename a User Project

Admin user needs to follow the below mentioned steps for renaming a user project:

  1. Select the user project that needs to be renamed. The project and sub-project is displayed in editable mode at the top of the list.

18

  1. Rename the project name and click the Rename Project button. A confirmation message is displayed, click OK. The project is renamed and updated in the list.

19

Rename a User Subproject

Admin user needs to follow the below mentioned steps for renaming a user sub-project:

  1. Select the user sub-project that needs to be renamed. The project and sub-project is displayed in editable mode at the top of the list.

20

  1. Rename the sub-project name and click the Rename Project  button. A confirmation message is displayed, click OK. The sub-project is renamed and updated in the list.

21

LDAP Server Settings

LDAP, Lightweight Directory Access Protocol, is an Internet protocol that email and other programs use to look up information from a server.

The user can configure the following settings:

  • Host:Port: Enter the Host name or IP address of your LDAP server. Enter the Port number used for LDAP communication (389 by default). If your server is an Active Directory Global Catalog server, you can specify port 3268 for a plain connection, or port 3269 for SSL.
  • Base Domain: A base dn is the point from where a server will search for users. For example, dc=ldap, dc=cavisson, dc=com
  • Enable user authentication: You can use the Lightweight Directory Access Protocol (LDAP) to authenticate users. Specify user roles by using group DNs for users who log in as an Administrator, Operator, or as a Viewer. The system has only one admin user and one operator.
  • Bind Domain: An LDAP client transmits a BIND request to a server in order to change the authorization state of the client connection. When a client first connects to an LDAP directory server, the server sets the authorization state of the connection to unauthenticated. For example, cn=admin, dc=ldap, dc=cavisson, dc=com.
  • Password: Enter the password.
  • Enable communication over secure protocol: Secure LDAP (LDAPS) allows you to enable the Secure Lightweight Directory Access Protocol for your Active Directory managed domains to provide communication over SSL (Secure Socket Layer)/TLS (Transport Layer Security). By default, LDAP communications between client and server applications are not encrypted.

Servers

Defining server’s information in Custom Monitor increases the complications for the features (Server name or IP, user name, password, Local/Remote Specifications).

This section describes the following tasks:

  • Add Server
  • Delete Server
  • Update Server
  • Upgrade CMon
  • Start CMon
  • Restart CMon
  • Stop CMon
  • Show CMon
  • CMon Version
  • Show Running Monitors
  • Run Command
  • Cavmon Stats
  • Upload File

Add Server

Admin user needs to follow the below mentioned steps for adding a server:

  1. Login to NetStorm as an admin user and click the Servers option under the Admin menu on the tool bar. The NetStorm – Server Administration window is displayed with a list of servers.

23

  1. Click the Add button, the NetStorm – Add Server window is displayed.

24

  1. Enter Server name, server type, installation directory, java home, agentless, port, SSH available, user name, password, and confirm password and click OK. The server is added to the servers list.

25

 

 NoteInstallation Dir and JAVA_HOME should have absolute path.

If server is Agentless is ‘yes’ and SSH Available is ‘No’. It gives an alert message.

If SSH Available is ‘No’ User Name, Password and Confirm Password all are disable.

Delete Server

Admin user needs to follow the below mentioned steps for deleting a server:

  1. Select the server that needs to be deleted and click the Delete button. A confirmation message is displayed.

26

  1. Click OK. The server is deleted.

Update Server

Admin user needs to follow the below mentioned steps for updating a server:

  1. Select the server that needs to be updated and click the Update button.The NetStorm – Update Server window is displayed.

27

  1. Update the required server information and click the OK button.
 NoteServer name cannot be changed.

One record can be updated at a time. Otherwise, system generates an alert message.

Upgrade CMon

Admin user needs to follow the below mentioned steps for upgrading CMon:

  1. Select the Server and click the Upgrade Cmon button. A dialog box is displayed.

28

  1. Admin user needs to specify the package name with full path that needs to be upgraded. The package should be on NetStorm machine. It shows upgrade output in text area.

29

  1. Click the Close button.

Start CMon

Admin user needs to follow the below mentioned steps for starting CMon:

  1. Select the server and click the Start Cmon button. The NetStorm – Start Cmon window is displayed and CMon is started (if not running currently).

30

  1. Click the Close button to close the window.

Restart CMon

Admin user needs to follow the below mentioned steps for restarting CMon:

  1. Select the server and click the Restart Cmon The NetStorm – Restart Cmon window is displayed and CMon is restarted.

31

  1. Click the Close button to close the window.

Stop CMon

Admin user needs to follow the below mentioned steps for stopping CMon:

  1. Select the server and click the Stop Cmon The NetStorm – Stop Cmon window is displayed and CMon is stopped.

32

  1. Click the Close button to close the window.

Show CMon

Admin user needs to follow the below mentioned steps for showing CMon:

  1. Select the server and click the Show Cmon The NetStorm – Show Cmon window is displayed with a message that CMon is running along with its pid.

33

  1. Click the Close button to close the window.

CMon Version

Admin user needs to follow the below mentioned steps for getting CMon version:

  1. Select the server and click the Cmon Version button. The NetStorm – Cmon Version window is displayed with CMon version.

34

  1. Click the Close button to close the window.

Show Running Monitors

Admin user needs to follow the below mentioned steps for getting running monitors:

  1. Select the server and click the Show Running Monitors button. The NetStorm – Running Monitors window is displayed showing all the running monitors.

35

  1. Click the Close button to close the window.

Cavmon Stats

Admin user needs to follow the below mentioned steps for getting the CavMon statistics:

  1. Select the server and click the Cavmon Stats button. The NetStorm – CavMon Stats window is displayed.

38

  1. The NetStorm – CavMon Stats window contains CavMon stats, such as heap info. It also contains Active threads info, such as thread id, thread type, test run, program name, program argument and start date & time.
  2. Click Refresh to refresh the data, click Cancel to close the window.
 NoteAdmin User can filter the records by entering the keyword and clicking the Apply button.

Clicking the Show All button displays all records.

Records can be auto-refreshed by selecting the Auto Refresh checkbox and specifying the interval.

Upload File

Admin user needs to follow the below mentioned steps for uploading a file to a server:

  1. Select the server and click the Upload File button. The NetStorm – Upload File To Server window is displayed.

39

 

 NoteAdmin User can also select the server from the Server drop-down list in the NetStorm – Upload File To Server window.
  1. Enter the NetStorm source file path and destination path and click Upload. The file is uploaded to the on the server at the destination path.
  2. Click the Close button to close the window.

Settings

Here, the user can configure the module tab settings.

  • To open the module in the application tab, select the Open in Application Tab option.
  • To open the module in a browser tab, select the Open in Browser Tab option.

Manage Controllers

Controllers are the shared blades in specific hardware. These are multiple soft appliances in single hardware with shared resources. This window displays – appliance name, controller name, controller URL, and Service Endpoint IP.

Here, the user can manage controllers, such as add , rename, or delete.

Add a Controller

To add a controller, click the Add button. This displays the Add Controller window.

Provide the following inputs:

  • Controller Name
  • Controller Type
  • Appliance Name
  • Controller IP
  • Controller Port (HTTP and HTTPs)
  • Service End Point IP
  • Recorder Port Range (Start Port and End Port)

Rename a Controller

  1. Select a controller name that you want to rename and click the Rename button.

  1. This displays the Edit Controller Name window where the existing controller name is prefilled.
  2. Enter the new controller name and click OK.
  3. The controller name is renamed with the provided new controller name.

GIT Configuration

Git is an open-source distributed version control system that enables you to save your NetStorm test assets including scenarios, scripts, test suites, and test cases in a Git repository. A Git repository is the directory where all your project files and related metadata reside. This section provides information about how to configure the GIT repository settings in NetStorm.

Getting Started

For GIT configuration in NetStorm, you need to first select the required work profile and enable GIT settings options. Then, provide your server configuration details, branch information, and author info for connecting remotely to the GIT repository.  Perform the following steps:

  1. Access a work profile in NetStorm.
  2. Enable GIT settings in NetStorm.
  3. Specify the server configuration.
  4. Specify the GIT branch and author info.
  5. Save your GIT configuration and perform GIT operations.

Note: Before configuring GIT settings in NetStorm, you must create a Cavisson directory in the GIT repository.

Access a Work Profile

A work profile enables you to save your selected data in a workspace. You can create multiple work profiles in your respective workspace. For configuring GIT settings, you need to first select a work profile in NetStorm. For more information, see Managing Work Profiles.

To access a profile:

  1. Log in to NetStorm by specifying your username and password.

2. Expand the user profile drop-down list on the top-right corner of the NetStorm window. The list of available test profiles is displayed. You can access and switch profiles from this drop-down menu, as highlighted in the following figure:

Note: The default profile of the user is highlighted in the user profile list.

Enable GIT Settings

After selecting the required work profile, all the configurations associated with the profile will be loaded in NetStorm. You can now enable GIT configuration options for the selected profile.

To enable GIT configuration in NetStorm:

  1. Select Admin > GIT Configuration in NetStorm. The GIT Configuration window is displayed.
  2. Select the Use GIT for Version Control option.

Note: If you do not use GIT for version control, the Cavisson version control system will be used by default.

3. The GIT configuration options are enabled in the window:

 

Specify Server Configuration

In the Server Configuration section,  you need to provide a remote GIT repository URL and valid user credentials to connect and perform GIT operations on the GIT repository.

Repository URL

Specify the remote GIT repository URL in the Repository URL field. It can contain HTTP/HTTPS URL or SSH/GIT URLs. For example, you can use the following types of URLs:

git@gitlab.com:test1/abc.git or https://gitlab.com/test2/abc.git

HTTP/HTTPS Repository URL

If you configure an HTTP/HTTPS repository URL, the SSL certificate is disabled by default. Provide a username and password:

  • Disable SSL Certificate: If you do not want to perform a security certificate check, accept the default value of this option.
  • User Name: Username of the GIT account that needs to be remotely accessed.
  • Password: Password of the GIT account that needs to be remotely accessed.

SSH Repository URL

If you want to configure an SSH/git repository URL , you can either provide username and password or passphrase/sshkey.

You can log in using the following options:

  • Via Username/Password
  • Via SSH key
Via Username/Password

Provide the GIT username and password.

Via SSH Key

Selecting the Via SSH Key option displays the following options:

User Name

Username of the GIT account that needs to be remotely accessed.

Password

Password of the GIT account that needs to be remotely accessed.

Pass Phrase

Passphrase for the SSH key that is generated by the user. You can secure your SSH keys by adding a passphrase to your SSH keys.

SSH Key

You can either generate an SSH key or import an existing key.

Generate SSH key

You can generate an SSH key with or without specifying a passphrase.

To generate an SSH key:

  1. Click the Generate SSH Key icon .  A pair of public and private keys are generated.

2. Copy the generated key and add it in GitLab to establish a connection between your machine and GitLab.

Import an Existing SSH Key

To import an existing SSH key:

  1. Click the Import Existing SSH Key icon . A Paste SSH key text field is displayed:

2. Add your private SSH key in the Paste SSH Key text box.

3. This key will be uploaded to the following path when you save the GIT configuration:

$NS_WDIR/workspace/<user_name>/<profile_name>/

Select a Branch

After providing the repository URL and valid credentials, you can fetch the list of branches from the remote GIT repository. Based on the selected repository, the branch options are updated in the Branch drop-down list. 

  • If GIT configuration is already saved, the branches are fetched automatically.
  • If you are configuring GIT for the first time or configuring some other remote GIT repository, then you have to manually click the Fetch Branch icon.

To select a branch:

  1. Click the  icon. The Branch drop-down list is updated with the related branches.

2. Select the required Branch from the drop-down list.

Specify Author Details

Provide the following author information:

  • Full Name: This field requires the full name of the user who is configuring GIT and performing git operations.

Note: Full name is different from “User Name” as it refers to the remote git server user name.

  • Email: Email of the user who is configuring Git and will be performing GIT operations.

Save your GIT Configuration

After providing GIT configuration, you must save the settings before performing GIT actions. To save:

  1. Click the Save button in the GIT Configuration window.
  2. Your GIT configuration will be saved in GIT_CONFIG and VERSION_CONTROL keyword in the .workprofile.conf in the selected work profile at following path:

                $NS_WDIR/workspace/<user_name>/<profile_name>/

Perform GIT Operations

After you have saved your GIT configuration, the GIT operations will be enabled in the GIT drop-down list:

Note: if you want to perform GIT operations, a Cavisson directory should exist in the GIT repository.

You can perform the following GIT actions:

  • GIT Clone: GIT clone will clone the provided remote git repository inside following path:

$NS_WDIR/workspace/<user_name>/<profile_name>/

  • GIT Pull: GIT pull will fetch the latest code from the provided GIT repository.
  • GIT Commit: GIT Commit from GIT Configuration window will commit all the modified files in one go.
  • GIT Checkout: GIT Checkout will checkout the particular branch that is saved in the .workprofile.conf file.

Managing Work Profiles

In NetStorm, users will have their own workspace. Each workspace will have multiple profiles and each profile will have its own set of test assets. For example: $NS_WDIR/workspace/<user_name>/

By default, new users (non-cavisson user) will have a ‘system’ profile referring to the following directory: $NS_WDIR/workspace/admin/system

You can link each profile with a remote GIT repository and configure git settings for each profile. Each profile will have its own Git configuration saved in the .workprofile.conf file in a particular profile. For example: $NS_WDIR/workspace/<user_name>/<profile_name>/.workprofile.conf.

Support for Multiple Work Profiles

NetStorm supports multiple work profiles for each user. You can create multiple profiles for saving data in separate profiles. For example, you choose to create a new work file for saving your scenarios, test suites, test cases, or check profiles in a separate profile.  Each work profile of a user will have its own Git configuration including Git Repository URL, Display name, Email ID, UserName, Password, and other details.

Select a Default Work Profile

Clicking the star icon , you can designate a particular work profile as the default profile. It means that whenever you ogs into the ProductUI, then by default the default profile will be accessed.

Select an Active Work Profile

Clicking the selected work profile in the profile drop-down list, you can switch to the particular profile. All the test assets will be fetched from the selected work profile and all operations, like addition, will be performed on the selected work profile only.

Create a New Profile

To create a new profile:

  1. Expand the user profile drop-down list on the top-right corner of the NetStorm window. The list of available test profiles is displayed.

2. Select the Create new profile option. The Create New Work Profile dialog box is displayed:

3. Provide a work profile name.

4. Expand the Advanced Settings section.

5. Select Make as default to log in using this work profile every time you access NetStorm.

6. If you select the Link to existing directory option, specify the path where your test asset is saved that you want to be linked with the profile.

7. Note that the “default” work profile of a user will be linked with the “default” work profile of “admin”, while creating a Workspace for a user. Therefore, the work profile is saved in the default folder, if you do not choose any other path.

8. Create Create. A new work profile is created.

Delete a Work Profile

Clicking the trash icon, you can delete a particular profile. Before deleting, you will be prompted to give your confirmation.

Note: You cannot delete the ‘system’ and default work profile.

Agent Info

ND Agent is an agent running on the host where the ND application under test is running. Its task is to provide a communication channel between BCI Agent and ND Collector. In this section, users can view a list of ND agents along with their status. To view the ND agents list, click the Agent Info option within the Admin section.

On clicking this link, a new window is displayed. This window provides the status of machine agents and application agents. Machine agents are the cavisson monitoring agents (CMON) and application agents are the BCI agents or the ND agents.

Machine Agent Status

This section provides machine agent information, such as process id (PID), tier, server, server IP, operating system, version, agent start time, setting last updated time, status (either active/inactive), and action(s).

Application Agent Status

This section provides application agent information, such as PID, tier, server, instance, installation directory, agent type, version, agent start time, and status.

Operations on Agents

A user can perform the following operations on machine agent and application agent:

  • Searching an agent
  • Apply filters on agents
  • Download reports
  • Restart an agent
  • Refresh agent status list
  • View or update the settings

Searching an Agent

For searching an agent, use the search bar at the top-left section of the window. Enter the desired value to perform a search (in any column), the searched results are displayed accordingly. In the below image, we have searched ‘Instance1’ and system displays the results containing this text.

Apply Column Filters

A user can also apply column filters, which can work same as search, but can also be applied on multiple columns. To do this, click the  icon on the top-right corner of the window. The filter panel is displayed. Here, we have applied filter on two columns – ‘Instance’ and ‘Agent Start Time’.

To hide column filters, click the  icon again .

Download Reports

A user can also download reports of agent status in various formats, such as word, excel, and pdf. To do this, click the desired format, which is displayed at the bottom-left section of the screen.

Restart an Agent

The user can restart the machine agent. To do this, click the Restart icon .

Refresh Agent Status List

On clicking the Refresh icon , the agent list gets refreshed and updated list id displayed on the panel.

View or Update the Settings

The user can view or update the machine configuration by clicking  or  icon in the Action(s) column.

  • View Configuration

On clicking the  icon, the following window is displayed where the user can view the current settings and advance settings of the machine.

  • Update Configuration

On clicking the  icon, the following window is displayed where the user can edit the settings of the machine.

NetHavoc

The overall performance of a service is directly linked, among other things, to its ability to tolerate failures. This aspect of an application/software can be tested by deliberately injecting random faults and failures into the application infrastructure.

NetHavoc is a powerful feature added to NetStorm, which allows users to test the resilience of the applications. NetHavoc can be used to inject various faults into the application infrastructure during a load test. The after-effects of the fault injection can be monitored through NetStorm’s powerful monitoring capabilities.

For more details, refer to the NetHavoc section.

Second Level Authorization

To avoid unwanted hits on server, the user (with required privileges) first needs to set (6-digit) authorization key (via Admin > Second Level Authorization) which is used while starting a test on that machine and saving the scenario schedule settings.

  • On starting a test, the user is required to provide the authorization key. If the key matches with the one as set by the privileged user, the test starts and ‘Test Initialization Screen‘ is displayed, else an error message is displayed.
  • In addition, on saving the scenario schedule settings, the user is required to provide the authorization key. If the key matches with the one as set by the privileged user, the user is allowed to save the scenario schedule settings else and error message is displayed.

Note: When a new scenario is created, if user starts the test without saving the scenario, an alert pop-up is displayed which states that “Test cannot be started because scenario is not saved.” On saving the scenario, the user can start the test. This behavior is valid only for new a scenario not for already created scenario (i.e. scenario in edit mode).

Setting Authorization Key

  1. Go to Admin > Second Level Authorization.

2. This displays the Second Level Authorization window.

  1. Select the checkbox and provide the current and new password. Re-enter the password and click Save.
  2. This saves the authorization key and a confirmation message is displayed.

Note: It is prompted to the user when starting a test or applies scheduling from the Scenario Schedule window.

Starting a Test

  1. For starting a test, when the user clicks the button, provides the test name, and clicks the Start Scenario button, the user is prompted to provide the activation key.

2. On matching the activation key, the test gets started and Test Initialization window is displayed.