Infor ERP LN 6.1 Data Converter

Transcription

1 Infor ERP LN 6.1 Infor ERP LN 6.1 Data Converter User's Guide

2 Copyright 2008 Infor All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor. By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor pursuant to a separate agreement ( Purpose ). In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above. Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause. Trademark Acknowledgements All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners. Publication Information Document code: U8261C US Release: Infor ERP LN 6.1 Publication date: July 08

3 Table of Contents Chapter 1 Introduction Target group Scope User profile Requirements Hardware requirements Software requirements Other requirements Known limitations of the tool Overview of the data converter tool Overview of the copy company tool Data conversion steps Copy Company Data steps Chapter 2 Conversion parameters Target environment Conversion Parameters (bctls0100m000) Source environment Conversion Parameters (bctls0101m000) Chapter 3 Preconversion activities Target environment Maintain Default Loading Method (bctls9588m000) Checking for Onpload Database Population (bctls0207m000) Source environment Import List of Tables to Convert (bctls9188m000)

4 ii Table of Contents Copy Data Dictionary (bctls2100s000) Generate Domain Differences between Source and Target (btls1110m000) Generate Table/Fields Differences between Source and Target (bctls1112m000) Maintain Table Linked Functions (bctls1115m000) Chapter 4 Conversion run Target environment Dump and Load (bctls0200m000) Load Only (bctls1214m000) Source environment Data dumping process Chapter 5 Utilities Analyze Utility Before Conversion (bctls5405s000) Details of Users Connected (bctls5406s000) Chapter 6 Reports Target environment Generate Error Report (bctls5200m000) Print Error Report (bctls5400s000) Source environment Create Data Dumps (bctls1113m000) error messages Target environment Load Data (bctls1214m000) error messages To recover after a data loading failure in case of DB2 database Manual procedure Step 1: Create a unique environment for the workstation environment Step 2: Create shared memory parameters Step 3: Create the table definition file Step 4: Set Variable BSE_REM Step 5: Create root remote user files Step 6: Start the shared memory manager Step 7: Start ba server for Infor ERP To establish the connection between the client and the server

5 Table of Contents iii To change your user data To create a second remote user file Set the BSE environment Start the bshell Environment variables Guidelines to write functions for new or changed fields: Guidelines to write functions for new tables: Common Path Settings OPERATING SYSTEM: UNIX Oracle Informix DB SQL Server

6

7 About this Guide This document is a User s Guide that describes the steps the user must take to use the Infor ERP LN 6.1 Data Converter tool. This document is intended for users who want to migrate the current data of the SSA ERP LN 6.1 earlier Service Pack-applied version to the Infor ERP LN 6.1 later Service Pack-applied version. You can use this tool as the Copy Company tool. To better understand the tool, and to determine the steps that you must take, read this document thoroughly before you start the actual tool. In addition, the contents of this document are easier to understand if you have a basic understanding of the Baan application. This User s Guide is divided into the following chapters: Chapter 1, Introduction, provides a brief overview of the Data Converter tool and the steps required to perform the data conversion. Chapter 2, Conversion parameters, provides information and instructions to run the Conversion Parameter sessions. Chapter 3, Preconversion activities, provides information and instructions to carry out the preconversion activities. Chapter 4, Conversion run, provides information and instructions on how to run the dump and load conversion sessions. Chapter 5, Utilities, provides information and instructions on how to run the utilities provided as a part of the tool. Chapter 6, Reports, provides information on which reports you can use for particular reasons, and describes the output expected from each report.

8 vi Table of Contents Appendix A, Troubleshooting, provides a list of warnings and error messages that you can encounter during the conversion, and describes the solutions to resolve these problems. Appendix B, Workstation installation of ERP on the target environment, provides instructions on to install the Baan client on the target environment. Appendix C, Customization of Data Converter tool, provides guidelines to write functions for fields and tables, along with some sample code. Appendix D, Installation of client for cross-platform Conversion, provides instructions to install the client on a Windows NT/2000 target platform, if the conversion is cross-platform. Appendix E, BW Configuration for various databases, provides Infor Windows (BW) configuration settings to be set for several types of databases used on the Infor ERP LN 6.1 target environment side. Send us your comments We continually review and improve our documentation. Any remarks/requests for information concerning this document or topic are appreciated. Please e- mail your comments to documentation@infor.com. In your , refer to the document code and title. More specific information will enable us to process feedback efficiently.

9 Chapter 1 Introduction 1 The product has substantially changed between the various releases. The changes were required to enable users to handle their business processes better and more efficiently. All customers who want to use the advance release of Infor must have a tool that helps migrate the data environment. The fact that the amount of change is huge and that major functionality was introduced in each new version of Infor makes the process of moving this data difficult and tedious. One of the reasons behind the development of the Data Converter tool is to support the user in data conversion for migration projects. The purpose of this document is to assist the user of the Data Converter tool. This document also helps you clearly understand the steps required to use the Data Converter tool and illustrates the actions that you must perform. The migration tool that will be described in this document can be used to carry out data migration from the Infor ERP LN 6.1 or earlier Service Packapplied version to the Infor ERP LN 6.1 or later Service Pack-applied version. You can also use this tool as Copy Company tool. This tool replaces the various steps of the traditional migration process, such as bdbpre, bdbreconfig, bdbpost, and correction of data.

10 1-2 Introduction Note: For the sake of convenience, this document refers to the Infor ERP LN 6.1 release as ERP. Target group This document is intended for users who want to migrate their existing ERP environment with an earlier Service Pack-applied data set to the ERP environment with a later Service Pack-applied data set or Infor users who want to copy the data of one company into another company with the same data model. Scope This document highlights the data conversion from the ERP or earlier Service Pack-applied version to the ERP or later Service Pack-applied version. The tool supports the following databases and operating systems: Database UNIX Windows 2000 Oracle 7.3** X X Oracle 8.1** X X Informix 7.3** X X Informix 9.2** X X DB2** X X SQL-Server 7** X X Database independent** X X **: Level II. X: Supported.

11 Introduction 1-3 User profile For a flawless data analysis, extensive knowledge of ERP is required. This knowledge must span across both the technical and functional areas of the application. You must also have basic knowledge of the UNIX or Windows NT operating systems. Requirements Hardware requirements Hardware requirements usually specify the amount of free disk space available for the data dumps. During the migration process, temporary files are used to store the converted data for each individual table. Sizing approximation The sizing norm is usually as follows: If the size of the ERP data set is x GB, the size of the data files is 1.3 times x GB, and the target environment data set size is 1.5 times x GB. Software requirements The software requirements are the following: Operating system with required network software. ERP and target environment applications completely installed and configured. RDBMS software environment for ERP and for target environment. Configured database source and at target side with the parameters set accordingly. The Load utility of the underlying database.

12 1-4 Introduction Other requirements The user login must have Infor superuser privileges for the ERP environment, read-write permissions for the directories, and must be able to create files in the working directory. Known limitations of the tool You can use this tool to perform simultaneous data dumping from the same company and to load the data into various companies as a copy company tool. However, you cannot do this if the tool is used as Data Converter tool for the same company number. Overview of the data converter tool The tool consists of a generic part and a specific part. The generic part of the tool compares the data dictionaries of the source and the target versions and lists out the differences. During migration, the tool automatically handles the general data dictionary changes, such as case conversion and alignment changes. If some specific functions are to be run for some fields or tables, the functions must be attached to the table or field so that the functions are applied onto the data during migration. When the conversion rules are applied to the data, the tool creates ASCII data dumps, one for each target table. The data is then loaded into the target tables using database specific loaders, such as SQL*Loader if the destination database is Oracle, High Performance Loader (HPL) if the destination database is Informix, and so on. A database-independent loader is also provided so that you can load the data using Infor insert statements irrespective of the target database. This tool can perform the data dumping in parallel with multiple bshells. Similarly, you can also perform data loading using multiple bshells. The Infor source and target application environment can be present on the same machine or two separate machines.

