Category Archives: Tech-Bits

Installing IBM Connections 5.0, CR2 and IBM Docs on Linux – Guides

My colleague Charles Price has created two guides covering the installation of IBM Connections 5.0, CR2 and IBM Docs on Linux. While I have created guides like that before, I have always done them on Windows, as Linux is, for me at least, a different kind if beast that I have so far avoided as much as I can. ūüėČ

Here you go:

Installation guide IBM Connections 5.0 on Linux

Installation guide IBM Connections 5.0 CR2 on Linux

Installation guide IBM Docs 1.0.7 on IBM Connections 5.0 CR2 on Linux 

 In the last one I especially like the two topics of upgrading CCM for Docs as well as the description on how to configure either NFS or CIFS shares.

Upload a new version of a document with IBM Docs 1.0.6

One of the new features of IBM Docs version 1.0.6 is, that you are now able to upload a new version of a document, even if the Document is “owned” by IBM Docs. To enable the “Upload new version”-button again you need to enable this feature though. Which steps you need to do depends on where you are in the installation, since the steps for enabling the upload new version feature are different depending on whether you enable it before you install the IBM Docs extension plug-in, before you upgrade the plug-in, or after you install or upgrade the plug-in.

 

To enable before installing IBM Docs extension plug-in:
1. Log in to the system where you installed IBM Connections, with the user who runs the Deployment Manager process.
2. Extract the installation package to a directory.
3. Open a command prompt and then go to the IBMDocsExt4IC_Install_Package/installer directory.
4. Copy the response file that you created to the current directory.
5. Rename the response file cfg.properties and add the following parameter under section [ICExt]:
enable_upload_new_version=true
6. Save the file.
7. Run the silent installation file:
Linux: ./install.sh
Windows: install.bat

 
To enable before upgrading IBM Docs extension plug-in:
1. Log in to the system where you installed IBM Connections, with the user who runs the Deployment Manager process.
2. Extract the upgrade package to a directory.
3. Open a command prompt and go to the DocsLCExtension/installer directory.
4. Copy the response file that you created to the target folder.
5. Rename the response file cfg.properties and add the following parameter under section [ICExt]:
enable_upload_new_version=true
6. Save the file.
7. Run the silent upgrade file:
Linux: ./upgrade.sh -installRoot
Windows: upgrade.bat -installRoot

 
To enable after installing or upgrading the IBM Docs extension plug-in:
1. Locate the IBM Connections Deployment Manager.
2. Log in to the system where you installed IBM Connections, with the user who runs the Deployment Manager process.
3. Find the configuration file “files-config.xml” in one of the following locations:
Windows: In the LotusConnections-config folder
Linux: Usually in /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/$CELLNAME/LotusConnections-config
4. Edit files-config.xml, changing the section that contains <objectType id=”00000000-00000-0000-0001-00000000000000″> to the following:
<actionControl>
<objectType id=”00000000-00000-0000-0001-00000000000000″>
<actions>
<action enabled=”true” name=”uploadNewVersion”>
</action>
<action enabled=”true” name=”download”/>
<action enabled=”false” name=”downloadEmptyFile”/>
<action enabled=”true” name=”restoreVersion”>
</action>
</actions>
</objectType>
</actionControl>
5. Save the file.
6. Log in to the IBM Connections Deployment Manager administrator console.
7. Synchronize all nodes.
8. Restart the Connections clusters that run the Files and Community applications.

Once you decide to work with a document offline and intend to upload a new version later it is advised, though, to lock the file in Connections Files to prevent others working on it online and their changes being consequently overwritten by uploading the new version.

How to disable automatic LTPA Key generation in WebSphere

When setting up SSO between WebSphere and Domino the automatic LTPA key generation must be turned off. These are the steps on how to do this:

 

  1. Log into the WebSphere Application Server Integrated Solutions Console as an administrator, expand Security, and select Global Security.
  2. Click LTPA in the Authentication section and then, in the Key generation section, click Key set groups.
  3. Select NodeLTPAKeySetGroup in the table and, in the Key generation section, un-check the Automatically generate keys check box, if is already checked.
  4. Click OK to save the changes.

