SolutionPack for Storage Compliance

Table of Contents

Overview

This article explains how to install and configure the SolutionPack for Storage Compliance.

The SolutionPack for Storage Compliance allows users to manage compliance policies and rules and perform ESM matching. It also generates breach, track configuration changes, and policy reports. This enables the identification of any deviation from configuration best practices, including items that do not comply with the EMC ViPR SRM Release Notes. The reports can be found in Dashboard Operations Storage Compliance. The Policy & Rule Management and ESM management screen can be launched from the Administration screen.

This article applies to EMC ViPR SRM version 3.5.1.
report screen

SolutionPack for Storage Compliance

Back to Top

Technical specifications

SolutionPack version

Compatible ViPR SRM version

Main reports in the User Interface section of the console

Back to Top

Installing the SolutionPack

Before you begin

Procedure

  1. Log in.
  2. Click Administration.
  3. Click Centralized Management.
  4. Click SolutionPacks.
  5. Select SolutionPack Center.
  6. Select the SolutionPack for Storage Compliance in the Browse and Install SolutionPacks screen.
  7. Click Install.
    The steps below assume a typical four VM deployment.
  8. Type the instance name.
  9. For compliance notifications, select the appropriate VMs. For example, for Compliance Notifications and Compliance Backend, select the Primary Backend VM. For Compliance Reports and Compliance Frontend, select the Frontend VM.
  10. Click Next.
  11. Select an item in the Breach Notification Details field of the Compliance Notifications window. If you select Add a new Breach Notification Details, select an instance to receive breach notifications.
  12. Click Next.
  13. Select a configuration for Property Store.
    Reuse the answer if any other SolutionPack is using property store configuration. Otherwise create a new property store configuration by selecting Add a new property store configuration. Provide the Frontend hostname as the Webservice host name. Type 58080 as the Webservice port number. Provide the web service username and password.
  14. Select a configuration for Breach Notification Details.
    Reuse the answers if another solution pack is using Alerting backend. Otherwise create a new configuration by selecting Add a new Breach Notification Details. In the Alerting Backend hostname or IP address, type the Primary Backend host. Type 2010 as the port.
  15. Select a configuration for Alert Consolidation Details.

    Reuse the answers if another solution pack is using Alert Consolidation Details. Otherwise create a new configuration by selecting Add a new Alert Consolidation Details. In the Alert Consolidation hostname field, type the Primary Backend host. Type 2040 as the port.

    If SOM RCA installation needs to be done, the alert consolidation configuration is required. For more details, refer to the "How to" article for SOM.

  16. Click Next.
  17. In the Administration Web-Service Instance field of the Compliance Frontend window, select the Frontend host.
  18. Click Next.
  19. Click Install.

    Select the maximize arrow next to each component to view the installation process. Review the information on the install screen and make changes as necessary. It is preferable to preserve the default settings.

    Answer the questions during installation. The recommended answer for a delete questions is n.

    When the installation successfully completes, a green checkmark appears.

  20. Click Ok once installation is complete.
    Select the appropriate VMs for respective modules for installation. For , for Compliance Notifications and Compliance Backend select Primary Backend VM, Compliance Frontend and Compliance Reports select Frontend VM.
Back to Top

Post-installation configuration

This topic describes any required or suggested configuration for the SolutionPack . After installing the SolutionPack you have to restart specific services.

Procedure

  1. Configure compliance-frontend.xml.
    • Change the directory path to /opt/APG/Web-Servers/Tomcat/Default/ conf/Catalina/localhost/ and edit the compliance-frontend.xml file to make changes to localhost and replace it with the name of the primary backend VM (location where the compliance backend is installed) in the following three entries:
      <Resource name="manager/ComplianceManager" auth="Container" 
      type="com.emc.srm.base.compliance.jmx.ComplianceManagerFactory"
      factory="org.apache.naming.factory.BeanFactory" user="admin" 
      pass="changeme" 
      url="service:jmx:rmi:///jndi/rmi://localhost:52755/jmxrmi" />
      <Resource name="manager/ComplianceESMManager" auth="Container" 
      type="com.emc.srm.base.compliance.jmx.ComplianceManagerFactory"
      factory="org.apache.naming.factory.BeanFactory" user="admin" 
      pass="changeme" 
      url="service:jmx:rmi:///jndi/rmi://localhost:52755/jmxrmi" />
      <Resource name="manager/CompliancePolicyTemplateManager" auth="Container" 
      type="com.emc.srm.base.compliance.jmx.ComplianceManagerFactory" 
      factory="org.apache.naming.factory.BeanFactory" user="admin" 
      pass="changeme" 
      url="service:jmx:rmi:///jndi/rmi://localhost:52755/jmxrmi" />
      
    • Perform the following configuration for all APG databases.
      <!-- Gives access to the timeseries database. -->
      	<ResourceLink name="jdbc/APG-DB:{ cachegrp=DB }" 
      global="jdbc/APG-DB" type="javax.sql.DataSource" />
  2. Restart the tomcat service:
    1. Go to /OPT/APG/bin
    2. Run the command ./manage-modules.sh service restart tomcat instance-name
  3. If you reset the web service password,
    1. Reconfigure the compliance backend from the Central Configuration Repository.
    2. Restart the Compliance Backend service.
Back to Top