HPE Software Blog: All About the Apps
Share |

Throwback Tuesday! What was new in the February ALM Octane releaseOpen in a New Window

HPE ALM Octane – Why it's great!

Agile adoption is soaring, fueled by the need to rapidly innovate, respond to threats, and achieve the faster cycles demanded by modern business apps. HPE ALM Octane is our flagship modern platform for lifecycle and quality management to deliver innovative applications with quality at scale. HPE ALM Octane is designed specifically to help customers manage and accelerate their Software Development Lifecycle and supports DevOps, Agile, or traditional Waterfall methodologies. The end user experience of HPE ALM Octane is designed from the ground up to be simple, responsive, and serve the platforms and form factors that practitioners use—browsers, tablets or mobile devices.

 FEb 1.png

 

ALM Octane What's New! April EditionOpen in a New Window

HPE ALM Octane – Traceability and Quality! In recent years the software development industry has undergone a rapid transition from waterfall-based methodologies to more agile-based methodologies.  Although this has greatly increased an organizations ability to deliver software more quickly, it has created additional complexities in maintaining high levels of product quality and made development traceability more difficult.  Octane was specifically engineered to not only natively support enterprise agile development but also support agile quality at scale along with software development traceability in a single, unified platform.    

Title Menu.png

 

Light up your image with reds and greensOpen in a New Window

During the troubleshooting process many challenges will arise, like problem isolation, triaging, and finger pointing across technology tiers teams.

Learn to represent your data in Hewlett Packard Enterprise Application Performance Monitoring/Business Service Management.

 

My Impressions from the latest Selenium conference in AustinOpen in a New Window

The HPE team has just returned from an exciting week at the Selenium conference in Austin. Keep reading to hear our favorite parts, what we learned and what major misconception we cleared up for the attendees.1 (2).jpg

 

 

 

 

 

 

 

Unrevealed tricks of Integrating HPE AppPulse Active with HPE APMOpen in a New Window

BPM BSM Plugin for APA teaser.png

 

HPE Application Performance Monitoring and AppPulse Active now have an integration for proactive monitoring. Keep reading to get some “Never before seen” tricks of the integration.

 

SiteScope Amazon Web Services Monitor (AWS) - Auto Scaling and Dynamic FeatureOpen in a New Window

My previous blog “SiteScope AWS Agentless Monitoring” discussed on how to configure an AWS monitor in SiteScope. In this blog, I will highlight the top use cases for the Auto Scaling and Dynamic nature of the AWS monitor.  

With the SiteScope 11.33 version, AWS monitor was enhanced to a dynamic and browsable monitor in addition to supporting the auto scaling feature of AWS.

 A browsable monitor  enables you to browse  the available counters/metrics for the monitor and select the ones  that you want to display onthe SiteScope dashboard.

 Dynamic monitoring is a way to automatically adjust the SiteScope monitoring configuration based on changes that are happening in your IT environment. You can define regular expressions based on which monitors can automatically update themselves over time by adding and removing counters as changes occur in the system. For example, counters/metrics will be removed as the instances are stopped/deleted from system. ). In addition, you can select counter patterns to be used as threshold conditions. In this way, thresholds are also updated automatically when the counters are updated.

 Use Case 1: Support  Auto Scaling feature of Amazon

 The Auto Scaling feature of Amazon Web Services helps maintain application availability and allows to scale the Amazon EC2 instances up or down automatically according to pre-defined conditions.

 Earlier versions of SiteScope supported monitoring Amazon EC2 instances that are up and running at the time of the monitor creation.

 With SiteScope 11.33, the AWS monitor supports refreshing the AWS monitor counters automatically to reflect the EC2 environment accurately as it scales up or down. The monitor can be configured once and then left to automatically discover any changes in the monitored EC2 environment and update itself.

 Consider an environment where I have instances 1, 2, and 3 on AWS up and running at the time of monitor creation. Let us assume the monitor run frequency is set at 1 minute interval. Suppose I provide a regular expression </.*/By Instance Id/.*/State/> for monitoring. Any volumes/instances matching the regular expression are displayed on the Sitescope dashboard. Next, I add a new instance 4 to the environment. On the next monitor run, the counters matching the regex from the new instance 4 will be dynamically detected and reported to the SiteScope dashboard. And suppose I delete instance 2, then on the next monitor run the status of the counters fetched from instance 2 are displayed as “stopped” on the SiteScope dashboard when it is refreshed.Running instances of AWSRunning instances of AWS

 Select the regex and monitor run frequencySelect the regex and monitor run frequency

