Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(1 Rating)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

HOW TO: Run the CSM Client for ILM
Solution

The Configuration Support Manager(CSM) is used to collect the system, environment and product details of the machine hosting Information LifeCycle Management (ILM).

The CSM Client output for ILM can be generated using one of the following methods:

  • Command line interface (CLI)
  • Web Application

CLI

The steps to generate the CSM Client output for ILM using command line interface are the following:

  1. Download and extract (unzip) the csm-ilm-release-1.0.zip\csm-ilm-cli.zip file in a location from where CSM will run.
  2. Assign execute permissions to the executable file only in UNIX platforms.
  3. Depending on the operating system run one of the following:
    • Windows use run.bat
    • UNIX, LINUX, SUNOS and HPUX, use run.sh
  4. Run the CSM using one of the following modes:
    • Command line option:
       ./run.sh ilm –h <Database host> -o <Database port> -d <Database service> -u <Database username> -x <Database password> -t <Database type> -i <ILM installation directory> -s
      When prompted for the Java home directory provide the path to either the JDK bin directory or JRE bin directory.
    • Interactive command line option:
      ./run.sh
      When prompted for the Java home directory provide the path to either the JDK bin directory or JRE bin directory.
      Also provide the necessary inputs as and when required
      The output is an XML file with the following naming convention csmclient<hostname>.xml
      Open the XML in Internet Explorer to view the formatted output.
Note

Ensure that the JAVA_HOME environment variable is set. It is mandatory to have Java 1.5 or above (JRE or JDK) in the path before running the CSM Client. Otherwise, the ILM product information will not be fetched.

Web Deployment

The following are the steps to generate the CSM Client output for ILM using web application:

  1. Download and extract (unzip) the csm-ilm-release-1.0.zip\csm-ilm-web-deployable.zip file.
  2. Assign execute permissions to the executable file only in UNIX platforms.
  3. Depending on the operating system run one of the following:
    • Windows use deploy.bat
    • UNIX, LINUX, SUNOS and HPUX, use deploy.sh
      When prompted for the ILM home directory provide the path of the ILM home directory.
  4. Rerun the startApplimation.sh file on UNIX platforms and startApplimation.bat on windows machine.
  5. Launch the URL <ILM_URL>/csm/generatecsm.jsp
    By default, the following AMHOME.properties details are displayed:
  6. Change the Database Type according to the AMHOME.properties database type.
    The following are the valid values:
    • Oracle
    • SQL Server
    • DB2
  7. Enter password in the Database User Password text box.
  8. Click Generate New CSM.
    The following screen is displayed. Do not refresh or navigate away from this page:
  9. The following screen appears after the CSM XML is generated:
More Information

Depending on the system configuration the CSM Client utility gathers the following information:

System (UNIX)

System Information
CPU Information
Environment Variables
File System
Operating System Patches
Network Information
User Limits
Swap Information

System (Windows)

Memory Information
CPU Information
Environment Variables
Disk Information
Operating System Information
Network Configuration

Product (ILM)

Installed Products
Product Patches
Amhome Db Details
Amhome Db Objects
Amhome Properties
Repository Attributes
Instance Statistics
Installed PFVs
Archived Entities
Standalone Jobs
User Roles
ILM Db Links
Configuration Properties
Quartz Properties
Attachment Properties
Java Version

Reference
Applies To
Product: Data Archive
Problem Type:
User Type:
Project Phase:
Product Version: ILM Platform 5.3
Database:
Operating System:
Other Software:
Attachments
Last Modified Date:10/24/2011 1:39 AMID:124460
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)