Repository tables

In BusinessObjects 6.5 Repository have 57 tables.


Security Domain tables 25


1. OBJ_M_ACTOR
2. OBJ_M_USRATTR
3. OBJ_M_DOCCST
4. OBJ_M_GENPAR
5. OBJ_M_MAGICID
6. OBJ_M_RESLINK
7. OBJ_M_UNIVCST
8. OBJ_M_UNIVSLC
9. OBJ_M_ACTORDOC
10. OBJ_M_DOCUMENTS
11. OBJ_M_UNIVERSES
12. OBJ_M_ACTORLINK
13. OBJ_M_TIMESTAMP
14.OBJ_M_UNIVDBCST
15.OBJ_M_CONNECTION
16.DS_USER_LIST
17.OBJ_M_REPOSITORY
18.OBJ_M_CATEG
19.OBJ_M_CONNECTDATA
20.OBJ_M_OBJSLICE
21.OBJ_M_RESERVATION
22.DS_PENDING_JOB
23.OBJ_M_DOCCATEG
24.OBJ_M_DOCAT
25.OBJ_M_DOCATVAR


Document Domain have 1 tables

1.OBJ_X_DOCUMENTS

Universe Domain have 31 tables

1. UNV_JOIN
2. UNV_AUDIT
3. UNV_CLASS
4. UNV_RELATIONS
5. UNV_DIM_OBJ
6. UNV_OBJECT
7. UNV_OBJ_TAB
8. UNV_TAB_OBJ
9. UNV_CONTEXT
10. UNV_CTX_JOIN
11. UNV_TAB_PROP
12. UNV_JOIN_DATA
13. UNV_PROP_DATA
14. UNV_PROPERTY
15. UNV_UNIVERSE
16. UNV_CLASS_DATA
17. UNV_DIMENSION
18. UNV_PROP_TAB
19. UNV_OBJECT_DATA
20. UNV_CONTEXT_DATA
21. UNV_JOINCONTENT
22. UNV_UNIVERSE_DATA
23. UNV_OBJCONTENT
24. UNV_TABLE
25. UNV_TABLE_DATA
26. UNV_OBJECT_KEY
27. UNV_JOIN_OBJECT
28. UNV_COLUMNS
29. UNV_COLUMN_DATA
30. UNV_OBJ_COLUMN
31. UNV_X_UNIVERSES

Read more »

Business Objects Repository Basics

• One security domain
• Multiple document and universe domains allowed
• All domains may be located on a single database (monolithic)
• Document and universe domains may be located across different databases (distributed)

Key required to access the repository

• Can be located on the users workstation (LocData) or in ashared folder (ShData)
  

- Pdac.lsi or pdac.ssi defines personal connections to the database
- Sdac.lsi or Sdac.ssi defines shared connections to the database
- All other .lsi and .ssi files are user login files. These files contain the security
information needed to run Business Object when not connected to the repository

• Security domain maps actors to resources via resource links
  

-Actors can be a user or a group
-Resources include documents, universes and domains
- Access to a resource may be linked directly to the user or inherited from further up the security hierarchy

Read more »