The Smarts Outbound Alert Plugin populates Smarts notifications with information about the alert and the system to which it belongs. These fields are used to identify the alert and reporting system on the Smarts side.
These fields can be made to populate other notification fields, or can be left blank to instruct the plugin not to use this field.
Table 3‑1. Customizable Fields
Field Name Description Default Value
vcopsurlfield This field is used by the Global Console Custom View. If using this view, this field must be present and must be in the default field, otherwise the view will fail to load the notifications. If not using this view, then this field may be blank.
UserDefined8
alertidfield This field is required. If using the Global Console Custom View, this value must be the default value. If not using the view, it can be in any user defined notification field.
UserDefined9
alerturlfield This field is required for the integration tools to work (Launch-in-context). If the field is changed from the default, the integration tool script must also be updated to use the correct field (for instance, if this field is now set to populate UserDefined3, the script must be updated to use the UserDefined3 field instead of UserDefined10).
UserDefined10
Installing and Configuring the Global Console Custom View
You can install and configure the vCenter Operations Manager custom view so that operators can view alert details in the Global Console.
Install the Global Console Custom View
You install the vCenter Operations Manager custom view on the EMC Smarts server.
The Global Console custom view feature is supported only with the following vCenter Operations Manager versions:
n Standalone versions 5.0, 5.6, 5.7, and later n vApp versions 5.6 , 5.7, and later
The Global Console custom view feature is not supported with Standalone 5.0.x or with any vApp version earlier than 5.6.
Prerequisites
n Verify that you have a compatible version of EMC Smarts. See “Installation and Configuration Requirements,” on page 10.
n Verify that you have a supported vCenter Operations Manager version.
n Verify that the keytool utility is added to the system path on the EMC Smarts server. The keytool utility is provided with Java.
Chapter 3 Configuring EMC Smarts Integration
Procedure
1 Download the GlobalConsoleCustomView.zip file from the Resource tab at https://solutionexchange.vmware.com/store/products/emc-smarts.
Make sure that you download the correct file for your vCenter Operations Manager version.
Option Action
Standalone version 5.0 Copy thevcops_emc.jar file from the VCOPS-Third Party Tool Adapters/EMC-Smarts/GlobalConsoleCustomView/vCOPS-5.0-Standalone folder you extracted from GlobalConsoleCustomView.zip.
Standalone version 5.6, 5.7, or later Copy the vcops_emc.jar file from the VCOPS-Third Party Tool Adapters/EMC-Smarts/GlobalConsoleCustomView/vCOPS-5.6+ folder you extracted from GlobalConsoleCustomView.zip.
vApp version 5.6, 5.7, or later Copy the vcops_emc.jar file from the VCOPS-Third Party Tool Adapters/EMC-Smarts/GlobalConsoleCustomView/vCOPS-5.6+ folder you extracted from GlobalConsoleCustomView.zip.
2 Place the vcops_emc.jar file in the SmartsRoot/SAM/smarts/local/classes folder on the EMC Smarts client.
SmartsRoot is the root folder of the EMC Smarts installation. The default root folder is InCharge9 for EMC Smarts 9.x.
3 Configure certificate authentication for the Global Console custom view.
When you configure certificate authentication, users cannot view alert information from the Global Console custom view panel for vCenter Operations Manager systems that are not trusted.
a Use an archiving program, such as 7-Zip, to extract the truststore file from the vcops_emc.jar file to any directory on the EMC Smarts client file system.
The truststore file is in the com/integrien/alive/alertsummary/resources/ folder in vcops_emc.jar. b Make sure that the truststore file is writeable.
c Use the keytool utility to change the default truststore password.
For example: keytool -storepasswd -keystore truststore
The keytool utility prompts you for the default password, which is oxygen, and then for your new password.
d In the connection.properties file, set TRUSTSTORE_LOCATION to the path for the truststore file and TRUSTSTORE_PASSWORD to the new truststore password.
The connection.properties file is in the com/integrien/alive/alertsummary/resources/ folder in vcops_emc.jar.
In the example, the truststore file is in the C:/temp directory on a Windows system and the truststore password is cat.
TRUSTSTORE_LOCATION=C:/temp/truststore TRUSTSTORE_PASSWORD=cat
4 On the EMC Smarts client, open the runcmd_env.sh file in a text editor.
The runcmd_env.sh file is located at SmartsRoot/CONSOLE/smarts/local/conf. 5 In runcmd_env.sh, set SM_CLASSPATH to the path for the vcops_emc.jar file.
For example:
SM_CLASSPATH= C:\InCharge7\SAM\smarts\local\classes\vcops_emc.jar
What to do next
If you do not want users to be prompted to add certificates to the truststore file when they click an alert for a vCenter Operations Manager system that is not trusted, you can manually add certificates to the truststore file. See “Manually Add a Certificate to the Truststore File,” on page 27.
Add the custom view in the Global Console. See “Add the Custom View in the Global Console,” on page 28.