### Manually Deploy Guardian Agent

For Guardian versions 1.0.7 and above, you must manually deploy the new Guardian Agent in WebLogic Server before you can use Guardian to evaluate your environment.

Note: | If you have enabled Online Signature/Software Updates in your Guardian Preferences, Guardian periodically performs an automatic update for the latest Guardian version. Clicking the Update button in Guardian also initiates a software version update. If you were previously able to activate domains and run evaluations in Guardian, but are no longer able to do so, this may be due to an update to Guardian 1.0.7 or above. You must delete the earlier Guardian Agent and deploy the new Agent to continue using Guardian.

You can use the WebLogic Server Administration Console to uninstall the existing Guardian Agent and then install and deploy the new Agent. The WebLogic Server Administration Console provides a series of Web-based deployment assistants that guide you through the deployment process. For a summary of the steps involved in deploying the Guardian Agent, see Deploy Guardian Agent from WebLogic Server Adminstration Console on page 37 . For complete instructions on deploying applications, see the Administration Console Online Help, and WebLogic Server documentation.

If you want to deploy the Guardian Agent to multiple servers, you can use a WebLogic Scripting Tool to automate this task. For basic instructions, see Deploy Guardian Agent to Multiple Servers on page 38. For instructions on using a script to activate multiple domains in Guardian, see Activate Multiple Domains on page 49. For complete instructions on using the WebLogic Scripting tool to deploy applications, see the WebLogic Scripting Tool documentation.

#### Deploy Guardian Agent from WebLogic Server Adminstration Console

You can use the WebLogic Server Administration Console to manually deploy the Guardian Agent on that server. This section provides a summary of the basic steps involved for WebLogic Server versions 9.0 and above. For complete instructions for your specific version of WebLogic Server, please see your WebLogic Server documentation and Administration Console Online Help. Please also refer to the Guardian 1.1 Installation Guide and Guardian 1.1 Release Notes for additional important information.

To use the Administration Console to manually deploy the Guardian Agent, do the following:

1. Start the WebLogic Administration Console, and select Lock & Edit in the left pane.

Caution: | Make sure that Lock & Edit is selected for each of the following procedures.

2. Stop the existing Guardian Agent deployment in the WebLogic Server.

By default, the Guardian Agent is named bea-guardian-agent.

Note: | For detailed instructions for this procedure, see “Start and stop a deployed Enterprise Application” in the WebLogic Administration Console Online Help.

3. Delete the existing Guardian Agent deployment from the WebLogic Server, and activate your changes.

Note: | For detailed instructions for this procedure, see “Delete an Enterprise Application” in the WebLogic Administration Console Online Help.

4. Install the new Guardian Agent in the WebLogic Server, and activate your changes.

The Guardian Agent is a WAR file named `bea-guardian-agent.war`, and is located in the following directory:

WARNING: | Do not change the name of the Guardian Agent when deploying it. Be sure to use the default name, `bea-guardian-agent.war`.

`<``root``>\guardian\plugins\com.bea.guardian.agent.weblogic_<``guard-version``>\weblogic<``wls-version``>`

Where:

`<``root``>` is the parent directory for the Guardian installation. For example:
`C:\\Program Files`

`<``guard-version``>` is the current (updated) Guardian version.

`<``wls-version``>` is the version of WebLogic Server in which you are deploying this Agent.

If you are installing the Agent on WebLogic 8.1.x, install the `bea-guardian-agent.war` file located in the `..\weblogic8` directory. For WebLogic Server 9.x and 10.x, install the `bea-guardian-agent.war` file located in the `..\weblogic9` directory.

Note: | For detailed instructions for this procedure, see the section entitled, “Install an Enterprise Application” in the Administration Console Online Help.

5. Start the new Guardian Agent in the WebLogic Server.

Note: | For detailed instructions for this procedure, see “Start and stop a deployed Enterprise Application” in the WebLogic Administration Console Online Help.

6. Start Guardian and activate the neccessary domains in Guardian.

Note: | For detailed instructions for this procedure, see “Activate Domain” in the BEA Guardian Online Help.

You can now use Guardian to evaluate the activated domains in your environment.

#### Deploy Guardian Agent to Multiple Servers

If you need to deploy the Guardian Agent to multiple servers in a cluster environment, you can use the `weblogic.Deployer` command in the WebLogic Server Command Line Interface to automate this task. You can also use the BEA WebLogic Diagnostics Framework (WLDF) to deploy the Agent. This section provides basic instructions for using the `weblogic.Deployer` command for this purpose. For instructions on using WLDF, please see the WebLogic Diagnostics Framework product documentation.

Note: | Please also refer to the Guardian 1.1 Installation Guide and Guardian 1.1 Release Notes for additional important information.

WARNING: | Do not change the name of the Guardian Agent when deploying it. Be sure to use the default name, `bea-guardian-agent.war.`

At the WebLogic Server CLI prompt, enter the following command line:

`java weblogic.Deployer -debug -adminurl http://`<admin_url`>:<`port`> -username <`username`> -password <`password`> – targets adminserver,<`cluster1`>,<`cluster2`> -deploy -sourcerootforupload <`dir_path`>\bea-guardian-agent.war`

Where:

- `<`admin_url`>` is the URL for the WLS Admin Server.
- `<`port`>` is the port number for the WLS Admin Server.
- `<`cluster1`>,<`cluster2`>` are the names of all configured clusters.
- `<`dir_path`>` is the directory path to the Guardian Agent WAR file (`bea-guardian-agent.war`).