Installing Remote Composer

Composers are licensed based on a thread count. By default, the server includes two threads and will activate up to two composers (limited only by the total thread count). Additional composers can be added to the server or they can be installed and run on a remote system.

The Compose component (Composer) is a system that performs message conversion tasks for the server. A server supports multiple composers, all managed by the Compose component on the server. A remote system that hosts a composer is called a Remote Composer.

 

When you install a server, the Compose component is installed as part of the Component Package and a Composer is created locally. As Composers are added, the Compose component workload is distributed automatically. Workload distribution can be manipulated by modifying the capabilities of each Composer. By default, a General Composer composes all types of messages, all enabled file types and final formats, and all template types, but each Composer can be modified to accept only certain types of jobs. This filtering enables a Composer to become specialized for certain types of conversions. It is also possible to enforce policies that would cause messages with certain types of files or templates to fail. See About Compose Component for more information.

When scaling an environment with additional connectors or components, contact Technical Support. A Technical Support engineer can assist you in correctly identifying potential bottlenecks in the system based on workload and other factors. Moreover, the Technical Support engineer can provide helpful information on the overall impact of increasing the speed and efficiency of the system. Performance and stability consulting are also available for a fee. To purchase additional Composers, contact your Account Manager. If a detailed analysis of the environment is necessary, Technical Support may recommend a fee-based consultation.

Hardware and software requirements

Remote Composer requires a system that meets the following minimum requirements.

  • Windows NT domain computer that always runs in the same domain as the server
  • Dual core processor
    • 2 GHz
    • 4GB of RAM
    • RAID 5W with 100 GB of disk space
    • Microsoft mouse or compatible pointing device

Note: Upland Upland AccuRouterecommends using a core for each compose thread that is configured to do OCR. The server comes with 4 Compose threads. You can increase the number of threads as needed. Contact your Account Manager for more information.

  • Windows 2012 64-bit, Windows 2008 R2 64-bit
  • Disable Internet Explorer Enhanced Security Configuration (Windows Component).
  • If this component is not disabled, it will not let you proceed with the installation. After you disable the component, you must reboot your system before proceeding with the installation.
  • Microsoft Internet Explorer 7.0 (minimum)

Message conversion software requirements

The Remote Composer requires one of the following applications. An item is required only if the Composer needs to convert documents into file types associated with the application. For example, if you are planning to use Crystal Reports for compose, it must be installed on the Composer.

  • Microsoft Visio 2007 for *.VSD and *.VDX message attachments
  • Crystal Reports v10.0 or earlier for *.RPT message attachments

Note: Routing Sheet templates are provided in *.DOC and *.OMTPL format, and these templates can be edited in Word and WordPad respectively.

Visual Basic for Applications is required for PowerPoint document conversion. You must install this component for PPT and PPTX document formats to compose successfully on the server. If this component is not installed, and you try to compose a PowerPoint document, you will get an error.

Additional installation requirements

Remote Composer installation also requires the following:

  • Access to the network copy of the server setup
  • Windows user account that belongs to the Administrators group
  • License key for each additional Composer

Note: A license key is not required if the local Composer is being moved to a remote system.

  • Verifying the NtfsDisable8dot3NameCreation registry value is set to 0

 

Before installing a Remote Composer on a Windows 2008 R2 system, allow DCOM port 135 as an exception. Otherwise you will not be able to add the Remote Composer.

  1. Log in to the system where you will install the Remote Composer using an account that belongs to the Administrators group.
  2. Navigate to the network share where you have kept the server setup files.
  3. Run \MessageServer\setup.exe. The InstallShield wizard opens and configures your system for installation.

  4. Click Next. The setup shows the License Agreement page.

  5. Review the License Agreement. You must scroll to the bottom of the Agreement before you can accept the terms.

  6. Select I accept the terms of the license agreement.

  7. Click Next. The Setup Type options are displayed.

  8. Select Custom and click Next. The setup shows a list of features.

  9. Select Component Package, clear all the other features that you are not installing at this time.
  10. Click Next. The setup checks the system for installation requirements and displays the results.

Note: The setup cannot continue until all required components are installed. (Double-click an item in the list for more information.) If any required components were not detected, click Cancel and click Yes to exit the setup and install the components that are required to complete the installation.

  1. Click Next to continue the installation. The setup requests logon credentials for the service account. The NT Domain and User Name fields are populated automatically based on the current Windows user.

  2. Enter the logon credentials of the service account.

    • In the NT Domain field, enter the name of the Windows domain.
    • In the User Name field, enter the user name.
    • In the Password and Confirm Password fields, enter the password for the user.
  3. Click Next. The setup validates the user account and then shows installation settings.

Note: If other installation features are included, the setup might request additional information before displaying installation settings.

  1. Review the installation settings and click Next to start the installation. The setup installs the selected component and displays a message indicating that the installation is complete.

  2. Click Finish. The Remote Composer is installed on the remote system, add the Composer to the Compose component on the server. Continue to Adding a Composer.

 

To add a new Composer to the server, go to Adding a new Composer to the server. To replace the local Composer with the new Remote Composer, go to Replacing the local Composer with the new Remote Composer. For each additional Composer you add to your environment, you must get a license key. Contact your Account Manager for more information.

 

  1. On the Start menu, click Upland AccuRoute > Upland AccuRoute Server Administrator.
  2. Expand the Server Administrator tree and select the server name.
  3. Right-click the server name and select Licensing.
  4. Click the Activate License... button. The License Activation page is displayed.
  5. Activate the license automatically or manually.
  6. After activating the license, click Close to complete the procedure.

 

  1. On the Start menu, click Upland AccuRoute > Upland AccuRoute Server Administrator.
  2. Expand the Server Administrator tree and click Components.
  3. Double-click Compose in the details pane to open the Compose Properties page.
  4. Click the Composers tab.
  5. Click Add. The Add Composer Package page opens.
  6. In the Server Address box, enter the machine name or IP address of the Remote Composer. Enter localhost if the composer is being added to the server.
  7. Click OK.
  8. Click OK to close the Composer page. The Remote Composer begins performing conversion tasks immediately.

 

You will remove the General composer in the procedure below and replace the local composer with the new remote composer.

Note: You must purchase a license key for each additional composer you add to your environment. Contact your Account Manager, if necessary.

  1. On the Start menu, click Upland AccuRoute > Upland AccuRoute Server Administrator.

  2. Expand the Server Administrator tree and click Components.
  3. Double-click Compose in the details pane to open the Properties page.
  4. Click the Composers option.
  5. Select localhost, click Delete, and then click Yes to continue. The local Composer is removed.

Tip: The local Composer must be removed first so that the new Composer can be added without a license key.

  1. Click Add. The Add Composer Package page opens.
  2. In the Server Address box, enter the machine name or IP address of the Remote Composer.

  3. Click OK to close the Composer page. The Remote Composer begins performing conversion tasks immediately.

 

See also

Installing Remote Modem Server