Table of Contents

Search

  1. Preface
  2. Introduction
  3. Accessing Data Archive
  4. Working with Data Archive
  5. Scheduling Jobs
  6. Viewing the Dashboard
  7. Creating Data Archive Projects
  8. Salesforce Archiving
  9. SAP Application Retirement
  10. Creating Retirement Archive Projects
  11. Integrated Validation for Archive and Retirement Projects
  12. Retention Management
  13. External Attachments
  14. Data Archive Restore
  15. Data Discovery Portal
  16. Data Visualization
  17. Data Privacy
  18. Oracle E-Business Suite Retirement Reports
  19. JD Edwards Enterprise Retirement Reports
  20. Oracle PeopleSoft Applications Retirement Reports
  21. Language Settings
  22. Appendix A: Data Vault Datatype Conversion
  23. Appendix B: Special Characters in Data Vault
  24. Appendix C: SAP Application Retirement Supported HR Clusters
  25. Appendix D: Glossary

Report Migration

Report Migration

In addition to an application, you can also migrate Data Visualization reports created on one environment, for example a pre-production environment, to another environment, for example a production environment.
There are two types of resources (reports and catalogs) that you can migrate:
Published Resources
Published resources are managed entirely in the JReport Server and support all of the actions available on the server. You can delete published resources from Data Archive and also the Jinfonet user interface. Custom reports created with Data Visualization Designer or from the Data Archive user interface are examples of published resources.
Real Path Resources
Real path resources are managed in both the server and OS. In the server, when you access a resource node which is linked with a real path, the local resources in the real path are loaded to the node and displayed together with other server resources, including the published resources, in the node. You cannot delete the real path resources directly from the Data Archive or Jinfonet user interface, but you can remove the resources from the local disk. SAP reports and reports within the Application Retirement for Healthcare accelerator are examples of real path resources.
Depending on whether the reports you want to migrate are real path resources or published resources, complete the following tasks to migrate the reports:

Migrating Published Resources

  1. Download the reports and catalog from the source environment.
  2. Edit the catalog connection details in the downloaded catalog.
  3. Edit the catalog table section.
  4. Edit the schema name in any "Imported SQLs."
  5. Rename the existing catalog.
  6. Create a report folder and publish the resource in the target JReport server.
  7. Run a migrated report from Data Archive.

Migrating Real Path Resources

  1. Download the reports and catalog from the source environment.
  2. Edit the catalog connection details in the downloaded catalog.
  3. Create a report folder and publish the resource in the target JReport server.
  4. Create a report folder in the target file system.
  5. Copy the reports and catalog from the source to the target file system.
  6. Map the folder deployed on the JReports server to the target file system.
  7. Select the migrated target connection in the Patient Archives.

0 COMMENTS

We’d like to hear from you!