Editing the plugin_customization.ini file to add custom features and change default preferences

You can customize the plugin_customization.ini file to add features from a custom plug-in or to change the default installed preferences.

Before you begin

Download the client installation files to prepare them for customizing.

Procedure

Follow these steps to customize the plugin_customization.ini file.
  1. Open the downloaded plugin_customization.ini file in a text editor.

    Mac

    install_mpkg\deploy\plugin_customization.ini

    Windows™

    install-kit-base-dir\deploy\plugin_customization.ini

  2. Change the default preferences that you want users to receive. For a list of preferences you can add, see Sametime® client preferences.

    After installation, users can manually override the preferences set with the plugin_customization.ini file by using the Preferences dialog in their Sametime Connect clients. If you prefer to set preferences at runtime with the option of locking the preferences, use the Expeditor managed settings framework to set read-only preferences instead.

  3. If you created a custom plug-in, identify the features to install.
    1. Add the features to the plugin_customization.ini file.
      For example:

      com.ibm.collaboration.realtime.community/SametimeServer=chat1.sametime.example.com

      com.ibm.collaboration.realtime.ui/stbranding=custom.branding.custom_feature

    2. If you did not sign the plug-in, comment out these four lines from the plugin_customization.ini file. Otherwise the installation will fail:

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

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

      #com.ibm.rcp.security.update/UNSIGNED_PLUGIN_POLICY=PROMPT

      #com.ibm.rcp.security.update/UNTRUSTED_SIGNATURE_POLICY=PROMPT

  4. Close and save the file.
  5. Repackage the download image before distributing it to your users. If you are making the client installation package available on an HTTP server, generate a new installation package.

What to do next

If you plan to install clients in silent mode, change the CREATECOMMUNITYTEMPLATE setting in the silentinstall.ini file to false.