This documentation supports the 19.08 version of Remedy and applies only to the on-premises deployment model.

To view an earlier version, select the version from the Product version menu.


Preparing to install BMC Remedy Smart Reporting

If you have not already done so, plan the BMC Remedy Smart Reporting deployment.

Best Practice

We recommend that you do not install BMC Remedy Smart Reporting and BMC Remedy AR System Server on the same computer.

Note

You must perform the user onboarding process from BMC Remedy AR System to BMC Remedy Smart Reporting only after BMC Remedy ITSM installation. 

Before you begin

Before you perform the installation, consider the following:

  • Ensure that the machine on which you are installing this component meets the following requirements:
    • Java version 8 update 45 or later is installed

    • Terminal server configuration is completed
  • Ensure that your firewall does not block the following ports:
    • Default port 8181 used by Smart Reporting
    • Default SQL Server port 1433  
    • Default Oracle Server port 1521

    • Default PostgreSQL port 5432

To configure the terminal server (Windows only)

  1. Go to Start > Run.

  2. In the Run dialog box, enter gpedit.msc, and press Enter.
  3. Choose Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary Folders.
  4. Enable the following options:
    1. Do not Delete temp folder on Exit
    2. Do not use temp folder per session
  5. Restart the system.
  6. If the settings are not enabled:
    1. Choose Start > Run.
    2. In the Run dialog box, enter regedit and press Enter.
    3. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEMCurrentControlSet\Control\Terminal Server and update the PerSessionTempDir and DeleteTempDir OnExit options to 0.
    4. Restart the system.

Preparing the AR System server for installing Smart Reporting

Consider the following information perform the relevant actions on the AR System server that is connected to Smart Reporting:

  1. When installing the AR System server, ensure that the AR Server is connected to the Remedy production environment database and not the replicated database. 

  2. After installing the AR System server, you must apply the AR license key by connecting to the production environment database which is in read/write mode. 

  3. From the Remedy production environment database, delete the following references of AR System server: 

    Database tableInfo to be deleted
    servgrp_applic
    select * from servgrp_applic;
    delete from servgrp_applic where serverName = 'name of the AR Server to be consumed by Smart Reporting'
    servgrp_board
    select * from servgrp_board;
    delete from servgrp_board where serverName = 'name of the AR Server to be consumed by Smart Reporting'
    servgrp_config
    select * from servgrp_config;
    delete from servgrp_config where serverName = ‘name of the AR Server to be consumed by Smart Reporting’;
    servgrp_ftslic
    select * from servgrp_ftslic;
    delete from servgrp_ftslic where serverName = ‘name of the AR Server to be consumed by Smart Reporting’;
    servgrp_resources
    select * from servgrp_resources;
    delete from servgrp_resources where serverName = ‘name of the AR Server to be consumed by Smart Reporting’
    servgrp_userlic
    select * from servgrp_userlic;
    delete from servgrp_userlic where serverName = ‘name of the AR Server to be consumed by Smart Reporting’
  4. From the Remedy production environment AR System Server Group Operation Ranking form, do not remove any entries referencing the AR System server consumed by Smart Reporting.

  5. Update the following information in the ar.cfg or ar.conf file:

    Modify the following parameters in
    ar.cfg or ar.conf file

    Disable-Alerts: T

    Disable-Archive: T

    Disable-Escalations: T 

    Full-Text-Mode: Disabled 

    Full-Text-Disable-Indexing: T

    Full-Text-Disable-Searching: T

  6. Update the following information in the armonitor.cfg or armonitor.conf file:

    Comment out the following parameters in
    armonitor.cfg or armonitor.conf file

    FTS secondary plugin

    Email Engine

    Flashboard

    Carte server

    Approval

    DSO

  7. Shutdown the AR server and connect it to the replicated database.  Below are the parameters that needs to change to reflect the Replicated SR database in the ar.cfg/ar.conf file

    1. Db-name: ARSystem
    • Db-user: ARAdmin
    • Db-Host-Name: <Replicated_DB_server_name>
  8. Start the AR Server.
    In the arerror.log, If you see the following error message, ignore it:
    Failed to update database "ARSystem" because the database is read-only

Preparing for installation of the Smart Reporting database on Oracle

You must create a database user prior to Smart Reporting installation.

