Hi yangnigon,
JBoss simply tells that it checks the file /HPBSM/AppServer/deploy/Site/placeholder.txt hasn't been deployed.
This will never happen, as a .txt file cannot be deployed.
On my 9.26 IP2 system I can find in C:\HPBSM\AppServer\deploy\Site\ the file sitetmc-jboss-server.jar,
I guess on your box you will have the same file plus "placeholder.txt"
If your only message about not eployed is on placeholder.zxz, you can ignore it.
Greetings
Siggi
Hi SoniaSinha,
where do you wanna see a different name?
In BSM -> Admin -> SAM -> Summary, as on my screenshot
where the Sitecope instances are listed under Summary?
In that case you need to change the Display Name by right-click on the Instance and then Edit SiteScope, under Main Settings -> Display Name.
If you are talking about another area in BSM, plesase specify.
Greetings
Siggi
I guess I was looking at the wrong direction as you mentioned that all SiteScopes report to BSM, and thus you need to be able to differentiate them in BSM.
Usually people create individual groups to separate monitors by organisations or locations.
Changing the element of the root name from "SiteScope" to anything else cannot be done.
You can of course create a group direclty underneath SiteScope and call it SIteScope_DataCenter_Chicago or whatever.
Greetings
Siggi
Hi Infinity9999,
check out
/t5/SiteScope-Support-Customer-Forum/SiteScope-REST-Examples/td-p/6864596
it shows what you need to do to call a SiteScope API function.
Greetings
Siggi
Hi yangnigon,
the CR
QCCR1I110909 Unable to log in with LDAP after upgrade
unfortunately doesn't contain more details than just
..
After removing the entry with the NULL values and restarting BSM, LDAP users could login fine.
..
To have <NULL> values for the fields SP_SUB_CONTEXT, SP_HOST_ID and SP_VALUE_CLOB can be perfectly fine.
My understanding - based on the very limited CR description - is that you would have two entries or two sets of entries,
while one set contains <NULL> values for the relevant fields, mainly SP_VALUE.
So if you find duplicate entries with same SP_CONTEXT and SP_NAME (SP_ID will be different), but both SP_VALUE and SP_VALUE_CLOB are empty,
these wouöld be the entries to delete.
You need to stop BSM first, create a backup copy of the table, delete the duplicate entries and start BSM
Greetings
Siggi
Hi gmatrozos,
you are talking about the OMi Event Console, and here the Description field of an event, while the event is sent to BSM / OMi from SiteScope.
While I'm not an OMi guy, I checked around and found one case indicating
..
Currently this is not possible in BSM 9.24, but it has been implemented in OMi 10.01.
..
so it seems that BSM / OMi 9.2x is uable to handle HTML tags in the Event Desciption field.
Enhancement Request QCCR8D37113 has been opened to request this functionality in BSM/OMi 9.2x as well, but this has not (yet) been implemented.
Greetings
Siggi
Hi yangnigon,
I'm glad to hear that my suggestions helped to resolve the issue
Greetings
Siggi
Hi Mohamed,
as far as I know you only need the usual BSM license to exeecute a BPM transaction.
For example on my system I use the license of type "Transaction Unlimited Location" for a UFT / QTP script.
Greetings
Siggi
Hi Arunkumar,
as per the SiteScope 11.32 manual "Monitor Reference",
the following Windows OS versions are supported for the Directory monitor:
..
- This monitor supports monitoring remote servers running on the following Windows operating systems:
Windows Server 2003, 2003 R2, 2008, 2008 R2, 2012, 2012 R2 Update 1.
..
so no Windows 7 here.
It might work if you enable your Windows 7 system to communicate with SiteScope via SSH, but it's a "might" only,
I was not able to test tht.
Greetings
Siggi
Hi Robert,
I guess you need to explain your issue in greater detail.
The article at
/t5/SiteScope-Support-Customer-Forum/SiteScope-REST-Examples/td-p/6864596
states as URL for the POST request
http://localhost:8080/SiteScope/api/monitors/monitor/run
plus all the parameter required.
Do you write your own code, or do you use a browser to access the URLs?
You can access the API via a client like Chrome and the POSTMAN Add-On, or other extensions / tools,
or the command line toolset under
<SiteScope>\examples\integrations\api\bin
which is usually my way to start.
For example by executing
C:\SiteScope\examples\integrations\api\bin>get_full_configuration.bat -host myhost -port myport -useSSL false -login myuser -password mypass
..
_enabled: true
_ownerID: 200981110
-----------------------------------------------------
Entity name : CPU sov02bac29.eu.hpecorp.net
-----------------------------------------------------
Entity properties:
_prioritySelection: MEASURMENT
_prevKeyAttrMap: -84.-19.0.5.115.114.0.19.106.97.118.97.46.117.116.105.108.46.65.114.114.97.121.76.105.115.116.120.-127.-46.29.-103.-57.97.-99.3.0.1.73.0.4.115.105.122.101.120.112.0.0.0.0.119.4.0.0.0.10.120.
..
When I use IE I only get this message
Click here to navigate to SiteScope home page
when using the wrong entry point, for example
http://<my_sitescope>.<port_it_runs_on>/api/admin/monitors/status
("/api/admin/monitors/status" instead of "/SiteScope/api/admin/monitors/status")
When I use
http://<my_sitescope>.<port_it_runs_on>/SiteScope/api/admin/monitors/status
I don't get anything back, because the SiteScope API doesn't know what you want,
as "behind" "api/admin/monitors/status" it expects the method / end point, for example
getSiteScopeMonitoringStatusWithIdentifier
and the parameters required,
but that cannot be provided via a plain browser.
Does this help?
Greetings
Siggi
Hi Adr,
have a look at the manual
Using System Health -> Chapter 6: Managing BSM Processes
..
The following table displays the processes that run on the BSM servers:
..
It lists all processes BSM consists of.
You might need to get the real name as reported on the system, for example
dbloader Runs the component on the server which loads the data into the database.
Process name: mercury_db_loader
but on Windows the real process name (which you might need to monitor it) is "hpbsm_db_loader.exe".
C:\HPBSM\AppServer\resources>tasklist | findstr hpbsm
hpbsm_RTSM.exe 11592 Services 0 673,844 K
hpbsm_pmanager.exe 11080 Services 0 174,440 K
hpbsm_marble_loader.exe 4104 Services 0 202,828 K
hpbsm_analytics_loader.ex 8148 Services 0 353,384 K
hpbsm_db_loader.exe 12928 Services 0 216,832 K
hpbsm_marble_worker_1.exe 5948 Services 0 353,216 K
hpbsm_marble_matcher.exe 2064 Services 0 136,736 K
hpbsm_wde.exe 9188 Services 0 447,832 K
hpbsm_marble_supervisor.e 336 Services 0 250,328 K
hpbsm_offline_engine.exe 14464 Services 0 279,896 K
hpbsm_basel_engine.exe 11224 Services 0 188,632 K
hpbsm_opr-scripting-host. 7672 Services 0 240,420 K
hpbsm_pi_engine.exe 11008 Services 0 241,540 K
hpbsm_opr-backend.exe 11920 Services 0 617,180 K
hpbsm_bizImpact.exe 7296 Services 0 112,512 K
plus Nanny, HortnetQ and the webserver
Depending on the Server Deployment and installation type (typical, GW or DPS) you might need to customize the list of processes you monitor.
While BSM can live and will continue to run with some processes being down (for example Partition Manager),
all processes have to be up and running, so every process failing is bad.
Greetings
Siggi
P.S.: Below you'll find a screenshot from Process Explorer showing the usual process of a small single server deplyoment
Hi hp4u,
if your assumption is that the script size is too big to allow BSM to upload it into the script repository, you should encounter an error in BSM while doing so.
Check out
KM00399805 - BSM - Unable to upload huge VuGen script
there the issue was with a 13MB (!) RDP script, but the reason and resolution might be the same.
Greetings
Siggi
Hi Neetoo,
for such kind of questions the SiteScope manual set is your best friend.
Check out this one:
HPE SiteScope Software Version: 11.32 Monitor Reference
Chapter 22: Database Query Monitor
..
Supported Platforms/Versions
This monitor supports monitoring on any database with a valid JDBC driver that supports SQL queries.
..
So all you need to find is a suitable JDBC driver which support Oracle 12c,
for example via
http://www.oracle.com/technetwork/database/features/jdbc/jdbc-drivers-12c-download-1958347.html
Then
..
You must install or copy a compatible JDBC database driver or database access API into the required
SiteScope directory location.
Many database driver packages are available as compressed (zipped) archive files or .jar files. Copy the
downloaded driver file into the <SiteScope root directory>\WEB-INF\lib subdirectory. If the file is in zip
format, unzip the contents to a temporary directory. Stop and restart the SiteScope service after copying
the driver file to the SiteScope machine.
..
and you are done.
If you are looking at specific Oracle monitor:
Oracle 10g Application Server Monitor, Oracle 9i Application Server Monitor
they obviously don't support Oracle 12
but this one does:
Chapter 75: Oracle Database Monitor
Supported Platforms/Versions
The monitor supports monitoring server performance statistics from Oracle Database 8i, 9i, 10g, 11i, 11g R2
(11.2.0.1), 11g R2 Real Application Clusters (RAC), and 12c (12.1.0.1) servers.
Greetings
Siggi
Hi Infinity9999,
..
how to send the Post data in a REST URL call.
..
Understood.
..
I'm assuming that for the runExistingMonitorEx example,
the body just has to be "fullPathToMonitor=TopLevel_sis_path_delimiter_SecondLevel_sis_path_delimiter_ThisIsMyMonitor".
..
No, as per the API description the dfinition of the API call is
..
runExistingMonitorEx
The runExistingMonitorEx method runs the monitor. The monitor must be deployed before invoking this method.
REST End Point
/api/monitors/monitor/run
Method POST
Form Parameters
fullPathToMonitor– A string specifying the full path to the monitor. The path starts with the
name of the first child under the SiteScope root directory and ends with the name of the
monitor with path elements separated by the string "_sis_path_delimiter_".
timeOut– Timeout value in milliseconds.
identifier – Identifier to be associated with the operation and written to audit log.
Return Type
A HashMap representation of the status of the run and the status message as it would
appear on the UI.
Status Codes 200, 400, 500
..
..
Right now, when I use the command
Invoke-RestMethod -uri http://user:password@1.1.1.1:8080/Sitescope/api/monitors/monitor/run -method Post -body {"<monitor path>"}
I get the error:
Invoke-RestMethod : HTTP Status 405 - HTTP method POST is not supported by this URL
..
To be honest, I tried for the last two days to get this working, and failed badly.
This is really strange, as I had this working before.
I also tried with earlier versions of SiteScope, but get the same error.
I used PostMan with
http://<my_host>:<myport>/SiteScope/api/monitors/monitor/run
Authentication
Basic
<SiteScope_admin_username>
<SiteScope_admin_password>
Header
Content-Type:application/x-www-form-urlencoded
(I also tried "Content-Type: multipart/form-data" and "Content-Type:application/json")
Body : form_data
fullPathToMonitor : Test_sis_path_delimiter_ping (or also "Test/ping" or "Test\ping" or SiteScope\Test\ping")
timeOut : 5000
identifier : Siggi_via_API
and POST method
When I use
"Content-Type: multipart/form-data"
or
"Content-Type:application/json"
I get the famous error 415,
when I use
"Content-Type:application/x-www-form-urlencoded"
I get
HTTP 400 and
"Error Code: 55200. Error Description: Invalid path to group. Group could not be found : [Ljava.lang.String;@2ebdb3b7"
I also tried with Powerhsell using this cmdlet:
..
$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Content-Type","application/x-www-form-urlencoded")
$mybody = @{
fullPathToMonitor = "Test/ping"
timeOut = "50000"
Identifier = "Siggi"
}
$myjson = $mybody | ConvertTo-Json
$response = Invoke-RestMethod -uri 'http://<user>:<pass>@sov02bac15.eu.hpecorp.net:18080/Sitescope/api/monitors/monitor/run' -method Post -headers $headers -body $myjson
but only get
Invoke-RestMethod : HTTP Status 405 - HTTP method POST is not supported by this URL
At the moment I'm without a clue, but will check into this deeper until I find the solution (has to be something really trivial!)
Greetings
Siggi
Hi Adr,
the Query is for pre-BSM 9 times (BAC 8 and before) and yes, it will no longer work in BSM 9,
as the profile database table structures have changed.
if HP provided the query to you, I would expect that you also can get an updated version from them?
You can check KCS document
KM1165162 - BSM 9.x Database Schema changes
to review some of the changes.
In any case, here is a list of obvious changes:
EVENT_METER is now BPM_TRANS, most of the field names didn't change, some have been added, some other might have been deleted
[SAMPLETIME]
,[TUID]
,[DBDATE]
,[CUSTOMER_ID]
,[INTERNAL_TRANSACTION_ID]
,[INTERNAL_LOCATION_ID]
,[SCRIPT_ID]
,[BPM_AGENT_ID]
,[INTERNAL_SUBNET_ID]
,[SERVER_IP]
,[SERVER_NAME]
,[STATUS_ID]
,[EM_ID]
,[EM_RESULT_VALUE]
,[EM_PAGE_CBD_COUNT]
,[EM_DOWNLOAD_DATA_SIZE]
,[EM_W_CONNECTION_TIME]
,[EM_W_DNS_TIME]
,[EM_W_SSL_TIME]
,[EM_W_NETWORK_TIME]
,[EM_W_NETWORK_FB_TIME]
,[EM_W_SERVER_FB_TIME]
,[EM_W_DOWNLOAD_TIME]
,[EM_W_RETRY_TIME]
,[EM_S_CONNECTION_TIME]
,[EM_S_DNS_TIME]
,[EM_S_SSL_TIME]
,[EM_S_NETWORK_TIME]
,[EM_S_NETWORK_FB_TIME]
,[EM_S_SERVER_FB_TIME]
,[EM_S_DOWNLOAD_TIME]
,[EM_S_RETRY_TIME]
,[BASELINE_RESP_TIME_MEAN]
,[BASELINE_RESP_TIME_STD]
,[BASELINE_RESP_TIME_LOC_MEAN]
,[BASELINE_RESP_TIME_LOC_STD]
,[BASELINE_DOWNLOAD_TIME_MEAN]
,[BASELINE_DOWNLOAD_TIME_STD]
,[BASELINE_SERVER_TIME_MEAN]
,[BASELINE_SERVER_TIME_STD]
,[BASELINE_FIRSTBUF_TIME_MEAN]
,[BASELINE_FIRSTBUF_TIME_STD]
,[BASELINE_NETWORK_TIME_MEAN]
,[BASELINE_NETWORK_TIME_STD]
,[TOT_OK_HITS]
,[TOT_MINOR_HITS]
,[TOT_CRITICAL_HITS]
,[DOWNTIME_STATE]
,[ERROR_COUNT]
,[AVAILABILITY_STATUS]
Hoever, with BSM 9 the concept and the way of storing TRANSACTION and LOCATION information has changed dramatically. The tables don't exist anymore, but have been replaced by multiple others, and the way accessing the data has changed dramatically, but lucky enoguh we do have the *_DIM tables.
I checked the sample data you attached:
you can get to the transaction name via
<profile_db>.BPM_TRANS.INTERNAL_TRANSACTION_ID = <profile_db>.TRANSACTION_DIM.INTERNAL_TRANSACTION_ID
field name holding the transaction name is TRANSACTION_DIM.TRANSACTION_NAME
you can get to the location name via
<profile_db>.BPM_TRANS.INTERNAL_LOCATION_ID = <profile_db>.LOCATIONS_DIM.INTERNAL_LOCATION_ID
field name holding the location name LOCATIONS_DIM.LOCATION_NAME
Overall I guess your query should work
SELECT BPM_TRANS.SAMPLETIME ,TRANSACTIONS_DIM.TRANSACTION_NAME ,BPM_TRANS.STATUS_ID ,BPM_TRANS.EM_RESULT_VALUE ,BPM_TRANS.DBDATE
FROM BPM_TRANS,TRANSACTIONS_DIM,LOCATIONS_DIM
WHERE BPM_TRANS.INTERNAL_TRANSACTION_ID = TRANSACTIONS_DIM.INTERNAL_TRANSACTION_ID AND BPM_TRANS.INTERNAL_LOCATION_ID = LOCATIONS_DIM.INTERNAL_LOCATION_ID
That's from one of my test systems (I only retrieved top 10 results)
SAMPLETIME TRANSACTION_NAME STATUS_ID EM_RESULT_VALUE DBDATE
1472116260.000000 Step 0 - Google 1 1418 2016-08-25 11:12:29.787
1472116294.000000 Step 0 - Start JPetStore 0 2526 2016-08-25 11:12:29.787
1472116268.000000 Green 0 5000 2016-08-25 11:12:29.787
1472116278.000000 Yellow 0 10007 2016-08-25 11:12:29.787
1472116296.000000 Step 1 - Login 0 1913 2016-08-25 11:12:29.787
1472116296.000000 Step 2 - Order a bird 1 8 2016-08-25 11:12:29.787
1472111267.000000 tx Rand Availability 0 2984 2016-08-25 09:48:39.097
1472116317.000000 Step 0 - Start JPetStore_SOE 0 2554 2016-08-25 11:13:19.803
1472116319.000000 Step 1 - Login_SOE 0 1944 2016-08-25 11:13:19.803
1472116319.000000 Step 2 - Order a bird_SOE 1 5 2016-08-25 11:13:19.803
BTW, I have no idea where to find
TRANSACTIONS.RANK_1_FROM ,TRANSACTIONS.RANK_1_TO
Hope it gives you a start anyway
Siggi
Hi yangnigon,
the password is stored in the SESSIONS table in the Management database, but as far as I understood it cannot be decrypted.
It is a one-way encrpytion, so when you enter the password, it gets encrypted and compared to the encrypted string stored in the database
(as it was written there ncrypted when the profile DB was created in BSM).
So while you can get hold of the password, you cannot use it, as you cannot decrypt it.
Greetings
Siggi
Hi yangnigon,
> It sounds like there's no way of retrieving actual password once it's forgotten. Please correct me if this statement is wrong.
this is correct.
At least I don't know a way $arrogance_filter on$ so I would guess that there is none $arrogance_filter off$
As Dmitry stated
> No need to re-create a new schema. It's enough just to change password on the existing schema while keeping all data collected intact.
you can change the password via the GUI, AFTER your DBA changed the password and told you what it is.
Your follow-up question somehow goes into a different direction.
..
If I created a new profile database with changed password AND changed SID on the existing schema,
is it going to impact the all data collected intact?
(The end goal is to keep everything with different SID)
..
Aaah, this is what you are looking at:
changing the password and the SID of an exisiting profile database.
correct?
Check the BSM Disaster Recovery steps in the Installation manual,
Appendix E: Disaster Recovery for BSM,
Switch references in the Sessions table on the management database of the DR environment to
the backup databases.
It shows you how to change the information for the profile db,
and it will only change the access to the data (he way BSM accesses the profile db, no matter whether you change the host, the SID, the username, whatever)
Internally BSM wouldn't recognize the difference, thus accessing the data would work without problems.
Greetings
Siggi
Hi niravu,
this is a question for your AIX SysAdmins.
As SiteScope logs into the remote server and executes commands, these commands are logged by the shell built-in mechanism.
I use this quite often to track what commands are executed on a system on behalf of a specific monitor.
You simply need to approach your AIX SysAdmin and check if / how this feature can be disabled, or use Google and check yourself.
Perhaps it's a per-user setting perhaps it's a per shell setting, perhaps it's a per session setting, no idea.
But it's nothing you can configure in SiteScope, as long as it's not a simple shell coammand you can use as initial command when SiteScope logs into the remote server.
Greetings
Siggi
Hi SK3210,
I found a similar report for BSM 9.24,
there the answer from R&D was:
please see what's written in the Hardening Guide:
..
Using Basic Authentication in BSM
The BSM platform fully supports the basic authentication schema, which provides BSM with the
ability to authenticate a client communicating with a BSM server via HTTP or HTTPS.
The basic authentication schema is based on the client sending its credentials to the server so that
the server can authenticate the client. The client’s credentials are sent in a Base64 encoding format
and are not encrypted in any way. If you are concerned that your network traffic may be monitored
by a sniffer, it is recommended that you use basic authentication in conjunction with SSL. This
sends the client’s credentials over an encrypted wire (after the SSL handshake has been
completed).
For information on configuring the BSM platform to support SSL communication, see "Using SSL in
BSM" on page 39.
So the only solution here is use SSL.
Also by passing Web Server (using port 8080) is not a good practice for accessing BSM.
Customer should use port 443 and web server will provide to jboss decoding credentials.
..
by no way you are supposed to update packages which are delivered as part of BSM, like Apache Web Server or alike.
Greetings
Siggi
Hi ADR,
it seems that this informarion moved to the BSM Management database table EUMBPM_TRANS
(so not the profile database!):
..
RANK_1_FROM INT NOT NULL,
RANK_1_TO INT NOT NULL,
..
RANK_1_FROM_ROLL INT NULL,
RANK_2_FROM_ROLL INT NULL,
BASEL_RANK_UPPER_LIMIT NUMERIC(24,6) NULL,
..
AVAIL_THRESHOLD INT DEFAULT 90000 NOT NULL,
..
BASEL_RANK_LOWER_LIMIT NUMERIC(24,6) NULL);
..
Greetings
Siggi