Versions Compared

Old Version 20

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 21

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Go to Start > Control Panel > Programs > Programs and Features.
  2. On the left Side Bar, select Turn Windows features on or off.
  3. Wait for the Windows Features dialog box to open and fill, and then expand Internet Information Services.
  4. SelectSelect IIS 6 Metabase Compatibility service under IIS 6 Management Compatibility.
  5. Click OK.

...

  1. Select one of the available Microsoft IIS versions from the drop-down menu:.

    Info

    If the IIS version or Web site name (next step) is not auto-detected, enter it manually.

  2. Select the Detected Web site name from the menu.
  3. Select the Application type (Web or Siebel) from the menu.
  4. Select the Application version from the menu. This textbox is unavailable  when Web is chosen.
  5. Enter the Instance name. Use a free-text identifier to distinguish between multiple monitored Web sites.

  6. Optional. Check Allow internet information service restart. If you leave this box empty, post-installation actions are required. 

  7. Click Next.

...

  1. Select the Web site from the menu.
    The fields for a WebLogic, WebSphere, and Apache Web server are auto-detected and populated when you select one of the auto-discovered Web sites in the Detected Web sites list.
    The following information appears:

    • Apache. The full path of the configuration file.

      Info

      The auto-detection mechanism is limited in different ways, depending on whether Apache is on a Windows or UNIX server. On Windows, the detection is based on the services list. Therefore, Apache will not be detected if it is not defined as a service. On UNIX, the detection is based on running processes. The Web server version is not detected if the Precise user does not have execute permission on the Apache executable (HTTPD).

  2. Enter the Web site configuration file. To browse for the appropriate folder and file, click the browse (...) button.
    This input is required for Apache and Sun iPlanet. For all other web servers, it is recommended to manually enter the value to optimize the installation process. If however, the value is unavailable, the field can be left blank.
    The following values are auto-detected:
    • Apache. The full path and name of the main configuration file. For example:
      C:\WebServers\Apache\Apache13\conf\httpd.conf
      For Apache that serves Oracle applications:
      /rac_shared/env/appl/apps/tech_st/10.1.3/Apache/Apache/conf/httpd.conf
      or
      /rac_shared/env/inst/apps/VIS_pool-linux-rac-1/ora/10.1.3/Apache/Apache/conf/htt pd.conf)
    • Sun One or Sun iPlanet. The full path to the server.xml file of a specific server on a specific node in a specific cell. For example: c:\WebServers\Sun\WebServer6.1\https-admserv\config\server.xml.

    • Tomcat. The full path to the server.xml file. For example: c:\WebServers\Tomcat\conf\server.xml.

      Info

      If the auto-detected value is incorrect, you can change it manually.

  3. Select the Web server version from the menu.
    The Tier installer normally auto-detects and displays the Web server version in this field. If the Web server version is not auto-detected, or incorrect, enter the inputs manually.
    Select one of the following Web server version options from the list:
    • Apache: 1.3.x, 2.0.x, or 2.2.x
    • Sun One: 6.1
    • Apache Tomcat 5.x, 6.x
    • Sun iPlanet 6.0
  4. Select the appropriate Web Server bits from the drop-down menu.
    This input is required only when using Apache or Sun iPlanet. For other Web servers, this input field is grayed-out. Normally the Tier installer will auto-detect and display the Web server bits in this field.
    If the Web server bit number is not auto-detected, or incorrect, enter the bit number manually. Select one of the following Web server bit numbers from the list:
    • 32
    • 64
  5. Select the application type from the drop-down menu.
    This is the application served by this Web server site. This information enables better configuration of the Web Tier Collectors. The following options are available:
    • Web (default)
    • Siebel
    • PeopleSoft
    • Oracle Applications
  6. Select the application version from the drop-down menu.
    This is the version of the application server chosen in the previous field. Select an application server version:
    • Siebel 7.7-8.1.1x.x
    • PeopleSoft 8.44-8.50x.x
  7. Enter the instance name. Use a free-text identifier to distinguish between multiple, monitored Web sites.
  8. Click Next.

