SyteLine ERP. Installation Guide. MAPICS, Inc Windward Concourse Parkway Suite 100 Alpharetta, GA Version 7.03.

Transcription

1 SyteLine ERP Installation Guide Version MAPICS, Inc Windward Concourse Parkway Suite 100 Alpharetta, GA

2 Installation Guide Copyright MAPICS, Inc All Rights Reserved November 2004 Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS , and Rights in Data-General at FAR , as applicable. Name of Contractor: MAPICS, Inc., 1000 Windward Concourse Parkway, Suite 100, Alpharetta, GA MAPICS is a trademark of MAPICS Solutions Group, Inc. All other product names used in this manual are trademarks, registered trademarks, or trade names of their respective companies.

3 Contents Introduction Recommended Hardware Recommended Setup Order of Events Recommended Machines Operating Systems MAPICS Tools Data Collection Client Workflow Automation Microsoft Outlook Service Packs Uninstalling SyteLine ERP Setting Up the Database Server Requirements Install Components on the Database Server Configure the Database Server Development Environment Create Separate Databases Setting up a Microsoft Visual SourceSafe Environment for Object Studio Setting Up the Utility Server Requirements Install Components on the Utility Server Configure the Utility Server Final Data Collection Steps Set up the DC Client Directory and Data Collection Parameters Set Up the Background Processor Run Test Transactions Setup a Utility Server to send Notifications for Reports Troubleshooting Install Crystal Reports Install All Features Install Crystal Reports Service Pack and Hot Fixes Setting Up a Client Workstation Requirements Upgrade Message Installation Options Configure the Client Install End User Client Configure End User Client Install Administrative Client MAPICS, Inc. SyteLine ERP 7 Installation Guide i

4 Contents Configure Administrative Client Configure Permissions for Resource Gantt Charts Run SyteLine ERP Setting Up Workflow Automation Prerequisites Setup the Exchange Server Machine Run the SyteLine Configuration Wizard Setup the Utility Server Machine Create Public Folders within Outlook Install Lexign Flow Server Configure Lexign Flow Server Activate Server Scripting Create the Inbox Agent Setup the Administrative Client Machine Install the Sample Outlook Forms Create the Template Set the Path to the Workflow Test Template Set the Address Within SyteLine ERP Register the Workflow Template Restart the SyteLine Session Setting Up a Multi-Site Environment Configure the Database Server Post Installation Setup Create a Multi-site Test Environment Setting Up a Developer Environment Install SyteLine ERP Developer on Database Server Configure SyteLine ERP Developer on Database Server Install SyteLine ERP Developer on a Client Configure SyteLine ERP Developer on a Client Setting Up the Planning Server Requirements Install the Planning Server Components Creating and Starting ERDB Databases Allocating Memory for the Database Generate the Depth and Width Requirements Enter the Depth and Width Settings Fine-Tuning the Memory Allocation for Depth Additional Sizing Guidelines Setting Up the Web Server Requirements Data Collection Setup Install the Web Server Components ii SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

5 Contents Configure the Web Server Components Creating Additional Analyzer Start-Up Pages Install and Configure Analyzer Clients Installing the Analyzer Client Configuring the Analyzer Client Configure Permissions for the Gantt Chart Enter SyteLine Planning Parameters Test the Analyzer Connection Troubleshooting the Analyzer Connecting to Web-Based Data Collection Upgrading a SyteLine Application Database Requirements Service Packs Multiple Service Pack Installs Apply Service Pack Apply Changes to Objects Database Run the Database Upgrade Utility FormSync Post Upgrade Steps Troubleshooting Converting From SyteLine 5 or SyteLine 6 (Single Site) Requirements Conversion Steps (Single Site) Start the SyteLine Database Migration (Optional) Run the Overstuffing Detection Program (Optional) Run the Foreign-Key Validation Program (Optional) Run the Null Validation Program (Optional) Run the Check-Constraint Program Log Out of SyteLine ERP on All Clients Shut Down Servers Backup Databases Unload Data from the Database To Be Converted Run uet-dump.p. (Only if User Extended Tables are Used) Create a Report of User-Defined Field Usage (Optional) Create a SyteLine 7 Application Database for Each Site Select the Phases to Run on the Phases Tab Phases Make Selections on the Source Tab Make Selections on the Destination Tab Make Selections on the Options tab Click the Run Conversion Button Click Run Conversion Button for Additional Phases or Table Ranges Perform Post Conversion Tasks Post-Conversion Tasks MAPICS, Inc. SyteLine ERP 7 Installation Guide iii

6 Contents Outputs Disk Usage Troubleshooting Resolving Foreign-Key Conflicts Relative Duration Re-entrance Parallel Execution Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Requirements Conversion Steps (Multi-Site) Start the SyteLine Database Migration (Optional) Run the Overstuffing Detection Program (Optional) Run the Foreign-Key Validation Program (Optional) Run the Null Validation Program (Optional) Run the Check-Constraint Program Log out of SyteLine on all clients Shut Down Servers Backup Databases Unload Data from the Database To Be Converted Run uet-dump.p. (Only if User Extended Tables are Used) Create a Report of User-Defined Field Usage (Optional) Create a SyteLine 7 Application Database for Each Site Load Data From Global Database Make Selection on the Overview Tab Select the Phases to Run on the Phases Tab Make Selections on the Source Tab Make Selections on the Destination Tab Make Selections on the Options tab Click the Run Conversion Button Repeat Previous 6 Steps if Necessary Load Data From Entity Database(s) Make Selection on the Overview Tab Select the Phases to Run on the Phases Tab Make Selections on the Source Tab Make Selections on the Destination Tab Make Selections on the Options tab Click the Run Conversion Button Repeat Previous 5 Steps if Necessary Perform Post Conversion Tasks Repeat for additional Entity database(s) Load the Data From Site Database(s) Make Selection on the Overview Tab Make Selections on the Source Tab Make Selections on the Destination Tab iv SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

7 Contents Make Selections on the Options tab Click the Run Conversion Button Click Run Conversion Button for Additional Phases or Table Ranges Perform Post Conversion Tasks Repeat Load the Data From Site Database(s) steps for Additional Site Databases Post-Conversion Tasks Outputs Disk Usage Troubleshooting Resolving Foreign-Key Conflicts Relative Duration Re-entrance Parallel Execution Uninstalling SyteLine ERP Setting Up the Online Help A-1 Installing Help to a Central Location... A-1 Troubleshooting Online Help Access... A-6 Help doesn t display... A-6 Help window appears but topics display blank... A-9 Topics display with an error message... A-10 Links within the help do not work... A-11 Add Note or Open Form buttons do not work... A-11 Installing the Fax Service B-1 Replication Setup Checklist C-1 For Your Reference...C-1 Replication Categories and Replication Rules Forms...C-1 Set Up the Database Server...C-2 Run the SyteLine Configuration Wizard on the Database Server...C-2 Set Up the Web Server...C-2 Make Sure Services are Started...C-2 Open Replication Management Form...C-3 Replication Setup Complete...C-5 Troubleshooting...C-5 Setting Up an End User Client for HTTP Access D-1 Web Server Setup...D-1 Client Installation and Setup...D-1 Run SyteLine ERP...D-2 MAPICS.NET Web Service Test Utility E-1 Starting the Utility... E-1 Connecting (Logging In) to the Web Service... E MAPICS, Inc. SyteLine ERP 7 Installation Guide v

8 Contents Loading a Data Set...E-3 Viewing Results...E-4 Index INDEX-1 vi SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

9 1 Introduction After installing all the pieces of your system, you MUST apply the latest service pack to ensure everything works properly. See Service Packs on page 10-2 for information on how to download and apply the service packs. This chapter provides an introduction to the SyteLine ERP 7 Installation Guide. It contains the following topics: Recommended Hardware Recommended Setup Online Help SyteLine Components (MAPICS Tools) Data Collection Client Microsoft Outlook Service Packs Uninstalling SyteLine ERP. Recommended Hardware You should have appropriately powerful clients and servers when running SyteLine ERP software. The recommended minimum requirements are listed in the Guide to Technology found on MAPICS s website here - support.mapics.com/. Once there, perform the following steps: 1. Login. 2. Select the radio button to Load the SyteLine menu. 3. Click OK. 4. Click the link for Product documentation. 5. Follow the links to the version of the Guide to Technology you want MAPICS, Inc. SyteLine ERP 7 Installation Guide 1-1

10 Introduction Recommended Setup There are many pieces to install described in this guide. Depending on your company s needs, you may or may not install every piece described. The chapters are listed in the order in which the pieces should be installed. The order is determined mainly because one piece may rely on the fact that another piece is already installed. For example, during a client install, you are required to point to the utility server; therefore, you need to set up the utility server prior to installing clients. If you have purchased SyteLine Configuration, see the SyteLine Configuration Installation Guide for installation and setup instructions BEFORE installing SyteLine ERP. If you have purchased any other product that interfaces with SyteLine ERP, see the installation guides for those products for direction BEFORE installing SyteLine ERP. Order of Events For a SyteLine ERP installation, the order of events is as follows: 1. Database Server 2. Utility Server 3. Client (End User or Administrative) 4. Exchange Server 5. Developer Code (if applicable) Developer code comes on a separate CD from SyteLine ERP. Install the code from this CD after you have installed SyteLine ERP. See Setting Up a Developer Environment on page 7-1 for information on how to set up a developer environment. 6. Planning Server 7. Web Server (if applicable) 8. Install Latest Service Pack After installing all the pieces of your system, you MUST apply the latest service pack to ensure everything works properly. See Service Packs on page 10-2 for information on how to download and apply the service packs. 1-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

11 Recommended Machines We recommend that you set up each of the following pieces on its own machine: Database Server Exchange Server Utility Server Web Server Planning Server Introduction You can put an end user or administrative client on a machine of its own or on any of the server machines listed above except for the database server. A developer client should go on an administrative client machine. Operating Systems We support Windows 2000 Server for use as servers in all cases and Windows Server 2003 for use as servers in some cases. We support Windows XP or Windows 2000 as clients. Use the chart below to see which piece of SyteLine ERP is appropriate for which Windows server: Windows Server 2003 Windows 2000 Server Database Server Yes Yes Utility Server Yes Yes Planning Server Yes Yes Terminal Server Yes Yes (Unless you are using SyteLine Configuration; then it has to be Windows 2000 Server) Web Server Yes Yes Exchange Server No Yes There are some additional setup procedures necessary for some of the servers using Windows Server That information is given at the beginning of each chapter when necessary MAPICS, Inc. SyteLine ERP 7 Installation Guide 1-3

12 Introduction Online Help SyteLine ERP online help gives you instant access to procedures and information about forms and fields. You can access Help from SyteLine ERP forms, from other topics within Help, or from the search (index) function. Select Help>Contents and Index from the SyteLine ERP title bar to open the Help, or use the F1 key to get help on any form or field. Developer-Level Help To access the help for developers, select Help>Customizing Forms. MAPICS Tools Depending on what type of install you are performing, certain development tools are installed. These tools are located in the installation folder where applicable; usually C:\Program Files\MAPICS\SyteLine. All of them have their own online help. Client Configuration Manager (WinStudioConfig.exe) - Use the Client Configuration Manager to configure client workstations. You can specify the application database, forms database, and templates database to be used by a WinStudio run-time user or by a developer customizing forms. You can also set the common middleware login (or the password for the WinStudio administrator sa login). Client Configuration Manager is found on the administrative and developer client. FormSync (Formsync.exe) - Use FormSync to reconcile differences between two copies of the forms database. FormSync is found on the utility server and administrative client machines. WinStudio App ID Editor (WinStudioAppIDEditor.exe) - Use the Application ID Editor to create, edit, and export WinStudio application IDs which encapsulate various application-specific and client-specific configuration settings. WinStudio App ID Editor is found on the administrative client. Configuration Manager (mongooseconfig.exe) - Use Configuration Manager to set up a development environment, including creating the required databases and establishing logins for developers. Configuration Manager is found on the developer client. FormControl (FormControl.exe) - FormControl manages version control for forms and related form objects. FormControl can be used in developing new applications; we do not recommend that you use it with existing MAPICS applications such as SyteLine ERP. Future upgrades to the MAPICS application cannot be reliably synchronized with your forms database through FormSync. FormControl is found on developer clients. 1-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

13 Introduction Tree (Tree.exe) - Tree allows you to build and view tree hierarchies which show cross-references between various types of programming objects in the presentation layer, the middleware layer, and the database layer of a WinStudio application. Tree is found on developer clients. Form Links (formlinks.exe) - Form Links populates the development application database with information used by Tree. Form Links is found on the developer client. ObjectStudio (ObjectStudio.exe) - Use ObjectStudio to create and build IDOs for the middleware. ObjectStudio supports a multi-developer environment through integration with Visual SourceSafe. ObjectStudio is found on the developer client. Table Utility (MGTableInit.exe) - Use the Table Utility to create SQL Server tables with the required columns and triggers or to add these requirements to existing tables. Table Utility is found on the developer client. Data Collection Client If you are a data collection user, you may want to use a Data Collection (DC) Client when you set up your SyteLine 7 ERP system, depending on your specific system and hardware requirements. Your system configuration will depend on several factors, including the number of readers and the data collection environments (RF, serial, or network) used. See your SyteLine consultant for advice for your specific configuration needs. If you are using a Data Collection Client, install the following components on it from the Custom Setup screen: Data Collection Web server components SyteLine Client components. Workflow Automation Note: We recommend you set up a DC Client machine if you are using TRAKKER Antares store and forward data collection. See the TRAKKER Antares Reader Installation Guide for more information. After you install the Data Collection Client, run the SyteLine Configuration Wizard (Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard) to configure the client. Before installing Workflow Automation, the following tasks must be completed: 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 1-5

14 Introduction The SyteLine database must be licensed. SyteLine replication must be configured. A dedicated instance of Exchange Server must be installed and integrated with your corporate server. This instance of Exchange Server is typically installed on the SyteLine database server. The SL_Internal user must be a Super User. Two mailbox accounts must be created within Outlook (or Active Directory users and Computers if you are running Exchange 2000 with Active Directory). These accounts should be named SyteLine and Workflow. Microsoft Outlook Service Packs If you apply a Microsoft Security Outlook Service Pack, of reports and report notification fails. To correct this problem, perform the following tasks: 1. Go to Microsoft s web site here appndx/toolbox.htm#secupd and download admpack.exe. 2. Run admpack.exe. You are asked to choose a directory for the files. Do so. 3. Once the files are extracted, read readme.txt. 4. Follow the instructions in the readme to install the form on an Exchange administrative machine. 5. Create and publish the form. 6. Use the newly published form to modify the Exchange mail account for only the USER ACCOUNT that will be used for the mail profile on the Utility Server. 7. Change only the following settings on the PROGRAMMATIC SETTINGS TAB (leave the other TABS to their default values) to "Automatically approve" and leave the other default settings to "Prompt User": When sending items via Simple MAPI: When resolving names via Simple MAPI: When opening messages via Simple MAPI: 8. Modify the registry of the Utility Server to have a new key to check the security settings on the exchange server. Create the following DWORD registry key: HKCU\SW\Policies\Microsoft\Security\CheckAdminSettings 1-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

15 Introduction The value for this new DWORD key should be "1" for Office 2000 or "2" for Office XP. This is the version of Office/Outlook that you have installed on the Utility Server. 9. Once the above steps are complete, see Setup a Utility Server to send E- mail Notifications for Reports on page 3-30 for further instructions. Uninstalling SyteLine ERP If you are upgrading your system from one version of SyteLine ERP 7 to another (for example from SyteLine ERP 7.02 to SyteLine ERP 7.03) you MUST first uninstall the old version before installing the new version. This is true for all pieces of your system; the database server, utility server, all clients, planning server, web server, and exchange components. See Chapter 13, Uninstalling SyteLine ERP" for uninstall instructions MAPICS, Inc. SyteLine ERP 7 Installation Guide 1-7

16 Introduction 1-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

17 2 Setting Up the Database Server The steps in this chapter detail how to set up the database server in a single site environment. Requirements If you want to set up a multi-site environment, complete the steps in this chapter first and then see Setting Up a Multi-Site Environment on page 6-1. SQL 2000 Server is already installed and configured on the database server machine. If your database server is on a Windows Server 2003 machine, you MUST enable Network COM+ and Network DTC Access. If you have applied SyteLine ERP Service Pack 5 or greater, you must set some default SQL Server settings on the database server. These settings can be set either before or after a SyteLine ERP installation. Within SQL Server Enterprise Manager, open the Properties dialog box for the server (NOT the database). On the Connections tab, select the check box for the following items: ANSI warning, ANSI padding, ANSI nulls, Arithmetic abort, Quoted identifier. Install Components on the Database Server 1. Insert the SyteLine ERP CD into the CD-ROM drive of the database server machine MAPICS, Inc. SyteLine ERP 7 Installation Guide 2-1

18 Setting Up the Database Server 2. After a few seconds, the initial SyteLine ERP install screen appears. If it doesn t appear, access the CD-ROM drive and double click Setup. 2-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

19 Setting Up the Database Server 3. Select Database Server as the configuration type. The Install SyteLine ERP Database Migration button appears and the Select a Database Type check box list appears. 4. From the Select a Database Type check box list, select or clear Database Upgrade. Database must be selected. If you select Database Upgrade, a utility is installed to upgrade your database from a previous version. The utility upgrades a SyteLine database within a major point release (7.02 to 7.03 for example). It does not upgrade from version 6 or earlier. See Chapter 10, Upgrading a SyteLine Application Database" for more information about this utility. 5. Select one of the two button choices on this screen: If you click the Install SyteLine ERP Database Migration button, you must do so BEFORE you install SyteLine ERP. Run the SyteLine Configuration Wizard after you have installed both pieces. Install SyteLine ERP Click this button to install SyteLine ERP and its databases on the database server MAPICS, Inc. SyteLine ERP 7 Installation Guide 2-3

20 Setting Up the Database Server Install SyteLine ERP Database Migration Click this button to install all the necessary components to convert from an earlier version of SyteLine ERP to SyteLine ERP 7. Follow the instructions in the wizard to complete the install. If you are not converting from an earlier version of SyteLine ERP, do not click this button. For more information on conversion, see the appropriate conversion chapter (multi-site or single site) in this guide. 6. Click the Install SyteLine ERP 7.03 button. The Welcome screen appears. 7. Click Next. The Custom Setup screen appears. 8. With Database Server expanded, deselect SyteLine Configuration Database if you did not purchase SyteLine Configuration. If you need to install SyteLine Configuration, see the SyteLine Configuration Installation Guide for installation and setup instructions BEFORE installing SyteLine ERP. 9. Click Next. 10. Click Install. 11. Once the installation process is complete, click Finish. 2-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

21 Configure the Database Server Setting Up the Database Server Once the installation completes, run the SyteLine Configuration Wizard to create the SyteLine ERP database environment. 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard to create the SyteLine application, forms, and templates databases. The Introduction screen appears. 2. Select Setup a new SyteLine Database Environment. You would choose Configure this computer to use a SyteLine Database Environment only if you have installed pieces other than SyteLine ERP that you need to configure MAPICS, Inc. SyteLine ERP 7 Installation Guide 2-5

22 Setting Up the Database Server 3. Click Next. The Choose Database Setup Tasks screen appears. 4. On the Choose Database Setup Tasks screen, either accept the default values or clear SyteLine Templates Database if you do not wish to create a templates database. Select Link Multi-Site Databases if you want to set up a multi-site environment. For the purposes of this chapter, leave it unchecked. If you want to set up a multi-site environment, see Setting Up a Multi-Site Environment on page 6-1. The Environment Creation Tasks are defined as follows: SyteLine Application Database - This is where your company data will be stored. This database is a requirement. SyteLine Forms Database - The forms database holds all of the information about each form in SyteLine ERP. For example, components such as text boxes, labels, tabs, radio groups, buttons, and all of the associated properties (such as size, color, validation, events) are kept in the forms database. This database is a requirement. SyteLine Templates Database - This database is a central holding place for changed SyteLine default screens. This database is optional. 2-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

23 Setting Up the Database Server Link Multi-Site Databases - Select Link Multi-Site Databases if you want to set up a multi-site environment. If you want to set up a multisite environment, see Setting Up a Multi-Site Environment on page Select Next. The Temporary Folder Location for Database Creation screen appears. 6. Accept the default location for the temporary folder or click the browse button to specify a different location MAPICS, Inc. SyteLine ERP 7 Installation Guide 2-7

24 Setting Up the Database Server 7. Select Next. The Create Application Database screen appears. 8. Enter or update the following data: Server Name - This option is not updateable since databases can only be created on the local server. Database Name - Accept the default database name or enter a name for the SyteLine ERP application database that will be created. sa Logon - sa is defaulted here and you cannot change it. sa Password - Enter the SQL Server password. Data File Location - Accept the default path or browse to select the location for the application database data file. Log File Location - Accept the default path or browse to select the location for the application database log file. 2-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

25 Setting Up the Database Server 9. Click Next. The Select Application Database Type screen appears. 10. Select from among the following three options: Empty Database - Select this option only if you are upgrading from a previous version of SyteLine. If you need to choose this option, see the appropriate conversion chapter (multi-site or single site) in this manual. No instructions on conversion are given in this chapter. Initialized Database - Select this option to create a new SyteLine database. This creates an empty database which you will then need to populate. Demo Database - Select this option for demonstration or testing purposes. This option populates the database with demo data so you can test many of SyteLine s functions MAPICS, Inc. SyteLine ERP 7 Installation Guide 2-9

26 Setting Up the Database Server 11. Click Next. The Site Parameters for Application Database screen appears. 12. On the Site Parameters for Initialized Application Database screen, enter or update the following data: Site ID - Enter the Site ID. The ID is a shorter version of the Site Name (8 characters maximum). If you are integrating SyteLine with MAPICS CRM, do not enter a site ID with greater than 5 characters; note that for an empty or initialized database, the "Default" site has greater than 5 characters and will not work with CRM. For a demo database, the default Site Id is "Demo" and will work with CRM. Site Name - Enter the site name for the Application database environment being created. Site Description - Enter a description for the database environment being created. Site Group - Enter a group name for the environment being created. Site Currency Code - Accept the default value of USD or assign the appropriate currency code for the environment being created. Site Type - Accept the default value of Site. You would choose Entity if you were setting up an Entity database in a multi-site environment SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

27 Setting Up the Database Server 13. Click Next. The Create Forms Database screen appears. 14. Enter or update the following data for the forms database: Server Name - This option is not updateable since databases can only be created on the local server. Database Name - Accept the default forms database name or enter a name for the SyteLine demo forms database that will be created. sa Logon - sa is defaulted here and you cannot change it. sa Password - Enter the SQL Server password. Data File Location - Accept the default path or browse to select the location for the forms database data file. Log File Location - Accept the default path or browse to select the location for the forms database log file MAPICS, Inc. SyteLine ERP 7 Installation Guide 2-11

28 Setting Up the Database Server 15. Click Next. If you chose to set up a templates database, the Create Templates Database screen appears. 16. Enter or update the following data for the templates database: Server Name - This option is not updateable since databases can only be created on the local server. Database Name - Accept the default templates database name or enter a name for the SyteLine demo templates database that will be created. sa Logon - sa is defaulted here and you cannot change it. sa Password - Enter the SQL Server password. Data File Location - Accept the default path or browse to select the location for the templates database data file. Log File Location - Accept the default path or browse to select the location for the templates database log file. 17. Click Next. The Review Changes screen appears. 18. Verify that the information is correct, and click Commit. 19. Once the configuration is complete, click Finish SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

29 Development Environment Setting Up the Database Server Create Separate Databases If you purchase developer code and wish to do major customizations to existing forms or if you need to modify backend objects such as stored procedures, we recommend you set up a development environment. You will need to create separate forms and/or application databases for that purpose. Run the SyteLine Configuration Wizard again on the database server to create these databases. You can use FormSync to migrate form customizations from one forms database to another. Setting up a Microsoft Visual SourceSafe Environment for Object Studio If you plan to install developer code and you plan to use Microsoft Visual SourceSafe to manage your Object Studio development work, you need to do the following before setting up the development client machines: 1. Create a Visual SourceSafe Database. 2. Create a project named ObjectStudio. After you install the first developer client machine, add all of the files recursively that are in the MAPICS/SyteLine/ObjectStudioProjects folder (this will provide the baseline before you start customization). Your hierarchy in SourceSafe should look like $/ObjectStudio/SyteLineDev/. After you install each developer client, perform the following steps: 1. Select Start>Programs>MAPICS>Tools>Configuration Manager to launch the Configuration Manager. 2. Select the configuration you want to edit. 3. Click Edit. 4. Select the SourceSafe tab. 5. Click the Advanced button. 6. Enter "SyteLineDev" and then exit the Configuration Manager MAPICS, Inc. SyteLine ERP 7 Installation Guide 2-13

30 Setting Up the Database Server 2-14 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

31 3 Setting Up the Utility Server Requirements SQL 2000 Client Tools are already installed and configured on the utility server. You can install SQL 2000 Server, but it is not necessary. Microsoft Messaging Queue (MSMQ) is installed; or Message Queuing if on a Windows Server 2003 machine. If the utility server is on a Windows Server 2003 machine, you must configure the machine as an Application Server role. Install Components on the Utility Server 1. Insert the SyteLine ERP CD into the CD-ROM drive of the utility server machine MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-1

32 Setting Up the Utility Server 2. After a few seconds, the initial SyteLine ERP install screen appears. If it doesn t appear, access the CD-ROM drive and double click Setup. 3. Select Utility Server. 4. Click the Install SyteLine ERP 7.03 button. The Welcome screen appears. 3-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

33 5. Click Next. The Custom Setup screen appears. Setting Up the Utility Server 6. Expand Utility Server. The default selections are shown in the screen shot above. Intelligent Data Objects (IDO) and MAPICS Task Manager Service are necessary components for SyteLine ERP. If you are installing SyteLine Workflow Automation, make sure Message Posting is selected. Planning and Scheduling Service is necessary for APS, and Data Collection Middleware is necessary for data collection. For the purpose of this chapter, we selected everything except SyteLine Configuration. If you want to install SyteLine Configuration, see the SyteLine Configuration Installation Guide for installation and setup instructions BEFORE installing SyteLine ERP. 7. Click Next. The Ready to Install the Program screen appears. 8. Click Install. 9. Once the installation process is complete, click Finish. Configure the Utility Server Once the installation completes, run the SyteLine Configuration Wizard to configure the SyteLine ERP utility server. If you choose not to configure a piece as you go through the wizard, leave the screen blank and click Next MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-3

34 Setting Up the Utility Server 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. The Introduction screen appears. 2. Click Next. The Configure the SyteLine Client? screen appears. 3. Select the Configure the SyteLine Client? field. 3-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

35 Setting Up the Utility Server 4. Click Next. The Choose Client Configuration to Create/Modify screen appears. 5. Select the Configuration Name from the list. Click New if you want to create a new configuration or select the configuration and click Delete if you want to delete it. 6. If you want to place a shortcut on the desktop, select the Create SyteLine shortcut on the desktop? field MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-5

36 Setting Up the Utility Server 7. Click Next. The Application Database Information for SyteLine screen appears. 8. Enter the following information: Server Name - Select the server machine where the databases reside; usually the database server. Security Logon - Enter the logon; usually "sa". Security Password - Enter the security password. Application Database - Select the name of the application database you created when you set up the database server. 3-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

37 Setting Up the Utility Server 9. Click Next. The Forms Database Information for SyteLine screen appears. 10. Enter the following information: Server Name - Select the server machine where the databases reside; usually the database server. Security Logon - Enter the logon; usually "sa". Security Password - Enter the security password. Forms Database - Select the name of the forms database you created when you set up the database server MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-7

38 Setting Up the Utility Server 11. Click Next. The Templates Database Information for SyteLine screen appears. 12. This screen appears regardless of whether you created a templates database on the database server. If you did not create a templates database, leave the Templates Database field empty. If you did create a templates database, enter the following information: Server Name - Select the server machine where the databases reside; usually the database server. Security Logon - Enter the logon; usually "sa". Security Password - Enter the security password. Templates Database - Select the name of the templates database you created when you set up the database server. 3-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

39 Setting Up the Utility Server 13. Click Next. The Configure the MAPICS Task Manager Service? screen appears. 14. Select the Configure the MAPICS Task Manager Service? field MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-9

40 Setting Up the Utility Server 15. Click Next. The MAPICS Task Manager ODBCs to Monitor screen appears. 16. Make sure MAPICS Task Manager is selected. There may be more ODBC names in the list depending on what else is on the database server. If you come back into the SyteLine Configuration Wizard to reconfigure an ODBC, you must do it for ALL the ones listed; otherwise you will run into errors. You must appropriately fill in the information on ALL the screens for each ODBC SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

41 Setting Up the Utility Server 17. Click Next. The ODBC Settings for MAPICS Task Manager screen appears. 18. Enter the following information: Server Name - Select the server machine where the databases reside; usually the database server. SQL Logon Id - Enter the SQL logon id; usually "sa". SQL Password - Enter the SQL password. Application Database - Select the name of the application database you created when you set up the database server. This information is used to create the ODBC dataset name to which Task Manager will connect MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-11

42 Setting Up the Utility Server 19. Click Next. The MAPICS Task Manager Settings for ODBC MAPICS Task Manager screen appears. 20. Enter the following information: MAPICS Task Manager Database Logon - Enter the user name that Task Manager will use when connecting to the database; usually sa. MAPICS Task Manager Database Password - Enter the password Task Manager will use when connecting to the database. Forms Db Server - Select the name of the database server where the Forms database containing the string table resides. Forms Db Name - Select the name of the forms database containing the string table. String Table (Optional) - Enter the name of the forms database that contains the strings tables this site will use - for example, OH_forms. The information you enter here becomes the default value for the String Table Specifications field on the Sites/Entities form. The database name must be enclosed in square brackets if it contains periods or begins with a number. For example, if your database is named , then you should enter [ ] SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

43 Setting Up the Utility Server 21. Click Next. The MAPICS Task Manager Service Logon screen appears. 22. Select the Set MAPICS Task Manager Service Logon Id field. 23. Enter your service logon (DOMAIN\Username) and password. The DOMAIN\Username must: already exist have print and privileges on the utility server be able to create directories and files on the utility server have access to the database server machine. If you set up the MAPICS Task Manager Logon ID, the service runs as a windows user account. If you do not set up the MAPICS Task Manager Logon ID, the service runs as a local system account, which does not support notifications or the printing of reports. You can set up or change the logon username and password information later: a. In Windows, select Start>Settings>Control Panel>Administrative Tools. b. Double-click Services MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-13

44 Setting Up the Utility Server c. Right-click on the MAPICS Task Manager service. d. Select Properties. e. Select the Log On tab. f. Set the account and password information. 24. Click Next. The Configure SyteLine Replication Services? screen appears. 25. Select the Configure SyteLine Replication Services? field SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

45 Setting Up the Utility Server 26. Click Next. The Replication Services Configuration and User screen appears. 27. Enter the following information: Configuration - Select the configuration name. The configuration name must match the replication site name. If the configuration name and the replication site names do not match, a configuration matching the replication site name is automatically created. Replication Site - Select the replication site. The configuration name must match the replication site name. If you choose a replication site that does not match the chosen configuration, the system will create a new configuration for you to match the replication site name MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-15

46 Setting Up the Utility Server 28. Click Next. The Create SyteLine Replication Queues screen appears. 29. Select the Create SyteLine Replication Queues field SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

47 Setting Up the Utility Server 30. Click Next. The Security for MAPICS Replication Listener Service screen appears. 31. Enter your service logon (DOMAIN\Username) and password. The system automatically assigns the proper permissions to the MSMQ queues for the username you enter MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-17

48 Setting Up the Utility Server 32. Click Next. The Security for MAPICS Replicator Service screen appears. 33. Enter your service logon (DOMAIN\Username) and password. The system automatically assigns the proper permissions to the MSMQ queues for the username you enter. Once you set up the clients in the Setting Up a Client Workstation chapter, you need to perform some additional steps regarding the SL_Internal user if you are a multi-site or Workflow user that will require you to come back here to the Utility Server and re-run the SyteLine Configuration Wizard. See Run SyteLine ERP 7 on page 4-14 for instructions. For now, continue through the SyteLine Configuration Wizard and then come back after you have set up the clients SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

49 Setting Up the Utility Server 34. Click Next. The Configure Session Server Components screen appears. 35. Select the Configure Session Server Components? field. We recommend that you select this field. If you clear this field you will not be able to run Print Previews on your client machines. If you need to set up the utility server for testing purposes and you do not select this field, set the ODBC setting manually within Data Sources (ODBC) in Control Panel of the client machines to run Print Preview. The ODBC must have the same name as the WinStudio Configuration and must point to the SyteLine application database MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-19

50 Setting Up the Utility Server 36. Click Next. The Session Server Components Username and Password screen appears. 37. Enter the Network Logon for the COM+ Package (DOMAIN\Username) and password SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

51 Setting Up the Utility Server 38. Click Next. The Configure the MAPICS SyteLine Workflow Utility Components? screen appears. 39. Clear the Configure Workflow Utility Components? field. You will install and configure SyteLine Workflow Automation in Setting Up Workflow Automation on page MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-21

52 Setting Up the Utility Server 40. Click Next. The Configure Gateway Services screen appears. The Gateway Service supports the MRP and APS features by running a process that synchronizes the planning database with the SyteLine application database. You must set up one Gateway Service for each SyteLine application database SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

53 Setting Up the Utility Server 41. Click the Add button. The Gateway Parameters screen appears. The information on the Gateway Parameters screen should be filled in automatically. If you need to provide the information or add additional gateways, enter the information as follows: Server Name - The name of the SQL Server where the SyteLine application database is installed. SQL Logon Id - The SQL Server user that can log in to the application database (for example, sa). SQL Password - The password for the SQL logon id. Application Database - The name of the SyteLine application database with which this gateway service will communicate. Service Username - A domain user account under which the Gateway service can run. Enter the domain name and user name (for example, "MYDOMAIN\Myusername"). Service Password - The password for the service user account MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-23

54 Setting Up the Utility Server Interval - The time delay (in seconds) before the service runs the process that synchronizes the planning database and SyteLine application database. The default interval is 300 seconds. 42. Verify that the information is correct and click OK. The Configure Gateway Services screen appears with the name of the Gateway Service SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

55 Setting Up the Utility Server 43. Click Next to add the Gateway Service. After the process is complete, the Planning and Scheduling Service Setup screen appears. The Planning and Scheduling Service supports the MRP and APS features. You need one Planning and Scheduling Service for each SyteLine application database MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-25

56 Setting Up the Utility Server 44. Click the Add button. The Server Service Parameters screen appears. The information should be filled in automatically. If you need to provide the information or add an additional server service, enter the information as follows: Server Name - The name of the SyteLine database server where the SyteLine application database is installed. SQL Logon Id - The SQL Server user that can log in to the application database (for example, sa). SQL Password - The password for the SQL logon Id. Application Database - The name of the SyteLine application database with which the server service will communicate. Service Username - A domain user account under which the server service can run. Enter the domain name and user name (for example, "MYDOMAIN\Myusername"). Service Password - The password for the service user account SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

57 Setting Up the Utility Server Port Number - The port number to use for the service (must be a number from ). This must be a different port number than the port on which the planning database is running (you set up the planning database in Chapter 8, Setting Up the Planning Server"). Temp Directory - The path to a folder where the server service can write temporary files (such as c:\temp). This directory must allow full control by the local administrator user account. 45. Verify that the information is correct and click OK. The Planning and Scheduling Service Setup screen appears with the name of the Planning and Scheduling Service. 46. Click Next to add the Planning and Scheduling Service. After the process is complete, the Review Changes screen appears. 47. Verify that the information is correct, and click Commit. 48. When the configuration process is complete, click Finish. When the configuration process is complete, you must reboot the server. This ensures that all necessary Windows services are started MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-27

58 Setting Up the Utility Server Final Data Collection Steps The following steps are for Data Collection users only. Set up the DC Client Directory and Data Collection Parameters After you have installed data collection components and run the SyteLine Configuration Wizard, you need to set up the DC Client Directory, parameters, and background processor on the Data Collection Parameters form. We recommend you access the Data Collection Parameters form from the DC Client workstation or on the machine where you will be running the background processor. To set up the DC Client Directory and Data Collection Parameters: 1. Select the Background tab on the Data Collection Parameters form. 2. Enter the path of the DC Client Directory in the DC Client Directory field. The system creates this directory if it does not already exist. The directory path c:\program Files\MAPICS\SyteLine\ DataCollection\Intermec\DcSfc is created during installation of the data collection components on the utility server. 3. If you entered a different path than the default, you must manually copy the contents of default directory to the newly created DC Client Directory. You must set up a unique DC Client Directory for each SyteLine ERP database in a multi-site environment. Repeat these steps for each site to create a unique DC Client Directory. 4. Set the other parameters on the Data Collection Parameters form, such as polling frequency and auto-post parameters, if required for your implementation. Set Up the Background Processor To set up the data collection background processor: 1. Select the Background tab on the Data Collection Parameters form. 2. Set the Run Data Collection Background Process field to either Background Task mode or Standalone mode. Consider the amount of data to be processed and your system requirements when deciding which mode to use. See the online help for the Run Data Collection Background Process field for more information SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

59 Setting Up the Utility Server 3. If you selected to run the background processor in background mode, you must: Edit the dcbackground.bat file in the DC Client Directory and change the line: "C:\Program Files\MAPICS\SyteLine\DataCollection\InterMec\DcSfc\Dc Background.exe" user=sl_internal password= config= SYMDCBKG=ENABLED where: user=sl_internal is required. password is the password defined for SL_Internal (default is blank). config is the site name. SYMDCBKG=ENABLED is used to record the start and end of each poll in the collect.err file. Since this will require more disk space, you may want to use this value primarily for troubleshooting. Remove this value if not needed. For example: user=sl_internal password= config=ohio SYMDCBKG=ENABLED. Open the Background Task Definitions form In SyteLine 7 ERP. Select the Dcbackground task, and in the Executable Name field, enter dcclientdirectorypath\dcbackground.bat, where dcclientdirectorypath is the DC Client Directory path. 4. If you selected to run the background processor in standalone mode, set the parameters for the background process shortcut. Right click Start>Explore All Users. Select Start Menu>Programs>MAPICS>Tools. Select DC Background and right click Properties. In the Target field add user=sl_internal password= config=sitename SYMDCBKG=ENABLED. Enter the password defined for SL_Internal (default is blank). SiteName is the name of the SyteLine site. Enter SYMDCBKG=ENABLED to record the start and end of each poll in the collect.err file. Since this will require more disk space, you may want to use it primarily for troubleshooting. Remove this value if not needed. 5. Start the background processor. See the online help for the Run Data Collection Background Processor field for more information on how to do this for the mode selected MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-29

60 Setting Up the Utility Server Run Test Transactions After you have completed installing SyteLine 7 ERP, you may want to run test data collection transactions. We recommend you clear all auto-post parameters on the Data Collection Parameters form and do not use your primary database for testing. You can also use the purge utilities to delete the transactions in error processing instead of posting them. Setup a Utility Server to send Notifications for Reports TaskMan uses MAPI to send notifications. Although the following steps explain how to set up the utility server using Outlook, any MAPI service will work. 1. Create an Outlook profile. If an Outlook icon is on the desktop, right-click on it and choose Properties. Then select Show Profiles. If the icon doesn t exist on the desktop, click Start>Settings>Control Panel. Double-click the Mail icon. On the Services tab, click Show Profiles... a. Highlight MS Exchange Settings and choose Copy. If this choice is not available, create a valid default profile in Outlook. b. Name the copy TaskMan (note the capitalization) and click OK. 2. Perform the following tasks to notify TaskMan to send attachments: a. Start Syteline ERP. b. Open the Sites/Entities form. c. Click on the row in the grid representing your site. d. Right-click on the Intranet Name field and choose Details. e. Click on the Reports/TaskMan tab. f. Make sure the Send Notification checkbox is checked. 3. Setup each report where notifications are required: a. Start Syteline ERP b. Open the Background Task Definitions form c. Filter on the required task names d. For each task: Click on Report Options. Click on the row for the user and task name SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

61 Setting Up the Utility Server Choose any output format. Set notification to Yes. If you want the report attached to the , set Attach Report to Yes. 4. Make sure the user printing the report contains a valid address: a. Start Syteline ERP. b. Open the Users form. c. Filter on the user name in question. d. Make sure the Address field is filled in and correct. 5. Print the report. Troubleshooting Open the Background Task History form in SyteLine ERP, filter on the Task Name field and investigate possible errors that TaskMan encountered. Open the Application Event Log for the operating system ( Event Viewer in the control panel). Look for errors that TaskMan might have logged. If there are still no errors reported, start TaskMan with the debug nowait Start parameters. Consult the Application Event Log for debug messages that TaskMan logs. Install Crystal Reports Crystal Reports must be installed on the machine with Task Manager (this is typically the utility server). Install Crystal Reports based on the installation instructions on the Crystal Reports CD. However, in order for Crystal Reports to function properly with SyteLine, you must install every feature, then install the service pack and hot fixes. Crystal Reports online help does not install with the product. For a workaround, visit the Crystal Decisions website: MAPICS, Inc. SyteLine ERP 7 Installation Guide 3-31

62 Setting Up the Utility Server Install All Features 1. During the install, when the Select Installation Type screen displays, select Custom. 2. Click Next. On the Select Features screen, click on Crystal Reports and select Extra feature will be installed on local hard drive. 3. Continue the installation process based on the Crystal Reports documentation located on the CD. Install Crystal Reports Service Pack and Hot Fixes After installing Crystal Reports, install the service pack and hot fixes included on the Crystal Reports CD. 1. Navigate to the SP1 folder on your Crystal Reports CD. 2. Double click cr90win_en_sp1.exe. Follow the on-screen instructions to complete the service pack installation. 3. After the service pack install is complete, navigate to the HotFixes folder on your Crystal Reports CD. 4. Follow the instructions in _HotFixReadMe.txt to install each of the three hot fixes SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

63 4 Setting Up a Client Workstation Requirements A client workstation is a personal computer with access to the network. A client workstation must have a Windows 2000 or Windows XP operating system. SQL 2000 client components are already installed on all SyteLine ERP Administrative Clients. This is not necessary for the End User or Analyzer Clients. To view report output (whether previewing or printing) in the following formats, you must have the associated applications installed on the client machine: Crystal, Excel 8.0, HTML 4.0, Word for Windows, Acrobat Format, and XML. Upgrade Message If a SyteLine client is an older version than the database, a message will appear on the client that a more current version is available. Installation Options There are three options from which to choose when installing to a client machine. End User Client - Minimum files and setup for User Interface to SyteLine ERP. Administrative Client - User Interface to Syteline ERP that can utilize remote IDOs or use local IDOs per configuration or environment. Some additional tools for system administrators are added MAPICS, Inc. SyteLine ERP 7 Installation Guide 4-1

64 Setting Up a Client Workstation Analyzer Client - Web components and middleware for accessing the Analyzer Web application. The Analyzer allows you to test the viability of alternative planning and scheduling situations using a copy of your database, without affecting your production SyteLine data. For installation and configuration instructions see Setting Up the Web Server on page 9-1. There is a fourth option; an HTTP Client. See Setting Up an End User Client for HTTP Access on page D-1 for installation and setup instructions. Configure the Client After you install one of the client options, you must configure that client machine with the SyteLine Configuration Wizard. You will find the configuration instructions after the installation instructions in this chapter. If you plan to set up an HTTP client, you do not need to run the SyteLine Configuration Wizard after you install the End User Client. See Setting Up an End User Client for HTTP Access on page D-1 for installation and setup instructions. Installation and configuration must be performed on all client machines. After you configure the client, see Run SyteLine ERP 7 on page 4-14 for direction on how to launch SyteLine ERP. Install End User Client 1. Insert the SyteLine ERP CD into the CD-ROM drive of the client machine. 4-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

65 Setting Up a Client Workstation 2. After a few seconds, the initial SyteLine ERP install screen appears. If it doesn t appear, access the CD-ROM drive and double click Setup MAPICS, Inc. SyteLine ERP 7 Installation Guide 4-3

66 Setting Up a Client Workstation 3. Select Client as the configuration type. The Select a Client Type box appears on the screen. 4. Select End User Client from the Select a Client Type box. 5. Click the Install SyteLine ERP 7.03 button. The Welcome screen appears. 4-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

67 6. Click Next. The Custom Setup screen appears. Setting Up a Client Workstation 7. Expand Client and then End User as in the screen shot above. Notice that SyteLine Configuration is deselected by default. If you need to install SyteLine Configuration, see the SyteLine Configuration Installation Guide for installation and setup instructions BEFORE installing SyteLine ERP. 8. Click Next. The Ready to Install the Program screen appears. 9. Click Install. 10. When the installation process is finished, click Finish to close the installation screen. Configure End User Client After you finished the install for the End User Client, you must run the SyteLine Configuration Wizard to configure the End User Client. 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. The Introduction screen appears MAPICS, Inc. SyteLine ERP 7 Installation Guide 4-5

68 Setting Up a Client Workstation 2. Click Next. The Configure the SyteLine Client? screen appears. 3. Select the Configure the SyteLine Client? field. 4-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

69 Setting Up a Client Workstation 4. Click Next. The Session Server Settings screen appears. 5. Select the session server name. The session server name is the name of the utility server you set up earlier. 6. Click Next. The Review Changes screen appears. 7. Verify that the information is correct, and click Commit. The Configuration Results screen appears. 8. Click Finish. Install Administrative Client 1. Insert the SyteLine ERP CD into the CD-ROM drive of the client machine MAPICS, Inc. SyteLine ERP 7 Installation Guide 4-7

70 Setting Up a Client Workstation 2. After a few seconds, the initial SyteLine ERP install screen appears. If it doesn t appear, access the CD-ROM drive and double click Setup. 4-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

71 Setting Up a Client Workstation 3. Select Client as the configuration type. The Select a Client Type box appears on the screen. 4. Select Administrative Client from the Select a Client Type box. 5. Click the Install SyteLine ERP 7.03 button. The Welcome screen appears MAPICS, Inc. SyteLine ERP 7 Installation Guide 4-9

72 Setting Up a Client Workstation 6. Click Next. The Custom Setup screen appears. 7. Expand Client and then Administrative as in the screen shot above. Notice that SyteLine Configuration is deselected by default. If you need to install SyteLine Configuration, see the SyteLine Configuration Installation Guide for installation and setup instructions BEFORE installing SyteLine ERP. 8. Click Next. The Ready to Install the Program screen appears. 9. Click Install. 10. When the installation process is finished, click Finish to close the installation screen. Configure Administrative Client After you finished the install for the Administrative Client, you must run the SyteLine Configuration Wizard to configure the Administrative Client. 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. The Introduction screen appears SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

73 Setting Up a Client Workstation 2. Click Next. The Configure the SyteLine Client? screen appears. 3. Select the Configure the SyteLine Client? field MAPICS, Inc. SyteLine ERP 7 Installation Guide 4-11

74 Setting Up a Client Workstation 4. Click Next. The Session Server Settings screen appears. 5. Select the Uses COM+ Connection field and add the name of the session server in the Session Server Name field. The session server name is the name of the utility server you set up earlier SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

75 Setting Up a Client Workstation 6. Click Next. The Specify the Session Server Shortcut Name screen appears. 7. Provide the application name for the session server. Select or clear the Create Desktop Shortcut? field depending on your preference. 8. Click Next. The Configuration Results screen appears. 9. Click Finish. Configure Permissions for Resource Gantt Charts To use the "Highlights" feature of the Resource Group Gantt Chart and Resource Gantt Chart forms, you must allow any non-administrator users Full Control permission rights to the C:\Program Files\MAPICS\SyteLine\Analyzer\ReportFiles\Gantt.mdb file. 1. Log in as the Administrator user on the SyteLine client machine. 2. In Windows Explorer, navigate to the C:\Program Files\MAPICS\SyteLine\Analyzer\ReportFiles folder. 3. Right-click on the ReportFiles folder and choose Properties. 4. Select the Security tab. 5. Click Add MAPICS, Inc. SyteLine ERP 7 Installation Guide 4-13

76 Setting Up a Client Workstation 6. In the Look In field, select the appropriate domain. 7. Select Everyone (or choose the appropriate user groups that will be using the Resource and Resource Group Gantt Chart forms). 8. Click Add. 9. Click OK. Run SyteLine ERP 7 Perform these steps on any machine that will be used to access the Analyzer application (see Chapter 9, Setting Up the Web Server" for information about setting up the Analyzer). Critical information is contained in the steps immediately below, especially if you are a multi-site or Workflow user. Once you have set up your client workstation, you should be able to run SyteLine ERP Choose Start>Programs>MAPICS. 2. Select the name of the shortcut you specified earlier. The following logon screen appears: 3. Logon as "sa", leaving the password blank. This user allows you to enter SyteLine ERP so that you can set up other users and parameters for your system. The "sa" user is a single session user, so you will not be able to logon to another machine with that user ID if you are still logged on as "sa" somewhere else. 4. Select the appropriate configuration name from the Data Source Config field, and click OK. SyteLine ERP will open SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

77 Setting Up a Client Workstation 5. Open up the License Management form and apply your license. See the SyteLine ERP 7 System Administration Guide for information about the License Management form and how to apply your license. 6. On the Order Entry Parameters form, specify the invoice length in the Invoice Length field. The default for this field is blank, and you can set it to any length up to 12. We recommend that you use 12 as the length. The invoice length must be the same for all sites in the system. It must be set at each site; it cannot be replicated to the other sites. This field must be set when no other users are in the system. After you save the change, the system updates about 50 database tables, so it will take a long time to process. Once the Invoice Length field is set to a non-null value, the value can never be updated. 7. If you are not a multi-site, CRM, or Workflow user, you are finished with these steps. If you are a multi-site, CRM or Workflow user, open the Users form. 8. Make the SL_Internal user a Super User. SL_Internal is the SyteLineprovided user that is necessary for Workflow and CRM. 9. Provide a password for SL_Internal and save your changes. 10. Go back to the Utility Server machine(s) and launch the SyteLine Configuration Wizard (Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard). Follow the wizard steps and reconfigure replication. Provide the required information on all the replication screens within the SyteLine Configuration Wizard. Rerunning the SyteLine Configuration Wizard writes the password you set for the SL_Internal user into the registry. You can now set up additional users on the Users form and begin using SyteLine MAPICS, Inc. SyteLine ERP 7 Installation Guide 4-15

78 Setting Up a Client Workstation 4-16 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

79 5 Setting Up Workflow Automation Perform the following tasks to install and configure Workflow Automation. On the Exchange Server machine, 1. Install MSMQ. 2. Create the SyteLine and Workflow user accounts and mailboxes. 3. Install the Message Posting component. 4. Configure Workflow Automation. 5. Check the services. 6. Set Client Permissions on EventConfig_Servername. On the utility server machine, 7. Install and configure Outlook 2000 with Collaboration Data Objects. 8. Set up the Workflow Profile. 9. Install and configure Lexign Flow Server. 10. Install the Message Posting component. 11. Configure Workflow Automation. 12. Create a temporary directory. 13. Configure Outlook to use Workflow. 14. Configure permissions for the Workflow queue. 15. Configure and check the services. On the client machine, 16. Install Lexign Flow Designer. 17. Create a test Workflow template within Outlook. 18. Activate Workflow in SyteLine. 19. Test Workflow Automation MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-1

80 Setting Up Workflow Automation Prerequisites Before installing Workflow Automation, the following tasks must be completed: The SyteLine database must be licensed. SyteLine replication must be configured. A dedicated instance of Exchange Server must be installed and integrated with your corporate server. This instance of Exchange Server is typically installed on the SyteLine database server. However, if you are running your database on a Windows 2003 machine, you must install Exchange Server on a different machine. The SL_Internal user must be a Super User. Setup the Exchange Server Machine The Exchange Server machine MUST be a Windows 2000 Server machine. It can not be Windows Server Step 1: Install MSMQ To install Message Queuing on the Exchange server, perform the following steps: 1. Logon using a Domain Administrator Account and run Add/Remove Programs from within Control Panel. 5-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

81 Setting Up Workflow Automation 2. Select Add/Remove Windows Components. Once the Windows Components Wizard appears, select Message Queuing Service. 3. The next screen that appears prompts you to select the Message Queuing Type. Select Message Queuing server. Click Next MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-3

82 Setting Up Workflow Automation 4. Select Message Queuing will not access a directory service. Click Next. 5. After the MSMQ installation has completed, click Finish. Step 2: Create the SyteLine and Workflow User Accounts and Mailboxes When you create a new user in Active Directory Users and Computers, a mailbox is automatically created for that user. 1. Log into Active Directory Users and Computers. 2. Expand the Users folder. 3. Right-click on the Users folder, then select New>User. 4. Create a new user account named syteline. 5. After creating the user, enable Advanced Features by selecting View>Advanced Features. 6. Right-click on the user you just created and select Properties. 7. On the Exchange Advanced tab, click Mailbox Rights. 8. Add the Domain Admins user. 9. Give this user account full access. 10. Click OK. 11. Repeat steps 2 through 10 to create a workflow user (name this user account workflow). 12. Close Active Directory Users and Computers. 5-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

83 Setting Up Workflow Automation Step 3: Install the Message Posting Component If you have previously installed SyteLine components on this machine, you must perform the following steps to activate the install shield: 1. In Control Panel, double-click Add/Remove Programs. 2. Select MAPICS SyteLine ERP and click Change. 3. When the Welcome screen appears, click Next. 4. Choose to modify the current setup. 5. Enable Exchange Server>Message Posting Component. 6. Click Next and continue through the install shield. 7. After the Message Posting installation is complete, skip to Step 4: Configure Workflow Automation. 1. Insert the SyteLine ERP CD into the CD drive of the Exchange Server machine. 2. After a few seconds, the initial SyteLine ERP install screen appears. If it does not appear, access the CD-ROM drive and double click Setup. 3. Select Exchange Server. 4. Click the Install SyteLine ERP button. The Welcome screen appears. 5. Click Next. The Custom Setup screen appears MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-5

84 Setting Up Workflow Automation 6. Click the Exchange Server icon to expand the list of components. Make sure Message Posting is selected. 7. Click Next. The Ready to Install the Program screen appears. 8. Click Install. 9. Once the installation process is complete, click Finish. Step 4: Configure Workflow Automation Run the SyteLine Configuration Wizard 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. 2. The Introduction screen appears. Click Next. 3. On the Configure MAPICS SyteLine Workflow Exchange Server Components? screen, ensure that the Configure Workflow Exchange Server Components? field is selected. 5-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

85 Setting Up Workflow Automation 4. Click Next. The Workflow Queue Listener Server screen appears. 5. In the Session Server field, select your utility server. The session server is the server on which the MAPICS Workflow Queue Listener service is running. The MAPICS Workflow Queue Listener service is created when you install Workflow on the utility server. 6. Click Next. The Review Changes screen appears. 7. Verify that the information is correct, then click Commit. 8. When the configuration is complete, the Configuration Results screen appears. 9. Click Finish to complete the configuration. Step 5: Check the Services Ensure that the following services are running and are set to run automatically: All Microsoft Exchange services Microsoft Message Queue Service MS-Exchange Event Services MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-7

86 Setting Up Workflow Automation Step 6: Set Client Permissions on EventConfig_Servername 1. Select Start>Programs>Microsoft Exchange>System Manager. 2. When the System Manager screen displays, select Administrative Groups>First Administrative Group>Folders>Public Folders. If you chose not to display routing groups and administrative groups, then select Folder>Public Folders instead. 3. Right-click on the Public Folders folder and select View System Folders. 4. In the left windowpane, select Events Root. In the right windowpane, select the EventConfig_Servername that will handle message posting. Right-click and select Properties. 5. Once the EventConfig_Servername properties page appears, select the Permissions tab. 6. Click Client Permissions. 7. Add the SyteLine mailbox and set the role to at least Author. 5-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

87 Setting Up Workflow Automation 8. Add the domain administrator and set the role to at least Author. 9. Click OK to save the changes. Setup the Utility Server Machine Step 7: Install Outlook 2000 with Collaboration Data Objects Consult your Microsoft Office documentation for Outlook 2000 installation instructions. If you have already installed Outlook 2000 on this machine, perform the following steps to add Collaboration Data Objects: 1. Select Start>Settings>Control Panel>Add/Remove Programs. 2. Select Microsoft Office and click Change. 3. Proceed through the Outlook installation and ensure that the Collaboration Data Objects component is selected. Step 8: Set up the Workflow Profile Before installing Lexign Flow Server and the Message Posting component, you must set up the workflow profile (the workflow user account was created in Step 2. Consult your Miscrosoft Outlook documentation for instructions about setting up a profile. Step 9: Install and Configure Lexign Flow Server Create Public Folders within Outlook The Outlook public folders can be created anywhere under Public Folders/All Public Folders. They can also be named whatever you choose. Below are examples of Public Folders you might create and their purpose. Templates - This folder will store the Workflow templates for all workflows Active Flows - This folder is used to store active flows that do not post data back into SyteLine. Completed Flows - This folder is used to store completed flows. Follow the steps below to create the Workflow folders within Outlook. 1. Open Outlook and navigate to Public Folders/All Public Folders. 2. If you are creating your Workflow folders under All Public Folders, right click and select New-Folder. 3. Enter the name of the new folder. 4. Repeat steps 2 through 3 until all folders are created. Install Lexign Flow Server 1. Insert the MAPICS Integration CD MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-9

88 Setting Up Workflow Automation 2. Enter your license key. 3. Select SyteLine as the product, and Utility Server as the server type. 4. Click Install Lexign Flow Click Next at the Welcome screen. 6. Click Yes to accept the license agreement. 7. When the Install Lexign Flow Components screen appears, select Lexign Flow Server. 8. Enter the destination path or accept the default. Click Next. 9. Enter the path to the Lexign Flow license key file. Click Next. 10. Enter the program folder or accept the default. Click Next. 11. Click Next to complete the installation. 12. On the Setup Complete screen, choose whether to view the documentation, then click Finish. Configure Lexign Flow Server 1. Select Start>Programs>Lexign>Lexign Flow>Setup Lexign Flow Server. 2. Select the Workflow Outlook profile. Click Ok. 3. Configure the Workflow server for the following settings: Domain User Account Password Profile Domain name Administrator Administrators password flowserver 4. Click Save/Register. 5. Verify that Lexign Flow Server is installed, registered and running. This information is displayed in the lower portion of the Setup Lexign Flow Server screen SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

89 Setting Up Workflow Automation Step 10: Install the Message Posting Component If you have previously installed SyteLine components on this machine, you must perform the following steps to activate the install shield: 1. In Control Panel, double-click Add/Remove Programs. 2. Select MAPICS SyteLine ERP and click Change. 3. When the Welcome screen appears, click Next. 4. Choose to modify the current setup. 5. Enable Utility Server>Message Posting Component. 6. Click Next and continue through the install shield. 7. After the installation is complete, skip to Step 11: Configure Workflow Automation. 1. Insert the SyteLine ERP CD into the CD drive of the Utility Server machine. 2. After a few seconds, the initial SyteLine ERP install screen appears. If it does not appear, access the CD-ROM drive and double click Setup. 3. Select Utility Server. Click the Install SyteLine ERP button. The Welcome screen appears. 4. Click Next. The Custom Setup screen appears. 5. Click the Utility Server icon to expand the list of components. Make sure Message Posting is selected MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-11

90 Setting Up Workflow Automation 6. Click Next. The Ready to Install the Program screen appears. 7. Click Install. 8. Once the installation process is complete, click Finish. Step 11: Configure Workflow Automation On the Utility Server, run the SyteLine Configuration Wizard to configure Workflow. 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. The Introduction screen appears. 2. Click Next. The Configure the SyteLine Client? screen appears. 3. Leave the Configure the SyteLine Client? field blank. 4. Click Next. The Configure the MAPICS Task Manager Service? screen appears. 5. Leave the Configure the MAPICS Task Manager Service? field blank. 6. Click Next. The Configure SyteLine Replication Services? screen appears. 7. Leave the Configure SyteLine Replication Services? field blank. 8. Click Next. The Configure Session Server Components screen appears. 9. Leave the Configure Session Server Components? field blank SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

91 Setting Up Workflow Automation 10. Click Next. The Configure the MAPICS SyteLine Workflow Utility Components? screen appears. 11. Select the Configure Workflow Utility Components? field MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-13

92 Setting Up Workflow Automation 12. Click Next. The Select Workflow Mailbox screen appears. 13. Enter the following information: MS Exchange Server - Select the MS Exchange Server that was set up for Workflow. Mailbox - Enter the mailbox that will be used for Workflow. Workflow Templates Folder - Enter the path to the workflow templates folder. This path must match the path that was created in Outlook SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

93 Setting Up Workflow Automation 14. Click Next. The SyteLine Workflow Mailbox Login screen appears. 15. Enter the following information: Mailbox Username (DOMAIN\Username) - Enter the mailbox username. Password - Enter the mailbox password. 16. Click Next on any remaining screens until the Review Changes screen appears. 17. Verify that the information you entered is correct, then click Commit. 18. When the configuration process is complete, click Finish. Step 12: Create a Temporary Directory Workflow Automation needs to write temporary files to C:\Temp. Ensure that this directory exists. Step 13: Configure Outlook to use Workflow Activate Server Scripting Prior to creating the Inbox Agent, you must also activate server scripting on the SyteLine Inbox. The steps below are for Outlook 2000 and may vary depending on the version of Outlook that is installed. To activate server scripting: 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-15

94 Setting Up Workflow Automation 1. Open Outlook. 2. Select the posting mailbox, usually SyteLine. 3. From the menu bar, select Tools>Options. 4. Select the Other tab. Click Advanced Options. 5. Click Add-in Manager. 6. Select Server Scripting. Click OK several times to finish activating server scripting. Create the Inbox Agent In order to see the Agents tab, you must be logged in as either SyteLine or a domain administrator, and the SyteLine mailbox must be the default mailbox. 1. Open Outlook and select the posting mailbox s inbox. 2. Right-click on the inbox and select Properties. 3. Select the Agents tab. 4. Click New. When the New Agent screen displays: a. Enter a name for the Workflow agent b. Select A New Item is Posted in This Folder. c. In the lower portion of the screen, select Other. Use the drop-down menu to select SyteLine 7 Agent. d. Click OK SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

95 Setting Up Workflow Automation Step 14: Configure Permissions for the Workflow Queue 1. From the desktop, right-click on My Computer and select Manage. The Computer management window displays. 2. Select Services & Applications>Message Queuing>Private Queues>Workflow>Properties. 3. On the Security tab, give the "Everyone" user full permissions. 4. Click Ok, then close the Computer Management window. Step 15: Configure and Check the Services Verify that the following services are set to auto start and are configured to log on as a domain administrator account: MAPICS Workflow Posting Service MAPICS Workflow Queue Listener Lexign Flow Server MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-17

96 Setting Up Workflow Automation Setup the Administrative Client Machine Step 16: Install Lexign Flow Designer on the Administrative Client Machine Outlook must be installed and configured prior to installing Lexign Flow. 1. Insert the MAPICS SyteLine ERP Integration CD into the CD-ROM drive of the administrative client machine. 2. Ensure that Outlook is not running. If Outlook remains open during this installation, you will receive a message asking you to re-start Outlook after the installation is complete. 3. Run the MAPICS Integration CD and enter your license key. 4. Select the SyteLine product, then the Utility Server server type. 5. Click the Install Lexign Flow button. 6. Click Next at the Welcome screen. 7. Click Yes to accept the license agreement. 8. When the Install Lexign Flow Components screen appears, select Lexign Flow Designer. Click Next. 9. When the Select Installation Type screen appears, select Typical. Click Next. 10. Enter the destination path or accept the default. Click Next. 11. Enter the program folder or accept the default. Click Next. 12. Review your installation choices, then click Next to begin the installation. 13. Click Finish when the installation is complete. Step 17: Create a Test Workflow Template Within Outlook Create a Workflow template to test workflow posting. This template will send a message to a recipient to approve a Purchase Order. Once approved, is routed to syteline for posting. Install the Sample Outlook Forms Outlook Forms are part of Microsoft Outlook, and provide a way to customize the presentation of your . The SyteLine ERP client install includes two sample forms, which will be used in the test Workflow template. For more information about creating and modifying Outlook Forms, see your Microsoft Outlook documentation SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

97 Setting Up Workflow Automation Before you can use the sample forms, you must first publish them within Outlook. You can publish the sample forms on the utility server, database server, or any administrative client machine. 1. Navigate to \\Program Files\MAPICS\Syteline\Custom Outlook Forms. 2. Double-click Outlook Form For FYI with Text message box.oft. The FYI template displays. 3. Select Tools>Forms>Publish Form As In the Look In field, select Organizational Forms Library. 5. In the Display Name field, enter KeyFlow.Task.FYI.Default. The Display Name field is duplicated in the Form Name field. 6. Click Publish to make this form available to other users. 7. Navigate back to \\Program Files\MAPICS\Syteline\Custom Outlook Forms. 8. Double-click Outlook Form for Response with Text message box.oft. The FYI template displays. 9. Select Tools>Forms>Publish Form As In the Look In field, select Organizational Forms Library. 11. In the Display Name field, enter KeyFlow.Task.Response.Default. The Display Name field is duplicated in the Form Name field. 12. Click Publish to make this form available to other users MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-19

98 Setting Up Workflow Automation Create the Template Prior to selecting the Workflow icon within Outlook, make sure that you have the Templates folder selected. Lexign Flow does not have a Save As... menu option. Therefore, the template is saved in the folder you are in when you click on the Workflow icon. 1. The Review PO step can be sent to any recipient for approval. The possible response is approved. 2. The Approved step must be sent to the syteline mailbox set up for posting. The possible responses are Success and Failure. When creating the Approved step, Open the Forms tab of the workflow step, select the Message Class field, and after the read-only text "KeyFlow.Task.Response." enter fsslworkflow. 3. The Success FYI step can be sent to advise the post was successful. 4. The Failure response step sends a message to someone who can correct the error. The possible response is Corrected. 5. The Loop step forwards the back to the original recipient for approval. 6. Save the template as Review Purchase Order SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

99 Step 18: Activate Workflow in SyteLine 1. Log into SyteLine and open the Sites/Entities form. Setting Up Workflow Automation 2. For each site where Workflow is enabled, select the Workflow Enabled checkbox, located in the lower portion of the form. Set the Path to the Workflow Test Template 1. Open the Work Flows form. 2. Enter the form name (PurchaseOrders). 3. In the Action field, select Update. 4. In the Active Flows Folder field, append the existing path with the path to the folder that holds the posting workflows. This entry must match the folder created within All Public Folders and is case-sensitive. 5. In the Flow Name field, enter the flow template name (Review Purchase Orders). 6. Select Suspend. 7. Save your changes. 8. Later, after you add more templates, repeat steps 1 through 6 for each form that will utilize workflows. Set the Address Within SyteLine ERP Perform the following steps from within SyteLine ERP: 1. Open the Users form. 2. Select the record of a user who will be launching workflows. 3. Ensure that the user has a valid address. 4. Repeat steps 2 through 3 for each user who will add, insert, or delete records or any form where a workflow or other automated process may be invoked. Register the Workflow Template Before a flow can succeed, the template on which it is based must be registered in SyteLine. To register a template, perform the following steps: 1. Open the Workflow Templates form. 2. Select Actions>New or click on an empty row. 3. Use the drop-down menu to select the template you want to register MAPICS, Inc. SyteLine ERP 7 Installation Guide 5-21

100 Setting Up Workflow Automation 4. Select Actions>Save to register the template. Restart the SyteLine Session After activating Workflow in SyteLine, restart the SyteLine session. Step 19: Test Workflow Automation 1. Update the Vend PO field on a Syteline Purchase Order. This will send e- mail to the user designated to approve the PO. 2. Check for an active flow within the Posting Flows folder. 3. Open the within Outlook and select Approved as the response. Click Reply. 4. Check for an in the SyteLine Inbox. Within a few minutes, this e- mail should be processed automatically. 5. Refresh the record within SyteLine to verify that the Vend PO field is updated SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

101 6 Setting Up a Multi-Site Environment The steps in this chapter detail how to set up the database server in a multisite environment. If you want to set up a single site environment, see Setting Up the Database Server on page 2-1. Before performing the steps in this chapter, you must have already set up the database server. See Setting Up the Database Server on page 2-1 for set up instructions. Configure the Database Server Run the SyteLine Configuration Wizard on the database server to create the SyteLine ERP database environment MAPICS, Inc. SyteLine ERP 7 Installation Guide 6-1

102 Setting Up a Multi-Site Environment 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. The Introduction screen appears. 2. Select Setup a new SyteLine Database Environment. 6-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

103 Setting Up a Multi-Site Environment 3. Click Next. The Choose Database Setup Tasks screen appears. 4. Deselect all options except for Link Multi-Site Databases. You can not create a new database at the same time you try to link databases. If you attempt, you get an error MAPICS, Inc. SyteLine ERP 7 Installation Guide 6-3

104 Setting Up a Multi-Site Environment 5. Click Next. The Link Multi-Site Databases screen appears. 6. In the Group Name field, leave the default name or enter a group name. The group name ties the sites together and can be changed on the Site Groups form. 6-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

105 Setting Up a Multi-Site Environment 7. Click Add. The Select Database to Link screen appears. 8. Enter the following information: Server Name - Select the name of the database server. sa Logon Id - sa defaults here and you can not change it. sa Password - Enter the sa password. Database Name - Select the name of the database you want to belong in a multi-site environment. Site Id - The site ID you created when you set up the database displays. Site Name - The site name you created when you set up the database displays MAPICS, Inc. SyteLine ERP 7 Installation Guide 6-5

106 Setting Up a Multi-Site Environment Site Description - The site description you created when you set up the database displays. Site Currency Code - The currency code for the site displays. Site Type - The site type displays. It will either be "Site" or "Entity". Site Intranet - If the site belongs to an intranet, the intranet name displays. Sites are associated with intranets on the Sites/Entities form. 9. Click OK. The Link Multi-Site Databases screen appears again with the database added. 10. Click Next. The Review Changes screen appears. 11. Click Commit. The Configuration Results screen appears. 12. Click Finish. Post Installation Setup If you plan to use non-transactional replication, you MUST do the following things: 6-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

107 Setting Up a Multi-Site Environment 1. Set up the Web Server components on the utility server. See Chapter 9, Setting Up the Web Server" for information on how to install and configure these components. 2. Make sure the MAPICS Replication Listener and MAPICS Replicator services are started on the utility server. 3. On the General tab of the Intranets form, make sure Private Queue is selected. 4. On the Site User Map tab of the Sites/Entities form, complete the From Site and User Name fields for each site. The user name must be the same at both the source and target sites. After you get all your server machines and a client set up, you can enter SyteLine ERP and set the parameters for your multi-site environment. See the SyteLine ERP 7 System Administration Guide for more information about multi-site environments. Create a Multi-site Test Environment Before you "go live" with a multi-site environment, you may wish to set up a test environment with your company's data. Follow the steps below to set up a multi-site test environment: 1. Use backup/restore to create new application and forms databases with unique names for each site. You can use the live forms database and only backup/restore the application databases for each site if you wish, but any form customizations you make are then applied to both your live and test environments. 2. Create configurations pointing to the test sites with ClientConfigurationManager at Start>Programs>MAPICS>Tools>ClientConfigurationManager. You can use ConfigManager instead, if you purchased source code. 3. Log in to the new configurations and on each site, enter the new licenses that match the new names (and possibly different database server names) for the test databases. 4. On each site, open the Sites/Entities form and change the database names for each site (you will need to also change the database server names on the Live Linked Sites tab, if the test databases are on a different server). 5. On each site, open the Replication Management form and click the Regenerate Replication Triggers button MAPICS, Inc. SyteLine ERP 7 Installation Guide 6-7

108 Setting Up a Multi-Site Environment 6-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

109 7 Setting Up a Developer Environment You must have purchased the developer code to proceed with the steps in this chapter. The developer code comes on its own CD. Set up a developer environment after you have already set up your SyteLine ERP 7 system. There are two pieces to the developer installation: Database installation - This piece goes on the SyteLine ERP 7 database server. Client installation - This piece goes on a client machine. We recommend that you put this on an administrative client and not an end user client. Install SyteLine ERP Developer on Database Server 1. Insert the SyteLine ERP Developer CD into the CD-ROM drive of the database server machine MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-1

110 Setting Up a Developer Environment 2. After a few seconds, the initial SyteLine ERP Developer install screen appears. If it doesn t appear, access the CD-ROM drive and double click Setup. 3. Select Database and click the Install SyteLine ERP Developer 7.03 button. 4. The Welcome screen appears. 7-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

111 5. Click Next. The Custom Setup screen appears. Setting Up a Developer Environment 6. Click Next. The Ready to Install the Program screen appears. 7. Click Install. The InstallShield Wizard Complete screen appears. 8. Click Finish. Configure SyteLine ERP Developer on Database Server Once the installation completes, run the SyteLine Configuration Wizard MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-3

112 Setting Up a Developer Environment 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. The Introduction screen appears. 2. Select Setup a new SyteLine Database Environment. 7-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

113 Setting Up a Developer Environment 3. Click Next. The Choose Database Setup Tasks screen appears. 4. Clear everything except SyteLine Objects Database MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-5

114 Setting Up a Developer Environment 5. Click Next. The Temporary Folder Location for Database Creation screen appears. 6. Accept the default location for temporary files or click the browse button to choose another location. Make sure the drive you choose has enough space. 7-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

115 Setting Up a Developer Environment 7. Click Next. The Create Objects Database screen appears. 8. Enter the following information: Server Name - The server name is the local machine and can not be changed. Database Name - Enter the name you want to give the SyteLine Objects Database. sa Logon - sa is defaulted here and can not be changed. sa Password - Enter the sa password. Data File Location - Accept the default path or browse to select the location for the objects database data file. Log File Location - Accept the default path or browse to select the location for the objects database log file. 9. Click Next. The Review Changes screen appears. 10. Verify that the information is correct, and click Commit. 11. Once the configuration is complete, click Finish MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-7

116 Setting Up a Developer Environment Install SyteLine ERP Developer on a Client 1. Insert the SyteLine ERP Developer CD into the CD-ROM drive of the client machine. 2. After a few seconds, the initial SyteLine ERP Developer install screen appears. If it doesn t appear, access the CD-ROM drive and double click Setup. 3. Select Client and click the Install SyteLine ERP Developer 7.03 button. 4. The Welcome screen appears. 7-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

117 5. Click Next. The Custom Setup screen appears. Setting Up a Developer Environment 6. Click Next. The Ready to Install the Program screen appears. 7. Click Install. The InstallShield Wizard Completed screen appears. 8. Click Finish. Configure SyteLine ERP Developer on a Client Once the installation completes, run the SyteLine Configuration Wizard. 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. The Introduction screen appears MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-9

118 Setting Up a Developer Environment 2. Click Next. The Configure the SyteLine Client? screen appears. 3. Select the Configure the SyteLine Client? field SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

119 Setting Up a Developer Environment 4. Click Next. The Session Server Settings screen appears. 5. Clear the Uses COM+ Connection field. This forces the IDOs to be placed on the local machine where you need them in a developer environment. If you check the field, the IDOs are placed on the utility server MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-11

120 Setting Up a Developer Environment 6. Click Next. The Choose Client Configurations to Create/Modify screen appears. 7. Click New or Rename to create a new configuration. We chose SyteLineDev as the configuration name. SyteLineDev will appear in the title of most of the remaining screens. If you have more than one Configuration Name listed on this screen, the SyteLine Configuration Wizard will take you through screens to configure all the names listed. For the purposes of this manual, we used only one configuration name SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

121 Setting Up a Developer Environment 8. Click Next. The Application Database Information for SyteLineDev screen appears. 9. Enter the following information: Server Name - Select the name of the server where the application database resides; usually the database server. Server Logon - Enter the security logon; (example, sa ) Security Password - Enter the security password. Application Database - Select the name of the application database on the database server MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-13

122 Setting Up a Developer Environment 10. Click Next. The Forms Database Information for SyteLineDev screen appears. 11. Enter the following information: Server Name - Select the name of the server where the forms database resides; usually the database server. Server Logon - Enter the security logon; (example, sa ) Security Password - Enter the security password. Forms Database - Select the name of the forms database on the database server SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

123 Setting Up a Developer Environment 12. Click Next. The Templates Database Information for SyteLineDev screen appears. 13. If you did not create a templates database on the database server, clear all the fields on this screen. Otherwise, enter the following information: Server Name - Select the name of the server where the templates database resides; usually the database server. Server Logon - Enter the security logon; (example, sa ) Security Password - Enter the security password. Templates Database - Select the name of the templates database on the database server MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-15

124 Setting Up a Developer Environment 14. Click Next. The Production Forms Database Information for SyteLineDev screen appears. 15. This screen is used only if you are using FormControl. We do not recommend that you use FormControl with existing MAPICS applications such as SyteLine ERP. Clear all the fields SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

125 Setting Up a Developer Environment 16. Click Next. The Production Templates Database Information for SyteLineDev screen appears. 17. This screen is used only if you are using FormControl. We do not recommend that you use FormControl with existing MAPICS applications such as SyteLine ERP. Clear all the fields MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-17

126 Setting Up a Developer Environment 18. Click Next. The Archived Forms Database Information for SyteLineDev screen appears. 19. This screen is used only if you are using FormControl. We do not recommend that you use FormControl with existing MAPICS applications such as SyteLine ERP. Clear all the fields SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

127 Setting Up a Developer Environment 20. Click Next. The Archived Templates Database Information for SyteLineDev screen appears. 21. This screen is used only if you are using FormControl. We do not recommend that you use FormControl with existing MAPICS applications such as SyteLine ERP. Clear all the fields MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-19

128 Setting Up a Developer Environment 22. Click Next. The Objects Database Information for SyteLineDev screen appears. 23. Enter the following information: Server Name - Select the name of the server where the objects database resides; usually the database server. Server Logon - Enter the security logon; (example, sa ) Security Password - Enter the security password. Objects Database - Select the name of the objects database on the database server SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

129 Setting Up a Developer Environment 24. Click Next. The ObjectStudio Information for SyteLineDev screen appears. 25. Enter or browse to the Local Projects Directory. This is the directory where IDO projects are built. All source code files generated by ObjectStudio for a project are placed in a subdirectory in the local projects directory 26. Select the Visual SourceSafe Enabled? field if you are using Microsoft s Visual SourceSafe version control system. It is not required that you use Visual SourceSafe. 27. Leave the Autobuild Projects Directory field blank MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-21

130 Setting Up a Developer Environment 28. Click Next. The Form Control Information for SyteLineDev screen appears. 29. Clear the Visual SourceSafe Enabled? field. This screen is used only if you are using FormControl. We do not recommend that you use FormControl with existing MAPICS applications such as SyteLine ERP. Clear all the fields SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

131 Setting Up a Developer Environment 30. Click Next. The Visual SourceSafe Information for SyteLineDev screen appears. 31. If you are using Microsoft s Visual SourceSafe version control system, enter the following information: Server Name - Enter or browse to the srcsafe.ini file. VSS Logon - Enter the Visual SourceSafe logon. VSS Password - Enter the Visual SourceSafe password. 32. Click Next. The Review Changes screen appears. 33. Verify that the information is correct and click Commit. 34. The Configuration Results screen appears. 35. Click Finish MAPICS, Inc. SyteLine ERP 7 Installation Guide 7-23

132 Setting Up a Developer Environment 7-24 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

133 8 Setting Up the Planning Server The Planning Server components support the SyteLine Planning activity and Get ATP/CTP functions, which are features associated with the SyteLine MRP and APS modules. Requirements The Planning Server must have SQL Client Tools installed. If the Planning Server is on a Windows Server 2003 machine, you must configure the machine as an Application Server role. Install the Planning Server Components Follow these steps to install the Planning Server components: 1. Insert the SyteLine ERP CD into the CD-ROM drive of the Planning Server machine. 2. After a few seconds, the initial SyteLine ERP install screen appears. If it doesn t appear, access the CD-ROM drive and double click Setup MAPICS, Inc. SyteLine ERP 7 Installation Guide 8-1

134 Setting Up the Planning Server 3. In the Select a Configuration Type field, select Planning Server. 4. Click Install SyteLine ERP. The Welcome to the InstallShield Wizard for MAPICS SyteLine ERP screen appears. 8-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

135 5. Click Next. The Custom Setup screen appears. Setting Up the Planning Server 6. Make sure the Planning Server component is selected and click Next. The Ready to Install the Program screen appears. 7. Click Install to begin installing the Planning Server components. 8. Click Finish to complete the installation. Creating and Starting ERDB Databases An Entity Relation Database (ERDB) must be installed and running before you can run the Planning activity or use the Get ATP/CTP functions. Use the Planner Manager to create and start ERDBs. If you plan to use the Analyzer to analyze multiple sets of data (each set of data is called an "alternative"), you must create and start a separate ERDB for each alternative. You create the alternative records in SyteLine on the Planning Parameters form, on the Sites tab MAPICS, Inc. SyteLine ERP 7 Installation Guide 8-3

136 Setting Up the Planning Server For more information about the Planner Manager commands, see the Planner Manager Online Help. Do NOT perform these steps through a Remote Desktop Connection. 1. Start the Planner Manager utility. Select Start>Programs>MAPICS>Tools>Planner Manager from the Windows Start menu. The Planner Manager appears. 2. Click the Start button in the Database Manager section of the screen to start the Database Manager. 3. Click the Create button in the Databases section of the screen to create a new database. 8-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

137 Setting Up the Planning Server 4. Enter a name for the new database and click the Create button. A Command Prompt windows displays and prompts you to press a key to continue. 5. Press any key to finish creating the database. The database name appears in the list with the status "Not Started" and a blank server port. You will specify the server port later when you start the database. The names of the databases are not case-sensitive, so the Planner Manager does not allow you to create a database called "Demo" if a database called "demo" already exists. 6. Select the new database in the list and click the Start button. The Specify Start Parameters dialog appears. 7. In the Port Number field, enter an unused port number for this database to run on. The system limits this selection to ports between 5000 and 65000, to avoid conflicts with ports already in use. If you are starting the database for the first time, you don t need to select anything in the Option field; the database starts empty automatically. You should always start the database empty because it is populated automatically from the SyteLine application database MAPICS, Inc. SyteLine ERP 7 Installation Guide 8-5

138 Setting Up the Planning Server 8. Click the Start button to start the database. A Command Prompt windows appears, prompting you to press any key to continue. 9. Press any key to complete the process. For each ERDB you start, a minimized Command Prompt window appears on your Windows taskbar. Do NOT close the minimized Command Prompt windows for the ERDBs you start. Allocating Memory for the Database Do not continue with this section until after you have completely set up the SyteLine system. Your SyteLine database must be populated with your production data and the SyteLine reporting feature must be set up before you can perform these steps correctly. The ERDB database runs in the Planning server s memory. Each database field requires a certain memory depth (the number of records that can be stored for a field) and width (the largest length of an identifier for a record). The ERDB sizing process consists of getting an estimate of the required depth and width settings for the fields in the ERDB schema and entering those settings into the schema file. Then, after completing the steps in this section, you may continue to Fine-Tuning the Memory Allocation for Depth to obtain a report of your exact memory usage (which allows you to fine-tune your depth settings). Generate the Depth and Width Requirements Use the MRP-APS Sizing Report to generate a list of memory requirements for your data. This report examines the data in your SyteLine application database and provides a memory depth and/or width estimate for each corresponding ERDB database field. The report inflates these statistics by the value you specify in the Database Inflation Factor on the Planning Parameters form. The default inflation is 20%. This inflation allows for growth in your data. 8-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

139 Setting Up the Planning Server To generate the MRP-APS Sizing Report: 1. After installing all SyteLine components, start SyteLine on any client workstation. This procedure assumes your SyteLine database is already populated, and you have created and started your empty ERDB database as described in the previous section. 2. Navigate to the MRP-APS Sizing Report form. See the "Printing a Report" help topic in the SyteLine online help for steps you must complete to print a report. 3. Click the Print button to generate the report. The statistics are presented in this format: 4. Continue on to the next section to make the necessary changes to the ERDB database s schema file to support these requirements. Enter the Depth and Width Settings 1. Each ERDB database uses a separate schema file named ol_schema.txt. The schema files are located on the server where you installed the Planning server components, in the Program Files\MAPICS\Planner\projects\<database name>\ol_dba\ol_cfg folder. In a separate window or instance of your text editor, open the ol_schema.txt file for the database you are working with. You must make the changes in the ol_schema.txt file for each existing ERDB. You should also make the schema changes in the "master" ol_schema.txt file, located in the \dbt\ol_dba\ol_cfg subdirectory. If you modify this master version of the database schema, all future ERDBs you create will use those sizing settings (unless you then change the individual schema files). 2. In the ol_schema.txt file, notice the lines that have a c=<value> and d=<value> statement (shown in bold below). For example: n=part t=ke, f=c, c=31, d=100 cr 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 8-7

140 Setting Up the Planning Server In this example, the depth value (d=100) represents the maximum number of part records your database can contain. The character width value (c=31) represents the character width of the largest part number your database can contain. 3. In the MRP-APS Sizing Report, note the requirements for each field. For example, the Part field s statistics might look like this: Max Width: 32 Actual Width: 32 Depth: 217 The reported character width requirement for the Part field is actually one character larger than your database actually needs this extra character accounts for a character the system reserves. 4. Return to the ol_schema.txt file and enter the reported depth value requirement in the d= statement. For example: n=part t=ke, f=c, c=31, d=250 cr Add some buffer to the required depth value to allow for any future growth in your database (you can increase this value later as necessary). The reported depth value represents the estimated space needed at this time. If any records are added above that value, the Planning activity will abort and display an error message. 5. Enter the reported width value requirement in the c= statement. For example: n=part t=ke, f=c, c=40, d=200 cr The maximum character width for any field is 80. If you have a field that requires more than 80 characters, the system truncates the field. This situation may cause "duplicate key" errors during the Planning activity. 6. Repeat steps 3-5 for each field that is listed with a depth and/or character width requirement in the aps.err file. If a field is not listed in the sizing report, leave it unchanged (SyteLine does not use it). 7. Save the ol_schema.txt file. 8-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

141 Setting Up the Planning Server 8. Now you must find out how large the shared memory partition on the APS database server must be to contain your database. On the server where the Planning server components are installed, open a Command Prompt (Start>Programs>Accessories>Command Prompt). 9. Navigate to the \Program Files\MAPICS\Planner\projects\<database name>\ol_dba\ol_cfg directory. 10. Enter this command: rdmbuild sz=ol_schema.txt, ex 11. The information this command returns looks something like this: 135 data dictionary entries required total bytes user defined bytes = 39.63% RdmBuild done. The "total bytes" figure corresponds to the size figure in the header of the ol_schema.txt file: size=<value>,*size of shared memory segment 12. Round up the total bytes figure to the nearest MB and enter that figure in the size=<value> statement in the ol_schema.txt file. 13. Save the ol_schema.txt file and restart the ERDB database (use the Planner Manager program to restart the database with the Start Empty option). If you saved the database before modifying the schema, you can now use the Restore function in the Planner Manager to restore your database. 14. To populate your ERDB database, run the Planning activity in SyteLine. If any fields still have insufficient memory allocated, the system generates an error message (viewable on the Background Task History form). A more detailed version of the message may also appear in the ERRORLOG table in the SyteLine application database. For example, the message might look like this: "Unable assign a priority to site <site name>]". Fine-Tuning the Memory Allocation for Depth The estimated memory allocation suggested by the MRP-APS Sizing Report may be sufficient for your needs. However, this report provides only an estimate. You can get a more exact report of the depth requirements for each field by using the "rdmwh" command line utility MAPICS, Inc. SyteLine ERP 7 Installation Guide 8-9

142 Setting Up the Planning Server This utility displays a list of all the fields in the database, with the depth you have defined and the current actual usage. This information allows you to readjust the depth values to reflect the current needs of your database more accurately. If you have a large database with many users, you should do this to make sure your memory is allocated efficiently. Follow these steps: 1. After running the Planning activity, open a Command Prompt. 2. Navigate to the \Program Files\MAPICS\Planner\projects\<database name>\ol_env folder. 3. Enter this command: set ataenv=c:\program files\mapics\planner\projects\<database name>\ol_env\ol_env.txt You must reset this environment variable for each database you want to check. 4. Navigate to the \Program Files\MAPICS\Planner\bin folder. 5. Enter this command: rdmwh <refresh rate> The refresh rate is the delay in seconds before the report runs again. For example, if you want to refresh the report every 5 seconds, enter rdmwh 5. To run a single report (no refresh), enter rdmwh. A list displays, showing all the fields in the database, with the current Depth you have defined and the current actual usage. Additional Sizing Guidelines The MRP-APS Sizing Report provides a less-accurate estimate for memory depth on certain fields. For fine-tuning the memory depth allocation for these fields, use these guidelines. Field Schedule Sch22Res Res22Sch Ord22Sch Sizing Considerations Set the depth value equal to the total number of supply orders plus the estimated number of demand order work assignments. The system generates work assignments for every demand order throughout its routing/ bill of material down to the operation level. Long cycle-time operations may cross shifts to create several work assignments. If every planned work assignment will, on average, require 2 resources, set the depth equal to twice the Schedule depth. Set the depth equal to the Sch22Res depth. Set the depth equal to the Schedule depth SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

143 Setting Up the Planning Server Field Ord22SchSup Ord22PrtPur Prt22Sch OrderDashPart XfrChildren RemoteOrder Sizing Considerations Set the depth to the number of schedule events that indicate the usage of inventory from supply orders. For distribution sites, set it to around 75% of the Schedule depth. For manufacturing sites, set it to around 25% of the Schedule depth. For mixed sites, set it to 50% of the Schedule depth. Set the depth to the highest number of purchased items in a demand's exploded bill of material. The value should be the maximum number of items that might be specified as purchased (not manufactured) across all demands. Set the depth equal to the Schedule depth. Set the depth to the total number of remote orders this site will generate for component parts. For example, suppose this site has 100 end-item demands, and 50 of the orders demand a single component from a remote site and another 10 of those demands require two components from remote sites. In this example, set the depth to 70. Set the depth equal to OrderDashPart. Set the depth to the total number of remote orders, where a demand at this site will supply material to, or demand material from, the remote demand. For example, suppose this site has 100 end-item demands, 50 of which require a single component from a remote site and another 10 demand two components from a remote site. In addition, other sites make a total of 5 demands to this site for components. In this example, set the depth to MAPICS, Inc. SyteLine ERP 7 Installation Guide 8-11

144 Setting Up the Planning Server 8-12 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

145 9 Setting Up the Web Server The Web Server components support the SyteLine Analyzer application, Webbased data collection, and the http/xml and.net web service interfaces into SyteLine. The http/xml interface is used by WinStudio when configured to connect over the Internet, by the replication system when sites are on different intranets, and by the generic External Financial interface. This chapter describes how to install the Web server components and configure the Analyzer application. Requirements SQL Server 2000 Client Tools are already installed and configured on the Web server. To use the reporting features in the Analyzer client, Crystal Reports version 9 is required on the client machine where you are running the Analyzer. Microsoft Messaging Queue (MSMQ) is installed; or Message Queuing if on a Windows Server 2003 machine. If you re using Windows Server 2003 as your Web server, make sure Active Server Pages and ASP.NET v are allowed. If you configure your clients for HTTP access, install the web server on the same machine as the utility server. See Setting Up an End User Client for HTTP Access on page D-1 for installation and setup instructions. Data Collection Setup If you are using Web-based data colleciton, you must follow the steps in this chapter to install and configure the data collection Web server components MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-1

146 Setting Up the Web Server Install the Web Server Components Follow these steps to install the Web Server components: 1. Insert the SyteLine ERP CD into the CD-ROM drive of the Web Server. 2. After a few seconds, the initial SyteLine ERP install screen appears. If it doesn t appear, access the CD-ROM drive and double click Setup. 3. In the Select a Configuration Type field, select WEB Server. 9-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

147 Setting Up the Web Server 4. Click Install.NET Framework. This process launches the Microsoft.NET Framework installation. This product is needed for the SyteLine.NET Application Programming Interface. 5. Click OK after reading the informational message. 6. Click Yes when asked if you want to install the.net Framework package. The.NET Framework Setup screen appears MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-3

148 Setting Up the Web Server 7. Click Next. The.NET components begin installing. 8. Click OK at the "Installation of Microsoft.NET Framework is complete" message. If prompted to restart the machine, click No. 9. Return to the SyteLine ERP setup program screen. 10. Click the Install SyteLine ERP 7.03 button. The Welcome to the InstallShield Wizard for MAPICS SyteLine ERP screen appears. 11. Click Next. The Custom Setup screen appears. 12. Make sure the Web Server components are selected. Deselect SyteLine Configuration Database if you did not purchase SyteLine Configuration. If you need to install SyteLine Configuration, see the SyteLine Configuration Installation Guide for installation and setup instructions BEFORE installing SyteLine ERP. 13. Click Next. The Ready to Install the Program screen appears. 14. Click Install to begin installing the Web Server components. 15. Click Finish to complete the installation. 9-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

149 Configure the Web Server Components Setting Up the Web Server This procedure requires that you set up at least one planning site record on the Sites tab on the Planning Parameters form in SyteLine. See Enter SyteLine Planning Parameters on page 9-24 for steps on how to set up the planning parameters. 1. Start the SyteLine Configuration Wizard by selecting Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. The Introduction screen appears. 2. Click Next. The Configure the SyteLine Client screen appears. 3. If you will be configuring the replication virtual directory (for Web-based Data Collection) and/or the Planning and Scheduling Promiser, you must set up a local SyteLine client configuration on the Web server. Select the Configure the SyteLine Client check box. See Chapter 4, Setting Up a Client Workstation" for specific instructions. At least one client configuration on the Web server must be a local configuration. Make sure the "Uses COM+ Connection" field is cleared on the Session Server Settings screen. If you are not using these components, clear the box and continue with the steps in this chapter MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-5

150 Setting Up the Web Server 4. Click Next. The Configure the SyteLine Replication Services screen appears. 5. If you are NOT integrating this SyteLine environment with MAPICS CRM, clear the Configure SyteLine Replication Services? field. Replication Services are used in a multi-site environment and are put on the Utility Server in a non-crm implementation. If you are integrating with MAPICS CRM, you must select this field and set up replication services on this server. This process sets up the necessary registry entries for data to replicate between SyteLine and CRM. See steps on page 3-14 for detailed steps. If your SyteLine utility server is a different machine than your SyteLine Web server, you can use the same configuration information that you used when you set up replication services on the utility server. 9-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

151 Setting Up the Web Server 6. Click Next. The Configure the Planning and Scheduling Analyzer Web Server screen appears. 7. The Analyzer allows you to perform preliminary planning (with MRP or APS) and scheduling with a copy of your SyteLine application database. This ability lets you experiment with dates and capacity allocations and observe the resulting effects without making changes to your actual data. To configure the Analyzer Web and middleware components, select the Configure the Planning and Scheduling Analyzer Web Server? field. Clear the field if you want to skip the Analyzer configuration MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-7

152 Setting Up the Web Server 8. Click Next. If you chose to configure the Analyzer, the Analyzer ODBC Setup screen appears. Otherwise, continue past this screen to the next one. 9. The appropriate information may be filled in automatically. If it is not, enter or select the appropriate information as follows: Startup Page Name: the base Analyzer access page is Analyzer_SyteLine. You cannot change the name. Later, you ll use this name in the URL to connect to the Analyzer from your Web browser (for example, Analyzer_SyteLine.htm).You may create additional Analyzer pages later, for connecting to other databases. See Creating Additional Analyzer Start-Up Pages on page 9-17 for more information. Server Name: select the name of the SQL server where the SyteLine application database resides. SQL Logon ID: enter the name of the access account for the SQL server (such as "sa"). SQL Password: enter the password associated with the above SQL logon ID. Application Database: select the SyteLine application database you want this Analyzer configuration to access (such as SyteLine_App). 9-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

153 Setting Up the Web Server 10. Click Next. The Configure the Planning and Scheduling Analyzer Middleware Components screen appears. 11. The Analyzer middleware components (.dlls and other files) reside on the Web server and retrieve data from the SyteLine application database. You must configure the middleware components to use the Analyzer. To configure the middleware components, select the Configure Planning and Scheduling Analyzer Middleware Components? field. Clear the field if you want to skip configuration of the middleware components MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-9

154 Setting Up the Web Server 12. Click Next. If you chose to configure the middleware components, the Planning and Scheduling Analyzer Middleware Components screen appears. Otherwise, continue past this screen to the next one. 13. In the Network Logon for Package field, enter a domain user account. For example, MYDOMAIN\MyUserName. This user must have permissions to access the registry on the Web server, but does not necessarily require full administrator permissions. 14. In the Network Password for Package field, enter the password associated with the domain user account you entered above SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

155 Setting Up the Web Server 15. Click Next. The Configure the SyteLine Web Server? screen appears. 16. Select the Configure SyteLine Web Server Components? field MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-11

156 Setting Up the Web Server 17. Click Next. The Create SyteLine Virtual Directory screen appears. This virtual directory is used for two.asp pages used for replication and XML data transfer: <virtual_directory>/ido/sessionmanager.asp <virtual_directory>/inboundqueue.asp 18. The appropriate information for the virtual directory may be filled in automatically. If it is not, enter the virtual directory name (for example, "SL"), your DOMAIN\Username, and password SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

157 Setting Up the Web Server 19. Click Next. The Configure Data Collection Web Server? screen appears. 20. If you are using Web-based Data Collection, select the Configure Data Collection Web Server Components? field. Otherwise, clear the field MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-13

158 Setting Up the Web Server 21. Click Next. The Create Data Collection Virtual Directory screen appears. 22. The appropriate information may be filled in automatically. If it is not, enter the virtual directory name (for example, "fsdatacollection"), DOMAIN\Username, and password. You will use this virtual directory name in the URL to connect to Webbased data collection form from your data collection device. For more information, including more steps that you need to perform, see Connecting to Web-Based Data Collection on page SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

159 Setting Up the Web Server 23. Click Next. The Configure the Availability Web Service screen appears. 24. The Availability Web Service is a Microsoft.NET application. It is required for Web-based systems such as MAPICS CRM and MAPICS Intelligent Sourcer to request product availability information from MRP or APS processes in SyteLine. Select the Configure the Availability Web Service? field, or clear it and skip this screen if you are not using MAPICS CRM. You may configure the Availability Web Service using the MAPICS Supply Chain Setup Wizard or using this SyteLine ERP Configuration Wizard. You do not need to configure it in both wizards. If you configure it at this time, you must have already defined a planning site record on the Sites tab on the Planning Parameters form in SyteLine. See Enter SyteLine Planning Parameters on page 9-24 for steps on how to set up the planning parameters MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-15

160 Setting Up the Web Server 25. Click Next. The Create Availability Web Service Virtual Directory screen appears. 26. This virtual directory will be used in the URL that other applications (such as MAPICS CRM) will use to connect to MRP or APS functions through the Web. Enter or select the appropriate information: Configuration Name: select the SyteLine configuration name in the Configuration Name box with which you want the product availability requests to connect. Username for Virtual Directory Access: enter the domain and user name of the account under which the Availability Web Service will run. This user account must have access to the SyteLine application database, to the physical folder where the Web service files are located (most likely C:\Program Files\MAPICS\Components\SupplyChain\WebService\ApsPromiser\ Bin), and to the C:\Winnt\Temp folder. Password: enter the password associated with the user account you specified above. 27. Click Next. The Review Changes screen appears. 28. Verify that the information is correct and click Commit. 29. Once the configuration is complete, click Finish SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

161 Setting Up the Web Server Creating Additional Analyzer Start-Up Pages If you have more than one SyteLine application database at a given site that you want to be accessible from the Analyzer, follow these steps to create a separate Analyzer configuration for each database (for example, you might want one configuration to analyze demo data and one to analyze your production data). 1. On the Web server, select Start>Programs>MAPICS>Setup>Analyzer Configuration. The Analyzer Configuration screen displays MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-17

162 Setting Up the Web Server 2. Click Create New Analyzer Configuration. The Create New Analyzer Configuration screen displays. 3. Enter appropriate information in the fields as follows: Start-Up Page Name: Enter a name for this Analyzer configuration, such as "Analyzer_Demo." Later, you ll use this name in the URL to connect to the Analyzer from your Web browser (for example, mywebserver/analyzer/analyzer_demo.htm). SQL Server: Select the name of the SQL server where the database you want to connect to is installed. SQL User: Enter the name of the access account for the SQL server (such as "sa"). SQL Password: Enter the password associated with the SQL user. Confirm Password: Enter the SQL password again to confirm. Database: Select the database you want this Analyzer configuration to use. Data Source Name: Enter a name for the ODBC connection to create for this Analyzer configuration (use the same name as the start-up page). The form fills in this name automatically. Registry Key: Enter a registry key name for the ODBC connection (use the same name as the start-up page). The form fills in this name automatically. Connection Timeout: Use the default value of 60 seconds SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

163 Setting Up the Web Server 4. Click Create. Click OK when the success message displays. 5. Close the Analyzer Configuration screen. Install and Configure Analyzer Clients Before you can run the Analyzer on a client machine, you must install and configure the Analyzer client components. To use the reporting features in the Analyzer client, Crystal Reports version 9 is also required on the client machine. Perform these procedures on each client machine that will run the Analyzer application. The Analyzer is an intranet application and cannot be accessed over the Internet. The server components and clients must be able to establish communication using the Microsoft Distributed Component Object Model (DCOM), which means that the clients and Web server must be on the same private business network. Installing the Analyzer Client 1. Insert the SyteLine ERP CD into the CD-ROM drive of the client machine. After a few seconds, the initial SyteLine ERP install screen appears. If it doesn t appear, access the CD-ROM drive and double click Setup MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-19

164 Setting Up the Web Server 2. In the Select a Configuration Type field, select Client. 3. In the Select a Client Type field, select Analyzer Client SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

165 Setting Up the Web Server 4. Click the Install SyteLine ERP 7.03 button. The Welcome to the InstallShield Wizard for MAPICS SyteLine ERP screen appears. 5. Click Next. The Custom Setup screen appears. 6. Verify that the Analyzer Client option is selected and click Next. The Ready to Install the Program screen appears. 7. Click Install. After the files have been installed, the InstallShield Wizard Completed screen appears. 8. Click Finish to complete the process. Configuring the Analyzer Client If you installed the Analyzer client components on the same server where you installed the Web server components, skip this section. 1. Select Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard. The Introduction screen appears MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-21

166 Setting Up the Web Server 2. Click Next. The Configure Planning and Scheduling Analyzer Client? screen appears. 3. Make sure the Configure Analyzer Client? field is selected SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

167 Setting Up the Web Server 4. Click Next. The Analyzer Client Web Server screen appears. 5. In the Analyzer Client Web Server field, select the name of the server where the Analyzer Web server components reside. 6. Click Next. The Review Changes screen appears. 7. Click Commit to start the configuration process. After the client middleware package has been installed, the Configuration Results screen appears. 8. Click Finish to complete the process. Configure Permissions for the Gantt Chart To use certain features of the Gantt Chart screen in the Analyzer, you must allow Full Control access to the C:\Program Files\MAPICS\SyteLine\Analyzer\ReportFiles\Gantt.mdb file, for any user account that needs to use the Gantt Chart screens. Configure these permissions on each Analyzer client machine as described in Configure Permissions for Resource Gantt Charts on page MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-23

168 Setting Up the Web Server Enter SyteLine Planning Parameters The Analyzer requires at least one Site record to be present in the SyteLine Planning Parameters. 1. On a machine in your environment where the SyteLine client software is set up, start a client session that connects to the SyteLine application database associated with this Analyzer configuration. 2. Navigate to the Planning Parameters form. 3. Select the Sites tab. 4. Enter appropriate data in these fields: Alternative: Enter 0. Alternative 0 is the container for your actual production SyteLine data. If you plan to use the Analyzer to analyze one or more scenarios with copies of your production data, you must create additional alternative records (alternative 1, 2, and so on). You may not edit data within alternative 0 in the Analyzer. The alternative 0 data is read-only in the Analyzer. Planning Site: Enter a site name for this site (even if you're not using multi-site, you still need at least one site record for each alternative). Priority: This is the priority sequence in which sites will be replanned during a global multi-site planner run. The sites with the lowest numerical priority values are planned first (0 is lowest). For example, enter 0. Type: Enter Local. If you are setting up a multi-site planning environment, see the SyteLine online help for instructions on how many "Remote" sites you need to represent. Planning Host Name: Enter the name of the server where you installed the Planning and Scheduling Service (probably the Utility server). Planning Port: Enter the port number you used when you configured the Planning and Scheduling Service SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

169 Setting Up the Web Server ERDB Host Name: Enter the name of the server where you installed the "Planning Server" components (the machine where the ERDB database is running). ERDB Port: Enter the port number where you started your ERDB database in Setting Up the Planning Server on page 8-1. SQL Host Name: Enter the name of the server where the SyteLine application database is installed. SQL Database Name: Enter the name of the SyteLine application database. Timeout: Enter 60 (seconds). This is the time-out value for contacting remote sites during a multi-site planning activity. 5. Select Actions>Save to save the parameters. Test the Analyzer Connection You may now test the Analyzer. On the client machine, navigate to in Internet Explorer. The Analyzer application may take a few moments to load. Troubleshooting the Analyzer Most of these errors occur when you try to launch the Analyzer Web page. Some errors also log additional information in the Event Viewer on the Web server that hosts the Middleware and Web components. To access the Event Viewer, select Start/Programs>Control Panel>Administrative Tools>Event Viewer. Error Message/Symptom "Error accessing database 'Default'. See the event viewer on the middleware server for additional details." Web Server: "Data source name not found and no default driver specified. Microsoft OLE DB Provider for ODBC Drivers." Explanation/Solution Possible Cause A: The data source name has not been entered correctly in the registry. Select Start>Run and type regedit. Search for the Analyzer\Database\Default folder. Double-click on the key DSN. The value should be the name of the ODBC datasource name set up for the Analyzer in the ODBC administrator. If the registry entry is correct, see cause B below. Possible Cause B: An ODBC datasource has not been defined for the Analyzer in the ODBC administrator MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-25

170 Setting Up the Web Server Error Message/Symptom "Error accessing database 'Default'. See the event viewer on the middleware server for additional details." Web Server: "Specified SQL server not found. Microsoft OLE DB Provider for ODBC Drivers." "Error accessing database 'Default'. See the event viewer on the middleware server for additional details." Web Server: "Could not find stored procedure 'ApsGetStringsByListIDSp'. Microsoft OLE DB Provider for ODBC Drivers." "Run-time error '429' ActiveX component cannot create object." May be in combination with a blank screen with a dot in the left hand corner of the browser. Web Server: N/A "There are no free planning alternatives. Unable to copy." (Happens while trying to copy the base alternative to a new alternative on the Analyzer alternatives view.) Web Server: N/A Explanation/Solution Cause: The SQL Server is down. Check the status of the SQL Server and restart it if necessary. Cause: The ODBC datasource does not point to the SyteLine application database. Select Start>Settings>Control Panel and double-click the Data Sources (ODBC) icon. Select the System DSNs tab and select the Analyzer DSN. Click the Configure button and proceed through the wizard until you see the "Change the default database to" field. Verify that the correct database is specified. Cause: The application proxy RSN value may contain blank spaces. When you downloaded the Client Package from the admin.htm page, a file was created at C:\Program Files\ComPlus Application\"Long QUID Value". You may have multiple QUID values. Locate the QUID, which contains several APS TLB files. Using regedit on client machine, search for the "Long QUID Value" in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ appid. There should be two registry key entries: RemoteServerName and RunAS. If the RemoteServerName is blank, do the following: Uninstall the Application Proxy on the client machine. On the Web server, delete the export package from the \Inetpub\wwwroot\analyzer\bin directory (apsv50msi & apsv50msi.cab). In Component Services, delete the APSV50 com application. Right-click on the My Computer listing, select Properties, and then select the Options tab. Set the focus on Application proxy RSN field. Make sure the field does not contain spaces (delete any values in the field). Run the analyzer Middleware Setup utility and then reinstall the export package on the client machines. You cannot copy data to a planning alternative to which you have previously copied data. In the Analyzer alternatives view, delete the alternative you are trying to copy data to and try again SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

171 Setting Up the Web Server Error Message/Symptom "Unable to create middleware object" (followed by error code 876). Browser background is blue w/ portion of the navigation bar visible. Web Server: "The run-time environment was unable to initialize for transactions required to support transactional components. Make sure that MSDTC is running." "Visual Basic Run Time Error." Web Server: "Cannot open database requested in login ' '. Login fails. Microsoft OLE DB Provider for ODBC Drivers." "Visual Basic Run Time Error." Web Server: "Error in GetSiteList: 429- ActiveX component can't create object AltUtil.AlternativeInfo." Any general problems with copying alternatives. The Web browser shows only a white screen with a small gray box in the corner. Web Server: N/A Explanation/Solution Possible Cause A: The Analyzer client and/or middleware server are not installed on a domain. All clients and the middleware server must be installed on a domain. Possible Cause B: The MSDTC service is not running on the Web server. To start the MSDTC service, select Start/Settings/ Control Panel and double-click the Services icon. Find the MSDTC service and click the Start button. You should change this service to start automatically (select the service, click the Startup button, and select Automatic). Cause: The SyteLine application database is not specified in the APSSITE table in the SyteLine Application database. Use SQL Server Enterprise Manager to open the APSSITE table in the application database and verify that the SQLDBNAME field is defined correctly. SyteLine populates this field from the value you enter in the SQL Database Name field on the Planning Parameters form. Cause: The Site ID specified in the APSSITE table of the SyteLine Application database may contain leading spaces. Use SQL Server Enterprise Manager to check the Site ID. If the Site ID contains spaces at the beginning of the value, you must reenter the entire record for this site in the APSSITE table. The copy dataset function writes temporary files to the c:\temp folder by default (you can specify a different folder when you start the Planning and Scheduling Server Service). Check to make sure this folder allows full local administrator access. Cause: The Analyzer Client components have not been configured correctly. Check the Add/Remove Programs list (Start/ Control Panel/ Add/Remove Programs) for the presence of: APS Analyzer: client components Remote Application - APSV50 (remove only): client package If one of these components is missing from the list of programs, rerun the Analyzer Client Configuration process MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-27

172 Setting Up the Web Server Connecting to Web-Based Data Collection If you re using Windows Server 2003 as your Web server, go to the Virtual Directory created for DC (fsdatacollection), right click it and select Properties, click on the Configuration button, select the App Options tab and make sure that Enable parent paths is selected. If you run into connection timeout errors (Server.Execute failed), you may need to increase the connection timeout setting on your web server machine. Within the Internet Services Manager, select your Web Server in the left pane, then select the DC Web site in the right pane and right-click on it. Select Properties. Select the Web Site tab. Increase the Connection Timeout, and make sure that HTTP Keep-Alives Enabled is selected. Use the name of the data collection virtual directory installed previously in the URL to connect to Web-based data collection from your specific device. For example, enter login.asp?browser=stylesheetname, where stylesheetname is the name of the specific style sheet used. Enter one of the values below in the URL to use that stylesheet. The Web-based data collection style sheets are installed on the Web server at C:\INETPUB\wwwroot\fsDataCollection\Web, which contains the following subdirectories. Subdirectory Style Sheet Name Description For TRAKKER 2425 with Intermec dcbrowser. Wedge Wedge For a wedge reader running Internet Explorer with barcode data entry. Default Default For a wedge reader running Internet Explorer with barcode data entry and keyboard data entry. For instance, use the URL datacollectionvirtualdirectoryname/login.asp?browser=default to connect with the default style sheet SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

173 Setting Up the Web Server You can also create a custom xml menu file for each user. If you do so, you must enter the name of the XML menu file for each user in the Web DC Menu field on the Users form. This field defaults to * (asterisk), which uses the standard XML menu file (Menu.xml). This file is installed on the web server at: C:\Inetpub\wwwroot\FSDataCollection\Web\Wedge\Menu\Menu.xml. See the online help for this field for more information. You can use any Web-based data collection device that supports Internet Explorer or Intermec dcbrowser. You may need to modify a provided stylesheet or create your own depending on your specific hardware requirements. Refer to the documentation for your data collection device for more information. See the TRAKKER Antares Reader Installation Guide (at support.mapics.com) for more information on using the TRAKKER 2425 with Intermec dc Browser. On the MAPICS support web site ( support.mapics.com), perform the following steps: 1. Login. 2. Select the radio button to Load the SyteLine menu. 3. Click OK. 4. Click the link for Product documentation. 5. Follow the links to the version of SyteLine Data Collection you want, and there you will find the TRAKKER Antares Reader Installation Guide MAPICS, Inc. SyteLine ERP 7 Installation Guide 9-29

174 Setting Up the Web Server 9-30 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

175 10 Upgrading a SyteLine Application Database This chapter contains information that may or may not apply to your specific situation, and each section (Service Packs, Database Upgrade utility, FormSync) is prefaced with the conditions under which you would need to perform the steps in that section. The sections are listed in the order in which the operation should be performed. If a certain section does not apply to your situation, skip to the next section. Before you upgrade to a new version, make sure you do not have bad data such as duplicate language codes; otherwise, the upgrade will fail. If you have a version of SyteLine ERP 7 and want to upgrade to another version of SyteLine ERP 7 (for example, from SyteLine ERP 7.02 to SyteLine ERP 7.03), you MUST uninstall the old version before installing the new version. This is true for all pieces of your system; the database server, utility server, all clients, planning server, web server, and exchange components. See Uninstalling SyteLine ERP on page 13-1 for uninstall instructions. Before performing an upgrade, make sure to back up your database. The upgrade process will NOT result in a loss of data. This chapter contains information on the following: SyteLine ERP Service Packs - The latest service pack MUST be installed BEFORE running the Database Upgrade utility. Database Upgrade Utility - Use this utility to upgrade your SyteLine application database from an earlier point release to a later one. For example, if you need to upgrade your database from 7.01 to 7.03, you need to run the Database Upgrade utility. FormSync - Perform this only if you made form customizations that you want to preserve MAPICS, Inc. SyteLine ERP 7 Installation Guide 10-1

176 Upgrading a SyteLine Application Database Requirements You must back up your SyteLine application database before running the Database Upgrade utility. All users must be out of the system before running the Database Upgrade utility. The target SyteLine version is already installed along with upgrade module on the database server. See Chapter 2, Setting Up the Database Server" for instructions on how to install SyteLine on the database server and how to install this upgrade utility. You must apply the latest service pack prior to running the upgrade process. You have modified stored procedures, triggers, and functions in accordance with the approved method. You will create a new Sp/Trig/ Func and not modify base code. Init data has been customized in accordance with the approved method. Init data does not need to be re-installed after upgrade. Custom modifications and add-on packages (SyteLine/CRM Integration for example) must be reinstalled after the upgrade. Service Packs The Service Pack application process does not affect the objects database. To apply changes to the objects database, see Apply Changes to Objects Database on page 10-5 AFTER you have applied the current service pack. All clients must be updated any time the client toolset is changed. To see if the client toolset has changed, refer to the readme file for the service pack you are applying on the SyteLine ERP Installation Advisory and Software Patches web page. Once you install a service pack, it cannot be uninstalled. If you installed your SyteLine ERP system from the CD and not a network location, you will be prompted to place the CD in the machine on which you are applying a service pack. If you did not install SyteLine ERP from the CD, and the location of the files is the same as it was when you installed, you will not be prompted for the CD SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

177 Upgrading a SyteLine Application Database Multiple Service Pack Installs The maximum number of Service Pack versions you can span in a single upgrade is twenty five (25). This means that your currently installed Service Pack versions must be within 25 or less of the Service Pack you are planning to install. To ensure that you have the ability to upgrade from any Service Pack level to the latest Service Pack, MAPICS will always provide the latest Service Pack and all service packs that are multiples of 25 as needed. If you are more than 25 Service Packs behind, you will be required to upgrade to one or more of the prior Service Packs to bring your system to a Service Pack level that is within the 25 Service Pack range of the latest Service Pack. For example: Only the latest Service Pack will be provided until we reach Service Pack 25. Service Pack 25 and the latest Service Pack will be provided until we reach Service Pack 50. Service Pack 25, 50 and the latest Service Pack will be provided until we reach Service pack 75, etc. To upgrade from Service Pack 10 to Service Pack 43, for example, is a jump greater than 25, so a double step is required. You would first upgrade from Service Pack 10 to Service Pack 25 (a jump of 15), then you would upgrade directly from Service Pack 25 to Service Pack 43 (a jump of 18). Apply Service Pack You are only required to perform multiple upgrades if your current system is more than 25 Service Pack levels lower than the most current Service Pack version. Before beginning this process, everyone MUST be logged out of the system. Service Packs for SyteLine ERP 7 are available from our website at support.mapics.com/. Once there, perform the following steps to find the service pack: 1. Login. 2. Select the radio button to Load the SyteLine menu. 3. Click OK. 4. Click Installation Advisories/Software Patches MAPICS, Inc. SyteLine ERP 7 Installation Guide 10-3

178 Upgrading a SyteLine Application Database 5. In the left pane under Support, click Installation Advisories/Software Patches. 6. Choose SyteLine. 7. Click the link to the SyteLine area for which you need a patch. After you apply the service pack, your task is not complete. You MUST run the SyteLine Configuration Wizard as detailed below. If you only apply the service pack (run the executable) but do not then run the SyteLine Configuration Wizard, users will not be able to log into the system. To apply the service pack, perform the following steps: 1. Log everyone out of the system. 2. Download the latest appropriate service pack from our website. The three executable files are: SPnumber_MAPICS_SyteLine_ERP_Developer - If you have installed developer code, run this on the database server and on any developer client machines. SPnumber_MAPICS_SyteLine_ERP_Migration - Run this on the database server only if you installed SyteLine ERP Migration components. SPnumber_MAPICS_SyteLine_ERP - Run this on all servers and clients. 3. Double-click the executable on the appropriate server and/or client. 4. The Installation Wizard launches. This part of the process varies depending on which server or client you are on. Depending on how your SyteLine ERP system was installed, you may be prompted here for the SyteLine ERP CD. Follow the prompts until the wizard is complete. On the utility server, web server, and planning server, you are prompted to reboot after running the service pack. You MUST do this. We recommend you also reboot the client machine before continuing SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

179 Upgrading a SyteLine Application Database 5. Run the SyteLine Configuration Wizard (Start>Programs>MAPICS>Setup>SyteLine Configuration Wizard) on each client and server where a service pack was applied. Follow the prompts until the wizard is complete. When you apply the service pack on the database server, updates are made but NOT to the databases. Databases are updated when you apply the service pack on the utility server. On the utility server, when you run the SyteLine Configuration Wizard, you have the option to apply the service pack to individual databases or not. Apply Changes to Objects Database Perform the steps in this section only if you have a developer environment in which you made changes to IDOs or created IDOs. When you apply a service pack, it does not apply to the objects database. In order to realize any updates to IDOs, you must complete the following steps after you have applied the service pack. The first step below tells you to delete all updated IDOs. If you made any modifications to an IDO, make sure you are aware of all the modifications you made before you delete it. If you want to keep the modifications you made to the IDO, you need to modify the IDO again after you follow the steps below. 1. Delete the appropriate IDOs from your database; these would be IDOs that MAPICS updated and included in the latest service pack. You can tell which IDOs to delete because there is an XML file with a similar name in the same folder for each updated IDO. For example, the XML file is named <idoname>.xml, so you can just delete that IDO. 2. After you have deleted all the IDOs, save the project. 3. Use Object Studio to import the new IDO definitions from the XML export file. Within Object Studio, choose Project>Import Wizard, and then follow the steps in the wizard. 4. Regenerate source code for the imported IDOs. Select each imported IDO in the tree view and choose Tools>Generate Source>Current IDO from the Tools menu. 5. Check in the imported IDOs. Right-click the IDO in the tree view and select Check In from the pop up menu MAPICS, Inc. SyteLine ERP 7 Installation Guide 10-5

180 Upgrading a SyteLine Application Database 6. Rebuild the project. The IDOs will now work with the patched forms and application databases. If you had customized any IDO that has been updated by MAPICS, and you wish to keep those changes, you need to modify the IDO again. Run the Database Upgrade Utility 1. Back up your SyteLine application database. 2. Make sure that all users are logged out of the system. 3. Make sure that the target SyteLine version is already installed along with upgrade module on the database server. See Chapter 2, Setting Up the Database Server" for instructions on how to install SyteLine on the database server. 4. Apply the latest service pack prior to running the upgrade process. 5. On the database server, select Start>Programs>MAPICS>Tools>Database Upgrade Utility. 6. The SyteLine Database Upgrade Utility screen appears: 10-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

181 Upgrading a SyteLine Application Database 7. Fill in the following information: Server Name - Choose the name of the database server from the drop down list. This is the machine you are running this utility on. Use NT Authentication - Select this field to use NT Authentication. This means that instead of supplying a SQL Server login/password, the server uses the username of the person currently logged in to the Windows machine and logs in automatically. Username - Enter your username. This username must have system administrator privileges. Password - Enter the password associated with your username. Database Name - Select the name of the application database you want to upgrade from the drop down list. MAPICS Directory - Accept the path to the MAPICS directory, or click the browse button to browse to the proper path. 8. Click the Upgrade button. This process will take several minutes. 9. A message appears telling you the process is complete. Click OK. Once the upgrade is complete, we highly recommend that you check the upgrade log for any errors. A log is created for each database you upgrade and is found in the Logs folder subordinate to the installation directory, typically here - C:\Program Files\MAPICS\SyteLine\Upgrade\Logs. The log files are created using the name of the upgraded database as part of the name with the following syntax: Upgrade-databasename.log You should investigate any error reported in the log. You should fix the errors until none are present in the log before you can consider your database to have upgraded successfully MAPICS, Inc. SyteLine ERP 7 Installation Guide 10-7

182 Upgrading a SyteLine Application Database FormSync If you have customized any forms, you need to perform a FormSync after you complete the database upgrade. Follow the FormSync instructions immediately below. If you have NOT customized forms, you do not need to perform the FormSync, and you can skip this section. In this case, you can just create a new forms database of the proper version. The use of FormSync is a very complex topic, and it is best to understand it as best you can before using it. See About Form Synchronization at (then follow the links to product documentation) for more technical info. Customized versions of forms and other objects (like Strings or Validators) are kept in the forms database along with the original versions of those objects. When the original versions are updated (via a service pack, or an upgrade release), the utility FormSync allows you to integrate the changes in the new versions into your customized versions. FormSync is found on the utility server and administrative client machines. Select Start>Programs>MAPICS>Tools>FormSync. To get additional information about FormSync, click the Help button once the utility opens. To run FormSync you will need two forms databases. Perform the following steps: All of the steps in this FormSync section are performed on the utility server. If you have multiple forms databases, this procedure must be completed for each forms database. 1. Backup your forms database and restore a new database from that backup. Name the new database <dbname>_temp. 2. Run the SyteLine Configuration Wizard, select the checkbox to configure the client, and create a new configuration which points to the <dbname>_temp forms database. Alternatively, you can use the Client Configuration Manager tool to create the configuration. The application and forms databases are required. 3. Apply the SPnumber_MAPICS_SyteLine_ERP service pack to the <dbname>_temp configuration SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

183 Upgrading a SyteLine Application Database 4. Run FormSync (Start>Programs>MAPICS>Tools>FormSync) against your forms databases, specifying the source as the <dbname>_temp database which contains the updates, and the target as your existing forms database. Then click Synchronize. 5. Log in to SyteLine ERP and test the results of the synchronization. You can use the following SQL query to obtain a list of all the customized forms in your database: SELECT Name, ScopeType, ScopeName FROM <dbname>_forms.dbo.forms WHERE ScopeType > 0 Post Upgrade Steps If you just upgraded to SyteLine ERP 7.03 or later version, you MUST run the Rebalance Item Qty Allocated to Prod and WIP utility. This utility is found within SyteLine ERP. Troubleshooting If you have modified the application database schema by adding new constraints or updating table definitions, you will most likely get an error when you run the upgrade. If initialization data has been updated, this could cause an error. We recommend that you run through a pilot upgrade on a test database to address possible issues. If schema or initialization data issues persist, contact your service representative MAPICS, Inc. SyteLine ERP 7 Installation Guide 10-9

184 Upgrading a SyteLine Application Database SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

185 11 Converting From SyteLine 5 or SyteLine 6 (Single Site) If you are converting a multi-site database, see Converting From SyteLine 5 or SyteLine 6 (Multi-Site) on page The steps in this chapter detail how to convert from SyteLine 5 or SyteLine 6 on Progress to SyteLine ERP 7 on SQL. If you are running a version of SyteLine earlier than SyteLine 5, you need to upgrade to SyteLine 6 before converting to SyteLine 7 (you could upgrade to SyteLine 5 and convert from there, but we recommend that you upgrade to SyteLine 6 before converting to SyteLine ERP 7). The steps to upgrade from an earlier version of SyteLine to SyteLine 6 are found in the Getting Started manual for SyteLine 6. You can download this manual from MAPICS s web site at Once there, perform the following steps: 1. Login. 2. Select the radio button to Load the SyteLine menu. 3. Click OK. 4. Click the link for Product documentation. 5. Follow the links to the Getting Started manual for SyteLine MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-1

186 Converting From SyteLine 5 or SyteLine 6 (Single Site) Requirements In the list of requirements below, there are some paths to programs referenced. These paths and programs will not exist until AFTER you extract the files in the first step of the conversion procedure. Use the list of requirements only as reference. Do not use this list as your step-by-step procedure. The procedure begins AFTER the list of requirements. Your computer must have access to the.d files to be unloaded from the source (Progress) database, and access to about the same amount of disk space again (to hold the prepared.d7 files). Conversion can be run on any Windows NT, 2000, 2003, or XP computer. If User Extended Tables (UETs) are used in the SyteLine 5 or SyteLine 6 database, access to the Progress database is required to run the program uet-dump.p to unload the UET schema definitions to a flat file (zuetstruct.d7). If the conversion computer does not have access to Progress, the program can be copied to another appropriate computer and the flat file copied back from there. If a Multi-Byte code-page is used in the SyteLine 5 or SyteLine 6 database, access to the Progress database is required to run the program DumpUTF8.p to unload the data in a common format (data/*.d7w). If the conversion computer does not have access to Progress, the program and its sub-programs ("<InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\<verid>\Dump\*.r") can be copied to another appropriate computer (using the same directory structure) and the data files copied back from there. If a Single-Byte code-page is used in the SyteLine 6.01 or later database and faster loading is desired for certain large tables (for example, ledger & matltran), access to the Progress database is required to run the program Dump4bcp.p to unload the data from those tables in a post-converted format (data/sql/*.d7b). If the Conversion computer does not have access to Progress, the program and its sub-programs ("<InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\Data4bcp\*.r" and *.fmt, and "<InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\<verid>\Dump4bcp\*.r") can be copied to another appropriate computer (using the same directory structure) and the data files copied back from there SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

187 Converting From SyteLine 5 or SyteLine 6 (Single Site) SyteLine ERP 7 must be installed on this computer. The conversion programs are installed in the installation directory under " \SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL". Scripts under " \SyteLine\ApplicationDB\Foreign Keys" (Phase 4) and "\SyteLine\ApplicationDB\Init Data\Empty db" and "\SyteLine\ApplicationDB\Messages" (Final Phase) are also used during the conversion process. See Setting Up the Database Server for installation instructions. You must have installed the SyteLine ERP Database Migration pieces. See Setting Up the Database Server for installation instructions. Enough of SQL Server 2000 must be installed in order to have the bcp utility on this computer. SQL Server 2000 installation automatically adds the appropriate directory to the system Path. On the Server Settings Tab of the SQL Server Properties dialog, two-digit year support must be set to match the Progress -yy setting. For example, If -yy 1930 is used in symixrun.pf and admin.pf, then set to When a twodigit year is entered, interpret it as a year between: 1930 and This setting can be adjusted as desired after conversion is complete. When unloading data from the source SyteLine database(s), one of the following startup parameter combinations must be used: -d mdy OR -d ymd -yr4def In addition, the following startup parameter may not be used, because its output is not recognizable by the implicit SQL conversion algorithm: -d dmy These startup parameters can be used in the unloading session without affecting other logged in users, by utilizing a separate parameter-file. To verify the setting, inspect the trailer of an unloaded.d file for the dateformat setting; if -yr4def is used, also inspect any non-empty line in a.d for a table that contains a meaningful date field to verify that a 4-digit year is being output. Microsoft Data Access Components (MDAC) 2.7 is required for proper operation, due to a bug in earlier versions. If you need the proper version of MDAC, download it from Microsoft s site: MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-3

188 Converting From SyteLine 5 or SyteLine 6 (Single Site) Conversion Steps (Single Site) Use the following procedure to convert your single site database to SyteLine ERP 7. We recommend that you read the entire chapter before you begin. Following the Post-Conversion Tasks on page 11-20, the rest of this chapter contains reference material and troubleshooting tips. Step A: Start the SyteLine Database Migration Select Start>Programs>MAPICS>Tools>SyteLine Database Migration on a computer that has access to the data paths and can connect to the SQL Server where the target databases reside. The following screen appears: When the SyteLine Database Migration screen appears, the Extract tab is selected. 1. Multi-Byte - Select Multi-Byte if your source database uses a multi-byte code-page. 2. Schema Level - Choose the schema level of the source database. 3. Click Extract SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

189 Converting From SyteLine 5 or SyteLine 6 (Single Site) Step B: (Optional) Run the Overstuffing Detection Program Run the overstuffing detection program (<InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\overstuff.p) in the source database to detect all character fields with values set longer than the display format. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line in the Progress Query Editor: RUN <InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\overstuff.p The double-quotes in the example above are necessary due to spaces in the path. 4. Press the F2 key. Certain fields deliberately overstuffed by SyteLine ERP standard code are accepted as-is into the target database, and others shown below are accepted as-is into the Conversion Database (if Load Obsolete Data is checked) but are obsolete. Table.Field Display Format Data Allowed into Conversion Database *-audit.audit-prog X(20) 50 Batchrpt.rpt-name X(8) 15 Frzcost.job X(7) 30 Lasttran.trans-file X(27) 30 Lictkn.rsvd3 X(8) 33 Msg-lib.msg-fmt X(8) 300 Msg-lib.msg-id X(8) 40 Msg-lib.msg-syntax X(30) 200 p-funct.trn-funct X(30) 32 Rf-xref.rf-class X(8) 30 Rf-xref.description X(8) MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-5

190 Converting From SyteLine 5 or SyteLine 6 (Single Site) Rpt-opt.options X(78) 400 Rpt-opt.rpt-name X(8) 15 Sys-code.loc-code X(8) 20 Sys-code.loc-desc X(8) 60 Sys-code.reserved1 X(8) 12 Sys-code.sym-code X(10) 20 Sys-fld.table-name X(20) 32 Sys-menu.req-module X(12) 18 Tmp-ser.ref-str X(25) 30 User-browse.column-list X(40) 150 Usrprint.rpt-name X(8) Use the output to decide whether to: Correct the fields before unloading and save the extraneous data for later use, or Correct the fields before unloading and automatically truncate the fields during conversion (if the extraneous data is not needed), or Modify the target database structure and conversion scripts to accept longer values, or A combination of the above methods, per table. Step C: (Optional) Run the Foreign-Key Validation Program Run the foreign-key validation program (<InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValFK.p) in the source database to detect all invalid links between records. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN <InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValFK.p The double-quotes in the example above are necessary due to spaces in the path. ValFK.p automatically adjusts the PROPATH to find its subprocedures SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

191 Converting From SyteLine 5 or SyteLine 6 (Single Site) 4. Press the F2 key. 5. Use the output to decide whether to: Set the fields to valid values before unloading, or Set the fields to the unknown value before unloading, or Create missing master table records to make the links valid, or Delete the records containing invalid values (if the data is old or not needed). Phase 4 of the conversion can not be completed until all links are valid. Step D: (Optional) Run the Null Validation Program Run the Null validation program (<InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValNull.p) in the source database to detect all invalid (Blank) or (Unknown) field values. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN <InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValNull.p The double-quotes in the example above are necessary due to spaces in the path. ValNull.p automatically adjusts the PROPATH to find its subprocedure. 4. Press the F2 key. 5. Use the output to decide whether to: Set the fields to valid values before unloading, or Delete the records containing invalid values (if the data is old or not needed). Step E: (Optional) Run the Check-Constraint Program Run the Check-Constraint program (<InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValCk.p) in the source database to detect all remaining invalid field values. 1. Log in to SyteLine. 2. Launch the Progress Query Editor MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-7

192 Converting From SyteLine 5 or SyteLine 6 (Single Site) 3. Enter the following line: RUN <InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValCk.p The double-quotes in the example above are necessary due to spaces in the path. ValCk.p automatically adjusts the PROPATH to find its subprocedure. 4. Press the F2 key. 5. Use the output to decide whether to: Set the fields to valid values before unloading, or Delete the records containing invalid values (if the data is old or not needed). Step F: Log Out of SyteLine ERP on All Clients Make sure everyone is out of the system. Step G: Shut Down Servers Shut down your servers. Step H: Backup Databases Backup all databases. Step I: Unload Data from the Database To Be Converted Do not unload the databases from within a SyteLine session. Do not unload the databases by using Progress utilities. The only supported unload for the SL7 conversion is from the SyteLine Administration Menu utility. This step involves two options. Read the entire step before proceeding. You only need to run DumpUTF8.p if your database uses a Multi-Byte code-page. Option 1 - This process unloads your database into ASCII text files that are read into your new database. On your existing system, perform the following steps to unload your database(s): A. Select Admin/Run SyteLine from the Administration screen. B. Select Load/Unload then No Integrity or Full Integrity. We suggest Full Integrity. If your system is multi-division, you can unload a Global database only by connecting to one of the Division databases SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

193 Converting From SyteLine 5 or SyteLine 6 (Single Site) C. Select the parameter file of the database to be unloaded. D. Login to the database as user symix. E. Select Unload Database Files. The databases referenced by the parameter file are listed. The Main database is highlighted as the default. The first time through, select the Main database. (You might return to this step later.) F. The list of all available files appears. Press Enter to select ALL. An asterisk is placed to the left of the word ALL. Press the F1 key. G. When asked for a data path, enter the directory where the unloaded data (.d files) will be placed. This directory was created in Step 5. Make sure that you have adequate space in the directory and that you have permission to write to the directory. Chart mapping files and.d files must be in the same directory. If a Scheduling or Audit-Trail database is referenced in the parameter file, repeat steps E-F. A Scheduling database or Audit-trail database should be unloaded to the same directory as its Main database, but only after the Main database has been unloaded. The License Manager database does not need to be unloaded. H. If your system is multi-division, repeat steps E, F, and G for each of the divisions and the Global database: Each division, including its Main, Scheduling, and Audit-trail databases, should be unloaded to a separate directory. A Scheduling database or Audit-trail database should be unloaded to the same directory as its Main database, but only after the Main database has been unloaded. If another division is referenced by the parameter file of the database being unloaded, it appears in the list of databases in Step F. The Global database should also be unloaded to a separate directory MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-9

194 Converting From SyteLine 5 or SyteLine 6 (Single Site) Option 2 - If your database uses a Multi-Byte code-page, run the UTF8 unload program (<InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\DumpUTF8.p) instead. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN <InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\DumpUTF8.p The double-quotes in the example above are necessary due to spaces in the path. DumpUTF8.p automatically adjusts the PROPATH to find its sub-procedures. For SyteLine 6.01 or later databases utilizing a Single-Byte code-page, run the bcp unload program (<InstallDir>\ApplicationDB\Upgrade Scripts\Pro2SQL\Dump4bcp.p) also. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN "<InstallDir>\ApplicationDB\Upgrade Scripts\Pro2SQL\Dump4bcp.p" The double-quotes in the example above are necessary due to spaces in the path. Dump4bcp.p automatically adjusts the PROPATH to find its sub-procedures. 4. Press the F2 key. 5. Write the output (*.d7b) to the Prepared Data Path, or copy it there before running Phase 2. Remember to select Fast- Load Large Tables for Phases 2 and 3. The table(s) unloaded in this manner can be excluded from the normal unload performed using the SyteLine Database Utilities, to save time. If you have multi-database structures (for example, a separate scheduling database), unload all the component databases into the same data path used for the main database. Step J: Run uet-dump.p. (Only if User Extended Tables are SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

195 Converting From SyteLine 5 or SyteLine 6 (Single Site) Used) If User Extended Tables (UETs) are used and the data is to be carried forward to SyteLine ERP 7, run the program uet-dump.p to unload the UET schema definitions to a flat file named zuetstruct.d7. You must have access to the Progress database on the conversion computer to be able to run uet-dump.p. If the conversion computer does not have access to the Progress database, copy uet-dump.p to a computer that does, run it there, and then copy the flat file back to the conversion computer. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN <InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\uet-dump.p The double-quotes in the example above are necessary due to spaces in the path. Write the output file (zuetstruct.d7) to the Prepared Data Path, or copy it there before running Phase Press the F2 key. Step K: Create a Report of User-Defined Field Usage (Optional) To create a report of User-Defined Fields usage, run userflds.p in the source database to create userflds.txt. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN "<InstallDir>\ApplicationDB\Upgrade Scripts\Pro2SQL\userflds.p" The double-quotes in the example above are necessary due to spaces in the path. This information can be used after conversion to setup the same User-Defined Fields in appropriate SyteLine 7 Forms. 4. Press the F2 key MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-11

196 Converting From SyteLine 5 or SyteLine 6 (Single Site) Step L: Create a SyteLine 7 Application Database for Each Site Use the SyteLine Configuration Wizard to create a SyteLine 7 Application database for each site. See Chapter 2, Setting Up the Database Server" for information on how to use the Syteline Configuration Wizard. Step M: Select the Phases to Run on the Phases Tab 1. On the SyteLine Database Migration screen, select the Phases Tab. 2. Select the phases you need to run; all phases may not be necessary for your company. See immediately below for specific information about each phase, and make sure you understand each one before you run the conversion. After you select the phases, there are still some things to do on other tabs before you click the Run Conversion button. Once you have completed all the preparatory tasks, you can click the Run Conversion button, but you won t do that within this step SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

197 Converting From SyteLine 5 or SyteLine 6 (Single Site) Phases Each phase should be completed before beginning the next phase, with the exception of phase 8, which can be completed anywhere after phase 1 but before phase 9. Since the SyteLine ERP 7 schema is stringent with respect to the format of data and cross-references, the entire process usually cannot be run unattended through all phases until a trial conversion has proven that any data inconsistencies have been addressed. We recommend therefore that you run one phase at a time during a trial conversion period. The types of data problems are outlined in the section titled Troubleshooting on page Conversion occurs in the following 9 phases: 1. Prepare Data Files - Each Progress EXPORT-format flat-file (*.d) is read line-by-line, converted to a SQL-loadable format, and written out to a new flat-file (*.d7). 2. Load Data Files - Each SQL-loadable flat-file (*.d7) is loaded into a corresponding table in a SQL Conversion database. 3. Convert Data - Tables in the SyteLine ERP 7 Application database with known SyteLine 6 roots are populated from appropriate columns in rows in the appropriate table(s) in the Conversion database. Transformations are carried out for date and logical data-types, and Progress (Unknown) or (Blank) vs. SQL NULL values. Conversions are carried out for table splits and merges. New columns are populated from defaults or from other columns. After you ve converted the data, click the Compare Converted Record Counts button on the Options tab. This action compares the recordcounts of the tables in the selected range between the Conversion and Application Databases, and reports those which are different. Use this to verify that no tables were inadvertently skipped. 4. Apply Foreign-Key Constraints - SQL constraints are loaded to ensure the existence of a record on the lookup end of most foreign-key references. 5. Final Conversion - Other conversions are carried out that require all tables to be populated. After Phase 5 is complete, the Application database is ready for login and licensing. You may now modify the data in the UET forms (e.g., remove the "pref-type" class), then logout and continue with Impact Schema. This is a way to purge unwanted extensions, as only the columns present in both the conversion database and Application database are converted in Phase MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-13

198 Converting From SyteLine 5 or SyteLine 6 (Single Site) 6. Initialize APS - APS (Advanced Planning and Scheduling) tables are initialized from Work Center and Bill of Material and Job Routing data. 7. Impact Schema (for UET) - Creates columns to store table extensions. 8. Load UET Data Files - Each SQL-loadable UET flat-file (x*.d7) is loaded into a corresponding table in the Conversion database. 9. Convert UET Data - Table extensions are copied from the Conversion database to the appropriate records in the Application database. Step N: Make Selections on the Source Tab 1. Schema Level - Choose the Schema Level of the source database. This is the highest level in the drop-down that is before or equal to the version of SyteLine ERP last run against the database from which the data was unloaded. 2. Multi-Byte - Select Multi-Byte if the source database uses a Multi-Byte code-page. Phase 1 looks for.d7w files created by DumpUTF8.p and translate them to.d7u files. Phase 2 looks for.d7u files. All data is translated to Unicode during conversion, regardless of the Multi-Byte setting. 3. Multi-Site - Do not select Multi-Site. This is selected when the source database is already a member of a multi-site structure SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

199 Converting From SyteLine 5 or SyteLine 6 (Single Site) 4. Multi-Currency - Select Multi-Currency if the source database had Multi- Currency enabled. Otherwise clear this option and enter a new currency code on the Destination tab. 5. Data Path - Enter the Data Path to which the source database was unloaded. 6. Prepared Data Path - Enter a new directory into Prepared Data Path, where prepared data files will be stored during conversion. This drive requires available space approaching the total size of the unloaded files located in the Data Path. Step O: Make Selections on the Destination Tab 1. SQL Server - Enter the name of the SQL Server on which all databases will reside. 2. sa Password - Enter the password for the System Administration user 'sa' on the SQL Server. 3. Conversion Database - Enter the name of an intermediate conversion database to be used during conversion, then click the Create button. Its structure is built during phase Refresh Database Lists - Click the Refresh Database Lists button to populate the Application Database drop-down list MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-15

200 Converting From SyteLine 5 or SyteLine 6 (Single Site) 5. Application Database - Select the Application Database created in Step Site - Enter the Site identifier for all records in the target database. This value may not be left blank, and you cannot change the value during or after the conversion. 7. Currency - If Multi-Currency was not enabled in the source database, enter a Currency code for all records in the target database. This value may not be left blank, and you cannot change the value during or after the conversion. Step P: Make Selections on the Options tab 1. MAPICS Path - The SyteLine ERP 7 installation path defaults here. 2. Logfile Path - Enter a Logfile Path where logfiles will be written. The default is the Working Directory of the conversion program SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

201 Converting From SyteLine 5 or SyteLine 6 (Single Site) 3. Starting and Ending Table - (Optional) Enter Starting and Ending Table to limit processing to a specific range of data. This is a strict range and does not accept wildcards. It can be used to parallel-process portions of certain phases on different computers connected to one SQL Server (ensuring that each phase is completed on all computers before beginning the next phase), or to resume conversion or re-convert individual tables after correcting errors in the source data. For Phase 1, use extensionless.d names. For Phase 2, use SyteLine 6 table names (with hyphens). For Phases 3-4, 7, and 8, use SyteLine 7 table names (with underscores instead of hyphens). For User Extended Tables, specify the extensionless.d name in Phase 1 and the corresponding SyteLine table in other Phases according to the guidelines in the preceding sentence. When using ranges, note that hyphen sorts lower than (i.e., comes before) a, and underscore sorts higher than (i.e., comes after) z. A simple method for starting at the first table after table is to specify Starting Table as table- (the name of the table followed by a hyphen). This excludes table itself but processes any table having a prefix identical to table followed by any letter, hyphen, or underscore. A simple method for ending at the last table before table is to specify Ending Table as tabld_zz (the name of the table with its last character replaced by the preceding letter or digit followed by underscore and 2 z s). Again this excludes table itself but processes any table having a prefix near to table followed by any letter, hyphen, or underscore and any other letters (because no SyteLine tables contain 2 adjacent underscores). Using these methods, it is not necessary to know the entire list of tables or at which specific table the process is to be started or ended. Refer to the tables below as examples: In Phase 1 To process: memo-top.d memo-top.d7 prd-item.d prd-item.d7 item.d item.d7 xitem.d xitem.d7 Specify: memo-top prd-item item xitem 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-17

202 Converting From SyteLine 5 or SyteLine 6 (Single Site) In Phase 2 To process: memo-top.d7 [memo-topic] prd-item.d7 [prod-mix-item] item.d7 [item] xitem.d7 [ux-item] Specify: memo-topic prod-mix-item item item In other Phases To process: [memo-topic] memo_topic [prod-mix-item] prod_mix_item [item] item [ux-item] item Specify: memo_topic prod_mix_item item item 4. Performance - On multi-processor computers, use the fields in this section to distribute Phase 3 processing among the CPUs. Multi-Thread Tables Larger than N Rows - Check this field and then enter the number of rows a table must have before multi-thread begins. Threads - Enter the desired number of simultaneous threads (2-9). A single thread is used for tables having less than or equal to the number of rows designated in the Multi-Thread Tables Larger than N Rows field above SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

203 Converting From SyteLine 5 or SyteLine 6 (Single Site) 5. Fast-Load Large Tables - If Dump4bcp.p was used to unload large tables from the Progress database, this field can be set to load directly from the resulting *.d7b files into the application database during Phase 2 (bypassing the conversion database and eliminating or significantly reducing the Phase 3 processing for these tables). Notes attached to these records are loaded during Phase 3. Initial tables supported by Dump4bcp.p are: ledger & matltran (and its sub-table matltran_amt) for SyteLine 6.01 or later source databases. 6. Stop at First Error - Select Stop at First Error to stop the conversion upon first detection of any error or data anomaly. Clear this option to continue processing the next table(s) and/or Phase(s). In either case, detected errors are logged to the Status tab and written to a logfile. 7. Truncate Overstuffed Character Fields - Select Truncate Overstuffed Character Fields to automatically truncate all character fields with values in the source database set longer than the display format. The extraneous data remains in the conversion database, but no warning is shown. Clear this option to abort loading the entire table when this condition is detected. This allows anomalies to be found without running overstuff.p. 8. Substitute for Leading Spaces - Enter a single character to Substitute for Leading Spaces in non-formatted character fields. Leading spaces are not allowed in SyteLine ERP 7, except in alpha-keys (for example, CO number, PO number), and in account numbers when the account format is numeric with leading zeroes suppressed (for example, "ZZZZZ"). To maintain sorting as in the source database, enter a character that sorts before the first character of the lowest-sorting non-space-led field in any field in any table containing leading spaces (exclamation, double-quote, #, $, %, &, single-quote, (,), *, +, comma, -, period, slash; and unless digits are used to start fields, also any digit, colon, semi-colon, <, =, >, questionmark, Step Q: Click the Run Conversion Button Click the Run Conversion button to start processing. The Status tab shows the progress. An alert-box and bell signal completion. At completion, the progress is appended to a file "convert.log" in the Logfile Path. Step R: Click Run Conversion Button for Additional Phases 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-19

204 Converting From SyteLine 5 or SyteLine 6 (Single Site) or Table Ranges Repeat the above steps for additional phases or table ranges, and click the Run Conversion button when ready. After Phase 3 is complete, click the Compare Converted Record Counts button on the Options tab to display any tables with mismatched record-counts between the Conversion and Application database. This is helpful to catch any tables that were neglected if incorrect table ranges were used. Do not run the final conversion phase until all prior phases have completed. Step S: Perform Post Conversion Tasks After conversion is complete, perform the Post-Conversion Tasks below. Following the Post Conversion Tasks, the rest of this chapter is reference material and troubleshooting tips. Post-Conversion Tasks The following tasks are required after conversion to prepare the application database for use with SyteLine ERP 7: 1. Open the License Management form and enter your license key. See the SyteLine ERP 7 System Administration Guide for more information on license management. 2. Enter password for all user records. Because passwords are stored in an encrypted format, they cannot be brought forward from the source database. 3. Set up form-based, user-, and group-level security. See the SyteLine ERP 7 System Administration Guide or the online help for more information on how to set up user authorizations. 4. Unhide and appropriately label any desired User-Defined Fields on Forms User-Defined tabs SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

205 Converting From SyteLine 5 or SyteLine 6 (Single Site) Outputs Disk Usage Name Phase Directory Contents Convert.log All Logfile Path Contents of the Status tab Load.log 2 Prepared Data Path Number of records loaded per table; format is comparable to "un-load.log" from the Database Unload utility. Load2.log 3 Logfile Path Number of records converted per table Crewsize.log Final Logfile Path List of records whose nonintegral Crew Size was altered Plan for the following space requirements: Data Store Source database (Progress) Troubleshooting Estimated Size X Needed Through Database Utilities Unload (pre Conversion) Unloaded data files (*.d) 80% of X Conversion Phase 1 (Prepare Data Files) Prepared data files (*.d7) 55% of X Conversion Phase 2 (Load Data Files) Conversion database (SQL) Application database transaction log (SQL) Application database data files (SQL) High-water mark when minimizing 150% of X Final Conversion (OK to Shrink after Phase 2) 35% of X Final Conversion (OK to Shrink after Final Conversion) 350% of X % of X N/A Total when not minimizing 770% of X N/A Following are some common errors that might occur during conversion, with suggested remedies: Phase Error Where Remedy 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-21

206 Converting From SyteLine 5 or SyteLine 6 (Single Site) 2 String data, right truncation 3 Cannot insert the value NULL into column 'xxx', table 'zzz.dbo.yyy'; column does not allow nulls. INSERT fails. 3 INSERT statement conflicted with COLUMN CHECK constraint 'CK_yyy_xxx'. The conflict occurred in database 'zzz', table 'yyy', column 'xxx'. 4 ALTER TABLE statement conflicted with COLUMN FOREIGN KEY constraint 'kkk'. The conflict occurred in database 'zzz', table 'yyy', column 'xxx'. <Prepared Data Path>\ <dumpname.err> Convert.log Convert.log Convert.log Run overstuff.p in the source database to find overstuffed fields. Correct these in the source database and unload again, or modify the <VerId>/*.tbl file to allow for more data, and use the Truncate option. Run ValNull.p in the source database to find invalid (Blank) and (Unknown) fields. Correct these in the source database and unload again, or Use SELECT statements in the Conversion database to find offending records. Correct or delete these and re-run Phase 3 for this table. Use SELECT statements in the Conversion database to find offending records. Correct or delete these and re-run Phase 3 for this table. Run ValFK.p in the source database to find invalid foreign-key references. Correct these in the source database and unload again, or Use SELECT statements in the Application database to find offending records. Correct or delete these and re-run Phase 4 for this table. See Resolving Foreign-Key Conflicts SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

207 Resolving Foreign-Key Conflicts Converting From SyteLine 5 or SyteLine 6 (Single Site) A Foreign-Key Relationship is a reference in one record to the primary-keys of another record. For example, most G/L Account columns must either be Null or refer to an existing record in the Chart of Accounts table. The SyteLine 7 Application database utilizes SQL Foreign-Key Constraints to enforce these relationships, thus ensuring referential integrity between tables. If a reference is incorrect in the source database, a Foreign-Key Conflict is raised during Phase 4. All such conflicts must be resolved before the database is ready for use with SyteLine 7. Following is an example of resolving a Foreign-Key Conflict. The SQL error message for this example is: *** Error occurred during Apply coh.key to SyteLine_App ALTER TABLE statement conflicted with TABLE FOREIGN KEY constraint 'cohfk1'. The conflict occurred in database 'SyteLine_App', table 'customer'. The above message has the following information: The record containing the incorrect reference is located in the "coh" table (foreign-key table). The reference is intended to identify a record in the "customer" table (primary-key table). The name of the foreign-key relationship is "cohfk1" (constraint name). The relationship is described in the file <InstallDir>\SyteLine\ApplicationDB\Foreign Keys\coh.key. If the relationship is based on a single key column, its name is also given. This information is also listed in the.key file. To resolve the conflict, do the following: 1. Determine which columns in the foreign-key table "coh" are meant to refer to which columns in the primary-key table "customer." These are listed in the.key file under the name of the relationship as in the example below: ADD CONSTRAINT cohfk1 FOREIGN KEY ( cust_num, cust_seq ) REFERENCES customer ( cust_num, cust_seq 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-23

208 Converting From SyteLine 5 or SyteLine 6 (Single Site) ) 2. Build a T-SQL statement in the Query Analyzer to find incorrect references as in the example below: SELECT co_num, cust_num, cust_seq FROM coh WHERE cust_num IS NOT NULL AND NOT EXISTS(SELECT 1 FROM customer WHERE customer.cust_num = coh.cust_num AND customer.cust_seq = coh.cust_seq) The above statement shows (SELECT) the key column(s) (co_num) and incorrect references (cust_num, cust_seq) from every record in the foreign-key table (coh) whose foreign-keys (coh.cust_num, coh.cust_seq) seemingly refer to a record (NOT NULL) but do not identify (NOT EXISTS) a record in the primary-key table (customer). A grid is displayed that lists the selected columns for each record with an incorrect reference. You now decide how to address each incorrect reference. Choose from among the following 3 options: Change the foreign-key columns to refer to an existing primary-key record. For example: UPDATE coh SET cust_seq = 4 WHERE coh.co_num = 'S ' Add a new primary-key record with primary-keys to match the foreign-keys (not recommended at this point in the process, because SyteLine triggers are disabled and will not provide their normal validation or cascading actions); or Change the foreign-key columns to Null. For example, to affect all incorrect records: UPDATE coh SET cust_num = NULL, cust_seq = NULL FROM coh WHERE cust_num IS NOT NULL AND NOT EXISTS(SELECT 1 FROM customer WHERE customer.cust_num = coh.cust_num AND customer.cust_seq = coh.cust_seq) All references are correct for this constraint when the SELECT statement above displays an empty grid SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

209 Converting From SyteLine 5 or SyteLine 6 (Single Site) After all references are correct for all constraints in a.key file, phase 4 can be re-run for the foreign-key table (enter the table name "coh" in both the Starting Table and Ending Table fields). Relative Duration Re-entrance The following table approximates the relative successful completion times of each phase: Phase % Results may vary and can differ greatly when parallel processes are used. Phases 1-4, 6, and 8 can be re-executed for individual tables or ranges if data inconsistencies are detected and corrected. The following table provides details: Phase Preparation Required Before Re-execution Details 1 None.d7 file will be overwritten by default 2 None Table in Conversion database is dropped and re-created by default 3 Truncate table in Application database Depending on the type of error received during previous execution, data may remain in the table; we do not truncate by default 4 None Existing constraints are dropped for each table and re-created by default 6 None Stored Procedure purges all data before recreating it. 8 None Table in Conversion database is dropped and re-created by default 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 11-25

210 Converting From SyteLine 5 or SyteLine 6 (Single Site) Parallel Execution Phases 1-4 can be executed on multiple computers or multiple processes in parallel, to reduce total duration. This is especially useful on multi-processor systems. 1. Start multiple instances of SLConv.exe on 1 or more computers. 2. Enter a unique Logfile Path for each instance; all other options should be identical. 3. Use the Starting Table/Ending Table range option to split the load. Note your largest tables by size of.d and attempt to group these separately (for example, if largest tables are ledger and matltran, then use 4 ranges: a-l, l-m, m-n, n-z). Note: Range l-m does not process any tables beginning with "m", because "matlearn" (the first table beginning with "m") sorts higher than "m" in dictionary order. Another way to process the same range is l-l_zz. When using parallel execution, follow these guidelines for minimum contention: Phase Guideline 1 None 2 None 3 Start first instance; wait until it has finished dropping foreign-keys and loaded user_local table; then start remaining instances. 4 None Monitor system load to avoid performance degradation SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

211 12 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) If you are converting a single site database, see Converting From SyteLine 5 or SyteLine 6 (Single Site) on page The steps in this chapter detail how to convert from SyteLine 5 or SyteLine 6 on Progress to SyteLine ERP 7 on SQL. If you are running a version of SyteLine earlier than SyteLine 5, you need to upgrade to SyteLine 6 before converting to SyteLine 7 (you could upgrade to SyteLine 5 and convert from there, but we recommend that you upgrade to SyteLine 6 before converting to SyteLine ERP 7). The steps to upgrade from an earlier version of SyteLine to SyteLine 6 are found in the Getting Started manual for SyteLine 6. You can download this manual from MAPICS s web site at Once there, perform the following steps: 1. Login. 2. Select the radio button to Load the SyteLine menu. 3. Click OK. 4. Click the link for Product documentation. 5. Follow the links to the Getting Started manual for SyteLine MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-1

212 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Requirements In the list of requirements below, there are some paths to programs referenced. These paths and programs will not exist until AFTER you extract the files in the first step of the conversion procedure. Use the list of requirements only as reference. Do not use this list as your step-by-step procedure. The procedure begins AFTER the list of requirements. Your computer must have access to the.d files to be unloaded from the source (Progress) database, and access to about the same amount of disk space again (to hold the prepared.d7 files). Conversion can be run on any Windows NT, 2000, 2003, or XP computer. If User Extended Tables (UETs) are used in the SyteLine 5 or SyteLine 6 database, access to the Progress database is required to run the program uet-dump.p to unload the UET schema definitions to a flat file (zuetstruct.d7). If the conversion computer does not have access to Progress, the program can be copied to another appropriate computer and the flat file copied back from there. SyteLine ERP 7 must be installed on this computer. The conversion programs are installed in the installation directory under "\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL". Scripts under "\SyteLine\ApplicationDB\Foreign Keys" (Phase 4) and "\SyteLine\ApplicationDB\Init Data\Empty db" and "\SyteLine\ApplicationDB\Messages" (Final Phase) are also used during the conversion process. See Setting Up the Database Server for installation instructions. You must have installed the SyteLine ERP Database Migration pieces. See Setting Up the Database Server for installation instructions. Enough of SQL Server 2000 must be installed in order to have the bcp utility on this computer. SQL Server 2000 installation automatically adds the appropriate directory to the system Path. On the Server Settings Tab of the SQL Server Properties dialog, two-digit year support must be set to match the Progress -yy setting. For example, If -yy 1930 is used in symixrun.pf and admin.pf, then set to When a twodigit year is entered, interpret it as a year between: 1930 and This setting can be adjusted as desired after conversion is complete. When unloading data from the source SyteLine database(s), one of the following startup parameter combinations must be used: -d mdy OR 12-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

213 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) -d ymd -yr4def In addition, the following startup parameter may not be used, because its output is not recognizable by the implicit SQL conversion algorithm: -d dmy These startup parameters can be used in the unloading session without affecting other logged in users, by utilizing a separate parameter-file. To verify the setting, inspect the trailer of an unloaded.d file for the dateformat setting; if -yr4def is used, also inspect any non-empty line in a.d for a table that contains a meaningful date field to verify that a 4-digit year is being output. Microsoft Data Access Components (MDAC) 2.7 is required for proper operation, due to a bug in earlier versions. If you need the proper version of MDAC, download it from Microsoft s site: Conversion Steps (Multi-Site) Use the following procedure to convert your multi-site database to SyteLine ERP 7. We recommend that you read the entire chapter before you begin. The procedure is divided up in to several sections, and each section contains a series of steps. Following the Post-Conversion Tasks on page 12-32, the rest of this chapter contains reference material and troubleshooting tips MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-3

214 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Step A: Start the SyteLine Database Migration Select Start>Programs>MAPICS>Tools>SyteLine Database Migration on a computer that has access to the data paths and can connect to the SQL Server where the target databases reside. The following screen appears: When the SyteLine Database Migration screen appears, the Extract tab is selected. 1. Multi-Byte - Select Multi-Byte if your source database uses a multi-byte code-page. 2. Schema Level - Choose the schema level of the source database. 3. Click Extract. Step B: (Optional) Run the Overstuffing Detection Program Run the overstuffing detection program (<MAPICSInstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\overstuff.p) in each site and entity database. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line in the Progress Query Editor: RUN <MAPICSInstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\overstuff.p 12-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

215 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) The quotes in the example above are necessary due to spaces in the path. 4. Press the F2 key. Certain fields deliberately overstuffed by SyteLine ERP standard code are accepted as-is into the target database, and others shown below are accepted as-is into the Conversion Database (if Load Obsolete Data is checked) but are obsolete. Table.Field Display Format Data Allowed into Conversion Database *-audit.audit-prog X(20) 50 Batchrpt.rpt-name X(8) 15 Frzcost.job X(7) 30 Lasttran.trans-file X(27) 30 Lictkn.rsvd3 X(8) 33 Msg-lib.msg-fmt X(8) 300 Msg-lib.msg-id X(8) 40 Msg-lib.msg-syntax X(30) 200 p-funct.trn-funct X(30) 32 Rf-xref.rf-class X(8) 30 Rf-xref.description X(8) 100 Rpt-opt.options X(78) 400 Rpt-opt.rpt-name X(8) 15 Sys-code.loc-code X(8) 20 Sys-code.loc-desc X(8) 60 Sys-code.reserved1 X(8) 12 Sys-code.sym-code X(10) 20 Sys-fld.table-name X(20) 32 Sys-menu.req-module X(12) MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-5

216 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Tmp-ser.ref-str X(25) 30 User-browse.column-list X(40) 150 Usrprint.rpt-name X(8) Use the output to decide whether to: Correct the fields before unloading and save the extraneous data for later use, or Correct the fields before unloading and automatically truncate the fields during conversion (if the extraneous data is not needed), or Modify the target database structure and conversion scripts to accept longer values, or A combination of the above methods, per table. Step C: (Optional) Run the Foreign-Key Validation Program Run the foreign-key validation program (<MAPICSInstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValFK.p) in each site and entity database to detect all invalid links between records. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN <MAPICSInstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValFK.p The quotes in the example above are necessary due to spaces in the path. ValFK.p automatically adjusts the PROPATH to find its sub-procedures. 4. Press the F2 key. 5. Use the output to decide whether to: Set the fields to valid values before unloading, or Set the fields to the unknown value before unloading, or Create missing master table records to make the links valid, or 12-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

217 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Delete the records containing invalid values (if the data is old or not needed). Phase 4 of the conversion can not be completed until all links are valid. Step D: (Optional) Run the Null Validation Program Run the Null validation program (<MAPICSInstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValNull.p) in each site and entity database to detect all invalid (Blank) or (Unknown) field values. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN <MAPICSInstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValNull.p The quotes in the example above are necessary due to spaces in the path. ValNull.p automatically adjusts the PROPATH to find its sub-procedure. 4. Press the F2 key. 5. Use the output to decide whether to: Set the fields to valid values before unloading, or Delete the records containing invalid values (if the data is old or not needed). Step E: (Optional) Run the Check-Constraint Program Run the Check-Constraint program (<InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValCk.p) in the source database to detect all remaining invalid field values. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN <InstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\ValCk.p The double-quotes in the example above are necessary due to spaces in the path. ValCk.p automatically adjusts the PROPATH to find its subprocedure. 4. Press the F2 key MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-7

218 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 5. Use the output to decide whether to: Set the fields to valid values before unloading, or Delete the records containing invalid values (if the data is old or not needed). Step F: Log out of SyteLine on all clients Make sure everyone is out of the system. Step G: Shut Down Servers Shut down your servers. Step H: Backup Databases Backup all databases. Step I: Unload Data from the Database To Be Converted Do not unload the databases from within a SyteLine session. Do not unload the databases by using Progress utilities. The only supported unload for the SL7 conversion is from the SyteLine Administration Menu utility. This step involves two options. Read the entire step before proceeding. You only need to run DumpUTF8.p if your database uses a Multi-Byte code-page. Option 1 - This process unloads your database into ASCII text files that are read into your new database. On your existing system, perform the following steps to unload your database(s): A. Select Admin/Run SyteLine from the Administration screen. B. Select Load/Unload then No Integrity or Full Integrity. We suggest Full Integrity. If your system is multi-division, you can unload a Global database only by connecting to one of the Division databases. C. Select the parameter file of the database to be unloaded. D. Login to the database as user symix. E. Select Unload Database Files. The databases referenced by the parameter file are listed. The Main database is highlighted as the default. The first time through, select the Main database. (You might return to this step later.) 12-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

219 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) F. The list of all available files appears. Press Enter to select ALL. An asterisk is placed to the left of the word ALL. Press the F1 key. G. When asked for a data path, enter the directory where the unloaded data (.d files) will be placed. This directory was created in Step 5. Make sure that you have adequate space in the directory and that you have permission to write to the directory. Chart mapping files and.d files must be in the same directory. If a Scheduling or Audit-Trail database is referenced in the parameter file, repeat steps E-F. A Scheduling database or Audit-trail database should be unloaded to the same directory as its Main database, but only after the Main database has been unloaded. The License Manager database does not need to be unloaded. H. If your system is multi-division, repeat steps E, F, and G for each of the divisions and the Global database: Each division, including its Main, Scheduling, and Audit-trail databases, should be unloaded to a separate directory. A Scheduling database or Audit-trail database should be unloaded to the same directory as its Main database, but only after the Main database has been unloaded. If another division is referenced by the parameter file of the database being unloaded, it appears in the list of databases in Step F. The Global database should also be unloaded to a separate directory. Option 2 - If your database uses a Multi-Byte code-page, run the UTF8 unload program (<MAPICSInstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\DumpUTF8.p) instead. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN <MAPICSInstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\DumpUTF8.p 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-9

220 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) The quotes in the example above are necessary due to spaces in the path. DumpUTF8.p automatically adjusts the PROPATH to find its subprocedures. If you have multi-database structures (for example, a separate scheduling database), unload all the component databases into the same data path used for the main database. Due to a constraint in the Database Utilities, if Shared Customer Master is enabled in any sites, you must login to one of those sites to unload the "custa-audit" table. Also, if Shared Vendor Master is enabled in any sites, you must login to one of those sites to unload the "venda-audit" table. In some circumstances, these tables are not available for selection when logged into an Entity database. Step J: Run uet-dump.p. (Only if User Extended Tables are Used) If User Extended Tables (UETs) are used and the data is to be carried forward to SyteLine ERP 7, run the program uet-dump.p to unload the UET schema definitions to a flat file named zuetstruct.d7. 1. Log in to SyteLine. 2. Launch the Progress Query Editor. 3. Enter the following line: RUN <MAPICSInstallDir>\SyteLine\ApplicationDB\Upgrade Scripts\Pro2SQL\uet-dump.p The quotes in the example above are necessary due to spaces in the path. Write the output file (zuetstruct.d7) to the Prepared Data Path, or copy it there before running Phase Press the F2 key. Step K: Create a Report of User-Defined Field Usage (Optional) To create a report of User-Defined Fields usage, run userflds.p in the source database to create userflds.txt. 1. Log in to SyteLine. You must have access to the Progress database on the conversion computer to be able to run uet-dump.p. If the conversion computer does not have access to the Progress database, copy uet-dump.p to a computer that does, run it there, and then copy the flat file back to the conversion computer SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

221 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 2. Launch the Progress Query Editor. 3. Enter the following line: RUN "<MAPICSInstallDir>\ApplicationDB\Upgrade Scripts\Pro2SQL\userflds.p" The quotes in the example above are necessary due to spaces in the path. This information can be used after conversion to setup the same User- Defined Fields in appropriate SyteLine 7 Forms. 4. Press the F2 key. Step L: Create a SyteLine 7 Application Database for Each Site Use the SyteLine Configuration Wizard to create a SyteLine 7 Application database for each site. See Chapter 2, Setting Up the Database Server" for information on how to use the Syteline Configuration Wizard. Load Data From Global Database Step A: Make Selection on the Overview Tab 1. On the SyteLine Database Migration screen, click the Overview tab 2. Select Load 'symglbl' Data MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-11

222 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Step B: Select the Phases to Run on the Phases Tab 1. Select the Phases tab. 2. Select the phases to run (either Phase 1 or Phase 2, or both). You can run phases 3-9 only after 1-2 have been run and after you clear the Load 'symglbl' Data field on the Overview tab. There are nine phases on this tab, defined as the following: Not all the phases can be run at this point in the procedure. Please read the detail for each phase below for ones with special instructions. Phase 1, Prepare Data Files - Each Progress EXPORT-format flat-file (*.d) is read line-by-line, converted to a SQL-loadable format, and written out to a new flat-file (*.d7). Run this phase and phase 2 before the other phases. Phase 2, Load Data Files - Each SQL-loadable flat-file (*.d7) is loaded into a corresponding table in a SQL Conversion database. Run this phase and phase 1 before the other phases SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

223 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Phase 3, Convert Data - Tables in the SyteLine 7 Application database with known SyteLine 6 roots are populated from appropriate columns in rows in the appropriate table(s) in the Conversion database. Transformations are carried out for date and logical data-types, and Progress (Unknown) or (Blank) vs. SQL NULL values. Conversions are carried out for table splits and merges. New columns are populated from defaults or from other columns. Phase 4, Apply Foreign-Key Constraints - SQL Constraints are loaded to ensure the existence of a record on the lookup end of most foreign-key references. Phase 5, Final Conversion - In this phase, other conversions are carried out that require all tables to be populated. After Phase 5 is complete, the Application database is ready for login and licensing. At this point, you may modify the data in the UET forms (e.g., remove the "pref-type" class), then logout and continue with Impact Schema. This is a way to purge unwanted extensions, as only the columns present in both the Conversion database and Application database will be converted in Phase 8. Phase 6, Initialize APS - APS (Advanced Planning and Scheduling) tables are initialized from Work Center and Bill of Material and Job Routing data. Run this phase only AFTER the latest SyteLine service pack has been installed. Phase 7, Impact Schema (User Extended Tables) - This phase creates columns to store table extensions. Run this phase only AFTER the latest SyteLine service pack has been installed. Phase 8, Load UET Data Files - Each SQL-loadable UET flat-file (x*.d7) is loaded into a corresponding table in the Conversion database. Run this phase only AFTER the latest SyteLine service pack has been installed. Phase 9, Convert UET Data - Table extensions are copied from the Conversion database to the appropriate records in the Application database. Run this phase only AFTER the latest SyteLine service pack has been installed MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-13

224 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Step C: Make Selections on the Source Tab Make selections in the following fields: 1. Schema Level - Choose the schema level of the source database. 2. Multi-Byte - Select Multi-Byte if the source database uses a Multi-Byte code-page. Phase 1 looks for.d7w files created by DumpUTF8.p and translates them to.d7u files. Phase 2 looks for.d7u files. All data is translated to Unicode during conversion, regardless of the Multi-Byte setting. 3. Data Path - Enter the data path to which the 'symglbl' database was unloaded. 4. Prepared Data Path - Enter a new directory into Prepared Data Path, where prepared data files are stored during conversion. This drive requires available space approaching the total size of the unloaded files located in the data path SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

225 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Step D: Make Selections on the Destination Tab Make selections in the following fields: 1. SQL Server - Enter the name of the SQL Server on which all databases will reside. 2. sa Password - Enter the password for the System Administration user 'sa' on the SQL Server. 3. Conversion Database - Enter the name of an intermediate 'symglbl' Conversion Database to be used during conversion, and click the Create button. Its structure is built during Phase MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-15

226 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Step E: Make Selections on the Options tab 1. MAPICS Path - The SyteLine ERP 7 installation path defaults here. 2. Logfile Path - Enter a Logfile Path where logfiles will be written. 3. Starting and Ending Table - (Optional) Enter Starting and Ending Table to limit processing to a specific range of data. If you leave these fields blank, all tables are processed. 4. Performance - On multi-processor computers, use the fields in this section to distribute Phase 3 processing among the CPUs. Multi-Thread Tables Larger than N Rows - Check this field and then enter the number of rows a table must have before multi-thread begins. Threads - Enter the desired number of simultaneous threads (2-9). A single thread is used for tables having less than or equal to the number of rows designated in the Multi-Thread Tables Larger than N Rows field above SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

227 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 5. Fast-Load Large Tables - If Dump4bcp.p was used to unload large tables from the Progress database, select this field to load directly from the resulting *.d7b files into the Application database during Phase 2 (thus bypassing the Conversion database and eliminating or significantly reducing the Phase 3 processing for these tables). Notes attached to these records are loaded during Phase 3. Initial tables supported by Dump4bcp.p are: ledger & matltran (and its new sub-table matltran_amt) for SyteLine 6.01 or later source databases. 6. Stop at First Error - Select Stop at First Error to stop the conversion upon first detection of any error or data anomaly. 7. Maximum Errors for bcp - Phase 2 uses the bcp (Bulk Copy) utility to import data from flat-files. Bcp performs minimal validation as rows are imported, including checking for proper data-types and lengths. If the number of rows that fail validation is below a threshold, bcp imports the remaining rows and reports the errors encountered. Otherwise bcp imports nothing. Enter the number of data errors for bcp to detect before aborting the import for each table. Use this option if a table is failing validation. To help determine which rows contain errors, increase the value until the remaining rows are imported, then determine which rows are missing from the Conversion database. 8. Truncate Overstuffed Character Fields - Progress allows character fields to be "overstuffed" (i.e., to contain more characters than indicated by the Display format). However, SQL does not allow columns to contain more characters than allocated. Where standard SyteLine has produced overstuffed fields, the corresponding SQL columns have been made wide enough to accommodate the data. In the case of custom programs that have created overstuffing, an error is logged during the Load phase. In this case, you have the option of going back to the Progress database and adjusting the record(s) and again Unloading the table(s) in error, or adjusting the script that creates the table(s) in the Conversion database. This will allow the data to be loaded into the Conversion database cleanly. In the Convert phase, select this field to signal the conversion script to detect data that is longer than the destination column's precision and automatically truncate the extra character(s). When this field is cleared, an error is logged and the data will not be converted. If you need to keep the extra character(s), you can either adjust the Application database to increase the precision in the appropriate columns (probably by modifying the User Defined Data Types in DataType.sql and rebuilding the database), or adjust the conversion script to store the data elsewhere. 9. Substitute for Leading Spaces - Leading spaces are not allowed in most SyteLine 7 character fields. The character you enter here replaces each leading space in offending fields MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-17

228 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Step F: Click the Run Conversion Button Click the Run Conversion button to start processing. The Status tab shows the progress. An alert-box and bell signal completion. At completion, the progress is appended to a file "convert.log" in the Logfile Path. Step G: Repeat Previous 6 Steps if Necessary Repeat for an additional Phase or Table ranges. Load Data From Entity Database(s) Entities that share their Currency Master with subordinate Sites or Entities must be loaded first, at least through Phase 2, so the subordinate Sites and Entities can read the appropriate records from the parent Entity s Conversion Database. Step A: Make Selection on the Overview Tab On the Overview tab, clear Load 'symglbl' Data SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

229 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Step B: Select the Phases to Run on the Phases Tab Select the phases to run. Do not run Phase 5 (Final Conversion) until phases 1-4 have completed MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-19

230 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Step C: Make Selections on the Source Tab 1. Schema Level - Choose the schema level of your source database. 2. Multi-Byte - Select Multi-Byte if the source database uses a Multi-Byte code-page. Phase 1 looks for.d7w files created by DumpUTF8.p and translates them to.d7u files. Phase 2 looks for.d7u files. All data is translated to Unicode during conversion, regardless of the Multi-Byte setting. 3. Multi-Site - Select Multi-Site. When you select this field, the Reports To Entity field becomes active. 4. Reports To Entity - Select this field if this Entity reports to a higher-level Entity in the hierarchy. 5. Multi-Currency - Select Multi-Currency if the source database had multicurrency enabled. If not, clear this field and enter a new currency code on the Destination tab. 6. Shared Currency Master - Select Shared Currency Master if this Entity shared the Currency master data from a higher-level Entity or from the global database. 7. Data Path - Enter the data path to which the entity database was unloaded SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

231 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 8. Prepared Data Path - Enter a new directory into Prepared Data Path, where prepared data files will be stored during conversion. This drive requires available space approaching the total size of the unloaded files located in the data path. Step D: Make Selections on the Destination Tab 1. SQL Server - Enter the name of the SQL Server on which all databases will reside. 2. sa Password - Enter the password for the System Administration user 'sa' on the SQL Server. 3. Conversion Database - Enter the name of an intermediate Conversion Database to be used during conversion, and click the Create button. Its structure is built during Phase Refresh Database Lists - Click the Refresh Database Lists button to populate the Entity Conversion Database, 'symglbl' Conversion Database, and Application Database drop-downs. 5. Entity Conversion Database - If Reports To Entity and Shared Currency Master are checked on the Source tab, select the Entity Conversion Database that was loaded earlier at least through Phase 3, corresponding to this Site's direct parent or "Reports To" Entity MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-21

232 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 6. 'symglbl' Conversion Database - Choose the 'symglbl' Conversion Database loaded earlier. 7. Application Database - Select the Application Database for this entity. 8. Currency - If multi-currency was not enabled in the source database, enter a currency code for all records in the target database. This value may not be left blank, and you cannot change the value during or after the conversion. Step E: Make Selections on the Options tab 1. MAPICS Path - The SyteLine ERP 7 installation path defaults here. 2. Logfile Path - Enter a Logfile Path where logfiles will be written. The default is the Working Directory of the conversion program SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

233 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 3. Starting and Ending Table - (Optional) Enter Starting and Ending Table to limit processing to a specific range of data. This is a strict range and does not accept wildcards. It can be used to parallel-process portions of certain phases on different computers connected to one SQL Server (ensuring that each phase is completed on all computers before beginning the next phase), or to re-convert individual tables after correcting errors in the source data. For Phase 1, use extensionless.d names. For Phase 2, use SyteLine 6 table names (with hyphens). For Phases 3-4, 7, and 8, use SyteLine 7 table names (with underscores instead of hyphens). For User Extended Tables, specify the extensionless.d name in Phase 1 and the corresponding SyteLine table in other Phases according to the guidelines in the preceding sentence. Refer to the tables below as examples: In Phase 1 To process: memo-top.d memo-top.d7 prd-item.d prd-item.d7 item.d item.d7 xitem.d xitem.d7 Specify: memo-top prd-item item xitem In Phase 2 To process: memo-top.d7 [memo-topic] prd-item.d7 [prod-mix-item] item.d7 [item] xitem.d7 [ux-item] Specify: memo-topic prod-mix-item item item In other Phases To process: Specify: 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-23

234 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) [memo-topic] memo_topic [prod-mix-item] prod_mix_item [item] item [ux-item] item memo_topic prod_mix_item item item After you ve converted the data, click the Compare Converted Record Counts button on the Options tab. This action compares the record-counts of the tables in the selected range between the Conversion and Application Databases and reports those which are different. Use this to verify that no tables were inadvertently skipped. 4. Fast Load Large Tables - Select Fast-Load Large Tables for Phases 2 and/or 3 and if Dump4bcp.p was used to unload large tables from the source database. 5. Stop at First Error - Select Stop at First Error to stop the conversion upon first detection of any error or data anomaly. Clear this option to continue processing the next table(s) and/or Phase(s). In either case, detected errors are logged to the Status tab and written to a logfile. 6. Maximum Errors for bcp - Phase 2 uses the bcp (Bulk Copy) utility to import data from flat-files. Bcp performs minimal validation as rows are imported, including checking for proper data-types and lengths. If the number of rows that fail validation is below a threshold, bcp imports the remaining rows and reports the errors encountered. Otherwise bcp imports nothing. Enter the number of data errors for bcp to detect before aborting the import for each table. Use this option if a table is failing validation. To help determine which rows contain errors, increase the value until the remaining rows are imported, then determine which rows are missing from the Conversion database. 7. Truncate Overstuffed Character Fields - Select Truncate Overstuffed Character Fields to automatically truncate all character fields with values in the source database set longer than the display format. The extraneous data remains in the conversion database, but no warning is shown. Clear this option to abort loading the entire table when this condition is detected. This allows anomalies to be found without running overstuff.p SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

235 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 8. Substitute for Leading Spaces - Enter a single character to Substitute for Leading Spaces in non-formatted character fields. Leading spaces are not allowed in SyteLine ERP 7, except in alpha-keys (for example, CO number, PO number), and in account numbers when the account format is numeric with leading zeroes suppressed (for example, "ZZZZZ"). To maintain sorting as in the source database, enter a character that sorts before the first character of the lowest-sorting non-space-led field in any field in any table containing leading spaces (exclamation, double-quote, #, $, %, &, single-quote, (,), *, +, comma, -, period, slash; and unless digits are used to start fields, also any digit, colon, semi-colon, <, =, >, questionmark, Step F: Click the Run Conversion Button Click the Run Conversion button to start processing. The Status tab shows the progress. An alert-box and bell signal completion. At completion, the progress is appended to a file "convert.log" in the Logfile Path. Step G: Repeat Previous 5 Steps if Necessary Repeat for additional Phases or Table ranges. The Final Conversion phase should not be run until all prior Phases have completed. Step H: Perform Post Conversion Tasks After conversion is complete, perform the Post-Conversion Tasks on page Step I: Repeat for additional Entity database(s) Repeat the above Load Data From Entity Database(s) steps for any additional entity databases MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-25

236 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Load the Data From Site Database(s) Step A: Make Selection on the Overview Tab On the Overview tab, clear Load 'symglbl' Data SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

237 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Step A: Make Selections on the Source Tab 1. Schema Level - Choose the schema level of your source database. 2. Multi-Byte - Select Multi-Byte if the source database uses a Multi-Byte code-page. Phase 1 looks for.d7w files created by DumpUTF8.p and translates them to.d7u files. Phase 2 looks for.d7u files. All data is translated to Unicode during conversion. 3. Multi-Site - Select Multi-Site. The Reports To Entity becomes active. 4. Reports To Entity - Select Reports To Entity if this site reports to a higher level entity in the hierarchy. 5. Multi-Currency - Select Multi-Currency if the source database had multicurrency enabled. If not, clear this field and enter a new currency code on the Destination tab. 6. Shared Currency Master - Select Shared Currency Master if this site shared the currency master data from a higher-level entity or from the global database. 7. Data Path - Enter the data path to which the entity database was unloaded MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-27

238 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 8. Prepared Data Path - Enter a new directory into Prepared Data Path, where prepared data files will be stored during conversion. This drive requires available space approaching the total size of the unloaded files located in the data path. Step B: Make Selections on the Destination Tab 1. SQL Server - Enter the name of the SQL Server on which all databases will reside. 2. sa Password - Enter the password for the System Administration user 'sa' on the SQL Server. 3. Conversion Database - Enter the name of an intermediate Conversion Database to be used during conversion, and click the Create button. Its structure is built during Phase Refresh Database Lists - Click the Refresh Database Lists button to populate the Entity Conversion Database, 'symglbl' Conversion Database, and Application Database drop-downs. 5. Entity Conversion Database - If Reports To Entity and Shared Currency Master are checked on the Source tab, select the entity conversion database that was loaded earlier, corresponding to this site's direct parent or "Reports To" Entity SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

239 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 6. 'symglbl' Conversion Database - Choose the 'symglbl' Conversion Database loaded earlier. 7. Application Database - Select the Application Database for this entity. 8. Currency - If multi-currency was not enabled in the source database, enter a currency code for all records in the target database. This value may not be left blank, and you cannot change the value during or after the conversion. Step C: Make Selections on the Options tab 1. MAPICS Path - The SyteLine ERP 7 installation path defaults here. 2. Logfile Path - Enter a Logfile Path where logfiles will be written. The default is the Working Directory of the conversion program. 3. Starting and Ending Table - (Optional) Enter Starting and Ending Table to limit processing to a specific range of data. This is a strict range and does not accept wildcards. It can be used to parallel-process portions of certain phases on different computers connected to one SQL Server (ensuring that each phase is completed on all computers before beginning the next phase), or to resume conversion or re-convert individual tables after correcting errors in the source data. For Phase 1, use extensionless.d names MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-29

240 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) For Phase 2, use SyteLine ERP 5 or 6 table names (with hyphens). For Phases 3-4, 7, and 8, use SyteLine ERP 7 table names (with underscores instead of hyphens). For User Extended Tables, specify the extensionless.d name in Phase 1 and the corresponding SyteLine table in other phases according to the guidelines in the preceding sentence. When using ranges, note that hyphen sorts lower than (i.e., comes before) a, and underscore sorts higher than (i.e., comes after) z. A simple method for starting at the first table after table is to specify Starting Table as table- (the name of the table followed by a hyphen). This excludes table itself but processes any table having a prefix identical to table followed by any letter, hyphen, or underscore. A simple method for ending at the last table before table is to specify Ending Table as tabld_zz (the name of the table with its last character replaced by the preceding letter or digit followed by underscore and 2 z s). Again this excludes table itself but processes any table having a prefix near to table followed by any letter, hyphen, or underscore and any other letters (because no SyteLine tables contain 2 adjacent underscores). Using these methods, it is not necessary to know the entire list of tables or at which specific table the process is to be started or ended. Refer to the tables below as examples: In Phase 1 To process: memo-top.d memo-top.d7 prd-item.d prd-item.d7 item.d item.d7 xitem.d xitem.d7 Specify: memo-top prd-item item xitem SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

241 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) In Phase 2 To process: memo-top.d7 [memo-topic] prd-item.d7 [prod-mix-item] item.d7 [item] xitem.d7 [ux-item] Specify: memo-topic prod-mix-item item item In other Phases To process: [memo-topic] memo_topic [prod-mix-item] prod_mix_item [item] item [ux-item] item Specify: memo_topic prod_mix_item item item 4. Fast Load Large Tables - Select Fast-Load Large Tables for Phases 2 and/or 3 and if Dump4bcp.p was used to unload large tables from the source database. 5. Stop at First Error - Select Stop at First Error to stop the conversion upon first detection of any error or data anomaly. Clear this option to continue processing the next table(s) and/or Phase(s). In either case, detected errors are logged to the Status tab and written to a logfile. 6. Truncate Overstuffed Character Fields - Select Truncate Overstuffed Character Fields to automatically truncate all character fields with values in the source database set longer than the display format. The extraneous data remains in the conversion database, but no warning is shown. Clear this option to abort loading the entire table when this condition is detected. This allows anomalies to be found without running overstuff.p MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-31

242 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 7. Substitute for Leading Spaces - Enter a single character to Substitute for Leading Spaces in non-formatted character fields. Leading spaces are not allowed in SyteLine ERP 7, except in alpha-keys (for example, CO number, PO number), and in account numbers when the account format is numeric with leading zeroes suppressed (for example, "ZZZZZ"). To maintain sorting as in the source database, enter a character that sorts before the first character of the lowest-sorting non-space-led field in any field in any table containing leading spaces (exclamation, double-quote, #, $, %, &, single-quote, (,), *, +, comma, -, period, slash; and unless digits are used to start fields, also any digit, colon, semi-colon, <, =, >, questionmark, Step D: Click the Run Conversion Button Click the Run Conversion button to start processing. The Status tab shows the progress. An alert-box and bell signal completion. At completion, the progress is appended to a file "convert.log" in the Logfile Path. Step E: Click Run Conversion Button for Additional Phases or Table Ranges Repeat the Load the Data From Site Database(s) steps for additional phases or table ranges, and click the Run Conversion button when ready. Do not run the final conversion phase until all prior phases have completed. Step F: Perform Post Conversion Tasks After conversion is complete, perform the Post-Conversion Tasks on page Step G: Repeat Load the Data From Site Database(s) steps for Additional Site Databases Repeat the Load the Data From Site Database(s) steps for additional site databases. The steps for performing conversion are now complete. Following the Post Conversion Tasks, the rest of this chapter is reference material and troubleshooting tips. Post-Conversion Tasks The following tasks are required after conversion to prepare the application database for use with SyteLine ERP 7: 1. Open the License Management form and enter your license key. See the SyteLine ERP 7 System Administration Guide for more information on license management SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

243 Outputs Disk Usage Converting From SyteLine 5 or SyteLine 6 (Multi-Site) 2. Enter password for all user records. Because passwords are stored in an encrypted format, they cannot be brought forward from the source database. 3. Set up form-based, user-, and group-level security. See the SyteLine ERP 7 System Administration Guide or the online help for more information on how to set up user authorizations. 4. Unhide and appropriately label any desired User-Defined Fields on Forms User-Defined tabs. Name Phase Directory Contents Convert.log All Logfile Path Contents of the Status tab Load.log 2 Prepared Data Path Number of records loaded per table; format is comparable to "un-load.log" from the Database Unload utility. Load2.log 3 Logfile Path Number of records converted per table Crewsize.log Final Logfile Path List of records whose nonintegral Crew Size was altered Plan for the following space requirements: Data Store Source database (Progress) Estimated Size X Needed Through Database Utilities Unload (pre Conversion) Unloaded data files (*.d) 80% of X Conversion Phase 1 (Prepare Data Files) Prepared data files (*.d7) 55% of X Conversion Phase 2 (Load Data Files) Conversion database (SQL) Application database transaction log (SQL) Application database data files (SQL) 150% of X Final Conversion (OK to Shrink after Phase 2) 35% of X Final Conversion (OK to Shrink after Final Conversion) 350% of X MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-33

244 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) High-water mark when 535% of X N/A minimizing Total when not minimizing 770% of X N/A SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

245 Troubleshooting Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Following are some common errors that might occur during conversion, with suggested remedies: Phase Error Where Remedy 2 String data, right truncation 3 Cannot insert the value NULL into column 'xxx', table 'zzz.dbo.yyy'; column does not allow nulls. INSERT fails. 3 INSERT statement conflicted with COLUMN CHECK constraint 'CK_yyy_xxx'. The conflict occurred in database 'zzz', table 'yyy', column 'xxx'. 4 ALTER TABLE statement conflicted with COLUMN FOREIGN KEY constraint 'kkk'. The conflict occurred in database 'zzz', table 'yyy', column 'xxx'. <Prepared Data Path>\ <dumpname.err> Convert.log Convert.log Convert.log Run overstuff.p in the source database to find overstuffed fields. Correct these in the source database and unload again, or modify the <VerId>/*.tbl file to allow for more data, and use the Truncate option. Run ValNull.p in the source database to find invalid (Blank) and (Unknown) fields. Correct these in the source database and unload again, or Use SELECT statements in the Conversion database to find offending records. Correct or delete these and re-run Phase 3 for this table. Use SELECT statements in the Conversion database to find offending records. Correct or delete these and re-run Phase 3 for this table. Run ValFK.p in the source database to find invalid foreign-key references. Correct these in the source database and unload again, or Use SELECT statements in the Application database to find offending records. Correct or delete these and re-run Phase 4 for this table. See Resolving Foreign-Key Conflicts MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-35

246 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Resolving Foreign-Key Conflicts A Foreign-Key Relationship is a reference in one record to the primary-keys of another record. For example, most G/L Account columns must either be Null or refer to an existing record in the Chart of Accounts table. The SyteLine 7 Application database utilizes SQL Foreign-Key Constraints to enforce these relationships, thus ensuring referential integrity between tables. If a reference is incorrect in the source database, a Foreign-Key Conflict is raised during Phase 4. All such conflicts must be resolved before the database is ready for use with SyteLine 7. Following is an example of resolving a Foreign-Key Conflict. The SQL error message for this example is: *** Error occurred during Apply coh.key to SyteLine_App ALTER TABLE statement conflicted with TABLE FOREIGN KEY constraint 'cohfk1'. The conflict occurred in database 'SyteLine_App', table 'customer'. The above message has the following information: The record containing the incorrect reference is located in the "coh" table (foreign-key table). The reference is intended to identify a record in the "customer" table (primary-key table). The name of the foreign-key relationship is "cohfk1" (constraint name). The relationship is described in the file <MAPICSInstallDir>\SyteLine\ApplicationDB\Foreign Keys\coh.key. If the relationship is based on a single key column, its name is also given. This information is also listed in the.key file. To resolve the conflict, do the following: 1. Determine which columns in the foreign-key table "coh" are meant to refer to which columns in the primary-key table "customer." These are listed in the.key file under the name of the relationship as in the example below: ADD CONSTRAINT cohfk1 FOREIGN KEY ( cust_num, cust_seq ) REFERENCES customer ( cust_num, cust_seq SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

247 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) ) 2. Build a T-SQL statement in the Query Analyzer to find incorrect references as in the example below: SELECT co_num, cust_num, cust_seq FROM coh WHERE cust_num IS NOT NULL AND NOT EXISTS(SELECT 1 FROM customer WHERE customer.cust_num = coh.cust_num AND customer.cust_seq = coh.cust_seq) The above statement shows (SELECT) the key column(s) (co_num) and incorrect references (cust_num, cust_seq) from every record in the foreign-key table (coh) whose foreign-keys (coh.cust_num, coh.cust_seq) seemingly refer to a record (NOT NULL) but do not identify (NOT EXISTS) a record in the primary-key table (customer). A grid is displayed that lists the selected columns for each record with an incorrect reference. You now decide how to address each incorrect reference. Choose from among the following 3 options: Change the foreign-key columns to refer to an existing primary-key record. For example: UPDATE coh SET cust_seq = 4 WHERE coh.co_num = 'S ' Add a new primary-key record with primary-keys to match the foreign-keys (not recommended at this point in the process, because SyteLine triggers are disabled and will not provide their normal validation or cascading actions); or Change the foreign-key columns to Null. For example, to affect all incorrect records: UPDATE coh SET cust_num = NULL, cust_seq = NULL FROM coh WHERE cust_num IS NOT NULL AND NOT EXISTS(SELECT 1 FROM customer WHERE customer.cust_num = coh.cust_num AND customer.cust_seq = coh.cust_seq) All references are correct for this constraint when the SELECT statement above displays an empty grid MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-37

248 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) After all references are correct for all constraints in a.key file, phase 4 can be re-run for the foreign-key table (enter the table name "coh" in both the Starting Table and Ending Table fields). Relative Duration Re-entrance The following table approximates the relative successful completion times of each phase: Phase % Results may vary and can differ greatly when parallel processes are used. Phases 1-4, 6, and 8 can be re-executed for individual tables or ranges if data inconsistencies are detected and corrected. The following table provides details: Phase Preparation Required Before Re-execution Details 1 None.d7 file will be overwritten by default 2 None Table in Conversion database is dropped and re-created by default 3 Truncate table in Application database Depending on the type of error received during previous execution, data may remain in the table; we do not truncate by default 4 None Existing constraints are dropped for each table and re-created by default 6 None Stored Procedure purges all data before recreating it. 8 None Table in Conversion database is dropped and re-created by default SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

249 Parallel Execution Converting From SyteLine 5 or SyteLine 6 (Multi-Site) Phases 1-4 can be executed on multiple computers or multiple processes in parallel, to reduce total duration. This is especially useful on multi-processor systems. 1. Start multiple instances of SLConv.exe on 1 or more computers. 2. Enter a unique Logfile Path for each instance; all other options should be identical. 3. Use the Starting Table/Ending Table range option to split the load. Note your largest tables by size of.d and attempt to group these separately (for example, if largest tables are ledger and matltran, then use 4 ranges: a-l, l-m, m-n, n-z). Note: Range l-m does not process any tables beginning with "m", because "matlearn" (the first table beginning with "m") sorts higher than "m" in dictionary order. Another way to process the same range is l-l_zz. When using parallel execution, follow these guidelines for minimum contention: Phase Guideline 1 None 2 None 3 Start first instance; wait until it has finished dropping foreign-keys and loaded user_local table; then start remaining instances. 4 None Monitor system load to avoid performance degradation MAPICS, Inc. SyteLine ERP 7 Installation Guide 12-39

250 Converting From SyteLine 5 or SyteLine 6 (Multi-Site) SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

251 13 Uninstalling SyteLine ERP If you have a version of SyteLine ERP 7 and want to upgrade to another version of SyteLine ERP 7 (for example, from SyteLine ERP 7.02 to SyteLine ERP 7.03), you MUST uninstall the old version before installing the new version. This is true for all pieces of your system; the database server, utility server, all clients, planning server, web server, and exchange components. Uninstalling DOES NOT remove databases. When going through the uninstall wizard, follow all the prompts you are given, including any requests to reboot your machine. 1. Make sure all users are logged out of the system. 2. Make a backup of all databases. 3. At the server or client machine of your choice, go to Add/Remove Programs. You can uninstall in any order. 4. Select the SyteLine ERP piece you want to uninstall and click the Change button. 5. Navigate through the wizard until you get the option to Modify, Repair, or Remove. 6. Select Remove and click Next. 7. The next screen gives you two options: Removing to Upgrade - Choose this option if you are upgrading from one version of SyteLine ERP 7 to another (for example, from SyteLine ERP 7.02 to SyteLine ERP 7.03). This option leaves some registry entries regarding configurations so that you don t have to define them again when installing the new version. Removing Product - Choose this option if you want to completely remove SyteLine ERP. Select either Removing to Upgrade or Removing Product. 8. Click Next MAPICS, Inc. SyteLine ERP 7 Installation Guide 13-1

252 Uninstalling SyteLine ERP 9. At the Remove the Program screen, click Remove. The uninstall process may take several minutes. 10. When the uninstall process if complete, click Finish SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

253 A Setting Up the Online Help By default, the SyteLine ERP online help is installed on each client computer and you do not need to perform any special steps to use it. However, you can install the help on a network server for central access by all client computers. This appendix describes how to configure each SyteLine client computer to open the help from a network server. This chapter also provides troubleshooting information to help you solve any possible problems with accessing the online help, whether it is installed on the local client computer or on a network server. Installing Help to a Central Location You can install the help on a network server for central access by all client computers. Follow the steps below. 1. Create a folder structure for the online help on a server where you want to store the help files (make sure your SyteLine client machines can access this server). The folder structure should consist of a root folder of any name (for example, "sytelinehelp") followed by the \Language subfolder and the appropriate language ID subfolders. These language ID subfolders are specified for each language ID in the HelpSubDirectory field on the Language IDs form in SyteLine. For example, if your system supports English (1033) and Japanese (1041) languages, you may have a folder structure like this: \\myserver\sytelinehelp\language\1033 \\myserver\sytelinehelp\language\ MAPICS, Inc. SyteLine ERP 7 Installation Guide A-1

254 Setting Up the Online Help 2. Copy the following.chm files and corresponding.chw files from c:\program files\mapics\syteline\language\1033 folder (on any computer where you have installed SyteLine) to the corresponding network location for the help: config.chm customer.chm dc.chm edi.chm financial.chm hr.chm material.chm production.chm projects.chm symforms.chm syteline.chm vendor.chm winstudio.chm winstudiouser.chm The location you copy the files to should be <servername>\<root folder>\language\<helpsubdirectory>, where root folder is some folder you have designated as the location for the help files and HelpSubDirectory is the folder associated with the Language ID as specified on the Language IDs form. For example, \\myserver\sytelinehelp\language\1033. A-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

255 Setting Up the Online Help 3. Use the WinStudio Application ID Editor to edit the SyteLine Application ID. a. Select Start>Programs>MAPICS>Tools>WinStudio App ID Editor or select WinStudioAppIDEditor.exe from the folder where SyteLine ERP 7 is installed (usually C:\Program Files\MAPICS\Syteline). b. In the Application IDs list, select the application ID you defined when you set up this SyteLine client (for example, it may be "SyteLine- <sessionsservername>" or "SyteLine"). If you aren t sure what application ID SyteLine is using, check your SyteLine shortcut s Properties. The Target specification should contain the path to Winstudio.exe, followed by a "-a" parameter that specifies the application ID. If the path does not contain the -a parameter, SyteLine is using the <default> application ID MAPICS, Inc. SyteLine ERP 7 Installation Guide A-3

256 Setting Up the Online Help c. Click Edit. The following screen appears. d. On the Main tab, edit the Base Help Path to point to the root help folder for the online help on the server (for example, \\myserver\sytelinehelp). Do not point to the individual language ID folders. Although your English help files are located in \\myserver\sytelinehelp\language\1033, you should still enter the Base Help Path as \\myserver\sytelinehelp. Do not end this path with a backslash. This path can be a UNC specification, as shown in the example, or can be a mapped drive. e. In the Base Help File field, enter syteline.chm. A-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

257 f. Click OK. You should be back at the initial screen. Setting Up the Online Help 4. In the Application IDs list, select SyteLine. 5. Click Export. 6. Save the application ID with the name SyteLine.reg. 7. Distribute the saved file to clients whose machines have network access to the Base Help Path folder. 8. Run the SyteLine.reg file on the client machines. 9. On all client computers that will run the help from the central location, you must delete the.chm and.chw help files (from the list shown in step 2) from the default local location, such as c:\program Files\MAPICS\Syteline\Language\1033). Doing this prevents the system from incorrectly calling help from the local location MAPICS, Inc. SyteLine ERP 7 Installation Guide A-5

258 Setting Up the Online Help Troubleshooting Online Help Access This section lists possible problems that may arise with using the SyteLine online help and how you can solve them. In the descriptions below, the phrase "online help files" refers to the 13.chm files that are installed with SyteLine (for example, syteline.chm, material.chm, customer.chm, etc.). Help doesn t display PROBLEM Help doesn t display when you click the help button, use the Help menu, or press F1. The error message may look like this: In some cases, the error may not appear and the help does not display. SOLUTION 1. Edit the properties for the shortcut you are using to start SyteLine (rightclick the shortcut icon and choose Properties). 2. Verify that the Start in specification points to the location of Winstudio.exe. This is most likely C:\Program Files\MAPICS\SyteLine. A-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

259 Setting Up the Online Help 3. Look at the Target specification to determine the application ID that SyteLine is using when you start your client session. If the command line contains the "-a" parameter, the application ID is specified in the -a parameter. For example, in the picture above, the application ID is "MyAppID." If the command line does NOT contain the -a parameter, SyteLine is using the "<default>" application ID. Make a note of the application ID name because you will need it in the next steps. 4. Close the shortcut s Properties dialog. 5. If the SyteLine Administrative Client is installed on this client computer, open the WinStudio Application ID Editor (Start > Programs > MAPICS > Tools > WinStudio App ID Editor) program. If the client computer has the SyteLine End User Client installed, the Winstudio Application ID Editor is not available; skip to step In the Application ID Editor, select the application ID you identified in step 3. Select <default> if you determined that you aren t using an application ID. 7. Click the Edit button. 8. On the Properties form for the application ID, find the "Help Information" box: 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide A-7

260 Setting Up the Online Help 9. Verify that the Base Help Path is pointing to the location where your help files are installed. By default, the Help Base Path is empty. This empty state directs SyteLine to open the help files from the local client computer in the \Language\1033 folder under the folder containing the Winstudio.exe program (most likely C:\Program Files\MAPICS\SyteLine\Language\1033). If you are using a CITRIX server, the empty Help Base Path does not resolve correctly; therefore, if you are using CITRIX, you must enter the path to, but not including, the local \Language folder where your help files are installed. For example, in a default SyteLine installation using CITRIX, the Help Base Path should be C:\Program Files\MAPICS\SyteLine. Do not end this path with a backslash. Also, the empty Help Base Path may not resolve correctly in some standard, non-citrix installations. If you have a problem accessing the help, you may need to enter the full local path to the help as described above. The Base Help Path can also be a path pointing to, but not including, a remote \Language folder on a network. For example, if your help files are located in \\myserver\helpfolder\language\1033, the Help Base Path should be \\myserver\helpfolder. This path can be a UNC specification, as shown in the example, or can be a mapped drive. Do not end this path with a backslash. 10. If the WinStudio App ID Editor is not available on this computer, open the Windows Registry Editor. 11. If you identified an application ID in step 3, navigate to the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Mongoose\<application ID name>\winstudio\appid. If you determined that you are not using an application ID, navigate to the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Mongoose\Winstudio\AppID. 12. Locate the HelpBasePath string value. 13. As described in step 9, verify the path specified in the HelpBasePath value. A-8 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

261 Help window appears but topics display blank Setting Up the Online Help PROBLEM The SyteLine help window appears, but the help topic is blank. SOLUTION Check your Internet Explorer security settings under the Local Intranet zone; Active Scripting must be set to Enable. 1. In Internet Explorer, select Tools > Internet Options. 2. Select the Security tab. 3. Select Local Intranet. 4. Click the Custom Level button MAPICS, Inc. SyteLine ERP 7 Installation Guide A-9

262 Setting Up the Online Help 5. In the Security Settings dialog, find the Scripting section. Make sure Active Scripting is set to Enable: 6. Click OK to save your settings. Topics display with an error message PROBLEM When you open a help topic within the SyteLine help, you see the message "Your current security settings prohibit running ActiveX controls on this page. As a result, the page may not display correctly." SOLUTION Check your Internet Explorer security settings under the Local Intranet zone. Script ActiveX controls marked safe for scripting must be set to Enable. Run ActiveX controls and Plugins must be set to Enable. 1. Follow steps 1-4 in Help window appears but topics display blank above. 2. In the Security Settings dialog, find the ActiveX Controls and Plugins section. Make sure Script ActiveX controls marked safe for scripting is set to Enable. 3. Make sure Run ActiveX controls and Plugins is set to Enable. 4. Click OK to save your settings. 5. Follow steps 1-4 in Help window appears but topics display blank above. 6. In the Security Settings dialog, find the ActiveX Controls and Plugins section. Make sure Run ActiveX controls and Plugins is set to Enable. A-10 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

263 Links within the help do not work Setting Up the Online Help PROBLEM When you click a link with the SyteLine help, you see an error message like this: "Internet Explorer Script Error: an error has occurred in the script on this page." POSSIBLE SOLUTION 1 You may be using Internet Explorer version 6.0 without service pack 1. To check the version, open Internet Explorer and select Help > About Internet Explorer. The Update Versions field should list SP1 (or a later service pack) as one of the update versions. If it does not, you must download service pack 1 from the Microsoft Web site. POSSIBLE SOLUTION 2 Check your Internet Explorer security settings under the Local Intranet zone. Script ActiveX controls marked safe for scripting must be set to Enable. Run ActiveX controls and Plugins must be set to Enable. See Topics display with an error message above for steps. Add Note or Open Form buttons do not work PROBLEM When you click the Add Note or Open Form buttons that appear at the top of the SyteLine help window, you see an error message like this: "Internet Explorer Script Error: an error has occurred in the script on this page." SOLUTION You must install the KeyHelp.OCX file on the client computer in a folder that is in the computer s PATH environment variable, such as C:\Winnt\System32. This file should have been installed automatically during the SyteLine setup process MAPICS, Inc. SyteLine ERP 7 Installation Guide A-11

264 Setting Up the Online Help If you have Web access on this computer, the online help will prompt you to download the missing KeyHelp.OCX file each time you open a different help topic: When you see this message, simply click Yes and the file will be installed. If you are unable to install the file in this manner, contact Support to obtain a copy of KeyHelp.OCX. A-12 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

265 B Installing the Fax Service We recommend that you install your fax server on the machine that is running Task Manager (typically the utility server). However, if your fax server is on a different machine, follow these instructions to install the fax service, which will enable Task Manager to communicate with your fax server. 1. Create a directory on the fax server machine to hold the service. This directory can be located anywhere on the fax server machine and can be named anything. 2. On the utility server machine, navigate to \\Program Files\MAPICS\SyteLine\Taskman, and copy the following files to the directory you created on the fax server machine: SendFax.exe FaxService.exe FaxSvrInstall.exe FaxSvrRemove.exe. 3. Navigate to the folder you created on the fax server machine, and doubleclick on FaxSvrInstall.exe to create the service. 4. In the registry, create the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Mongoose\FaxServer 5. For each instance of Task Manager the service is to monitor, create a string value called TaskmanPathN, where N is the total number of Task Manager instances that the service will be monitoring MAPICS, Inc. SyteLine ERP 7 Installation Guide B-1

266 Installing the Fax Service B-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

267 C Replication Setup Checklist Use this checklist as you set up your multi-site environment. The checklist refers you at times to certain chapters in this manual. Some of the steps have prerequisites that aren t listed in this appendix; you will read those prerequisites in the chapter to which you are referred. For example, when you set up the database server, a prerequisite is to already have SQL 2000 Server installed and configured on the database server machine; that information is in the database server chapter and not in this appendix. Use this checklist as a guide, but get the details from the chapters to which you are referred. For Your Reference In addition to the chapters in this manual to which you are referred, use the following manuals as reference material about multi-site and replication: SyteLine ERP 7 System Administration Guide (Multi-site chapter) Replication Both manuals are found on the web at Once there, perform the following steps: 1. Login. 2. Select the radio button to Load the SyteLine menu. 3. Click OK. 4. Click the link for Product documentation. 5. Follow the links to SyteLine ERP for the version you want. Replication Categories and Replication Rules Forms We strongly recommend that you contact MAPICS Professional Services for assistance if you plan to change existing categories or create new ones. Improperly creating and executing replication categories and rules can result in a catastrophic loss of data MAPICS, Inc. SyteLine ERP 7 Installation Guide C-1

268 Replication Setup Checklist Step A: Set Up the Database Server See Setting Up the Database Server on page 2-1 for set up instructions. The steps in that chapter detail how to set up a single site environment; that is the first step in the process of setting up a multi-site environment. You need to set up an application database for each site or entity in your multi-site environment. While it is not required to set up the utility server and clients before moving on to the next step, if you want to have a working single site environment before you set up your multi-site environment, set up the utility server and clients here (you need to have the utility server and at least one client set up before you can complete all the steps in this appendix; this is a good time to do it). See Setting Up the Utility Server on page 3-1 to set up the utility server and Setting Up a Client Workstation on page 4-1 to set up clients. Perform all appropriate post-installation tasks mentioned in those chapters. Step B: Run the SyteLine Configuration Wizard on the Database Server This is not the first time you will have run the SyteLine Configuration Wizard on the database server. The first time you ran the wizard on the database server was to configure each database. This time you run the wizard to link the databases you want to link. See Setting Up a Multi-Site Environment on page 6-1 for instructions. Step C: Set Up the Web Server If you plan to use non-transactional replication, you MUST set up the Web Server components on the utility server. See Chapter 9, Setting Up the Web Server" for information on how to install and configure these components. If you will be using only transactional replication, you can skip this step. Step D: Make Sure Services are Started If you plan to use non-transactional replication, make sure the MAPICS Replication Listener and MAPICS Replicator services are started on the utility server. C-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

269 Step E: Open Replication Management Form Replication Setup Checklist At this point, you must have your utility server and at least one client set up. You should have also applied your license on the License Management form by now. Use the Replication Management form as a guide as you set up the rest of the multi-site environment. You need to come back here and click the Regenerate Replication Triggers button to put into effect any changes you make on the Replication Rules form. 1. On the Replication Management form, click the Intranets link to open the Intranets form. Every site MUST be attached to an intranet. The installation process creates one intranet named USA. You can attach sites to the USA intranet (on the Sites/Entities form), or you can create other intranets. On the Reports/TaskMan tab of the Intranets form, make sure the Task Man Path is set properly; this is the path to the folder containing the Task Manager utility. If this folder is on the COM+ server (the utility server), you can specify the full path (for example, c:\program Files\MAPICS\SyteLine\Taskman). Otherwise, you can specify the path from a shared drive (for example, \\myserver\taskman). If you plan to use non-transactional replication, make sure the Private Queue field on the General tab is selected MAPICS, Inc. SyteLine ERP 7 Installation Guide C-3

270 Replication Setup Checklist 2. On the Replication Management form, click the Sites/Entities link to open the Sites/Entities form. Use this form to define a site by a code and a description. You can also attach sites to an intranet. If two or more sites are on the same LAN, you can attach them to the same intranet to speed up the data transfer during non-transactional replication. On this form, at a minimum, be sure to visit the following tabs/fields: System Info tab - Verify the information in the Strings Table Specification field. Without this information, the labels on reports will not display properly. The information defaults here from information you provided during the utility server configuration (you could have opted to leave the field blank). Live Linked Sites tab - This is where you create the connection from one site to another. Choose the To Site from the drop down list, and enter in the linked server name. Site User Map tab - The user name must be the same at both the source and target sites. You must enter a record for each site. For example, suppose you have three sites: Ohio; Arizona; and Michigan. In Ohio, set up a site user map with From Site set to Arizona and another record with From Site set to Michigan. In Arizona, set up a site user map connecting to Ohio and another connecting to Michigan. In Michigan, set up a site user map connecting to Arizona and another connecting to Ohio. In Ohio, the setup would look like this: Site From Site User Name OH AZ Bob OH MI Bob Link Info tab - Use the fields on this tab only if you want to disable replication without having to change the replication rules. 3. On the Replication Management form, click the Replication Categories link to open the Replication Categories form. SyteLine ERP is shipped with several categories, but you can create more if you wish. If you plan to create your own categories, we strongly recommend that you contact MAPICS Professional Services for assistance. Improperly creating and executing replication categories and rules can result in a catastrophic loss of data. All tables and stored procedures associated with each category are listed; select the category in the left pane to see the tables and stored procedures associated with it on the right. C-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

271 Replication Setup Checklist 4. On the Replication Management form, click the Replication Rules link to open the Replication Rules form. Use this form to set rules for replication. You choose the source site and the target site and the intervals at which you want the replication to occur (intervals other than "Transactional" are for non-transactional replication). Once you change the replication rules, you must go to the Replication Management form and click the Regenerate Replication Triggers button for the changes to take effect. Replication Setup Complete At this point you are finished setting up replication for your multi-site environment. You still need to establish all the financial parameters in the system. There are other forms in the system regarding replication and multisite discussed in the SyteLine ERP 7 System Administration Guide (Multi-site chapter). Troubleshooting If replication isn t working, check the following things: 1. Replication Errors form - This form shows the data that failed to submit to a target site during non-transactional replication. Use the form to fix and resubmit data, or delete it. 2. Replication Triggers - You MUST click this button on the Replication Management form after any replication rules have been changed. Failure to do so will result in replication not working properly. 3. ReplicatedRow3 and ShadowValues tables - When something is to be replicated it gets copied to the ReplicatedRow3, and ShadowValues tables. If the data is not there, it is likely that either your replication rules aren t set properly or that you need to click the Regenerate Replication Triggers button on the Replication Management form. 4. Services - If you plan to use non-transactional replication, make sure the MAPICS Replication Listener and MAPICS Replicator services are started on the utility server. 5. MSMQ or Message Queuing - Turn on journaling MAPICS, Inc. SyteLine ERP 7 Installation Guide C-5

272 Replication Setup Checklist C-6 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

273 D Setting Up an End User Client for HTTP Access You can configure end user clients to access the utility server by using HTTP/ XML protocol instead of the standard DCOM calls. You should do this if: the end user client is outside the firewall, or your system does not use Microsoft networking software. In either of these cases, the standard DCOM calls will not work. We recommend that you set up only End User Clients for HTTP access, not Administrative Clients. Web Server Setup If you configure your clients for HTTP access, install the web server on the same machine as the utility server. Client Installation and Setup After installing the End User Client as described on page 4-2, do not run the SyteLine Configuration Wizard, which is normally how you define the client s session server (utility server). Instead, use one of the following methods to define the session server on the client: Add a command line parameter to the SyteLine shortcut. winstudio.exe -shttp://<url>/<virt_directory>/ido/sessionmanager.asp URL could be either: the utility server name, if running over a LAN, or an internet-accessible URL (for example, if running across the internet. See your IIS documentation for more information about mapping that URL address to a server MAPICS, Inc. SyteLine ERP 7 Installation Guide D-1

274 Setting Up an End User Client for HTTP Access virt_directory is the virtual directory specified during the Web Server installation (see page 9-12), for example, the virtual directory might be named SL. Use the WinStudioApplicationIDEditor utility and specify the server name in the Session Manager Server field. WinStudioApplicationIDEditor is installed only on Administrative clients. However, you can perform an export from WinStudioAppIDEditor, which creates a.reg file that you can then run on each client to set the Session Manager value in the client s registry. Run SyteLine ERP Once you have set up your client workstation, you should be able to run SyteLine ERP from your SyteLine shortcut. D-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

275 E MAPICS.NET Web Service Test Utility This utility provides a test client for the.net Web Service (.NET API). If you install the.net web service on your SyteLine web server and want to verify that it is installed and configured correctly without writing your own client, you can use this utility. You can test logging in and loading a collection (query). Starting the Utility From the web server machine s Start menu, select Start>All Programs>MAPICS>Tools> MAPICS.NET Web Service Test Utility. The following window displays: 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide E-1

276 MAPICS.NET Web Service Test Utility Connecting (Logging In) to the Web Service You can connect to the web service by selecting Connect from the WebService menu. The following dialog displays: Enter this information: Field Web Service URL User Name Password Configuration Description Enter a URL that points to the web service, in the format where webserver is the local host. Enter the name of a user who has access to the configuration. Enter the user s password. Click on the Configuration link to select from a list of configurations available for this web server, or enter an existing configuration name. When you have successfully connected to the web service, the status bar at the bottom of the utility window will look like this: E-2 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.

277 MAPICS.NET Web Service Test Utility Loading a Data Set After you log in, you can select Open DataSet from the WebService menu. This brings up the Open Data Set Parameters dialog: Enter the following information to specify the data set you want to load: Field IDO Name Properties Filter Description SyteLine IDO name, for example SYMIX.SLCustomers A comma-delimited list of property names to include in the data set, for example CustNum, Name Optional filter, for example CustNum like XYZ% Record Cap Default: use the default record cap (currently 200) Unlimited: no cap Other: Enter a user-specified cap 2004 MAPICS, Inc. SyteLine ERP 7 Installation Guide E-3

278 MAPICS.NET Web Service Test Utility Viewing Results Click OK to view the resulting data set. For example: E-4 SyteLine ERP 7 Installation Guide 2004 MAPICS, Inc.