This section provides basic reference information for what constitutes a valid notesurl value.

The entry format is as follows:

notes://Host/DominoObject?Action

Where:

• Host = a DNS entry or an IP address or IBM® Lotus® Domino(TM) server name
• DominoObject = a Domino construct (for example, a database, view, document, form, navigator, agent, and so on). URL commands for accessing DominoObjects use the following syntax:

  notes://Host/Database/DominoObject?Action where Database = the database in which the DominoObject resides.

• Action = the desired operation on the specified DominoObject (For example, ?OpenDatabase, ?OpenView, ?OpenDocument, ?EditDocument, ?OpenForm, and so on).

Syntax Guidelines

• DominoObject can be any of the following:
  • For a database -- the database name or replica ID
  • For other objects -- the DominoObject’s name, universal ID, or special identifier
  For example, to specify a view in a URL, you can use any of the following:
  • view name
  • view universal ID
• An IBM® Lotus® Notes® database can be specified by its file name, for example leads.nsf, or by placing a double underscore before the replica ID and adding an .nsf suffix to the end. For example, specify __852562F3007ABFD6.nsf.
• A DominoObject’s name and universal ID are identical in all replicas of a database. One name or alias can refer to two objects, for example two forms with the same name when one is hidden from Notes users and one is hidden from Web users.
• Action can be explicit or implicit. Examples of explicit actions include ?OpenDatabase, ?OpenView, ?OpenDocument, ?OpenForm, and ?EditDocument. Examples of implicit actions include ?Open, ?Edit, and ?Delete. If you do not specify an action, Domino defaults to the ?Open action.
• Because URLs cannot contain spaces, use the + (plus sign) or the hex value %20 to represent a space. For example:
  • notes://www.merabx.com/discussion.nsf/By+Author
  • notes://www.merabx.com/discussion.nsf/By%20Author
• If you are generating your own URLs for any part of an application, use simple aliases whenever possible to avoid URLs with unsupported characters.

OpenDatabase

Sample syntax and examples are presented.

Syntax

notes://Host/__DatabaseReplicaID.nsf?OpenDatabase

Examples

notes://www.merabx.com/leads.nsf?OpenDatabase

notes://www.merabx.com/sales/discussion.nsf?OpenDatabase

notes://www.merabx.com/__852562F3007ABFD6.nsf?OpenDatabase

OpenView

Sample syntax and examples are presented.

Syntax

notes://Host/Database/ViewName?OpenView

notes://Host/Database/ViewUniversalID?OpenView

Examples

notes://www.merabx.com/leads.nsf/By+Salesperson?OpenView

notes://www.merabx.com/leads.nsf/DDC087A8ACE170F8852562F300702264?OpenView

OpenFrameset

Sample syntax and examples are presented.

Note The URLs shown below are for example only. They do not point to existing Web sites.

Syntax

notes://Host/Database/FramesetName?OpenFrameset

notes://Host/Database/FramesetUNID?OpenFrameset

Examples

notes://www.merabx.com/discussion.nsf/main?OpenFrameset

notes://www.merabx.com/discussion.nsf/35AE8FBFA573336A852563D100741784?OpenFrameset

OpenForm

Sample syntax and examples are presented.

Syntax

notes://Host/Database/FormName?OpenForm

notes://Host/Database/FormUniversalID?OpenForm

Examples

notes://www.merabx.com/products.nsf/Product?OpenForm

notes://www.merabx.com/products.nsf/625E6111C597A11B852563DD00724CC2?OpenForm

Creating a Notes URL that points to the user mail file and other user settings

Use the following examples for creating a Notes URL that points to a user mail file and to other user settings:

• User's mail file -- Example: Notes:///0000000000000E00
• User's address book -- Example: Notes:///0000000000000E01
• User's subscriptions -- Example: Notes:///0000000000000E02
• User's bookmarks -- Example: Notes:///0000000000000E03
• Current database (this is used to address components in the same database as the composite application definition) -- Example: Notes:///0000000000000000

Assembling and wiring your composite application
Additional methods for creating Notes-based applications
Deploying and testing your composite application

Glossary