OpenEdge Getting Started: Multi-tenancy Overview - Product ...

More documents

Recommendations

Info

Chapter 2: Multi-tenant feature capabilities • Dump database contents — You can dump table or group data in a text format from the console. The console creates a text file that contains the dump data of each table or group you specify. This file has a .d extension and is stored in the work directory you specify. You can dump data either from a shared table, a multi-tenant table, or both. You can also dump data from a group of tenants sharing a table. You can use these .d files to load data into a database. The console creates a separate contents file for each table or group you dump. Note: You must have administrator privileges to dump table and group contents. • Commit and monitor database updates — You can commit updates to the database, either from an uploaded data definition file or as a result of other changes you make. As changes are being saved to the database, the My Dashboard page opens to allow you to monitor the updates’ progress. The page presents a task viewlet that shows the activity as the updates are being applied. • Filter database connections by container — You can view all database connections for all containers, or you can choose which container’s connections you want to view. • Manage domains — You can create and modify a domain for each tenant. • Manage authentication systems — You can view, create, or delete authentication systems. • Establish and manage user and table security settings — While you can create and work with users for a particular tenant, you can also create, edit, and delete users at the database level. You can define and review table and field security for the database users, and you can review a summary that provides details about the database’s security. You can also configure one or more security administrators who have control over authentication and authorization. 44 OpenEdge Getting Started: Multi-tenancy Overview
Database Administration Console • Manage sequence definitions and values — You can manage sequences and sequence values by: – Viewing a list of all sequences in a database. This includes both the sequences enabled for multi-tenancy and those sequences not enabled for multi-tenancy. – Viewing and editing the current values for multi-tenant-enabled sequences for a specific tenant. – Viewing and editing the current values for all tenants of a sequence. – Exporting sequence current values for one tenant, multiple tenants, or all tenants in a multi-tenant database. Note: Full access to a tenant’s sequences functionality requires a database connection for a user associated with either a super tenant or that specific tenant. • Improve database performance — The performance of a multi-tenant database may be improved by using multi-tenant governors: Login Governor (-nGovernor) and Lock Governor (-LGovernor). These governors limit the amount of each individual tenant’s allocation of shared database resources, so that one tenant does not fully control these resources at the expense of all of the other tenants. These governors apply to the default and regular tenants in a multi-tenant database. They do not apply to super-tenants. For more information on managing these governors, see OpenEdge Management and OpenEdge Explorer: Configuring Multi-tenancy. OpenEdge Getting Started: Multi-tenancy Overview 45
Page 1 and 2: ® ® PROGRESS® OPENEDGE® OpenEdg
Page 3 and 4: Contents Preface . . . . . . . . .
Page 5 and 6: Preface This Preface contains the f
Page 7 and 8: Using this manual Preface OpenEdge
Page 9 and 10: Preface { } Small braces are part o
Page 11 and 12: Long syntax descriptions split acro
Page 13 and 14: OpenEdge messages Preface OpenEdge
Page 15 and 16: Preface USE, DATA, OR PROFITS; OR B
Page 17 and 18: Preface (INCLUDING NEGLIGENCE OR OT
Page 19 and 20: Preface SPECIAL, INDIRECT OR CONSEQ
Page 21 and 22: Preface DAMAGES OR ANY DAMAGES WHAT
Page 23 and 24: Preface RESULTING FROM LOSS OF USE,
Page 25 and 26: Preface SPECIAL, EXEMPLARY, OR CONS
Page 27 and 28: Preface ITS CONTRIBUTORS BE LIABLE
Page 29 and 30: Preface modifications, if any, made
Page 31 and 32: Introducing multi-tenancy This chap
Page 33 and 34: What are the advantages of multi-te
Page 35 and 36: How does data access work? How does
Page 37 and 38: How does data access work? Figure 2
Page 39 and 40: How does data access work? The numb
Page 41 and 42: Multi-tenant feature capabilities T
Page 43: Database Administration Console •
Page 47 and 48: Database utilities Database utiliti
Page 49 and 50: Auditing Auditing For multi-tenant
Page 51 and 52: Progress Developer’s studio for O
Page 53 and 54: Multi-tenancy and ABL Support for m
Page 55 and 56: ABL Support If you already have dom
Page 57 and 58: Super-tenant data updates ABL Suppo
Page 59 and 60: ABL Support Groups also have identi
Page 61 and 62: Entity interface members ABL API fo
Page 63 and 64: Multi-tenancy and OpenEdge SQL Open
Page 65 and 66: DBA use cases DBA use cases The fol
Page 67 and 68: Alter a tenant To alter a tenant, r
Page 69 and 70: Super tenant use cases Super tenant
Page 71 and 72: Update rows of a tenant partition S
Page 73 and 74: SQL utility use cases Writing schem
Page 75 and 76: Multi-tenancy documentation map Thi
Page 77 and 78: Glossary of terms This chapter prov
Page 79 and 80: Multi-tenant objects A tenant can b
Page 81 and 82: Table types Tenants Table types Use

OpenEdge Getting Started: Multi-tenancy Overview - Product ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?