Baan IVb, IVc; BaanERP 5.0b, 5.0c. Baan Data Navigator 2.6 Administrator Guide

Transcription

1 Baan IVb, IVc; BaanERP 5.0b, 5.0c Baan Data Navigator 2.6 Administrator Guide

2 A publication of: Baan Development B.V. P.O.Box AC Barneveld The Netherlands Printed in the Netherlands Baan Development B.V All rights reserved. The information in this document is subject to change without notice. No part of this document may be reproduced, stored or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Baan Development B.V. Baan Development B.V. assumes no liability for any damages incurred, directly or indirectly, from any errors, omissions or discrepancies between the software and the information contained in this document. TopTier Software Inc, HyperRelational, HyperRelational Navigation, HyperRelational Navigation Protocol, HRNP, Drag and Relate, Point of View Navigation, and TopTier are trademarks or registered trademarks of TopTier Software Inc. in the United States and elsewhere in the world. Document Information Code: U7408B US Group: User Documentation Edition: B Date: February, 2001

3 Table of contents 1 Introduction 1-1 How HyperRelational navigation works 1-2 Navigation on the Web 1-2 Logging on to the Web Client Managing Users and Security 2-1 User Types 2-1 Finding Users 2-2 Changing Passwords 2-3 Importing Roles, Users and Security Settings 2-4 Importing Users and Security Settings from Baan IV 2-4 Importing Roles from BaanERP 2-5 Creating a Super User 2-6 Enabling Access to Multi-company Data Periodically Updating the BDN Repository 3-1 Database Updates 3-1 Table Size 3-1 Table Properties 3-2 Table Indexes Monitoring the BDN Server 4-1 Activating the BDN Server 4-1 Running the Server Monitor 4-3 Controlling Servers from the Server Monitor 4-3 Running Remote Servers 4-5 Monitoring Server Status 4-6 Server Options 4-6 Defining Server Properties 4-7 Scheduled BDN Server Shut Down 4-8 Generating Detailed Performance Logs 4-9 Memory 4-9 Toptier_sql_trace 4-10 Baan_debug_level 4-10 Baan_sql_trace 4-10 i

4 Table of contents 5 Managing Query Performance 5-1 Building a Large Table Repository 5-1 Setting Query Cost Preferences 5-2 Additional Query Management Functions Enabling Query Stop and Timeout 6-1 Implementing Stop and Timeout Changes Troubleshooting 7-1 TT Analyzer Utility 7-1 The BDN Server Does Not Respond 7-1 BDB Errors 7-2 BDB Error BDB Error Additional BDB Errors 7-2 The Web Navigator ActiveX Control/Plug-in will Not Download 7-3 First Installation 7-3 Tables Cannot be Found TopTier Analyzer 8-1 About TopTier Analyzer 8-1 Running the Utility 8-1 Performing the Analysis 8-2 Menu Usage The BDNP.ini File 9-1 [logging] 9-1 [database settings] 9-4 [environment] 9-6 [Extra Net Settings] 9-7 [Reports] 9-7 [Memory Settings] 9-7 [Excel Settings] 9-8 [Model Transport] Upgrading to BDN Implementing the BDN Upgrader 10-1 Additional Notes Licensing Baan Data Navigator Index 12-1 ii

5 About this document The Baan Data Navigator (BDN) product suite consists of two environments: The BDN run-time environment The BDN deployment environment This guide explains how to administer the BDN run-time environment. It covers periodic maintenance tasks such as importing new roles or users, security updates, or other database modifications from Baan. It provides troubleshooting for common problems, and explains how to monitor and improve system performance. For details regarding initial setup and configuration requirements see the Baan Data Navigator Installation Guide. For details regarding moving the BDN server to another machine, see the section 'Moving the BDN Server' in the Baan Data Navigator Deployer's Guide. If your Baan implementation is very similar to the standard version, then your system should be fully operational once you have completed installation. If you are using extensions that are significantly different, or if you have made changes to central tables such as customers, suppliers, items, sales orders, or purchase orders, you can customize the standard component set using the administrative tools provided with BDN. Chapter 1 provides an overview of the BDN product suite. Chapter 2 explains how to manage users and user security. Chapter 3 describes how to import information from the Baan database into the BDN environment, following changes to the Baan database. Chapter 4 explains how to monitor the BDN server and to increase server capacity. Chapter 5 explains how to monitor query performance and to limit access to resource-intensive queries. Chapter 6 explains the implementation of the query timeout and stop functions so that they work properly on both NT and Unix servers. Chapter 7 provides advice about troubleshooting problems that may arise during system administration. iii

6 About this document Chapter 8 describes the TopTier Analyzer utility and its role in system administration and/or troubleshooting activities. Chapter 9 provides a detailed description of the BDNP.ini file, which enables generating detailed log files and defining various environment parameters. Chapter 10 provides details about the BDN Upgrader. Chapter 11 details the Baan Data Navigator licensing procedures. This guide assumes that you have experience administering Baan systems. iv

7 1 Introduction BDN HyperRelational technology provides a new, easy way to work with Baan systems. An innovative Drag and Relate interface allows both experienced Baan users and those with no database skills, to access and correlate information from within Baan and from diverse data sources throughout your organization. Unlike conventional hypertext front-ends, BDN HyperRelational navigation features: Logical links to dynamic database information, as opposed to static physical links or hard-coded queries. Many-to-many relationships for referencing multiple database tables that have no predefined relationship between them. User-controlled navigation paths, rather than a predefined set of links. With HyperRelational navigation, users create their own queries using a simple drag-and-relate interface. BDN 2.6 supports Baan IVb, Baan IVc, BaanERP 5.0b, and BaanERP 5.0c standard versions. The BDN security mechanism is fully integrated with the one in the Baan environment. The BDN product suite includes a run-time environment with predefined HyperRelational components based on the most commonly used Baan sessions. By using the BDN Deployment Environment, you can enhance and extend the package. 1-1

8 Introduction How HyperRelational navigation works You can perform HyperRelational navigation from a Web browser. Navigation on the Web HyperRelational navigation from a Web browser involves your Baan database, a standard Web server, and the BDN server. BDN Web client Web (HTTP) server BDN server BDN repository BAAN database Users work in a standard Web browser with BDN s WebNavigator. The Web Navigator is a plug-in for Netscape browsers or an ActiveX control for Microsoft Internet Explorer. The Web Navigator sends requests for information to the BDN server. See the BAAN Data Navigator Installation Guide for instructions on how to install the Web Navigator. The BDN server receives requests from the browser, populates HTML templates with information from the BDN repository and the Baan database, and then sends the information back to the Web client. A standard Web server is used to handle images and the home page of the BDN application. The BDN repository contains information about the database model and the relationships between data that enables HyperRelational navigation. It is included as part of the server installation. 1-2

