Managing the SAP Web Application Server

eG Enterprise can automatically discover the SAP Web Application Server in the environment and also lets you to add the SAP Web Application Server component if the server is not auto-discovered. The following steps explain you how to manage the server that is auto-discovered and how to manually add the SAP Web Application Server using the eG administrative interface.

  1. Log into the eG administrative interface.
  2. If a SAP Web Application Server is already discovered, then directly proceed towards managing it using the COMPONENTS – MANAGE/UNMANAGE page (Infrastructure -> Components -> Manage/Unmanage).
  3. However, if it is yet to be discovered, then run discovery (Infrastructure -> Components -> Discover) to get it discovered or add the component manually using the COMPONENTSpage (Infrastructure -> Components -> Add/Modify). Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS – MANAGE / UNMANAGE page.

  4. To add the component manually, follow the Components -> Add/Modify menu sequence in the Infrastructure tile of the Admin menu.
  5. In the COMPONENT page that appears next, select SAP Web Application Server as the Component type. Then, click the Add New Component button. This will invoke Figure 1.

    Figure 1 : Adding a SAP Web Application server

    Note:

    A SAP WAS cluster typically has one/more server processes running within a single SAP WAS instance. To monitor a SAP WAS cluster, each server process in the cluster should be added as a separate SAP Web Application Server component in eG Enterprise.

  6. Then, try to sign out of the eG administrative interface. Upon doing so, Figure 2 will appear listing the unconfigured tests for the SAP Web Application server.

    Figure 2 : The list of unconfigured tests for the SAP Web Application server

  7. Click on any test in the list of unconfigured tests to configure. Refer to Monitoring the SAP Web Application Server chapter to know more details on configuring these tests.
  8. Finally, signout of the eG administrative interface.