While trying to install the fixpack for Tivoli Directory Integrator I got the following message:
The reason was some incompatibility with the network share where the installation sources were located. They were mounted via NFS from an EMC Isilon SAN
IBM Connections: Connection to LDAP is lost after some time
Customer has connected IBM Connections (means: Websphere Application Server) to an Atos DirX directory. The federated repository has been configured as “CUSTOM” type. After starting the Deployment Manager everything works, and the local wasadmin user and also admin users from the
IBM Connections 5: NextGen theme not displayed
After installation of IBM Connections 5.0 the new look & feel (NextGen UI) is not displayed. The UI still looks like the old 4.5 theme. In addition you find the following error in the SystemOut.log
The reason
IBM Connections: Installing Connections with LDAP user
If you are using a user from the LDAP for installing IBM Connections make sure that you are using the specified login name (e.g. “uid”) of that user and NOT the full distinguished name (DN). Otherwise you might have trouble
Logviewer for Windows
If you work with products like IBM Connections, IBM Sametime etc. you need a tool to view all the Websphere logs without the need to manually open them one by one. I used Baretail if the log files were on
IBM Connections 5.0 CR1 just arrived
You can now download IBM Connection 5.0 CR1 from FixCentral. Some more information: Fixlist New functions included Database Upgrade Information Information on updating FileNet for use with IBM Connection Content Manager (CCM)
IBM Sametime 9: Connection Problems to Sametime Video Manager
After installing the Sametime 9 Media Manager components I had problems to connect from the System Console to the Video Manager. E.g. you were unable to edit the default media manager policy as you got the error “AIDSC#####: Could not