Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Connections On-Premise Wiki
  • THIS WIKI IS READ-ONLY.
  • HCL Forums and Blogs
  • Home
  • API Documentation
Search
Community Articles > Customization > Customizing themes for Connections 4.5 CR1
  • Share Show Menu▼

Recent articles by this author

Customizing themes for Connections 4.5 CR1

You can edit the LotusConnections-config.xml file that controls the IBM® Connections theme to incorporate the new cascading style sheet (CSS) theme. Also, the new theme requires you to switch off Internet Explorer 7 compatibility mode. Switching off compatibility mode is required for the new theme ...

IBM Connections Plug-in for Microsoft Outlook

Documentation for Connections Plug-in for Microsoft Outlook

What's New in Connections 4.5

This video shows the new and changed features in Connections 4.5

Using Files - Connections 4

Watch this Connections video to learn how to use Files to store, share, organize, and collaborate on files.

Customizing the Connections 3.0.1 UI: Different Themes in a Single Installation

This article shows how to create different themes for Connections based on different domain names in a single installation.
Community articleCustomizing themes for Connections 4.5 CR1
Added by ~Ben Brekrolit | Edited by ~Sean Fezveluskilen on August 1, 2013 | Version 4
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
You can edit the LotusConnections-config.xml file that controls the IBM® Connections theme to incorporate the new cascading style sheet (CSS) theme. Also, the new theme requires you to switch off Internet Explorer 7 compatibility mode. Switching off compatibility mode is required for the new theme only, it does not apply to deployments that are not configured to use the new theme as default. Connections 4.5 CR 1 is a prerequisite for the new theme.

About this task

You can add a configuration setting to LotusConnections-config.xml to make the new theme the default theme.

Procedure

  1. Start the wsadmin client by completing the following steps:
    1. Open a command prompt and then change to the following directory of the system on which you installed the deployment manager:
    2. Directory path conventions ic45Create New Article/profiles/dm_profile_root/bin

      where dm_profile_root is the Deployment Manager profile directory; this directory is usually called dmgr01. For example, on Windows, the directory is C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01\bin

      Attention: You must run the command to start the wsadmin client from this specific directory because the Jython files for the product are stored there. If you start the client from a different directory, the execfile() command does not work correctly.
    3. Enter the following command to start the wsadmin client:
      • AIX or Linux: ./wsadmin.sh -lang jython -user admin_user_id -password admin_password -port SOAP_CONNECTOR_ADDRESS_PORT
      • IBM i: wsadmin -lang jython -user admin_user_id -password admin_password -port SOAP_CONNECTOR_ADDRESS_PORT
      • Microsoft Windows: wsadmin -lang jython -user admin_user_id -password admin_password -port SOAP_CONNECTOR_ADDRESS_PORT
      where:
      • admin_user_id is the user name of the Administrator role on IBM WebSphere® Application Server. This administrator must be configured at the cell level, not at the cluster, node, or server level.
      • admin_password is the password of the WebSphere Application Server administrator.
      • SOAP_CONNECTOR_ADDRESS_PORT is the SOAP port for the WebSphere Application Server deployment manager server. The default value of the SOAP port is 8879. If you are using the default port value, you do not have to specify this parameter. If you are not using the default value and you do not know the port number, you can look up its value in the WebSphere Application Server Integrated Solution Console. To look up the SOAP port number, complete the following steps:
        1. Open the WebSphere Application Server Integrated Solution Console for the deployment manager, and then select System Administration -> Deployment Manager.
        2. In the Additional properties section expand Ports, and then look for the SOAP_CONNECTOR_ADDRESS port entry to find the port number.
      For example:
      • AIX or Linux: ./wsadmin.sh -lang jython -username primaryAdmin -password p@assword -port 8879
      • IBM i: wsadmin -lang jython -username primaryAdmin -password password -port 8879
      • Microsoft Windows: wsadmin -lang jython -username primaryAdmin -password p@assword -port 8879

  2. Use the wsadmin client to check out IBM Connections configuration files:
    1. Enter the following command to access the IBM Connections configuration file: execfile("connectionsConfig.py")
    2. If you are prompted to specify a service to connect to, type 1 to select the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file by using a local file path, you must select the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.
    3. Enter the following command to check out IBM Connections configuration files:
    4. LCConfigService.checkOutConfig("working_directory","cell_name")

      where:
      • working_directory is the temporary working directory to which configuration files are copied. The files are kept in this working directory while you edit them.
      • Notes:
        • When you specify a path to the working directory on a system that is running Microsoft Windows, use a forward slash for the directory. For example: "C:/temp".
        • AIX, IBM i, and Linux only: The directory must grant write permissions or the command fails.

      • cell_name is the name of the WebSphere Application Server cell that hosts the IBM Connections application. If you do not know the cell name, display it by typing the following command in the wsadmin client: print AdminControl.getCell()
      • Note: This input parameter is case-sensitive.
    For example:
    • AIX or Linux: LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")
    • IBM i: LCConfigService.checkOutConfig("/temp","foo01Cell01")
    • Microsoft Windows: LCConfigService.checkOutConfig("c:/temp","foo01Cell01")

  3. Disable forced IE7 compatibility mode. Using a text editor, open LotusConnections-config.xml from the local directory to which you checked it out and set the following property:
  4. <properties>
         <genericProperty name="com.ibm.lconn.core.web.request.HttpRequestFilter.IECompatMode">false
         </genericProperty>
         <!-- other properties -->
    </properties>


    Note: Disabling forced IE7 compatibility mode applies only to the new theme. It does not apply to any existing Connections themes.
  5. Pick the com.ibm.social.gen4.theme_4.0.0.20130530-1409.jar from the business solutions catalog.
  6. Drop it into the <CONNECTIONS_PROVISION_PATH>/webresources directory.
    Note: You can read the value of <CONNECTIONS_PROVISION_PATH> from the IBM Console, under Environment -> WebSphere variables.
  7. Stop the WebSphere Application Server.
  8. Clear the WAS/temp directory.
  9. Set the genericProperty configuration property in LotusConnections-config.xml to "gen4" before the closing </config> tag:
  10.  <properties>
            <genericProperty name="com.ibm.lconn.core.web.styles.theme.default">
            gen4</genericProperty>
            <!-- other properties>
    </properties>

  11. When you make the update, type the following command to deploy the changes:
  12. synchAllNodes()

  13. Restart WebSphere Application Server.

Results

IBM Connections now uses the new theme.

  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (4)Aug 1, 2013, 3:37:29 PM~Sean Fezveluskilen  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility