ETERNUS SF Disk Space Monitor User's Guide - Microsoft(R) Windows Server(TM) 2003/Solaris(TM) Operating System/Linux - 13.0

16.2 Setting up a Virtual Directory

To communicate with a management server, it is necessary to register a virtual directory for a Web server.

In this section, the registration procedure will be explained using the following five Web servers as examples:

• Microsoft(R) Internet Information Server
• Apache HTTP Server 1.3.26
• Netscape(R) Enterprise Server 3.0
• Interstage HTTP Server (bundled with Interstage Application Server)
• InfoProvider Pro (bundled with Interstage Application Server)

When the Web server is Microsoft(R) Internet Information Server and any of the following conditions apply, a virtual directory is set up automatically during installation. (The WWW Service - World Wide Web Publishing Service - must already be running.)

• When an operation management client is installed
• When Agent is installed with HTTP Pull operation selected

However, if the operating system is Microsoft(R) Windows Server(R) 2003, and the sqc~setc.bat commands are executed as additional commands, these commands will not be executed automatically and so will need to be executed manually.

In an operation management client, it is necessary to set up virtual directory security in addition to a virtual directory. The method used to set up directory security is explained in the following section.

16.2.1 For Microsoft(R) Internet Information Server

1. Create a virtual directory.

   

   The WWW Service (World Wide Web Publishing Service) must already be running when the setup commands below are executed. Also, if Microsoft(R) Internet Information Server V5.0 or V6.0 is used, check that the site specified as "Existing Website" does exist.

   

   To execute these commands, open a Command Prompt window and change the current directory to installation directory\bin.

   Execute the following commands to set up the virtual directory:

   • For operation management clients
     Installation directory\bin\sqcSetIISreg.exe -c
   • For Agent
     Installation directory\bin\sqcSetIISreg.exe -a

   For Microsoft(R) Windows Server(TM) 2003, execute the following commands as well:

   • For operation management clients
     Installation directory\bin\sqccsetc.bat
   • For Agent
     Installation directory\bin\sqcasetc.bat

   

   Errors may occur with this command in the following situations:

   • If IIS has not been installed
   • If a Windows Scripting Host has not been allocated
   • If a virtual directory has already been set up
2. Set up directory security.

   

   Directory security setup is only needed on the operation management client.

   1. Open the Microsoft(R) Internet Information Server setup window and select the virtual directory name "SSQC".
   2. Open the Properties window of this virtual directory and click the Directory Security tab.
   3. Set an account with Administrator privileges to be used with anonymous access.
   4. For authorized access, clear the Basic authentication check box.

   

   If access control needs to be performed for the Admin Console, refer to Section 16.3, "How to Set Up Basic Authentication for Operation Management Clients".

16.2.2 For Apache HTTP Server 1.3.26 

1. Open the configuration file from the Start menu as follows:

   Start

   Programs

   Apache HTTP Server

   Configure Apache Server

   Edit the Apache httpd.conf Configuration File

   

   If the user's environment differs from that shown above, adjust accordingly.

2. Set up the virtual directory.

   Add the following lines to the end of the file.

   ScriptAlias /alias/cgi-bin/"installation directory/www/cgi-bin/"

   <Directory "installation directory/www/cgi-bin">

   Options ExecCGI

   AllowOverride None

   Order allow,deny

   Allow from all

   </Directory>

   Alias /alias/"installation directory/www/"

   <Directory "installation directory/www">

   Options None

   AllowOverride None

   Order allow,deny

   Allow from all

   </Directory>

   
   

   

   If necessary, change the access permission settings, etc., to more appropriate values.

   Virtual directory settings vary according to the version of Apache that is used.

   Refer to the Apache manual for details.

3. Apply the settings.

   Overwrite the previous file and close the editor. Restart Apache HTTP Server if it is running.

1. Open the configuration file in the editor.
2. Set up the virtual directory.

   Add the following lines to the end of the file:

   ScriptAlias /alias/cgi-bin/ "installation directory/www/cgi-bin/"

   <Directory "installation directory/www/cgi-bin">

   Options ExecCGI

   AllowOverride None

   Order allow,deny

   Allow from all

   </Directory>

   Alias /alias/ "installation directory/www/"

   <Directory "installation directory/www">

   Options None

   AllowOverride None

   Order allow,deny

   Allow from all

   </Directory>

   

   If necessary, change the access permission settings, etc., to more appropriate values.

   Virtual directory settings vary according to the version of Apache that is used.

   Refer to the Apache manual for details.

3. Since character transformation may be caused in the state of the early stages of Apache2.0, please set it as the following state if needed.

   AddDefaultCharset Off

4. Apply the settings.

   Overwrite the previous file and close the editor. Restart Apache HTTP Server if it is running.

16.2.3 For Netscape(R) Enterprise Server 3.0 

1. Open the Server Administration Page by selecting the following items from the Start menu:

   Start

   Programs

   Netscape SuiteSpot

   Administration

   

   If the user's environment differs from that shown above, adjust accordingly.

2. Select the server to which a virtual directory is to be added and display the Server Manager Page.

   Create the virtual directory.

   Click the Content Management button located at the top of the page and then click the link to Additional Document Directories in the list in the left-hand column to display the Additional Document Directories page.

   Enter the following settings and click the OK button. When the Save and Apply Changes page appears, click the Save and Apply button.

   URL Prefix:Alias

   Map To Directory:Installation directory/www

