Architecture Diagram

TeamWork™, Database Change Management, Architecture Diagram




  1. User Workstation
    TeamWork offers multiple facilities and tools suitable for different needs:
    1. TeamWork Management Studio – Used for setting and configuring TeamWork, performing change management tasks and generating reports
    2. TeamWork Sidebar – Used for day-to-day change management tasks
    3. TeamWork VS2008 Add-in – Used for day-to-day change management tasks
    4. TeamWork Deployment Manager – Used for determining what will be deployed, dealing with conflicts, and creating an autonomous package for deployment
  2. Application Server
    TeamWork services are installed on an application server. The server can be a virtual machine and doesn't have to be dedicated for TeamWork only.
  3. Database
    1. TeamWork repository holds all versioning information and development assets. It is created during server setup process and doesn’t require setup of a dedicated Oracle database (it can be placed on any existing Oracle database, which may continue and serve other organizational needs as well).
    2. On every Oracle database instance which has at least one schema, managed by TeamWork, another small TeamWork footprint is created (this is a completely standard Oracle schema, and requires no agent or other services to run). No changes are done to other user schemas.
By implementing the dbMaestro solution, We can finally take control of our database. By Integrating the application alongside our source control and continuous integration paradigm, We are able to deploy our application within minutes.
Mr. Jonathan Bar-Sela, Development Manager, Clalbit systems



Next Steps

View a Demo
Request a Live Demo
Request a Test Drive
Download White Papers
Download TeamWork
Request a Quote
Please Contact Me