...

  1. Select the Web site from the drop-down menu.
    The fields for a WebLogic and WebSphere will be auto-detected and populated when you select one of the auto-discovered Web sites in the Detected Web sites list.
    The following information is shown:
    • WebLogic. The server name (if it exists) or full path of the configuration file.

    • WebSphere. The server name attribute from the server.xml file, or the full path of the configuration file.

      Info

      However, instances that are installed as Windows services will are not be detected whether even when they are running or not. On UNIX, in most configurations of HP, Linux, Sun, and AIX prior to version 5.3 patch 5, the Web servers may be partially detected or not detected at all.

  2. Enter the Web site configuration file. To browse for the appropriate folder and file, click the browse (...) button.
    For non-cluster installations, it is recommended to manually enter the value to optimize the installation process. If however, the value is unavailable, the field can be left blank. For cluster installations, this is ignored.
    The following values are auto-detected:
    • WebLogic. The full path and name of the config.xml file (for example:
      c:\WebServers\bea\weblogic81\samples\domains\medrec\config.xml).

    • WebSphere. The full path to the server.xml file of a specific server on a specific node in a specific cell (for example: c:\WebServers\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\I4W-VM-SRV3Node01Cell\nodes\I4W-VM-SRV3Node01\servers\server1\server.xml).

      Info

      If the auto-detected value is incorrect, you can change it manually.

  3. Select the Web server version from the drop-down menu.
    Normally the Tier installer will auto-detect and display the Web server version in this field. If the Web server version is not auto-detected, or incorrect, enter the inputs manually. Select one of the following Web server version options from the list:
    • WebLogic. 8.x, 9.x, 10.x
    • WebSphere. 6.0, 6.1-6.x, 7.0
  4. Select the application type from the drop-down menu.
    This is the application served by this Web server site. This information enables better configuration of the Web Tier Collectors. The following options are available:
    • Web (default)
    • PeopleSoft
  5. Enter the instance name. Use a free-text identifier to distinguish between multiple, monitored Web sites.
  6. Click Next.

...

  1. Select the application server from the drop-down menu.
    The textboxes for the Oracle 10g Application Server will be auto-detected detect and populated populate when you select one of the auto-discovered Web sites in the Detected Web sites list. You can manually change the auto-detected values. The auto-detection mechanism has the following limitations:
    • The Web server version is not returned if you don’t have are lacking read permissions on the inventory/ContentsXML/configtools.xml file in the Application server folder.
    • On Solaris and AIX prior to version 5.3 patch 5, the Oracle 10g Application Server may be partially or not detected.
    • Instances that are currently not running are not detected. On Windows, instances that are installed as services are not detected , whether even if they are running or not.

  2. Select the Oracle Application server configuration file. To browse for the appropriate folder and file, click the browse (...) button.

    Info

    The configuration file should be named opmn.xml. Example for a configuration file path:

    /i4t/i3/websun1_webservers/OracleAS/10.1.3/opmn/opmn.xml.

    Info

    Normally the Tier installer will auto-detect detects and display displays the Oracle Application server configuration file and the Apache Web server configuration file (step 3) in their fields. If the server configuration files are not auto-detected, or incorrect, enter the inputs manually.

  3. If there is an Integrated Apache web server running before the Oracle AS, select its configuration file. To browse for the appropriate folder and file, click the browse (...) button.
    For example, the configuration file of apache in an Oracle Applications 12 installation:
    /rac_shared/env/appl/apps/tech_st/10.1.3/Apache/Apache/conf/httpd.conf
    or
    /rac_shared/env/inst/apps/VIS_pool-linux-rac-1/ora/10.1.3/Apache/Apache/conf/httpd.conf

  4. Select the Oracle Application server version, from the drop-down menu.

    Info

    Normally, the Oracle Application server version will be auto-detected. If it’s it is not auto-detected, manually enter the server version.

  5. Select the application type from the drop-down menu.
  6. Select the application version from the drop-down menuthe menu. The following options are available:
    • Web (default)
    • PeopleSoft
    • Oracle Applications
  7. Enter the instance name. Use a free-text identifier to distinguish between multiple, monitored web sites.
  8. Click Next.

...

  1. Run the netstat command to see a list of all open connections on the server machine.
  2. On a UNIX server, use the lsof utility located in the <precise_root>/products/insight/host/bin folder on the monitored server.

To use the utility to obtain a list of all TCP/IP ports used by a service, run the following command:

lsof -P|grep LISTEN|grep listener process name

To access a list of lsof utility options, run the following command:

lsof -h

Info

The lsof utility is only available if the Insight Savvy for Network is installed. If you want to run this utility before completing the Savvy installation, log in as the root user and locate the bin/lsof.<operation-system-version> file in the Insight installation folder.

...

  1. Mark one of the listed domains.
  2. Mark the SSL box if the domain is secured (HTTPS).
    If the desired domain is not on the list, or requires editing, follow steps a-f:f
    1. Click Add or Edit.

    2. Choose either “All IPs” or “Specific IP” All IPs or Specific IP.

      Info

      If every IP address that the server listens on , is a real IP address, then they should all be specified. If the different names are actually virtual hosts, then only one should be specified. If the only difference is in the ports (same IP address with several ports), then only one of them should be specified.

    3. If a Specific IP is selected, enter the Specific specific IP name.
    4. Enter the port number for this domain.
    5. Enter the Host Header name for this domain (If , if it exists).
    6. Mark the Check SSL box if  if the domain is secured (HTTPS).
    7. Click Add.Click , and then click Next.

About the AdminPoint Tier installation preview screen

...

At this screen, you can still change any of the settings displayed. Click Back to change any of the displayed settings. Click , click Next to continue installation. Click , or click Cancel to stop the installation process.

...

This screen appears when the AdminPoint Tier installer is actually performing installation. Installation may take several minutes.

The progress screen visually displays the progress of actual installation on selected servers.

...