You also need to modify LotusConnections-config.xml to set service_extension_auth for Communities and Profiles to “DSX-Admin”:

To do so there is a nice little tool provided with WAS called WASService which adds the server instance as a Windows service:

So for example, to add a service called “lcMisc“ based on a server definition “lcMisc” you would add it like this:

The credentials specified with -userid define the local or domain user account who will be used to start the service.

NOTE: When WAS admin security is enabled you need to provide that information with -stopArgs. Otherwise you won’t be able to stop the server through Services.msc.

When looking at Services.msc you should see the service you have just created:

You can also use WASService to remove the service:

NOTE: When you need to update the configuration of the service (e.g. changed credentials), just re-use the -add command as shown above with the changed information.

The configuration of the service is stored in Windows registry in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\, for example:

OPTIONAL: Sometimes you need to start services in a specific order, let’s say database first and WAS server second. To do so, please follow the instructions on How to delay loading of specific services in the Microsoft Knowledge Base.

Basically, you need to add a value called “DependOnService” with a data type of REG_MULTI_SZ to the service definition and add the name of the service it depends on as the data of that value. For example:

NOTE: As this value is of type REG_MULTI_SZ you can provide more than one service name (each on a separate line).

In the following example, “nodeagent” needs DB2 and Lotus Domino to be started while itself is a pre-condition for “lcApps” and “lcMisc” services.

NOTE: You can’t modify these dependencies in Services.msc, you have to modify the Windows registry instead.

As you probably know from the Info Center Lotus Connections provides statistics for each component but not consolidated for all of them on one page.

When I looked at the database it became clear that a simple SQL UNION would not work as by default different databases are created during installation.

As I personally love the functionality of IBM Mashup Center I came up with the idea to combine the results from each database script and provide the output as an ATOM feed for further processing.

Here’s what I did:

1. First I created 5 SQL scripts for Profiles, Communities, Blogs, Dogear, and Activities to retrieve the GUIDs of all active users.
2. Then I used those SQL scripts as feeds in InfoSphere MashupHub. Here some screenshots:

3. After I defined 5 feeds, I created a feed mashup using simple operators and published the result as an ATOM feed:

4. In Lotus Mashups I made a sample page to verify everything worked as expected. On the left hand side you can see the feeds I created in 2. and as you may notice different users were active in Activities and Communities. On the right hand side you can see the feed mashup and how it combines the active users into one consolidated result…

I’m loving it!

When a specific application doesn’t provide a setting to switch the language of the UI, you can still “force” the application to use another language.

Here’s how:

Let’s say Aperture opens in German because the language of Mac OS X is set to German.

Now ctrl-click (right click) on the Aperture icon in Applications and choose “Get Info”:

When Aperture info opens, you’ll find a section labeled “Languages”. This were you can deselect any unwanted languages (in my case all except English):

The next time you start Aperture, it’ll run in English:

I love Mac OS X!

BTW, the open beta of Lotus Notes 8.5 doesn’t yet provide any other language but English.

After the installation of the Communities Connector for Confluence, you’re ready to use it within your communities.

When starting a new community you can also create a new wiki for that community automatically:

The wiki is accessible from Lotus Connections as from Confluence directly:

On the backend, a new user group will be created in the Confluence wiki database. This helps to keep group memberships in Lotus Connections Communities and Confluence wiki in sync. Both are connected to the same LDAP.

When adding a new user to the community, he will also be added to the wiki’s user group automatically:

When the community is deleted in Lotus Connections, it’ll be also removed from Confluence:

So much for basic operations with the Communities Connector for Confluence. Let me know if you need further information.

First you need to install and configure Confluence (LDAP/SSL) and define authenication aliases on WAS: one as an LDAP bind user and another one to manage the Confluence wiki.

Then, you are ready to start the installation of the Communities Connector for Confluence:

Interested in more information about the Communites Connector for Confluence? Continue reading here…

Restart Notes client.

1. First let’s make sure the volume isn’t already mounted:

2. Now mount the Windows share in Finder (Command (Apple) – K):

3. The Windows share will appear in the ‘Shared” section in Finder:

4. To verify, open Terminal and check the mounts:

5. Enter “defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1″ in the Terminal window to make unsupported network volumes visible to Time Machine:

6. Now you can configure Time Machine (System Preferences -> System -> Time Machine):

7. Done. Time Machine is now ready to backup your data…

8. …unfortunately there is not enough space on the Windows share

9. But at least you can see that Time Machine tried its best:

BTW, with “defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 0” you can revert the setting.