Deacom Cloud Local - Previous Versions

Deacom Cloud Local makes network-accessible peripherals inside a company network available to a Deacom application server running remotely. This agent was built for customers of Deacom's managed cloud services, but can be used by any customer running an off-premises Deacom application server.

Deacom Cloud Local complements Deacom Local running on each individual user's workstation. Where Local makes an individual workstation's peripherals available to the browser running Deacom, Cloud Local runs as a service on one Windows machine to make network-accessible peripherals available directly to the Deacom application server. This allows all clients, including mobile and WMS users, to access these peripherals.

Notes:

  1. Deacom Cloud Local is available in versions 15.03 and later.
  2. Beginning in version 17.03, the Deacom installation program will automatically add a new entry, "CLOUDLOCALPORT", to the .ini file during installation/upgrading. This entry is used to connect Deacom Cloud Local Service with the Web Service/Console and Automation Service. The value defaults to '1091'.

Installing DEACOM Cloud Local Service

Setup & Configuration

Cloud Local runs on a server in the customers network and requires firewall changes. It is recommended that Cloud Local is installed on an already configured print server.

Server

  1. Identify the server that will run Deacom Cloud Local and install and configure the desired printers.
  2. Obtain a copy of the Deacom Cloud Local installer. Since the Deacom application server is not accessible, Cloud customers can request a copy of the installer to be placed in their client FTP directory.
  3. Run Deacom.Cloud.Local.Installer.msi on the server that will host the Deacom Cloud Local service.
  4. The installer will create a shortcut to Cloud Local Options on the desktop. Double-click the shortcut to open the Cloud Local Options dialog.
  5. Set the Service URL and Service Port to the public hostname and port of the Deacom application server. See the example Cloud Local Options screenshot below for more information.
    1. Please note, it is essential to input the "https://" in the address in order for Cloud Local to properly function.
  6. Set the Local URL and Local Port to the public IP of the location running Cloud Local and the port that is opened in the client site firewall and forwarded to the internal machine hosting the Cloud Local service.
  7. In the list of printers displayed, select each printer that should be made available to the Deacom application server.
  8. Save and close the Cloud Local Options dialog.

Firewall

Configure the customer network firewall and Cloud Local server firewall for Cloud Local traffic. The Cloud Local service connects to the Deacom application server with instructions for establishing a connection back to the Cloud Local service running on the customer's network.

The customer will need to make the following firewall changes:

  1. App server firewall:
    1. Create an incoming access rule to allow incoming traffic from the Cloud Local public IP to the Deacom application server on the specified automation service port.
    2. For Deacom MCS customers, open a service ticket to allow access with the cloud hosting department. For non-MCS customers, the customer IT department is responsible for this configuration.
  2. Network firewall:
    1. Create an incoming Access Rule to allow incoming traffic from the Deacom appserver IP on any port to the customer public IP and port.
      1. The Deacom appserver IP is the same IP that the scanners connect to. It can also be found by pinging the web URL (Service URL) or requesting it from the Deacom team.
      2. The customer public IP and port are the same as the Local IP and Port from Cloud Local Options. See the Cloud Local Options screenshot for more information.
      3. The Deacom application server will use a random TCP port to connect to Cloud Local. To prevent communication issues please allow all ports.
    2. Configure a NAT to translate the customer public IP and port to the private IP and port of the server running Cloud Local.
  3. Cloud Local server firewall (if needed):
    1. Create a firewall rule to allow incoming traffic from the Deacom appserver IP on any port.

Additional Steps

To confirm the printer is accessible using the main application

  1. Navigate to any location in the system where you can print something (grid, lot label, etc.).
  2. When selecting a printer, verify that the printer(s) you selected are shown as available printers with the label (Cloud Local).
  3. Print to a Cloud Local printer. Verify that the label/form/report prints correctly and to the correct printer.
  4. If desired, try to print a ZPL label to a ZPL printer. Verify that the label is able to print correctly.

To confirm the printer is accessible using the scanner

  1. Navigate anywhere in WMS where you can print something (such as Find Inventory or finishing a job).
  2. When printing, verify that the printer(s) you selected are shown as available printers with the label (Local).
  3. Print to a Cloud Local printer. Verify that the label/form/report prints correctly and to the correct printer.
  4. If desired, try to print a ZPL label to a ZPL printer. Verify that the label is able to print correctly.

To setup Deacom Cloud Local for non production environments (Test, Validation, etc.), please follow these instructions.

  1. Navigate to Deacom Cloud Local install path (default is C:\Program Files\Deacom).
  2. Copy ‘Cloud Local’ directory and name it ‘Cloud Local Test’.
  3. Go into ‘Cloud Local Test’.
    1. Run Deacom.Cloud.Local.Options.exe and update the options as desired per the Setup section.
  4. Run the following command from an elevated Command Prompt
    1. Sc create Deacom.Cloud.Local.Test binPath= "C:\Program Files\Deacom\Cloud Local Test\Deacom.Cloud.Local.Service.exe" depend= nlasvc/pla start= auto displayname= “Deacom Cloud Local Service Test” obj="NT Authority\NetworkService"
  5. Start the new service.
  6. Confirm that the printer is accessible when using the main application and the scanner.

Install Barcode Fonts

Since all Cloud Local print jobs will be sent via the print server, the standard Deacom barcode fonts need to be installed on it. Make sure to install fonts for all users. This will require administrator access. If barcode output does not display, verify that fonts are installed for all users and that the fonts are not blocked (see https://learn.microsoft.com/en-us/windows/security/threat-protection/block-untrusted-fonts-in-enterprise).

Troubleshooting and monitoring active Cloud Local connections

Beginning in version 17.03, the system will add logging to the cloud local connection management in the Deacom Web Service. Every hour, each active cloud local connection's client IP, client port, and available printers will be written to the Windows Event Log under the source "Deacom Web Service"