9 Introduction Logging on to the Web Client The following procedure takes you to the logon dialog box: 1 Make sure that the Web server is running. 2 Invoke your Web browser. You can use either Netscape or the Microsoft Internet Explorer. 3 Open the main page of the application by typing the following URL address in the field at the top of the Web browser, and pressing enter: For example, if the Web server is located on a computer that is identified as Martin_O on the network, type the following address: This formula is correct when the Shell.html file is located directly inside the Web server root. If the Shell.html file is located in a subfolder of the Web server root, then the address should include the full path to the Shell.html file from within the Web server root. When you are prompted, enter your user name and password. The main page of the DataNavigator appears, with a toolbar displayed on the left side. If your application supports SSL, the URL for accessing BDN in the SSL configuration begins with https rather than http; the added s stands for secure. In addition, it points to ssl_shell.html, in the same location. For example, if the URL for the normal configuration is then the URL for the SSL configuration is: 1-3

10 Introduction Introducing data navigation BDN data navigation consists of dragging data records from one session and dropping them onto another to retrieve related information. This technology is called Drag and Relate. Users decide what information they want and determine a navigational path on the fly, without relying on predefined, hard-coded queries defined by the system author. This section illustrates data navigation with BDN. The screen below is the Find form displayed when the Customers icon is doubleclicked. It lets you search for a particular customer in the Sales group. Find Icon Click the Find icon (without limiting the search) to display a list of customers in the database. Click the Next and Previous buttons to view all the records. 1-4

11 Introduction Each link in the screen is HyperRelational and can be clicked or dragged onto another component. For example, dragging customer number 9001 onto Sales Orders displays a list of all of that customer's orders. 1-5

12 Introduction The purple icon at the top of the form, called a HyperRelational Track link, enables data navigation with multiple data records. For instance, dragging this icon onto the Sales Order Lines component displays the details of all three sales orders. Note that below the form is a description of the navigation path used to generate this particular list of data records. In this example, customer 9001 was dragged onto the Sales Orders components, then all the Sales Orders records in the list were dragged onto the Sales Order Lines component. In other words, the list displays the Sales Order lines records for the orders placed by customer Click the asterisk (*) in the View field (above form) to display the details of an order line in a single-occurrence form. 1-6

13 Introduction To view the invoice associated with this order, drag the orange or purple icon from the top of the form to the Invoices icon. Or, to view the delivery status, drag one of the icons onto Delivery. With BDN, you can continue to drag and relate data until you find the data you need. For more information about data navigation, see the Baan Data Navigator Web Navigation Guide. 1-7

14 Introduction 1-8

15 2 Managing Users and Security The Baan system includes user (Baan IVb, IVc) or role (BaanERP 5.0b, 5.0c) definitions, and security profiles. These parameters are handled in the Baan system and imported into BDN. User passwords must be defined separately in both the Baan system and BDN. The security-related BDN administration tools enable: Finding and viewing BDN users. Changing user passwords. Importing users or roles, and security definitions from Baan into BDN. Defining user access to data from more than one company at a time, only for BaanERP. NOTE: User Types The BDN administrator has three user logons available: The user Setup has access to all BDN administration tools. To perform all routine administration, log on as Setup. The default password is Setup. The user toptier has access to all BDN deployment tools, including the Model Transporter, the Component Editor, and Autocomplete Relations. This user must also be defined on the Baan system. The default password is toptier. The user TTPassword allows the administrator or deployer to log on as any net user by entering a universal password. This user is not imported from Baan, but is a Super User created by the administrator or deployer. The default password is TTPassword. The logon fields are case-sensitive. It is recommended that you change the password to improve security (see below). All users imported from Baan are of TTBaan type. Users with administrator privileges within the Baan system can change user passwords within BDN, but will not have access to any other BDN administration tools unless they log on as user Setup or user toptier. This guide indicates when it is necessary to log on as Setup, and when as toptier. 2-1

16 Managing Users and Security Finding Users The User tool lets you check which users are currently defined in BDN. To find a specific user: 1 Log on to the BDN desktop client as user Setup or toptier. 2 Double-click the User icon in the Utilities toolbar. 3 Type in the user name and click Find. If the user is defined, the rest of the details appear. To display a list of all users in the system: 1 Double-click the User icon in the Utilities toolbar. 2 Leave all fields in the User dialog box blank, and click Find. 3 To display details about a specific user, double-click in the User Name field. 2-2

17 Managing Users and Security Changing Passwords When importing users from Baan, BDN assigns the user name as the initial password, since the actual passwords cannot be obtained directly from Baan. To improve security, it is recommended to redefine user passwords. You change passwords with the User tool. Users can change their own passwords. Baan administrators can also change passwords for other users. To change a password: 1 Log on to the BDN desktop client as a valid Baan user with administrator privileges, or as user Setup. 2 Launch the User component from the Utilities toolbar. 3 Type in the user name and click Find. 4 Click Change Password. Type in the new password, confirm, and click Change. 2-3

18 Managing Users and Security Importing Roles, Users and Security Settings During the setup stage following installation, you use the Security Update tool to import the role profiles from BaanERP, or the current user and security profiles from Baan IVb and IVc. As new roles or users are added to the system, you import them into BDN. You also import updates to role and user security profiles. Importing Users and Security Settings from Baan IV 1 Log on to BDN desktop as user Setup (default password Setup). Note that these fields are case-sensitive. 2 In the Utilities toolbar double-click Security Update. 3 In the Import? column, select the users to import. 4 You can import security data from the Baan installation by company, by session, by table, or by table data. Select the options that are appropriate to your Baan implementation. 5 Click Import. A progress bar at the bottom of the BDN window reports on the import process. To import all the security data may take some time. 6 When the import process is complete, click Close. 2-4

19 Managing Users and Security Importing Roles from BaanERP 1 Log on to BDN desktop as user Setup (default password Setup). Note that these fields are case-sensitive. 2 In the Utilities toolbar double-click Security Update. 3 You can import security data from the Baan installation by hierarchy, by session, by table, or by table data. In the User/Security Transporter dialog box, select the options that are appropriate to your Baan implementation. 4 To launch the process, click Import or Exclusive Import. With Import, the process takes significantly longer than with Exclusive Import; however, choosing Import enables users who are logged on to the system to continue working during the security update. Do not use the Exclusive Import option unless you are sure that no user is logged on. When the import process begins, a progress bar appears at the bottom of the BDN window. To import all security data may take some time. 5 When the import process is complete, click Close. 2-5

