Sage_SalesLogix_Implementation_Guide

Sage SalesLogix Implementation Guide

Version 7.2

Developed by Sage SalesLogix Technical Publications

Sage SalesLogix Implementation Guide

DocumentationComments

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

Copyright Copyright © 1997-2007, Sage Software, Inc. All Rights Reserved. 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 Software and its licensors, if any.

Version Version 7.2 (062107) 2007

Trademarks SalesLogix is a registered trademark of Sage Software, Inc.Other product names may be trademarks or registered trademarks of their respective companies and are hereby acknowledged.

Disclaimer Sage Software 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 Software assumes no responsibility or liability for errors or inaccuracies with respect to this publication or usage of information. Further, Sage Software 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

Technical Support is available to customers who purchased their support contracts directly from Sage Software, and to Certified Business Partners. Calls are answered during business hours, Monday through Friday, excluding holidays. More information about the levels of Technical Support available can be found on the Sage CRM Solutions Web site at http://www.sagecrmsolutions.com/products/sagesaleslogix/support.

Customers with a valid technical support contract and a Web access code can request technical support electronically on the Sage SalesLogix SupportOnline Web site: http://support.saleslogix.com. Revisions to the PDF are also posted on this Web site.

Contents

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1What You Need to Know. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Planning Your Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Part I Installing with the Express Installation

Chapter 1 Implementation Checklist - Express Installation . . . . . . . . . . . . . . . . . . 5

Chapter 2 Preparing for Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11SpeedSearch Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Outlook Integration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Understanding Additional Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Running Sage SalesLogix as a Restricted User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3 Installing with Sage SalesLogix Express . . . . . . . . . . . . . . . . . . . . . . . . 13Understanding Sage SalesLogix Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Running the Express Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 4 Configuring the Sage SalesLogix System . . . . . . . . . . . . . . . . . . . . . . . 15Logging On to the Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Understanding the Setup Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Adding Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Entering Office Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configuring Sage SalesLogix Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Setting Database Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Activating Advanced Outlook Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Setting Accounting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Adding Customer Service and Support Information. . . . . . . . . . . . . . . . . . . . . . . 19Running Sage SalesLogix on a Multiuser Environment . . . . . . . . . . . . . . . . . . . . 20Example Registry Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Maintaining Database Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 5 Configuring Sage SalesLogix Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Understanding the Admin User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Creating Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Adding New Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Configuring Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Setting Access to Customer Service Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 6 Installing Network Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Creating Automated Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Installing the Sage SalesLogix Network Client . . . . . . . . . . . . . . . . . . . . . . . . . . .28Performing an Automated Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Performing a Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Starting the Sage SalesLogix Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Understanding Outlook Integration and Intellisync for Sage SalesLogix . . . . . . .30Configuring Outlook Integration and Intellisync for Sage SalesLogix. . . . . . . . . . . . . . . 30Adding Outlook Contacts to Sage SalesLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Adding Address Lists to the Outlook Addressing Tab. . . . . . . . . . . . . . . . . . . . . . . . . . 32

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

Chapter 7 Configuring Marketing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Configuring the Marketing Services Configuration Manager . . . . . . . . . . . . . . . . .35Creating a Marketing Services Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Creating a Marketing Services User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Chapter 8 Configuring the Synchronization Server. . . . . . . . . . . . . . . . . . . . . . . . . 39Creating Synchronization Transfer Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Creating a Network Synchronization Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Creating an FTP Synchronization Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Setting Up a Sage SalesLogix FTP Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Creating an FTP Sync Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Creating an HTTP Synchronization Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Setting Up a Sage SalesLogix HTTP Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Creating an HTTP Sync Transfer Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Starting the Synchronization Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Modifying Virus-Checking Software for the Synchronization Server. . . . . . . . . . . . . . . . 45

Understanding the Monitor Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Chapter 9 Configuring the Sage SalesLogix Remote Client. . . . . . . . . . . . . . . . . . . 47Planning for Remote Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Using Subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Creating Subscription Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Manually Subscribing to Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configuring Remote User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Setting Synchronization Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Creating a Remote User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Installing the Sage SalesLogix Remote Client . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Performing an Automated Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Performing a Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Installing the Remote User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Starting the Sage SalesLogix Remote Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Creating a SpeedSearch Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Part II Installing with the Standard Installation

Chapter 10 Implementation Checklist - Standard Installation . . . . . . . . . . . . . . . . . 57Required Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Synchronization Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Remote User Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Remote Office Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 11 Preparing for Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63SpeedSearch Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Remote Office Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Outlook Integration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Understanding Logging Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Understanding the Logging Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Creating the Logging Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Creating the Remote Office Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Sharing Folders and Granting Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Granting Full Access Rights to All Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Sharing Folders and Granting Rights to User Groups . . . . . . . . . . . . . . . . . . . . . . . . . .67

Creating User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Sharing Folders by Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Understanding Additional Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Running Sage SalesLogix as a Restricted User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Chapter 12 Installing with Sage SalesLogix Standard . . . . . . . . . . . . . . . . . . . . . . . 69Understanding Sage SalesLogix Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Running the Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Creating Database Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Creating Microsoft SQL Server 2000 Database Connections . . . . . . . . . . . . . . . . . . . . .72Creating Microsoft SQL Server 2005 Database Connections . . . . . . . . . . . . . . . . . . . . .73Creating Oracle Database Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Creating Client Database Connections for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . 76Creating a Net Service Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Creating a Client Database Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Chapter 13 Configuring the Sage SalesLogix System. . . . . . . . . . . . . . . . . . . . . . . . 79Logging On to the Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Understanding the Setup Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Adding Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Entering Office Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Configuring SpeedSearch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Understanding SpeedSearch Indexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Configuring SpeedSearch for Multiple Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Configuring Sage SalesLogix Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Setting Database Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Setting Conflict Resolution Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84Activating Advanced Outlook Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Setting Accounting Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Adding Customer Service and Support Information . . . . . . . . . . . . . . . . . . . . . . .85Running Sage SalesLogix on a Multiuser Environment . . . . . . . . . . . . . . . . . . . . .86Example Registry Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Maintaining Database Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Chapter 14 Configuring Sage SalesLogix Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Planning for Sage SalesLogix Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89Understanding the Admin User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Creating Departments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Creating Administrative Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Creating Security Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Creating Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91Creating User Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Configuring General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Setting Employee Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Setting Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Setting Client System Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Setting Service and Support Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Adding New Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Configuring Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Setting Access to Customer Service Management . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Understanding Optional User Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . .99Creating Teams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 15 Installing Network Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Creating Automated Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101Installing the Sage SalesLogix Network Client . . . . . . . . . . . . . . . . . . . . . . . . . .102Performing an Automated Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Performing a Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Starting the Sage SalesLogix Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103Understanding Outlook Integration and Intellisync for Sage SalesLogix . . . . . .104Configuring Outlook Integration and Intellisync for Sage SalesLogix. . . . . . . . . . . . . . 104Adding Outlook Contacts to Sage SalesLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Adding Address Lists to the Outlook Addressing Tab. . . . . . . . . . . . . . . . . . . . . . . . . 106

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

Chapter 16 Configuring Marketing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Configuring the Marketing Services Configuration Manager . . . . . . . . . . . . . . . .109Creating a Marketing Services Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Creating a Marketing Services User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Chapter 17 Configuring the Synchronization Server. . . . . . . . . . . . . . . . . . . . . . . . 113Creating Synchronization Transfer Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113Creating a Network Synchronization Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Creating an FTP Synchronization Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Setting Up a Sage SalesLogix FTP Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Creating an FTP Sync Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Creating an HTTP Synchronization Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Setting Up a Sage SalesLogix HTTP Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Creating an HTTP Sync Transfer Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Creating a Synchronization Service Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Starting the Synchronization Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Modifying Virus-Checking Software for the Synchronization Server . . . . . . . . . . . . . . . 122

Understanding the Monitor Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Chapter 18 Configuring the Sage SalesLogix Remote Client . . . . . . . . . . . . . . . . . 123Planning for Remote Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Using Subscription. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Creating Subscription Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Manually Subscribing to Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Configuring Remote User Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Setting Synchronization Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Creating a Remote User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Installing the Sage SalesLogix Remote Client . . . . . . . . . . . . . . . . . . . . . . . . . . 126Performing an Automated Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Performing a Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Installing the Remote User Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Starting the Sage SalesLogix Remote Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Creating a SpeedSearch Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 19 Configuring a Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Configuring the Remote Office Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Adding Users to a Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Creating a Remote Office Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Installing a Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Installing the Remote Office Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Starting the Remote Office Synchronization Client . . . . . . . . . . . . . . . . . . . . . . 134Installing Remote Office Network Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

AppendixA Creating a Database for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Creating an Oracle Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Creating a Database Instance on Oracle 9.2.0.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Creating a Database Instance on Oracle 10.2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Creating a Net Service Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Configuring the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Creating Tablespaces and Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Creating the Database Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Importing the Database Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Indexing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Adding Database Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

AppendixB Automating Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Customizing the Sage SalesLogix Configuration File . . . . . . . . . . . . . . . . . . . . . 143Understanding Features and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Example Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

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

AppendixC Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Introduction

Sage SalesLogix is the 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, and Support automation solutions.

About This GuideThis is the Sage SalesLogix Implementation Guide. It provides step-by-step instructions for installing Sage SalesLogix. This guide is written for system administrators and information system (IS) professionals.

The Sage SalesLogix Implementation Guide consists of two sections:

• Part I: Installing with Sage SalesLogix Express – This section explains the steps required to install and configure Sage SalesLogix using the Express Installation. The Express Installation is intended for an implementation of 5 to 25 users using the Microsoft SQL Server database platform.

• Part II: Installing with Sage SalesLogix Standard – This section explains the steps required to install and configure Sage SalesLogix using the Standard Installation. The Standard installation is intended for implementations that have more than 25 users, run Sage SalesLogix on Oracle, run Sage SalesLogix over the Web, or include one or more Remote Offices.

What You Need to KnowThe Sage SalesLogix Implementation Guide assumes you have a working knowledge of Microsoft Windows operating systems, as well as experience with relational database management systems. 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 ImplementationThe 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.

• Select the hardware for each component.

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

1Sage SalesLogix Implementation Guide v7.2

Introduction

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

• Prepare your network for Sage SalesLogix.

You can obtain a copy of the Sage SalesLogix Planning Guide on the Sage SalesLogix DVD, from your Business Partner, from a Professional Services Group (PSG) representative, or on Sage SalesLogix SupportOnline/Sage Software Online Support and Services at http://www.support.saleslogix.com.

Related DocumentationIn addition to the Sage SalesLogix Implementation Guide and Sage SalesLogix Planning Guide, the following documentation is available. All documents are available on SupportOnline/Sage Software Online Support and Services.

• The Compatibility Checklist outlines the hardware and software currently recommended for a Sage SalesLogix implementation.

• The Sage SalesLogix Web Implementation Guide provides detailed instructions for installing and configuring the Sage SalesLogix Web Client and other SalesLogix Web interfaces, such as Customer Portal and LeadCapture. The Sage SalesLogix Web Implementation Guide is available on the Sage SalesLogix DVD.

• The Sage SalesLogix LAN Developers Reference provides VBScript, COM, and SQL functions you can use to customize Sage SalesLogix to meet your specific needs.

• The Sage SalesLogix API Reference online Help provides information about functions and code that you can use to customize Sage SalesLogix to meet the needs of your business.

Additional resources and documentation are available on the Sage SalesLogix SupportOnline/Sage Software Online Support and Services Web site at http://support.saleslogix.com, and Help is available in each Sage SalesLogix application.

Sage SalesLogix Implementation Guide v7.22

Installing with the Express InstallationPart I

Chapte

Sage SalesLogix Implementation Guide v7

r 1
Implementation Checklist - Express Installation
The Express Installation is intended for a Sage SalesLogix configuration of 5 to 25 users using the Microsoft SQL Server database platform. If your implementation includes more than 25 users, Oracle, the Web, or Remote Offices, you should use the Standard Installation as detailed in Part II of this guide. For Express installations, the Database Server, Sage SalesLogix Server, and Administrative Workstation are all located on one computer.

This implementation checklist outlines the tasks you must complete to implement Sage SalesLogix using the Express Installation (for additional configuration information and tasks not required for an Express Installation, review the Standard Installation section of this guide). 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, refer to the appropriate Upgrading document located in the Documentation folder on the Sage SalesLogix DVD.

Task Page Computer

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

2 Install and configure your system prerequisites. 9 All computers and servers

3 Install the Sage SalesLogix Server components. 13 Database Server

4 Add the appropriate Sage SalesLogix licenses. 16 Administrative Workstation

5 Enter your main office information. 16 Administrative Workstation

6 Configure options. 17 Administrative Workstation

7 Add Office Information for Customer Service and Support.

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

19 Administrative Workstation

8 If necessary, configure the SLXSystem.exe to run as a Windows Service.


9 Add new users and configure user profiles. 23 Administrative Workstation

10 Set access to Customer Service Management options.



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


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

28 Sage SalesLogix Client computers

13 Start the Sage SalesLogix Network Client. 29 Sage SalesLogix Client computers

5.2


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. See “Setting Conflict Resolution Options” on page 84 for more information.

Dashboards Dashboards allow users to display and interact with a variety of analytical information in a dashboard. You can set options to display data relative to a specified fiscal calendar, the Gregorian calendar, or both. See the “Displaying the Sales Dashboard” topic in the Sage SalesLogix Client Help for more information.

Departments You can create additional departments to assign to users. See “Creating Departments” on page 89 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.

Password Options You can set restrictions on user passwords. For example, you can require that all users have a password (not blank). See the “Setting Password Options” topic in the Administrator Help for more information.

14 (Optional) Configure Outlook Integration and Intellisync for Sage SalesLogix on each Sage SalesLogix Network user’s computer.


15 Create Area, Category, and Issue lists.


32 Sage SalesLogix Client computer

16 (Optional) Configure Marketing. 35 Sage SalesLogix Server

Remote User Tasks

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


18 Start the Synchronization Server (Sync Server). 45 Synchronization Server

19 Create subscription rules and assign them to Remote users.


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


21 Create Remote user databases. 49 Administrative Workstation

22 Install the Sage SalesLogix Remote Client. 50 Sage SalesLogix Remote Client computers

23 Install the Remote user database. 51 Sage SalesLogix Remote Client computers

24 Start the Sage SalesLogix Remote Client on every Remote user’s computer.

52 Sage SalesLogix Remote Client computers

25 (Optional) Create a SpeedSearch schedule on the Remote user’s computer.


Task Page Computer



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.

Sage SalesLogix Mobile Sage SalesLogix Mobile extends Sage SalesLogix functionality to Pocket PC and BlackBerry devices. Sage SalesLogix Mobile provides instant access to customer information wherever you are and exactly when you need it; all via a compact, convenient, handheld-based application. Sage SalesLogix Mobile is add-on functionality that requires separate installation and pricing. Contact your Sage SalesLogix representative for more information.

SpeedSearch If necessary, you can customize the SpeedSearch indexes (requires the SpeedSearch Server Advanced license) and index schedules. See the “Managing SpeedSearch Indexes” and “Managing SpeedSearch Schedules” topics in the Administrator Help for more information.

Synchronization Service Profile You can create profiles to run synchronization on a specific schedule without an administrator logged on to the server. See “Creating a Synchronization Service Profile” on page 119 for more information.

Teams You can create teams of users who require access to the same set of accounts. See “Creating Teams” on page 99 for more information.

Windows Authentication With Windows Authentication, users are automatically logged on without entering their Sage SalesLogix user names or passwords. See the “Using Windows Authentication” topic in the Administrator Help for more information.

Sage SalesLogix Implementation Guide v7.2 7

Chapte


r 2
Preparing for Implementation
Before installing Sage SalesLogix, review and address the system prerequisites. This chapter outlines the necessary requirements for a successful implementation.

Note For Express installations, the Database Server, Sage SalesLogix Server, Sync Server, and Administrative Workstation are all located on one computer.

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

implementation.

• Compatibility Checklist. Refer to this document to ensure your hardware and software meet Sage SalesLogix supported versions.

• 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, Sync Client, or Mail Client.

• 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 Microsoft DAC (Windows Vista). Microsoft Data Access Components are required on every computer running Sage SalesLogix.

• Microsoft SQL Express installed on the Administrative Workstation. Microsoft SQL Express is required if you have a Microsoft SQL Server 2000 database and there will be Remote users created, 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 SLXMaster. If you install Microsoft SQL Express from another source, you must set the sa password to SLXMaster (it is generally blank). To install Microsoft SQL Express with the same configuration settings as Sage SalesLogix, use one of the following files on the Sage SalesLogix DVD:

• For the Administrative Tools and Servers installation, run ...\SQLExpress\setup.exe /settings "...\<SQLExpress>\Administrative Tools and Servers.ini"

• For the Sage SalesLogix Client installation, run ...\SQLExpress\setup.exe /settings "...\<SQLExpress>\SalesLogix Client.ini".

• Microsoft .NET Framework. .NET Framework is required for .NET Extensions on the Administrative Workstation, Architect, and Sage SalesLogix Client computers.

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

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

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

• TCP/IP installed and configured on every computer running Sage SalesLogix. TCP/IP is required as the network communication protocol.

9.2


• Microsoft Internet Explorer. You must install Internet Explorer on every computer running Sage SalesLogix. Refer to the Compatibility Checklist for supported versions.

• 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 XP, Collaboration Data Objects can be installed from the Control Panel > Add or Remove Programs > MS Office > Change > Add or Remove Features > Microsoft Outlook > Collaboration Data Objects > Run from My Computer.

• For Outlook 2007, download Collaboration Data Objects version 1.2.1 from the Microsoft Web site at www.microsoft.com.

• 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 computer for mail merge.

• Crystal Reports Professional. 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 as an option on the Sage SalesLogix DVD browser.

• Mail client configured on the Administrative Workstation.

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

• 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.

For Visual Studio installed with Microsoft SQL Server 2005, launch Visual Studio > Tools > Options > Debugging > Just-In-Time > and clear all three options.

Server RequirementsIn addition to the “General Requirements” in the previous section, ensure the Server computer(s) meet the following requirements.

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

Note 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.

• 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.

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

• Microsoft SQL Server Client and Server component versions match. For example, if the Connection Manager uses the Microsoft SQL Server 2005 driver, then the Sage SalesLogix Clients must use the 2005 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.



Client RequirementsIn addition to the “General Requirements” on page 9, ensure the following are set up on each Client computer.

