océ direct archive installation and configuration...manual sql server 2008 r2 express edition...

Océ Direct Archive Installation and configuration

Version 5.1 Confidential © 2020 Canon Solutions America

Océ System Administrator User Guide

Direct Archive - Installation and configuration manual

Table of Contents

Table of Contents .................................................................................................................................... 2

Guide Notes ............................................................................................................................................. 3

Preparing the Direct Suite Web Server ........................................................................ 4 Installing and Configuring Prerequisites – Credentials .................................................................... 4

Océ Direct View Service Account ....................................................................................... 4 Installing and Configuring Prerequisites – IIS .................................................................................. 6

Windows Server 2008 Preparation ..................................................................................... 6 Windows Server 2012 Preparation ..................................................................................... 9

SQL Server Express Edition Installation ................................................................... 13 Manual SQL Server 2008 R2 Express Edition Installation ............................................................ 13 SQL Server TCP/IP Protocol Configuration ................................................................................... 18 Network Configuration.................................................................................................................... 20

Software Installation ................................................................................................... 21 Prerequisites .................................................................................................................................. 21 Component and Module Details ..................................................................................................... 21 Server Installation .......................................................................................................................... 22 Océ Direct Archive – Client Installation .......................................................................................... 26

Full..................................................................................................................................... 26 Basic ................................................................................................................................. 27

Updating ......................................................................................................................................... 27

Shares and Permissions ............................................................................................. 28

3rd Party Software ........................................................................................................ 29

Troubleshooting .......................................................................................................... 29




Guide Notes The Installation Guide exists to assist in the installation process of the Direct Suite product. It details what is involved with configuring Windows Server and SQL Server in preparation, how to migrate exist customers and how to install the product on both server and client machines. The guide is structured in a linear format, so that following it step by step will lead from preparation to installation.




Preparing the Direct Suite Web Server

Installing and Configuring Prerequisites – Credentials

NOTE: If the customer will not use Océ Direct View, skip this section.

Océ Direct View Service Account

The Océ Direct View web application runs under the IIS web server. You will need to provide credentials for ASP.NET, so that the web application has appropriate rights to access various files necessary to function. If the customer already has a user with admin rights, then that user can be used. Alternatively, you can create new user credentials for the web application to use, as follows.

Creating an Océ User Account

The web server will use Windows user credentials for services and transactions such as preparing PDFs and accessing files on the vault server.

• Create a network UserID. This user ID will be used to access to the shares where the vault(s) and print inbox reside.

o Web Server on Domain: This account should be a Domain User with local Administrator rights on the web server.

o Web Server on Workgroup: This account should be created as a local user on Web and Vault (if separate) Servers. It should have administrator rights on the web server and user rights on the vault server.

• Use Computer Management’s “Users and Groups” to create a service account user.

• Name the user.

• Check only the Password Never Expires attribute.

• On the Web Server PC, open Properties for the new user, select the Member Of tab, and add to the local administrators group. Select the Users group and select Remove.




Installing and Configuring Prerequisites – IIS

Windows Server 2008 Preparation

IIS is not a standard component of Windows Server 2008. If it is not installed on the web server machine, it must be added with the Window Component Wizard.

NOTE: If the machine is running Windows Server 2012, go back to the appropriate section.

Pre-Installation Procedures for Windows Server 2008

• Clean System: Start with a clean Windows Server 2008 system.

• Start with normal security: If security settings have been modified, restore them to system defaults.

• Add Server to Domain or Workgroup: Configure your web server on or off the domain. If the server is added to a domain or moved to a new workgroup after IIS is installed, web applications may perform erratically until IIS is uninstalled and reinstalled.

• Drive Choice: Choose a drive with at least 4 GB for the Inetpub directory (more for heavy viewing). See the “PDF space requirements” section for more information.

Verify IIS installation by opening the Server Manager. If not already selected, in the left pane, click on “Server Manager ([Server Name])”. In the right pane, scroll down to the “Roles Summary” sub section. If IIS is installed, it will be listed under “Roles”. If IIS is not installed, perform the following steps. If IIS is installed proceed to the next step. In the same sub section, click on “Add Roles” to start the wizard.




Select Next view the role selection page, and add “Web Server (IIS)”.

Select Next to display the IIS feature form.

Make sure to include the following features: ASP.NET, Windows Authentication




Select Next and review the chosen features. Select Next again to begin the installation.

After the installation is complete, the server will be ready to host web applications.




Windows Server 2012 Preparation

Microsoft’s web server (Internet Information Server) is not a standard component of Windows Server. If it is not installed on the web server machine, it must be added with the Window Component Wizard.

NOTE: If the machine is running Windows Server 2008, go back to the appropriate section.

Pre-Installation Procedures for Windows Server 2012 If IIS is not already installed, it will need to be added as a role.

a. From the server manager, add a new role