20 Managing Users and Security Creating a Super User The system administrator or deployer must be able to view data and system layout from any particular user's perspective. Therefore, you must define a Super User with a universal password. For example, if a user forgets a password or has problems with the client machine, the administrator can log on as that user, using the universal password, and solve the problems. To create a Super User: 1 Log on to the desktop as toptier/toptier or Setup/Setup. 2 In the Utilities toolbar, click the User component to display the User dialog box. 3 From the toolbar Data menu select Add User. 4 Type TTPassword in both the Name and Description fields. 5 Check the Define user as an administrator checkbox. 6 Click Save and then click Close. The password TTPassword is hard coded. The system detects that a user has been added and accepts TTPassword as a universal password. When an administrator logs on as another user, the system checks the password. If it is not the user's password, it checks if it is the universal password and allows the logon. Enabling Access to Multi-company Data The Baan security mechanism defines which companies each user can access. If you are working with BaanERP, the Multi Company Settings component lets you enable users having access to more than one company to view data from several companies at once. Initially, you use the Multi Company Settings component to import the company access definitions of all Baan users. Following this setup step, users navigating in the Use Multi Company mode will see data related to all of the companies to which they have access in component forms that display multiple records. You can also use the Multi Company Settings component to specify, per user, that only data related to certain companies is displayed in the Use Multi Company mode. 2-6

21 Managing Users and Security For example, if Baan defines a user as having access to 16 different companies, you could use the Multi Company Settings component to specify three of these companies. When the user navigates in the Use Multi Company mode, only data from the three selected companies is displayed in component forms that display multiple records. To enable access to multi-company data: 1 Make sure that you are logged on as user Setup. 2 In the Utilities toolbar, double-click the Multi Company Settings icon; a list of users appears. 3 Click Import to import all users' company access definitions from Baan. 4 Double-click a user to display a dialog box with a list of companies the user is allowed to access. 5 In the Allowed field of each company in the list, select Yes or No from the popup menu to include or remove the company from the list of companies whose data is displayed in component forms in the Use Multi Company mode. 6 Click Save. 2-7

22 Managing Users and Security 2-8

23 3 Periodically Updating the BDN Repository The BDN repository contains session data, including information about forms, fields, and relations imported from the Baan Data Dictionary into the BDN system. By default, the information in the BDN repository corresponds to the standard Baan version. During installation, use the BDN tools to update automatically the BDN repository to reflect the local Baan version. Following the initial installation and setup, you periodically update the BDN repository to reflect additional modifications to the Baan system. You use the Database Updates tool to import information about table size, indexes, and properties into the BDN repository. This process can take some time to complete, depending on the size of your system tables and the number of tables involved. Database Updates The Database Updates tool imports information about column attributes, table sizes, and table indexes from the Baan system into the BDN repository. Following a Baan system update, you use the Database Updates tool to import the current Size, Index, and Property data into BDN. If the database changes also affect component forms, you can use the Model Transporter to regenerate components, as described in the Baan Data Navigator Deployer's Guide. Table Size The Update Table Size command imports information about the size of the tables in the Baan database. It ensures accurate performance monitoring during run time. To update table sizes: 1 Log on to the BDN desktop as Setup/Setup. 2 In the Utilities toolbar double-click the Database Updates icon. 3 In the Database Updates dialog box, select the tables that have changed, and click Size. 4 The import process begins and a progress bar is displayed at the bottom of the BDN window. 3-1

24 Periodically Updating the BDN Repository Table Properties The Update Table Properties command imports information from your Baan database regarding alignment of fields such as items or customers, as well as several other configurable parameters. To update property attributes: 1 Log on to the BDN desktop as Setup/Setup. 2 In the Utilities toolbar, double-click the Database Updates icon. 3 In the Database Updates dialog box, select the tables that have been modified, and click Properties. 4 The import process begins and a progress bar is displayed at the bottom of the BDN window. Table Indexes The Update Table Indexes command imports information about the Baan database indexes. To update table indexes: 1 Log on to the BDN desktop as Setup/Setup. 2 In the Utilities toolbar, double-click the Database Updates icon. 3 In the Database Updates dialog, select the tables that have changed, and click Index. 4 The import process begins and a progress bar is displayed at the bottom of the BDN window. 5 After the import process is complete, click Close. 3-2

25 4 Monitoring the BDN Server The BDN server is responsible for all communication between the Web browser and the database. The browser sends requests to the BDN server, which populates the HTML templates with the requested data and sends HTML files back to the browser. The number of users and requests, database speed, the complexity of queries and various other factors all affect the performance of the system. You can run more than one BDN server when warranted by the load on your application. A single server monitor lets you control and view the status of all running BDN servers. BDN supports Secure Sockets Layer (SSL) in Microsoft Internet Explorer. The Secure Sockets Layer protects transmissions in a network by guaranteeing an authenticated connection between server and client and enabling encrypted communication between them. For complete information about SSL support in BDN applications, see Baan Data Navigator Installation Guide. Activating the BDN Server To activate the BDN server: From the Windows Start menu, open the BDN program group and select the BDN Server Monitor. A prompt appears indicating that the service is not active and offering the option to start it. 4-1

26 Monitoring the BDN Server Alternatively, to activate the BDN server from the Windows Settings menu: 1 From the Windows Start > Settings menu, open the Control Panel, and double-click Services. 2 In the Services dialog box, scroll to select your server. The server name begins with TopTier Server and includes the BDN project name. 3 Click Startup to display the Service dialog. In Startup Type, it is recommended that you change the startup mode to Automatic so that the server starts automatically each time the system starts. 4 Press Start to run the server. NOTE: If you make any changes in the Startup mode while the server is running, stop and then restart the server. 4-2

27 Monitoring the BDN Server Running the Server Monitor To run the server monitor, choose BDN Server Monitor from the Microsoft Windows Start > Programs > BDN menu. If you attempt to run the monitor before starting the service, you are prompted to start the server. By default, the BDN server runs a single server instance on the local machine. You can run additional servers on your machine, and run servers on remote machines, as described later in this chapter. Controlling Servers from the Server Monitor The server monitor is a multiplexer program that can run and monitor multiple TopTier servers. Server monitor BDN server BDN server BDN server 4-3

28 Monitoring the BDN Server The server monitor functions as a load distributor that distributes requests among the servers. It also monitors the servers, so that if one fails, it is automatically reinvoked. By using the server monitor you can add and remove servers, including remote servers. The Active Server Instances list displays the currently running servers. The box at the bottom of the window displays a log of requests that are sent through the monitor. To add a server: 1 Click the Change Capacity button in the Server Monitor window to display the Set Local Capacity dialog box. 2 In the Set Local Capacity dialog box, enter the number of server instances you want to run on this machine. 3 Click OK. 4-4

29 Monitoring the BDN Server To decrease server capacity: 1 Select the server name from the Active Server Instances list. 2 Click the Remove button. Alternatively you can decrease the number of server instances in the Set Local Capacity dialog box. Running Remote Servers During periods of intense user traffic, you can run additional BDN servers on remote host machines. These servers have their own local capacity; however, one central server monitor acts as the entry point for the entire application, channeling all requests to server instances on the local machine and to servers on remote machines. When connecting to a remote server, the central server automatically detects the remote port number and capacity. The central server also detects any change in the capacity of the remote server. To run additional servers: 1 Click Use Remote Server in the TopTier Server Monitor dialog box. 2 Enter the Address and click OK. It is recommended you use the Fully Qualified Domain Name (e.g. joe_nt.company.com); however, you can also use the IP address (e.g ) or the host name (e.g. joe_nt). 3 From the list, select the service that you want to run and click OK. 4-5

30 Monitoring the BDN Server Monitoring Server Status The status area below the Active Server Instances list displays information about the number and frequency of hits, and of heavy hits. A heavy hit is a request that took a relatively long time to carry out. Use the information about heavy hits to analyze the performance of your application and to adjust the number of servers accordingly. The server log lists all events associated with the servers currently running from the server monitor, including errors, add and remove, hits, and heavy hits. In addition to the information provided in the online monitor, the log indicates the request that resulted in a heavy hit. With this information, you can determine if there are performance problems with particular queries. To view the BDN server log, click the View Log button. Server Options Click the Options button to: Set the server monitor s port. The default is Modify this port if another device already uses this port number. Set the length of a heavy hit. Enable the log file. 4-6

31 Monitoring the BDN Server Defining Server Properties To view or modify server properties, in the BDN Server Monitor click Properties, or choose BDN Server Properties from the Start > Programs > BDN menu. Note that the properties apply to all BDN servers running on the same machine. The following is a description of the BDN server properties: Project Name: The unique name of the BDN application. Media Path: The full path to the directory that contains all the media items used in the application, such as images, movies, and so on. Media Path Alias: The alias for the media path. The value must be TopTierMedia. Plug in location: The name of the file containing the updated plug-in to download. Central Server Address: The IP address of the central server. 4-7

32 Monitoring the BDN Server Central Server Port: The port number of the central server. Server address to appear in HTML links: The format of the server name to be used in the HTML files. You may have to change the address type in order to make the server accessible to all machines. IP Address: :9999/BIOG/Person_ID/5 Fully Qualified Domain Name: joe.company.com:9999/biog/person_id/5 Host Name: Joe_NT:9999/BIOG/Person_ID/5 Allow guests: This option is not implemented, as it reduces security. Guests Account: Defines a user name for the guest account when Allow guests option is implemented. Scheduled BDN Server Shut Down Many BDN installations have their Baan server shut down periodically, causing lost connectivity to the BDN server. The BDN server is also used for operations other than connection to Baan. In order to avoid the inconvenience of these shutdowns, you need to configure an automatic shutdown of the BDN server that corresponds to the times of the Baan server shutdown. To schedule these shutdowns, use the OS net start option for stopping and restarting services provided with WinNT. 1 Open the DOS window. 2 At the Command prompt, type the following: at TIME net start\stop "ServiceName ProjectName" For example: at 15:30 net start "TopTierServer BDN_B1" at 19:00 net stop "TopTierServer BDN_B1" 4-8

33 Monitoring the BDN Server Generating Detailed Performance Logs BDN enables generating detailed log files that can be used for diagnostic purposes. These files are in addition to the log file maintained by the BDN Server Monitor. You activate the different log options in the BDNP.ini file, which is located in the BDN\Datafile folder. See Chapter 9, The BDNP.ini File, for a detailed description of the file. There are four log options: memory, toptier_sql_trace, baan_debug_level, and baan_sql_trace. When you activate the memory option, a log file called SrvMemx.xls is created in the BDN application folder, where x is the log file instance. In other words, the first time you activate the log and restart the server, SrvMem1.xls is created. If you restart the server, SrvMem2.xls is generated, etc. The log information generated by the other three log options is written to a file called DBG_StdErr_x.log in the BDN application folder, where x is the log file instance. Memory While the Memory log option is active, memory usage data is logged for each hit. You can use this log to locate memory leaks and evaluate system performance. By default this log is off. To turn it on, change the memory value to 1 (1= ON, 0= OFF), and restart the BDN server. SrvMemx.xls is created in the BDN application folder. This file is formatted for viewing in an Excel spreadsheet. 4-9

34 Monitoring the BDN Server Toptier_sql_trace Toptier_sql_trace logs all transactions between the BDN server and the BDB library. By default this log option is off. To turn it on, change the toptier_sql_trace value to 1 (1= ON, 0= OFF), and restart the BDN server. Log information is written to DBG_StdErr_x.log. Baan_debug_level Baan_debug_level logs all activity in the BDB library. To activate this log option, change the baan_debug_level value to YES, which defines the default log level 02000, and restart the BDN server. Alternatively, you can set a specific Baan log level and restart the BDN server. Log information is written to DBG_StdErr_x.log. Baan_sql_trace Baan_sql_trace logs all transactions between the BDB library and the Baan server. To activate this log, change the baan_sql_trace value to YES, which defines the default log level 1, and restart the BDN server. Alternatively, you can set a specific Baan log level and restart the BDN server. Log information is written to DBG_StdErr_x.log. 4-10

35 5 Managing Query Performance BDN enables users to navigate throughout the entire Baan database, even between tables that have no indexes. As a result, performance issues can arise while you navigate through large tables. The database update functions and the Query Cost tool can help you monitor, and if necessary, limit access to resourceintensive queries. Building a Large Table Repository The Update Table Size function in the Database Updates dialog box imports information about large tables in the Baan database, and stores it in the BDN repository. This information includes the number of records in each table, and is used to evaluate the expected length of time to perform a non-indexed query. You run the table size update during the setup stage following installation. If there are significant changes to the sizes of tables in the database, you must run it again, as described in Chapter 3, Periodically Updating the BDN Repository. 5-1

36 Managing Query Performance Setting Query Cost Preferences You can activate query cost monitoring and set preferences that affect all BDN users. There are two types of preferences that you can set: Query Cost Limit: The cost of a query is measured by the number of records that have to be scanned in order to provide an answer to the query. The actual execution time varies, depending on the performance of the Baan server. The Query Cost Limit is an indicator of relative length, and can be fine-tuned based on experience. When a user generates a query through drag-and-relate operations, if the number of records that needs to be scanned exceeds the defined Query Cost Limit, a warning appears indicating that the query may take a long time to process. The user can choose to continue the query or to stop it. You can set upper and lower limits so that if the estimated query cost exceeds the upper limit that you set, the user will not be able to proceed. Similarly, if the estimated query cost is less than the warning level, no warning message is displayed. Efficient Drags Only: Enables drag and relate operations only on fields that are indexes, primary keys, or foreign keys. This limits HyperRelational navigation, but eliminates performance problems. You can set a lower limit, so that drag and relate operations may be permitted on very small tables, even when the fields are not indexed. To set query cost preferences: 1 Log in as user Setup. 2 Double-click the Query Cost Settings icon in the Utilities toolbar. 3 Change the preferences (see list below). Click Close when you are done. 5-2

