Thank you for this pointer.  I went through this setup on WAS and restarted the server. When I tried to map my blue groups to the jts roles that are defined (Like JazzAdmin) my search returned nothing but this message.
The selected realm cannot be accessed at this time. You might need to start the server. Otherwise, you can use the following fields to add users by their unique user IDs.

One more piece of information is that once I followed the instructions that Krishna provided, I am able to log in to the WAS console using my LDAP identity in Bluepages, so the realm seems to be configured properly. I am just unable to map my LDAP Bluepage groups to the JTS roles because the search returns the message I provided  in my previous post.

Perhaps if someone could send me the actual screen shots from the WAS console of their Security->Global Security->Stand Alone LDAP registry configuration and the advanced LDAP user registry settings.  I'm using WAS 7.0. These are my settings.
Standalone LDAP registry.  (This is set as current)
Endbled: Automatically generated server identity
Type of LDAP server: Custom
Host: bluepages.ibm.com
Port: 389
Base distinguished Name: o=ibm.com
Enabled: Reuse connection
Enabled: Ignore case for authorization

Advanced LDAP settings.
User filter: (mail=%v1)
Group Filter: (uniquemember={0})
User ID map:  :mail
Group ID map:  :cn
Group member ID map:  ibm-allGroups:member;ibm-allGroups:uniqueMember
Disabled:  Perform a nested group search

 Hello Thomas

I found another developer works article that has a very descriptive configuration and instructions. This has all the configuration details too.

Anyone ever seen or more importantly solved "The selected realm cannot be accessed at this time." ?  I'm trying to migrate an upgraded ( 4.0.6 ) CLM into WebSphere 8.X.  I chatted with Tom who did solve, but he couldn't find the reference to share.