baan data navigator 2.6 administrator guide ivb, ivc.pdf · 2017-12-04 · about this document baan...

Baan IVb, IVc; BaanERP 5.0b, 5.0c

Baan Data Navigator 2.6Administrator Guide

A publication of:

Baan Development B.V.P.O.Box 1433770 AC BarneveldThe Netherlands

Printed in the Netherlands

© Baan Development B.V. 2001.All rights reserved.

The information in this documentis subject to change withoutnotice. No part of this documentmay be reproduced, stored ortransmitted in any form or by anymeans, electronic or mechanical,for any purpose, without theexpress written permission ofBaan Development B.V.

Baan Development B.V.assumes no liability for anydamages incurred, directly orindirectly, from any errors,omissions or discrepanciesbetween the software and theinformation contained in thisdocument.

TopTier Software Inc,HyperRelational,HyperRelational Navigation,HyperRelational NavigationProtocol, HRNP, Drag andRelate, Point of View Navigation,and TopTier are trademarks orregistered trademarks of TopTierSoftware Inc. in the UnitedStates and elsewhere in theworld.

Document Information

Code: U7408B USGroup: User DocumentationEdition: BDate: February, 2001

i

Baan Data Navigator 2.6 Administrator Guidei

1 Introduction 1-1How HyperRelational navigation works 1-2Navigation on the Web 1-2Logging on to the Web Client 1-3

2 Managing Users and Security 2-1User Types 2-1Finding Users 2-2Changing Passwords 2-3Importing Roles, Users and Security Settings 2-4Importing Users and Security Settings from Baan IV 2-4Importing Roles from BaanERP 2-5Creating a Super User 2-6Enabling Access to Multi-company Data 2-6

3 Periodically Updating the BDN Repository 3-1Database Updates 3-1Table Size 3-1Table Properties 3-2Table Indexes 3-2

4 Monitoring the BDN Server 4-1Activating the BDN Server 4-1Running the Server Monitor 4-3Controlling Servers from the Server Monitor 4-3Running Remote Servers 4-5Monitoring Server Status 4-6Server Options 4-6Defining Server Properties 4-7Scheduled BDN Server Shut Down 4-8Generating Detailed Performance Logs 4-9Memory 4-9Toptier_sql_trace 4-10Baan_debug_level 4-10Baan_sql_trace 4-10

Table of contents

Table of contents

Baan Data Navigator 2.6 Administrator Guideii

5 Managing Query Performance 5-1Building a Large Table Repository 5-1Setting Query Cost Preferences 5-2Additional Query Management Functions 5-4

6 Enabling Query Stop and Timeout 6-1Implementing Stop and Timeout Changes 6-1

7 Troubleshooting 7-1TT Analyzer Utility 7-1The BDN Server Does Not Respond 7-1BDB Errors 7-2BDB Error 850 7-2BDB Error 506 7-2Additional BDB Errors 7-2The Web Navigator ActiveX Control/Plug-in will Not Download 7-3First Installation 7-3Tables Cannot be Found 7-3

8 TopTier Analyzer 8-1About TopTier Analyzer 8-1Running the Utility 8-1Performing the Analysis 8-2Menu Usage 8-6

9 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] 9-8

10 Upgrading to BDN 2.6 10-1Implementing the BDN Upgrader 10-1Additional Notes 10-2

11 Licensing Baan Data Navigator 2.6 11-1

12 Index 12-1

Baan Data Navigator 2.6 Administrator Guideiii

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 coversperiodic maintenance tasks such as importing new roles or users, securityupdates, or other database modifications from Baan. It provides troubleshootingfor common problems, and explains how to monitor and improve systemperformance.

For details regarding initial setup and configuration requirements see the BaanData 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 yoursystem should be fully operational once you have completed installation. If youare using extensions that are significantly different, or if you have made changesto central tables such as customers, suppliers, items, sales orders, or purchaseorders, you can customize the standard component set using the administrativetools 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 intothe BDN environment, following changes to the Baan database.

� Chapter 4 explains how to monitor the BDN server and to increase servercapacity.

� Chapter 5 explains how to monitor query performance and to limit access toresource-intensive queries.

� Chapter 6 explains the implementation of the query timeout and stopfunctions so that they work properly on both NT and Unix servers.

� Chapter 7 provides advice about troubleshooting problems that may ariseduring system administration.

About this document

About this document

Baan Data Navigator 2.6 Administrator Guideiv

� Chapter 8 describes the TopTier Analyzer utility and its role in systemadministration and/or troubleshooting activities.

� Chapter 9 provides a detailed description of the BDNP.ini file, which enablesgenerating 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.

Baan Data Navigator 2.6 Administrator Guide1-1

BDN HyperRelational� technology provides a new, easy way to work withBaan systems. An innovative Drag and Relate� interface allows bothexperienced Baan users and those with no database skills, to access and correlateinformation from within Baan and from diverse data sources throughout yourorganization.

Unlike conventional hypertext front-ends, BDN HyperRelational� navigationfeatures:

� Logical links to dynamic database information, as opposed to static physicallinks or hard-coded queries.

� Many-to-many relationships for referencing multiple database tables thathave no predefined relationship between them.

� User-controlled navigation paths, rather than a predefined set of links. WithHyperRelational navigation, users create their own queries using a simpledrag-and-relate interface.

BDN 2.6 supports Baan IVb, Baan IVc, BaanERP 5.0b, and BaanERP 5.0cstandard versions. The BDN security mechanism is fully integrated with the onein the Baan environment. The BDN product suite includes a run-timeenvironment with predefined HyperRelational components based on the mostcommonly used Baan sessions. By using the BDN Deployment Environment,you can enhance and extend the package.

