Register an App Volumes Instance as a Target

For synchronization operations to occur, a source and target relationship is necessary. To achieve this relationship, an instance must be added as a target to another instance. As a result, the instance to which the target is added becomes the source. You can register a target instance by using the Add Target button on the source's App Volumes Instances page.

After a synchronization relationship is established between the source and target, the applications and packages on the target instance can be managed only from the source. If the target is removed, the source no longer manages the applications and packages for this target and the target's inventory items are manageable from the target instance.

An instance can have multiple sources and multiple targets.

To understand the definition of terminologies such as App Volumes instance, source instance, target instance, and so on, see the Terminologies used in the context of App Volumes Application Synchronization in Configure Multiple App Volumes Instances for Application Synchronization.

Prerequisites

Ensure that the domain of the source instance is accessible by the target instance.
Ensure that a target instance has a trusted certificate.
Ensure that you use valid credentials and have permissions to access the instance that is configured as a target.
Ensure that you are aware of the Criteria for Application Synchronization.
To understand how synchronization operations occur, see Configure Multiple App Volumes Instances for Application Synchronization.

Procedure

In the App Volumes Manager admin UI, navigate to INFRASTRUCTURE > Instances.
On the App Volumes Instances page, click Add Target.

On the Add App Volumes Instance Target page, enter the following information:

Option Description

Secure Address

Option	Description
Secure Address	IP address or the host name of the target instance You can also specify the port address of the target instance. For example: `<IP_address>:<port_address>`. By default, the port number used is `443`. Note: Communication between the source and target instances occurs via HTTPS.
Username and Password	Administrator credentials required to access the target instance
Domain	Domain for the service account to which the target instance belongs.

IP address or the host name of the target instance

You can also specify the port address of the target instance.

For example: <IP_address>:<port_address>.

By default, the port number used is 443.

Note: Communication between the source and target instances occurs via HTTPS.

Username and Password Administrator credentials required to access the target instance

Domain Domain for the service account to which the target instance belongs.

Click Add and follow the UI prompts.
The target instance is listed in the Related Instance table.
In the Related Instances table, you can expand the + sign and view the target instance's details.

Results

After the target is successfully registered on the source, you can navigate to the target instance and observe the following UI changes on the target:

The source instance is listed in the Related Instance table.
If you have already imported the application packages, which are replicated from the source instance, then the applications and packages on the target are in a synchronized relationship with the source. Such applications and packages can now be managed only from the source by using the Manage Source button.
For more information about managing the applications and packages from the source instance, see Manage a Synchronized App Volumes Application at the Source.

What to do next

If you want to edit the details of this instance, see Edit an App Volumes Instance.
If you want to monitor synchronization, see Monitor App Volumes Synchronization Operations.
If you want to establish a synchronization relationship with the source, you must replicate the application packages from the source using storage groups and import these packages on this instance. For more information, see Configure Multiple App Volumes Instances for Application Synchronization.
You can verify whether an imported application package is associated with the correct application on the source by using the application GUID. On the target instance, navigate to the application's summary page and view the GUID. This must match the application GUID on the source instance.