eG Help

eG Administration

CONFIGURING NETWORK LOCATION

If one/more network/geographic locations have already been configured for intranet users, then GEO LOCATIONS page will display those locations. If not, then a message to that effect will be displayed. To configure a new network location, follow the below steps:

Click on the Configure Network Location button in GEO LOCATIONS page.

CONFIGURE NETWORK LOCATION page will then appear. To add a new network location, click on the Add New Network Location button in this page.

The NETWORK LOCATION page then pops up for adding the new network location. Let us use an example to help you understand how to configure a new geographic location. Assume that your enterprise has offices in the East Coast of USA, with a branch in Boston. The Boston branch spans three different buildings, namely - North Building, South Building, and East Building. Each building is in a different network. Users from these buildings communicate with your web site over the intranet. To configure a geo location mapper XML file for the East Coast, first specify the Name of the new location you are creating - say, EastCoast.

Then, proceed to specify the location of the mapper file, where the IP ranges of every building in the East Coast are specified. In the case of our example however, this mapper file is yet to be created. Therefore, first click on the Download sample XML link. A geolocation-sample.xml file will then get downloaded to the local host. Open this XML file in a text/XML editor. You need to configure the IP ranges in your geography in this XML file only. This can be performed in one of the following ways:
- By configuring the starting IP and ending IP address of each range, OR;
- By configuring the starting IP address and the sub-net mask of each range.

If you know the starting and ending IP addresses of every network, then go with the first option - i.e., configure the starting and ending IP addresses of every network in the geolocation-sample.xml file to indicate the geographic location. In this case, do the following:

Scroll down the geolocation-sample.xml file until the following sample code block comes into view:
<location start-ip-address="192.168.8.1" end-ip-address="192.168.8.150">
<country>India</country>
<region>Tamil Nadu</region>
<city>Chennai</city>
<country-code>IN</country-code>
<latitude>13.0827</latitude>
<longitude>80.2707</longitude>
</location>

Edit this code block to suit your needs. For instance, assume that the starting and ending IP addresses of every building in our example is as follows:

Starting IP address	Ending IP address	Building
192.168.8.1	192.168.8.250	North Building
192.168.9.1	192.168.9.250	NSouth Building
192.168.10.1	192.168.10.250	East Building

Now, alter the sample code block to configure the location of the North Building. For this, you need the change the values contained within the <location>, <country>, <region>, <city>, <country-code>, <lattitude>, and <longitude> XML tags, as indicated below:

