What is the Local Processing (HVR) hub?
In a replication setup, the HVR hub is an installation of HVR that plays the role of the master for the data flowing between the source(s) to target(s).
- Every HVR replication must have a hub i.e. an installation of HVR that plays the role of the hub.
- There is only one download/installation of HVR per operating system, independent of whether the installation will be playing the role of a hub.
- The hub installation must run a scheduler service to manage jobs that move data between databases/locations (capture jobs, integrate jobs, refresh jobs, compare jobs). An installation of HVR that does not play the role of a hub – typically referred to as an agent installation – does not run a scheduler service.
- The HVR hub must connect to a database – the "hub database" – to store the metadata repository consisting of 15 relational tables. The hub database can be running on the same machine as the HVR hub, or it can be a remote database (e.g. a database service in the Cloud, or a database on another server). To establish the connection to the hub database HVR must have access to connectivity libraries for the specific database. Refer to the release notes $HVR_HOME/hvr.rel for the requirements per database.