eG Administration
 

Auto Discovery of Segment Topology

To automatically discover the topology of a segment, do the following:

  1. In the ADD NEW SEGMENT page, start configuring the segment by providing a Segment name, pick Auto as the Segment type, and then choose None from the Associated to the zone list. Then, click on the Add button. The AUTO TOPOLOGY page then appears.

  2. The interconnections between components of a segment must be configured from left-to-right, with the left most node(s) representing the entry points through which users access the web services offered in the target environment. To begin the configuration therefore, pick the type of component that serves as the ‘entry point’ for your web services from the Component Type list.
  3. All managed components of the chosen type will then appear in the List of Components drop-down. Select a component of the chosen type from this drop-down. The AUTO TOPOLOGY page allows you to pick any managed component in your environment for inclusion in the segment, even if that component is part of another segment. Only those components that are included in a zone will be unavailable for selection in the LIST OF COMPONENTS drop-down.

    Say for example, users access the services offered by the segment through the network node, select Network Node as the Component Type and the node, for e.g.,192.168.10.1:NULL from the List of Components drop-down.

  4. Say that the network node, 192.168.10.1:NULL, in our example connects to a Web server (192.168.10.12:80), which shares a logical relationship with a Netscape Application server (192.168.10.28:10818), which in turn relies on an Oracle database (192.168.10.8:1521:egurkha) for its data needs. If the eG agent's component discovery and automatic topology discovery abilities are enabled, then as soon as the network node is chosen, all the other components that form part of the topology and their inter-relationships will be automatically discovered and displayed in this page.
  5. The symbol that appears alongside each component in the segment topology of this page indicates that the corresponding components are ‘recent’ additions to the topology.
  6. If for some reason, any segment component was not automatically discovered by the eG agent, you can alter the segment topology ‘on-the-fly’ to include that component(s). For instance, say, the Netscape Application server in this page talks to an LDAP server (192.168.10.61:389) as well. Since the eG agent has not auto-discovered the inter-connection between the application server and the LDAP server, let us manually add the LDAP server to the segment topology. To do this, first, right-click on the segment component with which the LDAP server interacts - in the case of our example, it is the Netscape Application server. Doing so will bring up a shortcut menu.
  7. To establish a Uses connection between the Netscape application server chosen and the LDAP server, pick the Uses option from the shortcut menu. This will invoke a pop up widow.
  8. To an auto-discovered topology, you can add any managed component or a component that has just been dsicovered and is yet to be managed. To add a managed component to the topology, select the Managed option from the pop up window. For adding a component that has only been discovered and not managed, select the New option from this window. The LDAP server in our example has already been managed. Therefore, pick the Managed option, and select LDAP from the list of component types. All managed LDAP servers will then appear in the LIST OF COMPONENTS section. Click on the check box alongside the LDAP server that you want to add to the topology. The topology will instantly change to reflect the addition.
  9. Likewise, you can add multiple components to an auto-discovered topology. You can then close the pop up window by clicking the X button at the right, top corner of the window.
  10. In addition to components, component groups can also be added to the topology. Say that the Netscape Application server in our example is mapped to a group comprising of an LDAP server and an Oracle database server. To add this group to the topology, first, right-click on the Netscape Application server component in the topology, and pick the Uses option.
  11. When the pop up window appears, select the Managed option, pick Group from the list of component type, and select the group to be associated with the Netscape application server from the LIST OF COMPONENTS section.
  12. Upon selecting the group, a Uses relationship will be automatically established between the Netscape application server (in our example) and the group.
  13. Besides adding components/component groups, you can also remove one/more components/groups from an auto-discovered topology. For instance, consider the auto-discovered topology comprising a network node that is physically connected to two Linux servers - one that is already managed and another that has just been discovered and is yet to be managed (indicated by the symbol, ).
  14. Assume that you want to remove the managed Linux server, named linux, from the topology, and retain the newly discovered server, 192.18.122.1. For this, first, right-click on the linux server to be removed, and pick the Remove option from the shortcut menu that appears.
  15. The change will be immediately reflected in the topology page.
  16. You can then proceed to save the topology. However, note that a segment topology can contain only ‘managed components’. In the case of our example, the Linux server, 192.168.122.1, is yet to be managed. To be able to save the topology, you first need to manage this server. For this, right-click on the Linux server in the segment topology, and pick the Manage option from the shortcut menu.
  17. The NEW COMPONENT DETAILS page will then appear, using which you can change the configuration of the server being managed. Using this page, the Nick name of the server, the status of the Agentless flag and the Internal agent assignment flag (if available), and the External agent assigned to the server can be changed. Finally, click the Add button to add the server.
  18. With that, the unmanaged server has been managed. The topology display too will change to this effect.
  19. You can now save the topology by selecting the Save topology option that appears when the button at the right, top corner of this page is clicked.
  20. You can click on the Refresh option in the menu that appears in this page to refresh a topology, so that it displays recent additions/removals. To clear a topology, select the Clear all option from the shortcut menu.
  21. In a topology with a limited number of newly discovered components, you can right-click on each unmanaged component to manage it, as discussed previously. However, when many components in a topology are unmanaged, managing each component one after another, will be a cumbersome task! To save the time and trouble involved in this exercise, the AUTO TOPOLOGY page provides you with the option to manage all the newly discovered components in the topology at one shot! For instance, consider the topology that consists of many newly discovered components.
  22. To manage all these components simultaneously, click on the button at the right, top corner of this page and pick the Manage all option from the menu that appears. A pop up window will then appear listing all the unmanaged components in the topology.
  23. To add all the listed components to the eG Enterprise system, select the check box in the top row of the table in the pop up window, and click on the Add / Manage button. Once the components are managed, the topology display will change to indicate the same.