Application Delivery Management
Application Modernization & Connectivity
CyberRes by OpenText
IT Operations Management
When a domain's MTA loads it reads a configuration file called 'domainname.MTA'. This configuration file as several switches in it that if set can increase the performance of the MTA. A majority of the switches in the configuration file are also available via ConsoleOne and the MTA object. Some are not. I will note here that you should always make sure to fill in the attributes in the eDirectory MTA objects. This ensures those attributes are logged into the databases and synchronized with the rest of the GroupWise system. Even if I am using an attribute in an MTA configuration file, if that attribute exists in the eDirectory object, I fill it in. Let's look at a few MTA configuration file switches.
When GroupWise is installed, the objects appear in eDirectory. Most day to day management of GroupWise is as simple as managing these objects. Where in eDirectory should the GroupWise objects be placed? The answer is it depends. The majority of the time, I recommend a GroupWise Organizational Unit (OU) underneath the Organization (O) in the eDirectory tree. This assumes GroupWise is managed centrally and that the Primary Domains MTA will have eDirectory access to read the users for its 'eDirectory User Sync' process from a ROOT or O eDirectory replica. If GroupWise is managed by container or site administrators, then having the appropriate site-oriented GroupWise objects located in the site container makes sense. However, in the last several years organizations have been centralizing GroupWise into one data center, and clustering it. So, site administrators for GroupWise are slowly fading away.
There is very little that requires additional tuning in the domain eDirectory object. The two items I see most are the Description and Administrator attribute. While these do not directly affect the performance of GroupWise they do ease the management, especially when someone new comes along to manage the GroupWise system.
In the case of the MTA eDirectory object, there are quite a few attributes that should be filled in. The first of which is the Description. This attribute is read by the MTA when it loads on the server and shows the information input on the MTA server screen. I recommend placing the IP address and ports of the MTA as well as the name of the domain it is servicing. See Figures 6 and 7 below.
The Agents Setting tab of the MTA object has 2 attributes that can increase the performance of the GroupWise message flow. They are:
The MTA Log Settings tab requires a bit of work. I always recommend stating where the MTA Log files are to be located. This helps new administrators find these log files and it also leaves no doubt as to where they are being written. A tip here, I prefer to create a subdirectory underneath the domain directory called 'LOGS' and I point all MTA and child gateway logs to this directory. Since the MTA and the gateways have different naming conventions for their logs, the logs are not overwritten. Finally, I always recommend Verbose mode. It provides more information and is very handy when trying to troubleshoot issues with an MTA. See Figure 9.
The last MTA parameter I like to tune is the Scheduled Events. As I stated earlier, I want the Primary domain to handle all eDirectory User Synchronization. Therefore, I do not allow the other MTA's to run a Schedule Event. This makes the Primary domain MTA the single point of failure for eDirectory User Synchronization, but in most organizations this process only runs once a day and only the 'delta' is synchronized. The Primary Domain's MTA scheduled event I set to some off time preferably with backups are not running. See Figure 10.
A tip for you: If you use the GroupWise 6.02 snap-in's against a GroupWise 6.5 database, you will find an 'Interval' setting for MTA Scheduled Events. This 'interval' setting allows you to set an hourly eDirectory User Synchronization schedule, very helpful in large systems with lots of daily changes. See Figure 11.
Setting the Primary domains MTA as THE eDirectory Synchronization MTA also requires you to go into ConsoleOne under Tools| System Operations| eDirectory User Synchronization and 'Change Assignment' for all domains in the GroupWise system. See Figure 12.
This brings me to the end of this article. Keep in mind that Best Practices are created every day by finding new and improved ways to make GroupWise run longer and stronger, not to mention faster. With a few domain design changes and a couple parameter adjustments your organizations GroupWise system will become more fault tolerant, have increased stability and be easier to manage.