Importing out-of-the-box content
Import process overview
Content is the core of Remedy Smart Reporting, which provides various reporting options for data from the Remedy applications. During the installation of individual applications such as Atrium CMDB or HR Case Management, fresh and upgrade content is pushed to a Remedy AR System form. The content import process imports the content for each application from the form to Remedy Smart Reporting.
If you install or upgrade an application after importing the content for the first time, you can manually trigger the content import process again. The process imports content only for newly installed or upgraded applications, not for applications for which you imported content earlier. For example, suppose you are upgrading Remedy applications from version 19.02.00 to version 19.11.00. In version 19.02.00, you had Atrium CMDB and Remedy ITSM. While upgrading to version 19.11.00, you also installed a new application, HR Case Management. When you run the content import process, it imports fresh content for the HR Case Management application and upgrades the content for Atrium CMDB and Remedy ITSM.
If you upgrade an application and run the content import process, the process overwrites the existing content that was imported during the previous installation. Similarly, if you directly customize out-of-the-box content and run the import process, the process overwrites customized content.
Consider the following examples:
Example for upgraded content | Report_A was imported earlier as fresh content for Remedy ITSM 19.02.00. Now, you have upgraded Remedy ITSM to version 19.11.00. With the upgrade, Report_A was updated as Report_A_1902. When you run the content import process after the upgrade, the process overwrites Report_A with the new Report_A_1911. |
---|---|
Example for customized content | In Remedy Smart Reporting 19.02.00, you customized an out-of-the-box report, Report_B, and saved a copy as Report_B_Custom. You upgraded Remedy applications to version 19.11.00 and ran the content import process after the upgrade was complete. In version 19.02.00, out-of-the-box Report_B was updated. After you run the content import process for upgraded content, the process overwrites Report_B from version 19.02.00 with Report_B from version 19.11.00. The process does not update Report_B_Custom. You must manually reconcile any changes to Report_B_Custom after upgrading. |
Before you begin
- If secured login (https) is enabled on the Remedy Smart Reporting Tomcat server, configure the onboarding and content import link for secured login.
- Onboard users in BMC Remedy Smart Reporting.
To import content to Remedy Smart Reporting, ensure that you are a member of:
- The AR Admin group
or - The Struct Admin group and Smart Reporting Admin group—You must belong to both these groups to be able to import content.
- The AR Admin group
- In multicompany onboarding, to share common content across multiple tenants at the same time, you must be a member of the shared organization. For more information, see Synchronizing-common-content-across-multiple-tenants and Organizations-in-a-multitenancy-environment.
To import out-of-the-box reporting content
- Log in to the Remedy Smart Reporting Administration Console as a Smart Reporting super administrator (siadmin).
The path to the console is http://RemedySmartReportingServerHostName:port/AdminConsole/#. - Select Services > Import Content.
- Select the customer for whom you want to import the reporting content, and click Next.
- Follow the import content wizard to complete the content import.
Select the product name and version (current and later versions only) for which you want to import content, and click Add. The following products are available:
- BMC CMDB
- Remedy ITSM
- BMC Service Request Management
- BMC Service Level Management
- Smart IT
Repeat this step for each product and version you want to import content for.
- Validate your selection, and click Start Import.
After completion, the process displays the content import result. The import content wizard displays the product names for which the import process has passed or failed. For additional information about any failures, refer to the sr.timeStamp.log file. You can fix the issues and re-import the content for the applications for which the import process has failed.