About the Reports Server feature

The Reports Server feature is highly recommended for agencies with heavy report usage or large amounts of data that may affect performance during times of critical functionality. The feature allows agencies to implement a dedicated reports instance that provides users with access to reports and reporting tools while reducing the impact to overall system performance.

The Reports Server feature is versatile. It can be set up to run reports against the production database. To achieve even greater performance improvements, the feature can be set up to run reports against a replicated database. The Reports Server feature does not require a license, can be used with or without the Reports Module, and can be implemented without assistance from UKG.

Warning: Agencies must provide hardware for the dedicated reports instance and replicated database, and meet the minimum requirements based on their existing infrastructure. For details, refer to the UKG GovTA System Installation and Requirements Guide, "Section 3. Minimum Hardware Sizing Requirements." Agencies are responsible for replicating the database.

Terminology

For clarification, here's a general definition of terms as they are used throughout this topic.

Dedicated reports instance. Refers to a separate UKG GovTA application instance. The reports instance can point to the production database or a replicated database.
Replicated database. Refers to a copy of the production database. Agencies are responsible for replicating the database.
Production database. Refers to the database that supports time and attendance data and payroll processing on the UKG GovTA production server.
Production server. Refers to the UKG GovTA application server that supports payroll processing against an active production database.

Configuration scenarios and replication

Note: For details about setting up the reports server, refer to the UKG GovTA System Requirements and Installation Guide available from UKG Community or your UKG Support Representative.

These configuration scenarios are supported:

Scenario A: In this scenario, the agency implements the UKG GovTA production server and production database on one server and a dedicated reports instance and replicated database on another server. All reports run on the reports instance against the replicated database. UKG recommends this scenario.

Scenario B: In this scenario, the agency implements the UKG GovTA application and reporting application on the same server. A replicated database is on a separate server. Reports run on the application server against the replicated database.

Agencies are responsible for database replication, including timing and frequency. Database replication procedures are available from Oracle and PostgreSQL. The entire UKG GovTA database must be replicated (not select tables.)

About the production server

The UKG GovTA production server supports current payroll processing against an active production database. This means that users can enter, update, save, and delete time and attendance data. Depending on how agencies implement the system, the production server may limit user access to historical data.

If a dedicated reports instance is implemented, users do not work with reports on the production instance. The only option under the Reports section on the main menu is the Reports Server (Opens in New Window) link. Users click the link to go to the UKG GovTA reports instance log in page. Alternatively, users may launch the reports instance URL from the browser and log in.

About the reports instance

The reports instance can be set up to access the production database or a replicated database. Depending on the agency’s implementation, a read-only schema may be created. In this case, users will not be able to save changes on the reports instance. Users may run standard reports, and, if the Reports Module is implemented, users may create, publish and share ad hoc reports. Each agency determines how many years of data are available and how often the reports instance is updated with data from the production server if a replicated database is implemented.

Note: The reports server does not include the tiles functionality. Consequently, the Home page does not display tiles when user log in.

Reports server authentication

Users log on to the UKG GovTA reports instance using the same authentication method as the UKG GovTA production instance. Some examples are provided below:

If SSO is implemented on the UKG GovTA production instance, the user is logged on to the reports instance via SSO.
If MFA is enabled on the production instance, the user must use MFA authentication to log on to the reports instance.
If standard UKG GovTA database authentication is implemented on the production instance, the user must log into the reports instance using UKG GovTA database authentication.

Reports server and SAML 2.0

If SAML 2.0 is enabled (Passwords & Authentication > SAML 2 Configuration) and the Reports Server feature is also enabled, the SAML 2 Configuration page includes these fields:

External Report Server URL Prefix. This value will be populated from Report Server Management > Reports Server URL. The value is read-only.
Report Server SP Entity ID. This value is read-only. The Download Report Server metadata option is available for downloading the metadata file for the report server.