• Microsoft SQL Express or Microsoft SQL Server. For Remote Clients only, Microsoft SQL Express or Microsoft SQL Server must be installed. See the Compatibility Checklist for supported versions.




• Microsoft Outlook. You must install Outlook if you are using Outlook Integration. Ensure Outlook is installed and configured before installing Sage SalesLogix.

See “Outlook Integration Requirements” in the following section 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).

To access this setting from the Windows Control Panel, double-click Display. On the Settings tab, click Advanced.

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

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.

• Use User Account Control (UAC) to help protect your computer. If you are running Sage SalesLogix on Windows Vista, ensure this setting is disabled.

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.

SpeedSearch RequirementsIn addition to the “General Requirements” on page 9, 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 does not have enough inherited permissions to run the service.

Outlook Integration RequirementsIn addition to the “General Requirements” on page 9, ensure the following requirements are met if you are using Outlook Integration.

• Install and configure Outlook before installing Sage SalesLogix.



• Set Internet Security. If your company uses Windows 2003, you must adjust the default Internet Security setting in order for the Outlook Integration menu and toolbar items to display.

To adjust security, open Internet Explorer. On the Tools menu, click Internet Options, click the Security tab, and then set the Security level for the Internet zone to any setting other than High.

• Download the WinHelp Engine (WinHlp32.exe). If you are running Sage SalesLogix on Windows Vista and will synchronize information using Intellisync for Sage SalesLogix, you must download the WinHelp engine to access the Online Help. Windows Vista does not include the Help engine necessary for viewing the Intellisync for Sage SalesLogix Help. Refer to the Microsoft Web site for download information.

Understanding Additional Security OptionsTo 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.

Running Sage SalesLogix as a Restricted UserAlthough 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.

• (Read/Write Access) Program Files\Common Files\PUMATECH Shared - 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 from the Windows folder to the Windows Folder\System 32.

Note 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.

After completing this chapter...

You have completed tasks 1-2 of the implementation checklist. See Chapter 3, “Installing with Sage SalesLogix Express” to install Sage SalesLogix.


Chapte


r 3
Installing with Sage SalesLogix Express
The Express Installation installs the following components. In addition, the installation creates and shares the default system folders.

• Sage SalesLogix Databases (Microsoft SQL Server)

• Sage SalesLogix Server

• Administrator

• Architect

• Sage SalesLogix Utilities

• SpeedSearch Service

• Synchronization Service

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

Understanding Sage SalesLogix DatabasesThe 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 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.) unless you have specified a different default data directory. 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.

Important Do not use the evaluation database as your production database.

Running the Express InstallationInstall Sage SalesLogix directly from the Sage SalesLogix DVD or from a network drive. To install from a network drive, copy the entire contents of the DVD to a shared network directory.

If the installation detects that MDAC must be updated, you will be prompted to install it. The installation may appear inactive while MDAC is installed. After MDAC is installed, the computer is restarted without warning. Then, the Sage SalesLogix installation continues.

To run the Express installation

1. Insert the Sage SalesLogix DVD. If the installation program does not start automatically, locate and double-click Install.exe.

Before completing this chapter...

Verify you have installed the prerequisites described in Chapter 2, “Preparing for Implementation.”

13.2

Installing with Sage SalesLogix Express

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

Note If you do not have Microsoft .NET Framework installed, the Sage SalesLogix installation may appear to be inactive while installing the Framework. This installation may take a long time.

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

4. If you have a password set for the sa account on the SQL Server, the SQL Server sa password screen appears. Type your sa password in the appropriate box and then click Next to continue.

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

• To automatically open the Administrator after the installation, select the Launch Administrator check box.

• The Install .Net AJAX Extensions, Install SQL Server 2k5 Exception Message Box, and Install SQL Server 2k5 Backwards Compatibility check boxes are selected as appropriate for your system configuration. If necessary, these components will be installed after Sage SalesLogix.

6. If necessary, reboot your computer.

The next step...

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

• If you are installing on Windows XP or 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.

• To enable SpeedSearch to function correctly, you must place all files and folders to be included in the default indexes in the C:\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. See “Server Requirements” on page 62 for more information about creating a Network user (SLXService) with the necessary access. See “Managing SpeedSearch Indexes” in the Administrator Help for more information on customizing SpeedSearch indexes.


You have completed task 3 of the implementation checklist. See Chapter 4, “Configuring the Sage SalesLogix System” to configure Sage SalesLogix.


Chapte


r 4
Configuring the Sage SalesLogix System
Once you have installed the components necessary for your implementation, you must log on to the Administrator and complete the following tasks:

• Add licenses.

• Enter Office information.

• 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 AdministratorThe Administrator is used to manage users, servers, and offices. The following steps are also used when logging on to other Client applications, such as Architect, Sage SalesLogix Client, and so on.

To log on to the Administrator

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.

Understanding the Setup AssistantThe 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. You can exit the Assistant at any time and add information manually.


Install Sage SalesLogix using the Express installation as described in Chapter 3, “Installing with Sage SalesLogix Express.”

15.2


Adding LicensesAll implementations require a Sage SalesLogix license (Standard, Advanced, or Premier). Additional 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.

The first time you log on to a Sage SalesLogix database that does not contain licenses, the Setup Assistant appears.

To add licenses using the Setup Assistant

1. In the Setup Assistant, select Step 1 - Add Licenses using the License Wizard, and then click Run Selected Step.

If the Setup Assistant is not open, on the Help menu, click Setup Assistant.

2. In the Customer ID box, type your customer ID.

Ensure your customer ID matches the ID to which Sage SalesLogix issued licenses. Your licenses correspond with your customer ID.

3. In the License Wizard, add all your licenses, and then click Next.

You can add licenses by typing the license numbers or using copy and paste from a text file. The License Wizard filters extraneous text from the text file.

4. Depending on your implementation, you may see additional screens prompting for information related to a Synchronization Server license(s). Use the following to enter synchronization information:

a. In the Description box, type a name or description for the Sync Server.

b. Click Next.

5. To apply your licenses, click Finish.

Proceed to the following section to complete Step 2.

Entering Office InformationAfter 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 office information using the Setup Assistant

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.

Note Only the Company Name is a required field.

3. Click OK.

To add office information without using the Setup Assistant, see the “Entering Office Information” topic in the Administrator Help.



Adding UsersThe last step of the Setup Assistant simplifies the process of adding Sage SalesLogix users. The process for adding users is detailed in Chapter 5, “Configuring Sage SalesLogix Users.”

Configuring Sage SalesLogix OptionsYou 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.

Setting Database OptionsDatabase options allow you to configure the default settings when creating Remote user databases. If your implementation does not include Remotes, you do not need to set database options.

To set database options

1. On the Administrator Tools menu, click Options, and then click the Database tab.

2. In the Host DB Admin ID box, type the user name of the database system administrator.

This is usually sa, but may be any admin level SQL Server user identity.

3. In the Host DB Admin password box, type the sa password used by the host database.

4. The Sync Global remote SA Password for existing databases option allows you to set a global SA password for all Remote users. 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.

Note If the Microsoft SQL Express instance on the Remote was installed from the Sage SalesLogix DVD, then the default instance password is SLXMaster.

5. In the Create Remote DB in server directory box, 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.

Note 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.

The next step...

Do one of the following:

• Complete the information in the following sections to configure your Sage SalesLogix system. Then use the processes detailed in Chapter 5, “Configuring Sage SalesLogix Users” to add users.

• Refer to Chapter 5, “Configuring Sage SalesLogix Users” to add users. Then return to the following sections to complete your Sage SalesLogix system configuration.

Refer to the “Configuring SalesLogix Options” topic in the Administrator Help for information on other options.



6. Select when you want the Data Transformation Services (DTS) file and Remote database to be created:

• Prepare Remote DB and create it immediately automatically 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. This method requires a user interface and scheduler to connect to the database and run the DTS package.

7. Click OK.

Activating Advanced Outlook IntegrationIntegration with Microsoft Outlook enables Sage SalesLogix users to use Outlook’s advanced calendar system when sending e-mail, scheduling activities, and managing contacts. For example, using Outlook enables users to schedule activities for other Sage SalesLogix users using the Attendee Availability tab in the Sage SalesLogix Client.

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 Advanced Outlook Integration

1. On the Administrator Tools menu, click Options, and then click the Outlook tab.

2. Select the Activate Advanced Outlook Integration check box.

After activating Advanced Outlook Integration, you can add Internet domains that you want to exclude from Send SLX functionality. 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.”

3. Click Add.

4. 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.

5. Click OK.

6. Repeat steps 3-5 to add additional domains.

You must configure Outlook Integration in the Sage SalesLogix Client. This configuration is outlined in “Configuring Outlook Integration and Intellisync for Sage SalesLogix” on page 30.

Setting Accounting OptionsAccounting 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.

Adding Customer Service and Support InformationIf 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 customer service and support information

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.

See the “Setting Accounting Options” topic in the Administrator Help for details.



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.

• 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 32.

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.

9. Click OK.

Running Sage SalesLogix on a Multiuser EnvironmentIf you are running Sage SalesLogix on a multiuser environment such as Citrix, Web Server, or Terminal Server, it is highly recommended that you configure the SLXSystem.exe to run as a Windows Service. On Windows 2003 SP1 or later, the service must be installed in install mode. Running SLXSystem.exe as a service removes the startup/shutdown time when the Client creates a connection to a database using the SLXSystem.exe.

The SLXSystem service starts and stops when connections are created. However, you can set the service to remain open for a set amount of time before shutting down. To set a specific amount of time for the service to remain open, add the registry key HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\ShutdownDelay(DWORD). The key accepts values 1 through 1440, where the value indicates the number of minutes the service will run before shutting down (after it detects no activity). Setting the value to 0 indicates the service never shuts down.

By default, the SLXSystem.exe service is set to Automatic with a registry value of 0 so that it is always on.

To install SLXSystem.exe as a service

1. If currently running, close the current SLXSystem.exe using Task Manager.

2. On the Start menu, click Run.

3. In the Open box, type “C:\Program Files\SalesLogix\SLXSystem.exe” /install.

The service can be removed using the “C:\Program Files\SalesLogix\SLXSystem.exe” /uninstall command.

Refer to the “Understanding the SpeedSearch Approval Process” topic in the Administrator Help for more information.



Example Registry EntryThe following is an example registry entry that allows the same Data Link to be available for users logging on to Sage SalesLogix.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\CUD]

[HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\CUD\ADOLogin]

[HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\CUD\ADOLogin\Connection1]

"Data Source"="SLX"

"DBPassword"=""

"DBUser"=""

"Extended Properties"="PORT=19026;LOG=ON"

"Initial Catalog"="SLX"

"Provider"="SLXOLEDB.1"

"Alias"="SLX"

@=""

Maintaining Database SecurityAfter 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 Enterprise Manager.

After changing the sysdba password in SQL Server Enterprise Manager, you must change the password in the Connection Manager on the Sage SalesLogix Server. See the Connection Manager Help for detailed instructions.


You have completed tasks 4-8 in the implementation checklist. See Chapter 5, “Configuring Sage SalesLogix Users” to continue your implementation.


Chapte


r 5
Configuring Sage SalesLogix Users
When creating Sage SalesLogix users, you must add new users and modify the user profile.

Understanding the Admin UserSage 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

• Teams

• Sync

Admin user access is restricted to ensure the system administrator is not included in your company’s security model.

Creating UsersBefore 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:


Add licenses and configure the system as described in Chapter 4, “Configuring the Sage SalesLogix System.”

For detailed information on default Sage SalesLogix user templates, see the “Creating a User Template” topic in the Administrator Help. If necessary, you can customize the default templates.

Creation Method Description

Add new users based on an existing user template

You can add new users based on an existing user template or a custom user template you create.

23.2


The following sections detail how to add users based on existing Windows’ users, and then how to complete and activate the new users. For information on creating user templates, refer to “Creating User Templates” on page 92.

Adding New UsersUse the following sections to add users by importing existing Windows’ users to Sage SalesLogix.

To add users based on existing Windows’ users

1. On the Administrator Navigation Bar, click Users.

2. On the Insert menu, point to Import Users, and then click From Windows.

You can also access the Import Windows Users dialog box from the Setup Assistant. Select Step 3 - Import Users from Windows, and then click Run Selected Step.

3. In the Windows Domain box, select the domain from which you want to map your Windows' users.

Existing Windows users appear in the Windows Username and Windows Full Name columns.

4. To quickly locate a specific Windows' user, type a Windows Username in the Search for box.

You can use a variety of search methods in this box. For example, if you type the letter J, all Windows user names that contain a J will appear.

5. Press CTRL and select all users that you want to create for a specific user type. For example, select all users that you want to create as Network users.

6. In the User Type box, select the type of user that you want to create.

7. In the Template box, select the user template that you want to apply to the user(s).

You can select a custom template or a pre-configured system template. If you do not select a template, users are created with a blank user profile with only system defaults enabled.

8. Click Create User(s).

A check mark appears next to each user that will be created.

9. Repeat steps 4-8 for all other user types that you want to create.

Create Sage SalesLogix users based on existing Windows’ users

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.

Import users from a comma-delimited text file 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.

Create users individually 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.


For information on other methods of adding users, see the “A New Employee Needs Access to Sage SalesLogix” topic in the Administrator Help.



10. If you want to import information from Windows’ Active Directory to each user’s profile, ensure Update SalesLogix user information with Windows information is selected. Otherwise, clear this check box.

