 |
TRFC (TransReplicator Reload Facilitation Coordinator)
TRFC is a web-based portal supporting the workflow associated with the database reloads.
This product integrates with the
TransReplicator Navigator and Loader modules. This is typically a manually-intensive, time consuming process that requires the coordination of developers, DBAs and project managers.
TRFC automates this process into a user-defined workflow that coordinates the reload process with all of the resources involved thus helping to minimize the overall time and effort required to support a database reload.
The TRFC client administrator begins by defining each of the databases, users and reload processes (upload-able from the user's workstation) into the portal's database.
Users are then associated with specific databases and then granted access roles that determine the overall workflow of the reload process.
Once this simple setup process is complete users can begin to use the system.
Typically the workflow begins with a request for a database reload (e.g., because the data is out of date or because the data has become unusable...) from a developer or tester.
If so configured, one or more power-users or managers may be required to approve the request before the request can be scheduled.
Once approved the request is scheduled to be performed either manually, by the DBA, or in an automated fashion, with TransReplicator running in a batch mode and interacting with the TRFC portal using industry standard Web Services.
If a load is performed manually then the DBA will be able to specify the status of the load (e.g., Success, Failure with reason).
Running in an automated manner, the DBA is only
needed to configure the reload process...after that,
the developers and tester can perform their own
reloads as needed.
All communication with users is performed via emails, which contain links when necessary to allow their recipients to interact with the workflow process (e.g., Approvers will receive emails with links to the portal that allow them to approve or reject requests, etc...).
Users can always view the status of past and scheduled reloads.
|
|
|