Home
IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
Application Management
Welcome to the Application Management section of Domino® Designer Help.
Deploying an application
The tasks involved with application design, database design, database management, and DominoTMsystem administration may overlap, depending on the size of your organization and the structure of job responsibilities. In some organizations, an application developer may be responsible for both application and database design, while in others, a database manager may handle all database design and management tasks. In addition, database management overlaps with Domino® system administration.
Replication settings
By default, two replicas exchange all edits, additions, and deletions if the servers the replicas are on have the necessary access. However, you can customize replication. For example, to save disk space, you can prevent the transfer of irrelevant documents. Using replication settings, you can:

IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
- Application Design
  Welcome to the Application Design section of Domino® Designer Help.
- Domino® Designer templates
  The templates described in the following table are available with Domino® Designer and are specifically intended for use by application developers.
- Importing to and exporting from views
- Developing applications using MAPI
  Domino® Designer Release 6 and later supports the messaging application program interface (MAPI), which allows mail integration between Domino and a MAPI-compliant messaging application, such as Microsoft™ Outlook, Microsoft Office applications, or user-written C++ programs.
- Features to avoid using in Web applications
  Developers creating applications specifically for the Web, or for the dual purpose of serving Notes® and Web clients, should review the following tables for features that are not supported on the Web.
- URL commands for Web applications
  You have a variety of options for programming a Web site. You can directly manipulate objects such as documents or views in an application using Domino® URL commands. Adding Domino URL commands as HTML in forms gives users shortcuts for navigating databases and performing other tasks quickly.
- Application Management
  Welcome to the Application Management section of Domino® Designer Help.
  - Security in an application
    Domino® offers a multi-layered approach to security. Server administrators can secure databases, servers, and domains. Database designers and managers control the following:
  - Completing an application and managing design changes
    As you prepare to deploy an application, consider these finishing touches:
  - Deploying an application
    The tasks involved with application design, database design, database management, and DominoTMsystem administration may overlap, depending on the size of your organization and the structure of job responsibilities. In some organizations, an application developer may be responsible for both application and database design, while in others, a database manager may handle all database design and management tasks. In addition, database management overlaps with Domino® system administration.
    - Rolling out a database
      As you roll out your application, you need to work closely with your Domino® server administrator to organize your application on a server and perform a set of administrative tasks. The following tables list the mandatory and optional tasks that the Domino administrator performs to put a database into production. You must have Manager access in a database access control list (ACL) to perform these tasks.
    - Copying a new database to a server
    - Setting up replication for an application
      As you prepare to deploy an application, you must work with your Domino® server administrator to create a replication plan. Replication allows replica copies of databases to exchange updates. You can replicate both design elements and database content between replica copies. Replication can be unidirectional -- for example you can push out design changes but not receive any, or it can be directional, in which cases changes are both sent and received. Generally you perform design work on one copy of a database -- for example, you might keep a copy on your local hard drive -- then you replicate design changes to database replicas on servers.
    - Creating one replica manually
      These steps create one replica of a database.
    - Replication settings
      By default, two replicas exchange all edits, additions, and deletions if the servers the replicas are on have the necessary access. However, you can customize replication. For example, to save disk space, you can prevent the transfer of irrelevant documents. Using replication settings, you can:
      - Limiting the contents of a replica
      - Assigning miscellaneous replication settings
        The Other panel of the Replication Settings dialog box includes these miscellaneous settings.
      - Limiting what a replica sends
        Use these settings to limit what one replica sends to other replicas.
      - Specifying replication settings
      - Examples of specifying replication settings for multiple replicas
        The following examples describe scenarios for various types of replication.
    - Disabling and enabling replication of a database
    - Forcing a server database to replicate
  - Procedure for optimizing and troubleshooting databases
- Composite Applications - Design and Management
  Composite applications are a key element in a service-oriented architecture (SOA) and contextual collaboration strategy. The ability to create and edit composite applications lets you easily integrate different types of components and technologies.
- DB2® Access views
  Domino® Designer includes two types of design elements to assist you in managing data contained in DB2® enabled Notes® databases:
- Programming Overview and User Interface
  This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
- Formula Language
  This section documents the formula language.
- LotusScript® Language
  Welcome to the LotusScript® Language section of Domino® Designer Help.
- LotusScript/COM/OLE Classes
- Java/CORBA Classes
  This section documents the Java/CORBA classes.
- Lotus® Connectors
  Lotus® Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
- Javadoc™ for Domino® Designer related APIs
  As part of providing additional Java™ reference documentation, Domino® Designer ships with a help plugin that contains Javadoc™ for additional Domino Designer related APIs.
- Accessibility and keyboard shortcuts
  Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.

Replication settings

By default, two replicas exchange all edits, additions, and deletions if the servers the replicas are on have the necessary access. However, you can customize replication. For example, to save disk space, you can prevent the transfer of irrelevant documents. Using replication settings, you can:

You can specify replication settings when you create a replica or on an existing replica. You can specify some replication settings for multiple replicas at once from one replica. You must have Manager access to a replica to set replication settings for it.

CAUTION: Replication settings are not intended to be used as a security measure.

This table summarizes the available replication settings. An asterisk (*) marks the settings you can manage for multiple replicas from a central source replica.


Setting	Controls	Panel in File - Replication - Settings dialog box
Remove documents not modified in the last x days	When Domino® purges document deletion stubs and, optionally, unmodified documents.	Space Savers panel
Only replicate incoming documents saved or modified after: date	The cutoff date, so that a replica only receives documents created or modified since the date. Which documents are scanned during the first replication after clearing the replication history.	Other panel
Receive summary and 40KB of rich text only	The size of documents that a replica receives.	Space Savers panel
Replicate a subset of documents*	Which documents a replica receives.	Space Savers panel Advanced panel
Replicate*	Which non-document elements this replica receives.	Advanced panel
Do not send deletions made in this replica to other replicas	Whether a replica can send document deletions to other replicas.	Send panel
Do not send changes in database title and catalog info to other replicas	Whether a replica can send changes to the database title and Database Catalog categories to other replicas.	Send panel
Do not send changes in local security property to other replicas	Whether a replica can send changes to the Encryption database property (in the Basics tab of the Database properties box) to other replicas.	Send panel
Temporarily disable replication	Whether a replica can replicate.	Other panel
Scheduled replication priority	The replication priority of a database used in Connection documents for scheduling replication.	Other panel
CD-ROM publishing date	The publishing date for a database on a CD-ROM.	Other panel