Enabling & Disabling the Agents and signing the DB

To enable an agent in the database on the database in question through domino designer and on the left hand pane select code->agents-> we should double click the agent tab then we would see the list of agents in the right side work area ? Now select the specific agent you would want to enable/disable by either right clicking it or do it by selecting the button on top.

In the figure where you see the agents which marked in red must be double clicked, this will list all the available agents in the right hand side. Right click on any agent and disable and sign it.

If you have to sign the whole database you would have to select xx.nsf on the left hand side and click the sign button on top, which will sign the database. Please be sure to log in using your correct ID file. It is certainly simple.

How to run back-to-back NSDs on Windows systems to troubleshoot performance or hang issues

Question

You are encountering numerous hangs or periodic slowdowns on your Lotus Domino server running on a Windows system, and have been advised by IBM Support to run frequent NSDs, also referred to as "back-to-back" NSDs.

Is there a way to do this without having to continually close the NSD windows (which ultimately forces a restart of Domino)?

Answer

It is possible to run periodic NSDs while the Domino server is up and running. The steps to do so vary by Windows platform (as well as version of NSD) and are outlined below.

Windows 2003, 2008 & XP

Windows 2003, 2008 and Windows XP allows for a debugger to detach from the process without terminating that process.

---

IMPORTANT NOTE: If still attached, you must issue the NSD command "detach" before exiting NSD.

---

1. Open a DOS Prompt window and change directories to your Domino\data directory

2. Execute NSD. You will need specify the explicit path to nsd.exe, which is normally found in the Domino program directory.

3. NSD will run and write information to the console. When it finishes execution, depending on the version of NSD you are running, NSD will display its own command prompt "nsd>". Do NOT exit NSD (by either closing the command prompt window, or typing exit).

4. Periodically, at the time of the slowdown, or as directed by IBM Support, type the word "DUMP" in the NSD window. This will result in the collection of call stacks an additional time by NSD. Other sections of data may be gathered such as "memcheck" by issuing the appropriate command.

By leaving the original NSD window open, you have the opportunity to capture NSDs when the server is running efficiently and when it is not.

Versions of NSD

In versions of NSD prior to Notes/Domino 7.0.2, on Windows 2003, 2008 & XP, NSD will still remain attached to all processes, but you can detach from all processes using the "detach" command at the NSD prompt.

Beginning in Notes/Domino 7.0.2, NSD will automatically detach from all processes on Windows 2003, 2008 & XP. If you wish to remain attached, you may use the NSD -monitor switch, and issue the command "detach" when you are ready to quit NSD.

NSD Log Results

The output of each execution of NSD will be written to the IBM_Technical_Support directory, relative to your Domino\Data directory. In cases where you execute back-to-back dumps before exiting NSD, the data from each subsequent dump will be appended to the same NSD file. In cases where NSD automatically detaches from Notes/Domino on Windows 2003, 2008 & XP, multiple NSD files will be generated. You will need to provide each NSD to the Software Engineer you are working with.

NSD in windows

http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21204263

Installing Domino Step by Step

http://www.techyv.com/article/step-step-installation-ibm-lotus-domino-85

Manual NSD in Windows ?

Detailed information for the notes.ini Keyword: NSD_LogDir

Short Description: Defines a directory where NDS files will be placed.

Description:

In Domino 6.x, the NSD output is generated in different locations, depending on how it is executed. If you create NSD output manually by executing the tool from the DOS prompt, the file will be generated in the Data directory. Administrators can change this default location, using the NSD_LOGDIR Windows environment variable. NSD output will be placed in the directory to which NSD_LOGDIR points.

If NSD is triggered by the panic handling code, in response to a crash, the output is put in the diagnostic directory. The diagnostic directory defaults to the IBM_TECHNICAL_SUPPORT directory under your Data directory, but can be modified by the Logfile_Dir INI parameter. Note that NSD will still be generated in the Data directory, if you manually run it.

An enhancement request was submitted to Lotus software Quality Engineering to have NSD logs by default be written to the IBM_TECHNICAL_SUPPORT directory; however, there are no plans to address this in the 6.x code stream.



Default value:
None

Syntax:
NSD_LogDir=drivename and folder

Example:
NSD_LogDir=D:\logs\NSD

Replication Types

Replication Type:

Four Different types of replication exist. The type you choose affects the direction of
replication as well as which of the servers performs the work of the replication.
Pull Pull: Replication is bidirectional, whereby the source server initiates replication and pulls
documents from the target server. The source server then signals the target server's Replica task to
pull documents in the opposite direction. Both servers are involved in the replication.
Pull Push (Default): Replication is bidirectional, whereby the source serves’s replica task performs all
of the work, pushing and pulling documents to and from the target server. The target server's Replica
task is never engaged.
Pull Only: Replication is one-way, whereby the source server pulls documents from the target.
Push Only: Replication is one-way, whereby the source server pushes documents to the target.

Router Tell commands

The table below describes other Tell commands you can use with the Router task.

Command	Result
Tell Router Delivery Stats	Shows Router delivery statistics.
Tell Router Compact	Compacts MAIL.BOX and cleans up open Router queues. You can use this command to compact MAIL.BOX at any time. If more than one MAIL.BOX is configured for the server, each MAIL.BOX database will be compacted in sequence. By default, MAIL.BOX is automatically compacted at 4 AM.
Tell Router Show Queues	Shows mail held in transfer queues to specific servers and mail held in the local delivery queue.
Tell Router Exit	Stops the Router task on a server.
Tell Router Update Config	Updates the server's routing tables to immediately modify how messages are routed. This removes the 5 minute delay before a Router configuration change takes effect. To determine the best route for delivering a message to its destination, the Router creates routing tables, which map a path to the destination. The routing table derives information from variables in the NOTES.INI file and from the Configuration Settings, Domain, Connection, and Server documents in the Domino Directory. The command does not update the routing tables with changes made to the Global Domain document. By default, mail the router automatically refreshes its configuration every 5 minutes to absorb changes made in its sources. In previous versions of Domino, you had to restart the router task to update the routing tables after making changes in the sources documents. The command is case insensitive. Caution If the Tell Router Update Config command is initiated on an R5 server, it loads shared mail. The Tell Router U portion of the command loads shared mail on R5 servers.
Tell Router Quit Load Router	Stops the Router task on a server. Start the Router task on a Server