Starting and Stopping Web Agents

Contents
sm1252sp1
Contents
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 Single Sign-On
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 one of the following values:
    • For a Framework agent, change the value of the
      EnableWebAgent
      parameter to
      Yes
      .
    • For a Traditional agent, change the value of the
      EnforcePolicies
      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.
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.
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
Note:
In the RedHat JBoss Enterprise Web Server-2.1 and RedHat JWS HTTP server 3.0 apachectl script, the value of LD_LIBRARY_PATH gets updated to the following path and existing LD_LIBRARY_PATH values are lost:
<JWS_HOME>/lib
The web agent ships version 1.5.3 of libkrb5.so.3, but JWS needs version 1.10.3 of krb5 module which comes by default with RHEL and is available under /lib64.
For the web agents to work, edit the apachectl script and append $LD_LIBRARY_PATH so that the export line is as follows:
export LD_LIBRARY_PATH=<JWS_HOME>/lib:/lib64:$LD_LIBRARY_PATH
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 command. Use the stop and start commands instead.
Start an Oracle 11.g.x HTTP Server with the opmnctl Command
Valid on RedHat Enterprise Linux
Starting or stopping an Oracle HTTP server requires extra configuration steps.
Follow these steps:
  1. Open the opmnctl script with a text editor.
  2. Update the LD_LIBRARY_PATH variable with the agent installation directory. Use the following example as a guide:
    export LD_LIBRARY_PATH=/opt/CA/webagent/bin:$LD_LIBRARY_PATH
  3. Add the following directory to the PATH variable:
    CA/webagent/bin
  4. Save your changes and close the opmnctl script.
  5. Start the agent with the following command:
    opmnctl startall