Optimizing Argos for WAN environments

Argos 7 is designed to be scalable in WAN environments with many remote offices. The following configuration changes are recommended to limit the amount of traffic generated by the remote servers.

Adjust Argos Communication Service connection settings

The Argos Communication Service is designed as the "gateway" from each remote office to the SQL Server. If the connection to the SQL Server fails, the communication service will continue to function, receive activity and prompt users for billing. It caches information about users, projects, statuses, media and activity locally. The frequency at which these caches are updated can be configured to communicate across the WAN less often.

The following settings can be found in c:\Program Files\Sepialine\Argos7\Communication\AppServer.Communication.Service.exe.config:

        <add key="JobsUpdateIntervalInSeconds" value="1"></add>
        <add key="UsersUpdateIntervalInSeconds" value="20"></add>
        <add key="DevicesUpdateIntervalInSeconds" value="30"></add>
        <add key="MetadataUpdateIntervalInMinutes" value="2"></add>
        <add key="ClientCleanupIntervalInMinutes" value="10"></add>
        <add key="ClientInactivityTimeoutInMinutes" value="5"></add>
        <add key="DimensionsDetectorUpdateIntervalInSeconds" value="300"></add>
        <add key="PhoneOptionsUpdateIntervalInSeconds" value="120"></add>

If you are experiencing more WAN traffic than usual, we recommend changing to:

        <add key="JobsUpdateIntervalInSeconds" value="10"></add>
        <add key="UsersUpdateIntervalInSeconds" value="200"></add>
        <add key="DevicesUpdateIntervalInSeconds" value="300"></add>
        <add key="MetadataUpdateIntervalInMinutes" value="20"></add>
        <add key="ClientCleanupIntervalInMinutes" value="100"></add>
        <add key="ClientInactivityTimeoutInMinutes" value="50"></add>
        <add key="DimensionsDetectorUpdateIntervalInSeconds" value="3000"></add>
        <add key="PhoneOptionsUpdateIntervalInSeconds" value="1200"></add>

Disable unnecessary  Argos services

The Argos Application server installs a number of services that are used for various purposes. Not all are required in every installation. To limit bandwidth and CPU usage, you can disable any services not actually in use.

Argos Application server installs these services:

• Argos Communication Service (always used, do not disable)
• Argos Express Keypads (used when Argos Keypad hardware is connected to legacy MFPs)
• Argos Integration (always used, do not disable)
• Argos Keypad Gateway (used when Argos Keypad hardware is connected to legacy MFPs)
• Argos OnBoard for Canon (used with Canon MFP integration)
• Argos OnBoard for HP (used with HP small format MFP integration)
• Argos OnBoard for Konica Minolta (used with Konica Minolta MFP integration)
• Argos OnBoard for Sharp (used with Sharp MFP integration)
• Argos OnBoard for Xerox (used with Xerox MFP integration)
• Argos Release Broker (used with Argos Secure Release)
• Argos Secure Release for mobile (used with Argos Secure Release)

If all services are installed, you can disable them through services.

1. Click Start>Run and type "services.msc"
   
2. Double-click on any services that should not be used
3. Change "Startup Type" to "Disabled"
4. Change "Service status" to "Stopped"
   
5. Click "OK"

You can also disable these services during the Argos installation.

1. Instead of clicking "SetupLauncher.exe" during installation, choose Argos7Installers\AppServer\Setup.exe
2. When prompted for "Custom" or "Complete" install, choose "Custom"
3. Uncheck any services you do not want to install
   

Remove unnecessary WAN traffic

In a large Argos installation, there are a lot of components running on a lot of computers. Are they all talking to the correct place?

The biggest cause of WAN traffic in an Argos environment is typically user workstations that are connecting to the wrong Argos Communication service.

In a multi-office environment, there is typically an Argos database in one office, and Argos Communication services in each office.

If 50 workstations in a San Francisco office are talking with the communication service in New York, this will create a large amount of extra network traffic.

Smart Deployment

In any large install, planning ahead can save a lot of time later. There are typically two methods for pushing the Argos client to workstations - The Argos Deployment Center and an MSI file.

The Argos Deployment Center is designed for a single office installation - if you're using it with multiple offices, we recommend installing it in each office and configuring it separately.

A better option is to deploy an MSI file via Active Directory Group Policy, SMS, or whatever other remote deployment tools the IT department is used to working with. Custom transform files can be made for each remote office to ensure workstations are connecting to the correct Argos Communication service.

Even when deploying via MSI, you can use the Argos Deployment Center to see which Communication service is used by a particular workstation:

The Deployment Center works best in an environment where computers are organized in Active Directory by office - this way, it is simple to see which Communication service a workstation should be talking to.