Customizing Sametime Connect Entry 8.5

The IBM Lotus products are sometimes a bit messy to customize. Many customers want a silent installations that does-the-whole-job, which includes:

  • Hard coded server address
  • Swedish dictionary
  • Some features on or off by default

I have created several packages of Lotus Notes, Lotus Symphony and recently Lotus Sametime.

The problem with Lotus Sametime (as with Lotus Symphony) is that there are many undocumented features. And doing even the simplest thing can be troublesome. Also the manual sometimes contains outdated information. Whats good about customizing Lotus Sametime is that it is only text files that needs to be editied. It’s not like when customizing Lotus Notes where the buggy (but useful) InstallShield Tuner for Lotus Notes has to be used.

Anyway, this is how I did it:

  1. using “optional-components-update-site.zip” i extracted the 2 dictionary files and included them in the Sametime Connect installfiles

  2. Updated site.xml (copying information from site.xml in the above zip-file)

  3. Updated install.xml (the tricky part, and I copyed the line from the american dictionary and modifyed it)
  4. Updated install.xml to include Outlook integration

  5. Updated silentinstall.ini

  6. Updated plugin_customization.ini

I ran into two major issues doing this package:

  1. Dictionary refuse to install and leaving the whole installation broken
  2. Interface language still enlish even though “silentinstall.ini” explicitly says swedish

To solve part 1 I had to dig into the logfiles, and finally I found out that it had something to do with signing. However I found a solution:

Installing the spell checker (dictionary) on Sametime Connect or integrated Sametime in Notes 8 http://www-01.ibm.com/support/docview.wss?uid=swg21260550 which contains this information:

Note: After updating the install.xml file to point to those jar files, you might receive the following error message: SEVERE CWPST1015W: Plugin com.ibm.langware.v5.dic.es_ES.feature_5.3.1.9-200810091628 failed to install. The reason provided is CWPST1001W: No signature found

com.ibm.rcp.security.internal.update

And the solution is to add this to [installdir]/deploy/plugin_customization.ini

# settings for enabling PKI based provisioning security

com.ibm.rcp.security.update/VERIFICATION_LISTENER=com.ibm.rcp.security.update.DefaultVerificationListener

com.ibm.rcp.security.update/EXPIRED_SIGNATURE_POLICY=ALLOW

com.ibm.rcp.security.update/UNSIGNED_PLUGIN_POLICY=ALLOW

com.ibm.rcp.security.update/UNTRUSTED_SIGNATURE_POLICY=ALLOW

Part 2 was a little bit trickier.

The installation command was not correct. After a lot of testing, this is what I used:

msiexec /i setup.msi /Lv install.log /qn SETUPEXEDIR=”MY_SETUP_DIR” INSTALLDIR=”C:\Program Files\IBM\Lotus\Sametime Connect” STSILENTINIFILE=”silentinstall.ini” STSILENTINSTALL=TRUE

About these ads

Tags: ,

7 Responses to “Customizing Sametime Connect Entry 8.5”

  1. D Says:

    Where do you specify the server it should use ?

  2. usablesoftware Says:

    silentinstall.ini:
    [Properties]

    LAPAGREE=YES

    STSERVERNAME=ServerName.com
    STCOMMUNITYNAME=CommunityName

    STSERVERPORT=1533

    STSENDKEEPALIVE=true

    STKEEPALIVETIME=60

    STCONNECTIONTYPE75=direct

    STPROXYHOST=

    STPROXYPORT=

    STRESOLVELOCALY75=

    STPROXYUSERNAME=

    STPROXYPASSWORD=

    STCOUNTRYLANG=sv

    STAUTHSERVERURL=

    STLOGINBYTOKEN=false

    STAUTHTYPE=TAM-SPNEGO

    STLOGINATSTARTUP=false

    STUNINSTALL75=1

    STUNINSTALLPRE75=1

  3. D Says:

    Thanks

  4. ardent Says:

    Thanks, this helped me a lot. I ran into this bundling a third party plugin into sametime. Can this be avoided by having the plugin signed? If so, by whom?

    Lastly, for the life of me I can’t discern the difference in the msiexec string you posted versus the one in the sametime.standalone install folder provided in the 8.5 release, unless I am overlooking something. What was the difference?

    • usablesoftware Says:

      Hi ardent!

      Ok, the mention of the msiexec string was just a hint that sometimes it ca be tricky to use a long complicated string with slashed and quotes.

      • ardent Says:

        Is there a reason to use .exe over .msi or vice versa?

        Thanks again!

  5. usablesoftware Says:

    “setup.exe” can sometimes perform a more stable installation than using msi. But there should be no real differences.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Follow

Get every new post delivered to your Inbox.

%d bloggers like this: