3.10 EMC SMARTS

Create an adapter for each instance of EMC SMARTS on the network (see Section 2.1, Creating an Adapter). See the integration information in the following sections and then modify the adapter properties (see Section A.11, EMC SMARTS).

The following topics provide information on integrating to EMC SMARTS:

• Section 3.10.1, Integrating EMC SMARTS
• Section 3.10.2, Disabling Operations and Filtering Information from EMC SMARTS
• Section 3.10.3, Error Handling
• Section 3.10.4, Discovery of EMC SMARTS Elements
• Section 3.10.5, Viewing Attributes, Details, Programs, and Libraries
• Section 3.10.6, Creating and Managing Instances
• Section 3.10.7, Saving and Restoring the Element Repository
• Section 3.10.8, Event Notifications and Alarms Mappings
• Section 3.10.9, Alarm Properties
• Section 3.10.10, Subscribing to Events
• Section 3.10.11, Correlating Events
• Section 3.10.12, Recomputing the InCharge Codebook

3.10.1 Integrating EMC SMARTS

To integrate to EMC SMARTS:

1. Stop the Operations Center server. For instructions, see Stopping the Operations Center server in Windows and Stopping the Server and the mosdaemon manually in UNIX in the Operations Center Server Installation Guide .
2. Verify that the Operations Center server is not configured to restart automatically. For more information, see the Operations Center Server Configuration Guide .
3. Copy the following files from the EMC SMARTS installation /classes directory into the / OperationsCenter_install_path /classes/ext directory:

• clsapi.jar
• clsapi_err.jar
• cryptojFIPS.jar
• i18napi.jar
• icu4j-3_8_1.jar
• net.jar
• platform.jar
• platform_err.jar
• skclient.jar
• skclient_err.jar
• sslj.jar

• The hostname of the SMARTS Broker
• The port that the SMARTS Broker listens on (default is 9002)
• A valid user name and password, if SMARTS is running with authentication required
• The structure of your SMARTS environment. The discovery of instances is dependent on a match of both Domain List and Domain Manager properties. If a domain isn’t subscribed to by the specified Domain Manager, Operations Center won’t be able to access it.

3.10.2 Disabling Operations and Filtering Information from EMC SMARTS

The EMC SMARTS adapter can be restricted from performing various operations on the EMC SMARTS server. This includes various intrusive functions such as saving or restoring the Repository file or performing codebook correlation updates.

Operations Center uses properties files to restrict server-side access for all EMC SMARTS adapters and apply filter relation and alarm information. The following default files located in the / OperationsCenter_install_path /database directory apply to all adapter instances:

SmartsSecurityFilter.properties: Disable various adapter operations and functions to the EMC SMARTS server.

If no property file exists, no restrictions apply to the adapter.

Table 3-9 describes the default property files.

Table 3-9 EMC SMARTS –Properties Files and Filter/Disable Options

Disables Consistency Update and Correlate Now operations.

Disables Store Repository and Restore Repository operations.

Disables Manage and Unmanage element operations.

Disables Instance Create and Delete operations on elements.

Disables the subscription to topology change notifications.

Allows any alarms to pass with the specified alarm column value. Separate values with a “|” symbol and show spaces in values with an underscore (_) symbol.

Indicates the relations to show. The default value is pass=ServiceOffering .

Indicates the relations to show, but does not show any children. Default values include: Bridges , BridgedVia , ConnectedPorts , ConnectedTo , ConnectedVia , ConsistsOf , LayeredOver , MemberSystems , Members , Underlying , Manages , Consumes , Produces , Serves , HostedBy , ManagedBy , ConsumedBy , ProducedBy , ServedBy , and MemberOf .

Indicates those relations to filter out (not shown). Default values include: ConfiguredBy , SettingsAppliedBy , Realizes , RealizedBy , Notifications , Notifies , NotifiedBy , NeighboringSystems , part of , MemberOf , ParentGroup , Factory , and ConsistsOf .

These filter properties files can be customized for a specific adapter.

To apply a property file for a single adapter:

1. Make a copy of the property file in / OperationsCenter_install_path /database and rename using the adapter name such as SmartsfilterTypeFilter.adapterName.properties . Use underscores in place of spaces within an adapter name. For example, if the adapter name is InCharge on serverx , rename the filter file to SmartsAlarmFilter.InCharge_on_serverx.properties .
2. Modify the properties file as required.

3.10.3 Error Handling

The integration might throw exceptions in the case of errors or malfunctions. All exceptions are logged in a standard format using the Operations Center logging features. Each logging statement is associated with an ERROR, INFO, WARN or DEBUG level.

3.10.4 Discovery of EMC SMARTS Elements

The EMC SMARTS adapter automatically performs element discovery synchronization that includes:

• Discovery of all the technology elements from the InCharge database and populates the Operations Center object model
• Discovery of classes, instances, and relations between objects for use in the Service Views
• Relationship mapping between object for n ‑deep nested class/instance/relation sets
• Subscriptions to event notifications
• Management of instances (when available)
• Element property mapping and property pages for elements
• Automatic adapter updates for InCharge instance create and delete notifications

The specific objects are implemented as proxy objects of the actual InCharge objects. When values (or other data) are queried in Operations Center, the adapter requests the data on‑demand from the InCharge server. The adapter caches some common data values for efficiency.

Table 3-10 describes the InCharge object icons.

Table 3-10 InCharge Objects

The Root Element represents an instance of a Domain Manager

Elements in Operations Center are identified by a unique key value. The key value consists of a concatenation of up to 3 string values delimited by “:”. This key value is used to uniquely identify the element instance in the Operations Center element repository.

Operations Center aggregates all data from various consoles into the element hierarchy. When comparing the Operations Center element hierarchy tree to the InCharge console, typically more relation instances are displayed in Operations Center than in a single InCharge console. This is because the InCharge console only shows the relations applicable to the console.

Parent a single element to multiple spots in the element hierarchy by using a key value that consists of concatenating the root hierarchy key and all element keys for each of its parents.

• Class instance key values are simply the class name. For example, Host.
• Instance key values are the concatenation of the class with the instance name. For example, Host:server.mosol.com.
• Relation instance key values are the concatenation of the class, instance, and relation name. For example, Host:server.mosol.com:ComposedOf.

Normally, the default condition algorithm determines the condition of a Operations Center element. The default condition algorithm sets the element condition equal to the most critical severity of any alarm attached to the element or to its children. The exception is for relation elements, which do not propagate up their condition.

Table 3-11 outlines the ACL permission on various element menu operations.

Table 3-11 EMC SMARTS—ACL Permissions on Element Operations