Sage SalesLogix 8.0 Customer Relationship Management (CRM) Solution Implementation Guide

PDF

Dokument

Reklaam

Sage SalesLogix

Implementation Guide

Version 8.0

Developed by Sage SalesLogix User Assistance

Sage SalesLogix

Implementation Guide

Documentation

Comments

Copyright

Address

Version

Trademarks

Disclaimer

Technical

Support

This documentation was developed by Sage SalesLogix User Assistance. For content revisions, questions, or comments, contact the Sage SalesLogix writers at [email protected].

This product and related documentation are protected by copyright and are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization of Sage and its licensors, if any.

Sage

8800 North Gainey Center Drive, Suite 200

Scottsdale, AZ 85258

USA

Version 8.0

(113012)

SalesLogix is a registered trademark of Sage Software, Inc.

Sage, the Sage logos, SalesLogix, and the Sage product and service names mentioned herein are registered trademarks or trademarks of Sage Software, Inc., or its affiliated entities. All other trademarks are the property of their respective owners.

Sage has thoroughly reviewed this manual. All statements, technical information, and recommendations in this manual and in any guides or related documents are believed reliable, but the accuracy and completeness thereof are not guaranteed or warranted, and they are not intended to be, nor should they be understood to be, representations or warranties concerning the products described. Sage assumes no responsibility or liability for errors or inaccuracies with respect to this publication or usage of information. Further, Sage reserves the right to make changes to the information described in this manual at any time without notice and without obligation to notify any person of such changes.

Technical Support is available to customers with support contracts directly from Sage Software, and to Certified Business Partners. Calls are answered during business hours, Monday through

Friday, excluding holidays. Current contact information is available on the Sage SalesLogix Web site: http://www.sagesaleslogix.com

Partners with a valid technical support contract and a Web access code can request technical support electronically on the Sage SalesLogix Partner Support Portal Web site: partners.sagenorthamerica.com.

Customers with a valid technical support contract and a Web access code can request technical support electronically on the Sage SalesLogix Customer Support Portal Web site: customers.sagenorthamerica.com.

Revisions to this book are available through both Portal Web sites. Check regularly for current Sage SalesLogix product documentation.

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chosing Components for Your Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

What You Need to Know. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Planning Your Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 1 Implementation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Required Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Web Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Mobile Client Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Customer Portal Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Synchronization Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Remote User Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Remote Office Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Intellisync for SalesLogix Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Optional Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Part I Administration Tools and Servers

Chapter 2 Preparing Your Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

User Rights and Network Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Understanding Commonly-Used Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Permissions Required for the SLXService User (without Administrator rights). . . . . . . . 14

The WebDLL User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Web Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

SData Portal Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Process Orchestration Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Windows Authentication Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Windows Authentication in the Sage SalesLogix Network Client . . . . . . . . . . . . . . . . . 20

Windows Authentication in the Sage SalesLogix Web Client . . . . . . . . . . . . . . . . . . . . 20

Sage Job Service Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Sage SalesLogix Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Web Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Remote Office Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

SpeedSearch Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Outlook Integration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Intellisync for SalesLogix Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Logging Access Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Understanding the Logging Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Creating the Logging Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Creating the Remote Office Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Sharing Folders and Granting Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Granting Full Access Rights to All Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Sharing Folders and Granting Rights to User Groups. . . . . . . . . . . . . . . . . . . . . . . . . . 27

Creating User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Sharing Folders by Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Running Sage SalesLogix as a Restricted User . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Running Sage SalesLogix on a 64-Bit System . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Chapter 3 Installing Sage SalesLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Selecting Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Understanding Sage SalesLogix Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Installing Sage SalesLogix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Running the Express Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Running the Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Creating Database Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Creating Client Database Connections for Oracle . . . . . . . . . . . . . . . . . . . . . . . . .36

Creating a Net Service Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Creating a Client Database Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Creating a 32-bit OLE DB UDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Chapter 4 Configuring the Sage SalesLogix System . . . . . . . . . . . . . . . . . . . . . . . . 39

Logging On to the Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Understanding the Setup Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Adding Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Entering Office Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Configuring Sage SalesLogix Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Setting Accounting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Setting Database Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Understanding E-Mail Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Activating Advanced Outlook Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Adding Address Lists to the Outlook Addressing Tab. . . . . . . . . . . . . . . . . . . . . . . . . 45

Adding Customer Service and Support Information . . . . . . . . . . . . . . . . . . . . . . .45

Understanding SpeedSearch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Maintaining Database Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Chapter 5 Installing the Web Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Installing the Web Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Building a Web Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Deploying a Sage SalesLogix Web Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Configuring the WebDLL User for Windows Authentication. . . . . . . . . . . . . . . . . . . . . . 53

Modifying the Log On User for Sage Job Service . . . . . . . . . . . . . . . . . . . . . . . . . .53

Configuring the SData Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Windows 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Configuring for Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Configuring IIS Settings for Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Enabling HTTP Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

IIS 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

IIS 7 with IIS 6 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Configuring ASP.NET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configuring Application Pool Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configuring Permissions for Desktop Integration . . . . . . . . . . . . . . . . . . . . . . . . 59

Defining the Default Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Installing Web Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Deploying the Web Reporting Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Mapping the Web Reporting Server to the Directory . . . . . . . . . . . . . . . . . . . . . . . . . .61

Chapter 6 Configuring Sage SalesLogix Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Planning for Sage SalesLogix Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Understanding the Admin User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Creating Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configuring Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Setting Access to Customer Service Management . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Part II Installing Sage SalesLogix Clients

Chapter 7 Installing Network Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Creating Automated Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Installing the Sage SalesLogix Network Client. . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Performing an Automated Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Performing a Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Starting the Sage SalesLogix Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Creating Area, Category, and Issue Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Creating the SyncSalesLogix Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Assigning the SyncSalesLogix Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Chapter 8 Configuring the Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuring Windows Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuring the WebDLL User for Windows Authentication . . . . . . . . . . . . . . . . . . . . . .76

Configuring the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Windows 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Configure the Web Client Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Configuring Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Testing the Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Linking from Your Company’s Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Configuring Client Computers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Enabling UTF-8 Support for Internet Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Installing Desktop Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Creating the SyncSalesLogix Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Assigning the SyncSalesLogix Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Chapter 9 Configuring the Sage SalesLogix Mobile Client . . . . . . . . . . . . . . . . . . . 85

Understanding the Mobile Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Deploying the SLX Mobile Portal and the SData Portal. . . . . . . . . . . . . . . . . . . . . 85

Defining the Default Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Testing the Mobile Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Sending the Mobile Portal URL to Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Chapter 10 Configuring Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Understanding Customer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Understanding Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Adding the Sage SalesLogix Customer Portal User . . . . . . . . . . . . . . . . . . . . . . . .88

Setting User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Deploying the Sage SalesLogix Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . .89

Configuring the Sage SalesLogix Customer Portal . . . . . . . . . . . . . . . . . . . . . . . .89

Configuring SpeedSearch Indexes for Customer Access . . . . . . . . . . . . . . . . . . . . . . . 89

Enabling the Contact Web Access Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Testing the Customer Portal Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Linking from Your Company’s Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Configuring Client Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Part III Remote Offices, Users, and the Offline Web

Chapter 11 Configuring Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Creating Synchronization Transfer Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Creating a Network Synchronization Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Creating an FTP Synchronization Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Setting Up a Sage SalesLogix FTP Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Creating an FTP Sync Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Creating an HTTP Synchronization Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Setting Up a Sage SalesLogix HTTP Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Creating an HTTP Sync Transfer Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Creating a Synchronization Service Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Starting the Synchronization Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Modifying Virus-Checking Software for the Synchronization Server. . . . . . . . . . . . . . . 101

Chapter 12 Configuring the Sage SalesLogix Remote Client . . . . . . . . . . . . . . . . . 103

Planning for Remote Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Configuring Remote User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Setting Synchronization Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Creating a Remote User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Installing the Sage SalesLogix Remote Client . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Performing an Automated Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Performing a Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Installing the Remote User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Creating the Database Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Starting the Sage SalesLogix Remote Client . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Creating a SpeedSearch Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Chapter 13 Configuring a Remote Office. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Configuring the Remote Office Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Adding Users to a Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Creating a Remote Office Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Installing the Web Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Installing a Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Installing the Remote Office Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Creating the Database Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Deploying Web Portals for the Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Deploying an Intellisync Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Starting the Remote Office Synchronization Client . . . . . . . . . . . . . . . . . . . . . . 116

Installing Remote Office Network Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Configuring Remote Office Web Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Configuring Intellisync for SalesLogix for Remote Office Clients. . . . . . . . . . . . 117

Chapter 14 Configuring Offline Web Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Configuring the Offline Web Client User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Deploying the Web Site to Offline Web Clients. . . . . . . . . . . . . . . . . . . . . . . . . . 119

Running a Synchronization Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Understanding the Offline Web Client Installation. . . . . . . . . . . . . . . . . . . . . . . 120

Installing Without Administrator Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Installing With Administrator Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Installing the Offline Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Installing the Remote User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Running a Synchronization Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Logging on to the Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Installing Desktop Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Part IV Appendices

AppendixA Creating a Database for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Creating an Oracle Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Creating a Net Service Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Configuring the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Creating Tablespaces and Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Creating the Database Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Importing the Database Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Indexing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Adding Database Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

AppendixB Configuring Intellisync for SalesLogix . . . . . . . . . . . . . . . . . . . . . . . . . 129

Setting the Provider Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Configuring Intellisync for SalesLogix on the Web. . . . . . . . . . . . . . . . . . . . . . . 130

Installing Intellisync for SalesLogix on Web Client Computers . . . . . . . . . . . . . . . . . . . 130

Deploying the Intellisync for SalesLogix Portal to the Remote Office and Offline Web Clients131

Configuring Intellisync for SalesLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Distributing Connection URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Configuring Synchronization Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Adding Outlook Contacts to Sage SalesLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

AppendixC Configuring Accounting Integration . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Accounting Integration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Configuring Accounting Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Running the Account Integration Phone and E-mail Update Utility . . . . . . . . . . . . . . . . 136

Configuring Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Comparing and Configuring Schema Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Configuring Matching Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Configuring the Accounting Integration Synchronization Service . . . . . . . . . . . . . . . . . 139

Exporting and Merging Records from your Accounting System . . . . . . . . . . . . . . . . . . 139

Configuring User Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

AppendixD Advanced Web Host Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Scaling the Web Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141

Monitoring Active Thread Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Configuring Web Hosts/Virtual Servers: Windows 2003 Server . . . . . . . . . . . . .142

Creating the Web Site(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Enabling the Active Server Pages Web Service Extension . . . . . . . . . . . . . . . . . . . . . 142

Configuring ASP.NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Configuring Application Pool Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Using Application Pools (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Configuring Web Hosts/Virtual Servers: Windows 2008 Server . . . . . . . . . . . . .143

Creating the Web Site(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Configuring Application Pool Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Using Application Pools (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Using Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

RPC Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Monitoring Web Host Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145

AppendixE Manually Configuring IIS for Web Host . . . . . . . . . . . . . . . . . . . . . . . . 147

AppendixF Advanced Web Reporting Configuration. . . . . . . . . . . . . . . . . . . . . . . . 149

Manually Configuring Web Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

AppendixG Automating Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Customizing the Sage SalesLogix Configuration File. . . . . . . . . . . . . . . . . . . . . .151

Understanding Features and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Example Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Customizing the Administrative Tools and Servers Configuration File . . . . . . . .154

AppendixH Silent Installs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Commands and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Setting Properties on the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

AppendixI Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Introduction

Sage SalesLogix is a leading customer relationship management solution that enables small to medium-sized businesses to acquire, retain, and develop profitable customer relationships through integrated Sales, Marketing, Customer Service, Accounting Integration, and Support automation solutions.

About This Guide

This is the Sage SalesLogix Implementation Guide. It provides step-by-step instructions for installing Sage SalesLogix version 8.0. This guide is written for system administrators,

Webmasters, and information system professionals.

Installing Sage SalesLogix 8.0 provides a full version of the product. No additional upgrading is required for this release.

• If you have never installed Sage SalesLogix, follow the steps in this guide.

• If you are upgrading from Sage SalesLogix version 7.5 or later, refer to the guide called

Upgrading Sage SalesLogix from Version 7.5. to 8.0.PDF.

If you are upgrading from a version of Sage SalesLogix prior to version 7.5, use the appropriate upgrade documents to first upgrade to version 7.5.0 before upgrading to version

8.0. These documents are available from the Support Portal Web sites:

• Sage SalesLogix Partner Support Portal Web site: partners.sagenorthamerica.com.

• Sage SalesLogix Customer Support Portal Web site: customers.sagenorthamerica.com.

Chosing Components for Your Implementation

Sage SalesLogix is a feature-rich product with multiple possible installation scenarios. You can choose your core installation option (Express or Standard), and then install the Sage

SalesLogix Clients and peripherals based on the needs of your organization. The following table provides an overview. See the Sage SalesLogix Planning Guide for more information about available Sage SalesLogix Components.

Component

Core components

Choose one of two installation options.

Available Options

• Express

• Standard

Clients

You can install any combination of Sage SalesLogix

Clients.

Remotes

• Windows (LAN)

• Web

• Mobile

Remotes are installations where users have a subset of the Sage SalesLogix database located locally.

• Offline Web Client

• Remote Office

• Remote Users

Sage SalesLogix Implementation Guide v8.0

Introduction

Component

Synchronization

Synchronization enables exchange of data between databases. It is only required if your implementation includes Remotes.

Intellisync

Only required if your implementation uses

Intellisync.

Required For

• Offline Web Client

• Remote Office

• Remote User

The Help symbol precedes online Help topic names, where you can find additional information about features or procedures not detailed in this guide.

What You Need to Know

The Sage SalesLogix Implementation Guide assumes you have a working knowledge of

Microsoft Windows operating systems, Microsoft Windows server technology and security,

Microsoft Internet Information Services (IIS) Manager, and Web technology. You should also understand the client/server computing environment, especially networking strategies for network and remote users.

You should be familiar with your database platform and its operation and administration.

Depending on the selected database platform, a Database Administrator (DBA) may be required for database tuning, maintenance, and customizations.

Planning Your Implementation

The most important element of a successful implementation is planning. The Sage SalesLogix

Planning Guide helps you plan your implementation process, from developing an implementation schedule to rolling out the system. The Sage SalesLogix Planning Guide helps you:

• Determine who will perform the implementation and select your implementation team.

• Understand the product components and their purpose.

• Determine a method for synchronizing data between the main office and remotes (if applicable).

• You can obtain a copy of the Sage SalesLogix Planning Guide from your Business Partner, from a Professional Services Group (PSG) representative, or from a Sage SalesLogix

Support Portal web site:

• Sage SalesLogix Partner Support Portal Web site: partners.sagenorthamerica.com.

• Sage SalesLogix Customer Support Portal Web site: customers.sagenorthamerica.com.

Chapter 1 Implementation Checklist

This chapter outlines the tasks you must complete to implement Sage SalesLogix. These tasks are designed to help you organize and make decisions regarding your Sage SalesLogix implementation. Any tasks that are recommended, but not required, are designated as

Optional.

If you are implementing Sage SalesLogix for the first time, read each chapter thoroughly to ensure you have correctly completed the necessary steps.

If you are upgrading from a previous version, do not use this document. Refer to the appropriate Upgrading document located in the Documentation folder.

Required Tasks

All implementations require the following tasks.

Task

1. Read the Sage SalesLogix Planning Guide and create an implementation plan.

Page

2. Set security and access for the WebDLL and

SLXService users.

3. Install and configure your system prerequisites.

Computer

Administrative Workstation

All computers and servers

Synchronization Server 4. Create and share the logging folders.

You do not need to create the folders in an

Express Installation.

5. For Oracle installations, create your Sage

SalesLogix database.

Note You must run the CreateOracleViews.sql script on your database before you can log into any Sage SalesLogix products.

125

Database Server

For Microsoft SQL Server, the database is created during the installation.

6. Install the Sage SalesLogix Server components.

7. Create Server database connections (if necessary).

8. For Oracle installations, create the Net Service

Name and Client database connection.

9. For 64-bit systems, create a 32-bit OLE DB

UDL.

10. Add the appropriate Sage SalesLogix licenses.

11. Enter your main office information.

12. Configure options.

13. Understand e-mail integration options.

All computers and servers

Sage SalesLogix Server

Administrative Workstation

Sage SalesLogix Implementation Guide v8.0

Implementation Checklist

Task

14. Add office information for customer service and support.

This task applies if your installation uses customer service or support features.

15. Add new users and configure user profiles.

Page Computer

Administrative Workstation

Administrative Workstation 16. Set user access to Customer Service

Management.

This task applies if your installation uses customer service or support features.

17. (Optional) Create automated installations for the Sage SalesLogix Network Client.

18. Install the Sage SalesLogix Network Client on all Sage SalesLogix user’s computers.

19. For Oracle installations, create a Net Service

Name and Client database connection.

20. Start the Sage SalesLogix Network Client.

Administrative Workstation

Sage SalesLogix Client computers

Sage SalesLogix Client computer

21. Create Area, Category, and Issue lists.

This task applies if your installation uses customer service or support features.

22. Create and assign the SyncSalesLogix group.

This task applies if your installation includes

Outlook Integration or Intellisync for

SalesLogix.

and

Sage SalesLogix Client and

Web Client computers

Web Tasks

In addition to the “Required Tasks” on page 5 , implementations that include Web components

require the following tasks.

Task

1. Install the Web Host.

Page Computer

Web Host server

2. Build the Web platform.

3. Deploy the Sage SalesLogix Web Client portal.

Administrative Workstation

4. Configure the SData portal.

5. Configure IIS performance settings.

6. Enable HTTP Compression.

7. Configure ASP.NET.

Web Host server

8. Configure Application Pool permissions.

9. Configure permissions for Desktop Integration.

10. Define the default document.

11. Install Web Reporting.

12. Deploy the Web Reporting portal.

Web Host server

IIS Server

Web Reporting server

Administrative Workstation

6 Sage SalesLogix Implementation Guide v8.0

Implementation Checklist

Task

13. Configure Windows Authentication.

14. Change the user assigned to the Sage Job

Service.

This task is required for the Sage SalesLogix

Web Client but may also apply to LAN Client installations that will include custom jobs for long-running or resource-intensive tasks.

15. Configure roles.

16. Test the Web site.

17. Create a link from your company’s Web site

(intranet).

18. Configure Web Client user computers.

19. (Optional) Configure Accounting Integration.

Page Computer

Administrative Workstation

Web Host server

135

Web Client computer

Web Host server

Company intranet server

Web Client computers

Administrative Workstation and Web Client computers

Mobile Client Tasks

In addition to the

“Web Tasks” on page 6

, implementations that include the Mobile Client require the following tasks.

Task

1. Deploy the Mobile Portal.

2. Define the default document.

3. Test the Web site.

4. Send the Mobile Portal URL to users.

Page Computer

Administrative Workstation

IIS Server

Web Host

Administrative Workstation

Customer Portal Tasks

In addition to the

“Web Tasks” on page 6

, implementations that include Customer Portal require the following tasks.

Task

1. Add the Customer Portal User.

2. Set user security.

3. Deploy the Customer Portal.

4. Configure the SpeedSearch Indexes access setting for Public Access (if necessary).

5. (Optional) Enable employees to grant access to

Customer Portal.

6. Test the Web site(s).

7. Create a link from your company’s Web site

(intranet).

8. Configure Customer Portal user computers.

Page Computer

Administrative Workstation

Web Host

Company internet or intranet server

Customer Portal computers

Sage SalesLogix Implementation Guide v8.0

Implementation Checklist

Synchronization Tasks

In addition to the “Required Tasks” on page 5 , the following tasks are required for all

implementations that include Remote users or Remote Offices. If your implementation does not include Remotes, the following do not apply.

Task

1. Configure synchronization transfer profiles for your selected method of synchronization.

2. Start the Synchronization Server.

Page Computer

Administrative Workstation

101

Synchronization Server

Remote User Tasks

In addition to the “Required Tasks” on page 5 the following tasks are required for all

implementations that include Remote users. Remote users can access their local database using the Sage SalesLogix Remote Client or Offline Web Client.

Task Page

1. Set synchronization options and assign a synchronization transfer profile to each Remote user.

103

2. Create Remote user databases.

105

Computer

Administrative Workstation

3. Deploy the Web site to all Offline Web Clients.

119

4. Install the Sage SalesLogix Remote Client and/or Offline Web Client.

107

and

121

Administrative Workstation

Remote user computers

Remote user computers 5. Install the Remote user database.

107

and

121

6. Run a synchronization cycle on all Offline Web

Client computers.

7. Start the Sage SalesLogix Remote Client and/or

Web Client.

107

and

122

8. Instruct Offline Web Client users to download the Desktop Integration Module.

122

Remote user computers

Remote Office Tasks

In addition to the “Required Tasks” on page 5 , implementations that include Remote Offices

require the following tasks.

Task

1. Configure the Remote Office profile.

2. Add Network users to the Remote Office.

3. Create the Remote Office database.

4. Install the Web Host at the Remote Office

Page Computer

111

Administrative Workstation

112

113

Administrative Workstation

Remote Office computer

8 Sage SalesLogix Implementation Guide v8.0

Implementation Checklist

Task

5. Install the Remote Office.

6. Install the Remote Office database.

7. Deploy Web Portals for the Remote Office.

8. Start the Remote Office Sync Client.

9. Install the Remote Office Network Clients and/or Web Clients.

Page Computer

113

Remote computer

114

Remote Office Database

Server

115

Administrative Workstation

116

Remote computer

117

Sage SalesLogix Client computers

Intellisync for SalesLogix Tasks

In addition to the

“Required Tasks” on page 5 , the following tasks are required for all

implementations that include Intellisync for SalesLogix.

Task

1. Create and assign the SyncSalesLogix group.

This task applies if your installation includes

Outlook Integration or Intellisync for

SalesLogix.

Page

and

2. Set the provider alias.

3. Deploy the Intellisync for SalesLogix portal to

Offline Web Clients.

129

131

4. Install Intellisync for SalesLogix for Web Client users.

130

131

5. Deploy the Intellisync for SalesLogix portal to the Remote Office(s)

6. Configure Intellisync for SalesLogix.

132

Computer

Sage SalesLogix Client and

Web Client computers

Administrative Workstation

Web Client computers

Administrative Workstation

7. Add Outlook Contacts to Sage SalesLogix.

133

Sage SalesLogix Client and

Web Client computers

Sage SalesLogix Client and

Web Client computers

Optional Tasks

After completing the previous tasks, you can begin using Sage SalesLogix. However, you may want to learn more about the following features to further customize your implementation.

Conflict Resolution You can define the criteria to use during synchronization to determine what changes are kept when more than one user has changed data. Conflict resolution is only necessary if your implementation includes Remotes. See the “Conflict Resolution” topic in the

Administrator Help for more information.

Multi-currency If your company has users in multiple countries using different currencies, you can enable multi-currency support. See the “Managing Currency” topic in the

Administrator Help for more information.

Monitor Console The Monitor Console receives and displays information from the

Synchronization (Sync) Service. This enables remote monitoring of the status of processes and jobs running on the Sync Server. See the Monitor Console Help for more information.

Sage SalesLogix Implementation Guide v8.0

Implementation Checklist

Sales Processes Sales Processes are groups of steps and procedures that help users manage their Sales pipeline. A sales process shows users the steps to complete while working to make the sale. Processes can also prompt the user to complete activities, such as making phone calls and writing letters. For information on creating and managing Sales

Processes, see the “Managing Sales Processes” topic in the Architect or Sage SalesLogix

Client Help.

Teams After adding and configuring users, you can create teams containing the users who require access to the same set of accounts. Teams customarily reflect the structure of your company, such as corporate regions, sales territories, or departments. See the “Working

With Teams” topic in the Administrator Help for more information.

10 Sage SalesLogix Implementation Guide v8.0

Part I

Administration Tools and Servers

Chapter 2 Preparing Your Environment

Before installing Sage SalesLogix, review and address the system prerequisites outlined in this chapter. This will minimize delays and enable your implementation to be successfull.

Before You Begin

Review the available documention:

• Sage SalesLogix Planning Guide. Read this manual to help plan your entire implementation.

• Compatibility Checklist. Use this document along with the requirements outlined in this chapter to ensure your hardware and software meet Sage SalesLogix supported versions.

General Requirements

The requirements listed here apply to all Sage SalesLogix installations.

User Rights and Network Permissions

• You must have Administrator rights for the computer on which you are installing Sage

SalesLogix components. See your Microsoft documentation for instructions on granting administrator rights using one of the following options:

• Add each user to the local machine’s Admin group for the duration of the implementation.

• Use a domain user account that is a member of the domain admin group for the duration of the implementation.

You do not need administrator rights to run the Sage SalesLogix Client, Sage SalesLogix

Web Client, Sync Client, or Mail Client.

The Offline Web Client installation does not require administrator rights if all prerequisites are installed prior to installing the Offline Web Client.

• TCP/IP must be installed and configured on every computer running Sage SalesLogix.

TCP/IP is required as the network communication protocol.

• No debuggers, programs, or screen savers running. Close all programs and turn off all debuggers, screen savers, or anti-virus programs that may interfere with the installation.

Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

Understanding Commonly-Used Users

The instructions in this document reference several default users and user types. This section explains these users and provides instructions for creating them where necessary.

•

Local System Account This default Microsoft Windows account includes the privileges necessary for Sage SalesLogix services. The Local System user has full rights on the local computer, but not domain access. This user must be mapped to a Sage SalesLogix user, usually the Admin user.

If you plan to run Agents, the Local System Account cannot be used to log on and cycle the Sync Server the first time. You must use a Domain account to log on and run a manual synchronization cycle for Agents to work correctly.

• SLXService User: Create this user if you have modified the default settings for the Local

System Account or prefer to specify a different user. See “Permissions Required for the

SLXService User (without Administrator rights)” on page 14

for more information. Although named “SLXService User” in this document, you may give this user any unique name.

• WebDLL User: Create this domain user if your installation includes Web components.

See “The WebDLL User” on page 15

for more information. This user is usually mapped to the Sage SalesLogix Admin user. Although named “WebDLL User” in this document, you may give this user any unique name.

• Admin User: This is a Sage SalesLogix user and has full permissions to the Sage

SalesLogix product and database. It must be mapped to a user such as the Local System

Account, SLXService User or WebDLL User.

• Named User (Network or Remote): This is a Sage SalesLogix user. Each license enables a single named user to access any number of copies of any Web, Remote,

Mobile, or Sage SalesLogix Network Client software. One license is assigned per user for each named user.

See the Sage SalesLogix Planning Guide for more information about the user types available in Sage SalesLogix.

Permissions Required for the SLXService User (without Administrator rights)

If you choose to create the SLXService User, you must assign the following required permissions. These permissions apply to Windows XP/2003/2008/2012. You must log on as a user with Administrative rights to configure permissions.

To create the SLXService user

1. Log on as a user with Administrative rights.

2. Set “Access this computer from the Network”, “Allow log on locally”, and “Log on as a service” rights on the Sage SalesLogix Server, SpeedSearch Server, and Sync Server computers.

3. Give the SLXService user Full control to the following registry keys:

• Sync Service

• HKLM\Software\SalesLogix

• SLXService User

• HKLM \SYSTEM\CurrentControlSet\Services\Eventlog

• HKLM\Software\Description\Microsoft\Rpc\UuidTemporaryData

4. Grant the SLXService user security rights to the following directory and file locations:

• DBEventing Service

• C:\Windows\Debug\ (Full control)

• Sync Service and Sync Servers

14 Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

• Logging path for each Sync Server (Full control)

• Library folder (Full control)

• Documents folder (Full control)

• Sync Service folder (Full control)

• Remote Office Sync Logs folder (Full control for Everyone accessing the Remote

Office)

• Remote Office Documents folder (Full control)

• Remote Office Library folder (Full control)

• If an alternate location is used for the log files created, then this path must also be enabled for modify (read/write) access.

• SpeedSearch Service

• C:\Program Files\SalesLogix\Speedsearch (Full Control)

• Intellisync for SalesLogix

• Program Files\SalesLogix\SlxIntellisync folder (Read/Write Access)

• Program Files\Common Files\Intellisync (Read/Write Access)

(If exists) The folder is created during the Sage SalesLogix Client installation.

• Microsoft SQL Express

• Program Files\Microsoft SQL Server\instance name\Data

The Windows user for the Sage SalesLogix Remote Client must be given this access. Access is only required for Remote users with a Microsoft SQL Express database.

The WebDLL User

If your installation includes Web components, Intellisync for SalesLogix, or the Sage

SalesLogix Job Server, you must create the WebDLL user. This user is a valid network logon name with security permissions that allow the Web Host, Web Reporting Server, Intellisync for SalesLogix, and the Sage Job Service to access all necessary directories.

The WebDLL user has certain minimum security settings required to run Intellisync for

SalesLogix and the Web components on Microsoft Windows. The exact settings depend on the requirements of your company. The minimum requirements are detailed in this section.

Individual Sage SalesLogix users do not require any Windows permissions to be set to use the

Web Client. All required access comes from the permissions granted to the WebDLL user.

Because the IIS default user, IUSR_<machinename>, is created locally, you should create a new user.

For information on creating users, modifying user groups, and assigning folder permissions, refer to the Microsoft Windows online Help.

Use the following settings to create the WebDLL user without Administrator rights on the Web

Host. You must log on as a user with Administrative rights to configure permissions.

To create

1. Create the WebDLL User in your company’s domain where all servers involved in the implementation are located.

Since you must be a domain administrator to do this, typically an IT department creates the user.

a. For the User name, type WebDLL.

Do not use spaces.

b. Set password options to:

• Password never expires.

Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

• User cannot change password.

• If selected by default, clear User must change password at next logon.

2. Add the WebDLL user to the following user group:

• For Microsoft Windows 2003: IIS_WPG

• For Microsoft Windows 2008: IIS_IUSRS

3. Set Full permissions to the following registry locations:

• Service User (WebDLL)

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog

4. Set Read Only access to the following registry location:

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificate\Disallowed

5. Set Read/Write access to the following locations:

• Needed for Sage SalesLogix:

• C:\Windows\Temp folder

• C:\Windows\SysWOW64\config\systemprofile\AppData\Local" (2008 R2) (64 bit)

• Needed for Web Reporting:

• C:\Documents and Settings\Default User\Local Settings\Application

Data\SalesLogix\SlxOLEDB\SalesLogix (XP/2003 only)

• HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects

• HKEY_CURRENT_USER\Software\Business Objects

• Create and grant C:\inetpub\wwwroot\slxwebrpt\Run

6. Grant access to the IIS metabase and other directories used by ASP.NET.

a. Open a CMD prompt and navigate to

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

b. Type: aspnet_regiis -ga domainname\username c. Press Enter.

The following messages will appear.

“Start granting slxapp access to the IIS metabase and other directories used by

ASP.NET.”

“Finished granting slxapp access to the IIS metabase and other directories used by ASP.NET.”

7. If it does not already exist, under the systemprofile, create the \My

Documents\SalesLogix\Reports\w3wp folder: a. Browse to SystemProfile and do one of the following:

• i.x86: C:\Windows\System32\config\systemprofile\

• ii.x64: C:\Windows\SysWOW64\config\systemprofile\ b. Modify the folder security for the \SalesLogix folder by giving WebDLL full control

(including sub-folders).

Software Requirements

• Latest supported Windows Service Pack. Install the latest supported service pack for your

Windows platform, available from Microsoft at www.microsoft.com.

• MDAC (Microsoft Windows versions earlier than Vista) or Windows DAC (Microsoft

Windows Vista or Windows 7). Microsoft Data Access Components are required on every computer running Sage SalesLogix.

If your Database Server contains only the Sage SalesLogix database and no other Sage

SalesLogix components, you do not need to install MDAC/Windows DAC on that server.

16 Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

• Microsoft SQL Express installed on the Administrative Workstation. Microsoft SQL Express is required if you have an Oracle database and there will be Remote users or Remote

Offices created, if your remote databases are a different Microsoft SQL Server version than the host, or if the Resync utility will be used.

If Microsoft SQL Express is installed with Sage SalesLogix, it installs as a SALESLOGIX instance with the sa password set to SLXMa$t3r. If you install Microsoft SQL Express from another source, you must set the sa password to SLXMa$t3r (it is generally blank). To install Microsoft SQL Express with the same configuration settings as Sage SalesLogix, create a setup.ini file in the SQLExpress install folder with the following information. When creating the file, copy the Redist\SQLExpress folder from the Sage SalesLogix media to your local machine (for example, C:\SQLExpress).

[OPTIONS]

ADDLOCAL=SQL_Engine

INSTANCENAME=SALESLOGIX (The INSTANCENAME can be any name you want. Sage

SalesLogix defaults the INSTANCENAME as SALESLOGIX.)

SAPWD=SLXMa$t3r

SECURITYMODE=SQL

Run the setup of SQL Express using a command line. At the command prompt, change the location of SQL Express using the following command: setup.exe /qb /settings

“location\of\setup.ini” (change "location\of\setup.ini" to the full path to the file, for example, c:\sqlexpress\setup.ini).

• Microsoft SQL Server 2005 Native Client. For Microsoft SQL Server 2005, the Microsoft

SQL Native Client must be installed on every computer that will connect to a Sage

SalesLogix database.

• Microsoft SQL Server 2008 R2 and 2012 Native Providers. For Microsoft SQL Server 2008

R2 and 2012 , the Microsoft SQL Server Native Providers must be installed on every computer that will connect to a Sage SalesLogix database.

• Microsoft Windows Installer. Windows Installer is required for use with .NET Framework.

The Sage SalesLogix installation automatically installs .NET Framework if it is not detected on the computer where you are installing Sage SalesLogix.

• Microsoft .NET Framework with ASP.NET enabled. .NET Framework with ASP.NET enabled is required for .NET Extensions on the Administrative Workstation, Web Host, and Sage

SalesLogix Client computers.

Ensure you install IIS before you install Microsoft.NET Framework; otherwise, ASP.NET is not installed.

• Microsoft Collaboration Data Objects. If you plan to run agents with e-mail output, you must install the Collaboration Data Objects (CDO.dll) on your Sync Server.

• For Outlook 2007, download Collaboration Data Objects version 1.2.1 from the

Microsoft Web site at www.microsoft.com.

• For Outlook 2010, most of the functionality has been incorporated into the Outlook

2010 object model.

• Microsoft Internet Explorer or Firefox. You must install a supported browser on every computer running Sage SalesLogix. Microsoft Internet Explorer 8 and 9 must be running in Native mode.

• Microsoft Word. You must install Word on the Administrative Workstation (or the computer on which you install Architect) for template management and on each Sage

SalesLogix Client and Web Client computer for mail merge.

• Crystal Reports Professional version XI Service Pack 4. If you plan to create or edit reports, you must install Crystal Reports on the Administrative Workstation (or the computer on which you install Architect) for report management.

The Crystal Reports installation is available with Sage SalesLogix, on a separate DVD.

• Adobe Acrobat Reader. Required to view Sage SalesLogix documentation.

Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

The following table shows the software prerequisites that will be installed if they are not detected during the Sage SalesLogix installation. Installing these prerequisites may require your computer to restart.

Prerequisites

Windows Installer 3.1

Windows Installer 4.5

Microsoft Exception

Message Box

Microsoft .NET

Framework 2.0

Microsoft .NET

Framework 4.0

Microsoft .NET

Framework Multi-

Targeting Pack

SQL Server 2005

Backward

Compatibility

Microsoft SQL Server

2008 R2 Express RTM

(Optional)

PowerShell 1.0 for

Windows Server 2003

(x86)

Microsoft Windows

Imaging Component

Microsoft Visual C++

2010 x86

Redistributable

Admin

Tools and

Servers

LAN

Client

X X

Remote

Office

Remote

Client

Offline

Web

Client

Web

Host

Web

Reporting

Server

• When the operating system is Windows 2003 Server 64-bit, SP2, .Net 2.0, and

3.5.1 must already be installed to enable Sage SalesLogix to install the .Net 4.0 and SQL 2005 Backwards Compatibility prerequisites. You can find these versions of .Net on the Sage SalesLogix DVD, in the Redist folder.

•

Microsoft .NET Framework v2.0 is installed in Classic mode.

Microsoft .NET Framework v4.0 is installed in Integrated mode.

Web Requirements

• Internet Information Services (IIS). The Web Host and Web Reporting Server require IIS.

When running a 64-bit server, IIS must be running in 32-bit mode.

• IIS 6 Compatibility. If you are running Sage SalesLogix on Windows 2008 Server, enable

IIS 6 Compatibility on the Web Host.

• To enable compatibility, open Server Manager, expand Roles, right click Web Server

(IIS) and select Add Role Services. In the Select Role Services list under

Management Tools, select IIS 6 Management Compatibility. The following sub-items

18 Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment are automatically selected: IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility,

IIS 6 Scripting Tools, and IIS 6 Management Console.

• Firewalls disabled on the Web Host (Windows 2008 Server). Firewalls can be active if a rule is added to allow inbound from ports 1433, 1025, and your SalesLogix Web site port.

• Windows Firewall port 11211. Open Windows Firewall and add an exclusion for port

11211. The SalesLogix Cache Server requires access to this port.

• .Net version 3.5.1 must be installed on the machine that hosts the Sage SalesLogix Web

Host when the Web Host uses the following operating systems:

• Microsoft Windows 2008 R2 32 and 64 bit: .NET version 3.5.1 must be installed in

Server Manager.

• Microsoft Windows 7: .NET version 3.5.1 must be installed in Programs and Features.

• Microsoft Windows 2003 32 and 64 bit: .NET version 3.5.1 must be installed in

Programs and Features.

• Crystal Reports Server. If you want your Web Client users to be able to access, run, and filter the same reports as Sage SalesLogix Network Client users, you must install Crystal

Reports Server on your Web Reporting Server. See the Compatibility Checklist for the appropriate Crystal Reports version.

• While the Web Host and Web Reporting components may reside on one machine, Sage SalesLogix recommends you install Web Reporting on a separate Web server to avoid performance issues.

• The Web Host installation automatically sets up IIS configuration. If you prefer to manually set up your web site instead of using the Web Host install, see the steps for configuring IIS before continuing with the installation.

SData Portal Requirements

Sage Data (SData) provides a standard protocol for reading data from and writing data to

Sage Business Applications, either on-premises (server or desktop based) or on the Web.

If your implementation includes Windows Authentication, Desktop Integration, Sage

Job Service, and/or Sage SalesLogix Mobile, but not the Sage SalesLogix Web components, you must still create the WebDLL user, install the Web Host, and

configure the SData portal. See page 54

for instructions.

The SData portal requires the following:

• On the Visual Studio development Web server, assign your domain user to a Sage

SalesLogix user, as the development server runs under the current logged in user.

• Internet Explorer version 7 or later. Earlier Internet Explorer versions do not have

ATOM/RSS support.

• The default authentication model for the SData Portal is Basic Authentication which:

• Does not require an association between the WebDLL user and a Sage SalesLogix user.

• Is used with Secure Sockets Layer (SSL).

• Is required for Sage SalesLogix Mobile and Offline Web Client, and Desktop

Integration functionality.

Process Orchestration Server Requirements

Process Orchestration allows you to create a process to be associated with any entity in Sage

SalesLogix. Any entity can be associated to multiple processes. Process Orchestration requires the Process Orchestration Host which executes/monitors the process instances in the

Web Client. The Process Orchestration Host is installed with the Web Host.

• Windows 2003 Server or later required for .NET Framework.

Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

• .NET Framework 3.0 or later. The Process Orchestration Server will not run using .NET

Framework versions earlier than 3.0.

• Disable IIS Integrated Windows Authentication for the ProcessHost Web site.

• A Sage SalesLogix user must be associated with the same Windows user that is assigned to the application pool for Process Orchestration. Typically, this is the Sage SalesLogix admin user.

For steps to associate a Sage SalesLogix user to a Windows user, see “Configuring the

WebDLL User for Windows Authentication” on page 76 .

If your implementation does not include the Web, you must still create the

WebDLL user, install the Web Host, and configure Application Pool permissions for the process orchestration portal (see

page 49 for instructions). Then refer to the

“Implementing Process Orchestration” topic in the Application Architect Help for additional implementation steps.

Windows Authentication Requirements

If you choose to implement Windows Authentication for Sage SalesLogix Client users in your installation, users who are already logged on to Microsoft Windows will be able to access the

Sage SalesLogix Clients without having to pass through a Sage SalesLogix Client log on screen. The Microsoft Windows user must be mapped to a Sage SalesLogix user for this to be successful.

Windows Authentication functions and is configured for the Network and Web Clients.

Windows Authentication in the Sage SalesLogix Network Client

In the Sage SalesLogix Network Client, when Windows Authentication is enabled

• If a Windows user is mapped to a valid Sage SalesLogix Client user, he or she does not see a Sage SalesLogix Client log on page. The Network Client application simply opens.

• If a Windows user is not found to be mapped to a Sage SalesLogix Network Client user, you can configure either of the following:

• Display a log on screen and require the user to log on manually

• Display an error screen.

In this case the user cannot log on to Sage SalesLogix

To configure Windows Authentication for the Web Client, you must:

• Ensure the Use Windows Authentication check box is selected on the User Profile General

tab for each Sage SalesLogix Client user. For more information see “Configuring Users” on page 64

Windows Authentication in the Sage SalesLogix Web Client

In the Sage SalesLogix Web Client, when Windows Authentication is enabled:

• If a Windows user is mapped to a valid Sage SalesLogix Client user, he or she does not see a Web Client log on page. The Web Client application simply opens.

• If a Windows user is not found to be mapped to a Sage SalesLogix Web Client user, the the user cannot access the Sage SalesLogix Web Client through this portal. An error message displays.

• To enable users to log on as the administrator, you must configure and deploy a second

Web Client portal that does not include Windows Authentication.

20 Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

Ensure the Use Windows Authentication check box is selected on the User Profile

General tab for each Sage SalesLogix Client user. For more information see

“Configuring Users” on page 64 .

Other options for Windows Authentication in the Sage SalesLogix Web Client can be configured by editing the Web.Config file and are:

• Windows Authentication off, SData on

• Windows Authentication off, SData off.

For information about these configuration options, see the Enabling Windows Authentication

Access for Web Client Users topic in the Administrator Help.

To configure Windows Authentication for the Web Client, you must:

• Configure the WebDLL user. See

“Configuring the WebDLL User for Windows Authentication” on page 53

• Deploy an SData portal. See

“Deploying a Sage SalesLogix Web Portal” on page 51 .

•

Configure your Web Server. See “Configuring the Web Server” on page 76

•

Configure your Web Client computers. See “Configuring the WebDLL User for Windows

Authentication” on page 76 .

• In the Adminstrator, open the User Profile General tab for each Web Client user and ensure the Use Windows Authentication check box is selected. See the topic called “User

Profile General Tab” in the Administrator help.

Sage Job Service Requirements

The Sage SalesLogix Job Service is a shared service that enables scheduling single and recurring tasks for immediate or delayed execution. This service executes tasks out of process, and so releases worker threads and memory for client sessions.

• Long running tasks offloaded to the Job Server can run asynchronously. When user sessions do not have to wait for long running processes to complete, fewer time-outs occur.

• Processing/memory intensive tasks offloaded to the Job Server eliminate competition for computing resources. The Job Server runs in a different process from the Web Host and consequently has a separate thread pool. It can be located on a separate server if necessary.

Although it is only required for a Sage SalesLogix Web Client installation (including the Offline

Web Client and Web Clients deployed at Remote offices), the Sage Job Server can be consumed by any Sage SalesLogix client when custom jobs are created to do so. Consider this service if your organization uses LAN or Mobile and typically has long-running tasks and/or resource intensive tasks. See An Introduction to Job Server in Sage SalesLogix.pdf for more information about creating custom jobs.

The Sage SalesLogix Job Service is installed with Admin Tools and Servers and requires the following:

•

Web Host and the SData portal must be installed, built, and deployed. See “Installing the

Web Host” on page 49 and

“Configuring the SData Portal” on page 54

for more information.

• After installation, you must ensure the default Sage SalesLogix user assigned for the Job

Server to log on as has access to SLX Application Entities and Activities. Use the WebDLL

user after associating it with the Sage SalesLogix Admin user. See “Modifying the Log On

User for Sage Job Service” on page 53

for more information.

Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

If you prefer, you can change the Sage Job Server Base Directory (the folder root for the file system deployment) from the default setting. You must do this after installation and then modify the Sage.Scheduling.Server.exe.config file. Refer to An Introduction to Job Server in

Sage SalesLogix.pdf for details.

Server Requirements

In addition to the “General Requirements” on page 13 , ensure the Server computer(s) meet

the following requirements.

• Microsoft SQL Server or Oracle. Your database platform must be installed and running on the Database Server.

When installing Oracle, ensure that the Oracle OLE DB Provider is installed.

By default, Sage SalesLogix uses the OLE DB Provider installed with MDAC v2.8. If your implementation uses the SQL 2005 Native OLE DB Provider, you must install that provider on any computer where Sage SalesLogix is installed.

• Sage SalesLogix Logging Folders. Create and share the logging folders as detailed in

“Logging Access Requirements” on page 24 .

• Trust relationship. Establish a trust relationship if the Database Server is on a different network domain from some or all of the Sage SalesLogix users and components. Ensure that these domains have a trust relationship with each other and can share data.

Microsoft SQL Server

• SQL Server Sort Orders set to 52 or 54. To check sort order information, type sp_helpsort in SQL Server Query Analyzer.

• Sort Order 52 - Dictionary order, case-insensitive, for use with the 1252 character set.

• Sort Order 54 - Dictionary order, case-insensitive, accent-insensitive, for use with the 1252 character set.

• SQL Server security set to SQL Server and Windows authentication. Verify this authentication is set on the Sage SalesLogix Database Server.

To change the authentication mode, open SQL Server Management Studio, right-click the appropriate server, and then click Properties. On the Security tab, set the Authentication to SQL Server and Windows.

• (Recommended for best performance) Microsoft SQL Server Client and Server component versions match. For example, if the Connection Manager uses the Microsoft SQL Server

2008 driver, then the Sage SalesLogix Clients should use the 2008 driver.

• SYSDBA user is not assigned the System Administrators role. If the System

Administrator’s role within Microsoft SQL Server is selected for the SYSDBA user, you cannot log on to Sage SalesLogix.

Oracle

• Sage SalesLogix Oracle database is placed in its own instance.

• Oracle Provider for OLE DB Components. When installing, ensure that the Oracle Provider version matches your Oracle Server and Oracle Client version.

• Oracle Server, Oracle Client, and Oracle OLE DB Provider component versions match. The major version for all three pieces must be the same or compatibility issues may arise.

22 Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

Sage SalesLogix Client Requirements

In addition to the

“General Requirements” on page 13 , ensure the following are set up on each

Client computer.

• Microsoft Outlook. You must install Outlook if you are using Outlook Integration or

Intellisync for SalesLogix. Ensure Outlook is installed and configured before installing

Sage SalesLogix.

See

“Outlook Integration Requirements” on page 24 for additional requirements.

• Small Fonts/Normal Size. Ensure the user’s Windows’ Display settings are set to Small

Fonts or Normal Size (the name of the option varies depending on which version of

Windows is installed).

Access this setting using the Windows Control Panel.

• 1024 x 768 or higher screen resolution. Sage SalesLogix screens are designed for higher resolutions. For optimum viewing, set the monitor resolution to 1024 x 768 or higher.

• Data Execution Prevention (DEP) for essential Windows programs and services only. If you are running Sage SalesLogix on Windows Vista, ensure this setting is disabled.

To access this setting, right-click My Computer > Properties > System Properties >

Advanced tab > Performance > Settings > Performance Options > Data Execution

Prevention tab > Turn on DEP for essential Windows programs and services only.

• (Windows Vista running Sage SalesLogix Mail Client and\or Attach Remote only) User

Account Control (UAC). Ensure the UAC setting is disabled on the Sage SalesLogix Client computer if the operating system is Windows Vista and the user will be running the Sage

SalesLogix Mail Client and\or Attach Remote.

To access this setting from the Windows Control Panel, double-click User Accounts and then click the Turn User Account Control on or off hyperlink.

• (Remote Clients Only) Microsoft SQL Express or Microsoft SQL Server. See the “Microsoft

SQL Express installed on the Administrative Workstation” bullet in the

“Software

Requirements” section for installation details.

• (Oracle implementations only) Oracle Provider for OLE DB Components. You must install the OLE DB components on every computer running Sage SalesLogix for database connectivity.

When installing Oracle, ensure that the Oracle OLE DB Provider is installed. In addition, your Oracle Server version must match your Oracle Client version.

Web Client Requirements

In addition to the

“General Requirements” on page 13 , ensure the following are set up on each

Web Client user’s computer.

• A supported browser. See the Compatibility Checklist for supported browsers.

• 1024 x 768 or higher screen resolution. Sage SalesLogix screens are designed for higher resolutions. For optimum viewing, set the monitor resolution to 1024 x 768 or higher.

• Microsoft Outlook. You must install Outlook if you are using Web Client Mail Merge and

Outlook Send SLX capabilities.

• UTF-8 support for Internet Protocols enabled (Microsoft Office 2007). UTF-8 support must be enabled when users are exporting extended characters to e-mail.

Enable UTF-8 support in Outlook from Tools > Options > Mail Format tab > International

Options > Internet Protocols section.

Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

Remote Office Requirements

In addition to the

“General Requirements” on page 13

, ensure the following requirement is met if your implementation includes a Remote Office.

• Microsoft SQL Server, Microsoft SQL Express, or Oracle. Your database platform must be installed and running on the Remote Office computer.

• IIS. A Web Server is required to host a Web Remote Office.

SpeedSearch Requirements

In addition to the

“General Requirements” on page 13

, ensure the following requirement is met if your implementation includes SpeedSearch running on Windows Vista Business Edition.

• Admin user configured to run the SpeedSearch Service. If the SpeedSearch Service is installed on a machine with Windows Vista Business Edition, the Local System

Account/SLX Service User does not have enough inherited permissions to run the service.

For increased security, set a domain user to run the SpeedSearch Service. The domain user should be the application pool user with access to the SpeedSearch

Server.

Outlook Integration Requirements

In addition to the “General Requirements” on page 13 , ensure the following requirements are

met if you are using Outlook Integration.

• Install and configure Outlook before installing Sage SalesLogix.

Intellisync for SalesLogix Requirements

In addition to the

“General Requirements” on page 13

, ensure the following requirement is met if you are using Intellisync for SalesLogix.

• Internet Information Services (IIS). Intellisync for SalesLogix requires IIS to host the

Intellisync for SalesLogix Web portal.

Logging Access Requirements

Various Sage SalesLogix services and applications need access to the local file system or logging folders to transfer information. The following information applies to both the main office (Host) and any Remote Offices.

• The process running the Sage SalesLogix OLE DB Provider must have Write permissions to the local file system, specifically the “All Users” folder. Write access is necessary for the Provider to write queue files.

• The SLXSystem.exe must have Read/Write permissions to the local file system to read and delete the queue files created by the Provider. This process assumes the rights of the parent process that creates it. Therefore all Sage SalesLogix services or processes that use the Provider or SLXSystem.exe must have local file system access (for example,

SpeedSearch Service).

24 Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

• The SLX Server Service user needs Read/Write permissions to the local file system to write the queue files it receives from the Client SLXSystem.exe. The SLX Server Service also runs the SLXLoggingServer.exe so the service must have Read/Write permissions to the location of the Workgroup Logs.

• The Sync Server, Synchronization Client, and SLXLoggingServer are the only applications that need access to the shared logging path. Network users do not need access to the shared logging path.

Understanding the Logging Folders

The following logging folders must be created and shared for a Sage SalesLogix implementation. In an Express installation, the logging folders are created by Sage

SalesLogix.

Sync Logs Folder The Sync Logs folder is the root folder for synchronization files. The first time the Sync Server runs, sub folders are automatically created under the Sync Logs folder for synchronization and other functions.

Documents Folder The Documents folder is the root folder for Sage SalesLogix documents and for files attached to accounts, contacts, and opportunities.

Library Folder The Library folder is the root folder for the Library system and contains the entire contents of the Library.

SyncService Folder The SyncService folder is used to store the Sync Service configuration file. This folder must be shared with the Administrative Workstation computer and with the computer on which the Synchronization Service is installed. If your implementation does not include Remote users or Remote Offices, you do not need this folder.

Remote Office Sync Logs Folder The Remote Office Sync Logs folder is necessary for implementations that contain a Remote Office. This is the root folder for Remote Office synchronization files. This folder must be shared to allow access by everyone (including the

SLXService user).

Remote Office Library Folder The Remote Office Library folder contains all Library documents that Remote Office Network users have access to.

Remote Office Documents Folder The Remote Office Documents folder contains all documents that Remote Office Network users have access to.

Creating the Logging Folders

If your implementation does not include synchronization, the logging folder (Sync Logs) is usually located on the Administrative Workstation (the computer where you install the

Administrator). In installations that use synchronization, the Sync Logs folder is best located on the Synchronization Server if it is a dedicated server. If you have a Document server, you can use it for the Library and Documents folders.

To create

1. In Windows Explorer, create the SyncService folder (for example,

\\ServerName\SyncService).

If your implementation does not include Remote users or offices, you do not need to create this folder.

2. In Windows Explorer, create the Sync Logs folder (for example, \\ServerName\Sync

Logs).

Ensure the Logging folder is shared and all Network and Remote users have network access to it. The path must also follow universal naming conventions (UNC), and you must be able to browse to it.

Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

If you are using synchronization, and more than one Sync Server is required, create separate folders for each sync server (for example, \\ServerName\Sync Logs1,

\\ServerName\Sync Logs2).

3. In Windows Explorer, create the following folders:

• Library (for example, \\ServerName\Library).

• Documents (for example, \\ServerName\Documents).

The next step...

• If your implementation includes a Remote Office, create the Remote Office folders detailed in the following section.

• If your implementation does not include a Remote Office, share the logging folders as described in

“Sharing Folders and Granting Access Rights” on page 26 .

Creating the Remote Office Folders

A Remote Office contains a central set of shared folders used for synchronization, library files, and documents. If your implementation includes a Remote Office, you must create the

Remote Office folders at the Remote Office site.

Typically, the synchronization folder (RemOffice Sync Logs) is located on the Remote Office

Synchronization Client. However, you can create the synchronization folder on a separate file server. The Library and Documents folders can be created on the Remote Office

Synchronization Client or a separate document server.

To create

1. In Windows Explorer, create the Remote Office Sync Logs folder (for example,

\\ServerName\RemOffice Sync Logs) to store the synchronization sub folders.

2. In Windows Explorer, create the following.

• Library (for example, \\ServerName\Library).

• Documents (for example, \\ServerName\Documents).

Sharing Folders and Granting Access Rights

The Sage SalesLogix folders must be shared before users can connect to them from the network.

When sharing folders, select one of the methods described in the following sections:

•

“Granting Full Access Rights to All Users”

•

“Sharing Folders and Granting Rights to User Groups”

Granting Full Access Rights to All Users

To share folders and assign access rights to everyone, you must:

• Enable file and print sharing.

• Assign the folders to be shared. This includes the SyncService, Documents, Library, Sync

Logs, and Remote Office Sync Logs folder.

This share includes the SLXService user. The SLXService user must have permissions set to Full Control for the Sage SalesLogix folders.

Refer to Microsoft documentation for instructions to share folders and enable file and print sharing.

26 Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

Sharing Folders and Granting Rights to User Groups

User groups allow you to manage permissions to the Sage SalesLogix folders by group, rather than by individual users. For example, you can create a group of Remote users and assign access rights to the entire group. When a new user is created, you add that user to the group, and the permissions are already defined. This saves time when administering a large number of users.

Creating User Groups

Should you decide to grant access rights by group, you must create global groups on the

Windows Server. A global group is available in its own domain, as well as any trusting domain you may have.

Refer to Microsoft documentation for instructions to create user groups. The following user groups are recommended.

User Group

SlxAdmin

SlxNetwork

SlxSync

SlxRemote

Represents

System Administrator and SLXService user

Sage SalesLogix Network users

Synchronization Server

Sage SalesLogix Remote users

If Remote users need direct access to the main office database, include those users in both the SlxNetwork and SlxRemote user groups. For example, this would be necessary if users work remotely and also dock their laptop when in the office.

Sharing Folders by Group

After creating user groups, you must set the folder sharing rights and permissions for each group. Refer to Microsoft documentation for instructions to set folder permissions. The following user group access is recommended.

User Group

SlxAdmin

SlxNetwork

SlxSync

SlxRemote

Type of Access

Full Control

Change

Running Sage SalesLogix as a Restricted User

To control security at a user level, you can create restricted users for Sage SalesLogix. Since

Admin rights to the local Windows computer are not required to run the Sage SalesLogix

Client, a restricted user with limited rights has full functionality.

Although Admin rights are not required to run Sage SalesLogix, users need permissions to access specific directories on the local computer. You can set permissions using one of the following methods:

• Add the user to the local machine’s Power User’s group. Although this allows more than the minimum required rights, it requires less administration.

• Set permissions to specific directories. This grants the minimum required permissions but requires more administration. Set permissions to the following:

• (Read/Write Access) Program Files\SalesLogix\SlxIntellisync folder.

Sage SalesLogix Implementation Guide v8.0

Preparing Your Environment

• (Read/Write Access) Program Files\Common Files\Intellisync - this folder is created during the Sage SalesLogix Client installation.

• (Read/Write Access) Program Files\Microsoft SQL Server\instance name\Data folder - this folder is only needed for Remote users running Sage SalesLogix on a Microsoft

SQL Express database.

• (Citrix users only) Copy the contents of the Business Objects folder to the

Windows\System32 folder.

Restricted users cannot register custom ActiveX objects contained in some Sage

SalesLogix Client views. A user with Admin rights must license and install the necessary components on each Sage SalesLogix Client computer.

Running Sage SalesLogix on a 64-Bit System

When installing Sage SalesLogix on 64-bit systems, be sure you have made the following adjustments to installation.

• The Web Host and Web Reporting Server require IIS. When these components are installed on a 64-bit server, IIS must be running in 32-bit mode. For the Web Host, this setting is applied as part of the installation.

• When creating an HTTP Synchronization profile on Microsoft Windows 2008, open IIS

Service Manager and enable 32-bit applications. See “Creating an HTTP Synchronization

Profile” on page 96 for more information.

• For Web installations running on 64-bit versions of Windows 2003, you must enable the

32-bit of ASP.NET 4.0. This setting is applied as part of the installation. If you manually

set up your web site instead of using the Web Host install, see Appendix E, “Manually

Configuring IIS for Web Host” on page 147 for more information on completing this task for

IIS 6 and IIS 7.

• If you are running Sage SalesLogix on a 64-bit system, you must run the Data

LinkManager in 32-bit mode. See “Creating a 32-bit OLE DB UDL” on page 35 .

• When setting permissions for the WebDll user, read the steps under

“The WebDLL User” on page 15 carefully to ensure you have enabled access to the locations required in a 64-

bit system

• Although Export to File is supported in a 64-bit environment, Export to Excel requires integration with 32-bit Microsoft Office.

• SendSLX and Mail Merge require integration with 32-bit Microsoft Office.

After completing this chapter...

You have completed tasks 1-4 of the “Required Tasks”

checklist. Proceed with Chapter 3,

“Installing Sage SalesLogix” .

28 Sage SalesLogix Implementation Guide v8.0

Chapter 3 Installing Sage SalesLogix

Before beginning this chapter...

Verify you have installed the prerequisites and created the logging folders as described in

Chapter 2, “Preparing Your Environment” .

If you are installing Sage SalesLogix on Oracle, ensure you have created the Sage SalesLogix

database as described in Appendix A, “Creating a Database for Oracle” .

Use the instructions in this chapter to...

Install the Sage SalesLogix administration tools and server components. These components are required for all Sage SalesLogix installations.

Selecting Your Installation

Sage SalesLogix provides two installation options:

• The Express Installation is intended for a Sage SalesLogix configuration of 5 to 25 users using the Microsoft SQL Server database platform. A supported version of Microsoft

SQL Server or SQL Express must already be installed.

The Express installation installs the following components on a single using system assigned default settings. It also creates and shares the default system folders.

• Sage SalesLogix Server

• Sage SalesLogix Blank and Evaluation Databases (Microsoft SQL Server)

• Administration Workstation components:

• Administrator

• Architect

• Application Architect

• Sage SalesLogix Utilities

• SpeedSearch Service

• Synchronization Server and Service

An Intellisync Web portal is required for all installations (Network and Web) using Intellisync for SalesLogix. The Intellisync Web Portal is not installed with the Express installation. If your implementation includes Intellisync for

SalesLogix, you must install using the Standard installation.

The SData portal is not installed with the Express Installation. The Job Service,

Windows Authentication, and Sage SalesLogix Mobile all require the SData portal. If your implementation will use any of these modules, you must install using the Standard installation.

• The Standard installation allows you to choose what components you want to install and the location where you want to install them.

The Standard Installation is intended for Sage SalesLogix implementations that have more than 25 users, run on an Oracle database, access Sage SalesLogix over the Web, use

Intellisync for SalesLogix, or include a Remote Office(s).

For more information on system components, see the Sage SalesLogix Planning Guide.

Sage SalesLogix Implementation Guide v8.0

Installing Sage SalesLogix

Understanding Sage SalesLogix Databases

Your Sage SalesLogix Implementation provides two databases: blank (for use as your production database), and evaluation (containing dummy data you can use for demonstrations and evaluations).

Do not use the evaluation database as your production database.

Microsoft SQL Server

Unless you have specified a different default data directory, the databases are installed to the same location as the Master.mdf (typically in the Microsoft SQL Server Data folder. The Data folder is a sub folder under your SQL instance name folder.) If the Sage SalesLogix installation does not find SQL Server, or a Sage SalesLogix database already exists, the databases are not installed.

SalesLogix.mdf This is your production database. The user name for this database is

admin; the password is password.

SalesLogix_Eval.mdf This database contains accounts, contacts, tickets, defects, and so on, for demonstration or testing purposes. You can log on as admin, Lee, Dan, or any other regular user in the database. No password is required.

Creating a database on SQL Server with a name beginning with a number is not supported as a regular identifier, and therefore, not recommended. If you create a

Host database using a name that begins with a number, you will receive errors when attempting to create a Remote user or Remote Office database.

The Sage SalesLogix Express installation installs both the blank and evaluation Microsoft SQL

Server databases and automatically creates two database connections named

SalesLogix_Server (to the blank database) and SalesLogix_Eval (to the evaluation database).

The Standard installation installs the Microsoft SQL Server databases if Microsoft SQL Server is detected on the computer on which you are installing the Sage SalesLogix Server.

Oracle

The SLX_Blank.dmp and SLX_Eval.dmp files are used to import data and the database structure to the Sage SalesLogix database.

SLX_Blank.dmp This DMP file provides data that serves as your production database. The user name for the Sage SalesLogix database created from the DMP file is admin; the password is password.

SLX_Eval.dmp This DMP file imports accounts, contacts, tickets, defects, etc., to your evaluation database for demonstration or testing purposes. You can log on to the Sage

SalesLogix database created from this DMP file as admin, Lee, Dan, or any other regular user in the database. No password is required.

If you have an Oracle database, you must create your database manually using the steps

outlined in Appendix A, “Creating a Database for Oracle” .

30 Sage SalesLogix Implementation Guide v8.0

Installing Sage SalesLogix

Install Sage SalesLogix directly from the Sage SalesLogix media or from a network drive. To install from a network drive, copy the entire contents of the media to a shared network directory. The installation steps outlined in this guide assume the main installation browser is active. If the installation program does not start automatically, locate and double-click

Setup.exe.

The Sage SalesLogix installations create folders and apply permissions necessary for

Sage SalesLogix to function. To avoid unexpected results, Sage recommends contacting Sage SalesLogix Professional Services Group or your Business Partner before changing default settings on these folders.

Refer to one of the following sections as appropriate for your implementation:

•

“Running the Express Installation” in the following section.

•

“Running the Standard Installation” on page 32

Running the Express Installation

To install

1. On the Sage SalesLogix Installation screen, click Express Server Installation.

If the installation does not detect the necessary prerequisites, you will be prompted to install them. Click Install to allow Sage to install the required components or Cancel to stop the installation. Installing these prerequisites may require your computer to restart.

2. On the Welcome and License Agreement screens, read the information, accept the agreement, and then click Next.

3. Depending on your installation type, you will be prompted to enter some or all of the following information on the installation screens:

• SQL Server sa password - If you have a password set for the sa account on the

SQL Server, type your sa password. The installation requires this password to install and attach the Sage SalesLogix databases.

• SQL Server sysdba password - Type your Microsoft SQL Server sysdba password.

The installation must validate the password of the sysdba user to create a valid connection string for the Sage SalesLogix database.

If you do not enter the sa and/or sysdba password, the databases are not installed.

4. On the remaining screens, click Install and Finish to complete the installation.

To automatically open the Administrator after the installation, select Launch Administrator on the last screen.

Sage SalesLogix Implementation Guide v8.0

Installing Sage SalesLogix

5. If necessary, restart your computer.

The next step...

Depending on your installation and licenses, you may need to do the following after running the Express Installation:

• To enable SpeedSearch to function correctly, you must place all files and folders to be included in the default indexes in the ...\Program Files\SalesLogix\SpeedSearch\TextFile folder on the computer to which you installed Sage SalesLogix. If you plan to customize the SpeedSearch indexes to include files located on another computer, you must change the Local System Account to a Network user such as the SLXService user. See

“Permissions Required for the SLXService User (without Administrator rights)” on page 14

for more information about creating the SLXService user with the necessary access. See

“Managing SpeedSearch Indexes” in the Administrator Help for more information on customizing SpeedSearch indexes.

• If you are installing on Windows 2003 Server, you must share the Sync Logs folder

(created during the installation) and set security to Full Control. The Sync Logs folder is created in \\My Server\Sync Logs.

• Proceed with

Chapter 4, “Configuring the Sage SalesLogix System”

Running the Standard Installation

Depending on your implementation, you may need to run the Standard Installation on multiple computers. Use the following instructions to install all components necessary for your implementation (for example, Sage SalesLogix Server, Administrative Workstation,

Sync Server, and so on).

If you are installing the Sage SalesLogix database on a separate Database Server instead of the same computer as the Sage SalesLogix Server, run the Standard

Server Installation > Install SQL Databases installation on the Database Server before running the Standard Server Installation > Required Administrative Tools and

Servers installation on the Sage SalesLogix Server and other computers.

To install

1. On the Sage SalesLogix Installation screen, click Standard Server Installation.

2. On the Standard Server Installation screen, click Required Administrative Tools

and Servers.

3. On the Welcome and License Agreement screens, read the information, accept the agreement, and then click Next.

4. On the Setup Type screen, select an installation type, and then click Next.

Depending on your configuration, you may need to run the Administrative Tools and

Servers installation on multiple computers. If you have not already done so, review the

Sage SalesLogix Planning Guide for more information on where to install Sage SalesLogix components.

• Select Complete to install all program features and the Microsoft SQL Server databases.

32 Sage SalesLogix Implementation Guide v8.0

Installing Sage SalesLogix

Selecting this option installs Sage SalesLogix using the Local System Account. To set a different user, particularly if SpeedSearch indexes include files located on another computer, select the Typical option.

• Select Typical to select the components to install on this computer.

• Select SalesLogix Server to install the components that primarily handle logging and licensing for Sage SalesLogix.

• Select Administrative Workstation to install the Administrator, Architect, and other Sage SalesLogix utilities.

• Select Application Architect to install the components used to configure and customize the Sage SalesLogix Web components.

• Select Synchronization Server to install the Sync Server.

• Select SpeedSearch Server to install the SpeedSearch Service.

• Select IntelliSync Web Portal to install and deploy the Intellisync Web site to the Administrative Workstation. An Intellisync Web portal is required for implementations that include Intellisync for SalesLogix. If your implementation includes Intellisync for SalesLogix and you prefer to deploy the Web site manually,

refer to Appendix B, “Configuring Intellisync for SalesLogix” .

IIS must be installed for the Intellisync Web Portal. If IIS is not detected, the

Intellisync Web Portal is not installed.

• Sage SalesLogix SData Sync Server - installs the service used for Accounting

Integration functionality.

• Sage SalesLogix Job Service - Installs the service used for scheduling tasks for immediate or delayed execution. You must install this service if your implementation includes any type of Sage SalesLogix Web Client because it is required for features such as rolling over activities, and updating support contracts, opportunities, and leads.

• Select Custom to install only certain components or to change the installation location. Use the Custom Setup screen to enable or disable items for installation.

5. Depending on your installation type, you will be prompted to enter some or all of the following information on the installation screens:

• SQL Server sa password - If you have a password set on the sa account on the SQL

Server, type the sa password. The installation requires this password to install and attach the Sage SalesLogix databases.

• SQL Server sysdba password - Type your Microsoft SQL Server sysdba password.

The installation must validate the password of the sysdba user to create a valid connection string for the Sage SalesLogix database.

If you do not enter the sa and/or sysdba password, the databases are not installed.

• Use Local System Account - Select this option if the local user account has the correct security permissions to install Sage SalesLogix. If you clear this option, set the information for the Sage SalesLogix Service user you created as described in

“Permissions Required for the SLXService User (without Administrator rights)” on page

If SpeedSearch indexes include files located on another computer, do not use the Local

System Account. SpeedSearch requires a Network user to access information on other computers.

• Domain - Type the network domain where you created the Sage SalesLogix

Service user.

• User Name - Type the name of the Sage SalesLogix Service user (for example,

SLXService).

• Password and Confirm - Type the Sage SalesLogix Service user’s password.

Sage SalesLogix Implementation Guide v8.0

Installing Sage SalesLogix

• Port Change button - Changes the port number used for communication between the

Clients and Sage SalesLogix Server. In most implementations, the default port number does not need to be changed. However, if you have another application or service using port 1706, you should change the port number to an unused port.

• Install Blank and Eval databases if they don’t already exist (SQL Server Only)

- This check box appears if you selected the option to install the Sage SalesLogix

Server, or the Complete installation. Unless you previously ran the Install SQL

Databases installation, select this check box to ensure the databases are created.

• Password required for external read-only access - If necessary, type a password used to allow third-party applications to import Sage SalesLogix data but not allow changes to the Sage SalesLogix database.

• Password required for external read/write access - If necessary, type a password used to allow third-party applications to import Sage SalesLogix data and make changes to the Sage SalesLogix database.

For more information on password settings for third-party applications, see the “Understanding Third-Party Access Scenarios” topic in the Connection

Manager Help.

• Create Web Site – This option is available if you selected to install the Intellisync for

SalesLogix Web Portal. Select this check box if you want the installation to automatically create and deploy an Intellisync for SalesLogix Web Site.

If you want to add the portal to an existing Web site, click the Use an existing web site button and specify your existing site.

• Enter a Web site name – Type the name of the Web site that will appear in IIS.

The default name is SalesLogix.

• Enter a Web Site Port – Enter the port number that the SalesLogix Web site will use. Note the port number for future reference.

• Domain – Enter the network domain where you created the WebDLL user as described in

“The WebDLL User” on page 15 .

• User Account – Enter the name of the WebDLL user you created. The default value is WebDLL. If you used a different name, type it exactly as you did when you created it.

• Password and Confirm Password – Type the WebDLL user’s password.

6. On the remaining screens, click Install and Finish to complete the installation.

If your database platform is Microsoft SQL Server and your database is installed on the same machine as the Sage SalesLogix Server, select the Launch Administrator option and

proceed with Chapter 4, “Configuring the Sage SalesLogix System”

. Otherwise, do not select this option and continue with the following sections to create database connections.

7. If necessary, restart your computer.

Creating Database Connections

If you installed Sage SalesLogix using the Express Installation or you ran the Standard

Installation and installed the Sage SalesLogix Server on the Database Server (Microsoft SQL

Server only), Sage SalesLogix automatically creates your database connections.

If your installation includes one of the following scenarios, you must create your database connection manually or modify the default connection. Generally you will create a connection to the blank and evaluation databases.

• If your database platform is Microsoft SQL Server 2008, you must modify the default database connections.

34 Sage SalesLogix Implementation Guide v8.0

Installing Sage SalesLogix

• If your database platform is Microsoft SQL Server, and you are installing the Sage

SalesLogix Server and Sage SalesLogix database on different computers, you must manually create database connections.

• If your database platform is Oracle, you must manually create database connections.

• If you are running Sage SalesLogix on a 64-bit system, you must run the Data Link

Manager in 32-bit mode. See

“Creating a 32-bit OLE DB UDL” on page 37 .

To create

1. On the Start menu, point to Programs, point to Sage SalesLogix, and then click

Connection Manager.

2. In the SalesLogix Connection Manager, do one of the following:

• Click Add to create a new connection.

• Select an existing connection and click Edit.

3. In the Connection Name box: a. In the Name used to refer to this connection box, type a name for the connection.

The connection name can be a maximum of 32 characters and may include spaces.

Duplicate names are not permitted.

b. (Optional) To restrict third-party client access through this connection, set the

Read/Write password for this connection, and if necessary, the Read-Only

password for this connection. (Click the Change button next to the appropriate box to set the password.) c. Click OK.

4. On the Provider tab in the Data Link Properties dialog box, select the appropriate provider for your database platform, and then click Next.

• Microsoft SQL Server 2005: select SQL Native Client

• Microsoft SQL Server 2008: select SQL Native Client 10

• Microsoft SQL Server 2012: select SQL Native Client 11

• Oracle: select Oracle Provider for OLE DB

If the Oracle Provider for OLE DB is not listed on the Provider tab, ensure you have installed the Oracle OLE DB Provider. See

“Windows Authentication Requirements” on page 20 for more information.

5. On the Connection tab: a. For Microsoft SQL Server 2005: In the Data Source box, type the name of the

SalesLogix Server.

For Microsoft SQL Server 2008 or 2012: In the Select or enter a server name box, type the name of the SalesLogix Server.

For Oracle: In the Data Source box, type the Net Service name for your database.

b. Under Enter information to log onto the server, ensure Use a specific user

name and password is selected.

c. In the User name box, type the user name used to log on to the Database server

(for example, sysdba).

d. In the Password box, type the user password (for example, Ma$t3rk3y).

Passwords are case-sensitive.

e. Select the Allow saving password check box. You must select this option or the connection fails.

For Microsoft SQL Server: specify the database to connect to:

• For Microsoft SQL Server 2005, in the Enter the Initial Catalog to Use box, select the Sage SalesLogix database from the list.

• For Microsoft SQL Server 2008 or 2012, select the Select a database option, and then select the database from the list.

Sage SalesLogix Implementation Guide v8.0

Installing Sage SalesLogix g. Click Test Connection to verify the connection.

If you cannot connect to the database, verify that the settings are correct (passwords are case-sensitive). Also verify that the database platform service is running on your

Database Server.

6. (Microsoft SQL Server 2008 Only) On the All tab: a. Double-click Persist Security Info.

b. In the Property Value drop-down list, select True.

c. Click OK.

d. Double-click Integrated Security.

e. Click Reset Value.

Data may exist that does not display in the Value field. This value must be reset to ensure that all data is removed.

Click OK.

7. (Oracle Only) On the All tab: a. Double-click Extended Properties.

b. In the Property Value box, type chunksize=3000.

You must set the Property Value if you plan to create custom views that will be included when you create a remote database. If the value is not set, the SQL View is truncated on the remote database.

c. Click OK.

8. Click OK to save the information and close the Data Link Properties dialog box.

The next step...

•

For installations running Sage SalesLogix on a 64-bit system, proceed with “Creating a

32-bit OLE DB UDL” on page 37 .

• For Microsoft SQL Server installations, proceed with

Chapter 4, “Configuring the Sage

SalesLogix System”

• If your implementation included the Sage Job Service and Sage SData portals, you must install the Web Host, build and deploy the portals and modify the WebDll user permissions. See

Chapter 5, “Installing the Web Components” .

• For Oracle installations, create client database connections as detailed in the following section.

Creating Client Database Connections for Oracle

After installing a Client application (Administrator, Sage SalesLogix Client, etc.) on Oracle, you must create a Net Service Name in the Oracle Net Configuration Assistant and a database connection in the Data Link Manager.

Creating a Net Service Name

You must create the Net Service Name (also called database alias) on the computer on which you installed a Client application. The Data Link Manager uses this alias to connect to the

Sage SalesLogix database.

Ensure that the database connection name is the same for every connection you create on all your Sage SalesLogix Client computers. The names must match exactly for all connections to work.

Refer to the Oracle documentation for instructions to create a database alias.

36 Sage SalesLogix Implementation Guide v8.0

Installing Sage SalesLogix

Creating a Client Database Connection

The Data Link Manager is used to create a connection from the Client computer to the Sage

SalesLogix Server. This connection is configured automatically for Microsoft SQL Server installations. However, you must create a connection manually on each computer running

Sage SalesLogix on Oracle.

To create

1. Click Start, point to Programs, point to Sage SalesLogix, and then click the application you want to log on to (for example, Administrator).

2. In the Please log on dialog box, click the ellipsis button in the Log on to box.

3. In the Data Link Manager, click Add.

4. On the Provider tab of the Data Link Properties dialog box, select the SalesLogix

OLE DB Provider and then click Next.

5. In the Select or enter the SalesLogix Server box, select the computer on which you installed the Sage SalesLogix Server.

For Remote users, enter the computer name on which the Remote user’s database is installed.

6. In the Select SalesLogix database name box, select the name of the connection configured for your database using the Connection Manager.

See

“Creating Database Connections” on page 34

for more information.

7. In the SalesLogix User Name and SalesLogix Password boxes, type the user name and password used to log on to Sage SalesLogix.

• When logging on to a third-party application using the Sage SalesLogix OLE DB

Provider, these fields allow you to log on using Sage SalesLogix security.

• If you are not using a third-party application, the user name and password are used to test the connection.

8. Select the Allow Saving Password check box. You must select this option or the connection fails.

9. Click OK.

Creating a 32-bit OLE DB UDL

If you are running Sage SalesLogix on a 64-bit system and you have installed the provider extensions, you must run the Data Link Manager in 32-bit mode. Use the following steps to configure the Data Link Manager for a 64-bit system.

Both 32-bit and 64-bit machines must run the Data Link Manager and access the Sage

SalesLogix OLE DB Provider in 32-bit mode.

To create

1. Using Notepad create a blank UDL file named “test.udl”.

2. Save the UDL file to your C: drive.

3. Open the blank UDL file doing one of the following:

• For a 64-bit machine, run the following command:

C:\Windows\syswow64\rundll32.exe "C:\Program Files (x86)\Common

Files\System\Ole DB\oledb32.dll",OpenDSLFile C:\test.udl

• For a 32-bit machine, double-click the file in the file manager and run

C:\Windows\system32\rundll32.exe "C:\Program Files\Common Files\System\OLE

DB\oledb32.dll",OpenDSLFile <SalesLogix install folder>\’test’.udl

Sage SalesLogix Implementation Guide v8.0

Installing Sage SalesLogix

4. With the blank UDL open, open the Data Link Manager.

To open the Data Link Manager, open a Sage SalesLogix application and click the ellipsis button in the Log on to box.

5. In the Data Link Manager, create a new database connection and make sure you select the SalesLogix OLE DB Provider on the Provider tab.

6. Save the connection.

7. Move the UDL file to all computers that require a connection to Sage SalesLogix.

By default, the file should be stored in C:

After completing this chapter...

You have completed tasks 6-9 of the “Required Tasks”

checklist.

Proceed with Chapter 4, “Configuring the Sage SalesLogix System”

38 Sage SalesLogix Implementation Guide v8.0

Chapter 4 Configuring the Sage SalesLogix System

Before beginning this chapter...

Install Sage SalesLogix as described in Chapter 3, “Installing Sage SalesLogix”

Use the instructions in this chapter to...

Configure the Sage SalesLogix system components and set up your main office.

These tasks are required for all Sage SalesLogix installations.

Once you have installed the server components, you must log on to the Administrator and complete the following tasks:

• Add licenses.

• Enter Office information.

• (Oracle Only) Apply the Service Pack bundle.

• (Optional) Configure SpeedSearch.

• Configure Sage SalesLogix options.

• Add Customer Service and/or Support information (if you are using the customer service and/or support features).

Logging On to the Administrator

The Administrator is used to manage users, servers, and offices. The following steps are also used when logging on to other Sage SalesLogix Client applications.

To log on

1. On the Start menu, point to Programs, point to Sage SalesLogix, and then click

Administrator.

2. In the Please log on dialog box: a. In the Username box, type admin.

b. In the Password box, type the corresponding password for the user name.

The initial admin password for your production (blank) database is password.

Passwords are case-sensitive and must be entered in lowercase characters, with no spaces. c. In the Log on to box, ensure the correct database connection name displays (for example, SalesLogix_Server).

If necessary, you can add a new connection or change an existing connection using the Connection Manager.

3. Click OK.

If you cannot connect to the database, ensure that the database path is correct in the Data

Link Manager.

Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix System

Understanding the Setup Assistant

The Setup Assistant is used to simplify the installation of licenses, to simplify the configuration of your office information, and to create users based on a Windows user list or pre-configured system templates.

Adding Licenses

Licenses determine the servers, offices, and users you can add to Sage SalesLogix. See the

Sage SalesLogix Planning Guide for a description of each available license.

You can add licenses by typing the license number, using copy and paste from a text file, or by loading them directly from a file (right-click, and then click Load from file). The License

Wizard filters extraneous text from the text file.

• All implementations require a Sage SalesLogix license (Standard, Advanced, or Premier).

• The Web Host requires the Sage SalesLogix Web Server license.

• To add Web Viewer users, you must add a WebViewer license. Users who access

WebViewer require the same hardware, browser, and configuration as users who access the Web Client. See the “WebViewer User” topic in the Administrator Help for more information.

See the “Using the License Wizard to Add Licenses” topic in the Administrator Help for detailed steps.

Entering Office Information

After adding licenses, use the Setup Assistant to enter your main office information. This information includes your primary address, shipping address, and phone numbers.

To enter

1. In the Setup Assistant, select Step 2 - Enter Office Information, and then click Run

Selected Step.

2. Type your company information such as division name (if applicable), primary and shipping addresses, and telephone numbers. Only the Company Name is a required field.

3. Click the Sync Options tab.

4. In the Shared Paths section, make sure the Sales Library and Attachments paths are correctly mapped to the folders you created when configuring logging access. See

“Creating the Logging Folders” on page 25 for details.

5. Click OK.

The last step of the Setup Assistant simplifies the process of adding Sage SalesLogix users.

The process for adding users is detailed in

Chapter 6, “Configuring Sage SalesLogix Users”

Configuring Sage SalesLogix Options

You can configure the appearance of the Administrator and Sage SalesLogix Client, set default password and Remote database options, and configure other custom options. The options required for a successful implementation are detailed in the following sections.

Refer to the “Configuring SalesLogix Options” topic in the Administrator Help for information on other options.

40 Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix System

Setting Accounting Options

Accounting options contain system-level information that allows Sage SalesLogix to communicate with external accounting applications. This information must be configured before database transfer between Sage SalesLogix and the accounting application can take place.

• See the “Setting Accounting Options” topic in the Administrator Help for details.

• When sharing accounting information using Accounting Integration, see

Appendix C, “Configuring Accounting Integration”

for configuration details.

Setting Database Options

Database options allow you to configure the default settings used when creating Remote user or Remote Office databases. If you have a Microsoft SQL Server database and your implementation does not include Remotes, you do not need to set database options.

To set

1. On the Administrator Tools menu, click Options, and then click the Database tab.

Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix System

Option

Databases Used

Site Codes begin with these characters

Action

Select your database type(s) for the main office and Remotes. The database type defaults to Microsoft SQL Server. You must set your database type(s) before using DB Manager.

Type a one- or two-digit prefix for Remote site codes. If you do not use this feature, site codes are randomly generated. Forcing a prefix helps identify the source of a particular file, such as a

Remote Office.

Allow Unicode field types

Select to enable field selectable Unicode support.

Field selectable-Unicode is limited to specific feature areas.

Extending the database for Unicode requires a strong knowledge of Sage SalesLogix and its database schema. Before implementing this feature, you should carefully review the “Understanding

Unicode” topic in the Administrator Help for details.

Host DB Owner ID Type the user name of the Remote database owner. This must be set to sysdba.

Host DB Owner password

Type the sysdba password used by the host database. This is configured automatically when logging on to Sage SalesLogix.

Host DB Admin ID Type the user name of the database system administrator. This is usually sa, but may be any admin level SQL Server user identity.

If the Host database is Oracle, then it must be set to sa.

Host DB Admin password

Type the password corresponding to the Host DB Admin ID user name. For Oracle, leave this field blank.

Sync Global Remote

SA Password for existing databases

Select this option to send a new password to a remote database through synchronization. This check box is only available to users who have logged on as admin. During synchronization, if the password set in the Current Remote SA Password box matches the password on the Remote Microsoft SQL Express instance, then the password is changed to the password set in the New Remote SA

Password box. The new password is sent to remotes during the next synchronization cycle.

Server Name

Note

If the SQL Express instance was installed from the Sage

SalesLogix media, and you correctly set the SAPWD property, the default instance password is SLXMa$t3r.

Displays the machine name of the server.

This field is Read Only for a SQL Server host, and is blank for an

Oracle host. For Oracle, set this value to a computer where

Microsoft SQL Express is running (for example, the administrator's computer).

42 Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix System

Option

Create Remote DB in server directory

Action

Type the path to the location where Remote databases will be created.

The location of the folder can be on the Database Server, the

Administrative Workstation’s Microsoft SQL Express instance, or any Microsoft SQL Server where the appropriate permissions have been provided (for the sa or similar user). Use the format drive letter:\shared_folder_path. Do not include the computer name.

• The folder must be shared.

• If you are creating remote databases on the Microsoft SQL

Server Host, ensure the permissions for Creator Owner are set to a minimum of Change.

Prepare Remote DB and create it immediately

Creates and runs the DTS file. The DTS file creates the remote database. This is the recommended option.

Prepare Remote DB and wait for

Administrator

Creates and saves the DTS file. This enables you to run the DTS file and create the database at a later time. This setting is not recommended unless you are an experienced Microsoft SQL DBA.

This method requires a user interface and scheduler to connect to the database and run the DTS package.

2. Click OK.

Understanding E-Mail Integration

Sage SalesLogix is integrated with Microsoft Outlook to allow users to share information between the two applications.

Feature and Availability

Standard Outlook Integration

Allows users to: Availability

• Add Sage SalesLogix Contacts to Outlook Network only

• Use the Send SLX button in Outlook to record information to Sage SalesLogix

Network and Web

Network and Web • Save Outlook attachments to Sage

SalesLogix

• Record to Sage SalesLogix History from

Outlook in one click

Network and Web

• Drag and drop from the Outlook Inbox to

Sage SalesLogix History

• Use the Sage SalesLogix Address Book in

Outlook

Network and Web

Network only

• Attach documents from the Sage

SalesLogix Library to an Outlook e-mail

Network only

• Attach a Sage SalesLogix Contact vCard in

Outlook

Network only

Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix System

Feature and Availability

Advanced Outlook Integration

Intellisync for SalesLogix

Allows users to:

• Use Outlook Attendee availability in Sage

SalesLogix

• Schedule meeting requests in Sage

SalesLogix and Outlook (even for non-

Sage SalesLogix users)

• Use the Outlook Calendar in Sage

SalesLogix

• Flag Outlook e-mail received from Sage

SalesLogix Contacts

• Fully synchronize with Outlook

• Synchronize to a PDA

• Add Outlook Contacts to Sage SalesLogix

Availability

Network only. Advanced

Outlook Integration is not available for the Web.

Full functionality available for Network and Web.

Activating Advanced Outlook Integration

When Advanced Outlook Integration is activated, the following features are enabled. All other

Advanced Outlook Integration features require no activation.

• The Attendee Availability tab appears when a user schedules a meeting or phone call in the Sage SalesLogix Client, which automatically places the request on the users’ Sage

SalesLogix and Outlook calendars.

• When a user accepts a meeting invitation in Outlook, the meeting is automatically placed on the user’s Sage SalesLogix and Outlook calendars.

Internet Only Mode is not recommended for Advanced Outlook Integration.

To activate

1. On the Administrator Tools menu, click Options, and then click the Outlook tab.

2. Select the Activate Advanced Outlook Integration check box.

3. Select how attachments using Send SLX are saved with a history record.

• Save attachments as individual files - Attachments to e-mail are saved as individual files on the Attachments tab for the e-mail activity record (in History). If the user answers “Yes” to the prompt which asks if the user would like to save attachments to the account or contact that is associated to the e-mail, the individual files are saved as attachments.

• Bundle attachments with e-mail message (MSG format) - The e-mail is attached as an MSG file to the history record. If the user answers “Yes” to the prompt which asks if the user would like to save attachments to the account or contact that is associated to the e-mail, the MSG file is saved as an attachment.

4. Configure Internet domains that should be excluded from some of the features of

Advanced Outlook Integration.

When you add a domain, e-mail messages are not recorded to history for users in that domain and e-mail messages from users in the domain do not contain the “Flag for Follow up.” a. Click Add.

b. In the New Domain Entry dialog box, type the domain name.

Use the format sage.com or [email protected]. Domain exclusion settings are case-sensitive.

c. Click OK.

After you add a domain exclusion, you can deactivate, edit, or delete it by selecting the domain and clearing the check box or clicking the appropriate button.

44 Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix System

Additional configuration is required for Standard Outlook Integration and Intellisync for

SalesLogix. Configuration steps are detailed in

Chapter 7, “Installing Network Clients”

Chapter 8, “Configuring the Web Client” , and

Appendix B, “Configuring Intellisync for SalesLogix” .

Adding Address Lists to the Outlook Addressing Tab

Adding Sage SalesLogix Address Lists to the Outlook Addressing tab allows users to perform contact name resolution. Contact name resolution occurs when a user types a contact name in the To, Cc, or Bcc fields in an e-mail message. Outlook then reconciles the contact name with the information in the Sage SalesLogix Address List. In addition to contact names, you can add Account and/or Opportunity Address Lists to reconcile Sage SalesLogix account, opportunity, ad-hoc groups, and user names.

This section applies to Standard Outlook Integration in a Network environment. The following steps are not required if you are implementing Advanced Outlook

Integration, Intellisync for SalesLogix, or Standard Outlook Integration on the Web.

To add

1. In Microsoft Outlook, on the Tools menu, click Address Book.

The Address Book dialog box appears.

2. On the Tools menu, click Options.

3. In the Addressing dialog box, click Add.

4. In the Add Address List dialog box, scroll to the SalesLogix Address Book listing, and select an address list (for example, Contacts).

5. Click Add.

6. Continue adding the appropriate Sage SalesLogix address lists, and when finished, click

Close.

7. In the Addressing dialog box, click OK.

8. Close the Address Book dialog box.

Adding Customer Service and Support Information

If you are using customer service and/or support features, you must complete the

Service/Support tab on the Office Information dialog box. Use this tab to set the hours of operation for your business and to determine how tickets are assigned.

To add

1. On the Administrator Navigation Bar, click Systems.

2. Click the Offices tab, double-click your main office in the grid, and then click the

Service/Support tab.

3. In the Open and Close boxes, select the time your normal business hours start and end.

The Hours of Operation area defines the time used for certain reports and follow-up activities.

4. In the Time units in minutes box, type the smallest billable time unit to use for tracking the time spent on a ticket.

5. If your company includes the weekend as part of the regular work week, select the Work

weekends check box.

6. In the Ticket Assignment Options area, select one of the following:

• Unassigned - Tickets are left unassigned until a user views the call and assigns it.

• Logged-in user - Tickets are assigned to the user that saves the ticket.

Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix System

• Auto-assignment - Tickets are assigned to the user or team associated with an

Area. If an Area has no associated user or team, the ticket is left unassigned. Area values are configured in

“Creating Area, Category, and Issue Lists” on page 72

7. Select the Default user or team assigned to account overrides Ticket Assignment

Options check box if you want the Default User/Team selected on the Sage SalesLogix

Client > Account > Notifications tab to override the Ticket Assignment Option.

For example, if you set the Ticket Assignment Option to Logged-in user, and select this check box, any tickets created for an account that has a Default User/Team set in the Sage

SalesLogix Client will be assigned to the defined user/team. Any accounts that do not have a Default User/Team set, will be assigned to the logged-in user. If this check box is cleared, new tickets for an account are assigned to the logged-in user even if the account has a user/team selected as the default for new tickets.

8. Under SpeedSearch, choose whether or not to use an approval process to determine which new tickets and defects are added to SpeedSearch.

Refer to the “Understanding the SpeedSearch Approval Process” topic in the

Administrator Help for more information.

9. Click OK.

Understanding SpeedSearch

SpeedSearch allows users and external customers to search for information stored in the

Sage SalesLogix database, such as tickets, standard problems, procedures, attachments,

Library documents, and external documents on your network. An index is a collection of files or records that a user can search against.

The Advanced SpeedSearch license is required to search the History and Activity indexes.

Typical implementations include only one SpeedSearch Service. However, if your implementation includes multiple Sage SalesLogix Servers and databases, you should install additional instances of the SpeedSearch Service on separate machines. Then, you must use a configuration utility to match each SpeedSearch Service with the appropriate Sage

SalesLogix Server and database connections.

If you have more than one SpeedSearch Server or for more SpeedSearch information, see the following topics in the Administrator Help.

• To configure SpeedSearch for multiple databases, see "Updating the SpeedSearch

Service Configuration".

• For a description of the default indexes, see “Standard SpeedSearch Indexes”.

• For detailed steps on creating new file system and database indexes, see

“Managing SpeedSearch Indexes”.

• To change the default index schedules or create new schedules, see “Managing

SpeedSearch Schedules”.

• To understand how SpeedSearch information synchronizes with Remotes, see

“Understanding SpeedSearch and Remotes”.

46 Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix System

Maintaining Database Security

After installing and configuring Administrator, you should change passwords to maintain maximum security. For security reasons:

• Change the administrator user password when you configure your users. See the

“Changing a User’s Password” topic in Administrator Help for more information.

• Change your database password using SQL Server Management Studio or DBA Studio.

After changing the sysdba password in SQL Server Management Studio or DBA Studio, you must change the password in the Connection Manager on the Sage SalesLogix Server. See the Connection Manager Help for detailed instructions.

After completing this chapter...

You have completed tasks 10-14 in the “Required Tasks”

checklist. If your implementation includes the Web components, Intellisync for SalesLogix with Remote offices or Offline Web

Client users, or the Sage SalesLogix Job Server, proceed with Chapter 5, “Installing the Web

Components” . Otherwise, proceed with

Chapter 6, “Configuring Sage SalesLogix Users” .

Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix System

48 Sage SalesLogix Implementation Guide v8.0

Chapter 5 Installing the Web Components

Before beginning this chapter...

Ensure the Admin Tools and Servers network components are installed, configured, and working correctly as detailed in Part I of this guide.

Use the instructions in this chapter to...

Install server components and deploy your Web site. These tasks are required for all

Sage SalesLogix Web installations, including Remote Offices and Offline Client Users.

The Sage SalesLogix Web components provide the infrastructure supporting the portals needed for the following functionality:

• Sage SalesLogix Web Client

• Intellisync for SalesLogix

• Job Service

• SData

• Sage SalesLogix Mobile

• Web Reporting.

The Sage SalesLogix Web components are:

• Web Host: required for users to access Sage SalesLogix functionality via the Web

• SalesLogix Cache Server: used to store Web data which allows the cache to be real-time.

• Web Reporting Server: required for Web Client users to access, run, and filter the same reports as Sage SalesLogix Network Client users.

Most implementations of Web Host and Web Reporting components require two Web servers.

While the Web Host and Web Reporting components may reside on one machine, Sage

SalesLogix recommends you install Web Reporting on a separate Web Server to avoid performance issues. Refer to the typical Web implementation scenarios outlined in the Sage

SalesLogix Planning Guide for the Web implementation scenario that best matches your company’s needs.

Installing the Web Host

The Web Host enables users to access Sage SalesLogix functionality via the Web. Larger implementations require additional Web Hosts and/or virtual servers. (For more information, see

“Scaling the Web Implementation” on page 141 .)

This installation:

• Installs the Web components and Web content files.

• Automatically creates a Web site if you select the Create Web Site check box during the installation.

To install

1. You must log on as the local administrator to install the Web components on each machine.

2. On the Sage SalesLogix Installation screen, click Standard Server Installation.

Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

3. On the Standard Server Installation screen, click Web Host on IIS.

4. On the Welcome and License Agreement screens, read the information, accept the agreement, and then click Next.

5. On the Setup Type screen, select an installation type, and then click Next.

• Select Complete to install the Web Host and SalesLogix Cache Server.

• Select Custom to install only certain components or to change the installation location. Use the Custom Setup screen to enable or disable items for installation.

By default, the SalesLogix CacheServer is installed on the Web Host. If you install the SalesLogix Cache Server on a server other than the Web Host, you must manually configure the web.config file to access the SalesLogix Cache

Server computer. See the “Configuring the SalesLogix Cache Server” topic in the Application Architect help for details.

6. Depending on your installation type, you will be prompted to enter some or all of the following information on the installation screens:

• Use an existing web site - If you want the installation to use an existing Web site, click this button and select the Web site name. If you created a Web site for

Intellisync for SalesLogix in the Administrative Tools and Servers installation, you can select the existing SalesLogix Web site for the Web components.

• Create Web Site – Select this check box if you want the installation to automatically create a Web Site. Selecting this check box creates a Web site you can use to deploy the Web portals.

If you prefer to perform Web site configuration manually, clear the Create Web Site check box and follow the instructions in

Appendix D, “Advanced Web Host

Configuration”

• Enter a Web site name – Type the name of the Web site that will appear in IIS. The default name is SalesLogix.

• Port – Enter the port number that the SalesLogix Web site will use. Note the port number for future reference. You must use port number 1025 or greater.

• Domain – Enter the network domain where you created the WebDLL user as described in

“The WebDLL User” on page 15 .

• User Account – Enter the name of the WebDLL user. The default value is WebDLL. If you used a different name, type it exactly as you did when you created it.

• Password and Confirm Password – Type the WebDLL user’s password.

• Configure SalesLogix Database - Clear this check box if you do not want to connect to the Sage SalesLogix database, but still want to create a Web site. When you clear this check box, the other options on this screen are disabled.

• SalesLogix Server – Select or type the name of the computer on which you installed the Sage SalesLogix Server.

• SalesLogix Database Alias – Select or enter the name of the connection to the

Sage SalesLogix database.

• Search for servers on port - Enter a port. By default, this is set to port number

1706.

• User Name – Enter a Sage SalesLogix Server user name (such as Admin).

• Password – Enter the Sage SalesLogix Server password for the SalesLogix user.

7. On the remaining screens, click Install and Finish to complete the installation.

50 Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

Building a Web Platform

You must build the Web platform before you configure or deploy Web application files.

To build

1. Open the Application Architect.

2. On the View menu, click Project Workspace Manager.

The Project Workspaces window opens and the default Sage SalesLogix Web project workspace appears (VFS on server:saleslogixdb).

The server is the name of your Web server, and the SalesLogix DB is the name of your Sage SalesLogix database.

3. Double-click the default project workspace.

The Project Explorer window opens and the project you selected appears in a tree view.

4. Click the project, and then on the Build menu, click Build Web Platform.

Failure to build the Web platform before deploying will result in errors.

5. If necessary, on the View menu, click Output Window to view the build status.

Deploying a Sage SalesLogix Web Portal

The Application Architect Deployment Explorer allows you to create deployments that consist of Targets (destinations) and Portals (configurations). A deployment is used to configure a portal, or Web application, for deployment to a specific target or destination.

Typically, Web portals are deployed to localhost on IIS. However, you have the option of deploying the Web portals to a Web site you create during Web Host installation or to a Web site you create using IIS.

To deploy

1. On the Application Architect View menu, click Deployment Explorer.

2. Expand Deployments, and then double-click the appropriate deployment name. The following default portals are available:

• Core Portals - contains the Sage SalesLogix Web Client, ProcessHost, SData, and

SageJobService portals. The ProcessHost and SlxClient portals are dependent on each other; although the Process Host is not necessary for the Web Client to function. The

SageJobService portal requires the SData portal.

• Customer Portal - contains the Customer Portal portal.

• Intellisync Portal - contains the Intellisync for SalesLogix portal. If your implementation includes Intellisync for SalesLogix, deployment information is

detailed in “Deploying the Intellisync for SalesLogix Portal to the Remote Office and

Offline Web Clients” on page 131 .

• Lead Capture - (if available) contains the Lead Capture portal.

• Mobile Portal - contains the Mobile Client portal. If this portal is not visible, select

Core Portals, right-click IIS, select the SlxMobile portal and then click OK.

• Remote Sales Client - contains the Sage SalesLogix Web Client and the Intellisync for SalesLogix portals.

• Remote Web Reporting - contains the Sage SalesLogix Web Reporting portal.

• Web Reporting - contains the Sage SalesLogix Web Reporting portal.

3. In the Name box, type a name for the deployment.

4. In the Description box, type a description for this deployment.

Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

5. (Optional) Select the Use this deployment for debugging option to set this deployment as your default deployment.

This option allows you to use the Run button on the toolbar to perform a one-click deployment of all portals you designate in a default deployment.

6. In the Deployment Targets tree view, click IIS.

The IIS Target Settings appear.

a. In the Server box, type the name of your Web Host server.

By default, this is localhost; however, you can deploy to any Web Host server.

b. In the Base Directory box, type the location where the files generated for the Web server will be saved.

• The default is ...\inetpub\wwwroot. If necessary, click the ellipsis button to browse for and select a different directory path.

The Sage Job Server default Base Directory is %ALLUSERSPROFILE%\Sage\

Scheduling\Tenants. If you change this default, you must change the tenantRoot key value in the Sage.Scheduling.Server.exe.config file. Refer to

An Introduction to Job Server in Sage SalesLogix.pdf for details.

c. In the Port box, type the port number for your Web Host server. It must match the port for the Web site. For example, if you used the default port 3333 during Web Host installation, the port is 3333.

d. In the App Pool box, type the name of the application pool for your Web site.

This name corresponds to the associated application pool for your Web site. For example, if you used the default SalesLogix Web site, the App Pool is SalesLogix. For the Process Host portal, you can use the same IIS application pool used by the Sage

SalesLogix Web Client portal.

e. Ensure the Deploy Target check box is selected. This indicates the target is active and should be deployed.

(Process Host and SData only) Ensure the Restore Virtual Directory Settings on

Update option is cleared.

g. (Web Reporting only) Ensure you select the Restore Virtual Directory Settings on

Update option.

7. Click the SlxClient tab: a. In the Virtual Directory box, type the alias name for the virtual directory. The default Virtual Directory is the portal name. For example, SlxClient,

SLXCustomerPortal, and so on.

If you are configuring the SData portal, do not change the virtual directory value.

b. In the Sub Directory box, type the folder name where all portal files will be copied under the target’s base directory.

c. Select the Deploy Portal option.

This indicates the portal is active and should be deployed.

When the Inherit from Target check box is selected, the deployment uses the port and application pool settings of the current target to deploy the portal

(these settings are specified under IIS Target Settings). If necessary, clear this check box and set a different Port and App Pool for the portal.

8. When deploying the Core Portals, repeat step 7 for the ProcessHost and SData portal

tabs.

9. In the Deployment Targets tree view, click SageJobService (File System).

a. In the Base Directory box, type the location where the files generated for the Job

Service will be saved.

52 Sage SalesLogix Implementation Guide v8.0

Installing the Web Components b. The default is ...%ALLUSERSPROFILE%\Sage\Scheduling\Tenants. If necessary, click the ellipsis button to browse for and select a different directory path.

10. On the SlxJobService tab: a. In the Sub Directory box, type the folder name where all portal files will be copied under the target’s base directory.

b. Select the Deploy Portal option.

This indicates the portal is active and should be deployed.

11. Click Save.

12. Click Deploy All.

When the Output Window indicates the deployment is finished, define the default document for the Web site.

For more process orchestration information, refer to the “Implementing Process

Orchestration” topic in the Application Architect help.

Configuring the WebDLL User for Windows Authentication

You must configure the WebDLL user for Windows Authentication to allow the Sage

SalesLogix Web Client to open a connection to the Sage SalesLogix database. This task must be completed even in installations that do not include Windows Authentication for Sage

SalesLogix Network and Web Client users.

To configure

1. Open the Administrator.

2. On the Navigation Bar, click Users.

3. In the Users view, double-click the Admin user name, and then click the General tab.

4. Select the Use Windows Authentication check box.

5. In the Windows ID box, click the Find button.

The Please select a Windows user to match the SalesLogix user dialog box appears.

6. In the Add Name box, type your server name and WebDLL user name, and then click

OK.

For example, servername\WebDLL.

7. In the Import user data box, click No, and then click OK.

8. Set permissions to allow the WebDLL user to alter the DNS on the domain.

To configure Windows Authentication for Web Client users, setspn commands must be executed by a user that has rights to modify the active directory. This permission can be removed from the WebDLL user after running the setspn commands.

If you have a DNS admin user with proper permissions, you can omit this step.

Modifying the Log On User for Sage Job Service

The Sage Job Service must be able to log on as a Sage SalesLogix user, and that user must have access to SLX Application Entities (such as Leads and Opportunities) and Activities. By default, the user assigned to the Sage Job Service is the Local System Account user. After installation, you must set the Job Service to log on as the WebDLL user after making sure the

WebDLL user is mapped to the Sage SalesLogix Admin user. If your implementation includes

Remote Office(s), ensure there is a trust relationship between the domain at the Main office and the domain at the Remote office.

If you are using the WebDLL user and have already completed “Configuring the

WebDLL User for Windows Authentication” on page 53

, begin at step 8.

Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

To configure

1. Open the Administrator.

2. On the Navigation Bar, click Users.

3. In the Users view, double-click the Admin user name, and then click the General tab.

4. In the Windows ID box, click the Find button.

The Please select a Windows user to match the SalesLogix user dialog box appears.

5. In the Add Name box, type your server name and user name, and then click OK.

For example, servername\WebDLL.

6. In the Import user data box, click No, and then click OK.

7. Set permissions to allow the WebDLL user to alter the DNS on the domain.

8. Open Windows Services and right-click the Sage Job Service.

9. Click Properties.

10. In the Sage Job Service properties dialog box, click the Log On tab, and select the

This account option button.

11. Click Browse.

12. Specify the Location.

For example, the domain where you created the WebDLL user.

13. Type the name of the domain user credentials specified in step 5.

In this example, the WebDLL user.

14. Restart the Job Service and verify that it started successfully.

Configuring the SData Portal

The SData portal provides RESTful data access to the Sage SalesLogix database through

SData feeds. It also provides a communication front-end to the synchronization service used to integrate with accounting systems and to the Sage Job Server. The SData portal is also required for Desktop Integration functionality, Windows Authentication, and Sage SalesLogix

Mobile.

Refer to one of the following sections as appropriate for your Windows version:

•

“Windows 2003” on page 54

•

“Windows 2008” on page 55

Windows 2003

After deploying the SData portal, you must configure authentication settings and configure handler mapping.

To configure

1. Open IIS Manager, expand Web Sites, and then expand the SalesLogix Web site.

2. Right-click the SData portal, and then click Properties.

3. Click the Directory Security tab, and then, under Authentication and Access

Control.

4. Check Enable anonymous access and enter the User name and Password for the

WebDLL user.

5. Under Authenticated Access, clear the Integrated Windows Authentication option.

6. Click OK.

54 Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

7. On the Virtual Directory tab, in the Application Settings section, click

Configuration.

The Application Configuration dialog box opens.

8. On the Mappings tab, under Application Extensions, select the .ashx extension, and then click Edit.

The Add/Edit Application Extension Mapping dialog box opens.

9. Select the entire entry in the Executable box, right-click, and then click Copy.

10. Select the All verbs option, and then click OK.

11. In the Wildcard Application Maps area, click Insert.

12. In the Add/Edit Application Extension Mapping dialog box, right-click the

Executable box, and then click Paste.

The file C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll is pasted into the box.

13. Clear the Verify that file exists check box.

14. Click OK.

15. Click OK twice more.

16. Close IIS Manager.

If you are using Windows Authentication, see the topic "Enabling Windows Authentication

Access for Web Client Users" in the Administrator Help for additional configuration steps.

Windows 2008

No manual configuration steps are required. Integrated app pools (used in Sage SalesLogix version 8 and later) do not require manual handler mapping setup. Any other settings are performed by the deployment.

If you are using Windows Authentication, see the topic "Enabling Windows Authentication

Access for Web Client Users" in the Administrator Help for additional configuration steps.

Configuring for Performance

This section contains recommendations for optimizing your Web site performance.

Configuring IIS Settings for Performance

In order to cache, and therefore improve performance, use the following IIS settings for the css, images, and libraries subdirectories in each Web Client portal that you deploy.

To configure for IIS6

1. In IIS Manager, expand Web Sites, and then expand the Web site containing the Web

Client portal you want to configure for performance.

2. Expand SlxClient, right-click the css subdirectory folder, and then click Properties.

3. Click the HTTP Headers tab.

4. Select the Enable content expiration check box.

5. Select Expire after and set the expiration for 365 days.

Sending a query more frequently will impact performance. If you often customize files in the css, images, and libraries directories, you can either set a shorter expiration period or else users may need to clear the browser cache to get changes.

6. When you are finished, click Apply.

7. Repeat steps 2-6 for the images, jscript, and libraries subdirectories, and then click OK.

Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

To configure for IIS7.x

1. In IIS Manager, expand Web Sites, and then expand the Web site containing the Web

Client portal you want to configure for performance.

2. Expand SlxClient and click the css subdirectory folder.

3. In the IIS section, open the HTTP Response Headers item.

4. In the Actions panel, select the Set Common Headers... link.

5. Select the Expire Web Content check box.

6. Select Expire after and set the expiration for 365 days.

7. When you are finished, click OK.

8. Repeat steps 2-6 for the images, jscript, and libraries subdirectories, and then click OK.

Enabling HTTP Compression

If your Web site(s) use large amounts of bandwidth, or if you would like to more effectively use bandwidth, you may want to consider enabling HTTP compression. HTTP compression provides faster transmission time between compression-enabled browsers and IIS.

Compression has no one-size-fits-all solution that enables all users to achieve the same results in different environments. However, there are some guidelines that may increase performance in terms of lighter network bandwidth at the expense of CPU and memory used by the IIS server.

You must be a member of the Administrators group on the local computer to enable compression.

Refer to one of the following sections as appropriate for your implementation:

•

“IIS 6”

in the following section.

•

“IIS 7 with IIS 6 Compatibility” on page 57

IIS 6

Use the following steps to enable HTTP compression on IIS 6.

To enable

1. Open IIS Manager, double-click the local computer, right-click the Web Sites folder, and then click Properties.

2. Click the Service tab, and in the HTTP compression section: a. Select the Compress application files check box to enable compression for dynamic files.

b. Select the Compress static files check box to enable compression for static files.

c. In the Temporary directory box, type or browse the path to a local directory.

Once a static file is compressed, it is cached in this directory until it expires, or the content changes. The directory must be on the local drive. The directory cannot be compressed or shared, and the directory must include Full Control access to the identity of the application pool or to the IIS_WPG group.

d. Under Maximum temporary directory size, select Unlimited.

If you specify a maximum size, then when the limit is reached, IIS automatically cleans up the temporary directory by applying the "least recently used" rule.

3. Click Apply, and then click OK.

4. On the Start menu, point to Programs, point to IIS Resources, point to Metabase

Explorer, and then click Metabase Explorer.

Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

HTTP compression requires the Internet Information Services (IIS) 6.0 Resource Kit Tools.

For download information, go to www.microsoft.com and search on 6.0 resource kit tools.

5. In IIS Metabase Explorer, expand your server, expand LM, expand W3SVC, expand

Filters, and then expand Compression.

a. Select deflate and set the following values:

• HcDoDynamicCompression = 1

• HcDynamicCompressionLevel = 10

• HcFileExtensions = htm,html,txt,css,xml,js

• HcScriptFileExtensions = asp,dll,exe,aspx,ashx,asmx b. Select gzip and set the following values:

• HcDynamicCompressionLevel = 10

• HcFileExtensions = htm,html,txt,css,xml,js

• HcScriptFileExtensions = asp,dll,exe,aspx,ashx,asmx c. Select Parameters and set the following Data values:

• HcDoDynamicCompression = 1

• HcDoStaticCompression = 1

• HcNoCompressionForHttp10 = 0

• HcNoCompressionForProxies = 0

6. Close IIS Metabase Explorer.

IIS 7 with IIS 6 Compatibility

Use the following steps to enable HTTP compression on IIS 7 with IIS 6 compatibility.

By default, only static compression is enabled in IIS 7. Enabling dynamic compression will provide significantly smaller files over the network. In addition, there are a number of configuration elements that may be modified to provide more benefits. You may need to try different settings to achieve optimum results.

The following information can be used as a guide to implement compression in your Sage

SalesLogix implementation. To help evaluate and test your specific compression settings, you may want to use a third-party HTTP compression debugging tool.

To enable

1. Open IIS Manager, and select your Sage SalesLogix Web site.

2. Under IIS, double-click Compression.

3. Select the Enable dynamic content compression check box.

If necessary, enable the dynamic content compression module in Server Manager (Roles) to enable the check box.

4. In the Actions pane, click Apply.

5. If necessary, modify the ApplicationHost.config file using the following example. This file is stored in %SystemRoot%\System32\inetsrv\config\ApplicationHost.config.

In IIS 7 the configuration file replaces the Metabase Explorer compression values used in

IIS 6. For more information, see the Microsoft IIS Web site at http://www.iis.net/ConfigReference.

• Example Configuration Settings:

Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

</staticTypes>

</dynamicTypes>

</httpCompression>

Configuring ASP.NET

Microsoft .NET Framework with ASP.NET enabled is required on the Web server and the required version is installed as a prerequisite to your Sage SalesLogix installation. The

Application Architect automatically configures the necessary portal settings, so no manual configuration steps are necessary.

Configuring Application Pool Permissions

You must configure the Application Pool Permissions for your Web Site. The default Web site is SalesLogix, unless you change it during the Web Host installation.

The recommended Identity for the Application Pool is configured for the WebDLL user. The

WebDLL user is typically associated to the Sage SalesLogix admin user to run the process orchestration and SData service portals. This association is set up in the Sage SalesLogix

Administrator.

See one of the following sections as appropriate for your server version.

To configure on Windows 2003 Server

1. Open Internet Information Services (IIS) Manager.

2. Expand the local computer, and then expand Application Pools.

3. Right-click SalesLogix (or the name of your SalesLogix Web Site), and then click

Properties.

The properties dialog box for your SalesLogix Web site application pool appears.

4. On the Identity tab, select the Configurable option.

5. In the User name box, type the WebDLL user name.

6. In the Password box, type the password for the WebDLL user.

7. Click Apply, and then click OK.

8. Restart the machine to apply the local security policies.

To configure on Windows 2008 Server

1. Open Internet Information Services (IIS) Manager.

2. Expand the local computer, and then click Application Pools.

3. Right-click SalesLogix (or the name of your SalesLogix Web site), and then click

Advanced Settings.

4. Under Process Model, select Identity, and then click the ellipsis button.

The Application Pool Identity dialog box opens.

58 Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

5. Select Custom account, and then click Set.

The Set Credentials dialog box opens.

6. In the User name box, type the Domain\WebDLL user name.

Ensure you include Domain\ in the user name.

7. In the Password and Confirm password boxes, type the WebDLL user’s password.

8. Click OK, and then click OK again.

Configuring Permissions for Desktop Integration

You must set permissions for the Sage SalesLogix Web site Libraries folder to enable Web

Client users to download the Desktop Integration Module installation.

To set permissions on IIS 6

1. On the Web Host, open IIS Manager.

2. Expand your server, expand Web Sites, expand your Sage SalesLogix Web site, and then expand the SlxClient folder.

3. Right-click the Libraries folder, and then click Properties.

4. Click the Directory tab.

5. In the Execute permissions drop-down list, select Scripts only.

6. Click OK.

To set permissions on IIS 7

No manual steps are required as the configuration is automatically set by the deployment.

Defining the Default Document

Default documents can be a directory’s home page or an index page containing a site document directory listing. You must be a member of the Administrators group on the local computer to define a default document.

To define

1. In IIS, expand the Web Sites directory, and then expand the Web site where you deployed the Web Client or (if available) Lead Capture portal.

2. Right-click the appropriate virtual directory, and then click Properties.

For example, the virtual directory for the Web Client is SlxClient.

3. Click the Documents tab.

4. Ensure the Enable default content page check box is selected.

5. Click Add to add a new document to the list.

The Add Content Document dialog box appears.

6. In the Default Content page: box, type the page name, and then click OK.

For example, the default content page for the Web Client is Default.aspx.

7. Click Move Up to move the document to the top of the list.

8. Click Apply, and then click OK.

Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

Installing Web Reporting

Web Reporting enables Web Client users to access, run, and filter the same reports as Sage

SalesLogix Network Client users. It is integrated with Crystal Reports. The Web Reporting installation installs the Web Reporting libraries to enable users to access Crystal Reports through the Web Client, performs most of the configuration necessary for the SLX Web

Reporting site, and finds an open port for the site.

Sage SalesLogix uses Crystal Reports Server. Crystal Reports must be installed on the Web

Reporting Server before you install and configure the Web Reporting components. If the Web

Reporting installation does not detect the correct version of Crystal Reports, you will be prompted to install or upgrade it.

Ensure you have granted the WebDLL user ASP.NET access as detailed in “The

WebDLL User” on page 15

before installing Crystal Reports Server.

To install

1. On the Sage SalesLogix Installation screen, click Standard Server Installation.

2. On the Standard Server Installation screen, click Web Reporting Server.

If the installation does not detect the necessary prerequisites, you will be prompted to install them. Click Install to allow Sage to install the required components or

Cancel to stop the installation.

3. On the Welcome and License Agreement screens, read the information, accept the agreement, and then click Next.

4. You will be prompted to enter some or all of the following information on the installation screens:

• Create Web Site – Select this check box if you want the installation to automatically create a Web Site.

If you prefer to perform configuration manually, clear the Create Web Site check box

and follow the instructions in Appendix F, “Advanced Web Reporting Configuration”

• Enter a Web site name – Enter the name of the Web Reporting site in IIS. The default value is SLX Web Reporting.

• Enter a Web Site Port – Enter the port that the Web site will use. Note the port number for future reference. You must use port number 1025 or greater.

• Enter a virtual directory name – Enter the name of the virtual directory that will be set up for Web Reporting. The default virtual directory name is slxwebrpt.

• Domain – Enter the network domain where you created the WebDLL user as described in

“The WebDLL User” on page 15 .

• User Account – Enter the name of the WebDLL user you created. The default value is WebDLL. If you used a different name, type it exactly as you did when you created it.

• Password and Confirm Password – Type the WebDLL user’s password.

• SalesLogix Server – Select or enter the machine name where the Sage SalesLogix

Web Server resides.

• SalesLogix Database Alias – Select or enter the name of the connection to the

Sage SalesLogix database.

• Search for servers on port - Enter a port. By default, this is set to port 1706.

• User Name – Enter a Sage SalesLogix Server user name (such as Admin).

60 Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

• Password – Enter the Sage SalesLogix Server password for the SalesLogix user.

5. After you have completed the information on the SalesLogix Database Connection screen, click Next.

6. On the remaining screens, click Install and Finish to complete the installation.

Deploying the Web Reporting Portal

Web Reporting is enabled by deploying the Web Reporting portal using the Deployment

Explorer. The Web Reporting portal contains the Web Reporting application files and is deployed as a dependency of the SlxClient portal.

If you are running Web Reporting at your main office and any Web Remote Offices, you must

deploy the Web Reporting portal to both locations. Refer to “Deploying a Sage SalesLogix Web

Portal” on page 51 for build and deploy instructions.

Mapping the Web Reporting Server to the Directory

After building and deploying the Web Reporting portal, you must configure parameters and map to folders.

To configure

1. On the Web Reporting Server, stop the Report Application Service (RAS).

2. From the Start menu, click Business Objects, and then click Central Configuration

Manager.

3. Right-click Report Application Server, click Properties, and then select the

Parameters tab.

Sage SalesLogix Implementation Guide v8.0

Installing the Web Components

4. Change Option Type: from Database to Server.

5. Change the Report Directory to C:\inetpub\wwwroot\slxwebrpt\run

This is the folder created in step 5 under “The WebDLL User” on page 15 .

6. Change the Temp Directory to C:\CrystalTemp.

7. Click OK.

8. Restart the RAS service.

9. Right click the Report Application Server and select Start.

10. Close the dialog box.

After completing this chapter...

You have completed tasks 1-14 in the “Web Tasks”

checklist. Proceed with Chapter 6,

“Configuring Sage SalesLogix Users” .

62 Sage SalesLogix Implementation Guide v8.0

Chapter 6 Configuring Sage SalesLogix Users

Before beginning this chapter...

Add licenses and configure the system as described in

Chapter 4, “Configuring the Sage

SalesLogix System”

Use the instructions in this chapter to...

Create and configure Sage SalesLogix users. These tasks are required for all Sage

SalesLogix installations.

When creating Sage SalesLogix users, you must add new users and modify the user profile.

Planning for Sage SalesLogix Users

Before adding new users, you can create departments, administrative roles, and security profiles that can be assigned to individual users. Administrative roles and security profiles help define what information is available to the user and what tasks they can perform.

For detailed steps to create departments, administrative roles, and security profiles, see the following topics in the Administrator help.

• Managing Administrative Roles

• Creating a Department

• Security Profile Manager

The Web Client also contains administrative features that allow users with the appropriate security access to manage competitors, departments, lead sources, literature items, pick lists, products, packages, users, teams, and Web security (roles).

For more information on the administrative features available in the Web Client, see the following Web Client help topics:

• Adding a User

• Working with Teams

• What are Roles and Secured Actions?

Understanding the Admin User

Sage SalesLogix contains an Administrator user type which is the default user profile created for the system administrator. The system administrator has full access to all features and functions in the system when logging on as admin.

The Administrator user profile cannot be modified in Administrator with the same access as other Sage SalesLogix users (Network, Remote, and so on). Access on the General tab is restricted except for the E-mail and Use Windows Authentication boxes and the Change

Password button. The following tabs are not visible and cannot be edited:

• Service / Support

Sage SalesLogix Implementation Guide v8.0

Configuring Sage SalesLogix Users

• Teams

• Sync

Admin user access is restricted to ensure the system administrator is not included in your company’s security model.

Creating Users

Before creating users, determine the best method of configuring the user’s profile for your company’s size and structure.

If you plan to add several users with identical profiles (for example, the same department, division, manager, security settings, and so on), Sage SalesLogix recommends you use a user template. Templates are recommended because they significantly reduce administration time.

When creating users, you can apply a Sage SalesLogix user template, or a custom template you create, which applies the appropriate settings to each user. User templates do not consume a license and cannot log on to Sage SalesLogix.

The following options are available for adding users. See the appropriate topic in the

Administrator Help to add users to your implementation.

Creation Method

Add new users based on an existing user template

Create Sage SalesLogix users based on existing Windows’ users

Import users from a commadelimited text file

Create users individually

Description

You can add new users based on an existing user template or a custom user template you create.

Administrator Help Topic

Creating a User Template

If you want your existing Windows’ users to also be Sage SalesLogix users, you can import your Windows’ user information to

Sage SalesLogix. During this process, you can select an existing user template to configure user profile settings.

Importing Windows

Users/Matching Sage SalesLogix

Users to Windows Users

If your company maintains user information in another application, you can export the information and import it to Sage SalesLogix to add users. During this process, a user template can be applied to configure user settings not found in the import file.

If you have a small number of users, or each user requires a distinct profile with settings that differ substantially, you can add users individually and configure each profile as appropriate.

Importing Users from a CSV File

Adding a User

Configuring Users

If you create a user from a template, from an existing Windows’ user, or import the user information from another application, you must complete additional configuration steps before the user can log on.

If your installation includes Remote users, additional options are configured in

Chapter 12,

“Configuring the Sage SalesLogix Remote Client”

. Remote user options cannot be configured until you complete various synchronization configuration steps.

64 Sage SalesLogix Implementation Guide v8.0

Configuring Sage SalesLogix Users

To configure

1. On the Administrator Navigation Bar, click Users.

2. In the Users view, double-click a user to open the profile.

3. If necessary, select the Use Windows Authentication check box. In the Windows ID box, select the name the user enters to log on to Windows.

With Windows Authentication, users are automatically logged on without entering their

Sage SalesLogix user names or passwords.

4. In the Username box, type the name the user will use when logging on to Sage

SalesLogix.

The user name is required and cannot contain spaces or an apostrophe. For Remote users, the user name must also follow the Rules for Regular Identifiers specific to the version of

Microsoft SQL Server that you are using to create Remote databases. The Remote user name must follow these rules as it is sent to the Microsoft SQL Server or Microsoft SQL

Express instance to be used as part of a Remote database name.

5. In the Name box, enter the user’s name.

If you selected the Update SalesLogix user information with Windows information check box on the Import Windows Users dialog box, the Username and Name boxes are pre-filled with Windows information. This information does not need to be changed.

6. In the E-Mail box, enter the user’s e-mail address.

7. Select the User is a Manager check box if the user is a manager whose name should appear in the Manager list.

8. In the User Type box, select the user type.

9. Click the Employee tab.

10. If necessary, in the Accounting ID field, type the user's accounting identification code.

(This is the ID used by the accounting software.)

11. Click the Teams tab.

The Teams tab allows you to create user teams and add or remove the user from system teams. User teams allow users to access accounts owned by another user. For example, if you want Lee to have access to all Dan’s accounts, you can add Lee to Dan’s user team.

System teams group users together so that all team members have access to the same accounts.

12. In the User Team section, click Add to add other users to this user’s team.

Users you add to this user’s profile can access all accounts owned by the main user (the user whose profile you are editing).

13. In the Field Security of selected user box, select a security profile for the user selected in the User Team section. This profile only applies when accessing accounts owned by the main user (the user whose profile you are editing).

Field security never applies to accounts owned by an individual when that individual is the user accessing the accounts.

14. Click the Calendar tab.

The Calendar tab sets permission rights for users to view and modify other user’s calendars.

15. In the Other Calendars section, click Add Users to set access for this user to add, edit, delete, or sync activities for another user.

16. In the This User’s Calendar section, click Add Users to set access for other users to add, edit, delete, or sync activities to this user’s calendar.

17. Click OK.

Sage SalesLogix Implementation Guide v8.0

Configuring Sage SalesLogix Users

Setting Access to Customer Service Management

If necessary, you can give users access to management functions in the Sage SalesLogix

Client. If you are using customer service, you may want to allow users to manage options for ticket entry, time tracking, setting auto-assignment, managing area, category, and issue lists, user defaults, and ticket rates.

The following steps detail the options that can be set for customer service management. For details on other functions, see the “User Profile Function Security Tab” topic in the

Administrator Help.

To set function security options

1. On the Administrator Navigation Bar, click Users.

2. In the Users view, double-click the user that you want to give access to customer service management options.

3. Click the Function Security tab, expand the Tools menu, and then expand the Manage menu.

4. Double-click the appropriate options to give access to this user:

• Customer Service Defaults - Allows the user to access the Manage Customer

Service Defaults dialog box which contains options for ticket entry and time tracking.

• AreaCategoryIssue - Allows the user to manage the Area, Category, and Issue lists. Area, Category, and Issue lists are used to classify tickets and defects.

• Customer Service Options - Allows the user to access the Manage Customer

Service Options dialog box, which contains options for setting auto-assignment, User

Defaults, and Ticket Rate options.

5. Click OK.

After completing this chapter...

You have completed tasks 15-16 in the

“Required Tasks” checklist. Proceed to Part II:

“Installing Sage SalesLogix Clients” .

66 Sage SalesLogix Implementation Guide v8.0

Part II

Installing Sage SalesLogix Clients

Chapter 7 Installing Network Clients

Before beginning this chapter...

Create and configure users as described in Chapter 6, “Configuring Sage SalesLogix Users”

Use the instructions in this chapter to...

Install the Sage SalesLogix Client for Network users. These tasks are required for all

Sage SalesLogix Network installations.

You can install the Sage SalesLogix Client using one of two methods.

Automated installation Automated installations create an executable file that allows the

Sage SalesLogix Client to be installed with no user intervention.

Automated installations also reduce administration time when you upgrade to a new version and then add new users to Sage SalesLogix. During the upgrade process, you can update the

Client installation (Network and\or Remote) directly by performing the “Build Sage SalesLogix

Network Client Install” or “Build Sage SalesLogix Remote Client Install” and install the new image files over the previously-installed files. For new installations, the shortcut stored in the

Image folder can be distributed to each machine. For upgrades, users can click on the existing shortcut on their desktops.

Store these files on a network share that is accessible by all client machines.

Standard Sage SalesLogix Client installation The Sage SalesLogix Client can be installed on each user’s computer using the Client installation. The standard installation includes

Typical and Custom options which allow you to install all components or choose the components necessary for your implementation.

Creating Automated Client Installations

You can create automated installations of the Sage SalesLogix Network and Sage SalesLogix

Remote Clients.

If you want to customize the standard configuration file or create your own configuration file, see

Appendix G, “Automating Client Installations” for instructions.

Before creating automated installations, ensure you have access to a shared network folder in which you want to create the installs.

To create

1. On the Sage SalesLogix Installation screen, click Sage SalesLogix Client

Installations.

2. On the Sage SalesLogix Client Installation screen, click Build Sage SalesLogix

Network Client Install or Build Sage SalesLogix Remote Client Install.

3. On the Welcome screen, click Next.

4. On the Administrative Install Options screen, enter the information as appropriate for your installation type, and then click Next.

Sage SalesLogix Implementation Guide v8.0

Installing Network Clients

• Click Modify default feature set to change any of the features included in the install.

• Select or clear the Pre-configure SalesLogix Server connection check box.

Selecting this option allows you to configure the port for all installations, as well as the server and database alias for Network Client installations.

• In the SalesLogix Server box, select or type the name of the computer on which you installed the Sage SalesLogix Server.

This setting is not available if you are creating a Sage SalesLogix Remote Client installation.

• In the SalesLogix Database Alias box, select or type the name of the database connection.

This setting is not available if you are creating a Sage SalesLogix Remote Client installation.

• If necessary, in the Port box, change the port number used for communication between the client and the Sage SalesLogix Server.

In most implementations, the default port number does not need to be changed.

However, if you have another application or service using port 1706, you should change the port number to an unused port.

5. In the Network Location box, type or browse to the location where the automated installation should be created. This location must be a shared network path.

If you move the automated installation from this location at a later time, ensure you do the following:

• Modify the shortcut created on the desktop to reference the new installation location.

Redistribute the shortcut as necessary.

• Modify the UNC paths within the configuration file to reference the new installation location.

6. On the remaining screens, click Install and Finish to complete the installation.

The automated installation is created in the specified shared network location and a shortcut to the installation is created on the desktop.

7. Distribute the shortcut or installation to users.

Installing the Sage SalesLogix Network Client

If your company uses Outlook Integration, ensure you have completed the required steps under

“Outlook Integration Requirements” on page 24

before you install the Sage

SalesLogix Network Client.

Network Clients are the computers running Sage SalesLogix that access the main database through a direct connection or wide-area network. Depending on your installation type, see the following instructions:

• If you created an automated installation, see

“Performing an Automated Installation”

•

If you plan to use the standard installation, see “Performing a Manual Installation”

70 Sage SalesLogix Implementation Guide v8.0

Installing Network Clients

Performing an Automated Installation

Installing the Sage SalesLogix Client using an automated installation configures the Client computer with the settings selected when the installation was built.

When installing Sage SalesLogix using an automated installation, third-party

(prerequisite) applications are not installed. Third-party applications must be installed separately. Installations for these applications can be found in the Redist folder on the

Sage SalesLogix media.

To run an automated installation, instruct the user to double-click the client installation shortcut or custom SalesLogix Network Client.msi file. Shortcuts are typically distributed via e-mail and open the installation from a shared network drive.

After installation, you must start the Sage SalesLogix Client. See

“Starting the Sage SalesLogix

Client” on page 71

for details.

Performing a Manual Installation

Run a manual installation if you do not want to install some components.

To run

1. On the Sage SalesLogix Installation screen, click Sage SalesLogix Client

Installations.

2. On the Sage SalesLogix Client Installation screen, click Install Sage SalesLogix

Network Client.

3. On the Welcome and License Agreement screens, read the information and accept the agreement, and then click Next.

4. On the Setup Type screen, select an installation type, and then click Next.

• Click Complete to install the most common components.

• Click Custom to install only certain components or to change the installation location. Use the Custom Setup screen to enable or disable items for installation.

5. On the remaining screens, click Install and Finish to complete the installation.

If your company is not using Intellisync for SalesLogix to share information between Sage

SalesLogix and Outlook, clear the Install Intellisync for Sage SalesLogix check box.

After installation, you must start the Sage SalesLogix Client.

Starting the Sage SalesLogix Client

Before starting the Sage SalesLogix Client on Oracle, you may need to create a Client

database connection on each Client computer. See “Creating Client Database Connections for

Oracle” on page 36

for instructions.

After installation, the user who installed Sage SalesLogix must log on to the Client computer(s) for the first time and launch each of the following applications. This process creates the necessary registry entries for each application.

• If the standard user has installation rights, he or she can log on and begin using the Sage

SalesLogix Client.

Sage SalesLogix Implementation Guide v8.0

Installing Network Clients

• If the standard user does not have rights to install Sage SalesLogix, an admin user must start the Client application. This is because the Sage SalesLogix Client must write to restricted areas of the registry. After an admin user has logged on and run the Client, a standard user can read from the registry’s restricted area.

The Sage SalesLogix installation creates connection information in the Current User area of the registry. Therefore, if the user logging on to the Client is not the user who installed the Client, a new database connection must be created.

Creating Area, Category, and Issue Lists

Before users begin working with tickets and defects, you must create custom lists for the

Area, Category, and Issue fields. The Area, Category, and Issue lists contain information specific to your company that is used to describe the problem or issue documented by a ticket or defect.

The Area, Category, and Issue lists are linked in a hierarchy. The Area you select determines the options available for the Category, and the Category you select determines the options available for the Issue.

The Area, Category, and Issue lists are used to reduce administration time when users are creating tickets and defects. If you are not using the customer service or support features, you do not need to create the Area, Category, and Issue lists.

To create

1. On the Sage SalesLogix Client Tools menu, point to Manage, click Customer Service

Options, and then click the Area/Category/Issue tab.

2. Click Add.

3. In the Area box, type a short description (limited to 64 characters) for an area value that is applicable to your company's business. For example, you could type "Software".

The Area provides a high-level description of the customer’s problem (on a ticket) or the type of defect.

4. In the Category box, do one of the following:

• Select a category that is appropriate for the area.

• Type a short description (limited to 64 characters) for a category that is appropriate

for the area. For example, in Step 3 you created the Area of Software, so the

Category might be the name of the software manufacturer.

The Category value provides more detailed information about the cause of the customer's problem and is grouped with a specific Area value.

5. In the Issue box, do one of the following:

• Select an issue value that is appropriate for the category.

• Type a short description (limited to 64 characters) for an issue.

The Issue value provides even more detailed information about the customer's problem and is grouped with a specific Category value.

6. Select the Ticket check box if you want the items to be available in the Sage SalesLogix

Client and Web Client Ticket views.

7. Select the Defect check box if you want the items to be available in the Defect view.

8. Select the Customer Portal check box if you want the items to be available in the

Customer Portal Ticket view.

9. Click OK.

10. If necessary, select the Issue text must match a list item check box on the

Area/Category/Issue dialog box.

72 Sage SalesLogix Implementation Guide v8.0

Installing Network Clients

When this option is selected, the user must type or select an Issue that already exists.

When cleared, a user can type a new value in the Issue box in the Sage SalesLogix Client and Web Customer Portal.

11. Repeat steps 2-10 as necessary to create all area, category, and issue values for your

company.

12. Click OK.

Creating the SyncSalesLogix Group

If your implementation includes Standard Outlook Integration or Intellisync for SalesLogix, you must create the SyncSalesLogix ad hoc group. Contacts in this group synchronize between Sage SalesLogix and Outlook.

Additional Intellisync for SalesLogix configuration steps are detailed in

Appendix B,

“Configuring Intellisync for SalesLogix”

To create

1. Open the Sage SalesLogix Client.

2. Open the Contacts List view.

3. Select the contacts you want to synchronize with Microsoft Outlook.

4. Right-click the selected contacts, and then click Add Selected Members to New

Group.

5. In the Query Builder Name box, type SyncSalesLogix.

6. In the Display Name box, type SyncSalesLogix.

7. Click OK.

8. Click Close.

Assigning the SyncSalesLogix Group

After creating the SyncSalesLogix group, you must specify that group to be used to transfer information between Microsoft Outlook and Sage SalesLogix.

To assign

1. On the Sage SalesLogix Tools menu, click Options.

2. Click the Lookups and Groups tab.

3. In the Sync Configuration section, click New.

4. In the Contact Sync Group dialog box, click Choose Group.

5. Select SyncSalesLogix, and then click OK.

6. Click OK.

After completing this chapter...

You have completed tasks 17-22 in the “Required Tasks”

checklist.

If your implementation includes the Web Client, proceed with Chapter 8, “Configuring the Web

Client”

If your implementation does not include the Web Client but does include remotes, proceed with

Chapter 11, “Configuring Synchronization”

Sage SalesLogix Implementation Guide v8.0

Installing Network Clients

74 Sage SalesLogix Implementation Guide v8.0

Chapter 8 Configuring the Web Client

Before beginning this chapter...

Install and configure the Web Host and Web Reporting as described in Chapter 5, “Installing the Web Components” . In addition, restart all servers involved in the implementation.

Use the instructions in this chapter to...

Configure the Sage SalesLogix Web Client. These tasks are required for all Sage

SalesLogix Web installations.

The Sage SalesLogix Web Client is highly customizable using the Application Architect. You can rapidly build, customize, manage, and deploy coded and codeless Web application solutions. After building and deploying the Web Client, you must configure various settings on the Host and Client computers.

For more information, refer to the “Common Tasks in Application Architect” topic in the Application Architect help.

Configuring Windows Authentication

Windows Authentication allows Web users to automatically log on to the Web Client using their Microsoft Windows logon credentials. This method uses a cryptographic exchange with the user's Web browser to confirm the identity of the user.

When Windows Authentication is enabled:

• Users do not see a Sage SalesLogix Web Client log on page.

• To enable users to log on as the administrator, you must configure a second Web Client implementation that does not include Windows Authentication.

Ensure the Use Windows Authentication check box is selected on the User Profile

General tab for each Web Client user. For more information see “Configuring Users” on page 64 .

To configure Windows Authentication you must:

• Configure the WebDLL user

• Configure your Web Server

• Configure your Web Client computers

The following instructions configure Windows Authentication for Web Client users to prevent logging on manually if the Windows user is not mapped to a user in Sage

SalesLogix. This method is referred to as “Forms”. It attempts to log the user on automatically but displays an error message if the user information is not found. For additional configuration scenarios, see the “Enabling Windows Authentication Access for Web Client Users” topic in the Administrator Help.

Sage SalesLogix Implementation Guide v8.0

Configuring the Web Client

Configuring the WebDLL User for Windows Authentication

You must configure the WebDLL user for Windows Authentication to allow the Sage

SalesLogix Web Client to open a connection to the Sage SalesLogix database. If you have not

already completed this task, see the steps in Chapter 5, “Installing the Web Components”

Configuring the Web Server

Use one of the following sections to configure Windows Authentication on your Web Server.

•

“Windows 2003”

in the following section.

•

“Windows 2008” on page 78 .

Windows 2003

The following instructions configure Windows Authentication for Web Client users on Windows

2003.

Windows Authentication requires the setspn.exe. For download information, go to www.microsoft.com and search on Windows 2003 Support Tools.

To configure

1. On the Web Server computer, log on as a domain administrator or as a user with rights to modify the Active Directory.

This user should be the Application Pool user.

2. Add permissions for Web Client users or groups.

a. In IIS, right-click the Application Pools folder, and then click Properties. b. Click the Identity tab.

c. Verify that the user indicated in the User name: box is the user logged in as the domain administrator or user with rights to modify the Active Directory.

3. Run setspn.exe to manually modify the service account's SPN information to run correctly with Windows Authentication.

Service Principal Names (SPNs) are used to locate a target principal name for running a service. The setspn.exe is included in the Windows 2003 Support Tools.

a. Open a Command Prompt window.

Do not use a colon or second forward slash in the following setspn commands.

Type the commands exactly as documented.

b. At the command prompt, type the following command. setspn -A http/server.domain.com domain\username

The server.domain.com is the fully qualified machine name, the domain is the Sage

SalesLogix domain, and the user name is the user that has rights to modify the active directory (this is the user specified in the application pool). Use the username created

in “Configuring Application Pool Permissions” on page 58 .

c. At the command prompt, type the following command. setspn -A http/server domain\username

The server is the machine name, the domain is the Sage SalesLogix domain, and the user name is the user that has rights to modify the active directory. Use the username

created in “Configuring Application Pool Permissions” on page 58

d. At the command prompt, type the following command. setspn -L username

This step checks to ensure the SPN entries created in steps b and c have been registered correctly. If you do not see the two entries, repeat steps b and c.

76 Sage SalesLogix Implementation Guide v8.0

Configuring the Web Client

4. On the Web Server computer, add IIS permissions for Web Client users or groups. a. Open Internet Information Services (IIS) Manager.

b. Expand the Web Server computer name, expand Web Sites, and then expand the name of the Web site where you deployed the Sage SalesLogix Web Client portal.

c. Right-click SlxClient, and then click Permissions.

d. On the Security tab, click Add.

e. In the Select Users or Groups dialog box, add your Web Client domain users, and then click OK.

5. On the Web Server computer, enable Windows Authentication for the Web Client using the following method to restrict Web Client users from logging on if the Windows user is not mapped to a Sage SalesLogix.

a. Open Internet Information Services (IIS) Manager.

b. Expand the Web Server computer name, expand Web Sites, and then expand the name of the Sage SalesLogix Web Client Web site.

c. Right-click SlxClient, and then click Properties.

d. In the Properties dialog box, click the Directory Security tab.

e. In the Authentication and access control section, click Edit.

Ensure the Enable anonymous access check box is selected.

g. Ensure the Integrated Windows authentication check box is selected.

h. Click OK.

Modify the Web.config file.

In Application Architect, make the following edits in the web.config file in the Sage

SalesLogix portal. For more information about editing the web.config file see the

"Editing Configuration Files" topic in the Application Architect Help.

ii. Modify the web.config file by commenting out the sections labeled Windows

Authentication – off and removing the comment markup from the sections labeled Windows Authentication – on.

The three sections that must be modified are the <authentication>,

<httpModules>, and <modules>.

Comment markup begins with "" j .

(Optional) Remove the Sage SalesLogix Log on screen.

When a user logs off from Sage SalesLogix, a log on button displays that allows the user to log back on. To remove this button, you must edit the Logoff.aspx file.

Change the line:

<div id=”LogoffFormButtonPanel”><a href=”~/Login.aspx” id=”loginLink” runat=”server”><%= GetLocalResourceObject(“ReturnToLoginMessage”)

%></a></div>

<div id=”LogoffFormButtonPanel”><a href=”~/Default.aspx” id=”loginLink” runat=”server”><%= GetLocalResourceObject(“ReturnToLoginMessage”)

%></a></div>

6. Enable Integrated Authentication for SData Portal Configuration a. Open Internet Information Services (IIS) Manager.

b. Expand the Web Server computer name, expand Web Sites, and then expand the name of the Sage SalesLogix Web Client Web site.

c. Right-click your SData virtual directory, and then click Properties.

d. In the Properties dialog box, click the Directory Security tab.

e. In the Authentication and access control section, click Edit.

Clear the Enable anonymous access check box.

g. Select the Integrated Windows authentication check box.

Sage SalesLogix Implementation Guide v8.0

Configuring the Web Client h. Click OK.

Under the SData folder, open and modify the Web.config file.

Windows 2008

The following instructions configure Windows Authentication for Web Client users on Windows

2008.

To configure

1. On the Web Server computer, log on as a domain administrator or as a user with rights to modify the Active Directory.

This user should be the Application Pool user.

2. Add the WebDLL user to the IIS_IUSRS group.

3. Make sure all Sage SalesLogix Web Client users who will be using Windows

Authentication have the following permissions to the SLXClient and SData folders:

• Read

• Write

• Execute

4. Add Windows Authentication security.

a. In the Server Manager, under Web Server (IIS), click Add Role Services.

b. In the tree view under Security, select Windows Authentication.

c. Click Install.

5. Run setspn.exe to manually modify the service account's SPN information to run correctly with Windows Authentication.

Service Principal Names (SPNs) are used to locate a target principal name for running a service. The setspn.exe is included in Windows 2008.

a. Open a Command Prompt window.

Do not use a colon or second forward slash in the following setspn commands.

Type the commands exactly as documented.

b. At the command prompt, type the following command. setspn -A http/server.domain.com domain\username

The server.domain.com is the fully qualified machine name, the domain is the Sage

SalesLogix domain, and the user name is the user that has rights to modify the active

directory. Use the username created in “Configuring Application Pool Permissions” on page 58

c. At the command prompt, type the following command. setspn -A http/server domain\username

The server is the machine name, the domain is the Sage SalesLogix domain, and the user name is the user that has rights to modify the active directory. Use the username

created in “Configuring Application Pool Permissions” on page 58

d. At the command prompt, type the following command. setspn -L username

This step checks to ensure the SPN entries created in steps b and c have been registered correctly. If you do not see the two entries, repeat steps b and c.

6. On the Web Server computer, enable Windows Authentication in IIS. This method restricts Web Client user from logging on if the user is not found in Sage SalesLogix.

a. Open IIS Manager, and click Advanced Settings.

b. In the Advanced Settings dialog box, click the Physical Path Credentials ellipsis.

c. In the Connect As dialog box, select Application user (pass-through

authentication), and then click OK twice.

78 Sage SalesLogix Implementation Guide v8.0

Configuring the Web Client d. Double-click Authentication and verify that only Windows Authentication is enabled.

By default, Sage SalesLogix uses Basic Authentication.

e. Right-click Windows Authentication, and then click Edit.

Click Advanced settings.

g. Ensure that the Enable Kernel-mode authentication check box is not selected.

h. Click OK. i.

Modify the Web.config file.

In Application Architect, make the following edits in the web.config file in the Sage

SalesLogix portal. For more information about editing the web.config file see the

"Editing Configuration Files" topic in the Application Architect Help.

ii. Modify the web.config file by commenting out the sections labeled Windows

Authentication – off and removing the comment markup from the sections labeled Windows Authentication – on.

The three sections that must be modified are the <authentication>,

<httpModules>, and <modules>.

Comment markup begins with "" j .

(Optional) Remove the Sage SalesLogix Log on screen.

When a user logs off from Sage SalesLogix, a log on button displays that allows the user to log back on. To remove this button, you must edit the Logoff.aspx file.

Change the line:

<div id=”LogoffFormButtonPanel”><a href=”~/Login.aspx” id=”loginLink” runat=”server”><%= GetLocalResourceObject(“ReturnToLoginMessage”)

%></a></div>

<div id=”LogoffFormButtonPanel”><a href=”~/Default.aspx” id=”loginLink” runat=”server”><%= GetLocalResourceObject(“ReturnToLoginMessage”)

%></a></div>

7. Enable Windows Authentication for the SData Portal.

d. Open Internet Information Services (IIS) Manager.

e. Select the SData virtual directory, and click Advanced Settings.

In the Advanced Settings dialog box, click the Physical Path Credentials ellipsis button.

g. In the Connect As dialog box, select Application user (pass-through

authentication), and then click OK.

h. Click OK to close the Advanced Settings dialog box.

Double-click Authentication and set the following:

• Disable anonymous access.

• Enable Windows Authentication.

• Enable Basic Authentication

By default, Sage SalesLogix uses Basic Authentication.

Right-click Windows Authentication, and then click Advanced Settings.

k. In the Advanced Settings dialog box, verify that Enable Kernel-mode

authentication is not selected, and then click OK.

Under the SData folder, open and modify the Web.config file.

Sage SalesLogix Implementation Guide v8.0

Configuring the Web Client

Configure the Web Client Machines

The following instructions configure Windows Authentication for Web Client users accessing

Sage SalesLogix. Use one of the following procedures as appropriate for your browser type.

To enable on Internet Explorer

1. On each Web Client computer, open your browser.

2. On the Tools menu, click Internet Options.

3. Click the Security tab, select Trusted Sites, and then click Sites.

4. In the Add this Web site to the zone: text box, enter either the Web Server name or the IP address to the Web Server (http://10.40.0.35).

For users using Windows Authentication, the URL address must include the windows.aspx page (http://10.40.0.35/slxclient/windows.aspx).

To enable on Firefox

1. On each Web Client computer, open your browser.

2. In the Location Bar, type about:config, and then press Enter.

3. If a warranty message opens, click I’ll be careful, I promise!.

4. Double-click the network.automatic-ntlm-auth.trusted-uris preference.

5. In the Enter string value box, type your Web Host URL using the format http://hostserver:port.

6. Click OK.

Configuring Roles

A role determines what functionality a user can access in the Web Client. Roles use secured actions to control access to user interface elements such as pages, menus, menu items, toolbars, and buttons. When you control access to individual user interface elements, you can control access to actions such as editing, deleting, or printing.

By default, users created in the Web Client are assigned the Standard User role. This role allows add, edit, and delete permissions to Web Client non-administrative entities such as accounts, contacts, and opportunities.

Users created in the Administrator are not assigned a role and role security cannot be set in the Administrator. If you create new Web Client users in the Administrator, you must assign users to the Standard User role.

To assign

1. Open the Users List view in the Web Client.

2. Select the users that should have add, edit, and delete permissions to non-administrative entities in the Web Client.

3. In the User Tasks pane, click Add to Role.

4. In the Select Role dialog box, lookup and select the Standard User role, and click OK.

5. Click OK.

Review the “What are Roles and Secured Actions?” topic in the Web Client help to understand the default roles and how you want to apply them to users.

80 Sage SalesLogix Implementation Guide v8.0

Configuring the Web Client

Testing the Web Site

After you have deployed a Web portal and defined the default document, you are ready to test the Web site.

To test

1. Ensure the following services are running on the Web Host: Indexing Service, IIS Admin

Service, and World Wide Web Publishing Service.

2. Reset IIS.

3. Depending on where you deployed the Web Client portal, use one of the following URLs to test the Web site. If you deployed the Sage SalesLogix Web Client portal to:

• localhost (your Web server), the format is http://localhost/SlxClient or

http://server/SlxClient.

• localhost (your Web server) with Windows Authentication enabled, the format is

http://server:port/SlxClient/Windows.aspx.

• a Web site and port you designated during Web Host installation, or to another Web site you created manually in IIS, the format is http://server:port/SlxClient.

The server is the Web Host server and port is the port number you designated during

Web Host installation.

4. When the Sage SalesLogix Web Client logon page appears, enter your User Name and

Password.

5. (Optional) Sage SalesLogix Web components provide optional extended features in the

Web Client that may require additional components to be downloaded.

• On the login screen, click Enhance SalesLogix.

• In Options, click the General/Search tab and click Enhance SalesLogix.

• If prompted to install Sage SalesLogix Desktop Integration and you want to use this feature, click Yes.

6. Click Log On.

7. If you configured Web Reporting, on the Navigation Bar, click Reports.

8. Ensure the Reports View appears and that you can run a report.

9. Log off the Sage SalesLogix Web Client.

10. Send the Web Client URL to users or create a link from your company’s Web site (detailed in the following section).

Linking from Your Company’s Web Site

When you are ready to make the Web Client accessible to users, you can create a link on your company’s Web site (typically an intranet site) to provide access. For example, you may want to display a link that reads “SalesLogix” in a prominent location on your intranet site.

Create the link in the following format:

<A HREF=”webservername/virtualdirectoryname”>SalesLogix</A>

The server is the name of your Web Host machine. The virtual directory name is SlxClient, unless you specified a different name in the Sage SalesLogix Web portal Deployment

Properties in Application Architect.

Sage SalesLogix Implementation Guide v8.0

Configuring the Web Client

Configuring Client Computers

To ensure the Web Client functions correctly, you must configure several options on each user’s computer.

To configure

1. Ensure the user is a member of the local Power Users or Administrators group.

This allows ActiveX controls to work correctly if this user enables and downloads extended features on the Web Client Log On page.

2. Ensure the Scrollbar Item setting is set to 17 or less.

• (XP/2003) The Scrollbar option is set in the Control Panel > Appearance and Themes

> Display properties Appearance tab > Advanced > Item drop-down menu.

• (Vista/7/2008) The Scrollbar option is set in the Control Panel > Personalization >

Window Color > Window Color and Appearance > Item drop-down menu.

3. The default browser settings should be used for the Sage SalesLogix Web site. In addition to your browser defaults, the following options are required.

The option locations and wording may vary depending on your browser version.

For more information on these options, refer to your browser’s Help.

Browser Option

Internet Explorer

Setting

Temporary Internet Files>Settings Check for newer versions of stored pages

Automatically.

Security>Trusted sites>Sites

Security tab

• Add the Sage SalesLogix Web site (SlxClient) to the trusted sites list. Type http:// followed by the Web

Host server name for the Web Client site (for example, http://server).

• Turn OFF protected mode for trusted sites

(Vista/7/2008).

• Enable Script ActiveX controls marked safe for

scripting.

• Enable (or set to prompt) Initialize and script

ActiveX controls not marked safe for scripting.

• Enable Drag and drop or copy and paste files

(Allow access to the clipboard).

Enabling UTF-8 Support for Internet Protocols

(Microsoft Office 2007) If users export extended characters from Sage SalesLogix to e-mail,

UTF-8 support must be enabled.

To enable

1. Open Microsoft Outlook.

2. On the Tools menu, click Options.

3. Click the Mail Format tab, and then click International Options.

4. Under Internet Protocols, select Enable UTF-8 Support.

5. Click OK.

82 Sage SalesLogix Implementation Guide v8.0

Configuring the Web Client

Installing Desktop Integration

Desktop Integration extends Sage SalesLogix Web Client functionality by downloading clientside files for the following features:

• Office Integration encompasses Mail Merge, Export to Excel, and Drag and Drop functionality. Administrators can also drag-and-drop library files.

• Outlook Integration encompasses SendSLX and Record to History.

Before users install and configure these features, ensure you configured SData as detailed in

“Configuring the SData Portal” on page 54 .

To install and configure

1. Open the Web Client login screen.

2. Click Install Enhancements.

3. Do one of the following:

• Click Run to install Desktop Integration from it’s current location.

• Click Save to save the install locally before running it.

4. Follow the steps in the Wizard.

5. At the Setup Type screen, do one of the following:

• Select Complete to install all Desktop Integration features (both Office Integration and Outlook Integration).

• Select Custom to choose between Office Integration and Outlook Integration.

Both options are selected by default. In the Custom Setup screen, click the down arrow to the left of the feature you do not want to install and then click This feature will

not be available.

6. Continue to follow the prompts in the wizard.

7. At the end of the installation, click Finish.

8. After installing, you must open the Desktop Manager and configure it with the appropriate portal information. Click the the Find out more link to open the “Installing and Using

Sage SalesLogix Desktop Integration” help topic for browser specific configuration information.

Users can also install Desktop Integration from the link located in the Sage

SalesLogix Web Client, in User Options, on the General tab.

Creating the SyncSalesLogix Group

Additional Intellisync for SalesLogix configuration steps are detailed in

Appendix B,

“Configuring Intellisync for SalesLogix” .

To create

1. Open the Web Client Contact List view.

2. Select the contacts you want to synchronize with Microsoft Outlook.

3. Right-click the selected contacts, and then click Save Records as Group.

The Add Records to new Group dialog box opens.

4. In the Group Name box, type SyncSalesLogix.

5. Click OK.

Sage SalesLogix Implementation Guide v8.0

Configuring the Web Client

Assigning the SyncSalesLogix Group

After creating the SyncSalesLogix group, you must specify that group to be used to transfer information between Microsoft Outlook and Sage SalesLogix.

To assign

1. Open the Sage SalesLogix Web Client.

2. Click Options.

3. In the Intellisync Contact Group box, select SyncSalesLogix.

4. Click Save.

After completing this chapter...

You have completed tasks 13-18 in the

“Web Tasks”

checklist. If your implementation includes:

•

The Mobile Client: proceed with Chapter 9, “Configuring the Sage SalesLogix Mobile Client”

•

Customer Portal: proceed with Chapter 10, “Configuring Customer Portal”

•

Remotes: proceed with Chapter 11, “Configuring Synchronization” .

Otherwise, you can begin using Sage SalesLogix.

84 Sage SalesLogix Implementation Guide v8.0

Chapter 9 Configuring the Sage SalesLogix Mobile Client

Before beginning this chapter...

Install and configure the Web Host and the SData portal as described in

Chapter 5, “Installing the Web Components” . In addition, restart all servers involved in the implementation.

Use the instructions in this chapter to...

Configure the Sage SalesLogix Mobile Client. These tasks are required for all Sage

SalesLogix installations that include the Mobile Client.

Understanding the Mobile Client

Sage SalesLogix Mobile provides secure, reliable mobile access to Sage SalesLogix information when using mobile devices with internet browsers that support HTML5 and CSS3.

For data security, make sure your Sage SalesLogix Web Server has a valid Secured Sockets

Layer (SSL) security certificate installed. You can use the Web Server where you deployed your SLX Client portal.

Deploying the SLX Mobile Portal and the SData Portal

See

“Deploying a Sage SalesLogix Web Portal” on page 51

for detailed steps to deploy the SLX

Mobile and SData portals.

Defining the Default Document

Default documents can be a directory’s home page or an index page containing a site document directory listing. The default document for the Mobile Client portal landing page is index.html, and should have been added to the documents list on the IIS Web site by the installation. If your URL <https://YourSlxWebServer/SlxMobile> is not defaulting to call the index.aspx, you may want to define it manually.

See

“Defining the Default Document” on page 59

for detailed steps to define the default document.

Testing the Mobile Web Site

Use the same procedure to test the Web site as you did for the Web Client (as explained in

“Testing the Web Site” on page 81 ); however, modify the URL as follows:

http://localhost/SlxMobile

If you deployed the Mobile portal to a different Web site in IIS, use the following format: http://servername:port/SLXMobile

Before installing the Sage SalesLogix Mobile portal, make sure your environment meets the following requirements:

• Sage SalesLogix is installed and has a functioning Web environment.

Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix Mobile Client

• The Web Server has a valid Secured Sockets Layer (SSL) security certificate installed. You can use the Sage SalesLogix Web Server where you deployed your SLX Client portal.

• The SData portal has already been deployed successfully.

To confirm that SData is set up correctly, type the following URL into your browser: http://<servername>/sdata/$system/adapters. Enter the user credentials of the

SalesLogix user that SData is configured under (for example, Admin). The adapters page

Sage SalesLogix Mobile v1.2 Implementation Guide should load and list the available feeds.

Sending the Mobile Portal URL to Users

Send the Sage SalesLogix Mobile portal URL to mobile users through email. Your users click the URL or type it into a compatible browser on a desktop computer, mobile device, or tablet computer. Any Sage SalesLogix user can access Sage SalesLogix information from his or her compatible mobile device by clicking the portal link. No specific user configuration is needed.

For security purposes, make sure you set up SSL encryption on the server and access the client using HTTPS. An example URL is: https://YourSlxWebServer/SlxMobile.

Note

The browser may ask users if it is OK to store data on their computer for offline use.

This is expected, as the mobile application is cached on the computer for improved performance. After the application has been cached, the user can quickly move from screen to screen because only data needs to be transferred over the wire from the

SData portal.

For more information, refer to the “Common Tasks in Application Architect” topic in the Application Architect help.

After completing this chapter...

You have completed steps 1 to 4 in the “Mobile Client Tasks”

checklist.

•

Customer Portal: proceed with Chapter 10, “Configuring Customer Portal”

•

Remotes: proceed with Chapter 11, “Configuring Synchronization” .

Otherwise, you can begin using Sage SalesLogix.

86 Sage SalesLogix Implementation Guide v8.0

Chapter 10 Configuring Customer Portal

Before completing this chapter...

Install and configure the Web Client as described in Chapter 8, “Configuring the Web Client”

Use the instructions in this chapter to...

Configure and deploy Customer Portal. These tasks are required for installations that include Customer Portal.

Customer Service and Customer Portal extend Sage SalesLogix customer service features onto the Web for employees and customers.

Understanding Customer Service

Customer Service features in the Sage SalesLogix Web Client allow employees to add or update tickets, track their time as ticket activities for processing and resolving tickets, create calendar activities for tickets, add related ticket information, access SpeedSearch to find solutions to customers’ problems, and run reports. Customer Service is enabled for all named users by default.

Understanding Customer Portal

Customer Portal enables you to provide customers with user names and passwords so that they can view information about existing tickets, create new tickets, and change the status of tickets. Customers can also access SpeedSearch to find solutions. Customers are granted permissions to Customer Portal by an internal Sage SalesLogix user.

Customer Portal features require:

• Sage SalesLogix Advanced License

• Sage SalesLogix Customer Portal License

• Additional configuration in Administrator and Application Architect.

Before you configure Customer Portal, ensure:

•

The Web Host is installed and configured according to Chapter 5, “Installing the Web

Components”

• SpeedSearch Server is installed and configured on the same server as the Web Host or on a separate server.

• Employees who use Customer Service are active Sage SalesLogix users (not WebViewer users).

• Users who access Customer Portal have the same hardware, browser, and configuration as users who access the Web Client.

Sage SalesLogix Implementation Guide v8.0

Configuring Customer Portal

Adding the Sage SalesLogix Customer Portal User

Sage SalesLogix Customer Portal requires a generic, named Sage SalesLogix user. This user may be set up as a Named Web User or Concurrent User. In addition, the user must be a member of every team, and every user’s team, so that customers can access records owned by all teams.

The admin user can be used for Customer Portal if you do not want to create a separate named user.

To add

1. On the Administrator Navigation Bar, click Users.

2. Click the Add button on the toolbar.

3. In the Add Users dialog box: a. In the Add box, select Named Web or Concurrent User. b. In the Quantity box, ensure 1 appears.

c. Ensure the Create Profile From check box is cleared.

d. Click OK.

The User Profile for <NewUser> dialog box appears.

4. On the General tab: a. In the Username box, type customerportal (one word).

b. In the Name box, type Customer Portal.

c. Ensure the Login Active check box is selected.

d. In the Department box, select a department for this user.

This can be any department.

e. Verify the User Type is Named Web or Concurrent User.

5. On the Teams tab: a. In the Teams area, click Manage.

b. In the Teams dialog box, select each team. Ensure you have selected all teams.

c. Click OK.

6. Click OK.

The new Customer Portal user appears in the Users grid.

Setting User Security

Sage SalesLogix Customer Portal requires a Web access user, which permits users who are not named SalesLogix users to access parts of Sage SalesLogix functionality. The Web access user uses the permissions of the named Sage SalesLogix Customer Portal user

(customerportal) to perform certain actions, and records any history, logs, and so on to that user name.

To set

1. On the Application Architect Tools menu, click Web User Security.

2. In the Select a Web Access User list, select Portal, Customer.

If you are using a different user name for the Customer Portal user, set the value to that

name; however, make sure that user name has been configured as instructed in “Adding the Sage SalesLogix Customer Portal User” on page 88 .

3. Click OK.

4. On the Build menu, click Build Web Platform.

88 Sage SalesLogix Implementation Guide v8.0

Configuring Customer Portal

Deploying the Sage SalesLogix Customer Portal

See “Deploying a Sage SalesLogix Web Portal” on page 51 for detailed steps to deploy Customer

Portal.

Configuring the Sage SalesLogix Customer Portal

Additional configuration for SpeedSearch indexes and Web access is required for Customer

Portal.

Configuring SpeedSearch Indexes for Customer Access

To make SpeedSearch indexes available to customers so that they can search for information, ensure you have given Customer access to each index under the Public Access setting. If you have already assigned Customer access to indexes when you originally set them up, disregard this section.

To configure

1. On the Administrator Manage menu, click SpeedSearch Indexes.

2. In the Manage SpeedSearch Indexes dialog box, select an item under Index Name that you want to allow customers to access, and then click Edit.

3. In the SpeedSearch Index Definition dialog box, under Public Access, select 1-

Customer.

Internal employees can still access this index when Public Access is selected.

4. Click OK.

5. If necessary, continue selecting indexes and editing the Public Access for each one.

Enabling the Contact Web Access Tab

By default, only the system administrator can grant contacts access to Customer Portal.

However, you can give certain employees who use Customer Service this ability as well.

When employees have this access, they can see the Web Access tab in the Contact Detail view within Sage SalesLogix Network Client and Sage SalesLogix Web Client.

To enable

1. Make a list of employees who should be able to grant contacts access to Customer Portal.

2. On the Administrator Navigation Bar, click Users.

3. In the Users grid, double-click the first user in your list to open the user’s profile.

4. On the Service/Support tab, select User may grant access to Customer Portal.

This enables the employee to use Sage SalesLogix with Customer Service or Sage

SalesLogix Web Client with Customer Service to open a contact record, click the Web

Access tab, and set up a user name and password for the contact so the user can log on using Customer Portal.

5. Click OK.

6. Repeat steps 3-5 for each employee on your list.

7. Inform the employees that when they log on to the Sage SalesLogix Network Client or the

Sage SalesLogix Web Client with Customer Service, and open a contact record, the Web

Access tab appears so that they can set up a user name and password for the contact.

Once this is set up, the contact can log on to Customer Portal to view tickets, create new tickets, close and re-open tickets, and access SpeedSearch. For more information, see the

Customer Portal Help.

Sage SalesLogix Implementation Guide v8.0

Configuring Customer Portal

Testing the Customer Portal Web Site

Use the same procedure to test the Web site as you did for the Web Client (as explained in

“Testing the Web Site” on page 81

); however, modify the URL as follows:

http://localhost/SlxCustomerPortal

The localhost is the name of your Web Host server.

If you deployed the Sage SalesLogix Customer Portal to a Web site you created during the Web Host installation, or to another Web site you created manually in IIS, the format is: http://servername:portnumber/SlxCustomerPortal.

The server is the name of your Web Host server. The port is the port number you specified during the Web Host installation.

Linking from Your Company’s Web Site

After Customer Portal configuration is complete, you must create a link to it from your company’s Web site.

Create the link in the following format: http://servername/SlxCustomerPortal

For example:

<a href=“http://servername/SlxCustomerPortal

“> Report a Problem/Check for a Response</a>

If you deployed the Sage SalesLogix Customer Portal to a different Web site in IIS, create the link in the following format:

<A HREF=”http://servername:portnumber/SlxCustomerPortal”

“> Report a Problem/Check for a Response</a>

The server is the name of your Web Host machine. The port is the name of the port the Web site is using. The Web site name is SlxCustomerPortal, unless you specified a different name when deploying Sage SalesLogix Customer Portal.

Configuring Client Computers

To ensure the Customer Portal functions correctly, configure settings in each user’s browser as described in the following table.

The option locations and wording may vary depending on your browser version. For more information on these options, refer to your browser’s Help.

Internet Explorer Option Setting

Temporary Internet Files>Settings Check for newer versions of stored pages

Automatically.

Privacy tab Medium or lower (cookies must be enabled).

After completing this chapter...

You have completed steps 2 to 8 in the “Customer Portal Tasks”

checklist. If your implemenatation includes Remotes, proceed with Part III:

“Remote Offices, Users, and the

Offline Web”

90 Sage SalesLogix Implementation Guide v8.0

Part III

Remote Offices, Users, and the Offline Web

Chapter 11 Configuring Synchronization

Before beginning this chapter...

Add licenses and configure the system as described in Chapter 4, “Configuring the Sage

SalesLogix System”

Use the instructions in this chapter to...

Configure synchronization. These tasks are required for all Sage SalesLogix installations that include remotes.

Synchronization Server refers to both the software that runs synchronization and the hardware on which the server is installed. A Sync Server is only necessary if you have

Remote users (including Offline Web Client users) or Remote Offices, or you plan to run agents.

Use the Sage SalesLogix Planning Guide to understand the synchronization process in detail and to make decisions regarding your synchronization requirements.

Creating Synchronization Transfer Profiles

Sage SalesLogix supports three methods of synchronization. Each synchronization method is defined by one or more Sync Transfer Profiles. To create a Sync Transfer Profile, refer to one of the following:

•

“Creating a Network Synchronization Profile” in the following section.

•

“Creating an FTP Synchronization Profile” on page 93

•

“Creating an HTTP Synchronization Profile” on page 96 .

Creating a Network Synchronization Profile

One way to synchronize with the main office is through a VPN (Virtual Private Network) connection. Using VPN, Remote users or offices connect to the Sage SalesLogix network via the internet to send and receive transactions from the main office database.

This is the default method of synchronization. Unless you want to change the Sync Transfer

Profile settings, Remotes can synchronize via network synchronization without additional configuration.

The next step...

Proceed to

“Creating a Synchronization Service Profile” on page 100 .

Creating an FTP Synchronization Profile

FTP support is built into both the Sync Server and Sync Client. When the Sync Server cycles, it connects to the FTP site and searches the FTP Infiles directory for any transaction exchange files that were sent by Remote users. Likewise, when the Sync Client cycles, it connects to the FTP site and searches the FTP Outfiles directory for transaction exchange files placed there by the main office. Essentially, all transaction exchange files, library files, and documents are delivered to and received from the FTP site.

Sage SalesLogix Implementation Guide v8.0

Configuring Synchronization

Logging on to an FTP site can be accomplished in one of two ways:

• Global login - Using a global login, the Sync Server and all Remote users share the same login and password.

• Personal logins - Using personal logins, the Sync Server and each Remote user is assigned a different login to the FTP site.

Setting Up a Sage SalesLogix FTP Site

An FTP site is a collection of files on an FTP server. The FTP server allows users to upload or download files through the Internet or other TCP/IP network using a File Transfer Protocol

(FTP). By default, IIS uses Passive FTP connections.

When setting up an FTP site, you must:

• Create three folders on the FTP server. For example, /Infiles, /Outfiles, and /FailedTrans.

These folders must be shared, and all Remote users and the Sync Server must have read, write, and delete access.

• Create three virtual directories that point to the Infiles, /Outfiles, and /FailedTrans folders. All Remote users, as well as the Sync Server, must have read, write, and delete access to these directories.

• For FTP performance tips, see the “Improving FTP Synchronization Performance” topic in the Administrator Help.

• To configure FTP synchronization to use Active FTP connections, see the

“Configuring FTP Sync to Run in Active or Passive Mode” topic in the

Administrator Help.

If your implementation includes multiple Sync Servers, note the following:

• You can only have one /Infiles, /Outfiles, and /FailedTrans folder per Sync Server.

• You can have multiple FTP virtual folders per Sync Server. However, Sage SalesLogix recommends approximately 50 Remote users per FTP virtual folder.

• Sage SalesLogix recommends that your FTP Server is on the corresponding Sync Server

(if possible).

Creating an FTP Sync Profile

The Sync Transfer Profile identifies the DLL file used for FTP synchronization.

To create

1. On the Administrator Manage menu, click Sync Transfer Profiles.

2. In the Sync Transfer Profiles dialog box, click Add.

3. In the DLL box, select FTP Sync Transport v1.2 (SSftp.dll).

If FTP Sync Transport is not available in the DLL list, verify the SSftp.dll file is located in the SalesLogix folder.

4. In the Description box, type a description of the synchronization method.

5. Click Setup.

6. In the FTP Site box, type the address of the primary FTP site to which the Sync Client connects (for example, ftp.yourcompany.com).

You can use a named FTP site (for example, yourcompany.com), or an IP address (for example, ftp.123.45.67.8).

7. In the Port box, type the primary site’s port number on the FTP server.

Port numbers allow IP packets to be sent to the FTP site.

94 Sage SalesLogix Implementation Guide v8.0

Configuring Synchronization

8. In the Alternate Site box, type an alternate address that connects to your FTP site.

If the Sync Client cannot connect using the primary address, it attempts to use the alternate address. For example, you can use the named FTP site as the primary site and the IP address as the alternate site.

9. In the Port box, type the alternate site’s port number on the FTP server.

10. In the File Names box, select Uppercase, Lowercase, or Unspecified.

Response time improves considerably if this setting matches the way file names are stored on your FTP server. The default is Unspecified.

11. In the Infiles, Outfiles, and FailedTrans boxes, type the Infiles, Outfiles, and

FailedTrans folder names on your FTP server (for example, /Infiles, /Outfiles, and

/FailedTrans).

Creating the folders is outlined in

“Setting Up a Sage SalesLogix FTP Site” on page 94 .

12. Under Login:

• Click Login and password below to assign the same login and password to the

Sync Server and all Remote users. Then in the Login box, type the general login that is shared by all Remote users and Sync Server(s) when logging on to the FTP site. In the Password box, type the corresponding password. Then, click OK.

If you choose to use a global login, you can use the default anonymous user that comes with FTP. This user is already configured with the necessary permissions. This user has a Login of anonymous, and the corresponding Password is your domain name.

• Click Personal login and password to assign a different login and password to each

Sync Server and Remote user. Then, click OK.

Use the FTP Sync Transport Local Options dialog box to set the login for the sync server. Personal logins for Remote users are set in the individual’s user profile. The instructions for configuring the user login are in

Chapter 12, “Configuring the Sage

SalesLogix Remote Client” .

Sage SalesLogix Implementation Guide v8.0

Configuring Synchronization

13. If you selected the Personal login and password option, in the Edit Sync Transfer

Profile dialog box, click Server Settings. In the Login and Password boxes, type the

Sync Server’s login and corresponding password to the FTP site.

14. Click OK.

15. Proceed to

“Creating a Synchronization Service Profile” on page 100

Creating an HTTP Synchronization Profile

HTTP Synchronization provides a secure method of transferring data using a Web site on an

HTTP Server. When the Sync Server cycles, it connects to the HTTP Server and searches the

Infiles folder for any transaction exchange files (TEFs) that were uploaded by Remote users.

Likewise, when the Sync Client cycles, it connects to the HTTP Server and searches the

Outfiles folder for any transaction exchange files placed there by the main office. All transaction exchange files, library files, and documents are uploaded to and downloaded from the HTTP Server.

If you are creating an HTTP site on Windows 2008, IIS 6 compatibility is required.

Ensure you enable IIS 6 compatibility on the HTTP Server. See “Web Requirements” on page 18 for details.

Setting Up a Sage SalesLogix HTTP Site

An HTTP site is a collection of files on an HTTP Server that allow users to upload or download files via the Internet. HTTP synchronization requires Internet Information Services (IIS) with

World Wide Web Service installed.

When synchronizing using HTTP, you must set up IIS and configure the necessary folders for file transfer.

Before creating the HTTP Site, ensure you have IIS with HTTP Support installed and running.

See one of the following sections as appropriate for your server version.

•

“To create an HTTP site on Windows 2003” in the following section.

•

“To create an HTTP site on Windows 2008” on page 97 .

To create an HTTP site on Windows 2003

1. On the HTTP Server, create a folder where you want the Sage SalesLogix Web site you create to point. For example, SLXHTTPSync.

2. In the folder you created in the Step 1, create the following three sub folders:

• Infiles

• Outfiles

• FailedTrans

3. Open Internet Information Services (IIS) Manager.

Ensure that WebDAV (Web-based Distributed Authoring and Versioning) is enabled.

Athough WebDav has been determined to impact SData, you can enable it here without issues. It is automatically disabled in the SLXClient, SData and ProcessHost portals at deployment. This will not affect HTTP sync.

4. In the Internet Information Services tree view, expand your HTTP Server, and then expand Web Sites.

5. Right-click the Web Sites folder, point to New, and then click Web Site.

6. On the Web Site Creation Wizard Welcome screen, click Next.

Sage SalesLogix Implementation Guide v8.0

Configuring Synchronization

7. On the Web Site Description screen, type a name for the Web site. For example,

SalesLogix HTTPSync.

8. Click Next.

9. On the IP Address and Port Settings screen, complete the following (the screen may vary depending on your implementation): a. In the Enter the IP address to use for this Web site box, leave the default setting of All Unassigned.

b. In the TCP Port this Web site should use box, change the port number to port

1024 or higher. Record the port number you are using.

c. In the Host header for this Web site box, leave the field blank.

d. Click Next.

10. On the Web Site Home Directory screen:

a. In the Path box, click Browse and navigate to the folder you created in Step 1. DO

NOT point to the network logging path.

b. Clear the Allow anonymous access to this Web site check box.

c. Click Next.

11. On the Web Site Access Permissions screen: a. Enable only the following Permissions: Read, Write, and Browse.

b. Click Next.

12. Click Finish.

13. In the Internet Information Services tree view, right-click your new Web site, and then click Properties.

14. In the Web Site Properties dialog box, click the Directory Security tab.

15. In the Authentication and access control section, click Edit.

16. In the Authenticated access section, select Digest authentication for Windows

domain servers.

17. In the IIS Manager information dialog box, click Yes to continue.

18. In the Authentication Methods dialog box, click the Realm Select button, browse to and select the domain of your HTTP Server, and then click OK.

19. In the Authentication Methods dialog box, click OK.

20. In the Web Site Properties dialog box, click the HTTP Headers tab.

21. Click the MIME Types button.

22. In the MIME Types dialog box, click New.

23. In the MIME Type dialog box: a. In the Extension box, type SLXT.

b. In the MIME type box, type Text/Plain.

c. Click OK.

24. In the MIME Types dialog box, click OK.

25. In the Web Site Properties dialog box, click OK.

26. Reset IIS.

After setting up IIS, you must create a Sync Transfer Profile in the Administrator. Proceed to

“Creating an HTTP Sync Transfer Profile” on page 99 .

To create an HTTP site on Windows 2008

1. On the HTTP Server, create a folder where you want the Sage SalesLogix Web site you create to point. For example, SLXHTTPSync.

2. In the folder you created in the step 1, create the following three sub folders. Set folder

permissions to Read, Write, and Modify.

• Infiles

Sage SalesLogix Implementation Guide v8.0

Configuring Synchronization

• Outfiles

• FailedTrans

3. Open Internet Information Services (IIS) Manager.

a. Create or use an existing Sage SalesLogix application pool.

b. Ensure the identity of the application pool is set to log on with a user that has Read,

Write, and Modify permissions to the HTTP sync folders you created in step 2.

c. For 64-bit operating systems, enable 32-bit applications.

4. In the Connections tree view, expand your HTTP Server, and then expand Sites.

5. Right-click the Sites folder, and then click Add Web Site.

The Add Web Site dialog box opens.

a. In the Site name box, type a name for the Web site. For example, SalesLogix

HTTPSync.

b. In the Physical path box, browse to the folder you created in Step 1. DO NOT point

to the network logging path.

c. Click Connect as, verify Application user (pass-through authentication) is selected, and click OK.

d. Click Test Settings to verify the connection.

e. In the Type box, ensure http is selected.

In the IP address box, select All Unassigned.

g. In the Port box, change the port number to port 1024 or higher. Record the port number you are using.

If necessary, port 80 can be used.

h. Leave the Host name box blank.

Click OK.

6. In the Connections tree view, select your Sage SalesLogix HTTP Web site.

7. In the Features View under IIS, double-click Authentication.

8. In the Authentication list, select Anonymous Authentication, and in the Actions pane click Disable.

9. Enable Windows Authentication.

a. In the Authentication list, select Windows Authentication, and in the Actions pane click Enable.

b. In the Actions pane, click Advanced Settings.

The Advanced Setting dialog box appears.

c. In the Extended Protection drop-down, select Off or Accept (either option works), and then click OK.

d. In the Actions pane, click the Providers link.

e. In the Enabled Providers list, select NTLM and move it to the top of the list.

Click OK.

10. In the Features View under IIS, double-click MIME Types.

a. In the Actions pane, click Add.

b. In the File name extension box, type SLXT.

c. In the MIME type box, type text/plain.

d. Click OK.

11. In the Features View under IIS, double-click Directory Browsing.

12. In the Actions pane, click Enable.

98 Sage SalesLogix Implementation Guide v8.0

Configuring Synchronization

13. Enable and configure WebDAV (Web-based Distributed Authoring and Versioning).

a. In the Features View under IIS, double-click WebDAV Authoring Rules.

If WebDAV Authoring Rules is unavailable, download the WebDAV Extensions for IIS from Microsoft.

b. In the Actions pane, click Enable WebDav.

c. In the Actions pane, click Add Authoring Rule.

d. In the Add Authoring Rule dialog box, set the following options, and then click OK.

• Under Allow access to, select All Content.

• Under Allow access to this content to, select All users.

• Under Permissions, select the Read, Source, and Write options.

14. Reset IIS.

After setting up IIS, you must create a Sync Transfer Profile in the Administrator.

Creating an HTTP Sync Transfer Profile

The Sync Transfer Profile identifies the DLL file used for HTTP synchronization.

To create

1. On the Administrator Manage menu, click Sync Transfer Profiles.

2. In the Sync Transfer Profiles dialog box, click Add.

3. In the DLL box, select HTTP Sync Transport v1.2 (SShttp.dll).

If HTTP Sync Transport is not available in the DLL list, verify the SShttp.dll file is located in the SalesLogix folder.

4. In the Description box, type a description of the synchronization method.

5. Click Setup.

6. In the Web Site box, type the name of the HTTP Server to which the Sync Client connects for file transfer (for example, httpserver). This is the name of the server the

Sync Client connects to, not the URL.

Use the format: Servername or Servername.DomainName. Do not include http:// before the server name.

7. In the Port box, type the port number of your HTTP Server.

This is the port number you defined in Step 9 of the previous section.

8. Select the Secure Comm (SSL) check box if you are using a secure connection to transfer files between the HTTP Host and Sage SalesLogix.

9. In the Alternate Site box, type an alternate HTTP Server for file transfer.

If the Sync Client cannot connect using the primary Web Site, it attempts to use the alternate site.

10. In the Port box, type the alternate site’s port number on the HTTP Server.

11. If necessary, select the Secure Comm (SSL) check box if you are using a secure connection for your alternate site.

12. In the Infiles, Outfiles, and FailedTrans boxes, type the Infiles, Outfiles, and

FailedTrans folder names on your HTTP server (for example, /Infiles, /Outfiles, and

/FailedTrans).

Creating the folders is outlined in

“Setting Up a Sage SalesLogix HTTP Site” on page 96

13. Under Login:

Sage SalesLogix Implementation Guide v8.0

Configuring Synchronization

• Click Login and password below to assign the same login and password to the

Sync Server and all Remote users. Then in the Login box, type the general login that is shared by all Remote users and Sync Server(s) when logging on to the HTTP

Server. In the Password box, type the corresponding password. Then, click OK.

• Click Personal login and password to assign a different login and password to each Sync Server and Remote user. Then, click OK.

Use the HTTP Sync Transport Local Options dialog box to set the login for the Sync

Server. Personal logins for Remote users are set in the individual’s user profile. The instructions for configuring the user login are in

Chapter 12, “Configuring the Sage

SalesLogix Remote Client”

14. If you selected the Personal login and password option, in the Edit Sync Transfer

Profile dialog box, click Server Settings. In the Login and Password boxes, type the

Sync Server’s login and corresponding password to the HTTP Server.

15. Click OK.

Creating a Synchronization Service Profile

Since synchronization can require a lot of system resources, it is recommended that you run synchronization during off-peak times, such as before or after normal business hours. To implement a synchronization schedule, you can use the Synchronization Service. Running the

Sync Server from a Windows service allows synchronization to process without an administrator logged on to the server. In addition, the Monitor Console allows you to remotely view the status of the Sync Server and its scheduled jobs.

To create a Synchronization Service Profile, see the “Configuring Synchronization

Server Automated Services” topic in the Administrator Help.

100 Sage SalesLogix Implementation Guide v8.0

Configuring Synchronization

Starting the Synchronization Server

After installation and configuration, run a synchronization cycle to create the synchronization folders. This manual cycle also creates a registry entry that is used by Agent Runner to build a connection string.

You must log on to the Synchronization Service computer as a Domain user. You cannot log on using the Local System account to cycle the Sync Server the first time.

The Local System account does not have the correct privileges for running Agents.

To start

1. Click Start, point to Programs, point to Sage SalesLogix, and then click

Synchronization Server.

2. In the Please log on dialog box: a. In the Username box, type admin.

b. In the Password box, type the admin user’s password.

c. In the Log on to box, ensure the correct database connection name displays.

This is the connection name established in the Connection Manager.

3. Click OK.

4. If necessary, click Yes to register this computer to the database.

5. If the Verify Administrator Password dialog box appears, retype the administrator password, and then click OK.

6. Click Sync Now to cycle the Sync Server.

7. On the File menu, click Exit when the process is complete.

The first time you cycle the Sync Server, a sub folder is created in Documents and

Settings\All Users\Application Data\SalesLogix\Sync. The folder name is server_namealias_name. In addition, the Sync Server creates the ConfTran.stm file used for conflict resolution.

Modifying Virus-Checking Software for the Synchronization Server

If you have virus-checking software scanning the synchronization folders at the same time that the Sync Server tries to use a file within the folders, you may receive an “Error deleting file or folder” error. This occurs when the virus checking software checks the file at the same moment that the Sync Server tries to use that file.

To avoid errors, set your virus-checking software to modify scans to skip the following folders during real-time scans and/or scans scheduled to run at the same time the Sync Server is scheduled to run. If anti-virus programs are scanning the following folders in real time during a synchronization cycle, it may cause problems with synchronization to Remotes.

• WriteCache

• Infiles

• Outfiles

• FailedTrans

• WGLogs

• SharedLogs

• Archives

Sage SalesLogix Implementation Guide v8.0

101

Configuring Synchronization

After completing this chapter...

You have completed the “Synchronization Tasks”

checklist. If your implementation includes:

•

Remote users: proceed with Chapter 12, “Configuring the Sage SalesLogix Remote Client”

• Remote Offices: proceed with

Chapter 13, “Configuring a Remote Office”

• Offline Web Client: proceed with

Chapter 14, “Configuring Offline Web Clients”

102 Sage SalesLogix Implementation Guide v8.0

Chapter 12 Configuring the Sage SalesLogix Remote Client

Before beginning this chapter...

Configure the Sync Server as described in Chapter 11, “Configuring Synchronization”

Use the instructions in this chapter to...

Install and configure Sage SalesLogix Remote Clients. These tasks are required for installations that include Remote users.

Remote Clients keep a subset of the main office database on their local computer (a laptop, for example) and use synchronization to transfer changes between their system and the main office. To synchronize data, the main office and each Remote client must have a set of synchronization folders on their computers and have the ability to transfer files. Remote users can also connect directly to the main office database using a LAN or WAN connection.

Planning for Remote Users

The computer used for creating remote databases must have SQL 2005 Native client installed.

Before adding Remote users, consider creating subscription rules to limit the number of account records stored on the Remote user’s database. Subscription gives Remote users access only to accounts that they use on a regular basis. This maintains the Remote user’s database at a manageable level and improves overall system performance. The use of subscription and subscription rules for Remote users is strongly recommended.

For more information, refer to the “What is Subscription?” and “Subscription

Recommendations” topics in the Administrator Help.

Configuring Remote User Profiles

The Administrator is used to manage user profiles. In addition to the settings for Network users, Remote user profiles must contain synchronization and subscription information.

If you have not created your Remote users, refer to

“Creating Users” on page 64 . Then,

configure the synchronization options as described in the following section.

Setting Synchronization Options

Synchronization options assign the Remote user to a Sync Server, and determine how the user synchronizes with the main office.

You must create system Sync Transfer Profiles before setting the Remote user’s Sync

Transfer Options. If you have not created your system profiles, see

“Creating Synchronization

Transfer Profiles” on page 93 for instructions.

To set

1. On the Administrator Navigation Bar, click Users.

2. In the Users view, click the Remote Users tab, and then double-click a user name.

Sage SalesLogix Implementation Guide v8.0

103

Configuring the Sage SalesLogix Remote Client

3. In the User Profile dialog box, click the Sync tab.

4. In the SyncServer box, select the Sync Server to which this user is assigned.

If your implementation includes multiple Sync Servers, review the recommendations in the Sage SalesLogix Planning Guide for assigning users to Sync Servers.

5. In the Sync Transfer Profile box, select the Remote user’s method of synchronization.

Your choices depend on the system sync transfer profiles configured in “Creating

Synchronization Transfer Profiles” on page 93

If FTP or HTTP is your synchronization method, and you are using individual logins and passwords for each user and the Sync Server, type the user’s login and password in the appropriate boxes.

6. To set subscription rules for the user, click Subscription Rules.

a. In the Subscription Rules dialog box, select the rule(s) you want to apply to this user. Click Copy.

b. Click OK.

7. To configure how attachments are sent to this Remote user, click Attachment Filters.

In the Attachment Filter Options dialog box: a. To set a size limit, select File Size Less Than, and then type in a size limit.

When this value is set, any attachments larger than the specified value will not automatically synchronize to the Remote. The Remote user can request the attachment, but it will not be sent when creating a Remote database or during the normal synchronization process.

104 Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix Remote Client b. To set a date limit, select Files Added Within Last, and then type in a number of days.

When this value is set, any attachments older than the specified value will not automatically synchronize to the Remote. The Remote user can request the attachment, but it will not be sent when creating a Remote database or during the normal synchronization process.

Offline Web Client users cannot request attachments.

c. To apply these options to all Remote users, click All Users.

d. Click OK.

8. In the User Profile dialog box, click OK.

Creating a Remote User Database

Remote databases can be created using a Microsoft SQL Server Express instance.

When a remote database is created, it uses the host server collation settings. When the database is sent to the remote it will use the SQL Express installation collation settings.

To create

1. On the Administrator Tools menu, click Create Remote User Databases.

2. In the Create Databases dialog box, under Available Users, select the user(s) for whom the database(s) will be created, and click the arrow to move them to the Selected

Users box.

Configuring the default database settings is explained in

“Setting Database Options” on page

. To change the settings for this user only, click Options or Properties and configure the changes.

3. Each database is placed in the folder specified in the Create Remote DB in server

directory box on the Database tab of the Options dialog box. To create the database(s), do one of the following.

• To create the database(s) immediately, click Now.

• To create the database(s) at a later time, click Later.

• In the calendar, select a date and time, and then click OK.

The Administrator is unavailable when the timer is active.

• The Create Databases dialog box displays a countdown to the scheduled date and time.

A test is performed to ensure the settings are configured and that the database can be created in the chosen location.

The database is created with the file name SLX_userid_dat.sxd.

4. Click OK to confirm successful completion.

If the Remote user’s computer is connected to the network, create a folder on the

Administrative Workstation and copy the database to the folder. Share this folder so that the

Remote user’s computer has access to it.

If the Remote user is not connected to the network, copy the database to the user’s computer using some form of removable media. Another option is to zip the database, e-mail it to the

Remote user, and instruct the user to copy it to his or her computer and unzip it.

Sage SalesLogix Implementation Guide v8.0

105

Configuring the Sage SalesLogix Remote Client

Installing the Sage SalesLogix Remote Client

If your company uses Outlook Integration, ensure you have completed the required steps under

“Outlook Integration Requirements” on page 24

before you install the Sage

SalesLogix Remote Client.

Install the Sage SalesLogix Remote Client on every Remote user’s computer. The Sage

SalesLogix Remote Client cannot be installed on the same computer as the Administrative

Workstation.

• If you created an automated installation using the instructions in

“Creating Automated

Client Installations” on page 69

, see

“Performing an Automated Installation”

in the following section.

•

If you did not create an automated installation, see “Performing a Manual Installation”

Performing an Automated Installation

Installing the Sage SalesLogix Client using an automated installation configures the Client computer with the settings selected when the installation was built.

When installing Sage SalesLogix using an automated installation, third-party

(prerequisite) applications are not installed. Third-party applications must be installed separately. Installations for these applications can be found in the Redist folder on the

Sage SalesLogix media.

To run

1. Distribute the entire folder structure created during the automated installation to the remote computer.

2. Instruct the Remote user to double-click SalesLogix Remote Client.msi in the root folder.

3. Install the Remote user database as detailed in

“Installing the Remote User Database” on page 107

Performing a Manual Installation

Run a manual installation if you do not want to install some components or if you want to change the installation location.

To run

1. On the Sage SalesLogix Installation screen, click Sage SalesLogix Client

Installations.

2. On the Sage SalesLogix Client Installation screen, click Install Sage SalesLogix

Remote Client.

3. On the Welcome and License Agreement screens, read the information and accept the agreement, and then click Next.

4. On the Setup Type screen, select an installation type, and then click Next.

• Click Complete to install the most common components.

• Click Custom to install only certain components or to change the installation location. Use the Custom Setup screen to enable or disable items for installation.

106 Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix Remote Client

If your company is not using Intellisync for SalesLogix to share information between

Sage SalesLogix and Outlook, clear the Install Intellisync Web Portal check box.

5. On the remaining screens, click Install and Finish to complete the installation.

After installation, you must install the Remote user database as outlined in the following section.

Installing the Remote User Database

Before logging on to the Remote Client, you must attach the Remote database using the

Remote Database Setup dialog box.

The connection contains the following values:

• The Database Name is set to SLXRemote.

• The Server Name is set to the name of the Remote user’s computer.

To change this value, right-click My Computer on your desktop, and click Properties. The computer name appears on the Computer Name tab.

• The User name is set to sa.

• The sysdba password is set to Ma$t3rk3y.

When attaching the remote database, if the sysdba user does not exist, the user is created with a password set to Ma$t3rk3y. If the sysdba user already exists in the remote Microsoft

SQL instance, then the sysdba user’s password remains unchanged. However, the database installation sets the sysdba password in the Connection Manager to Ma$t3rk3y.

Therefore, if the sysdba password on the remote database is set to a value other than

Ma$t3rk3y, the Remote user must open the Connection Manager and change the sysdba password to the value in their database.

To install

1. Browse to the location of the Remote user database. The database file name is

SLX_userid_dat.sxd.

2. Double-click the Remote database.

3. In the SalesLogix Attach Remote dialog box click OK to confirm a successful installation.

If more than one Microsoft SQL Server instance is detected, you must select the instance you want to use in the Select the name of the SQL instance to use dialog box.

The Attach Remote utility assumes the sa password is SLXMa$t3r. If you did not install

Microsoft SQL Express using the Sage SalesLogix installation, you may have to change the sa password in the Remote Database Setup dialog box before the database can be successfully attached.

Creating the Database Login

If you manually attach the SQL databases instead of using Attach Remote, you must enable the sysdba user or the Sage SalesLogix database will not be listed in the Connection

Manager. This task is only necessary if attaching the database manually.

To configure the sysdba user

1. In the SQL Server Management Studio dialog box, on the Tools menu, click SQL

Server Query Analyzer.

2. If you are not connected to the server, the Connect to SQL Server dialog box opens. In the Connect to SQL Server dialog box: a. In the SQL Server box, select your server.

Sage SalesLogix Implementation Guide v8.0

107

Configuring the Sage SalesLogix Remote Client b. Type the system administrator (sa) password.

c. Click OK.

3. On the File menu, click Open, and browse to sysdbafix_script.sql.

This script is located in the Database folder on the DVD.

4. In the Query dialog box: a. In the DB box, select your new database.

b. Click Execute Query (the green arrow) to start the script.

The number of orphaned users fixed with this statement should be 1.

5. Exit the Query dialog box and the SQL Server Management Studio.

After running the sysdbafix_script.sql, refresh the SQL Server Management Studio to display the sysdba user in the database.

Starting the Sage SalesLogix Remote Client

After installation, the user who installed Sage SalesLogix must log on to the Client computer(s) for the first time and launch various applications. This process creates the necessary registry entries for each application and creates a connection to the Remote database.

If the standard user does not have rights to install Sage SalesLogix, an admin user must start the Client application. If the standard user has installation rights, he/she can simply log on and begin using Sage SalesLogix. The Sage SalesLogix Client must write to restricted areas of the registry. Therefore, once an admin user has logged on to the Client, a standard user can read from the registry’s restricted area.

To start

1. On the Start menu, point to Programs, point to Sage SalesLogix, and then click Sage

SalesLogix Client.

2. In the Please log on dialog box: a. Type your Username and Password.

b. In the Log on to box, ensure the correct database connection name displays (for example, SLXRemote). c. Click OK.

3. If you are using Intellisync for SalesLogix, create and assign the SyncSalesLogix group as detailed in

“Creating the SyncSalesLogix Group” on page 73

. Then, complete additional

configuration steps as detailed in “Configuring Intellisync for SalesLogix” on page 129 .

4. Open the SLMailClient.exe.

By default, the Mail Client is installed in ...\Program Files\SalesLogix\SLMail.

5. (Optional) Configure synchronization of the Remote user’s database to run automatically when the user is logged on to the main office database.

For more information on automated synchronization, see the “Sage SalesLogix

Synchronization Client” topic in the Sage SalesLogix Client Help.

108 Sage SalesLogix Implementation Guide v8.0

Configuring the Sage SalesLogix Remote Client

Creating a SpeedSearch Schedule

You can set a schedule on the Remote user’s computer to determine when SpeedSearch indexes are run. If a schedule is not set and your Host updates indexes when the Remote computer is turned off, the indexes on the Remote are updated when the user starts their computer. This update may delay the user as he/she cannot immediately start their work.

Offline Web Clients cannot set a SpeedSearch schedule.

To create

1. On the Sage SalesLogix Client Tools menu, click SpeedSearch Options.

2. In the Index list, select the index(es) for which you want to set a schedule.

3. In the Full Update section, select the date and time you want the index(es) to complete a full update.

4. In the Daily Update section, select how you want to schedule daily incremental updates.

• When SalesLogix Opens - All enabled indexes are updated when you open the

Sage SalesLogix Client.

• When SalesLogix Closes - All enabled indexes are updated when you close the

Sage SalesLogix Client.

• Once at - Select the time of day that you want to update all enabled indexes.

• Repeat Every - Select or type how often you want all enabled indexes to be updated.

5. Click OK.

After completing this chapter...

You have completed the “Remote User Tasks” checklist. If your implementation includes:

•

Remote Offices: proceed with Chapter 13, “Configuring a Remote Office”

•

Offline Web Client: proceed with Chapter 14, “Configuring Offline Web Clients”

If your implementation does not include additional components, you can now begin using

Sage SalesLogix.

Sage SalesLogix Implementation Guide v8.0

109

Configuring the Sage SalesLogix Remote Client

110 Sage SalesLogix Implementation Guide v8.0

Chapter 13 Configuring a Remote Office

Before beginning this chapter...

Configure the Sync Server as described in

Chapter 11, “Configuring Synchronization”

Use the instructions in this chapter to...

Install and configure a Remote Office. These tasks are required for installations that include a Remote Office(s).

A Remote Office consists of a group of users who access a Remote Office database. Unlike

Remote users, these users do not individually synchronize with the main office. Instead, synchronization occurs when the Remote Office database synchronizes with the main office. A

Remote Office may support any combination of Network and Web Client users.

The main office’s Administrator manages the Remote Office and Remote Office users.

Remember that SQL 2005 Native client is required on the computer that creates Remote databases.

Configuring the Remote Office Profile

Before configuring the Remote Office profile, you must have a Remote Office license(s) installed. One license is required for each Remote Office.

To configure

1. On the Administrator Navigation Bar, click Systems, click the Offices tab, and then double-click the Remote Office name.

2. On the Sync Options tab in the Office Description box, type the Remote Office name.

3. Under Remote Office Options: a. Use the Synchronize Changes check box to activate or deactivate synchronization for this remote office.

Select this option only after you install and configure the Remote Office Sync Client, and the database is ready to accept synchronization files.

b. Ensure the Sequence Files Before Apply check box is selected to check for missing, duplicate, or incorrect index numbers in Transaction Exchange Files (TEFs) before changes are made to the main office database.

If this option is selected, the Archives folder stores a copy of all files sent to the main office. Once a confirmation is received from the main office that all files were successfully transferred, the archives are deleted. c. Click Transfer Options. In the Transfer Options dialog box:

• In the Sync Transfer Profile box, select the Remote Office’s method of synchronization.

Your choices depend on the system sync transfer profiles configured in

“Creating

Synchronization Transfer Profiles” on page 93 .

• Click Custom Settings to enter a login and password for the Remote Office.

• Click OK.

Sage SalesLogix Implementation Guide v8.0

111

Configuring a Remote Office

4. Under Shared Paths: a. In the Logging box, type the location of the Remote Office logging folder using UNC conventions and the shared names.

For example, \\MyServer\RemOffice Sync Logs, not \\MyServer\C:\RemOffice Sync

Logs.

It is not possible to use a logging path on a different (trusted) domain if the

SLX Service is using the local system account. To use a logging path on a different domain, you must change the SLX Service from the local system account to a domain user with rights on both domains.

b. In the Library box, type the location of the Remote Office Library folder using UNC conventions and the shared names.

For example, \\MyServer\Library, not \C:\RemOffice Sync Logs\Library.

c. In the Attachments box, type the location of the Remote Office Documents folder using UNC conventions and the shared names.

For example, \\MyServer\Documents, not \\MyServer\C:\RemOffice Sync

Logs\Documents.

If you are connected to the network, browse to the Remote Office folders.

5. Click OK.

Adding Users to a Remote Office

After configuring the Remote Office profile, assign Network and\or Web Users to the Remote

Office.

To add

1. If necessary, use Administrator to create users as described in “Creating Users” on page 64

2. In the User Profile dialog box, click the Sync tab.

3. Under General, in the Location box, select the remote office to which you want to assign the Network user.

4. Click OK.

5. Repeat this procedure for all Remote Office Network users.

Creating a Remote Office Database

Create Remote Office databases using Administrator.

When a remote database is created, it uses the host server collation settings. When the database is sent to the remote it will use the SQL Express installation collation settings.

To create

1. On the Administrator Tools menu, click Create Remote Office Databases.

2. In the Create Databases dialog box, under Available Remote Offices, select the office(s) for which the database(s) will be created, and click the arrow to move them to the Selected Remote Offices box.

The default database settings were configured in

“Setting Database Options” on page 41 . To

change the settings for this office only, click Options and make the changes.

112 Sage SalesLogix Implementation Guide v8.0

Configuring a Remote Office

3. Each database is placed in the folder specified in the Create Remote DB in server

directory box on the Tools > Options > Database tab. To create the database(s), do one of the following.

• To create the database(s) immediately, click Now.

• To create the database(s) at a later time, click Later.

• In the calendar, select a date and time, and then click OK.

The Administrator is unavailable when the timer is active.

• The Create Databases dialog box displays a countdown to the scheduled date and time.

A test is performed to ensure that the settings are configured and that the database can be created in the chosen location.

The database is created with the file name SLX_sitecode_dat.sxd.

4. Click OK to confirm successful completion.

Transfer the database to the remote office database computer. If the computer is connected to the network, create a folder on the Administrative Workstation and copy the database to the folder. Share this folder so the remote office’s computer has access to it.

If the Remote Office computer is not connected to the network, copy the database to the office’s computer using some form of removable media. Another option is to zip the database, e-mail it to the Remote Office, and then copy it to the Remote Office’s computer and unzip it.

Installing the Web Host

If the Remote Office will be using the Sage SalesLogix Web Client or Intellisync for

SalesLogix, you must install the Web Host. Follow the instructions detailed in “Installing the

Web Host” on page 49 .

Installing a Remote Office

The Remote Office is the computer that processes synchronization files and ensures that the main office and Remote Office database contain the same information. Because the synchronization process is resource intensive, do not install the Remote Office on the same computer as the Remote Office database. Rather, install the Remote Office on a dedicated computer with direct access to your network.

To install

1. On the Sage SalesLogix Installation screen, click Standard Server Installation.

2. On the Standard Server Installation screen, click Remote Office Server.

3. On the Welcome and License Agreement screens, read the information and accept the agreement, and then click Next.

4. On the Setup Type screen, select an installation type, and then click Next.

• Select Complete to install all components on this computer.

• Select Custom to install only certain components or to change the installation location. Use the Custom Setup screen to enable or disable items for installation.

5. Depending on your installation type, you will be prompted to enter some or all of the following information on the installation screens:

Sage SalesLogix Implementation Guide v8.0

113

Configuring a Remote Office

• Use Local System Account - Select this option if the local user account has the correct security permissions to install Sage SalesLogix.

If you do not select this option, set the information for the Sage SalesLogix Service user you created as described in

“Permissions Required for the SLXService User (without

Administrator rights)” on page 14

• Domain - Type the network domain where you created the Sage SalesLogix Service user.

• User Name - Type the name of the Sage SalesLogix Service user (for example,

SLXService).

• Password and Confirm - Type the Sage SalesLogix Service user’s password.

• Port Change button - Changes the port number used for communication between the

•

Configure IIS for the Web Server - Select this check box if your installation includes the Sage SalesLogix Web Client and\or Intellisync for SalesLogix portals.

This makes necessary modifications to IIS.

• Create Web Site – Select this check box if your installation includes the Sage

SalesLogix Web Client and\or Intellisync for SalesLogix. This is the site that will be used to deploy the portals to.

• Enter a web site name – Type the name of the Web site. The default name is

SalesLogix.

• Port – Enter the port number that the SalesLogix Web site will use.

• Domain – Enter the network domain where you created the WebDLL user as described in

“The WebDLL User” on page 15 .

• User Account – Enter the name of the WebDLL user you created. The default value is WebDLL. If you used a different name, type it exactly as you did when you created it.

• Password and Confirm Password – Type the WebDLL user’s password.

6. On the remaining screens, click Install and Finish to complete the installation.

Installing the Remote Office Database

Note the following when using SpeedSearch at your remote office:

• If the SpeedSearch Service is started before you install the Remote Office database, no

SpeedSearch indexes are created.

• If the SpeedSearch Service is started after the Remote Office database is installed, but before the first Sync Client cycle, the SpeedSearch indexes are created but there are no documents in either the Library or Documents folder. A search will not find anything until the first schedule for those indexes is run.

• If you rename the database in the Attach Remote utility, you must complete additional steps to ensure the SpeedSearch indexes are created. See the “SpeedSearch Indexes Not

Built For New Database” troubleshooting topic in the Administrator Help for more information.

To install

1. Browse to the location of the Remote Office database. The database file name is

SLX_sitecode_dat.sxd.

2. Double-click the remote database.

3. In the Remote Database Setup dialog box, click OK.

4. In the SalesLogix Attach Remote dialog box click OK.

114 Sage SalesLogix Implementation Guide v8.0

Configuring a Remote Office

If more than one Microsoft SQL Server instance is detected, you must select the instance you want to use in the Select the name of the SQL Server instance to use dialog box.

After installing the Remote Office database, you are ready to start the Remote Office

Synchronization Client.

Creating the Database Login

If you manually attach the SQL databases instead of using Attach Remote, you must enable the sysdba user or the Sage SalesLogix database will not be listed in the Connection

Manager. This task is only necessary if attaching the database manually.

To configure the sysdba user

1. In the SQL Server Management Studio dialog box, on the Tools menu, click SQL

Server Query Analyzer.

2. If you are not connected to the server, the Connect to SQL Server dialog box opens. In the Connect to SQL Server dialog box: a. In the SQL Server box, select your server.

b. Type the system administrator (sa) password.

c. Click OK.

3. On the File menu, click Open, and browse to sysdbafix_script.sql.

This script is located in the Database folder on the DVD.

4. In the Query dialog box: a. In the DB box, select your new database.

b. Click Execute Query (the green arrow) to start the script.

The number of orphaned users fixed with this statement should be 1.

5. Exit the Query dialog box and the SQL Server Management Studio.

After running the sysdbafix_script.sql, refresh the SQL Server Management Studio to display the sysdba user in the database.

Deploying Web Portals for the Remote Office

The Web Portals are:

• Sage SalesLogix Web Client

• Intellisync for SalesLogix

• JobService

• SData

• Web Reporting

If the Remote Office will include these features, you must use the Application Architect installed at the main office to deploy the relevant portal(s).

Ensure you run a synchronization cycle on the Host before deploying the Web site

(see “Starting the Synchronization Server” on page 101 ). The sync cycle creates the

PortalDeployments folder required for the Web site deployment.

To deploy

1. On the Application Architect View menu, click Deployment Explorer.

2. In the Deployments tree view, double-click Remote Sales Client.

3. In the Name box, type a name for the deployment.

Sage SalesLogix Implementation Guide v8.0

115

Configuring a Remote Office

4. In the Description box, type a description for this deployment.

5. In the Deployment Targets tree view, do one of the following:

6. Click Remote Office(s).

The Remote Office Target Settings appear.

a. In the Server box, type the name of your Web Host server.

If you did not install the Web Host, and you are deploying to a separate Web server, type the name of your Web server.

b. Ensure the Deploy Target check box is selected.

This indicates the target is active and should be deployed.

c. In the Port box, type the port number for your Web Host server. It must match the port for the Web site.

d. In the App Pool box, type the name of the application pool for your Web site.

For example, if you used the SalesLogix Web site, the App Pool is SalesLogix.

7. In the Company Name list, select the Remote Office(s) to which you want to deploy the

Web Client.

8. Select the tab for each portal you want to deploy (SlxClient, SlxIntellisync, SData, and\or

SlxJobService): a. In the Virtual Directory box, type the alias name for the virtual directory.

b. In the Sub Directory box, type the folder name where all portal files will be copied under the target’s base directory.

c. Ensure the Deploy Portal check box is selected.

This indicates the portal is active and should be deployed.

When the Inherit from Target check box is selected, the deployment uses the port and application pool settings of the current target to deploy the portal

(these settings are specified under IIS Target Settings). If necessary, clear this check box and set a different Port and App Pool for the portal.

9. Click Save.

10. Do one of the following:

• Click Deploy to deploy portals individually.

• Click Deploy All to deploy all portals in the Remote Office.

The RemoteManifest.xml file is created which contains the settings used by the remote registration services to add an existing IIS Web site or register the site with a server instance. When the Synchronization Server at the main office cycles, the portals are deployed to the remote.

Deploying an Intellisync Portal

If your Remote Office users (Network or Web) will use Intellisync for SalesLogix, you must deploy an Intellisync portal. If you have not already done so, follow the steps outlined in

“Deploying Web Portals for the Remote Office” on page 115

. In step 8, be sure to select the

SLXIntellisync portal for deployment.

Starting the Remote Office Synchronization Client

The first time the Remote Office Synchronization Client runs, the synchronization folders are created under the root RemOffice Sync Logs folder. This process only occurs if you configured the shared paths to the Remote Office (

“Configuring the Remote Office Profile” on page 111

) and shared the RemOffice Sync Logs folder.

116 Sage SalesLogix Implementation Guide v8.0

Configuring a Remote Office

The synchronization cycle processes the portal(s) deployed from the main office and allows access to the Web site.

The following files are created under the main RemOffice Sync Logs folder.

• Archives

• Infiles

• WGLogs

• What’s New.tlg

To start

1. Click Start, point to Programs, point to Sage SalesLogix, and then click

Synchronization Client.

2. In the Log on to dialog box: a. In the Database box, select the Remote Office database to which you want to log on.

b. Click OK.

The Remote Office Sync Client assumes you are logging on as the system administrator.

3. In the Synchronization Client dialog box, click Execute.

The Remote Office Server creates the synchronization folders under the main RemOffice

Sync Logs folder.

4. Click Close when the “Sync Process Completed” message appears.

Remember to select the Synchronize Changes option on the Administrator >

Systems > Offices > Remote Office > Sync Options tab to activate synchronization for this remote office.

You can choose to run the Remote Office Synchronization Client as a service. For more information, see the Sage SalesLogix Client Help topic called “Running the

Remote Office Synchronization Client as a Service”.

Installing Remote Office Network Clients

To install Sage SalesLogix Network Clients in the Remote Office, refer to “Installing the Sage

SalesLogix Network Client” on page 70

Configuring Remote Office Web Clients

After installing and configuring the Web Remote Office, you must provide access to the

Remote Office for Web Client users. Use the following URL format: http://servername:port/<virtual directory name>. For example, http://servername:8086/SlxClient.

Configuring Intellisync for SalesLogix for Remote Office Clients

After installing and configuring the Intellisync for SalesLogix portal, you must provide your users with access. Use the following URL format:

Sage SalesLogix Implementation Guide v8.0

117

Configuring a Remote Office http://servername:port/<virtual directory name>. For example, http://servername:8086/SLXIntellisync.

After completing this chapter...

You have completed the “Remote Office Tasks” checklist. If your implementation includes

Offline Web Clients, proceed with Chapter 14, “Configuring Offline Web Clients”

. If not, you can begin using Sage SalesLogix.

118 Sage SalesLogix Implementation Guide v8.0

Chapter 14 Configuring Offline Web Clients

Before beginning this chapter...

Configure the Sync Server as described in

Chapter 11, “Configuring Synchronization”

Use the instructions in this chapter to...

Install and configure Offline Web Clients. These tasks are required for installations that include Offline Web Client users.

Offline Web Client users are remote users that connect to their local database using the Web

Client. Synchronization is used to transfer changes between the Offline Web Client user’s database and the main office database.

Configuring the Offline Web Client User

Offline Web Client users must be created as Remote users in the Administrator. Remote user profiles must contain synchronization and subscription information.

To create Remote users that will access Sage SalesLogix using the Web Client, refer to the following sections:

•

“Planning for Remote Users” on page 103

- to determine subscription rules.

•

“Creating Users” on page 64 - to add Remote users. Offline Web Clients users are added in

the Administrator as Remote users.

•

“Setting Synchronization Options” on page 103

- to configure how the Offline Web Client user synchronizes with the main office.

•

“Configuring Roles” on page 80

- to configure Web Client access for Offline Web Client users.

•

“Creating a Remote User Database” on page 105

- to create the remote database.

After adding Remote users, setting synchronization options, and creating remote databases, install the Offline Web Client.

Deploying the Web Site to Offline Web Clients

Use the Application Architect to deploy the Sage SalesLogix Web site to Remotes. You must add the SData portal to this deployment for the Desktop Integration Module to support the

Offline Web Client.

Ensure you run a synchronization cycle on the Host before deploying the Web site (see

“Starting the Synchronization Server” on page 101 ). The sync cycle creates the

PortalDeployments folder required for the Web site deployment.

Offline Web Clients must be deployed using the Virtual File System (VFS).

Deployments created from a local file system are not supported and will not function correctly.

To deploy

1. On the Application Architect View menu, click Deployment Explorer.

Sage SalesLogix Implementation Guide v8.0

119

Configuring Offline Web Clients

2. In the Deployments tree view, double-click Remote Sales Client.

3. (Optional) In the Name box, type a deployment name. For example, Offline Web Clients.

4. In the Description box, type a description for this deployment.

5. In the Deployment Targets tree view, click Remote Users.

The Remote User Target Settings appear.

6. In the Deployment Targets tree view, right-click Remote Users and then click Add

Portal(s).

7. In the Select Portal(s) dialog box, select SData, and then click OK.

8. Select the remote users who will receive the Web Client deployment.

9. On the SlxClient tab: a. In the Virtual Directory box, type the alias name for the virtual directory.

By default, the Virtual Directory is SlxClient.

b. In the Port box, type the port number for the Web site.

The Sage SalesLogix Web Server requires its own port for each portal instance. The port for each portal must be unique.

c. Ensure the Deploy Portal check box is selected.

This indicates the portal is active and should be deployed.

10. Click Save.

11. Click Deploy.

The RemoteManifest.xml file is created which contains the settings used by the remote registration services to add an existing IIS Web site or register the site with a personal server instance.

Running a Synchronization Cycle

After deploying the Web site, a synchronization cycle must run to deploy the portal to remotes. Synchronization is set to run automatically every 30 minutes. You can run a manual synchronization cycle immediately or wait for an automated cycle to complete.

Understanding the Offline Web Client Installation

Users do not need administrator rights to install or run the Offline Web Client. However, the

Offline Web Client installation installs third-party prerequisites if they are not detected on the user’s computer. Administrator rights are required to install the following:

• Windows Installer 4.5

• Windows Powershell 1.o for Windows 2003 (x86)

• Microsoft SQL Express 2008 R2

If Microsoft SQL Express 2008 R2 is not detected, Sage will install it. If a previous version of Microsoft SQL Express with a SalesLogix instance is detected during the

Sage SalesLogix installation, the SalesLogix instance will be upgraded and 2008 R2 will be installed in addition to the earlier version.

• .Net Framework 4.0 installed in Integrated mode

• Microsoft SQL 2005 Backwards Compatibility

• .Net AJAX Extensions

• Internet access to Microsoft.com

You can grant the user installing the Offline Web Client administrator rights or install all the required prerequisites before running the Sage SalesLogix installation.

120 Sage SalesLogix Implementation Guide v8.0

Configuring Offline Web Clients

Installing Without Administrator Rights

To install the Offline Web Client without administrator rights, ensure you have installed all the prerequisites listed in the previous section. If the Offline Web Client installation does not detect the necessary prerequisites and the user running the installation does not have administrator rights, the Offline Web Client installation will not complete.

Installing With Administrator Rights

To install the Offline Web Client and the required prerequisites, you must grant the user administrator rights for the computer on which you are installing Sage SalesLogix. See your

Microsoft documentation for instructions on granting administrator rights using one of the following options:

• Add each user to the local machine’s Admin group for the duration of the implementation.

• Use a domain user account that is a member of the domain admin group for the duration of the implementation.

Installing the Offline Web Client

The Sage SalesLogix Personal Web Server is installed with the Offline Web Client to host the

Sage SalesLogix portals on the Remote computer. Therefore, IIS is not required on the

Remote Client computer.

To install

1. On the Sage SalesLogix Installation screen, click Sage SalesLogix Client

Installations.

2. On the Sage SalesLogix Client Installation screen, click Install Sage SalesLogix

Offline Web Client.

3. On the Welcome and License Agreement screens, read the information and accept the agreement, and then click Next.

4. On the remaining screens, click Install and Finish to complete the installation. The following option may appear on the last screen:

• Install Intellisync for SalesLogix - If your company is not using Intellisync for

SalesLogix to share information between Sage SalesLogix and Outlook, clear this check box.

Installing the Remote User Database

Install the Offline Web Client database using the steps outlined in

“Installing the Remote User

Database” on page 107

Running a Synchronization Cycle

Users must run a synchronization cycle before they can log on to the Web Client. The synchronization cycle processes the portal(s) deployed from the main office and allows access to the Web site.

To run

1. On the Start menu, point to Programs, point to Sage SalesLogix, and then click

Synchronization Client.

2. Log on using your Sage SalesLogix user name and password.

Sage SalesLogix Implementation Guide v8.0

121

Configuring Offline Web Clients

3. Click Sync Now.

Logging on to the Web Client

After running a synchronization cycle to set up the portal, you can log on to the Web Client using the system tray icon.

To log on

1. Right-click the system tray icon, and then click Open Site.

2. Log on using the standard Web Client log on screen.

Installing Desktop Integration

Offline Web Client users must download and configure the Desktop Integration Module to use

Web Reporting. See “Installing Desktop Integration” on page 83

for details.

After completing this chapter...

You have completed the “Remote User Tasks”

checklist. You can now begin using Sage

SalesLogix.

122 Sage SalesLogix Implementation Guide v8.0

Part IV

Appendices

Appendix A

Creating a Database for Oracle

Before beginning this chapter...

Verify you have installed the prerequisites and created and shared the logging folders as

described in Chapter 2, “Preparing Your Environment”

Sage recommends having an experienced Oracle database administrator (DBA) to properly administer, tune, and maintain the Sage SalesLogix database, especially in a UNIX environment. The Sage SalesLogix Planning Guide provides a discussion of the Oracle database platform and implementation considerations.

The instructions in this chapter are provided as an example of creating an Oracle database for Sage SalesLogix. This information can be safely used in a demonstration environment. For production systems, your Oracle DBA may use the information in the Sage SalesLogix scripts as an example, but the database should be created by your DBA specifically for your environment.

To create a database for Oracle, you must do the following:

1. Create an Oracle database instance

2. Create a Net Service Name

3. Configure the Oracle database

4. Import the database structure

5. Index the database

6. Add database views

Creating an Oracle Database Instance

Refer to your Oracle documentation to create a database on UNIX. In a demonstration environment, you can accept the Oracle defaults for the Sage SalesLogix database.

Ensure the Sage SalesLogix database is placed in its own instance.

Creating a Net Service Name

After creating the database instance, you must create a Net Service Name (also called database alias).

Refer to the Oracle documentation for instructions to create a database alias.

Configuring the Oracle Database

After creating the database instance and Net Service Name, you must configure the database for Sage SalesLogix. This process is automated using scripts provided by Sage SalesLogix.

Depending on your Oracle version, use SQL *Plus Worksheet or SQL Developer to perform the following tasks:

• Create permanent, temporary, and index tablespace and data files.

Sage SalesLogix Implementation Guide v8.0

125

Creating a Database for Oracle

• Create an Oracle database login.

You must run the scripts used to complete these tasks in a specific order. If you do not run the scripts in the order outlined in the following sections, they do not work.

When running the scripts, you must log on with the Oracle sysdba option. Log on as “sys” with the Connect as option set to sysdba.

Due to legacy requirements of an earlier database platform, the name of the Sage

SalesLogix schema owner is sysdba.

Creating Tablespaces and Data Files

A tablespace logically organizes data in an Oracle database, while physically storing the data in one or more associated data files. To use Oracle with Sage SalesLogix, you must create the permanent (SLX_DATA), temporary (SLX_TEMP), and index (SLX_INDEX) data files.

The CreateOracleSpace.sql script must be run as the sys user using the sysdba role.

To create

1. Open the CreateOracleSpace.sql script.

The script is located in the Database\Oracle folder on the Sage SalesLogix media.

2. Modify the Tempfile and Datafile paths as appropriate for your environment.

If necessary, you can also modify the script to ensure that tablespace and data files are sized correctly.

3. Log on to SQL *Plus Worksheet or SQL Developer.

4. In the Login Information dialog box: a. In the Username box, type sys.

b. In the Password box, type the corresponding system password.

c. In the Service box, type the name of the database instance.

d. Verify that Connect As is set to sysdba.

e. Click OK.

5. On the File menu, click Open.

6. Browse to the CreateOracleSpace.sql script.

7. To load the script into the Query section, click Open.

8. To run the script, click Execute.

9. Run the script as described in the following section to create the database login.

Creating the Database Login

To connect to an Oracle database, a user must have a login name in the database and privileges to perform specific database operations. Since Sage SalesLogix uses sysdba to log on to the Oracle database, you must create a new login for the sysdba user and grant the appropriate privileges.

The CreateOracleUser.sql script must be run as the sys user using the sysdba role.

126 Sage SalesLogix Implementation Guide v8.0

Creating a Database for Oracle

To create

1. Open Oracle SQL *Plus Worksheet or SQL Developer.

2. On the File menu, click Open.

3. Browse to the CreateOracleUser.sql script.

The script is located in the Database\Oracle folder on the Sage SalesLogix media.

4. To load the script into the Query section, click Open.

5. To run the script, click Execute.

After creating the database login, you must import the database structure. Do not change the sysdba password before importing the database structure. If you change the password prior to importing the database structure, the import fails.

Importing the Database Structure

Sage SalesLogix uses a DMP file to import the database structure into the Oracle database.

The DMP file copies the default views, pick lists, reports, plugins, and other system information to the Oracle database. The DMP files are located in the Database\Oracle folder on the Sage SalesLogix media.

The SLX_Blank.dmp file creates the blank Sage SalesLogix database. To create an evaluation database, run the SLX_Eval.dmp file.

Before importing the database structure, do the following:

• If running Oracle on UNIX, FTP the DMP file(s) to the Oracle Server.

• If running Oracle on Windows, copy the DMP file(s) to the Oracle Server.

To import

1. On the Oracle Server, open a command window.

2. Type imp USERID='sys/sys_password@database_instance_name AS SYSDBA' fromuser=sysdba touser=sysdba grants=n statistics=none ignore=y file=absolute path to the location of the .dmp file\SLX_Blank.dmp.

For example, if the database instance name is SLX, and it is located in the

C:\Oracle\Databases folder, the command line would be imp USERID=’sys/sys_password@SLX AS SYSDBA’ fromuser=sysdba touser=sysdba grants=n statistics=none ignore=y:

FILE=C:\Oracle\Databases\SLX_Blank.dmp

Indexing the Database

After importing the database using the DMP file, you must create Oracle-centric indexes in the appropriate tablespace. The CreateOracleIndexes file used to create the indexes can be modified as your database changes to drop or rebuild indexes as necessary.

The CreateOracleIndexes.sql script can be run as the sys user or the Sage SalesLogix user “sysdba”.

To index

1. Open Oracle SQL *Plus Worksheet or SQL Developer.

2. On the File menu, click Open.

3. Browse to the CreateOracleIndexes.sql script.

The script is located in the Database\Oracle folder on the Sage SalesLogix media.

4. To load the script into the Query section, click Open.

Sage SalesLogix Implementation Guide v8.0

127

Creating a Database for Oracle

5. To run the script, click Execute

Adding Database Views

After indexing the database, you must add database views for Sage SalesLogix. The

CreateOracleViews script creates new views to improve performance. Running this script allows you to create the necessary Sage SalesLogix views without extra permissions for the sysdba user.

The CreateOracleViews.sql script must be run as the sys user using the sysdba role.

To add

1. Open Oracle SQL *Plus Worksheet or SQL Developer.

2. On the File menu, click Open.

3. Browse to the CreateOracleViews.sql script.

The script is located in the Database\Oracle folder on the Sage SalesLogix media.

4. To load the script into the Query section, click Open.

5. To run the script, click Execute.

The next step...

If you are completing task 5 of the “Required Tasks” checklist, refer to

Chapter 3, “Installing

Sage SalesLogix”

to install Sage SalesLogix.

128 Sage SalesLogix Implementation Guide v8.0

Appendix B

Configuring Intellisync for SalesLogix

Before beginning this chapter...

Install Sage SalesLogix Network Clients as described in

Chapter 7, “Installing Network Clients”

or configure the Web Client as described in Chapter 8, “Configuring the Web Client”

. In addition,

ensure users have created and assigned the SyncSalesLogix group as detailed on page 73 and

page 83 .

Intellisync for SalesLogix allows you to fully synchronize contacts, appointments, and To-Do’s with Microsoft Outlook. Intellisync for SalesLogix is deployed as a Web portal and configured on each client computer.

Depending on your installation, one or more of the following Intellisync for SalesLogix portals are required:

• Main Office portal - All Sage SalesLogix Network users at the main office connect to this portal. The portal is automatically deployed if you selected the IntelliSync Web Portal check box and Create Web Site option in the Administrative Tools and Servers installation

(

page 32 ). If you did not select these options, you must manually deploy the portal. The

Main Office portal requires IIS to host the portal.

• Remote Office portal - All Network and Web Client users at the Remote Office connect to this portal. You must open the Application Architect at the main office and manually deploy the Intellisync for SalesLogix portal. The Remote Office requires IIS to host the portal.

• Remote user portals - All Remote users connect to their own Intellisync for SalesLogix portal located on the remote computer. The portal is automatically deployed for Sage

SalesLogix Remote Client users. However, you must deploy an Intellisync for SalesLogix portal to each Offline Web Client. Remote users require the Sage SalesLogix Personal

Web Server to host the portal. The Sage SalesLogix Personal Web Server is included in the Sage SalesLogix Client installations (Remote User and Offline Web Client).

Setting the Provider Alias

By default, Sage SalesLogix sets the Intellisync for SalesLogix alias connection setting to

SLXRemote. Before users can connect to the Intellisync for SalesLogix portal, you must change the provider alias setting in the configuration file to the correct alias for your company.

To set

1. On the Administrative Workstation, browse to ...\inetpub\wwwroot\SlxIntellisync.

This folder is located on the computer on which you installed the Administrative Tools and

Servers including Intellisync for SalesLogix.

2. Open the connection.config file in a text editor (such as Notepad).

3. Modify the Initial Catalog value to the provider alias for your production database. For example, Initial Catalog=SalesLogix.

4. Save and close the file.

5. Reset IIS.

Sage SalesLogix Implementation Guide v8.0

129

Configuring Intellisync for SalesLogix

If the Web Server (any portal) has not been accessed or initialized, an IIS Reset is not necessary. If the Web Server has been accessed or initialized (the w3wp.exe process is running on the server), an IIS Reset is required for the Intellisync Web portal to update with the changes in the configuration file.

Configuring Intellisync for SalesLogix on the Web

If your installation does not include the Web, proceed to “Configuring Intellisync for SalesLogix” on page 132 to configure your Network Client computers.

Installing Intellisync for SalesLogix on Web Client Computers

If you have Web Client users running Intellisync for SalesLogix, each Web Client user must install the Intellisync for SalesLogix application. Intellisync for SalesLogix is included in the installation for Network, Remote, and Offline Web Clients. However, Web Client users accessing the Host database and Web Client users accessing a Web Remote Office must install Intellisync for SalesLogix separately.

Ensure the SlxIntellisync portal is deployed to Remote users and Remote Offices before installation.

To install

1. Log on to the computer where you deployed the Intellisync for SalesLogix portal. Typically this is Administrative Workstation or Web Host computer.

2. Browse to the folder where you deployed the SlxIntellisync portal.

You can verify the server name and base directory in the Application Architect Intellisync

Portal Target Settings (for IIS and Remote Offices).

3. In the portal deployment folder (the folder identified in step 2), create a new folder

named Downloads.

4. On the Sage SalesLogix media, browse to the Installs > Redist folder and select the

IntellisyncInstall.zip file.

5. Copy the IntellisyncInstall.zip file and paste it to the Downloads folder created in

step 3.

When the .zip file is copied to this folder, a link appears in the portal that users can access to download the Intellisync for SalesLogix application.

6. Repeat steps 2-5 on all Web Remote Office computers.

7. Distribute the Intellisync for SalesLogix portal URL to all Web Client users.

By default, the Sage SalesLogix installations create the portal in

\\MachineName:port\SlxIntellisync.

8. Instruct users to click the link to download the Intellisync for SalesLogix application.

130 Sage SalesLogix Implementation Guide v8.0

Configuring Intellisync for SalesLogix

Deploying the Intellisync for SalesLogix Portal to the Remote Office and Offline Web Clients

The Sage SalesLogix installations create and deploy the Intellisync for SalesLogix portal for the main office, Network, and Web Client users. Use the following steps to deploy Intellisync for SalesLogix to the Remote Office and to Offline Web Clients. After deployment, Offline Web

Client users must access the site to install the Intellisync for SalesLogix application.

If you did not create the Intellisync for SalesLogix Web site during installation, you must deploy the SlxIntellisync portal to the appropriate servers using the Application

Architect. See the “Deploying the Intellisync for SalesLogix Portal” topic in the

Application Architect Help for instructions.

To deploy

1. On the Application Architect View menu, click Deployment Explorer.

2. Expand Deployments, and then double-click Intellisync Portal.

3. In the Name box, type a name for the deployment.

4. In the Description box, type a description for the deployment.

5. In the Deployment Targets tree view, right-click Deployment Targets, and then click

Add Target(s).

The Select Target(s) dialog box opens.

6. Under Select Deployment Target(s), select one of the following:

• Remote Users

• Remote Office

7. Under Select Portal(s), select SlxIntellisync.

8. Click OK.

9. In the Deployment Targets tree view, click one of the following (based on your selection in step 6):

• Remote Users: The Remote User Target Settings appear.

• Remote Office(s): The Remote Office Target Settings appear.

10. Select the Remote users or Offices for which you want to deploy the Intellisync for

SalesLogix portal.

11. On the SlxIntellisync tab: a. In the Virtual Directory box, type the alias name for the virtual directory.

b. In the Port box, type the listening port on the remote.

• Remote users: The Sage SalesLogix Personal Web Server requires its own port for each portal instance. The port for each portal must be unique.

• Remote Offices: The default port is 3333.

c. Ensure the Deploy Portal check box is selected.

This indicates the portal is active and should be deployed.

12. Click Save.

13. Click Deploy.

14. Note the portal information.

15. Run a synchronization cycle at the main office to send the portal to remotes.

16. Instruct each Offline Web Client and\or Remote Office to run a synchronization cycle to receive the portal.

Sage SalesLogix Implementation Guide v8.0

131

Configuring Intellisync for SalesLogix

If your company is using Intellisync for SalesLogix, you must configure synchronization preferences. This configuration must be completed on each user’s computer. The following steps outline the recommended synchronization settings between Microsoft Outlook and

Intellisync for SalesLogix.

The instructions for configuring Intellisync for SalesLogix are available to users in the Sage SalesLogix Client Help and Web Client Help. Refer users to the

“Configuring Intellisync for SalesLogix” topic for the information referenced in this chapter.

Distributing Connection URLs

Before configuring Intellisync for SalesLogix, ensure each user has the correct connection

URL. The connection URL is the path to the Intellisync for SalesLogix portal for that user. For

Network users, the path is to the Intellisync for SalesLogix portal on the Host. For Remote

Office users, the portal is typically located on the Remote Office computer. For Remote users, the portal is located on their local machine.

If the Sage SalesLogix installations automatically created your Intellisync for SalesLogix Web site and portals, distribute the following connection URLs to users. If you manually deployed the Web site, distribute your specific connection information as defined in Application

Architect.

• Main Office Network and Web Client users -

http://server:port/SlxIntellisync/Default.aspx

The server is the Administrative Workstation machine name and port is the port number you designated during the Administrative Tools and Servers installation. By default, the

Sage SalesLogix installation defaults the port to 3333. If 3333 is not available, the next open port is used.

• Remote Office Network and Web Client users -

http://server:port/SlxIntellisync/Default.aspx

The server is the Remote Office machine name and port is the port number you designated during the Remote Office installation. By default, the Sage SalesLogix installation defaults the port to 3333. If 3333 is not available, the next open port is used.

• Remote users - http://localhost/SlxIntellisync/Default.aspx

By default, the port is 8087.

Configuring Synchronization Preferences

Use the Intellisync for SalesLogix application on each user’s computer to set the connection to the Intellisync for SalesLogix portal and define the information to synchronize between

Sage SalesLogix and Microsoft Outlook.

To configure

1. On the Start menu, point to Programs, point to Sage SalesLogix, point to Intellisync

for SalesLogix, and then click Intellisync for SalesLogix.

The Intellisync for SalesLogix dialog box opens.

2. Click Setup.

3. In the User ID box, type your Sage SalesLogix user name.

4. In the Password box, type the corresponding password.

5. In the Connection URL box, type the path to your Intellisync for SalesLogix portal. If necessary, contact your system administrator for the portal location.

132 Sage SalesLogix Implementation Guide v8.0

Configuring Intellisync for SalesLogix

6. Click Application Setup.

7. On the Setup screen, select the type of data you want to synchronize (for example,

Appointments), and then click Setup Wizard.

8. On the Desktop Application screen, select Microsoft Outlook, and then click Next.

9. On the What to Sync screen, select All Intellisync for SalesLogix applications that

are supported by Microsoft Outlook, and then click Next.

10. On the How to Sync screen, select Two way sync, and then click Next.

11. On the When To Sync screen, select when you want synchronization to occur.

12. On the Microsoft Outlook Connection Information screen, select your Outlook user profile.

13. Complete additional screens as appropriate for the type of information you are synchronizing.

a. On the Microsoft Outlook options for ToDo’s screen, select Transfer all items.

This options synchronizes all active, non-completed, and completed ToDo’s.

b. On the Microsoft Outlook options for Appointments screen, select Transfer

only future items.

14. On the Intellisync for SalesLogix Connection Information screen, verify your Sage

SalesLogix user ID, password, and the connection to your Intellisync for SalesLogix portal, and then click Next.

15. Click Finish.

16. Click Close.

Adding Outlook Contacts to Sage SalesLogix

To add Outlook contacts to Sage SalesLogix, create the SyncSalesLogix category in Outlook, and then assign it to the appropriate contacts. When a user synchronizes using Intellisync for

SalesLogix, any changes made to Outlook contacts are sent to Sage SalesLogix.

To create

1. Open Outlook, and then open the Contacts view.

2. On the Edit menu, click Categories, and then click Master Category List.

3. In the New category box, type SyncSalesLogix. Capitalize it exactly as shown.

4. Click Add, and then click OK.

5. In the Categories dialog box, click OK.

6. From the Contacts view, double-click a contact that you want to synchronize, and then click Categories.

7. In the Categories dialog box, select SyncSalesLogix, and then click OK.

8. You can continue assigning the SyncSalesLogix category to Outlook contacts by

repeating steps 6 and 7.

The SyncSalesLogix filter is used when synchronizing contacts. It is not necessary to use this filter when you are exporting contact information to Outlook.

After completing this chapter...

You have completed the “Intellisync for SalesLogix Tasks” checklist.

Sage SalesLogix Implementation Guide v8.0

133

Configuring Intellisync for SalesLogix

134 Sage SalesLogix Implementation Guide v8.0

Appendix C

Configuring Accounting Integration

Before beginning this chapter...

Install and configure Web components as described in Chapter 5, “Installing the Web

Components”

and

Chapter 8, “Configuring the Web Client” .

Accounting Integration allows you to share information between Sage SalesLogix and any accounting system that supports the Sage CRM ERP Contract. Sage SalesLogix Web Client users can view open sales orders, customer invoices, customer payments, open invoices, and their corresponding details. This feature is not available to Sage SalesLogix Windows or

Mobile Client users.

Sage SalesLogix supports the synchronization of information between Sage SalesLogix and supported accounting applications. However, depending on your accounting system, some of this information may not be available. Each accounting system determines the record types they will synchronize with Sage SalesLogix. Depending on your integration, you may be able to synchronize all or some of the following:

• Accounts/Trading Accounts

• Addresses

• Contacts

• Contracts/Invoices

• Opportunities/Sales Quotes

• Prospects/Customers

• Sales Orders

Synchronization of information in real-time requires an internet connection. When using Accounting Integration on the Offline Web Client, data in real-time data views will be current as of the last time the Client connected with the host database.

Accounting Integration Features

When you integrate Sage SalesLogix with an accounting system, you can transfer information between systems so that your front-office and back-office systems work together and contain the same data. Users can:

• View current pricing and discounts in Sage SalesLogix with information pulled from the accounting system.

• Use price lists and products that originate in the accounting system.

• Submit sales orders from Sage SalesLogix to the accounting system and receive confirmation when the order has posted.

• View warehouse information and product availability from Sage SalesLogix.

• View order information such as price, discounts, shipping dates, and more in real-time.

Sage SalesLogix Implementation Guide v8.0

135

Configuring Accounting Integration

To configure Accounting Integration you must enable endpoints, start the service, import records, and configure users and roles.

Caution: Configuring Accounting Integration modifies the connection to the Sage

SalesLogix product table so it is no longer possible to add products to an open opportunity. If you are using these instructions to add Accounting Integration to an existing Sage SalesLogix 8.0 installation, make any necessary modifications to open opportunities first.

Running the Account Integration Phone and E-mail Update Utility

Before setting up your Accounting Integration endpoints, you must run the Account Phone

Number and E-mail record update utility. This utility creates a record in the

ERPPHONENUMBER or ERPEMAILADDRESS table for each phone number and email column in either of the ACCOUNT or CONTACT tables. Those records are mapped back to the original entity column where they originated.

Windows Authentication must be configured for the administrative user before running the Account Integration Phone and E-mail Update utility.

For detailed steps, see the "Using Windows Authentication" topic in the

Administrator Help.

To run

1. On your Administrative Workstation, browse to the ICLegacyPhoneEmailUpdater.exe and ICLegacyPhoneEmailUpdater.config files.

By default the configuration files are in ...\Program Files\SalesLogix.

2. Double-click ICLegacyPhoneEmailUpdater.config to open the file in a text editor of your choice.

3. Scroll to the <connectionStrings> section and change the Initial Catalog value from

SALESLOGIX_EVAL to your database alias.

For example:

<connectionStrings> <clear/> <add name="Default" connectionString="Provider=SLXOLEDB.1;Persist Security Info=True;Initial

Catalog=MyDatabaseAlias;Data Source=localhost;Extended

Properties="PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSI

ZE=1;SVRCERT=12345;ACTIVITYSECURITY=OFF;TIMEZONE=NONE""/>

</connectionStrings>

4. Double-click ICLegacyPhoneEmailUpdater.exe to run the utility.

5. Click Create ERP Phone Records to create phone records.

6. Click Create ERP E-mail Records to create e-mail records.

7. Click the Close button.

Configuring Endpoints

Accounting Integration is enabled when the Sage SalesLogix endpoint and at least one target endpoint is configured and enabled. At least one endpoint must be active to share data between Sage SalesLogix and your accounting system.

To set

1. On the Sage SalesLogix Web Client Administration menu, click Integration Setup.

136 Sage SalesLogix Implementation Guide v8.0

Configuring Accounting Integration

2. In the SalesLogix Feed box, type the SData URL that Sage SalesLogix uses to share information between systems. Do one of the following:

• If your implementation does not use the default port (port 80), use format http://server:port/sdatavirtualdir/application/contract/operatingcompany/-/

• If your implementation uses port 80, omit the port number from the URL. The Sync

Service automatically strips the default port from the URL which causes matching issues and errors. Avoid this by using format http://server/sdatavirutaldir/application/contract/operatingcompany/-/

• Set application to slx.

• Set contract to gcrm.

• Set operatingcompany to - (Sage SalesLogix does not have an operating company).

3. In the User Name box, type the user name for the Sage SalesLogix database that the accounting system connects to.

4. In the Password box, type the password for the user name.

5. In the Display Name box, type the display name for the feed.

6. Click Save.

7. If necessary, select the Restrict account promotion to single accounting system option to limit your integration to Sage SalesLogix and one accounting system.

8. Click the Accounting Systems tab to configure the feed details for your accounting system(s).

9. Click Add.

10. Set the following values in the Setup Accounting Integration dialog box.

Box

Accounting Feed

User Name

Password

Test Feed

Display Name

Description/Action

Type the SData URL to the accounting system.

1. Do one of the following:

• For implementations that do not use the default port (port 80), use format http://server:port/sdatavirtualdir/application/cont

ract/operatingcompany/-/

• For implementations that use port 80, omit the port number from the URL. The Sync Service automatically strips the default port from the URL which will cause matching issues and errors.

Avoid this by using format http://server/sdatavirutaldir/appliation/contract/o peratingcompany/-/

2. Set application to your accounting application name.

For example, Sage1000.

3. Set contract to gcrm.

4. Set operatingcompany to the operating company in your accounting application that you are integrating with.

Type the user name used to log on to the account system.

Type the password for the corresponding user name.

Click to test and display the connection status.

Type a display name for the accounting system. This name displays in the Web Client when users are linking records between Sage SalesLogix and the accounting system.

Sage SalesLogix Implementation Guide v8.0

137

Configuring Accounting Integration

Box

Enables Synchronization,

Linking and Transacting

Filter By Resource

Description/Action

Select to enable this feed.

Select a resource type and click the Execute button to display schema differences in the grid. This feature compares the schema for the selected resource in the two integrated systems and returns any differences in string lengths. If string values do not match, use the Database

Manager or other application to modify the schema in one of the systems.

11. Click OK.

Comparing and Configuring Schema Differences

Sage recommends comparing the database schema in Sage SalesLogix with your accounting application schema to ensure data integrity. You can compare data for various resources to determine if differences in string lengths exist between systems.

This feature compares the schema for the selected resource in the two integrated systems and returns any differences in string lengths.

To compare

1. On the Web Client Administration menu, click Integration Setup.

2. On the Accounting Systems tab, click Edit for the enabled accounting system.

3. In the Setup Accounting Integration dialog box, use the Schema Differences section to find differences between systems.

a. In the Filter By Resource box, select the resource type.

b. Click Execute.

c. Review the differences in the grid.

d. Note any information that may cause data integrity issues. For example, an accounting system field may only accept three characters when the same field in

Sage SalesLogix accepts free text.

4. Repeat step 3 for all resource types.

5. Use the Database Manager or other application to modify the schema in one of the systems.

Configuring Matching Criteria

Use the Matching tab to set global default matching criteria for users creating links. These settings will apply to all users as they link accounts between Sage SalesLogix and your accounting system.

Sage SalesLogix has defined default matching criteria for accounts. To modify the criteria specific for your company, see the “Matching Tab” topic in the Web

Client help.

138 Sage SalesLogix Implementation Guide v8.0

Configuring Accounting Integration

Configuring the Accounting Integration Synchronization Service

The Accounting Integration Synchronization Service (Sage SalesLogix SData Sync Service) allows data transfer between Sage SalesLogix and your accounting system. The service must be started and set to run as automatic.

To configure

1. Make sure you configure and enable endpoints as detailed in “Configuring Endpoints” on page 136

before starting the service.

2. Review the Sage.SalesLogix.SyncEngineService.exe.config file to ensure the connection is defined correctly at the end of the file. The connection information should match the connection.config deployed to your Web site.

By default the configuration file is in ...\Program

Files\SalesLogix\Sage.SalesLogix.SyncEngineService.exe.config and the connection file is deployed to ...\inetpub\wwwroot\slxclient

3. On the Administrative Workstation, open Services.

4. Right-click the Sage SalesLogix SData Sync Service, and then click Properties.

a. In the Startup type box, select Automatic.

b. Set the service to log on and run as the WebDLL user.

Ensure you have enabled Windows Authentication for the WebDLL user. See

“Configuring the WebDLL User for Windows Authentication” on page 76 for details.

c. Click Start.

5. Click OK.

Exporting and Merging Records from your Accounting System

After configuring the integration endpoints and starting the synchronization service, you can export records from your accounting system to Sage SalesLogix. Any records imported into

Sage SalesLogix will be linked to the corresponding record in your accounting system. After exporting records, you should check for duplicate records.

The Check for Duplicates wizard compares records in Sage SalesLogix to determine if your data contains duplicates. The wizard creates a job containing possible duplicate data. You can use the job results to merge or remove duplicates.

To export and merge

1. Use the export tool provided by your accounting system to export the appropriate data into Sage SalesLogix.

2. On the Web Client Tools menu, click Check for Duplicates.

3. On the Select a Source screen: a. In the Select type of Job drop-down list, select the entity type for which you want to check for duplicates.

b. In the Group drop-down list, select the group of records within the selected entity type.

c. Click Next.

4. On the Search Options screen, select the filters you want the wizard to use when matching data.

If you select a value, the data in both records must be an exact match to be considered a duplicate.

5. (Optional) Click Advanced Match to set additional match options.

6. Click Next.

7. On the Review screen, verify your selections for this job.

Sage SalesLogix Implementation Guide v8.0

139

Configuring Accounting Integration

8. Click Submit.

9. Click the Job Number link to open the Check for Duplicates History Detail view and view any potential duplicates.

10. On the Potential Duplicates tab, click the Resolve link.

11. In the Duplicate Search Results section:

• Click the Merge link for the account with which you want to merge this record. Then, use the Merge Data dialog box to select the data you want to keep.

• Click Not a Duplicate if the record is not a duplicate and should be left as a separate record.

12. Return to the Check for Duplicates History Detail view and merge or mark records as not a duplicate for all records in the job.

Configuring User Roles

By default, users created in the Web Client are granted the Standard User role which allows access to accounts, contacts, opportunities, and other Sage SalesLogix records. When enabling Accounting Integration, you should assess the roles required for each user depending on the tasks they will perform.

Review the “What are Roles and Secured Actions?” topic in the Web Client help to determine what access is required for each of your Sage SalesLogix Accounting

Integration users and use the Roles view to assign and remove your user’s roles as appropriate.

After completing this chapter...

You have completed task 19 in the “Web Tasks”

checklist.

140 Sage SalesLogix Implementation Guide v8.0

Appendix D

Advanced Web Host Configuration

To maximize performance, you may need to scale your Web implementation. The Web components can be scaled at any time after your initial implementation. This appendix explains how to scale the implementation and includes instructions for completing a manual configuration.

Scaling the Web Implementation

If many users access the client(s) simultaneously, you may need to add virtual servers or secondary Web Hosts to improve performance. A virtual server uses all of the same components as the Web Host, but exists on a different port (for example, a different Web site) on the same machine. Secondary Web Hosts are separate, physical Web servers.

In addition to the number of concurrent users, other factors, including database size, Server hardware, and Web Host hardware, influence performance. The need for additional virtual servers or Web Hosts must be individually evaluated for each implementation.

To add a virtual server

1. Manually configure the Web site using an available port. See one of the following as appropriate.

•

“Configuring Web Hosts/Virtual Servers: Windows 2003 Server” on page 142

•

“Configuring Web Hosts/Virtual Servers: Windows 2008 Server” on page 143

To install a secondary Web Host

1. Follow the instructions in

“The WebDLL User” on page 15

2. Install the Web Host as detailed in

“Installing the Web Host” on page 49 .

3. Ensure that the secondary Web Host has network access to the primary Web Host so that the necessary HTML and JavaScript files are available.

4. In each user’s browser, make the Web site a Trusted site with the Default Level of security (Low).

Monitoring Active Thread Count

The recommended default thread setting is 32, and in most cases, it should not be necessary to modify this setting.

Sage SalesLogix does not recommend lowering the default thread setting unless server responses are slow because of processing demands, and does not recommend raising the default thread setting, except in rare cases.

For example, it may be helpful to raise the default thread setting if you are experiencing random 500 errors from IIS. It may also be helpful to raise the default thread setting in situations where many long-running, low-intensity actions are being performed by a user.

For best performance, create another Web site (virtual server) on the same machine or on a different machine rather than raising the default thread setting.

To monitor active thread count (ISAPI connections) on your Web Host after you complete the implementation, use the Sage SalesLogix counters in Microsoft System Monitor.

For more information, refer to

“Monitoring Web Host Performance” on page 145

Sage SalesLogix Implementation Guide v8.0

141

Advanced Web Host Configuration

Configuring Web Hosts/Virtual Servers: Windows 2003 Server

If you use Windows 2003 Server, and you would prefer to manually create a Web site and virtual directories, follow the instructions in this section.

Creating the Web Site(s)

To enable users to access the Web Client, create a Web site in IIS for each Web Host and virtual server.

To create

1. Use the IIS wizard to create each Web site with the following settings: a. TCP port - Any available port greater than 1024.

Port numbers 1024 and less are reserved by Microsoft.

b. Path to your home directory - C:\inetpub\wwwroot.

This is the default setting. You have the option to change the default path.

c. Access Permissions:

• Select Read access.

• Clear Run scripts.

All other default settings in the wizard are acceptable.

2. Right-click the name of each site, and then click Properties. Set the following options:

Tab

Web Site

Home

Enabling the Active Server Pages Web Service Extension

To ensure the Sage SalesLogix Web components run correctly, you must enable the Active

Server Pages Web service extension. By default, this extension is disabled when it is installed.

To enable

1. In IIS, click the Web Service Extensions folder.

2. In the details view, select Active Server Pages, and then click Allow.

142 Sage SalesLogix Implementation Guide v8.0

Advanced Web Host Configuration

Configuring ASP.NET

Microsoft .NET Framework with ASP.NET enabled is required on the Web server. If a previous version of Microsoft .NET Framework with ASP.NET has been installed, ensure that ASP.NET is selected in IIS after you install the Web components. Select ASP.NET in the ASP.NET tab.

If you install Microsoft .NET Framework before you install IIS, ASP.NET is not installed.

See

“The WebDLL User” on page 15

for the steps to configure ASP.NET.

Configuring Application Pool Permissions

You must configure the Application Pool for your Sage SalesLogix Web site to ensure you have sufficient permissions to start the Sage SalesLogix OLE DB Provider. The Web site is named SalesLogix, unless you changed it during Web Host installation.

See

“Configuring Application Pool Permissions” on page 58 for detailed configuration steps.

Using Application Pools (Optional)

An application pool is a configuration that links one or more applications to a set of one or more work processes. Because each application in an application pool is separate from other applications by work process boundaries, an application in one application pool is not affected by problems caused by applications in other application pools. This means that each pool can be restarted without affecting other applications.

By default, an application pool named SalesLogix is created when you install the Sage

SalesLogix Web Host. Moving Sage SalesLogix to an application pool is optional; it is not required to run Sage SalesLogix Web components.

Configuring Web Hosts/Virtual Servers: Windows 2008 Server

If you use Windows 2008 Server, and you would prefer to manually create a Web site and virtual directories, follow the instructions in this section.

Creating the Web Site(s)

To enable users to access the Web Client, create a Web site in IIS for each Web Host and virtual server.

To create

1. Use the IIS wizard to create each Web site with the following settings: a. TCP port - Any available port greater than 1024.

Port numbers 1024 and less are reserved by Microsoft.

b. Path to your home directory - For example, C:\inetpub\wwwroot.

c. Pass-through Authentication:

• Click Connect As, and then click Specific User. Enter the credentials for your

WebDLL user. For example, domain\WebDLL.

All other default settings in the wizard are acceptable.

Sage SalesLogix Implementation Guide v8.0

143

Advanced Web Host Configuration

2. Right-click the name of each site, and then click Properties. Set the following options:

Tab

Web Site

Configuring Application Pool Permissions

See “Configuring Application Pool Permissions” on page 58 for detailed configuration steps.

Using Application Pools (Optional)

By default, an application pool named SalesLogix is created when you install the Sage

SalesLogix Web Host. Moving Sage SalesLogix to an application pool is optional; it is not required to run Sage SalesLogix Web components.

Using Firewalls

If your company uses firewalls, you must open certain ports to enable the Web components to function correctly. You can set up your Web Host(s) and Web Reporting Server in a

Demilitarized Zone (DMZ) as long as the ports for the Web sites are open to the outside.

Internally, the Web Host(s) must be able to access the appropriate ports on the Database

Server, Sage SalesLogix Server, and the server where the Documents and Library folders reside (typically the Synchronization Server). The Web Reporting Server must also be able to access the appropriate ports on the Database Server and the Sage SalesLogix Server.

Assuming your Sage SalesLogix Web servers sit between two firewalls (one connecting to the outside and the other to your LAN), use the following table as a guideline.

Server

Database Server

Port

1433 (MS SQL)

Open on

Inside firewall

144 Sage SalesLogix Implementation Guide v8.0

Advanced Web Host Configuration

Server

Web Host

Port

1706 (OLEDB)

1025 and/or other higher (HTTP port configured for each Web site)

Open on

Inside firewall

Outside firewall

Web Reporting Server

11211 (required for the SalesLogix Cache

Server)

1706 (OLEDB)

If using Domain Name Service (DNS), also open these:

135 (TCP/UDP - Remote Procedure Calls)

Inside firewall

Synchronization Server*

(Shared Documents &

Library folders)

1025 or other higher (port configured for Web

Reporting)

Outside firewall

NetBIOS

138 (UDP)

139 (TCP)

Inside firewall

137 (TCP - DNS)

445 (TCP/UDP - DS)

*The Documents and Library folders may be located on another machine, such as the

Administrative Workstation (for example, if your organization does not use synchronization).

Be sure to open the ports on the correct machine.

RPC Communication

When deploying the VFS from a Sage SalesLogix server (running Application Architect) to a separate Web Host, the Windows Firewall must be configured to ensure the proper Remote

Procedure Call (RPC) communication.

To configure

1. Open Windows Firewall and click Advance Settings.

2. Create a new inbound rule and select “Remote Administration”

3. Click Next

4. Select the check boxes for all the of the available rules.

5. Click Next.

6. Select Allow the Connection and then click Finish.

Monitoring Web Host Performance

You can install the Sage SalesLogix counters for Microsoft System Monitor to measure the performance of your Web Host(s). The monitor can help you identify peak times, shortcomings, and bottle necks.

To monitor

1. Open the Performance Monitor:

• (Windows 2003 Server) From the Start menu, point to Programs, point to

Administrative Tools, and click Performance. Then, select System Monitor.

Sage SalesLogix Implementation Guide v8.0

145

Advanced Web Host Configuration

• (Windows 2008 Server) From the Start menu, point to Programs, point to

Administrative Tools, and click Reliability and Performance. Then, select

Performance Monitor.

The Performance snap-in appears in the Microsoft Management Console.

2. Click the Add button.

The Add Counters dialog box appears.

3. Select the Use local computer counters option.

4. In the Performance object box, select Web Service.

5. Select the All counters option.

-or-

Select the Select counters from list option. Then, press CTRL and click each counter you want to use.

For more information on the function of each counter, select the counter and click Explain.

A counter definition appears.

6. Select the Select instances from list option, and then click SalesLogix.

7. Click Add, and then click Close.

The Performance Monitor Chart appears, and you can view the activity of your server.

For more information on using Performance Monitor, refer to the Performance Monitor

Help or the Microsoft MDSN Web site.

146 Sage SalesLogix Implementation Guide v8.0

Appendix E

Manually Configuring IIS for Web Host

The Web Host installation automatically sets up IIS configuration. If you prefer to manually set up your web site instead of using the Web Host install, you must address the following system prerequisites before continuing with your Sage SalesLogix installation.

Note

You do not need to apply these manual settings if you created your web site using the

Sage SalesLogix Web Host install.

• ASP.NET 4.0, 32-bit version. For Web installations running on 64-bit versions of Windows

2003, you must enable the 32-bit mode.

• IIS 6 - To enable the 32-bit version of ASP.NET 4.0, open a command prompt (Start

> Run > cmd) and type the following commands:

• cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET

W3SVC/AppPools/Enable32bitAppOnWin64 TRUE

• %SYSTEMROOT%\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis

-i

• cscript %SYSTEMROOT%\Windows\System32\iisext.vbs /EnFile

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll

• %SYSTEMROOT%\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis

-s W3SVC/2/root/slxclient

• %SYSTEMROOT%\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis

-s W3SVC/2/root/sdata

• %SYSTEMROOT%\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis

-s W3SVC/2/root/processhost

After running the commands, make sure the status of ASP.NET version 4.0.30319(32bit) is set to “Allowed” in the Web service extension list in IIS Manager.

If the ASP.NET version 4.0.30319(32-bit) is not visible, restart your computer to refresh the service extension list.

• IIS 7 - Use IIS Manager to enable 32-bit applications in the Sage SalesLogix

Application pool.

• In IIS Manager, open the Sage SalesLogix Application Pool Basic Settings. In the

.NET Framework version box, select .NET Framework version 4.0.30319.

• In the Managed pipeline mode box, select Integrated.

• Open the Application Pool Advanced Settings. Set “Enable 32-Bit Applications” to

True.

Sage SalesLogix Implementation Guide v8.0

147

Manually Configuring IIS for Web Host

148 Sage SalesLogix Implementation Guide v8.0

Appendix F

Advanced Web Reporting Configuration

By default, the Web Reporting installation performs most configuration necessary for the

Sage SalesLogix Web Reporting site on an available port greater than 1024. If you prefer to perform this configuration manually, follow the instructions in this appendix.

Manually Configuring Web Reporting

To enable users to access reports over the Web, you must create a Web site in IIS.

To create the Web site in IIS6

1. Use the IIS Wizard to create the Web site with the following settings: a. TCP port - Any available port greater than 1024.

Port numbers 1024 and less are reserved by the Microsoft operating system. Make a note of the port number you use for the site; it is required to complete Web Reporting configuration in Application Architect. b. Path to your home directory - C:\inetpub\wwwroot\ slxwebrpt.

c. Access Permissions:

• Select Read access.

• Clear Run scripts.

All other default settings in the wizard are acceptable.

2. Right-click the name of the site, and then click Properties. Set the following options.

Tab Step(s)

Home Directory Clear the Index this

resource check box.

Appendix G

Automating Client Installations

Automating Client installations allows you to deploy customized installations of the Sage

SalesLogix Client to Network and Remote users. Using automated installations, the system administrator can create a configuration file containing all the desired Sage SalesLogix settings and send it to users. Once received, the user can bypass the steps in the Installation

Wizard and use the custom configuration file to install Sage SalesLogix.

There are several advantages to using automated installations. You can:

• Enforce the use of specific settings for all users.

• Specify different configurations for different users.

• Install Sage SalesLogix with minimal user input.

When installing Sage SalesLogix using an automated installation, third-party

(prerequisite) applications are not installed. Third-party applications must be installed separately. Installations for these applications can be found in the Redist folder on the

Sage SalesLogix media.

Customizing the Sage SalesLogix Configuration File

You can modify the standard configuration file created using the Build Network Client Install or Build Remote Client Install on the Sage SalesLogix media or create your own configuration

file. Creating the standard configuration file is detailed on page 69

The configuration file has an .ini file format and contains the following sections:

Features Contains name/value pairs in the format “<FeatureName>=<Value>”. Valid values are “YES” and “NO”. If a feature is not listed, the default value is YES.

Properties Contains name/value pairs for any Windows Installer property that you want to set. Standard Windows Installer properties and values can be found in the Microsoft Platform

SDK documentation.

To customize

1. Open the standard configuration file or create a new configuration file. The standard configuration file name is the same as the corresponding .msi file. For example, SalesLogix

Network Client.cfg.

2. Customize the configuration file features and properties as appropriate using the

information in the “Understanding Features and Properties” section.

3. To deploy the configuration file to users, copy the entire directory structure of the Sage

SalesLogix Client installation to a shared network folder.

Ensure the .cfg file is in the same folder as the .msi file.

4. Instruct users to run the SalesLogix Network Client.msi file on their computer.

The .msi file reads the configuration file and installs Sage SalesLogix according to your custom settings.

Sage SalesLogix Implementation Guide v8.0

151

Automating Client Installations

Understanding Features and Properties

Use the following settings to customize the Sage SalesLogix Network Client or Sage

SalesLogix Remote Client configuration file.

Features

Use the Features section to determine the components you want to install on the Client computer. The following are the Sage SalesLogix Client install features:

Feature Name

MailMerge

ImportWizard

MailClient

NetForm

ClientHelp

ImportWizHelp

SpeedSearchHelp

Documentation

Descriptive Name

MailMerge

Import Wizard

Mail Client

.Net Extensions

Client Help

Import Wizard Help

SpeedSearch Client Help

Documentation

Properties

The following properties can be set in the configuration file:

Property

BROWSER

Description

Determines whether the install was launched from the browser.

Values

• “Yes” if the installation was launched from the browser

(or you want it to think that it was).

• “No” if the installation was launched by some other means. This is the default.

• “CHECKED” installs

Intellisync for SalesLogix.

INSTALLINTELLISYNC Determines whether to install

Intellisync for SalesLogix.

Database Connection Properties

The installation can set a default database connection if the appropriate properties are set.

SLXDBSERVERPORT The port number that the Sage

SalesLogix Server is listening on.

“1706”. This is the default value.

SLXDBSERVER

SLXDBSERVERALIAS

The name or TCP/IP Address of the Sage SalesLogix Server.

The Alias that will be used for this connection.

Install Helper Files Path Properties

RTFFILEPATH The String value containing the fully qualified path of the License

File.

152 Sage SalesLogix Implementation Guide v8.0

Automating Client Installations

Property

MSDEPATH

READMEFILE

Description

The String value containing the fully qualified path of the

Microsoft SQL Express installation path.

The String value containing the fully qualified path of the readme file.

Values

Microsoft SQL Express Related Properties

The following properties can be set in the configuration file and are passed to the Microsoft

SQL Express installation:

INSTANCENAME A string containing the desired name of the Microsoft SQL

Express instance that is being installed.

SAPWD A string containing the password for this Microsoft SQL Express instance. The default value is

“SLXMa$t3r”.

Example Configuration File

The following is an example of the Features section in the SalesLogix Network Client.cfg file:

[Features]

NetForm=NO

The following is an example of the Properties section in the SalesLogix Network Client.cfg file:

[Properties]

BROWSER=Yes

SLXDBSERVERPORT=1706

SLXDBSERVER=SalesLogix

SLXDBSERVERALIAS=SalesLogix_Eval

RTFFILEPATH=\\<SomeServer>\<SharedFolder>\

MSDEPATH=\\<SomeServer>\<SharedFolder>\SQLExpress\Setup.exe

INSTANCENAME=SalesLogix

SECURITYMODE=SQL

DISABLENETWORKPROTOCOLS=0

READMEFILE=\\<SomeServer>\<SharedFolder>\

Sage SalesLogix Implementation Guide v8.0

153

Automating Client Installations

Customizing the Administrative Tools and Servers

Configuration File

The following Feature names can be used to customize the Administrative Tools and Servers installation. This may be necessary if you have multiple Administrative users and you want to deploy only specific applications to designated Administrative users.

Feature Name

SalesLogixServer

SyncServer

SpeedsearchServer

Administrator

ApplicationArchitect

Architect

Utilities

NetForm

MailMerge

SyncEngineService

Descriptive Name

SalesLogix Server

Synchronization Server

SpeedSearch Server

SalesLogix Administrator

Application Architect

Architect

Administrative Utilities

.Net Extensions

MailMerge

SalesLogix SData Sync Server

154 Sage SalesLogix Implementation Guide v8.0

Appendix H

Silent Installs

Silent installs allow you to install Sage SalesLogix components without any visible interface interaction, using command line prompts.

Commands and Options

The following table shows the basic MSIEXEC commands and options to use to install the

Sage SalesLogix components from the command prompt.

For a complete list of MSI options, run the following at the command prompt:

> msiexec /?

Feature Name

OLEDB Provider

Administrative

Tools and Servers

Web Host

Web Reporting

Remote Office

Server

Network Client

Network Remote

Client

Offline Client

Command Line Script

> msiexec /i "Sage SalesLogix OLE DB Provider.msi"

ALLUSERSPROFILE="%ALLUSERSPROFILE%" /qb+

> msiexec /i "Sage SalesLogix Admin Tools and Servers.msi"

ALLUSERSPROFILE="%ALLUSERSPROFILE%"

SLXDBSERVER=<YOUR_SERVER_NAME>

/L*v <PATH><LOG FILE> /qb+

> msiexec /i "Sage Saleslogix Web Host.msi"

ALLUSERSPROFILE="%ALLUSERSPROFILE%"

SLXDBSERVER=<YOUR_SERVER_NAME> /L*v <PATH><LOG FILE>

/qb+

> msiexec /i "Sage SalesLogix Web Reporting.msi"

ALLUSERSPROFILE="%ALLUSERSPROFILE%" /L*v <PATH><LOG

FILE> /qb+

> msiexec /i "Sage Saleslogix Remote Office.msi"

ALLUSERSPROFILE="%ALLUSERSPROFILE%" /L*v <PATH><LOG

FILE> /qb+

> msiexec /i "Sage Saleslogix Network Client.msi"

ALLUSERSPROFILE="%ALLUSERSPROFILE%" /L*v <PATH><LOG

FILE> /qb+

> msiexec /i "Sage Saleslogix Remote Client.msi"

ALLUSERSPROFILE="%ALLUSERSPROFILE%" /L*v <PATH><LOG

FILE> /qb+

> SlxOfflineClientSetup.exe /s /v"/qn /L*v <PATH><LOG FILE>"

Desktop Integration

Note

Change “C:\Program Files\<installationfolder>\” to your specific installation path.

For Desktop Integration, command line installs only work with Internet Explorer.

Complete SlxDesktopIntegrationSetup.exe /s /v"/qn INSTALLDIR=\"C:\Program

Files\<installationfolder>\""

Sage SalesLogix Implementation Guide v8.0

155

Silent Installs

Feature Name

Custom - Office

Integration

Custom - Outlook

Integration

Command Line Script

SlxDesktopIntegrationSetup.exe /s /v"/qn

INSTALLDIR=\"C:\SLXDESKTOP\" ADDLOCAL=OfficeIntegration

SlxDesktopIntegrationSetup.exe /s /v"/qn

INSTALLDIR=\"C:\SLXDESKTOP\" ADDLOCAL=OutlookIntegration

Setting Properties on the Command Line

Power users can set certain properties on the command line.

For the installs that setup a database connection

CONFIGSLXDB="YES" ("YES" is the default. Flag to determine whether or not we update the Sage SalesLogix database.)

SLXDBUSER

SLXDBPSWD

SLXDBSERVER

SLXDBSERVERALIAS

SLXDBSERVERPORT

For the installs that can create a web site (for Web Host installs)

CREATEWEBSITE= "Yes" ("Yes" is the default. Flag to create a website.)

WEBSITENAME

WEBSITEDOMAIN

WEBSITEPORT

WEBSITEUSERNAME

WEBSITEUSERPSWD

For installs that pre-configure the Desktop Manager (Desktop Integration)

Using the INI file allows you to preconfigure the Desktop Manager settings for the user. This includes settings for the SData portal.

SlxDesktopIntegrationSetup.exe /s /v"/qn INIFILEPATH=<path_to_ini_file>

INSTALLDIR=\"C:\Program Files\<installationfolder>\""

Sample DesktopIntegrationModule.INI file:

[Settings]

SDataServer=http://MyTLDATASdataServer:80

PromptDuplicates=1

PromptContacts=0

PromptUnresolved=1

ShowHistoryDetails=0

ShowTrayNotifications=1

UseWindowsAuthentication=0

156 Sage SalesLogix Implementation Guide v8.0

Appendix I

Glossary

Account A company with which there is a current or potential business relationship. Accounts are owned by an individual user, a team of users, or everyone.

Administrative User A user who can perform tasks in the Administrator normally reserved for the system administrator.

Administrative Workstation The primary computer for administering and customizing Sage

SalesLogix. Usually, this is either the system administrator’s personal computer or a separate computer dedicated to Sage SalesLogix. The Administrator, Architect, Application Architect and Sage SalesLogix Client are usually installed on this computer.

Agents A method of scheduling reports, running Basic scripts, SQL scripts, etc., at intervals specified in the Administrator and Synchronization Server profile. Agents can be scheduled to run once or on a regular basis.

Application Architect A development environment containing the tools that allow developers to rapidly build, customize, manage, and deploy coded and codeless Web application solutions with one-click functionality.

Architect A development environment for creating customized views, menus, toolbars, and scripts for Sage SalesLogix.

Bundle A bundle is a group of plugins or other customizable components that are packaged together for installation as a unit, rather than having to move them one by one, or re-create them on every database. Bundles containing Network plugins (.sxb files) are installed using the Administrator. Bundles containing Web customizations (.zip files) are installed using the

Application Architect.

Concurrent Users The number of users accessing the database at any one time. In Sage

SalesLogix, a license type that enables multiple Sage SalesLogix users to share the same license. For example, if you have 40 users and 30 Concurrent User licenses, all 40 users can log on to Sage SalesLogix but only 30 can be logged on at the same time.

Contacts The prospects or customers in a company (account) that users interact with. Each account can contain one or more contacts.

Contract An agreement between your company and the customer to provide support services, either for free or for a specified fee.

Customer Service Customer Service allows designated users to track, qualify, and resolve customer questions and issues.

Database Manager Part of the Administrator and Architect that allows you to add, view, and delete tables and fields, as well as name indexes, in the Sage SalesLogix database.

Defect A record describing a problem in a product or process, or a feature request for a product or process.

Entity A business object, such as account or product that contains business rule methods and events, relationships, properties, and forms. Entities can also have other related entities associated with them, either through child relationships or extensions.

Form A Smart Part containing normal content, markup, and controls. A Web form is similar to Forms created in the Architect.

Host A term commonly used for a Sage SalesLogix database that supports both Network and

Remote users.

Infiles A folder in which the main office, or Remote users or Remote Offices, place sync files during synchronization.

Sage SalesLogix Implementation Guide v8.0

159

Glossary

Join A database operation that connects two database tables having a common field.

Library A central repository for company information. The library may include product information, policies and procedures, presentations, and so on.

Logging Folders Type body text here

Lookup Lookups enable users to search for information under any of the major families (for example; account, contact, ticket, and so on) that shares certain characteristics. Once a lookup is created, you can save the result as a group. Lookups can be managed from the

Architect or Administrator.

Offline Web Client Remote users that keep a subset of the main database on their computers (such as a laptop) and use synchronization to transfer changes between their system and the main office. Offline Web Client users make changes to their local database using the Web Client.

Outfiles A folder in which the main office places sync files during synchronization. Remotes obtain files from this location.

Opportunities Potential sales to accounts or contacts.

Package A group of related entities, forms, Smart Parts, templates, and aliases that are grouped together under a common name. Packages make it easier to manage your Web customizations.

Page A unit within a Web Portal. A page is a collection of workspaces.

Plugins Components that customize and add functionality to Sage SalesLogix. Plugins include views, processes, reports, templates, Visual Basic scripts, and SQL scripts.

Portal Represents a collection of Web pages.

PortalDeployments A folder in which the main office places deployed Web portals to be delivered to Remote users and Remote Offices.

Process Orchestration Allows you to create and configure process definitions and manage them with the Process Orchestration Host. Processes can be created for any entity, and any entity can be associated to multiple processes.

Processes A plugin that represents a series of tasks executed in a specific sequence over a set time period. Processes are used to perform repetitive tasks, implement a sales process, or provide an automated way of following up with customers. The Web components may only schedule processes and change process status.

Project A group of Web packages or plugins that are grouped together for easy retrieval and use.

Relational Database Management System (RDBMS) An engine and method of managing a database consisting of tables (rows and columns) and the relationships between those tables.

Remote Office A group of users that access a single Remote Office database directly. Unlike

Remote users, Remote Office users do not synchronize with the database at the main office.

Instead, the remote office regularly synchronizes with the database at the main office.

Sage SalesLogix Client An installation of the Sage SalesLogix Client where the user is directly connected to a network database to access and manage customer accounts, contacts, tickets, defects, activities, and related information.

Sage SalesLogix OLE DB Provider A client-side component that handles all database access and applies security.

Sage SalesLogix Personal Web Server Hosts the Sage SalesLogix portals on the Remote computer. The Sage SalesLogix Personal Web Server functions as a personal Web server for

Offline Web Clients.

160 Sage SalesLogix Implementation Guide v8.0

Glossary

Sage SalesLogix Remote Client Sage SalesLogix Client users that keep a subset of the main database on their computers (such as a laptop) and use synchronization to transfer changes between their system and the main office. They can also connect directly to the main office database using a LAN/WAN connection.

Sage SalesLogix Server Components that primarily handle logging and licensing for the

Sage SalesLogix system. The computer where the components are installed is also referred to as the SalesLogix Server and it may be combined with the SalesLogix Database Server.

SalesLogix Cache Server Stores Web data which allows the cache to be real-time.

SData Using SData features, you can expose an entity or a business rule to RESTful-based

Web services, allowing you to integrate and enhance Sage SalesLogix data with data from outside the application.

Security Determines what a user can access in Sage SalesLogix. Security is controlled by a combination of account ownership, management hierarchy, and level of access rights to information.

Security Profile Determines each user’s access to information, tables and fields, and functionality.

Site Code A unique identification code assigned to each Network user, Remote user,

Synchronization Server, and Remote Office that represents the user or component.

SLXService user A Windows logon name with security permissions that allow the SalesLogix

Server and Synchronization Service to access all necessary directories.

SpeedSearch Enables users to find information stored in the Sage SalesLogix database or external files.

Subscription Allows a Remote user to select or subscribe to accounts used on a regular basis and store the accounts in the Remote user’s local database. Subscription rules identify the criteria for selecting accounts.

Synchronization The process of reconciling changes between remotes (users or Offices) and

Network users. Synchronization can occur through a direct connection (LAN/WAN), FTP, or

HTTP.

Synchronization (Sync) Server The application that runs synchronization and agents. It can also refer to the hardware on which the Sync Server application resides.

Synchronization Service A Windows service that communicates with the Synchronization

Server(s) and SyncServices.cfg file for scheduling.

Team A group of users who have access to the same accounts. Members of the same team may have different security access to data.

Ticket A record of a call relating to a question or problem experienced by the customer.

Transaction Exchange Files (TEFs) Files that are transferred between Remote users and

Remote Offices, and the main office to synchronize data.

Web Remote Office A group of Remote users that access a single Remote Office database using the Web Client.

WGLogs A folder in which Network users place transaction files as changes are made to the database.

Sage SalesLogix Implementation Guide v8.0

161

Glossary

162 Sage SalesLogix Implementation Guide v8.0

Numerics

64-bit

and ASP.NET 4.0

147

and Data Link mgr

Data Link mgr connection

HTTP on Windows 2008

installation permissions

64-Bit OS

Accounting Integration

135

endpoints

136

Active thread count monitoring

141

Adding

Customer Portal user

virtual directories

149

virtual server(s)

141

virtual servers/Web Hosts

141

Administrative Tools and Servers components of install

Administrative Workstation defined

159

Administrator configuring

Administrator rights

Adobe Acrobat Reader

Advanced Outlook Integration

132

activating

requirements

Agents

and .NET v 3.5.1 for 2003

and .NET v 3.5.1 for 2008 R2

and Sage SalesLogix, overview

Application Architect defined

159

Archives folder

117

ASP.NET

configuring

143

Automated installations

Browsers configuring

Bundles, defined

159

Calendar options, user

Client computers configuring

Index

Compatibility Checklist

Concurrent users

159

Configuration file example

features

properties

Configuring

Administrator

browsers

82 ,

Customer Portal access to SpeedSearch Indexes

manual settings for Web Hosts

Remote Office

ConfTran file

Connection Manager creating Microsoft SQL Server connection

creating Oracle connection

Connection, creating to database

Contact Web Access Tab

Contacts

159

Contract

159

Counters for Performance Monitor

145

Custom Sage SalesLogix installations

151

155

Customer Portal adding user

configuring access to SpeedSearch Indexes

creating the Web access user

enabling the Contact Web Access Tab

linking customers

testing Web site

URL example

Data Link Manager creating Oracle Client connections

Database configuring for Oracle

125

creating Client connections

creating connections to

creating for remote office

112

creating for Remote user

105

creating Oracle login

126

installing for remote office

114

Database Instance for Oracle

Database Manager

Database Server port

using firewalls

Sage SalesLogix Implementation Guide v8.0

163

Index

Defect

159

deploying the portal

116

Desktop Integration

DMP files

Documentation

Documents folder

Everyone granting rights to

FailedTrans

Firewalls

144

Folders

Database

documents

FailedTrans

Infiles and Outfiles

library

RemOffice Sync Logs

SyncService

Folders, Sage SalesLogix creating

granting rights to everyone

sharing

for Remote Office

116

FTP server settings

100

setup

site for Sage SalesLogix, configuring

sync profile

sync transfer profile

FTP synchronization

HTTP setup

site for Sage SalesLogix, configuring

sync transfer profile

HTTP compression

HTTP Keep-Alives Enabled check box

142

144

Importing Oracle database structure

127

Infiles

117

folder

159

Installations, customizing

151

155

Installing

Remote Client

106

Remote Office

113

remote office database

114

Sage SalesLogix Network Client

Sage SalesLogix Server

106

secondary Web Host

141

Web Reporting

164 Sage SalesLogix Implementation Guide v8.0

Intellisync for SalesLogix

requirements

116

Internet Explorer

Join, defined

160

LAN Developer’s Reference

Library folder

Licenses adding

Web Host

Logging on

Sage SalesLogix applications

126

FTP synchronization

MDAC

MDF files

Microsoft Outlook

Microsoft SQL Express

Microsoft SQL Server databases

Microsoft SQL Server authentication

Microsoft Word

Net Service Name, creating for Oracle

125

Network and Web

Network synchronization

Network users adding to remote office

112

Network, sync profile

Office information entering

support options

Offline Web Client

defined

installing

Opportunities

Options accounting

configuring

configuring for users

database

Oracle configuring database

125

creating database login

126

database files

import database structure

127

Outfiles

94 ,

folder

160

Index

Outlook integration requirements

integration with Sage SalesLogix

prerequisite

Outlook integration

132

Password blank database

evaluation database

Planning, for implementation

Plugins

160

PortalDeployments folder

160

Processes defined

160

Profiles

Remote Office

111

Remote user, creating

103

sync transfer for FTP

sync transfer for HTTP

Synchronization Service

100

Public Access for SpeedSearch Indexes

Relational database management system

(RDBMS)

160

RemOffice Sync Logs folder

Remote Client creating profiles

103

installing

106

Remote Office adding network users

configuring

creating database

defined

installing

sync transfer options

111

Remote Office synchronization client starting

116

Remote Saless Client

Restricted user

Roles

Sage Job Server and the SData portal

Sage Job Service requriements

user permissions

Web Host required

Sage SalesLogix applications, starting

license for

Sage SalesLogix API Reference

Sage SalesLogix counters monitoring active thread count

141

Sage SalesLogix Job Server

WebDLL User

Sage SalesLogix Job Service

Sage SalesLogix OLE DB Provider

160

Sage SalesLogix Personal Web Server

160

Sage SalesLogix Planning Guide

Sage SalesLogix Remote Client defined

161

subscription

103

synchronization options

103

Sage SalesLogix Server defined

161

installing

SageJobService portal

Sales library folder

Scaling

141

Security

161

advanced

allowing administration of Customer

Portal

profile

161

WebDLL user

Server settings

FTP

100

Site code

161

SLXService user creating

defined

161

SLXWebRpt virtual directory setting properties

149

Software requirements

Web Client computers

Sort orders setting

SpeedSearch configuring

access for Customer Portal users

indexes

Remotes

SpeedSearch Server

Starting

Sage SalesLogix applications

Subscription

161

overview

103

Sync Logs folder creating

Sync transfer options remote office

111

Sync transfer profile

FTP

HTTP

network

Synchronization accounting integration

139

creating folders

folder structure

Remote user options

103

Sync Logs Folder

Sage SalesLogix Implementation Guide v8.0

165

Index

Synchronization methods

Synchronization Server defined

ports

starting

using firewalls

Synchronization Service creating a profile

100

defined

161

SyncService Folder

Sysdba sysdbafix_script.sql

108

115

Tablespace

126

TCP/IP requirements

Teams

161

user options

Ticket

161

Transaction Exchange Files defined

161

Transfer profiles for synchronization

Trust relationship

URL

Web Client

User groups

granting rights to

sharing folders

Users concurrent

159

remote office

112

setting calendar options

setting team options

UTF-8 support

Virtual directory(ies)

Web Host

Windows 2003

142

Windows 2008

143

Virtual Private Network

Virtual server(s) adding

141

VPN

Web Client configuring computers

creating link for users

roles

testing Web site

Web Host configuring

Windows 2003 Server

142

Windows 2008 Server

143

installing secondary server

141

monitoring performance of

145

ports

145

using firewalls

145

Web Host and IIS

Web Reporting installing

Web Reporting and IIS

Web Reporting Server

ports

145

using firewalls

145

Web site(s) creating

Windows 2003

142

Windows 2008

143

creating link

linking

testing

WebDLL user

creating

WGLogs folder

117

Windows security

sharing folders

Windows Authentication configuring for Web

requirements

requriements

SQL Server security

Windows 2003

Windows 2008

166 Sage SalesLogix Implementation Guide v8.0

Reklaam

Sage SalesLogix

Implementation Guide

Sage SalesLogix

Implementation Guide

Contents

Introduction

About This Guide

Chosing Components for Your Implementation

What You Need to Know

Planning Your Implementation

Related Documentation

Chapter 1

Implementation Checklist

Required Tasks

Web Tasks

Mobile Client Tasks

Customer Portal Tasks

Synchronization Tasks

Remote User Tasks

Remote Office Tasks

Intellisync for SalesLogix Tasks

Optional Tasks

Part I

Administration Tools and Servers

Chapter 2

Preparing Your Environment

Before You Begin

General Requirements

User Rights and Network Permissions

Understanding Commonly-Used Users

Permissions Required for the SLXService User (without Administrator rights)

The WebDLL User

Software Requirements

Web Requirements

SData Portal Requirements

Process Orchestration Server Requirements

Windows Authentication Requirements

Windows Authentication in the Sage SalesLogix Network Client

Windows Authentication in the Sage SalesLogix Web Client

Sage Job Service Requirements

Server Requirements

Microsoft SQL Server

Oracle

Sage SalesLogix Client Requirements

Web Client Requirements

Remote Office Requirements

SpeedSearch Requirements

Outlook Integration Requirements

Intellisync for SalesLogix Requirements

Logging Access Requirements

Understanding the Logging Folders

Creating the Logging Folders

Creating the Remote Office Folders

Sharing Folders and Granting Access Rights

Granting Full Access Rights to All Users

Sharing Folders and Granting Rights to User Groups

Creating User Groups

Sharing Folders by Group

Running Sage SalesLogix as a Restricted User

Running Sage SalesLogix on a 64-Bit System

Chapter 3

Installing Sage SalesLogix

Selecting Your Installation

Understanding Sage SalesLogix Databases

Microsoft SQL Server

Oracle

Installing Sage SalesLogix

Running the Express Installation

Running the Standard Installation

Creating Database Connections

Creating Client Database Connections for Oracle

Creating a Net Service Name

Creating a Client Database Connection

Creating a 32-bit OLE DB UDL

Chapter 4

Configuring the Sage SalesLogix System

Logging On to the Administrator

Understanding the Setup Assistant

Adding Licenses

Entering Office Information