11. If you want to enable Windows Authentication (single log-on) for the selected users, ensure Use Windows Authentication is selected. If you simply want to import the users, clear this option (in this case users will be required to log on to the Sage SalesLogix Client unless you enable Windows Authentication in each user's profile).

12. Click OK to create the new users.

Configuring UsersIf 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.


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 to be used as part of a Remote database name.

For more information on importing from Active Directory, see the “Importing Additional User Information from Windows” topic in the Administrator Help.



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. Click the Employee tab.

9. If necessary, in the Accounting ID field, type the user's accounting identification code. (This is the ID used by the accounting software.)

10. Click OK.

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


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.

If your installation includes Remote users, additional options are configured in Chapter 9, “Configuring the Sage SalesLogix Remote Client.” Remote user options cannot be configured until you complete various synchronization configuration steps.


You have completed tasks 9 and 10 in the implementation checklist. See Chapter 6, “Installing Network Clients” to continue your implementation.


Chapte


r 6
Installing Network Clients
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 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 images directly from the upgrade wizard. Then when you add new users and install Sage SalesLogix, the installation includes all service packs and upgrades that are installed on your system.

Important When installing the Sage SalesLogix Client using an automated installation, third-party applications are not installed. This includes Intellisync for Sage SalesLogix (Network and Remote Client) and Microsoft SQL Express (Remote Client). Third-party applications must be installed separately, and can be found in the Redist folder on the Sage SalesLogix DVD.

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 InstallationsYou can create automated installations of the Sage SalesLogix Network and Sage SalesLogix Remote Clients.

Note If you want to customize the standard configuration file or create your own configuration file, see Appendix B, “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 an automated Client installation


2. On the Sage SalesLogix Installation screen, click Install SalesLogix Client.

3. On the Install SalesLogix Client Installation screen, click Build Network Client Install or Build Remote Client Install.

4. On the Welcome screen, click Next.

5. On the Administrative Install Options screen, enter the information as appropriate for your installation type, and then click Next.

• 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.


Create and configure users as described in Chapter 5, “Configuring Sage SalesLogix Users.”

27.2


• 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.


• 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.

6. 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.


The automated installation is created in the specified shared network location and a shortcut to the installation is created on the desktop.

8. Distribute the shortcut or installation to users.

Installing the Sage SalesLogix Network ClientNote If your company uses Outlook Integration, ensure you have completed the required steps

under “Outlook Integration Requirements” on page 11 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”.

Performing an Automated InstallationInstalling the Sage SalesLogix Client using an automated installation configures the Client computer with the settings selected when the installation was built.

To run an automated installation, instruct the user to double-click the client installation shortcut or custom SalesLogix 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 29 for details.

Performing a Manual InstallationRun a manual installation if you do not want to install some components or if you want to change the installation location.

To run a manual installation





3. On the Install SalesLogix Client screen, click Install SalesLogix Network Client.

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

5. On the Setup Type screen:

• Click Complete to install the most common components. Click Next.

• 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. Click Next.


If your company is not using Intellisync for Sage 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. See the following section for details.

Starting the Sage SalesLogix ClientAfter 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.

• Sage SalesLogix Client

• MailClient.exe (installed with the Sage SalesLogix Client)

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 or she can simply log on and begin using the Sage SalesLogix Client. The Sage SalesLogix Client must write to restricted areas of the registry. Therefore, once an admin user has logged on and run the Client, a standard user can read from the registry’s restricted area.

Note 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.

The next step...

• If you are using Outlook Integration, configure your Sage SalesLogix Client computers as detailed in the following section.

• If you are not using Outlook Integration and you are using Customer Service and/or Support, create Area, Category, and Issue lists as detailed in “Creating Area, Category, and Issue Lists” on page 32.

• If you are not using Outlook Integration, Customer Service, or Support, configure Marketing as detailed in Chapter 7, “Configuring Marketing.”



Understanding Outlook Integration and Intellisync for Sage SalesLogix

Sage SalesLogix is integrated with Microsoft Outlook to allow users to share information between the two applications.

Configuring Outlook Integration and Intellisync for Sage SalesLogixIf your company is using Outlook Integration features, and/or Intellisync for Sage SalesLogix, you must configure synchronization preferences.

By default, the Intellisync for Sage SalesLogix configuration files are created in the ...\Program Files\SalesLogix\SlxIntellisync folder. If necessary, you can change this location after installation. This may be necessary if you are running Sage SalesLogix in a Citrix environment. See the “Changing the Intellisync Default Installation Path” topic in the Administrator Help for detailed instructions.

To configure Outlook Integration and Intellisync for Sage SalesLogix

1. In Sage SalesLogix Client, on the Outlook menu, click Outlook Sync Preferences.

The Options dialog box appears with the Outlook Synchronization tab selected.

2. In the Sync Configuration area, the Contact Sync Group shows as <none>. Click New to select a group. Then, complete the following:

a. Ensure the name of the ad hoc group is SyncSalesLogix.

b. Click OK.

Note If you are using Outlook Integration features without Intellisync for Sage SalesLogix, you do not need to complete the remaining steps. Continue with step 3 to configure Intellisync

Feature Allows users to:

Standard Outlook Integration • Add Sage SalesLogix Contacts to Outlook• Use the Send SLX button in Outlook to record information to

Sage SalesLogix • Save Outlook attachments to Sage SalesLogix• Record to Sage SalesLogix History from Outlook in one click• Drag and drop from the Outlook Inbox to Sage SalesLogix

History• Use the Sage SalesLogix Address Book in Outlook• Attach documents from the Sage SalesLogix Library to an

Outlook e-mail• Attach a Sage SalesLogix Contact vCard in Outlook

Advanced Outlook Integration • 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

Intellisync for Sage SalesLogix • Fully synchronize with Outlook• Synchronize to a PDA• Add Outlook Contacts to Sage SalesLogix

If your company uses Lotus Notes or GroupWise, see the “Setting Sync Preferences for Outlook and Intellisync” topic in the Sage SalesLogix Client Help for step-by-step configuration instructions.



or proceed to “Adding Address Lists to the Outlook Addressing Tab” on page 32 if you want users to have the ability to perform Sage SalesLogix Contact name resolution in Outlook.

3. In the Sync Configuration area, click Configure. The Intellisync for SalesLogix Configuration dialog box appears.

You do not need to click the Login button for configuring the sync options unless you plan to use several databases. The first time the sync options run, you will be prompted for the database login.

4. To configure contact synchronization, select Contacts.

5. In the Choose Translator dialog box, do the following:

a. Select MS Outlook.

b. Ensure Synchronize is selected in the Operation area.

c. Click OK.

6. Click Configure and then click Advanced Settings.

7. In the Advanced Settings for Contacts dialog box, click the Filters tab, and then click New.

8. In the Filter Name dialog box, type SyncSalesLogix, being sure to capitalize it exactly as shown, and then click OK.

9. On the Conditions tab, complete the following:

a. Click Field, and then select Categories from the list.

b. In the Operator box, select contains.

c. In the Value box, type SyncSalesLogix, being sure to capitalize it exactly as shown.

d. Click Add to List, and then click OK.

The Advanced Settings for Contacts dialog box reappears, displaying the Filters tab. Notice that SyncSalesLogix is added to the list of available filters.

10. Ensure SyncSalesLogix is selected, and then click OK.

The Intellisync for SalesLogix Configuration dialog box appears. Notice that "Contacts Filtering with SyncSalesLogix" appears on the right side.

11. If you want to set up synchronization for other items, such as appointments (meetings and phone calls), events, timeless appointments, or to-dos, select the item, and then click Choose. Repeat Step 5 to select the translator, and then repeat steps 6 through 10. If you do not set up synchronization for timeless appointments, any existing timeless appointments are included on both the Sage SalesLogix and Outlook calendars. However, updates and new timeless appointments are not synchronized.

12. Click OK to close Intellisync for SalesLogix Configuration.

13. In the Confirmation Options area of the Outlook Synchronization tab, Ignore all confirmation items is selected by default. If you want to receive a confirmation message when items are synchronized (not recommended), clear this check box.

14. In the Sync Run Options area of the Outlook Synchronization tab, under Calendar Activities and Contacts, select the options that apply to your sync preferences.

For example, if Automatically (after any activity changes) is selected, automatic synchronization with Outlook is triggered when you delete an activity in Sage SalesLogix.

15. When all settings are complete, click OK.

Adding Outlook Contacts to Sage SalesLogixTo 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 Sage SalesLogix, any changes made to Outlook contacts are sent to Sage SalesLogix.

To create the SyncSalesLogix category in Outlook and assign to a contact

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.

Note The SyncSalesLogix filter is used when synchronizing contacts. It is not necessary to use this filter when you are exporting contact information to Outlook.

Adding Address Lists to the Outlook Addressing TabAdding 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.

To add Address Lists to the Outlook Addressing Tab

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.

Creating Area, Category, and Issue ListsBefore 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.

See the “Setting Sync Preferences for Outlook and Intellisync” topic in the Sage SalesLogix Client Help for information on adding Sage SalesLogix Contacts to Outlook.

The next step...

• If you are using Customer Service and/or Support, create Area, Category, and Issue lists as detailed in the following section.

• If you are not using Customer Service or Support, configure Marketing as detailed in Chapter 7, “Configuring Marketing.”



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 the Area, Category, Issues lists

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.

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.


You have completed tasks 11-15 in the implementation checklist. See Chapter 7, “Configuring Marketing” to continue your installation.


Chapte


r 7
Configuring Marketing
Marketing is fully integrated in the Sage SalesLogix Client and requires no additional configuration. If you want to use the additional functionality provided by Marketing Services, you must configure the Marketing Services Configuration Manager, create a Marketing Services account, and then create a Marketing Services user.

If your implementation does not include Marketing Services, proceed to Chapter 8, “Configuring the Synchronization Server”.

Note Marketing Services is a regional option and may not be available in all locations.

Configuring the Marketing Services Configuration ManagerMarketing Services is a Web-based ASP application that enables users to create and manage fully branded HTML eMarketing campaigns while providing the ability to track results in real-time. Using the marketing services you can upload lead and account information, manage aspects of the campaign on their Web site, and download tracking information to use in Sage SalesLogix Marketing reports. Some views in the Sage SalesLogix Client receive information from the marketing services. If you choose not to create a marketing services account, portions of these views are blank.

To configure the Marketing Services Configuration Manager

1. Click Start, point to Programs, point to Sage SalesLogix, and then click EmPulse Configuration Manager.

2. On the Database tab, set the information for your Sage SalesLogix database(s).

a. In the Select the SalesLogix Server box, select the computer on which the Sage SalesLogix Server is installed.

b. Click Refresh.

c. In the database list, select the databases that the service will connect to for data transfer.

d. Click the Server tab.

3. On the Server tab, configure the TCP/IP settings used to communicate with EmPulse’s server and to configure a SOCKS proxy (if necessary).

a. In the Service host box, type the name of the EmPulse host computer.

The default host is sync.emailpulse.net.

b. In the Service port box, type the port number used by the EmPulse host.

• Use 6501 for a Secure Sockets Layer (SSL) connection.

• Use 6500 if you are not using a Secure Socket Layer (SSL) connection.

c. Select the This server requires a secure connection (SSL) check box if your connection to EmPulse uses a SSL connection.

If you are using 6501 as the EmPulse port, a SSL connection is required and you must select this option.


Install Sage SalesLogix Network Clients as described in Chapter 6, “Installing Network Clients.”

35.2


d. If your Sage SalesLogix Server is not directly connected to the Internet, select the Use a SOCKS proxy check box, and complete the following information.

• In the Host box, type the computer name, IP address, or URL of the computer that hosts the SOCKS server.

• In the Port box, type the SOCKS server port number.

• In the Authentication box, select saUsernamePassword if an account and password are required to log on to the SOCKS server. Select saNOAuthentication if an account and password are not required.

• In the Version box, select your SOCKS version number.

• In the Account name box, type the SOCKS account name (if you selected saUsernamePassword in the Authentication box).

• In the Password box, type the SOCKS password (if you selected saUsernamePassword in the Authentication box).

e. Click the Notifications tab.

4. On the Notifications tab, configure your settings for the SMTP server that is used to send e-mail notifications regarding the processing of batch jobs that are scheduled using the Sage SalesLogix Client. You can also configure the recipients of e-mail notifications.

a. Select the Send e-mail notifications check box if you want EmPulse to send notifications regarding successes, failures, and so on. If you do not want to send e-mail notifications, proceed to step 5.

b. Select the Login required check box if you want to be prompted to log on to the SMTP server before notifications are sent.If a login is required, set the Account name and Password used to log on to the SMTP Server in the appropriate boxes.

c. In the SMTP host box, type the SMTP address of the SMTP Host Server.

d. In the SMTP port box, select the port number on which the SMTP Server communicates with Sage SalesLogix.

e. Select the Include details of failed Service imports and exports check box if you want detailed error reports when transactions between EmPulse and Sage SalesLogix fail.

f. Under E-mail Recipients, select the Campaign manager box if you want to send e-mail notifications to the manager of the campaign as assigned in Sage SalesLogix.

g. Select Request owner to send e-mail notifications to the user that scheduled the request in Sage SalesLogix.

h. Select Service account owner to send e-mail notifications to the individual that owns the account with EmPulse. For example, this may be a Business Partner or some company executive not associated with the campaign in Sage SalesLogix.

i. Select the Other address check box to manually add e-mail addresses to which you want to send e-mail notifications. Use the Other addresses grid to add additional e-mail addresses.

j. Click the Scheduling tab.

5. On the Scheduling tab, set schedules for downloading and processing information from EmPulse.

a. In the Download Responses On section, select which days of the week you want to receive responses from EmPulse.

b. If necessary, select Limit polling and set a time that you want to connect to EmPulse during the selected day(s).

When this option is selected, Sage SalesLogix only attempts to connect with EmPulse during that time of the day.

c. Click the Options tab.



6. On the Options tab, select when you want to receive error messages and other processing options.

• In the Windows Event Logging section, select the events for which you want to receive error messages.

• Errors creates a log if a significant problem occurs, such as loss of data or loss of functionality.

• Warnings creates a log if an event occurs that is not necessarily significant, but may indicate a possible future problem.

• Information creates a log that describes the actions taken by the service. This can be used for troubleshooting problems.

• If necessary, select the Only process responses for active SalesLogix campaigns check box.

When this option is selected, response information is only received from EmPulse for campaigns in Sage SalesLogix that are currently active.

• Select the Map User fields to EmPulse Custom fields check box to automatically map Userfield1 - Userfield10 in the Sage SalesLogix CONTACT and LEAD tables to the Custom 11 - Custom 20 fields in the EmPulse database.

7. Click OK to close the Configuration Manager.

Creating a Marketing Services AccountYou must create a Marketing Services account on the EmPulse Web site.

To create a Marketing Service account

1. On the Sage SalesLogix Client Tools menu, point to Manage, and then click Marketing Services.

The Manage Marketing Services dialog box appears.

2. Click Get started now! to connect to the service provider Web site.

3. Complete the account requirements defined by the provider Web site. This includes identifying a Partner Code, User Logon (Service Login), password, and the account owner’s e-mail address. An access code (Promotion Code) will be supplied by the service provider.

After completing the provider requirements, the Manage Marketing Services screen is populated with the Service Login ID, Service Code, and the account owner’s e-mail address.

Creating a Marketing Services UserYou must add a Marketing Services user that will access the marketing service account.

To create a Marketing Services user



2. Click the Add button.

The Add Marketing Services User dialog box appears.



3. In the SalesLogix User box, select the user that will access the marketing services account.

If you want to automatically import campaign responses associated with this user, select the Automatically import responses for this user check box. If this option is not selected, the user must perform dynamic imports to analyze responses.

4. Under Service Login, the Primary option is selected.

When adding the first Marketing Services user, the Service Login section is disabled. There must always be a primary account and the first user defaults to that primary account. If additional Marketing Services users are added, you can select the Use Primary option to use the Primary credentials when communicating with EmPulse. The Secondary option allows the user to access an account other than the primary. For example, you may want to use one account for your Sales department and another for your Marketing department.

5. In the Owner E-mail box, type the e-mail address of the EmPulse account owner. This option is necessary only if the Service account owner check box is selected in the E-mail Recipients section of the Notification tab on the Marketing Services Configuration Manager.

The e-mail address must be an SMTP address. Use the format [email protected] or “Some Name <[email protected]>".

6. Click OK.


You have completed task 16 in the implementation checklist. See Chapter 8, “Configuring the Synchronization Server” to continue your implementation. If your implementation does not include Remotes, begin using Sage SalesLogix.


Chapte


r 8
Configuring the Synchronization Server
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 Sage SalesLogix Remote Clients 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 ProfilesSage 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 39.

• “Creating an HTTP Synchronization Profile” on page 42.

Creating a Network Synchronization ProfileOne way to synchronize with the main office is through a VPN (Virtual Private Network) connection. Using VPN, Remote users 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.

Creating an FTP Synchronization ProfileFTP 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.

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.



The next step...

Proceed to “Starting the Synchronization Server” on page 45.

39.2


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).

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.

• Ensure your FTP Server is set to use Passive mode. The SSftp.dll only supports Passive mode. If your implementation includes Internet Information Services (IIS), Passive mode is set automatically.

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 an FTP sync transfer profile

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).

Note 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.

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.

For FTP performance tips, see the “Improving FTP Synchronization Performance” topic in the Administrator Help.



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 Infiles folder is outlined in “Setting Up a Sage SalesLogix FTP Site” on page 40.

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 9, “Configuring the Sage SalesLogix Remote Client.”

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.

The next step...

Proceed to “Starting the Synchronization Server” on page 45.



Creating an HTTP Synchronization ProfileHTTP 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.

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.

Note Before creating the HTTP Site, ensure you have IIS with HTTP Support installed and running.

To create an HTTP site

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. Click Start, click Control Panel, double-click Administrative Tools, and then double-click Internet Information Services (IIS) Manager.

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.

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.

You can reset IIS using the IISReset Run command.

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 an HTTP sync transfer profile



3. In the DLL box, select HTTP Sync Transport v1.2 (SShttp.dll).

Note If HTTP Sync Transport is not available in the DLL list, verify the SShttp.dll file is located in the SalesLogix folder.


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).

Use the format: Servername or Servername.DomainName. Do not include http:// before the server name.

Note This is the name of the server the Sync Client connects to, not the URL.

7. In the Port box, type the port number of your HTTP Server.

This is the port number you defined in Step 10 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 Infiles, Outfiles, and FailedTrans folders is outlined in “Setting Up a Sage SalesLogix HTTP Site” on page 42.

13. 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 HTTP Server. In the Password box, type the corresponding password. 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 9, “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.



Starting the Synchronization ServerIf you plan to run Agents using the Synchronization Service, you must manually start the Sync Server and run a synchronization cycle. This manual cycle creates a registry entry that is used by Agent Runner to build a connection string.

Note 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 the Synchronization Server

1. Click Start, point to Programs, point to Sage SalesLogix, and then click Synchronization Server.



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_name-alias_name. In addition, the Sync Server creates the ConfTran.stm file used for conflict resolution.

Modifying Virus-Checking Software for the Synchronization ServerIf 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



Understanding the Monitor ConsoleThe Monitor Console allows you to monitor the status of jobs scheduled on the Sync Server.

If your company has multiple administrators using the Monitor Console, they must be aware that any changes made to the services registered through one Console affect what other Console users can see. Consequently, you must take care when registering and un-registering services. The Monitor Console Help explains this process.

The first time you log on to the Monitor Console, you must set the name of the Sync Server computer. Then you must register the synchronization service(s) to view data. This process is detailed in the Monitor Console Help.

By default, the Monitor Console is installed in C:\Program Files\SalesLogix. To open the Monitor Console, double-click SlxMonitorConsole.exe.


You have completed tasks 17-18 of the implementation checklist. See Chapter 9, “Configuring the Sage SalesLogix Remote Client” to continue your implementation.


Chapte


r 9
Configuring the Sage SalesLogix Remote Client
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 Sage SalesLogix 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 UsersBefore 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.

Using SubscriptionThere are two ways to subscribe to accounts:

• Use subscription rules to request accounts based on specific criteria or conditions.

• As needed, use manual account subscription to select accounts using the Administrator or Sage SalesLogix Remote Client.

Creating Subscription Rules

Subscription rules specify the criteria for selecting accounts from those the user has access to (based on account ownership). For example, a subscription rule may request accounts for all companies in the state of California with revenues over one million dollars.

When a subscription rule is written, only accounts that meet the criteria are sent to the Remote user during synchronization. However, subscription rules are dynamic. Once a rule is written and applied to a user, any new accounts that meet the rule’s conditions are automatically synchronized to the Remote user. Users can have multiple subscription rules applied to them.


Configure the Sync Server as described in Chapter 8, “Configuring the Synchronization Server.”

For detailed instructions to create subscription rules, refer to the “New Subscription Rule or Template” topic in the Administrator Help.

47.2


Manually Subscribing to Accounts

Remote users manually subscribe to accounts by evaluating each account in the main office database and then selecting individual accounts for subscription. A disadvantage of manual subscription is that several synchronization cycles are required before the Remote user receives the account. For example, the first time a Remote user syncs, only a request for the account is sent to the main office. The next time the Sync Server is run, it processes the request and creates a transaction. When the Remote user syncs again, he or she receives the requested account.

To manually subscribe a user to an account, use the Sync tab on the Remote user’s profile.

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 “Adding New Users” on page 24. Then, configure the synchronization options as described in the following section.

Setting Synchronization OptionsSynchronization 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 39 for instructions.

To set synchronization options


2. In the Users view, click the Remote Users tab, and then double-click a user name.

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 39.

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.



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.

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 DatabaseRemote databases are created as a Microsoft SQL Server Express instance.

To create a Remote user database

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 17. 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.

Installing the Sage SalesLogix Remote ClientInstall 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.

Note If your company uses Outlook Integration, ensure you have completed the required steps under “Outlook Integration Requirements” on page 11 before you install the Sage SalesLogix Remote Client.

• If you created an automated installation using the instructions in “Creating Automated Client Installations” on page 27, see “Performing an Automated Installation” in the following section.

• If you did not create an automated installation, see “Performing a Manual Installation” on page 50.


To run the automated installation

1. Distribute the entire folder structure created during the automated installation to the remote computer.

2. Instruct the Remote user to double-click SalesLogix Client.msi in the root folder.

3. Install the Remote user database as outlined in “Installing the Remote User Database” on page 51.







3. On the Install SalesLogix Client screen, click Install SalesLogix Remote Client.






• If the installation did not detect either Microsoft SQL Express or Microsoft SQL Server, the Install Microsoft SQL Express check box appears. Ensure it is selected before you click Finish.

• If your company is not using Intellisync for Sage SalesLogix to share information between Sage SalesLogix and Outlook, clear the Install Intellisync for Sage SalesLogix check box.

After installation, you must install the Remote user database as outlined in the following section.

Installing the Remote User DatabaseBefore 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 Network Identification tab.

