HPE AppPulse Mobile. Software Version: 2.1. IT Operations Management Integration Guide

Transcription

1 HPE AppPulse Mbile Sftware Versin: 2.1 IT Operatins Management Integratin Guide Dcument Release Date: Nvember 2015

2 Cntents Overview: The IT Operatins Management Integratin 3 System Requirements 3 Hw t Integrate HPE AppPulse Mbile Metrics With BSM 3 BSM License 4 Step 1: Open a Ticket 4 Step 2: Install the Plug-In 4 Step 3: Cnfigure AppPulse Mbile 5 Step 4: Cnfigure the Plug-In 5 Step 5: Cnfigure BSM 5 Changing the Client Secret r Disabling the Integratin 6 Advanced Cnfiguratin and Supprt 6 What Can I See in BSM? 6 URL Pattern Gruping 7 Custm Gruping 8 Trubleshting 8 URLs missing in BSM 8 Hw t Integrate HPE AppPulse Mbile Events With OMi 9 Step 1: Open a Ticket 9 Step 2: Install the Plug-In 9 Step 3: Cnfigure AppPulse Mbile 10 Step 4: Cnfigure the Plug-In 10 Step 5: Cnfigure BSM Cnnectr 10 Step 6: Cnfigure the App Name in OMi (if needed) 11 Changing the Client Secret r Disabling the Integratin 11 Advanced Cnfiguratin and Supprt 11 Hw t Update the Plug-In 12 HPE AppPulse Mbile (2.1) Page 2 f 14

3 Overview: The IT Operatins Management Integratin The IT Operatins Management integratin enables yu t view metrics and events frm AppPulse Mbile, within BSM and OMi 10.x. T d this, yu need t install the AppPulse-BSM plug-in, which cnnects between the SaaS and n-prem envirnments. This dcument describes hw t set up the BSM and OMi integratins separately; hwever if yu have installed the plug-in fr ne integratin it can be used fr the ther as well. System Requirements The integratin requires that yu install the AppPulse-BSM plug-in. The BSM integratin requires that yu pen prt 8180 n the plug-in t receive incming requests frm BSM. The OMi integratin des nt need any inbund prts frm the internet. The plug-in is a lightweight cmpnent that cnnects between the SaaS and n-prem envirnments; it therefre des nt require significant prcessing. The minimum requirements are 40Gb free disk space, 4Gb RAM, and 2 cres. The supprted OSs are Linux and Windws 64 bit. Hw t Integrate HPE AppPulse Mbile Metrics With BSM This sectin describes hw t integrate HPE AppPulse Mbile with HPE Business Service Management (BSM 9.24 and higher), in rder t view data frm yur mbile app in BSM reprts. This dcument assumes yu are already wrking with BSM. IT Operatins can use the AppPulse-BSM integratin t manage mbile applicatin health using BSM Service Health, Alerts, and applicatins reprts, while the Line Of Business teams can utilize the benefits f the AppPulse Mbile interface itself. Fr details abut the BSM reprts relevant fr the integratin, see "What Can I See in BSM?" n page 6. The integratin prcess invlves the fllwing: "BSM License" n the next page "Step 1: Open a Ticket" n the next page "Step 2: Install the Plug-In" n the next page "Step 3: Cnfigure AppPulse Mbile" n page 5 "Step 4: Cnfigure the Plug-In" n page 5 "Step 5: Cnfigure BSM" n page 5 HPE AppPulse Mbile (2.1) Page 3 f 14

4 BSM License The IT Operatins Management integratin is supprted fr BSM 9.24 and higher. Once yu have an AppPulse Mbile license, the integratin is free f charge. If yu have BSM 9.26 IP1 r higher, n licensing is required. Please cntact HPE SaaS Supprt if yu are using earlier versins f BSM supprted by the integratin. Step 1: Open a Ticket Open a ticket with HPE SaaS Operatins, and tell them yu want t set up an integratin between AppPulse Mbile and BSM. HPE SaaS Operatins will enable the HPE IT Operatins Management Integratin UI in yur AppPulse Mbile tenant, and send yu the AppPulse-BSM plug-in t install. Step 2: Install the Plug-In T enable the integratin, install the AppPulse-BSM plug-in in yur n-prem BSM envirnment. This des nt need t be installed in the DMZ; it will be used t pull data frm the SaaS envirnment. The plug-in will cnnect t BSM as a data cllectr. T install the plug-in: 1. Unzip the AppPulse-BSM plug-in files in yur BSM envirnment. 2. On the plug-in hst, run the fllwing: \AppPulse-BSM-Plug-In\bin\InstallService.bat (r InstallService.sh fr Linux). Here's an architecture diagram: Nte that there is a slight lag in data arrival: The data cllectin frequency is 5 minutes, and data is aggregated every 5 minutes, s the ttal lag is typically arund up t 10 minutes. Fr security purpses, we recmmend setting up a reverse prxy between the plug-in and AppPulse Mbile. HPE AppPulse Mbile (2.1) Page 4 f 14

5 Step 3: Cnfigure AppPulse Mbile 1. Within AppPulse Mbile, using administratr permissins, access Settings > Integratins > HP IT Operatins Management. (If yu dn't see this ptin, cntact HPE SaaS Operatins and verify that they enabled the integratin.) 2. Click Generate Client Secret. This creates a client ID, and a client secret. 3. Cpy the client ID and secret, as well as yur tenant ID; yu will need them in the next step. Nte that yu will nt be able t retrieve the secret after yu clse the dialg bx! If yu clse the dialg yu can create a new secret, but that will invalidate the riginal ne. 4. Select the applicatins whse data yu want t see in BSM, and save yur selectin. Step 4: Cnfigure the Plug-In 1. Within the unzipped AppPulse-BSM plug-in files, edit the file cnf\cnfiguratin.jsn as fllws: a. Within the bsmsettings area, enter the fllwing: enginename. Enter the name with which the plug-in is registered in BSM. httpsettings > hst. Enter the BSM hst name. b. Within the apppulsesettings area, enter the fllwing: clientid. Enter yur client ID. tenantid. Enter yur tenant ID. clientsecretplaintext. Enter the client secret generated in the previus step. Nte: If yu change these settings at any pint, yu must restart the plug-in fr the changes t take effect. 2. Run the fllwing t start the service: \AppPulse-BSM-Plug-In\bin\StartService.bat (r StartService.sh fr Linux). Verify in the Task Manager that the AppPulse-BSM-Plug-In service has started. The client secret is nw encrypted and n lnger visible. Step 5: Cnfigure BSM 1. Within BSM, create a RUM Mbile Applicatin (Admin > EUM > RUM Mbile Applicatin) fr each f the apps yu are mnitring in the integratin. Chse Mbile Applicatin in the template name, and click Next. 2. When yu define the Mnitring Settings > Applicatin Key in BSM, enter the applicatin key that is already defined fr the app within AppPulse Mbile. (Yu can find this in AppPulse Mbile, in the app's settings.) Fr example, here is the applicatin key in AppPulse Mbile, which we will enter in BSM: HPE AppPulse Mbile (2.1) Page 5 f 14

6 Nte that the threshlds defined in BSM n the RUM tab have n effect. The nly threshlds that are used fr this app in BSM are thse that are defined in AppPulse Mbile. 3. When yu define the Mnitring Settings > Engine in BSM, select the AppPulse-BSM plug-in which will cllect data frm AppPulse Mbile. (This is the enginename that yu previusly inserted int the cnfiguratin.jsn file.) Yu can nw see data frm AppPulse Mbile in yur BSM reprts, as described in "What Can I See in BSM?" belw. Changing the Client Secret r Disabling the Integratin Befre yu generate a new client secret r revke a secret, stp the plug-in service by running the cmmand \AppPulse-BSM-Plug-In\bin\StpService.bat (r StpService.sh fr Linux). If yu d nt stp the service yu will be lcked ut fr an hur. T generate a new secret, access Settings > Integratins > HP IT Operatins Management, and click Generate New Client Secret. Yu then enter the new secret in the plug-in files and restart the service as described in "Step 4: Cnfigure the Plug-In" n the previus page. T disable a secret, access Settings > Integratins > HP IT Operatins Management, and click Revke Client Secret. The integratin will be disabled until yu cnfigure it using a new secret. T disable the integratin cmpletely, select Cancel Integratin. Advanced Cnfiguratin and Supprt If yu need infrmatin n advanced cnfiguratin and hardening, r if yu have any prblems setting up the integratin, please pen a ticket at HPE SaaS Supprt. What Can I See in BSM? After setting up the integratin, yu can see infrmatin abut yur mbile apps within the Service Health applicatin, and in the fllwing BSM reprts: Actin Summary Reprt Actins Over Time Reprt HPE AppPulse Mbile (2.1) Page 6 f 14

7 Applicatin Health Reprt a. Availability and lad ver time (applicatin status) b. Perfrmance and lad ver time (applicatin status) c. Dmain and lcatins (sessin status) d. Sessins ver time (vlume and prblems) e. Alerts cunt ver time Applicatin Summary Reprt RUM Mbile Health Reprt a. Gegraphic/Lcatin perfrmance and availability b. Dmains c. HTTP Requests Send RUM Applicatin Alert URL Pattern Gruping When reprting mbile applicatin netwrk activity, AppPulse Mbile sends URLs t BSM that are displayed in the fllwing reprts: Actin Summary Reprt, Actins Over Time Reprt, and RUM Mbile Health Reprt (HTTP Requests sectin). T prevent flding BSM with unnecessary URLs and t help maintain security, AppPulse Mbile masks dynamic parameters, and grups URLs based n their patterns. URL parameters are masked as fllws: Befre: After: URL paths use the fllwing default gruping rules: 1. UUID gruping: Befre: After: 2. Hash IDs: Befre: 132c.js After: 3. File names: Befre: HPE AppPulse Mbile (2.1) Page 7 f 14

8 132c.js After: Custm Gruping In sme cases, additinal custm gruping rules are needed t mask all the dynamic parts f a URL - fr example URLs with nn-standard IDs such as s AppPulse Mbile reprts a maximum f 200 gruped URLs per applicatin; if this limit is exceeded, new URLs that d nt match any existing grup are thrwn. If yu want t create a custm gruping that applies t yur particular applicatin, please cntact HPE SaaS Supprt. Trubleshting URLs missing in BSM If BSM is nt displaying all the URLs yu expect t see in the Actin Summary Reprt, Actins Over Time Reprt, and RUM Mbile Health Reprt, this may be a result f default masking rules nt being effective fr yur applicatin. See "URL Pattern Gruping" n the previus page fr mre details, and cntact HPE SaaS Supprt t create custm gruping rules fr yur applicatin. HPE AppPulse Mbile (2.1) Page 8 f 14

9 Hw t Integrate HPE AppPulse Mbile Events With OMi This sectin describes hw t integrate HPE AppPulse Mbile with HPE Operatins Manager i (OMi 10.0 and higher), in rder t view AppPulse Mbile alerts as events in OMi. (This dcument assumes yu are already wrking with OMi and BSM Cnnectr.) The integratin prcess invlves the fllwing: "Step 1: Open a Ticket" belw "Step 2: Install the Plug-In" belw "Step 3: Cnfigure AppPulse Mbile" n the next page "Step 4: Cnfigure the Plug-In" n the next page "Step 5: Cnfigure BSM Cnnectr" n the next page "Step 6: Cnfigure the App Name in OMi (if needed)" n page 11 Step 1: Open a Ticket Open a ticket with HPE SaaS Operatins, and tell them yu want t set up an integratin between AppPulse Mbile and OMi. HPE SaaS Operatins will enable the HPE IT Operatins Management Integratin UI in yur AppPulse Mbile tenant, and send yu the AppPulse-BSM plug-in t install. Step 2: Install the Plug-In T enable the integratin, install the AppPulse-BSM plug-in in yur n-prem BSM envirnment. This des nt need t be installed in the DMZ; it will be used t send data frm the SaaS envirnment t OMi using the BSM Cnnectr. T install the plug-in: 1. Unzip the AppPulse-BSM plug-in files in yur BSM envirnment. 2. On the plug-in hst, run the fllwing: \AppPulse-BSM-Plug-In\bin\InstallService.bat (r InstallService.sh fr Linux). Here's an architecture diagram: HPE AppPulse Mbile (2.1) Page 9 f 14

