Replication of metadataIf Agile e6 is used in a distributed environment
on different sites, metadata stored in the database can also be saved
redundantly in a local database. In
such a replicated environment an own database, Agile e6 server, fileserver
and business service is installed on server side. 2. Master-Snapshot 1. The allocation of C_IDs is carried out site-specific
via database sequences from disjunctive areas. This has to be configured
This has some consequences for the workflow: |
|
Therefore,
replication groups have to be modified, if needed, so that the dataview
tables for masks, fields, menus and selections are defined as "updatable".
This is a necessary prerequesite in order to use the
workflow functionality on a location with a snapshot database.
Presently, the following limitations apply for
the workflow in replicated environments: A prerequesite for the operation of the business
service is a correct configuration of the database for the replication.
|
|
Changes for the business service: In the file tpl_ABS_env.ini in the directory <ep_root>\axalant\ini the following changes have to be made: |
|
![]() |
In the module [Adapter4Objectwarehouse]
the following entries have to be made: [Adapter4Objectwarehouse] (...) DB_SRV_ID=<repl_id> ReplSeqStart=1000000001 ReplSeqStop=1999999999 (...) means: existing entries (can be different from customer to customer). |
The replication id is the location identification of a database location.
This means that here the same replication
id as for the appropriate database is entered.
The start and stop values (the values indicated above are only
exemplary - use your own values) of the particular replication environment
have to match each other. In other words, the start and stop values of
the C_ID sequence have to be the same as in the corresponding database.
Intersections between different locations are not allowed! With these settings the workflow is configurated for a replicated environment. |