Installing Resource Metric Viewer

Resource Metric Viewer must be installed on the server where Jazz for Service Management is installed.

Before you begin

Extract the rmv.zip file to <JAZZSM_HOME> from the location where you have downloaded and extracted the WirelessModelling_<version>-win32.win32.x86.zip file. Where <JAZZSM_HOME> is the location where the Jazz for Service Management Components is installed. By default, /opt/IBM/JazzSM.

For more information, see Installing the Tivoli Netcool Performance Manager - Application Studio.

Procedure

  1. Go to the admin folder and run the rmv_install.sh command by using the following commands:
     cd admin
    ./rmv_install.sh
    Provide the following inputs.
    1. Enter the JDBC URL for the administrative database. Due to an Oracle limitation, the host name cannot exceed 60 characters. If the host name exceeds 60 characters, use the IP address instead.
      Please enter the database url:(jdbc:oracle:thin:@hostname:1521:vtdb):
      jdbc:oracle:thin:@10.55.236.187:1521:vtdb
    2. Enter the directory where the Oracle client is installed.

      For example,/appl/oracle/product/11.2.0/db_1.

      Please enter the location for ORACLE_HOME:(/appl/oracle/product/11.2.0/db_1):
      /appl/oracle/product/11.2.0/db_1
    3. Enter the name of the administrative database user nasaccess
      Please enter the username for database:(nasaccess):
      nasaccess
    4. Enter the password of the administrative database user nasaccess
      Please enter the password for database:(nasaccess):
      nasaccess
    5. Enter the Jazz for Service Management installation directory. By default,/opt/IBM/JazzSM.
      Please enter the JazzSM location:(/opt/IBM/JazzSM):
      /opt/IBM/JazzSM
    6. Enter a Jazz for Service Management administrator user name. By default, smadmin.
      Please enter the JazzSM username:(smadmin):
      smadmin
    7. Enter a Jazz for Service Management administrator user name. By default, smadmin.
    8. Enter the Cognos Dispatcher port.
      Please enter the Dispatcher port:(16310):
      16310
    The install script runs with the following output:
    Running sql: /opt/IBM/JazzSM/MH_RMV/rmv/sql/create_user.sql
    
    PL/SQL procedure successfully completed.
    
    Running sql: /opt/IBM/JazzSM/MH_RMV/rmv/sql/create_tables.sql
    
    Grant succeeded.
    
    Grant succeeded.
    
    Grant succeeded.
    
    Grant succeeded.
    
    Grant succeeded.
    
    Grant succeeded.
    
    
    Grant succeeded.
    
    Grant succeeded.
    
    Grant succeeded.
    
    Grant succeeded.
    
    Grant succeeded.
    
    Grant succeeded.
    
    
    Grant succeeded.
    
    Grant succeeded.
    
    Grant succeeded.
    
    PL/SQL procedure successfully completed.
    
    
    PL/SQL procedure successfully completed.
    
    Running sql: /opt/IBM/JazzSM/MH_RMV/rmv/sql/create_views.sql
    
    View created.
    
    View created.
    
    
    View created.
    
    View created.
    
    View created.
    
    View created.
    
    Running sql: /opt/IBM/JazzSM/MH_RMV/rmv/sql/bi_rmv_merge.pks
    
    Package created.
    
    Running sql: /opt/IBM/JazzSM/MH_RMV/rmv/sql/bi_rmv_merge.pkb
    
    Package body created.
    
    WASX7209I: Connected to process "server1" on node JazzSMNode01 using SOAP connector;  
    The type of process is: UnManagedProcess
    
    rmv.install.intro
    
    tools.install.configuringJdbc
    tools.install.getJDBCDetails
    tools.install.getJDBCDetails
    tools.install.configuringJdbcProvider
    tools.install.deletingJdbcProvider
    tools.install.createdJdbcProvider
    tools.install.configuringJdbcDataSource
    tools.install.createdJdbcDataSource
    
    WASX7209I: Connected to process "server1" on node JazzSMNode01 using SOAP connector;  
    The type of process is: UnManagedProcess
    com.ibm.isclite.DeployBundleActivator.start(BundleContext context) Entry
    WASX7327I: Contents of was.policy file:
    //
    // Template policy file for enterprise application.
    // Extra permissions can be added if required by the enterprise application.
    //
    // NOTE: Syntax errors in the policy files will cause the enterprise application FAIL to start.
    // Extreme care should be taken when editing these policy files. It is advised to use
    // the policytool provided by the JDK for editing the policy files
    // (WAS_HOME/java/jre/bin/policytool).
    //
    
    grant codeBase "file:${application}" {
    };
    grant codeBase "file:${jars}" {
    };
    grant codeBase "file:${connectorComponent}" {
    };
    grant codeBase "file:${webComponent}" {
    };
    
    grant codeBase "file:${ejbComponent}" {
    };
    
    ADMA5078I: Update of isc has started.
    ADMA5058I: Application and module versions are validated with versions of deployment targets.
    ADMA5009I: Extracting application archive to
    /opt/IBM/JazzSM/profile/wstemp/appmgmt/mbean/AppManagement_14501ead05a_1/app_14503982d04/ext/tnpmrmv.war.
    ADMA5064I: FileMergeTask completed successfully for isc.
    ADMA5005I: The application isc is configured in the WebSphere Application Server repository.
    ADMA5005I: The application isc is configured in the WebSphere Application Server repository.
    ADMA5005I: The application isc is configured in the WebSphere Application Server repository.
    CWLAA10007I: Explanation: The help plug-in of the Integrated Solutions Console module was deployed successfully. 
    User action: No user action required.
    CWLAA10001I: Explanation: The Integrated Solutions Console module was deployed successfully. 
    User action: No user action required.
    ADMA5005I: The application isc is configured in the WebSphere Application Server repository.
    ADMA5113I: Activation plan created successfully.
    ADMA5005I: The application isc is configured in the WebSphere Application Server repository.
    ADMA5011I: The cleanup of the temp directory for application isc is complete.
    ADMA5079I: Update of isc has ended. The application or its web modules may require a restart when a save 
    is performed.
  2. Restart the Jazz for Service Management.
  3. Optional: Run the db2start command to restart the database instance.
    cd /
    ./home/smadmin/sqllib/adm/db2stop
    ./home/smadmin/sqllib/adm/db2start