• The User name is set to sa.

To install a Remote user database

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 SLXMaster. 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.



Starting the Sage SalesLogix Remote ClientAfter 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 the Sage SalesLogix Remote Client

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


a. In the Username box, type your Sage SalesLogix user name.


c. In the Log on to box, ensure the correct database connection name displays (for example, SLXRemote).

d. Click OK.

3. If you are using Outlook Integration, complete additional configuration steps as necessary. See “Configuring Outlook Integration and Intellisync for Sage SalesLogix” on page 30 for details.

4. Open the SLMailClient.exe.

By default, the Mail Client is installed in C:\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.

Creating a SpeedSearch ScheduleYou 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.

To create a SpeedSearch schedule

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.

For more information on automated synchronization, see the “Sage SalesLogix Synchronization Client” topic in the Sage SalesLogix Client Help.



• 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.


You have completed tasks 19-25 of the implementation checklist. Begin using Sage SalesLogix.


Installing with the Standard InstallationPart II

Chapte


r 10
Implementation Checklist - Standard Installation
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, or include a Remote Office(s).

This implementation checklist outlines the tasks you must complete to implement Sage SalesLogix using the Standard Installation. These tasks are designed to help you organize and make decisions regarding your Sage SalesLogix implementation.

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, refer to the appropriate Upgrading document located in the Documentation folder on the Sage SalesLogix DVD.

Required TasksAll Standard implementations require the following tasks to be completed. Any tasks that are recommended, but not required, are designated as Optional.

Task Page Computer

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

2 Install and configure your system prerequisites. 61 All computers and servers

3 Create and share the logging folders. 65 Synchronization Server

4 For Oracle installations, create your Sage SalesLogix database.

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

137 Database Server

5 Install the Administrative Tools and Servers components.

70 All computers and servers

6 Create Server database connections (if necessary). 72 Sage SalesLogix Server

7 For Oracle installations, create the Net Service Name and Client database connection.


8 Add the appropriate Sage SalesLogix licenses. 80 Administrative Workstation

9 Enter your main office information. 80 Administrative Workstation

10 (Optional) Customize the SpeedSearch indexes (requires SpeedSearch Advanced Server license) and index schedules.


11 If your implementation includes multiple Sage SalesLogix Servers and databases, set up multiple SpeedSearch Services.


12 Configure options. 82 Administrative Workstation

13 (Optional) Activate Advanced Outlook Integration.


57.2


Synchronization TasksIn addition to the “Required Tasks” on page 57, 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. Any tasks that are recommended, but not required, are designated as Optional.

14 Add Office Information for Customer Service and Support.



15 If necessary, configure the SLXSystem.exe to run as a Windows Service.


16 Create departments. 89 Administrative Workstation

17 (Optional) Create administrative roles. 90 Administrative Workstation

18 Add new users and configure user profiles. 91 Administrative Workstation

19 Set user access to Customer Service Management.



20 (Optional) Create teams. 99 Administrative Workstation

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


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


23 For Oracle installations, create a Net Service Name and Client database connection.


24 Start the Sage SalesLogix Network Client. 103 Sage SalesLogix Client computers

25 (Optional) Configure Outlook Integration and Intellisync for Sage SalesLogix on each Sage SalesLogix Network user’s computer.


26 Create Area, Category, and Issue lists.


106 Sage SalesLogix Client computer

27 (Optional) Configure Marketing. 109 Sage SalesLogix Server

Task Page Computer

Task Page Computer

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


2 (Optional) Create a synchronization service profile.


3 Start the Synchronization Server (Sync Server). 121 Synchronization Server



Remote User TasksIn addition to the “Required Tasks” on page 57, the following tasks are required for all implementations that include Remote users. If your implementation does not include Remote users, the following do not apply. Any tasks that are recommended, but not required, are designated as Optional.

Remote Office TasksIn addition to the “Required Tasks” on page 57, implementations that include Remote Offices require the following tasks. If your implementation does not include a Remote Office, the following do not apply.

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.

Dashboards Dashboards allow users to display and interact with a variety of analytical information in a dashboard. You can set options to display data relative to a specified fiscal calendar, the Gregorian calendar, or both. See the “Displaying the Sales Dashboard” topic in the Sage SalesLogix Client Help for more information.

Task Page Computer

1 (Optional) Create rules for conflict resolution. 84 Administrative Workstation

2 Create subscription rules and assign them to Remote users.


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


4 Create Remote user databases. 125 Administrative Workstation

5 Install the Sage SalesLogix Remote Client. 126 Sage SalesLogix Remote Client computers

6 Install the Remote user database. 127 Sage SalesLogix Remote Client computers

7 Start the Sage SalesLogix Remote Client on every Remote user’s computer.


8 (Optional) Create a SpeedSearch schedule. 128 Sage SalesLogix Remote Client computers

Task Page Computer

1 Configure the Remote Office profile. 131 Administrative Workstation

2 Add Network users to the Remote Office. 132 Administrative Workstation

3 Create the Remote Office database. 132 Administrative Workstation

4 Install the Remote Office. 133 Remote Office computer

5 Install the Remote Office database. 134 Remote Office Database Server

6 Start the Remote Office Sync Client. 134 Remote Office computer

7 Install the Remote Office Network Clients. 135 Sage SalesLogix Client computers



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.

Password Options You can set restrictions on user passwords. For example, you can require that all users have a password (not blank). See the “Setting Password Options” topic in the Administrator Help for more information.

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.

Sage SalesLogix Mobile Sage SalesLogix Mobile extends Sage SalesLogix functionality to Pocket PC and BlackBerry devices. Sage SalesLogix Mobile provides instant access to customer information wherever you are and exactly when you need it; all via a compact, convenient, handheld-based application. Sage SalesLogix Mobile is add-on functionality that requires separate installation and pricing. Contact your Sage SalesLogix representative for more information.

Windows Authentication With Windows Authentication, users are automatically logged on without entering their Sage SalesLogix user names or passwords. See the “Using Windows Authentication” topic in the Administrator Help for more information.


Chapte


r 11
Before installing Sage SalesLogix, review and address the system prerequisites. This chapter outlines the necessary requirements and the files and folders that must be created for a successful implementation.

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

implementation.

• Compatibility Checklist. Refer to this document to ensure your hardware and software meet Sage SalesLogix supported versions.

• 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, Sync Client, or Mail Client.

• Sage SalesLogix database is placed in its own instance. This applies to Oracle implementations only.

• 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 Microsoft DAC (Windows Vista). 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/Microsoft DAC on that server.

• Microsoft SQL Express installed on the Administrative Workstation. Microsoft SQL Express is required if you have a Microsoft SQL Server 2000 or Oracle database and there will be Remote users or Remote Offices created, 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 SLXMaster. If you install SQL Express from another source, you must set the sa password to SLXMaster (it is generally blank). To install SQL Express with the same configuration settings as Sage SalesLogix, use one of the following files on the Sage SalesLogix DVD:



• Microsoft .NET Framework. .NET Framework is required for .NET Extensions on the Administrative Workstation, Architect, and Sage SalesLogix Client computers.

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

61.2


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

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

• TCP/IP installed and configured on every computer running Sage SalesLogix. TCP/IP is required as the network communication protocol.

• Microsoft Internet Explorer. You must install Internet Explorer on every computer running Sage SalesLogix. Refer to the Compatibility Checklist for supported versions.

• 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 XP, Collaboration Data Objects can be installed from the Control Panel > Add or Remove Programs > MS Office > Change > Add or Remove Features > Microsoft Outlook > Collaboration Data Objects > Run from My Computer.

• For Outlook 2007, download Collaboration Data Objects version 1.2.1 from the Microsoft Web site at www.microsoft.com.

• 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 computer for mail merge.

• Crystal Reports Professional. 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 as an option on the Sage SalesLogix DVD browser.

• Mail client configured on the Administrative Workstation.

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

• Required hardware and software for Web components. See the Sage SalesLogix Web Implementation Guide for complete details.

• 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.

For Visual Studio installed with Microsoft SQL Server 2005, launch Visual Studio > Tools > Options > Debugging > Just-In-Time > and clear all three options.

Server RequirementsIn addition to the “General Requirements” on page 61, ensure the Server computer(s) meet the following requirements.

• Microsoft SQL Server or Oracle (See the Compatibility Checklist for details on supported versions). Your database platform must be installed and running on the Database Server.

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

Note 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.

• Local System Account or SLXService user. The default Windows’ Local System Account includes the privileges necessary for Sage SalesLogix services. However, if you have changed the Local System Account or prefer to specify a different user, create the SLXService user as follows:

Note 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 in order for Agents to work correctly.

• Create the SLXService user in your company’s domain. This is the security domain for the area of the network where the Sage SalesLogix Server, SpeedSearch Service, and Synchronization Service are located.



• Add the SLXService user to the local Administrators group on the Sage SalesLogix Server, SpeedSearch Server, and Sync Server computers. The local domain is the security domain for that particular computer.

• 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.

• Set Full permissions for the Library and Documents folders on the Administrative Workstation, as well as for the Sync Logs folder on all Sync Servers.

• Sage SalesLogix Logging Folders. Create and share the logging folders as detailed in “Understanding Logging Access” on page 65.

• Oracle Provider for OLE DB Components (Oracle implementations only). When installing, ensure that the Oracle Provider version matches your Oracle Server and Oracle Client version. The major version for all three pieces must be the same or compatibility issues may arise.

• 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 computer where you are installing the Sage SalesLogix database.

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

• Microsoft SQL Server Client and Server component versions match. For example, if the Connection Manager uses the Microsoft SQL Server 2005 driver, then the Sage SalesLogix Clients must use the 2005 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• Oracle Server, Oracle Client, and Oracle OLE DB Provider component versions match. The

Oracle version installed on your Database Server must be the same major version that is installed on your Client computers. Compatibility issues arise when the versions are different.

Client RequirementsIn addition to the “General Requirements” on page 61, ensure the following are set up on each Client computer.



• Microsoft SQL Express or Microsoft SQL Server. For Remote Clients only, Microsoft SQL Express or Microsoft SQL Server must be installed. See the Compatibility Checklist for supported versions.




• Microsoft Outlook. You must install Outlook if you are using Outlook Integration. Ensure Outlook is installed and configured before installing Sage SalesLogix.

See “Outlook Integration Requirements” on page 65 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).

To access this setting from the Windows Control Panel, double-click Display. On the Settings tab, click Advanced.

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

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.

• Use User Account Control (UAC) to help protect your computer. If you are running Sage SalesLogix on Windows Vista, ensure this setting is disabled.

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.

• Oracle Provider for OLE DB Components (Oracle implementations only). 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.

SpeedSearch RequirementsIn addition to the “General Requirements” on page 61, 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 does not have enough inherited permissions to run the service.

Remote Office RequirementsIn addition to the “General Requirements” on page 61, 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.



Outlook Integration RequirementsIn addition to the “General Requirements” on page 61, ensure the following requirements are met if you are using Outlook Integration.

• Install and configure Outlook before installing Sage SalesLogix.

• Set Internet Security. If your company uses Windows 2003, you must adjust the default Internet Security setting in order for the Outlook Integration menu and toolbar items to display.

To adjust security, open Internet Explorer. On the Tools menu, click Internet Options, click the Security tab, and then set the Security level for the Internet zone to any setting other than High.

• Download the WinHelp Engine (WinHlp32.exe). If you are running Sage SalesLogix on Windows Vista and will synchronize information using Intellisync for Sage SalesLogix, you must download the WinHelp engine to access the Online Help. Windows Vista does not include the Help engine necessary for viewing the Intellisync for Sage SalesLogix Help. Refer to the Microsoft Web site for download information.

Understanding Logging AccessVarious Sage SalesLogix services and applications need access to the local file system or logging folders in order 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).

• 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 FoldersThe following logging folders must be created and shared for a Sage SalesLogix implementation.

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 FoldersIf 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 the logging folders

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).

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).

Creating the Remote Office FoldersA 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 (RemOfficeSync 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 the Remote Office synchronization folders

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.

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 67.



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

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

Sharing Folders and Granting Access RightsThe 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 UsersTo share Sage SalesLogix 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.

Sharing Folders and Granting Rights to User GroupsUser 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.

Note 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.

User Group Represents

SlxAdmin System Administrator and SLXService user

SlxNetwork Sage SalesLogix Network users

SlxSync Sage SalesLogix Synchronization Server

SlxRemote Sage SalesLogix Remote users



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.

Understanding Additional Security OptionsTo 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.

Running Sage SalesLogix as a Restricted UserAlthough 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.

• (Read/Write Access) Program Files\Common Files\PUMATECH Shared - 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 from the Windows folder to the Windows Folder\System 32.

Note 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.

User Group Type of Access

SlxAdmin Full Control

SlxNetwork Change

SlxSync Change

SlxRemote Change


You have completed tasks 1-3 of the “Required Tasks” checklist. See Chapter 12, “Installing with Sage SalesLogix Standard” to install Sage SalesLogix. If you are installing Sage SalesLogix on Oracle, see Appendix A, “Creating a Database for Oracle” before installing Sage SalesLogix.


Chapte


r 12
Installing with Sage SalesLogix Standard
The Standard installation allows you to choose what components you want to install and the location where you want to install them.

Understanding Sage SalesLogix DatabasesThe Standard installation installs two Microsoft SQL Server databases if Microsoft SQL Server is detected on the computer on which you are installing the Sage SalesLogix Server. If you have an Oracle database, you must create your database manually using the steps outlined in Appendix A, “Creating a Database for Oracle”.

Microsoft SQL ServerThe Sage SalesLogix Server component of the Standard installation installs the blank and evaluation Microsoft SQL Server databases, provided that you select the option to install the databases. 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.) unless you have specified a different default data directory. 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.


Note While it is possible to create a database on SQL Server with a name beginning with a number, it 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.

OracleThe 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.


Verify you have installed the prerequisites and created and shared folders as described in Chapter 11, “Preparing for Implementation.” 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.”

69.2


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.


Running the Standard InstallationInstall Sage SalesLogix directly from the Sage SalesLogix DVD or from a network drive. To install from a network drive, copy the entire contents of the DVD to a shared network directory.

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.

Note If the Standard installation detects that MDAC must be updated, you will be prompted to install it. The installation may appear inactive while MDAC is installed. After MDAC is installed, the computer is restarted without warning. Then, the Sage SalesLogix installation continues.

To run the Standard Installation


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

3. On the Standard Server Installation screen, click Required Administrative Tools and Servers.

Note If you do not have Microsoft .NET Framework installed, the installation may appear to be inactive while installing the Framework. This installation may take a long time.

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.

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 the Sage SalesLogix Server, Sage SalesLogix Databases (Microsoft SQL Server only), Administrative Workstation, Application Architect, Synchronization Server, SpeedSearch Server, and Marketing Services (EmPulse) on this computer.

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 Marketing Services (EmPulse) to install the Marketing Services Configuration Manager and other Marketing components.

• Select Custom to choose the components you want to install and the location where you want to install them on this computer.

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

• 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 “Server Requirements” on page 62.

Note 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 - Type the Sage SalesLogix Service user’s password.

• Confirm - Re-type the Sage SalesLogix Service user’s password.

• 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.

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

7. On the remaining screens, click Install and Finish to complete the installation. One of the following options may appear on the last screen:

• Launch Administrator - If your database platform is Microsoft SQL Server and your database is installed on the same machine as the Sage SalesLogix Server, select this option and proceed with Chapter 13, “Configuring the Sage SalesLogix System”. Otherwise, do not select this option and continue with the following sections to create database connections.

• Install Microsoft SQL Express - This option appears if you installed the Administrative Workstation without the Sage SalesLogix Server. Microsoft SQL Express is required on the Administrative Workstation if you have an Oracle database

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



or if the Resync utility will be used. Microsoft SQL Express is optional if you have a Microsoft SQL Server database, but is required if the Resync utility will be used.

• Install .Net AJAX Extensions, Install SQL Server 2k5 Exception Message Box, and Install SQL Server 2k5 Backwards Compatibility - These options are selected as appropriate for your system configuration. If necessary, these components will be installed after Sage SalesLogix.

8. If necessary, reboot your computer.

Creating Database ConnectionsIf your database platform is Microsoft SQL Server, and you are installing the Sage SalesLogix Server on the Database Server, the Sage SalesLogix installation automatically creates two database connections named SalesLogix_Server (to the blank database) and SalesLogix_Eval (to the evaluation database).

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

• 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.

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

• “Creating Microsoft SQL Server 2000 Database Connections” in the following section.

• “Creating Microsoft SQL Server 2005 Database Connections” on page 73.

• “Creating Oracle Database Connections” on page 74.

Creating Microsoft SQL Server 2000 Database ConnectionsUse the following instructions to create a connection to a Microsoft SQL Server 2000 database.

To create a Microsoft SQL Server 2000 connection

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

2. In the SalesLogix Connection Manager, click Add.

3. In the Connection Name box:

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

b. In the Read/Write password for this connection box, type the password used to allow read/write access to Sage SalesLogix data from any third-party applications.

c. In the Read-Only password for this connection box, type the password used to allow read-only access to Sage SalesLogix data from any third-party applications.

d. Click OK.

4. On the Provider tab in the Data Link Properties dialog box, select Microsoft OLE DB Provider for SQL Server, and then click Next.

a. In the Select or enter a server name box, select your Sage SalesLogix Server.

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, masterkey).

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

f. In the Select the database on the server box, select your database.

5. Click Test Connection. If successful, click OK.

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. To save the information and close the Data Link Properties dialog box, click OK.

Creating Microsoft SQL Server 2005 Database ConnectionsUse the following instructions to create a connection to a Microsoft SQL Server 2005 database.

To create a Microsoft SQL Server 2005 connection






The next step...

Proceed with Chapter 13, “Configuring the Sage SalesLogix System”.




d. Click OK.

4. On the Provider tab in the Data Link Properties dialog box, select SQL Native Client, and then click Next.

a. In the Data Source box, type the name of your Sage SalesLogix Server.

b. Under Enter information to log onto the server, ensure Use a specific user name and password is selected.




f. In the Enter the initial catalog to use box, select your Sage SalesLogix database.



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

Creating Oracle Database ConnectionsUse the following instructions to create a connection to an Oracle database.

