Edit GlobalConfig

Build 1501 on 14/Nov/2017  This topic last edited on: 11/Nov/2016, at 09:32

Important: this is a critical system file and inappropriate changes can put at stake the production!

GlobalConfig contains number of parameters that drive the GN4 server behavior.

You can edit this configuration as a file on disk and then import it in your database (you can make a safe backup before making changes), or directly in EdAdmin4 (no backup, unless you copy and paste into a backup document before applying changes).

The parameters are described within the file itself.

IMPORTANT: To make these changes available to the GN4 users, after you saved the GLOBALCONFIG.XML file and imported it into the database, or after you modified it in EdAdmin4 and saved, recycle the GN4 application pools on all IIS servers and then make all users log out and log back in.

Click to toggle expandEdit GlobalConfig in EdAdmin4

1.Run EdAdmin4, and then under Application Configuration click Client Applications.

2.Click button_small_down to expand search panel, and then in Name, enter GlobalConfig.

3.Click 113_Refresh_16 refresh button if necessary.

4.Double-click GlobalConfig in the navigator results, to display it in the content tab.

5.Select all text and paste it in a Notepad, to have a last good backup before making changes.

6.Edit and then on the Config menu, click Save.

7.Recycle the GN4 application pools on all IIS servers and then make all users log out and log back in.

Important

The changes you make in EdAdmin4 won't be reflected on the GlobalConfig.XML configuration file stored in ..\GN4\config folder. Therefore, if you ever reload the configuration file again, you will lose the changes made above.
Click to toggle expandEdit GlobalConfig.XML (as file)

1.Locate ..\GN4\config\global\ folder.

2.Locate the GlobalConfig.XML and make a copy, to have a last good backup before making changes.

3.Open the GlobalConfig.XML file in Visual Studio Express or any other XML-enabled editor.

4.Modify what you want and save your changes.

5.Import the modified GlobalConfig.XML into the database.

6.Recycle the GN4 application pools on all IIS servers and then make all users log out and log back in.
Click to toggle expandExport GlobalConfig from the database to a file

1.Open the Administrator Command prompt window.

2.Switch to the applications folder (typically c:\tera\gn4\bin).

3.Execute the command:

<cmd4path>\cmd4 config -name GlobalConfig -out c:\temp\GlobalConfig.xml -srvurl http://<servername>/GN4/adminsrv.asmx -username <username> -password <password>

4.Open the GlobalConfig.XML in Visual Studio Express or any other XML-enabled editor and review it or edit it.

5.Save your changes.
Click to toggle expandImport modified GlobalConfig.xml into the database

1.Open the Administrator Command prompt window.

2.Switch to the applications folder (typically c:\tera\gn4\bin).

3.Execute the command:

cmd4 config -in <fullpath>\GlobalConfig.XML -srvurl http://<servername>/GN4/adminsrv.asmx -username <username> -password <password>

4.Recycle the GN4 application pools on all IIS servers and then make all users log out and log back in.
Click to toggle expandNotes

•Replace <cmd4path> with the path of your GN4 application folder.

•Replace <itemname> with the name of the item (without .xml extension).

•Replace <filepath> with the full path to the file to be imported or exported, including file extension.

•Replace <servername> with the real name of your GN4 server.

•Replace <username> with the name of a GN4 user who has administrative permissions.

•Replace <password> with the password of the <username> GN4 user.

•Replace <fullpath> with the drive letter and the path to the file, including extension.

Note

Some parts of the GlobalConfig related to the error reporting via E-mail are modified remotely, from the Tera License Server. Have this in mind when enabling, disabling, or reconfiguring the error reporting via E-mail: communicate promptly all your changes to the Tera support, otherwise your changes will be overwritten.