IBM Connections requires that XMLHTTP is enabled in Internet Explorer, either through ActiveX or native object, for the dynamic AJAX functionality to function correctly.
Check Enable native XMLHTTP support in the Advanced tab of the Internet Options dialog
Information from IBM TN 1698438
Some users are receiving the message bellow instead of the search results:
CLFRW0075W: Failed to load the index at startup, it may not have been created yet�
The search index on one node was created/copied.
To solve the problem i just copy the index from another node.
1. Update strategy for IBM Connections 5.0:
http://www-01.ibm.com/support/docview.wss?uid=swg21683118
2. IBM Connections 5.0 requirements for IBM FileNet for use with Connections Content Manager (CCM):
http://www-01.ibm.com/support/docview.wss?uid=swg21683147
3. IBM Cognos Wizard for IBM Connections 5.0 Cumulative Refreshes (CRs)
http://www-01.ibm.com/support/docview.wss?uid=swg21696033
4. Fix list for IBM Connections 5.0 CR2:
http://www-01.ibm.com/support/docview.wss?uid=swg21694318
5. Updating the IBM Connections 5.0 databases to the required schema versions for Cumulative Refresh 2 (CR2):
http://www-01.ibm.com/support/docview.wss?uid=swg21694319
6. New functions included in IBM Connections 5.0 CR2
http://www-01.ibm.com/support/docview.wss?uid=swg21695145
7. Upgrade to IBM Connections 5.0 CR2 from IBM Connections 5.0 CR1 With Connections Content Manager (CCM)
http://www-01.ibm.com/support/docview.wss?uid=swg21696235
Security researchers have discovered a vulnerability in a piece of adware called Superfish that makes your computer vulnerable to all kinds of attacks. Superfish ships preloaded on many Lenovo computers, but can also be installed on any machine. Here’s what’s going on and how to test if you’re infected.
See the full article here
Due to security vulnerabilities (CVE-2012-6153 and CVE-2014-3577) WebSphere Portal is removing the Apache commons-httpclient JAR files from all releases and replacing them with the newer version (Apache HttpClient 4.3.6).
Note that the JAR files may not be removed by a specific interim fix but the interim fix will remove all WebSphere Portal uses of those JAR files and the JAR files will be removed by a subsequent Cumulative Fix associated with that release.
These JAR files have been on the Portal classpath in many releases. They were never intended to be used by our customers but it is possible that they could be used by a customer’s custom portlets or by a third party’s custom portlets.
The specific JAR files that will be removed are the following:
commons-httpclient-2.0.jar
commons-httpclient-3.0.jar
commons-httpclient-3.0.1.jar
The WebSphere Portal releases in which the removal takes place are:
WebSphere Portal V6.1.0.6
WebSphere Portal V6.1.5.3
WebSphere Portal V7.0.0.2
WebSphere Portal V8.0.0.1 (included in CF15)
WebSphere Portal V8.5.0.0
If you do not have any custom code or third party code that uses these JAR files you do not have to do anything as consequence of this removal.
If you do have custom code or third party code that depends on these JAR files to be in the Portal Server classpath then you will have to make a change. There are many options. You can simply add a copy of the JAR back into the WebSphere Application Server or WebSphere Portal classpath, add the JAR into the appropriate portlet WAR file (neither of which will protect you from the security vulnerabilities) or change your custom source code to use the new Apache HttpClient 4.3.6 JAR that does fix the security vulnerability. Changing the source code is the best option. Note that Apache HttpClient 4.3.6 is a complete rewrite of the library and there is no backward compatibility. Reference the Apache web site for more details.
From TN 1695483
External collaboration is a new feature of Connections 5.
External user are any users “marked” or “selected” as a external.
External users can:
The process is not complicated. The key is how to mark or select external users on your ldap. The options are;
1 – Map standard LDAP attribute for external users
2 – Map standard LDAP attribute using JavaScript
3 – Use an LDAP branch to store external users.
I use the option 3 because on our LDAP external users are in another branch
I am using linux .
1 – First create another folder above /opt/IBM/TDI/V7.1.1 and copy the content of the TDISOL. I create with the nameTDISOLEXTERNAL
2- Edit map_dbrepos_from_source.properties and add a line
mode={func_mode_visitor_branch}
3 Edit profiles_tdi.properties and set the properties
source_ldap_url_visitor_confirm=ldap://
source_ldap_search_base_visitor_confirm=ou=external,o=Plansis
source_ldap_search_filter_visitor_confirm=(&(objectclass=inetOrgPerson))
source_ldap_search_base=ou=external,o=Plansis
source_ldap_search_filter=(&(objectclass=inetOrgPerson))
source_ldap_urlldap://
4- Append a string to an external user´s display name in map_dbrepos_from_source.properties
displayName={func_decorate_displayName_if_visitor}
displayNameLdapAttr=cn
decorateVisitorDisplayName=-Terceiro
5 – Run collect.dns and verify the list of users. Do not run sync_all_dns.sh or you will inactivate internal users!
6 – run populate_from_dn_file.sh
7 – Only internal users with the role EMPLOYEE_EXTENDED can share content with external users. Add the role to the users using wsadmin
execfile(“profilesAdmin.py”)
ProfileService.setRole(“[email protected]”, EMPLOYEE_EXTENDED)
Now you can collaborate with external users.
After i setup the IBM Connections 5.0 CR1 i open the homepage and the theme was show as the old IBM Connections theme not the new one.
I found on the systemout.log the following
net.jazz.ajax.internal.util.TraceSupport warn The StyleSheet “com.ibm.lconn.core.styles.oneui3/base/applications/profiles”
To solve the problem shutdown the connections server and clean the temp folder of the websphere application server on all nodes.
Restart the server and everything must be ok.
Thanks to Michael Urspinger tip
Email productivity is a hot topic and several companies will launch new products including IBM with IBM Verse.
But do not forget: Good spam protection is a important piece.
Several months ago, in our company, i setup Lotus Protector for Mail Security.
Before the setup, on mornings, we have a lot of spam and undesired messages do deal with.
We loose lots of hours / month just cleaning the inbox.
Some important messages was deleted during this clean process.
Using traveler on mornings was a nightmare.
The life after Protector is very different, there is no inbox cleaning anymore and blocked messages is managed by the users using IBM Notes integrated with Protector
Almost 90% of the hits are blocked, thousand of messages are blocked every day with zero false positive
Today i setup an IBM HTTPServer on top of Red Hat 6 64bits . The wct.sh command doesn´t work.
I found on the log some missing libs
To solve the problem:
yum install gtk2-engines.i686
yum install libXtst.i686
For a variety of purposes, such as Anti-virus exclusion or scripting, it may be necessary to know all or at least the majority of the file extensions that Notes uses. This document has a list and the purpose of some of the more commonly used ones.
.box – Used for mail routing. Mail is stored either in the client’s or server’s mail.box before being routed to the recipient.
.dic – User dictionary file (obsolete as of 8.5.x Standard if using the new spell check engine)
.dll – Dynamic-link Library
.dmp – Dump file, usually created during a crash.
.exe – Executable file.
.ft – Full Text Index
.gif – Type of an image
.hst – History file, Example fault_recovery.hst
.id – A Notes/Domino ID file, belonging to a user, server, or a certifier ID
.ini – Configuration settings file (INI = Initialize). These files are most commonly read at launch time.
.jar – Java class package file
.jpg – JPEG image
.lck – A file which locks another. Usually you will see a file with its normal extension and another with .lck if the file is in use or locked for other reasons
.lock – Same as .lck
.log – Non-Eclipse log file. Usually used to troubleshoot core client issues (ones that would be seen in the Basic client, like console logs and NSD files). Eclipse logs are in .XML format.
.nbf – Process table file
.ncf – Files similar to databases but are not read by humans. Examples include ~editclp.ncf (Notes clip board file) and cluster.ncf (File which contains cluster information)
.ndk – Another file similar to .ncf. Examples include Cache.NDK (Client cache) and Desktop8.ndk (Where workspace icons, some cached design elements among other things are stored)
.nsf – Notes System File, a Notes/Domino database.
.ntf – Notes Template file, a Notes/Domino template.
.prefs – A preference file, commonly found in
.properties – Similar to ini files but in the Eclipse side. Example, rcplauncher.properties, a file read by rcplauncher.exe when Notes2.exe is run.
.prov2install
.txt – A text file
.xml – An XML file. Most commonly used for Eclipse logs (Found in Data/Workspace/Logs)
I got this information from the TN1675947