Installation and Upgrade Guides › Web Agent Installation Guide for Apache-based servers › Starting and Stopping Web Agents

Starting and Stopping Web Agents

Enable a Web Agent

Configure your agent parameters and then enable the agent to protect the resources on the web server.

Note: No resources are protected until you also define policies in the CA SiteMinder® Policy Server.

Follow these steps:

1. Open the WebAgent.conf file with a text editor.

   Note: Agents for IIS installed on 64-bit operating environments have two WebAgent.conf files. One file for 32-bit Windows applications. The other file is for 64-bit Windows applications. Modify both WebAgent.conf files when starting or stopping the Agent for IIS.

2. Change the value of the EnableWebAgent parameter to yes.
3. Save and close the WebAgent.conf file.
4. Restart the web server (the web server itself, not the computer on which it runs).

   The Web Agent is enabled.

More information:

WebAgent.conf File Locations

Modify the Oracle iPlanet Startup Script to Prevent Crashes when the Server Stops

Disable a Web Agent

If you want to stop the Web Agent from protecting the resources on your web server, disable the Web Agent.

Follow these steps:

1. Open the WebAgent.conf file with a text editor.

   Note: Agents for IIS installed on 64-bit operating environments have two WebAgent.conf files. One file for 32-bit Windows applications. The other file is for 64-bit Windows applications. Modify both WebAgent.conf files when starting or stopping the Agent for IIS.

2. Change the value of the EnableWebAgent parameter to no.
3. Save and close the WebAgent.conf file.
4. Restart the web server (the web server itself, not the computer on which it runs).

   The Web Agent is disabled.

More information:

WebAgent.conf File Locations

Starting or Stopping Most Apache-based Agents with the apachectl Command

Starting or stopping most Apache-based agents with the apachectl command on UNIX or Linux operating environments requires setting the environment variables for the product first.

Note: The Apache-based agents do not support the apachectl -restart option. This procedure does not apply to Apche-based IBM HTTP servers. Use this procedure instead.

Follow these steps:

1. For UNIX/Linux operating environments, set the environment variables by running the following script:

   ./ca_wa_env.sh
   

2. Use one of the following commands:

   apachectl -stop
   

   apachectl -start
   

Start an IBM HTTP Server with the apachectl Command

Starting or stopping an Apache-based agent on an IBM HTTP server with the apachctl command requires extra configuration steps. Before running the apachectl command on the UNIX or Linux operating environments, do the following tasks:

• Source the environment variable script.
• Export appropriate variable for your operating environment from the following list:
  • LD_LIBRARY_PATH (32-bit and 64-bit operating environments)
  • LD_LIBRARY_PATH_64 (Solaris only)

Follow these steps:

1. For UNIX/Linux operating environments, set the environment variables by running the following script:

   ./ca_wa_env.sh
   

2. Do one of the following tasks:
   • For 32-bit or 64-bit operating environments, set the LD_LIBRARY_PATH variable to the location of the lib directory of the IBM HTTP web server. Use the following example as a guide:

     export LD_LIBRARY_PATH=/opt/IBM/HTTPServer/lib:$LD_LIBRARY_PATH
     

   • (Solaris only) For 64-bit operating environments, set the LD_LIBRARY_PATH_64 variable to the location of the lib directory of the IBM HTTP web server. Use the following example as a guide:

     export LD_LIBRARY_PATH_64=/opt/IBM/HTTPServer/lib:$LD_LIBRARY_PATH_64
     

3. Run the apachectl command, as shown in the following example:

   apachectl -start
   

Note: The Apache-based agents do not support the apachectl -restart option. Use the -stop and -start commands instead.