Versions Compared

Old Version 17

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 18

changes.mady.by.user Nadja Pollard

Saved on

Key

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

...

To install a Web instance on IIS7.x, the “IIS6 IIS6 Metabase Compatibility” Compatibility service and “ISAPI filters” ISAPI filters must be installed.

To enable IIS6 Metabase Compatibility and ISAPI filters on Windows 2008

  1. Go to Start>Control Panel>Programs>Programs Start > Control Panel > Programs > Programs and Features.
  2. On the left Side Bar, select Turn Windows features on or off.
  3. Go to Roles ' Web Server (IIS), click Add Role Services, and then select the following:
    1. IIS6 Metabase Compatibility under IIS 6 Management Compatibility.
    2. ISAPI filters under Application Development.
    3. ISAPI Extension, if you want to collect post-paremetersparameters
  4. Click Next, and then follow then instructions on the screen.

To enable IIS6 Metabase Compatibility on Windows 7

  1. Go to Start>Control Panel>Programs>Programs 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. Select the IIS 6 Metabase Compatibility service under IIS 6 Management Compatibility.
  5. Click OK.

Pre-installation tasks for WebLogic, WebSphere, Tomcat, and Sun One (J2EE stack)

At the end of the installation, you will need to must provide the path to the application file you wish to monitor (.EAR, .WAR, or web.xml file of the application).

...

Info

Before adding a Tier instance, create a list of all required inputs based on the screen information below.

To add a Tier instance

  1. From StartPoint, click the AdminPoint tab.
  2. Click the Setup tab.
  3. From the drop-down menu, select Instances & Clusters.
  4. Click the All instances tree item.
  5. At the bottom of the Display Instances & and Clusters screen, click Add Instance. An Add New Instance dialog box appears.
  6. Select the required technology from the list.
  7. Select the application from the list. If the desired application is not on the list, use the following steps:
    1. Click Add.
    2. In the In Application Name field, type in the new application name.
    3. In the In Application System field, select the system application from the list.

    4. Click OK.

      Info

      To install an instance in an application, you must have ADMINISTRATE.INSTALL permission for the application in which you want to install the instance. If you only have permission for a specific technology, you will only be able to install in an application that is either empty, or is comprised of only the same technology.

  8. Select a Tier from the list.

  9. Click OK to view the next screen.

    Info

    Always refresh AdminPoint after adding an instance.

...

To define the Web Tier property settings, you must first select which Web server type you want to monitor, as well as its location.

To select the Web server type and its location

  1. Select one of the following Web server types , from the drop-down menu:
    • IIS (Microsoft)
    • Apache
    • iPlanet (Sun)
    • WebLogic (Oracle)
    • WebSphere (IBM)
    • Tomcat (Apache)
    • Sun One
    • Oracle AS
    • SAP WAS J2EE

    • Other J2EE

      Info

      The options Apache, SAP WAS J2EE, Sun iPlanet, Oracle 10g Application Server, Sun ONE, and other J2EE Web servers are supported, but currently without Web server statistics. Client-side instrumentation is not supported by Sun iPlanet and Apache 1.3.

  2. Select From the menu, select the server where the Web server instance is located, from the drop-down menu. Click Add to enter the name of a server not on the list. For more information, see see Adding a new server.

    Info

    This is the name or IP address of the server where you want to install the Web Tier Collector with a specific operating system. The server name or IP address appears in the list only if you previously defined it as a Precise server. If using Microsoft IIS, you cannot install on a UNIX platform.

  3. Click Next.

The next installation screen will be is dependent upon which Web server type has been is selected. Click the relevant link below to view the installation procedure for the selected Web server:

...

Anchor
DefiningaMicrosoftIISTierinstance
DefiningaMicrosoftIISTierinstance
Defining a Microsoft IIS Tier instance

To define a Microsoft IIS Tier instance

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

    7.x

  2. 6.x
    3. Info

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

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

  7. OPTIONAL: Mark the box “Allow Optional. Check Allow internet information service restart”restart.

    Info

    If you

    don’t mark the

    leave this box empty, post-installation actions

    will be

    are required. 

  8. Click Next.

Anchor
Definingoneofthefollowinginstances
Definingoneofthefollowinginstances
Defining one of the following instances: Apache, iPlanet, Sun ONE, SAP WAS J2EE, Other J2EE, or Tomcat

Info

A Web site configuration file is mandatory for Sun iPlanet and Apache servers, but is optional for other servers. During installation, the Web site configuration file is editable. If it’s it is not inserted, you will have to must enter Web server listening ports manually on the next screen (Domain Information).

To define one of the above instances

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

    • 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 . 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 . For example: c:\WebServers\Sun\WebServer6.1\https-admserv\config\server.xml).

    • Tomcat. The full path to the server.xml file (for . 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 drop-down menu.
    Normally the The Tier installer will normally auto-detect detects and display 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.1
    • PeopleSoft 8.44-8.50
  7. Enter the instance name. Use a free-text identifier to distinguish between multiple, monitored Web sites.
  8. Click Next.

...