There will be occasions where you will need to run a test GN4 system, e.g. prior an upgrade, for self-learning, etc.

You can easily install a GN4 test bed as follows:

•Laptop or desktop computer (no VM): install SQL server, and enable (if required) IIS. Perform installing steps as explained in Install GN4. Such system can be used for all testing, also when you are not connected to any network.

•Laptop or desktop computer with VM: If your main GN4 server runs a VM, clone it and copy it on your laptop or desktop. Such system can be used for all testing, also when you are not connected to any network.

•A small test server: any of above explained solutions. Note: to connect to the test server, you'll need a network or Internet connection.

About cloning virtual machines

These are the steps to clone a VM from a source to a target computer, when both VMs are on the same network:

1.On the source computer, shutdown the VM you want to clone.

2.Copy the VHD file over to the target computer.

3.On the target computer, create a new virtual machine and attach the copied VHD file.

4.Before starting the new VM on the target computer, disable the networking in its settings.

5.Start the new VM and change name and IP address - if using a fixed IP address.

6.Shutdown the new VM and re-enable the networking in its settings.

7.Start the new VM.

8.Open the command prompt window, and remove the GN4 licenses to avoid the cloning warning. Use srv4 license -clear

9.Request new licenses with the command srv4 license -url http://licenses.teradp.com -name [license name]

10.Recycle the application pool.

How to create a test environment from a production environment

The GNPortal/Gn4/Tark4 environment uses a complicated license system. This system automatically updates the license before the expiration. Every update renew the expiration date. In some situation is needed to have a test environment with the same configuration as the production environment. This is very useful to debug and/or to test the software upgrade. To replicate it is very easy you have to dump the production database and restore it on the test machine. The very first time the application is accessed via web interface or client interface a license's request is forwarded to the license's server. If the license is already in the license server with a different guid this clone will take the license ownership. So the production environment will not be able to update its license and at the expiration date the software will be unusable. To prevent this situation, it is very import that you follow these steps before start any other operation (iis, back4 or clients) after the database restore.

Clear the license from the test environment database:

srv4 license -clear -name "Customer description"

Note: in older versions, also the:

srv4 license -clear

will work, but the recent versions require also the parameter -name.

Generate a new license request for the test environment:

srv4 license -url http://licenses.teradp.com -name "Customer description"

Recycle the application pool.

NOTE: the syntax of the "Customer description" string is CustomerName:Server/Type:Application

Samples of valid customer's name:

DAILY-HERALD:Production:GN4

TERA-US:Demo:Tark4

RCS:Server-name:GNPortal

To view the new licenses and the GUID of your test installation

srv4 license -show

Then you have to ask us the number and typology of needed licenses at licenses@teradp.com

When the licenses are added you will receive a confirmation email. So you have to update the licenses on your test environment with:

srv4 license

Recycle the application pool.