The next step...

Proceed with Chapter 13, “Configuring the Sage SalesLogix System”.



To create an Oracle database connection







d. Click OK.

4. On the Provider tab in the Data Link Properties dialog box, select Oracle Provider for OLE DB, and then click Next.

If the Oracle Provider for OLE DB is not listed on the Provider tab, ensure you have installed the Oracle OLE DB Provider. See “Server Requirements” on page 62 for more information.

a. In the Data Source box, type the Net Service name for your database.

b. Under Enter information to log on to the server, ensure Use a specific user name and password is selected.








6. To save the information and close the Data Link Properties dialog box, click OK.

Creating Client Database Connections for OracleAfter 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 NameYou 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.

To create an Oracle Net Service Name

1. Click Start, point to Programs, point to Oracle - OraHome, point to Configuration and Migration Tools, then click Net Configuration Assistant.

2. On the Welcome screen, click Local Net Service Name configuration, and then click Next.

3. On the Net Service Name Configuration screen, click Add, and then click Next.

4. On the Database Version screen, select Oracle8i or later database or service, and then click Next.

5. On the Service Name screen, in the Service Name box, type your database name, and then click Next.

6. On the Select Protocols screen, select the network protocol used to connect to and communicate with the database (for example TCP), and then click Next.

7. On the Protocol screen, type your host name in the Host name box, and then click Next.

• If you are running Oracle on Windows, type the computer name of your Database Server.

• If you are running Oracle on UNIX, type the IP address.

8. On the Test screen, click Yes, perform a test to test the database connection, and then click Next.

9. On the Net Service Name screen, in the Net Service Name box, type a name for this database connection (for example, databasename.servername), and then click Next.

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.

10. Click No when prompted to configure another Net Service Name.

11. Click Next, and then click Finish.

Creating a Client Database ConnectionThe 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 a connection in the Data Link Manager

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 72 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.


You have completed tasks 5-7 of the “Required Tasks” checklist. See Chapter 13, “Configuring the Sage SalesLogix System” to continue your implementation.


Chapte


r 13
Once you have installed the components necessary for your implementation, you must log on to the Administrator and complete the following tasks:

• Add licenses.

• Enter Office information.

• 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 AdministratorThe Administrator is used to manage users, servers, and offices. The following steps are also used when logging on to other Client applications, such as Architect, Sage SalesLogix Client, and so on.

To log on to the Administrator

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




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.

Understanding the Setup AssistantThe 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. You can exit the Assistant at any time and add information manually.


Install Sage SalesLogix using the Standard installation as described in Chapter 12, “Installing with Sage SalesLogix Standard.”

79.2


Adding LicensesAll implementations require a Sage SalesLogix license (Standard, Advanced, or Premier). Additional 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.

The first time you log on to a Sage SalesLogix database that does not contain licenses, the Setup Assistant appears.

To add licenses using the Setup Assistant

1. In the Setup Assistant, select Step 1 - Add Licenses using the License Wizard, and then click Run Selected Step.


2. In the Customer ID box, type your customer ID.

Ensure your customer ID matches the ID to which Sage SalesLogix issued licenses. Your licenses correspond with your customer ID.

3. In the License Wizard, add all your licenses, and then click Next.

You can add licenses by typing the license numbers or using copy and paste from a text file. The License Wizard filters extraneous text from the text file.

4. Depending on your implementation, you may see additional screens prompting for information related to a Synchronization Server license(s). Use the following to enter synchronization information:

a. In the Description box, type a name or description for the Sync Server.

b. In the Shared path for Logging box, browse to the Sync Logs folder (for example, \\MyServer\Sync Logs) that you created in Chapter 11, “Preparing for Implementation.”

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. If the path is not entered correctly, the Sage SalesLogix clients will not be able to access the database through the Sage SalesLogix OLE DB Provider.

Note It is not possible to use a logging path on a different (trusted) domain if the SLX Service is using the Local System Account. If you want to use a logging path on a different (trusted) domain, you must change the SLX Service from Local System Account to a domain user with rights on both domains.

c. Click Next.

5. To apply your licenses, click Finish.

Proceed to the following section to complete Step 2.

Entering Office InformationAfter 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 office information using the Setup Assistant

1. In the Setup Assistant, select Step 2 - Enter Office Information, and then click Run Selected Step.


To add office information without using the Setup Assistant, see the “Entering Office Information” topic in the Administrator Help.



2. Type your company information such as division name (if applicable), primary and shipping addresses, and telephone numbers.

Note Only the Company Name is a required field.

3. Click OK.

Adding UsersThe last step of the Setup Assistant simplifies the process of adding Sage SalesLogix users. The process for adding users is detailed in Chapter 14, “Configuring Sage SalesLogix Users.”

Configuring SpeedSearchSpeedSearch 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. It also supports the Keyword Search features in the Sage SalesLogix Client.

Note The Advanced SpeedSearch license is required to search the History and Activity indexes.

By default, the installation creates a shared SpeedSearch folder on the SpeedSearch Server, which contains indexes and is necessary for SpeedSearch to function correctly.

Understanding SpeedSearch IndexesAn index is a collection of files or records that a user can search against. The SpeedSearch Service builds the indexes used for SpeedSearch. The Sage SalesLogix database includes default indexes. You cannot edit these indexes unless you have the SpeedSearch Server Advanced license.

Initially, Sage SalesLogix automatically builds the default indexes and includes the following index schedules:

• Full build – By default, each index is scheduled to be completely rebuilt every Saturday at 12 a.m.

• Incremental build – By default, each index is scheduled to be updated with the changes made since the last build each day Monday through Friday at 12 a.m.

The next step...

Do one of the following:

• Complete the information in the following sections to configure your Sage SalesLogix system. Then use the processes detailed in Chapter 14, “Configuring Sage SalesLogix Users” to add users.

• Refer to Chapter 14, “Configuring Sage SalesLogix Users” to add users. Then return to the following sections to complete your Sage SalesLogix system configuration.

See the “Managing SpeedSearch Indexes” topic in the Administrator Help for a description of the default indexes and for detailed steps on creating new file system and database indexes.

• To change the default index schedules or create new schedules, see the “Managing SpeedSearch Schedules” topic in the Administrator Help.

• To understand how SpeedSearch information synchronizes with Remotes, see the “Understanding SpeedSearch and Remotes” topic in the Administrator Help.



Configuring SpeedSearch for Multiple DatabasesTypical 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.

The following rules apply to this type of configuration:

• Each SpeedSearch Service can handle only one Sage SalesLogix Server.

• Multiple SpeedSearch Services can share the responsibility for different database connections on one Sage SalesLogix Server. (For example, SpeedSearch Service 1 can handle Sage SalesLogix Database 1 and Sage SalesLogix Database 2, while SpeedSearch Service 2 handles Sage SalesLogix Database 3 and Sage SalesLogix Database 4.)

• SpeedSearch Services cannot share responsibility for the same database connection. (For example, SpeedSearch Service 1 and SpeedSearch 2 cannot both handle Sage SalesLogix Database 1.)

Once you have installed all Sage SalesLogix Servers, set up all databases, installed all SpeedSearch Services, and created any custom schedules, complete the following procedure on each machine where the SpeedSearch Service is installed.

To configure each SpeedSearch Service

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

2. Complete the boxes in the Step 1 area of the SpeedSearch Service Configuration Manager following the instructions in the dialog box.

Only change the port number and local SpeedSearch system path if you changed them during installation.

3. Click Refresh Connection List to display all Sage SalesLogix database connections for the selected Sage SalesLogix Server.

4. Select the database connections you want to assign to this SpeedSearch Service.

5. Click OK.

Note If you configured the SpeedSearch Service before creating your schedules, you must click the Run Now button on the Schedules tab of the Manage SpeedSearch Configuration dialog box or stop and restart SpeedSearch to commit your changes.

Configuring Sage SalesLogix OptionsYou 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.

Setting Database OptionsDatabase options allow you to configure the default settings 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.

Refer to the “Configuring SalesLogix Options” topic in the Administrator Help for information on other options.



To set database options

1. On the Administrator Tools menu, click Options, and then click the Database tab.

2. In the Databases Used section, 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.

3. In the Site Codes begin with these characters box, 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.

4. In the Host DB Owner ID box, type the user name of the Remote database owner. This must be set to sysdba.

This is configured automatically when logging on to Sage SalesLogix.

5. In the Host DB Owner password box, type the sysdba password used by the host database.

This is configured automatically when logging on to Sage SalesLogix.

6. In the Host DB Admin ID box, 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.

7. In the Host DB Admin password box, type the sa password used by the host database.

For Oracle, leave this field blank.

8. The Sync Global remote SA Password for existing databases option allows you to set a global SA password for all Remote users and offices. 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.

Note If the Microsoft SQL Express instance on the Remote was installed from the Sage SalesLogix DVD, then the default instance password is SLXMaster.

9. The Server name box 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).

10. In the Create Remote DB in server directory box, 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.

Note 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.

11. Select when you want the Data Transformation Services (DTS) file and Remote database to be created:

• Prepare Remote DB and create it immediately automatically 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. This method requires a user interface and scheduler to connect to the database and run the DTS package.

12. Click OK.

Setting Conflict Resolution OptionsConflict resolution is the process used during synchronization to determine what changes are kept when multiple users change the same data. You can use the default conflict resolution rules, add new rules, or change the existing rules for your implementation. Conflict resolution is only necessary if your implementation includes Remotes.

Up to three criteria may be used to determine which changes update the database when a conflict occurs. Sage SalesLogix analyzes the conflicting transactions, and then determines a win, loss, or tie. In the event of a tie, the next criterion is used to settle the conflict. Generally, if all other options are exhausted, and the transactions are still in conflict, the most recent change to prevails.

The default conflict resolution rules are:

1. The user wins if (s)he is a remote client.

2. If after step one both users are equal, the user wins if (s)he is the owner of the record.

3. If after step two both users are equal, the user wins if (s)he made the most recent change.

Refer to the “Creating Conflict Resolution Rules” topic in the Administrator Help if you want to change the default conflict resolution rules or add additional rules.



Activating Advanced Outlook IntegrationIntegration with Microsoft Outlook enables Sage SalesLogix users to use Outlook’s advanced calendar system when sending e-mail, scheduling activities, and managing contacts. For example, using Outlook enables users to schedule activities for other Sage SalesLogix users using the Attendee Availability tab in the Sage SalesLogix Client.

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 Advanced Outlook Integration

1. On the Administrator Tools menu, click Options, and then click the Outlook tab.

2. Select the Activate Advanced Outlook Integration check box.

After activating Advanced Outlook Integration, you can add Internet domains that you want to exclude from Send SLX functionality. 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.”

3. Click Add.

4. 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.

5. Click OK.

6. Repeat steps 3-5 to add additional domains.

You must configure Outlook Integration in the Sage SalesLogix Client. This configuration is outlined in “Configuring Outlook Integration and Intellisync for Sage SalesLogix” on page 104.

Setting Accounting OptionsAccounting 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.

Adding Customer Service and Support InformationIf 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 customer service and support information


2. Click the Offices tab, double-click your main office in the grid, and then click the Service/Support tab.

See the “Setting Accounting Options” topic in the Administrator Help for details.



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.

• 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 106.

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.

9. Click OK.

Running Sage SalesLogix on a Multiuser EnvironmentIf you are running Sage SalesLogix on a multiuser environment such as Citrix, Web Server, or Terminal Server, it is highly recommended that you configure the SLXSystem.exe to run as a Windows Service. On Windows 2003 SP1 or later, the service must be installed in install mode. Running SLXSystem.exe as a service removes the startup/shutdown time when the Client creates a connection to a database using the SLXSystem.exe.

The SLXSystem service starts and stops when connections are created. However, you can set the service to remain open for a set amount of time before shutting down. To set a specific amount of time for the service to remain open, add the registry key HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\ShutdownDelay(DWORD). The key accepts values 1 through 1440, where the value indicates the number of minutes the service will run before shutting down (after it detects no activity). Setting the value to 0 indicates the service never shuts down.

By default, the SLXSystem.exe service is set to Automatic with a registry value of 0 so that it is always on.

To install SLXSystem.exe as a service

1. If currently running, close the current SLXSystem.exe using Task Manager.

2. On the Start menu, click Run.

Refer to the “Understanding the SpeedSearch Approval Process” topic in the Administrator Help for more information.



3. In the Open box, type “C:\Program Files\SalesLogix\SLXSystem.exe” /install.

The service can be removed using the “C:\Program Files\SalesLogix\SLXSystem.exe” /uninstall command.

Example Registry EntryThe following is an example registry entry that allows the same Data Link to be available for users logging on to Sage SalesLogix.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\CUD]

[HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\CUD\ADOLogin]

[HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\CUD\ADOLogin\Connection1]

"Data Source"="SLX"

"DBPassword"=""

"DBUser"=""

"Extended Properties"="PORT=19026;LOG=ON"

"Initial Catalog"="SLX"

"Provider"="SLXOLEDB.1"

"Alias"="SLX"

@=""

Maintaining Database SecurityAfter 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 Enterprise Manager or DBA Studio.

After changing the sysdba password in SQL Server Enterprise Manager 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.


You have completed tasks 8-15 in the “Required Tasks” checklist. See Chapter 14, “Configuring Sage SalesLogix Users” to continue your implementation.


Chapte


r 14
When creating Sage SalesLogix users, you must add new users and modify the user profile. Optionally, you can create teams. Teams contain users who require access to the same set of accounts.

Planning for Sage SalesLogix UsersBefore 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.

After creating departments, administrative roles, and security profiles, you can apply these rights when creating your users.

Understanding the Admin UserSage 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

• Teams

• Sync

Admin user access is restricted to ensure the system administrator is not included in your company’s security model.

Creating DepartmentsDepartments contain users, but cannot contain teams. However, teams can contain departments. A user can belong to more than one department and more than one team.

The default department named None is automatically applied to all new users.

To create a department


2. On the Edit menu, click New Department.

3. In the Department Name box, type a name for the department, and then click OK.

4. Repeat steps 2-3 to create additional departments.



89.2


Creating Administrative RolesAdministrative users can perform tasks in Administrator normally reserved for the system administrator. To designate someone as an Administrative user, the system administrator creates an administrative role and adds it to the user’s security profile. Administrative users then log on to the Administrator using their user name (for example, Lee or Dan). The system administrator remains as the only user with full access to all features and functions in the system.

Note Administrative roles are not available with the Standard license.

To create an administrative role

1. On the Administrator Manage menu, click Administrative Roles.

2. In the Manage Administrative Roles box, click New Role.

3. In the Enter Role Name box, type a name for the role.

4. Click OK.

5. Double-click each function within the role that you want users assigned this role to have the ability to perform.

Creating Security ProfilesSecurity profiles can exist for a user at the individual level and at the team level. Therefore, a user may have one security profile for accounts owned by a team of which they are a member, and another for accounts owned by them as an individual.

Security profiles enhance standard security by allowing you to limit access to specific tables and fields. For example, Dan is Lee’s assistant. You want to add Dan to the same team as Lee so that he can find information on Lee’s accounts. However, you want Dan to have access only to the account address and contact information. In this scenario, you create a security profile that limits access to all tables and fields except address and contact. When this profile is applied to Dan, he can only view address and contact information for any accounts owned by Lee’s team.

The following rules apply to security profiles:

• Security profiles never apply to accounts owned by Everyone. Using Everyone for account ownership is equivalent to no security.

• Security profiles never apply to accounts owned by a specific user. For example, if an account is owned by Lee, Lee will always have full access to that account.

• Security profiles apply to accounts that are owned by an individual, but are accessed by another user. For example, if Lee is the account owner, Dan may be given Read Only access to the account. Lee will always have full access and Dan will have Read/Only access.

The following default security profiles can be applied to new users:

• Read Only Default - Sets all database tables and fields to Read Only access.

• Read/Write Default - Sets all database tables and fields to Read/Write access except the Account table Seccodeid field. This restricts the user from reassigning account ownership.

• Team Owner Profile - Sets all database tables and fields to Read/Write access. This allows the user to reassign account ownership.

Note Field security profiles are not available with the Standard license.

For detailed information on each function, see the “Administrative Functions” topic in the Administrator Help.



To create security profiles

1. On the Administrator Manage menu, click Field Security Profiles.

2. In the Security Profile Manager, click Add.

3. In the Description box, type a name for the security profile.

4. In the Profile Type box, select User or System.

No functional difference exists between the two profile types; they are simply for organization. System profiles can indicate templates for entire groups, while User profiles indicate a security profile for one user.

5. Use the tree view to select which tables/fields to restrict access to with this profile. To restrict all fields listed for a table, select the table. To select specific fields in a table, expand the table and press CTRL while you select each field. Then, click one of the following buttons:

• No Access – Users cannot view or edit the data.

• Read Only – Users can only view the data.

• Read/Write – Users can view and edit the data. This is the default option assigned to all tables and fields.

6. Click OK.

7. Add additional profiles as appropriate.

Creating UsersBefore 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:

The following sections detail how to create a custom user template, add users based on existing Windows’ users, and then how to complete and activate the new users.

Creating User TemplatesUser templates define the settings you want to use when creating new users. For example, you can create a template named Manager. This template establishes the generic user profile for all managers in your company. Then, when you create users and apply the template, the manager’s profile is already configured with the appropriate settings.

To create a user template


2. In the Users view, click Add.

3. In the Add box, select Template.

4. In the Quantity box, type or select the number of user templates that you want to add.

5. Click OK.

Once the template is created, the User Profile dialog box appears, in which you can configure the template settings. The settings required for adding and configuring user templates are outlined in the following sections. Additional settings that apply to individual users (not templates) are discussed in “Configuring Users” on page 98.

For detailed information on default Sage SalesLogix user templates, see the “Creating a User Template” topic in the Administrator Help. If necessary, you can customize the default templates.


Add new users based on an existing user template

You can add new users based on an existing user template or a custom user template you create.

Create Sage SalesLogix users based on existing Windows’ users

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.

Import users from a comma-delimited text file 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.

Create users individually 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.

For information on other user options not detailed here, refer to the “Modifying a User’s Profile” topic in the Administrator Help.



Configuring General Options

The User Profile General tab sets information that identifies the user to Sage SalesLogix. This information is used in reporting, document templates, and security.

