Inhaltsverzeichnis

Cloning eBiss systems

Preparations in the existing system

  1. disable all eBiss automations and stop the eBiss service.
  2. Make sure you have a backup1) and dump the database2)) and move it to the new location.
  3. Upgrade to the latest version.
  4. Dump all eBiss nodes.
  5. Move the message store (keeps the physical messages in files on the drive).
  6. Move the plugins that represent your integration(s).

Activities in the new location (e.g. staging environment)

  1. Install the same version as an „empty“ system.
  2. Add the individual integration plugins3).
  3. Configure eBiss with a new DB.
  4. Import the eBiss dump objects into the appropriate nodes.
  5. Adapt the endpoints to the new environment.

Note: check also Guide for server relocation

Alternative

The executable eBiss.DBCopy.exe allows dumping and importing of the eBiss database including all nodes and transactional data (but excluding the message contents) and can therefore be taken for identical mappings including specific passwords on communication channels and users, but care should be taken, because the communication channels are finally „sharp“.

1)
data backup of VM for example
2)
The executable eBiss.DBCopy.exe allows to DUmp and IMport the eBiss database including transactional data(but exclusive of message content
3)
The plugins that represent your specific eBiss integration.