b. Choose the role-based installation and continue.

c. Make sure the print server is chosen.




d. On the server roles page, add the web server (IIS).

e. Include the management tools.




f. Skip the general features page and continue to the IIS role services page. Leave the default IIS features, but also make sure to add:

• Security > Windows Authentication

• Application Development > .NET Extensibility 4.5, ISAPI Extensions, ISAPI Filters, ASP.NET 4.5

g. Continue to install the role.




SQL Server Express Edition Installation This section of the guide will explain how to install a new instance of SQL Server. If SQL Server is already installed, an existing instance can be used instead, in which case, skip to the next section. It is recommended to let setup.exe install SQL 2008 R2 in an automated way as it is preconfigured for use by the application. NOTE: Engineering Exec does not support SQL Server 2008 or later. If using Engineering Exec concurrently with Direct Suite, SQL Server 2005 is required.

Manual SQL Server 2008 R2 Express Edition Installation Insert the Direct Suite DVD into the server and browse to the SQL Server installation folder SQL2008R2_x86 or SQL2008R2_x64 for 64-bit. This can be done either manually or using the provided script. Using the script Run SQLsetup.cmd to start the installation. A command window will load and show progress. This will take a while and will install SQL and create an OCEPRINT SQL Instance. Manual installation Run setup.exe to begin the installation. The SQL Server Installation Center will open and you can follow the steps below.




Select “New installation or add features to an existing installation”:

SQL Server will perform some automatic checks to ensure that the server is ready to continue:




After accepting the user agreement, click next to reach the Feature Selection form. Choose all features and then click next:

SQL Server will briefly check more installation rules, and then display the Instance Configuration form. The instance can be named anything. Optionally, change the root directory of the instance.




In Server Configuration, make sure the startup type of the SQL Server Browser is set to automatic (the Database Engine should also be automatic):

In the Database Engine Configuration form, change the “Authentication Mode” to “Mixed Mode”. Specify a password for the SQL Server authentication. NOTE: You made need this in the future. It should be saved to your notes and provided to the customer.




Continue and the installation will begin. This may take several minutes to complete.




SQL Server TCP/IP Protocol Configuration In order for the Direct Suite clients to communicate with the SQL Server instance, the TCP/IP Protocol needs to be enabled.

1. Launch SQL Server Configuration Manager from under Microsoft SQL Server 2008 R2 in the Start Menu.

2. In the left pane, open “SQL Server Network Configuration” and select the appropriate

Direct Suite SQL instance. In the right pane, right click on “TCP/IP” and choose “Enable”.




3. Right click again on “TCP/IP” and choose “Properties”. Click on the “IP Addresses” tab. Scroll down to the “IPAll” section. If there is a value in “TCP Dynamic Ports”, delete it. Then, if not already there, change the “TCP Port” value to 1433. Click “OK”

4. Notice the warning after making the changes. Restart the SQL Server service to fully

apply the changes.




Network Configuration

Some services and clients require TCP/IP and UDP communication with the server over specific ports. Verify that the following ports are open on server and client firewalls.

TCP 1433 SQL Server Database Connection UDP 1434 SQL Server Browser




Software Installation

Prerequisites • On the server:

o The server has been configured as a web server with IIS (if using Direct View). o SQL Server has been installed and configured.

• On both server and client: o Microsoft .NET 4.6

After necessary prerequisites have been installed and configured, the machine is ready for installation.

Component and Module Details • Print Client1,2 – The primary print client, used to submit print jobs to supported devices.

Also used to create/delete distribution lists for set-print environments.

• Print Server1 – This is the core component of the printing utility. This service detects submitted print jobs and delivers them to configured devices.

• Port Monitor3 – This allows print queues to be mirrored as shared Windows printers. Users can then print from any application to the Direct Suite environment using the typical File>Print command.

• Indexing Client1,4 – This will allow the client user to use the indexing tool.

• Server Configuration Tool1,4 – This will allow the client user to modify major server settings (e.g., archive settings, queue settings, user/recipient settings, licensing settings).

• Sample Files3,4 – This is a collection of sample image files.

• Create SQL Database3* – Creates the primary OcePrint database.

• Web server3 – Creates the web server used by the Direct View web application. Not needed if the customer will not use Direct View.

• Document Linking3 – Provides user-to-document level permissions. Used strictly with Direct View.

• Script Processor3 – Service that provides custom ticket and hot-folder support primarily for third party integration.

• New Archive3** – Generates archive tables that reside within the OcePrint database and the archive file structure.

• Direct Export3,4 – Can be used to export batches of documents from the archive.

• Direct Import3,4 – Can be used to import documents from an external data source.

1 Required by server 2 Required by client 3 Optional for server 4 Optional for client * Required if doing a fresh installation and an existing OcePrint database does not already exist. ** Required if doing a fresh installation and an existing archive (e.g. from Engineering Exec) does not already exist.




