### Manually Update Guardian

To update Guardian on servers that do not have Internet access, you can perform a manual update. To do so, first automatically update Guardian on a server that has Internet access, and then copy the updated files to the server(s) without access.

WARNING: | If you are upgrading from Guardian 1.0.x to Guardian 1.1.0 and want to preserve your Guardian Registry, you must first back up and then manually update the Guardian Registry. For instructions, see Manually Update Guardian Registry on page 86. Please also refer to the Guardian 1.1 Installation Guide and Guardian 1.1 Release Notes for additional important information.

To manually update Guardian, do the following;

1. Automatically update Guardian on a server that has Internet access.

For instructions, see Automatically Update Guardian on page 81.

2. Shut down Guardian on the offline server(s).

Select File > Exit from the titlebar menu.

3. Update the Guardian Signatures Repository on the secure (offline) machine.

Copy the following directory and all of its contents from the updated server to the offline server(s) you want to update, overwriting the old contents:

`<..>\guardian\repository\archives`

Where:

<`..`> is the parent directory of the Guardian installation root directory. The Guardian installation root directory is named `guardian`.

Note: | If you only want to update the Guardian Signatures Repository but not the Guardian application itself, you can skip the remainder of these steps.

4. (Optional) Remove the old Signature Features directories from the offline server(s).

The Signature Features directories are kept in the following directory:

`<..>\guardian\features\`

Where:

<`..`> is the parent directory of the Guardian installation root directory. The Guardian installation root directory is named `guardian`.

The Signature Features directories are named according to the following convention:

`com.bea.guardian.feature.signature.weblogic_<``old_version``>`

Where:

`<``old_version``>` is the old signature release version.

For example:

`..\guardian\features\com.bea.guardian.feature.signature.weblogic_1.0.42`

5. Copy the updated Signatures Features directory to the offline server(s).

Copy the following directory and all of its contents from the updated machine to the offline server(s):

..\guardian\features\com.bea.guardian.feature.signature.weblogic_<CurVersion>

Where:

<`..`> is the parent directory of the Guardian installation root directory. The Guardian installation root directory is named `guardian`.

`<``CurVersion``>` is the most current signature release version.

6. (Optional) Remove the old Signature Plugins JAR files from the offline server(s).

The Signature Plugins JAR files reside in the following directory:

`<..>\guardian\plugins\`

Where:

<`..`> is the parent directory of the Guardian installation root directory. The Guardian installation root directory is named `guardian`.

The files are named according to the following convention:

`com.bea.guardian.signature.weblogic_<``old_version``>`

Where:

`<``old_version``>` is the old signature release version.

7. Copy the updated Signatures Plugins file to the offline server(s).

Copy the following file from the updated machine to the offline server(s):

..\guardian\plugins\com.bea.guardian.signature.weblogic_<CurVersion>

Where:

<`..`> is the parent directory of the Guardian installation root directory. The Guardian installation root directory is named `guardian`.

`<``CurVersion``>` is the most current signature release version.

8. Restart Guardian on the newly-updated offline servers.
9. Check the new configuration.

Do the following:

1. Select Help > Manage Guardian to open the Product Configuration page.
2. In the Product Configuration tree (left pane), expand the BEA Guardian folder and subfolders.
3. Check the version numbers for each item.