Category: <span>Uncategorized</span>

What are IBM Lotus Quickr Limits?

Below are the known best practices for IBM Lotus Quickr server in numbers:
– Files limit size to upload?
Theoretically there is no limit but we recommend not uploading files greater than 1GB. Unlimited upload size is set by setting Maximum size of request content to 0 in the HTTP tab of the Server document.

– Room limit size?
This is dictated by the maximum database size in Domino, which is 64GB. However, we don’t recommend DBS greater than 15 GB as this is when corruption or other errors begin to occur.

– Folder limit size?
Again, this must remain with the 64 GB limit of the database.

– How many level of sub-folder can we use?
If created only through the Web UI, there is no limit. There is an issue in later releases if the folders are created using the Connector and the Web UI, there was a limit of 8 folders deep, but this is now resolved.

– How many level of sub-room can we use?
This has been tested up to 500 rooms, without hitting any issue

– Is it a limit of number of characters for Folders and rooms name?
256 characters because of a Microsoft limitation.

– What are the forbidden characters for folders and rooms name?
| @ * ? < % " / { } [ ] – What are the issues already encountered that we can avoid?
I’m not sure I understand this question. Can you please clarify what you are looking for?

– Number of characters for a document?
Again, 256 characters because of the MS limit

– Number of folder you can have?
10,495, but we recommend no more than about 7,000 as this is when we begin to see issues.

from TN 1613591

The goal of this white paper is to explain the various administration and configuration tools offered by IBM WebSphere Portal 8.0. Learn about which tool to use for which task and about the new capabilities of WebSphere Portal 8.0, and understand differences from previous versions of WebSphere Portal. We take you through exercises for each tool so you can learn hands-on how to use them.

In this white paper

• Introduction
• What is WebSphere Portal?
• Installing WebSphere Portal
• Understanding the WebSphere Portal file system structure
• Installing the latest Combined Cumulative Fix
• Command line tools
• Administration user interface: Admin portlets
• WAS Admin user interface
• Conclusion
• Resources
• Author biography

I’m working on a project to migrate the portal version.  The  portal server use a remote WCM.
We need to migrate a Portal Server environment and WCM environment.
There  is no path to migrate Portal Server V6.0 to Portal Server V7.0, only Express, Enable and Extend and this situation is not documented by IBM.
I opened a PMR and the lab told me to upgrade Portal Server V.6.0 using WCM 7.0 binaries.
If you didn´t know, in Portal V6, Portal and WCM was the same binaries and if you wish WCM after the setup process you run a command line to setup the wcm authoring interface, etc, etc.
Since Portal 6.1 the binaries of WCM and Portal is not the same, you need to download different images from passport advantage.

IBM forgot that some customers have Portal Server installed. Imagine if my client doesn´t have the WCM license….

There are two different ways you can setup the size restriction of message on Domino server

1) you can create a mail server rule on the Domino server, it’s in the Domino configuration document -> Router/SMTP tab -> Restrictions and Controls tab -> Rules tab

Create a mail server rule for Size (in bytes) is less than or is greater than any size you want, and you have options to journal this messages, move to database, don’t accept message, don’t deliver message, change routing state or stop processing.

2) you can also restrict the message size using a setting in the Domino configuration document -> Router/SMTP tab -> Restrictions and controls tab -> Restrictions tab -> “Maximum message size” field.

The maximum message size in KB the server accepts.  The router rejects any messages that exceed this size for both transfer and delivery.  A non delivery message will be returned to the sender reporting the reason of the failure. The default is 0 KB, which does not limit message size.  

Both Size restriction is applied on total size of messages, not attachment.  Total size of messages which include the attachment, body of messages and headers information.  So if you need to make sure certain size of attachment go through you have to add some additional size for the size restriction on the server.

The maximum number of worker thread for each Internet protocols is by default 40. Using notes.ini you can modify the worker threads for each protocol

LDAPMaxWorkerThreads=#

SMTPMaxWorkerThreads=#

IMAPMaxWorkerThreads=#

POPMaxWorkerTreads=#

DIIOPMaxWorkerThreads=#

HTTPMaxWorkerThreads=#

  Note: that HTTP is currently the only protocol where worker threads can be set in the server document.

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.

1. Increase the “Minimum size of object before Domino will store in DAOS” setting to the newly desired value in the server document.  Note:  Do not use special characters such as commas or periods when entering the minimum size.
2. Restart the Domino server to enable the new minimum size.
3. Run a copy style compact (compact -c) on all databases that currently have DAOS enabled to allow the server  to bring the small attachments back into the mail file.
4. Wait for the “object deletion” interval to pass for prune to remove the small .nlo files.  If you have taken a recent backup and would like to delete the small files more immediately you can run the following command:

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.

1. Change the “Defer object deletion” interval to your newly desired value.
2. Wait for prune to run at 2:00 a.m. or start manually with the console command:

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.