Thursday, 16 September 2010

More things I had forgotten - metrics in Lotus Connections 2.5 Profiles

Whilst I was hacking around inside Profiles to identify why I'm seeing this exception

Error: The stylesheet http://mashups.uk.ibm.com/profiles/home.do?lang=en was not loaded because its MIME type, "text/html", is not "text/css".
Source File: http://mashups.uk.ibm.com/mum/enabler#pid=AAE0A31CC29BB444C75C2ECA68C786000040&
Line: 0

I found a neat little JSP called: -

servermetrics_not_used.jsp

and thought .... hmmm, I wonder what that does, so I loaded it up in a browser: -

http://lc25.uk.ibm.com:9083/profiles/servermetrics_not_used.jsp

and get a nice little table of data about my Profiles environment: -




Profiles Metrics

Name Value
Total number of employees 3
Number of employees who have updated their background 0
Number of employees with a picture supplied 2
Number of employees with pronunciation supplied 0
Number of employees logged in today 1
Number of employees logged in the last week 2
Number of employees logged in the last month 2

Not hugely impressive on my own VMware image of Lotus Connections, but it might just be useful one day.

3 comments:

Dave Hay said...

And, as if by magic, I solved my own problem.

I was incorrectly specifying the path to the styles.css, which meant that the Profiles application had to go and look for it and, I guess, was returning something that wasn't properly formatted as text/css.

So the CSS URL changed from: -

http://lc25.uk.ibm.com:9083/profiles/css/styles.css

to: -

http://lc25.uk.ibm.com:9083/profiles/help/css/styles.css

e.g. added the subdirectory "help" into the URL.

Sorted :-)

Stuart McIntyre said...

That is ace! Really useful stats, beyond those included in the normal set. Cheers Dave!

Brownie said...

very neat Dave. I have been thinking about ways of building some reporting around the usage of Connections. Someone has obviously made a start!

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...