This document
provides an overview of the changes made to the HP Operations Manager Smart
Plug-In for Remedy Action Request System (Remedy SPI) for the 4.06 patch
release. It contains important information not included in the manuals or in
online help.
In This Version
Documentation Updates
Installation Notes
Enhancements and Fixes
Known Problems, Limitations, and Workarounds
Documentation Errata
Support
Legal Notices
The first page of
this release notes document contains the following identifying information:
To check for recent
updates or to verify that you are using the most recent edition, visit the
following URL:
http://support.openview.hp.com/selfsolve/manuals/
1.
In
the Product list, click the product name.
2. In the Version
list, click the version number.
3. In the OS
list, click the OS type.
4. In the document
list, click the document title.
5. To retrieve the
document, click Open or Download.
NOTE: To view files in PDF
format (*.pdf), Adobe Acrobat Reader must be
installed on your system. To download Adobe Acrobat Reader, go to the following
URL:
http://www.adobe.com/
The Software and Hardware Requirements are listed in Administrator’s Reference guide for the Remedy SPI.
The document file is included on the
product's CD media as SPI-DVD for HPOM\Documentation\SPI
Guides\Remedy_Config.pdf.
The Remedy SPI server needs the dynamic link libraries
(DLLs) from the Action Request System server to run. These have to be copied to
the HPOM management server before the Remedy SPI server can be started.
After the Remedy SPI has been installed, the Remedy SPI service is not started
automatically. This is because the SPI configuration files have to be created
and propagated accordingly and the ARS libraries have to be copied in place
first.
If, after installing the SPI, the HPOM management
server is rebooted before these steps have been completed, an error window is
shown after the reboot, stating the inability of the service manager to locate
the ARS libraries (because the Remedy SPI service is configured to start
automatically on reboot). This error can be ignored until the SPI has been
configured and the ARS libraries have been copied.
If the Remedy SPI is to be upgraded from a prior
version, then the following steps should be performed:
If, for any reason, the upgrade has not been performed
in this sequence, but the new version was installed while the previous version
was still in place, then the following should be noted:
There is no policy group called “Auto-Deploy”
located under these groups as with the previous version. Thus, the old policy
groups called “Auto-Deploy” should now be removed. This applies only if you upgrade from a
version older than 02.90.
The steps needed to install the Remedy SPI are
contained in this section. For a detailed discussion of the configuration,
please see the Administrator’s Reference guide for the Remedy SPI.
The document file is included on
the product's CD media as SPI-DVD for HPOM\Documentation\SPI
Guides\Remedy_Config.pdf.
1. Install the new version of the Remedy SPI using the full
installation media (HP Operations Manager
Smart Plug-Ins DVD: 2009 for 4.00 (HPOM 8), 2010.3 for 4.03 (HPOM 9)).
2. Copy the following
Action Request System server libraries into the directory %OvInstallDir%\bin\REMSPI. The ARS server libraries may be found on your original Action
Request System Install CDs.
§ arapi71.dll
§ arrpc71.dll
§ arutl71.dll
3.
Create and update the Remedy SPI configuration
file %OvShareDir%\conf\REMSPI\remspi.cfg
according to the detailed description in the Administrator’s Reference guide for the Remedy SPI. You may use
the file remspi.cfg.new in this directory as a starting point.
4. Create and update
the Remedy SPI configuration file %OvShareDir%\conf\REMSPI\rules according to the detailed description in the Administrator’s
Reference guide for the Remedy SPI.
You may use the file rules.PR in this directory as a starting point.
5. Deploy the REMSPI and
the SHS Data Collector instrumentation to the managed nodes that will be put in to
the SPI for Remedy ARS node groups in the HPOM console in the next step. For Windows
nodes, add the Microsoft Windows instrumentation.
6. Copy the ARS server
and the HPOM management server icons into the appropriate node group in the
HPOM console.
7. Configure the ARS
form and ARS filters on the ARS server according to the instructions in Administrator’s
Reference guide for the Remedy SPI
to enable the communication from ARS to HPOM.
8. Start the Remedy
SPI service using the HPOM tool Remedy
SPI Admin \ Start SPI Server or use
the command net start “HP
OV SPI for Remedy service” in a command window on the HPOM management server.
|
Remedy SPI log files need to
be self-maintained |
|
Utilize Remedy Plugin instead of a run-process
itoupdate to update messages in OMU |
|
Enhancement Request for
ownership in Remedy SPI |
|
remspisrv aborts on unexpected
input |
|
$NODE_IP$ shows the IP
addresses in reverse |
|
OML Remedy SPI support Remedy v8, Remedy SPI needs
to Support ARS 7.7 |
|
remspisrv should check for supported AR field
types upfront and not during operation |
|
Use of an Administrator
account different than opc_adm |
|
Remedy SPI can't start when
OMU server has PAM enabled |
|
Customer requests to
dynamically change the Remedy spi ARS user |
|
Implement ATTACH_TO_EXISTING keyword |
|
Add info for Load Balancer
configuration |
|
Setting CMA sometimes fails:
'Access denied' - Update documentation |
|
Wrong doc for defining actions
to different targets |
|
Incomplete mapping of MCE
codes to text |
|
remspisrv aborts in submit
while searching conditions |
|
Remedy SPI can't resolve ARS
hostname anymore |
|
Wrong keyword ARRPCPORT in comment of rules file |
|
Remote DB with Oracle client 11.2: Cannot connect
to database – Add info to RemSPI
documentation |
|
|
PROBLEM: |
The tool remspi_qutil does not lock the SPI queues. If executed while the
SPI server is running this may lead to inconsistencies in the queue files. |
|
|
SOLUTION: |
Use
this tool only if the SPI server is not running. If you experience problems
due to inconsistencies in the queues, stop the server, delete all files in
the queue directories (%OvDataDir%\tmp\remspi\queue.*)and restart the server. |
|
|
|
|
|
|
PROBLEM: |
Do not use
multiple ON_SUBMIT sections for a TARGET in the rules file.
Although syntactically correct, the SPI will only use the statements found in
the last ON_SUBMIT section of the TARGET. |
|
|
SOLUTION: |
It’s
always possible to define all needed ON_SUBMIT statements in one section per TARGET in
the rules file. All ON_SUBMIT statements will be executed in a predefined sequence
which is not related to the appearance of the statements in the rules
file. |
|
|
|
|
|
|
PROBLEM: |
Internal
SPI messages (i.e. Application = "Remedy SPI") are not submitted
either automatically or manually nor is the SPI
server informed about their update. |
|
|
SOLUTION: |
This
is not an error of the SPI, but intended behavior to prevent loops. |
|
|
|
|
Please visit the HP support web site at:
http://support.openview.hp.com/
This web site provides contact information and details
about the products, services, and support that HP offers.
HP online software support provides customer self-solve
capabilities. It provides a fast and efficient way to access interactive
technical support tools needed to manage your business. As a valued support
customer, you can benefit by being able to:
§ Search for knowledge documents of interest
§ Submit and track progress on support cases
§ Submit enhancement requests online
§ Download software patches
§ Manage a support contract
§ Look up HP support contacts
§ Review information about available services
§ Enter discussions with other software customers
§ Research and register for software training
NOTE: Most of
the support areas require that you register as an HP Passport user and sign in.
Many also require an active support contract. To find more information about
support access levels, go to the following URL:
http://support.openview.hp.com/access_level.jsp
To register for an HP Passport ID, go to the following
URL:
©Copyright 2013 Hewlett-Packard
Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software,
Computer Software Documentation, and Technical Data for Commercial Items are
licensed to the U.S. Government under vendor's standard commercial license.
The only warranties for HP products and services are
set forth in the express warranty statements accompanying such products and
services. Nothing herein should be construed as constituting an additional
warranty. HP shall not be liable for technical or editorial errors or omissions
contained herein.
For information about third-party license agreements,
see the spi-thirdparty-license-agreements
directory in the product installation directory.
The information contained herein is subject to change
without notice.