Pages

Showing posts with label testing. Show all posts
Showing posts with label testing. Show all posts

Monday, April 4, 2011

Calling IBM Social Business Partners

View Comments

One of the things that I've been working on in my new role, along with many colleagues, is on a new program for our business partners.

On Friday, IBM started to offer a Social Business Authorization where Business Partners can certify as Social Business partners. I thought this was interesting because the authorization (or certificaions, depending on how you want to call it) is focused more on demonstrated skills than on actual certifications (i.e. passing tests). There is, however, a requirement to pass certain mastery tests.

The authorization also includes offerings from different brands in the IBM portfolio for a complete Social Business offering. The idea is that a partner must know how to work with Connections but also with the complementary offerings from Cognos and/or SPSS.

If you would like to be part of this new authorization, or want to learn about the benefits, you can find out more about in PartnerWorld here. The list of mastery tests is included here.


Monday, February 9, 2009

Lesson Learned And Addendum to InfoCenter

View Comments

As I said on my previous post, Friday was a VERY long day. Early in the morning I was told that there was a CritSit at a customer. The situation had been escalated all the way up to Jeff Schick (VP of Social Software). Since it's never good to have a VP associate a CritSit to your name, I had to get this resolved (and quickly) to make sure the blame would not come my way .

And it starts...

The week before, I had upgraded this customer up to Lotus Connections v2.0.1. At first, the environment was working ok, but then on Wednesday they ran into some issues:

  • users couldn't log in
  • forums in private communities were not working
  • widgets in the profiles page weren't working properly

In summary, it was a mess!

Troubleshooting

The first step was to resolve the login issue. To do this, we enabled several traces (see below) in the WAS admin console to see what was going on with WALTZ (the component that fetches users for Lotus Connections). After carefully reviewing the trace log, we noticed that the mapping for GUID (the system's globally unique id) was being re-mapped from 'dominoUNID' to 'DistinguishedName'.

com.ibm.directory.profile.*=all:com.ibm.connections.directory.services.*=all:
com.ibm.websphere.wim.*=all:com.ibm.ws.wim.*=all

For some time we couldn't figure this out. By default, the default mapping for GUID (a.k.a ExtId) is dominoUNID when the LDAP server is Domino (which was the case for the customer). Then one of the developers on the call, spotted this warning in the internal Wiki:

200902081935.jpg Warning

If Domino R8 & beyond is in need and the binding credential, which is used in setting up LDAP repositories on WAS, do not have administrators' privilege to query for Domino LDAP schema, then this manual procedure is a MUST-HAVE to configure 'dominoUNID' as the VMM (external) ID!

Success! The user that we are using to bind to the Domino LDAP is not an administrator and our Domino server is R8. This warning is not in the InfoCenter, so we never did this manual procedure. Now the question was: why did it work before and broke after the upgrade?

200902081653.jpgWell, turns out that apparently there are some broken iFixes. When I did the upgrade, I went ahead and installed all 32 of the available iFixes. I was questioned by one of the developers as to why I did this since iFixes should not be installed unless mandated by support. Turns out that I didn't know that and when I started looking at the iFix list chronologically, most of them said 'Mandatory' so I proceeded to install.

We were told by development to remove iFixes 36025 and 36482. I can't remember what those were for, but today I noticed that the iFix page has 26 fixes instead of 32. Therefore, I'm assuming some other iFixes were not working properly. Anywho, we uninstalled those two iFixes and users were able to log in again!

The final problem was fixing the forums in private communities. This was quite easy to find: the SSO domain for the LTPA token was misconfigured.

Lesson Learned

So, lesson learned:only install iFixes when mandated by support, unless they are clearly marked as 'Mandatory'. And if you are deploying Lotus Connections with a Domino R8+ LDAP and the bind user is not an administrator, you must manually map ExtId to dominoUNID.

Monday, July 14, 2008

Does the lack of browser support drive you crazy?

View Comments

The other day I discovered PlanetLotus via Twitter. By the way, if you are a Lotus employee, evangelist, tech sale, seller, user, fan, etc, you HAVE to bookmark PlanetLotus. The creator of this site is Yancy Lent who has his own external blog.

As I read Yancy's blog, I found an entry called: "A screenshot of your web page from 64 browsers and 4 OS's" and in it I learned about browsershots.org!

The way it works is that you simply enter a URL and the site gives you the screenshots of how it would look like from 64 browsers and 4 different OS's. I entered my external blog's URL and discovered that my blog doesn't quite work well in MSIE v5.5 (but what works in that browser, anyway?). Also, Epiphany on Ubuntu is really bad combination for my blog.


200807141513.jpg

Isn't social software cool ??

Anyway, I really think that all major software companies, Lotus included, should look into this technology so right off the bat we can support 64 browsers on 4 OS's. Currently, when a product ships, it usually supports 2-4 browsers (unless it's a MS product, then only 1 browser is supported), based on what the testers had time to test with. Using this technology, we can quickly and efficiently see how products behave on the different browser and OS combinations that are out there! Food for thought....