1 Introduction

Introduction


How HyperRelational navigation worksYou can perform HyperRelational navigation from a Web browser.

Navigation on the WebHyperRelational navigation from a Web browser involves your Baan database, astandard Web server, and the BDN server.

BAANdatabase

BDNrepository

BDN serverWeb (HTTP)server

BDN Web client

Users work in a standard Web browser with BDN�s WebNavigator. The WebNavigator is a plug-in for Netscape browsers or an ActiveX control for MicrosoftInternet Explorer. The Web Navigator sends requests for information to the BDNserver. See the BAAN Data Navigator Installation Guide for instructions on howto install the Web Navigator.

The BDN server receives requests from the browser, populates HTML templateswith information from the BDN repository and the Baan database, and then sendsthe information back to the Web client. A standard Web server is used to handleimages and the home page of the BDN application.

The BDN repository contains information about the database model and therelationships between data that enables HyperRelational navigation. It is includedas part of the server installation.

Introduction


Logging on to the Web ClientThe 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 MicrosoftInternet Explorer.

3 Open the main page of the application by typing the following URL addressin the field at the top of the Web browser, and pressing enter:

http://host_name/Shell.html

For example, if the Web server is located on a computer that is identified asMartin_O on the network, type the following address:

http://Martin_O/Shell.html

This formula is correct when the Shell.html file is located directly inside theWeb server root. If the Shell.html file is located in a subfolder of the Webserver root, then the address should include the full path to the Shell.html filefrom within the Web server root.

http://Martin_O/BDN_3/Shell.html

When you are prompted, enter your user name and password. The main pageof the DataNavigator appears, with a toolbar displayed on the left side.

If your application supports SSL, the URL for accessing BDN in the SSLconfiguration begins with https rather than http; the added s stands forsecure. In addition, it points to ssl_shell.html, in the same location.

For example, if the URL for the normal configuration is�

http://alice.toptier.com/bdn/shell.html

then the URL for the SSL configuration is:

https://alice.toptier.com/bdn/ssl_shell.html

http://host_name/Shell.html

http://martin_o/Shell.html

http://martin_o/BDN_3/Shell.html

http://alice.toptier.com/bdn/shell.html

Introduction


Introducing data navigationBDN data navigation consists of dragging data records from one session anddropping them onto another to retrieve related information. This technology iscalled Drag and Relate. Users decide what information they want and determinea navigational path on the fly, without relying on predefined, hard-coded queriesdefined by the system author.

This section illustrates data navigation with BDN.

The screen below is the Find form displayed when the Customers icon is double-clicked. 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 inthe database. Click the Next and Previous buttons to view all the records.

Introduction


Each link in the screen is HyperRelational and can be clicked or dragged ontoanother component. For example, dragging customer number 9001 onto SalesOrders displays a list of all of that customer's orders.

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 thisicon onto the Sales Order Lines component displays the details of all three salesorders.

Note that below the form is a description of the navigation path used to generatethis particular list of data records. In this example, customer 9001 was draggedonto the Sales Orders components, then all the Sales Orders records in the listwere dragged onto the Sales Order Lines component. In other words, the listdisplays the Sales Order lines records for the orders placed by customer 9001.

Click the asterisk (*) in the View field (above form) to display the details of anorder line in a single-occurrence form.

Introduction


To view the invoice associated with this order, drag the orange or purple iconfrom the top of the form to the Invoices icon. Or, to view the delivery status, dragone of the icons onto Delivery. With BDN, you can continue to drag and relatedata until you find the data you need.

For more information about data navigation, see the Baan Data Navigator WebNavigation Guide.

Introduction



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 Baansystem and imported into BDN. User passwords must be defined separately inboth 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 forBaanERP.

User TypesThe BDN administrator has three user logons available:

� The user Setup has access to all BDN administration tools. To perform allroutine administration, log on as Setup. The default password is Setup.

� The user toptier has access to all BDN deployment tools, including theModel Transporter, the Component Editor, and Autocomplete Relations.This user must also be defined on the Baan system. The default password istoptier.

� The user TTPassword allows the administrator or deployer to log on as anynet user by entering a universal password. This user is not imported fromBaan, but is a Super User created by the administrator or deployer. Thedefault password is TTPassword.

The logon fields are case-sensitive. It is recommended that you change thepassword to improve security (see below).

� All users imported from Baan are of TTBaan type. Users with administratorprivileges within the Baan system can change user passwords within BDN,but will not have access to any other BDN administration tools unless theylog on as user Setup or user toptier. This guide indicates when it is necessaryto log on as Setup, and when as toptier.

2 Managing Users and Security

NOTE:

Managing Users and Security


Finding UsersThe 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 thedetails 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.



Changing PasswordsWhen importing users from Baan, BDN assigns the user name as the initialpassword, since the actual passwords cannot be obtained directly from Baan. Toimprove security, it is recommended to redefine user passwords.

You change passwords with the User tool. Users can change their ownpasswords. 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 administratorprivileges, 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 clickChange.



Importing Roles, Users and Security SettingsDuring the setup stage following installation, you use the Security Update tool toimport the role profiles from BaanERP, or the current user and security profilesfrom Baan IVb and IVc. As new roles or users are added to the system, youimport them into BDN. You also import updates to role and user securityprofiles.

Importing Users and Security Settings from Baan IV1 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, bysession, by table, or by table data. Select the options that are appropriate toyour Baan implementation.