13 Introduction 1-5 Table specific logic Table specific logic Data Converter Data Converter RDBMS ibaan ERP DD RDBMS ibaan ERP DB Driver Direct load Direct DB Driver load Direct load ASCII files Database Database ibaan ERP source environment ibaan ERP target environment Figure 1-1 Diagram of the migration from the Infor ERP source environment to the Infor ERP target environment Overview of the copy company tool Architecture of the copy company tool is essentially the same as the architecture of data converter tool, except the data dictionary comparison process and applying the data conversion rules process. The data dictionary comparison process and applying the data conversion rules process is not required, because the data model of the target company is same as the source company.

14 1-6 Introduction Data conversion steps Scenario 1: Source and target environment located on the same physical machine as two different environments Or: Source and target environment located on the same physical machine as one single environment with different package combinations for source and target: Figure 1-2 Flowchart of steps to perform migration in case of Scenario 1 1 Run the Conversion Parameters (bctls0100m000) session in the target environment.

15 Introduction Run the Conversion Parameters (bctls0101m000) session in the source environment. 3 Run the following preconversion sessions on the target environment in the following order: a b c d Run the Maintain Default Loading Method (bctls9588m000) session and, on the Specific menu, click Generate Default Loading Method to generate the default loading method for all the companies you want to convert. Choose Export Table Information from the Specific menu in the Maintain Default Loading Method (bctls9588m000) session to start the Import List of Tables to Convert (bctls9188m000) session in the source environment. Choose Continue from the Specific menu. Run the Checking for Onpload Database Population (bctls0207m000) session only if you use an Informix database on the target side. 4 Run the following preconversion sessions in the source environment in the following order: a b c d Copy Data Dictionary (bctls2100s000) Generate Domain Differences between Source and Target (bctls1110m000) Generate Table/Field Difference between Source and Target (bctls1112m000) Maintain Table Linked Functions (bctld1115m000) 5 Run the Dump and Load (bctls0200m000) session in the target environment, which internally invokes the Dump Only (bctls1213m000) session of the source environment.

16 1-8 Introduction Scenario 2: Source and target environment located on two different machines with Client-Server connectivity between them: Figure 1-3 Flowchart of steps to perform migration in case of Scenario 2 1 Install the Infor source environment client software for UNIX or Windows NT/2000 in the target environment. For more information on the installation and configuration procedure, refer to Appendices B, D, and E in this document. 2 Run the Conversion Parameters (bctls0100m000) session in the target environment. 3 Run the Conversion Parameters (bctls0101m000) session in the source environment. 4 Run the following preconversion sessions in the target environment in the following order:

17 Introduction 1-9 a b c Run the Maintain Default Loading Method (bctls9588m000) session and, on the Specific menu, click Generate Default Loading Method to generate the default loading method for all the companies you want to convert. Choose Export Table Information from the Specific menu in the Maintain Default Loading Method (bctls9588m000) session to start the Import List of Tables to Convert (bctls9188m000) session in the source environment. Run the Checking for Onpload Database Population (bctls0207m000) session only if you use an Informix database on the target side. 5 Run the following preconversion sessions in the source environment in the following order: a b c d Run the Copy Data Dictionary (bctls2100s000) session. In the case of source and target environment running on a Windows NT platform, copy the Data Dictionary (DD) manually from the target to source environment before you run this session. Run the Generate Domain Differences between Source and Target (bctls1110m000) session. Run the Generate Table/Field Difference between Source and Target (bctls1112m000) session. Run the Maintain Table Linked Functions (bctld1115m000) session. 6 Run the Dump and Load (bctls0200m000) session in the target environment, which internally invokes the Dump Only (bctls1213m000) session of the source environment.

18 1-10 Introduction Scenario 3: Source and target environment located on two different machines without Client-Server connectivity between them: Figure 1-4 Flowchart of steps to perform migration in case of Scenario 3 1 Run the Conversion Parameters (bctls0100m000) session in the target environment. 2 Run the Conversion Parameters (bctls0101m000) session in the source environment. 3 Run the following preconversion sessions in the target environment in the following order: a Run the Maintain Default Loading Method (bctls9588m000) session and, on the Specific menu, click Generate Default Loading Method

19 Introduction 1-11 b c d to generate the default loading method for all the companies you want to convert. Choose Export Table Information on the Specific menu in the Maintain Default Loading Method (bctls9588m000) session to start the Import List of Tables to Convert (bctls9188m000) session in the source environment. Choose Continue from the Specific menu. Run the Checking for Onpload Database Population (bctls0207m000) session only if you use an Informix database on the target side. 4 Copy the Tables.info file manually from $BSE/tmp/migration/<target company number>/<user ID> directory on the target server to $BSE/tmp/migration/<source company number>/<user ID> directory on the source server. 5 Run the following preconversion sessions in the source environment in the following order: a b c d e Run the Generate List of Target Tables Being Converted (bctls9188m000) session. Run the Copy Data Dictionary (bctls2100s000) session. In the case of source and target environment running on Windows NT platform, copy Data Dictionary (DD) manually from the target environment to the source environment before you run this session. Run the Generate Domain Differences between Source and Target (bctls1110m000) session. Run the Generate Table/Field Difference between Source and Target (bctls1112m000) session. Run the Maintain Table Linked Functions (bctld1115m000) session. 6 Run the Conversion (bctls1213m000) session in the source environment. 7 Copy all the dump data files manually from source to target environment. 8 Run the Load Data (bctls1214m000) session in the target environment.

20 1-12 Introduction Copy Company Data steps Scenario 1: Source and target environment located on the same physical machine as two different environments Or: Source and target environment located on the same physical machine as one single environment with different package combinations for source and target Or: Source and target environment located on the same physical machine as one single environment within the same package combination with the target company data model same as the source company Figure 1-5 Flowchart of steps to perform copy company data in case of Scenario 1 1 Run the Conversion Parameters (bctls0100m000) session in the target environment.

21 Introduction Run the Conversion Parameters (bctls0101m000) session in the source environment with the Is Source and Target Data Model Same field value set to Yes. 3 Run the following preconversion sessions on the target environment in the following order: a b c d Run the Maintain Default Loading Method (bctls9588m000) session and, on the Specific menu, click Generate Default Loading Method to generate the default loading method for all the companies you want to convert. Choose Export Table Information from the Specific menu in the Maintain Default Loading Method (bctls9588m000) session to start the Import List of Tables to Convert (bctls9188m000) session in the source environment. Choose Continue from the Specific menu. Run the Checking for Onpload Database Population (bctls0207m000) session only if you use an Informix database on the target side. 4 Run the Dump and Load (bctls0200m000) session in the target environment, which internally invokes the Dump Only (bctls1213m000) session of the source environment.

22 1-14 Introduction Scenario 2: Source and target environment located on two different machines with Client-Server connectivity between them: Figure 1-6 Flowchart of steps to perform copy company data in case of Scenario 2 5 Install the source environment client software for UNIX or Windows NT/2000 in the target environment. For more information on the installation and configuration procedure, refer to Appendix B, D, and E in this document. a b c d Run the Conversion Parameters (bctls0100m000) session in the target environment. Run the Conversion Parameters (bctls0101m000) session in the source environment with the Is Source and Target Data Model Same field value set to Yes. Run the following preconversion sessions on the target environment in the following order: Run the Maintain Default Loading Method (bctls9588m000) session and, on the Specific menu, click Generate Default Loading Method

23 Introduction 1-15 e f g to generate the default loading method for all the companies you want to convert. Choose Export Table Information from the Specific menu in the Maintain Default Loading Method (bctls9588m000) session to start the Import List of Tables to Convert (bctls9188m000) session in the source environment. Choose Continue from the Specific menu. Run the Checking for Onpload Database Population (bctls0207m000) session only if you use an Informix database on the target side. 6 Run the Dump and Load (bctls0200m000) session in the target environment, which internally invokes the Dump Only (bctls1213m000) session of the source environment.

