Pats 0 Systems Management Guide

6.3 Business Objects Software

6.3.1 Crystal Reports XI

All of the standard reports used by PATS run under Crystal Reports XI. Crystal Reports is a rich client application used to design reports. The reports all use the output from Oracle stored procedures in the PATSRPTS schema. Information about the stored procedures themselves, the associated report templates, the folder structure within which the reports are stored, and the configuration of the reports has been previously described in the Database – Oracle chapter, and the Repository and Central Management Console section of this chapter.

6.3.2 WebI Universe Designer XI

The PATS Universe used within the Web Intelligence product for all ad hoc reporting was designed using the Business Objects Enterprise XI Designer tool. The Designer is a rich client application used to define database connections, and to create universes, a meta-layer on data dictionary tables that can be viewed from the Web Intelligence reporting product.

6.3.3 Central Management Console

The Business Objects Enterprise XI Central Management Console is a web based application that is used to configure all of the objects in the BOEXI Repository. This includes all of the objects needed to store and support both standard and ad hoc reports.

6.3.4 InfoView

This is a web based portal that gives end users access to the folder structure and to existing reports in the repository to which they have access (both Crystal Reports and Web Intelligence Reports). It is part of the Business Objects suite. It also allows them to create new Web Intelligence reports, to save them locally, and if they have access, to move them to other locations. In order to maintain single sign-on for end users, users of the PATS application will not use the InfoView product directly. Instead, Web Intelligence and portions of InfoView have been incorporated into PATS and can be launched directly from PATS.

6.3.5 Web Intelligence

Web Intelligence is a web based ad hoc query builder/report generation tool that is part of the Business Objects suite. This allows users to connect to the PATS database and to create queries and simple reports. PATS incorporates access to this tool from within the PATS application.

6.4 Multiple PATS Instances Sharing the Same BOEXI Repository

The HSI has multiple instances of the PATS application sharing the same BOEXI repository. This section describes the setup of the Hines server BOEXI repository at the present time. The future plan for production will be somewhat different. Current plans indicate that the BOEXI repository at Falling Waters will host the production and support data and the repository at Hines will host the training and failover production data.
BOEXI Folder Structure at the HSI

Folder	Sub-Folder
PATS	Ad Hoc PATS Reports Employee Facility Service Section Issue Code National Patient Report of Contact

Folder	Sub-Folder
PATS_Staging	Ad Hoc – Staging PATS Reports – Staging Employee Facility Service Section Issue Code National Patient Report of Contact
PATS_Training	Ad Hoc – Training PATS Reports – Training Employee Facility Service Section Issue Code National Patient Report of Contact

6.4.1 Standard Reports

1. 
   The PATS folder contains all of the sub-folders and objects for the PATS production instance. Two additional folders were created at the same level as PATS—one for the Staging instance of PATS (PATS_Staging) and one for the Training instance (PATS_Training).
   
2. 
   In each of these new top level folders, a new folder was created to hold the standard reports—PATS Reports – Staging and PATS Reports – Training (see diagram above).
   
3. 
   The folder structure and objects in the PATS Reports folder were copied into the two new folders (see diagram above).
   
4. 
   The database connection information for all standard reports in the new staging and training sub-folders was changed using the CMC to connect to the staging (or training) database.
   
5. 
   The gov.va.med.pats.businessobjects.enterprise.properties files for both the staging and training instances of the application were edited. For the training instance:
   

• 
  PatsPublicFolderName was changed from PATS to PATS_Training
  
• 
  PatsCmsFolderName was changed from PATS Reports to PATS Reports – Training
  

6.4.2 Ad Hoc Reports

1. 
   In each of the new top level folders described in step 1 above, PATS_Staging and PATS_Training, a new folder was created to hold the public ad hoc reports, Ad Hoc – Staging and Ad Hoc – Training. (See the diagram above.)
   
2. 
   The PATS Universe was cloned two times under new names for the staging and training accounts (PATS Universe – Training and PATS Universe – Staging).
   
3. 
   The PATS Oracle 10G universe connection was cloned two times under new names for the staging and training accounts (PATS Oracle 10G – Training and PATS Oracle 10G – Staging).
   
4. 
   The new universes for staging and training were edited using the BOEXI Designer tool to use the new universe connections.
   
5. 
   The database connection information for the new universe connection objects was changed using the BOEXI Designer tool, to connect to the staging (or training) database.
   
6. 
   The gov.va.med.pats.businessobjects.enterprise.properties files for both the staging and training instances of the application were edited. For the training instance: UNIVERSE_NAME was changed from PATS Universe to PATS Universe – Training.