1. First page
  2. Documentation
  3. Common Procedures
  4. Test environment
  5. Copy environment

Copy environment

Procedure below describes how to copy testing environment into production or vice-versa if needed.

To maintain documents validity the documents are not copied over to the new system.

CREATE TEST EBA DMS FROM PRODUCTION WITHOUT DOCUMENTS

Following procedure is to create separate test system based on settings in production environment.
This procedure copies users, doc types, supporting document and authorisation schema.

PREREQUISITES

Make sure that ini settings are pointing towards TEST Agency as this setup will use same ebaid as production.
If you trigger send/receive it can mess with your documents if you don’t point to TEST Agency.

Ebaid and supreme administrator must be registered on TEST Agency in order to execute send/receive action.
Please provide us correct ebaid as we will register it on TEST Agency when registering on TEST Agency.

We recommend use of SQL Browser tool to easily backup and restore tables from EBA DMS database.

  1. On existing production database backup following tables:

eba_authorization_history
eba_certificate_store
eba_counters
eba_crlcalist
eba_ctx_catalog
eba_ctx_field_desc
eba_ctx_fields
eba_doc_types
eba_doc_types_desc
eba_extern_statuses
eba_extern_statuses_names
eba_extern_statuses_vectors
eba_forms
eba_global_settings
eba_licence_list
eba_mutex
eba_organization_tags
eba_organizationschema
eba_replacements_log
eba_rules_history
eba_rules_new
eba_schemas
eba_supporting_doc_def
eba_sys_app
eba_user_replacements
eba_users_changes
eba_users_ex

ALSO include if you want to transfer script projects:

  1. Create new database. Apply commands for MS SQL or ORACLE if needed.
  2. Create tables on new database with EBA DMS Client.
  3. Restore backed up tables from existing system onto new table.
  4. Update database with EBA DMS Client.

How can we help?