5 Click Import. A progress bar at the bottom of the BDN window reports onthe import process. To import all the security data may take some time.

6 When the import process is complete, click Close.



Importing Roles from BaanERP1 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, bysession, by table, or by table data. In the User/Security Transporter dialogbox, 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 ExclusiveImport; however, choosing Import enables users who are logged on to thesystem to continue working during the security update.

Do not use the Exclusive Import option unless you are sure that no user islogged on.

When the import process begins, a progress bar appears at the bottom of theBDN window. To import all security data may take some time.

5 When the import process is complete, click Close.



Creating a Super UserThe system administrator or deployer must be able to view data and systemlayout from any particular user's perspective. Therefore, you must define a SuperUser with a universal password. For example, if a user forgets a password or hasproblems with the client machine, the administrator can log on as that user, usingthe 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 dialogbox.

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 hasbeen 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 allowsthe logon.

Enabling Access to Multi-company DataThe Baan security mechanism defines which companies each user can access. Ifyou are working with BaanERP, the Multi Company Settings component letsyou enable users having access to more than one company to view data fromseveral companies at once.

Initially, you use the Multi Company Settings component to import thecompany access definitions of all Baan users. Following this setup step, usersnavigating in the Use Multi Company mode will see data related to all of thecompanies to which they have access in component forms that display multiplerecords.

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 MultiCompany mode.



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 thesecompanies. When the user navigates in the Use Multi Company mode, onlydata from the three selected companies is displayed in component forms thatdisplay 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; alist 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 useris allowed to access.

5 In the Allowed field of each company in the list, select Yes or No from thepopup menu to include or remove the company from the list of companieswhose data is displayed in component forms in the Use Multi Companymode.

6 Click Save.


The BDN repository contains session data, including information about forms,fields, and relations imported from the Baan Data Dictionary into the BDNsystem. By default, the information in the BDN repository corresponds to thestandard Baan version. During installation, use the BDN tools to updateautomatically the BDN repository to reflect the local Baan version.

Following the initial installation and setup, you periodically update the BDNrepository to reflect additional modifications to the Baan system. You use theDatabase Updates tool to import information about table size, indexes, andproperties 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 UpdatesThe Database Updates tool imports information about column attributes, tablesizes, and table indexes from the Baan system into the BDN repository.Following a Baan system update, you use the Database Updates tool to importthe current Size, Index, and Property data into BDN. If the database changes alsoaffect component forms, you can use the Model Transporter to regeneratecomponents, as described in the Baan Data Navigator Deployer's Guide.

Table SizeThe Update Table Size command imports information about the size of thetables in the Baan database. It ensures accurate performance monitoring duringrun 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, andclick Size.

4 The import process begins and a progress bar is displayed at the bottom of theBDN window.

3 Periodically Updating the BDNRepository

Periodically Updating the BDN Repository


Table PropertiesThe Update Table Properties command imports information from your Baandatabase regarding alignment of fields such as items or customers, as well asseveral other configurable parameters.

To update property attributes:


2 In the Utilities toolbar, double-click the Database Updates icon.

3 In the Database Updates dialog box, select the tables that have beenmodified, and click Properties.


Table IndexesThe Update Table Indexes command imports information about the Baandatabase indexes.

To update table indexes:


2 In the Utilities toolbar, double-click the Database Updates icon.

3 In the Database Updates dialog, select the tables that have changed, andclick Index.


5 After the import process is complete, click Close.


The BDN server is responsible for all communication between the Web browserand the database. The browser sends requests to the BDN server, whichpopulates the HTML templates with the requested data and sends HTML filesback to the browser.

The number of users and requests, database speed, the complexity of queries andvarious other factors all affect the performance of the system. You can run morethan one BDN server when warranted by the load on your application. A singleserver monitor lets you control and view the status of all running BDN servers.

BDN supports Secure Sockets Layer (SSL) in Microsoft Internet Explorer. TheSecure Sockets Layer protects transmissions in a network by guaranteeing anauthenticated connection between server and client and enabling encryptedcommunication between them. For complete information about SSL support inBDN applications, see Baan Data Navigator Installation Guide.

Activating the BDN ServerTo activate the BDN server:

From the Windows Start menu, open the BDN program group and select theBDN Server Monitor. A prompt appears indicating that the service is not activeand offering the option to start it.

4 Monitoring the BDN Server

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, anddouble-click Services.

2 In the Services dialog box, scroll to select your server. The server namebegins with TopTier Server and includes the BDN project name.

3 Click Startup to display the Service dialog. In Startup Type, it is recommended thatyou change the startup mode to Automatic so that the server starts automatically eachtime the system starts.

4 Press Start to run the server.

If you make any changes in the Startup mode while the server is running, stopand then restart the server.

NOTE:



Running the Server MonitorTo run the server monitor, choose BDN Server Monitor from the MicrosoftWindows Start > Programs > BDN menu. If you attempt to run the monitorbefore 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 remotemachines, as described later in this chapter.

Controlling Servers from the Server MonitorThe server monitor is a multiplexer program that can run and monitor multipleTopTier servers.

Server monitor

BDN server BDN server BDN server



The server monitor functions as a load distributor that distributes requests amongthe servers. It also monitors the servers, so that if one fails, it is automatically re-invoked.

By using the server monitor you can add and remove servers, including remoteservers. 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 sentthrough the monitor.

To add a server:

1 Click the Change Capacity button in the Server Monitor window to displaythe Set Local Capacity dialog box.

2 In the Set Local Capacity dialog box, enter the number of server instancesyou want to run on this machine.

3 Click OK.



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 LocalCapacity dialog box.