24 1-16 Introduction Scenario 3: Source and target environment located on two different machines without Client-Server connectivity between them: Figure 1-7 Flowchart of steps to perform copy company data in case of Scenario 3 1 Run the Conversion Parameters (bctls0100m000) session in the target environment. 2 Run the Conversion Parameters (bctls0101m000) session in the source environment with the Is Source and Target Data Model Same field value set to Yes. 3 Run the following preconversion sessions in the target environment in the following order:

25 Introduction 1-17 a b c Run the Maintain Default Loading Method (bctls9588m000) session and, on the Specific menu, click Generate Default Loading Method to generate the default loading method for all the companies you want to convert. Choose Export Table Information from the Specific menu in the Maintain Default Loading Method (bctls9588m000) session, select option to export data to the Tables.info file. Run the Checking for Onpload Database Population (bctls0207m000) session only if you use an Informix database on the target side. 4 Copy the Tables.info file manually from the $BSE/tmp/migration/<target company number>/<user id> directory on the target server to the $BSE/tmp/migration/<source company number>/<user id> directory on the source server. 5 Run the Import List of Target Tables to Convert (bctls9188m000) preconversion session in the source environment. 6 Run the Dump Only (bctls1213m000) session in the source environment. 7 Copy all the dump data files manually from the source environment to the target environment. 8 Run the Load Only (bctls1214m000) session in the target environment.

26

27 Chapter 2 Conversion parameters 2 Target environment Conversion Parameters (bctls0100m000) Figure 2-1 Conversion Parameters (bctls0100m000), Dump Details tab

28 2-2 Conversion parameters Note You must fill in the details on the Dump Details tab only in the case of Scenario 1 and Scenario 2. In the case of Scenario 3, only the value for the Is Source and Target on Same Server field must be selected. A separate set of conversion parameters are maintained for every Infor application user. The Dumping Details tab contains the following fields: Is Source and Target on same server: Select Yes if the source environment and the target environment is present on the same server. Select No if the source environment and the target environment are located on separate servers. Source Server Name: Specify the source server name if the source environment and the target environment are located on separate servers. Source BSE: If the source environment and the target environment are located on separate systems (Scenario 2), specify the client BSE path as the source BSE path. If the source environment and the target environment are located on the same system (Scenario 1), specify the BSE path of the source environment. Source BSE_TMP: If the source environment and the target environment are located on separate systems, specify the Client BSE_TMP path as the Source BSE_TMP Path. If the source environment and the target environment are located on the same system, specify the BSE_TMP path of the source environment. Bshell Name: Specify the bshell name to start the conversion session of the source environment. Current Dumping User: The name of the currently logged in user. Current User Password: Specify the user password of the currently logged in user. BW Path on the Client: Specify the BW path on the client system to invoke the bshells.

29 Conversion parameters 2-3 BW Protocol: BW Protocol that will be used to connect to the Infor server. Is Source and Target on Same Infor Environment: Select Yes if your source and target is present in the same Infor environment with a different package combination. Source Package Combination: Specify the source environment package combination. Source Company: Specify the source company number. Figure 2-2 Conversion Parameters (bctls0100m000), Loading Details tab The Loading Details tab contains the following fields: Number of Loaders: Specify the number of parallel loaders to load the data. The maximum number of loaders that you can specify in case of DB2 database is one. Bshell Name: Specify the bshell name of the target environment to invoke parallel bshells. Current User Password: Specify the current user password to invoke parallel bshells. BW Path on the Client: Specify the directory where you installed Infor Windows on the local system to invoke the parallel bshells.

30 2-4 Conversion parameters Database Name: Select the database name present on the target side. Select Oracle X - C/S Different OS option if the target database is Oracle installed on the Windows NT/2000 based machine and target Infor application server is installed on the UNIX based machine. In the case of target-company data stored under multiple databases and, if one of the databases is Oracle, select the Oracle option to generate control files required to load the data. Note In the case of Oracle 7, string length is limited to 255 characters. Database Driver: Select the driver: Level 1 driver or Level 2 driver. Figure 2-3 Conversion Parameters (bctls0100m000), Oracle tab The Oracle tab contains the following fields: Username for SQL Loader: Specify the oracle user name to load the data. This field is available only if you select ORACLE as the database name in the Database Name field. Password for SQL Loader: Provide the corresponding password to load the data into the database. This field is available only if you select ORACLE as the database name in the Database Name field.

31 Conversion parameters 2-5 TWO_TASK: Enter the value for this parameter in case target Oracle database is installed on the Windows-based machine and target Infor application server is installed on the UNIX-based machine. You can find the value for this parameter in the $BSE\bin\Tabledef6.2 file. You can also find the value for this parameter in the Maintain DB Definitions (ttaad4110m000) session. Figure 2-4 Conversion Parameters (bctls0100m000), Informix tab The Informix tab contains the following fields: Informix Directory: Specify the directory where Informix is installed. Database Name: Specify the target database name created on the Informix server. Server Name: Specify the server name where Informix is installed.

32 2-6 Conversion parameters Figure 2-5 Conversion Parameters (bctls0100m000), DB2 tab The DB2 tab contains the following fields: Database Name: Specify target database name created on the DB2 server. Figure 2-6 Conversion Parameters (bctls0100m000), SQL Server tab The SQL Server tab contains the following fields: Database Name: Specify the target database name created on the MS SQL Server.

33 Conversion parameters 2-7 Username for Loader: Specify the database user name to load the data Password for Loader: Specify the corresponding password to load the data. Source environment Conversion Parameters (bctls0101m000) Figure 2-7 Conversion Parameters (bctls0101m000) Path for Data Dumps: Specify the directory where you want to create the data files. Number of Bshells: Specify the number of parallel bshells to be used to create the data dumps. Bshell Name: Specify the bshell name to invoke parallel processes. Current Dumping User: The name of the currently logged in user. Current User Password: Specify the current user password to invoke the parallel bshells.

34 2-8 Conversion parameters BW Path on the Client: Specify the path where you have installed Windows on the local client system. For example, if Windows is installed on C:\Program Files\Baan\Baan Windows, you must specify the path as C:\progra~1\baan\baanwi~1. Target Database Name: Specify the database name of the target environment, which will be used to create the control files. Control files will be used to load the data into the target database. Is Source and Target Data Model Same: Select the Yes option if the source and target data model is same and you want to use this tool for a Copy Company Functionality. Dump All Tables of Selected Range: Click Yes to create data files for the range of tables specified in the Table Name field, otherwise, click No. If you select No, the tool only creates data files for the tables that are not the same in the target environment. Is the Target Company Same As Source Company: Click Yes if both the target and source company number are the same, otherwise, click No. Should Data Be Corrected for Company Number: In a multisite scenario, company numbers are also part of the data. Click Yes to change the company number in the data while creating the data files, otherwise, click No. Company Number Mapping: Specify the company number mapping if the target and source company number are not the same. To specify multiple company number mappings, you can separate the mappings with commas, for example: , , Target Database: Select the database application name present on the target side. Select Oracle X - C/S different OS option if target database is Oracle installed on the Windows NT/2000 based machine and target application server is installed on the UNIX based machine. Note: In the case of Oracle 7, string length is limited to 255 characters. BW Protocol: The BW Protocol that will be used to connect to the server.

35 Chapter 3 Preconversion activities 3 Target environment Maintain Default Loading Method (bctls9588m000) Figure 3-1 Maintain Default Loading Method (bctls9588m000)

36 3-2 Preconversion activities In this session, you can maintain the parameters for each migrated table whose list was generated by the system in the Generate Default Loading Method (bctls9288m000) session. The Maintain Default Loading Method (bctls9588m000) session contains the following fields: Table Name: The name of the table. Load Option: Can be either Truncate or Append: In Oracle, Truncate means that the table is truncated before the load, and Append means that data is appended to the existing data in the table. The Truncate option is not available in the Informix-specific loader. If the load option is Truncate, the table rows are manually deleted with SQL, and the Append option is the default option. For more information, refer to Conversion (bctls0200m000), in Chapter 6, Conversion run. Bypass: If set to Yes, this table is not considered for migration in this company. Duration: By default, all the tables are marked Shorter. Select Longer if the table is extremely large in ERP. While dumping, all the tables marked as Longer are dumped first, followed by tables marked as Shorter. This helps in load balancing, and ensures that dumping the large tables does not start last and take a long time when all the other bshells are already finished dumping. A list of tables that usually contain a large amount of data are marked as Longer. You can choose a list of tables on your own, based on your specifics. Load balancing is a technique that you can use to improve the performance of the tool to maximize the throughput. Generate a mix of Longer and Shorter tables in a ratio of 60:40 for the dump b-shells. Mode of Loading: Used during the generation of the control file: The Oracle SQL* Loader has two load modes, Direct and Conventional: If you set the load mode to Automatic, and the size of the data file is greater than 10,000 bytes, the load mode of SQL* Loader is set to Direct. Otherwise, the load mode is Conventional.

37 Preconversion activities 3-3 If you set the load mode to Conventional, the load mode of SQL* Loader is set to Conventional Informix HPL has two load modes: Express and Deluxe: If you set the load mode in Informix to Automatic, and the size of the data file is greater than 10,000 bytes, the load mode of Informix HPL is set to Express. Otherwise, the load mode is Deluxe. If you set the load mode to Conventional, the load mode of the Informix HPL is set to Deluxe. Figure 3-2 Special menu options for Maintain Default Loading Method (bctls9588m000) session Choose Generate Default Loading Method from the Specific menu to generate the default loading method for all the companies you want to convert using Generate Default Loading Method (bctls9288m000) session:

38 3-4 Preconversion activities Figure 3-3 Generate Default Loading Method (bctls9288m000) This session accepts the range of companies and generates default-loading method for all the tables of companies that are linked to the current user package combination in the selected range. Bypass tables with data: If the check box is selected, while generating the target table information, for all the target tables already having data, the Bypass option in Maintain Default Loading Method (bctls9588m000) session is filled with YES else with NO. The Bypass Option for Error Tables option is useful if you want to load the data only for the tables for which data could not be loaded successfully when the conversion run was carried out last time. Before you choose Bypass Option for Error Tables from the Specific menu, run the Generate Error Report (bctls5200m000) session from the Reports section to set the Bypass option to Yes for all the tables other than tables in which data could not be loaded successfully.

39 Preconversion activities 3-5 Choose Set Bypass Yes/No To Range of Tables from the Specific menu to set the Bypass option to Yes or No for a specific range of tables specified as shown in the following figure: Figure 3-4 Set Bypass Yes/No To Range of Tables (bctls9285m000) session Enter the range of Company Number, Package, Module, and Table and click Bypass Yes or Bypass No, depending upon whether you want to set the Bypass field value to Yes or No for the specified range of tables. After you maintain the details, to export the data to the source environment, click Export Table Information on the Specific menu to start the Import List of Tables to Convert (bctls9188m000) session of the source environment. To import the data into the source database in Scenarios 1 and 2, click Continue on the Specific menu, as shown in the following figure:

40 3-6 Preconversion activities Figure 3-5 Import List of Tables to Convert (bctls9188m000) session Checking for Onpload Database Population (bctls0207m000) Figure 3-6 Generate Onpload (bctls0207m000) You must run this session only if you use an Informix database on the target side. The onpload database contains information that the onpload utility requires to perform data loads and unloads. The onpload database can reside on any database server on your network. In addition, any Onpload utility can use the onpload database, as long as the Onpload utility can access the database server that contains the onpload database. In contrast, the Onpload utility must run on the same computer as the database server that contains the target database.

41 Preconversion activities 3-7 To fill up the onpload database, run the Generate Onpload Database (bctls0207m000) session, as shown in the following figure. To carry out multiple-company conversion, select the Multiple Company Conversion Yes/No? check box before you click Continue. To perform the conversion process for the first time, you must create an onpload database and run an SQL script, which comes with the onpload utility, to create objects in that database before you run this session. For more information, refer to the Informix Technical Manuals. If you are not carrying out the conversion process for the first time, you must remove all the data from the following tables before you run this session: formatitem formats maps mapitem session mapoption

42 3-8 Preconversion activities Source environment Import List of Tables to Convert (bctls9188m000) This session generates list tables to be converted. This session also imports load data from the target environment. Figure 3-7 Import List of Tables to Convert (bctls9188m000) Note The user must run this session to connect from the target environment for Scenario 1: Source and target environment located on the same physical machine as two different environments, and Scenario 2: Source and target environment located on two different machines with Client-Server connectivity between them. You must run this session after you copy the Tables.info file manually in the case of Scenarios 3 and 4. For more information, refer to Steps to perform migration, in Chapter 1, Introduction.

43 Preconversion activities 3-9 Copy Data Dictionary (bctls2100s000) To perform the data migration, you must compare the data dictionaries of the source and the target version. Therefore, the target data dictionary files must be available for the tool to compare to the source data dictionary files. If the source and target data dictionary files are present on two separate servers, the process of comparing domains and tables takes a long time. For this reason, to reduce the time required, the Copy Data Dictionary (bctls2100s000) session, as shown in the following figure, copies the target data dictionary files into the source data dictionary directories with an extension.nw. If a directory for a target module is not present in the source data dictionary directory structure, the directory is created and the data dictionary files are copied. The tool assumes that the target data dictionary files are present in the same directory structure as the source data dictionary files, but with an extension.nw. The user who runs this session requires read and write permissions to access the directories where the source data dictionary files are present. You can obtain this directory name from the Package Combinations (ttaad1120s000) session activated from the Package Combinations (ttaad1520m000) session in the source environment. Note In the case of Scenario 2 or Scenario 4, and if the platform is Windows NT or cross platform (UNIX Windows NT), you must copy the Data Dictionary (DD) files to the source environment server. Next, copy the Dtt.pd directory under $BSE/tools/dd from the target environment server to the source environment server under the Data Dictionary (DD) files directory copied previously. Figure 3-8 Copy Data Dictionary (bctls2100s000)

44 3-10 Preconversion activities The Copy Data Dictionary session contains the following fields: Target DD Directory: This field specifies the directory from which the target data dictionary must be copied to the source environment. This path is the directory path of the remote server in case the target server and source server is not present on the same physical machine, otherwise, this path is the directory path of the local machine where the target data dictionary is present. Target BSE Path: This field specifies the BSE directory of the target environment. The value for this field must not be specified for Scenario 2 and Scenario 4. Source and Target on the Same Machine: If both the source and target application are present on the same physical machine, click YES in this list, otherwise, click NO. Note In the case of Scenario 2 or Scenario 4, and if the platform is Windows NT or cross platform (UNIX Windows NT), you must select YES from the list box because Windows NT does not support Remote Copy Program (RCP) that is used to copy the Data Dictionary (DD) files from the target environment to the source environment. Target Server Name: If the source and target environments are present on separate physical machines, specify the target server name. Login: If the source and target environments are on separate physical machines, specify the user login name to connect to the target server. This login is used to remotely copy the data. After you specify each of these details, click Continue to copy the target data dictionary to source. When the target data dictionary is present on the local machine, the files are simply copied to the source data dictionary directory with an extension.nw. If the target data dictionary is present on a remote machine, then the Remote Copy Program (RCP) utility of UNIX is used to copy the data dictionary to the source server. For RCP to work, the following conditions must be met:

45 Preconversion activities 3-11 In the file.rhosts in the $HOME of the source server, an entry must be present with the remote target server name and the remote login used to access this server. These two values must be separated by a space. In the file.rhosts in $HOME of the target server, similarly, an entry must be present with the source server name and the login that is used on the source server. In the /Etc/hosts file on both the servers, the IP address of each server and the server s name must be specified. When the copying process is complete, the target data dictionary is copied to the source data dictionary path with extension.nw, as shown in the following figure: Figure 3-9 Directory listing after you copy the data dictionary from the target environment Generate Domain Differences between Source and Target (btls1110m000) The Generate Domain Differences between Source and Target (btls1110m000) session generates the differences in the domains between the source and the target based on the data dictionary in terms of new, changed, deleted, and unchanged domains. This data is saved in the

46 3-12 Preconversion activities bctls110 table and is also used by the Generate Table/Fields Differences between Source and Target (bctls1112m000) session. If the domain difference data is already present in the bctls110 table when this session is invoked, the data present in the table bctls110 appears in this session. Click Continue to generate or regenerate the domain differences. You can also run this session while the source application is still in use by other users. In other words, running this session does not form part of the downtime. However, no data-model changes can be made to the source or target data model during and after this session run. The following figure shows the Form 1 tab of the Generate Domain Differences between Source and Target session: Figure 3-10 Generate Domain Differences between Source and Target (bctls1110m000), Form 1 tab The Form 1 tab on this session provides information about the domain. The Type of Domain field indicates whether the domain is a new domain, deleted domain, changed domain, or an unchanged domain. If the domain is a changed domain, the Type of Domain Change field indicates the type of domain changes. The available types of domain changes are the following:

47 Preconversion activities 3-13 Data type change. Legal characters range change. Illegal characters range change. Adjustment change between source and target: Left Right Center Number of digits change for byte, integer, long domain, number of digits before and after decimal, or divide factor changed for float and double domain. Number of enum values, the enum values or the enum constants changed for an enum, and length or conversion change for a string domain: Upper Lower No change The Form 2 and Form 3 tabs in this session provide details of the source and target. Generate Table/Fields Differences between Source and Target (bctls1112m000) The Generate Table/Fields Differences between Source and Target (bctls1112m000) session, as shown in the following figure, reads the source and target data dictionary, compares the two for each table and field, and records the differences between the table definitions into the bctls112 table, and displays the differences in the session. If the table difference data is already present in the bctls112 table when you start this session, the data present in the bctls112 table appears in this session. Click Continue to generate or regenerate the table differences.

48 3-14 Preconversion activities Figure 3-11 Generate Table/Field Differences between Source and Target (bctls1112m000) The Form 2 to Form 6 tabs in this session contain other details of the table fields. The Form 7 tab in this session, as shown in the following figure, provides a field to enter the function name that must be used to migrate the data of the field from source to target. This field is unavailable for index records. You can enter the function name in the Function field in this session. The function must already have been defined in the bctlsuserfunc library. Only one function name can be provided and no function calls within function are permitted. The input to the function will be the source field whose value is passed as a parameter and the function should return the resultant value because this value must be migrated to the target. Therefore, the return type of the function is the data type of the target field. For more details on function declaration, refer to Appendix C, Customization of the Data Converter tool.

49 Preconversion activities 3-15 Figure 3-12 Generate Table/Field Differences Between Source and Target (bctls1112m000), Form 7 tab The function names in this session correspond to the table fields only. If a function must be linked to an entire table, you can do this in the Maintain Table Linked Functions (bctls1115m000) session, which is described later in this chapter. Maintain Table Linked Functions (bctls1115m000) By default, when you start data migration for a company, the data dictionary differences are picked up from the bctls112 table and ASCII data files are generated in the target table definition format, based on the changes recorded in bctls112. However, to perform the dumping for a table using some special logic, you must define the function for dumping in the bctlsd<tablename> library using the example provided in Appendix C, Customization of the Data Converter tool. The name of the function must be defined as dump.<tablename> in the library. The parameters to be passed to the script are the directory path where the data file dump must be placed and the driver, whether L1 driver or not. The script should dump the data into an ASCII file in the target-table format.

50 3-16 Preconversion activities The following figure shows the Maintain Table Linked Functions session: Figure 3-13 Maintain Table Linked Functions (bctls1115m000) Note If a function name is specified for a table in this session, the function alone will be used to dump the data for the table, and no other details from the table bctls112 will be checked.

51 Chapter 4 Conversion run 4 This chapter describes the actual conversion process, which is comprised of the export and import processes. The export and import processes are the major tasks in the conversion run. Target environment You can start the conversion process from the target environment, invoke the source environment from the target environment, and carry out the dumping process. Dump and Load (bctls0200m000) You can start the data migration run from the Conversion (bctls0200m000) session, as shown in the following figure. The data on the form is the same as the data in the Conversion Parameters (bctls0100m000) session. To start the data migration process, click Continue.

52 4-2 Conversion run Figure 4-1 Conversion Parameters (bctls0100m000) Note Only one instance of this session can be running on the server at a time. This session invokes the conversion session of the source environment, as shown in the following figure: Figure 4-2 Conversion (bctls0200m000) Company Number: Enter the range of companies that must be migrated. Table Name: Enter the range of tables that must be migrated. Click Continue to create the data files. Figure 4-3 Data Dumping Complete message

53 Conversion run 4-3 During the dumping process, the data files (.DAT) are generated for the corresponding tables in the database. Data files in ASCII format are created in the path specified in the Path for Data Dumps field in the Conversion Parameters (bctls0100m000) session, for example: <Dump Directory> / <company number> / <module name1> / <tablename.dat>... <Dump Directory> / <company number> / <module name2> / <tablename.dat>... <Dump Directory> / <company number> / <module name3> / <tablename.dat>... The data file of the tcccp000 table is available in the following location: <Dump Directory> / <company number for which conversion is being run> / tcccp / tcccp000.dat The control files (.CTL) for the loading process are created in the same directory as the data files directory. The control files provides the input to the native database loader about the format of the.dat file from which the data is picked up and loaded into the specific target environment tables. A typical control file specifies the table name, field separator, and the sequence of fields. The control files are read by the database loader just before loading the data. The control files are applicable for Oracle databases only and are not applicable for DB2, Informix, or MSSQL Server databases. For MSSQL Server and DB2 databases, the format of the.dat is specified in the command generated for the loading utility. For Informix databases, the format of the.dat files is specified in the ONPLOAD database. The following message appears on the target environment when data loading is complete: Figure 4-4 Data Loading Complete message

54 4-4 Conversion run Load Only (bctls1214m000) The Load Data (bctls1214m000) session, as shown in the following figure, is used for loading the data at the target environment from the ASCII files created by the Create Data Dumps (bctls1113m000) session. Note Only one instance of this session can be running on the server at a time. Figure 4-5 Load Data (bctls1214m000) This session includes the following fields: Company Number: You have the option to load a single company or more than one company s data at a time. Specify the company range for which you want to load the data. Table Name: Select the range of tables for which you want to load the data files. Path of Data Dumps: Specify the directory path on which the data files exist. After you fill in this information in the session, click Continue to start the data-loading process.

55 Conversion run 4-5 After the load process is complete, the following message appears: Figure 4-6 Data Loading Complete message The control files (.CTL) are required to provide the input to the native database loader in case of an Oracle database about the format of the.dat file from which the data must be picked up and loaded into the specific target environment tables. The log files (.LOG) are created by the native database loader in case of an Oracle database, and indicate the result of data loading process from the data files (.DAT). The log files (.LOG) are created in the same directory where the data files are located. After you run the Load Data (bctls1214m000) session, check the log files (.LOG) to analyze the success of data loading process. The Oracle and MSSQL server native data loader creates the bad files (.BAD) in the same directory where the data files are located to specify the records that were rejected due to data errors. These files are created with the name <target environment tablename>.bad. After you run the Load Data (bctls1214m000) session, check whether any bad files (.BAD) are in the same folder in which data files (.DAT) are located. If bad files (.BAD) are found, this indicates that some part of the data loading process failed. For the list of warnings and error messages that you can encounter when you run this session, and the solutions to resolve these problems, refer to Appendix A, Troubleshooting.

