uStore® Installation Guide - XMPie

uStore®

Installation GuideVersion 8.3

Notices© 2015 XMPie®, A Xerox Company. All rights reserved.

U.S. Patents 6948115, 7406194, 7548338, 7757169 and pending patents. JP Patent 4406364B and pending patents.

uStore® Version 8.3 Installation Guide, Document Revision: 1.7, July 2015.

For information, contact XMPie Inc. 485 Lexington Avenue 10th. Floor New York, NY 10017

More information can be found at www.xmpie.com

XMPie provides this publication "as is" without warranty of any kind, either express or implied. This publication may contain technical inaccuracies or typographical errors. While every precaution has been taken in the preparation of this document, the publisher and author assume no responsibility for errors or omissions. Nor is any liability assumed for damages resulting from the use of the information contained herein. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. XMPie may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time.

XMPie, the XMPIE logo, PersonalEffect, uChart, uCreate, uMerge, uDirect, uEdit, uImage, uPlan, uProduce, uStore, StoreFlow, TransMedia, Circle, ADOR, XLIM, RURL, eMedia Cloud, and the slogan "one to one in one" are trademarks or registered trademarks of XMPie, A Xerox Company, and may not be used without permission. No part of these materials may be used or reproduced in any form, or by any means, without the express written consent of XMPie. To request permission to use these materials, please contact [email protected].

XEROX® and XEROX FreeFlow®, FreeFlow Output Manager® and FreeFlow Process Manager® are trademarks of Xerox Corporation in the United States and/or other countries.

Adobe Acrobat, Adobe Dreamweaver, Adobe Illustrator, Adobe InDesign, Adobe Photoshop and Adobe After Effects are trademarks of Adobe Systems Incorporated.

SQL Server 2014, SQL Server 2012, SQL Server 2008, SQL Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2008, Windows XP, Windows Vista, Windows 7, Windows 8, Microsoft Office, Microsoft Excel and Microsoft Access are trademarks or registered trademarks of Microsoft Corporation.

Mac OS is a trademark of Apple Computer, Inc.

ComponentArt is a trademark of ComponentArt Inc.

Other trademarks and service marks are the property of their respective owners.

www.xmpie.com

mailto:[email protected]

Contents 1

Contents

Chapter 1: System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

uStore Standalone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1uStore Distributed Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1uStore Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

uStore server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4File Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Database Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Connection to uProduce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Recommended Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Cluster Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2: Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Pre-installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

System Requirements Xerox FreeFlow Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 3: Preparing the uStore Environment . . . . . . . . . . . . . . . . . 10Checking Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Server Name Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Checking the Name of the Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Disabling Error Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Enabling Remote Desktop Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing Windows Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Contents 2

Windows Server 2012. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Installing IIS and Storage Services on Windows Server 2012 . . . . . . . . . . . . . . . . . . . . . . . 14