SiteScope Dashboard showing all the running instances matching the regexSiteScope Dashboard showing all the running instances matching the regex

AWS console with a “stopped” instanceAWS console with a “stopped” instance

SiteScope dashboard refreshed to display status of the stopped instanceSiteScope dashboard refreshed to display status of the stopped instance

Use Case 2: SiteScope monitors aggregated statistics as provided by Amazon CloudWatch

Amazon CloudWatch provides statistics based on metric data with aggregations such Minimum, Maximum, Sum, Average and Sample Count.

Prior to the 11.33 release, SiteScope retrieved the average statistic data based on the aggregation groups,  “image ID”, “Instance Type” and “All Instances”.

With  the11.33 release, the monitor is enhanced to  obtain  the Minimum, Maximum and Average statistics data for the supported aggregation groups (“image ID”, “Instance Type” and “All Instances”).

 This means as a SiteScope user, you can:

  • Monitor the maximum, minimum and average values of relevant metrics in AWS environment grouped by “image ID”, “Instance Type” and “All Instances”.
  • Configure alerts on number of instances when the system is scaling up/down automatically.
  • Get usage statistics on EC2 environment.
  • Get notified when the system is scaling up/down automatically.
  • View the relevant statistics on the dashboard and reports.

6.png

Use Case 3: Reports include graphs/details on all dynamically refreshed counters

The following screenshot shows that the SiteScope report  lists all metrics/counters that will be displayed on SiteScope dashboard as per the selected regular expressions.

7.png

Use Case 4: Build calculated expressions using any of the dynamic expressions that the new AWS monitor allows in monitor definition

All the regular expressions are listed in the calculated metrics. Calculated metric is a metric produced by performing an arithmetic function or logical operation on existing SiteScope metrics. The calculated metric then appears in the Thresholds Settings panel, enabling you to configure thresholds based on that metric.

For example, you can create a calculated metric to calculate the average of two or more existing metrics for a monitor instance, and then configure a threshold that triggers an alert if that average exceeds a certain number.

When creating a calculated metric expression for dynamic monitors, you can use both static metrics (for which you can use calculated metrics normally, without using patterns), and you can use regular expressions that are part of the dynamic monitor’s configured patterns.

Example:

To calculate the total CPU Utilization of all instances in AWS, create a calculated metric expression that is the sum of all metrics created from /.*/CPU Utilization/ as follows:

SUM(<</.*/CPU Utilization MB free/>>)

Note: You can use only one regular expression per calculated metric that is not part of a function (that is, a calculated metric that returns only one result).

8.png

Use Case 5: AWS monitor allows any of the dynamic expressions used in monitor definition to be selected for threshold definition

You can also select counter patterns to be used as threshold conditions. Thereby, thresholds are also updated automatically when the counters are updated.

The thresholds list always contains the counter patterns that were defined in the counters pattern table (not the final counters that were found). The values in this list are updated according to changes you make in the counter patterns table.

9.png

Explore and Connect

Stay up-to-date with the latest news on Twitter.

 You Might Also Like:

 

Using KeyStore Explorer to exchange trusted certificates between RUM and APM ServersOpen in a New Window

The information in this document is useful when you create HTTPs communication between a RUM Engine server and an APM/BSM server. Detailed steps for generating and exchanging certificates are described in the RUM Hardening Guide. This document showcases the use of an external tool, KeyStore Explorer, to add trusted self-signed certificates to the RUM Engine as well as APM Gateway servers. KeyStore Explorer is an open source GUI replacement for the Java command-line utilities keytool and jarsigner. KeyStore Explorer presents their functionality, and more, via an intuitive graphical user interface. This can be used freely under the terms of GNU General Public License version 3. Being a visual tool, KeyStore Explorer enables easy analysis and modifications of TrustStores, thereby simplifying the overall hardening process.

Prerequisites:

By default, the RUM Engine connects to the APM Gateway server using HTTP connections (and vice versa). This connection can be hardened to use HTTPS. Enabling HTTPS between any client and a server involves the following tasks:

  • Getting the server to work with HTTPS connections and, in the process, serve up its public certificate
  • Getting the client to trust the certificate served by the server

For the first task, refer to the Hardening Guides for APM and RUM:

  • APM 9.31 Hardening Guide (Chapter 4)
  • Real User Monitor 9.31 Hardening Guide (Chapter 7)

