For most of what you need, IBM has a great article on how to incorporate jQuery into your Cognos reports here:
https://www.ibm.com/developerworks/library/ba-pp-reporting-advanced-report-design-page647/index.html
However, there are some painful issues which vary based on whether you access reports through DASH/JazzSM or go directly to Cognos Reporting. Specifically, it appears that DASH adds some additional capabilities to the environment, possibly through the use of Dojo. Or it's possible that these capabilities are stripped off when logging directly into Cognos. Whatever the case, here are the caveats:
DASH/JazzSM adds some additional container elements to the HTML report such that you cannot use the browser "Print" function to print a multi-page report. All you get is the first page of the report, and this happens on all browsers. To get around this, I opened a new window and set the contents to be only the container enclosing the report. Then THAT window can be printed via the browser.
Logging directly into Cognos "removes" several methods that should exist in IE 11. For example, it undefines the Object.keys() method. So if any JavaScript you're using references that method, you'll need to use a workaround like this one:
https://stackoverflow.com/questions/18912932/object-keys-not-working-in-internet-explorer
Additionally when logging directly into Cognos, the HTMLCanvasElement.getContext() method is not defined. Personally, I got around this by commenting out any references to that method and it worked in my case. Unfortunately, I couldn't find any "good" solution to this problem, so this is all I've got.
Happy coding!
Monday, January 13, 2020
Tuesday, December 3, 2019
Adding an Unauthenticated JSP to IBM Control Desk
Background
We have a customer that needed to allow unauthenticated users to open tickets within IBM Control Desk, and we only had access to IBM HTTP Server and our Maximo/ICD WebSphere server to make that happen.Security Risks
Essentially, anyone with the link can get to the pages described in this article. They could even write a script to create a huge number of tickets, taking down your ICD installation. So in any pages you create using this article, you need to do *something* to guard against that behavior. Exactly what you do depends on your specific situation.
Where to Create the Unprotected JSP
You just need to create the .jsp file under:
.../installedApps/<cell__name>
For example, put the following in the file HelloWorld.jsp in the above directory:
<HTML>
<HEAD>
<TITLE>Hello World</TITLE>
</HEAD>
<BODY>
<H1>Hello World</H1>
Today is: <%= new java.util.Date().toString() %>
</BODY>
</HTML>
<HEAD>
<TITLE>Hello World</TITLE>
</HEAD>
<BODY>
<H1>Hello World</H1>
Today is: <%= new java.util.Date().toString() %>
</BODY>
</HTML>
Then access it with the url:
And this is what you'll see, with no login required:
That's it. Now you just need to write the JSP code to do what you need.
Caveats
A JSP file added in this way would need to be re-deployed after each time you deploy the application. These instructions do NOT tell you how to add the JSP file to the EAR build process.
You need to manually copy the JSP file(s) to the appropriate location for each MAXIMO UI JVM.
Monday, December 2, 2019
Creating incident ticket in IBM Control Desk using the new REST API
Background
Maximo 7.6.0.2 introduced a new REST API that can be accessed via .../maximo/oslc . Here's a link to the documentation on it:https://developer.ibm.com/static/site-id/155/maximodev/restguide/Maximo_Nextgen_REST_API.html
This is an all-JSON API that makes things a ton easier than it was with the older (and deprecated) XML-based REST API.
The Problem
However, that documentation is aimed at Maximo Enterprise Asset Management users and not IBM Control Desk users. That means there aren't any examples for creating incidents or service requests, for example.Why You're Here
You want an example of creating an INCIDENT in ICD, and that's what I'll provide. I'm using ICD 7.6.1.1 on WebSphere, DB2 and IBM HTTP Server, along with the sample data. That's how I have a classification ID and hierarchy structure in the example below.
Basically, the best way I've found is to use the MXOSINCIDENT object structure because it already has a bunch of relationships (including one to TICKETSPEC, so you can add specifications when creating an incident). Here are the details:
Additional header:
properties: *
BODY:
{
"reportedby":
"MXINTADM",
"description": "second
MXINCIDENT OS API",
"externalsystem":
"EVENTMANAGEMENT",
"classstructureid":
"21010405",
"ticketspec":
[{"assetattrid":
"computersystem_serialnumber","alnvalue":
"99999"}]
}
RESPONSE:
{
"affecteddate":
"2019-11-29T15:02:00-05:00",
"template": false,
"creationdate":
"2019-11-29T15:02:00-05:00",
"hierarchypath": "21 \\ 2101
\\ 210104 \\ 21010405",
"historyflag": false,
"actlabcost": 0.0,
"createwomulti_description":
"Create Multi Records",
"selfservsolaccess": false,
"outageduration": 0.0,
"ticketuid": 46,
"inheritstatus": false,
"reportdate":
"2019-11-29T15:02:00-05:00",
"class_description":
"Incident",
"description": "second
MXINCIDENT OS API",
"reportedby":
"MXINTADM",
"classificationid":
"21010405",
"sitevisit": false,
"_rowstamp":
"10009026",
"accumulatedholdtime": 0.0,
"createdby":
"MXINTADM",
"relatedrecord_collectionref":
"http://was.gulfsoft.rocks:80/maximo/oslc/os/mxosincident/_SU5DSURFTlQvMTA0MA--/incidentrelrec",
"isknownerror": false,
"affectedperson":
"MXINTADM",
"multiassetlocci_collectionref":
"http://was.gulfsoft.rocks:80/maximo/oslc/os/mxosincident/_SU5DSURFTlQvMTA0MA--/incidentmultiassetloci",
"class": "INCIDENT",
"ticketid": "1040",
"ticketspec": [
{
"localref": "http://was.gulfsoft.rocks:80/maximo/oslc/os/mxosincident/_SU5DSURFTlQvMTA0MA--/ticketspecclass/0-7",
"classstructureid":
"21010405",
"changeby":
"MXINTADM",
"changedate":
"2019-11-29T15:02:00-05:00",
"alnvalue":
"99999",
"mandatory": false,
"refobjectname":
"INCIDENT",
"ticketspecid": 7,
"assetattrid":
"COMPUTERSYSTEM_SERIALNUMBER",
"_rowstamp":
"10009029",
"refobjectid": 46,
"displaysequence": 1,
}
],
"status_description":
"New",
"externalsystem_description":
"EVENT MANAGEMENT",
"classstructureid":
"21010405",
"ticketspec_collectionref":
"http://was.gulfsoft.rocks:80/maximo/oslc/os/mxosincident/_SU5DSURFTlQvMTA0MA--/ticketspecclass",
"changeby": "MXINTADM",
"changedate":
"2019-11-29T15:02:00-05:00",
"externalsystem":
"EVENTMANAGEMENT",
"actlabhrs": 0.0,
"relatedtoglobal": false,
"hasactivity": false,
"statusdate":
"2019-11-29T15:02:00-05:00",
"createwomulti":
"MULTI",
"hassolution": false,
"virtualenv": false,
"pluspporeq": false,
"isglobal": false,
"oncallautoassign": false,
"pmscinvalid": false,
"status": "NEW"
}
Prerequisites
To successfully do the above, you do need to Configure Object Structure security: https://www.ibm.com/support/
I'm using Postman for testing, which I highly recommend: https://www.getpostman.com/downloads/
Of course you'll use some specific language (or curl) when you're doing this in production, but for testing, you want to use Postman.
A helpful link
In addition to the API documentation, this link was very helpful to me:
Tuesday, November 12, 2019
Special characters in passwords initially configuring IBM Control Desk 7.6.1.1
Several of the screens displayed by ConfigUI tell you that some passwords don't allow special characters. The rule of thumb I found the REALLY hard way is:
ONLY use underscore as a special character in any password initially.
We ran into problems mainly with dollar sign, but other ones will certainly bite you, too. We even ran into the problem with the root user's password. Any password can be changed after the initial deployment, so save yourself some headache and make them initially very simple. And the painful part is that some of the errors will just be silent, such as "Unable to access host with these credentials", but no other error. So just take the advice above and you'll be much happier.
ONLY use underscore as a special character in any password initially.
We ran into problems mainly with dollar sign, but other ones will certainly bite you, too. We even ran into the problem with the root user's password. Any password can be changed after the initial deployment, so save yourself some headache and make them initially very simple. And the painful part is that some of the errors will just be silent, such as "Unable to access host with these credentials", but no other error. So just take the advice above and you'll be much happier.
Subscribe to:
Posts (Atom)