Installation

NeoLoad Web can be deployed as a SaaS or can be installed on-premise.

We recommend you to choose the SaaS deployment option as this one is streamlining the deployment and management of the platform.

To get started with NeoLoad Web in SaaS, go to https://www.tricentis.com/software-testing-tool-trial-demo/neoload-trial/. Create an account in our user platform and have access to the SaaS!

In case it is not possible for you to leverage a SaaS deployment, we are providing a blueprint deployment based on a Kubernetes orchestration approach for on premises deployment. Note that from NeoLoad Web 2.10 onwards, only Kubernetes based deployment following this blueprint will get supported by Tricentis. We highly encourage you to touch base with our Implementation team for a different flavor of the deployment.

An upgrade from NeoLoad Web 2.10 is starting with a Helm-based installation. Please reach out to Support for the procedure.

Operations

This section provides detailed information to perform migration of MongoDB.

This section provides detailed information to perform migration of MongoDB from 3.4 to 3.6 version.

MongoDB recommendations for migration are available in documentation 3.4 to 3.6:

This procedure is specific to NeoLoad Web.

Note: If you are using replica set or a shared cluster please follow the specific MongoDB documentation here.

Preparation steps

Before starting the migration it is highly recommended to do a backup of the database as described here.

Once connected to the NeoLoad Web machine, pull the 3.6.16 Mongo image: docker pull mongo:3.6.16

Migration

  1. Stop NeoLoad Web: docker-compose -f docker-compose-all-in-one(-ssl).yaml down

  2. Modify the image in the docker compose file from mongo:3.4.13 to mongo:3.6.16

  3. Start Mongo 3.6: docker-compose -f docker-compose-all-in-one(-ssl).yaml up -d mongo

  4. Run the migration command with the Mongo client against the admin database:
    docker exec -it mongo mongo --eval "db.adminCommand( { setFeatureCompatibilityVersion: '3.6' } )"

  5. Verify the compatibility version is set to 3.6 with the command: docker exec -it mongo mongo --eval "db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )"

  6. It should return: { "featureCompatibilityVersion" : { "version" : "3.6" }, "ok" : 1 }

  7. Start NeoLoad Web: docker-compose -f docker-compose-all-in-one(-ssl).yaml up -d nlweb-backend nlweb-frontend

This section provides detailed information to perform migration of MongoDB from 3.6 to 4.0 version.

MongoDB recommendations for migration are available in documentation 3.6 to 4.0:

This procedure is specific to NeoLoad Web.

Note: If you are using replica set or a shared cluster please follow the specific MongoDB documentation here.

Preparation steps

Before starting the migration it is highly recommended to do a backup of the database as described here.

Once connected to the NeoLoad Web machine, pull the 4.0 Mongo image: docker pull mongo:4.0

Migration

  1. Stop NeoLoad Web: docker-compose -f docker-compose-all-in-one(-ssl).yaml down

  2. Modify the image in the docker compose file from mongo:3.6.16 to mongo:4.0

  3. Start Mongo 4.0: docker-compose -f docker-compose-all-in-one(-ssl).yaml up -d mongo

  4. Run the migration command with the Mongo client against the admin database:
    docker exec -it mongo mongo --eval "db.adminCommand( { setFeatureCompatibilityVersion: '4.0' } )"

  5. Verify the compatibility version is set to 4.0 with the command: docker exec -it mongo mongo --eval "db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )"

  6. It should return: { "featureCompatibilityVersion" : { "version" : "4.0" }, "ok" : 1 }

  7. Start NeoLoad Web: docker-compose -f docker-compose-all-in-one(-ssl).yaml up -d nlweb-backend nlweb-frontend