The steps listed below explain how the second task (Getting the client to trust the certificate served by the server) can be easily accomplished. 

Exporting APM/BSM Certificate

Step 1

Open the supported browser and browse to the server with HTTPS as shown in the examples below.

https://<hostname>:443/topaz/ (Replace <hostname> with your server name – BSM/APM Server name)

https://<hostname>:8443/rumwebconsole/ (Replace <hostname> with your server name – Data collectors like RUM)

Step 2

a.    Click the Certificate section as shown in the screenshot below. A Certificate window appears.

       converted.jpg

b.    Click the Details tab.

c.    Click Copy to File.

d.    Click Next.

e.    Select Base 64 encoded x.509 (.CER).

      base64image.jpg

 f.    Click Next.

g.    Click Browse and enter a meaningful name (e.g., APM_cert) to save the file locally.

h.    Click Next.

i.     Click Finish to save the file. The export was successful message appears.

  okButton.jpg

Importing the APM/BSM Certificate into the RUM Engine

Step 3

Copy the saved/downloaded certificate (e.g., APM_cert) to the RUM Engine server.

Step 4

Download KeyStore Explorer from the internet. (The current version is 5.2.2) and install it on the RUM Engine server.

Step 5

Open KeyStore Explorer which is installed in the RUM Engine server and click Open an existing KeyStore. If you are unable to open KeyStore Explorer by double-clicking, issue the following command in a command prompt under c:\Program Files (x86)\KeyStore Explorer 5.2.2:

java -jar kse.jar
kse_commandPrompt.png

Step 6

When you click Open an existing KeyStore, you will be asked to browse to the location of the KeyStore. For RUM, it is in <RUM_HOME>\JRE\lib\security\cacerts.

Step 7

Enter the KeyStore password. For the default KeyStore password, search the APM 9.31 Hardening Guide for the default value of “storepass”.

Step 8

a.    When the KeyStore for the cacerts opens, drag and drop the APM_cert to the KeyStore window and click Import.

b.    Keep the Enter Alias field intact and click OK.

modifiedKSE.jpg

 

Step 9

a.    Click OK in the Import screen and make sure that the certificate is imported in the KeyStore.

b.    Click Save.

modified2.jpg

 

Step 10

Close the KeyStore Explorer window and restart the RUM Engine services.

Step 11

a.    In RUM, click Configuration > APM Configuration Settings. The Application Performance Management Connection Settings page appears.

b.   Click Test RTSM password. A pop-up message appears that confirms a successful HTTPS connection between APM/BSM to RUM Engine.

 modified3.jpg

Exporting the RUM Certificate

To complete the HTTPS settings, you need to export the certificate from the RUM Engine server and import it to APM/BSM server.

Step 12

Download the RUM Engine certificate as described in Step 1 and Step 2. Browse to the RUM Engine server URL using HTTPS.

https://<hostname>:8443/rumwebconsole (Replace ‘hostname’ with RUM Engine Server name)

Importing the RUM Engine Certificate to APM/BSM:

Step 13

Install KeyStore Explorer in the APM/BSM server. In the KeyStore Explorer, open cacerts which is located in the <APM HOME >/JRE/lib/security folder and drag and drop the RUM certificate as described in Step 8 and Step 9.

Step 14

You also need to update the RUM certificate for cacerts which is located in the <APM HOME>/JRE64/lib/security folder. (cacerts file under both JRE and JRE64 should be updated with RUM certificate)

Step 15

Restart the APM/BSM services in the Gateway server. The two way communication for the RUM Engine to APM/BSM is in place.

Validation

a.    Step 11 validates a successful HTTPS connection from the RUM Engine to the BSM/APM server.

b.    To validate the connection from BSM/APM to the RUM Engine, on BSM/APM, try to open the RUM Session Analyzer report which is located under Applications > End User Management. The report is displayed if you have populated data. Otherwise you will see a No data message. Either of these outputs indicate that there is successful HTTPS communication between the servers.

c.    If there are problems with the connection, you will see an error as shown below. 

 httpsError.jpg

d.    You can refer to the ‘config.manager’ log file under C:\HPRUM\log for RUM and the 'gdeGatewayClient' log file under C:\HPBSM\log for BSM/APM to validate that both servers work seamlessly over HTTPS.

Other Notes:

If you have internal restrictions around installing KeyStore Explorer on the RUM Engine or APM/BSM servers, you can install it on any other server. In that case, you need to download the cacerts file from the RUM and BSM/APM servers, import the relevant certificates, and replace the updated cacerts file in the corresponding file location on each server.

 

