Personal Blog of Thomas Hampel - Creative Mythbusting in Development and Collaboration

Upcomming Trips

Social Networks

Popular Articles

Winmail.dat

Who am I?

Feeds

 Content
 Comments

Recent Entries

What’s Next - Event
Improving the Mail Templa
Available now: HCL Notes/
Available now: HCL Notes/
Next Week : SUTOL Symposi
Query results for : September 2012

EMC SourceOne- 27 September 2012 - (0) Comments

Thomas Hampel
 27 September 2012
When running EMC SourceOne with Domino, it might happen that users can only see a subset of the mails they have received, even if the mail itself is stored in the EMC system.
Here are the details...

Problem
When logging in with Active Directory credentials, users can only see emails which have been sent to the internet address of that user.
Logging in with Notes/Domino user name and HTTPPassword, only the Lotus Notes mails can be found.

Analysis
By opening one email in each account and looking at the header, it became clear that EMC SourceOne can not associate the AD user name with the Notes user name.
The Notes user name is stored in a custom attribute of the Active Directory user object, but there is no option to customize the EMC software to make use of this attribute.

For each mail, EMC seems to use the recipients name as a string to search ActiveDirectory. So if the mail has been sent to "firstname.lastname@company.com" it will find a corresponding user in AD and can associate it with the user.
When the mail is sent to "Firstname Lastname/OU/O", there is no corresponding user in AD, at least not among the list of objects which EMC is searching in.

Those of you who have already migrated from Exchange to Domino already know that for perfect CoExistence between both systems, the AD user needs to have a Notes proxyAddress defined.
Based on this knowledge it was easy to resolve the problem.

Solution
adding the Notes user name to the list of email addresses ("proxyAddresses") in  the AD user object resolved the issue.
Image:EMC SourceOne

The result is another proxy address "NOTES:CN=Firstname Lastname/OU=X/O=Y" in addition to the internet address itself.

IBM Connections Plugins you should have- 19 September 2012 - (1) Comments

Thomas Hampel
 19 September 2012
Based on a customer request, here are the links to the most wanted IBM Connections plugins....

In order to download them you'll need to click on Image:IBM Connections Plugins you should have in the top right corner and log on with your Greenhouse account.
The button will turn into a download button once you have logged in.

IBM Connections 4.0.0 - What you need to get started- 8 September 2012 - (0) Comments

Thomas Hampel
 8 September 2012
IBM Connections 4.0.0 has just been released under part number CB89IML (For licensing details, see this document)

In order to get this deployed in a Linux environment, here are the components you need for a medium deployment.

Download the following Installation Media from Passport Advantage

IBM Connections V4.0 for AIX, Windows, Linux Multilingual eAssembly(CRJH8ML)
  • IBM Connections V4.0 Wizard for Linux, AIX Multilingual(CIA3HML) - 538 MByte
  • IBM Connections V4.0 for Linux, AIX Multilingual(CIA3EML) - 1516 MByte

IBM WebSphere Application Server for Connections 4.0 Multilingual Multiplatform eAssembly(CRJI0ML)
  • IBM WebSphere Application Server Network Deployment V7.0 for Linux on x86-64 bit, Multilingual (C1G35ML) 771 MByte
  • IBM WebSphere Application Server Network Deployment V7.0 Supplements (1 of 2) for Linux on x86-64 bit (C1G36ML) 246 MByte
    (you do not need Supplements 2 of 2 for the Pilot)
 IBM DB2 and Tivoli for Connections 4.0 Multilingual Multiplatform eAssembly(CRJH9ML)
  • IBM Tivoli Directory Integrator Identity Edition V7.1 for Linux x86, Multilingual(CZ9MMML) - 524 Mbyte
  • IBM DB2 9.7, Enterprise Server Edition - Restricted Use - QuickStart Guide and Activation Multiplatform Multilingual (CZ381ML) 2 MByte

Download the following Installation Media from Fix Central
PS: Make sure to verify your environment with the system requirements documented in Technote 703593.

Domino Program documents and schedule- 6 September 2012 - (1) Comments

Thomas Hampel
 6 September 2012
Problem: A customer reported Domino would not be responding at a specific point in time, but servers dont crash - they are unresponsive.

Analysis: Looking into the Domino server logs at about the time when the problem reported showed that some scheduled tasks were running.
While scrolling down the logs it became clear that the compact task was blocking access to the server's system databases - in this case log.nsf - which caused the server to ignore incomming requests.
From the end users point of view the server came to an halt while from the servers point of view all was okay.

Action: Getting Domino program documents scheduled perfect could be a long journey. Here is my recommendation on how to do it right.
Program Command Line Schedule Comments
convert -l mailprimary.ind 18:50 each day
Repeat interval of: 0 minutes
Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat 		Generates a list of mail files by reading people's mail files from the Domino Directory and writes the list into an IND file.
compact -A mailprimary.ind 19:00 each day
Repeat interval of: 0 minutes
Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat 		Archive data but dont reduce the mail file size, thats because compacting will be done thru another program document.
compact -B -S 20 -w 23:00 each day
Repeat interval of: 0 minutes
Days of week: Fri 		Once per week, reduce the file size if there are at least 20% whitespace in the file
Exclude system DB's with option -w , for servers before 8.5.4 this requires the variable DEBUG_ENABLE_COMPACT_8_5=1
Note: Reducing the file size for every file every day will just increase the level of fragmentation and will reduce performance.
compact -b -w 23:00 each day
Repeat interval of: 0 minutes
Days of week: Sun, Sat 		Make sure the white space is located at the end of the NSF file for better performance when creating new documents
Note : Do not run on Friday, due to backup.
compact -b log.nsf 04:30 each day
Repeat interval of: 0 minutes
Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat 		Special schedule for log.nsf after 04:00 when purge has been completed.
To make sure the white space is located at the end of the NSF file for better performance when creating new documents.
catalog 01:00 each day
Repeat interval of: 0 minutes
Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat 		Updates information in catalog.nsf
updall 02:00 each day
Repeat interval of: 0 minutes
Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat 		Updates existing views
statlog 05:00 each day
Repeat interval of: 0 minutes
Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat 		Record statistics
daosmgr resync 23:30 each day
Repeat interval of: 0 minutes
Days of week: Mon, Wed, Fri 		Every second day resync the DAOS repository
collect At server startup only Remark: Make sure the task is not loaded in the Notes.ini via “ServerTasks=”
http At server startup only Remark: Make sure the task is not loaded in the Notes.ini via “ServerTasks=”
rnrmgr At server startup only Remark: Make sure the task is not loaded in the Notes.ini via “ServerTasks=”
(n)server -c "tell sched validate" 02:00 each day
Repeat interval of: 0 minutes
Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat 		Rebuilds the clubusy/busytime
(n)server -c "tell mtc purge 7" 00:00 each day
Repeat interval of: 0 minutes
Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat 		Purge data older than 7 days from the message tracking store





Optional Program Documents for Specific Server Types
Program Command Line Schedule Comments
(n)server -c “tell router compact” 18:00 each day
Repeat interval of: 0 minutes
Days of week: Sun 		This will reduce the file size of the mail.box'es, but will increase fragmentation on disk. Not recommended for servers with high mail volume.




Of course noone is perfect, so any comments and suggestions for improvements are very welcome !
Go ElsewhereSubscribe to RSSAboutStay ConnectedAnd More
Thomas Hampel, All rights reserved.