eOrder - Installation and Configuration Guide Volume 1: Overview & Requirements


eOrder provides a simple and secure way for your customers to submit jobs to your organization. Its unified workflow for all job types including color, monochrome, large format and small format, makes eOrder an ideal solution for online job submission.

Tightly integrated with PlotWorks Pro, eOrder also provides production automation for AEC work. Jobs consisting of large format plans can be configured to automatically appear in a PlotWorks Job Queue, pre-processed and ready for operator review.

eOrder runs on a server in your facility and easily integrates with your website, regardless of where your website is hosted. It supports both HTTP and HTTPS (secure) submissions and is compatible with browsers including Chrome, Firefox, Internet Explorer, Opera and Safari. Its job ticket is simple to customize, complementing your job submission process.


As a primary channel between you and your customers, eOrder should be classified as a mission-critical application and safeguarded accordingly. This includes the assurance of high-availability and nightly backups of uploaded files.


To provide high-bandwidth, local access to the uploaded files, the server which hosts eOrder should be located in your facility, optimally with a 1000 Mbps network interface card. eOrder does not require a dedicated server.

The incremental CPU and memory load placed on the server is low. For a typical Windows 2003/2008/2012 Server, 4GB of memory and a dual-core CPU is sufficient.

eOrder may be configured to store the uploaded files on a local drive or on a network drive. We recommend at least 50GB of free space to store the uploaded files. The storage location should be monitored on a regular basis, and older files should be archived or deleted when no longer needed.

Operating System

Although eOrder will run under Windows XP and Windows 7, these operating systems impose a limit on the number of concurrent network connections. This limitation, under some conditions, may prohibit your customers from successfully completing an eOrder transaction. Consequently, we strongly recommend an operating system such as Windows 2003 Server, Windows 2008 Server, or Windows 2012 Server.

The installation of Microsoft Internet Information Services (IIS) is not required. eOrder provides its own HTTP server which listens (by default) on port 8080. An alternate port number may be used if necessary and can be configured accordingly.

Use the DOS netstat command to determine if port 8080 is already in use by another application: C:\>netstat –ano | find ":8080"

Installation Path

The installer will detect platform architecture, installing a 32-bit version of the application with 32-bit operating systems, or a 64-bit version of the application with 64-bit operating systems. In all cases, the installation path is: C:\Program Files\PLP\OpCenter\Server\ and can be configured upon installation if need-be.


A platform-compatible instance of the Java Runtime Environment (JRE), version 6 or later, is required on the server. With a 32-bit operating system, the 32-bit version of JRE must be installed. With a 64-bit operating system, the 64-bit version of JRE must be install.
The eOrder installer will install an appropriate version of JRE for you. If you have already installed a platform-compatible instance JRE 6 or later on the server, you may cancel the JRE installation when installing eOrder.

Adobe Flash Player

The order forms displayed to your customers are Adobe Flash objects. If you wish to test eOrder while logged onto your server you will need Adobe Flash Player. If Adobe Flash Player is not installed, the following message will appear in your web browser:

This content requires the latest Adobe Flash Player.

A link to download Adobe Flash Player is provided at the end of the message.

Virus Scanning

Virus scanning software should be installed on the server to scan, in real time, every file that is uploaded. The virus scanning software should be configured to automatically download and apply updates to ensure protection against the latest threats.


Similar to any other mission-critical application, the location of the uploaded files and the eOrder installation directory should be backed up on a daily basis. In the event of a server failure, a well-tested disaster recovery plan will minimize downtime and enable preservation of customer data.


eOrder sends a confirmation e-mail to you and your customer upon the completion of each transaction. The e-mail confirmations are sent via an existing Simple Mail Transfer Protocol (SMTP) server, typically the same SMTP server that you use for outbound e-mail.
To enable outbound messaging you will need to provide the following e-mail configuration settings:
  • Host – the IP address or fully qualified domain name of your SMTP server
  • Port – the port on which your STMP server listens for incoming connections, typically 25, 465 or 587
  • Username – used to authenticate with the SMTP server
  • Password – used to authenticate with the SMTP server
  • SSL – whether or not the Secure Sockets Layer (SSL) protocol should be used to establish an encrypted connection to the SMTP server
  • TLS - whether or not the Transport Layer Security (TLS) protocol should be used to establish an encrypted connection to the SMTP server
  • From – the address from which the messages will be sent, and to which any replies will be delivered
  • To - where the email will be sent to
  • Connection Name - required if using eOrder for multiple forms/locations
If you are unsure of these settings, check with your IT resource, your ISP, or examine the settings in your e-mail client (examples: Outlook, Thunderbird).

Some SMTP servers are configured to block outbound mail if the "from" address is different than the account used to authenticate with the server. For example, if you were to authenticate as "john.doe@example.com," you may not be able to send a message where "orders@example.com" is the "from" address. To avoid this possibility, please make sure that the "from" address is associated with the account used for authentication.

If you already have an open STMP relay in your environment, you may wish to point eOrder at the open relay, and let the relay send the message to your SMTP server. If you are using an open relay, you will not need to specify a username or password. However, as mentioned above, the "from" address may need to be the same address used by the open relay to authenticate with the SMTP server.

Network Configuration

The diagram and example below are intended to provide a high-level understanding of a simple network configuration for eOrder.
  1. The server which hosts eOrder must have a static (internal/private) IP address, and must not block TCP traffic on port 8080.
  2. Your router or firewall must be configured to allow incoming TCP traffic (HTTP protocol) on port 8080 to be routed to port 8080 on the server.
  3. While not required, it is desirable to create a public DNS record which points to the external/public IP address of your router.

For example:
  • Internal/private IP address of the server hosting eOrder:
  • External/public IP address of the router:
  • Forwarding rule on router: TCP on port 8080 forwards to port 8080
Public DNS record: eorder.example.com resolves to

If you have any further questions/comments, please contact OpCenter's technical support team at the below contact information.

 |  | 
2300 Clarendon Boulevard

Suite 250, Box 29
Arlington, VA 22201-3367 USA

+1.703.740.8909 x3
+1.800.444.7568 x3

+1.703.740.8909 x2
+1.800.444.7568 x2


+1.703.995.4398 (fax)

Feedback and Knowledge Base