To set general options

1. In the User Profile dialog box, click the General tab.

If necessary, double-click a user in the Users view to open the profile.

2. In the Username box, type a name for the user template.

3. In the Name box, type the name of the user template.

This name displays when selecting the template to apply to other users. To correctly display a template name that contains more than one word, click the ellipsis button and add the name in the Last Name box.

4. Complete the Region, Division, Department, Manager, and Notes fields as appropriate.

Note Only Managers that can appropriately be a user’s manager display in the Manager box.

Refer to the next section to set options on the Employee tab.

Setting Employee Options

The User Profile Employee tab sets company and personal information for the user. The Employee tab also contains user-level information that allows Sage SalesLogix to communicate with supported accounting applications.



To set employee options

1. In the User Profile dialog box, click the Employee tab.

If necessary, double-click a user or template in the Users view to open the profile.

2. In the Work section, enter the user’s company name and address and work phone and fax numbers.

Refer to the next section to set options on the Security tab.

Setting Security Options

The User Profile Security tab sets the default security profile for a user. With advanced security, each user and team can be assigned a different security profile. This profile determines if the user can add or delete a view and what default view displays for the user when they log on to the Sage SalesLogix Client.

Note Feature security is not available with the Standard license.

To set security options

1. In the User Profile dialog box, click the Security tab.

If necessary, double-click a user in the Users view to open the profile.

2. In the Feature Security section, configure the user's rights to add or delete information in the Sage SalesLogix Client.

a. In the Entity Name box, select the main view type for which you want to set security.

The Entity Name list is dynamic based on your database. The list contains every main view for every main table that exists in your database. For example, Accounts, Contacts, Campaigns, and so on.

b. In the Allow user to section, select or clear the appropriate check box to determine if the user can add or delete records within the main view type.

For example, if you do not want this user to be able to add accounts, select Account in Entity Name box and then clear the Add ACCOUNTS check box.

c. If appropriate, in the Detail View and Lookup View boxes, select the name of the view that you want to appear when the user views the details or looks for information on the selected entity type. The fields default to the appropriate system view.

3. In the Default field security profile box, select the profile that will be the default profile when this user is added to a team or another user’s team. You can select a system profile or a custom profile you created using the steps in “Creating Security Profiles” on page 90.

If user A has been manually added to user B’s team (using the Teams tab), user A can access any records that user B can access. However user A’s ability to modify those records depends on their Field Security. Users always have read/write access to all individually owned accounts and accounts owned by Everyone.

4. If appropriate, in the Administrative Role box, select an Administrative Role for the user.



If you did not create administrative roles, refer to “Creating Administrative Roles” on page 90 for more information.

Refer to the next section to set options on the Client System tab.

Setting Client System Options

The User Profile Client System tab defines the word processing, fax, e-mail, and process manager options. Unless you restrict access to these options, users can change these settings on their computers.

To set client system options

1. In the User Profile dialog box, click the Client System tab.


2. In the Accounts box, select the default owner of new accounts created by this user.

3. Use the Fax Provider section to select the user’s default fax provider.

The Microsoft Fax Service (SalesLogix) option uses the Microsoft Fax Service that ships with Microsoft Windows.



4. In the Email section, select your company’s e-mail application. If you are using Outlook Integration, select Microsoft Outlook.

• (Microsoft Outlook) In the Profile Name box, select your local mail system profile.

• (Mail Client) In the Show names in address book by box, select how you want contact names to appear in the address book.

Refer to the next section to set options on the Service/Support tab.

Setting Service and Support Options

The Service/Support tab is used to set options related to customer service, support, and SpeedSearch.

To set service and support options

1. In the User Profile dialog box, click the Service/Support tab.


2. Select the Available for calls check box to allow other users to assign tickets to this user.

3. Select the Notify user of new Ticket check box to send an e-mail message when a ticket is assigned to the user.

An e-mail message is sent if a new ticket is assigned, or an existing ticket is reassigned to this user.

4. Select the User may grant access to Customer Portal check box to allow the user to give customers access to tickets through Web Customer Portal.

5. Select the User has “Submit to SpeedSearch” as default check box to make the Submit to SpeedSearch option selected by default when the user creates a new ticket.

6. Select the User may approve SpeedSearch submissions check box to allow the user to determine which tickets and defects are available through SpeedSearch.

This option is only available if the SpeedSearch approval process is enabled for your office.

7. Select the Notify user of new Defect check box to send an e-mail message when a new defect is assigned, or an existing defect is reassigned to this user.

8. Click OK.

After creating a user template(s), you can apply the template when adding new users. Then, you must configure additional options specific to each user. These options apply to individual users, not templates.

Adding New UsersUse the following sections to add users by importing existing Windows’ users to Sage SalesLogix.

To add users based on existing Windows’ users


2. On the Insert menu, point to Import Users, and then click From Windows.

You can also access the Import Windows Users dialog box from the Setup Assistant. Select Step 3 - Import Users from Windows, and then click Run Selected Step.

For information on other methods of adding users, see the “A New Employee Needs Access to Sage SalesLogix” topic in the Administrator Help.



3. In the Windows Domain box, select the domain from which you want to map your Windows' users.

Existing Windows users appear in the Windows Username and Windows Full Name columns.

4. To quickly locate a specific Windows' user, type a Windows Username in the Search for box.

You can use a variety of search methods in this box. For example, if you type the letter J, all Windows user names that contain a J will appear.

5. Press CTRL and select all users that you want to create for a specific user type. For example, select all users that you want to create as Network users.

6. In the User Type box, select the type of user that you want to create.

7. In the Template box, select the user template that you want to apply to the user(s).

You can select a custom template or a pre-configured system template. If you do not select a template, users are created with a blank user profile with only system defaults enabled.

8. Click Create User(s).

A check mark appears next to each user that will be created.

9. Repeat steps 4-8 for all other user types that you want to create.

10. If you want to import information from Windows’ Active Directory to each user’s profile, ensure Update SalesLogix user information with Windows information is selected. Otherwise, clear this check box.

11. If you want to enable Windows Authentication (single log-on) for the selected users, ensure Use Windows Authentication is selected. If you simply want to import the users, clear this option (in this case users will be required to log on to the Sage SalesLogix Client unless you enable Windows Authentication in each user's profile).

12. Click OK to create the new users.

For more information on importing from Active Directory, see the “Importing Additional User Information from Windows” topic in the Administrator Help.



Configuring UsersIf 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.


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 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. Click the Employee tab.

9. If necessary, in the Accounting ID field, type the user's accounting identification code. (This is the ID used by the accounting software.)

10. 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.

11. 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).

12. 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).

Creating system teams is detailed in “Creating Teams” on page 99.

Note Field security never applies to accounts owned by an individual when that individual is the user accessing the accounts.

13. Click the Calendar tab.

The Calendar tab sets permission rights for users to view and modify other user’s calendars.

14. In the Other Calendars section, click Add Users to set access for this user to add, edit, delete, or sync activities for another user.

15. 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.

16. Click OK.



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


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.

If your installation includes Remote users, additional options are configured in Chapter 18, “Configuring the Sage SalesLogix Remote Client.” Remote user options cannot be configured until you complete various synchronization configuration steps.

Understanding Optional User Configuration TasksAfter 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. They can also be created for different types of accounts.

Creating TeamsThe Sage SalesLogix Planning Guide describes how teams and team security function. Use that information to help you decide how many teams you want and who is on each team.

Teams define who owns an account and which users can access that account. Users can belong to more than one team and their security profiles can be different for each team.

To create a team

1. On the Administrator Navigation Bar, click Teams.

2. In the Teams view, click New Team.

3. In the Create New Team dialog box:

a. In the Team Name box, type the team name.

b. In the Team Owner box, select the user that you want to be the team owner. Teams may have multiple team owners.

c. In the Select team members box, click a user(s) to add them to the team.



d. Click OK.

For more information on teams, including how to set different security profiles within teams and making global changes to teams, see the “Working with Teams” topic in the Administrator Help.


You have completed tasks 16-20 in the “Required Tasks” checklist. See Chapter 15, “Installing Network Clients” to continue your implementation.


Chapte


r 15
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 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 images directly from the upgrade wizard. Then when you add new users and install Sage SalesLogix, the installation includes all service packs and upgrades that are installed on your system.

Important When installing the Sage SalesLogix Client using an automated installation, third-party applications are not installed. This includes Intellisync for Sage SalesLogix (Network and Remote Client) and Microsoft SQL Express (Remote Client). Third-party applications must be installed separately, and can be found in the Redist folder on the Sage SalesLogix DVD.

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 InstallationsYou can create automated installations of the Sage SalesLogix Network and Sage SalesLogix Remote Clients.

Note If you want to customize the standard configuration file or create your own configuration file, see Appendix B, “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 an automated Client installation



3. On the Install SalesLogix Client Installation screen, click Build Network Client Install or Build Remote Client Install.


5. On the Administrative Install Options screen, enter the information as appropriate for your installation type, and then click Next.

• 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.


Create and configure users as described in Chapter 14, “Configuring Sage SalesLogix Users.”

101.2


• In the SalesLogix Server box, select or type the name of the computer on which you installed the Sage SalesLogix Server.


• In the SalesLogix Database Alias box, select or type the name of the database connection.


• 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.

6. 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.


The automated installation is created in the specified shared network location and a shortcut to the installation is created on the desktop.

8. Distribute the shortcut or installation to users.

Installing the Sage SalesLogix Network ClientNote If your company uses Outlook Integration, ensure you have completed the required steps

under “Outlook Integration Requirements” on page 65 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”.


To run an automated installation, instruct the user to double-click the client installation shortcut or custom SalesLogix 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 103 for details.







3. On the Install SalesLogix Client screen, click Install SalesLogix Network Client.






If your company is not using Intellisync for Sage 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. See the following section for details.

Starting the Sage SalesLogix ClientBefore 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 76 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.

• Sage SalesLogix Client

• MailClient.exe (installed with the Sage SalesLogix Client)

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 or she can simply log on and begin using the Sage SalesLogix Client. The Sage SalesLogix Client must write to restricted areas of the registry. Therefore, once an admin user has logged on and run the Client, a standard user can read from the registry’s restricted area.

Note 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.

The next step...

• If you are using Outlook Integration, configure your Sage SalesLogix Client computers as detailed in the following section.

• If you are not using Outlook Integration and you are using Customer Service and/or Support, create Area, Category, and Issue lists as detailed in “Creating Area, Category, and Issue Lists” on page 106.

• If you are not using Outlook Integration, Customer Service, or Support, configure Marketing as detailed in Chapter 16, “Configuring Marketing.”



Understanding Outlook Integration and Intellisync for Sage SalesLogix

Sage SalesLogix is integrated with Microsoft Outlook to allow users to share information between the two applications.

Configuring Outlook Integration and Intellisync for Sage SalesLogixIf your company is using Outlook Integration features, and/or Intellisync for Sage SalesLogix, you must configure synchronization preferences.

By default, the Intellisync for Sage SalesLogix configuration files are created in the ...\Program Files\SalesLogix\SlxIntellisync folder. If necessary, you can change this location after installation. This may be necessary if you are running Sage SalesLogix in a Citrix environment. See the “Changing the Intellisync Default Installation Path” topic in the Administrator Help for detailed instructions.

To configure Outlook Integration and Intellisync for Sage SalesLogix

1. In Sage SalesLogix Client, on the Outlook menu, click Outlook Sync Preferences.

The Options dialog box appears with the Outlook Synchronization tab selected.

2. In the Sync Configuration area, the Contact Sync Group shows as <none>. Click New to select a group. Then, complete the following:

a. Ensure the name of the ad hoc group is SyncSalesLogix.

b. Click OK.

Note If you are using Outlook Integration features without Intellisync for Sage SalesLogix, you do not need to complete the remaining steps. Continue with step 3 to configure Intellisync

Feature Allows users to:

Standard Outlook Integration • Add Sage SalesLogix Contacts to Outlook• Use the Send SLX button in Outlook to record information to

Sage SalesLogix • Save Outlook attachments to Sage SalesLogix• Record to Sage SalesLogix History from Outlook in one click• Drag and drop from the Outlook Inbox to Sage SalesLogix

History• Use the Sage SalesLogix Address Book in Outlook• Attach documents from the Sage SalesLogix Library to an

Outlook e-mail• Attach a Sage SalesLogix Contact vCard in Outlook

Advanced Outlook Integration • 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

Intellisync for Sage SalesLogix • Fully synchronize with Outlook• Synchronize to a PDA• Add Outlook Contacts to Sage SalesLogix

If your company uses Lotus Notes or GroupWise, see the “Setting Sync Preferences for Outlook and Intellisync” topic in the Sage SalesLogix Client Help for step-by-step configuration instructions.



or proceed to “Adding Address Lists to the Outlook Addressing Tab” on page 106 if you want users to have the ability to perform Sage SalesLogix Contact name resolution in Outlook.

3. In the Sync Configuration area, click Configure. The Intellisync for SalesLogix Configuration dialog box appears.

You do not need to click the Login button for configuring the sync options unless you plan to use several databases. The first time the sync options run, you will be prompted for the database login.

4. To configure contact synchronization, select Contacts.

5. In the Choose Translator dialog box, do the following:

a. Select MS Outlook.

b. Ensure Synchronize is selected in the Operation area.

c. Click OK.

6. Click Configure and then click Advanced Settings.

7. In the Advanced Settings for Contacts dialog box, click the Filters tab, and then click New.

8. In the Filter Name dialog box, type SyncSalesLogix, being sure to capitalize it exactly as shown, and then click OK.

9. On the Conditions tab, complete the following:

a. Click Field, and then select Categories from the list.

b. In the Operator box, select contains.

c. In the Value box, type SyncSalesLogix, being sure to capitalize it exactly as shown.

d. Click Add to List, and then click OK.

The Advanced Settings for Contacts dialog box reappears, displaying the Filters tab. Notice that SyncSalesLogix is added to the list of available filters.

10. Ensure SyncSalesLogix is selected, and then click OK.

The Intellisync for SalesLogix Configuration dialog box appears. Notice that "Contacts Filtering with SyncSalesLogix" appears on the right side.

11. If you want to set up synchronization for other items, such as appointments (meetings and phone calls), events, timeless appointments, or to-dos, select the item, and then click Choose. Repeat Step 5 to select the translator, and then repeat steps 6 through 10. If you do not set up synchronization for timeless appointments, any existing timeless appointments are included on both the Sage SalesLogix and Outlook calendars. However, updates and new timeless appointments are not synchronized.

12. Click OK to close Intellisync for SalesLogix Configuration.

13. In the Confirmation Options area of the Outlook Synchronization tab, Ignore all confirmation items is selected by default. If you want to receive a confirmation message when items are synchronized (not recommended), clear this check box.

14. In the Sync Run Options area of the Outlook Synchronization tab, under Calendar Activities and Contacts, select the options that apply to your sync preferences.

For example, if Automatically (after any activity changes) is selected, automatic synchronization with Outlook is triggered when you delete an activity in Sage SalesLogix.

15. When all settings are complete, click OK.

Adding Outlook Contacts to Sage SalesLogixTo 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 Sage SalesLogix, any changes made to Outlook contacts are sent to Sage SalesLogix.

To create the SyncSalesLogix category in Outlook and assign to a contact

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.

Note The SyncSalesLogix filter is used when synchronizing contacts. It is not necessary to use this filter when you are exporting contact information to Outlook.

Adding Address Lists to the Outlook Addressing TabAdding 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.

To add Address Lists to the Outlook Addressing Tab

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.

Creating Area, Category, and Issue ListsBefore 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.

See the “Setting Sync Preferences for Outlook and Intellisync” topic in the Sage SalesLogix Client Help for information on adding Sage SalesLogix Contacts to Outlook.

The next step...

• If you are using Customer Service and/or Support, create Area, Category, and Issue lists as detailed in the following section.

• If you are not using Customer Service or Support, configure Marketing as detailed in Chapter 16, “Configuring Marketing.”



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 the Area, Category, Issues lists

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.

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.


You have completed tasks 21-26 in the “Required Tasks” checklist. See Chapter 16, “Configuring Marketing” to continue your installation.


Chapte


r 16
Marketing is fully integrated in the Sage SalesLogix Client and requires no additional configuration. If you want to use the additional functionality provided by Marketing Services, you must configure the Marketing Services Configuration Manager, create a Marketing Services account, and then create a Marketing Services user.

If your implementation does not include Marketing Services, proceed to Chapter 17, “Configuring the Synchronization Server”.

Note Marketing Services is a regional option and may not be available in all locations.

Configuring the Marketing Services Configuration ManagerMarketing Services is a Web-based ASP application that enables users to create and manage fully branded HTML eMarketing campaigns while providing the ability to track results in real-time. Using the marketing services you can upload lead and account information, manage aspects of the campaign on their Web site, and download tracking information to use in Sage SalesLogix Marketing reports. Some views in the Sage SalesLogix Client receive information from the marketing services. If you choose not to create a marketing services account, portions of these views are blank.

To configure the Marketing Services Configuration Manager

1. Click Start, point to Programs, point to Sage SalesLogix, and then click EmPulse Configuration Manager.

2. On the Database tab, set the information for your Sage SalesLogix database(s).

a. In the Select the SalesLogix Server box, select the computer on which the Sage SalesLogix Server is installed.

b. Click Refresh.

c. In the database list, select the databases that the service will connect to for data transfer.

d. Click the Server tab.

3. On the Server tab, configure the TCP/IP settings used to communicate with EmPulse’s server and to configure a SOCKS proxy (if necessary).

a. In the Service host box, type the name of the EmPulse host computer.

The default host is sync.emailpulse.net.

b. In the Service port box, type the port number used by the EmPulse host.

• Use 6501 for a Secure Sockets Layer (SSL) connection.

• Use 6500 if you are not using a Secure Socket Layer (SSL) connection.

c. Select the This server requires a secure connection (SSL) check box if your connection to EmPulse uses a SSL connection.

If you are using 6501 as the EmPulse port, a SSL connection is required and you must select this option.


Install Sage SalesLogix Network Clients as described in Chapter 15, “Installing Network Clients.”

109.2


d. If your Sage SalesLogix Server is not directly connected to the Internet, select the Use a SOCKS proxy check box, and complete the following information.

