Originally posted on IBM Developer blog “Exploring PureApplication System, Software Service and more” by Tom Bal on 11 September 2015 (6723 visits)
Most customers have multiple cloud group or multiple environment profiles with externally managed cloudgroups, – to segregate production from non-production instances, to support a cloud service for different departments, … – and within every cloud group, they provide some shared services.
It’s very likely they might even have created a so-called custom monitoring situation or a personal workspace. As these artifacts are not transferrable through the IBM PureApplication GUI, how can I get my favorite situation (i.e. monitor launching vi) and the workspace transferred from one of my cloud groups to the monitoring portal in the other cloud groups as a way to promote custom monitoring situation from within one environment to another, from non-production to production?
In this example we explain you how to export, delete and import a custom situation using the command line interface provided with the PureApplication monitoring shared service.
1. Login to the monitoring server as the sysadmin OS level user (password set at service creation time):
2. Go to /opt/IBM/ITMSS/bin and execute:
./tacmd login -s localhost -u sysadmin
and if you don’t add a password, you need to provide it at the prompt.
result:
KUIC00007I: User sysadmin logged into server on https://localhost:3661.
“KUIC00007I: User sysadmin logged into server on https://localhost:3661.”
3. Then issue:
./tacmd bulkExportSit
If you don’t provide a path where the artifacts should be exported to, it’ll take the current working directory just make sure you have the rights to create a directory “Bulk” at the working location or the one you specified. If not, please make sure you export to a location where you have those rights.
Result:
KUIBSE015I: All of the situations were successfully exported from the managed server at https://localhost:3661 to the application-specific subdirectories of /opt/IBM/ITMSS/bin/Bulk/SITUATION." (55E83D90.0011-1:kbbssge.c,52,"BSS1_GetEnv") HOME="/home/sysadmin
5. The Bulk directory will contain (in my case only Situations):
Situation subdirectory (extract):
S1:
KS1_Avg_Meeting_Startup_Long..xml KS1_Large_Number_User_Logins.xml KS1_Server_Login_Long.xml
KS1_Cluster_Down_Crit.xml KS1_Login_Operation_Failures.xml KS1_Server_Not_Running_Crit.xml
KS1_Few_Meeting_Connect_Remain.xml KS1_Meeting_No_Participant.xml
KS1_File_Transfer_Failures.xml KS1_Process_Not_Running.xml
… and many more.
One of them being my situation:
By the way, IBM recommends to run these commands using the root user as this lifts potential issues with user rights and (file or directory) access.
Next step could be to delete this situation and/or to import this situation (or all situations) into an existing PureApplication Monitoring shared service using the tacmd bulkImportSit.
Of course, if you are able to run those monitoring portal CLI commands remotely (from another instance), don’t forget to replace the localhost parameter.
More information
Check out the available monitoring portal CLI commands:
http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.2.3.1/com.ibm.itm.doc_6.2.3fp1/itm623fp1_cmdref11.htm%23tacmd?lang=en
In particular, look for these commands:
- tacmd bulkExportSit
- tacmd exportSitAssociations
- tacmd exportSysAssignments
- tacmd exportQueries
- tacmd exportWorkspaces
What did we describe here?
Using the command line tools provided with the PureApplication Monitoring shared service Portal, a monitoring administrator can easily define monitoring situations in one cloud group and transfer these to another cloud group or to another PureApplication Monitoring shared service instance.
IBM Cloud Pak System 