Adding IBM Connections / WebSphere Applications to Windows Services

When installing IBM Connections on Windows only the Deployment Manager is added as a windows service during the installation. Parts like the node agent or later on the Connections clusters are not added.  To do so you need to run the following command from /WebSphere/AppServer/bin :

WASService.exe -add SERVICENAME -servername SERVERNAME -profilePath “C:\IBM\WebSphere\AppServer\profiles\AppSrv01” -stopArgs “-user wasadmin -password password” -userid windowsadmin -password password -startType automatic

SERVICENAME

This a freely chosen name for the service.

SERVERNAME

This the name of the specific server that needs to be stopped (such as nodeagent).  To find out the names you can go to /WebSphere/AppServer/profiles/AppSrv01/bin and run serverstatus.bat -all . This will list all servers including the running status.

profilePath

Edit it to fit your environment.

stopArgs

These are necessary to be able to not just start the service, but to also stop it. It will provide the WAS admin credentials during the stop process. Enter your own wasadmin user ID / password.

userid

This user has to be a windows user that has the right to start and stop services.  Once the service is created you can change it in the service setting in the Services list from Windows to local system account.

startType

This defines whether this service is started automatically at booting or not.

Two Mac OS terminal commands to remember

I just upgraded to Mac OS Mountain Lion and I had to use my two favorite terminal commands and thought I’d share them with you, even though you can easily find them in the internet.

First: Since OS X Lion Apple decided to hide the Library folder from the user.  Since for example the Lotus Notes Data folder is located there from time to time I need to access it.  To see it permanently you need to open the terminal and run the following command:

sudo chflags nohidden ~/Library

You will need to provide your admin password.

This will set the access rights so the Library folder is visible again. But be warned, this only lasts until you “repair” the disc / file permission using the disc utility. That will reset the folder to be hidden. Just rerun the command then.

The second one is regarding the fabulous Time Machine.  Whenever your near your Time Capsule or do your backups regulary when time machine is enabled, then everything is fine. But once you are on the road the Time Machine starts making backups on your local hard drive until you reach your home again. While this is very smart in regards of file history, this can be bad when you have a SSD with limited room left.  To turn of the local backups you need to run this command:

sudo tmutil disablelocal

Here, too, you will have to provide your admin password after firing the command.

Files Plugin for Lotus Notes does not upload documents

If you are using the Files Plugin Lotus Notes from the Greenhouse Solutions Catalog, you may be finding yourself being able to see and download all files in IBM Connections Files repository, but when trying to upload a file though, you might get an error message like that:

A problem with the server was encountered.

 

To solve that problem you need to add one line to Lotus Notes plugin-customization.ini:

com.ibm.documents.connector.service/ENABLE_SSL=true

Then save the ini-files, restart the Notes Client and the upload should be working now.

The plugins-customization.ini can be found in your Notes install directory/framework/rcp in Windows. ¬†Mac user right click the Notes.app icon and choose “Show package content”. Then they go to Contents/MacOS/rpc/ .

iFix LO64399 for Mobile Support in Connections does not work on Windows 2008 R2 Enterprise Edition

Some may have noticed that even after installing the iFix LO64399 September Update for IBM Connections 3.0.1 the mobile Applications on iOS and Android don’t work, even though the iFix Installer says it has been sucessfully installed. ¬†Sjaak Ursinus found the reason for it: This problem only occurs on Windows 2008 R2 Enterprise Edition and is due to a missing support line for this OS in the iFix.

There are two solutions to it:

1. ¬†As found by Sjaak: ¬†Add the line for Windows 2008 R2 Enterprise Edition (“Windows 2008 R2”) to the MANIFEST.FM text file in the iFix (located with the fix:¬†LO64399\efixes\LO64399\components\mobile\update\META-INF\MANIFEST.MF) and install it again.

2.  As found by Brian Ocs:  Run the Update Installer you use to install the fix with in Windows 2003 compatibility mode.

 

Once you have done that you should be able to access IBM Connections using the free apps in the App Stores of iOS and Android.

Connections on iPad

Population of Connections Database Field DisplayName if this entry does not exist in LDAP

Today I noticed in a customer installation that nowhere in the LDAP a usable displayname (aka “Martti Garden”) was available. ¬†My collegue Barbara Koch helped me out solving this: ¬†The attributes surname (sn) as well as givenname (givenname) were available to I had to compute the display name.

 

So I edited the profiles_functions.js and added the following function:

 

// Function to compute the displayname from given name and surname

func_compute_dn(fieldname)

// Get the content of the “sn” field as a string

{‚Ä®var surname = work.getString(“sn”);

// Get the content of the “givenname” field as a string

var vorname = work.getString(“givenname”);

// If both entries are not empty

if (vorname != null && nachname != null) {

// return first name and last name separated by a space

return vorname + ” ” + nachname;

// otherwise

}

else {

// return the¬†content of the “cn” field as a string, if it is empty it will return NULL

return work.getAttribute(“cn”);

}‚Ä®}

 

Now I had to edit the map_dbrepos_from_source.properties and mapped the function to the diplayname field:

displayname={func_compute_dn}


Now I ran the populate_from_dn_file script and had the Displayname showed correctly in IBM Connections.

Resetting WAS-Admin Password when the Browser Console does not work anymore

If you have to reset the WAS Admin password without using the web interface  (e.g. if you cannot log in anymore for various reasons) here is how you reset a forgotten WAS-Admin password:


1. Go to your WAS-Profile/bin directory using a command prompt (in IBM Connections case this would be ../(washome)/AppServer/profiles/DMGR/bin )
2.  Type the following command: wsadmin -conntype NONE and hit Enter
3.  Then you should be in the wsadmin prompt.  You now enter:  $AdminTask changeFileRegistryAccountPassword {-userId <wpsadmin-UserID> -password <new-password-for-wpsadmin>} Then hit Enter.
4.  Now the new password is stored temporarily.  So finalize the changes type $AdminConfig save followed by Enter. 

Restart WAS and you should be able to login using the new password.


Sometime you just need to disable the WAS application security to disable the federated repositories.  This is done in a similar fashion:


1. Go to your WAS-bin directory using a command prompt (in IBM Connections case this would be ../(washome)/AppServer/profiles/DMGR/bin )
2.  Type the following command: wsadmin -conntype NONE and hit Enter
3.  Then you should be in the wsadmin prompt.  You now enter the simple command: securityoff Then hit Enter.
4.  To finalize the changes type $AdminConfig save followed by Enter.

Restart WAS and you can log into the console using any username without a password.


 

How to activate Spotlight-Search for Lotus Notes content

One of the greatest thing of Mac OS is the Spotlight-Search (CMD+Leertaste) that gives me instant access to data and information on my computer.  Spotlight can also be used to search and find mails in Lotus Notes Рactually even fast than the Notes search itself.  This must be activated first, though.

 

To do so click on Actions => Desktop Search when you are in your mailbox-view.

 

Actions / Desktop Search

 

On the next screen you set the checknark on¬†“Enable idexing of local Lotus Notes databases”:

EnableIndexing

 

Now you get a warning that data indexed by Spotlight will not be under Lotus Notes security control anymore (e.g. spotlight may give you a preview of a mails content). ¬†That’s why I leave the checkmark at ¬†“Index encrypted fields” unchecked so encrypted mails do not show up in spotlights index.

DesktopSearchWarning

 

Using “Add‚Ķ” you can also add further databases such as archives to the spotlight search. ¬†I found it harder to find the proper email when all my archives are included, since I usually need recent emails. ¬†Therefore I went back to only adding my mail file. ¬†Once you hit Apply the changes are saved and soon (or later ūüėČ ) the first results will show up in your spotlight window.

 

SpotlightNotesMails