• In the Host box, type the computer name, IP address, or URL of the computer that hosts the SOCKS server.

• In the Port box, type the SOCKS server port number.

• In the Authentication box, select saUsernamePassword if an account and password are required to log on to the SOCKS server. Select saNOAuthentication if an account and password are not required.

• In the Version box, select your SOCKS version number.

• In the Account name box, type the SOCKS account name (if you selected saUsernamePassword in the Authentication box).

• In the Password box, type the SOCKS password (if you selected saUsernamePassword in the Authentication box).

e. Click the Notifications tab.

4. On the Notifications tab, configure your settings for the SMTP server that is used to send e-mail notifications regarding the processing of batch jobs that are scheduled using the Sage SalesLogix Client. You can also configure the recipients of e-mail notifications.

a. Select the Send e-mail notifications check box if you want EmPulse to send notifications regarding successes, failures, and so on. If you do not want to send e-mail notifications, proceed to step 5.

b. Select the Login required check box if you want to be prompted to log on to the SMTP server before notifications are sent.If a login is required, set the Account name and Password used to log on to the SMTP Server in the appropriate boxes.

c. In the SMTP host box, type the SMTP address of the SMTP Host Server.

d. In the SMTP port box, select the port number on which the SMTP Server communicates with Sage SalesLogix.

e. Select the Include details of failed Service imports and exports check box if you want detailed error reports when transactions between EmPulse and Sage SalesLogix fail.

f. Under E-mail Recipients, select the Campaign manager box if you want to send e-mail notifications to the manager of the campaign as assigned in Sage SalesLogix.

g. Select Request owner to send e-mail notifications to the user that scheduled the request in Sage SalesLogix.

h. Select Service account owner to send e-mail notifications to the individual that owns the account with EmPulse. For example, this may be a Business Partner or some company executive not associated with the campaign in Sage SalesLogix.

i. Select the Other address check box to manually add e-mail addresses to which you want to send e-mail notifications. Use the Other addresses grid to add additional e-mail addresses.

j. Click the Scheduling tab.

5. On the Scheduling tab, set schedules for downloading and processing information from EmPulse.

a. In the Download Responses On section, select which days of the week you want to receive responses from EmPulse.

b. If necessary, select Limit polling and set a time that you want to connect to EmPulse during the selected day(s).

When this option is selected, Sage SalesLogix only attempts to connect with EmPulse during that time of the day.

c. Click the Options tab.



6. On the Options tab, select when you want to receive error messages and other processing options.

• In the Windows Event Logging section, select the events for which you want to receive error messages.

• Errors creates a log if a significant problem occurs, such as loss of data or loss of functionality.

• Warnings creates a log if an event occurs that is not necessarily significant, but may indicate a possible future problem.

• Information creates a log that describes the actions taken by the service. This can be used for troubleshooting problems.

• If necessary, select the Only process responses for active SalesLogix campaigns check box.

When this option is selected, response information is only received from EmPulse for campaigns in Sage SalesLogix that are currently active.

• Select the Map User fields to EmPulse Custom fields check box to automatically map Userfield1 - Userfield10 in the Sage SalesLogix CONTACT and LEAD tables to the Custom 11 - Custom 20 fields in the EmPulse database.

7. Click OK to close the Configuration Manager.

Creating a Marketing Services AccountYou must create a Marketing Services account on the EmPulse Web site.

To create a Marketing Service account



2. Click Get started now! to connect to the service provider Web site.

3. Complete the account requirements defined by the provider Web site. This includes identifying a Partner Code, User Logon (Service Login), password, and the account owner’s e-mail address. An access code (Promotion Code) will be supplied by the service provider.

After completing the provider requirements, the Manage Marketing Services screen is populated with the Service Login ID, Service Code, and the account owner’s e-mail address.

Creating a Marketing Services UserYou must add a Marketing Services user that will access the marketing service account.

To create a Marketing Services user



2. Click the Add button.

The Add Marketing Services User dialog box appears.



3. In the SalesLogix User box, select the user that will access the marketing services account.

If you want to automatically import campaign responses associated with this user, select the Automatically import responses for this user check box. If this option is not selected, the user must perform dynamic imports to analyze responses.

4. Under Service Login, the Primary option is selected.

When adding the first Marketing Services user, the Service Login section is disabled. There must always be a primary account and the first user defaults to that primary account. If additional Marketing Services users are added, you can select the Use Primary option to use the Primary credentials when communicating with EmPulse. The Secondary option allows the user to access an account other than the primary. For example, you may want to use one account for your Sales department and another for your Marketing department.

5. In the Owner E-mail box, type the e-mail address of the EmPulse account owner. This option is necessary only if the Service account owner check box is selected in the E-mail Recipients section of the Notification tab on the Marketing Services Configuration Manager.

The e-mail address must be an SMTP address. Use the format [email protected] or “Some Name <[email protected]>".

6. Click OK.


You have completed task 27 in the “Required Tasks” checklist. See Chapter 17, “Configuring the Synchronization Server” to continue your implementation. If your implementation does not include Remotes, begin using Sage SalesLogix.


Chapte


r 17
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 Sage SalesLogix Remote Clients 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 ProfilesSage 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 113.

• “Creating an HTTP Synchronization Profile” on page 116.

Creating a Network Synchronization ProfileOne 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.

Creating an FTP Synchronization ProfileFTP 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.



The next step...

Create a synchronization service profile as detailed in “Creating a Synchronization Service Profile” on page 119.

113.2


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).

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.

• Ensure your FTP Server is set to use Passive mode. The SSftp.dll only supports Passive mode. If your implementation includes Internet Information Services (IIS), Passive mode is set automatically.

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 an FTP sync transfer profile



3. In the DLL box, select FTP Sync Transport v1.2 (SSftp.dll).

Note If FTP Sync Transport is not available in the DLL list, verify the SSftp.dll file is located in the SalesLogix folder.


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.

For FTP performance tips, see the “Improving FTP Synchronization Performance” topic in the Administrator Help.



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 Infiles folder is outlined in “Setting Up a Sage SalesLogix FTP Site” on page 114.

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.


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 18, “Configuring the Sage SalesLogix Remote Client.”



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.

Creating an HTTP Synchronization ProfileHTTP 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.

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.

Note Before creating the HTTP Site, ensure you have IIS with HTTP Support installed and running.

To create an HTTP site

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. Click Start, click Control Panel, double-click Administrative Tools, and then double-click Internet Information Services (IIS) Manager.

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.

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.

The next step...

Create a synchronization service profile as detailed in “Creating a Synchronization Service Profile” on page 119.



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.

You can reset IIS using the IISReset Run command.

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 an HTTP sync transfer profile



3. In the DLL box, select HTTP Sync Transport v1.2 (SShttp.dll).

Note If HTTP Sync Transport is not available in the DLL list, verify the SShttp.dll file is located in the SalesLogix folder.


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).

Use the format: Servername or Servername.DomainName. Do not include http:// before the server name.

Note This is the name of the server the Sync Client connects to, not the URL.

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 Infiles, Outfiles, and FailedTrans folders is outlined in “Setting Up a Sage SalesLogix HTTP Site” on page 116.

13. 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 HTTP Server. In the Password box, type the corresponding password. 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 18, “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 ProfileSince 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.

Using Administrator, configure a profile for each of the synchronization services that you want to run. Only one service profile can be created per server. Each service profile can have any number of jobs using many different databases.

• If you have multiple databases that you want to run from one service, you can configure all profiles and jobs while logged on to one database in Administrator, or you can log on to each database individually. However, if you log on to one database to create profiles and jobs for multiple databases, cycle the Sync Server for that database last.

• If you have a secondary Sync Server, you must log on to the database with the secondary Sync Server to enable the server to appear in the Service Configuration dialog box.

To create a synchronization service profile


2. Click the Sync Automation Services tab.



The Sync Services File Path dialog box appears the first time this tab is accessed.

3. In the Sync Services File Path dialog box, type or browse to the shared folder that all synchronization services will access, and then click OK.

If you did not create the SyncService folder, see “Understanding Logging Access” on page 65 for instructions. By default, the Express installation automatically creates this folder in \\My Server\SyncService.

4. Right-click the grid, and then click Add Service.

The Service Configuration dialog box appears.

5. In the Service Name box, type a name for this service (for example, the name of the computer the service is installed on).

6. In the Service Machine box, type or browse to the name of the computer where the Synchronization Service is installed.

7. In the Service Port box, type the port number on which the Synchronization Service sends information to the Monitor Console.

The default port is 8950. Leaving this set to 8950 avoids conflicts. If conflicts occur, only information from one service displays in the Monitor Console.

8. In the Job Name box, type a name for the new job.

The job name is used to display history in the Monitor Console, therefore ensure you use a descriptive name.

9. In the Database list, select the database on which the job runs.

By default, the database to which you are currently logged on displays in the list.

10. In the SyncServer list, select the Sync Server for which this job is run.

11. In the Sync Data list, select the type of processing you want to perform:

• Sync All (Default) applies network and remote transactions, sends remote changes, runs subscription rules and sends new accounts, and runs any pending agents.

• Sync Updates Only applies network and remote transactions and sends remote changes.

12. In the Run on and Daily Schedule boxes, select the dates, times, and frequency of the synchronization cycle.

13. Select the Enabled check box to activate the job and add it to the synchronization schedule.

14. Click Apply Job.



You can create multiple jobs for each sync server. To create additional jobs, right-click the Jobs grid, and click Add Job. Then repeat steps 10-14.

15. Click OK.

Starting the Synchronization ServerIf you plan to run Agents using the Synchronization Service, you must manually start the Sync Server and run a synchronization cycle. This manual cycle creates a registry entry that is used by Agent Runner to build a connection string.

Note 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 the Synchronization Server

1. Click Start, point to Programs, point to Sage SalesLogix, and then click Synchronization Server.



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_name-alias_name. In addition, the Sync Server creates the ConfTran.stm file used for conflict resolution.



Modifying Virus-Checking Software for the Synchronization ServerIf 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

Understanding the Monitor ConsoleThe Monitor Console allows you to monitor the status of jobs scheduled on the Sync Server.

If your company has multiple administrators using the Monitor Console, they must be aware that any changes made to the services registered through one Console affect what other Console users can see. Consequently, you must take care when registering and un-registering services. The Monitor Console Help explains this process.

The first time you log on to the Monitor Console, you must set the name of the Sync Server computer. Then you must register the synchronization service(s) to view data. This process is detailed in the Monitor Console Help.

By default, the Monitor Console is installed in C:\Program Files\SalesLogix (with the Administrative Workstation). To open the Monitor Console, double-click SlxMonitorConsole.exe.


You have completed the “Synchronization Tasks” checklist. See Chapter 18, “Configuring the Sage SalesLogix Remote Client” to continue your implementation.


Chapte


r 18
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 Sage SalesLogix 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 UsersBefore 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.

Using SubscriptionThere are two ways to subscribe to accounts:

• Use subscription rules to request accounts based on specific criteria or conditions.

• As needed, use manual account subscription to select accounts using the Administrator or Sage SalesLogix Remote Client.

Creating Subscription Rules

Subscription rules specify the criteria for selecting accounts from those the user has access to (based on account ownership). For example, a subscription rule may request accounts for all companies in the state of California with revenues over one million dollars.

When a subscription rule is written, only accounts that meet the criteria are sent to the Remote user during synchronization. However, subscription rules are dynamic. Once a rule is written and applied to a user, any new accounts that meet the rule’s conditions are automatically synchronized to the Remote user. Users can have multiple subscription rules applied to them.



For detailed instructions to create subscription rules, refer to the “New Subscription Rule or Template” topic in the Administrator Help.

123.2


Manually Subscribing to Accounts

Remote users manually subscribe to accounts by evaluating each account in the main office database and then selecting individual accounts for subscription. A disadvantage of manual subscription is that several synchronization cycles are required before the Remote user receives the account. For example, the first time a Remote user syncs, only a request for the account is sent to the main office. The next time the Sync Server is run, it processes the request and creates a transaction. When the Remote user syncs again, he or she receives the requested account.

To manually subscribe a user to an account, use the Sync tab on the Remote user’s profile.

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 “Adding New Users” on page 96. Then, configure the synchronization options as described in the following section.

Setting Synchronization OptionsSynchronization 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 113 for instructions.

To set synchronization options


2. In the Users view, click the Remote Users tab, and then double-click a user name.


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.


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.



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.

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 DatabaseRemote databases are created as a Microsoft SQL Server Express instance.

To create a Remote user database

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 82. 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.





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.


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.

Installing the Sage SalesLogix Remote ClientInstall 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.

Note If your company uses Outlook Integration, ensure you have completed the required steps under “Outlook Integration Requirements” on page 65 before you install the Sage SalesLogix Remote Client.

• If you created an automated installation using the instructions in “Creating Automated Client Installations” on page 101, see “Performing an Automated Installation” in the following section.

• If you did not create an automated installation, see “Performing a Manual Installation” on page 127.


To run the automated installation

1. Distribute the entire folder structure created during the automated installation to the remote computer.

2. Instruct the Remote user to double-click SalesLogix Client.msi in the root folder.

3. Install the Remote user database as outlined in “Installing the Remote User Database” on page 127.







3. On the Install SalesLogix Client screen, click Install SalesLogix Remote Client.






• If the installation did not detect either Microsoft SQL Express or Microsoft SQL Server, the Install Microsoft SQL Express check box appears. Ensure it is selected before you click Finish.

• If your company is not using Intellisync for Sage SalesLogix to share information between Sage SalesLogix and Outlook, clear the Install Intellisync for Sage SalesLogix check box.

After installation, you must install the Remote user database as outlined in the following section.

Installing the Remote User DatabaseBefore 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 Network Identification tab.

• The User name is set to sa.

To install a Remote user database

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 SLXMaster. 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.



Starting the Sage SalesLogix Remote ClientAfter 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 the Sage SalesLogix Remote Client

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


a. In the Username box, type your Sage SalesLogix user name.


c. In the Log on to box, ensure the correct database connection name displays (for example, SLXRemote).

d. Click OK.

3. If you are using Outlook Integration, complete additional configuration steps as necessary. See “Configuring Outlook Integration and Intellisync for Sage SalesLogix” on page 104 for details.

4. Open the SLMailClient.exe.

By default, the Mail Client is installed in C:\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.

Creating a SpeedSearch ScheduleYou 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.

To create a SpeedSearch schedule

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.

For more information on automated synchronization, see the “Sage SalesLogix Synchronization Client” topic in the Sage SalesLogix Client Help.



• 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.


You have completed the “Remote User Tasks” checklist. If necessary, see Chapter 19, “Configuring a Remote Office” to continue your implementation. Otherwise, begin using Sage SalesLogix.


Chapte


r 19
Configuring a Remote Office
A Remote Office consists of a group of Network users who access a Remote Office database through a direct connection or wide-area network. Unlike Remote users, these Network users do not individually synchronize with the main office. Instead, synchronization occurs when the Remote Office database synchronizes with the main office.

The main office’s Administrator manages the Remote Office and Remote Office users.

Configuring the Remote Office ProfileBefore configuring the Remote Office profile, you must have a Remote Office license(s) installed. One license is required for each Remote Office.

To configure a Remote Office profile

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.


• Click Custom Settings to enter a login and password for the Remote Office.

• Click OK.

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.

Note It is not possible to use a logging path on a different (trusted) domain if the SLX Service is using the Local System Account. If you want to use a logging path on a different (trusted)



131.2


domain, you must change the SLX Service from 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.

Note If you are connected to the network, browse to the Remote Office folders.

5. Click OK.

Adding Users to a Remote OfficeOnce the Remote Office profile is configured, you can assign Network users to the Remote Office.

To add users to a Remote Office

1. If necessary, use Administrator to create Network users as described in “Adding New Users” on page 96.


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 DatabaseCreate the Remote Office databases using Administrator.

To create a Remote Office database

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 82. To change the settings for this office only, click Options and make the changes.

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.





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.




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 a Remote OfficeThe 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 a Remote Office


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

3. On the Standard Installation screen, click Remote Office Server.

Note If you do not have Microsoft .NET Framework installed, the Sage SalesLogix installation may appear to be inactive while installing the Framework. This installation may take a long time.


5. On the Setup Type screen, select an installation type:

• Select Complete to install all Remote Office components on this computer. Click Next.

• Select Custom to choose the components you want to install and the location where you want to install them on this computer. Click Next.

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

• 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 “Server Requirements” on page 62.

• 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 - Type the Sage SalesLogix Service user’s password.

• Confirm - Re-type the Sage SalesLogix Service user’s password.

• 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.




Installing the Remote Office DatabaseNote 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 a Remote Office database

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.

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.

Starting the Remote Office Synchronization ClientThe 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 131) and shared the RemOffice Sync Logs folder.

The following files are created under the main RemOffice Sync Logs folder.

• Archives

• Infiles

• WGLogs

• What’s New.tlg

To start the Remote Office Synchronization Client

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.

Note Remember to select the Synchronize Changes option on the Administrator > Systems > Offices > Remote Office > Sync Options tab to activate synchronization for this remote office.

Installing Remote Office Network ClientsTo install Sage SalesLogix Network Clients in the Remote Office, refer to “Installing the Sage SalesLogix Network Client” on page 102.


You have completed the “Remote Office Tasks” checklist. Begin using Sage SalesLogix.


Appendix


A
Creating a Database for Oracle
An experienced Oracle database administrator (DBA) is recommended 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.

Note 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 Use these general steps to set up a database on UNIX that meets the requirements for Sage SalesLogix. Ensure the Sage SalesLogix database is placed in its own instance.

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

• “Creating a Database Instance on Oracle 9.2.0.6” on page 137.

• “Creating a Database Instance on Oracle 10.2.0.1” on page 138.

Creating a Database Instance on Oracle 9.2.0.6The following instructions assume you are using the passwords associated with a default Oracle installation. Your Oracle DBA knows if these passwords are changed on your system.

To create an Oracle database instance on Oracle 9.2.0.6

1. Open the Database Configuration Assistant.


3. On the Oracle Database Configuration Assistant screen, select Create a database, and then click Next.

4. On the Database Templates screen, select New Database, and then click Next.

