Monthly Archives: November 2009

Notes on Installing the Connections 2.5 Pilot

The installation of the Lotus Connections 2.5 pilot looks easy. Unfortunately the out of the box experience was not at all pleasurable for me. Here are some of the issues that I encountered while doing the install. I’m not sure how many of these were specific to my environment, but they did all hurt.

1) Don’t install from a directory with spaces.

If you download the pilot to your desktop and try and install from here, things will crash and burn

2) Don’t expect the VM to be easily moved around networks

I started my second installation on my laptop at home, then brought it to work. This crashed and burned.

3) Use fully qualified hostnames

While the installer said that you could specify a short hostname or a fully qualified hostname, the short hostname did not work for me.

4) Connections 2.5 is RAM hungry

1.5 GBytes is not enough 2.5 GBytes is. Not sure of the exact threshold for it to work, but I can confirm that 2.5 GBytes is enough RAM.

Resetting IBM WebSphere Portal 6.1 Security

Situation 

You have received a WebSphere Portal VM that is setup to use security settings that don’t match your environment, and you need to go back to a simple config.

Running the recommended ConfigEngine wp-restore-default-repository-configuration does not work, because you have not got a working Portal environment in the first place, so it won’t start.

Overview of solution

Disable the security, then perform wp-restore-default-repository-configuration.

Files and Tools used

  • security.xml
  • ConfigEngine 
  • wkplc.properties

Whenever you see some code with bold and italics that is something for you to change to match your environment 

Details:

1) disable security.

This involves directly editing the security.xml file for your node. Note that your portal instance will NOT work when security is disabled, so performing this step will disable your portal instance. You should not think about doing this in a production environment (you probably shouldn’t be passing around Portal VM’s for production environments anyway). (The security.xml will live in the config for your node. I’ll assume you know where this is, if not use the find command on your operating system).

To disable security, edit the security.xml, and change the enabled attribute on the root security element to be false ie change enabled=”true” to enabled=”true”

2) start up your portal instance using whatever commands are appropriate.

On linux you might find service portal start useful.

3) Setup restore properties in your wkplc.properties file.

Profile/ConfigEngine/properties/wkplc.properties

# The realm name to be used. A realm with this name will be created.
restore.file.realm=New Unique Realm restore.file.delimiter=/

# Portal and WAS admin UID (short name) and password
restore.file.primaryAdminId=New Unique Admin ID 

restore.file.primaryAdminPassword=Password

# CN of portal admin group (short name)
restore.file.primaryPortalAdminGroup=adminGroupCN

4) run ConfigEngine.sh

Profile/ConfigEngine/ConfigEngine.sh wp-restore-default-repository-configuration

5) Turn on security (reversing step 1)

6) shutdown (or kill) portal

7) startup portal.

You should now see your portal server running without using LDAP.