Running Remote ServersDuring periods of intense user traffic, you can run additional BDN servers onremote host machines. These servers have their own local capacity; however, onecentral server monitor acts as the entry point for the entire application,channeling all requests to server instances on the local machine and to servers onremote machines.

When connecting to a remote server, the central server automatically detects theremote port number and capacity. The central server also detects any change inthe 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 FullyQualified Domain Name (e.g. joe_nt.company.com); however, you can alsouse the IP address (e.g. 199.273.123.71) or the host name (e.g. joe_NT).

3 From the list, select the service that you want to run and click OK.



Monitoring Server StatusThe status area below the Active Server Instances list displays informationabout the number and frequency of hits, and of heavy hits. A heavy hit is arequest that took a relatively long time to carry out. Use the information aboutheavy hits to analyze the performance of your application and to adjust thenumber of servers accordingly.

The server log lists all events associated with the servers currently running fromthe server monitor, including errors, add and remove, hits, and heavy hits. Inaddition to the information provided in the online monitor, the log indicates therequest that resulted in a heavy hit. With this information, you can determine ifthere are performance problems with particular queries.

To view the BDN server log, click the View Log button.

Server OptionsClick the Options button to:

� Set the server monitor�s port. The default is 9999. Modify this port if anotherdevice already uses this port number.

� Set the length of a heavy hit.

� Enable the log file.



Defining Server PropertiesTo view or modify server properties, in the BDN Server Monitor clickProperties, or choose BDN Server Properties from theStart > Programs > BDN menu. Note that the properties apply to all BDNservers 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 usedin the application, such as images, movies, and so on.

Media Path Alias: The alias for the media path. The value must beTopTierMedia.

Plug in location: The name of the file containing the updated plug-in todownload.

Central Server Address: The IP address of the central 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 beused in the HTML files. You may have to change the address type in order tomake the server accessible to all machines.

IP Address:199.205.156.78:9999/BIOG/Person_ID/5Fully Qualified Domain Name: joe.company.com:9999/BIOG/Person_ID/5Host 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 guestsoption is implemented.

Scheduled BDN Server Shut DownMany BDN installations have their Baan server shut down periodically, causinglost connectivity to the BDN server. The BDN server is also used for operationsother than connection to Baan. In order to avoid the inconvenience of theseshutdowns, you need to configure an automatic shutdown of the BDN server thatcorresponds to the times of the Baan server shutdown. To schedule theseshutdowns, use the OS net start option for stopping and restarting servicesprovided 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"



Generating Detailed Performance LogsBDN enables generating detailed log files that can be used for diagnosticpurposes. These files are in addition to the log file maintained by the BDNServer 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, andbaan_sql_trace.

When you activate the memory option, a log file called SrvMemx.xls is createdin 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 filecalled DBG_StdErr_x.log in the BDN application folder, where x is the log fileinstance.

MemoryWhile the Memory log option is active, memory usage data is logged for eachhit. You can use this log to locate memory leaks and evaluate systemperformance. By default this log is off. To turn it on, change the memory value to1 (1= ON, 0= OFF), and restart the BDN server. SrvMemx.xls is created in theBDN application folder. This file is formatted for viewing in an Excelspreadsheet.



Toptier_sql_traceToptier_sql_trace logs all transactions between the BDN server and the BDBlibrary. By default this log option is off. To turn it on, change thetoptier_sql_trace value to 1 (1= ON, 0= OFF), and restart the BDN server. Loginformation is written to DBG_StdErr_x.log.

Baan_debug_levelBaan_debug_level logs all activity in the BDB library. To activate this logoption, change the baan_debug_level value to YES, which defines the defaultlog 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_traceBaan_sql_trace logs all transactions between the BDB library and the Baanserver. To activate this log, change the baan_sql_trace value to YES, whichdefines 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.


BDN enables users to navigate throughout the entire Baan database, evenbetween tables that have no indexes. As a result, performance issues can arisewhile you navigate through large tables. The database update functions and theQuery Cost tool can help you monitor, and if necessary, limit access to resource-intensive queries.

Building a Large Table RepositoryThe Update Table Size function in the Database Updates dialog box importsinformation about large tables in the Baan database, and stores it in the BDNrepository. This information includes the number of records in each table, and isused 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. Ifthere are significant changes to the sizes of tables in the database, you must run itagain, as described in Chapter 3, Periodically Updating the BDN Repository.

5 Managing Query Performance

Managing Query Performance


Setting Query Cost PreferencesYou can activate query cost monitoring and set preferences that affect all BDNusers. There are two types of preferences that you can set:

�� Query Cost Limit: The cost of a query is measured by the number of recordsthat have to be scanned in order to provide an answer to the query. The actualexecution time varies, depending on the performance of the Baan server. TheQuery Cost Limit is an indicator of relative length, and can be fine-tunedbased on experience.

When a user generates a query through drag-and-relate operations, if thenumber of records that needs to be scanned exceeds the defined Query CostLimit, a warning appears indicating that the query may take a long time toprocess. 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 exceedsthe upper limit that you set, the user will not be able to proceed. Similarly, ifthe estimated query cost is less than the warning level, no warning message isdisplayed.

�� Efficient Drags Only: Enables drag and relate operations only on fields thatare indexes, primary keys, or foreign keys. This limits HyperRelationalnavigation, but eliminates performance problems. You can set a lower limit,so that drag and relate operations may be permitted on very small tables, evenwhen 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.



4 After you make modifications, test the system to make sure the results areappropriate.

The following settings are available:

