This document is an overview of the changes made to HP Operations Manager i (HP OMi). It contains important information that is not included in the product guides or the online help. You can find information about the following in this document:
What's New in This Release?
Supported Environments
Installation Notes
Limitations
Known Problems
Documentation Updates
Support
Legal
This release of HP Operations Manager i has many new and exciting features. The most significant features are:
HP Operations Manager i (HP OMi) is an event and performance manager that creates an operations bridge between your business service management and your infrastructure management. HP OMi is the central point where all your IT infrastructure monitoring comes together in one console from which you can manage and resolve the problems in your IT environment.
HP OMi presents an end-to-end view of every event in the IT infrastructure and displays monitoring alerts to HP OMi operators. This information enables you to establish structured processes for solving problems. Using HP OMi, you can deal with most of the events in your infrastructure by running HP OMi tools and HPOM actions on any system where a problem has occurred.
HP OMi increases productivity and efficiency by finding and solving issues before business service quality degrades, allowing subject matter experts to focus on strategic activities.
HP OMi helps you to manage your IT environment using the following main features:
All events are forwarded to HP OMi's central, consolidated console, which provides the following perspectives:
Event Perspective enables centralized event management which consolidates and correlates IT-infrastructure events from multiple sources, such as HP Operations Manager agents, HP Network Node Manager i, HP SiteScope, and HP Business Process Monitor.
Health Perspective uses health indicators and key performance indicators to provide a broader, more detailed, and much more accurate view of the health of the system infrastructure, networks, and IT infrastructure.
Duplicate events are filtered out, and the root cause and event relationships are automatically determined using topology-based event correlation.
Topology-based event correlation enables you to determine the root cause of an event and to automatically establish a link between the cause of an event and any symptoms of the event.
Events can be automatically assigned to the team responsible for the event area, and enriched with state information and annotations from subject matter experts.
Handling of events can be prioritized based on business impact.
Problems can be investigated and fixed using HP OMi's graphs and tools, or by running HP Operations Manager (HPOM) actions remotely:
Graphs and charts help you visualize performance-related problems and trends affecting the configuration items impacted by an event.
Tools specified in HP OMi help you to remotely address the causes of events occurring in your IT environment. Tools are run from events on the associated CI and are designed to help you solve common problems quickly, with the minimum of effort.
Automatic or user-initiated HP Operations Manager actions can be started directly from the HP OMi console, helping you to solve common event-related problems more easily.
For a detailed description of HP OMi, see the HP Operations Manager i Concepts Guide located at this web site: HP Software Product Manuals.
See the HP Operations Manager i Installation and Deployment Guide for the hardware and software prerequisites.
HP may add support for more environments after initial release. You can find the latest version of the Support Matrix for this product that lists all supported environments at this location: HP OMi Support Matrix.
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: Access levels.
To register for an HP Passport ID, go to: HP Passport Registration.
HP Operations Manager i (HP OMi) can now be installed on systems running Microsoft Windows 2008 in conjunction with HP Business Availability Center (BAC) 8.04.
To install HP OMi on a supported Windows 2008 system, complete the following steps:
Do no yet start the HP OMi configuration steps described in chapter 5, Configuring HP OMi.
%TOPAZ_HOME%
directory on every BSM server host system.%TOPAZ_HOME%\opr\bin\createJmsQueue-BAC804.bat
to
%TOPAZ_HOME%\opr\bin\createJmsQueue.bat
Installation requirements, as well as instructions for installing HP Operations Manager i, are documented in the HP Operations Manager i Installation and Deployment Guide, provided in Portable Document Format (PDF) format. You can find this guide on-line at the HP Software Product Manuals website. For information on how to find a specific document, see Documentation Updates.
The HP Business Service Management (BSM) platform is the foundation on which you install HP OMi. You install the BSM platform by installing HP Business Availability Center (BAC), and enabling the BSM platform with a valid HP OMi license.
HINT: Port conflicts can result in BAC not starting. To avoid port conflicts between BAC and the HPOM agent, if it is installed, reserve the ports required by BAC as described in the HP Business Availability Center Deployment Guide, section titled: Reserving Ports. You can find this guide on-line at the HP Software Product Manuals website. For information on how to find a specific document, see Documentation Updates
This release contains the following limitations.
HP OMi is available in English only.
If a high number of events with ETIs is forwarded to HP OMi over a long period of time (30 minutes or longer), the correlation engine only considers up to the specified number of most recent events. If this limit is exceeded, the oldest events are removed from the queue and no longer considered for correlation.
This limit is set using the Max Waiting Queue Size attribute and is located as follows:
Admin → Platform → Setup and Maintenance → Infrastructure Settings
The default value is 5000. The valid range is 100 to 20000.
If you are experiencing this problem, lower the incoming event rate or increase the Max Waiting Queue Size limit. If the limit
is increased, you should also monitor the memory consumption and, if necessary, increase the memory setting (parameter -Xmx) for
the opr-backend process. This parameter is configured in the %TOPAZ_HOME%\bin\opr-backend_vm_params.ini
file
where the actual value being used is contained. This parameter and its value are also stored in the
%TOPAZ_HOME%\conf\opr-deployment.xml
file where the standard values, related to deployment type, are listed.
The values in the opr-backend_vm_params.ini
file are copied from the opr-deployment.xml
file. It is
recommended that you edit the appropriate values in both files.
Microsoft Exchange Server Content Pack
CI Resolution for Exchange Cluster fails when discovered by DDM (sources other than topology synchronization). Exchange Cluster is resolved to host as the CI hint fails to resolve to correct CI.
WebSphere/WebLogic (J2EE) Application Server Content Pack
In case of parallel usage of topology synchronization and DDM, the CI J2EE Domain and all CIs that have J2EE Domain as root container get duplicated.
This release contains the following unresolved problems and their workarounds, organized under the following operational areas:
Installation and Performance Initial Configuration, Content Packs, and Synchronization CI Resolution General User Interface Event Perspective Health Perspective Graphing Filtering Indicators Manager Tools Manager Maintenance
When installing HP OMi on an existing HP BAC installation with an external UCMDB configured for high availability, the HP OMi backend process does not start, even though the all UCMDB servers in the high availability cluster were specified in the HP OMi Configuration Wizard using the expected syntax:
hostname01;hostname02;hostname03;...
The opr-backend.log
log file includes entries of the following type which are continuously repeated:
Note: If only one UCMDB server is entered, the backend process starts and operates as expected. The Solution: Install the HP Operations Manager i Hotfix:
QCCR1A118587_QCCR1A118564_external_UCMDB_fixes This hotfix ensures that when HP OMi is started, it connects to the active node of the cluster nodes specified during configuration.2011-01-04 17:32:28,601 [CTRL-SVCStarter] INFO UcmdbConnection.info(94) - integration user already Exist
2011-01-04 17:32:28,602 [CTRL-SVCStarter] ERROR UcmdbConnection.error(114) - Could not initialize UcmdbConnection
for user: oprint :java.net.UnknownHostException: hostname01.example.com;hostname02.example.com;hostname03.example.com;...
opr-backend
process does not start if BSM is configured to use an external UCMDB on a cluster. The opr-backend.log
log file shows that
opr-backend
treats the semicolon-separated list of cluster nodes as one hostname.
If HP OMi is deployed in a two machine deployment (Data Processing Server and Gateway Servers) with an external UCMDB server, the HP OMi installation on the Data Processing Server not only adds its opr-backend process but also activates and starts the cmd, fcmd and mam processes. It is not necessary for these processes to be running on the Data Processing Server.
When you run the BAC configuration, you specify the external UCMDB configuration using the Connect to an existing database ... option. However, this step does not exist when you run the HP OMi configuration. The database configuration done by BAC is overwritten by the HP OMi configuration. This includes activation of the reduntant UCMDB services via the Nanny.
Solution: After the HP OMi installation, rerun the BAC database configuration using the Connect to an existing database ... option to restore the external UCMDB server settings which are misconfigured by the HP OMi post-install configuration steps.
In a one-machine installation with a Microsoft SQL Server database, JDBC connection exceptions might occur. This is a known Microsoft SQL Server problem and occurs only in one-machine installations (database and HP OMi run on the same host system).
Solution: For production environments, use two-machine or multi-machine deployment. One-machine deployment is only supported for testing purposes.
If a very large number of CIs receive events for the first time within a short time interval, the rate of event processing can become very low (could be less than one event per second). In the worst case, where tens of thousands of CIs receive their first event, it can take in the region of two to three hours for message reception to complete. For less than a thousand CIs, this time delay is much less (in the order of minutes).
Solution: After the monitor CIs have been added to the CIs, the rate of event processing returns to normal.
After disabling HP OMi and re-enabling HP BAC, the opr-backend process is no longer listed in the Nanny section in the HP Business Availability Center Server Status page, but the HP OMi menu items are still available in the BSM platform management console. Clicking on these menu items results in "Page not found." errors.
Note: After disabling HP OMi from BAC, the HAC Status section of the HP Business Availability Server Status page lists the opr-backend process of the OPR service as STOPPED.
Solution: There is no workaround.
The HP Operations Manager i Installation and Deployment Guide, software version 8.10, dated 18 August 2009 specifies the wrong default location for the content packs on page 42.
The location is listed as:
%TOPAZ_HOME%\HPBAC\conf\opr\content
Solution: The correct path is %TOPAZ_HOME%\conf\opr\content.
When updating the HPOM for UNIX database with topology data from the UCMDB using HP Operations Manager Dependency Mapping Automation (HPOM DMA) and then updating the UCMDB with topology data from HPOM for UNIX, it is possible that two instances of the same nodes are created in the UCMDB.
Solution: Install the HPOM for UNIX 9.0 Server Patch: PHSS_41175.
BSM uses TQL queries to describe what CIs to get from the ODB in order to relate the CIs to the events that BSM receives. The out-of-the-box queries that BSM provides are necessarily broader than you probably need. You can improve performance by narrowing the scope of the out-of-the-box query so that it pulls only the CIs that you require from the ODB. The resolver tries to identify the most appropriate CI from the ODB by comparing event attributes and event resolver hints with attributes of discovered CIs in the resolver cache. Because no two managed environments are identical, there is no universal resolver definition. Instead, you should try to include only those CIs in your custom resolver cache to which you expect to map events. If you never (or rarely) expect to match other CI types, there is no need to include that CI type in the resolver TQL at all. (For example, if you are only concerned with managing Oracle databases, you should exclude databases of other types).
You modify TQL queries using the ODB Modeling Studio, which provides a graphical representation of the query. You can add or remove information from the query so that it pulls only those CIs from the ODB that you decide are important for your management environment. Generally, the procedure for modifying a query is as follows:
Tip:The CI Resolution Simulator is available with the OMI_00001 server patch for HP OMi. This tool can be used to do "dry runs" with new or changed TQLs to visualize the effects of the changes withut making any changes to the database.
The modification process is not difficult, but it takes some time to understand what to modify to get the results that you expect. You should read the Topology Query Language chapter of the HP Universal CMDB document "Model Management" to get a general introduction to TQL concepts. Especially important are the concepts of containment, cardinality, attributes, and relationships. Then read the rules below to help get an understanding of the factors that may have an influence on how to modify the query.
Some CI type attributes that are required for HPOM-HP OMi topology synchronization are missing from the BAC 8.02 Service Pack.
Correlation rules that link the Exchange area to the Active Directory Domain Controller do not execute and no matching CIs are found. For example, from Design Operations Content → Correlation Rules, clicking Find Matching CIs results in an empty table.
The UCMDB enrichment rule used to link the Exchange and Active Directory CIs is not included in the version of the UCMDB that forms part of
the supported BAC 8.02 release. The correlation rule is available as a .zip
file which you can upload and apply. A
prerequisite for using the enrichment rule is to create additional CI type attributes. The enrichment rules must be uploaded
and subsequently a new run of the topology synchronization must be done.
Solution: Complete the instructions in the sections:
Click Admin → Universal CMDB.
Select the Modeling tab.
Click CI Type Manager.
Select the CI Type for which you want to add the attributes and select the Attributes tab in the right pane.
Click Add (+) to add new attributes.
Type the attribute name, display name, and description in the Add Attribute dialog box.
Select string for the Attribute Type and specify 200
for the Value Size.
Make sure that the Visible and Editable check boxes are enabled in the Advanced tab.
Click OK to add the attribute.
Click the Save icon in the CI Types pane to save the attribute.
Repeat steps 4-9 to add attributes to other CIs.
CI: System → Software Element → Microsoft Exchange Server
Attribute 1 | |
Display Name: | Current Configuration Domain Controller |
Name: | current_config_domaincontroller |
Description: | The name of the Domain Controller Server configured to be used by Exchange for Active Directory Access |
Attribute 2 | |
Display Name: | Current Domain Controllers |
Name: | current_domaincontrollers |
Description: | List of the Domain Controller Servers used by the Exchange Server |
Attribute 3 | |
Display Name: | Current Global Catalogs |
Name: | current_globalcatalogs |
Description: | List of the Global Catalog Servers used by the Exchange Server |
CI: System → Software Element → DomainController
Display Name: | DNS Server |
Name: | dnsserver |
Description: | Primary DNS Server used by the Domain Controller |
CI: System → Software Element → Active Directory Application Mode
Display Name: | Edge Server Name |
Name: | edge_server_name |
Description: | Edge Server name where the Active Directory Application Mode is installed |
CI: System → Application Resource → Microsoft Exchange Resource → ... Exchange Role → Exchange Transport Server → Exchange Hub Server
Display Name: | Edge Subscription List |
Name: | edge_subscription_list |
Description: | List of Edge Server names which are subscribed to this Hub Server |
CI: System → Software Element → DomainController
Display Name: | DNS Server |
Name: | dnsserver |
Description: | Primary DNS Server used by the Domain Controller |
Upload the missing enrichment rules.
On one of the data processing servers, start the UI and navigate to the Package Manager:
Admin → Universal CMDB → Settings → Package Manager
Use Deploy Packages to Server and upload the following files from %HPBAC_HOME%\conf\opr\workaround
:
AD_Content_Enrichment_Rules.zip
Exchange_Content_Enrichment_Rules.zip
Execute the topology synchronization and the correlation rules should work.
No ETI value is set for normal severity events forwarded from the OSSPI-CD_Mem_Load policy.
Solution: Set the Message Key to <$MSG_NODE_NAME> <$NAME> <$INSTANCE> <END>
in the start action of the condition OSSPI-CD_Mem_Load.4
of the OSSPI-CD_Mem_Load
policy.
No ETI value is set for normal severity events forwarded from WINOSSPI-CpuBottleneck_Win2k
,
WINOSSPI-SysMon_PhysicalMemCheck
, and WINOSSPI-SysMon_PageFileCheck
policies.
Solution: Set the Message Key to <$MSG_NODE_NAME> <$NAME> <$INSTANCE> <END>
in the end action of the WINOSSPI-CpuBottleneck_Win2k
, WINOSSPI-SysMon_PhysicalMemCheck
, and
WINOSSPI-SysMon_PageFileCheck
policies.
The Virtual CPU Entitlement Usage Level impacts CPU Usage Level
correlation rule fails due
to two different instances of the ESX server.
Solution: To obtain the hotfix for this issue, submit a support case to HP Software Support at the web site: HP Software Support Online
The following correlation rules have a disk dependency and the disk (file system) CI type is not discovered by the Smart Plug-in for Oracle/Microsoft SQL Server.
Solution: Manually create the link between the database instances (Oracle or Microsoft SQL Server) and the disk.
It is generally possible to control HP OMi using keyboard navigation, but in some cases it is required to use a pointing device. Some examples are switching between tabs or activating context menus.
Solution: Use a pointing device when keyboard navigation is not possible.
Selecting an action in the context menu of the CI Tree View that open a new Internet Explorer browser window, might put this new window in the background.
Solution: Selecting the icon of the new Internet Explorer window in the Taskbar brings it to the foreground.
When first switching to the Event Perspective or Health Perspective, the GUI shows empty panes and no loading indicators.
Solution: Wait until the contents of the GUI panes are displayed. This may take up to 2 or 3 minutes.
If script debugging is enabled for the Internet Explorer you might experience errors when switching between main BSM tabs, for example, when switching between the Event Perspective to the Health Perspective or the Filter Manager.
Solution: Disable script debugging.
When a content pack import is running, the Administration GUI shows timeout errors and the Application GUI freezes. All processing on the server stops until the import is completed.
The problem occurs because database tables are locked by the import. The locks are released automatically and every request that was blocked resumes. In some GUIs, you might need to trigger a manual refresh.
Solution: Wait until the import has finished before using the system for monitoring or plan a maintenance outage to update the content packs. After an import has completed, an information dialog is displayed informing of whether the import was successful.
The + and - icons in the CI Type tree in the Operations Management Administration GUIs may stop working. As a result, the tree nodes can no longer be expanded or collapsed.
Solution: Reload the current GUI using the BSM menus.
For example, if the problem occurred in the Indicators manager, select the tab:
Design Operations Content → Indicators
When several Event Browser option dialogs are open simultaneously, changes to the column selection might be lost.
Solution: Close the Event Browser option dialog before opening another one in a different window.
When changing the Rows per page option in the Event Browser and the resulting number of pages is lower than the current page number, the browser shows an incorrect page number and does not allow any actions or modifications.
Solution: Enter a valid page number and select Go to page.
While the context menu for an event is open, clicking outside of the Event Browser GUI or right-clicking an event, the menu does not close automatically.
Solution:
Click on an empty area within the Event Browser GUI.
Select an action in the context menu or open the context menu for the same event again.
Selecting a different event in the Event Browser discards any unsaved changes in the Event Details tabs. If you navigate anywhere from the page (to another application, perspective, or the Filter Manager) or select a CI in the CI Tree View, unsaved changes are discarded.
When editing event details, switching between Event Details tabs does not lose changes and it is possible to navigate back to the original tab and continue editing. However, no change is committed unless Save is clicked for each edited tab.
Solution: Save modifications before switching Event Details tabs or selecting another event in the Event Browser.
When user groups are added or deleted, the change is not visible in the User Assignment dialog in the Event Browser or Event details.
Solution: After the refresh interval of 10 minutes, log off and back on again. The deleted users and groups should now be removed, and any added users and groups should now be available.
If an action (for example, Close, Open, ...) is executed which affects many events, the browser seems not to respond any longer and the
"hour glass" indicates that an action is still in progress. The affected events include the total number of the selected events and their
direct or indirect symptoms, including symptoms with a lifecycle state of CLOSED
.
Solution: Reload the page in the browser by pressing either F5 or by toggling between the Event Perspective and the Health Perspective.
Simultaneous Modification of Events — If several user simultaneously modify the same event, changes override each other as each user saves changes. The changes from the earlier user are lost. No user is informed that another user worked on this event.
Database Transaction Errors — If two users simultaneously change an event, for example, changing lifecycle state, priority, or severity, one action may be discarded due to concurrent modifications on the same database record. One of the two users receives the following error message:
Cannot modify properties of this event.
Closed Events — There are restrictions on the actions that can be executed on closed events. If the event is closed by another user after editing of an event is started, attempting to save the change in event details is the same as trying to edit a closed event. Since properties cannot be changed on closed events, the only change is setting the lifecycle state to that specified in the current edit. All property changes are discarded without any acknowledgment.
Solution:
Changes Overwritten — If your changes are overwritten by another user, ascertain the correct status of the event and update the event details.
Database Transaction Errors — Perform the action again. If possible, for example when editing event details, refresh to ensure that have the most current data before performing the action again.
Closed Events — Re-edit the event if appropriate.
When editing an event in the decomposed Event Details windows, the value of the severity of an event with the severity
value of Unknown
may change to Critical
without user intervention.
Solution: Select desired severity between Normal and Critical.
When the backspace key is used, the previously-selected perspective page is displayed. However, the tab selection is not updated.
Solution: The workaround is to change perspectives by selecting the appropriate tab and not by using the backspace key.
If you make changes to an event in the Event Details window, the changes are displayed immediately in the Event Perspective Details pane. If you make changes to an event from the Event Perspective Details pane, the open Event Details window for the selected event is not updated.
Solution: Close and reopen the Event Details window for the selected event. The changes should now be visible.
When using Event Assignment to direct incoming events to particular groups of users, it is possible that events are not being assigned to the expected users.
This problem is experienced if you have defined filters that have overlapping results. For example one filter searches for a particular host name, and another filter for the domain that this host belongs to, both filters return a valid selection. The chosen selection should be the selection with the smallest order number. However if the mapping rules are rearranged, reordering fails and events may be assign to incorrect user groups.
Solution: To avoid this problem:
Plan the required order of the mapping rules in advance, so as to avoid the need to rearrange.
If the HP Operations Manager for Windows user name is longer than 20 characters, the user name is truncated and the complete name is not displayed in the Event Browser. This occurs when HPOM for Windows is configured to use the UNIX compatibility mode, which truncates the name to accommodate older versions of HPOM for UNIX.
Solution: Set the compatibility mode to false. Refer to the HPOM for Windows online help for instructions.
In the case of a localized system, it is not possible to determine whether IIS or Apache was used
for the installation as the parsing of %TOPAZ_HOME%\dat\install.ini
fails. As a
consequence no virtual directory is created during configuration of HP OMi.
Solution for IIS:
For installations with IIS, complete the following steps:
Look up the IIS Web Site in %TOPAZ_HOME%\dat\install.ini
Open a command prompt.
Execute the command:
cscript %windir%\system32\iisvdir.vbs /create <IISWebSite>\images hiValues %TOPAZ_HOME%\opr\resources\images\hiValues
Where <IISWebSite>
is the Web Site you found in install.ini
and %TOPAZ_HOME%
is the directory where you installed HP OMi.
Solution for Apache:
For installations with Apache, add the following lines to %TOPAZ_HOME%\WebServer\conf\httpd.conf
file:
Alias /images "%TOPAZ_HOME%\opr\resources\images/" <Directory "%TOPAZ_HOME%\opr\resources\images/"> #Options Indexes FollowSymLinks Options FollowSymLinks AllowOverride None Order allow,deny Allow from all <LimitExcept POST GET HEAD> Require valid-user </LimitExcept> <FilesMatch "\.(sh|war|ear|bak|gif|jpg|png)$"> Order allow,deny Allow from all </FilesMatch> </Directory>
Where %TOPAZ_HOME%
is the directory where you installed HP OMi.
After the virtual directory is created, restart BAC.
Microsoft SQL SPI graph generation fails on HP OMi with the error "No Valid Metrics were found to be drawn".
Solution: Perform the following steps to view the graph:
Right click the relevant event and select Configure → Performance graph.
Select the Default Graph check box from the Graph Attribute page of the Design Wizard window and click Next.
Click Add Metrics from the Metric Selection page of the Design Wizard window.
Select Microsoft SQL Instance/Datasource from the Metric Selection dialog box and click Add.
Click Preview from the Metric Selection page of the Design Wizard window to view the graph.
Opening a perspective by selecting the associated tab, deselects the CI originally selected in the CI Tree View.
Solution: Re-select the CI after switching to the new perspective.
After renaming a filter in the Filter Manager, while this filter is in use in one of the Event Browser tabs, the name of the filter is not updated in the browser tabs.
Solution:
Select another filter and then select the changed filter name in the filter drop-down box in the Event Browser.
Select another filter in the selection box after Filter applied: and the new name is set.
When editing an indicator in the Indicators manager the OK button is not enabled even though all fields are valid.
Solution: If the OK button is disabled but all fields are valid, provoke a change in the Display Name field as follows:
Go to the General tab.
Click in the edit field Display Name.
Change the contents of the field, for example, delete the last character and re-enter it.
The OK button should now be enabled.
Health indicators that have been assigned to an event in the past cannot be deleted in the Indicators manager, even when the events are already closed.
Solution: To remove unwanted health indicators from the health perspective, complete the following steps:
Locate the corresponding HI definition in the Indicators manager.
Remove the HI definition from any KPI assignments.
Delete the HI definition with the option to keep the associated event type indicator.
Refresh the Health Perspective GUI.
The corresponding health indicators are no longer shown.
When you create mapping rules using the third page of the Create New Indicator
window or the
third tab of the Edit Indicator
window, in some cases you cannot successfully edit those mapping
rules. For example, when you change a mapping rule, those changes are applied to a different mapping rule.
Solution: Avoid adding too much data to an indicator in one step, especially when you want to add mapping rules. It is recommended that before you edit a mapping rule, you make sure that you have already saved the initially entered data.
For example, when you create a new indicator, you can add general properties, values, and mapping rules. However, even if you want to make changes to the newly created mapping rules, you should first finish the indicator creation. After creating the indicator, open it for editing and make the required changes to the mapping. For editing indicators, see also the release notes entry for QCCR1A91312.
Tool definition for tool type Script does not include 'unix shell script' in the language selection.
Solution: Use the following Perl code:
use FileHandle; my $exe_file = "/tmp/call_sh.sh"; my $str = "#!/sbin/sh echo hello > /tmp/done uname -a >> /tmp/done echo done >> /tmp/done echo command done "; open (FILE1, ">$exe_file"); autoflush FILE1 1; print FILE1 $str; autoflush FILE1 1; close FILE1; system "sh $exe_file";
If there are lots of events in the database, it is possible that the opr-archive-events.bat tool is not able to download or delete them.
Solution: Performance improvements have been implemented for the opr-archive-events tool and are included in the OMI_00007 - OMi Server 08.10.174 Windows patch.
The beginning 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 this web site: HP Software Product Manuals.
To retrieve a document, select the:
Product name.
Version list.
Operating System.
Preferred Language.
Document title.
Click Open or Download.
You must have Adobe Reader installed to view files in the Portable Document Format (*.pdf). To download Adobe Reader, go to the Adobe web site.
This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.
HP 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:
To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.
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: Access levels.
To register for an HP Passport ID, go to:
HP Passport Registration.
©Copyright 2008-2011 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.
The information contained herein is subject to change without notice.
For information about open source license and third-party license agreements, refer to one of the following locations:
\Licenses\Open_Source_Licences
and the
\Licenses\Third-Party_Licences
directories on the product media.
%TOPAZ_HOME%\opr\licenses
directory on the
HP OMi host system.
Adobe® is a trademark of Adobe Systems Incorporated.
Microsoft®, and Windows® are U.S. registered trademarks of Microsoft Corporation.
This product includes software developed by Andy Clark.
This product includes ANTLR.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/).
This product includes software developed by the JDOM Project (http://www.jdom.org/).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http:// www.openssl.org/).
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).
This product includes code licensed from RSA Data Security.
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
© 2008–2011 Hewlett-Packard Development Company, L.P.