10 Nte that there is a slight lag in data arrival, which may take up t 5 minutes. Fr security purpses, we recmmend setting up a reverse prxy between the plug-in and AppPulse Mbile. Step 3: Cnfigure AppPulse Mbile 1. Within AppPulse Mbile, using administratr permissins, access Settings > Integratins > HP IT Operatins Management. (If yu dn't see this ptin, cntact HPE SaaS Operatins and verify that they enabled the integratin.) 2. Click Generate Client Secret. This creates a client ID, and a client secret. 3. Cpy the client ID and secret, as well as yur tenant ID; yu will need them in the next step. Nte that yu will nt be able t retrieve the secret after yu clse the dialg bx! If yu clse the dialg yu can create a new secret, but that will invalidate the riginal ne. Step 4: Cnfigure the Plug-In 1. Within the unzipped AppPulse-BSM plug-in files, edit the file cnf\cnfiguratin.jsn as fllws: a. Within the misettings > bsmcnnectrhttpsettings area, enter the fllwing: hst: Enter the hst name f the machine n which the BSM Cnnectr is installed. prt: Enter the BSM Cnnectr prt that is pen fr the AppPulse Mbile alerts. b. Within the apppulsesettings area, enter the fllwing: clientid: Enter yur client ID. tenantid: Enter yur tenant ID. clientsecretplaintext: Enter the client secret generated in the previus step. Nte: If yu change these settings at any pint, yu must restart the plug-in fr the changes t take effect. 2. Run the fllwing t start the service: \AppPulse-BSM-Plug-In\bin\StartService.bat (r StartService.sh fr Linux). The client secret is nw encrypted and n lnger visible. Step 5: Cnfigure BSM Cnnectr 1. In the BSM Cnnectr UI, click the imprt buttn. 2. In the dialg bx that pens, brwse t the cnf\mi\plicies directry in the unzipped AppPulse- BSM plug-in files. 3. Select the fllwing files and click Open: 5880b f2-83ba-4632b9e7b7f8_data 5880b f2-83ba-4632b9e7b7f8_header.xml HPE AppPulse Mbile (2.1) Page 10 f 14

11 4. A new plicy called AppPulse Mbile is added t BSM Cnnectr and is displayed in the BSM Cnnectr UI. 5. Select the new plicy in the UI, right-click it and then click Activate. Step 6: Cnfigure the App Name in OMi (if needed) Fr an event t be crrelated t a CI in OMi, the applicatin name in AppPulse Mbile must be identical t a CI name in OMi. By default we try t link t an existing business applicatin CI with the same name as the app. If yu d nt have such a CI already, create a business applicatin within OMi RTSM Admin whse name is the same as the AppPulse Mbile app name. Alternatively, mdify the BSM Cnnectr plicy t crrelate the event t anther CI in OMi. This mapping can be custmized using the BSM Cnnectr UI. Triggered alerts frm AppPulse Mbile will nw be displayed in yur OMi Event Cnsle. Nte: Sample data is lcated in the cnf\mi\sample_data.xml file in the unzipped AppPulse-BSM plug-in files. Changing the Client Secret r Disabling the Integratin Befre yu generate a new client secret r revke a secret, stp the plug-in service by running the cmmand \AppPulse-BSM-Plug-In\bin\StpService.bat (r StpService.sh fr Linux). If yu d nt stp the service yu will be lcked ut fr an hur. T generate a new secret, access Settings > Integratins > HP IT Operatins Management, and click Generate New Client Secret. Yu then enter the new secret in the plug-in files and restart the service as described in "Step 4: Cnfigure the Plug-In" n the previus page. T disable a secret, access Settings > Integratins > HP IT Operatins Management, and click Revke Client Secret. The integratin will be disabled until yu cnfigure it using a new secret. T disable the integratin cmpletely, select Cancel Integratin. Advanced Cnfiguratin and Supprt If yu need infrmatin n advanced cnfiguratin and hardening, r if yu have any prblems setting up the integratin, please pen a ticket at HPE SaaS Supprt. HPE AppPulse Mbile (2.1) Page 11 f 14

12 Hw t Update the Plug-In If yu have already installed the AppPulse-BSM plug-in (fr either integratin) and want t update it with a new versin, perfrm the fllwing steps: 1. Run the fllwing t stp the service: \AppPulse-BSM-Plug-In\bin\StpService.bat (r StpService.sh fr Linux). 2. Run the fllwing t uninstall the service: \AppPulse-BSM-Plug- In\bin\UnInstallService.bat. 3. Make a backup cpy f the fllwing files: \AppPulse-BSM-Plug-In\cnf\cnfiguratin.jsn \AppPulse-BSM-Plug-In\AppPulse-BSM-Plug- In\persistency\persistent\persistence.jsn \AppPulse-BSM-Plug-In\AppPulse-BSM-Plug-In\cnf\cmmn\key flder 4. Delete the riginal plug-in files and flders lcated inside \AppPulse-BSM-Plug-In\. 5. Extract the new plug-in files t the riginal lcatin. 6. Cpy the backup files: persistence.jsn and cmmn\key flder, and place them in their crrespnding lcatins in the new plug-in installatin. 7. Run the fllwing t install the service: \AppPulse-BSM-Plug-In\bin\InstallService.bat (r InstallService.sh fr Linux). 8. Within the new plug-in files, edit the file cnf\cnfiguratin.jsn based n the backup yu just created. (Fr details, see "Step 4: Cnfigure the Plug-In" n page 5.) 9. Run the fllwing t start the service: \AppPulse-BSM-Plug-In\bin\StartService.bat (r StartService.sh fr Linux). Verify in the Task Manager that the AppPulse-BSM-Plug-In service has started. Fr OMi Integratins nly: After yu cmplete the abve steps, perfrm the fllwing: 1. Within BSM Cnnectr, deactivate the AppPulse Mbile plicy, and then delete the plicy. 2. Imprt the new plicy frm \AppPulse-BSM-Plug-In\cnf\mi\plicies, and then activate the new plicy. Fr details see "Step 5: Cnfigure BSM Cnnectr" n page 10. HPE AppPulse Mbile (2.1) Page 12 f 14

13 Legal Ntices Warranty The nly warranties fr Hewlett Packard Enterprise prducts and services are set frth in the express warranty statements accmpanying such prducts and services. Nthing herein shuld be cnstrued as cnstituting an additinal warranty. HPE shall nt be liable fr technical r editrial errrs r missins cntained herein. The infrmatin cntained herein is subject t change withut ntice. Restricted Rights Legend Cnfidential cmputer sftware. Valid license frm HPE required fr pssessin, use r cpying. Cnsistent with FAR and , Cmmercial Cmputer Sftware, Cmputer Sftware Dcumentatin, and Technical Data fr Cmmercial Items are licensed t the U.S. Gvernment under vendr's standard cmmercial license. Cpyright Ntice Cpyright 2015 Hewlett Packard Enterprise Develpment LP Trademark Ntices Apple is a trademark f Apple Cmputer, Inc., registered in the U.S. and ther cuntries. Ggle and Andrid are registered trademarks f Ggle Inc. HPE AppPulse Mbile (2.1) Page 13 f 14

14 HPE AppPulse Mbile (2.1) Page 14 f 14