�� Allow only efficient drags: Enables HyperRelational navigation only onfields that are indexes or keys. The default value, N, does not activate thisoption. If you change the value to Y, you must also define the Allow drags ifless than X records parameter.

�� Allow drag if less than X records: If the Allow only efficient drags option isactivated, this option will permit drag and relate operations on very smalltables, even when the fields are not indexed. The default value is 10,000records.

�� Maximum query cost allowed in rows: Indicates the upper limit for querycost evaluation. If the estimated cost exceeds this number (i.e. if the numberof records that have to be scanned to provide an answer to the query exceedsthis number), the user will not be allowed to proceed. The default value is500,000 records. You can change the upper limit for individual users.

�� Default lower limit in rows: Indicates the warning level for query costevaluation. If the estimated cost is less than this number, the user will not bewarned 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 valueto 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.



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

5 Click the Update button.

Additional Query Management FunctionsIn addition to the update database and query cost management functions, theadministrator can also limit the maximum number of records returned by anysingle 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 thecurrent query.

The Count function can be time-consuming if there are many records to count, orif the scanning of the records is slowed down for any reason. However, since thisfunction 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 bythe administrator. It is, therefore, advisable to use the Query Cost tool and toenable the Stop and Timeout functions. For a detailed discussion of thesefunctions, see the sections Setting Query Cost Preferences above, and theEnabling Query Stop and Timeout chapter.

To limit the maximum number of records retrieved by a single query, see thedatabase settings section of The BDNP.ini File chapter.


After the launching of a long query from a BDN client browser, a number ofactions can cause the interruption of that query before completion. For example,activating another component, or clicking the Back or Stop buttons cancel aquery in process; the elapse of an administrative time allowance per fetch alsostops a query in process. The BDN client server works in conjunction with theTopTier BDB server on a remote Unix machine. A Query launched from BDNactivates the BDB server in a data retrieval process. The administrator musttherefore implement adjustments after the BDN installation to ensure that thecancellation of a query process stops the entire query process, not only on theclient side, and enables the system to restart and be ready to handle a new query.

Implementing Stop and Timeout ChangesThe BDN server runs on NT opposite the TopTier BDB server which runs onUnix. The TopTier BDB server uses a database driver to access and retrieveactual data from the Baan database. If this database driver is located on the NTmachine where the BDN server is running, then the connection between BDNand the Baan database is a native connection. Where there is a native connectionthe administrator need only make definition changes on the NT side. The moreprobable scenario, however, is one without a native connection so that both theNT and the Unix administrators must make changes and additions to databasesettings and environment variables.

6 Enabling Query Stop and Timeout

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, addthe line Accept Stop=1.

2 In the database settings section of the BDNP.ini file, located in theinstallation 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 specifiednumber seconds.

server_bdb_dll = Sockets_BaanDB.dll

This entry indicates the use of a Unix process to enable the cancellation ofqueries.

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.

A native connection does not preclude the use of theSockets_BaanDB.dll, but the use of this .dll then requires the samechanges 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 onUnix.

NOTE:



bdb_port = <first_Unix_port>

The number indicating the Unix port must be identical to that entered for theTopTier BDB server Unix process. The default port number for the Unixside is 21500.

To implement the Unix changes:

1 Set the correct BSE and USER environment variables for the user running theprocess. Make sure the USER is identical to its respective setting in theBDNP.ini file on the NT side.

2 Run the ps -ef command and verify that the output line returns the entirecommand line, including the command parameters, that the PID columnappears 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 largelyavailable. It is the first gateway of communication between the BDN andUnix servers.

The port number is an optional parameter of the command line that executesthe running of the TopTier BDB server: TopTierBdbServer 23600 &,where 23600 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 whenthe BDN server is running.


This chapter discusses some problems or questions that may arise whileadministering the application.

TT Analyzer UtilityBDN includes TopTier Analyzer, a utility that is very useful for troubleshooting.It checks the BDN installation on your computer and provides additionalinformation 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. SeeTopTier Analyzer for complete information about this utility.

The BDN Server Does Not RespondIf 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 4.072 or higher,or Netscape Navigator version 4.0 or higher.

� Make sure you are typing the correct URL. See the Baan Data NavigatorInstallation Guide for information about logging on when the system has SSLsupport.

� Make sure your plug-in or ActiveX control is installed and up to date (if youare dealing with a system upgrade).

7 Troubleshooting

Troubleshooting


BDB ErrorsDuring run time, you may receive one of the following BDB error messages fromthe Baan server:

BDB Error 850Error 850 means there are no more user connections available for the BDNclient.

When the Baan server resides on a Windows NT server machine running aMicrosoft SQL server, a pre-set parameter in the SQL server determines thenumber of allowed user connections. You can check the number of userconnections available to your Baan server in the Microsoft SQL EnterpriseManager. For more information, refer to the Microsoft SQL Serverdocumentation.

Refer to your database administrator about increasing the number of SQL userconnections.

BDB Error 506The user logon is related to company 000 (for example, the user toptier), whichpermits no access to database tables.

Make sure you log on as a standard Baan user.

Additional BDB ErrorsThis list describes the BDB errors relevant to the Baan Data Navigator Suite. Fora complete list of all BDB errors, refer to the Baan documentation.

107 � Record is locked111 � No record is found113 � Table is locked116 � Cannot allocate memory. Out of memory142 � Some administration process is running202 � Database is locked208 � Permission denied506 � Table does not exist508 � Not logged on to a database511 � Version of client versus server not correct514 � Security error601 � Reference table is locked607 � Reference table is not found

Troubleshooting


The Web Navigator ActiveX Control/Plug-inwill Not DownloadThis section describes possible problems downloading the Web Navigator client.

First InstallationIf you cannot download the client ActiveX control/plug-in, check the propertysettings 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 Consolefrom Windows.

2 In the Console Root, under Internet Information Server, expand the folderrepresenting the IIS server machine, and select the BDN Web server rootdirectory.

3 From the Action menu, choose Properties, and in the Directory tab makesure under Access Permissions, Read is selected, but that under Permissions,Execute is not.

Tables Cannot be FoundFollowing installation, if you are unable to successfully navigate, either receivingmessages that the user table cannot be found, or failing to locate tables that youknow 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 thefile rbaan in the folder lib/user.

Troubleshooting



TopTier Analyzer is a utility designed to check your BDN installation. Ingeneral, it displays the attributes of the products comprising BDN, checks thedatabase connections, retrieves information about the computer on which theproduct suite is running, and checks the product files.

About TopTier AnalyzerThis utility is useful for troubleshooting purposes and for obtaining additionalinformation about the required software and hardware. The analysis is dividedinto sections, depending upon what is being checked. After testing thecomponents comprising each section, TTAnalyzer reports the results, includingerrors and inconsistencies.

Running the UtilityTopTier Analyzer is located in the Utilities\TTANALYZER folder of yourBDN application directory. Running the TTAnalyzer.exe file displays the generalsettings 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, 2.6.0.3

� The Datafile for each product; for example, the data folder of the BDNdesktop: 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 afterclearing ODBC settings, returns an error message.

8 TopTier Analyzer

NOTE:

NOTE:

TopTier Analyzer


Performing the AnalysisTo begin the analysis, select Start from the toolbar Tests menu. The Analyzerretrieves 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 Explorerfrom 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 forNETSCAPE.EXE and IEXPLORE.EXE, and shows the paths of all thebrowsers that were found. To skip this test, click 'S'.

� TopTier ActiveX path � Looks for the key of TopTier ActiveX in the registryand shows the path of the ActiveX if one is found. For example:

C:\WINNT\TopTierWebNav\WebNavigator.ocx

TopTier Analyzer


� TopTier Query Editor ActiveX path � Looks for the key of TopTier QueryEditor ActiveX in the registry and shows the path of the ActiveX if one isfound. For example:

C:\WINNT\TopTierComponents\TTQI.ocx

� TopTier Objects ActiveX path � Looks for the key of TopTier ObjectsActiveX in the registry and shows the path of the ActiveX if one is found. Forexample:

C:\WINNT\TopTierComponents\TTObjectsCtrl.ocx

� TopTier OLE-DB Provider path � Looks for the key of TopTier OLE-DBProvider in the registry and shows the path of the .DLL if one is found. Forexample:

C:\WINNT\system32\TTOleDB.dll

� TopTier DE OLE-DB Provider path � Looks for the key of TopTierdeployment environment OLE-DB Provider in the registry and shows thepath 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 theregistry and shows the path of the .DLL if one is found. For example:

C:\WINNT\TopTierWebNav\HRNPAPP.dll

Network� 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

The Analyzer retrieves the connection strings from ODBCSettings.prm and triesto connect to the database, using those strings. If the connection attempt fails, anODBC 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.

NOTE:

TopTier Analyzer


Example: BDN Desktop

� Repository � connection string:DRIVER=Microsoft Access Driver (*.mdb);DBQ=%DATA_FILE_DIR%TopTierRep.mdbConnected successfully.

Server Properties

TTAnalyzer retrieves the following information about the TopTier server and theTopTier 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 awarning 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 awarning 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 RunningRunningPaused

� Startup - Specifies when to start the service; can be one of the following:AutomaticManualDisabled

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

TopTier Analyzer


Application File Check

The utility makes a list of all the files that currently exist in the application folderand compares it to a list of files that describes the original files. Once it verifiesthat 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 problemswere found, the message reads: Completed successfully. If there areinconsistencies, it lists them, with an explanation.

Any additional files contained in the application, such as those that are installedafter performing Model Transporting, are not checked.

Menu UsageThe output of the analysis is displayed in the TopTier Analyzer window. Youcan:

� Print the analysis.

� Send the analysis as e-mail.

� Save the analysis by choosing the appropriate command from the File menu.

NOTE:


This chapter describes the BDNP.ini file in detail. BDNP.ini is located in theBDN installation Datafile folder.

[logging]BDNP.ini provides four different log options that enable generating detailed logfiles. These log files can be used for diagnostic purposes: memory,toptier_sql_trace, baan_debug_level, and baan_sql_trace.

memory = 0Any value other than '0' turns on the memory log. A file called SrvMem<n>.xlsis created in the BDN directory with the following information about eachrequest: the time, the request, and the current amount of memory allocated by theserver.

toptier_sql_trace = 0Any value other than '0' turns on the debug log. A file calledDBG_StdErr_<n>.log is created in the BDN directory with the followinginformation: Baan SQL Statements, SQL functions time stamps, and query costinformation.

9 The BDNP.ini File

The BDNP.ini File


baan_debug_level = 0Any numeric values other than '0' turn on the debug log. See below for a list ofvalid 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 followingoptions:

0000010: show data input actions

0000020: show object information

0000040: show reference paths

0000200: debug functions

0000400: database server information

0001000: show delayed locks

0002000: show process actions

0004000: show database reference information

0010000: show database actions

0020000: debug file access

0040000: use debug version of the cpu

0100000: show whether domains, data definitions and objects

are loaded from disk or shared memory

0200000: debug get.var and put.var functions

0400000: debug scheduler