4 Steps to ALM automation with automated testingOpen in a New Window

Customers have been asking for a simple way to automate Hewlett Packard Enterprise Application Lifecycle Management and thanks to HPE Unified Functional Testing automated testing software it is now easier than ever.

 

AppPulse Spring Release is now AvailableOpen in a New Window

HPE’s AppPulse Spring 2017 release is now available. It supports Mobile Sentiment Analysis, Monitoring SPA pages, and tracing Asynch calls. In this release, customers will get the AppPulse Trace Express version for FREE with AppPulse Active, Mobile, and Web, providing the visibility needed to find and fix app problems faster by investigating issues from the user action down to the line of code, exception, and log messages.

 

Real User Monitoring (RUM) for Single Page & Session SnapshotsOpen in a New Window

HPE Real User Monitoring (RUM) enables viewing both a single page & session snapshots for HTTP based applications.  Learn how

 

ALM Octane 12.53.20 ReleasedOpen in a New Window

ALM Octane continues its evolution in becoming an industry-leading product with frequent updates and strong integrations to DevOps products including third-party development, source code management, and build tools.  ALM Octane has had 8 releases/upgrades in the last 10 months with the next major release scheduled for June 2017 (subject to change).
ALM OctaneALM Octane

 

 

 

Announcement: HPE Project & Portfolio Management (PPM) version 9.41 is now availableOpen in a New Window

The latest version of HPE Project & Portfolio Management, version 9.41, is now available. 

Glad to be here! This was a phrase used by a former “Blue Angels” pilot, John Foley - in a Keynote session that I had the opportunity to hear him speak. Continue reading to learn more about the Blue Angles and...

Learn about the new updates and why PPM 9.41 can help your team reach success in the Digital Transformation era. 

 Blue Angels: an example of Strategy, Plan, and TeamworkBlue Angels: an example of Strategy, Plan, and Teamwork

 

 

 

 

 

 

 

 

Basic Custom Instrumentation for the HPE Diagnostics Java AgentOpen in a New Window

Many application servers and frameworks are supported by the default instrumentation provided by HPE Diagnostics Java Agent. Customers may have a need to instrument their own application classes, or entry points for the frameworks not covered by default. This blog presents the basics of the instrumentation of Java applications and provides some examples.

 

Mobile World Congress 2017 Wrap-up from Barcelona #MWC17Open in a New Window

I just got back home from my trip to Mobile World Congress 2017 in Barcelona, Spain. I was amazed with the size of the conference, one of the largest ones that I have attended, beating any other in terms of sessions, expo and attendees. It was around 108,000 people and 9 expo areas in 400,000 m2 at the Fira Barcelona event space.

Read the Mobile World Congress wrap-up report with impressions and news from the show. What’s new, interesting, HOT, and why it’s okay that the event has moved past “mobile”

p0.jpg

 

Dynamic Docker Monitoring with HPE SiteScope Now Available on the Docker StoreOpen in a New Window

The Dynamic Docker Monitor from HPE SiteScope is now available on the Docker Store. It provides monitoring of your Docker environment so that you can understand how it is performing in real-time.   Learn more

 

SiteScope Content Pack for SAP HANAOpen in a New Window

 

Capgemini, HPE’s Channel Partner, continues to add to the rich repertoire of SiteScope monitors with its latest addition of the SAP HANA Monitor. The SAP HANA monitor for SiteScope provides agentless monitoring capability for your SAP HANA instance. The custom monitor for SAP HANA can be installed as an add-on to your existing SiteScope instance.

Key features

  • Agentless monitoring of SAP HANA instance, requires no installation on SAP HANA host
  • Very small footprint and easy to install and configure
  • Add-in to SiteScope, can be installed without any impact on SiteScope instance already running
  • Leverages HPE SiteScope features such as alerts, reports and analysis
  • Enables monitoring over various aspects such as Connections, Disk Usage, Memory Usage, System, Cache,
           Workload, and Services with real time metrics. Full-featured version offers around 100+ SAP HANA metrics
           from different monitoring aspects.

Flavors

  • Evaluation version
  • Full featured version
  • Customized version

Contact the Capgemini team at info.hln.ig@capgemini.com for a copy of the evaluation version. 

Deployment Environment

  • Windows 64 bit / Linux 64 bit System
  • Site Scope Server 11.33 up and running
  • HANA DB content package

