David McCarthy 310000KJQX Visits (4692)
Steps For Changing connectionsAdmin J2C Alias to a LDAP User for IBM Connections V5.5/V6.0
The connectionsAdmin J2C authentication alias is configured during installation and can either be a local file-based repository WebSphere user (i.e. like "wasadmin") or a LDAP user.
Over time, it may be required to change from having "wasadmin" as the user mapped to this alias to a LDAP-based user. For example, if you want to enable SPNEGO, it's required to specify a LDAP user.
This post documents the steps taken in a IBM test environment (running v5.5 with CR3) to change from "wasadmin" to a LDAP user.
The same steps have been verified for a IC v6.0 environment.
Special thanks to Maik Weber for his excellent document below on which most of this post is based:
1. Add the new LDAP user as a WebSphere administrative user in the ISC.
Login to the WebSphere Admin Console (ISC) and select Users and Groups -> Administrative user roles.
Do a lookup for the LDAP user that you want to use as the new connectionsAdmin and add that user to the role.
2. Change the user that is mapped to the connectionsAdmin J2C alias:
Reference document: Changing references to administrative credentials
However, we ONLY need to do this procedure to update connectionsAdmin.
To confirm: UserID ”wasadmin” must be changed to “LDAP USER”.
Chad Scott 110000E1UB Visits (4419)
Recently I helped @Mar
Let's start by taking a look at the problem. In Blogs, it is possible to author an entry with a future publishing date. One example of this might be the Finance Department's communications about quarterly results. The content can be created ahead of the earnings announcement but not published until the information is made public. For example:
This works as expected in the native Blogs interface, where we see this:
That's exactly what we want users to see in this blog. The earnings announcement has not yet been made, so the entry describing those results should not be visible. However, when we surface this blog in ICEC's StaticContentBlog widget, we see the following:
Yikes! We have let our Q1 results slip early. This problem occurs due to the API used by the widget. Inspection of Stat
Save the new file as Stat
Next, we'll modify custom.js to use our new Stat
Add the following line to the init function, as shown below:
As mentioned earlier, this specific use case will be fixed in a forthcoming ICEC release. However, you can use this technique to implement any behavior modifications to the existing set of ICEC widgets, whether they are temporary fixes or custom extensions to the base functionality.
Chad Scott 110000E1UB Visits (4481)
My colleague @David McCarthy310000KJQX and I were chatting about an issue we're seeing with hanging WAS threads that eventually leads to a Connections server outage. He had the great idea to implement a monitor to detect the condition early and send an email alert so corrective actions could be performed before the outage. While I'm sure there are off-the-shelf packages that can be used or robust tools that can be developed using the JMX API, the goal here was something quick and dirty that we could implement in a minimal amount of time.
After having a crack at it this weekend, I created Simp
The specific issue we're working on is for Windows, so this is implemented as a PowerShell script. A Bash version would likely be even simpler.