1000000: debug pty's

2000000: show opened sequential files

4000000: debug TSS functions

If you set the value to 'yes' the default debug level 2000000 will be used.

The BDNP.ini File


baan_sql_trace = 0Any numeric value other than '0' will turn on the debug log. (See below for a listof valid values.) A file called DBG_StdErr_<n>.log will be created in the BDNdirectory. This turns on the Baan TT_SQL_TRACE option where you can usethe following options:

000001: Logs lexer information (a fly by of the tokens)

000002: Logs parser information

000004: (C) Logs entire internal query structure including

its evaluation views

000010: Logs debug information of view building process

000020: (C+S) Logs expressions just before they are evaluated

000040: (C) Show queries with their QID

000100: Logs debug information on level-1 evaluation

process

000200: (C) Show query execution times

002000: (C) Show calls of internal SQL functions

004000: (C+S) Show query evaluation plan

010000: (S) Show Query Evaluation Plan

020000: (S) Show Full Table Scan

(C)Client,(S)Server

If you set the value to �yes� the default SQL trace 000204 will be used.

The BDNP.ini File


[database settings]use_hints = 1

Defines the use of index hints for BDB. This option should be off forORACLE 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.

� 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 becreated.

� If there are different operators on different parts of the index, a hint might notbe 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 theindex is a combination of item number and project number (default index), thenthe system also looks for the project number in every drag operation involvingthe item number.

If the index was defined to be the item/project combination, you must set the flagto off, or '0'. If the index was defined to be item number only, the flag becomes atrue condition and must be set to '1'.

When working with Baan V, the flag should always be set to '1'.

NOTES:

The BDNP.ini File


query_max_records = 10000

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 dealwith runaway queries. The values are optional; those shown are the defaultvalues.

allow_count = 1

The value �1� for this parameter enables a count of the total records retrieved bya 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 isa 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 communicationbetween the BDN and the TopTierBDB servers.

The BDNP.ini File


[environment]Any set of <variable>=<value> used here will be set as an environment variablein the application�s process.

Example 1: DBSLOG = �This variable will tell the database driver to create a log file called dbs.log. Thefollowing values are available:

0000001: Data Dictionary info of tables within the driver

0000002: Query info (SQL-level1)

0000010: Row action info

0000020: Table action info

0000040: Transaction action info

0000200: Administration file info (SQL drivers)

0000400: DBMS SQL statements

0001000: General debug statements

0002000: Query processing info (for TT_SQL_TRACE info)

0004000: Data buffering info (communication)

Example 2: ORA_MAX_ARRAY_FETCH = �The Oracle7 Driver can use the Oracle array interface for array fetches and arrayinserts. With the array interface, communication between the Oracle7 Driver andthe Oracle7 RDBMS is more efficient: multiple rows are fetched or insertedsimultaneously. The environment variable ORA_INIT=0100000 enables thearray interface.

Note that the default ORA_INIT is 011000; therefore, enabling the arrayinterface so as not to affect other behavior should be done with the following:ORA_INIT=0111000.

When enabled, the array performs fetches and inserts on a maximum of five (5)rows. However, the maximum can be overruled with the environment variablesORA_MAX_ARRAY_FETCH and ORA_MAX_ARRAY_INSERT. Forexample, setting these values to 10 results in a maximum of 10 rows beingfetched or inserted at a time.

Array interfacing is especially useful when using SQL*Net to access a remotedatabase, because the number of network round trips is reduced.

The BDNP.ini File


[Baan Connection]Connection to the Baan server is defined during installation with the parametersbelow. 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 defaultsetting is '0'. Please refer to the SSL Support chapter in the Baan Data NavigatorInstallation 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 = 2000000

Sets the maximum size of the report preview file in bytes. The recommendeddefault, based on limitations of Microsoft Internet Explorer, is 2000000, or 2megabytes.

[Memory Settings]no_mem_limit = 1

When a server has memory problems, such as a leak, setting a memory limitprotects the machine. A '0' setting automatically shuts down the server if itreaches the limit. Server operations then switch to another server instance.

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 defaultsetting 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, inthe 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 locatedmust be defined as a trusted site; define this from the Tools > Internet Optionsmenu in your browser.

[Model Transport]interface_language = 2

Before model transporting Baan sessions with a custom forms that were createdin a language other than English, you must change the interface language valueto 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 codefield to open the Display Languages dialog.

4 Scroll to find the language you need. The number preceding the language isits code.


The BDN 2.6 Upgrader automatically copies your BDN 2.1 or 2.5 environmentsto the new BDN 2.6 installation. The Upgrader thereby enables working with thelatest BDN version without losing the environment created in the previousversion.

Implementing the BDN UpgraderIf you plan to upgrade your BDN application, it is advisable to install BDN 2.6with a clean repository. After BDN 2.6 is installed, you can activate theUpgrader for current older installations. Since the Upgrader copies files from theolder version to the newer, the older version remains intact and useable.

Before running the BDN Upgrader, make sure that the BDN servers of bothenvironments are not running.

To implement the BDN 2.6 Upgrader:

1 Access the BDN program group from the Windows Start menu and selectBDN Upgrader. The Upgrader screen appears.

10 Upgrading to BDN 2.6

IMPORTANT:

Upgrading to BDN 2.6


2 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 browsingto the installation folder.

4 Click Go. A message appears informing you that the Upgrader is about tocopy files.

This may take a few minutes after which a progress bar appears indicatingthat the Upgrader is in the process of copying files. The Upgrader promptsyou to click OK when it finishes.