4 simple steps to monitor your SAP HANA instance!

Step 1: Copy the SAP HANA Driver

Copy the Sap Hana Driver (ngdbc.jar) to lib folder at <SiteScope_Install_Directory>/WEB_INF/lib. Restart the SiteScope server.

Note: The SAP HANA Driver (ngdbc.jar) is installed as part of the SAP HANA client and is located at:

  • <Install_Dir>\Program Files\sap\hdbclient\ (Microsoft Windows)
  • /usr/sap/hdbclient/ (Linux and UNIX platforms)

Step 2: Import the Content Package

Log in to SiteScope as an administrator. Select the Templates context. In the template tree, right-click the template container into which you want to import the content package and click Import > Content Package. Browse to the location where you saved the content package and select the content pack. The SAP HANA Template is imported and available under the group container.pic1.pngpic2.png

Note: You will need to enter the password for the full version of the content package, which is provided at the time of purchase.

Step 3: Provide the Deployment Values

Provide the Server Name, System Number, Database Username and Database password of HANA Database and click OK.

Step 4: Run the monitor

Run the monitor to retrieve the metrics for the various SAP HANA monitors. The metrics are displayed on the SiteScope Dashboard.HANACacheMonitorHANACacheMonitorHANAConnectionAndDatabaseMonitorHANAConnectionAndDatabaseMonitorHANADiskUsageMonitorHANADiskUsageMonitor HANAServicesMonitorHANAServicesMonitor

Explore

Stay up-to-date with the latest news on Twitter.

Also, read the blog Manage your Mongo with SiteScope to know the details about the MongoDB content pack from Capgemini for managing your MongoDB database using SiteScope. 

You might also like to:

 

 

 

SiteScope 11.33 integration with OMi 10.12Open in a New Window

 

SiteScope integration with OMi

Our previous article discussed the SiteScope integration with APM 9.30. We will continue to discuss SiteScope integrations with this blog covering details on how to configure the SiteScope integration with OMi.

Before you get started

Ensure you have the following before you start:

  • SiteScope 11.33 installed, up and running!
  • Typical or distributed OMi 10.12 environment.
  • Appropriate licenses for SiteScope and OMi.
  • Install Operations Agent (OA) for sending events to OMi.

Note that one instance of SiteScope can be integrated with one instance of OMi. Whereas, a single instance of OMi can be integrated with different instances of SiteScope.

Prerequisite steps for OMi 10.12 on Linux

  1. Log in to the OMi 10.12 server.
  2. Navigate to the following path and back up the sitescope.zip file. <Install_Dir>/opt/HP/BSM/odb/conf/factory_packages/

Note: If OMi 10.12 is in a distributed environment, the log in to the Data Processing Server and navigate to the path <Install_Dir>/opt/HP/BSM/odb/conf/factory_packages/ and back up the SiteScope.zip file

3. Extract the SiteScope.zip file from the SiteScopePackages/Omi_10.12_package.zip folder which is available with the SiteScope 11.33 bits
.1.png2.png

4. Copy the extracted SiteScope.zip to the path 

<Install_Dir>/opt/HP/BSM/odb/conf/factory_packages/

5. Open the URL in a browser on the same APM machine: 

https://localhost:8443/jmx-console/HtmlAdaptor?action=inspectMBean&name=UCMDB:service=Packaging%20Services#deployPackages

The JMX console login page is displayed.

6. Enter the credentials that were configured during the OMi setup

7. Select “Deploy Packages” from the list of actions.

8. In the “packagesNames” field enter SiteScope.zip. The other fields can be ignored and left as is.

9. Click Invoke to deploy the package. On the next page, the deployed resources are displayed. If there is an error in deployment, an error message is displayed.

Note: The same prerequisite steps need to be performed for integration of SiteScope 11.32 IP2 with OMi 10.12.

Prerequisite steps for OMi 10.12 on Windows

  1. Log in to the OMi 10.12 server.
  2. Navigate to the following path and back up the sitescope.zip file. <Install_Dir>\HP\BSM\odb\conf\factory_packages\

Note: If OMi is in a distributed environment, the log in to the Data Processing Server and navigate to the path <Install_Dir>\HP\BSM\odb\conf\factory_packages\ and back up the SiteScope.zip file.

3. Extract the SiteScope.zip file from the SiteScopePackages/Omi_10.12_package.zip folder which is available with the SiteScope 11.33 bits
.1.png2.png

4. Copy the extracted SiteScope.zip file to the path 

