The following notes.ini settings should be used to do this update.
- CREATE_R85_DATABASES=1
- NSF_UpdateODS=1
- NSF_UpdatedToODS=51

Some databases, like names.nsf and bookmark.nsf, will be in use and the next time you are starting Lotus Notes these databases will be updated to latest ODS!

Policies can be used to add these settings to the Lotus Notes clients.

Bookmark:

I think this might come in handy for people that are ‘pimping’ Standard Notes web applications with dojo. I’m not talking about XPages here, just a simple Notes Web Form.

I’m not going to explain how to incorporate dojo in your form, that’s fairly simple and explained on the Dojo website.

However, if you start using the dijit.form.DateTextBox, you should note that the date format used by dojo is “yyyy-mm-dd”. I added a date field on my form, and added “”dojoType=’dijit.form.DateTextBox’” in the HTML Attributes and all seemed to work well… at first.

But when I saved and re-opened the document the values were no longer visible. They were saved in the fields, but the dijit DateTextBox requires the dates to be in the format “yyyy-mm-dd” to display them. Because I like the fact the I can put a Date in a Date Field, I don’t want to put it in a Text Field and then create a second Date Field to calculate a date…

This is a workaround:

1. Create a computed for display field (next to) the date field:

2. In the Computed For Display Field next to the Date Field, put the following @Formula:

dateField := @right(@ThisName;”_”);
@If(@GetField(dateField)=”" | @isdocbeingsaved;”";
@SetField(dateField;
@text(@year(@GetField(dateField)))+”-”+@right(“0″+@Text(@Month(@GetField(dateField)));2)+”-”+@Right(“0″+@Text(@Day(@GetField(dateField)));2)
))

3. That’s it…

Bookmark:

1. Open Domino Administrator.
2. Go to the Files tab.
3. Click ‘All’ to Change the view from ‘Tree’ to ‘All’.
4. Ctrl-A to select all, Ctrl-C to copy.
5. Switch to Excel or OpenOffice.
6. Ctrl-V to paste.

Every database on a server in Excel or OpenOffice, with all the files details.

Bookmark:

BES Express was finally released for IBM Lotus Domino, months after the release for Exchange. We installed our first server today on a Domino 8.5.2 server and everything went as smooth as it could. Take into account that BES Express is only supported on Domino 8.0.2, 8.5.1 and 8.5.2, and only for the 32-bit versions of Domino.

The installation takes a while and probably requires a reboot of your server. It doesn’t require a lot of changes to your Domino configuration. One thing you will probably need to do, is enabling DIIOP on the server. Too bad they didn’t choose LDAP here.
The new webinterface looks good and provides a lot of features the “old” Blackberry Manager client provides.

BES Express is free of charge, but if you want to download it, you need to “order” it from the Blackberry site for $0. After that, you get your SRP identifier and CAL.
The form and downloads can be found here.

Bookmark:

Setup for Security policy settings:

1. Create a new Security settings document or open an already existing Security settings document.  Settings documents are found under the People & Groups tab in Domino Administrator.
2. Select the “Proxies.”  If you do not see this tab, you may need to update the template version of names.nsf to 8.5.1 or later.
3. While the document is in Edit mode, click the “Edit list…” button.
4. Fill in the following fields:

Context: The path of the request to the proxy server, specifies which proxy the rule is for. Examples include:

/xsp/proxy/QuickrProxy/

URL: Address of the site to which this policy applies. This is the target of the proxy and will be the Quickr server’s address.

Actions: The set of HTTP actions this policy allows. These can be GET, POST, HEAD, PUT, DELETE. The most frequently used are GET and POST. For Lotus Quickr integration with Lotus iNotes, make sure that HEAD is included.

Cookies: Cookies allowed for this site. That is, the cookies that will be passed from the browser to the target URL server.

*Note – Cookies with specified names will always be proxied to this site. In addition, any incoming (Set-Cookie response headers) received from the site will also be remembered and eventually sent back on subsequent requests to this site.

Mime-types: Content types allowed back from the target server, or use * to allow all.

Headers: Headers allowed for this site, or use * to allow all. This attribute determines which headers are forwarded to the target server.

*Note - Cookies are not handled as a standard header. Putting the entry “cookie” in the headers list will have no effect.

Example:

Context:         /xsp/proxy/QuickrProxy/

URL:              http://url.quickrserver

Actions:         GET,POST

Cookies:        LtpaToken

Mime-types:   *

Headers:        *

5. Once the fields are filled out select the “Add/Modify Value ” button to complete add the rule. Select “Ok” to complete.

6. Save and close the Security settings document.

Bookmark: