Sage SalesLogix Planning Guide

पीडीएफ

दस्तावेज़

Sage SalesLogix Planning Guide

Version 7.5

Developed by Sage SalesLogix User Assistance

Sage SalesLogix Planning Guide

Documentation

Comments

Copyright

Version

Trademarks

Disclaimer

Technical

Support

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

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

Version 7.5 (

090508

)

2008

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.

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 is available to customers with support contracts directly from Sage Software and to Certified Business Partners. Calls are answered during business hours, Monday through

Friday, excluding holidays. Current contact information is available on the Sage SalesLogix

Web site. Customers with a valid technical support contract and a Web access code can request technical support electronically on the Sage SalesLogix SupportOnline/Sage Software Online

Support and Services Web site.

Sage SalesLogix Web site: www.sagecrmsolutions.com

Sage SalesLogix SupportOnline/Sage Software Online Support and Services Web site: http:// support.saleslogix.com

Revisions to this book are posted on the Sage SalesLogix SupportOnline/Sage Software Online

Support and Services Web site. Check this site regularly for current Sage SalesLogix product documentation.

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

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

What You Need to Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Chapter 1 Planning Your Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Defining the Implementation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Determining Project Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Determining the Components of Your Implementation. . . . . . . . . . . . . . . . . . . . . . . . . .3