Server Installation

Begin the installation and click “Next”.

Agree to the terms and select “Next”.

Optionally, change the path of the installation:




Change features for the installation as desired. To review modules and components, including which are required or optional for a server installation, see the appropriate subsection.




Next, choose the SQL Server instance that the database will be installed to (choose the [server name]\[instance name]. Change authentication methods if your current login credentials do not have access rights to the instance.

The installation is now ready to begin. Click “Next” to begin installing.

The setup will install all selected components and services.

Select “Install” to complete the setup process.




NOTE: If the customer intends to use BOTH Direct Archive and Engineering Exec side-by-side, then the file “OceServer.ini” must be copied from the Engineering Exec program directory to \\[server name]\OceServer$

After the installation has completed, you will need to add licensing information. See the System Administrator Guide for information regarding how to add necessary licenses and product activation. This should be done before the software is installed on any client machines.




Direct Archive – Client Installation

Full If the client will only be using the printing application, skip to the basic client installation section.

Start the installation like for the server (do not install SQL is using setup.exe) until you reach the feature selection page.

Change features for the installation as desired. To review modules and components, including which are required or optional for a client installation, see the appropriate subsection.

Continue through until you finish the installation:




Basic If the client needs components other than the printing application (e.g., System Administrator, Direct Index, etc.), go to the previous full client installation section. To install a basic client, run the Oce Direct Archive Client.msi. This is a very basic installation without any feature options and will only install the Direct Archive client. After the installation is complete, launch the print manager client. The application will ask you to locate the Direct Archive configuration file, located on the print server. Browse to the print server’s OceServer$ share, and select “OceDirectDefault.xml”.

Updating Updating Direct Archive is a largely seamless process. In most cases, simply run the new installer and click through the prompts. All machines (server and clients) using Direct Archive software will need to be upgraded, but start with the server. In some cases, the installer might complain that it cannot update from the version on the machine. If this occurs, the protocol is to uninstall and reinstall. Note that all configuration files (database and otherwise) are left untouched by the uninstaller. When reinstalling, the installation process will detect the previous configuration and use it. You might still have to choose the appropriate features.




Shares and Permissions The installation will create various shared directories that are used by various components of the software. The shares and permissions are listed here and detailed here for reference.

1. OceServer$ – This hidden, shared directory’s permissions are assigned to the “Everyone” group and set to “Read” and “Modify” by default. This directory is used by Oce applications to ensure that the local machine’s settings file (DirectDefault.xml) matches what is set on the server. In addition, if a client machine has the System Administrator tool installed, the tool will be able to update the server’s settings file. Default path:

• XP – C:\Documents and Settings\All Users\Application Data\Oce Direct Print

• Vista/7/8 – C:\ProgramData\Oce Direct Print 2. ODPInbox – This directory is used by Oce applications to deposit print jobs. By default,

permissions are assigned to the “Everyone” group and set to “Read” and “Modify”. Client machines with Direct Archive should have “Read” and “Modify” permissions, in order to properly submit print jobs. Default path:

• XP – C:\Documents and Settings\All Users\Application Data\Oce Direct Print\ODPInbox

• Vista/7/8 – C:\ProgramData\Oce Direct Print\ODPInbox 3. OceInstall – By default, permissions are assigned to the “Everyone” group and set only to

“Read”. This path can be used for easily distributing installation files (content pulled from installation media). If being used for distributing installation files, permissions should be set so that client machines can read from the path in order to access the files. Default path:

• XP – C:\Program Files (x86)\Oce\Direct Suite\OceInstall

• Vista/7/8 – C:\Program Files (x86)\Oce\Direct Suite\OceInstall 4. OceVault$ – This hidden, shared directory’s permissions are assigned to the “Users”

group and set to “Read” and “List folder contents”. This is the archive share where archived documents are stored. The location of the share depends on whether or not it was a fresh installation. If not, the share is likely located where ever it was for the previous installation. Default path:

• XP – C:\Documents and Settings\All Users\Application Data\Oce Direct Vault

• Vista/7/8 – C:\ProgramData\Oce Direct Vault




3rd Party Software In order to process or convert unsupported files, an interpreter program that can handle these file types must be installed. Direct Archive supports the use of either CADzation’s AcroPlot Repro™ and AcroPlot Auto, Ghostscript (by Ghostscript) as well as AnyDWG. If client side manipulation of unsupported formats is desired, the relevant converter should be installed on each client machine. For servers, the interpreter software should be installed if processing is required. Processing is required if target printing devices do not support the file format. Refer to the “Batch Files” section of the System Administrator guide for any proper reconfiguration (e.g., if the install directory of either program is changed from the default during installation).

Troubleshooting See the “Troubleshooting” section of the System Administrator guide to resolve any issues.