Tag	Description	Value
<location start-ip-address=	The IP address with which the IP range of the North Building begins	192.168.8.1
end-ip-address=	The IP address with which the IP range of the North Building ends	192.168.8.250
<country>	The country to which the North Building belongs	USA
<region>	The region in which the North Building is situated	East Coast
<city>	The city in which the North Building stands	Boston
<country-code>	The custom code using which you want to represent the North Building - in the case of our example, let us use the code ‘NB’	NB
<lattitude>, <longitude>	The co-ordinates that at least approximately indicate the location of the North Building. The RUM, VDI, and User Experience dashboards in the eG monitoring console include Geo Maps, where the user locations are visually indicated. These co-ordinates help compute and indicate the locations for intranet users in the Geo Maps. You can use any Lattitude/Longitude finder (eg., https://www.latlong.net/) to determine the co-ordinates for any location.	lattitude=42.360081 longitude=-71.058884

The edited code block will be as shown below:

<location start-ip-address="192.168.8.1" end-ip-address="192.168.8.250">
<country>USA</country>
<region>East Coast</region>
<city>Boston</city>
<country-code>NB</country-code>
<latitude>42.360081</latitude>
<longitude>-71.058884</longitude>
</location>

Similarly, you need to configure a code block for the South Building, and another for the East Building. For this, you need to insert two other <location> code blocks below the one that you have just configured for the North Building. The code blocks for the South and East Buildings will look like this:
<location start-ip-address="192.168.9.1" end-ip-address="192.168.9.250">
<country>USA</country>
<region>East Coast</region>
<city>Boston</city>
<country-code>SB</country-code>
<latitude>42.360085</latitude>
<longitude>-71.058890</longitude>
</location>

<location start-ip-address="192.168.10.1" end-ip-address="192.168.10.250">
<country>USA</country>
<region>East Coast</region>
<city>Boston</city>
<country-code>EB</country-code>
<latitude>42.360090</latitude>
<longitude>-71.058895</longitude>
</location>

From the <country-code> tag highlighted in the code blocks above, it is clear that the custom codes ‘SB’ and ‘EB’ have been assigned to the South and East Buildings, respectively. Also, note that the values of the <country>, <region>, and <city> XML tags in both the code blocks above are the same as that of the code block for the North Building. This is because, all 3 buildings are in the same city, region, and country. However, you will find that there is a marginal change in the values of the <lattitude> and <longitude> tags in the 3 code blocks.

Now that the locations we need have been configured, save the sample file, but in a different name, anywhere in the local host.

On the other hand, if you do not know the ending IP addresses, then you can have the eG Enterprise system automatically compute the IP address range of each of your networks. For this, you need to go with the second option - i.e., configure the starting IP address and sub-net mask of each of your networks. In this case, follow the steps below:

Assume that the starting IP address and subnet-mask of each building in our example is as follows:

Network IP Range	Subnet-mask	Building
192.168.8.0	255.255.254.0	North Building
192.168.9.0	255.255.254.0	South Building
192.168.10.0	255.255.254.0	East Building

Next, open the geolocation-sample.xml file that you downloaded at step 4 above in a text/XML editor. Search the file for the text, ‘Option 2’. Once you find it, scroll down further, so the following code block comes into view:

To use this code block, first ‘uncomment’ it by removing the , within which the code block is contained. Then, proceed to edit the block, to configure it with the location of the North Building in our example. For this, you need the change the values contained within the different tags in the sample code block, as indicated below:

Tag	Description	Value
<location network=	The IP address with which the IP range of the North Building begins	192.168.8.1
subnet-mask=	The subnet mask of the new location	255.255.254.0
<country>	The country to which the North Building belongs	USA
<region>	The region in which the North Building is situated	East Coast
<city>	The city in which the North Building stands	Boston
<country-code>	The custom code using which you want to represent the North Building - in the case of our example, let us use the code ‘NB’	NB
<lattitude>, <longitude>	The co-ordinates that at least approximately indicate the location of the North Building. The RUM, VDI, and User Experience dashboards in the eG monitoring console include Geo Maps, where the user locations are visually indicated. These co-ordinates help compute and indicate the locations for intranet users in the Geo Maps. You can use any Lattitude/Longitude finder (eg., https://www.latlong.net/) to determine the co-ordinates for any location.	lattitude=42.360081 longitude=-71.058884

The edited code block will be as shown below:

<location network="192.168.8.0" subnet-mask="255.255.254.0">
<country>USA</country>
<region>East Coast</region>
<city>Boston</city>
<country-code>NB</country-code>
<latitude>42.360081</latitude>
<longitude>-71.058884</longitude>
</location>

Similarly, you need to configure a code block for the South Building, and another for the East Building. For this, you need to insert two other <location> code blocks below the one that you have just configured for the North Building. The code blocks for the South and East Buildings will look like this:
<location network="192.168.9.0" subnet-mask="255.255.254.0">
<country>USA</country>
<region>East Coast</region>
<city>Boston</city>
<country-code>SB</country-code>
<latitude>42.360085</latitude>
<longitude>-71.058890</longitude>
</location>

<location network="192.168.10.0" subnet-mask="255.255.254.0">
<country>USA</country>
<region>East Coast</region>
<city>Boston</city>
<country-code>EB</country-code>
<latitude>42.360090</latitude>
<longitude>-71.058895</longitude>
</location>

From the <country-code> tag highlighted in the code blocks above, it is clear that the custom codes ‘SB’ and ‘EB’ have been assigned to the South and East Buildings, respectively. Also, note that the values <country>, <region>, and <city> XML tags in both the code blocks above are the same as that of the code block for the North Building. This is because, all 3 buildings are in the same city, region, and country. However, you will find that there is a marginal change in the values of the <lattitude> and <longitude> tags in the 3 code blocks.
Now that the locations we need have been configured, save the sample file, but with a different name, anywhere in the local host.

If you choose not to configure any specific geographic location for your intranet users, then you can make sure that the default location specification contained within the following code block automatically applies to all intranet users:

You will find this code block at the end of the geolocation-sample.xml file that you downloaded at step 4 above. To use this ‘default location’ code block, do the following:

The “default location” code block will be commented by default. To enable this code block, you should first uncomment it by removing the , within which the code block is contained.

Then, proceed to edit the code block by configuring the ‘default’ <country>, <region>, <city>, <country-code>, <lattitude>, and <longitude> for all your intranet users. In the case of our example, let us go with the following ‘default’ specification.

Tag	Description	Value
<country>	The country to which your intranet users belong	USA
<region>	The region to which your intranet users belong	East Coast
<city>	The city where your intranet users reside	Boston
<country-code>	The country code that represents the country to which your intranet users belong	NB
<lattitude>, <longitude>	The co-ordinates that at least approximately indicate the location of your users. The RUM, VDI, and User Experience dashboards in the eG monitoring console include Geo Maps, where the user locations are visually indicated. These co-ordinates help compute and indicate the locations for intranet users in the Geo Maps. You can use any Lattitude/Longitude finder (eg., https://www.latlong.net/) to determine the co-ordinates for any location.	lattitude=42.360081 longitude=-71.058884

The edited code block will be as shown below:
<location is-default="true">
<country>USA</country>
<region>East Coast</region>
<city>Boston</city>
<country-code>US</country-code>
<latitude>42.360081</latitude>
<longitude>-71.058884</longitude>
</location>

Note:

Note that the ‘default’ configuration will also apply to those users whose client IP addresses do not fall within the IP ranges configured/computed using options 1 and 2.
Finally, save the file, but with a different name, anywhere in the local host.

Now that the locations have been configured in the XML file, go back to NETWORK LOCATION page. Click the Browse button in this page to search for the XML file containing your location configurations. Once it is found, select it, so that your selection is reflected in the Geo location file text box.
Finally, click the Add button in NETWORK LOCATION page to add the new network location and upload the corresponding XML file to the eG manager. CONFIGURE NETWORK LOCATION page will then appear displaying the new location that you added.
At any given point in time, you can make changes to the XML file mapped to a network location, save the updated file in a different name, and reupload the new file to the eG manager. For this, all you need to do is click this icon corresponding to the network location displayed in CONFIGURE NETWORK LOCATION page. NETWORK LOCATION page will then appear, where you can specify the new XML file that should replace the old one.
You can delete a location configuration, by clicking on this icon corresponding to it in CONFIGURE NETWORK LOCATION page. Note that deleting a network location will not delete the XML file mapped to it.