Here are a few examples of tasks that you might do with server-based agents:

• Collect mail file statistics, such as mail file size.
• Add signatures to mail files.
• Act on faxes or voicemail messages.
• Do tasks related to the use of Customer Relationship Management (CRM) tools.

The following requirements apply to using server-based agents:

• Agents can run against mail files in the service but not against other databases in the service.
• The agents must be signed with the server ID of the server on which they run. See the steps in this article.
• The name of the server (agent signer) must have access to the mail files. To grant this access, you must add the server to a group in your directory, then add the group to mail files ACLs as type "Mixed group." To add the group to the mail file ACLs of existing users, see the topic Changing and viewing mail file access in the Administering SmartCloud Notes documentation. To add the group to the mail file ACLs of new users as you provision them, use a customized mail file template. For more information see the topic Preparing to use custom mail file templates.
• The server on which the agents run must be under the same organization certifier as the mail server in the service that hold the mail files, or the server must be cross certified with that certifier. For example, if the mail server is under /SCN/Renovations, then the server that runs the agent must be under the /Renovations organization or must be cross-certified with /Renovations.
• There must be a Connection document in the on-premises directory that enables the server that runs the agent to connect to the mail servers in the service. See the steps in this article. If you run the agent on a server that already connects to the service, for example, on an on-premises directory synchronization server or mail hub server, the Connection document will already exist and the steps are unnecessary.
• Public key checking must be disabled on the server that runs the agent. See the steps in this article. If you run the agent on a server that already connects to the service, this setting should already be disabled.

Signing the agent with the server ID file
1. From the Domino Administrator client, open the host server.
2. From the Files tab, select the database with the agent.
3. Click Tools > Database.
4. Click Sign...
5. In the dialog box that opens, click Active Server's ID, under the heading Which ID do you want to use?
6. Click OK to sign all database design elements with the host server ID.

The administration process (AdminP) signs the database. Signing is complete within a minute or two. Any errors are written to the server log file.

Creating a Connection document to connect to mail servers in the service
If there is no Connection document that connects the server that runs the agent to the mail servers in the service, complete the following steps to create one in the directory. If the server that runs the agent is in the same Domino domain as the on-premises directory synchronization server or mail hub server, the Connection document already exists and you can skip this procedure.

1. Open the Domino directory.
2. Click Configuration > Servers > Connections.
3. Add a Connection document with the following settings.

Table 1. Connection document used to connect to the service

Field	Value	Additional information
Basics - Connection type	Local Area Network	None
Basics - Source server	*	None
Basics - Source domain	Domino domain of the mail servers in the service, for example, PowerRenovations	Specify the same value for the Source and Destination domains.
Basics - Use the ports	Appropriate TCP/IP port	None
Basics - Usage priority	Normal	None
Basics - Destination server	*mail_server_certifier	For example, if the certifier used for your mail servers in the service is /SCN/Renovations, type */SCN/Renovations.
Basics - Destination domain	Domino domain of the mail servers in the service, for example, PowerRenovations	Specify the same value for the Source and Destination domains.
Basics - Optional network address	The host name that corresponds to the data center your company uses: notes.na.collabserv.com (North America) notes.ap.collabserv.com (Asia Pacific) notes.ce.collabserv.com (Europe)	DNS host name of the proxy server in the service.
Replication/Routing - Replication task	Disabled	None
Replication/Routing - Routing task	None	None
Schedule	Disabled	None

Disabling public key checking
Complete the following steps to disable public key checking on the server that runs the agent:

1. Open the Server document in the directory.
2. Click the Security tab.
3. In the Compare public keys field in the Security Settings section, select Do not enforce key checking.

How to invoke the agent ?
You can either schedule the agent, or run a below command to invoke it .

1) tell amgr run "db.nsf" 'agentname' .

2) You can also invoke the agent via a browser, http://Host/Database/AgentName?OpenAgent

It was identified that, invoking the agent by right click

---