#### To Upgrade a JBI Component

Upgrading a JBI component replaces a service engine or a binding component with a different version of the component. Upgrading a JBI component enables you to replace the component without the need to redeploy any service assemblies that are already deployed. You may upgrade to a later version or an earlier version of the component.

If the component that you are upgrading implements the `upgrade` method, the component obtains the paths to the directories of the previously installed version and the replacement version. This information enables the component to perform additional processing, for example, creating and deleting database tables.

Note - An upgrade to a JBI component applies to all targets. In domains that are configured to support clusters, you cannot upgrade a component on only a subset of available targets.

You can upgrade a component only if the component name remains unchanged after the upgrade. The component name is defined in the JBI metadata of the component archive.

###### Before You Begin

Ensure that the following prerequisites are met:

- The component that you are upgrading is shut down.

- You have the location of the archive file that contains the replacement version of the component.

- In domains that are configured to support clusters, all targets where the component is installed are started.

1. In the tree component, expand the JBI node.
2. Under the JBI node, select Components.

   The Components page opens.

3. In the Action column of the JBI Binding Components and Service Engines table, follow the Upgrade link for the component that you are upgrading.

   The Upgrade Component page opens.

4. In the Upgrade Component page, specify the archive file of the replacement version of the component.
   - If the file is located on the machine where your web browser is running, specify the file as follows:
     1. Select the Package File to Be Uploaded to the Application Server option.
     2. In the File to Upload field, specify the full path to the file.
   - If the file is located on the machine where the Domain Administration Server (DAS) is running, specify the file as follows:
     1. Select the Package File That is Accessible From the Server option.
     2. In the File to Copy field, specify the full path to the file.
5. Click Upgrade.

   After a successful upgrade, the directories of the previously installed version are deleted.

###### Troubleshooting

The replacement version of a component might not work with previously deployed Service Assemblies when the component is started after an upgrade. In this situation, perform the following sequence of operations to upgrade the component:

- Undeploying all Service Assemblies

- Uninstalling the existing version of the component

- Installing the replacement version of the component

- Redeploying all Service Assemblies

If the archive file of the replacement version is inconsistent with the archive file of the original version, the upgrade fails. If an upgrade fails, the directories of the replacement version are deleted.