56 4-6 Conversion run Source environment Data dumping process Dump Only (bctls1213m000) The Conversion (bctls1113m000) session, as shown in the following figure, is used for dumping the data from the source environment to ASCII files: Figure 4-7 Conversion (bctls1213m000) This session contains the following fields: Company Number: You have the option to migrate a single company or multiple companies at one time. In this field, specify the company range that you want to migrate. Table Name: Select the range of tables for which you want to create data files. After you fill in this information in the session, click Continue to start the data dumping process. When the dumping process is complete, a message appears on the screen to alert you that the process is finished. During the dumping process, the data files (.DAT) are generated for the corresponding tables in the database. Data files in ASCII format are created in the path specified in the Path for Data Dumps field in the Conversion Parameters (bctls0101m000) session, for example: <Dump Directory> / <company number> / <module name1> / <tablename.dat>...

57 Conversion run 4-7 <Dump Directory> / <company number> / <module name2> / <tablename.dat>... <Dump Directory> / <company number> / <module name3> / <tablename.dat>... The data file of the tcccp000 table is available in the following location: <Dump Directory> / <company number for which conversion is being run> / tcccp / tcccp000.dat The control files (.CTL) for the loading process are created in the same directory as the data files directory. The control files provides the input to the native database loader, about the format of the.dat file from which the data is picked up and loaded into the specific target environment tables. A typical control file specifies the table name, field separator, and the sequence of fields. The database loader reads the control files just before loading the data. The control files are applicable for Oracle databases only and are not applicable for DB2, Informix, or MSSQL Server databases. For MSSQL Server and DB2 databases, the format of the.dat is specified in the command generated for the loading utility. For Informix databases, the format of the.dat files is specified in the ONPLOAD database. For the list of warnings and error messages that you can encounter during the execution of this session, and the solutions to resolve these errors, refer to Appendix A, Troubleshooting.

58

59 Chapter 5 Utilities 5 Analyze Utility Before Conversion (bctls5405s000) Before you perform the conversion, you must analyze the hardware and software configurations to run the conversion tool. This Analyze utility helps in the conversion process. The Analyze utility provides the following information: User environment variables on target system. Target database name, configuration parameters, tablespace, and size of the database.

60 5-2 Utilities Figure 5-1 Analyze Utility Before Conversion (bctls5405s000) User details: Click Yes to display the user environment details, such as the user name, user type, default company, language, date format, and package combination. Verification of Tables: Click Yes to verify the tables in the target company. Report provides you the names of the tables that are not created properly and the number of records that each table currently contains. Database Environment Details: Click Yes to display the database name, configuration parameters, tablespaces, and the size of the database.

61 Utilities 5-3 This session prints the details that the user selected. Figure 5-2 Analyze Utility Before Conversion (bctls5405s000), report output Details of Users Connected (bctls5406s000) This session generates a report of number of users connected to a particular package combination of target environment at a given time. This session is developed with operating system commands of UNIX and NT, which are programmed in Infor. Note The Details of Users Connected utility works for all the databases in the UNIX environment, however, in case of Windows NT, only Oracle and SQL Server databases are supported.

62 5-4 Utilities To view the report of users connected, on the Menu Browser, click Baan Conversion Utilities to start the Details of Users Connected (bctls5406s000) session, as shown in the following figure: Figure 5-3 Details of Users Connected (bctls5406s000) Click Continue to continue the process. Click Close to stop the process. In ERP on a Windows NT environment, if you click Continue, the Get Database Path, Username and Password (bctls5106m000) session appears, as shown in the following figure. To fill the Database Path automatically, press the TAB key in the Database Path field without entering any value. Enter the database user name and password in the User Name and Password fields respectively before you click Continue. If the database is Oracle, the database user must be granted the role SELECT_CATALOG_ROLE before running this session. Figure 5-4 Get Database Path, Username and Password (bctls5106m000)

63 Utilities 5-5 The following figure shows the report output of the Details of Users Connected session: Figure 5-5 Details of Users Connected (bctls5406s000), report output The list of users connected to a particular package combination appears in the form of a report. The report displays the date, system login user names, possible Infor users connected, number of users connected for each login, and the company number.

64

65 Chapter 6 Reports 6 Target environment The following reports are available on the target side of the ERP Data Converter tool. Generate Error Report (bctls5200m000) The utility accepts the path of log files and the range of companies. For each company, the utility finds the database from the Tools tables. Depending on the database, the utility analyzes the log files and fills the error information in the bccnv500 table. Figure 6-1 Generate Error Report (bctls5200m000) Company From: First converted company. Company To: Last converted company.

66 6-2 Reports Path: Path of the directory where conversion data files and log files are stored. Print Error Report (bctls5400s000) This session, as shown in the following figure, prints all the errors that are generated in the Generate Error Report session: Figure 6-2 Print Error Report (bctls5400s000) This session accepts the company range and table range. Click Continue to display the error report, as shown in the following figure: Figure 6-3 Print Error Report (bctls5400s000), report output

67 Appendix A Troubleshooting A This appendix contains a list of warnings and error messages that you can encounter during the conversion and provides solutions to avoid these errors. Source environment Create Data Dumps (bctls1113m000) error messages No valid company number selected If you enter a non-existing company number in the Company Number field in the Create Data Dumps (bctls1113m000) session, this error message appears, as shown in the following figure: Figure A-1 No Valid Company Number Selected error message To avoid this error, you must enter the existing company number for which you want to dump the data.

68 A-2 Troubleshooting Target environment Load Data (bctls1214m000) error messages ORACLE_HOME and ORACLE_SID not set If you try to load the data on the target side with the help of the Load Data (bctls1214m000) session without setting the correct values for the ORACLE_HOME and ORACLE_SID parameters and if your database is Oracle, then this error message appears, as shown in the following figure: Figure A-2 Oracle Home, SID Not Set error message In the BW Configuration Properties dialog box, as shown in the following figure, on the Bshell Environment tab, you must set the ORACLE_HOME and ORACLE_SID parameters in the Command field. After you set these parameters, you must log on to your target environment again before you restart the Load Data (bctls1214m000) session:

69 Troubleshooting A-3 Figure A-3 BW Configuration Properties dialog box, Bshell Environment tab No data within selection If you enter an incorrect path in the Path of Data Dumps field or incorrect company number in the Company Number field in the Load Data (bctls1214m000) session, an error message appears, as shown in the following figure: Figure A-4 No Data Within Selection error message

70 A-4 Troubleshooting To avoid this error message, you must enter the correct path for data dumps and the correct company number for the company for which you have dumped the data using the Create Data Dumps (bctls1113m000) session, for example: If you have dumped the data for company number 200 in the /usr1/home/dump directory using the Create Data Dumps (bctls1113m000) session, you must specify the same path and not /usr1/home/dump/200 as the path for data dumps in the Load Data (bctls1214m000) session. To recover after a data loading failure in case of DB2 database If you stop the process, or if the data loading process stops responding while you load the data into the DB2 database, the DB2 loader places the table in load-pending state. As a result, you subsequently cannot use the tablespace. To unlock the DB2 tablespace, take the following steps: 1 Identify what table was loading at the time of crash. You can find this information from your home directory. Use the following command at the UNIX $ prompt: ll loaddb2* The result will resemble the following: -rwxrwxrwx 1 baan5db2 bsp 335 Dec 12 11:19 loaddb2tcccp020 In this file name, the last eight characters are the table name. In this example, the table name is tcccp Use the following command to lock the tablespace: db2 quiesce tablespaces for table ttcccp exclusive In the table name ttcccp020913, the first letter t is mandatory, tcccp020 is the table name, and 913 is the company number. 3 Place the following commands into a file named Unlock in the home directory: connect to baan5db2; load from /home/baan5db2/913/tcccp/tcccp020.dat of del modified by coldel0x01 chardel0xff delprioritychar

71 Troubleshooting A-5 DATEFORMAT="DD/MM/YYYY" TIMEFORMAT="HH:MM:SS" TIMESTAMPFORMAT="dd/mm/yyyy hh:mm:ss" usedefaults keepblanks WARNINGCOUNT 51 messages /home/baan5db2/913/tcccp/tcccp020.log terminate into BAAN5DB2.ttcccp020913; In these lines, baan5db2 is the DB2 database name and /home/baan5db2/913/tcccp/tcccp020.dat is the path of the data file. 4 Run the following mode to normal: db2 -tvf unlock command at the UNIX $ prompt to change the tablespace

72

73 Appendix B Workstation installation of Infor ERP on target environment B Infor ERP will be completely installed on the application system. A workstation installation of ERP must be performed on the target environment server. The master tape or a manual installation can carry out the workstation installation. Manual procedure Step 1: Create a unique environment for the workstation environment Create an own BSE directory for the ERP environment with the following directories: Directory Permission Purpose.../bse rwxr-xr-x Environment directory. All software components will be installed in this directory..../bse/bin rwxr-xr-x Directory for binaries..../bse/tmp Rwxrwxrwx Directory for temporary files.../bse/etc rwxr-xr-x Directory for environment scripts..../bse/log Rwxrwxrwx Directory for log files.

74 B-2 Workstation installation of Infor ERP on target environment Directory.../bse/lib Permission Purpose rwxr-xr-x.../bse/lib/terminf rwxr-xr-x Terminal information files..../bse/lib/user Rwxrwxrwx Directory for (remote) user files. Install the complete porting set in the ERP workstation environment $BSE/bin. Set BSE BSE_TMP TERM and PATH for the log on of root. Log on as root and start the ERP workstation environment $BSE/bin/binperm6.2. Copy the following files and directories of the original ERP environment to the workstation environment $BSE: Files srdd_tab6.1 ipc_info Binaries terminal files gif files postscript files Location $BSE/lib/srdd_tab6.1 $BSE/lib/ipc_info $BSE/bin $BSE/lib/terminf $BSE/gif $BSE/ps Step 2: Create shared memory parameters Run: $BSE/bin/shmvalues6.1 > $BSE/lib/shm_param. Owner: root:sys Permission: rw-r--r-- Step 3: Create the table definition file Create the file $BSE/lib/tabledef6.1: : *:*: <database server name>:n Owner: tbase:triton Permission: rw-r--r--

