HPE Software Forum: Webinars
Share |

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:

 

SiteScope – Application Monitoring Software for Azure Cloud ServicesOpen in a New Window

 

  

 

HPE will be at Mobile World Congress 2017Open in a New Window

HPE will be attending Mobile World Congress 2017 to demonstrate a full range of software solutions for application developers and owners.  MWC will run from February 27 through March 2 in Barcelona, Spain.  You can find the HPE team at HALL 8.1 BOOTH C31.

 

Accelerate Automated Testing with the New Version (14) of HPE Unified Functional Testing & LeanFTOpen in a New Window

Accelerate your software testing automation efforts with the latest major release of HPE’s UFT and LeanFT solutions.  

Version 14 is now available for you. Learn more on what it contains here

blog.jpg

 

New Release - Mobile Center 2.2 and Four Reasons to Get Excited about Mobile Testing!Open in a New Window

HPE Mobile Center 2.2 is now available. Developers, Test Automation Engineers, Mobile Administrators and Business/Application Owners, will find that MC 2.2 has made their respective tasks much easier. Learn more about the new features.

 

Using Selenium for Web Automation? Let UFT Pro (LeanFT) help you!Open in a New Window

Read how LeanFT can help you to create robust Selenium tests, easily and with joy.

OIC4Selenium.png

 

7 Leading UX & Product Experts in 20 Min Short Lectures – Now on YouTube!Open in a New Window

Continuing the successful event that we brought together more than 4000 people live from all around the world, in 6 excellent sessions given by 7 leading experts from across the High tech industry (Microsoft, HPE, Pepper, Photomyne, CrowdX & Healthy.io) sharing knowledge and best practices in short 20 minute TED format talks.

 

What’s New in SiteScope 11.33Open in a New Window

Learn about the newest capabilities and features of SiteScope version 11.33. Support for AWS Autoscaling, integration with Microsoft Azure and AWS, UI Rejuvenation, and more.

 

How to make most of Probe auto-assignment feature in HPE Diagnostics 09.30?Open in a New Window

Configuring auto-assignment with HPE Diagnostics 09.30.

 

Global ALM Octane Hackathon is LIVE: Enter to compete and WIN!Open in a New Window

Enter the worldwide virtual ALM Octane Hackathon with $10k in PRIZES. Hosted by AngelHack and & Hewlett Packard Enterprise

ALM Octane HackathonALM Octane Hackathon

 

Check out the new User Management Console in PPM 9.40Open in a New Window

Every existing and new Hewlett Packard Enterprise Project and Portfolio Management customer can realize efficiencies with the new User Management Console. Just imagine managing user security group assignments or license allocations from the browser rather than the workbench.

PPM 9.40 User4 Managaement ConsolePPM 9.40 User4 Managaement Console

 

 

Simple but impactful benefits of HPE PPM 9.40Open in a New Window

Every new version of HPE Project and Portfolio Management introduces some new usability benefits. Here is a quick summary of what was delivered in PPM version 9.40.

 

HPE ALM Groups>Users. Know who belongs where (or to which group)Open in a New Window

Large group teaser.png

Knowing which ALM users are in which ALM groups, for a single project or all projects, may be essential to maintaining your environment.

 

MF-Test and HPE ALM - Making a Difference in Mainframe Testing and Lifecycle ManagementOpen in a New Window

tester workstation teaser.png

The Israel Ministry of Transport (MOT) decided to expand vehicle registration numbers from 7 to 8 digits with the increase in cars on the road. But this project requires more than simply updating a number. It meant updating mainframe applications as well, while keeping quality high and through maintaining product’s lifecycle well defined for the present and for the future.

 

What’s new in the integration between HPE BPM 9.30 and HPE MobileCenter 2.0?Open in a New Window

BPM integration teaser.png

End user applications are no longer limited to workstations or laptops. The number of handheld devices is increasing and more applications are being developed for them. Learn how to embrace the power within the integration of HPE BPM and HPE Mobile Center.

 

Email delivery after ALM project is upgraded for the users belonging to itOpen in a New Window

There are times where you need to upgrade a project and remove users to perform the work. Now there is an easy way to alert HPE ALM users that upgrades have been performed successfully. Keep reading to learn more.  

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.