Jump to: navigation, search
(Cleaning up highlights for GIM-12328 in Iteration 14)
(Replacing the Cargo query with a template call)
Line 1: Line 1:
−
= Genesys Info Mart Tenant User Schema and Tenant Views =
+
= Genesys Info Mart {{Editgrn_open}}Tenant User Schema and{{Editgrn_close}} Tenant Views =
  
 
<onlyinclude>
 
<onlyinclude>
−
A Genesys-provided script, named <tt>make_gim_view_for_tenant.sql</tt>, is used to create read-only views to access data in the Genesys Info Mart fact and dimension tables.  
+
A Genesys-provided script, named <tt>make_gim_view_for_tenant.sql</tt>, is used to create {{Editgrn_open}}read-only{{Editgrn_close}} views to access data in the Genesys Info Mart fact and dimension tables.  
  
 
The views are created in:
 
The views are created in:
Line 20: Line 20:
 
{{AnchorDiv|TenantUserSchema}}
 
{{AnchorDiv|TenantUserSchema}}
 
==Views in the Tenant User Database Schema==
 
==Views in the Tenant User Database Schema==
−
These views (shown within the Tenant User database schema in [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:InfoMartDBSchema:{{PONYDOCSVERSION}}#TenantViewDiagram|Genesys Info Mart Data Organization and Tenant Views]]) can be used to make data access more specific to the needs of a particular tenant user. The tenant administrator creates these views in separate Tenant User database schemas by using the same <tt>make_gim_view_for_tenant.sql</tt> script.  
+
These views (shown within the Tenant User database schema in [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:InfoMartDBSchema:{{PONYDOCSVERSION}}#TenantViewDiagram|Genesys Info Mart Data Organization and Tenant Views]]) can be used to make data access more specific to the needs of a particular tenant user. The tenant administrator creates these views in {{Editgrn_open}}<strike>a</strike>{{Editgrn_close}} separate Tenant User database schema{{Editgrn_open}}s{{Editgrn_close}} by using the same <tt>make_gim_view_for_tenant.sql</tt> script.  
  
−
Because each tenant’s data is exposed through a different database schema, tenant administrators can control user access to tenant-specific data.
+
{{Editgrn_open}}<font color=red>'''Writer's note:''' The following material was formerly on the [[TenantUserDBSchema|"Tenant User Database Schema"]] page, which will be deleted.</font>{{Editgrn_close}}
 +
 
 +
<strike>In addition to the Genesys Info Mart database schema, Genesys Info Mart supplies a script to create a separate database schema for each tenant, so that each tenant user can access only its tenant’s data.</strike> Because each tenant’s data is exposed through a different database schema, tenant administrators can control user access to tenant-specific data.
 +
 
 +
{{Editgrn_open}}<font color=red>'''Writer's note:''' The following paragraphs are based on material on the Dep Guide [[Documentation:GIM:Dep:GIMDBModifs|"Completing Database Preparation"]] page.</font>{{Editgrn_close}}
  
 
Each Tenant User schema has a view on a single <tt>DATE_TIME</tt> table, so each schema supports a single time zone. To provide reports in multiple time zones, the downstream report developer must use a separate Tenant User schema for each time zone.  
 
Each Tenant User schema has a view on a single <tt>DATE_TIME</tt> table, so each schema supports a single time zone. To provide reports in multiple time zones, the downstream report developer must use a separate Tenant User schema for each time zone.  
  
−
The [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:InfoMartDBSchema:{{PONYDOCSVERSION}}#TenantViewDiagram|Genesys Info Mart Data Organization and Tenant Views]] diagram shows a Tenant User schema that contains table views for only one tenant. However, to simplify deployment of the reporting solution, Genesys Info Mart supports creating table views for more than one tenant in the same Tenant User schema. Therefore, the tenant administrator does not need to create a separate Tenant User schema for each combination of time zone and tenant. Instead, the tenant administrator can include all tenants, or a group of tenants, in a single schema per time zone. For more information, see [[Documentation:GIM:Dep:GIMDBModifs:8.5.0#TenantViews|Creating Read-Only Tenant Views]] in the ''Genesys Info Mart 8.5 Deployment Guide.''
+
The [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:InfoMartDBSchema:{{PONYDOCSVERSION}}#TenantViewDiagram|Genesys Info Mart Data Organization and Tenant Views]] diagram shows a Tenant User schema that contains table views for only one tenant. However, to simplify deployment of the reporting solution, Genesys Info Mart supports creating table views for more than one tenant in the same Tenant User schema. Therefore, the tenant administrator does not need to create a separate Tenant User schema for each combination of time zone and tenant. Instead, the tenant administrator can include all tenants, or a group of tenants, in a single schema per time zone. <span style="background-color:{{{1|#33fcff}}};">For more information, see [[Documentation:GIM:Dep:GIMDBModifs#TenantViews|Creating Read-Only Tenant Views]] in the ''Genesys Info Mart 8.5 Deployment Guide.''</span>
  
 +
{{Editgrn_open}}<font color=red>End of new, DG-based content</font>{{Editgrn_close}}
 +
 
 
Each Tenant User database schema contains:
 
Each Tenant User database schema contains:
 
* Dimension views
 
* Dimension views
 
* Fact views
 
* Fact views
 +
{{Editgrn_open}}<font color=red>End of deleted page content</font>{{Editgrn_close}}
  
 
The structure of the views created in the Tenant User database schema is identical to that of their underlying dimension and fact tables or views in the Genesys Info Mart database schema. For this reason, subject area diagrams and descriptions for the Tenant User views are not provided in this document.
 
The structure of the views created in the Tenant User database schema is identical to that of their underlying dimension and fact tables or views in the Genesys Info Mart database schema. For this reason, subject area diagrams and descriptions for the Tenant User views are not provided in this document.
  
−
A Tenant User database schema contains the following views, as well as additional views that are created for custom user data tables. For internal reasons in the case of some of the [[{{#replace:{{FULLPAGENAME}}|{{#explode:{{FULLPAGENAME}}|:|3}}|InfoMartDBSchema}}#DimensionViews|dimension views]], the Tenant User schema includes views of both the dimension view and its underlying table.
+
A Tenant User database schema contains the following views, as well as additional views that are created for custom user data tables. <span style="background-color:{{{1|#33fcff}}};">For internal reasons in the case of some of the [[{{#replace:{{FULLPAGENAME}}|{{#explode:{{FULLPAGENAME}}|:|3}}|InfoMartDBSchema}}#DimensionViews|dimension views]], the Tenant User schema includes views of both the dimension view and its underlying table.</span>
 +
 
 +
<div><font color=red><span style="background-color:{{{1|#33fcff}}};">'''Writer's note:'''The list is now generated by query and therefore will update automatically going forward. The following tables weren't in the previous hard-coded list:
 +
{{ColumnFormat|content=
 +
* <span style="background-color:{{{1|#33fcff}}};">BGS_*</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">CALLBACK_*</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">CDR_*</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">CHAT_SESSION_*</span>
 +
*<span style="background-color:{{{1|#33fcff}}};"> COBROWSE_*</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">GPM_*</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">GROUP_ANNEX</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">LDR_*</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">POST_CALL_SURVEY_*</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">RESOURCE_ANNEX</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">SDR_*</span>
 +
* <span style="background-color:{{{1|#33fcff}}};">SM_MEDIA_NEUTRAL_STATE_FACT</span>
 +
}}</span></font></div>
  
 
{{ColumnFormat|cols=2|content=
 
{{ColumnFormat|cols=2|content=

Revision as of 14:06, June 5, 2019

Genesys Info Mart Tenant User Schema and Tenant Views

A Genesys-provided script, named make_gim_view_for_tenant.sql, is used to create read-only views to access data in the Genesys Info Mart fact and dimension tables.

The views are created in:

In a multi-tenant environment, the two types of views can be used in combination.

Views in the Genesys Info Mart Database Schema

The purpose of these views (referred to as tenant-specific views in the Genesys Info Mart Data Organization and Tenant Views diagram) is to provide read-only access to data in the Genesys Info Mart database schema for tenant users who are working only with the data for a particular tenant. A separate set of views is created for each particular tenant. When the tenant administrator creates these views by using the make_gim_view_for_tenant.sql script, the script generates the names for created views.

Multi-tenant deployment applications should query Genesys Info Mart data by using these read-only views, instead of querying the tables and views that reside in the Genesys Info Mart database schema.

To restrict data access in single-tenant deployments, use the same script to create a similar set of read-only views. The data organization for the Tenant User that is shown in the Genesys Info Mart Data Organization and Tenant Views diagram is applicable to single-tenant deployments in which data-access views are created.

Views in the Tenant User Database Schema

These views (shown within the Tenant User database schema in Genesys Info Mart Data Organization and Tenant Views) can be used to make data access more specific to the needs of a particular tenant user. The tenant administrator creates these views in a separate Tenant User database schemas by using the same make_gim_view_for_tenant.sql script.

Writer's note: The following material was formerly on the "Tenant User Database Schema" page, which will be deleted.

In addition to the Genesys Info Mart database schema, Genesys Info Mart supplies a script to create a separate database schema for each tenant, so that each tenant user can access only its tenant’s data. Because each tenant’s data is exposed through a different database schema, tenant administrators can control user access to tenant-specific data.

Writer's note: The following paragraphs are based on material on the Dep Guide "Completing Database Preparation" page.

Each Tenant User schema has a view on a single DATE_TIME table, so each schema supports a single time zone. To provide reports in multiple time zones, the downstream report developer must use a separate Tenant User schema for each time zone.

The Genesys Info Mart Data Organization and Tenant Views diagram shows a Tenant User schema that contains table views for only one tenant. However, to simplify deployment of the reporting solution, Genesys Info Mart supports creating table views for more than one tenant in the same Tenant User schema. Therefore, the tenant administrator does not need to create a separate Tenant User schema for each combination of time zone and tenant. Instead, the tenant administrator can include all tenants, or a group of tenants, in a single schema per time zone. For more information, see Creating Read-Only Tenant Views in the Genesys Info Mart 8.5 Deployment Guide.

End of new, DG-based content

Each Tenant User database schema contains:

  • Dimension views
  • Fact views

End of deleted page content

The structure of the views created in the Tenant User database schema is identical to that of their underlying dimension and fact tables or views in the Genesys Info Mart database schema. For this reason, subject area diagrams and descriptions for the Tenant User views are not provided in this document.

A Tenant User database schema contains the following views, as well as additional views that are created for custom user data tables. For internal reasons in the case of some of the dimension views, the Tenant User schema includes views of both the dimension view and its underlying table.

Writer's note:The list is now generated by query and therefore will update automatically going forward. The following tables weren't in the previous hard-coded list:
  • BGS_*
  • CALLBACK_*
  • CDR_*
  • CHAT_SESSION_*
  • COBROWSE_*
  • GPM_*
  • GROUP_ANNEX
  • LDR_*
  • POST_CALL_SURVEY_*
  • RESOURCE_ANNEX
  • SDR_*
  • SM_MEDIA_NEUTRAL_STATE_FACT


  • CALLING_LIST_TO_CAMP_FACT_
  • GROUP_TO_CAMPAIGN_FACT_
  • PLACE_GROUP_FACT_
  • RESOURCE_GROUP_FACT_
  • RESOURCE_SKILL_FACT_
Comments or questions about this documentation? Contact us for support!