Excelent video if you want to compare files on Connections and MS Sharepoint
Excelent video if you want to compare files on Connections and MS Sharepoint
Option 1: Increase the minimum attachment size for DAOS and remove the small .nlo files
* In order to have a better understanding of how to choose an attachment size, you should download and run the DAOS estimator.
tell daosmgr prune <#_of_days_since _last_full_backup>
Option 2: Decrease the number of days for the “Defer object deletion” interval.
* In order to ensure you have all data saved in a disaster recovery situation you must not set your “defer object deletion” less than the largest number of days between full saves.
tell daosmgr prune <#_of_days_to_retain_nlo_files>
In general, as mentioned in the Portal info center, Page builder menus located at : fs-type1/themes/PageBuilder2/menuDefinitions
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Page_builder_menus_wcm7
So to remove/hide the Sign up link do the following :
1) Connect to your fs-type1 using a webDav :
http://localhost:10039/wps/mycontenthandler/dav/fs-type1
2) Go to fs-type1/themes/PageBuilder2/menuDefinitions/ directory
3) modify bannerLink.json
from
visibilityFn: com.ibm.pb.contextMenu.sharedActions.isAnonymous,
id: “BannerLinks:signUp”
to
visibilityFn: function(ID, resourceType, metadata, obj){ return false;},
id: “BannerLinks:signUp”
To remove/hide the Edit my profile link do the following :
1) modify userActions.json file in fs-type1/themes/PageBuilder2/menuDefinitions/ directory
from
visibilityFn: com.ibm.pb.contextMenu.sharedActions.isAuthenticated,
id: “UserActions:selfCare”
to
visibilityFn: function(ID, resourceType, metadata, obj){ return false;},
id: “UserActions:selfCare”
Note: you may want to clear the browser cookies and cache before testing and remove the sign up link from the login portlet. Just go to confirguration page of the portlet.
This problem happened with a few weeks again with a project I was working on.
In a WebSphere Portal v7.0.0.2 cluster, content changes (such as portlet preference updates) may not replicate to all nodes in the cluster until the nodes are restarted.
Is advised to install this fix
Started today a new project. We need to migrate a Portal and WCM environment to 7.0.0.2. Will be great adventure :-).
The first step was to download a ton of files, plan the migration and tomorrow i will start the setup process.
Interim Fix 1 for Lotus iNotes 8.5.3 Fix Pack 2 is now available for download from Fix Central. This Interim Fix is required only if running IBM Connections Mail 1.0. This Interim Fix is NOT required for stand-alone IBM Lotus iNotes and/or IBM Lotus Domino.
Get the fix here
Updates made to the Firefox browser in Firefox 15 and later, may result in iNotes no longer working as expected. For example, mail will not send when pressing the Send button after composing a mail message.
The use of signed scripts in Firefox by iNotes can be disabled at the server with a notes.ini setting.
After this is applied, aAttachments will use the older DHTML user interface, but will work. Mail, calendar events, and to do’s will send and save, but URLs will not be automatically converted into URL hotlinks. (However, many mail clients convert URLs into hotlinks when mail is received, so the absence of this conversion by iNotes may not be noticeable.)
In order to disable signed scripts in Firefox, set “iNotes_WA_FirefoxSignedScript=0” in the notes.ini, and then restart the http task for this to take effect.
To make this update, enter the following server console commands:
set config iNotes_WA_FirefoxSignedScript=0
restart task http
The information above is from TN 1610926
IBM has identified an opportunity to improve the login process used in WebSphere Portal and associated products.
This improvement of the login process provides a more secure authentication and more stable operating environment when the fixes for APARs PM08667 and PM12122 are installed together. Links to the fixes available from Fix Central.
You have a scheduled agent that runs at a set frequency (such as 30 minutes). This schedule agent runs correctly most of the time. If, however, the agent attempts to execute (per its schedule) while Compact is running on the same database, the agent stops running. The agent is also removed from the scheduled queue. (The scheduled agent queue is an internal queue that keeps track of which agents need to run.) The agent is not returned to the queue until Agent Manager refreshes the Cache. By default, the Cache is refreshed at 12 a.m.
| Starting with Domino 8.5.2 Fix Pack 3 and 8.5.3, you can use the following parameter to force agent retry despite the Compact:
DEBUG_AMGR_ENABLE_RETRY_ON_COMPACT=1 Workaround for earlier releases The following provides additional technical details on the expected behavior: To determine if the flag has been set for a database you can use the following parameter in the Domino server’s notes.ini: debug_amgr=l (lowercase L) The following will appear in the log: “AmgrDbg: CheckDbForTask – Setting DBOPTION_NO_BGAGENT for database When the flag has been cleared by the Cache refresh or Fixup the following entry should be observed: “AmgrDbg: CheckDbForTask – Clearing DBOPTION_NO_BGAGENT for database |
The information above is from TN 1084223
Today IBM publish this FAQ about iOS 6 support with traveler
Apple iOS 6 Support: