What is a Named Server?    

Often, Software Testers have requirements to install GenRocket Runtime on a Testing Automation Server so that it can run Test Data Generation Scenarios. We call this type of server a Named Server.
 

Any Named Server executing GenRocket Scenarios to generate synthetic test data must be registered in the GenRocket system. 


When software tests are run on an automation server and call GenRocket Scenarios to generate synthetic test data, a check is made to validate the Named Server.


We use the term Named Server because Test Automation Servers are sometimes changed, so the Named Server can be reassigned to a new Test Automation Server.  


In This Article


Who Can Add a Named Server?

  • Only Organization Admins can add a new Named Server to the GenRocket Web platform.

When Should a Named Server be Added? 

  • It is required for any Server that users will not directly log into when executing GenRocket Scenarios.
    • Example - Automated Test Server

  • A user profile is sufficient when users have their own logins and will be generating test data on their local machine or a shared machine within an organization. 

 

Step 1 - Add a Named Server

  • Expand the Organization Menu in the Menu Bar (contains the org name and user's first name).

  • Select My Organization.


  • Select the Servers Tab and click New Server to create a new server.


  • Enter a unique name for the server.
  • Optionally, add a description and email address.
  • The Enabled option will automatically be checked to enable the server. 
  • Click Save once finished.




Step 2 - Edit the Server Resource Path Values

  • Go to the Project Dashboard. 
  • Select the Server that was created.
  • If values are not present, click the Pencil to fill in the path information for each resource value.



  • The value for the resource.home.directory will be the server's home directory.

  • You can find the home directory by running the following command on the server:

    echo $HOME


  • The rest of the resource values can be any arbitrary location.



Step 3 - Download the Server Profile

Once added, the Organization Admin can download the Server Profile so that the Server may be used to execute GenRocket Scenarios. The Organization Admin can enable/disable a server as needed. Complete the following steps: This can be done in one of two ways: 


Method 1 - GenRocket Web Platform

  • Make certain the correct server is selected.


  • Expand the Download menu and select Download ServerProfile.grp.

     
  • If the server does not have internet connectivity and the file was downloaded to your local machine, you will need to move it to the server. You can do this with an SSH command. An example is provided below. 

    scp ssh '/path/to/your/download/GRXXXXXXXProfile.grp user@remoteip:/home/users/username/.genrocket

Method 2- CURL Commands

You will need to use two CURL commands. The first command obtains the access token, which the second command requires. Please see Using CURL Commands to Download GenRocket Runtime, Jars, and Server Profile.

Step 4 - Place the Server Profile in the .genrocket Folder

After downloading the profile, go to the Server machine and place the profile into the <SERVER_HOME>/.genrocket folder. These steps vary per operating system and can be done through the UI or command line. 


Linux or Mac OS Command

You can use the mv command shown below. Make sure it is set to the correct directory.

mv GRXXXXXXXProfile.grp .genrocket


Windows Command

Make sure the command prompt is pointing to the correct directory.


move filename destinationFolder


Example

move GRXXXXXXProfile.grp C:\Users\Username\.genrocket