37 Managing Query Performance 4 After you make modifications, test the system to make sure the results are appropriate. The following settings are available: Allow only efficient drags: Enables HyperRelational navigation only on fields that are indexes or keys. The default value, N, does not activate this option. If you change the value to Y, you must also define the Allow drags if less than X records parameter. Allow drag if less than X records: If the Allow only efficient drags option is activated, this option will permit drag and relate operations on very small tables, even when the fields are not indexed. The default value is 10,000 records. Maximum query cost allowed in rows: Indicates the upper limit for query cost evaluation. If the estimated cost exceeds this number (i.e. if the number of records that have to be scanned to provide an answer to the query exceeds this number), the user will not be allowed to proceed. The default value is 500,000 records. You can change the upper limit for individual users. Default lower limit in rows: Indicates the warning level for query cost evaluation. If the estimated cost is less than this number, the user will not be warned before this query is carried out. The default value is 45,000 records. Use query cost limit: Indicates whether query cost evaluation will be used. The default value, Y, activates query cost evaluation. If you change the value to N, no cost monitoring will be performed. To set the upper limit for individual users: 1 Double-click the Query Cost Settings icon in the Utilities toolbar. 2 Click the Set User Specific Upper Limit button. 5-3

38 Managing Query Performance 3 Enter a new value in the Query cost upper limit field. 4 Check the Update field next to each user to whom you want to apply the new value. 5 Click the Update button. Additional Query Management Functions In addition to the update database and query cost management functions, the administrator can also limit the maximum number of records returned by any single query, and also enable or disable the Count function. The Count function, if enabled, displays on the list form the total number of records returned by the current query. The Count function can be time-consuming if there are many records to count, or if the scanning of the records is slowed down for any reason. However, since this function is subject to the Stop and Timeout, as well as the Query Cost settings, the count can be stopped by the user at any time, or automatically by limits set by the administrator. It is, therefore, advisable to use the Query Cost tool and to enable the Stop and Timeout functions. For a detailed discussion of these functions, see the sections Setting Query Cost Preferences above, and the Enabling Query Stop and Timeout chapter. To limit the maximum number of records retrieved by a single query, see the database settings section of The BDNP.ini File chapter. 5-4

39 6 Enabling Query Stop and Timeout After the launching of a long query from a BDN client browser, a number of actions can cause the interruption of that query before completion. For example, activating another component, or clicking the Back or Stop buttons cancel a query in process; the elapse of an administrative time allowance per fetch also stops a query in process. The BDN client server works in conjunction with the TopTier BDB server on a remote Unix machine. A Query launched from BDN activates the BDB server in a data retrieval process. The administrator must therefore implement adjustments after the BDN installation to ensure that the cancellation of a query process stops the entire query process, not only on the client side, and enables the system to restart and be ready to handle a new query. Implementing Stop and Timeout Changes The BDN server runs on NT opposite the TopTier BDB server which runs on Unix. The TopTier BDB server uses a database driver to access and retrieve actual data from the Baan database. If this database driver is located on the NT machine where the BDN server is running, then the connection between BDN and the Baan database is a native connection. Where there is a native connection the administrator need only make definition changes on the NT side. The more probable scenario, however, is one without a native connection so that both the NT and the Unix administrators must make changes and additions to database settings and environment variables. 6-1

40 Enabling Query Stop and Timeout To implement the NT changes: 1 In the server.lst file, located in the root folder of the BDN installation, add the line Accept Stop=1. 2 In the database settings section of the BDNP.ini file, located in the installation datafile folder, add the following parameters and values: fetch_timeout = <number_seconds> A query is stopped if it does not begin to return a reply within the specified number seconds. server_bdb_dll = Sockets_BaanDB.dll This entry indicates the use of a Unix process to enable the cancellation of queries. OR: server_bdb_dll = rpc_baandb.dll In the case of a native connection, the rpc_baandb.dll may be used, requiring no changes to be made on the Unix side. NOTE: A native connection does not preclude the use of the Sockets_BaanDB.dll, but the use of this.dll then requires the same changes on the Unix side as if there were no native connection. bdb_host = <Unix_server_name Unix_server_FQDN Unix_server_IP_address> The bdb_host can be specified by any name that returns a ping reply on Unix. 6-2

41 Enabling Query Stop and Timeout bdb_port = <first_unix_port> The number indicating the Unix port must be identical to that entered for the TopTier BDB server Unix process. The default port number for the Unix side is To implement the Unix changes: 1 Set the correct BSE and USER environment variables for the user running the process. Make sure the USER is identical to its respective setting in the BDNP.ini file on the NT side. 2 Run the ps -ef command and verify that the output line returns the entire command line, including the command parameters, that the PID column appears second, and that the PPID appears third. 3 Verify that the port number of the TopTier BDB server is unused. Verify that the port number is in an area where the next 1000 ports are largely available. It is the first gateway of communication between the BDN and Unix servers. The port number is an optional parameter of the command line that executes the running of the TopTier BDB server: TopTierBdbServer &, where is merely an example. If the port number parameter is omitted the default, 21500, is used. 4 Make sure that the TopTier BDB server is running. It must be running when the BDN server is running. 6-3

42 Enabling Query Stop and Timeout 6-4

43 7 Troubleshooting This chapter discusses some problems or questions that may arise while administering the application. TT Analyzer Utility BDN includes TopTier Analyzer, a utility that is very useful for troubleshooting. It checks the BDN installation on your computer and provides additional information about required software and hardware. The Analyzer reports on: The BDN components located on your machine. Files required by each BDN component. User and computer information, system resources and operating system. Browsers and the path of the BDN ActiveX component. Network information. Database parameters. BDN server properties. The output is displayed in the TopTier Analyzer window and you can print it, send it or save it by choosing the appropriate command from the File menu. See TopTier Analyzer for complete information about this utility. The BDN Server Does Not Respond If the BDN server does not respond to requests from a Web Navigator client, check the following: Make sure the BDN server is running. Check the Web server settings. Make sure you are using Microsoft Internet Explorer version or higher, or Netscape Navigator version 4.0 or higher. Make sure you are typing the correct URL. See the Baan Data Navigator Installation Guide for information about logging on when the system has SSL support. Make sure your plug-in or ActiveX control is installed and up to date (if you are dealing with a system upgrade). 7-1

44 Troubleshooting BDB Errors During run time, you may receive one of the following BDB error messages from the Baan server: BDB Error 850 Error 850 means there are no more user connections available for the BDN client. When the Baan server resides on a Windows NT server machine running a Microsoft SQL server, a pre-set parameter in the SQL server determines the number of allowed user connections. You can check the number of user connections available to your Baan server in the Microsoft SQL Enterprise Manager. For more information, refer to the Microsoft SQL Server documentation. Refer to your database administrator about increasing the number of SQL user connections. BDB Error 506 The user logon is related to company 000 (for example, the user toptier), which permits no access to database tables. Make sure you log on as a standard Baan user. Additional BDB Errors This list describes the BDB errors relevant to the Baan Data Navigator Suite. For a complete list of all BDB errors, refer to the Baan documentation. 107 Record is locked 111 No record is found 113 Table is locked 116 Cannot allocate memory. Out of memory 142 Some administration process is running 202 Database is locked 208 Permission denied 506 Table does not exist 508 Not logged on to a database 511 Version of client versus server not correct 514 Security error 601 Reference table is locked 607 Reference table is not found 7-2

45 Troubleshooting The Web Navigator ActiveX Control/Plug-in will Not Download This section describes possible problems downloading the Web Navigator client. First Installation If you cannot download the client ActiveX control/plug-in, check the property settings of the BDN Web server root directory. To verify the property settings of the BDN Web server root directory: 1 Run the Internet Information Server in the Microsoft Management Console from Windows. 2 In the Console Root, under Internet Information Server, expand the folder representing the IIS server machine, and select the BDN Web server root directory. 3 From the Action menu, choose Properties, and in the Directory tab make sure under Access Permissions, Read is selected, but that under Permissions, Execute is not. Tables Cannot be Found Following installation, if you are unable to successfully navigate, either receiving messages that the user table cannot be found, or failing to locate tables that you know exist, check the following: Make sure the file BDNP.ini references the correct path for the Baan server. Make sure the remote server is defined correctly. Make sure the BSE string values in the registry reflect the correct path to the file rbaan in the folder lib/user. 7-3

46 Troubleshooting 7-4

47 8 TopTier Analyzer TopTier Analyzer is a utility designed to check your BDN installation. In general, it displays the attributes of the products comprising BDN, checks the database connections, retrieves information about the computer on which the product suite is running, and checks the product files. About TopTier Analyzer This utility is useful for troubleshooting purposes and for obtaining additional information about the required software and hardware. The analysis is divided into sections, depending upon what is being checked. After testing the components comprising each section, TTAnalyzer reports the results, including errors and inconsistencies. Running the Utility TopTier Analyzer is located in the Utilities\TTANALYZER folder of your BDN application directory. Running the TTAnalyzer.exe file displays the general settings of the application. These include: The application path; for example, E:\BDN 2.6. The products installed in the application folder; for example, BDN Desktop, BDN Server, Report Server and possibly the WebNavigator. The product version; for example, NOTE: NOTE: The Datafile for each product; for example, the data folder of the BDN desktop: E:\BDN 2.6. If all the products point to the same Datafile, it is shown only once. To run the utility: 1 Browse to the Utilities/TTANALYZER folder. 2 Double-click TTAnalyzer.exe. Running the TopTier Analyzer before connecting to a database driver, or after clearing ODBC settings, returns an error message. 8-1

48 TopTier Analyzer Performing the Analysis To begin the analysis, select Start from the toolbar Tests menu. The Analyzer retrieves the following information: User This is the name of the user currently logged onto the system. Computer This is the computer name of the current system. Computer Resources Processor type of processor. Total physical memory total number of KB of physical memory. Available physical memory number of KB of physical memory available. Swap file size total number of KB that can be stored in the paging file. Swap file usage total number of KB available in the paging file. Available disk space amount of free space on every local disk. Video display information about the display device. OS Version This is the version of the operating system that is currently running. Browsers The utility displays the following: Registered Browsers Shows the path of Netscape and Internet Explorer from the registry, if available. Default Browser Shows the path of the default browser from the registry. All Browsers (found on local disks) Scans all the local disks, looking for NETSCAPE.EXE and IEXPLORE.EXE, and shows the paths of all the browsers that were found. To skip this test, click 'S'. TopTier ActiveX path Looks for the key of TopTier ActiveX in the registry and shows the path of the ActiveX if one is found. For example: C:\WINNT\TopTierWebNav\WebNavigator.ocx 8-2

49 TopTier Analyzer TopTier Query Editor ActiveX path Looks for the key of TopTier Query Editor ActiveX in the registry and shows the path of the ActiveX if one is found. For example: C:\WINNT\TopTierComponents\TTQI.ocx TopTier Objects ActiveX path Looks for the key of TopTier Objects ActiveX in the registry and shows the path of the ActiveX if one is found. For example: C:\WINNT\TopTierComponents\TTObjectsCtrl.ocx TopTier OLE-DB Provider path Looks for the key of TopTier OLE-DB Provider in the registry and shows the path of the.dll if one is found. For example: C:\WINNT\system32\TTOleDB.dll TopTier DE OLE-DB Provider path Looks for the key of TopTier deployment environment OLE-DB Provider in the registry and shows the path of the.dll if one is found. For example: C:\WINNT\system32\TTDEOleDB.dll TopTier HRNPAPP path Looks for the key of TopTier HRNPAPP in the registry and shows the path of the.dll if one is found. For example: Network C:\WINNT\TopTierWebNav\HRNPAPP.dll Host DNS name The name of the local host, which can be a simple host name, or a fully qualified domain name). Host IP address The IP Address of the local computer. Database Parameters NOTE: The Analyzer retrieves the connection strings from ODBCSettings.prm and tries to connect to the database, using those strings. If the connection attempt fails, an ODBC error is displayed. It also tries to connect to the Repository. If all the products are using the same Datafile, the Analyzer tests only once; otherwise, it runs a test for each product that is different. 8-3

50 TopTier Analyzer Example: BDN Desktop Repository connection string: DRIVER=Microsoft Access Driver (*.mdb); DBQ=%DATA_FILE_DIR%TopTierRep.mdb Connected successfully. Server Properties TTAnalyzer retrieves the following information about the TopTier server and the TopTier report server. Server name same as the project name (TopTier server only) Central monitor address the multiplexer address Central monitor port the multiplexer port Type HRNP for TopTier server and Report for TopTier report server Default servers the port number of the default server instance Log file only for TopTier report server; shows the path of ReportServer.log; also checks if the folder is the same as the application folder, and issues a warning if it isn't Path only for TopTier report server; shows the path of ReportServer.mul; also checks if the folder is the same as the application folder, and issues a warning if it isn't TopTier Report Server as Service The Analyzer looks for the service with the same name as the project name. Name - name of the service Status - current state of the service; can be one of the following: Not Running Running Paused Startup - Specifies when to start the service; can be one of the following: Automatic Manual Disabled 8-4

