TVI EBO

Modified on Monday, 29 October 2012 11:33 AM by Administrator — Categorized as: Uncategorized

Tips for using the EBO

These are the five layers of security that were set up for EOC which was recently implemented in Production in order to use the TVI EBO to maintain vendor accounts owned by this application:
  1. An entry in an XML file (https://dotscosvnp1.co.dot.state.fl.us/svn/FEL2/trunk/FDOT.Enterprise.BusinessObjects.Vendor/Vendor/TVIApplications.xml) embedded in the Enterprise Library assembly containing the application ID (or acronym) and base URL as well server names on each environment where it will be used (FEL team)
  2. Generic mainframe user id managed through DBConnect using the generic user id syntax and secured by URL (DBAT)
  3. An application profile in the TVI database (stored in tables TVIT100_SYS_OWN and TVIT101_ACCT_PUR). (TVI Admin - Shannon Lanier)
  4. A resource profile (e.g. EOCTVIPF) associated to the generic user id (same as in #2). (Security)
  5. Granting the necessary database authorities to the generic user id on TVI tables updated by the EBO. (Security)

According to Warren, #5 is unnecessary since static plans for the code generated in cool:gen wrapped in the TVI EBO only need execute authority, which is basically what #4 does, in order to update the underlying TVI tables. Since #5 was done before #4 for EOC, we’re not planning to undo #5 any time soon to avoid any unanticipated impact.