Post-installation tasks for Connections Touchpoint

If you prefer, you can adjust TDI profile functions (TDISOL/profiles_functions.js) to match the LDAP structure in your IBM Connections environment.

1. Adjust the function func_generate_recommended_tags to return a comma-separated string with the LDAP attributes that you want as recommended tags, such as tag1, tag2, tag3.

   Example 1: Fetch displayName from LDAP and extract departmentCode (the value in braces). Then split it up by separator "/" and append all subvalues to the tags array.

   Example 2: Fetch workLocation(extattr.city) and append it to the tags array.

   Example 3: Fetch country and append it to the tags array.

2. Adjust the function func_make_department_keyto return the correct identifier that is later used to determine the "promoted" experts and communities for the following example: Fetch displayName from LDAP and extract the departmentCode (value in braces)
. Then split it up by separator "/" and return the first match.

After installing IBM Connections Touchpoint, you must synchronize your WebSphere Application Server cells.

1. Log in to the wasadmin console with the was administrator ID and password. (e.g. For example, log in from the following URL: https://HOST_NAME/ibm/console/logon.jsp).
2. Navigate to System administrationNodesSynchronize the selected node, for example, connectionsNode.

Add a new alias to all IBM HTTP Servers by editing the httpd.conf file.

1. In the /opt/ibm/data/HTTPServer/conf/httpd.conf file (Linux) or C:\IBM\data\HTTPServer\conf\httpd.conf file (Windows), add the following line to the end of the file:

    # TOUCHPOINT 
   Alias /touchpoint/img/upload_pic/ "/opt/ibm/data/connections/data/shared/touchpoint/upload_pic/" 
   <Directory "/opt/ibm/data/connections/data/shared/touchpoint/upload_pic/"> 
        Order Deny,Allow 
    Allow from all 
   </Directory> 
   # TOUCHPOINT

2. Adapt the path to the one you set previously. Check that the path ends with a slash ( / ).
3. Verify that users have access to the HTTP Server files. Find the following reference to the HTTPServer\conf\httpd.conf file:

   # Controls who can get stuff from this server.
           #
           Order allow,deny
           Allow from none

4. Replace the reference with these lines:

   # Controls who can get stuff from this server.
           #
           Order allow,deny
           Allow from all

5. From the command line, restart the HTTP Servers. If necessary, use the root as follows:

   su -

   <IBM HTTP Server>\bin>./apachectl –k stop

   <IBM HTTP Server>\bin>./apachectl –k start

Before you can see Touchpoint, you must restart your WebSphere Application Server cluster, IBM HTTP Servers, and all IBM Connections applications and servers.

1. To restart the WebSphere cluster that you configured in installation package/touchpoint.deploy.properties, from the wasadmin console, navigate to Servers > Server Types > WebSphere application servers > restart the configured server > .
2. Restart your IBM HTTP Servers as follows:
   1. Change the directory to the IBM HTTP Server command folder (for example, /opt/IBM/HTTPServer/bin).
   2. Run the scripts ./apachectl stop and ./apachectl start to restart the HTTP Servers.
3. Restart all IBM Connections applications and servers as follows:
   1. Change the directory to the WebSphere command folder (for example, /opt/IBM/WebSphere/AppServer/bin).
   2. Run the script services wasservice.sh stop and wasservice.sh start.

If your organization is deploying Orient Me in place of the standard IBM Connections home page, don't forget this step so that your users arrive at the correct home page once they successfully complete Touchpoint.