<Install_Dir>/HPBSM/odb/conf/factory_packages/

5. Open the URL in a browser on the same APM machine: 

https://localhost:8443/jmx-console/HtmlAdaptor?action=inspectMBean&name=UCMDB:service=Packaging%20Services#deployPackages

The JMX console login page is displayed.

6. Enter the credentials that were configured during the OMi setup.

7. Select “Deploy Packages” from the list of actions.

8. In the “packagesNames” field enter SiteScope.zip. The other fields can be ignored and left as is.

9. Click Invoke to deploy the package. On the next page, the deployed resources are displayed. If there is an error in deployment, an error message is displayed.

Note: The same prerequisite steps need to be performed for integration of SiteScope 11.32 IP2 with OMi 10.12.

Install Operations Agent (OA) on SiteScope

  1. Download and install OA 11.14 on the SiteScope server. For information to install OA, refer the OA Installation Guide at:

https://community.hpe.com/hpeb/attachments/hpeb/itrc-162/174556/1/agent_install_guide_11.14.pdf

 2. After installing OA successfully on SiteScope machine, check the status of OA using the command:

On windows

Open Command Prompt and execute the below command:

opcagt –status

On Linux

Go at path: cd /opt/OV/bin

Execute the command:

./opcagt –status

The output of the command shows the running status of OA.

3.png

3. Go to path <SiteScope_Installed_Dir>/bin/  and run the config_tool.bat (for Windows SiteScope) or config_tool.sh (for Linux SiteScope)

4. Select the option Configure HP Operations Agent installed separately.

4.png

5. Click Next. The following message is displayed “HP SiteScope will be configured with OA now.”

6. Verify the status of OA using the command.

Windows

Open Command Prompt and execute the below command:

opcagt –status

Linux

Go to path: cd /opt/OV/bin

Execute the following command:

./opcagt –status

The output of the command shows the status of SiteScope configuration with OA as running.

5.png

With this, you are all set to integrate SiteScope 11.33 with OMi 10.12 for sending Metrics, Topology and Events to OMi from SiteScope.

Start Integrating!

  1. Open the SiteScope URL and navigate to Preferences > Integration Preferences and select new HP Operations Manager Integration.6.png
  2. Provide the fully qualified domain name for OMi server and click Connect. This sends a certificate to the OMi server.7.png
  3. Open the OMi server URL from a browser. Click Setup > Maintenance > Certificate Requests. 
    Accept the request.8.png

    The status should change from ‘Granted’ to ‘Succeeded’.9.png

  4. Log in to SiteScope. Go to Preferences > Integration Preferences > HP Operations Manager Integration. The HP Operations Manager Integration Main Settings page is displayed.
  5. Make the following selections to configure the integration settings. Click Install Policies.10.png

Once the policies are installed successfully, you are done with the integration! Congratulations on successfully completing the integration of SiteScope 11.33 with OMi 10.12.

 We will proceed to highlight some issues that will help you troubleshoot the integration.

 Troubleshooting

  • Verify if integration is successful
    Send a sample message/test event to OMi 10.12 from SiteScope. Go to OMi > Workspace > Event Perspective and check if the message/event has been received.
    11.png
  • Verify if OMi 10.12 certificate is sent to SiteScope
            Run the following command on the SiteScope server from the Command prompt window

              ovcert –list

    12.png

    • Move the OMi integration to a different server       
             
      Perform the following steps to clear the previous OMi server configuration from OA manually.

 a. Remove the certificates with the following command.
Note: Before removing the certificates, it is recommended that you list the certificates first so that you know the correct ones to remove.

ovcert -list

b. Run the following command for all IDs in the output.

ovcert -remove <id>
13.png

c.  Remove the old OMi server details using the following command:

ovconfchg -ns -clear -all

d.  Restart OA.

ovc -kill

ovc -start

  • Remove the corrupted certificates and resend them.

Remove the certificate using the below command:

ovcert –remove <id>

 Resend the certificate using the command:

ovcert –certreq

  • View configuration of all the core IDs of OMi and SiteScope on OA.

Run the following command from the command prompt.

ovconfget
14.png

Run the following command to change these configurations. It opens up a text file that can be edited and saved.

ovconfchg –edit
15.png

  • Topology is not being reported to RTSM

-If SiteScope 11.33 is already integrated with OMi 10.12, verify if the steps listed in Pre-requisites for OMi 10.12 for Linux or Windows platform are performed. It is important to restart SiteScope after deploying the package for the new scripts to be available in SiteScope.

-If the new SiteScope.zip package available with the 11.33 bits is not imported then Topology will not be reported to RTSM in OMi 10.12

-If you get the following log snippet in the discovery.log file (located at path <SiteScope_Install_Dir>/logs/bac_integration/discovery.log)
16.png

 Perform the steps listed in the pre-requisites for deploying the SiteScope.zip package. After the new sitescope.zip package is imported, restart SiteScope server to report topology to OMi.

 

Explore

Stay up-to-date with the latest news on Twitter.

You might also like to:

 

7 ways to understand and optimize your end-users’ journeyOpen in a New Window

Think about end user teaser.jpg

 

Mobile and application end-users want speed. If your load times are more than four seconds or if it takes more than two seconds to move from screen to screen, they will stop using your application.

Find out what seven things you need to consider to optimize your end-user’s journey.

 

SiteScope AWS Agentless MonitoringOpen in a New Window

 

Cloud computing is no longer a distant possibility for many firms – it is an immediate reality. Every day, more firms are moving an increasingly large portion of their IT infrastructure into cloud environments and reaping substantial benefits as a result.

 For such companies, it's critical to develop the best possible strategy for maximizing the advantages that cloud computing can deliver. There are many factors that must go into an effective approach, but one of the most important – and frequently overlooked – is monitoring. With high-quality monitoring in place, a company will be well-positioned to gain the most value from its cloud investments.

Using SiteScope for Agentless Monitoring of AWS

HPE’s SiteScope tool is able to monitor your Amazon Web Services (AWS) cloud resources, starting with Amazon Elastic Compute Cloud service (EC2) and Amazon Virtual Private Cloud (VPC). It provides data on resource utilization, operational performance, and overall network demand patterns.

Data collected from AWS-hosted applications can also be reported to Amazon CloudWatch using the Amazon CloudWatch integration. This data can then be used for AWS AutoScaling, reporting and alerting.

How to Configure the AWS Monitor

Here are some prerequisites that you will need to get started creating your new Amazon Web Services monitor:

  • A valid subscription to Amazon Web Services
  • Access Key ID 
            Access Key can be viewed from the Users tab on the Amazon Account screen.
  • Secret Access Key
           It is important to copy this key at the time of creating a new key. After creating the new key, you cannot view it any    more. Therefore, ensure to copy the key at the time of creating it.
  • Region
            Region is displayed on the right-hand top corner on the title bar of the Amazon Account screen.

Create the AWS monitor

  1. Log in to SiteScope.
  2. Configure the SiteScope AWS monitor.
  3. Select the metrics that you would like to view.
  4. Save and run the monitor                                              

Access Key on AWSAccess Key on AWS

AWS Monitor SettingsAWS Monitor Settings

                                                               
                                               Metrics by Groups on AmazonMetrics by Groups on Amazon

 Counters/Metrics under the same grouping as on AmazonCounters/Metrics under the same grouping as on Amazon

                   

Counters on AmazonCounters on Amazon

 

Metrics Displayed on the Amazon DashboardMetrics Displayed on the Amazon Dashboard

  Metrics displayed on the SiteScope DashboardMetrics displayed on the SiteScope Dashboard If you thought monitoring a cloud-based application used to be a challenge, you can now see that it doesn’t need to be with SiteScope. SiteScope provides you with powerful features to monitor your cloud based application and infrastructure with ease, in an AWS environment and other environments as well. 

My next article will cover a more advanced scenario. I’m adding auto scaling into the equation and showing you how to monitor a cloud-based application when you have auto scaling in your AWS environment.  Stay tuned for the next blog on how SiteScope AWS integration has dynamic monitors that handle auto scaling.

 Explore and Connect

Stay up-to-date with the latest news on Twitter.

 You Might Also Like:

 

SiteScope 11.33 integration with APM 9.30 – The nuts and bolts of itOpen in a New Window

 

SiteScope Integration with APM
So you have installed the brand new SiteScope 11.33 and APM 9.30 and are rearing to go. But are you having sleepless nights as you foresee messy integration bottlenecks? Not anymore. This blog tutorial is intended to give you simple step-by-step instructions to have the integration up and running flawlessly.

Before you get started

Ensure you have the following before you start:

  • SiteScope 11.33 installed, up and running!
  • Typical or distributed APM 9.30 environment
  • Appropriate licenses for SiteScope, APM, and SAM Reports & Administration.

Note that one instance of SiteScope can be integrated with one instance of APM. Whereas, a single instance of APM can be integrated with different instances of SiteScope.

Prerequisite steps for APM 9.30 on Linux

1. Log in to the APM 9.30 server.

2. Navigate to the following path and back up the sitescope.zip file.

<Install_Dir>/opt/HP/BSM/odb/conf/factory_packages/

Note: If APM is in a distributed environment, the log in to the Data Processing Server and navigate to the path

<Install_Dir>/opt/HP/BSM/odb/conf/factory_packages/ and back up the sitescope.zip file

3. Extract the sitescope.zip file from the SiteScopePackages/APM_930_package.zip folder which is available with the SiteScope 11.33 bits.

    scb1.jpg

     scb2.jpg

4. Copy the extracted sitescope.zip file to the path

<Install_Dir>/opt/HP/BSM/odb/conf/factory_packages/

5. Open the URL in a browser on the same APM machine:

https://localhost:8443/jmx-console/HtmlAdaptor?action=inspectMBean&name=UCMDB:service=Packaging%20Services#deployPackages

The JMX console login page is displayed.

6. Enter the credentials that were configured during the APM setup.

7. Select Deploy Packages from the list of actions.

8. In the packagesNames field enter sitescope.zip. The other fields can be ignored and left as is.

9. Click Invoke to deploy the package. On the next page, the deployed resources are displayed. If there is an error in deployment, an error message is displayed.

 

Prerequisite steps for APM 9.30 on Windows

1. Log in to the APM 9.30 server.

2. Navigate to the following path and back up the sitescope.zip file.

<Install_Dir>\HP\BSM\odb\conf\factory_packages\

Note: If APM is in a distributed environment, the log in to the Data Processing Server and navigate to the path

<Install_Dir>\HP\BSM\odb\conf\factory_packages\ and back up the sitescope.zip file

3. Extract the sitescope.zip file from the SiteScopePackages/APM_930_package.zip folder that is available with the SiteScope 11.33 bits.

   scb3.jpg

   scb4.jpg

4. Copy the extracted sitescope.zip file to the path

<Install_Dir>/HPBSM/odb/conf/factory_packages/

5. Open the URL in a browser on the same APM machine:

https://localhost:8443/jmx-console/HtmlAdaptor?action=inspectMBean&name=UCMDB:service=Packaging%20Services#deployPackages

The JMX console login page is displayed

6. Enter the credentials that were configured during the APM setup.

7. Select Deploy Packages from the list of actions.

8. In the packagesNames field enter sitescope.zip. The other fields can be ignored and left as is.

9. Click Invoke to deploy the package. On the next page, the deployed resources are displayed. If there is an error in deployment, an error message is displayed.

Start Integrating!

With the prerequisites in place you are all set to integrate SiteScope with APM.

1. Launch APM 9.30 from a web browser.

2. Navigate to Admin > System Availability Management.

3. Click New SiteScope button under Summary.

4. Enter the data for all mandatory fields and click Submit.

scb5.jpg

On successful integration, the integration is listed under “Summary” in System Availability Management. You can view the integration from SiteScope in Preferences > Integration Preferences.

scb6.jpg

Troubleshooting

SiteScope 11.33 is already integrated with APM 9.30 but Topology is not being reported to RTSM

Perform the steps listed in Pre-requisites for APM 9.30 for Linux or Windows platform. It is important to restart SiteScope after deploying the package for the new scripts to be available in SiteScope.

Topology not being reported to RTSM in APM 9.30 

If the new sitescope.zip package available with the SiteScope 11.33 version is not imported then Topology will not be reported to RTSM in APM 9.30. Import the package and restart the SiteScope server.

You encounter the following log snippet in the discovery.log file                                          (<SiteScope_Install_Dir>/logs/bac_integration/discovery.log)

scb7.jpg

Perform the steps listed in the prerequisites section above for Windows or Linux, as relevant. After importing the new sitescope.zip package, restart the SiteScope server to report Topology to APM.

Integration of SiteScope 11.32 IP2 with APM 9.30
Perform the steps listed in the prerequisites section above for Windows or Linux, as relevant, before you start the integration.

Stay up-to-date with the latest news on Twitter.

You Might Also Like:

Contact Us

Vivit Worldwide
P.O. Box 18510
Boulder, CO 80308

Email: info@vivit-worldwide.org

Mission

Vivit's mission is to serve
the Hewlett Packard
Enterprise User
Community through
Advocacy, Community,
and Education.