Administration and Maintenance

Contents
casp1031
Contents
 
Customize a Service Editor Information Table
You can specify the information tables for services, customers, SLAs, and SLA templates in the Service Editor dialog. Specify the information types (columns) to include, the sort order (by status, by name, or by date for example), and the font and text size. You can revert to default settings. For more information about customizing interface settings, see the Using OneClick section
.
Follow these steps:
  1. Open the Service Editor.
  2. Select the tab for which you want to customize an information table and right-click any column heading.
    The Table Preferences dialog appears.
    In the Table Preferences dialog, the column name 'Current MOT' is now renamed as 'Peak Outage Time'. The 'Peak Outage Time' indicates the maximum outage time a service has undergone.
  3. Configure the table properties and click OK.
    The information table is customized.
Customize a Service Policy Editor Information Table
You can specify the information tables for policies, attribute maps, and rule sets in the Service Policy Editor dialog. Specify the information types (columns) to include, the sort order (by status, by name, or by date, for example), and the font and text size. You can also revert to default settings. For more information about customizing interface settings, see the Using OneClick section
.
.
Follow these steps:
  1. Open the Service Editor.
  2. Select the tab for which you want to customize an information table and right-click any column heading.
    The Table Preferences window appears.
    In the Table Preferences dialog, the column name 'Current MOT' is now renamed as 'Peak Outage Time'. The 'Peak Outage Time' indicates the maximum outage time a service has undergone.
  3. Configure the table properties and click OK.
    The information table is customized.
Remove Service Manager Historical Data from All Landscapes
You can remove Service Manager historical data from all landscapes.
Once you remove historical data from the database, you can no longer generate reports about them.
To remove Service Manager historical data from all landscapes, run the following script:
  • Windows:
    <$SPECROOT>\bin\SMIntializeDB.bat
  • UNIX/Linux:
    <$SPECROOT>/bin/SMIntializeDB
Remove Service Manager Historical Data from a Single Landscape
You can remove Service Manager historical data from a single landscape.
Once you remove historical data from the database, you can no longer generate reports about them.
To remove Service Manager historical data from a single landscape, run the following script:
  • Windows:
    <$SPECROOT>\bin\SMInitializeLandscape.bat <lh>
    • lh
      Indicates landscape handle.
  • UNIX/Linux:
    <$SPECROOT>/bin/SMInitializeLandscape <lh>
    • lh
      Indicates landscape handle.
Remove Destroyed Service Manager Models from All Landscapes
You can remove destroyed Service Manager models from all landscapes.
Note:
Once you remove destroyed Service Manager models from the database, you can no longer generate reports about them.
To remove destroyed Service Manager models (services, SLAs, and so on) and historical data for those models from all landscapes, run the following script:
  • Windows:
    <$SPECROOT>\bin\SMRemoveDestroyedModels.bat
  • UNIX/Linux:
    <$SPECROOT>/bin/SMRemoveDestroyedModels
Custom Resources Table
If a service using a policy with a custom attribute map is created, customize the Resources table to display the data you want to view about the monitored attribute that is specified in the custom attribute map. The Resources table appears in the following locations:
  • Resources link under the OneClick Information tab
  • List tab in OneClick Contents panel
  • Service Dashboard List tab
  • Resources tab in Service Editor
For more information about customizing OneClick interface elements, see the OneClick Customization section
.
The following table lists Resources table configuration files for attributes that are monitored by standard Service Manager attribute maps:
Attribute
Attribute ID
File
Contact Status
0x10004
table-resources-0x10044-config.xml
Condition
0x1000a
table-resources-0x1000a-config.xml
ConditionValue
0x1000b
table-resources-0x1000b-config.xml
Port Status
0x10f1b
table-resources-0x10f1b-config.xml
Service Health
0x12a40
table-resources-0x12a40-config.xml
Response Time
0x456008c
table-resources-0x456008c-config.xml
These default files are located in the following directory:
<$SPECROOT>/tomcat/webapps/<sp>/WEB-INF/slm/config
Suppose, for example, you have a service that monitors “load in” data on a set of port resources. In this case, you can create a custom Resources table to display NRM_PortLoadIn (0x12aad) attribute data for a set of ports that are monitored by the service instead of the default Condition attribute data. The NRM_PortLoadIn (0x12aad) attribute example is used in the sections that describe how to configure the custom file.
Create the Custom Table File
You can create the custom file from scratch and can save it to the custom file directory, or you can save a modified version of the default table-resources-config.xml file from the following directory to the custom file directory:
<$SPECROOT>/tomcat/webapps/spectrum/WEB-INF/slm/config
Follow these steps:
  1. Create the following custom file directory:
    <$SPECROOT>/custom/slm/config
  2. Save all custom Resources table configuration files for Service Manager to this directory.
  3. Create the custom file using the following naming convention:
    table-resources-<attribute ID>-config.xml
    For the load in attribute example:
    table-resources-0x12aad-config.xml
Example: Resources Table Configuration File
The following script shows an abbreviated example of the table-resources-0x12aad-config.xml configuration file. OneClick loads the table that is specified by this file to display the “load in” data column with other types of data for the port resources that are monitored by the service.
Elements pertaining to the “load in” example are highlighted in bold.
<?xml version="1.0" encoding="utf-8"?> <table id="table-resources-0x12aad-config" xmlns="http://www.aprisma.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.aprisma.com ../../common/schema/table-config.xsd"> <orientation>horizontal</orientation> <swing-table-template> <show-vertical-lines>true</show-vertical-lines> <show-horizontal-lines>false</show-horizontal-lines> </swing-table-template> <swing-header-row-template> <static-color idref="row-header-color-config"/> </swing-header-row-template> <swing-row-template> <enumerated-color idref="alternatingrow-color-config"/> </swing-row-template> <column-list> <column> <name>Load In</name> <content> <attribute>0x12aad</attribute> </content> <default-width>125</default-width> </column> <column idref="column-normalizedstatus-config"> <default-width>125</default-width> </column> <column idref="column-modelname-config"> <default-width>125</default-width> </column> </column-list> <default-sort> <sort-column-list> <sort-column> <name> com.aprisma.spectrum.app.topo.client.interfaces.render.NormalizedStatusColumn </name> <direction>ascending</direction> </sort-column> <sort-column> <name> com.aprisma.spectrum.app.util.render.ModelNameColumn </name> <direction>ascending</direction> </sort-column> </sort-column-list> </default-sort> </table>