Identifying Your Internal Implementation Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Implementation Manager or System Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Information Systems (IS) Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Webmaster (for Web installations only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Database Administrator (DBA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Customization Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Review Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Pilot Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Other Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Setting an Implementation Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Planning Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Development Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Rollout Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Training Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Review Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Developing a Prototype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Ordering and Installing Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Importing Data from Legacy Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Training Administrators and Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Understanding System Costs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2 Understanding Sage SalesLogix Components . . . . . . . . . . . . . . . . . . . . . 9

Sage SalesLogix Core Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Sage SalesLogix Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Sage SalesLogix Server and Sage SalesLogix OLE DB Provider . . . . . . . . . . . . . . . . . . . 10

Sage SalesLogix Logging Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Sage SalesLogix Administrative Components . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Application Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Process Orchestration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

SData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

.NET Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Sage SalesLogix Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SpeedSearch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Web SpeedSearch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

SpeedSearch Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Sage SalesLogix Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Synchronization Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Synchronization Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Web Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Web Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Sage SalesLogix Personal Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Sage SalesLogix Client Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Sage SalesLogix Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Customer Service and Support Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Sage SalesLogix Marketing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Sales Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Dashboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Mail Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Sage SalesLogix Remote Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Web Client Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Disconnected Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

WebViewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Web Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Lead Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

SpeedSearch Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Synchronization Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Sage SalesLogix Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

E-Mail Integration Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Sage SalesLogix Exchange Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Intellisync for SalesLogix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Direction of Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Sage SalesLogix Activities, Contacts, and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Conflict Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Intellisync for SalesLogix Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Remote Office Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Web Remote Office. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Additional Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Windows Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

MDAC/Microsoft DAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Microsoft® Windows .NET Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Web Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Adobe Acrobat Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Microsoft Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Microsoft Outlook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Crystal Reports Reporting Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Fax Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Sage SalesLogix Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Express Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Web Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Remote Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Automated Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Customizing Automated Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 3 Understanding Sage SalesLogix Licenses . . . . . . . . . . . . . . . . . . . . . . . 27

Sage SalesLogix Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

SpeedSearch License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Server Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 4 Understanding Sage SalesLogix Security. . . . . . . . . . . . . . . . . . . . . . . . 33

Sage SalesLogix Database Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Connection Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Sage SalesLogix Security and Other Software Applications . . . . . . . . . . . . . . . . . . . . . .35

Third-Party Access Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Sage SalesLogix Product Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Understanding Account Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Individual User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Understanding Security Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Calendar Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Determining Security in the Web Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Identifying Administrative Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

System Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Administrative Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Sage SalesLogix Security and the Windows Operating System . . . . . . . . . . . . . . . . . . .39

Using Windows Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 5 Selecting a Database Management System . . . . . . . . . . . . . . . . . . . . . . 41

Database Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Number of Accounts and Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Number of Active Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Number of New Tables and Fields Added for Customizations. . . . . . . . . . . . . . . . . . . . .41

Understanding Supported Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Microsoft SQL Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Understanding Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Running Other Applications on the Sage SalesLogix Database Server. . . . . . . . . 44

Chapter 6 Understanding Sage SalesLogix Hardware . . . . . . . . . . . . . . . . . . . . . . 45

Administrative Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Random Access Memory (RAM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Central Processing Unit (CPU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Database Server Size Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Number of Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Number of Active Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Estimating the Size of Your Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Approximate Table Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Express Installation Host Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Sage SalesLogix Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Remote Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Synchronization Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Sage SalesLogix Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

SpeedSearch Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Synchronization Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Disk Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

ConfTran.stm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

WriteCache files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Remote Office Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Additional Installation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Chapter 7 Synchronizing in Sage SalesLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Synchronization Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Site Codes and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Determining Your Synchronization Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Network Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

FTP Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

HTTP Secure Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Sync Transfer Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Folder Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Synchronization Folders at the Main Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Main Office Synchronization Sub Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Synchronizing the Main Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Remote Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Synchronization Folders and Remote Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Synchronizing Remote User Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Automatic Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Remote Office Synchronization Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Remote Office Synchronization Sub-Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Synchronizing the Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Remote Office, Account Ownership, and Security. . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Multiple Synchronization Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Multiple Synchronization Servers Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Scheduling the Sync Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Subscription. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Subscription Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Advantages of Subscription Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Subscription and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Unsubscription Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 8 Customizing Sage SalesLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

AppendixA Importing Data Into Sage SalesLogix. . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Importing from ACT! by Sage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Custom Import Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Importing from Common File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Preparing to Import Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Routine Data Imports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

AppendixB Networking Sage SalesLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Network Communication Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Networking Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

WINS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Using Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Running Sage SalesLogix Applications on Citrix MetaFrame . . . . . . . . . . . . . . . . 72

AppendixC Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

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 Guide

This guide helps you to plan for a successful implementation. It provides valuable insight and key technical information not available in any other Sage SalesLogix documentation.

The Sage SalesLogix Planning Guide helps you:

• Develop an installation strategy, identify the implementation team, and determine the role of each member.

• Understand the product components and identify the pieces necessary for Network,

Remote, and Web installations.

• Make informed decisions about selecting a relational database management system

(RDBMS).

• Choose a synchronization method and Synchronization Server hardware (if applicable).

• Prepare your network for Sage SalesLogix.

• Plan for customizations and for importing data from other systems.

Although you may not install or use all of the Sage SalesLogix components and functionality available to you, it is recommended that you familiarize yourself with each element of a Sage

SalesLogix implementation as described in this guide. This way, when you are ready to plan your implementation, you will thoroughly understand your system requirements. The checklist, in

Appendix C, “Planning Checklist” , is available to help you formulate your

implementation plan.

What You Need to Know

The Sage SalesLogix Planning Guide assumes you have a working knowledge of Microsoft

Windows operating systems and experience with relational database management systems.

You should also understand the concepts of a client/server computing environment, in particular, strategies for network and off-site users.

Installing and configuring the Sage SalesLogix Web components requires detailed knowledge of the Sage SalesLogix system, Windows security, Microsoft Internet Information Server, and

Web technology.

Chapter 1 Planning Your Implementation

Planning is essential for a successful Sage SalesLogix implementation. A well thought-out plan defines the business goals you want to achieve, helps you identify system requirements, and helps you ask the right questions and make knowledgeable decisions before the actual implementation. You can avoid many problems by developing a plan in advance of your implementation.

Defining the Implementation Plan

The tasks to successfully implement Sage SalesLogix may differ slightly from one installation to the next. The following are common to all installations:

• Determine project requirements.

• Determine the necessary Sage SalesLogix components.

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

• Set an implementation schedule.

• Prepare your network for Sage SalesLogix.

• Develop a prototype.

• Order and install hardware.

• Decide which data will be imported into Sage SalesLogix and how importing will be accomplished (if applicable).

• Train administrators and users.

This guide helps you develop an implementation plan and schedule necessary tasks.

Determining Project Requirements

First, define the business goals you want to achieve and how you will use Sage SalesLogix to achieve them.

• Describe your company’s objectives and desired outcome.

• Identify the Sage SalesLogix components needed to build the system that meets your company’s needs.

• Identify the impact Sage SalesLogix will have on your company, both for users and support personnel.

If Sage SalesLogix will be installed at multiple sites, we strongly recommend choosing one location as the pilot site in which to test the implementation. A pilot site lets you install and test the system in a live environment with a controlled number of users. Lessons learned at the pilot site will be beneficial for all subsequent installations.

Determining the Components of Your Implementation

This guide explains the components that comprise a Sage SalesLogix installation and how each can benefit your company. As you read this guide, consider:

• The Sage SalesLogix components and how they relate to the system as a whole.

• The relational database management system (RDBMS) that best fits your company and data capacity.

Sage SalesLogix Planning Guide v7.5

Planning Your Implementation

• The hardware for each component and how to configure it for maximum performance.

• The most appropriate methods for synchronizing data between the main office and remote locations (if applicable).

Identifying Your Internal Implementation Team

Leading an implementation requires organizational skills, technical experience, and an understanding of Sage SalesLogix components. As early as possible in the planning process, determine who in your company will assist with the implementation process and rollout.

Installing and configuring Sage SalesLogix requires detailed knowledge of Windows security.

Your system administrator must participate in the installation and customization.

Installing and configuring the Sage SalesLogix Web components requires Microsoft Internet

Information Server and Web technology. An individual familiar with Web technology, such as a Webmaster, should also participate in the installation and customization.

Your implementation team should include individuals who will be responsible for the Sage

SalesLogix project. Assign these team members well-defined roles and responsibilities before starting the project and ensure they understand the time commitment involved. It is important to assign adequate full-time resources to the Sage SalesLogix implementation project. It is also important to develop a communication plan to keep each team member informed of the project status and other related issues throughout the installation.

The following list identifies key players on the implementation team. You can assign other roles based on your project’s requirements and long-term needs.

• Implementation Manager or system administrator

• Information Systems (IS) Administrator

• Webmaster (required for Web installations only)

• Database Administrator (DBA)

• Customization Developer

• Review Team

• Pilot Group

• Other Resources

Implementation Manager or System Administrator

The Implementation Manager (or system administrator) is the team’s primary contact person and is responsible for the overall implementation. This role requires system administration expertise and knowledge of your sales or support team’s organization and requirements. As the project team leader, this person has final authority on implementation strategy and direction. The Implementation Manager (or system administrator) also handles any Network,

Remote, or Web user issues.

Once the implementation is complete, the Implementation Manager typically assumes the role of system administrator to manage the on-going system administration. This includes administering user information, updating and maintaining a clean database, and customizing

Sage SalesLogix.

The amount of time it takes to support Sage SalesLogix depends on how you choose to implement the system and the number of users. Consequently, it is important that the administrator be proficient in the selected databases and applications.

The administrator’s required knowledge and experience will vary from installation to installation based on the relational database management system (RDBMS) selected.

4 Sage SalesLogix Planning Guide v7.5

Planning Your Implementation

Information Systems (IS) Administrator

The Information Systems (IS) administrator manages the required network components. This individual is typically responsible for any network issues that arise during and after implementation. The IS administrator must be proficient in the following areas:

• Windows operating systems

• Networking protocols

• Remote data transfers (Network, FTP, or HTTP), if applicable

• Network architecture and configuration at your site

Sage SalesLogix is a client/server application that requires on-going network administration, so the importance of involving an experienced Information Systems professional cannot be overstated.

Webmaster (for Web installations only)

If your installation includes the Web components, a knowledgeable Webmaster is vital to the implementation team. The Webmaster is responsible for Internet site administration and security.

Database Administrator (DBA)

The Database Administrator administers and maintains the Sage SalesLogix database. This individual must have experience with relational databases, database structures (tables and fields), and database users.

The DBA also controls database security and performs routine maintenance and transaction recovery.

Customization Developer

The Customization Developer works closely with the Sage SalesLogix Implementation

Manager to design and customize Sage SalesLogix. The Customization Developer must be proficient in the following areas:

• Basic scripts (VBScript, Basic Script, Cypress Enable).

• ActiveX Data Object (ADO) for data access.

• Architect (which provides a development environment similar to the Integrated

Development Environment (IDE) found in Visual Basic).

• Application Architect (which provides a Web development environment based on

ASP.NET).

• Microsoft SQL or Oracle.

• Cascading style sheets (CSS) (Web only).

• HTML and/or DHTML (Web only).

• Internet Information Services (Web only)

• JavaScript (Web only).

• Additional languages or applications necessary to customize your system.

Review Team

This team may include business owners, senior managers, sales or support managers, and sales representatives. Company executives on the Review team work with the

Implementation Manager to ensure that the project meets strategic objectives. Managers and their staff define system requirements, determine customizations, and ensure the Sage

SalesLogix implementation meets their needs. This group can also function as a pilot group for the initial implementation. For Web installations, the review team should understand the requirements and approve prototypes of the system. (See,

“Developing a Prototype” on page 7 .)

Sage SalesLogix Planning Guide v7.5

Planning Your Implementation

Pilot Group

This team is the first group of users to test the product. Therefore, it should include individuals from a cross-section of the company. The team evaluates the Sage SalesLogix implementation before it is available to all users. Members of this team review data, customizations, and workflow, and make recommendations for improvement. It is important that the pilot group include individuals from every segment of the company that will be using

Sage SalesLogix. Their feedback is essential to the successful integration of Sage SalesLogix with current company processes.

Other Resources

In addition to individuals within your company, you may also want to consider the following resources:

Sage SalesLogix Business Partners These individuals are certified to install and support

Sage SalesLogix. They can assist with any customizations and scripting that may be required.

Sage SalesLogix Professional Services Group (PSG) This is an internal services department of Sage Software. The individuals in PSG are trained to manage the entire implementation project and can assist your Business Partner. Their services include customizations, data import, implementation planning, requirements definition, and installation configuration.

Consultants Internal or external consultants are another resource for implementation assistance. Although these individuals may not have the product experience, they can offer expertise in relational databases and client/server networks.

Setting an Implementation Schedule

As you plan your implementation, create a schedule for the tasks you want to accomplish.

This schedule allows you to see the time required for each task and to organize your projected completion dates. Initially, keep the process as simple as possible, and then expand it as you go. Adding complexity to the system (such as elaborate customizations) extends the rollout accordingly.

The following sections identify the tasks associated with each phase in a Sage SalesLogix implementation. You can add more tasks as needed. Once you identify tasks, assign estimated completion dates for each. You can save time and shorten the implementation cycle by combining some tasks or performing them concurrently. For example, you might conduct end user training during the final weeks of installation.

Planning Phase

• Identify an implementation team

• Perform a needs analysis

• Determine project requirements and specifications

• Establish hardware requirements and specifications

Note

For Web installations, do not establish hardware requirements until after prototyping is complete.

Development Phase

• Determine the implementation schedule

• Develop a prototype (particularly important for Web installations)

• Review the requirements and prototype

• Finalize the prototype

• Approve and freeze customizations

6 Sage SalesLogix Planning Guide v7.5

Planning Your Implementation

Rollout Phase

• Install and set up hardware

• Install Sage SalesLogix components

• Import legacy data (if necessary)

• Enter the initial data

• Test the system

Training Phase

• Schedule Administrator training

• Schedule end user training

Review Phase

Review the installation and determine if modifications are necessary.

Developing a Prototype

Sage SalesLogix is ready to install and use with only minor modifications. However, if your implementation plan calls for a large number of Remote users or many customizations, then a prototype is strongly recommended.

Developing a prototype is required for Web installations. Since many factors play a role in determining the number of Web servers your installation will require, a prototype is the only effective way to determine the needs of your company.

A prototype verifies that the application performs to your specifications and that the product operates in its intended environment. A prototype does not necessarily require a lot of customized views or reports in order to understand key Sage SalesLogix functions, such as security and synchronization.

Ordering and Installing Hardware

Determine what hardware you already have and the hardware you will need to purchase.

Order your hardware (or software) as early as possible in the implementation cycle. Most manufacturers have an ordering lead-time (the time between your equipment order and delivery), so make sure that the hardware delivery fits into your overall schedule. Failure to plan for equipment orders may significantly affect your implementation.

Importing Data from Legacy Systems

Sage SalesLogix easily imports ACT! by Sage; custom databases such as dBase, Paradox, and

ASCII; and any database with ADO connections. You can import accounts, contacts, activities, notes, and history from legacy systems to Sage SalesLogix, as well as map current users to Sage SalesLogix users. Evaluate your company’s existing systems and decide which systems will interface with Sage SalesLogix.

Research your particular importing scenario in detail to ensure that the desired result is achievable. When importing data into Sage SalesLogix, a Business Partner or Sage SalesLogix

PSG Engineer is a valuable resource. For more information, see Appendix A, “Importing Data

Into Sage SalesLogix”

Sage SalesLogix Planning Guide v7.5

Planning Your Implementation

Training Administrators and Users

Do not underestimate the importance of training your system administrators and users. Train administrators to configure and manage the system, and train users in the everyday use of

Sage SalesLogix.

A number of Business Partners offer training; some are Web-certified. You may also take advantage of training from the Sage SalesLogix Training Department.

• Everyone attending training must be familiar with the Microsoft Windows environment, including Internet Explorer. Administrators must have a good understanding of networking and relational database management systems (RDBMS).

• Administrators who attend Web product training must have knowledge of Web site administration and HTML.

Sage SalesLogix offers training programs designed to meet your needs. Please contact [email protected] for more information about available Web-based and classroombased training options. Contact the Training Department as far in advance of your implementation to ensure the classes and dates you want are available.

Understanding System Costs

When planning your Sage SalesLogix implementation, it is extremely important to consider the total system cost. Depending on the system size and total number of users, the Sage

SalesLogix software, licenses, hardware, and third-party products may be only a small part of the total system cost. Other costs may include resources, customization, training, and so on.

Consider the following costs and expenditures associated with a Sage SalesLogix implementation. These items contribute to the total system cost that must be included in your budget.

• Sage SalesLogix Licenses (including server and user licenses)

• Sage SalesLogix hardware

Hardware includes the Sage SalesLogix Server, Administrative Workstation, and Sage

SalesLogix Client installations.

• RDBMS

Your selected RDBMS costs include the RDBMS application, licenses, training, setup, administration, support, and maintenance resources. If you have multiple RDBMS’ (for example, an Oracle Host and Microsoft SQL Remotes), make sure you budget for both systems.

• Support personnel

• Data import and conversion from legacy systems

• Overall implementation

• Customization

• Training

• Additional software licenses (if applicable), such as Microsoft Outlook, Exchange, or

Office

8 Sage SalesLogix Planning Guide v7.5

Chapter 2 Understanding Sage SalesLogix Components

Each Sage SalesLogix installation contains required and optional components that you use to meet your company’s needs. This chapter explains the following Sage SalesLogix product components:

• Core components

• Administrative components

• Server components

• Client components

• E-Mail Integration components

• Remote Office components

• Additional software

• Sage SalesLogix installations

Using these components, you can create environments that support any combination of

Network users, Web users, Remote users, and Remote Offices.

Figure 1 Sage SalesLogix components

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

To assist you further with planning your implementation, hardware considerations for the

components listed in this chapter are discussed in Chapter 6, “Understanding Sage SalesLogix

Hardware” .

Sage SalesLogix Core Components

These components are required regardless of the other components you select for your system. The core components are:

• Sage SalesLogix Database

• Sage SalesLogix Server and Sage SalesLogix OLE DB Provider

• Sage SalesLogix Logging Folders

Sage SalesLogix Database

The Sage SalesLogix database includes the structure, or schema, for Sage SalesLogix.

Sage SalesLogix Server and Sage SalesLogix OLE DB Provider

The Sage SalesLogix Server handles synchronization logging, manages user connections to the database, and enforces licensing. The Sage SalesLogix Server can be installed on the

Sage SalesLogix Database Server, Synchronization Server, or a separate server.

The Sage SalesLogix OLE DB Provider is a client-side component that communicates with the

Sage SalesLogix Server to gain database access information. The Sage SalesLogix OLE DB

Provider is installed with Sage SalesLogix client applications.

Note

The Sage SalesLogix Client OLE DB Provider standalone installation is available on the Sage SalesLogix DVD for users who have third-party applications that need access to the Sage SalesLogix Server, but do not want a Sage SalesLogix Client installed on that machine.

Sage SalesLogix Logging Folders

Each Sage SalesLogix installation requires shared logging folders. A similar set of shared folders must exist if your installation includes a Remote Office.

Before you install Sage SalesLogix you must create and share the Sage SalesLogix logging folders. (If you are using the Express installation, the logging folders are created for you. For more information about available installation types, see

“Sage SalesLogix Installations”

in this chapter.)

When planning your Sage SalesLogix implementation, ensure you have access to create and share folders on the Administrative Workstation, Sync Server, and, if applicable, your documentation server. The Sage SalesLogix Implementation Guide describes the folders and permissions required for the logging folders in detail.

Sage SalesLogix Administrative Components

Administrative components are required for other Sage SalesLogix components to function.

They enable you to interact with your database, enter the licenses required to activate other components, deploy Web portals, customize your environment, and more. By default, most administrative components are installed on the Administrative Workstation with the

Administrative Tools and Servers installation. You can also install these components on other computers for customization purposes.

10 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Administrator

The Administrator enables you to do the following:

• Add licenses

• Add and maintain users

• Create and edit security profiles

• Install bundles for Network components

• Create Remote databases (if required)

Architect

The Architect provides a development environment for creating customized forms, menus, toolbars, and scripts for Sage SalesLogix Network components. These customizations are packaged together for installation as a unit or bundle. This enables your company to save and store customizations, which is advantageous for upgrades. It also enables controlled release of customizations. Network bundles are saved to files with the extension .sxb and work with any supported database type. Bundles containing Network plugins are installed or uninstalled using the Bundle Manager in the Administrator.

Application Architect

The Application Architect is the configuration, customization, and deployment tool for the

Sage SalesLogix Web components. Application Architect contains the tools that allow developers to rapidly build, customize, manage, and deploy coded and codeless Web application solutions.

You can create Web pages, modify the content of individual Web pages, and perform many other customization tasks without having to write code. You can make more advanced

(coded) changes to Web applications with code that has been modularized and exposed through each individual form and Web page. All common code snippet elements use the same code snippet architecture for business rules, quick forms, and custom properties. Common code snippets support VB and C#.

Process Orchestration

Process Orchestration allows you to create and configure process workflows in Visual Studio

2008 and provide access to the workflow runtime. Processes can be created for any entity, and any entity can be associated to multiple processes.

The following process types are available:

Sequential - A sequential process has steps you complete. When you complete one step, you go on to the next, in order, until all the steps in the process have been completed.

Goal-driven - A goal-driven process contains a series of activities or tasks that must be completed before moving on to the next activity or task.

Processes must be created in Visual Studio using Microsoft Workflow. After creating in Visual

Studio, processes can be run in Sage SalesLogix.

SData

Sage Data (SData) provides a simple standard protocol for reading data from and writing data to Sage Business Applications, either on-premise (server or desktop based) or on the

Web. This is done by applying industry standards like HTTP (Hyper Text Transfer Protocol),

XML (EXtensible Markup Language), Atom/RSS (Really Simple Syndication) under the umbrella of a REST (REpresentational State Transfer) architecture.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

You can generate SData feeds, making information available to other applications. For example, you can expose an entity or a business rule to RESTful-based Web services, allowing you to integrate and enhance Sage SalesLogix data with data from outside the application.

.NET Extensions

The SalesLogix .NET Extensions Manager enables developers to distribute, license, release, and deploy customizations written in Microsoft .NET Framework. This utility provides an option for developers who prefer to build customizations in .NET rather than directly in the

Architect.

Sage SalesLogix Utilities

Sage SalesLogix provides utility applications to aid in database customization and maintenance. They are installed as part of the Administrative Tools and Servers installation.

The following information details the function of each utility and how it can be used in your installation.

Group Copy Group Copy enables you to copy account information based on available account groups from one database to another, even if the databases are of different types

(such as copying Oracle to Microsoft SQL). In Group Copy, transactions are logged for synchronization.

Import Wizard The Import Wizard is a utility used for importing data into Sage SalesLogix from other software applications, such as ACT! by Sage.

Integrity Checker Integrity Checker enables you to locate errors and correct records in your database. Integrity Checker uses the concept of test libraries where each library is a file that has one or more tests. You can add, edit and delete tests, add new test libraries, or merge test libraries. You can load more than one test library at a time or save tests to a different name.

Monitor Console The Monitor Console receives and displays information from the

Synchronization (Sync) Service. You can install the Monitor Console in any location, on any computer that can connect to the computer on which the Sync Service is installed (the Sync

Service is explained on page 14

). This enables remote monitoring of the status of processes and jobs running on the Sync Server.

Resynchronize Remote Database Resynchronize Remote Database recovers data from a

Remote Client or Remote Office database that has not synchronized with the Host for an extended period or that is unable to synchronize due to other problems.

SalesLogix Profiler The SalesLogix Profiler provides a database independent profiling application to trace SQL and performance counters throughout the execution path of the

SalesLogix Provider. You can profile any Sage SalesLogix application(s) on your computer running the Sage SalesLogix OLE DB Provider (such as the Network Client or Web Client).

TrnAnalyzer TrnAnalyzer compiles statistics of Transaction Exchange File (TEF) contents.

TEFs are used by the synchronization process (synchronization is discussed in Chapter 7,

“Synchronizing in Sage SalesLogix” ). The statistics are presented as a list of the tables affected

by changes with the corresponding number of each type of change. You cannot edit the contents of a TEF. TrnAnalyzer displays what was logged and the number of instances, so it is useful for verifying that logging options are correctly set.

TrnViewer TrnViewer displays the contents of a TEF or server log used during synchronization. TrnViewer is view-only and does not enable you to edit the transaction.

12 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Update Date The Update Date utility is available in the Sage SalesLogix Client for use during presentations on a demonstration database. This utility allows you to move the data currently in the Evaluation database to a date you specify. You must log on to the Sage SalesLogix

Client as admin to access the utility (Contact Detail view > More Tabs > Personal > Update

Dates).

SpeedSearch

SpeedSearch enables users to locate information in Sage SalesLogix records such as defects and tickets, and in other documents on your network. If your company uses the Sage

SalesLogix Web components, your customers can search for information that is publicly available.

Web SpeedSearch

The Web search functionality makes information in SpeedSearch indexes available to your customers over the Web. Through the Administrator, your system administrator controls the type of information that is available to your customers. This can include information from defects, tickets, procedures, standard problems, standard resolutions, and other indexes.

SpeedSearch Service

The SpeedSearch Service builds indexes for SpeedSearch from records you specify. The

SpeedSearch Service can run on Remote users’ computers and at the Remote Office according to the build schedule set up at the main office. However, a Remote user can override that schedule and set his or her own. For example, if a schedule is set to build a certain index at 3 a.m. at the main office, it will run at 3 a.m. local time on the Remote users’ computers (provided computers are powered on and users have not set their own schedule).

If a schedule is not set and a remote computer is powered off when the main office builds the indexes, the indexes will be built when a user starts his or her computer.

A SpeedSearch Service can build indexes for only one Sage SalesLogix Server, so if your company has multiple servers, you will need multiple SpeedSearch Services. In situations where there are multiple databases on a server, you may choose to distribute responsibility for the databases among multiple SpeedSearch Services. Since only one database can be assigned to one SpeedSearch Service, you must specify the database for each SpeedSearch

Service using a configuration utility. The Sage SalesLogix Implementation Guide explains this process.

Sage SalesLogix Server Components

Sage SalesLogix server components manage and monitor the synchronization process and allow you to run Sage SalesLogix on the Web.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Synchronization Server

The Synchronization (Sync) Server is the application that runs the synchronization process and agents between the main Sage SalesLogix database and Remotes. Agents are a way to schedule reports, run scripts, and so forth. A Sync Server is only required if your installation needs to support Remote users and/or off-site locations. Regardless of the type of Remote

Office database and Remote client your installation supports, you will require a Sync Server.

Figure 2 Remote Components in a Sage SalesLogix Installation, and how they synchronize to the main database.

Synchronization Service

The Synchronization (Sync) Service is a Windows service that communicates with the Sync

Server(s) and the Administrator for scheduling purposes. It monitors synchronization by requesting information from the Sync Server and sending that information to the Monitor

Console.

Web Host

The Web Host contains the functionality of the Web components and provides the interface between Sage SalesLogix and Microsoft Internet Information Server™ (IIS). Your implementation may require one or more Web Hosts and virtual servers. Virtual servers enable you to scale your implementation without additional physical machines. The number of Web Hosts and virtual servers required for your company’s implementation depends on factors such as the number of active users, database size, and Web Host hardware.

Companies installing the Web components must evaluate their individual requirements for the implementation. The only reliable method of doing this is to prototype your installation.

Web Reporting

Web Reporting components require IIS and are integrated with Crystal Reports from Business

Objects (for more information about Crystal Reports from Business Objects, see

page 22 ).

Crystal Embedded Server is automatically installed with Web Reporting. Crystal Embedded

Server is a Web-based platform for reporting, analysis, and information delivery. Web Client users can access, run, and filter the same reports as Sage SalesLogix Network Client users.

The reports are managed through Architect and stored in your database. In addition, plugin security and data security are enforced.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Sage SalesLogix Personal Web Server

The Sage SalesLogix Personal Web Server is installed with disconnected Web Remote Clients for use as personal Web Sever. In a Web Remote Office installation, the Sage SalesLogix

Personal Web Server can be used as an alternative to IIS. However, the Sage SalesLogix

Personal Web Server is not scalable for more than five users. Therefore, it is not recommended in a large Web Remote Office environment.

The Sage SalesLogix Personal Web Server hosts the Sage SalesLogix portals on the Remote computer. The Sage SalesLogix Personal Web Server can run multiple portals. However, each portal instance must have a unique port on which it listens.

Sage SalesLogix Client Components

One or more client components are required for your Sage SalesLogix implementation. Client components are installed on your user’s computers.

Sage SalesLogix Client

The Sage SalesLogix Client enables users to connect to the Sage SalesLogix database to access and manage accounts, contacts, leads, opportunities, and activities.

Customer Service and Support Features

The Customer Service and Support features allow Sage SalesLogix Client users to effectively record, track, qualify, and resolve customer questions and issues. Customer service users can create tickets to track customer issues. Support features allow you to access and manage tickets, defects, products, procedures, and returns.

Sage SalesLogix Marketing

The features in Sage SalesLogix Marketing enable marketing departments to:

• Implement and track marketing campaigns.

• Track campaign responses that lead to new contacts and opportunities.

• Track opportunity results.

Marketing contains the following key features:

Leads Through Marketing, basic information about each lead is captured in order to qualify the prospective customer. Users can also import a list of Leads from a tab- or commadelimited file, matching the basic lead information (name, e-mail, phone, address, etc.) from the list to the lead record.

Qualification Marketing users can qualify a lead that is imported into Sage SalesLogix and convert it to a contact and account, and optionally create an opportunity. If a lead cannot be qualified, users can delete it from the system.

Campaign Management The Marketing campaign functionality allows users to track target leads and customers, and the stages in a campaign. It also helps users to capture budget and expense information related to the campaign. The campaign and lead source can be tracked for each lead, contact, account, and opportunity.

E-Mail Marketing Marketing offers integration with an e-mail based marketing tool. Users can select a list or group of leads, opportunities, or customers and generate formatted e-mail that is sent to all on the list. Users can track responses to the e-mail as well as remove targets from the list on request.

Segmentation and Groups Customers can be segmented using simple filtering tools to define groups or lists meeting specific criteria. Data can be exported to Excel for further analysis or to deliver mailing lists to external parties.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Campaign Reporting Marketing users can analyze the impact and cost of a marketing campaign and the resulting cost per lead through various reports.

Sales Processes

Sales Processes help manage the sales pipeline. A sales process shows the steps users should complete as they work to make sales. The sales process can be set up to prompt users to perform activities, such as making phone calls and writing letters. Typically, a sales manager or administrator develops sales processes, which are then defined and released through the

Architect. Users can then attach those processes to opportunities and manually drive the process from one step to the next.

Dashboards

Dashboards allow you to display and interact with a variety of performance and analysis information in a dashboard format. You can use the data to gain insight into organizational and individual performance—and to discover root causes for performance issues—allowing you to take corrective actions or make strategic decisions. You can also interact directly with other functions in the Sage SalesLogix Client, such as completing activities and navigating to opportunity views.

Mail Client

The Mail Client enables Sage SalesLogix to access selected e-mail systems and insert an email message into a contact’s history, integrate with a personal address book, and create custom folders. A compatible e-mail system must be installed on the user’s computer to successfully send and receive e-mail, add attachments, and perform other functions common to electronic mail systems. The Mail Client is installed with the Sage SalesLogix Client.

Refer to the Compatibility Checklist on SupportOnline/Sage Software Online Support and

Services Web site (http://support.saleslogix.com) for a list of currently supported versions.

Sage SalesLogix Remote Client

The Sage SalesLogix Remote Client is a stand-alone installation of the Sage SalesLogix

Client. The Remote user has a subset of the main office database in a local database on their computer, often a laptop. Synchronization is used to transfer changes between the Sage

SalesLogix Remote Client user’s database and the main office database. Note that Remote users never connect to a Remote Office, they only synchronize with the main office.

If you have less than five Sage SalesLogix Remote Client users, and it is not important that they share or have immediate access to the same accounts, then each user can be set up as a Remote user. A sales person traveling or a lone regional representative at an off-site location are both examples of Remote users.

Note

Sage SalesLogix Remote Client users can connect directly to the main office database if they have a network connection or a WAN connection with sufficient bandwidth.

Web Client Interfaces

The Web Client interfaces to Sage SalesLogix are:

• Web Client

• Disconnected Web Client

• WebViewer

• Web Customer Portal

• LeadCapture

16 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Web Client

The Web Client offers users access to the familiar Sage SalesLogix interface via the Web. In addition to tracking contacts, accounts, leads, opportunities, tickets and activities, users have access to tools for reporting, automating processes, and creating e-mails, faxes, and letters using mail merge.

Disconnected Web Client

The disconnected Web Client functions like the Sage SalesLogix Remote Client except that users connect to their local database using the Web Client. Synchronization is used to transfer changes between the disconnected Web Client user’s database and the main office database.

Note

Disconnected Web Clients require their own Web Server (IIS or Sage SalesLogix

Personal Web Server).

WebViewer

WebViewer is a subset of the Web Client that is enabled with a license. WebViewer users have read-only access to accounts, contacts, opportunities, and tickets. Depending on account and calendar security, WebViewer users can add, edit, and delete activities, notes, and history, but cannot use reporting or processes.

Web Customer Portal

Web Customer Portal enables you to provide customers with user names and passwords so that they can view existing tickets and create new tickets, as well as search for solutions to problems.

Lead Capture

Lead Capture provides the ability to collect information from prospects who access your company’s Web site to inquire about your products or services. This information is used to automatically create new accounts and contacts in your Sage SalesLogix database.

SpeedSearch Client

SpeedSearch Client is a search engine that is installed on each Sage SalesLogix user’s computer. It enables queries to be submitted against the data and documents in defined indexes.

Synchronization Client

The Synchronization (Sync) Client enables the transfer of database changes between a

Remote user or Remote Office and the database at the main office. The Sync Client is installed on the Remote user and/or Remote Office computer. In a Remote Office installation with a high level of synchronization traffic, install the Sync Client on a dedicated machine.

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.

Using Sage SalesLogix Mobile you can view or add accounts and contacts, schedule and complete activities, take notes, and track opportunities and review support tickets on a mobile device.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Sage SalesLogix Mobile is add-on functionality that requires separate installation and pricing.

Contact your Sage SalesLogix representative for more information.

E-Mail Integration Components

E-mail integration components allow your Sage SalesLogix users to share information between Sage SalesLogix and Microsoft Outlook. You can use a server-side or client-side application when sharing data between Sage SalesLogix and supported e-mail applications.

Sage SalesLogix Exchange Link

Sage SalesLogix Exchange Link allows Sage SalesLogix to exchange data with Microsoft

Outlook using a server-side application for configuration. Data exchange with Microsoft

Outlook can also be configured using Intellisync for SalesLogix and Advanced Outlook

Integration in the Sage SalesLogix Client. However, Intellisync for SalesLogix must be configured on each user’s computer and can be labor intensive. Sage SalesLogix Exchange

Link allows the administrator to configure all data exchange links on one computer. Exchange

Link is not recommended for Remote users.

Note

Sage SalesLogix Exchange Link is not available in all areas. Contact your Business

Partner or Sage SalesLogix reseller for availability.

Intellisync for SalesLogix

Intellisync for SalesLogix enables users to share their Sage SalesLogix activities and contacts with Microsoft Outlook. Intellisync for SalesLogix facilitates sharing information with non-

Sage SalesLogix users and enables synchronization of data to a PDA from the groupware application.

Intellisync for SalesLogix is deployed as a Web portal and configured on each client computer.

Depending on your installation, one or more of the following Intellisync for SalesLogix portals are required:

• Main Office portal - All Sage SalesLogix Network and Web Client users at the main office connect to this portal.

• Remote Office portal - All users at the Remote Office connect to this portal.

• Remote user portals - All Remote users (including disconnected Web Clients) connect to their own Intellisync for SalesLogix portal located on the remote computer.

Scenario Where do you get the

Intellisync Portal?

Network

Only

Network user Included in the

Administrative Tools and

Servers installation

Remote user Included in the Remote user installation

Where do users get the Intellisync for

SalesLogix Client?

Check box in the Sales

Client installation

Where do users get the

Sage SalesLogix

Personal Web Server?

n/a - Intellisync for

SalesLogix portal uses IIS

Check box in the

Remote Client installation

Included in the Remote

Client install

18 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Scenario

Web

Remote

Office

Where do you get the

Intellisync Portal?

Web Client disconnected

Web Client

Use the portal at the Main

Office that is included with the Administrative Tools and Servers installation

Deploy to the Remote user in Application Architect and then synchronize to the user

Network users Included in the Remote

Office installation

Where do users get the Intellisync for

SalesLogix Client?

Download link provided to users by the system administrator

Included in the disconnected Web

Client installation

Check box in the Sales

Client installation

Where do users get the

Sage SalesLogix

Personal Web Server?

n/a - Intellisync for

SalesLogix portal uses IIS

Included in the disconnected Web Client installation

Included in the Remote

Office install (to be used if

IIS is not available)

Web users Included in the Remote

Office installation

Download link provided to users by the system administrator n/a - Intellisync for

SalesLogix portal uses

IIS

Direction of Data Transfer

Each Intellisync for SalesLogix user must set configuration options and determine the direction of data transfer between the groupware application and the Sage SalesLogix database. Since this configuration process can be complicated, the system administrator or implementation manager should plan on providing initial implementation assistance for each

Intellisync installation.

The data direction options are:

• Two way sync compares data in the Sage SalesLogix database to the data in Outlook and updates both sets of data as needed. This option is selected by default.

• One way sync to Intellisync for SalesLogix pulls data from Outlook into the Sage

SalesLogix database. This option updates only the Sage SalesLogix database; the data in

Outlook is not affected.

• One way sync from Intellisync for SalesLogix sends data from the Sage SalesLogix database to Outlook. This option updates only the data in Outlook; the Sage SalesLogix database is not affected.

Sage SalesLogix Activities, Contacts, and Events

When you delete a contact, activity, or event from Outlook, Intellisync for SalesLogix does not directly delete those items from the Sage SalesLogix database; instead, a flag marks them as deleted by Intellisync for SalesLogix. Sage SalesLogix Administrators have the option of viewing and deleting the flagged records.

Note

You should include this as an administrative role in your company’s Implementation

Plan. Administrative roles are discussed on

page 39 .

Conflict Resolution

Each user can control how conflicts between Sage SalesLogix and Outlook are resolved by either marking a particular application as the source for automatic conflict resolution or by choosing to be notified when a conflict occurs. Notification allows users to compare the fields in question, and then make their own decisions regarding the data. Your system administrator should create business rules for shared contacts.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Customization

Each user can customize Intellisync for SalesLogix to work the way he or she does. A user can specify the Outlook data and corresponding Sage SalesLogix data to use. Or a user might customize the data transfer by specifying or modifying individual field maps between the other application and Sage SalesLogix. Intellisync for SalesLogix contains typing rules that block invalid mapping combinations. Furthermore, users can specify the date range to include timed items or turn off synchronization for completed to-do items. The Administrator Help provides information about field mapping. This is an area where your system administrator or implementation manager must provide guidance to individual users.

Intellisync for SalesLogix Requirements

To use Intellisync for SalesLogix and share data between two applications, you must:

• Be a licensed user of both Sage SalesLogix and the groupware application.

• Create an ad hoc group in Sage SalesLogix to identify the contact records that will synchronize with the groupware application.

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

Intellisync for SalesLogix Web portal.

Remote Office Components

Remote Office components support Sage SalesLogix users at a location other than the main office. These components enable satellite offices and employees to access the Sage

SalesLogix database at your main office, share (synchronize) data, and reconcile changes made.

Remote Office

A Remote Office is an installation of Sage SalesLogix at a location other than the main office

(an off-site location). The Remote Office consists of a Database Server, Synchronization

(Sync) Client, and Sage SalesLogix Client computers. Remote Office users are network users that work on the central Remote Office database and do not individually synchronize with the main office database. Only the Remote Office database regularly synchronizes with the main office database. (Remote users not connected to the Remote Office synchronize directly with the main office. See

Chapter 7, “Synchronizing in Sage SalesLogix” for more information.)

Set up the Remote Office if an off-site location meets the following criteria:

• There are more than five Sage SalesLogix Client users located at the same off-site location.

• All users are working on (sharing) the same accounts.

• All users need to see each other’s changes immediately.

Web Remote Office

A Remote Office can be deployed as a Web application that supports one or more Web

Clients. The Web Remote Office contains all components of a Remote Office with the addition of a Web Server (IIS or Sage SalesLogix Personal Web Server). Web Remote Office users are

Network users that connect to the Web Remote Office database via the Web Client. Only the

Web Remote Office database regularly synchronizes directly with the main office.

Web Remote Offices are created in the Administrator and managed in the Application

Architect similar to Web portals or applications.

20 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Additional Software

The products outlined in this section are compatible with Sage SalesLogix. Some of these products are required for Sage SalesLogix functionality, some must be purchased from a third-party vendor, and some ship with Sage SalesLogix at no additional cost.

For supported versions, refer to the Compatibility Checklist on the SupportOnline/Sage

Software Online Support and Services Web site.

Note

Additional third-party products may be used. For more information, see the Sage

SalesLogix Add-ons and Solutions Web site at http://techpartners.saleslogix.com.

Windows Operating System

Sage SalesLogix requires Microsoft Windows as your operating system for both Server and

Client computers. You must install Sage SalesLogix on a compatible version of Microsoft

Windows.

MDAC/Microsoft DAC

Sage SalesLogix uses Microsoft Data Access Components (MDAC or Microsoft DAC) to access data. MDAC (Microsoft versions earlier than Vista) is required for and distributed with Sage

SalesLogix, and must be installed before installing any Sage SalesLogix components.

Microsoft DAC (Windows Vista) is distributed with Windows Vista. The Sage SalesLogix installation prompts you to install MDAC if it is not detected on the computer where you are installing Sage SalesLogix.

Microsoft® Windows .NET Framework

.NET Framework version is a component of the Microsoft Windows® operating system used to build and run Windows-based applications. .NET Framework is required for .NET Extensions on the Administrative Workstation, Architect, Application Architect, Web Host, and Sage

SalesLogix Client computers.

Microsoft Windows Installer is required for use with .NET Framework. Sage SalesLogix automatically installs this if it is not detected on the computer where you are installing Sage

SalesLogix.

Web Browser

A compatible Web browser is required to access the Sage SalesLogix Web Client and Mail

Merge functionality in the Sage SalesLogix Client.

Adobe Acrobat Reader

Adobe Acrobat Reader enables you to read the Sage SalesLogix documentation distributed in

PDF format. Adobe Acrobat Reader is available from the Adobe Web site.

Microsoft Office

Sage SalesLogix is qualified for various Microsoft Office versions. Refer to the Compatibility

Checklist for details.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

Microsoft Word

The Sage SalesLogix Client uses Microsoft Word for word processing functionality. You will need Word if you intend to use word processing tools such as creating templates, writing letters to individuals or groups, attaching documents to an individual’s record, and creating history items to track the documents. Sage SalesLogix provides a basic letter, memo, and fax template, or you can add your own templates.

For mail merge template management, you must install Word on each Sage SalesLogix Client computer and on the computer on which you install Architect (usually the Administrative

Workstation).

Microsoft Excel

You can export groups from the Sage SalesLogix Client and the Web Client to an Excel spreadsheet.

Microsoft Outlook

Sage SalesLogix integrates with Microsoft Outlook and allows users to 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, and use the Sage SalesLogix Address Book in Outlook.

You can also enable Advanced Outlook Integration, which offers additional features such as the ability to flag Outlook e-mail received from Sage SalesLogix contacts.

Note

If you choose to enable Advanced Outlook Integration, your users must not select

Microsoft Word as their e-mail editor.

Crystal Reports Reporting Software

Crystal Reports is a third-party software reporting tool by Business Objects. It is used for creating custom reports. A Sage SalesLogix administrator usually creates new reports; however, any Sage SalesLogix user can create new reports if a supported version of the

Crystal Reports software is installed.

Use the Architect to save reports as plugins, and then release them to specific users or groups. You can integrate reports directly into dashboards and analytical summaries.

The typical Sage SalesLogix Client installation includes Crystal Reports Runtime files, which enable Network and Remote users to view and print Sage SalesLogix reports without needing a full Crystal Reports installation. Crystal Reports is also available over the Web, and addresses all steps in the reporting process; from data access to report design, management and delivery, and report integration with portals and applications.

Sage SalesLogix also provides an API for collecting a dynamic list of all open reports.

Fax Capability

Fax is available through the Microsoft Fax Service. A free Fax package ships with various

Windows versions and interfaces with the Sage SalesLogix Fax Provider. Sage SalesLogix also provides an API for integrating other fax providers.

Sage SalesLogix Installations

Sage SalesLogix provides two installation options, Express and Standard. This section explains the differences between the two installation types and provides information to help you determine which is the best option for your company.

22 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

If you are installing Sage SalesLogix on a Windows operating system, a domain user with specific permissions is required to install and run Sage SalesLogix. This user, referred to as the SLXService user, must be manually created if you install Sage SalesLogix using the

Standard installation. The Express installation automatically uses the Local System Account

as the SLXService user. For more information on this user type, see “Sage SalesLogix Security and the Windows Operating System” on page 39

Express Installation

The Express installation is intended for a Sage SalesLogix configuration of 5 to 25 users on a

Microsoft SQL Server database. If your implementation includes more than 25 users, the

Web, Remote Offices, Intellisync for SalesLogix, or an Oracle database, you should not use the Express installation.

The Express installation installs the following components on a single computer using system assigned default settings:

• Sage SalesLogix Server

• Sage SalesLogix Evaluation Database

• Sage SalesLogix Blank Database

• Administrative Workstation (Administrator, Architect, Application Architect)

• Sync Server

• SpeedSearch

• Marketing Services (EmPulse)

• Sage SalesLogix Utilities

• Sage SalesLogix Logging folders

When you have completed the Express installation, you can install Sage SalesLogix Clients.

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, include

Intellisync for SalesLogix, or include a Remote Office(s). The Standard installation allows you to select the components you want to install, and the location for each component.

When you have completed the Standard installation, you can install Sage SalesLogix Clients.

Web Installations

Sage SalesLogix Web components bring together the accessibility of the World Wide Web and the power of Sage SalesLogix. This combination gives your sales team, employees, channel partners, and suppliers a customer relationship management solution via the Web.

Web implementations require the following:

• The core Sage SalesLogix components

• Sync Server (if your company has Remote Office or Remote users)

• A minimum of two Web servers: one to serve as the Web Host and one for Web Reporting

Note

For a complete list of considerations for adding Web Components to your installation, see the Sage SalesLogix Implementation Guide.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

The following diagram describes three typical implementation scenarios.

Remote Installations

An installation that includes remote components requires all of the considerations of a network installation, as well as the following:

Synchronization Server Requirements

• Sync Server license

• Sync Server hardware

• Remote user or Remote Office

• Named User license

• User training and user support

• Additional software licenses, such as Microsoft Outlook, Exchange, or Office

Remote Office Requirements

• Remote Office Server license

• Named User or Named Web User licenses for each installation of the Sage SalesLogix

Client or Web Client

• Sage SalesLogix Client hardware

• Remote Office Synchronization Client hardware

• Remote Office database hardware

• RDBMS license

• Additional software licenses, such as Microsoft Outlook, Exchange, or Office

Automated Client Installations

To reduce the time required to install Sage SalesLogix, you can create Sage SalesLogix

Network Client and Sage SalesLogix Remote Client automated installations. Automated installations install the Sage SalesLogix Client with the configuration settings selected when the installation was built.

There are several advantages to using automated installations. You can:

24 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

• Enforce the use of specific settings for all users.

• Specify different configurations for different users.

• Install Sage SalesLogix with minimal user input.

Automated installations also reduce administration time when you upgrade to a new version, and then add new users to Sage SalesLogix. During the upgrade process, you can update the automated client installation images directly from the upgrade wizard. Then, when you add new users and install Sage SalesLogix, the Client installation includes all service packs and upgrades that are installed on your system.

Automated installations require a shared network folder in which you create the installations and from which they are accessed by your users. Users can install Sage SalesLogix by accessing the folder directly or by using a shortcut received through e-mail.

Remote Client installations require that you copy the entire automated installation folder structure and files to the remote computer.

Customizing Automated Installations

Automated installations create executable files that users can run to install Sage SalesLogix on their own machines. You can run the standard configuration file or customize it for your specific environment. The Sage SalesLogix Implementation Guide provides configuration settings you can use to customize the standard Sage SalesLogix configuration file.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Components

26 Sage SalesLogix Planning Guide v7.5

Chapter 3 Understanding Sage SalesLogix Licenses

Licenses control access to Sage SalesLogix features. They also determine the number and type of users that can access Sage SalesLogix. You must add licenses before the Sage

SalesLogix components are available for use and before adding users (Network, Remote,

Concurrent, etc.). For information about purchasing Sage SalesLogix products and licenses, see your Sage SalesLogix representative or Business Partner.

This chapter lists the available licenses and explains the functionality they enable in Sage

SalesLogix.

Sage SalesLogix Licenses

There are three Sage SalesLogix licenses that control specific features and functionality.

Licenses provide access to the Administrator, Architect, and Application Architect. The first time you log on to the Administrator, you must install one of the following licenses.

License Name Available Functionality

Standard • Account and Contact Management

• Sales Opportunities

• Marketing Campaign Management

• Customer Service

• The ability to apply bundles containing any plugin type

• Architect: You can open and edit an existing form, and save your changes under a new version number.

Restrictions / Exceptions

In Administrator:

• No access to

Administrative Roles.

• No access to Feature and

Team security, so users share all information.

• No access to agents.

In Architect:

• You can edit existing customizations, and save your changes, but you cannot create new customizations.

• You can edit existing

Contact Processes, but cannot create new.

• You cannot edit any other plugins including standalone scripts or main views.

• You cannot copy or paste in the Plugin Manager.

• You cannot access the

Stored Procedures manager or the Secured

Functions manager.

In Application Architect:

• No restrictions.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Licenses

License Name Available Functionality

Advanced Provides all functionality in the Standard license plus the following:

• Web functionality (including Web

Customer Portal).

• Sales Opportunity Statistics.

• Update Multiple Sales Opportunities.

• Sales Processes.

• Full Administrator capabilities including:

• User security.

• Field-level security.

• Administrative Roles.

• User teams.

• Agents.

Premier Provides all functionality in the Standard and Advanced licenses plus full Architect capabilities.

Restrictions / Exceptions

In Architect:

• You can edit existing customizations, and save your changes, but you cannot create new customizations.

• You can edit existing

Contact Processes, but you cannot create new.

• You cannot edit any other plugins including standalone scripts or main views.

• You cannot copy or paste in the Plugin Manager.

• You cannot access the

Stored Procedures manager or the Secured

Functions manager.

None

SpeedSearch License

All Sage SalesLogix users and systems receive standard SpeedSearch features:

• Ability to view the standard indexes. Standard indexes are detailed in the “Standard

SpeedSearch Indexes” topic in the Administrator Help.

• Ability to set up schedules to rebuild each standard index at certain times or intervals.

The SpeedSearch Advanced license allows Sage SalesLogix users to have additional functionality.

License Name

Advanced

Available Functionality

Allows the system administrator to add new (custom) indexes and edit the standard indexes. Custom indexes can search anywhere inside the Sage

SalesLogix system or within file directories on your network. The

SpeedSearch Advanced license limits the number of users who can access

SpeedSearch to the number specified in the license. You can purchase licenses in quantities to meet the needs of your company.

Restrictions / Exceptions

Custom FileSystem indexes are not available to Remote users.

28 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Licenses

Server Licenses

Server licenses apply to Sage SalesLogix software installed on one or more servers.

License Name Available Functionality

Customer Portal Enables a set number of users to access the Customer Portal features using the

Internet. The license is available for any number of users that your company requires. This license is required in addition to the Web Server license and the External Access License.

External Access

License

Required for each external application that accesses Sage SalesLogix data with the Sage SalesLogix OLE DB Provider and makes such data available to non-

Sage SalesLogix users. This license is not required for customizations built solely for use within a Sage SalesLogix

Client (including bundles and applications inside a Sage SalesLogix

Client) since only Sage SalesLogix users can access these customizations.

LeadCapture

Remote Office

Server

Activates the ability to collect information from a Web site and directly populate the database. A Web Server license is also required.

Allows one server to synchronize data between a satellite office and the main office database. When this license is installed, each user who has been assigned a Named User, Named Web

User, or WebViewer license can access the Sage SalesLogix database through the Remote Office Server.

Restrictions / Exceptions

Synchronization

Server

Permits one server to synchronize data between the Sage SalesLogix main office database and remote databases. When this license is installed, each user who has been assigned a Named User license can remotely access the Sage SalesLogix database through the Sync Server.

Oracle Host

Database

Required to install Sage SalesLogix on an

Oracle database.

This license should not be confused with any license(s) required from Oracle for the rights to use an Oracle database.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Licenses

License Name Available Functionality

Web Server Enables you to install and configure the

Web Host, which provides access to the

Sage SalesLogix database using the

Internet. This license is required for the

Application Architect, Web Client, Web

Client Customer Service, and Sage

SalesLogix for Web Phones, as well as the other Web components. All User licenses provide access to the Sage

SalesLogix database through the

Internet, but the number of users logged on at one time cannot exceed the number of licenses issued.

Restrictions / Exceptions

User Licenses

User licenses enable user access to Sage SalesLogix.

License Name Available Functionality Restrictions / Exceptions

Concurrent User Concurrent User licenses allow multiple

Sage SalesLogix users to share the same license. However, only the number of users for which you have licenses can log on at the same time. For example, if you have 40 users and a 30 Concurrent User license, all 40 users can log on to Sage

SalesLogix but only 30 can be logged on at the same time.

• Remote users cannot be

Concurrent users.

• Logging on to a Third Party product, like ADO Explorer, using the Sage SalesLogix

Provider and a Sage

SalesLogix Concurrent user name and password will consume a license.

Concurrent users can log on to the Web

Client, Sage SalesLogix Client,

Administrator, Architect, Application

Architect, Sync Client (Remote Office only), and a Remote Office. Every logon will consume one Concurrent User license. For example, if Samantha Brink logs on to the Web Client and Sage

SalesLogix Client and leaves them both open, it will consume two licenses.

Concurrent User licenses can be divided between the Host and any or all Remote

Offices. This assignment can be changed at any time. When you assign

Concurrent User licenses to a Remote

Office, the Host assumes all Remote

Office licenses are consumed at all times. For example, if you have a 30

Concurrent User license and you assign

10 licenses to one Remote Office, the

Host automatically subtracts the 10 licenses and only allows 20 Concurrent

Users to log on to applications at the main office.

30 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Licenses

License Name Available Functionality

Named Add-On

User

This license type, for use by third-party add-on products possessing a custom interface, enables creation of a Sage

SalesLogix user profile. It provides rights to use the Sage SalesLogix OLE DB

Provider, but does not permit logging on to any Sage SalesLogix Client.

Restrictions / Exceptions

Named User

(Network User or Remote User)

Named Web

User

WebViewer

(Restricted Use)

Each license enables a single named user to access any number of copies of any

Web, Remote, or Sage SalesLogix

Network Client software using a PC, laptop, Web phone, or browser. One license is assigned per user for each named user. For example, if you have

100 Named User licenses, only the 100 users whose names have been attached to a license can log on to Sage

SalesLogix.

Grants Internet access to the Sage

SalesLogix database via the Web Host server for a single, named user for each

Named Web User License granted.

Internet access may be by a browser or

Web phone. Named Web Users may not access any Remote or Network Client

Software.

Enables Internet access to the Sage

SalesLogix database via the Web Host server. Each WebViewer License permits access by one named user. Internet access may be by a browser or Web phone. Users are limited to read-only access to Sales information, although they can create and edit notes, history, and activities. Users do not have access to reports.

The Web Server License is required in conjunction with the

WebViewer license.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Licenses

32 Sage SalesLogix Planning Guide v7.5

Chapter 4 Understanding Sage SalesLogix Security

The two types of security in Sage SalesLogix are database security and account security. This chapter contains information about both.

Sage SalesLogix Database Security

Sage SalesLogix database security is controlled by the Sage SalesLogix OLE DB Provider. The provider can be explained as a layer between ADO and the OLE DB provider native to your database type (Oracle or Microsoft SQL Server). The Sage SalesLogix OLE DB Provider enforces field and record-level data security on all queries passed to the Sage SalesLogix database.

Figure 3 Sage SalesLogix Architecture

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Security

Figure 4 Sage SalesLogix Web Architecture

The Sage SalesLogix system architecture is made up of five physical tiers. These tiers can exist on the same machine, or on separate machines in a network. The tiers are:

Tier 1: Data Layer The data layer is the relational database layer. Sage SalesLogix supports

Microsoft SQL Server and Oracle.

Tier 2: Data Access Layer The basic data access layer is the native database OLE DB

Provider. The Sage SalesLogix OLE DB Provider extends the functionality of the native database OLE DB Provider by implementing extended interfaces that are not natively supported by the database.

Tier 3: Rules Layer The Sage SalesLogix Network and Web Clients handle business rules.

They also control all logic that deals with the flow of data. Data rules are handled by the Sage

SalesLogix OLE DB Provider, which spans the rules and data access layers.

Tier 4: Presentation Layer The presentation layer contains user interface views, basic scripts, reports, document templates, and all other customizable aspects of the Sage

SalesLogix Clients that are stored as objects in the database and retrieved as needed. The clients retrieve these objects from the database or from cache and display them in the user interface.

Tier 5: User Interface Layer The Sage SalesLogix Client and Sage SalesLogix Web Client serve as user interfaces.

34 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Security

Connection Pooling

The physical connection to your Sage SalesLogix database uses OLE DB Connection Pooling.

Each client query uses one connection from a pool of connections available for use on the

Sage SalesLogix Server, and then releases the connection when the query is complete. So a user might be logged on to Sage SalesLogix, but if he or she is not retrieving information from the database, a connection to the database is not being consumed.

More information about how OLE DB manages a shared pool of connections is available in the documentation on the Microsoft Developers Network.

Sage SalesLogix Security and Other Software Applications

The Sage SalesLogix OLE DB Provider uses standard Microsoft ADO and requires no proprietary API calls to access data. This means that Visual Basic, Active Server Pages (ASP),

Crystal Reports, or any other application that uses a standard OLE DB connection can access

Sage SalesLogix data as a client.

The SLX Provider must also be installed for third-party applications that use Sage SalesLogix

API (SLAPI) or the OLE DB Provider externally.

Third-Party Access Scenarios

The Sage SalesLogix OLE DB Provider controls access to Sage SalesLogix data from external applications by allowing the system administrator to use passwords to restrict access. The system administrator has three options for controlling third-party access to Sage SalesLogix.

No Access - Third-party applications cannot access Sage SalesLogix data.

Read-Only Access - Third-party applications can import Sage SalesLogix data but cannot make changes to the Sage SalesLogix database.

Read/Write Access - Third-party applications can import Sage SalesLogix data and make changes to the Sage SalesLogix database. The system administrator can specify passwords during installation or at any time afterwards using the Connection Manager. Users who log on to Sage

SalesLogix through a third-party application with a connection string containing the appropriate password are granted the correct access. (More information about connection strings is available in the

Sage SalesLogix LAN Developers Reference.)

Note

To prevent all access, the system administrator must set the Read/Write and Read-

Only passwords.

The following table describes how password settings influence third-party access:

Password Setting

No Read/Write or Read-Only

Access.*

Only the Read/Write password is set (Read-Only is blank).

Third-Party Access

Read/Write

If no default password is set, a user can access Sage

SalesLogix data through a third-party application, and the application can write to the Sage SalesLogix database.

Read/Write if the required password is passed in the connection string.

A user can access Sage SalesLogix data through a thirdparty application. The application can write to the Sage

SalesLogix database, however, only if the appropriate password is passed through the connection string.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Security

Password Setting Third-Party Access

Read/Write password is set to one password, and Read-Only is set to a different password.

Either Read/Write or Read-Only depending on which password is passed through the connection string.

Otherwise, no access.

Read/Write and Read-Only passwords are identical.

A user can access Sage SalesLogix data through a thirdparty application only if the appropriate password is passed through the connection string.

Read/Write (the most access "wins") if the required password is passed through a connection string.

Otherwise, no access.

*If no Read/Write password is set, the Read-Only password is not used (the Password box is unavailable in the Connection Name dialog box).

Sage SalesLogix Product Security

Sage SalesLogix enables your company to implement the level of product security that is appropriate to your needs. Using a combination of account ownership, security privileges, and team membership, security can range from none to stringent. This approach gives Sage

SalesLogix the adaptability and flexibility to meet the needs of a wide variety of companies.

Understanding Account Ownership

Security in Sage SalesLogix is based on account access. To understand how this works, it helps to understand the role of the account in Sage SalesLogix.

Accounts are the fundamental units of the Sage SalesLogix system. From the perspective of the Sage SalesLogix Client user, an account is any company that a salesperson is working with on a sale. Contacts are the individuals at the company, and potential sales are the opportunities. An account can have many contacts and opportunities associated with it.

These contacts may have activities and history items related to interactions with a salesperson. Users who do not have security access to the account are unable to access any account-related information, including the activities and history items.

From the perspective of the customer service or support user, an account is the company that has purchased or may purchase your company’s products. Contacts are the individuals at the company, and tickets are the reports received from contacts who are logged with your

Support Center. Information about defects and returns are also recorded by account. When users do not have access to a particular account, they cannot see any record associated with that account.

Account access is referred to in the system as Account Ownership. The three levels of

Account Ownership are:

• Individual User

• Team

• System

An individual user, a team of users, or everyone can own Public accounts.

During the planning stage, it is imperative that you consider your users and the access you will allow them to certain areas of your system. When you add customizations to your implementation, remember that Sage SalesLogix core tables will enforce Account-level rights and filter data accordingly.

36 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Security

Individual User

Each user added to Sage SalesLogix has a user profile. Settings in this profile determine the user’s ability to access accounts, edit account records, create new accounts, and assign account ownership. You can control access to data at the table or field level. A user can have one set of access rights as an individual owner of an account and another set as a member of a team who owns an account. For example, a user who owns an account as an individual has full access rights to all tables and fields, but might be limited to view-only rights as a member of a team.

Team

A team is a group of users who require access to the same set of accounts. You create teams in the Administrator. Teams define who owns an account and which users can access that account. When creating teams, consider what the team members have in common and what information they need to share.

A user automatically has access to accounts owned by any team to which they belong. For example, Lee Hogan belongs to the Midwest team and has access to all accounts owned by that team. However, Lee is not a member of the Northeast team, therefore does not have access to accounts owned by the Northeast team.

Department A department is a specialized team. All users must be assigned to a department. (By default, Sage SalesLogix assigns all new users to the “None” department.)

You can add a department to a team, and by doing so, everyone in the department has access to all of the accounts for that team. When a user is a member of both a team and a department assigned to the team, rights for the team prevail. A Department cannot own accounts.

System

There are two system teams:

Everyone This system team automatically includes all Sage SalesLogix users. When an account is owned by Everyone, any Sage SalesLogix user may view, edit, or delete account information or even delete the account itself. Consequently, using Everyone equals having no security. For this reason, Sage SalesLogix recommends creating specific teams, rather than using the Everyone system team.

Everyone - View Only This system team allows all users to view all of the accounts in the system, but withholds editing rights. This enables users to access accounts to answer customer questions, but still maintains a level of security by preventing those account records from being edited.

Understanding Security Profiles

Account security can be restricted at the individual and team level. The system administrator can implement more advanced security (field-level security) by specifying access rights to tables, fields, and application functions. You can restrict a user’s access to any item on a view in the Sage SalesLogix Client, since each of these items has a corresponding field in the database. This access may be set to read/write, read-only, or no access. This is done in the

Administrator. Users cannot modify their own security profiles.

Note

Security profiles do not apply to the Web.

Individual Security Profile A user’s individual security profile determines that user’s access to accounts, contacts, opportunities, and other records. Each user’s security profile for the

Sage SalesLogix Client is determined by the permissions the user is given in the

Administrator on the Security and Teams tabs in the user profile. When the account is owned by an individual, that individual always has read/write access.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Security

Team Security Profile Each user’s team security profile dictates the user’s access rights when an account is owned by a team. Each team can have multiple Team Owners. Additional team members have default rights as assigned on the Teams tab in their user profiles.

Team Owner Profile The Team Owner Profile is the only security profile that can change ownership. Any number of team members can be team owners.

The default security profile determines which profile will be assigned when the user is added to a team or to another user’s team. When a user is added to a team, you can choose to have his or her manager added to the team by default.

Separate security profiles can exist for a user as an individual and as a team member.

Consequently, a user may have one security profile for accounts owned by another individual and another for accounts owned by teams.

It is also possible for a user to have a separate security profile for each team to which he or she belongs. Consequently, a single user can have many security profiles, or as few as one.

Security profiles are generic and, once created, can be assigned to multiple users. You can evaluate your access requirements and build several generic security profiles for a large group of users rather than creating a custom security profile for each user.

For example, you may want one security profile for Sales Representatives that only allows them to view certain data. You may have another profile for Support Representatives that allows them to view all data, but only edit certain fields. Then, you could have an additional security profile for Sales Managers, Regional Managers, or Support Managers that allows read and write access to all data.

Your customer support department will not be able to access information for callers unless they are a member of the team that owns that account. For this reason, some companies choose to assign their support department to all teams, but give read-only privileges for certain views.

Calendar Security

Depending on their access rights, individuals can view or modify other users’ calendar activities or events. When setting calendar permissions, you should evaluate the structure of your company as well as the informational needs of your users.

By default, new Sage SalesLogix users do not have access to any other users’ calendars. To enable access to another user’s calendar, your system administrator must provide the permissions for that calendar. You will probably want to retain some limitations on who can view and edit calendars. For example, Lee Hogan may have calendar access to sales representatives in his region, however, he cannot view or edit the calendar activities of any other users.

All calendar activities and events are updated during synchronization based on the access granted to each individual or team. Allowing users to access other user’s calendars will increase the number of synchronization transactions.

Determining Security in the Web Products

Before you implement the Web components, you must understand the security differences between Sage SalesLogix Network and Web products. Security profiles for Sage SalesLogix

Web users are created in the Application Architect. Although account ownership determines what accounts users can view, you can use roles to restrict users from modules and Smart

Parts. For example, if a team using the Sage SalesLogix Network Client can view accounts but not edit them, that team can still edit those accounts from the Web Client unless the appropriate security role is created and assigned.

38 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Security

Identifying Administrative Roles

The Administrator is used to manage users and configure Sage SalesLogix applications (such as the Sage SalesLogix Client). Access to the Administrator is limited to the system administrator and to those users who have been assigned administrative roles.

You will need to decide whether to use administrative roles. If so, you will need to decide how many and who will be assigned to each role. Keep the number of administrative roles to a manageable level so that they are not difficult to maintain. In addition, keeping a record of users and their roles helps maintain the integrity of your database

System Administrator

The system administrator is the only user with full access to all features and functions in Sage

SalesLogix. The administrator’s access is activated when a Sage SalesLogix license is installed.

The Administrator user profile cannot be modified with the same access as other Sage

SalesLogix users (Network, Remote, and so on). See the Sage SalesLogix Implementation

Guide for details.

Administrative Users

Sage SalesLogix users can be assigned an administrative role, enabling them to perform tasks in the Administrator, normally reserved for the system administrator. These users can log on as themselves and do not have to log on as the administrator.

Note

Administrative Roles are not available under the Sage SalesLogix Standard license.

The default administrative roles are:

Sales Admin Users assigned this role can perform all functions except using the Database

Manager and modifying the Library.

DB Admin Users assigned this role can perform all functions except realigning territories, modifying sync transfer profiles, and modifying the Library.

Librarian Users assigned this role can only modify the Library.

You can also create any number of custom roles that meet the needs of your company. For example, you may grant one user the ability to only change user passwords.

Users assigned administrative roles require access to the Administrator in one of two ways.

Either the Administrator can be installed on the administrative user’s computer, or the administrative user can log on to the Administrator on the Administrative Workstation.

Administrative users are able to access only those features and functions for which an administrative role has been assigned.

The “Managing Administrative Roles” topic in the Administrator Help provides more information and instructions for creating Administrative Roles.

Sage SalesLogix Security and the Windows Operating System

Due to restrictions in security within the Windows operating system, the ability to perform certain functions is restricted to users who have been designated Administrative users in the

Windows operating system. These functions are:

• Installing and/or upgrading the Sage SalesLogix Client. This task includes opening the

Account, Contact, Opportunity, Defect, Return, Contract, and Ticket views, or Main views, in the Sage SalesLogix Client on each computer where it is installed. Failure to do this makes Main views inaccessible.

• Performing some configuration tasks.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Security

• Performing additional integration in the Sage SalesLogix Address book. (This only applies if using Outlook Integration.)

If you choose to implement higher security levels and set all Sage SalesLogix Client users as restricted users, then the system administrator will need to perform these tasks. If you leave all Sage SalesLogix users in the Windows Administrators group, they can perform these tasks for themselves.

Restricted users are able to use the Sage SalesLogix Client.

You will also require the following Windows domain users if you are installing the Sage

SalesLogix Client on a Windows operating system:

SLXService user This is a Windows logon name with security permissions that allow the

SalesLogix Provider and synchronization to access all necessary directories.

Note

In an Express installation, the local system account performs the function of the

SLXService user.

WebDLL user This user is required in companies where any of the Sage SalesLogix Web components and/or Intellisync for SalesLogix will be used.

The Sage SalesLogix Implementation Guide and Windows Help provide more information on how to create these users and why they are necessary.

Using Windows Authentication

With Windows Authentication, users are automatically logged on to Sage SalesLogix without entering their user names or passwords. Users’ Windows IDs are stored in the Sage

SalesLogix database paired with their Sage SalesLogix user names and passwords. It is possible to set up Windows Authentication for only certain users while others continue to log on manually. When a user opens Sage SalesLogix and their Windows Login ID does not match the one recorded in Sage SalesLogix, the user must log on manually.

If you import Windows users into the Sage SalesLogix user’s list, their Windows IDs are copied into Sage SalesLogix. During the import, you can choose whether to copy address book information to the user’s Sage SalesLogix profile.

40 Sage SalesLogix Planning Guide v7.5

Chapter 5 Selecting a Database Management System

The relational database management system (RDBMS) and the server hardware on which the database resides, significantly impacts performance of your Sage SalesLogix implementation.

The size and type of the database affects the server’s size and configuration, so before acquiring new hardware or allocating existing hardware for the database and server, read this chapter.

For supported RDBMS versions, refer to the Compatibility Checklist.

This chapter addresses:

• Database Considerations

• Supported Databases

• Database Hardware

Database Considerations

The appropriate database for your needs will depend on the size of your company, the Sage

SalesLogix products that you install, and the location (on- or off-site) of your users. In addition, the following key elements affect your choice of RDBMS.

• Number of accounts and contacts

• Number of active users

• Number of new tables and fields added for any customizations

You will need to consider these elements in relationship to the advantages and disadvantages of the available databases.

Number of Accounts and Contacts

Many tables in Sage SalesLogix depend on the presence of an account record. Generally, each account is associated with multiple contacts, each of which may have multiple history records.

Use the number of anticipated accounts and related contacts as a guideline when determining the optimal RDBMS. The greater the number of records, the greater the load on the RDBMS.

As the number of accounts and contacts increases, a more robust and scalable database is needed.

Number of Active Users

Active users are the number of users on the system at any one time. The larger the number of active users, the greater the load on the RDBMS and the Sage SalesLogix Server. As the number of concurrent users increases, a more robust and scalable RDBMS is needed.

Number of New Tables and Fields Added for Customizations

Adding new tables and fields to support customizations will impact the size of the database.

Consider the number of tables and fields added multiplied by the number of records that will be storing data in those tables and fields.

Sage SalesLogix Planning Guide v7.5

Selecting a Database Management System

Understanding Supported Databases

Sage SalesLogix supports the following databases:

• Microsoft SQL Server

• Microsoft SQL Express

• Oracle

Each database type has advantages and implementation considerations.

Your choice of database for Remote users and Remote Offices does not depend on the database selected for the main office. For example, you can use Oracle at your main office and Microsoft SQL Server or Microsoft SQL Express for your Remote Offices.

Microsoft SQL Server

Microsoft SQL Server is an excellent choice for a Sage SalesLogix database because it is scalable and powerful, yet relatively easy to learn and administer.

Advantages

• Optimized for the Windows environment

• Configuration tips are available

• Easy to back up and restore

• Scalable and robust

• Relatively easy to support

• Provides the capability to create SQL Express databases for distribution to your Remote

Offices and Remote users.

Implementation Considerations

• Schedule regular backups of the log device to prevent it from filling the space allocated.

• SQL Server 2005 requires .NET Framework 2.x, which will be installed during the SQL

Server 2005 installation.

• The Microsoft SQL Native Client must be installed on every computer that will connect to a Sage SalesLogix database installed on a Microsoft SQL Server 2005 instance.

Microsoft SQL Express

Microsoft SQL Express uses the same database engine as Microsoft SQL Server 2005. It is designed to provide a database platform that offers superior ease of use, enabling fast deployments for its target scenarios. Multiple Microsoft SQL Server 2005 Express installations can coexist on the same machine along with other installations of Microsoft SQL Server or

Microsoft Desktop Engine (MSDE).

Advantages

• Optimized for the Windows environment

• Capable of exchanging data with Microsoft SQL and Oracle

Implementation Considerations

• 4-gigabyte database size limit

• Supports one processor

42 Sage SalesLogix Planning Guide v7.5

Selecting a Database Management System

Oracle

Oracle is an extremely capable RDBMS. However, to achieve satisfactory performance, the hardware requirements are stringent. When Oracle is installed, the number of CPU processors, amount of RAM, and size of disk drives increase significantly.

Advantages

• Extremely configurable

• Handles large databases and a large number of concurrent users and tables when installed on a UNIX platform

• Extremely scalable on a UNIX platform

Implementation Considerations

• Requires extensive experience to achieve competency in administration and tuning.

• Tables must be sized correctly before the data is loaded. Otherwise, additional table extents or data files may be required.

• Extremely sensitive to disk contention due to its use of multiple processes. As a result, several physical disk drives are often necessary. Consequently, the files that are spread across these drives must be evaluated before any data is loaded.

• Separate data, index, and temporary tablespaces are recommended.

• To support synchronization, you must install Microsoft SQL Express on the Administrative

Workstation in order to create remote databases.

• Each user machine that will connect directly to the Oracle database must have the Oracle

Client and Oracle OLE DB components installed. This includes the Sync Server and the

Administrative Workstation, but not machines that use synchronization to connect to the

Oracle database.

• The major version of the Oracle Client must match the major version of the Oracle

Database. For example, if the database is Oracle 10.2.0.6, then the Oracle Client must also be 10.2.0.6.

• The major version of Oracle should match the major version of the Oracle OLE DB components. For example, if you are using Oracle 10.2.0.6, then the Oracle OLE DB components should be 10.2.0.6.

Understanding Database Backups

It is important to have a reliable, well-tested strategy for backing up your current database before rolling out Sage SalesLogix. Frequent and timely backups are the best way to prevent loss of data and to recover from catastrophic failure.

Back up the Sage SalesLogix database on a regular basis. Depending on your database, backups can be performed while the database is in use or during off-peak, low-volume times.

Nightly backups are recommended. Refer to your specific database documentation for the various backup methods available.

Always perform backups through your selected database (Microsoft SQL Server or Oracle) rather than through the server or workstation operating system. Since the operating system will not back up a database while it is running, the database must be stopped. Backups through the database, however, are more sophisticated than backups through the operating system and can be performed at the same time as other maintenance functions. Also, point- in-time recovery is much easier from a database backup than from an operating system backup.

Sage SalesLogix Planning Guide v7.5

Selecting a Database Management System

Running Other Applications on the Sage SalesLogix Database

Server

Sage SalesLogix does not recommend running applications other than the RDBMS and the

Sage SalesLogix Server on the Sage SalesLogix database server, except in an Express implementation.

44 Sage SalesLogix Planning Guide v7.5

Chapter 6 Understanding Sage SalesLogix Hardware

This chapter provides information that affects the hardware configuration for Sage SalesLogix components. You can use this information along with the minimum and recommended hardware configurations detailed in the Compatibility Checklist to help you understand your needs before acquiring hardware.

Administrative Workstation

The Administrative Workstation is usually either the system administrator’s personal computer or a separate computer dedicated to Sage SalesLogix administration. The

Administrative Workstation hardware configuration may vary based on the following elements:

• Number of accounts in the main database

• Number of other applications running on the Administrative Workstation

• Whether the Administrative Workstation is used for importing data

• Whether the Administrative Workstation hosts the Sage SalesLogix logging folders

RAM significantly improves performance, even under normal conditions, however, it must be increased if:

• Other applications are running on the Administrative Workstation

• The main database has more than 50,000 accounts

• The workstation is used to import large databases

Database Server

Database Server recommendations apply to database servers at both the main office and

Remote Office. The minimum and recommended hardware configurations for a Database

Server will vary considerably depending on the anticipated size of your database. After using

the information on page 47 to calculate the approximate size of your database, consult the

documentation from your database vendor (Microsoft SQL Server or Oracle) to determine the appropriate hardware to accommodate your company’s database.

The computer that hosts the Sage SalesLogix database is the heart of the Sage SalesLogix system; therefore, its selection and configuration can significantly affect performance. When purchasing a server, you should consider one that is larger and more powerful than your company currently needs so that you are prepared for future requirements.

Also consider a server that is scalable so you can upgrade it with more memory, additional processors, or more disk drives when needed. Switching to a different Database Server after implementation can be difficult and disruptive to your company.

The Database Server can be resource intensive, so you should dedicate the server to Sage

SalesLogix if possible. Follow these recommendations:

• Configure the Database Server as a stand-alone server and not a primary or backup domain controller.

• Do not use the Database Server as the primary Administrative Workstation in any installation except Express.

• Do not install the Sync Server on the Database Server unless you are using the Express installation.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Hardware

Random Access Memory (RAM)

Although each installation is different, you can use the following figures to estimate the amount of memory for a Sage SalesLogix Database Server.

• Allow an appropriate amount of RAM for the operating system and additional RAM for

Microsoft SQL Express (if Remote databases are created on the server).

• For the RDBMS and the Sage SalesLogix database itself, allow at least 128 MB of RAM.

More is better, so increase this number if the database is large.

• Each active user should have 5+ MB of RAM on the Sage SalesLogix Database Server.

Sage SalesLogix Client and Sync Server performance greatly improves when the database is cached in RAM. Use the database Cache Hit Ratio to determine whether the database is being cached in memory. Increase RAM if this percentage is low.

For performance reasons, running any applications other than the Sage SalesLogix Server on the Sage SalesLogix Database Server is not recommended.

Central Processing Unit (CPU)

The number and speed of the CPU(s), or processors, depends on the number of active users and the number of accounts in the system. The number of users affects both the volume and the type of transactions issued against the database. The number of accounts affects the processor time required to perform certain operations such as searches and sorting. Increase the size of your processor if you have a large number of active users and accounts.

Note

Be sure to include the Sync Server and Administrator in the active user count.

Check your database vendor’s documentation for recommendations about your company’s

database. Also, read Chapter 5, “Selecting a Database Management System”

before making any database hardware purchases.

Database Server Size Considerations

The number of accounts and contacts in the database are a factor when determining the size and configuration of the Sage SalesLogix Database Server.

Consider the following when determining the size and configuration of the Database Server:

• Number of accounts in the database

• Number of users who will be accessing the system at one time

• Number of tables and fields added to support any customizations

• Type of database management system

Number of Accounts

The number of accounts affects the amount and type of disk storage needed as well as the table sizes. The database size also affects the amount of RAM since performance greatly improves when all or much of the database is cached in memory. This means that RAM is more important than extra physical disk space when evaluating query performance.

Number of Active Users

The number of active users (the number of users accessing the database at any one time) affects three main areas.

• RAM

• Disk drives

• Processors

RAM Each active user requires a certain amount of RAM on the Sage SalesLogix Database

Server to perform functions such as sorting.

46 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Hardware

Disk Drives A large number of active users making many changes can put a significant load on the Sage SalesLogix Database Server disk drives, requiring more and faster drives.

Processors A large number of active users increase the number of processors required to handle requests without causing undue queuing.

Note

Be sure to include the Administrator and Sync Server in your count of active users.

Each counts as one active user.

Estimating the Size of Your Database

The size and type of RDBMS affects the amount of RAM and processor resources required on the Sage SalesLogix Database Server. Performance of both Oracle and Microsoft SQL Server improves when more RAM is allocated to the RDBMS and to each user. Oracle requires more

CPU resources due to its use of background resources. Another consideration is that the

RDBMS may affect the operating system you choose.

Sage SalesLogix Database Models

The size of your database is affected by the number of accounts it contains. Some average size estimates are shown in the following table. (These are average sizes only and assume that not all database fields are in use.)

To estimate the size of your company’s database, use the calculation: Number of Accounts multiplied by the Average Record Size plus the Space Occupied by Related Tables in the

Database.

You can use the following tables to help determine what your approximate database size should be prior to adding any customizations to Sage SalesLogix. The first table shows the approximate contents of an average database. The second table contains average record sizes for each of the fields. For example, in a company with 25,000 accounts, for each account you can expect to see approximately one opportunity, one contact, two sets of address records (the account address plus the contact address), three products, 50 known defects per product, and so forth. These figures will vary between companies. Also, most companies do not use all available fields. For these reasons, the figures you generate are only estimates. It is strongly recommended that you over-estimate your calculations.

Note

The figures in all of the tables in this section were compiled using average record sizes and an uncustomized version of Sage SalesLogix. When estimating the size of your database, use the information in these tables as a guideline only, since actual database size varies depending on the selected RDBMS. Also, each database maintains some system information within itself that may skew these numbers.

Approximate Table Contents

Figures shown are averages and should be used only as a guideline.

Number of Accounts

Number of Active Users

Opportunities per Account

Contacts per Account

Total Address Records (C+A)

Activities per Account

History per Account

Contracts per Account

Tickets per Account

Database A

25,000

50,000

1.5

Database B

75,000

225,000

Database C

250,000

100

1,500,000

100

3.5

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Hardware

Returns per Account

Products

Standard Problem/ Resolution per

Product

Defects per Product 50

Database A

1.5

Database B

Database C

100

Average Record Sizes

Figures shown are averages and should be used only as a guideline. When making your calculations, remember that some fields are static, and some are variable.

Sage SalesLogix file

Account

Contact

Opportunity

Address

Activity

History

Account Summary

Contract

Defect

Product

Returns

Standard Problem/Resolution

Ticket

Average record size (KB)

1.9

2.5

3.0

2.0

1.5

2.0

2.5

1.5

2.0

2.5

Express Installation Host Machine

When determining the necessary hardware for the machine serving as host to the Express installation, account for all the Sage SalesLogix components installed on this machine. This machine accommodates all of the Sage SalesLogix components, excluding the Sage

SalesLogix Client. For more information on the components included in an Express

Installation, see “Selecting an Installation Type” on page 21 .

Sage SalesLogix Client

When planning your configuration for the Sage SalesLogix Network Client, Sage SalesLogix

Remote Client, and Sage SalesLogix Network Client installations at a Remote Office, take into consideration network saturation.

More RAM and CPU resources are required on each client computer, depending on the number of other applications running on the computer, and as the number of accounts in the main database increases.

48 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Hardware

Remote Clients

A remote client machine must host the Remote user’s database and the Sync Client, so a more powerful machine will improve performance. Take into consideration the database size, synchronization method, and modem speed. Database size is determined by the number of records accessed, projected activity, features implemented, and subscription. As the size of the database increases, so does the need for a faster processor and more RAM.

• Increase the RAM on the remote computer if several other applications will be running or if the remote database has more than 5,000 accounts.

• You will require a faster CPU if the number of accounts in the remote database exceeds

5,000.

• Unless Sage SalesLogix Remote Clients are directly connected to a wide-area network

(WAN), you must install a Windows modem to synchronize via network, FTP, or HTTP.

Select a modem that gives you the speed and portability you want. Speed is limited when using a modem and phone line to synchronize the databases.

• Allow enough free disk space for the Sage SalesLogix applications, remote database, local

Sync folder, and synchronization files.

Synchronization Client

The load carried by the Sync Client varies depending on whether it is installed on a Remote

Office database server or on a Remote user machine. Consequently, the hardware requirements also vary.

RAM is the single most important resource for Sync Client when installed at a Remote Office.

Increase the amount of RAM for the Remote Office Sync Client based on the number of Sage

SalesLogix Clients served. For example, if you have more than 50 but less than 100 users, increase RAM by 64 MB.

If a single Remote Office is configured to handle more than 100 users, issues with Sync will arise.

• The Remote Office Sync Client CPU varies depending on the number of Sage SalesLogix

Clients and the selected operating system.

• The Remote Office Sync Client and related applications require approximately 50 MB of disk storage space. However, additional space may be required for processing, so make sure that an average of 200 MB is always free on the Remote Office Sync Client.

Sage SalesLogix Server

You can install the Sage SalesLogix Server and the Synchronization (Sync) Server on the same computer without adjusting hardware.

Note

The Sage SalesLogix Server requires the Windows operating system. If you are installing Sage SalesLogix using an Oracle database on a UNIX operating system, you must use a computer with the Windows operating system for the Sage SalesLogix

Server.

SpeedSearch Server

Requirements for the SpeedSearch Server depend on the size of your database, except for

Express installations. It is strongly recommended that you install SpeedSearch on a dedicated machine with a large hard drive.

Installation requires 22 MB. Additional space is required on the hard drive to build indexes of your documents. An index will occupy space roughly one third the size of your original document collection.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Hardware

Synchronization Server

The primary factor to consider when configuring the Synchronization (Sync) Server is the number of Remote users and Remote Offices. As the number of Remote Offices serviced by the Sync Server increases, the CPU size and amount of RAM must increase also.

With the exception of Express installations, install the Sync Server and Sage SalesLogix

Database Server on two separate computers, as the Sync Server and RDBMS both require significant resources. If the Sync Server supports more than five Sage SalesLogix Remote

Clients, it may reduce the client performance or even cause the server to stop responding altogether. Depending on your environment, it may be beneficial to divide your processing needs among several Sync Servers to balance the workload.

Some installations may require multiple Sync Servers. When determining the number of Sync

Servers, consider:

• Length of the Sync Server cycle

• Size and number of TEFs (more changes create larger files)

• Type of activity

See “Multiple Synchronization Servers” on page 60 for more information.

You can install the Sync Service on any computer with access to the Sync Server. The Sync

Service does not add to the hardware and software requirements of the machine on which it is installed, but the operating system must be a supported version of Windows.

Disk Storage

The Sync Server and related applications require approximately 50 MB of disk storage space.

However, when the Sync Server runs, it uses the following files, which also require space:

• Conflict resolution file (ConfTran.stm)

• WriteCache files

ConfTran.stm

The ConfTran.stm file is a stream file used to resolve conflicts between two users who have made changes to the same information within a given period of time. This period of time is specified in the Administrator along with the rules that govern conflict resolution. It is best to limit this time frame to something relatively small, such as 7 days, since a longer time interval results in a larger ConfTran.stm file, thus reducing Sync Server performance. During the course of a synchronization cycle, all updates processed by the Sync Server are copied to the ConfTran.stm, which may require one to five MB of disk space.

WriteCache files

WriteCache files are used to accommodate the internal process used for writing TEFs. When

WriteCache reaches a certain size, it creates a TEF. These temporary files may require as much as 100 MB depending on the number of Remote users supported by the Sync Server.

The following table shows the total space required by the Sync Server when these additional components are taken into consideration. These figures do not include the operating system files.

Sync Server files

Executable and support files

Conflict resolution stream file (ConfTran.stm)

WriteCache files

Total space required

Space required

50 MB

1-5 MB

20-100 MB

71-155 MB

50 Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Hardware

Remote Office Server

The Remote Office server accommodates the Remote Office database, including the Sync

Client and File Server.

Note

Remote Office installations do not require an Administrative Workstation, because this function is managed at the main office

Additional Installation Considerations

• The Sage SalesLogix Server requires TCP/IP as the network communication protocol.

TCP/IP must be installed and configured on every computer running the Administrator,

Architect, Application Architect, or SpeedSearch.

• Sage SalesLogix products use a four-digit year regardless of the Windows date format set on each individual computer.

• If the Sage SalesLogix Server is on a different network domain from some or all of the

Sage SalesLogix users and components, these domains must have a trust relationship with each other and must be able to share data.

Sage SalesLogix Planning Guide v7.5

Understanding Sage SalesLogix Hardware

52 Sage SalesLogix Planning Guide v7.5

Chapter 7 Synchronizing in Sage SalesLogix

If your installation supports Remote users or Remote Offices, changes to all Sage SalesLogix databases must be reconciled. Sage SalesLogix achieves this using synchronization.

In Sage SalesLogix, synchronization is basically an exchange of files (containing database changes) between Remote Offices, Remote users, and the main office. This file exchange is possible because all changes made to the Remote and main database are logged in

Transaction Exchange Files (TEFs).

Sage SalesLogix synchronizes at the field level; this means that when a specific value is changed, only the field change is sent. The entire record does not have to be sent to the main database or to the Remote Offices and users.

This chapter explains how synchronization works and the available methods for synchronizing.

Synchronization Overview

The illustration in Figure 5 provides an overview of the synchronization process for the main

office and remotes. The term “remotes” refers to Remote users, Remote Offices, disconnected Web Clients, and Web Remote Offices. Remote users connect to their own databases on their own computers (such as a laptop). A Remote Office supports Network users who connect to the Remote Office database via a network (a regional office, for example). A Web Remote Office supports WebViewer and Web Client users who connect to the Web Remote Office via the Internet.

The main office, which supports both Network and Remote users, requires the following:

• Main office database

• Central set of synchronization folders (under the shared Sync Logs folder)

• Synchronization Server

Remote users and the Remote Office require the following:

• Subset of the synchronization folders

• Sync Client

Figure 5 Synchronizing Remote and Main Office Databases

Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

Figure 5

shows how Remote Offices and Remote users use Sage SalesLogix applications (such as the Sage SalesLogix Remote Client) to make changes to the Remote databases. These changes are logged as TEFs in the Remote Sync folders (indicated by the black arrows on the

Remote side). Sage SalesLogix applications, such as the Administrator, make changes directly to the main database. These changes are logged as Network Logs (WGLogs) in the shared Sync folders (indicated by the black arrows on the main office side).

The Sync Client on the Remote side then transfers these TEFs to the shared Sync folders at the main office (indicated by the white arrows). The Sync Client is also responsible for moving files waiting in the main office shared Sync folders to the Remote Sync folders. These files are then applied to the Remote database (shown by the grey arrow on the Remote side) so that the Remote database contains the same information as the main database.

In turn, the Sync Server at the main office processes files from the Remote Offices and

Remote users and applies them to the main database. It also generates files of these changes for the other Remote Offices and users (indicated by the grey arrow on the main office side).

In addition, the Sync Server processes the WGLogs generated by users at the main office and sends them to multiple Remote Offices and users so that all distributed databases eventually contain the same information as the main database.

Site Codes and Synchronization

Each Sage SalesLogix user is assigned a site code. A site code is an alphanumeric code that is unique to every Sage SalesLogix component. Each user (Network, Remote, or administrative), each Remote Office, and each Sync Server has a unique site code in the

Sage SalesLogix system. Every Sage SalesLogix database also has a site code.

Site codes enable an individual Remote user to filter their TEFs from the files of other Remote users or a Remote Office. Sage SalesLogix tags all TEFs with the code of the Sage SalesLogix component that will eventually receive and process the file.

When a Remote user generates TEFs with changes to be sent to the main office, those files include the site code of the Sync Server the Remote user is assigned to. In turn, when the

Sync Server generates files to be sent to Remote Office and users, it tags the files with the site code of the user that will receive and process the file.

Determining Your Synchronization Method

When developing your synchronization strategy, you must determine how the Remote Office and Remote users are going to send and retrieve transactions. Three synchronization methods, Network Synchronization, FTP, and HTTP are supported in Sage SalesLogix.

Network Synchronization

You can synchronize with the main office 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.

FTP Synchronization

FTP support is built into both the Sync Server and Sync Client. Synchronization by FTP requires that you establish an FTP site on an FTP server. Remote Offices and Remote users upload and download files through the Internet or a TCP/IP network connection using FTP.

When creating an FTP site for Sage SalesLogix you must create shared folders on the FTP server and virtual directories that point to the shared folders. All Remote users and the Sync

Server must have read, write, and delete access to these folders.

Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

HTTP Secure Synchronization

HTTP Synchronization provides a secure method of transferring data using a Web site on an

HTTP Server. When the Sync Server cycles, it connects to the HTTP Server and searches the

Infiles folder for any TEFs that were uploaded by Remote Offices and Remote users. Likewise, when the Sync Client cycles, it connects to the HTTP Server and searches the Outfiles folder for any TEFs placed there by the main office. All TEFs, library files, and documents are uploaded to and downloaded from the HTTP Server. Internet Information Services is supported, however, any Web Server that supports mapping of folders for uploading and downloading can be used.

When synchronizing using HTTP Sync you must create shared folders on the HTTP server and virtual directories that point to the shared folders. All Remote users and the Sync Server must have read, write, and delete access to these folders.

Sync Transfer Profiles

In Sage SalesLogix, a single Sync Server can support any combination of synchronization methods. For example, some Remote users may synchronize via the network, while others use FTP or HTTP.

A Sync Transfer Profile in the Administrator defines each synchronization method and its parameters. You can create multiple Sync Transfer Profiles in Sage SalesLogix based on synchronization processes and number of FTP servers. Remote users must be assigned a

Sync Transfer Profile and Sync Server, in order to exchange files with the main office database. If a transfer profile is disabled, synchronization via that method will not occur.

Folder Structure

To synchronize the main office and Remote databases, all Sage SalesLogix users must have access to a synchronization folder. Consequently, you must create one folder for each Sync

Server in the system. In a Remote user installation, this folder is always called Sync Logs. In a Remote Office installation, you can create your own name for the folder. In this document, it is referred to as RemOfficeSync Logs. The computer on which this folder resides is referred to as the host.

No actual connection exists between the Sync Server and the Remote database. Instead,

Sage SalesLogix uses an off-line synchronization process where all communication is accomplished by both the Sync Server and the Sync Client placing files in, and retrieving files from, the shared Sync Logs folder.

The synchronization folder (either Sync Logs or RemOfficeSync Logs) is located on the Sync

Server or on a separate file server. The Administrator is used to assign the synchronization folder and Remote Offices and users to a particular Sync Server.

The Documents and Library folders also play a role in synchronization. Sync Server obtains copies of the necessary files in these folders and delivers them to the Remote Offices and users. In turn, files sent from the Remote Offices and users are placed in the shared Library or Documents folders so they can be used by the main office.

Synchronization Folders at the Main Office

The following folder structure is recommended for the synchronization folders:

\\ServerName\Sync Logs (root directory for sync folders and files)

\\ServerName\Documents

\\ServerName\Library

\\ServerName\SyncService (shared folder for the Sync Service)

Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

If you already have a document server, you can use that location for the Documents and

Library folders. If the Documents and Library folders cannot be found on the remote computer (user and office) they will be created by Sage SalesLogix. See the Synchronization

Server online Help for more information.

You must share the Sync Logs, Documents, and Library folders even if you are not using synchronization. See “Sage SalesLogix Logging Folders” on page 12 for more information. See the Windows Help for details on folder sharing.

When deciding where to place the Sync Logs folder, keep in mind that the number of users

(especially Remote users) and the use of attachments or the Library dramatically affect the size of this folder. It is important to have enough free disk space on the drive where the Sync

Logs folder resides, however, the amount required depends on your company. Some Sage

SalesLogix users report the Sync Logs folder as requiring gigabytes.

Main Office Synchronization Sub Folders

The shared Sync Logs folder at the main office contains sub-folders that Sage SalesLogix automatically creates the first time the Sync Server runs. These folders are:

• Infiles - Remote users and Remote Offices place their incoming TEFs in this folder when they synchronize with the main office.

If you have multiple Sync Servers, each Sync Server uses its own Infiles folder. TEFs from the Infiles folder on all Sync Servers are moved to the SharedLogs folder of the destination

Sync Server.

• Outfiles - All files to be sent to Remote Offices and Remote users are placed in this folder. During synchronization, Remote Offices and users obtain files from this location. If you have multiple Sync Servers, each Sync Server uses its own Outfiles folder.

• WGLogs - When users at the main office (including the administrator) use various Sage

SalesLogix applications to make changes directly on the main database, Sage SalesLogix places transaction files in this folder.

Note

All Network users at the main office are assigned to one Sync Server. Only this Sync

Server has files in WGLogs to share. Other Sync Servers at the main office only have

Remote Offices and Remote users assigned to them and therefore only have Infiles to share.

• FailedTrans - This folder contains transactions from both Remote Offices and Remote users, and the host that contain synchronization errors. When a synchronization error occurs, a transaction containing the error and information from the TEF is written to the

FailedTrans folder. In addition, errors are also written to the SyncError.txt file.

You can view the failed transaction files using TrnViewer. All transaction files must be manually deleted from the FailedTrans folder.

• Archives - This folder keeps a copy of all files sent to Remote users and offices with the exception of documents and attachments. There is no need to maintain a copy of documents and attachments sent to Remote Offices and Remote users since they already exist in the shared location on the network.

Archives are deleted once a confirmation is received from the Remote Office that the file was successfully transferred. However, this self-maintenance process only occurs if you configure the Sync Server to “sequence files before apply”. See the “Configuring the

Synchronization Server” topic in the Administrator Help for more information.

• SharedLogs - If you have multiple Sync Servers, this folder contains copies of the Infiles and WGLogs processed by the secondary Sync Servers. Each Sync Server uses its own

SharedLogs folder.

• Tasks - This folder is created the first time the Sync Server runs. It is empty until a

Remote user or Remote Office uses the Retrieve option under Remote Tasks to transfer a file. The Sync Client converts the file to a TEF, and sends it to the Host (the database from which Remotes were created), where the Sync Server identifies the file as a Task and deposits it in the Tasks folder.

56 Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

• PortalDeployments - This folder contains any new Web portals from the Application

Architect to be delivered to Web Remote users and Remote Offices. The information in this folder is converted to a TEF file and synchronized to remotes. After the Sync Server processes the folder, the contents are deleted.

Synchronizing the Main Database

Remote users and Remote Offices synchronize with the main office by sending and receiving

TEFs. The Sync Server then updates the main database with these files when it runs at regularly scheduled intervals.

The following steps occur during synchronization via the Sync Server.

1. The Sync Server processes the Sage SalesLogix Network Client and Web Client’s WGLogs files and prepares them for sending to Remote Offices and users.

2. The Sync Server processes any portals and prepares them for sending to disconnected

Web Client users and Web Remote Offices.

3. TEFs received from Remote Offices and users are applied to the main database.

4. Network and Remote Client files are then used to generate files for the Remote Offices and users containing all necessary changes. These files are placed in the Outfiles folder under the Sync Logs folder on the network.

Remote Synchronization

The Sync Client processes synchronization files and ensures that the main database and

Remote database(s) contain the same information. Remote users have the Sync Client installed on their computer.

Synchronization Folders and Remote Users

Each Remote user installation contains a set of synchronization folders that are used during synchronization. These folders are stored under the remote user’s Sync folder and are automatically created by Sage SalesLogix.

• Infiles - The Sync Client places files received from the main office in this folder when

Remote Offices and Remote users synchronize.

• Outfiles - All files to be sent to the host are placed in this folder. The Sync Client then moves the files from this location to the main office during synchronization.

• Archives - This folder keeps a copy of all files sent to the main office.

• FailedTrans - This folder is a temporary holding place for transactions that will be sent to the Host. When a synchronization error occurs (for example, a transaction failed to apply), a message flashes stating that Sync Client is sending failed transactions. Once the transactions are sent successfully, they are deleted from the FailedTrans folder.

This folder is created in C:\Documents and Settings\All Users\Application

Data\SalesLogix\Sync.

• QUEUEFiles - Stores transaction queue files generated by the Remote user. These queue files are created with every database commit and typically contain a small amount of data.

• PortalDeployments - This folder temporarily holds delivered portal files until they are registered. During the registration process the files are moved to their final location.

Synchronizing Remote User Databases

The following steps occur when Remote user databases synchronize with the main office:

1. The Remote user sends TEFs to the Host.

Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

2. The shared Sync Logs folder is accessed on the network at the main office. If the shared

Sync Logs folder cannot be located (for security or network reasons), synchronization does not take place.

3. The Sync Client copies the contents of the Outfiles folder on the Remote to the shared

Sync Logs\Infiles folder at the main office.

4. Files containing the Remote user’s site code are copied by the Sync Client from the shared Sync Logs\Outfiles folder at the main office to the Remote user’s Infiles folder.

5. The Sync Client copies the contents of the FailedTrans folder on the Remote to the shared

Sync Logs\FailedTrans folder at the main office.

6. The Sync Client updates the Remote database with the Sync Infiles, now on the Remote.

7. If the remote is a disconnected Web Client, and a portal has been synchronized to the local machine, the portal is processed.

a. Once the files have been moved to their destination the source manifest and portal are removed.

b. The site is registered with the Sage SalesLogix Personal Web Server.

Note

When the Sage SalesLogix Personal Web Server starts, a check is done to see if any portals are awaiting processing. If so, they are queued for processing.

Automatic Sync

Automatic Sync—available to Sage SalesLogix Remote Offices and Remote users—starts the synchronization process automatically when it detects that the computer is online and the

Sync Logs folder is available. The Sync Client begins the synchronization process in the background, while the user or office continues with other work. Remote users and Remote

Offices can suspend Automatic Sync, but must do so each time they log on to their computer.

They can also set up an automated synchronization schedule.

Remote Office Synchronization Folders

To synchronize the main office and Remote Office database, you must create a synchronization folder (for example, RemOfficeSync Logs) and it must be accessible to all

Sage SalesLogix users at the Remote Office. Typically, the synchronization folder is located on the Remote Office Synchronization Client. This is the best location to place it, but it is not a requirement. You may choose to install the synchronization folder on a separate file server instead.

When deciding where to place the RemOfficeSync Logs folder, keep in mind that it can consume large amounts of disk space. The amount varies depending on the number of accounts in the Remote Office database and the use of attachments or the Library. It is important to have enough free disk space on the drive where the RemOfficeSync Logs folder resides.

Use the following recommended file structure for the synchronization folder, regardless of its location.

\\ServerName\RemOfficeSync Logs (root directory for sync folders and files)

\\ServerName\Documents

\\ServerName\Library

The RemOfficeSync Logs folder must be created and shared to allow access by everyone

(including the SLXService user). The Library and Documents folders must also be created and shared on the Sync Client computer or a separate file server at the off-site location. If the

Documents and Library folders are not created, Sage SalesLogix automatically creates them under the RemOfficeSync Logs folder during the first synchronization cycle.

The Administrator at the main office is used to specify the location of the RemOfficeSync

Logs, Documents, and Library folders and to configure the Sage SalesLogix users attached to the Remote Office.

Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

Remote Office Synchronization Sub-Folders

In a Remote Office installation, Sage SalesLogix automatically creates sub-folders under the shared RemOfficeSync Logs folder. These folders are:

• Infiles - TEFs from the main office are placed in this folder when the Remote Office synchronizes. The Remote Office Sync Client then applies these files to the Remote Office database.

• Archives - This folder keeps a copy of all files sent to the main office.

• PortalDeployments - This folder temporarily holds delivered portal files until they are registered. During the registration process the files are moved to their final location.

Synchronizing the Remote Office

The following steps occur when Remote Office databases synchronize with the main office:

1. The Remote Office establishes a connection with the main office and accesses the Sync

Logs folder. If the Sync Logs folder cannot be located at the main office (for security or network reasons), synchronization does not take place.

2. The Remote Office sends the contents of the RemOfficeSync Logs folder to the main office

Sync Logs folder.

3. The Remote Office copies the contents of the WGLogs folder to the Sync Logs\Infiles folder at the main office.

4. Files containing the Remote Office site code in the file extension are copied from the Sync

Logs\WGLogs folder at the main office to the Remote Office Infiles folder.

5. The Remote Office copies the contents of the FailedTrans folder to the Sync

Logs\FailedTrans folder at the main office.

6. The Remote Office Sync Client updates the Remote Office database with Infiles now at the Remote Office.

7. If this is a Web Remote Office, and a portal has been synchronized to the local machine, the portal is processed.

a. Once the files have been moved to their destination the source manifest and portal are removed.

b. The site is registered with the Sage SalesLogix Personal Web Server or IIS.

Remote Office, Account Ownership, and Security

Users assigned to a Remote Office own accounts, belong to teams, and have security profiles just like Sage SalesLogix users at the main office. Security determines the accounts and other records that the Remote Office should receive; only accounts sent during synchronization are those that users at the Remote Office have permission to access. This includes all accounts owned by teams of which the user is a member. The user does not have to be the team owner for this to occur, but must have access to the account.

Records that a Sage SalesLogix user has access to are sent to the Remote Office during synchronization. It is important to keep this in mind when configuring teams and account ownership for Remote Office users because it is easy to end up with a Remote Office database that contains all the records in the main office database. Poor team and account ownership planning causes the Sync Servers at the main office and the Sync Client(s) at the Remote

Office(s) to process large volumes of files. This affects overall system performance.

Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

Multiple Synchronization Servers

Generally, Sync Servers can handle a large number of Remote users and/or users assigned to a Remote Office. This, of course, depends on the type of activity and the volume of TEFs on the server.

Multiple Sync Servers allow you to handle a larger number of Remote users and Remote

Offices, and to distribute the processing load evenly. When your Sage SalesLogix environment contains multiple Sync Servers, the primary Sync Server must process

Workgroup Logs. Therefore, all Remote Offices must be connected to the primary Sync

Server at the main office.

When implementing multiple Synchronization Servers, note the following general recommendations:

• The recommended maximum number of users per Sync Server is 150.

• If possible, allocate entire regions to the same Sync Server. For example, West, Central, and East.

• If your implementation includes a large number of Network users, reduce the number of

Remote users on the primary Sync Server. For example, if you have 200 Network users and 375 Remote users, assign 75 Remote users to the primary Sync Server and 150

Remote users to each of the secondary Sync Servers.

If most Remote users view account activity, but do not create new accounts or contacts, you can assign more users to one Sync Server.

Multiple Synchronization Servers Example

The following is an example of synchronization processing in a multiple Sync Server environment.

1. Network user A creates a team-owned account. Remote users A and B are members of the team that owns the updated account.

2. The Database Server is automatically updated with the account change and a Workgroup

Log is created on Sync Server 1 (the primary Sync Server).

3. Sync Server 1 sends a TEF containing the change to Remote user A and Sync Server 2.

4. Sync Server 2 sends the change to Remote user B.

5. Remote user C is not a member of the team which owns the account. Therefore, Sync

Server 3 does not receive or send the change.

60 Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

Scheduling the Sync Server

A synchronization cycle is the time required by the Sync Server to process changes and generate files for Remote users. The length of time it takes to complete this cycle varies depending on the amount of information being sent, the method of synchronization, and other network traffic.

Because synchronization can be taxing on the system, Sage SalesLogix recommends that you run synchronization during off-peak times, such as early morning, during lunch, or after normal business hours.

Prior to synchronization, you can specify which operations you want to perform. For example, you can elect to send only changes to Remote Office and users or to apply only TEFs to your database. The following table contains a typical Sync Server schedule.

Scheduled Time

Midnight

3:00 AM

6:00 AM

Noon

6:00 PM

9:00 PM

Jobs to Run

Sync All

Back up the Database (automated)

Sync All

Updates Only

Sync All

To implement this type of schedule, use the Synchronization Service. The Sync Service enables you to run the Sync Server from Windows as a service and to monitor synchronization jobs remotely using the Monitor Console. Sync server errors are written to the standard Windows Event Viewer. For more information about the Monitor Console see

“Sage SalesLogix Utilities” on page 11 .

Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

Third-party schedulers, such as WinAT, System Agent, Norton Scheduler, and others, are designed to run with command line options and can also be used to run synchronization. For example, if you are using the Sync Service to run Synchronization Server, the service cannot call any agents that require a third-party application, such as Outlook. The solution may be to create a window of time when the Sync Service does not have a job scheduled, then use a third-party scheduler to run Sync Server with agents during that time. That way, you can run agents that require a third-party application and take advantage of the Sync Service at the same time.

Note

If you plan to install Sage SalesLogix using the Express Installation, you must create a domain user in order to log on and cycle the Sync Server. The Local System account created in the Express Installation does not allow you to run agents.

For more information, see the “Sync Server Command Line Options” topic in the

Synchronization Server Help.

Subscription

Note

Subscription only applies to Remote users. It does not apply to Network users or

Remote Offices.

Subscription is designed for Remote users who must maintain a database on their local computer. It improves performance by allowing Remote users to select or “subscribe” to the accounts they use on a regular basis. Subscription minimizes the database size and the time required to synchronize data by giving each Remote user a subset of the main database.

System performance improves when a Remote user database is limited to approximately

3,000-5,000 accounts.

Subscription is determined at the account level. The system administrator or individual

Remote user specifies the accounts to which the user subscribes.

For example, John may have access to 10,000 accounts in the main office database, but only wants to keep a few hundred on his laptop computer (in a Remote database). John can subscribe to only those accounts he wants to keep on his laptop. There 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 Sage SalesLogix

Remote Client or Administrator.

Note

Manual account subscription does not apply to disconnected Web Clients. Web Client users accessing a local database receive accounts set up through subscription rules and forced subscription. Remote Web users cannot manually choose which accounts they want to receive.

Sage SalesLogix highly recommends the use of subscription because it improves performance by reducing the size of the Remote user database. Sage SalesLogix also recommends using

subscription rules rather than manually selecting accounts.

Subscription Rules

Subscription rules specify the criteria for selecting accounts from those the Remote 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.

Subscription rules are written using the Query Builder. When a subscription rule is written, only accounts that meet the criteria are sent to the Remote user during synchronization.

When multiple subscription rules apply to a user (for example, the user has a Team Owner profile, owns accounts as an individual, or has private accounts) all accounts that match each of the rules will be synchronized to the user.

Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

Advantages of Subscription Rules

Subscription rules are dynamic. Once a rule is written and applied to a user, any new accounts that match the rule’s conditions are automatically synchronized to the Remote user.

As a result, administration time is reduced because no one has to manually select the accounts for synchronization.

Another advantage to subscription rules is that they reduce the number of synchronization cycles it takes for a Remote user to receive a particular account. For instance, when a Remote user manually subscribes to an account, only a request for that account is sent to the main office the first time the Remote user synchronizes. The next time the Sync Server runs, it processes the request and creates a transaction containing the newly subscribed account.

When the Remote user synchronizes again, he or she receives the requested account.

However, using subscription rules, the Remote user receives the account the first time he or she synchronizes after the account is added to the system.

Subscription and Security

When determining if a Remote user receives an account through synchronization, you should consider two factors:

• Account ownership

• Subscription

Sage SalesLogix security determines which accounts a user has access to, based on account ownership as described in “Understanding Account Ownership” on page 33 . Remember that account ownership can be at the individual user level or at the team level, where “everyone” is a special system team.

Then, when security determines which accounts a user can access, some of these accounts are automatically synchronized to the Remote Office and user. This process is called forced

subscription.

The user has the ability to subscribe to the remaining accounts by using subscription rules.

The following table illustrates how security and account ownership are the foundation for subscription, particularly forced subscription.

And the user is… If the account owner is…

Individual User

Team

Everyone

The account owner

On the account owner’s team

A team member with the “Team

Owner” security profile

A team member

Any user

User is forced to subscribe

User can subscribe

Yes

N/A

Yes

N/A

Yes

Unsubscription Rules

Sage SalesLogix also supports unsubscription rules. These rules specify criteria for removing accounts from a Remote user’s local database. However, an unsubscription rule never removes accounts that were synchronized to a user as a result of forced subscription. A

Remote user cannot be unsubscribed from accounts where he or she (as an individual) is the account owner.

Sage SalesLogix Planning Guide v7.5

Synchronizing in Sage SalesLogix

64 Sage SalesLogix Planning Guide v7.5

Chapter 8 Customizing Sage SalesLogix

Sage SalesLogix is extremely customizable, with many options and tools for customizing both the procedures and the appearance of screens. You can customize Sage SalesLogix to accommodate your company’s unique environment and business needs.

It is not necessary to customize Sage SalesLogix with the initial installation. You can customize over time as your company becomes more comfortable with Sage SalesLogix and its components. The standard reports, forms, templates, and other information can be used as the foundation for your customizations. You can also use features included in the evaluation database as models.

When you are ready to customize Sage SalesLogix, use the following table to find information in the online Help systems that are specific to the changes you want to make. Help is available from the Help menu, Help buttons, or by pressing F1 from the application.

Note

The level of customization available depends on your Sage SalesLogix license type.

Licenses are described in “Sage SalesLogix Licenses” on page 25 .

What do you want to do?

Customize Sage SalesLogix Plugins

Customize the menus and toolbars users see in the Sage SalesLogix Client.

Help System - Topic Name

Architect - Menus and Toolbars

Sage SalesLogix Client - Customizing Menus and Toolbars

Application Architect - Adding Toolbar Menu

Items

Understand plugins and how they are used to customize Sage SalesLogix.

Architect - What are Plugins?

Understand templates and how you can build new templates or edit existing templates for documents such as letters, memos, or fax cover sheets.

Architect - Templates Overview

Customize your Web pages.

Basic Scripts: Write Basic code that can be used by views and reports, executed using agents, tied to menu or toolbar functions, or executed by a task in Processes.

Application Architect Help - Editing a Form

Architect - Basic Scripts

Bundles: Use bundles to package your custom components for easy installation and management.

Administrator Help- What are Bundles

Architect Help - Bundles and Bundle a Project

(Network)

SQL Scripts: Use SQL scripts to build SQL statements that can be used by views and reports, linked with views and objects on views, executed using agents, or tied to menu or toolbar items.

Application Architect Help - Creating a

Bundle

Architect - SQL Scripts

Sage SalesLogix Planning Guide v7.5

Customizing Sage SalesLogix

What do you want to do?

Help System - Topic Name

VBScripts: Use VBScripts to write code that can be used by views and reports, linked with forms and form controls, or tied to menu or toolbar items.

Architect - Visual Basic Scripts

Automate Sage SalesLogix Tasks

Agents: Schedule agents to automatically run reports, Basic scripts, SQL scripts, VBScripts, and so on.

Administrator - What are Agents?

Processes: Create processes to perform repetitive tasks or automate the customer follow-up process.

Architect - Managing Sales Processes

Make Sage SalesLogix Work for Your Business

Calculated Fields: Use calculated fields to combine the values of several fields from one or more tables to create a new value.

Administrator - Calculated Fields

Competitors: Keep track of competitors by supplying information such as rating, strengths, weaknesses, strategy, product information, and customer information.

Application Architect - Implementing Process

Orchestration

Sage SalesLogix Client - Managing

Competitors

Web Client - Competitors Tab

Dashboards: Dashboards are tool sets that allow you to display and interact with a variety of performance and analysis information to gain insight into organizational and individual performance.

Sage SalesLogix Client - Dashboards

Groups: Build groups of accounts, contacts, opportunities, or tickets based on complex queries.

Query Builder - Using the SalesLogix Query

Builder

Lead Sources: Manage lead sources to record how contacts heard about your company.

Web Client - What are Groups?

Sage SalesLogix Client - Manage Lead

Sources

Literature: Manage your company’s literature items (for example, by adding new items or editing the quantity on hand).

Web Client - What are Leads?

Sage SalesLogix Client - Manage Literature

Literature: Fulfill literature requests.

Sage SalesLogix Client - Fulfill or Complete a

Literature Request

Lookups: Use Lookups to give users different methods to search for accounts, contacts, opportunities, and related data.

Marketing: Capture lead information from a

Web page or external list and import into Sage

SalesLogix; track lead qualification and convert leads to contacts, accounts, or opportunities; use stages and tasks to design and organize campaigns; and analyze the impact and cost of a marketing campaign.

Administrator and Architect - Manage

Lookups

Sage SalesLogix Client - What are Lookups?

Sage SalesLogix Client - Introduction to

Marketing Services; Managing Campaigns and Campaign Tasks, Qualifying Leads;

Adding/Editing/Completing Campaign

Stages

Web Client - What are Leads?

66 Sage SalesLogix Planning Guide v7.5

Customizing Sage SalesLogix

What do you want to do?

Multi-Currency: Learn more about multicurrency support and the locations of the settings.

Help System - Topic Name

Administrator - Understanding Multi-

Currency Support

Sage SalesLogix Client and Web Client -

Understanding Multi-Currency

Pick Lists: Learn more about using pick lists to simplify data entry.

Administrator - Pick Lists

Architect and Sage SalesLogix Client - Pick

List Manager

Products: Specify detailed product and pricing information that users can select from when adding opportunities.

Sage SalesLogix Client - Managing Products

Quotas: Manage sales representatives and their quotas.

Resources: Manage resources such as conference rooms and equipment.

Sage SalesLogix Client - Managing Quotas

Sage SalesLogix Client - Manage Resources

Sales Processes: Manage your sales pipeline. Sage SalesLogix Client - Sales Processes

Work with the Sage SalesLogix Database

Use the Database Manager to name indexes, or add custom tables and fields to the database.

Administrator and Architect - Database

Manager

Sage SalesLogix Database Help System

Use the SalesLogix Profiling Tool Kit to trace

SQL and performance counters throughout the execution path of the provider for any Sage

SalesLogix application.

SalesLogix Profiler - SalesLogix Profiler Help

System

Sage SalesLogix Planning Guide v7.5

Customizing Sage SalesLogix

68 Sage SalesLogix Planning Guide v7.5

Appendix A

Importing Data Into Sage SalesLogix

Importing data transfers information from a source database into your Sage SalesLogix database. You can import data into Sage SalesLogix from other contact management systems (such as ACT! by Sage) or from legacy systems maintained by your company. You can also schedule data for automatic import into Sage SalesLogix on a regular basis (weekly or monthly, for example) from other systems.

Before the data transfer can take place, you must map tables and fields in the source database to corresponding tables and fields in the Sage SalesLogix database. You can accomplish this by using one of the following tools:

• The Import Wizard

• A third-party tool or custom application

Any table or field that is not mapped will not be imported.

Import Wizard

The Import Wizard is a utility used for importing data into Sage SalesLogix from ACT! by

Sage and other commonly used file formats.

5/ detailed Import Wizard instructions.

Importing from ACT! by Sage

Predefined import maps (templates) are available for the following versions of ACT! by Sage:

• Version 3.x (single-user or multi-user)

• Version 4.x (single-user or multi-user)

• Version 5.x (single-user or multi-user)

• Version 6.0 (use the version 5.0 import map)

Custom Import Maps

If the information you want to import does not have a predefined map, you can create a custom field map using the Import Wizard.

Importing from Common File Types

You can also import data stored in some common database formats (file types) into Sage

SalesLogix using the Import Wizard. Supported file types are:

• ASCII (with the exception of tab delimited)

• dBase

• Paradox

Sage SalesLogix Planning Guide v7.5

Importing Data Into Sage SalesLogix

Pre-configured Sage SalesLogix import maps are not available for the common file types. You must create a custom import map containing the correct data relationships. This requires a thorough understanding of the Sage SalesLogix database architecture and structure, so we recommend working with your Sage SalesLogix Business Partner or the Sage SalesLogix

Professional Services Group when creating a custom import map.

Preparing to Import Data

When importing data into Sage SalesLogix, you map current users to Sage SalesLogix users.

For mapping to take place, all users and teams from the source database must exist in the

Sage SalesLogix system prior to beginning the import process. Use the Administrator to create new users and teams in the Sage SalesLogix database if needed.

You can also import custom information into Sage SalesLogix. Tables and fields from the source database must have corresponding tables and fields in the Sage SalesLogix database.

You may need to add tables and fields to the Sage SalesLogix database.

For example, perhaps you would like to import additional information about contacts (such as their hobbies) into Sage SalesLogix. The default Sage SalesLogix database has no place for this information, so you must create a new table with fields for the additional information and associate it with (join it to) the Contact Table. Use DB Manager in the Administrator or

Architect to build this table.

Before any data is imported into Sage SalesLogix, you must know what additional tables and fields are required. This is especially true when using Microsoft SQL Server or Oracle for the

RDBMS because database objects must be sized for best performance.

9/5/08

Routine Data Imports

You can import data from other sources into the Sage SalesLogix database automatically at regularly scheduled intervals without user input. For example, you may want to routinely import mailing lists you have purchased or names from a lead tracking system into Sage

SalesLogix. To do this, create a Basic script to import the data, then run it as a Sage

SalesLogix agent at the end of the synchronization cycle. You can ask your Sage SalesLogix

Business Partner or Professional Services Group representative for more details.

70 Sage SalesLogix Planning Guide v7.5

Appendix B

Networking Sage SalesLogix

Sage SalesLogix is a 32-bit client/server application that operates most efficiently in a

Microsoft Windows environment. This means that communication between the clients and servers take place over a network using standard network protocols.

When preparing your network for Sage SalesLogix, be aware of the following requirements:

• The network protocol must be TCP/IP.

• In a mixed Novell/Windows network, you must have support for long file names.

When setting up the network, keep in mind that each Sage SalesLogix Client user must be able to access the Documents, Library, and synchronization folders. The Administrator,

Architect, Sync Server, and Sage SalesLogix Client are all reading from, writing to, and changing the contents of these folders throughout the day.

Network Communication Link

In Sage SalesLogix, a network connection is the default method of synchronizing files between the main office and Remote Offices and Remote users. This may be accomplished using a Remote Access Communication (RAS) or Virtual Private Network (VPN) connection.

After the network is installed, make sure that the communication link between the Remote

Office and users and the Sync Server folder is secure enough for large quantities of files to be copied.

Networking Operating Systems

In installations where you are networking operating systems, such as Novell with Windows,

Sage SalesLogix requires a supported Windows Server. The server may reside on a non-

Windows network.

WINS Servers

WINS Server is a dynamic database from Microsoft that is designed to resolve NetBIOSderived computer name to IP address translation. If you are using Dynamic Host

Configuration Protocol (DHCP) on your network, a WINS Server can handle the mapping between computer names and IP addresses. It also maintains a database that is automatically updated as the computer names and IP addresses change.

Note

DHCP and WINS may be required to obtain name resolution successfully in some mixed networks.

WINS servers provide the following benefits:

• Prevents users from registering duplicate NetBIOS computer names on the network

• Centralizes administration of the NetBIOS name database and its replication to other

WINS servers

• Reduces IP address broadcast traffic

• Supports Windows-based clients

• Depending on the router, has the ability to allow transparent browsing across routers for various Windows versions

Sage SalesLogix Planning Guide v7.5

Networking Sage SalesLogix

Using Terminal Server

Microsoft Windows with Terminal Server provides your company with a low cost, “thin client” network solution, with all the benefits of a centrally managed environment. Terminal Server allows a server to host multiple, simultaneous client sessions of Sage SalesLogix or any other

Windows-based applications.

Besides the Terminal Server, a Terminal Server Client application is required on each network and Remote user’s computer for connection to Sage SalesLogix.

The many advantages of using Sage SalesLogix on a Terminal Server include:

• It centralizes network administration and resources by putting the Sage SalesLogix application on a server rather than on individual desktop and laptop computers.

• It improves Sage SalesLogix maintenance because the system administrator only has to upgrade one server, instead of each user on the network.

• It gives Remote users access to the same data as local users, without the need of administering Sync Servers.

In a Terminal Server implementation, all Sage SalesLogix processing takes place on the server, with only video, mouse, and keyboard traffic passing between the client and Terminal

Server. This allows for the use of less robust computers than are normally recommended for client workstations.

For more information on planning and deploying Sage SalesLogix on a Terminal Server, see the Microsoft Web site at www.microsoft.com and Sage SalesLogix Knowledge Base Articles and White Papers.

Citrix MetaFrame is an add-on component to Terminal Server that provides benefits to both the network administrator and Sage SalesLogix users. It extends Terminal Server by providing user access to business-critical applications, regardless of connection, location, or devices. Citrix MetaFrame incorporates the Citrix Independent Computing Architecture

(ICA®), an industry standard for server-based computing. Terminal Server supports all types of Windows platforms. Citrix MetaFrame enhances this capability by also supporting non-

Windows devices, such as MS-DOS terminals, UNIX workstations, Macintosh computers, Java applications, and others. Users of both Windows and non-Windows platforms obtain a seamless integration with Sage SalesLogix regardless of the user’s hardware, operating system, or network connection to the main office.

This is especially true for Remote users who experience Network-like performance when using Sage SalesLogix on a Terminal Server with Citrix MetaFrame. Even in locations where bandwidth is less than optimal and network traffic is heavy, Remote users run significantly faster with MetaFrame. This is because Citrix MetaFrame is designed for low bandwidth connections.

In addition, Sage SalesLogix can be supported and managed from the main office, eliminating the need for remote administration. Even network users can gain performance increases with Citrix MetaFrame.

Another benefit of Citrix MetaFrame is that Remote users have complete access to local system resources. For example, they can print locally, have access to local files and programs, and copy/cut/paste between local and remote applications, preserving rich text format (.rtf). This is all possible even though users are running Sage SalesLogix remotely from the server.

Word Processing and synchronization in Sage SalesLogix will only operate under Citrix

MetaFrame if your company is a pure Citrix user. That is to say, all applications are installed on Citrix and none on the client computer.

72 Sage SalesLogix Planning Guide v7.5

Appendix C

Planning Checklist

This Planning Checklist outlines the tasks you must complete to plan your Sage SalesLogix implementation. These tasks are designed to help you organize and make decisions regarding your implementation.

If you are implementing Sage SalesLogix for the first time, be sure to read each chapter in this guide thoroughly and ensure you have completed the necessary steps.

Task Description For more information, see...

Page 3

1 Determine project requirements.

2 Identify your Implementation Manager or System

Administrator.

Page 4

Record the following information for each person involved in your implementation:

Name:

Company:

Phone:

E-mail:

Fax:

Role:

Responsible for:

3 Identify your IS Administrator.

Page 5

Record the following information for this role:

Name:

Company:

Phone:

E-mail:

Fax:

Role:

Responsible for:

4 For Web installations, identify your Webmaster.

Record the following information for this role:

Name:

Company:

Phone:

E-mail:

Fax:

Role:

Responsible for:

Page 5

Sage SalesLogix Planning Guide v7.5

Planning Checklist

Task Description For more information, see...

Page 5

5 Identify your Database Administrator.

Record the following information for this role:

Name:

Company:

Phone:

E-mail:

Fax:

Role:

Responsible for:

6 Identify your Customization Developer.

Record the following information for this role:

Name:

Company:

Phone:

E-mail:

Fax:

Role:

Responsible for:

7 Identify your Review Team.

Page 5

Record the following information for each person on this team:

Name:

Department:

Title:

Phone:

E-mail:

Fax:

8 Select a Pilot group.

Page 6

Record the following information for each person on this team:

Name:

Department:

Title:

Phone:

E-mail:

Fax:

9 Set an implementation schedule.

Plan for the following phases in your schedule:

• Planning

• Development

• Roll-out

• Training

• Review

Page 6

74 Sage SalesLogix Planning Guide v7.5

Planning Checklist

Task Description For more information, see...

Page 7

10 Develop a prototype.

11 Order and install hardware.

12 Determine who will provide administrator and end-user training.

Note: When making training decisions, consider where the training will be held.

Page 7

Page 8

13 Understand the total system cost of your Sage SalesLogix implementation and include this information in your planning and budgeting.

Page 8

14 Identify the Sage SalesLogix components that you will use in your company.

Page 10

When identifying the appropriate components, you should:

•

Understand the required core components ( page 10

•

Understand the required administrative components ( page 10

•

Understand the server components ( page 13

• Select the appropriate Client components (

page 15 ).

• If your installation includes Remote Offices and Remote users, select the appropriate remote components (

page 20 ).

15 Understand the software that Sage SalesLogix supports and identify if any upgrades or changes are necessary.

Page 21

16 Select an installation type.

17 Identify which Sage SalesLogix license(s) you need to purchase.

Page 22

Page 27

18 If you have third-party applications that will access your Sage

SalesLogix database, determine their security access.

Page 33

19 Determine what level of account access you want to implement in your company.

Page 36

20 Identify the departments you need to create for your company and the users assigned to those departments.

Page 37

Record the following information for each department:

Department Name:

Department Members:

Sage SalesLogix Planning Guide v7.5

Planning Checklist

Task Description For more information, see...

Page 37

21 Identify your teams and the team members.

Record the following information for each team:

Team Name:

Team Owner:

Team Members:

22 Determine if you need to implement advanced security profiles

(field-level security).

Page 37

23 Determine if users will have access to another user’s calendar

(calendar security).

Page 38

Record which users have access to another user’s calendar, the calendars they have access to, and the level of access for each calendar.

For example:

User: Lee Hogan

Calendars that can be accessed: Joan Smith, Tom Dale

Level of access: Joan Smith (read-only), Tom Dale (read/write)

24 If your installation includes Web components, understand the security differences been Sage SalesLogix Network and Web products.

Page 38

25 If you are implementing Administrative Roles, identify the roles you need to create and the user assigned to each role.

Page 39

Record the following for each administrative role:

Administrative Role Name:

Functions enabled for this role:

User assigned to this role:

26 Determine if you want your users to log on to Sage SalesLogix using Windows Authentication.

Note Windows authentication is enabled by default.

Page 39

27 Determine the RDBMS for your main office and Remotes.

28 Plan your database backup schedule.

Page 41

Page 43

76 Sage SalesLogix Planning Guide v7.5

Planning Checklist

Task Description For more information, see...

Page 45

29 Determine your hardware configuration for Sage SalesLogix components:

Use the Compatibility Checklist along with the information in

Chapter 6,

“Understanding Sage SalesLogix Hardware”

, to determine hardware for the following:

• Database Server

• Administrative Workstation

• Client computers

• Sage SalesLogix Server

• SpeedSearch Server

• Remote Office Server

30 Estimate the size of your main office database.

31 Determine your Synchronization Server hardware and disk storage space.

Page 45

Page 50

Synchronization Tasks

32 Determine your synchronization method.

33 Determine the location of your main office synchronization folders.

Page 53

Page 55

34 Determine the location of your Remote Office synchronization folders.

Page 58

Page 60

35 Determine if your company needs multiple synchronization servers.

36 Identify a synchronization server schedule.

Page 61

Page 62

37 Determine how your company will handle subscription for

Remote users.

38 Identify the necessary subscription rules for your company.

Page 62

Sage SalesLogix Planning Guide v7.5

Planning Checklist

78 Sage SalesLogix Planning Guide v7.5

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.

Active Users The number of users accessing the database at any one time. The number of active users affects the relational database management system (RDBMS) and server hardware you choose.

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.

Dashboards Allow 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.

Database Server Manages the database for the main office. The relational database management system (RDBMS) and its related data, log, and support files are located on this server.

Defect A record describing a problem in a product or process, or a feature request for a product or process.

Sage SalesLogix Planning Guide v7.5

Glossary

Disconnected Web Client Remote users that keep a subset of the main database on their computers (such as a laptop) and use synchronization to transfer changes between their system and the main office. Disconnected Web Client users make changes to their local database using the Web Client.

Documents Folder A folder containing files that are attached to an account, contact, opportunity, or ticket. For example, a Word letter.

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.

Expression A simple language that allows many processor parameters to be dynamically generated.

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.

Index A database index points to records within a Sage SalesLogix table, based on key values. Indexes can enforce uniqueness on the rows in a table.

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.

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.

80 Sage SalesLogix Planning Guide v7.5

Glossary

Process Orchestration Allows you to create and configure process definitions and manage them with the Process Orchestration Host. Processes can be created for any entity, and any entity can be associated to multiple processes.

Processes A plugin that represents a series of tasks executed in a specific sequence over a set time period. Processes are used to perform repetitive tasks, implement a sales process, or provide an automated way of following up with customers. The Web components may only schedule processes and change process status.

Processor A source or transformation of data that can be linked to other processors.

Project A group of Web packages or plugins that are grouped together for easy retrieval and use.

Queue Files Queue files are synchronization transaction files that are created with every database commit and typically contain a small amount of data.

Quick Forms The Quick Forms designer simplifies customization by using entity-bound forms referred to as quick forms. Quick forms are created for entities, such as accounts or contacts, within the Project Explorer. Quick form properties and data bindings are set by changing property values or by adding pre-defined form elements, allowing for codeless customization.

Relational Database Management System (RDBMS) An engine and method of managing a database consisting of tables (rows and columns) and the relationships between those tables.

Remote Office A group of users that access a single Remote Office database directly. Unlike

Remote users, Remote Office users do not synchronize with the database at the main office.

Instead, the remote office regularly synchronizes with the database at the main office.

Sage SalesLogix Client An installation of the Sage SalesLogix Client where the user is directly connected to a network database to access and manage customer accounts, contacts, tickets, defects, activities, and related information.

Sage SalesLogix OLE DB Provider A client-side component that handles all database access and applies security.

Sage SalesLogix Personal Web Server Hosts the Sage SalesLogix portals on the Remote computer. The Sage SalesLogix Personal Web Server functions as a personal Web server for disconnected Web Clients and Web Remote Offices.

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.

SData Using SData features, you can expose an entity or a business rule to RESTful-based

Web services, allowing you to integrate and enhance Sage SalesLogix data with data from outside the application.

Security Determines what a user can access in Sage SalesLogix. Security is controlled by a combination of account ownership, management hierarchy, and level of access rights to information.

Security Profile Determines each user’s access to information, tables and fields, and functionality.

Site Code A unique identification code assigned to each Network user, Remote user,

Synchronization Server, and Remote Office that represents the user or component.

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.

Sage SalesLogix Planning Guide v7.5

Glossary

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), FTP, or

HTTP.

Synchronization (Sync) Server The application that runs synchronization and agents. It can also refer to the hardware on which the Sync Server application resides.

Synchronization Service A Windows service that communicates with the Synchronization

Server(s) and SyncServices.cfg file for scheduling.

Team A group of users who have access to the same accounts. Members of the same team may have different security access to data.

Ticket A record of a call relating to a question or problem experienced by the customer.

Transaction Exchange Files (TEFs) Files that are transferred between Remote users and

Remote Offices, and the main office to synchronize data.

Web Remote Office A group of Remote users that access a single Remote Office database using the Web Client.

Workflow A sequence of operations that include processes.

WGLogs A folder in which Network users place transaction files as changes are made to the database.

82 Sage SalesLogix Planning Guide v7.5

Index

Symbols

.NET Extensions

defined

Account ownership

security

Accounts, number of

ACT! by Sage, importing from

Active users, number of

Administrative roles

Intellisync

Librarian

Sales

Administrative Workstation defined

hardware configuration

Administrator

ADO

Advanced Outlook Integration

Agents

Application Architect

defined

Archives folder

–

Backups

Basic scripts

Budgeting considerations

Bundles, defined

Business partners, Sage SalesLogix

Cache hit ratio

Calendar security

Citrix MetaFrame

Communications software, e-mail

Components, See Sage SalesLogix

Components

Concurrent users

Concurrent users, number of

Configuration minimum for database server

speedsearch server

recommended for database server

Configuration (continued) recommended for express installation Host machine

speedsearch server

Configuring synchronization client

Conflict resolution and Intellisync

ConfTran.stm file

Connection Pooling

Consultants

Contacts

Contract

Cost considerations

CPU database server

Remote Office server

Sync Client Remote Office

Crystal Reports

Customer Service

Customizing Sage SalesLogix

Intellisync

menus and toolbars

plugins

VBScripts

Dashboards

Data Transfer, direction

Database Manager

Database Server as file server

components

CPU

folder structure

hardware configuration

RAM

Remote Office

selecting

Database server

Databases administrator for

backups

supported

Defect

Disconnected Web Client

defined

Disk contention

Disk storage

Remote Office server

synchronization server

Documentation

Sage SalesLogix Planning Guide v7.5

Index

Documents folder

E-mail

Everyone account ownership

FailedTrans folder

Fax

Field-level security, defined

File server

File transfer protocol (FTP)

Folders archives

–

documents

FailedTrans

, infiles

library

logging

on file server

outfiles

PortalDeployments

, shared sync

WGLogs

Font settings

Forced subscription

FTP synchronization

GoldMine, importing from

Group Copy

Hardware configuration administrative workstation

database server

Hardware, planning for

Host synchronization

HTTP synchronization

IIS

Implementation checklist

planning

project requirements

Implementation team

Administrator

database administrator

implementation manager

IS administrator

pilot group

Import Wizard

Importing data

common file types

from legacy systems

into Sage SalesLogix

84 Sage SalesLogix Planning Guide v7.5

preparation

Importing data (continued) scheduling

Individual security profiles

Infiles folder

Installation types

automated

express

standard

Integrity Checker

Intellisync conflict resolution

customizing

overview

requirements

IP addresses

Join, defined

LeadCapture

Licenses

Advanced

Concurrent User

Customer portal

External Access

LeadCapture

Named

Add-On User

User

Web User

Network User

Oracle support

Premier

Remote Office Server

Remote user

Sage SalesLogix

SpeedSearch Server

Standard

Synchronization Server

WebViewer

Logging on, using Windows authentication

Long file names

Mail client, Sage SalesLogix

Main database, synchronizing

Marketing

Microsoft

.NET Framework

Developer’s Network

Excel

IIS

licenses

MDAC

Office

Microsoft 35 (continued)

RAS

required for Sage SalesLogix

SQL Server

importing data

selecting

Windows Installer

Word

Microsoft DAC

Modem for Remote clients

Monitor Console

NetBIOS

Network experience for IS contact

mixed

synchronization

Network client

Network protocols

Network synchronization

Network, sync profile

OLE DB, Connection Pooling

Operating System and Sage SalesLogix security

Operating systems supported

Opportunities

Oracle importing data

selecting as RDBMS

Outfiles folder

Outlook Integration

Pilot group

Planning

checklist

Plugins

process

scripts, Basic

scripts, SQL

PortalDeployments folder

Processes

defined

Professional Services Group

Profiler

Profiles, security individual

team

Project planning

Query Builder

QUEUEFiles folder

Index

RAM database server

Remote Office server

speedsearch server

SQL Express

synchronization server

RAS synchronization

Relational database management system

(RDBMS)

backups

considerations

Microsoft SQL Server

on database server

Oracle

planning for

RemOfficeSyncLogs folder

Remote clients defined

modem

subscription

synchronization folder structure

–

synchronizing databases

Remote components

Remote Office defined

Remote Office server

CPU

disk storage

RAM

Remote Office sync client, configuring

Remote Offices

database server

subscription

synchronization

Web

Resynchronize Remote Database

Rules, subscription

Sage

Sage SalesLogix administrator

budgeting for

business partners

components

Administrator

Architect

client components

Customer Service

Marketing

Remote

Sales Processes

Support

synchronization

utilities

customizing

Sage SalesLogix Planning Guide v7.5

Index

Sage SalesLogix (continued) database

documentation

file server

general cost of

importing data

–

licenses

Professional Services Group

Query Builder

security

server components

training

Sage SalesLogix OLE DB Provider

Sage SalesLogix Personal Web Server

Sage SalesLogix Remote Client defined

Sage SalesLogix Server defined

Sales library folder

teams

Sales Processes

Scheduler, third party

Scheduling the sync server

Screen Resolution

Scripts

Basic

SQL

Search functionality

SpeedSearch

Web Client with Customer Service

Web Customer Portal

Security

and account ownership

and the Windows operating system

calendar

in the Web products

profile

profiles

team profiles

Server components

Shared sync folders

Site codes

SLXService user

SpeedSearch

Client

license

Server

Service

SQL Express

RAM

SQL scripts

SQL Server importing data

selecting

SQL Server Express

Subscription

and Remote Offices

86 Sage SalesLogix Planning Guide v7.5

and security

Subscription 82 (continued) defined

forced

rules

unsubscription rules

Support

Sync Logs folder

size of

Sync transfer profile network

Synchronization automatic sync

folder structure

folders for Remote clients

for Remote Offices

on Host

overview

Host

methods of

overview

RAS

Remote Office

scheduling the server

server configuration

site codes

sync transfer profiles

transfer profiles

Synchronization Client

Synchronization server configuring

defined

disk storage

logging folders

processing

scheduling

Synchronization Service defined

Synchronizing main database

Remote client databases

Tasks folder

TCP/IP

Team account ownership

owner profiles

security profiles

Teams

TEFs, See Transaction Exchange Files

Terminal Server

Third-party software

Ticket

Training

Transaction Exchange Files

Transaction Exchange Files (continued) defined

logged

used with TrnAnalyzer

TrnAnalyzer

TrnViewer

Users active

concurrent

training

Utilities

Virtual Private Network

Web

Web browser

Web Client

Customer Service, search functionality

Web Customer Portal defined

search functionalty

Web Host

Web Remote Office

Web Reporting Server

WebDLL user

WebViewer

WGLogs folder

Windows administrative users

authentication

logging on to Sage SalesLogix

NT networks

WINS servers

WriteCache files

Index

Sage SalesLogix Planning Guide v7.5

Index

88 Sage SalesLogix Planning Guide v7.5

Sage SalesLogix Planning Guide

Sage SalesLogix Planning Guide

Contents

Introduction

About This Guide

What You Need to Know

Related Documentation

Chapter 1

Planning Your Implementation

Defining the Implementation Plan

Determining Project Requirements

Determining the Components of Your Implementation

Identifying Your Internal Implementation Team

Implementation Manager or System Administrator

Information Systems (IS) Administrator

Webmaster (for Web installations only)

Database Administrator (DBA)

Customization Developer

Review Team

Pilot Group

Other Resources

Setting an Implementation Schedule

Planning Phase

Development Phase

Rollout Phase

Training Phase

Review Phase

Developing a Prototype

Ordering and Installing Hardware

Importing Data from Legacy Systems

Training Administrators and Users

Understanding System Costs

Chapter 2

Understanding Sage SalesLogix Components

Sage SalesLogix Core Components

Sage SalesLogix Database

Sage SalesLogix Server and Sage SalesLogix OLE DB Provider

Sage SalesLogix Logging Folders

Sage SalesLogix Administrative Components

Administrator

Architect

Application Architect

Process Orchestration

SData

.NET Extensions

Sage SalesLogix Utilities

SpeedSearch

Web SpeedSearch

SpeedSearch Service

Sage SalesLogix Server Components

Synchronization Server

Synchronization Service

Web Host

Web Reporting

Sage SalesLogix Personal Web Server

Sage SalesLogix Client Components

Sage SalesLogix Client

Customer Service and Support Features

Sage SalesLogix Marketing

Sales Processes

Dashboards

Mail Client

Sage SalesLogix Remote Client

Web Client Interfaces

Web Client

Disconnected Web Client

WebViewer

Web Customer Portal

Lead Capture

SpeedSearch Client

Synchronization Client

Sage SalesLogix Mobile

E-Mail Integration Components

Sage SalesLogix Exchange Link

Intellisync for SalesLogix

Direction of Data Transfer

Sage SalesLogix Activities, Contacts, and Events

Conflict Resolution

Customization

Intellisync for SalesLogix Requirements