The upgrade process also creates a log file (BDNupgrade.log). The log recordsthe files the upgrader was not able to copy.

Additional NotesUpgrading from an older version brings all the toolbars, HTML form files, andrelations to the new application. Any extraneous elements or those no longerdesired must be removed manually from the new version.

Upgrading HTMLs

When upgrading from an older version, the HTML files from the older versionare retained. Therefore the BDN 2.6 Export to Excel features, such as keepingthe sort order while exporting, or other HTML dependent features, will not beavailable in the new version. If no specific work has been done on the oldHTMLs, it is recommended to regenerate the HTMLs of these components usingthe Deployment environment. These changes may be performed globally, usingthe Model Transport, or per component, using the Component Editor. In anycase, the generation of HTML files override the older versions. Consult yourdeployer 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 upgradingBDN 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 24019. Then drag the component to thetoolbar. This automatically adds the Web QI to the toolbars of all the users whohave not yet created personalized toolbars.

To add the QI for specific users:

Log in as TTBaan and install component 24019. Then drag the component to thetoolbar.



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 ofthe 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 auser tries to install the QI plug-in, a permission error is returned.


Baan Data Navigator 2.6 provides a 30-day trial period. Within 30 days ofinstalling 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 anunregistered version of BDN 2.6. Note that if you upgrade to BDN 2.6 from anearlier version of BDN or BDNP, you are immediately prompted to register thesoftware.

To register BDN 2.6:

1 From the BDN program group in the Windows Start menu, selectRegistration.

2 Go to the www.support.baan.com Web site. Click on Validation Forms toenter the Validation Web site. Click on Baan Data Navigator software andenter 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 allcharacters (including spaces).

3 In turn, Baan Validation will give you a code to activate the licensingmechanism. Enter this code in the editable field in the licensing dialog andclick License.

4 When the confirmation code is displayed, click OK, and in the followingdialog, click OK again to exit the registration program.

5 Restart the BDN Server and the BDN Desktop.

11 Licensing Baan Data Navigator 2.6

TIP:

http://www.support.baan.com/

Licensing Baan Data Navigator 2.6



A

activating the BDN server · 4-1application settings · 9-1

B

Baan Debug Level log · 4-10Baan SQL Trace log · 4-10BDB errors · 7-2BDN server

activating · 4-1adding · 4-4log · 4-6, 4-9monitoring · 4-3overview · 1-2properties · 4-7removing · 4-5scheduled shut down · 4-8status · 4-6troubleshooting · 7-1

BDN Server Monitor · 4-3BDNP.ini · 4-9BDNP.ini settings

Baan connection · 9-7database · 9-4environment · 9-6Excel settings · 9-8extra net settings · 9-7logging · 9-1memory settings · 9-7model transport · 9-8reports · 9-7

C

central monitor address · 4-7central monitor port · 4-8codes, language · 9-8company settings · 2-6Count function · 5-4

D

data navigation · 1-4database

table indexes · 3-2table properties · 3-2table size · 3-1, 5-1updates · 3-2updates · 3-2updates from Baan · 3-1

DBG_StdErr_X.log · 4-9diagnostic tools

performance logs · 4-9TopTier Analyzer · 8-1

12 Index

Index


E

efficient drags only · 5-2exclusive import · 2-5

G

guests · 4-8

H

HyperRelational link · 1-5HyperRelational navigation · 1-2HyperRelational track · 1-6

I

importingroles · 2-4security settings · 2-4users · 2-4

L

language codes · 9-8licensing procedures · 11-1link

HyperRelational · 1-5HyperRelational track · 1-6

logging on · 1-3logs

Baan Debug Level · 4-10Baan server · 4-9Baan SQL Trace · 4-10BDN server · 4-6, 4-9Memory · 4-9TopTier SQL Trace · 4-10

M

maximum records · 5-4media path · 4-7media path alias · 4-7Memory log · 4-9multi-company data · 2-6multi-company settings · 2-6

N

native connection · 6-1navigation

example · 1-4path · 1-6technology · 1-2

P

passwords, changing · 2-3plug-in location · 4-7project name · 4-7properties, server · 4-7

Q

querystop and timeout · 6-1

query costmonitoring · 5-1preferences · 5-2settings · 5-1, 5-3

query count function · 5-4query management

set maximum records · 5-4

Index


R

remote server, running · 4-5repository updates · 3-1roles, importing · 2-1, 2-4

S

Security Updates tool · 2-4importing roles · 2-4importing security settings · 2-4

serveractivating · 4-1adding instances · 4-4address · 4-8defining properties · 4-7monitoring · 4-1options · 4-6remote · 4-5removing instances · 4-5scheduled shut down · 4-8

server monitor, running · 4-3SrvMemX.xls · 4-9Super User, creating · 2-6

T

Table properties · 3-2TopTier Analyzer utility · 8-1TopTier SQL Trace log · 4-10troubleshooting

BDB errors · 7-2

BDN server · 7-1missing tables · 7-3strategies · 7-1TopTier Analyzer · 7-1, 8-1Web client · 7-3

U

updatesperiodic · 3-1repository · 3-1

Upgrader · 10-1adding the Web Query Interface ·

10-2uprading HTMLs · 10-2

usersfinding · 2-2importing · 2-1, 2-4managing · 2-1passwords · 2-3Setup · 2-1toptier · 2-1TTBaan · 2-1TTPassword · 2-1

Users tool · 2-2

W

Web clientlogging on · 1-3troubleshooting · 7-3

baan data navigator 2.6 administrator guide ivb, ivc.pdf · 2017-12-04 · about this document baan...

Documents