Clustering considerations for Unify in Portal

Note: This section applies to the Cleo Harmony and Cleo VLTrader applications only.

If you enable and use the Unify in Portal feature in Cleo Harmony, any Portal metadata that has been built up on your systems could be affected by switching from independent to clustered instances.

Note: The following applies only to the Unify in Portal feature and not the Cleo Harmony system itself.

You can safely add one or more instances to an existing instance of Unify in Portal without intervention provided the additional instances have had no previous Portal activity.

You can create a cluster from two or more instances that have each had previous activity. However, because there is no way to merge the underlying databases, all but one of the databases must be wiped. By default, the database with the most recent transaction is used moving forward and the others are wiped. Alternatively, you can choose to manually wipe all but one of them and use the remaining one moving forward. In either case, the remaining database is the basis for all databases moving forward.

You can back up the database on the instance in question by saving the contents of the directory, <install>/core/data/cleo.neo-store. To wipe the database, delete the directory, <install>/core/data/cleo.neo-store.

If you already have two or more instances of Cleo Harmony clustered and upgrade using a license that adds Unify in Portal, the clustering for Unify in Portal will work properly without any intervention.