myTC Account Database.

Environments

• Development: MTOAD.WORLD

• Testing: PREACC_CA.WORLD

• Acceptance: MTOAA.WORLD

• Production: MTOAP.WORLD 

Accounts

• Owner: MTOA

• Internal User : MTOA_USER

• MTOA API : MTOA_API

• External Protected ‘A’ : MTOA_EXTA

• External Protected ‘B’ : MTOA_EXTB (not currently used) 

Connection to Legacy Application Databases

As per DMI/DBA recommendation, it is advised to create a myTC Account in the legacy database to allow myTC Account interactions, instead of using the generic AAAA_user account.

For example, for the myTC Account ACP/AQPE Monitor Report service which interacts with the FTAE legacy database/application, a MTOA_FTAE account was created to differentiate the access to FTAE between a FTAE application USER and a myTC Account user.

Conceptual Model

Open

Stakeholder Management

Follows DMI (Data Management) corporate standard:

• Stakeholder

  • Internal

  • External

  • Organization

  • Application
    
    

• Coordinate

  • Mail

  • Email

  • Telephone

  • GIS

Authentication Management

• Supports Internal user accounts with Active directory and/or PKI

• Supports External user accounts with MBUN generated from GART or a GC Key partner

• Application API Keys

• Email confirmation codes

Authorization Management

• Associates an account to a service and a role

• Optionally associated to show representation to another stakeholder, either an organization or another individual; 

Service Management 

• Defines the services implemented in myTC Account , and which groups they belong

• Defines the service groups which are displayed in the My Services page

Notification Management

• Defines notification templates to be sent by email at different places in the service’s workflow

Service Request Management

• Manages the service requests made by authorized stakeholders

• Manages the temporary storing of paused reporting processes

• Manages the request transactions between myTC Account and their related business/legacy systems