Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Log & Event Manager (LEM) > Create LEM Custom Reports Using Crystal Reports

Create LEM Custom Reports Using Crystal Reports

 

Overview

This article describes how to create custom Reports for LEM 5.6 or later. This process will allow you to change the design and layout of your reports as you see fit and can also be used to migrate LEM 5.5 Reports to later LEM versions.

 

Alternate support article for DB Connection: Change the database connection

https://support.solarwinds.com/Succe...ase_connection

Environment

The following applications must be installed:

  • Java Runtime Environment (most current)
  • Crystal Reports 11 Runtime Engine (is installed as part of LEM deployment)
  • Crystal Reports XI R2 or 13

Resolution

If you are using Crystal Reports 13: Crystal Reports 13 has some new features that the Crystal Reports 11 Runtime Engine (which LEM uses) does not support. The degree of failure varies, depending on the features used. Some reports may run with warnings. Others may not be able to run.

In the latest LEM release, we migrated from a third party database software to an in-house database. Due to this change, there are several steps that need to be performed:

  • It is recommened to realign the report against the new schema since there have been changes in the schema. Using the new schema involves changing the Database Connection in the Crystal Reports IDE.
  • Using a customized database may present the following limitations:
    • All GroupBy operations have to be carried out by the Crystal Report and should NOT be delegated to the database server.
    • None of the stored procedures or SQL functions should be used while designing the SQL Query.
  • The following tables should not be joined with other alert tables in the same query as they do not depend on Lucius for their data. For example, a GenericAlert table should not be joined with an EventSummaryTable in the same query since EventSummary and GenericAlert have different data sources.
  • Eventsummary
  • Alertdatetimerange
  • Alertdailykeys
  • Internalusers
  • Internalrules
  • rulesubscriptions
  • If the existing Report refers to the genericAlert table {INSERTIONTIME}, this needs to be changed to {MANAGERTIME} when creating the new custom Report.

Guidelines when installing Crystal Reports XI R2

  1. Our base install of the CR Engine does not contain any java or JDBC connections. The java files must be pulled from the directories of a full Crystal Reports XI install.
  2. During installation of Crystal Reports XI R2, choose Custom install or the JDBC dll files will not be installed. (crdb_jdbc.dll & crdb_jdbc_res_en.dll) 
  3. Within the Select Features dialog, expand Data Access; Locate JDBC Data Driver and select Will be installed on local hard drive from the drop down menu.
  1. Install the Solarwinds LEM Report Console.
  • Get the lem_lucius.jar and the lem_util.jar files from the installed location (e.g. "C:\Program Files (x86)\SolarWinds Log and Event Manager Reports")
  • Copy the LEM Lucius jar file into C:\Program Files (x86)\Common Files\Business Objects\3.0\java\lib\external
  • The lem_lucius.jar file contains the files for running the HSQL DB and it's associated JDBC connections
  • There are a few modifications we made to the HSQL code which are required for the Crytals JDBC connection to LEM
  1. Update the CRConfig.xml
  1. Locate the CRConfig.xml file at "C:\Program Files (x86)\Common Files\Business Objects\3.0\java". (source CRConfig.xml).
  2. When a Crystal IDE is installed, an additional CRConfig.xml gets installed. The location of this file may vary from version to version of the CR.
    1. No Change is needed for CR R1.
    2. In case of CR R2, the file should be available at "C:\Program Files\Business Objects\Common\3.x\java"
    3. In case of CR 2013, the file should be available at "C:\Program Files\SAP Business Objects\Common\3.5\java".
    4. We recommend searching the "C:\Program Files (x86)\"  and "C:\Program Files\" for CRConfig.xml (destination CRConfig.xml)
    5. The following changes needs to done on the destination CRConfig.xml:
      1. Replace tag <JavaDir> in destination with that in the source.
      2. Prepend"${SWProgramFiles}lem_util.jar;${SWProgramFiles}lem_lucius.jar;${SWProgramFiles}lem_commons.jar;${SWProgramFiles}slf4j-api-1.7.5.jar;" to the value in the classpath tag.
      3. When the changes have been made to LEM 6.0.1, they should look like the following:
        custom report jar.jpg

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any. 

Last modified
12:31, 3 Jul 2017

Tags

Classifications

Public