51 TopTier Analyzer Baan Properties The TTAnalyzer searches for each setting in the following order: 1 HKEY_CURRENT_USER\Environment 2 HKEY_USERS\.DEFAULT\Environment 3 BDNP.ini Searching for the setting: BSE_REM BAAN Server Name (BSE_REM):BAAN_SERVER( was found in BDNP.ini) Searching for the setting: user user:baan (was found in BDNP.ini) Searching for the setting: BSE Location of BAAN client (BSE):'e:\bdn3' (was found in BDNP.ini). Baan connectivity Tests This section shows the results of the pinging attempt. Pinged the Baan server (BAAN_SERVER) successfully Failed querying BDB with the query "select T0.user:col0 from ttaad200 T0" Contents of tabledef6.1: The following error message was returned because the file was not in the folder. Cannot open the file tabledef6.1. Error: Access to E:\BDN3 was denied.. Contents of rbaan: Cannot open the file rbaan. Error: Access to E:\BDN3 was denied.. 8-5

52 TopTier Analyzer Application File Check NOTE: The utility makes a list of all the files that currently exist in the application folder and compares it to a list of files that describes the original files. Once it verifies that the file exists, it compares the: Version - Does it have a version, and is it correct? Attributes - Are the file attributes correct? At the end of this particular analysis, TTAnalyzer issues a report. If no problems were found, the message reads: Completed successfully. If there are inconsistencies, it lists them, with an explanation. Any additional files contained in the application, such as those that are installed after performing Model Transporting, are not checked. Menu Usage The output of the analysis is displayed in the TopTier Analyzer window. You can: Print the analysis. Send the analysis as . Save the analysis by choosing the appropriate command from the File menu. 8-6

53 9 The BDNP.ini File This chapter describes the BDNP.ini file in detail. BDNP.ini is located in the BDN installation Datafile folder. [logging] BDNP.ini provides four different log options that enable generating detailed log files. These log files can be used for diagnostic purposes: memory, toptier_sql_trace, baan_debug_level, and baan_sql_trace. memory = 0 Any value other than '0' turns on the memory log. A file called SrvMem<n>.xls is created in the BDN directory with the following information about each request: the time, the request, and the current amount of memory allocated by the server. toptier_sql_trace = 0 Any value other than '0' turns on the debug log. A file called DBG_StdErr_<n>.log is created in the BDN directory with the following information: Baan SQL Statements, SQL functions time stamps, and query cost information. 9-1

54 The BDNP.ini File baan_debug_level = 0 Any numeric values other than '0' turn on the debug log. See below for a list of valid values. A file called DBG_StdErr_<n>.log is created in the BDN directory. This turns on the Baan DEBUG_LEVEL option where you can use the following options: : show data input actions : show object information : show reference paths : debug functions : database server information : show delayed locks : show process actions : show database reference information : show database actions : debug file access : use debug version of the cpu : show whether domains, data definitions and objects are loaded from disk or shared memory : debug get.var and put.var functions : debug scheduler : debug pty's : show opened sequential files : debug TSS functions If you set the value to 'yes' the default debug level will be used. 9-2

55 The BDNP.ini File baan_sql_trace = 0 Any numeric value other than '0' will turn on the debug log. (See below for a list of valid values.) A file called DBG_StdErr_<n>.log will be created in the BDN directory. This turns on the Baan TT_SQL_TRACE option where you can use the following options: : Logs lexer information (a fly by of the tokens) : Logs parser information : (C) Logs entire internal query structure including its evaluation views : Logs debug information of view building process : (C+S) Logs expressions just before they are evaluated : (C) Show queries with their QID : Logs debug information on level-1 evaluation process : (C) Show query execution times : (C) Show calls of internal SQL functions : (C+S) Show query evaluation plan : (S) Show Query Evaluation Plan : (S) Show Full Table Scan (C)Client,(S)Server If you set the value to yes the default SQL trace will be used. 9-3

56 The BDNP.ini File [database settings] use_hints = 1 Defines the use of index hints for BDB. This option should be off for ORACLE level 2 where hints have no influence on the query engine. These are the available settings: 0: Hints are turned off. 1: (Default value) Hints enabled only for tables where there is a condition on a query variable or constant value. 2: Hints enabled for all tables if there is at least one table with a condition on a query variable or constant value 3: Hints enabled for all tables. NOTES: All other values map to the default (1). Hints are created only for Baan data tables. The conditions must be from the start of an index and on for a hint to be created. If there are different operators on different parts of the index, a hint might not be created. max_companies = 20 The maximum number of companies that will be used in a multi-company query. bdb_dll = Baan5DB.dll Indicates a Baan file containing the Baan database libraries. no_item_project_comb = 1 Sets the index definition for the Items table. If the index is only the item number, the system does not search for the project number during a drag operation. If the index is a combination of item number and project number (default index), then the system also looks for the project number in every drag operation involving the item number. If the index was defined to be the item/project combination, you must set the flag to off, or '0'. If the index was defined to be item number only, the flag becomes a true condition and must be set to '1'. When working with Baan V, the flag should always be set to '1'. 9-4

57 The BDNP.ini File query_max_records = Specifies the maximum limit for the number of records a single query can return; default 10,000. The next three entries apply to native connections or Baan connections and deal with runaway queries. The values are optional; those shown are the default values. allow_count = 1 The value 1 for this parameter enables a count of the total records retrieved by a query by means of clicking the Count link on the list form; default is 0 which disables this function. fetch_timeout = 10 If a query does not return a reply set within 10 seconds, it is stopped. desktop_bdb_dll = rpc_baandb.dll Enables a stop or timeout in desktop queries. server_bdb_dll = rpc_baandb.dll Enables a stop or timeout in Web queries when the connection to the database is a native connection. server_bdb_dll = Sockets_BaanDB.dll Enables a stop or timeout in Web queries on the Unix side TopTier BDB server. bdb_host = <Unix_server_name Unix_server_FQDN Unix_server_IP_address> Identifies the server machine on the Unix side. bdb_port = <first_unix_port> Identifies the Unix port which serves as the first gateway of communication between the BDN and the TopTierBDB servers. 9-5

