- This app can be installed either through UI from “Manage Apps” or by extracting the compressed file into $SPLUNK_HOME$/etc/apps folder
- Restart Splunk
- Before installing the new version if you have made any custom changes to ip_subnets lookup or app’s navigation bar make sure you backup ip_subnets.csv (located at: $SPLUNK_HOME$/etc/apps/BNW-app-powerconnect/lookups/ip_subnets.csv) and app’s navigation bar XML file (located at: $SPLUNK_HOME$/etc/apps/BNW-app-powerconnect/local/data/ui/nav/default.xml).
- If you are upgrading PowerConnect app from version 6.2.0 and have followed the first way of updating queries through UI given in the following KB document – https://www.powerconnect.io/wiki/kb-098-cpu-memory-and-availability-gauges-displayin g-0-values-v-6-2-0-bug/, then there would be a copy of the file sap_system_ovw.xml in $SPLUNK_HOME/etc/apps/bnw-app-powerconnect/local/data/ui/views directory. Remove this file from the location and then follow the steps below.
- Install the app through UI from “Manage Apps” > “Install app from file”.
- Restart Splunk
- From “Manage Apps” click on the “Set Up” link beside BNW-app-powerconnect entry. Follow the steps given in the following document to complete the Set up: https://www.powerconnect.io/wiki/kb-104-pc-splunk-app-setup-page-guide-6-3-0/
- After performing above mentioned installation/upgrade steps, configure the indexes to be accessible by admin and all other users and roles who will be accessing this application.
- The Lookups need to be populated with the event data. This step is required to be performed only once as there are separate savedsearches scheduled to run every hour for appending new items to existing lookups from new events and for some cases it’s only to populate static data in the lookup for once only. There are two ways to complete this step:
- Open the dashboard “Wizard for New SAP SIDs and Instances Discovery” under PowerConnect menu. Select the checkbox corresponding to the savedsearches name and click on the “Run Searches” button. The status of the search would get updated in the Status column of the table and the user can view the search results once the search has completed by clicking in the table cell. The step would be complete when all the searches specified in the table have completed execution successfully with the exception of “Cloud CPI Source – Lookup Gen – Run Once Only” search. This search should only be run if the user wants to use the “SAP Cloud – CPI Message Monitoring” dashboard.
- On Splunk’s menu bar, Click on Settings -> “Searches, reports, and alerts” and manually run all the savedsearches with the suffix ” – Run Once Only”. In case of a large number of events, if savedsearch execution does not get completed, try to reduce the time range and populate the lookups.
Optional Configuration (SAP Cloud product support):
- If the user wants to use “SAP Cloud – CPI Message Monitoring” dashboard, the user needs to enable the saved search “Cloud CPI Source – Lookup Gen”. The steps to enable the savedsearches are:
- On Splunk’s menu bar, Click on Settings -> Searches, reports, and alerts.
- Search for “Cloud CPI Source – Lookup Gen”.
- Click on “Edit” dropdown under “Actions” and click on “Enable”.
Optional Configuration (German or Japanese language support):
- The app version 6.4.0 supports German and Japanese languages apart from English. By default, Splunk automatically uses the language that the user’s browser is set to. To switch languages, either the browser’s locale setting can be changed or for a given Splunk session it can be changed by modifying the URL that you use to access Splunk. For different languages use the URL as specified:
- American English:
- British English:
*(Replace the placeholder in the URL)
Note: In case the dashboard is not getting shown in the expected language after going to the appropriate URL, the user should clear the browser cache and refresh the dashboard.
Note: Description works for Splunk version 7.3.x and above