Windows Server 2008 R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Installing Internet Information Services (IIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Installing File Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Installing Service Packs and Hot Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Installing the SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Installing Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 4: Installing uStore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Recommended Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

uStore Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 5: Cluster Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 6: Upgrading uStore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Upgrading to Version 8.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Upgrading from FreeFlow Connect to FreeFlow Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 7: Uninstalling uStore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Appendix A: Using Helicon ISAPI_Rewrite for Friendly URLs and Setting Up a Proxy Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Introduction to ISAPI_Rewrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Setting Up Secure Access through a Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Firewall Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Helicon ISAPI_Rewrite Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Contents 3

ISAPI_Rewrite License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53ISAPI_Rewrite Installation and Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Installing the ISAPI_Rewrite on a Proxy Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Updating the Proxy Server with Friendly URL Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter B: Configuring Windows NLB for Web Servers . . . . . . . . . . 60Overview – Network Load Balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Windows OS with one NIC – IIS load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Network Load Balancing Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Protocol Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Network Configuration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Configuring the NLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Manually Creating an NLB Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Using Network Load Balancing Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Configuration Required on Server 1/Node164

Administrating NLB Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Command Line Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Network Load Balance Manager Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

NLB Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

List of Figures 1

List of Figures

Figure 1: uStore Distributed Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Figure 2: uStore Cluster Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 3: Recommended uStore Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Figure 4: Recommended uStore Cluster Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Figure 5: Windows Server 2012: Server Manager>Local Server>Properties screen . . . . . . . . . . . 12

Figure 6: Error Reporting dialog box in Windows Server 2008 R2. . . . . . . . . . . . . . . . . . . . . . . . 13

Figure 7: Windows 2012 Server Manager Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 8: Selecting a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 9: Selecting File and Storage Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 10: Selecting Web Server IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 11: Web Server (IIS) Add Features dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 12: Selecting Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 13: Selecting HTTP Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 14: Windows Process Activation Service Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 15: Selecting Management Tools options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 16: Installation progress screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 17: Add Roles Wizard: Select Web Server (IIS) Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 18: Add Roles Wizard: Add Role Services Required for ASP.NET . . . . . . . . . . . . . . . . . . . . 23

Figure 19: Add Roles Wizard: Select Web Server (IIS) Services . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 20: Add Roles Wizard: Select Web Server (IIS) Services (cont.). . . . . . . . . . . . . . . . . . . . . 25

Figure 21: Add Roles Wizard: Web Server (IIS) Installation Results . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 22: Add Roles Wizard: Select File Services Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figure 23: Add Roles Wizard: Select Role Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 24: Add Roles Wizard: Select File Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 25: The Proxy Configuration dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Figure 26: Microsoft Office Installation success message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

List of Figures 2

Figure 27: uStore Server Installer: Choose Destination Location . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 28: uStore Server Installer: Choose Destination Location-uStore and File System on different servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Figure 29: uStore Server Installer: Database Server Login screen . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 30: uStore Server Installer: Browse - Database Server dialog . . . . . . . . . . . . . . . . . . . . . . 38

Figure 31: uStore Server Installer: uStore Server Configuration screen. . . . . . . . . . . . . . . . . . . . . 39

Figure 32: uStore Server Installer: uProduce Customer screen . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 33: uStore Server Installer: Logon Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 34: uStore Server Installer: uStore File Server Access screen . . . . . . . . . . . . . . . . . . . . . . 42

Figure 35: uStore Server Installer: Ready to Install the Program screen . . . . . . . . . . . . . . . . . . . . 43

Figure 36: uStore Cluster Installation: Affinity Single . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Figure 37: uStore Cluster Installation: Affinity None . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Figure 38: Recommended uStore Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 39: uProduce for Administrators - Settings, RURL Proxy Utilities page . . . . . . . . . . . . . . . . 55

Figure 40: uProduce Proxy MSI Installer Security Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 41: uProduce Proxy Internet Explorer - Security dialog box. . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 42: uProduce Proxy - ISAPI Rewrite Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 43: uStore Settings page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 44: uStore Presets - Proxy Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 45: Proxy Setup - Download Script Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 46: uStore Proxy VB Script File Security Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 47: uStore Proxy Update Confirmation message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 48: NLB Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Figure 49: NLB Cluster Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 50: NLB Cluster Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Figure 51: Add/Edit Port Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 52: Cluster Properties-Port Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Figure 53: Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Figure 54: Host Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

List of Figures 3

Figure 55: Network Load Balancing Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Figure 56: Network Load Balancing Manager-Add a Host to the Cluster . . . . . . . . . . . . . . . . . . . . 71

Figure 57: Connect to a host machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figure 58: Host Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 59: Network Load Balancing Manager-Cluster is ready with two nodes. . . . . . . . . . . . . . . . 72

Figure 60: Network Load Balancing Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 1

System ConfigurationServer Configuration

uStore is available in three configurations:

• uStore Standalone configuration

• uStore Distributed configuration

• uStore Cluster configuration

To add a layer of security, a Proxy server is used in front of an uStore server. All connections coming from the web to the uStore server are routed through the Proxy server. This configuration provides added security by preventing direct communication between the uStore server and remote computers that reside beyond the Firewall.

uStore Standalone ConfigurationIn the uStore Standalone configuration there is one server which incorporates the following components:

• uStore

• uProduce

• Database

Installing uStore, uProduce and the Database on the same server might cause memory or I/O bottlenecks. This will affect the responsiveness of the online store hosted by uStore and the ability to generate proofs quickly. Therefore, this configuration is suitable only for low traffic volumes or for experimenting with uStore.

uStore Distributed ConfigurationA uStore Distributed configuration includes the following components:

• One uStore server

Chapter 1: System Configuration Server Configuration

2

• uProduce server/s

• Database server

• File Storage

In a typical Distributed installation, uStore and uProduce are installed on separate servers. The database is installed either on a third server (recommended) or on the uProduce server. The File Storage of uStore and uProduce may reside on each server respectively, or on a dedicated external file system (recommended). This configuration should take into account the expected traffic volumes to the online stores. The higher the expected traffic, the more uProduce servers should be considered for proof generation.

uStore Cluster ConfigurationuStore supports a Cluster configuration, which enables administrators to link several uStore servers into a cluster.

A web site hosted by a uStore Cluster will be able to withstand more load, as traffic is balanced among the servers in the cluster.

Figure 1: uStore Distributed Configuration

Chapter 1: System Configuration Server Configuration

3

This configuration also delivers fault tolerant capabilities, diverting the load from a failed server and balancing it across all the other uStore servers.

A uStore Cluster configuration includes the following components:

• uStore servers

• uProduce in a Fault-tolerant mode

• Redundant File Storage*

• Redundant Database Cluster*

• Load balancer (Microsoft NLB) – see Configuring Windows NLB for Web Servers on page 60

* File Storage and Database Cluster redundancy are the customer’s responsibility.

Figure 2: uStore Cluster Installation

Chapter 1: System Configuration Network Configuration

4

uStore serverIn a typical Cluster installation, there are several uStore severs that are connected to a fault-tolerant File Storage and a Database cluster. This distributed configuration ensures scalability and high availability.

Scalability is ensured since the number of uStore servers can be increased to ensure load balancing between all servers.

Fault tolerance is achieved by redirecting the traffic to another server when the server to which the user was connected during a login session is down.

File StorageThe File Storage stores all the common files uploaded by the customer from any one of the uStore servers. No matter to what uStore server the user is connected when browsing the store, the files on the File Storage are always accessible. The File Storage should be fault-tolerant.

Database ClusterThe Database is also common to all the uStore servers and it should also be fault tolerant.

Connection to uProduceTo achieve fault tolerance, uStore should be connected to a fault tolerant uProduce Cluster.

uStore should be configured to use the common uProduce cluster IP address.

Network ConfigurationIt is highly recommended that you work in a staging environment before going live.

Recommended Network ConfigurationThe recommended network configuration is represented in Figure 3:

Important Note: The basic StoreFlow package does not include a staging environment.


5

In this network configuration, uStore and uProduce are installed in the LAN and a Proxy Server resides in the DMZ.

Cluster Network ConfigurationThe following diagram displays a Recommended Cluster configuration in which the uProduce Cluster, the Database, the File Storage and uStore reside all in the LAN. The Proxy Server resides in the DMZ.

Figure 3: Recommended uStore Network Configuration


6

The Cluster configuration is a private case of a general network configuration, described in Recommended Network Configuration section, above. In this case, the security is also ensured by the separation between the DMZ and the LAN networks via a dedicated Firewall.

Figure 4: Recommended uStore Cluster Network Configuration

Chapter 2

Installation OverviewThis chapter explains how to install the uStore application.

Installing the uStore application includes two stages:

1. Preparing the uStore environment:

a. Ensure that the Windows Server’s Internet Information Service (IIS) component is installed and correctly configured. See Installing Windows Components on page 14.

b. Install SQL Server Express Edition. See Installing the SQL Server on page 30.

c. Install Microsoft Office. See Installing Microsoft Office on page 30.

2. Installing the uStore application. See Installing uStore on page 33.

Pre-installation ChecklistBefore you begin the installation, make sure that you have the following:

• The URL to download the uStore installer, Microsoft Office installer and required documentation.

• Helicon ISAPI_Rewrite Key (provided by XMPie)

• Supported operating system (see Software Requirements on page 9):

Windows Server 2012

Windows Server 2012 R2

Windows Server 2008 R2 with Service Pack 1

• Supported SQL Servers (see Software Requirements on page 9)

Note: uStore does not support installation on computer systems that utilize Federal Information Processing Standards (FIPS). For more information on Federal Information Processing standards and guidelines, refer to the National Institute of Technology and Standards (NITS) web site at: http://www.nist.gov/itl/fipsinfo.cfm

Chapter 2: Installation Overview Hardware Requirements

8

• A working local area network

• uStore administrative user name (for example, an existing Domain user or Local user, to be used by the uStore installer). This should be the same user name as the one that has been used for uProduce installation.

• uProduce version compatible with the current version of uStore (for uProduce version compatibility and optional patches, see the “uStore Compatibility with uProduce Version” section in the uStore Release Notes.

• Active uProduce system and user account

System Requirements Xerox FreeFlow CoreWhen integrating Xerox FreeFlow Core with uStore, you must install the following components:

1. Microsoft SQL Server 2012 Service Pack 2 or Microsoft SQL Server 2014 Service Pack 1.

2. Microsoft.NET Framework 4.5. For Windows Server 2008 R2, download the installer from http://www.microsoft.com/en-us/download/details.aspx?id=40779

3. For Windows Server 2012 and 2012 R2, add the .NET 4.5 component as described in Installing IIS and Storage Services on Windows Server 2012 on page 14.

Hardware RequirementsuStore can be installed on a separate server or on the uProduce Server. For more information on the various uProduce system configurations, refer to the uProduce Installation Guide.

The uStore Server has the following hardware requirements:

• Two physical Quad Core Intel® Xeon®

• 12 GB RAM or more (depends on your system configuration)

• Two hard disks in RAID1 (mirroring) configuration, 500 GB each, with two partitions:

Note: You are required to install uProduce on a dedicated server. No other software application should be installed on the uProduce Server. Applications that use IIS and or .NET framework are known to interfere with the proper operation of the uProduce server.

Chapter 2: Installation Overview Software Requirements

9

Partition C: operating system (~80GB)

Partition D: XMPie (~420GB)

• Gigabit Ethernet Adapter

Software Requirements• Operating Systems with all hot fixes and critical updates from Microsoft

should be installed:

Windows Server 2012 Standard Edition

Windows Server 2012 R2 Standard Edition

Windows Server 2008 R2 Standard Edition with Service Pack 1

• SQL Servers:

SQL Server 2014 Express Edition with Service Pack 1.

SQL Server 2012 Express Edition with Service Pack 2.

SQL Server 2008 R2 Express Edition with Service Pack 2. The installation instructions can be found at: http://www.xmpie.com/docreferences.

Performance ConsiderationsTo improve the uStore server performance, you are required to install it on a dedicated machine. No other software application should be installed on the uStore Server.Installing and running antivirus software on the uStore machine might affect the Server performance and may require specific tuning to minimize performance degradation.

For more information see TechNote-0031-Excluding Folders from Antivirus Scanning on PersonalEffect Servers.pdf.

Important: The Windows operating system must be genuine and activated before you install uStore.

Note: All machines on which PersonalEffect system is installed must run on the same operating system. A blend of different operating systems is not supported.

Important: Xerox FreeFlow Core 4.0 supports Microsoft SQL Server 2012 SP2 or Microsoft SQL Server 2014 SP1. It is advised to use one Microsoft SQL Server instance for both uStore and Xerox FreeFlow Core. For more information, see Xerox FreeFlow Core Installation Guide (http://www.support.xerox.com/support/core/documentation/enus.html?operatingSystem=win81x64&fileLanguage=en).

http://www.xmpie.com/docreferences

http://www.support.xerox.com/support/core/documentation/enus.html?operatingSystem=win81x64&fileLanguage=en)



Chapter 3

Preparing the uStore EnvironmentThis chapter explains how to configure the IIS and ASP.NET components of the Windows operating system and how to install the required Adobe software. In addition, this section guides you through verifying additional server settings and prerequisites that are essential for the proper functioning of the uStore Server.

Before installing the uProduce software, verify the following:

• All computers on which you intend to install the uStore software is NOT a Domain Controller.

Before you begin the uStore installation, you are required to install the following components and applications:

Internet Information Service (IIS), see Installing Windows Components on page 14.

SQL Server, see Installing the SQL Server on page 30.

Microsoft Office installer, see Installing Microsoft Office on page 30.

Checking Server Settings This section offers important details regarding uStore Server name limitations. You are required to verify these settings to ensure proper functionality of the uStore Server.

Server Name LimitationsThe computer on which you install uStore must have a host name that includes only alphanumeric characters, dots ("."), or dashes ("-"). In addition, it must not exceed 15 characters.

Note: Do NOT install uStore on a computer whose name contains any characters other than dot ("."), dash ("-"), or English letters and numbers.

Chapter 3: Preparing the uStore Environment Preparing the uStore Environment

11

Checking the Name of the ComputerTo check the name of the computer that you are using:

1. Go to Control Panel>System. The Control Panel System window is displayed.

2. Under View basic information about your computer>Computer name, domain and workgroup settings section, click Change… The User Account Control window is displayed.

3. Click Continue. The System Properties>Computer Name tab is displayed.

4. Check the Full computer name, to make sure it includes only alphanumeric characters, dots ("."), or dashes ("-"), and does not exceed 15 characters.

5. To edit the computer name (if necessary) click Change. The Computer Name/Domain Changes window opens.

6. Under Computer Name, type the new name.

7. Click OK to close the Computer Name/Domain Changes window. An information message window is displayed announcing that you have to restart your computer.

8. Click OK.

9. Click Close, to close the System Properties window. A message window is displayed asking you to restart your computer.

10. Click Restart Now to force the changes to take effect.

Disabling Error ReportingWindows Server environments include automatic error reporting settings that might disrupt the proper functioning of the uStore software, and therefore should be disabled.

To disable Error Reporting on your server:

1. Start Windows and open the Server Manager.

2. Do one of the following:


12

On Windows Server 2008 R2:

i. Expand the Resources and Support area, if it is not already open.

ii. Select Turn Windows Error Reporting. The Windows Error Reporting Configuration dialog box is displayed (Figure 6).

On Windows Server 2012:

i. Open the Local Server>Properties screen:

ii. Next to Windows Error Reporting, click On. The Windows Error Reporting Configuration dialog box is displayed.

3. Select the I don’t want to participate, and don’t ask me again option. This option disables Windows Error Reporting, and prevents it from prompting you to send information about application failures to Microsoft.

Figure 5: Windows Server 2012: Server Manager>Local Server>Properties screen


13

4. Click OK to save your changes.

5. Close the Server Manager.

Enabling Remote Desktop Connection Remote Desktop enables the remote management of the Windows Server machine on which the uStore Server is to be installed. This feature does not require a license, and allows a maximum of two remote connections.

To enable Remote Desktop Connection:

1. Go to the Control Panel>System. The Control Panel System window is displayed.

2. Under Tasks section, click Remote Settings.

3. Click Continue. The Remote tab in the System Properties dialog box is displayed.

Figure 6: Error Reporting dialog box in Windows Server 2008 R2


14

4. Do one of the following:

a. On Windows 2008: In the Remote Desktop section, select the Allow connections from computers running any version of Remote Desktop (less secure) option.

b. On Windows 2012: In the Remote Desktop section, select the Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended) option.

5. To save your settings and close the System Properties dialog box, click OK.

6. Close the Control Panel>System window.

Installing Windows Components The procedures to install Internet Information Services (IIS) and Storage/File Services are slightly different on Windows Server 2008 R2 and Windows Server 2012. The following sections describe the procedures on both operating systems.

Windows Server 2012On Windows Server 2012, you install the Internet Information Services (IIS), Microsoft Message Queuing (MSMQ) and Storage Services in a single procedure.

Installing IIS and Storage Services on Windows Server 2012

The IIS component should be installed on the uProduce Server and/or uProduce Director Server.

To install IIS and Storage Services on Windows Server 2012:

1. Open the Server Manager.

2. In the Manage menu, select Add Roles and Features.


15

3. In the Before You Begin screen, click Next.

4. On the Installation Type tab, select the Role-based or feature-based installation option and then click Next:.

5. On the Server Selection tab, select the required server and then click Next. Note that Local is selected by default. In the example below (Figure 8), the server Sandy1 is selected.

Figure 7: Windows 2012 Server Manager Dashboard


16

6. In the Select server roles screen, in the Roles list, select File And Storage Services>Storage Services.

Figure 8: Selecting a server

Note: This component may already be installed on the server.

Figure 9: Selecting File and Storage Services


17

7. Scroll down the list and select Web Server (IIS).

8. If a dialog box asking to add the Web Server (IIS) Management Tools feature is displayed, click Add Features.

9. Click Next.

10. In the Select features screen, in the Features list, select the following options: .Net Framework 3.5 Features

Figure 10: Selecting Web Server IIS

Note: The Windows Server Update Services should not be installed. Make sure that this checkbox is unchecked before clicking Next.

Figure 11: Web Server (IIS) Add Features dialog box


18

HTTP Activation .Net Framework 4.5 Features

Once you select the HTTP Activation, you are required to confirm the installation of Windows Process Activation Service:

Figure 12: Selecting Features

Figure 13: Selecting HTTP Activation


19

Click Add Features to proceed.

11. Click Next.

12. In the Web Server Role (IIS) screen, click Next.

13. In the Role Services list, make sure that the following options are selected:

a. Under Common HTTP features, select: Default Document Directory Browsing HTTP Errors Static Content

b. Under Health and Diagnostics, select: HTTP Logging Custom Logging Logging Tools

c. Under Performance, select: Static Content Compression

d. Under Security, select: Request Filtering Basic Authentication

Figure 14: Windows Process Activation Service Installation


20

IIS Client Certificate Mapping Authentication Windows Authentication

e. Under Application Development, select: .Net Extensibility 3.5

i. If a dialog box asking to add features that are required for .NET Extensibility 3.5 is displayed, click Add Features.

.Net Extensibility 4.5 ASP

ii. If a dialog box asking to add features that are required for ASP is displayed, click Add Features.

ASP.NET 3.5

iii. If a dialog box asking to add features that are required for ASP .NET 3.5 is displayed, click Add Features.

ASP.NET 4.5

f. Under Management Tools, select all available options including the sub-options under IIS 6 Management Compatibility.

14. Click Next.

15. In the Confirm installation selections screen, click Install. The installation progress screen is displayed. It includes a summary of the installation settings and a progress bar.

Figure 15: Selecting Management Tools options


21

16. When the installation process is completed, click Close to exit the Add Roles and Features Wizard.

Windows Server 2008 R2This section includes the following procedures:

• Installing Internet Information Services, see below.

• Installing File Services, see Installing File Services on page 26.

Installing Internet Information Services (IIS)To install IIS on Windows Server 2008 R2:

1. Open the Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

2. Point to and click Roles in the left pane.

3. Click Add Roles. The Add Roles Wizard appears.

4. Click Next. The Select Server Roles page appears.

5. Click the Web Server (IIS) checkbox and click Next.

Figure 16: Installation progress screen


22

6. Click Next until you reach Select Role Services page.

7. Scroll down the list, and make sure the following components are selected:

Under Common HTTP features select all components (Figure 19).

Under Application Development (Figure 19)

ASP.NET. A dialog box may be displayed asking you to add role services required for ASP.NET. Click Add Required Role Services (Figure 18):

Figure 17: Add Roles Wizard: Select Web Server (IIS) Role


23

.NET Extensibility (selected automatically, once ASP.NET service is selected)

ASP ISAPI Extensions (selected automatically, once ASP.NET service is

selected)

ISAPI Filters (selected automatically, once ASP.NET service is selected)

Under Security (Figure 20): Basic Authentication Windows Authentication Client Certificate Mapping Authentication IIS Client Certificate Mapping Authentication Request Filtering

Figure 18: Add Roles Wizard: Add Role Services Required for ASP.NET


24

Under Performance, select Static Content Compression (Figure 20).

Under Management Tools select all options (Figure 20).

Figure 19: Add Roles Wizard: Select Web Server (IIS) Services


25

8. Click Next until you reach the Confirmation page and then click Install. The installation summary and status is displayed in the Installation Results page of the Add Roles Wizard.

Figure 20: Add Roles Wizard: Select Web Server (IIS) Services (cont.)


26

Installing File Services

To install File Services on Windows Server 2008 R2:

1. Open the Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

2. Point to and click Roles in the left pane.

3. Click Add Roles. The Add Roles Wizard appears.

4. Click Next. The Select Server Roles page appears.

5. Select the File Services checkbox and click Next.

Figure 21: Add Roles Wizard: Web Server (IIS) Installation Results


27

6. Click Next until you reach Select Server Roles page.

7. Select the File Server component only.

Figure 22: Add Roles Wizard: Select File Services Role

Note: By default, the Indexing service is not installed on Windows Server 2008 R2. Make sure that the Indexing Service checkbox is not selected.


28

8. Click Next until you reach the Confirmation page and then click Install. The installation summary and status is displayed in the Installation Results page of the Add Roles Wizard.

Figure 23: Add Roles Wizard: Select Role Services


29

Installing Service Packs and Hot FixesBefore you continue with the remainder of the installation, you should ensure that you have the necessary Service Pack and hot fixes for the Windows Server operating system.

To install the Windows Server 2008 R2 Service Pack 1:

1. Go to http://www.xmpie.com/docreferences, to get Windows Server 2008 Service Pack 1.

To install the latest hot fixes:

1. Go to http://www.xmpie.com/docreferences and click Microsoft Windows Update.

2. Scan for critical updates.

3. Follow the instructions on how to install critical updates.

Figure 24: Add Roles Wizard: Select File Services





30

Installing the SQL Server uStore comes by default with SQL Server Express Edition with Advanced services.

Note that there is a 10 GB limit for the SQL Server Express Edition database.

From this point on, the instructions in this guide assume that you have completed the SQL Server installation.

Installing Microsoft OfficeuStore version .x and above requires that you install Microsoft Office on the uStore server. XMPie provides an installation utility for installing Microsoft Office with one license of Microsoft Office to be used in the production environment.

PrerequisitesTo install Microsoft Office on the uStore server you need:

Note: If the SQL Server is already in use by uProduce Server and you intend to use the same database server for uStore, there is no need to install the SQL Server again.

Important: The SQL installation for uStore has custom settings that need to be implemented. Refer to the installation documents for SQL Server Express Edition with Advanced Services at http://www.xmpie.com/docreferences.




31

• Connection to the internet

If your organization uses a proxy server, you need the proxy server’s address (URL). If authentication is required, you will also need a username and password.

• uProduce license key

To install Microsoft Office:

1. Download the XMPie Office 2007 Installer.zip file from the website provided by your XMPie representative.

2. After the XMPie Office 2007 Installer.zip downloads, unzip it.

3. Run the XMPie Office 2007 Installer.exe.

The XMPie – Microsoft Office Installer window is displayed.

4. In the XMPie – Microsoft Officer Installer dialog box, select the I accept the terms of the license agreement checkbox.

5. In the XMPie uProduce License Key box, enter your uProduce license key.

6. If your organization uses a proxy server, click the Use Proxy button and follow the instruction below, if not, skip to step 7.

In the Proxy Configuration dialog box, enter the Proxy Address.

If authentication is required, enter the proxy server’s Username and Password and then click OK.

7. Click Install.

The Microsoft Office installation starts.

8. When the Microsoft Office installation is complete, a message prompts. To close the message, click OK.

Figure 25: The Proxy Configuration dialog box


32

Microsoft Office 2007 is now installed on the uStore server.

Figure 26: Microsoft Office Installation success message

Chapter 4

Installing uStoreuStore 8.3 is compatible with uProduce version 7.0 or later.

Recommended Installation StepsIt is recommended you install the uStore environment in the following order:

1. .NET Framework 4.5 (required if you are using Xerox FreeFlow Core).

2. Microsoft SQL Server (SQL Server 2012 with Service Pack 2 or SQL Server 2014 with Service Pack 1 is mandatory if you are using Xerox FreeFlow Core 4.0).

3. uProduce 7.0 (for installation and upgrade of uProduce, see uProduce Installation Guide).

4. uStore 8.3 (see uStore Installation on page 34).

5. FreeFlow Core 4.0 (for installation instructions, see Xerox FreeFlow Core Installation Guide at: http://www.support.xerox.com/support/core/documentation/enus.html?operatingSystem=win81x64&fileLanguage=en

Prerequisites• Dynamic print jobs are processed on uProduce, therefore, uStore version

must be installed together with a compatible uProduce version.

• If you intend to install the uStore File System on a different location than uProduce and uStore:

Create a uStore-dedicated File System folder on the remote machine or storage and make it shared.

Warning: For uProduce version compatibility and optional patches, refer to the “uStore Compatibility with uProduce Version” section in the uStore Release Notes.

http://download.support.xerox.com/pub/docs/FF_CORE/userdocs/any-os/en_GB/FFCoreInstallCUST.pdf

Chapter 4: Installing uStore uStore Installation

34

Grant full access to the shared File System folder for a uStore user. This can be a domain or a workgroup user. The same user should be used in the uStore installer (Figure 33).

• Make sure that Microsoft Office is installed on the uStore server prior to installing the uStore software. See Installing Microsoft Office on page 30.

uStore InstallationTo install uStore:

1. Click the uStoreSetup.exe file to launch the uStore application installer.

The Welcome screen is displayed.

2. Click Next to begin the installation.

The License Agreement screen is displayed.

3. Read the license agreement carefully. Select I accept the terms of the license agreement to accept its terms and then click Next to continue the installation. If you select I do not accept the terms of the license agreement, you will not be able to continue the installation.

The Choose Destination Location screen is displayed:

Note: You can click Cancel at any time during the installation to exit the uStore installer.


35

4. Choose the installation path for the uStore application and the File System.

The default path for uStore application is the largest hard disk drive. For example, D:\XMPie\uStore. Click the Change… button if you want to modify the installation path.

If you want to install the uStore File System on a separate File Storage, select the Install uStore File System to separate location checkbox and set up the File System path by clicking the lower Change… button (Figure 28). If you are installing the File System on a remote File Storage, the path should be \\<FileSystemDomain>\<SharedFolder>.

If you want to install the uStore application and the File System in the same location, leave this checkbox unselected. In this case the installation path of the File System will be identical to that of the uStore application.

Figure 27: uStore Server Installer: Choose Destination Location

Warning: Do not install uStore on compressed hard drives. Doing so will cause uStore application to malfunction.


36

5. Click Next.

6. The Database Server Login screen is displayed:

Figure 28: uStore Server Installer: Choose Destination Location-uStore and File System on different servers

Note: It is highly recommended that you do not install uStore on the same drive as the operating system (default 'C' drive).


37

The Database Server Login screen enables you to connect to local or remote database servers.

If you want to connect to a local database (that is, the database is located on the uStore machine), leave the default database unchanged: <(local)\XMPIE>.

If you want to connect to a remote database server, click Browse to select a database server from your local network. When you click Browse, the installer searches your network for computers that have an SQL Server database installed.

The resulting list is displayed in the Browse - Database Server dialog.

Figure 29: uStore Server Installer: Database Server Login screen


38

7. Select the database, to which you want to connect, and click OK. The name of the database server is displayed in the Database Server field (Figure 29).

8. Add the instance name of the instance you created during the SQL server installation after the name of the database server you selected to connect to the uStore database. Concatenate it to the server name as follows: ServerName\InstanceName. The instance name is usually XMPIE. If you selected a local database, the \XMPIE addition is added automatically so you don't have to add it again.

9. Select whether to connect using the SQL Server Authentication (SQL Server authentication using Login ID and password) or using Windows authentication (for example, if you located the database on your local machine and you are an administrator of that machine).

10. If you selected SQL Server authentication using Login ID and password, enter the Login ID and the password as you selected when installing the SQL server (usually login: sa) to connect to the uStore database. Click Next to continue.

The uStore Server Configuration screen is displayed. In this screen, you enter the uProduce machine name and your admin credentials in order to connect to the uProduce server.

Figure 30: uStore Server Installer: Browse - Database Server dialog


39

11. Specify the user account for uProduce by entering the uProduce machine name or IP address (Host) and the user information in the appropriate fields (User and Password).

12. Select Test connection to uProduce when I click Next to test the connection to uProduce using the provided connection details.

The uStore installer verifies the connection to uProduce. When the test completes, the Logon Information screen is displayed (see Figure 33).

If the Test connection to uProduce when I click Next checkbox is not selected, the test is not performed and the uProduce Customer screen is displayed:

Figure 31: uStore Server Installer: uStore Server Configuration screen


40

13. In the Customer field, enter the uProduce customer name, as it was entered during the uProduce installation in the Company Name field of the Customer Information screen. Click Next.

The Logon Information screen is displayed:

Figure 32: uStore Server Installer: uProduce Customer screen


41

14. Set up the user credentials (User Name, Password and Domain) to enable the Windows user account used by uStore application and the Windows user account used by uProduce to access the File System. You can select the existing user by clicking Browse… next to the User Name field, or create a new local user by clicking the New User… button. This user is granted permissions to the File System. Note note that the same user has to be defined on all the uStore servers, on uProduce and on the File Storage.

15. Click Next.

The uStore File Server Access screen is displayed.

Figure 33: uStore Server Installer: Logon Information screen


42

If uStore File System is installed on a different server from uProduce and uStore:

Verify that you can access the File System shared directory from the uProduce server.

Verify that you can access the File System shared directory from the uStore server using the user you selected.

Verify that the Windows user account used for running the uProduce services is granted permissions to the File System shared directory.

16. Select Run uStore and uProduce shared folders accessibility test when I press Next to verify that uStore and uProduce can access the uStore File System as configured in the previous steps.

17. Click Next when you have finished setting up the uStore File System access. The Ready to Install the Program screen is displayed.

Figure 34: uStore Server Installer: uStore File Server Access screen


43

18. Click Install to begin the uStore installation. The uStore Server Setup begins copying files onto the host machine.

19. When the process is completed, click Finish.

Figure 35: uStore Server Installer: Ready to Install the Program screen

Chapter 5

Cluster InstallationThere are two types of uStore Cluster installations:

• Session Management by the uStore server.

This is the default uStore Cluster installation. In this scenario, all network traffic from a particular client is directed to the same cluster host. Thus, once the user session is opened on one uStore server, it will always remain assigned to it unless the server is down. This configuration is defined as ‘Affinity Single’ in Microsoft NLB (see Configuring the NLB on page 63). When the server is not available, the client will be redirected to another cluster node, where new session will be created. The client will experience a session timeout and will be logged out from the previous session.

Figure 36: uStore Cluster Installation: Affinity Single

Chapter 5: Cluster Installation

45

• Session stored on the SQL server.

In this installation, the user session details are stored on the SQL server, and, therefore, the user is seamlessly routed to the less occupied server on the Cluster in terms of network load (For more details concerning the configuration of “Affinity None” in Microsoft NLB, see Configuring the NLB on page 63).

Note: When the session is stored on the SQL Server, uProduce Cluster cannot reside on the same hosts where uStore servers are currently installed. uProduce Cluster supports only sessions managed by the NLB. In case where uStore Cluster requires the session to be stored on the SQL Server, uProduce Cluster must be separated from the uStore Cluster. See Figure 2 on page 3.

Figure 37: uStore Cluster Installation: Affinity None

Chapter 5: Cluster Installation

46

To install uStore Cluster configuration (session stored on the SQL Server):

1. Install uStore for the first time (see Installing uStore on page 33).

2. In uStore Back Office, go to Presets > System Setup >Global Configurations and change the value of the SessionStateMode attribute from InProc (session managed by uStore server) to SQLServer (session is stored on the SQL server).

3. In Microsoft NLB, in the Add/Edit Port Rule window, change Affinity from Single to None (see Figure 51 on page 67).

4. Uninstall uStore (see Uninstalling uStore on page 49).

5. Re-install uStore.

To restore the default session management mode (session stored on the uStore server):

1. In uStore Back Office, go to Presets > System Setup >Global Configurations and change the value of the SessionStateMode attribute from SQLServer (session managed by SQL server) to InProc (session is managed by uStore server).

2. In Microsoft NLB, in the Add/Edit Port Rule window, change Affinity from None to Single (see Figure 51 on page 67).

3. Uninstall uStore (see Uninstalling uStore on page 49).

4. Re-install uStore.

Chapter 6

Upgrading uStoreTo upgrade to version 8.x, follow the instructions below:

PrerequisitesBefore upgrading uStore to a new version, make sure that you do the following:

1. Back up the uStore database.

2. Back up your XMPie\uStore folder using Windows backup tool (or any other backup utility).

3. Make sure that Microsoft Office is installed on the uStore server. For information on Microsoft Office installation, see Installing Microsoft Office on page 30.

4. Review section Installing uStore, to make sure that you have all the information required for the installation process. Among other things, you will need user credentials for the uProduce, database and uStore servers.

Upgrading to Version 8.xTo upgrade from older versions of uStore to version 8.x you must install uStore 8.x (see Installing uStore on page 33)

Warning: It is highly recommended that you upgrade and test uStore in a staging environment before going live with the new version.

Chapter 6: Upgrading uStore Upgrading from FreeFlow Connect to FreeFlow Core

48

Upgrading from FreeFlow Connect to FreeFlow Core

Pre-requisites:

• .NET Framework 4.5

• SQL Server 2012/2014

To upgrade from FreeFlow Connect 2.0.2.x:

1. Double-click the FreeFlow Connect 2.0.2.3-Setup.exe file and follow the on-screen installation instructions.

2. Once the installation is complete, click Yes to reboot the system.

3. Install and license FreeFlow Core base software and any optional modules, as applicable. For installation instructions, see Xerox FreeFlow Core Installation Guide.

When installing FreeFlow Core, you will be prompted with “Do you want to remove user defined settings, logs, and persistence date? Click No to retain the FreeFlow Connect 2.0.2.x information.

Note: Do not apply Easy Starts to systems that are upgraded. Skip the optional Easy Starts procedure in Chapter 3 of Xerox FreeFlow Core Installation Guide. In FreeFlow Connect 2.0.2.x, all workflows include a hidden Join node. In FreeFlow Core 3.0, Join is available as a component selection. After the installation, for all workflows upgraded from FreeFlow Connect 2.0.2.x, you will see a Join node at the beginning of each workflow.

Chapter 7

Uninstalling uStoreTo uninstall uStore software:

1. Begin by logging into the uStore Server.

2. Go to Control Panel > Programs and Features.

3. Select XMPie uStore and click Uninstall.

The Uninstall utility prepares to remove the software.

4. Click Yes, when you’re prompted to confirm removal of the XMPie uStore Server.

The uninstall utility begins removing the uStore Server software.

5. Click OK to close the Uninstall window.

Warning: Restart the server to ensure your changes take effect.

Appendix A

Using Helicon ISAPI_Rewrite for Friendly URLs and Setting Up a Proxy Server Introduction to ISAPI_Rewrite

ISAPI_Rewrite is a URL rewriter for Microsoft IIS. A URL rewriter translates a complex URL into a more comfortable and shorter URL. Another usage of the rewriter is to implement a proxy server.

uStore enables you set up a unique branded stores for multiple internal or external customers and uses ISAPI_Rewrite for friendly URLs.

uStore also uses ISAPI_Rewrite in the context of proxy server implementation. A proxy server is used in front of web servers to add a layer of security. All connections coming from the web to a personalized web site that was created using uStore, are routed through the proxy server. This feature provides added security by preventing direct communication between the uStore Server and remote computers that reside beyond the firewall.

The following sections explain how to set up ISAPI_Rewrite for proxy server and friendly URLs solution.

Setting Up Secure Access through a Proxy Server

To install the ISAPI_Rewite, we can assume that uProduce server has been already installed (for more details on uProduce installation, see the uProduce Installation Guide).

Appendix A: Using Helicon ISAPI_Rewrite for Friendly URLs and Setting Up a Proxy Server

51

“RURL Proxy Utils” is a uProduce feature that enables you to install ISAPI_Rewrite on a proxy server that resides in the DMZ (Demilitarized Zone) part of the Firewall.


52

A typical network configuration with a Firewall can be represented as follows:

Figure 38: Recommended uStore Network Configuration


53

Setting up a proxy configuration involves two stages:

1. Firewall Setup on page 87

2. Helicon ISAPI_Rewrite Installation on page 87

Firewall SetupTo allow communication into the proxy server from the web, several rules should be defined in the Firewall.

Work with your network administrator to ensure that TCP Ports 80 and 443 are accessible for HTTP/HTTPS traffic coming:

• From the web to the proxy server

• From the proxy server to the uStore server

In some organizations, the above settings are implemented using two Firewall devices: one between the Web and the DMZ network - Front-End firewall, and another one between the DMZ network and the internal LAN – Back-End firewall. In this case, the Firewall rules must be set on both Firewalls. On the Front-End firewall, the Web client must be allowed to access into the proxy server using ports 80 and 443, and on the Back-End Firewall, the proxy server is allowed to access the uStore Server only via ports 80 and 443.

Helicon ISAPI_Rewrite InstallationThe following section explains how to install the ISAPI_Rewrite on a Proxy Server.

ISAPI_Rewrite License Keys License key intended for installation of a new Helicon product (ISAPI_Rewrite 3.0) should be provided with PersonalEffect XM.

ISAPI_Rewrite Installation and UpdateIn the following configuration, uStore and a Proxy Server are installed on two separate machines.


54

Before continuing with the explanation below, we can assume that uProduce and uStore Servers are already installed. The following procedures should be performed on the Proxy Server:

• Install ISAPI_Rewrite 3.0 full version via uProduce Admin Settings section (see Installing the ISAPI_Rewrite on a Proxy Server on page 54).

• Update the Proxy Server (see Updating the Proxy Server with Friendly URL Settings on page 57).

This section explains how to use the uProduce Server RURL Proxy Utilities to install and set up the Proxy Server.

Installing the ISAPI_Rewrite on a Proxy ServerTo install the ISAPI_Rewrite:

1. From your Proxy Server, open a browser and go to: http://<machinename>/xmpiedashboard. Replace <machinename> with the name or IP address of the server on which uProduce is installed.

2. Log in to uProduce with the following default credentials:

User name: admin

Password: admin

3. Click the Settings button.

The uProduce Settings page is displayed (Figure 39).

Important: The following procedure must be performed on the Proxy Server. You must be logged on to the Proxy server as “administrator” to perform the following steps. In an XMPie Enterprise platform, the ISAPI_Rewrite is installed and updated on each Proxy server.


55

4. Under RURL Proxy Utils, click Download RURL Proxy Utility Installer for Windows Server 32 bit or 64 bit link in step 1 according to your Web Server Windows operating system.

A File Download-Security Warning window is displayed, warning you that an isapi_rwf.msi file is about to run.

5. Click Open or Run (depends on your browser) to run the proxy installer package (Figure 40).

An Internet Explorer - Security Warning dialog box is displayed (Figure 41).

Figure 39: uProduce for Administrators - Settings, RURL Proxy Utilities page

Figure 40: uProduce Proxy MSI Installer Security Warning


56

6. Click Run.

The Welcome to the ISAPI_Rewrite Full Installation Wizard screen is displayed (Figure 42).

7. In the ISAPI_Rewrite Full Setup screen, click Next.

8. Follow the on-screen instructions; click Finish to exit the ISAPI Rewrite Full Setup installer.

Figure 41: uProduce Proxy Internet Explorer - Security dialog box

Figure 42: uProduce Proxy - ISAPI Rewrite Setup

Important: Make sure to install the ISAPI_Rewrite utility in the default path defined in the installer (usually, C:\Program Files\Helicon\ISAPI_Rewrite3\). Note that the partition (C:\) can be changed, while the rest of the path should be the default of the Helicon Installer.


57

9. After you finish your ISAPI_Rewrite installation, you must enter the license key provided by XMPie Support. To register ISAPI_Rewrite 3.x:

a. Go to Programs >Helicon>ISAPI_Rewrite3>ISAPI_Rewrite Manager. The Helicon Manager -IIS Web Sites dialog box is displayed.

b. Click Register. The Enable ISAPI_Rewrite dialog box is displayed.

c. In the Registration Name field enter “XMPie” and in the Registration Key field enter the registration key provided with the XMPie licenses.

d. Click Accept.

e. Close the Helicon Manager -IIS Web Sites dialog box.

Updating the Proxy Server with Friendly URL SettingsThe Proxy Server update is necessary when enabling or changing the store’s Friendly URL settings in an online store.

This section explains how to update the Proxy Server settings. For further information on store settings, refer to the section: Setting Up A Store in the uStore User Guide.

To update the Proxy Server:

1. uStoreuStoreFrom your Proxy Server, open a browser and go to http://machinename/uStoreAdmin with the Admin logon credentials. Replace machinename with the name or IP address of the server on which uStore is installed. In the Cluster installation you need to go to the NLB’s IP.

2. Log in to uStore.

3. Click the Presets button.

The uStore Settings page is displayed (Figure 43).

Note: The registration name must be XMPie. Otherwise, the Register button will not become active.

Important: The following procedure must be performed on the Proxy Server. You must be logged to your Proxy Server computer as “administrator” to perform the following steps.


58

4. Click Proxy Setup. The Proxy Setup page is displayed.

5. Click Download Script. A message is displayed, warning you that this action should take place ONLY on the proxy server. Click OK to proceed.

Figure 43: uStore Settings page

Figure 44: uStore Presets - Proxy Setup

Figure 45: Proxy Setup - Download Script Warning


59

6. Click OK to proceed. The File Download – Security Warning dialog box is displayed (Figure 46).

7. To run the script file, click Open or Run (depends on the browser you are using).

8. In the the XMPie Proxy message, Click OK (Figure 47).

A message is displayed informing you that the XMPie reverse proxy was updated successfully.

Figure 46: uStore Proxy VB Script File Security Warning

Figure 47: uStore Proxy Update Confirmation message

Appendix B

Configuring Windows NLB for Web ServersOverview – Network Load Balancing

The purpose of Network Load Balancing is to provide a performance-based distribution of IP connections to a group of servers running the same application. This does not imply that NLB is aware of the application that the client is connecting to. An additional application must be used to check on the application or service to ensure that the service or application is running.

In this section we are looking at the Windows Load Balancing Service in the Windows Server, which makes creating an NLB Cluster quick and easy.

For example: When a single Web Server machine is not enough to handle the traffic on your Web site it is time to look into building a Cluster that uses multiple machines on the network acting as a single server.

Figure 48: NLB Cluster

Chapter B: Configuring Windows NLB for Web Servers Windows OS with one NIC – IIS load Balancing

61

Windows OS with one NIC – IIS load Balancing

This section provides a step-by-step explanation on how to setup Network Load Balancing (NLB) using Windows Server Network Load Balancing components with one network interface card.

BackgroundYou can use NLB to “balance” request traffic (load) between two or more servers. This section explains how to implement it and assumes that you know what NLB is for. If not, see the links in the Prerequisites section on page 61.

Network Load Balancing ClustersNetwork Load Balancing (NLB) Clusters can include up to 32 servers. These servers communicate with heartbeats once per second. If five heartbeats are missed from a server, that server is considered to be a failed server. Five missing heartbeats trigger a process called convergence. During convergence the Cluster is dynamically reconfigured to exclude the server from which the five heartbeats were missed.

When heartbeats from a new or repaired server coming online are detected by an NLB Cluster, the Cluster enters convergence again and the new server becomes a member of the Cluster and begins accepting inbound connections on behalf of the Cluster. Convergence requires less than 10 seconds from detection of a required change to completion. During convergence, functioning hosts in a Cluster continue to process inbound requests without interruption in service.

PrerequisitesMake sure you read and understand the following Microsoft article: Overview of Network Load Balancing, at http://technet.microsoft.com/en-us/library/cc725691(WS.10).aspx.

RequirementsSoftware Requirements

NLB Clusters are supported on Windows Server Standard or Enterprise Edition. The service is built in to the operating system. No other software is required.

http://technet.microsoft.com/en-us/library/cc725691(WS.10).aspx

http://technet.microsoft.com/en-us/library/cc725691(WS.10).aspx


62

Protocol RequirementsApplications must be able to use TCP or UDP protocols. Load balancing is only done on TCP or UDP or both over IP. The IP addresses on which load balancing is done are all manually assigned. DHCP assigned addresses are not supported. The address records must be manually entered into DNS. There is no support for dynamic DNS registrations.

Hardware RequirementsOne network adapter is mandatory for XMPie defined configuration.

You can configure Network Load Balancing on more than one network adapter. However, this scenario is beyond our scope.

Note that heartbeat traffic and Cluster traffic is done on the same network adapter card. No separate network exists for heartbeat traffic as there is on a shared device Cluster.

Network Configuration RequirementsAll hosts in an NLB Cluster must be on the same broadcast subnet or on a VLAN. IP address to MAC address (the Cluster's MAC address in this case) resolution is done with the ARP protocol which is a broadcast protocol, therefore all hosts in an NLB Cluster must be on the same broadcast subnet to be able to respond.

AssumptionsBefore moving forward to the steps below, we can assume that a Windows Server Network Load Balancing component is already installed on both Servers.

Below is a brief outline of the lab scenario employed in this technote:

Note: In the Windows Server, the Network Load Balancing component is not installed by default. To install it, read instructions at: http://technet.microsoft.com/en-us/library/cc731695.aspx.

S e r v e r 1 : S e r v e r 2 :

OS: Windows Server OS: Windows Server

Hostname: Node1.xmpie.com Hostname: Node2.xmpie.com

No. of Network adapters: 1 No. of Network adapters: 1

http://technet.microsoft.com/en-us/library/cc731695.aspx

http://technet.microsoft.com/en-us/library/cc731695.aspx


63

Configuring the NLBNLB Clusters can be created with either of two methods, either manually or by using the Network Load Balancing Manager. In this section, we focus on the enhanced configuration of the NLB Manager. Manual configuration of an NLB Cluster is done on the properties of the network adapter card. If Network Load Balancing is not present on the properties of the network adapter card, then install the network load balancing service on the network adapter.

Manually Creating an NLB ClusterCreating an NLB Cluster can be done manually by configuring each server with the same Cluster name, Cluster IP address, a unique host ID, and the same type and number of port rules. These settings are found on the properties of the network adapter cards on each server. After the parameters are configured the host will begin sending our heartbeats once per second and either form a Cluster if it is the first server configured, or the host will join an existing Cluster with the same parameters.

Using Network Load Balancing ManagerThe second method of creating a network load balanced Cluster is to use the Network Load Balancing Manager. This tool is found in the Administration tools on the desktop of every Windows Server. The NLB Manager tool is a graphical tool that can be used to create Clusters and to manage existing Clusters. It is a wizard

Public Interface: NIC1 Public Interface: NIC1

IP on NIC1: 192.168.15.128 IP on NIC1: 192.168.15.130

Subnet Mask: 255.255.255.0 Subnet Mask: 255.255.255.0

Gateway: 192.168.15.1 Gateway: 192.168.15.1

DNS: 192.168.15.155 DNS: 192.168.15.155

NLB Virtual

Virtual Hostname: NLB.xmpie.com

Virtual IP: 192.168.15.39


64

driven tool which simplifies the creation of NLB Clusters. Using this tool, the parameters of the Cluster are selected and then pushed to the servers in the Cluster. So, each server is configured correctly.

Configuration Required on Server 1/Node1Step 1. Install IIS

For step-by-step instructions on how to install IIS, see Prerequisites on page 61.

Step 2. Create a new NLB Cluster

1. Open the Network Load Balancing Manager by going to Administrative Tools > Network Load Balancing. Or type nlbmgr.exe in the Run window.

2. Choose Cluster >New:

Enter the information as below:

a. Cluster IP configuration > IP Address: Enter the “Virtual” IP of your Cluster. This is the NLB IP on which clients will connect. It should not be already in use on your network and must belong to the same subnet as your web servers.

b. Cluster IP configuration > Subnet Mask: Enter the subnet mask for your virtual IP. It should be same as what you use on the network containing your web servers.

c. Cluster IP configuration > Full Internet name: Enter the full DNS “virtual” name of your NLB Cluster. Your clients will connect to this hostname. Note that NLB manager does not automatically register this name in DNS, you will have to do it manually.

d. Select Multicast. For more information on Unicast and Multicast, see the Microsoft article.


65

3. Click Next.

4. If you need to add any additional virtual IPs for your Cluster, enter them in the screen below, else click Next.

Figure 49: NLB Cluster Parameters


66

5. Configuring Port Rules: Here you can specify whether to load balance traffic only for specific ports or to load balance all traffic. In this scenario, for web servers you can choose to load balance port 80 (HTTP) and port 443 (HTTPS) traffic. To do so, press Next.

6. By default, the whole port range is available for NLB traffic. Remove the generic port rule by pressing the Remove button and click Add to define a new port rule. The Add/Edit Port Rule dialog box appears.

Figure 50: NLB Cluster Parameters


67

7. Under the Cluster IP address check All.

8. Under the Port range type the desired port you would like to load balance in the NLB Cluster. In the example above, we are using TCP port 80 (HTTP) and TCP port 443 (HTTPS) for SSL connections.

9. Under Protocols, choose TCP.

10. Under Filtering mode, choose Multiple host and Affinity Single when a session is stored in the memory of each uStore server or None when the session is stored in the database.

Multiple host – means that all of the hosts in the Cluster will respond to inbound requests as determined by the NLB. Affinity: Single - this selection is used when information is stored on a Cluster host for a client. Subsequent connections from the same client (based on the clients IP address) will always return to the same cluster host so that the information stored for the client will be available).

None (no client affinity) - this selection is used when a session is stored on the SQL server. In this scenario, each request from the same IP address may be served by a different cluster host.

Figure 51: Add/Edit Port Rule


68

11. To save the new defined rule and to close the Add/Edit Port Rule dialog box, click OK.

12. To add a new port rule for HTTPS (port 443) traffic, repeat steps 6-11 to add a new port rule for HTTPS (port 443) traffic.

13. Click Next. In the next screen you will be prompted to enter the hostname of the first node in the Cluster.

14. Enter the hostname or IP address of the machine you are working on and click Connect. The interfaces available on the computer are displayed.

15. Select the interface that you want to load balance; for example, the public interface of the host.

Warning: When the session is stored on the SQL Server, uProduce Cluster cannot reside on the same hosts where uStore servers are currently installed. uProduce Cluster supports only sessions managed by the NLB. In case where uStore Cluster requires the session to be stored on the SQL Server, uProduce Cluster must be separated from the uStore Cluster. See Figure 2 on page 3.

Figure 52: Cluster Properties-Port Rules


69

16. Click Next. In the next screen, you see the host parameters for this configuration.

17. Review the host parameters for this configuration and click Next.

Figure 53: Connect


70

18. You will see the progress of adding the host on the new Cluster in the Network Load Balancing Manager window. Wait until the status of the host is Converged.

Step 3. Add second host to the NLB Cluster

Figure 54: Host Parameters

Figure 55: Network Load Balancing Manager


71

1. In the Network Load Balancing Manager, right-click on the Cluster and select Add Host to Cluster.

2. Type the name or IP address of the second node and click Connect.

3. Select the public interface on the second node and choose Next:

4. Review the host parameters and click Next:

Figure 56: Network Load Balancing Manager-Add a Host to the Cluster

Figure 57: Connect to a host machine


72

5. The NLB Manager displays the progress as the second node is added to the Cluster. Wait until the Status is Converged for both nodes:

Figure 58: Host Parameters

Figure 59: Network Load Balancing Manager-Cluster is ready with two nodes

Chapter B: Configuring Windows NLB for Web Servers Administrating NLB Cluster

73

6. To test NLB, connect to the virtual IP from the browser of any client connected to the network. You should get the webpage even if one of the nodes is shut down:

Step 4. Register NLB virtual name in DNS

On your DNS server, make sure to register your virtual IP address of the Cluster. Example: Nlb.xmpie.com > 192.168.15.39.

Administrating NLB ClusterAdministration

Network Load Balance Cluster administration consists of starting, stopping, and checking the status of the NLB Cluster. You can manage an NLB Cluster in two ways: command line administration done with the Windows Load Balance Service (WLBS.exe) and the graphical tool called Network Load Balancing Manager.

Command Line AdministrationRemote WLBS commands can be only be used if remote administration is allowed on the Cluster tab of NLB properties on the host. Below are some examples of commands that can be issued from either the command line or in scripts. These commands can be issued locally on one of the hosts in the Cluster or remotely. The commands can be sent to a single host or to all of the hosts in a Cluster.

The examples below are commands issued from a local host.

• WLBS query – this command will return the list of all the active hosts in the Cluster.

• WLBS stop – this command will stop the WLBS service on the local host which will trigger convergence and the local host will exit the Cluster.

• WLBS start – this command will start the WLBS service on the local host. When the WLBS service starts the host will begin sending heartbeats which will be recognized by other hosts in the Cluster. The discovered heartbeats which will trigger the convergence process and the host will join the Cluster.

• WLBS drainstop – this command will cause the local host not to accept anymore inbound requests, but it will not terminate existing client connections. This command allows a graceful exit of a host. When client connections no longer exist, a WLBS stop command can be issued to the host.

Chapter B: Configuring Windows NLB for Web Servers Administrating NLB Cluster

74

• WLBS suspend – this command will cause the host not to respond to any WLBS commands other than WLBS resume. If for instance, 4 particular hosts were issued a suspend command, we could issue a WLBS stop command to the entire Cluster without effecting these particular hosts.

• WLBS resume – this command causes hosts that have been issued a WLBS suspend command to begin responding to WLBS commands again.

• WLBS drain 80 – this command will cause a drainstop only on the port rule that contains port 80. This could be a rule with the single port of 80, or it could be the rule which contains a range of ports that included port 80.

• WLBS disable 80 – this command will disable the port rule that contains port 80. This could be a rule with the single port of 80, or it could be the rule which contains a range of ports that included port 80. Either way that port rule will be disabled on this host.

• WLBS enable 80 – this command will enable the port rule that contains port 80. This could be a rule with the single port of 80, or it could be the rule which contains a range of ports that included port 80. Either way that port rule will be enabled on this host.

Many other commands are available for specific hosts by specifying the host IP address or the Host ID. These commands can also be issued to an entire Cluster by using the name of the Cluster (for example, WLBS stop cluster1).

Network Load Balance Manager AdministrationThe WLBS.exe commands can be issued as above from the command line, or they can be issued from the Network Load Balance Manager graphical tool. In this tool, you can select the name of the Cluster to issue commands to the entire NLB Cluster, you can select a host to issue commands to only that host, or you can select a port rule to issue a command to control that port rule. A screen shot of commands available to issue to a single host is shown below.

Chapter B: Configuring Windows NLB for Web Servers NLB Troubleshooting Tips

75

NLB Troubleshooting Tips• In some cases while adding the second node, the process may fail and you

will not see the status Converged, instead you will find a yellow exclamation mark next to the second node. In this case, right-click on the node and choose Delete. Then, login to the second node directly and use the NLB Manager on the second node itself. Choose Cluster>Connect to Existing and type the host name of the first node. Then continue the process, working from the second node itself.

• At times you might get an error NLB not bound and an error code. In such cases, check the following:

IP addresses and subnet masks on public interface of both nodes and virtual IP address of the NLB Cluster.

On the node that is failing, check if the public interface has more than one IP address.

Make sure that Network Load Balancing service is installed on the public interface and not on the private interface

.

Figure 60: Network Load Balancing Manager

Note: Network Load Balancing Manager does not work with imaged servers. If you are using any kind of imaging mechanism, read the following article: http://support.microsoft.com/kb/828258.

http://support.microsoft.com/kb/828258

http://support.microsoft.com/kb/828258

Index 1

Index

Aantivirus 9Authentication

SQL Server 38Windows 38

Cchecklist

pre-installation 7Cluster

uProduce 3

DDatabase server 37

Eenvironment 33error reporting

disabling 11EULA 34

HHardware Requirements

uStore Server 8hot fixes 29

IInstallation

uStore Admin 7installation

stages 7Installing

uStore Admin 7

LLogging in 64, 71Login

authentication 38

MMicrosoft Office 30, 31, 34, 47

Pperformance

considerations 9

Rremote management 13

Sserver name 10service packs 29software requirements

uProduce Director 9Solo

uProduce 1

UUpgrade

prerequisites 47uProduce 47

uProduceCluster 3Solo 1upgrade 47

uProduce Accountuser 39

Index 2

uStoredatabase server 37installing 34

uStore Serverhardware requirements 8

WWindows

service packs 29Windows Server 2012 7

XXerox FreeFlow Connect 9

uStore® Installation Guide - XMPie

Documents

Transcript of uStore® Installation Guide - XMPie