To create a database user (Oracle)

  1. Login to the Oracle db as an Administrator. 
  2. In the SQL prompt, execute the following commands:

    SQL> create tablespace reporting datafile 'reporting' size 500M reuse autoextend on
    
    SQL> create user repadmin identified by RP#Admin# default tablespace reporting;
    
    SQL > grant unlimited tablespace to repadmin;
    
    SQL> create role RRole not identified;
    
    SQL > grant CREATE SESSION, alter session, create cluster, create sequence,create trigger, query rewrite, create synonym, create table, create view, create procedure to RRole;
    
    SQL> grant RRole to repadmin;

    The query rewrite parameter is required only if you use materialized views. The Remedy AR System does not use materialized views in its schema.

Preparing for installation of the BMC Remedy Smart Reporting database on Microsoft SQL Server

When running the Smart Reporting installer, you encounter the following panel:

 

The following table lists the possible combinations that result from the selections you make on the panel.

DB creation preferenceUserPre-requisitesSQL Server AuthenticationWindows Authentication
New DBNew userInstaller creates the database and the user. DBA credentials are required.SupportedNot supported
Existing DBExisting userValid DB and user must be available. DB must be clean. DBA credentials are not required.SupportedSupported
New DBExisting userInstaller creates the database. DBA credentials are required to create a new DB from the installer. Valid user must be available.SupportedSupported
Existing DBNew userValid DB must be available. Installer creates a new user. DBA credentials are required. SupportedNot supported

To add a pre-created database and user

  1. Login to the MS SQL server database, as an Administrator.
  2. Create the new database: 
    1. In the Object List right-click Databases
    2. Click New Databases
    3. Enter the database name. 
    4. Click OK. The database will get created.

    Or,
    Run the following command in the master DB query panel: 

    create database < database name>

Create a user and give permissions for the new database that you created. 

  1. In the Object List click Security > Logins.
  2. Right-click Logins and click New Login.
  3. Enter the details of the new user.
  4. Right-click the newly created user, under Owned Schemas and Database role membership, select db_owner .
  5. Click OK

Or,
Right-click the newly created database, click New Query, and run the following command:

# Creates the login <username> with password '<password>'.
CREATE LOGIN <username> 
WITH PASSWORD = '<password>';
GO
# Creates a database user for the login created above.
CREATE USER <username> FOR LOGIN <username>;
GO

Preparing for installation of the Smart Reporting database on PostgreSQL

The process of preparing for installation of the Smart Reporting database on PostgreSQL involves creating a login role and database for Smart Reporting and then updating the text file for silent installation of Smart Reporting. See Running the installer in silent mode.

Note

When you perform a fresh installation with a new database or with a new user option for PostgreSQL database, all the database objects such as tables and views are created in a public schema.

  1. Install pgAdmin.
  2. Log in to the pgAdmin console as an administrator and connect to your database instance.
  3. Create a login role and assign the required permissions:
    1. In the Object browser pane, expand the database server.
    2. Right-click Login Roles and select New Login Role.
      The New Login Role dialog box is displayed.
    3. In the Role Name field, provide a name for the role. For example, sradmin.
    4. Click the Definition tab and specify a password for the role.
    5. Click the Role privileges tab and assign the following privileges:
    6. Click OK.
  4. Create a database and select the owner:
    1. Right-click Databases and select New Database.
      The New Database window is displayed.
    2. In the Name field, provide a name for the database. For example, srdb.
    3. From the Owner list, select the role that you created in step 3.
    4. Click OK.
  5. Update the following parameters in the Options.txt file for silent installation:

    -J REPORTING_DB_TYPE=POSTGRESQL

    -J REPORTING_DB_OPTION=EXISTING_DB

    -J REPORTING_USER_OPTION=EXISTING_USER

    -J REPORTING_DB_HOST=<DB_HOSTNAME>

    -J REPORTING_DB_PORT=<DB_PORT>

    -J REPORTING_DB_NAME=<DB_NAME>

    -J REPORTING_DB_USER=<ROLE_NAME>

    -J REPORTING_DB_USER_PASSWORD=<ROLE_PASSWORD>

    -J REPORTING_DB_USER_CONFIRM_PASSWORD=<ROLE_PASSWORD>

    -J REPORTING_DB_ADMIN_USER=<DB ADMIN USER>

    -J REPORTING_DB_ADMIN_USER_PASSWORD=<DB ADMIN USER PASSWORD>

Related topics

Installing BMC Remedy Smart Reporting

Hardware requirements

Was this page helpful? Yes No Submitting... Thank you

Comments