3. Set the execution permissions for CGI programs in the "cgi-bin" subdirectory of the newly created virtual directory.

   Click the Programs button located at the top of the page and then click CGI Directory in the left-hand column to display the CGI Directory page.

   Enter the following settings and click the OK button. When the Save and Apply Changes page appears, click the Save and Apply button.

   URL Prefix:Alias/cgi-bin

   CGI Directory:Installation directory\www\cgi-bin

16.2.4 Interstage HTTP Server (bundled with Interstage Application Server) 

1. Use the editor to open the Interstage HTTP Server environment definition file.

   Edit the environment definition file stored at the following location.

   C:\Interstage\F3FMihs\conf\httpd.conf

   Note: When the default installation path is used

2. Set up the virtual directory.

   Add the following lines to the end of the file:

   ScriptAlias /Alias/cgi-bin/ "Installation directory/www/cgi-bin/"

   <Directory "Installation directory/www/cgi-bin">

   Options ExecCGI

   AllowOverride None

   Order allow,deny

   Allow from all

   </Directory>

   Alias /Alias/ "Installation directory/www/"

   <Directory "Installation directory/www">

   Options None

   AllowOverride None

   Order allow,deny

   Allow from all

   </Directory>

   

   Change the settings for access privileges and so on if necessary.

3. Apply the settings.

   Overwrite the previous file and close the editor. Restart Interstage HTTP Server if it is running.

   

4. Use the editor to open the Interstage HTTP Server environment definition file.

   Edit the environment definition file stored at the following location.

   /etc/opt/FJSVihs/conf/httpd.conf

   Note: When the default installation path is used

5. Set up the virtual directory.

   Add the following lines to the end of the file:

   ScriptAlias /Alias/cgi-bin/ "installation directory/www/cgi-bin/"

   <Directory "installation directory/www/cgi-bin">

   Options ExecCGI

   AllowOverride None

   Order allow,deny

   Allow from all

   </Directory>

   Alias /Alias/ "installation directory/www/"

   <Directory "installation directory/www">

   Options None

   AllowOverride None

   Order allow,deny

   Allow from all

   </Directory>

   

   Change the settings for access privileges and so on if necessary.

6. Apply the settings.

   Overwrite the previous file and close the editor. Restart Interstage HTTP Server if it is running.

16.2.5 For InfoProvider Pro (bundled with Interstage Application Server) 

1. Use the editor to open the InfoProvider Pro environment definition file.
2. Set up the virtual directory.

   Add the following lines to the end of the file:

   cgi-path-idnt: Installation directory\www\cgi-bin Alias/cgi-bin

   link: Alias Installation directory\www

3. Apply the settings.

   Overwrite the previous file and close the editor. Restart InfoProvider Pro if it is running.

   

   If the version of InfoProvider Pro is earlier than the version bundled with Interstage Standard Edition V2.0L20, it will not be possible to use the above setup method due to functional limitations. Use the following method instead:

4. Create the equivalent of a virtual directory.

Create a new directory named Alias in the highest directory that is made available by the Web server, then copy to this directory everything in Systemwalker Service Quality Coordinator installation directory\www except the "cgi-bin" directory. Use the editor to open the file named "viewer.html" in the Alias directory and insert the <PARAM> tag between the <APPLET> tags, as in the following example:

<APPLET codebase="./classes/" archive="viewer.jar" code="Viewer.class" width=950 height=512>

<PARAM name="CGI" value=http://xxx.yyy.com/Alias-cgi-bin/dbref.cgi>

</APPLET>

"xxx.yyy.com" in the above example represents the host address of the Web server. Change this to the correct address.

1. Use the editor to open the environment definition file of InfoProvider Pro and append the following line to the end of the file:

   cgi-path-idnt: Installation directory\www\cgi-bin Alias-cgi-bin

2. Apply the settings.

   Overwrite the previous file and close the editor. Restart InfoProvider Pro if it is running.

   

3. Use the editor to open the InfoProvider Pro environment definition file.

   Set up the virtual directory.

   Add the following lines to the end of the file:

   cgi-path-idnt: Installation directory/www/cgi-bin Alias/cgi-bin

   link: Alias Installation directory/www/cgi-bin

4. Apply the settings.

   Overwrite the previous file and close the editor. Restart InfoProvider Pro if it is running.

   

   If the version of InfoProvider Pro is earlier than the version bundled with Interstage Standard Edition 3.0, it will not be possible to use the above setup method due to functional limitations. Use the following method instead:

5. Create the equivalent of a virtual directory.

   Create a new directory named Alias in the highest directory that is made available by the Web server, then copy to this directory everything in Systemwalker Service Quality Coordinator installation directory\www except the "cgi-bin" directory. Use the editor to open the file named "viewer.html" in the Alias directory and insert the <PARAM> tag between the <APPLET> tags, as in the following example.

   <APPLET codebase="./classes/" archive="viewer.jar" code="Viewer.class" width=950 height=512>

   <PARAM name="CGI" value=http://xxx.yyy.com/Alias-cgi-bin/dbref.cgi>

   </APPLET>

   

   "xxx.yyy.com" in the above example represents the host address of the Web server. Change this to the correct address.

6. Use the editor to open the environment definition file of InfoProvider Pro and append the following line to the end of the file:

   cgi-path-idnt: Installation directory/www/cgi-bin Alias-cgi-bin

7. Apply the settings.

Overwrite the previous file and close the editor. Restart InfoProvider Pro if it is running.