58 The BDNP.ini File [environment] Any set of <variable>=<value> used here will be set as an environment variable in the application s process. Example 1: DBSLOG = This variable will tell the database driver to create a log file called dbs.log. The following values are available: : Data Dictionary info of tables within the driver : Query info (SQL-level1) : Row action info : Table action info : Transaction action info : Administration file info (SQL drivers) : DBMS SQL statements : General debug statements : Query processing info (for TT_SQL_TRACE info) : Data buffering info (communication) Example 2: ORA_MAX_ARRAY_FETCH = The Oracle7 Driver can use the Oracle array interface for array fetches and array inserts. With the array interface, communication between the Oracle7 Driver and the Oracle7 RDBMS is more efficient: multiple rows are fetched or inserted simultaneously. The environment variable ORA_INIT= enables the array interface. Note that the default ORA_INIT is ; therefore, enabling the array interface so as not to affect other behavior should be done with the following: ORA_INIT= When enabled, the array performs fetches and inserts on a maximum of five (5) rows. However, the maximum can be overruled with the environment variables ORA_MAX_ARRAY_FETCH and ORA_MAX_ARRAY_INSERT. For example, setting these values to 10 results in a maximum of 10 rows being fetched or inserted at a time. Array interfacing is especially useful when using SQL*Net to access a remote database, because the number of network round trips is reduced. 9-6

59 The BDNP.ini File [Baan Connection] Connection to the Baan server is defined during installation with the parameters below. Only the system administrator should change them. user = remote user name BSE = the home folder of BDN or the home folder of your local Baan installation. BSE_REM = the Baan Application Server Name [Extra Net Settings] SSL = 1 When the variable SSL is set to '1' the system is run in secure mode. The default setting is '0'. Please refer to the SSL Support chapter in the Baan Data Navigator Installation Guide for more information. web_server_location = When this variable is blank the Web server is located on the local machine. Otherwise a valid DNS is entered. [Reports] max_html_size = Sets the maximum size of the report preview file in bytes. The recommended default, based on limitations of Microsoft Internet Explorer, is , or 2 megabytes. [Memory Settings] no_mem_limit = 1 When a server has memory problems, such as a leak, setting a memory limit protects the machine. A '0' setting automatically shuts down the server if it reaches the limit. Server operations then switch to another server instance. 9-7

60 The BDNP.ini File [Excel Settings] excel_limit = 0 Sets the maximum limit on how many lines a user can export to an Excel file. This feature is meant to prevent users from overloading the system. The default setting is '0' and it places no limit. export_to_file = 1 Enables the export of data to file, for users of Internet Explorer 4 and above, in the event that Excel does not exist or if its version is prior to that of Office 97. The default setting is 0, which disables the export-to-file feature; a setting of 1 enables the feature. In order to enable this function, the domain where the BDN server is located must be defined as a trusted site; define this from the Tools > Internet Options menu in your browser. [Model Transport] interface_language = 2 Before model transporting Baan sessions with a custom forms that were created in a language other than English, you must change the interface language value to the one that represents the language in which the session forms were created. If you do not know the code for a particular language, follow this procedure: 1 Open Baan to display the Menu Browser dialog. 2 Browse to Baan IV Tools/User Management/General User Data/ Maintain User Data. 3 In the Maintain User Data dialog, click the arrow beside the Language code field to open the Display Languages dialog. 4 Scroll to find the language you need. The number preceding the language is its code. 9-8

61 10 Upgrading to BDN 2.6 The BDN 2.6 Upgrader automatically copies your BDN 2.1 or 2.5 environments to the new BDN 2.6 installation. The Upgrader thereby enables working with the latest BDN version without losing the environment created in the previous version. IMPORTANT: Implementing the BDN Upgrader If you plan to upgrade your BDN application, it is advisable to install BDN 2.6 with a clean repository. After BDN 2.6 is installed, you can activate the Upgrader for current older installations. Since the Upgrader copies files from the older version to the newer, the older version remains intact and useable. Before running the BDN Upgrader, make sure that the BDN servers of both environments are not running. To implement the BDN 2.6 Upgrader: 1 Access the BDN program group from the Windows Start menu and select BDN Upgrader. The Upgrader screen appears. 10-1

62 Upgrading to BDN Choose the version for upgrading by selecting the appropriate radio button. 3 Enter the full path to the upgrade target version, either by typing or browsing to the installation folder. 4 Click Go. A message appears informing you that the Upgrader is about to copy files. This may take a few minutes after which a progress bar appears indicating that the Upgrader is in the process of copying files. The Upgrader prompts you to click OK when it finishes. The upgrade process also creates a log file (BDNupgrade.log). The log records the files the upgrader was not able to copy. Additional Notes Upgrading from an older version brings all the toolbars, HTML form files, and relations to the new application. Any extraneous elements or those no longer desired must be removed manually from the new version. Upgrading HTMLs When upgrading from an older version, the HTML files from the older version are retained. Therefore the BDN 2.6 Export to Excel features, such as keeping the sort order while exporting, or other HTML dependent features, will not be available in the new version. If no specific work has been done on the old HTMLs, it is recommended to regenerate the HTMLs of these components using the Deployment environment. These changes may be performed globally, using the Model Transport, or per component, using the Component Editor. In any case, the generation of HTML files override the older versions. Consult your deployer or see the Deployment Guide. Adding the Web Query Interface Component To The Toolbar Since the Upgrader takes the old toolbar as is, another factor when upgrading BDN 2.1 is that you have add the Web Query Interface. To add the QI for all users: Log in as TTBaan and install component Then drag the component to the toolbar. This automatically adds the Web QI to the toolbars of all the users who have not yet created personalized toolbars. To add the QI for specific users: Log in as TTBaan and install component Then drag the component to the toolbar. 10-2

63 Upgrading to BDN 2.6 Restricting the use of the Web QI: If you want to restrict the use of the Web QI to certain users you can do one of the following: If the upgrade is from the BDN 2.1 version, add it only to specific users. You can restrict the access rights of specific users to the QI installer (BDNWebnavigator.exe) residing in the IIS root folder. With this method if a user tries to install the QI plug-in, a permission error is returned. 10-3

64 Upgrading to BDN

65 11 Licensing Baan Data Navigator 2.6 Baan Data Navigator 2.6 provides a 30-day trial period. Within 30 days of installing BDN version 2.6, you must register the software with Baan Company. Following the 30-day trial period, you will not be able to work with an unregistered version of BDN 2.6. Note that if you upgrade to BDN 2.6 from an earlier version of BDN or BDNP, you are immediately prompted to register the software. To register BDN 2.6: 1 From the BDN program group in the Windows Start menu, select Registration. TIP: 2 Go to the Web site. Click on Validation Forms to enter the Validation Web site. Click on Baan Data Navigator software and enter the key request code, along with any other required information. To use the key request code, use cut and paste to make sure you include all characters (including spaces). 3 In turn, Baan Validation will give you a code to activate the licensing mechanism. Enter this code in the editable field in the licensing dialog and click License. 4 When the confirmation code is displayed, click OK, and in the following dialog, click OK again to exit the registration program. 5 Restart the BDN Server and the BDN Desktop. 11-1