When my laptop sleep Sametime doesn’t auto-reconnect.
The following flag needs to be added to the plugin_customization.ini:
com.ibm.collaboration.realtime.community/forceLoginTokenRefresh=false
MySphere Posts
Websphere Portal 8 was launched and the downloads will be available on Friday .
See the what´s new in this link
This is a big projet here. Last week we start the setup of servers on top of zLinux.
The machine is big a new Dinosaur z196 . Very fast.
The Repair Calendar feature fixes issues with repeating calendar entries. This functionality only works if the user is running an 8.5 Notes client and the user’s mail database is based on the mail85.ntf template from Notes 8.5.
What is the Repair Calendar feature?
The Repair Calendar feature has been provided to help customers fix issues they encounter with repeating calendar entries such as meetings.
Specifically, this feature in Notes 8.5 fixes issues where duplicate repeating calendar entries exist in the mail file.
Please note that this functionality works only if the user is running an 8.5 Notes client AND the user’s mail database is based on the mail85.ntf template from Notes 8.5.
For more information see the TN 1326680
Very interesting articles of two friends who work at IBM support
If you want to know more about the recent contacts
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/ibm-lotus-notes-8-recent-contacts-and-type-ahead-features-faqs
The paper describes the steps and best practices for migrating an existing standalone WebSphere Portal 6.0 environment to a standalone WebSphere Portal V7 and should be followed by the majority of customers, even those in a Web Content Management environment.
The foundation for this document is the initial release of the V7 Information Center with additional information based on the outcome and experiences of our pre-release testing. With this document, we provide a more comprehensive guide and highlight some of the common pitfalls and mistakes when migrating.
Found it today on TN 1487071 but IBM doen´t tell the size of the very large attachment. I think to avoid this problem on the mail servers is to setup the max message size.
| Problem |
If serveral very large attachments are sent to DAOS enabled databases the daosfication process can use so much server resources as to be a risk to server function. The only way to stop it is to restart the server.
| Content |
| Since the Daos process is event driven stopping the event in process will be sufficent, it will not attempt to daosify the attachment again. However there is no task that can be brought down to stop DAOS, the server must be brought down. If the server is clustered this can be done one cluster mate at a time while user’s fail over. While the server is down look in the DAOS directory for large attachments created at the time the issue began. These can be removed.
Users who have the attachment and attempt to open it will produce messages on the console The database Pathname.nsf attempted to access a missing file: Pathname.nlo: File does not exist After the attachment has been removed from all servers the link can be removed from the mailfiles with the command fixup Path/name.nsf -J -D can remove the now bad links. The DAOS catalog will need to be resynchronized after this, it is best to do so when the server is less busy/ |
Portal search engine fails to crawl same content that may reside in different site areas of the same library
By default the crawler considers the content to be same and will only crawl the content item once even if it resides under different site areas. To resolve this issue simply add search service property CHECK_DUPLICATES = false and create new search collection