75 Workstation installation of Infor ERP on target environment B-3 Step 4: Set Variable BSE_REM Set the following on the UNIX level for the required variable users: BSE_REM=<hostname> Export BSE_REM The host name is the name of the original ERP server. Step 5: Create root remote user files Copy the user file of the original ERP environment to the workstation environment to $BSE/lib/user/u<username>. Create a remote user file with: Encrypt6.2 <password of the user on the original ERP server> >$BSE/lib/user/r<username> With the vi-editor add the next options the existing record: <Hostname original ERP server> < PATH of $BSE on the original ERP server> <encrypt passwd> Set the correct permissions of both the user files in the workstation environment $BSE/lib/user/* Step 6: Start the shared memory manager Start the shared memory manager for the workstation environment as user root: Shmmanager6.1 I Step 7: Start ba server for Infor ERP Set all variables for the used user (required user files in the workstation environment). Start ba6.1

76 B-4 Workstation installation of Infor ERP on target environment To establish the connection between the client and the server To establish the connection between the client and the server, Infor requires the remote user data file. You must to enter remote user data for the connection from the client to the server and from the server to the client. Note In each of the following examples, Curtis is considered the ERP source environment server, and Walker is considered the ERP target environment server. To create the first remote user file (connection from the server to the client) take the following steps: 1 Log on to the server (Curtis or Walker). 2 Start the Infor server. 3 Start the Maintain Remote User Data (ttaad2101m000) session. 4 Enter the remote user data for the connection from the server to the client: User: <UNIX log on code on client system> Hostname: <client name : aston, bade, and so on> BSE Path: <BSE on client system : /usr/bse_env2 (walker) or /usr/bse_env1 (curtis)> Old Password: <only required when you change an existing password> Password: <UNIX password on client system> Re-enter Password: <UNIX password on client system> Log on as Another User: No User on remote system: <empty> UNIX Auth. of Remote User: No Infor ERP source Auth. of Remote User: No 5 Dump the remote user data to runtime (CTRL+Z). The remote user file will be created on the server system in $BSE/lib/user/r<user>.

77 Workstation installation of Infor ERP on target environment B-5 To change your user data You must make a change in the user data to inform Infor of the client on which the user works. To change the user data, take the following steps: 1 Make sure you are in Infor on the server system. 2 Start the Maintain User Data (ttaad2100m000) session. 3 Add the following data: Application Server: <bshell_env1(curtis) or bshell_env2(walker)> Startup System: <client s name aston, bade, and so forth> 4 Dump the user data to runtime (CTRL+Z). The user file is created on the server system in $BSE/lib/user/u<user>. To create a second remote user file To create the second remote user file (connection from the Client to the Server) take the following steps: 1 Make sure you are in ERP source on the server system (Curtis or Walker). 2 Start the Maintain Remote User Data (ttaad2101m000) session. 3 Enter the remote user data for the connection from the client to the server: User: <UNIX log on code on server system> Hostname: <server name: walker or curtis> BSE Path: <BSE on server system : /c2/bse (walker) or /d4/bse (curtis)> Old Password: <only required when you change an existing password> Password: <UNIX password on server system> Re-enter Password: <UNIX password on server system> Log on as Another User: No User on remote system: <Empty> UNIX Auth. of Remote User: No Infor ERP source Auth. of Remote User: No

78 B-6 Workstation installation of Infor ERP on target environment 4 Dump the remote user data to runtime (CTRL+Z). The remote user file is created on the client system in $BSE/lib/user/r<user>. Set the BSE environment Log on to the client system (Aston, Bade, and so on). To select the appropriate BSE environment, type the following at the UNIX prompt: client: setbse (located in /usr/local/bin). To choose the environment, type 1 for ERP source (Curtis) or 2 for ERP target (Walker). Start the bshell Log on to the client system (Aston, Bade, and so forth). The bshell is started on the client in the normal way, for example, ba6.1 or bx6.1.

79 Workstation installation of Infor ERP on target environment B-7 Environment variables The client uses the following environment variables (setbse sets these environment variables automatically): Server System Curtis Infor ERP source environment Environment code : env1 BSE: /d4/bse Client System BSE=/usr/bse_env1 BSE_TMP=${BSE}/tmp PATH=${BSE}/bin:${PATH} BSE_REM=curtis BDB_DRIVER=curtis Export BSE BSE_TMP PATH BSE_REM BDB_DRIVER Server System Walker Infor ERP target environment Environment code: env2 BSE: /c2/bse Client System BSE=/usr/bse_env2 BSE_TMP=${BSE}/tmp PATH=${BSE}/bin:${PATH} BSE_REM=walker BDB_DRIVER=walker export BSE BSE_TMP PATH BSE_REM BDB_DRIVER After you establish the client-server connection, you must follow the step-bystep Conversion procedure, as described in the previous chapters, to complete the conversion.

80

81 Appendix C Customization of Data Converter Tool C Guidelines to write functions for new or changed fields: The function name must be <tablename>.<fieldname>.value. You must not pass any parameters to the function. The first executable line with in the function must be: companynr = lval(company.number). For all the queries that you are writing inside the function, add the condition <tablename>._compnr = :companynr so that your queries work for multiple company conversions. The function calls within a function are not permitted. Return value of the function must be the data type of the field. For all enum data types, use return data type as long. The following example shows a function for the field whinh220.cwar: function extern string whinh220.cwar.value() { companynr = lval(company.number) if whinh220.oorg = whinh.oorg.assembly then select whinh201.* from whinh201 where whinh201.oorg = :whinh220.oorg and whinh201.orno = :whinh220.orno and whinh201.oset = :whinh220.oset and whinh201._compnr = :companynr

82 C-2 Customization of Data Converter Tool else as set with 1 rows selectdo endselect select from where return(whinh201.cwar) whinh200.* whinh200 whinh200.oorg = :whinh220.oorg and whinh200.orno = :whinh220.orno and whinh200.oset = :whinh220.oset and whinh200.sfty = tctyps.warehouse and whinh200._compnr = :companynr as set with 1 rows selectdo return(whinh200.sfco) selectempty return(" ") endselect endif return(" ") } Guidelines to write functions for new tables: When you write the DLLs for new tables, use the following guidelines: Library name must be bctlsd<tablename>. Function that creates the data file for the new table must be dump.<tablename>. The first executable line in the function must be: companynr = lval(company.number). The parameters to be passed to the script are the directory path where the data file dump is to be placed and the driver (whether L1 driver or not). The script must dump the data into an ASCII file in the target table format. For all the queries that you are writing inside the function, add condition <tablename>._compnr = :companynr so that your queries work for multiple company conversions.

83 Customization of Data Converter Tool C-3 The following is an example of a function for the table ttcmcs001: #define REF.VARIABLES 0,0 * reference counters function extern dump.tcmcs001(string curr.dir(200),domain tcyesno l1.driver) { DLLUSAGE input: -i.curr.dir, current directory output: -o.seq.file,sequential data file constraints: nil ENDDLLUSAGE extern string SEPARATOR(1) * Field separator long fp * File ptr for ASCII dump long fperr * File ptr for Error log file long result.output * to check success of output long companynr companynr = lval(company.number) fp = seq.open(sprintf$("%s/tcmcs001.dat",curr.dir),"w") if (fp < 1) then seq.puts("error Opening tcmcs001.dat", fperr) * Error in opening the file, tcmcs001.dat return endif select tcmcs001.* from tcmcs001 where tcmcs001._compnr = :companynr selectdo ****************************************************** * This selects records from tcmcs001 and writes it * into BaaN V format of tcmcs001 table. * a) Field dsca has been left aligned ****************************************************** * Writing record to the file result.output = seq.puts(concat$("^a", tcmcs001.cuni, to.native(left.align(tcmcs001.dsca,30)), tcmcs001.tccu, tcmcs001.conv, tcmcs001.crnd, REF.VARIABLES),fp) endselect if (seq.close(fp)) then seq.puts("error : Closing the file tcmcs001.dat",fperr) endif } ************************ End of Program Script *******************************

84

85 Appendix D Installation of client for crossplatform conversion D When you migrate from ERP source environment to a ERP target environment on a Windows NT platform, a client server installation must be present on the NT machine. Take the following steps: 1 Create a user Infor on the NT system with administrator rights. Only this user can install the ERP porting set. In addition, create a conversion user on the NT machine. The user name must be exactly the same as the conversion user in the ERP environment and must have administrator rights. For example, if the conversion user Source environment is bsp, then you must also create a bsp user in NT. 2 Install the porting set for Windows NT, which is present on the CD-ROM, to a new ERP environment, for example, $BSE=E:\Baan5c. 3 Install the BW 1, which is also present on the CD-ROM, in a temporary directory if the BW is not present after you install the porting set. Copy the bin and lib directory to the ERP environment. Make sure to copy the new files, and do not overwrite the existing files. 4 Check whether the tabledef6.1 file exists in $BSE\lib and check the content. Add the following text, if this text is not yet present in the file: *:*:<baaniv server name>. 5 Start the Maintain Systems (ttaad0150m000) session in the source environment and enter the NT server name and the correct BSE path. 6 Start the Remote User Data (ttaad2101m000) session in the source environment and insert the conversion user. Enter the UNIX password in the password section. Close the session and convert the user to runtime.

86 D-2 Installation of client for cross-platform conversion 7 Copy the $BSE/lib/user/r<user> file, in which the user can be, for example, rbsp, in UNIX to the Windows NT server in the $BSE\lib\user directory. 8 Start regedit from the command line and go to the following directory: HKEY_LOCAL_MACHINE\software\baan\< BW environment name>. Create a new string value and name the string value BSE_REM. In the value data, enter the UNIX server name. 9 Start the ERP environment from the NT environment and test the client server. Use the following settings in the BW configuration: Hostname: NT Hostname. User: Conversion user. BSE: Infor ERP BSE. Bshell name: bshell.

87 Appendix E BW Configuration for various databases E Common Path Settings OPERATING SYSTEM: UNIX If the source $BSE is /a6/gemini/bse and Target environment $BSE is /a7/gemini/bse then: Scenario Single Machine Two Machine scenario with client server Two Machine scenario Without client server Common Path settings --- -set COMMOM=/a7/Gemini/tmp/ migration --- -set COMMOM=/a7/Gemini/tmp/ migration --- -set COMMOM=/a6/Gemini/tmp/ migration OPERATING SYSTEM: NT If the source $BSE is D:\Gemini and target $BSE is D:\GeminiMIG then: Scenario Single Machine Two Machine scenario with client server Two Machine scenario Common Path settings --- -set COMMOM=D:\GeminiMig\tmp\migration --- -set COMMOM=D:\GeminiMig\tmp\migration --- -set COMMOM=D:\Gemini\tmp\migration

88 6-2 Reports Scenario Without client server Common Path settings Oracle If your ERP target environment database is Oracle, before you start the conversion process, the value of Command field in the BW configuration must be set to run the ORACLE SQL* LOADER, as shown in the following figure: Figure E-1 BW Configuration, Command field As shown in this figure, the ORACLE_HOME and ORACLE_SID environment variables must be set in this Command field. ORACLE_SID is the database instance on which the ERP target environment runs. Note The ORACLE_HOME and ORACLE_SID values shown are specific to the previous figure. In your user environment, these values can differ. For details, consult your database administrator.

89 Reports 6-3 Informix If your ERP target environment database is Informix, then before you start the conversion process, the value of the Command field in the BW configuration must be set to run the Informix High Performance Loader. You must set the values INFORMIXDIR and INFORMIXSERVER in this Command field. INFORMIXDIR is the full path where Informix is installed, and INFORMIXSERVER specifies the name of the database server on which the ERP target environment runs. DB2 If your ERP target environment database is DB2, then before you start the conversion process, the value in the Command field in the BW configuration must be set to run the DB2 Loader. The DB2DIR and DB2INSTANCE environment variables must be set in this Command field. DB2DIR is the full path where Informix is installed. DB2INSTANCE specifies the name of the database instance on which the Infor ERP target environment runs. Note For a DB2 database, you must create two new tablespaces in the DB2 database with the following names in the target system before starting the first run of conversion. BCDAT tablespace to store bc tables data. BCIDX tablespace to store bc tables indices. Before you start the first run of conversion in the target environment, you must specify the following line in the db2_storage_param file, which is located in the $BSE/lib/db2 directory: bc*:*:t:group:<groupnumber>:<number>:array_size 5 T_SPACE BCDAT I_SPACE BCIDX Copy the group number and number information from the other lines of the same file.

90 6-4 Reports SQL Server If your Infor ERP target environment database is Microsoft SQL Server, before you start the conversion process, the value in the Command field in the BW configuration must be set to run the SQL Server loader. You must set the SQLDIR environment variable in this Command field. SQLDIR is the full path where the SQL server is installed. SQLDIR path is nothing less then the path of the bcp.exe command. For example, if the bcp.exe is in C:\Progarm Files\Microsoft SQL Server\80\tools\Binn then the SQLDIR path is set as set SQLDIR=C:\Progra~1\Micros~1\80\tools. It is not necessary to include the Binn directory in the setting. If a directory name contains spaces in between, then in the path we must mention the respective shortcut key. Shortcut keys may vary from system to system.