As soon as you have finished installing the MarvelClient database on your first IBM Domino server, further procedures depend on whichinstallation type you chose for initial installation.
Local Installation
Should you want to move from a previous local installation to a server-side one, you need to perform the following steps:
- Adjust the ACL of the Config, Analyze and Help databases so that you have sufficient rights after replicating them to your servers
- Use an Objects\A5. *.ini & Variables Action to change ini:MC_DB from the previous hardcoded servername!!directory\configfilename.nsf to
%notes_homeserver%!!directory\configfilename.nsf
(Adjust directory and configfilename.nsf as needed) - Continue with either the load-balanced/production or hub/spoke option
Dedicated Server
Should you want to move from a previous ONE dedicated server installation to one across multiple servers, you need to perform the following steps:
- Adjust the ACL of the Config, Analyze and Help databases so that you have sufficient rights after replicating them to other servers
- Use an Objects\A5. *.ini & Variables Action to change ini:MC_DB from the previous hardcoded servername!!directory\configfilename.nsf to
%notes_homeserver%!!directory\configfilename.nsf
(Adjust directory and configfilename.nsf as needed) - Continue with either the load-balanced/production or hub/spoke option
Recommended for environments up to a couple of thousand users: Load-balanced/Production
Create replicas of the Config, Analyze and Help databases on all (appropriate) mail servers.
Ensure that all servers have Manager rights with role [Server] in the Config database.
Ensure that all servers have Manager rights with role [Admin] in the Analyze database.
Ensure that all servers have Manager rights in the Help database.
Ensure that the Audit All and Cleanup agents in the MarvelClient Analyze database only run on ONE server.
Recommended for large environments (many thousands of users): Hub/Spoke
Create replicas of the Config, Analyze and Help databases on all (appropriate) mail servers.
Ensure that all ALL servers have Manager rights with role [Server] in the Config database.
Ensure that the HUB server has Manager rights with role [Admin] in the Analyze database.
Ensure that all SPOKE have Manager rights without any further roles in the Analyze database.
Ensure that ALL servers have Manager rights in the Help database.
Ensure that the Audit All and Cleanup agents in the MarvelClient Analyze database only run on EITHER the hub server only, OR on all spokes but not the hub server.
See Also
Installing panagenda MarvelClient
Installation Types
Getting started in just 20 minutes (Install Wizard)
Performing a manual install of panagenda MarvelClient
Configuring the ACL of the MarvelClient Configuration database
Configuring the ACL of the MarvelClient Analyze database
Final steps for initial server-side installation
Client-side notes.ini Entries
Rollout of panagenda MarvelClient to multiple end users