5. On the Database Identification screen, in the Global Database Name box, type the database instance name (for example, SLX), and then click Next.


Verify you have installed the prerequisites and created and shared the logging folders as described in Chapter 11, “Preparing for Implementation.”

137.2

6. On the Database Features screen, clear all options for this database, and then click Next.

7. On the Database Connection Options screen, select Dedicated Server Mode, and then click Next.

8. On the Initialization Parameters screen, click Next.

If appropriate for your installation, change the default settings.

9. On the Database Storage screen, read the database information, and then click Next.

10. On the Creation Options screen, select Create Database, and then click Finish.

Creating a Database Instance on Oracle 10.2.0.1The following instructions assume you are using the passwords associated with a default Oracle installation. Your Oracle DBA knows if these passwords are changed on your system.

To create an Oracle database instance on Oracle 10.2.0.1

1. Open the Database Configuration Assistant.


3. On the Oracle Database Configuration Assistant screen, select Create a database, and then click Next.

4. On the Database Templates screen, select New Database, and then click Next.

5. On the Database Identification screen, in the Global Database Name box, type the database instance name (for example, SLX), and then click Next.

6. On the Management Options screen, click Next to accept the defaults.

7. On the Database Credentials screen, enter and confirm the password that will be used for the listed accounts, and then click Next.

8. On the Storage Options screen, click Next to accept the defaults.

9. On the Database File Locations, Recovery Configuration and Database Content screens, click Next to accept the defaults.

10. On the Initialization Parameters screen, click Finish to accept the defaults.

If appropriate to your installation, change the default settings.

11. On the Confirmation screen, click OK.

12. On the Database Configuration Assistant screen, click Exit.

Creating a Net Service NameAfter creating the database instance, you must create a Net Service Name (also called database alias).

To create an Oracle Net Service Name

1. Click Start, point to Programs, point to Oracle - OraHome, point to Configuration and Migration Tools, and then click Net Configuration Assistant.

2. On the Welcome screen, click Local Net Service Name configuration, and then click Next.

3. On the Net Service Name Configuration screen, click Add, and then click Next.

4. On the Database Version screen, select Oracle8i or later database or service, and then click Next.

The next step...

Create a Net Service Name as detailed in “Creating a Net Service Name” on page 138.


5. On the Service Name screen, in the Service Name box, type your database name, and then click Next.

6. On the Select Protocols screen, select the network protocol used to connect to and communicate with the database (for example TCP), and then click Next.

7. On the Protocol screen, type your host name in the Host name box, and then click Next.

• If you are running Oracle on Windows, type the computer name of your Database Server.

• If you are running Oracle on UNIX, type the IP address.

8. On the Test screen, click Yes, perform a test to test the database connection, and then click Next.

9. On the Net Service Name screen, in the Net Service Name box, type a name for this database connection (for example, databasename.servername), and then click Next.

10. Click No when prompted to configure another Net Service Name.

11. Click Next, and then click Finish.

Configuring the Oracle DatabaseAfter 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. Use Oracle SQL *Plus Worksheet to perform the following tasks:

• Create permanent, temporary, and index tablespace and data files.

• Create an Oracle database login.

Note 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 to Oracle SQL*Plus Worksheet with the Oracle sysdba option. Log on as “sys” with the Connect as option set to sysdba.

Note Due to legacy requirements of an earlier database platform, the name of the Sage SalesLogix schema owner is sysdba.

Creating Tablespaces and Data FilesA 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.

Note The CreateOracleSpace.sql script must be run as the sys user.

To create tablespaces and data files

1. Open the CreateOracleSpace.sql script.

The script is located in the Database\Oracle folder on the Sage SalesLogix DVD.

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. Click Start, point to Programs, point to Oracle Home, point to Database Administration, and then click SQL *Plus Worksheet.

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 Oracle SQL *Plus Worksheet 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. Leave Oracle SQL *Plus Worksheet open and run the script as described in the following section to create the database login.

Creating the Database LoginTo 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.

Note The CreateOracleUser.sql script must be run as the sys user.

To create the database login


2. Browse to the CreateOracleUser.sql script.




After creating the database login, you must import the database structure.

Note 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 StructureSage 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 DVD.

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 the Oracle database structure

1. On the Oracle Server, open a command window.

2. Type imp sysdba/masterkey@database instance name FILE=absolute path to the location of the .dmp file\SLX_Blank.dmp IGNORE=Y

For example, if the database name is SLX, and it is located in the C:\Oracle\Databases folder, the command line would be C:\Oracle\Databases\imp sysdba/masterkey@SLX FILE=C:\Oracle\Databases\SLX_Blank.dmp IGNORE=Y.


Indexing the DatabaseAfter 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.

Note The CreateOracleIndexes.sql script can be run as the sys user or the Sage SalesLogix user “sysdba”.

To index the database


2. Browse to the CreateOracleIndexes.sql script.




Adding Database ViewsAfter 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.

Note The CreateOracleViews.sql script must be run as the sys user.

To add database views


2. Browse to the CreateOracleViews.sql script.




The next step...

You have completed task 4 of the “Required Tasks” checklist. Refer to Chapter 12, “Installing with Sage SalesLogix Standard” to install Sage SalesLogix.


Appendix


B
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 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.

Important When installing Sage SalesLogix using an automated installation, third-party applications are not installed. Third-party applications must be installed separately and include the following: Intellisync for Sage SalesLogix (Sage SalesLogix Client) and .Net AJAX Extensions, SQL Server 2k5 Exception Message Box, and SQL Server 2k5 Backwards Compatibility (Administrative Tools and Servers). Installations for these applications can be found in the Redist folder on the Sage SalesLogix DVD.

Customizing the Sage SalesLogix Configuration FileYou can modify the standard configuration file created using the Build Network Client Install or Build Remote Client Install on the Sage SalesLogix DVD or create your own configuration file. Creating the standard configuration file is detailed on page 27 and page 101.

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 create the Sage SalesLogix configuration file

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 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 CD or shared network folder. For example, copy the entire SalesLogix Client folder on the Sage SalesLogix DVD.

Ensure the .cfg file is in the same folder as the .msi file.

4. Instruct users to run the SalesLogix Client.msi file on their computer.

The .msi file reads the configuration file and installs Sage SalesLogix according to your custom settings.

5. If necessary, instruct users to install third-party applications.

143.2

Understanding Features and PropertiesUse the following settings to customize the Sage SalesLogix 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:

Properties

The following properties can be set in the Sage SalesLogix Client configuration file.

Feature Name Descriptive Name

MailMerge MailMerge

ImportWizard Import Wizard

MailClient Mail Client

NetForm .Net Extensions

ClientHelp Client Help

ImportWizHelp Import Wizard Help

SpeedSearchHelp SpeedSearch Client Help

Documentation Documentation

Property Description Values

CLIENT_TYPE Determines whether to perform a Network or Remote Sage SalesLogix Client installation.

• “1” for a Network Client installation.

• “2” for a Remote Client installation.

BROWSER Determines whether the install was launched from the DVD browser. To skip the "Client Type" screen in the Sage SalesLogix installation, set this property so that the installation assumes it was launched from the browser.

• “Yes” if the installation was launched from the DVD browser (or you want it to think that it was).

• “No” if the installation was launched by some other means. This is the default.

Note To ignore the Client Type screen and proceed with the Client installation, use both of the previous properties. For example, to run a Network Client installation, set CLIENT_TYPE=1 and BROWSER=Yes.

Database Connection Properties

Note 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 The name or TCP/IP Address of the Sage SalesLogix Server.

SLXDBSERVERALIAS 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.


Example Configuration FileThe following is an example of the Features section in the SalesLogix Client.cfg file:

[Features]

NetForm=NO

The following is an example of the Properties section in the SalesLogix Client.cfg file:

[Properties]

CLIENT_TYPE=1

BROWSER=Yes

SLXDBSERVERPORT=1706

SLXDBSERVER=SalesLogix

SLXDBSERVERALIAS=SalesLogix_Eval

RTFFILEPATH=\\<SomeServer>\<SharedFolder>\

MSDEPATH=\\<SomeServer>\<SharedFolder>\SQLExpress\Setup.exe

INSTANCENAME=SalesLogix

SECURITYMODE=SQL

MSDEPATH The String value containing the fully qualified path of the Microsoft SQL Express installation path.

READMEFILE The String value containing the fully qualified path of the readme file.

Microsoft SQL Express Related Properties

Note The following properties can be set in the configuration file and are passed on to the Microsoft SQL Express installation.

INCLUDEMSDE Tells the installation if the Microsoft SQL Express installation should be launched at the end of the Sage SalesLogix Client installation. This property is only used if CLIENT_TYPE=2.

• “1” if Microsoft SQL Express should be installed at the end of a Remote Client installation.

• “0” if Microsoft SQL Express should not be installed. This is the default value.

DISABLENETWORKPROTOCOLS Microsoft SQL Express installation property that determines whether other machines are allowed to connect to this Microsoft SQL Express instance.

• “1” to enable network protocols, allowing other computers to attach to this instance. This is the default value.

• “0” to disable network protocols.

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 “SLXMASTER”.

Property Description Values


DISABLENETWORKPROTOCOLS=0

READMEFILE=\\<SomeServer>\<SharedFolder>\

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 Descriptive Name

SalesLogixServer SalesLogix Server

SyncServer Synchronization Server

SpeedsearchServer SpeedSearch Server

Administrator SalesLogix Administrator

ApplicationArchitect Application Architect

Architect Architect

Utilities Administrative Utilities

Empulse Marketing Services

NetForm .Net Extensions

MailMerge MailMerge


Appendix


C
Glossary
.NET Extensions Allows the display and support of .NET customizations in Sage SalesLogix as standard database plugins.

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.

Archives A folder containing a copy of all files sent to Remote users or Remote Offices, or to the main office during synchronization.

Business Rule A method that is typically executed via code. A Business Rule is used to define the constraints that apply to an entity within a package.

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.

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 within the Sage SalesLogix Client.

Dashboards Part of Sage SalesLogix Client that allows users to display and interact with a variety of analytical information in a dashboard.

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.

Documents Folder A folder containing files that are attached to an account, contact, opportunity, or ticket. For example, a Word letter.

147.2

Glossary

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.

Import Wizard Used to import data into Sage SalesLogix from ACT! by Sage, or other commonly used file formats and databases.

Infiles A folder in which the main office, or Remote users or Remote Offices, place sync files during synchronization.

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.

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.

Method A piece of code associated with an entity. A method usually consists of a sequence of statements to perform an action, and possibly output a value. Methods provide a mechanism for accessing (for both reading and writing) the private data stored in an entity.

Microsoft .NET Framework A component of Windows used to build and run Windows-based applications.

Module A unit of work for the application to function correctly. Modules are parts of an assembly. Modules are always stored in the Bin or reference directory. Modules may contain Smart Parts.

Monitor Console A tool to remotely monitor the status of the Synchronization Server and its scheduled jobs.

Namespace A unique identifier that helps you to avoid duplicate entity names.

Network Clients Users that connect directly to the network database to access and manage customer accounts, contacts, opportunities, tickets, defects, activities, and related information.

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.

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.

Property Properties are contained on each form. Properties control the form behavior and appearance.


Glossary

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 network users that access a single Remote Office database directly. Unlike Sage SalesLogix Remote Clients, 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 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.

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.

Smart Part Forms that allow you to provide the UI for interacting with entities (for browsing, editing, and so on) created using quick forms. A Smart Part can exist outside an entity, but is typically associated with one specific entity. Smart Parts are secured by role.

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.

Sync Logs A root directory of other folders (Documents and Library) used for synchronization and other functions.

Synchronization The process of reconciling changes between remotes (users or Offices) and Network users. Synchronization can occur through a direct connection (LAN/WAN), dial-up connection (RAS), 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.


Glossary

Workspace A container for a Smart Part. Multiple workspaces can be combined in a template to organize Smart Parts.

WGLogs A folder in which Network users place transaction files as changes are made to the database.


Index

Symbols.NET Extensions

defined 147

AAdministrative Roles

applying 94creating 90

Administrative Tools and Serverscomponents of install 70

Administrative users 90Administrative Workstation

defined 147Administrator

configuring 15, 79Administrator rights 9, 61Adobe Acrobat Reader 10, 62Advanced Outlook Integration 30, 104

activating 18, 85requirements 11, 65

Agents 39, 113Application Architect

defined 147Archives folder 134, 147Automated installations 27, 101

BBundles, defined 147

CCalendar options, user 98Citrix 20, 86Client system options, user 95Compatibility Checklist 2Concurrent users 147Configuration file

example 145features 143, 144properties 143, 144

ConfiguringAdministrator 15, 79Remote Office 131

Conflict resolution 84ConfTran file 45, 121Connection Manager

creating Microsoft SQL Server 2000 connection 72

creating Microsoft SQL Server 2005 connection 73

creating Oracle connection 75

Connection, creating to database 72Contacts 147Contract 147Custom Sage SalesLogix installations 143

DDashboards 147Data Link Manager

creating Oracle Client connections 77Database

configuring for Oracle 139creating Client connections 76creating connections to 72creating for remote office 132creating for Remote user 49, 125creating Oracle login 140installing for remote office 134

Database Instance for Oracle 137Database Manager 147Defect 147Departments 89DMP files 69Documentation 2Documents folder 65, 147

EEmployee options 93Everyone

granting rights to 67

FFailedTrans 40, 114Folders

Database 66documents 65FailedTrans 40, 114Infiles and Outfiles 40, 114library 65RemOffice Sync Logs 66SyncService 66

Folders, Sage SalesLogixcreating 66granting rights to

everyone 67sharing 67

Folders, SalesLogixgranting rights to

user groups 67sharing 67

Folders, SyncService 65


Index

FTPserver settings 41, 44, 116, 119setup 40, 114site for Sage SalesLogix, configuring 40,

114sync profile 39, 113sync transfer profile 40, 114

FTP synchronization 39, 113

HHTTP

setup 43, 117site for Sage SalesLogix, configuring 42,

116sync transfer profile 43, 117

IImport Wizard 148Importing Oracle database structure 140Indexes, SpeedSearch 81Infiles 40, 41, 44, 114, 115, 118, 134

folder 148Installations, customizing 143Installing

Remote Client 50, 126Remote Office 133remote office database 134Sage SalesLogix Network Client 28, 102Sage SalesLogix Server 70

Internet Explorer 10, 62

JJoin, defined 148

LLAN Developer’s Reference 2Library folder 65Licenses, adding 16, 80Logging on

Sage SalesLogix applications 15, 79Login

creating for Oracle database 140FTP synchronization 39, 114

MMail client 10, 62MailClient 29, 103MDAC 9, 61MDF files 13, 69Microsoft SQL Express 9, 61Microsoft SQL Server

databases 13, 69Microsoft SQL Server authentication 10, 63Microsoft Word 10, 62Monitor Console 46, 122, 148

NNet Service Name, creating for Oracle 76,

138Network client 148Network synchronization 39, 113Network users

adding to remote office 132Network, sync profile 39, 113

OOffice information

entering 16, 80support options 19, 85

Opportunities 148Options

accounting 19, 85configuring 17, 82configuring for users 25, 98conflict resolution 84database 17, 82

Oracleconfiguring database 139creating database login 140database files 69import database structure 140

Outfiles 40, 41, 44, 114, 115, 118Outlook

integration requirements 11, 65integration with Sage SalesLogix 18, 85prerequisite 11, 64

Outlook integration 30, 104

PPassword

blank database 69evaluation database 70

Planning, for implementation 1Plugins 148Processes

defined 148Profiles

creating for user security 90Remote Office 131Remote user, creating 48, 124support user 96sync transfer for FTP 40, 114sync transfer for HTTP 43, 117Synchronization Service 119user 93

RRelational database management system

(RDBMS) 149RemOffice Sync Logs folder 66Remote Client

creating profiles 48, 124installing 50, 126


Index

Remote Officeadding network users 132configuring 131creating database 132defined 149installing 133sync transfer options 131

Remote Office synchronization clientstarting 134

Restricted user 12, 68Roles, administrative 90Rules, subscription 47, 123

SSage SalesLogix

applications, starting 15, 79license for 16, 80

Sage SalesLogix OLE DB Provider 149Sage SalesLogix Planning Guide 2Sage SalesLogix Remote Client

defined 149subscription 47, 123synchronization options 48, 124

Sage SalesLogix Serverdefined 149installing 70

Saleslibrary folder 65

Security 149advanced 12, 68creating user profiles 90profile 149Sage SalesLogix 94

Security options, user 94Server settings

FTP 41, 44, 116, 119Service options, user 96Site code 149SLXService user

creating 62defined 149

SLXSystem.exe 20, 86Sort orders

setting 10, 63SpeedSearch

configuring 81indexes 81Remotes 81

SpeedSearch Service 81Starting

Sage SalesLogix applications 15, 79Subscription 149

manual account 48, 124overview 47, 123rules 47, 123

Sync Logs folder 149creating 66

Sync transfer optionsremote office 131

Sync transfer profileFTP 39, 113network 39, 113

sync transfer profileHTTP 43, 117

Synchronizationcreating folders 66folder structure 66Remote user options 48, 124Sync Logs Folder 65

Synchronization methods 39, 113Synchronization Server

defined 149starting 45, 121

Synchronization Servicecreating a profile 119defined 149

SyncService Folder 65

TTablespace 139TCP/IP requirements 9, 62Teams 149

adding users 99creating 99user options 98

Templates 92Ticket 149Transaction Exchange Files

defined 149Transfer profiles for synchronization 39, 113Trust relationship 63

UUser

security, Sage SalesLogix 94User groups

granting rights to 67sharing folders 68

Usersadding to teams 99administrative 90concurrent 147configuring profiles 93creating security profiles 90remote office 132setting calendar options 98setting client system options 95setting employee options 93setting security options 94setting service options 96setting team options 98

VVirtual Private Network 39, 113VPN 39


Index

WWeb Developer’s Reference 2Web Implementation Guide 2Web Server 20, 86WGLogs folder 134

Windowssharing folders 68

Windows authentication 10, 63WinFax

Message Manager 29, 103WinHelp engine 12, 65


Sage_SalesLogix_Implementation_Guide

Documents

Transcript of Sage_SalesLogix_Implementation_Guide