Difference Study BaanERP 5.0b - 5.0c

BaanERP 5.
0c Tools
Difference Study BaanERP 5.0b - 5.0c
Difference Study P3167A US

Document information
Document
Document code : P3167A US
Document group : Product Information
Document title : Difference Study BaanERP 5.0b - 5.0c
Application/Package : BaanERP 5.0c Tools
Edition :A
Month modified : May, 2001
Check the PowerDOCS or CyberDOCS database to see if this document is

still a valid edition.
© Copyright 2001 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.
Table of contents
Document information i
About this document v
1. New concepts in BaanERP Tools 1-1
1.1 Integration of Microsoft Office applications in BaanERP 1-1
1.2 The BaanERP eMessage Connector 1-5
1.3 Application Response Measurement (ARM) 1-6
1.4 Microsoft Management Console (MMC) 1-6
1.4.1 BaanERP snap-ins for Microsoft Management Console (MMC) 1-7
1.5 MS Windows Performance Monitor 1-7
1.6 Active Directory Services 1-7
1.6.1 ADS in BaanERP 1-8
1.6.2 The integration of ADS in BaanERP 1-8
1.6.3 The function ADS in BaanERP 1-9
1.6.4 Net Change Server Management (From Service Pack-4) 1-10
1.7 Application Services Manager (ASM) (from Service Pack 6) 1-11
2. Summary of changes to Baan Tools 2-1
2.1 Usability features 2-1
2.1.1 Support for euro currency symbol (€) 2-1
2.1.2 File menu addition 2-1
2.1.3 Specific actions 2-2
2.2 System management features 2-4
2.2.1 Customized title bars 2-4
2.2.2 Roaming profiles 2-5
2.2.3 BaanLogin functionality in Baan Internet (BI) server 2-7
2.2.4 Informix level II and DB2 level II 2-7
2.2.5 Improved audit functionality 2-7
2.2.6 BaanERP system policy options 2-8
2.2.7 BSE_LOG environment variable for all executables 2-11
2.2.8 Baan Windows options 2-11
2.3 Programming features 2-12
2.3.1 File dialog 2-12
2.3.2 Multithreaded OLE automation 2-12
2.4 Connectivity features 2-12
2.4.1 Baan OpenWorld Adapter 2-12
2.4.2 Baan Automation Server 2-12
2.4.3 Exchange through the Data Access Layer (DAL) 2-13
2.5 Output features 2-14
2.5.1 Security Support Provider Interface 2-14
2.5.2 Intelligent Report Tagging 2-14
2.5.3 Integration with Seagate Info (from service pack 6) 2-15
2.6 Windows NT features 2-15
2.6.1 Combination virtual machine and database driver (Windows NT) 2-15

i
Table of contents
3. New functionality in Baan Tools 3-1

3.1 BaanERP Office integration solution 3-1
3.1.1 BaanERP Office integration solution’s BaanERP components 3-1
3.1.2 The BaanERP Office integration solution’s Office components 3-11
3.2 BaanERP eMessage Connector 3-21
3.2.1 BaanERP eMessage Connector repository 3-21
3.2.2 BaanERP eMessage message log 3-26
3.2.3 BaanERP eMessage address database 3-30
3.2.4 Additional BaanERP eMessage Connector sessions 3-33
3.3 Application Response Measurement (ARM) 3-35
3.4 BaanNT Manager 3-38
3.4.1 Baan Logic Service 3-39
3.4.2 BaanERP Licensing Service 3-40
3.4.3 Shared Memory Service 3-40
3.4.4 Job Daemon Service 3-40
3.5 MS Windows Performance Monitor 3-40
3.5.1 BaanERP specific performance counters 3-41
3.6 NetChange 3-42
3.6.2 Additional NetChange Server management sessions 3-49
3.7 Application Services Manager (ASM) 3-51
3.7.1 To define the ASM’s XML Files 3-51
3.8 Exchange through the Data Access Layer (DAL) 3-57
4. Procedures related to BaanERP Tools 4-1
4.1 BaanERP Office integration solution 4-1
4.1.1 BaanERP Office integration solution installation on the BaanERP server 4-1
4.1.2 The BaanERP Office integration solution installation on the client 4-3
4.1.3 To transfer the BaanERP data to Word 4-4
4.1.4 To transfer the BaanERP data to Excel 4-5
4.1.5 To work with the Excel Baan workbooks 4-7
4.2 The BaanERP eMessage Connector procedures 4-8
4.2.1 To set up the BaanERP eMessage Connector repository 4-8
4.2.2 To set up the address book data 4-10
4.3 Application Response Measurement procedures 4-13
4.3.1 To enable ART measurement for specific transactions 4-14
4.4 Baan NT management procedures 4-17
4.4.1 To enable and start a BaanERP service 4-18
4.4.2 To start a Baan software environment (BSE) 4-19
4.4.3 To configure the Baan Logic Service 4-20
4.4.4 To set the delegation trust for the user 4-23
4.4.5 To configure the Baan Shared Memory Service 4-25
4.4.6 To rename BSE environments 4-27
4.4.7 To edit the BSE variables 4-28
4.5 MS Windows Performance Monitor procedures 4-30
4.5.1 To View BaanERP Performance Counters 4-30
4.5.2 To set an alert in the MS Windows Performance Monitor 4-33
4.6 ADS procedures in BaanERP 4-37
4.6.1 To find the BaanERP environment information in ADS 4-37

ii
Table of contents
4.6.2 To publish a UNIX server in BECS 4-38

4.6.3 To maintain the Baan Windows configuration properties 4-39
4.7 Net Change procedures in audit management 4-40
4.7.1 Table management 4-40
4.7.2 Net Change Server management 4-45
4.8 BaanERP system policy procedures 4-50
4.8.1 Password storage procedure 4-50
4.8.2 BaanERP Windows (BW) configuration edit procedure 4-51
4.9 Application Services Manager (ASM) procedures 4-53
4.9.1 To run the ASM 4-53
4.9.2 ASM User Interface 4-54

iii
Table of contents

iv
About this document
This document provides an overview of the differences between BaanERP 5.0b

Tools and BaanERP 5.0c Tools for all modules, including BaanERP Exchange,
the BaanERP Webtop, and the Baan OpenWorld Adapter.
Familiarity with BaanERP 5.0b Tools, the overall structure of packages,
modules, and sessions in the BaanERP software will help you understand this
document.
Chapter 1, “New concepts in BaanERP 5.0c Tools,” provides an overview of
the new concepts used in BaanERP Tools.
Chapter 2, “Summary of the changes to BaanERP 5.0c Tools,” details the
changes of BaanERP 5.0c Tools compared to BaanERP 5.0b Tools.
Chapter 3, “New functionality in BaanERP 5.0c Tools,” describes how the new
and changed functionality of BaanERP 5.0c is implemented in the BaanERP
Tools sessions.
Chapter 4, “New procedures related to BaanERP 5.0c Tools,” describes the new
procedures related to BaanERP 5.0c Tools.
Note The BaanERP session windows on your screen can differ from the screen shots
in this document. Depending on your screen size, the session windows can have
more tabs or less tabs. Depending on the BaanERP functions that are available
in your system, and your authorization to use these functions, the sessions can
contain more fields and group boxes than appear on your screen.

v
About this document

vi
1. New concepts in BaanERP Tools
This chapter provides an overview on the following new concepts in BaanERP

Tools for BaanERP 5.0c:
n Integration of Microsoft Office applications in BaanERP
n The BaanERP eMessage Connector
n Application Response Measurement ARM
n The Microsoft Management Console (MMC)
n The Microsoft Windows Performance Monitor
n Active Directory Services (ADS)
n Net Change Server Management
n Application Services Manager (ASM)
1.1 Integration of Microsoft Office applications in

BaanERP
The purpose of the integration of Microsoft’s Excel and Word in BaanERP is to
supply Baan end users with the best of both worlds: the ease-of-use and
flexibility of Microsoft Excel, and BaanERP’s capability to store and retrieve
mass relational data.
With the Office integration, end users in a company can select data from a Baan
session and send that information to Microsoft’s Office applications. Word and
Excel can use the data to generate documents and workbooks, such as sales
contracts, based on a predefined Baan-related Word and Excel templates.
The templates are typically designed by a key user with experience with the
BaanERP functionality. The template designer can create a new template in
BaanERP or in the Office applications. When the templates are tested and
correct, the templates are published by the template designer to make them
available to the end users. The template will then be available to all sessions
that use the Baan table related that relates to the template.

1-1
New concepts in BaanERP Tools
For example, Figure 1-1 shows that the Word integration enables end users in
company 561 to send a selection of records from the Sales Contracts
(tdsls3500m000) session in BaanERP to the a predefined Contract Confirmation
template in Word.
Figure 1-1 Activating the Contract Confirmation template in Sales Contracts
The sales contact data is displayed in the Contract Confirmation template in

Word (see Figure 1-2).
Figure 1-2 Contract Confirmation template in Word

1-2
End users can also generate Excel workbooks based on a Baan-related Excel
template. The workbook can be created in BaanERP or with Excel. When the
workbook has been generated, end users can use all Excel functionality to
manipulate the Baan data. Any changes made to the Baan data can be written
back to Baan.
For example, Figure 1-3 shows that the Excel integration enables end users in
company 590 to send a selection of records from the Characteristics
(qmptc0101m000) session in BaanERP to the Characteristics workbook. The
Characteristics workbook is based on the predefined Characteristics template in
Excel.
Figure 1-3 To activate the Characteristics template in the Characteristics (qmptc0101m000)

session

1-3
The Characteristics data is displayed in the Characteristics template in Excel

(see Figure 1-4).
Figure 1-4 Characteristics template

1-4
1.2 The BaanERP eMessage Connector

With the BaanERP eMessage Connector, users can send report data from
BaanERP through e-mail, fax, and so on, to recipients (see Figure 1-5). The
eMessage Connector also enables you to send short cuts to Baan records:
n To your desktop.
n To Outlook or an other mail protocol to send the short cut to others.
n As task to the Outlook task list.
Figure 1-5 An example of an eMessage Connector-enabled session
The option that combines e-mail and shortcuts to the desktops enables end users
to work together in a very easy fashion.
The eMessage Connector enables you to build several classes of messaging
applications in the context of a BaanERP application. The types of messages
can include fax, e-mail, telex, SITA, and SMS. With the eMessage Connector,
the BaanERP application can:
n Send messages with the help of a mail client, for example, through
Microsoft Outlook or another MAPI-compliant mail client.
n Send messages to a server-side service provider.
n Process incoming EDI-style messages without any user assistance.
The BaanERP eMessage Connector is independent of the actual messaging
protocol used between sender and recipient.
The eMessage Connector is defined between a BaanERP messaging-enabled
application and one or more service providers. On the client side,
communication is one-directional, from BaanERP to external service providers.
On the server side, communication can occur in both directions.

1-5
1.3 Application Response Measurement (ARM)

Application Response Measurement (ARM) is an industry standard as well as a
set of tools that enables system administrators to monitor the overall user
response time of a whole system, such as BaanERP, as well to monitor specific
functionality in a specific application. You can use the acquired data to analyze
system performance or functionality performance.
ARM helps the IT manager to check whether the service level agreement is met.
The system administrator uses ARM to detect slow responses to users and to
find bottlenecks in an installed BaanERP environment. ARM also helps to
provide additional information to help answer some key questions, such as:
n How does the application perform?
n What is the response time?
n What is the workload throughput?
n Do I meet my service level agreement?
n Why does the application perform poorly?
n Who uses the application, how frequently do they use the application, and
what types of operations are performed?
n Which servers provide the services?
The Baan software does not process or visualize the data generated by ART. To
process the ART data, you must have a third-party tool, such as IBM’s Tivoli or
Hewlett Packard’s HP-Openview, that supports standard ARM solutions.
Currently, the Computer Management Group (CMG) standardizes ARM
solutions.
1.4 Microsoft Management Console (MMC)

The MMC is a Windows-based multiple document interface (MDI) application
that assists the administration of Microsoft Windows NT 4.0 and later.
MMC itself does not perform any management tasks, but provides a common-
console framework into which you can load management tools. The tools,
which can consist of one or more applications, are built into modules called
snap-ins. You load the snap-ins into the MMC to perform the management
tasks. Snap-ins are created by Microsoft, or independent software vendors
(ISVs) such as Baan.
The MMC offers a comprehensive, and consistent interface that enables Baan to
develop management tools that integrate with a unified console. Baan uses
MMC to support simplified administration through integration, delegation, task
orientation, and overall interface simplification.

1-6
1.4.1 BaanERP snap-ins for Microsoft Management Console (MMC)
In BaanERP 5.0c, the following BaanERP snap-ins are introduced:

n The Baan NT Manager snap-in.
For servers only. Installed automatically during installation of BaanERP.
n Application Services Manager snap-in.
For servers and clients. Requires manual installation.
Baan NT Manager snap-in

Baan introduced the Baan NT manager snap-in, which you can use to manage
BaanERP on your Windows NT 4.0 or later server. You can use the Baan NT
manager snap-in to:
n View all BaanERP environments.
n View the status of the BaanERP-specific services for each Baan
environment.
n Add, change, or remove BaanERP-environment-specific variables.
n Install, start, and stop BaanERP-specific services.
n Edit the settings of the BaanERP-specific services.
Application Services Manager snap-in

Baan also introduced the Application Services Manager snap-in. You can use
the ASM snap-in to command the ASM to start, and stop application services in
a BaanERP environment. For more information about ASM, refer to
“Application Services Manager (ASM),” later in this chapter.
1.5 MS Windows Performance Monitor

The MS Windows Performance Monitor is a graphical tool that enables you to
measure and view the performance of your local computer and network
computers.
BaanERP publishes the following specific performance indicators, which you
can view with the MS Windows Performance Monitor:
n Baan Environment Counters.
n Baan System Counters.
1.6 Active Directory Services

Microsoft’s Active Directory is the directory service for Microsoft’s Windows
2000 Server. Microsoft’s Active Directory stores information about objects on
the network and makes this information easy for administrators and users to
find and use. Active Directory service (ADS) uses a structured data store as the
basis for a logical, hierarchical organization of directory information.

1-7
Network security is integrated with ADS through logon authentication and

access control to objects in the directory. With a single network logon,
administrators can manage directory data and organization throughout their
network, and authorized network users can access resources anywhere on the
network.
1.6.1 ADS in BaanERP
BaanERP uses ADS for the following reasons:

n ADS stores the client configuration settings.
n The Baan Logic Service publishes the connection points to the Baan
software environments (BSE) in ADS.
In BaanERP, the Active Directory Service (ADS) is a directory that you can use
to store the client configuration settings that are available to all systems
connected to a network. ADS enables you to use the client configuration
settings on other systems in the network. With ADS, the users can access
information on any system in the network. In other words, the network users are
no longer tied to using their own client, with their own settings, in the network.
The Baan Logic Service publishes the connection points to the BSE
environments in ADS. Baan Windows (BW) uses these connection points to
connect to these environments. The Baan Environment and Configuration
Selector (BECS) uses these connection points to display information about all
available environments.
1.6.2 The integration of ADS in BaanERP
The following components are used for the integration of ADS in BaanERP:
n Windows NT registry.
n Baan Logic Service.
n Baan Windows (BW).
n Baan Environment and Configuration Selector (BECS).
n A library with abstraction functions.
The Baan Logic Service retrieves information about the available environments
from the Windows NT registry, and publishes this information as connection
points to the BSE environment in ADS. These connection points are used by
BW to connect to that environment, and by BECS to display the available
environments.

1-8
Figure 1-6 shows a schematic overview of the integration in BaanERP.
NT Registry
Logic service BW & BECS
Connection
points
ADS
Figure 1-6 A schematic overview of the integration in BaanERP
The Baan Logic Service publishes the services without any user interaction.
Note To make sure that the directory is always available for a UNIX environment,
you must use at least one Windows NT system as a directory server.
1.6.3 The function ADS in BaanERP
At startup, the Baan Logic service publishes the connection points in ADS for
each environment on the server with information such as the name of the server
to connect to and the name of the BSE-environment. BW uses this information
to set up a connection to the server.
For each environment on a server, the Baan Logic Service creates an object in
ADS. This object is of class serviceConnectionPoint. The objects are smaller
than 1K bytes. The objects in ADS are automatically updated at startup when
the configuration of a Baan Software Environment (BSE) changes, for example,
when the name of the server or the logon protocols are changed.
The Baan Logic Service uses the following string attributes:
n cn.
This string attribute is used to store the name of the environment that is
published.
n serviceDNSName.
This string attribute is used to store the name of the server where the
environment is located.

1-9
n serviceBindingInformation.
This multi-valued string attribute is used to store additional connection
information. Currently, the port-number, protocol, porting set number, and
the BSE-path is stored in this attribute, for example:
Port = 512
BSE = c:\BaanV
Protocol = EXEC
Porting set = 7.1b
n Keywords.
Administrators can use this multivalued string to perform queries. The
Logic Service stores the company name (Baan Company) and the product
name (BaanERP) in this attribute.
The names of classes and attributes must be unique in a company that uses ADS
in BaanERP. The use of unique names makes name clashes less likely.
However, the use of unique names does not guarantee that name clashes will not
occur.
1.6.4 Net Change Server Management (From Service Pack-4)
The Net Change Server enables the retrieval of changed business objects from
BaanERP. Net Change defines the net result of all changes on a business object
in a specific period of time. For example, if a sales order is added and
subsequently updated several times, the net result is a new sales order. If a sales
order line is updated and, after some time, another line from the same sales
order is updated, the net result is an updated sales order, which consists of an
unchanged header and two changed lines.
When transactions are carried out on the BaanERP database, the Net Change
Server picks up the changes, translates the changes into a business object,
checks whether the business object is within the range of business objects to be
published, and transforms or formats the business object, if required.
Subsequently the changed business objects are stored and made available for
retrieval. The Net Change Server can either store each change on an object
separately, or combine multiple changes on the same object into a single net
change.
The Net Change Server reduces processing time and network load for interfaces
or applications that read data from BaanERP. To achieve this reduction,
BaanERP exchanges net changes rather than regenerating all data regularly, and
has the requested data already available before the actual request from a client
application arrives.
The Net Change Server minimizes the impact of integration for the end user of
BaanERP. This is achieved by in the user transaction only doing what is
absolutely necessary, that is, send the changes to the audit trail so the Net
Change Server can start processing the changes.

1-10
The main characteristics of the Net Change Server are:

n Configurable.
The structure. and properties of the business object and the mapping to
BaanERP database tables and columns can be configured. In addition, the
range of business objects (filters) and the format (such as a date/time
format) is configurable. The Net Change Server configuration requires no
changes to the existing BaanERP applications.
n Reliable.
The Net Change Server assures the completeness and consistency of the
business objects and makes sure the changes are presented in the correct
sequence. Net Change Server also keeps track of what changes have been
retrieved, so no changed objects will be missing and no changed objects
will be transferred twice unless explicitly asked.
n Open.
The business objects are published in XML format.
n Near real-time (asynchronous).
As soon as the user transaction is finished, the Net Change Server is
triggered and it immediately starts translating the database changes into a
changed business object that an external application can use.
1.7 Application Services Manager (ASM) (from Service

Pack 6)
The ASM is an administrative tool that you can use to start, and in some cases
stop, BaanERP application services. For example, the ASM can:
n Start, and stop a job daemon.
n Start (but not stop) Baan OpenWorld adapters.
In XML files, you can predefine the application services that the ASM can start,
and in some cases stop. To define the XML files, you use the Baan sessions that
you can find if you click Baan Tools Application Configuration
Application Services Manager, which includes the following sessions:
n Baan Software Environments (ttaad0570m000)
n ASM Service Templates (ttaad0573m000)
n ASM Service Instances (ttaad0574m000)
n Convert ASM to Runtime (ttaad0270m000)
You can send commands to, and receive responses from, the ASM using the
following:
n Microsoft Management Console (MMC) with ASM snap-in.
n Command prompt.

1-11
Through the ASMs API interface, users of external software modules can
command the ASM to start a BaanERP application service.
ASM can run on:
n Windows NT, as an NT service.
n UNIX, as a daemon process.
n AS/400, as a job.

1-12
2. Summary of changes to Baan Tools
This chapter provides a summary of the changes in the modules of in 5.0c

compared to 5.0b. The changes are categorized by:
n Usability features.
n System management features.
n Programming features.
n Connectivity features.
n Output features.
n Windows NT features.
2.1 Usability features

This section describes the new usability features that will help users to fully use
the BaanERP tooling and BaanERP functionality.
2.1.1 Support for euro currency symbol (€)
To be compliant with the euro currency symbol (€), the euro symbol is added to
currently used character sets. The key areas that are required to support the euro
currency symbol are:
n Keyboard input.
n Display on screen.
n Printing on paper.
n Storage in a database.
2.1.2 File menu addition
A new menu option, Send to, is added to the File menu of Baan overview
sessions. If you select a record in the overview session, click the File menu, or
right-click on the record, and pause over Send to. From the sub-menu, you can
choose the following:
n Desktop.
Use this option to add to your desktop a link to the record you selected in
the Baan session.
n Mail Recipient…
Use this option to send a link by e-mail to the record you selected in the
Baan session.
n Task List…
Use this option to add a link to the record you selected in the Baan session
to your Tasks folder in MS Outlook.

2-1
Summary of changes to Baan Tools
2.1.3 Specific actions
Shortcut menus
You can now make the commands on a session’s Specific menu available as a
shortcut menu. The behavior of the shortcut menu is identical to the options on
the Specific menu. To enable the shortcut menu, you must first select a record
in the grid and then right-click on the mouse (see Figure 2-1).
Figure 2-1 Shortcut menu

2-2
Menu buttons
A menu button is a command button with a drop-down arrow that shows a drop-
down menu to reveal more options or information. Menu buttons are used when
multiple actions are available under one button, for example, when you can
create multiple types of texts (see Figure 2-2).
Figure 2-2 Menu button

2-3
2.2 System management features

This section describes the new system management features that will help
administrators and key-users to optimize the BaanERP functionality for end
users.
2.2.1 Customized title bars
BaanERP Tools 7.1a SP3 and later, enables you to customize the menu
browser’s and session’s title bar. You can use this option, for example, to show
the application’s server, or to make a clear distinction for the end user between
the production system and the test system.
You can modify title bar with additional command line options in the BW
Configuration Properties dialog box, which you can start from the Baan
Environment and Configuration Selector (see Figure 2-3).
Figure 2-3 BW Configuration Properties
On the Bshell Environment tab, in the Command field, you can specify
additional command line options for the title bar in the following format.
-- -set BAAN_WIN_TITLE="some string"

2-4
You can substitute "some string" in the previous command line with the
following options:
n %h Host name.
n %c Company number.
n %C Company description.
n %s Session code.
n %S Session description.
n %p Package combination.
In the Command field, you can combine more then one option. You can also
define a self-defined string combined with more then one option.
Example If you enter -- -set BAAN_WIN_TITLE="Test Environment - %S %s", as
shown in Figure 2-3, a session’s title bar is modified to indicate a test
environment as shown in figure 2-4.
Figure 2-4 User Data (ttaad2500m000)
Note that the session’s description and session code are also shown.
2.2.2 Roaming profiles
To improve sharing of desktops in a BaanERP environment, the user’s

BaanERP Windows Client (.bwc) configuration files are moved to the user’s
roaming profile. A roaming profile stores the user’s BaanERP configuration
information on the server on which the user is validated. This profile is
available every time the user logs on to any computer on the network. Any
changes made to the user’s roaming user profile are updated on the server.
With roaming user profiles, users can log on to any computer in their domain.
After the roaming user profile has been authenticated in the directory service,
the user profile stored on the server is copied to the local computer. All of the
users’ settings and documents that are stored on the server in the roaming user
profile are copied to the local computer. In other words, in BaanERP 5.0c, the
user’s BaanERP Windows Client (.bwc) configuration files go where the users
go.

2-5
From Active Directory, you can assign a server location for user profiles. If you
enter a user profile path into a user's domain account, a copy of the user’s local
user profile is saved both locally and in the user profile path location when the
user logs off. The next time that user logs on, the user profile in the user profile
path location is compared to the copy in the local user profile folder, and the
most recent copy of the user profile is opened. The local user profile becomes a
roaming user profile because of the centralized domain location. The user’s
documents and settings are available wherever the user logs on. For more
information about roaming user profiles, refer to the Microsoft documentation.
In the Baan Environment and Configurator Selector (BECS), on the Tools
menu, you can open the Options dialog box. You can use this dialog box to
define the location of the user’s profile. Click Other and define the user’s
profile storage path as shown in Figure 2.5.
Figure 2-5 Baan Enviroment and Configurator Selector Options
The user profile can be located on any server; and does not have to be a domain
controller. When the user logs on, Windows checks the user’s account to see
whether a user profile path exits. If this path exists, the user profile is located by
the system and copied to the local computer.

2-6
2.2.3 BaanLogin functionality in Baan Internet (BI) server
In BaanERP5.0c, the Baan Internet (BI) server can now use the BaanLogin
functionality to connect to the BaanERP back end. The BaanLogin functionality
provides extra security and more flexibility with firewalls (configurable port).
2.2.4 Informix level II and DB2 level II
The Informix level II and DB2 level II database drivers are introduced to
provide a better scalable solution. Database drivers can be of level I or level II.
A level I database driver typically splits up the query into smaller queries. A
level II database driver sends the query to the database from the BaanERP
software as is.
2.2.5 Improved audit functionality
BaanERP Exchange is a generic tool that is used for replicating data, for
exporting data from, or importing data into, a BaanERP database, or for
integrating BaanERP with other applications. Exchange based on audit enables
the user to replicate changes. In other words, you do not send all data, but just
the changes in a specific period of time. You can replicate changes regularly,
for example, every week, every day, or every hour.
The exchange based on audit uses the audit trail, in which the changes on the
source database are logged. BaanERP Exchange selects the changes from the
audit trail, performs any transformations as specified by the user, and sends the
resulting data to one or more other sites where the changes are replayed on the
target database.
In BaanERP 5.0c, the following changes are introduced in the BaanERP’s audit
functionality:
n A new Audit Trail API is introduced to make use of the new transaction
notifications.
n The audit server and database client layer of the Virtual Machine (VM) are
updated. The audit server generates a new transaction ID. In addition, a
transaction notification is created for each transaction that is audited, which
makes the audit trail reliable and accessible.
The Audit Trail API

The new Audit Trail API enables BaanERP Exchange to retrieve information
from the audit trail in a different way. BaanERP Exchange is no longer
concerned with the technical structure of the audit trail, but with the transaction
data that meets specific criteria. The new Audit Trail API enables BaanERP
Exchange to create queries that can output transaction data for table X and/or
table Y that have a commit time between t1 and t2. You can then process the
transactions and actions.

2-7
The replication process is not table-based, but transaction-based. The batch-

oriented Exchange export creates one file for each database table. As a result,
the Exchange export retrieves the data from the audit trail for each table.
However, because the transaction ID and the sequence number of the action in
the transaction is available, the relation between all database actions on various
tables is preserved. This enables the Exchange import process to replay the
database actions on the target database transaction-based: the data for several
tables are merged and sorted by transaction when importing at the target site.
Transaction notifications for auditing

An important part of data replication is to determine which records are actually
changed. Therefore, the record’s history is kept. In BaanERP 5.0c, keeping the
change history is part of the transaction. Keeping a record’s change history
ensures that you never have in-doubt transactions in the change history.
The new Audit Trail API uses transaction notifications to quickly select the
audit data that is within the audit range. As a result, you do no longer have to go
through the audit files to find the required transaction data, but you can quickly
select and collect the data you need efficiently, based on the Audit Trail API
functions.
For a large audit interval with several updates, the impact is limited because
relatively more time is spent in processing, rather than in collecting changes. If
a limited number of changes are processed at a time, for example, because the
process runs often, the performance increases. As a result, BaanERP Exchange
enables the user to run the replication more frequently, which reduces latency.
Additional Audit improvements

With BaanERP Tools 7.1a’s improved audit functionality, you can select the
fields that must be audited. For example, you can specify whether all table
fields must be logged into the audit file or only some key-fields, and, of course,
you can specify the changes. The $BSE/lib/audit_spec file sets the selective
auditing.
2.2.6 BaanERP system policy options
BaanERP 5.0c introduces default BaanERP system policy options to centralize

the following configuration actions on the network domain controller, rather
than on the local client:
n Password storage.
n BaanERP Windows (BW) configuration editing.

2-8
Password storage
In BaanERP 5.0c, each user can store and retrieve passwords, which are used to
authenticate a user to a Baan Application Server. Some secure environments do
not want a BW password to be stored on the local client, which would enable
unauthorized access to the Baan environment when such a password file is
stolen or accidentally put on a shared directory. Therefore, an option is
introduced to disable the local storage of the BW password.
Figure 2.6 shows that the Password check box in the BW Configuration
Properties dialog box is disabled.
Figure 2-6 BW Configuration Properties
BaanERP Windows (BW) configuration editing

In some environments, BW configuration files are stored on a shared drive and
managed centrally by a system administrator. In such a configuration, you do
not want each individual user to be able to create, delete, and modify BW
configuration files. Therefore, an optional feature is introduced, which permits
only system administrators to edit the BW configuration files.

2-9
Typically, a user can edit a BW configuration through the Baan Environment

and Configuration Selector (BECS) (see Figure 2-7) and the BW Configuration
Properties editor (see Figure 2-8).
Figure 2-7 BECS – Baan Environment and Configuration Selector
However, if the BaanERP Windows (BW) configuration editing policy is

enabled, you can start the BW Configuration Properties dialog box through
BECS, but the fields in the editor are disabled, as shown in Figure 2.8.
Figure 2-8 BW Configuration Properties dialog box

2-10
2.2.7 BSE_LOG environment variable for all executables
All binaries in the BaanERP Tools 7.1a porting set can use the BSE_LOG
environment variable. If the BSE_LOG environment variable is set, logging is
written to the directory specified by the BSE_LOG variable. If the BSE_LOG
environment is not set, $BSE/log directory is used as the default log directory.
Note The BSE_LOG environment variable only applies to non-Windows NT and
Windows 2000 operating systems. Windows NT and Windows 2000 use
Microsoft’s Event Viewer, which is located in Administrative Tools. Event
Viewer maintains logs about application, security, and system events.
2.2.8 Baan Windows options
In BaanERP Tools 7.1a, central deployment of Baan Windows (BW) is

improved. As a result, you can install BW on a central server, and point the
users to the central server by means of shortcuts or Uniform Naming
Convention (UNC) path names to start BW.
UNC is a method of naming files among computers on a network so that a file
on a given computer has the same pathname when accessed from any of the
other computers on the network.
Example If the directory c:\path1\path2\...pathn on computer baan1 is shared under the
name pathdirs, a user on another computer can open
\\baan1\pathdirs\filename.ext to access the c:\path1\path2\...pathn\filename.ext
file on baan1.
Other new Baan Windows options in BaanERP Tools 7.1a include:
n The default Windows logon name can be used when no login name is
specified in the BW configuration file.
n You can specify a login name when you start BW with the BW executable,
for example, bw.exe /user <user-name>.
n Automatic registration of OLE Custom Control (OCX) components. OCX
is a software module based on OLE and COM technologies, which, when
called by an application, produces a control that adds some desired feature
to the application.
n Log files are written to the %TEMP% directory on Windows 95.
n If BSE_TMP is not set, tmp files are written to the %TEMP% directory.
n You can now create a unique registry entry to use OLE Automation with the
bw.exe /reg option.

2-11
2.3 Programming features

This section describes the new programming features that will help developers
to optimize the BaanERP functionality for end users.
2.3.1 File dialog
A number of applications must provide the user with the ability to select files on
the client PC. For this, a standard Windows file open dialog is provided.
2.3.2 Multithreaded OLE automation
In BaanERP Tools 7.1a, the OLE automation functionality is multithreaded.

The OLE automation objects in BW/BI are implemented in separate threads
using the COM apartment-threading model. Multithreading enables the user to
run multiple calls simultaneously, and enables recursion when applications are
connected through OLE automation.
2.4 Connectivity features

This section describes the new connectivity features that will enable BaanERP
to connect to, and communicate with, third party systems and software.
2.4.1 Baan OpenWorld Adapter
The Baan OpenWorld Adapter is introduced in BaanERP 5.0c to enable Baan

products and third-party products to connect to BaanERP. The Baan
OpenWorld Adapter uses standard middleware and XML messages. The Baan
OpenWorld Connector has introduced:
n A new way to create BOIs.
n A Java virtual machine integration with the Baan Virtual Machine (VM).
n A Baan virtual machine that can run without a user iInterface.
2.4.2 Baan Automation Server
Baan Automation Server provides a very easy-to-use mechanism of performing

calls to Baan DLLs from development environments as Visual Basic and vice
versa.

2-12
2.4.3 Exchange through the Data Access Layer (DAL)
In BaanERP 5.0c, BaanERP Exchange can make use of the Data Access Layer
(DAL). The BaanERP Exchange Import (XCH) module enables you to import
through the DAL. In other words, all logic specified in the DAL can be applied
during the data import without any programming.
The import through DAL can be used for standard interfaces developed by Baan
for partner products, as well as for specific interfaces built by customers, for
example, to integrate BaanERP with legacy systems. When you build interfaces
with other applications, the use of DAL in BaanERP Exchange is very useful.
The constraint checks and integrity checks that are programmed in the DAL are
automatically carried out. Updates on affected tables are also carried out.
Exchange through the Data Access Layer is also available for multisite
environments.
If the DAL is not used, the updates are carried out directly on the BaanERP
database. Only the checks specified in the data model are executed, such as
domain constraints and references. If the import through DAL is used, the
updates are not sent directly to database, but by means of the DAL.
If the DAL is used for a table relation during a database table data import, the
functions dal.new, dal.update, and dal.destroy are used as an
alternative for the db.insert, db.update, and db.delete functions.
In other words, the functionality included in these DAL functions is carried out
when the data is imported.
To use the DAL during an import, in the Table Relations (Import)
(tuxch0121s000) session, select each of the check boxes under Data Access
Layer. Depending on the check box selections the DAL, property checks are
carried out. You can combine the use of DAL for database tables with not using
DAL for other tables. As a result, import batch can contain both types of table
relations simultaneously. The import through DAL works for both the import
based on audit or indicators (inserts, updates, deletes) and the full import
(inserts only).

2-13
2.5 Output features

This section describes the new output features that enable BaanERP to output
data.
2.5.1 Security Support Provider Interface
The Microsoft Security Support Provider Interface (SSPI) is the well-defined

common API for obtaining integrated security services for authentication,
message integrity, message privacy, and security quality of services for any
distributed application protocol. Baan uses this API to provide Single Sign-on
facilities for the end users. The principle of Single Sign-on is that the users then
must only enter their passwords once. The security context of that particular
user is passed to all “trusted” servers that the user accesses. For example, a
BaanERP 3-tier environment is using two servers and the desktop of the user.
Usually, this user must provide a user name and a password to log on to the
desktop. When BaanERP is started, the user must again provide a user name
and password. With SSPI, users must provide their user names and passwords
only once.
2.5.2 Intelligent Report Tagging
Intelligent Report Tagging provides an open interface to Baan report results.

Computer programs can use this interface to produce formatted reports with
proportional fonts and company logos. You can also use the interface to extract
data from report results and post-process the data, for example, in the context of
applications for the Internet. The interface is based on the XML standard. XML
(eXtensible Markup Language) defines facilities for the definition of document
structures and for marking up documents to make the documents’ structure
visible. You can analyze a document to check whether the document conforms
to the type definition, and applications can process documents based on their
recognition of the markup. The intelligently tagged (IRT) file is an intermediate
file that is produced in the process of report production. The IRT file plays the
same role as the intermediate file, which is currently produced by the Baan
report writer, but provides post-processing applications more information about
their structure. This enables improved post-processing. Devices for IRT files
can be written in the Baan programming environment using the XML parser in
the Baan 4GL engine, or the devices can offer a bridge to non-Baan applications
for document production that run outside the Baan environment. Reports must
be printable by both XML savvy and non-XML savvy devices. The print
process decides, based on the Baan Print Device settings, whether or not the
printing device selected by the user requires XML, and generates an
intermediate file of the right type accordingly.

2-14
2.5.3 Integration with Seagate Info (from service pack 6)
BaanERP is connected to Seagate Info to produce presentation-quality reports

and to enable easy distribution and sharing of the reports. The output of existing
Baan reports can be sent to Seagate Info to be post processed. This enables you
to change the font and add graphics, such as company logos and graphs. Seagate
Info can then share these reports over the Web.
2.6 Windows NT features

This section describes the Windows NT and Windows 2000 features that
BaanERP 5.0c supports.
2.6.1 Combination virtual machine and database driver

(Windows NT)
Today, Baan database drivers always run as a separate process and

communicate with the Baan virtual machine through IPC, even if the Baan
virtual machine and database driver are on the same machine (Host mode). This
model introduces a high degree of context switching, which limits the
scalability on many platforms, but especially for Windows NT. Because Host
mode has proven to be the most efficient model, and is the mode of choice,
Baan has created a Baan Virtual Machine and Database Driver that run in the
same process for Windows NT. The Windows NT installations will have this
mode enabled during and after the installation. This also required a change in
the ${BSE}/lib/ipc_info file. If the Baan VM and Database driver are
combined, the ipc_info file looks like the following:
msql d msql_srv
msql7 d msql7_srv
The Baan VM loads the shared library of the requested database from the
${BSE}/shlib directory. The expected performance gain is approximately 20%.
These combos are available for all database drivers on Windows NT.

2-15

2-16
3. New functionality in Baan Tools
This chapter describes the following new or changed functionality of BaanERP

Tools.
n BaanERP Office integration solution.
n BaanERP eMessage Connector.
n Application Response Measurement (ARM).
n Baan NT Manager.
n Microsoft Windows Performance Monitor.
n NetChange.
n Application Services Manager (ASM)
3.1 BaanERP Office integration solution

You can start the BaanERP Office integration solution components in BaanERP
and Microsoft Office applications.
3.1.1 BaanERP Office integration solution’s BaanERP components
To support the Baan Office Integration solution in BaanERP, the BaanERP

Office Integrations package is introduced in BaanERP’s Main menu. In this
package you can start the BaanERP sessions that are required to create Baan-
related templates. You can also use the BaanERP Office Integrations package to
start the sessions to maintain, test, publish, copy, and delete the Baan-related
templates.
You can also start the BaanERP sessions in Microsoft Word and Excel if the
following components are installed:
n Baan Generic Automation Server.
n Tools Template Designer, which is called BaanERP Field Mapper in pre-
Service Pack 6 versions.
n Tools End Users, which is called BaanERP Document Creator in pre-
Service Pack 6 versions.
n Server Base Template, for pre-Service Pack 6 versions only.
For the installation procedure of the listed components, refer to Chapter 4,
“Procedures related to BaanERP Tools.”

3-1
New functionality in Baan Tools
Baan Generic Automation Server Parameter (asint0100s000)

You must set the Baan Generic Automation Server parameters for every
company in your Baan environment before you use the BaanERP Office
Integration solution’s functionalities. You can set these parameters in the Baan
Generic Automation Server Parameters (asint0100s000) session, as shown in
Figure 3-1.
Figure 3-1 Baan Generic Automation Server Parameter (asint0100s000)
Office Parameters (ntint0500m000)

The Office parameters must be set for your Baan environment. The Office
parameters are applicable to all companies in your Baan environment. You can
set the Office parameters in the Office Parameters (ntint0500m000) session.
Figure 3-2 Office Parameters (ntint0500m000)

3-2
BaanERP-Related Word Templates (ntwrd0510m000)

This session shows an overview of all currently existing Baan-related Word
templates. The session also shows who created the template and the publish
status of the template.
Template designers can use this session to start the BaanERP-Related templates
(ntwrd0110s000) session to create new templates.
Figure 3-3 BaanERP-Related Word Templates (ntwrd0510m000)
Template designers can also use this session to:

n Open a template to view the template’s properties.
n Test a completed template.
n Publish the templates that are tested and correct to make the template
available to the end users in a specified range of sessions.
n Unpublish the template.
n Copy existing templates.
n Delete unused templates.
n Find an overview in which sessions the templates are published.

3-3
Baan-Related Templates (ntwrd0110s000)

Template designers can use this session to view a template’s properties, or to
define the properties of a new Word template.
Figure 3-4 Baan-Related Templates (ntwrd0110s000)
In the Local Path field, you can define a directory on your client where the
template must be stored during the template’s creation and test phase. If the
template is tested and correct, the template is moved to an appropriate directory
on the BaanERP server to make the template available to the end users.
In the Description field, you can enter the template’s name. The template’s
name will appear as a Send To option in a BaanERP session’s File menu.
In the Related Table field, you can enter or select the BaanERP table from
which you want to use data in the template. The templates are, by default,
available to the sessions that are related to the specified tables. When the
template is published, you can specify additional sessions for which the
template must be available. If you click Sessions, the Baan-Related template –
Published in Sessions (ntwrd0130m000) session appears, in which you can add
additional sessions to which the template must be available.
You can select the Create a new document for each record check box to
make sure that Word creates a new document, based on the template, for each
record the end user selects in a BaanERP session. If the check box is cleared,
Word creates one single-document with the selected records shown in tables.
In this session, you also have the options described for the BaanERP-Related
Word Templates (ntwrd0510m000) session.
BaanERP-Related Excel templates (ntexl0110s000)

This session shows an overview of all currently-existing Baan-related Excel
templates. The session also shows who created the template and what the
template’s publish status is.
Template designers can use this session to start the BaanERP-Related templates
(ntexl0110s100) session to create new templates.

3-4
Figure 3-5 BaanERP-Related templates (ntexl0110s000)
Template designers can also use this session to:

n Open a template to view the template’s properties
n Test a completed template.
n Publish the templates that are tested and correct to make the template
available to the end users in a specified range of sessions.
n Unpublish the template.
n Copy existing templates.
n Delete unused templates.
n Find an overview in which sessions the templates are published.
BaanERP-Related templates (ntexl0110s100)

The BaanERP-Related templates (ntexl0110s100) session can appear in the
following modes:
n New template mode.
n Properties mode.

3-5
In the new template mode (see Figure 3-6), the template designer can create a
new template.
Figure 3-6 BaanERP-Related templates (ntexl0110s100) in new-template mode
In the Local Path field, you can define a directory on your client where the
template must be stored during the template’s creation and test phase. When the
template is tested and correct, the template is moved to an appropriate directory
on the BaanERP server to make the template available to the end users.
In the Description field, you can enter the template’s name. The template’s
name will appear as a Send To option in a BaanERP session’s File menu.
In template properties mode (see Figure 3-7), the template designer can view
and maintain the properties of currently existing Excel templates.
Figure 3-7 BaanERP-Related templates (ntexl0110s100) in template-properties mode
In the Local Path field, you can change the directory on your client where the
template is stored during the template’s creation and test phase. In the
Description field, you can rename the template.
Under Create a workbook, you can let Excel create a new workbook that is
based on the template for each record the end user selects in a BaanERP
session. You can also let Excel create a new workbook that contains all selected
records.
Under User can select records in, you can specify the application the end user
can use to select records based upon which the workbook is created.

3-6
If you click Sessions, the Baan-Related template – Published in Sessions

(ntwrd0130m000) session appears, in which you can define sessions to which
the template must be available.
Test Baan-Related Template (ntwrd0210m000)

Before the template designer can make the template available to the end users,
the template must be tested. You can use this session to view the Word
documents and Excel workbooks that are based on the Baan-related templates.
This session can appear in the following modes:
n Word mode.
n Excel mode.
In the Word mode (see Figure 3-8), under Test with the following records, you
can specify a range of records for the BaanERP table fields that are defined in
the table. In this example, the Configuration field, the Object field, and the
Object Number field.
If you click Test, Word creates one or more documents based on your template
and the records you have selected.
Figure 3-8 Test Baan-Related Template (ntwrd0210m000) in Word mode
In Excel mode (see Figure 3-9), in the Test this template with records from
table field, you can specify the table from which the data must be used during
the test. Additionally, under Test with the following records, you can specify a
specific range of records for the test for the template’s BaanERP table fields.
Figure 3-9 Test Baan-Related Template (ntwrd0210m000) in Excel mode
If you click Test, Excel creates one or more workbooks documents based on
your template and the records you have selected.

3-7
Publish Baan-Related Template (ntwrd0211m000)

If the template is tested and correct, the templates designer can use this session
to publish the template to make the template available to all users in a company.
The published is removed from the template designer’s client and moved to the
BaanERP server.
This session can appear in the following modes:
n Word mode.
n Excel mode.
Figure 3-10 Publish Baan Related Template (ntwrd0211m000) in Word mode
In Word mode (see Figure 3-10), in the Template field and in the Description
field, you can define the name under which the template will be published. Note
that you can rename the template before you publish the template.
In the Excel mode (see Figure 3-11), you can also define the name under which
the template will be published.
Figure 3-11 Publish Baan Related Template (ntwrd0211m000) in Excel mode
Additionally, under Create a workbook, you can choose to enable Excel to

create a new workbook, based on the template, for each record the end user
selects in a BaanERP session. You can also enable Excel to create a new
workbook that contains all selected records.
Under User can select records in, you can specify the application that the end
user can use to select records, based upon which the workbook is created.

3-8
Baan Related Template – Published in Sessions (ntwrd0130m000)

If you publish a template, by default the template is available in all sessions
based on the table you related to the template. This session shows an overview
of the sessions in which the template is available by default. Template designers
can use this session to make the template unavailable in one or more of the
sessions in which the template is currently available. To make the template
unavailable, you can clear the Available check box. As a result, the template
will not appear in the corresponding session’s Send To option on the File
menu.
Figure 3-12 Baan Related Template – Published in Sessions (ntwrd0130m000)
Copy Baan- Related Templates (ntwrd0215m000)

You can use this session to create a copy of a Baan-related template. You can
create copies of published, as well as unpublished, templates. However, the
copy of a template will always be an unpublished template stored on your local
hard disk. If necessary, you can publish the copy of a template.
If you have an unpublished template, you can copy the file to another directory
on your client. As a result, the template will no longer be properly related to
BaanERP. To correct this problem, in the Local Path field, you can enter a new
path for the template’s file.

3-9
You can also use this session box to copy a template to another company. By
default, a template will be created for your default company. In the Company
field, you can define a company other than your default company.
Figure 3-13 Copy Baan- Related Template (ntwrd0215m000)
Unpublish Baan-Related Template (ntwrd0212m000)

To modify a template, you must first make the template unavailable to the end
users. You can use this session to move the template file from the BaanERP
server to your client. In the Local Path field, define the directory on your client
to which you want to move the template’s file. As a result, the end users can no
longer start the template.
Figure 3-14 Unpublish Baan-Related Template (ntwrd0212m000)

3-10
Delete Baan-Related Template (ntwrd0216m000)

To delete an unpublished template from your client, you must use this session.
If you do not use this session, Word templates will still be listed in the Baan-
Related Word Templates (ntwrd0510m000), and Excel templates will still be
listed in the Baan-Related Excel Templates (ntexl0110s000) session.
Figure 3-15 Delete Baan-Related Template (ntwrd0216m000)
3.1.2 The BaanERP Office integration solution’s Office components
To support the Baan Office Integration solution in the Office applications, you
must install the following components:
n Baan Generic Automation Server.
n Tools Template Designer, called BaanERP Field Mapper in pre-Service
Pack 6 versions.
n Tools End Users, called BaanERP Document Creator in pre-Service Pack 6
versions.
n Server Base Template (for pre-Service Pack 6 versions only)
For the installation procedure of the listed components, refer to “The BaanERP
Office Integration solution,” in Chapter 4, “Procedures related to BaanERP
Tools.”
After the listed components are installed, additional options are introduced in
Word and Excel to enable the template designer to create Baan-related
templates. In Excel, additional options are made available to the template
designers to maintain the templates.
In Excel, end users can create new workbooks that are based on a Baan-related
template.
New Baan Template dialog box

The template designer can use this dialog box to create a new BaanERP-related
Excel template. The New Baan Template dialog boxes cover the functionality
described for the Baan-Related Word Templates (ntwrd0110s000) session and
the Baan-Related Excel Templates (ntexl0110s000) session in the previous
section.

3-11
The New Baan Template dialog box can appear in the following modes:
n Word mode.
n Excel mode.
Figure 3-16 New Baan Template dialog box in Word mode
In Word mode (see Figure 3-16), the template designer must type or select a
BaanERP table. The table fields of the selected BaanERP table are used in the
Word documents that are based on the template.

3-12
In Excel mode (see Figure 3-17), the template designer cannot select a
BaanERP table. Instead, a new dialog box is introduced called the Insert Baan
Fields dialog box. This dialog box is available as an option on Excel’s Insert
menu.
Figure 3-17 New Baan Template dialog box in Excel mode
You can start the New Baan Template dialog box from the File menu in Word
or Excel. Template designers can use this dialog box to create new Baan-related
templates.

3-13
Insert Baan fields

The template designer can use this dialog box to specify the BaanERP table and
the table fields from which data must be used in the Excel workbooks that are
based on the BaanERP-related Excel template.
The New Baan Template dialog box can appear in the following modes:
n Word mode.
n Excel mode.
Figure 3-18 Insert Baan Fields dialog box in Excel
If you start this dialog box for the first time, the dialog box appears empty. You
must click Add Table… to start the Add Table dialog box, which you can use
to select BaanERP tables for the Baan-related Excel template.
Figure 3-18 shows an example of the Insert Baan Fields dialog box for the
Sales Contracts Excel template. The left pane shows the BaanERP table that is
selected for the templates and all tables that are related to the selected BaanERP
table.
The top-right pane shows the table fields of the selected BaanERP table. The
bottom-right pane shows the table fields that are selected from the top-right
pane and which will actually be used in the Baan-related Excel template.
To select a table field for the Excel template, you can double-click a table field
in the top-right pane, or select the table field and click Select.

3-14
The following icons can appear in the Insert Baan Fields dialog box:
Icon Reference
Key fields
Non-repeating tables
Fields from non-repeating tables
Repeating tables
Fields from non-repeating tables appear in your template as a single field. For
repeating table fields, Excel inserts multiple rows for each selected record.
After you add all table fields for the template, you must click Insert to create
the template.
Figure 3-19 Insert Baan Fields dialog box in Excel
In Excel, you have additional options. Under Field Attributes, you can specify
the attributes for each database field. You have the following options:
n Write.
In the Baan Excel workbook, the end user can change data that is based on
the Baan-related template. The changes are copied to BaanERP.

3-15
n Group by.
The field can be used to group data.
To copy data back to BaanERP system, you must define the key fields in the
Baan-related template. A unique key identifies each record in Baan. The unique
key consists of one or more key fields. For example, the key fields for a sales
order line are Sales Order Number and Position Number.
Under Location, you can specify the exact location for each field in the Excel
spreadsheet. Typically, for a new template, you do not specify an exact location.
The fields are default positioned beginning in the spreadsheet’s top-left corner.
You can always reposition the fields in Excel.
You can start the Insert Baan Fields dialog box from Excel’s Insert menu. .
Add Table dialog box

The Add Table dialog box appears when you click Add Table in the Insert
Baan Fields dialog.
The Add Table dialog box shows a history of the BaanERP tables you have
used previously in a Baan-related template. If the BaanERP table you want to
use is not listed, click More Tables to view a list of all the available BaanERP
tables that you can use in your template in the Table Definitions
(ttadv4526m000) session in BaanERP.
Figure 3-20 Add Table dialog box

3-16
Baan Field Properties dialog box

Use this dialog box to view and maintain the properties of the BaanERP table
field in the template.
Figure 3-21 Baan Field Properties dialog box
On the Properties tab (see Figure 3-21), you can view the BaanERP field’s
label and bookmark as used in the Excel template and workbook. BaanERP uses
the bookmark BaanERP to relate the BaanERP field to its table. Do not change
the bookmark.
If you select the Group by this field check box, the BaanERP field is used to
group data.
If you select the Write this field to Baan check box, the end user can change
data in the Excel/BaanERP workbook that is based on the Baan-related
template. Changes in the workbook are copied to BaanERP.
Figure 3-22 Baan Field Properties dialog box

3-17
The Path tab (see Figure 3-22) displays the path of the BaanERP table field to
its parent BaanERP table field. Fields from non-repeating tables appear in your
template as a single field. Fields from repeating tables are shown in Excel by
multiple rows for each selected record in your Excel/BaanERP workbook. You
can use this dialog box to view and maintain additional details of a BaanERP
table field in the BaanERP-related Excel template.
The following icons can be shown on the Path tab:
Icon Represents
Key fields
Non-repeating tables
Fields from non-repeating tables
Repeating tables
You can start the Baan Field Properties dialog box from the Insert Baan
Fields dialog box or the Excel menu. In the Insert Baan Fields dialog box,
under Selected Fields, select the BaanERP table field and right-click the
selected field. A shortcut menu appears, on which you can choose Properties.
To view the properties of a BaanERP field in Excel, right-click the field in the
template. On the shortcut menu, click the Baan Field Properties ( ) button.
Filter on Baan Fields dialog box

You can use the Filter on Baan Fields dialog box to define filters for BaanERP
table fields in the BaanERP-related Excel template. In this dialog box, you can
select a field and specify the BaanERP table field’s filter criteria. You can
specify the following value types as criteria:
n Fixed value, for example, order status equals open. The end user cannot
change a fixed value criterion.
n Cell value, for example, order status equals Sheet1!$A$3. The end user can
specify the exact criterion by defining the cell value.
Filtering is especially useful for a Baan-related template that is made available
to the users in Excel. By default, all records from the table you select are used
when Excel generates an Excel/BaanERP workbook. If you specify a filter for
the Baan-related template, you can specify which records must be inserted from
the BaanERP table.

3-18
If the end user starts from Excel, all BaanERP records are used to generate the
Excel/BaanERP workbook. If the end user starts from a BaanERP session, then
by default all records that the end user selects are used to generate
Excel/BaanERP workbook. However, you can specify a filter to only use those
records from the user's selection that comply with particular criteria. Only
records that match these criteria are then used to generate Excel/BaanERP
workbooks.
You can only filter on fields you add to the template; therefore, you cannot filter
on fields that are not available in your template. In this dialog box, you can
select a field and specify a criterion for the field. You can use two types of
values as a criterion in a filter:
n Fixed value, for example, order status equals open. The end user cannot
change a fixed value criterion.
n Cell value, for example, order status equals Sheet1!$A$3. The end user can
specify the exact criterion by defining the cell value.
If you use a fixed value as a criterion in a filter, end users cannot see that the
template filters the BaanERP data. You must indicate the use of fixed values in
the template. For example, if you specify in your filter that the order status must
equal active, you can include the following text in your template: This template
contains only orders with status active.
NOTE If you specify a criterion for a field, the field's name appears in bold in the Field
area in the Filter on Baan Fields dialog box (see Figure 3-22).
Figure 3-23 Filter on Baan Fields dialog box
The Field area displays the fields in the BaanERP table for which you can
specify a filter. You can select a field, and then, under Only include records
where:, define the filter criteria. In the Field area, the fields for which a filter is
appear in bold.
To combine more than one criteria for the selected BaanERP table field, you
must click And. To define at least one criteria for the BaanERP table field, click
Or.

3-19
To create a filter, or to edit an existing filter, on the Excel Tools menu, point to
Baan Template, and click Filter ( ). The Filter on Baan Fields dialog box
appears.
New Baan Workbook dialog box

End users can use this Excel dialog box to select the template that they want to
use to create a new workbook. Excel generates an Excel/Baan workbook based
on the template that you select.
To start the New Baan Workbook dialog box (see Figure 3-24), on Excel’s
File-menu, click the New Baan Workbook ( ) option.
Figure 3-24 New Baan Workbook dialog box

3-20
3.2 BaanERP eMessage Connector

The BaanERP eMessage Connector consists of the following components:
n A repository.
n A message log.
n An address database.
Additional eMessage Connector sessions can be started not with the BaanERP
main menu, but with:
3.2.1 BaanERP eMessage Connector repository
The Repository holds information about the services and service providers that
the eMessage Connector can use. You can use the repository sessions to enter
and update services and services providers.
If BaanERP receives a message, it first determines the type of message service
required. BaanERP uses the Address Types by Service (ttcmf0140m000)
session for this.
After BaanERP knows what type of message service to use, it refers to the
Services (ttcmf0130m000) session to determine what type of service provider to
use. BaanERP then uses the Service Providers (ttcmf0110m000) session to link
the message to the correct 4GL connector.
Before you can use eMessage Connector, you must enter the relevant
information regarding message services and service providers. Values for these
service providers are entered into the following Repository sessions:
n Service Providers (ttcmf0110m000)
n Provider Parameters (ttcmf0120m000)
n Services (ttcmf0130m000)
n Address Types by Services (ttcmf0140m000).
NOTE To enter values for Outlook, you must run the ttcmfinit script, typically at
installation.

3-21
Service Providers (ttcmf0110m000)

You can use this session to link each connector to a particular provider. The
value that you enter in the 4GL connector field must exist in the Sessions
(ttadv2506s000) session.
Figure 3-25 Service Providers (ttcmf0110m000)
In the Provider field you must enter the name of the service provider. In the
4GL Connector field, you must enter the session name of the BaanERP 4GL
connector process that is associated with the selected provider.
If you click the Provider Parameters command on the Specific menu, you can
start the Provider Parameters (ttcmf0120m000) session, which you can use to
maintain the parameters for the provider.
Provider Parameters (ttcmf0120m000)

You can only start this session from the Service Providers (ttcmf0110m000)
session. You can use this session to specify the startup parameter values for a
particular connector in the Parameter Value field.
Figure 3-26 Provider Parameters (ttcmf0120m000)

3-22
The eMessage Connector uses the 4GL Connector to automatically fill in the
provider parameters when the Provider Parameters (ttcmf0120m000) session
starts. You cannot use this session to add new parameters. However, you can
change existing parameter values.
Services (ttcmf0130m000)
You can use this session to specify the available services, and the providers that
support these services. Note that only one provider for each service environment
is permitted. BaanERP creates the message storage path directory and the inbox
and outbox subdirectories after you save each entry.
Figure 3-27 Services (ttcmf0130m000)
In the Service Name field, you must enter the name of the service offered by a
provider. In the Provider field, you can type or select the service provider. To
enable the service, you must select the Enabled check box.
If you select the Logging check box, the messages sent by this service are
logged to the message log, which is displayed in the Message Log
(ttcmf1500m000) session.
In the Message Storage field, you must enter the path to the directory where
messages from this service are stored. In this directory, inbox and outbox
subdirectories are created.
BaanERP can use the eMessage Connector to send reports. In the File Type
field, you must select preferred attachment type for the service. The report is
converted to the selected format. You can select for BaanERP the following
formats:
n Plain Text ASCII.
n Postscript.
n RTF.
n HTML ASCII.
n HTML Unicode.
n Plain Text Unicode.

3-23
Address Types by Service (ttcmf0140m000)

You can use this session to set up the link between an address type and the
address type’s service type. You can also use this session to specify whether
you see the message before BaanERP forwards the message.
Figure 3-28 Address Types by Service (ttcmf0140m000)
In the Address Type field, you must enter a valid eMessage Connector address
type. You have the following options:
n SMTP.
n FAX.
n Telex.
n SITA.
n SMS.
To enable additional user interaction before the message transfer is complete,
you must select the UI Required check box. In other words, the user can
change the messages before the message is sent. For example, the Outlook
connector enables user interaction
You can select the Resolve Capability check box to enable the service shown
in the Service Name field to find the address when only the user’s name and
address type are specified. The resolve capability functionality is only supported
by Outlook.
In the Service Name field, you must type or select the service and paper type or
the address type.
Daemon Groups (ttcmf3100m000)

The eMessage Connector daemon handles the delivery reports that external
service providers send to BaanERP. The daemon updates the message log to say
whether the message was successfully delivered or not.
Daemons are divided into groups, with each group residing on an individual
BaanERP Virtual Machine. BaanERP sends the delivery reports to the
ttcmfnotify daemon on which the BaanERP Virtual Machine is running.
ttcmfnotify must therefore be started once for each BaanERP Virtual Machine.

3-24
In addition, the delivery reports use the default address of ttcmfnotify running in
the current company of the user (ttcmfnotify.<comp_nr>.<hostname>).
Therefore, for each application host, there must be a notification daemon
running for each company so that BaanERP can handle the notifications from
the printer dialog.
You can use this session to maintain, view, and print daemon groups. BaanERP
uses one or more daemon group names as startup parameters, and then activates
the corresponding daemons using the service name, company number, and
address as parameters.
You can use the command line to start the Daemon Starter on NT or UNIX, for
example:
bshell -server ttcmfdaemon saturn
The command in the example activates all the 3GL daemon programs in the
saturn group on the bshell. The -server option causes the bshell to run without a
user interface. You can also use separate VMs to write a UNIX script to start
multiple groups. You can place the UNIX script in the BaanERP rc.start script
so that the eMessage Connector daemons are invoked automatically when you
start BaanERP.
Figure 3-29 Daemon Groups (ttcmf3100m000)
In the Daemon Group field, you must enter a name for the daemon group.

3-25
Daemons (ttcmf3110m000)
You can use this session to maintain, view, and print daemons. BaanERP uses
daemons to handle the delivery reports that external service providers send to
BaanERP. The daemon updates the message log to say whether the message
was successfully delivered or not.
Figure 3-30 Daemons (ttcmf3110m000)
To set this daemon into a logical sequence in the daemon group, you must enter
a unique number in the Sequence Number field. In the Session field, you can
enter a session that must be linked to the daemon. You can use this session to
access a session that does not have a user interface, for example, ttcmfdaemon.
In the Service Name field, you must type or select service to which the daemon
connects when the eMessage Connector starts. In the Company Number field,
you can type or select the company in which the daemon must start.
In the Inbound Address field, you must specify the address the daemon uses to
connect to eMessage Connector when it starts. If you leave this field empty,
BaanERP uses the address in the format
session_code.company_number@hostname.
3.2.2 BaanERP eMessage message log
The BaanERP eMessage Connector logs all incoming and outgoing messages as
they are processed. You can view the incoming and outgoing messages with the
following sessions:
n Message Log (ttcmf1500m000)
n Delete Message Log (ttcmf1200m000)
n Message Log by Service Name (ttcmf1501m000)
n Message Log by Application Name (ttcmf1502m000)
You can view the messages grouped by BAAN message ID, by service name, or
by application name.

3-26
Message Log (ttcmf1500m000)

The Message Log (ttcmf1500m000) session contains a log of all the processed
messages, and their status. The BAAN message ID corresponds to the
subdirectory name in which the message parts are stored so that you can retrieve
the actual message. External messages are assigned a Baan message ID in
addition to retaining their external ID.
You can sort messages according to the Time Stamp, BAAN ID, or External ID.
The Message Log (ttcmf1500m000) session appears in the overview session
mode.
Figure 3-31 Message Log (ttcmf1500m000)t
You can double-click a message in the grid to view the message details as
shown in Figure 3-32.
Figure 3-32 Message Log Details (ttcmf1500m000)
The Message Log Details session (ttcmf1500m000) shows the message details.
This session also enables you to click Attachments to view any attachments
that are sent with the message, and to click Recipients to view the listed
message recipients.
The Baan Message ID field displays the unique message ID of the message in
BaanERP. The Baan message ID corresponds to the directory name where the
serialized message components are stored. The message ID is a string with a
maximum of 40 characters. The first 10 characters in the string is the UTC date
and time (number of seconds since Jan 1, 1970 converted to a string) followed
by a period (.). The next group of characters in the string, up to a maximum of
five, denotes the bshell pid followed by a period (.).

3-27
The next group of characters in the string, up to a maximum of three, denotes

the bshell process ID followed by a period (.). The following group of
characters in the string, up to a maximum of three, denotes a counter in case of
multiple transactions per second (max 999) followed by a period (.). The last
group of characters in the string represents the first characters of the server’s
hostname.
The Application Name field displays the name of the BaanERP application that
sent or handled the message.
The Time Stamp field shows the date and time in UTC at which the message
was originally obtained by the BaanERP eMessage Connector.
If the message is originated in an external system, the External/Original ID
field displays the unique message ID of the message in the external system.
The Status field displays the current status of the message, from the point of
view of the connector. The possible values are:
n Message Received.
n Message Sent.
n Message Error.
n Reply Received.
n Reply Sent.
n Reply Error.
The Status Time field displays the time at which the message status was
reported. The Status Message field displays additional information about the
message’s status, for example, an error message or the message ID of a reply
received
Delete Message Log (ttcmf1200m000)

To delete messages, you must specify ranges on the BaanERP ID, external ID,
service name, application name, and time stamp. If you delete a message, the
database entry and all associated disk files are removed.
Figure 3-33 Delete Message Log (ttcmf1200m000)

3-28
Message Log by Service Name (ttcmf1501m000)

You can use the Message Log by Service Name (ttcmf1501m000) session to
view the messages grouped by service name. This session has the same
functionality as the Message Log (ttcmf1500m000) session.
Figure 3-34 Message Log by Service Name (ttcmf1501m000)
For information about the fields in this session, refer to “The Message Log
(ttcmf1500m000),” previously in this chapter. The Message Log by Service
Name (ttcmf1501m000) session, however, has one additional field. The
Message Direction field shows whether the message was inbound to the bshell
or outbound from the bshell. Inbound messages are stored in the inbox
subdirectory of the message storage directory. Outbound messages are stored in
the outbox subdirectory of the message storage directory.
Message Log by Application Name (ttcmf1502m000)

You can use the Message Log by Application Name (ttcmf1502m000) session
to view the messages grouped by service name. This session has the same
functionality as the Message Log (ttcmf1500m000) session.
Figure 3-35 Message Log by Application Name (ttcmf1502m000)
For information about the fields in this session, refer to “Message Log
(ttcmf1500m000),” previously in this chapter. The Message Log by Application
Name (ttcmf1502m000) session also has the Message Direction field, as
described for the Message Log by Service Name (ttcmf1501m000) session in
the previous section.

3-29
3.2.3 BaanERP eMessage address database
The address book enables you to easily retrieve addressing information about
users. The BaanERP eMessage Connector Address Book stores addressing
information in a central location. This enables applications to both display a list
of addresses and to determine the address for a particular recipient.
The data access layer (DAL) object for the address book contains functions to
enable you to easily add, modify, and delete recipient information. BaanERP
applications also use the DAL functions to update the address book whenever
relevant information changes.
You can also build distribution lists from the entries in the address book. The
distribution lists enables you to easily set up multirecipient messaging.
The BaanERP eMessage addressing functionality contains the following
sessions:
n Address Book (ttcmf2100m000)
n Distribution Lists (ttcmf2110m000)
Address Book (ttcmf2100m000)

You can use this session to view the listed entries in BaanERP’s address book
and to add a new entry.
You cannot delete an entry if the entry is still present in other tables. If the entry
can be deleted, the DAL removes the entry automatically from all distribution
lists. In addition, if you double-click an entry in the Distribution List category,
the Distribution Lists (ttcmf2110m000) session starts, which displays the
members of the selected list.
Figure 3-36 Address Book (ttcmf2100m000)

3-30
In the Address Book (ttcmf2100s000) details session, you can fill in the new
entries data, or update existing entries.
Figure 3-37 Address Book (ttcmf2100s000)
In the Category field, you can enter the category of the entry. The Category
field is a free form text field with no constraints, so you can develop your own
categories. The initial categories are Employee, Business Partner, BaanERP
User, and Distribution List. The category Distribution List is reserved and you
cannot add records to this category.
In the Key field, you can enter a new key, for example an abbreviation of a
person’s name, jsmith. Note that the combination category/key must be unique.
In the Display Name field, you can enter, or enable BaanERP to enter, the full
name of the recipient to which the entry applies, which in this example is John
Smith.
In the E-mail Type field, you can define the address type of the e-mail address,
for example, SMTP, X400, Lotus Notes, ccMail Novell Messaging, or
Microsoft Mail. In the E-mail Address field, you can specify the recipient’s
e-mail address. BaanERP checks the validity of the e-mail address based on the
e-mail type.
In the Telephone Number field, you must enter the absolute telephone number
of the recipient, including the country code. The format must be a plus sign (+),
followed by the country code, and then the number. For European and other
countries with similar schemes, omit the zero at the beginning of the number.
For example, +31342428888 is valid. The recipient’s fax-number can be
specified in the same manner in the Fax Number field.
Other recipient addresses include the Telex address, SITA address, and SMS
address. SITA addresses can take two formats. The first format consists of three
uppercase alphabetic characters, followed by four alphanumeric characters. The
second format consists of a number sign (#) followed by six uppercase
alphanumeric characters.

3-31
In the Default field, you must enter the recipient’s default address. BaanERP
uses the default when an application does not specify how a message must be
sent to the user. If you use a default message type, you must also supply an
address for that type. You can also leave this field empty, which means that this
user has no default message type.
The data in the Address Book (ttcmf2100s000) session is also used in the
BaanERP user’s user profile. The user’s profile is defined in the User Data
(ttams1100s000) session. You can start this session through the User Data
(ttaad2500m000) session.
Distribution lists (ttcmf2110m000)

You can use this session to create and maintain distribution lists. You can also
create nested distribution lists.
To create a distribution list, you must click the New Group icon and name the
list in the List Name field.
Figure 3-38 Distribution lists (ttcmf2110m000)
In the Display Name column, you can type or select a recipient that must be
added to the distribution list. In the Address Type field, you can choose, for
example, to send the message to the recipient by e-mail. You can choose more
than one address type for each recipient.
To create a nested distribution list, create a new distribution list. In the Display
Name column, enter the name of the distribution list that you want to include.

3-32
3.2.4 Additional BaanERP eMessage Connector sessions
The sessions described in this section are not listed in the BaanERP’s main
menu. You can start the described sessions through other BaanERP sessions.
Select Device (ttstpsplopen)

You can print eMessage Connector reports from any print session in BaanERP.
In the Select Device (ttstpsplopen) session, the Send Message tab is introduced,
which contains fields that enable you to identify the message, specify delivery
options for the message, and enter information about the recipients.
You can start this session from any print-enabled session in BaanERP. After
you define the report data that must be sent, you can click Print to start the
Select Device (ttstpsplopen) session. On the Send Message tab, you must enter
the data relevant to sending the report.
Figure 3-39 Select Device (ttstpsplopen)
In the Subject field, you can enter a brief description of the report. The
description appears in the recipient’s mailbox as the subject of the message. The
Categories field is currently only supported for Outlook. This field contains a
comma-delimited list of the categories to which the message belongs.
Under Delivery Options, you can specify the report’s message properties. In
the Priority field, you must specify the priority of the message. The possible
values in this field are Low, Normal, or High. The default priority setting is
Normal. In the Sensitivity field, you can specify the message’s sensitivity. The
possible values in this field are Normal, Personal, Private, Confidential, and
Secret. The default sensitivity setting is Normal.
In the Deliver After field, you can specify after what time the message must be
delivered. If you leave this field empty, the message is delivered immediately.

3-33
In the Expire After field, you can specify at what time the message must
expire. If you leave this field empty, the message never expires.
In addition, in the Notification field, you can enter the message’s notification
options. The possible values in this field are Always, Delivery, Non Delivery,
or Never. The default notification option is Non Delivery.
The BaanERP eMessage Connector enables you to add a message to the report.
If you click Message, a text editor appears, which you can use to compose the
message. If you select the Show message before sending check box, you can
preview the message before the message is actually sent. You can use this
option for a client-side service, for example, Outlook.
Under Fax Options, you can specify the data required for fax messages only. In
the Template Code field, you can enter a predefined template to be used for the
fax message. In the Charge Code field, enter the charge code for this message.
The charge code determines who will be charged for sending/receiving this
message.
Recipient List (ttcmf2120m000)

The Recipient List (ttcmf2120m000) session enables the user to build a
recipient list for messages to be sent. To start this session from the Select
Device (ttstpsplopen), you must click Recipients on the Message tab.
To use this session to build a recipient list, you must zoom to an address book
or enter the information manually. If you change the address type for a recipient
in the list, the address book is accessed and the address corresponding to the
new type is placed in the Address field. If no address is found for the new
address type, the address field remains clear.
Figure 3-40 Recipient List (ttcmf2120m000)

3-34
In the Role field, you must specify the recipient’s role. You can use the
following options:
n The To option, in combination with the name in the Name field, specifies
the message’s principal addressee.
n The CC (copy) option, in combination with the name in the Name field,
specifies to whom the message must be copied.
n The BCC (blank copy) option can be used to copy the message to an
addressee. The addressee will remain anonymous to other addressees listed
in the CC list.
n The OBO (on behalf of) option is not supported. You cannot send messages
on behalf of others.
In the Type field, you can specify the means to send the message, for example,
e-mail, fax, SMS, or SITA. If the recipients address does not appear in the
Address field, you must enter the recipients address manually.
3.3 Application Response Measurement (ARM)

For the Application Response Measurement (ARM) module in BaanERP, the
following new sessions are introduced:
ART Parameters (ttaad6102s000)

BaanERP’s Virtual Machine (VM) provides the 4GL Engine with the
Application Response Time (ART) functions that can be used to log times of
transactions. The 4GL Engine starts and stops these transactions while
performing specific tasks.
You can use the ART parameters to measure and monitor the performance of
the Baan application and find any bottlenecks. ART provides you information
that will help you tune your application in the best way possible.
After you initialize the Application Response Time (ART) parameters in Baan,
and install a third-party tool, such as HP Openview or Tivoli (IBM), you can
use BaanERP’s Application Response Measurement (ARM).
System administrators can use this session to set a system’s ART parameters for
the transactions in a BaanERP environment for which the application response
time (ART) measurement must be activated.
In this session, the system administrator defines the system’s ART parameters,
such as the server as it is known in the third party ARM tool and on which the
BaanERP environment runs, and the BSE environment variables. The system
administrator can enable ART measurement for the following transactions:
n Application transactions.
These transactions can be built into session scripts, DALs, and BOIs by
4-GL programmers. For more information about this transaction, refer to
the online Help.

3-35
n All Standard transactions.

These transactions are all transactions measured by the 4GL-Engine when a
specific form command is activated.
n Specific Standard Transactions.
This transaction is the same as the All Standard Transactions, but the
System-administrator can choose which ones are measured.
Note If you select the Specific Standard Transactions check box, the Choose
button is enabled. This button enables you to turn individual 4GL commands on
or off in the Standard Transactions Measured with ART (ttaad6101s000)
session.
Figure 3-41 ART Parameters (ttaad6102s000)
Standard Transactions Measured with ART (ttaad6101s000)

The system administrator can use this session to view and maintain a list of
4GL transactions in session for which the ARM is enabled. This session is
enabled if the Specific Transactions check box in the ART Parameters
(ttaad6102s000) session is selected.
You can enable ARM for the following 4GL engine transactions in a session:
n Form command.
This command measures the time of the execution of specific form
commands when a user activates the commands. The time between the start
of before.choice (if available) until the end of the form command function is
measured.
In the Session/Function field, zoom to the Form Commands
(ttadv3518m000) session to activate ART for a specific form command.

3-36
n Read record(s).
The 4GL Engine reads a record set from the session main table, for
example, when you start a session when the grid in an overview session is
refreshed. This time is clocked when the option is activated.
n Update record(s).
After the user finishes modifying a record, the modification must be
checked and the record must be written to the database. This time will be
measured for all records together. The number of records is passed to ARM
as a metric.
n Insert record(s).
After the user finishes inserting a record, the modification must be checked
and the record must be written to the database. This time will be measured
for all records together. The number of records is passed to ARM as a
metric.
n Delete record(s).
If the user deletes a record, the record must be deleted from the database.
This time will be measured for all records together. The number of records
is passed to ARM as a metric.
Figure 3-42 Standard Transactions Measured with ART (ttaad6101s000)
In the Session field, you must type or select a session, and in the Transaction
Type field, you can select one of the listed transaction types. If you have
selected Form command, you can, in the Session/Function field, select the
form command or session for which ART must be enabled.

3-37
3.4 BaanNT Manager

The Baan NT manager snap-in for the Microsoft Management Console (MMC)
provides the tools to manage the Baan Software Environments (BSE) on your
system. For more information on the MMC, refer to “BaanERP snap-ins for
Microsoft Management Console (MMC)” in Chapter 1, “New concepts in
BaanERP tools.”
The Baan NT manager lists the Baan environments on your system (see
Figure 3-43). You can independently administer the displayed BSEs.
Figure 3-43 Baan NT manager
The Baan NT manager shows the following generic services for every BaanERP
installation, which you can enable or disable:
n BaanLogic Service.
n BaanERP Licensing.
The Baan NT manager shows the following services for every BSE, which you
can enable or disable:
n Shared Memory Service.
n Job Daemon Service.

3-38
3.4.1 Baan Logic Service
Use the Baan Logic Service to configure the Baan connection protocols. The
Baan Logic Service connects the Baan Windows (BW) client to the BaanERP
server and checks whether the user has the authorization to connect to the Baan
server. With the Baan Logic Service, you can start/stop the Baan Virtual
machine (VM) and the database driver.
The Baan Logic Service offers you the following methods to connect to the
Baan server:
n Rexec.
The standard remote execution protocol. Rexec does not use passwords
encryption.
n Baan login.
Encrypts the Baan password of the users.
n Security Support Provider Interface (SSPI)
Only available on Windows NT and later. SSPI makes single-sign-on (SSO)
available for BaanERP.
Single sign-on
BaanERP Tools 7.1a uses Microsoft’s Security Support Provider Interface
(SSPI) to enable single sign-on for end users in a network environment. Single-
sign-on (SSO) is a mechanism whereby a single action of user authentication
and authorization can permit users access to all computers and systems where
they have access permission, without the need to enter multiple passwords.
If you trust the user for delegation, the user can connect to another system and
use that system to connect to a third system. In other words, with single sign-on,
the end users enter their password only once.
SSO does not use passwords, but uses the Windows NT user authentication.
With SSO, users are no longer required to perform multiple logons, nor are the
users required to remember multiple passwords to access network resources.
The user logs on once on Windows NT, and no further passwords are required.
All SSO-specific information is stored in a single repository, the Active
Directory, which provides a single, authoritative listing of each user’s rights and
privileges. You can change a user’s privileges and the results will be distributed
network wide.

3-39
3.4.2 BaanERP Licensing Service
With the BaanERP Licensing Service, you can enable or disable your BaanERP
license. The tools to license and validate your Baan installation are not part of
the BaanERP Licensing Service. To license your Baan installation, refer to
“License management and validation,” in the BaanERP 5.0c Administrator’s
Guide (U7189A US for pre-Service Pack 6 or U7189B US for Service Pack 6).
If your Baan installation is licensed and validated, the BaanERP Licensing
Service is automatically enabled. If you disable the BaanERP Licensing
Service, you cannot use BaanERP. To use BaanERP if it is disabled, but you
have a license, you must enable the BaanERP Licensing Service.
3.4.3 Shared Memory Service
With the Shared Memory Service, you can configure BaanERP’s shared
memory. The shared memory is a part of the physical memory intended for
common use. Programs communicate with each other with shared memory. The
use of shared memory results in faster access to the components loaded in
shared memory. Before you start the application, you must initialize and set up
the shared memory. The following components can be loaded into shared
memory:
n Report objects.
n Program objects.
n Table definitions.
3.4.4 Job Daemon Service
With the Job Daemon Service, you can enable or disable BaanERP’s job
daemon. The job daemon runs permanently on the BaanERP server. If a job is
present, the job daemon activates the job at the job’s scheduled time.
Note If you use the Application Services Manager (ASM) to start and stop a job
daemon in BaanERP environment, you must stop and disable the Job Daemon
Service for that BaanERP environment.
3.5 MS Windows Performance Monitor

BaanERP publishes BaanERP specific performance indicators in the MS
Windows Performance Monitor, which is a graphical tool that you can use to
measure the performance of your local computer and network computers. With
the MS Windows Performance Monitor, you can view the behavior of objects,
such as processors, memory, cache, threads, and processes. Each of these
objects has an associated set of counters that provide information about device
usage, queue lengths, delays, and information used to measure throughput and
internal congestion.

3-40
The MS Windows Performance Monitor provides charting, alerting, and

reporting capabilities that reflect both current activity and ongoing logging. The
following overview lists how you can use the MS Windows Performance
Monitor to view the performance of objects:
n View the BaanERP system and environment counters.
n View data from any number of computers simultaneously.
n View, and dynamically change, charts to reflect current activity and to show
counter values that are updated at a user-defined frequency.
n Export data from charts, logs, alert logs, and reports to spreadsheet or
database programs for further manipulation and printing.
n Add system alerts that list events in the Alert Log. To notify you, the charts
can revert to Alert view, log the event in Event Viewer's Application log, or
issue a network alert.
n Run a predefined program either every time or only the first time a counter
value goes over or under a user-defined value.
n Create log files that contain data about objects on various computers.
n Append selected sections of existing log files to a single file, to form a long-
term archive.
n View current-activity reports or create reports from existing log files.
n Save individual chart, alert, log, and report settings, or save the entire
workspace setup to reuse when required.
3.5.1 BaanERP specific performance counters
BaanERP publishes the following BaanERP-specific performance counters in

the MS Windows Performance Monitor.
n Baan Environment Counters:
− Shared Memory Uptime.
− Shared Memory Attachments.
− Shared Memory In Use.
− Shared Memory Size.
n Baan System Counters (pre-Service Pack 3 versions):
− Incorrect Login attempts (total/per minute).
− The number of aborted processes (total/per minute).
− BaanERP licenses (in use).
− BaanERP license uptime.
− BaanLogic Service uptime.

3-41
n Baan System Counters (Service Pack 3 and later versions):

− Incorrect Login attempts.
− Incorrect Login attempts per second.
− Process terminations in Baan.
− BAAN IV licenses.
− BAAN IV licenses in use.
− BaanERP licenses.
− BaanERP licenses in use.
− Baan ERP Licensing Service total.
− BAAN IV Licensing Service uptime.
− BaanLogic Service uptime.
− Process terminations in Baan Tools per second.
You can view these performance counters in charts. You can also use the MS
Windows Performance Monitor to create alerts that are activated if a BaanERP
specific performance counter exceeds a predefined limit. For example, if more
than 100 BaanERP users are logged in a BaanERP environment, an alert can be
triggered to inform the BaanERP system administrator.
3.6 NetChange
The components required to set up, use, and manage NetChanges are positioned
in the following BaanERP components:
n Database management.
n NetChange Server management.
The components in Database management are not changed in BaanERP 5.0c.
NetChange Server management is a new menu in the BaanERP 5.0c main
menu. The following components are used to set up, and maintain net changes:
n Stores (danch3510m000) overview
n Stores (danch3510m000) details
n Subscriptions (danch3120m000)
n Stores by Subscriptions (danch3125m000)
n Servers (danch2510m000) overview
n Servers (danch2510m000) details
n Start/Stop Servers (danch2210m000)
Stores (danch3510m000)
You can use this session to list stores. A store contains all changes or net
changes on a business object type. A store can only hold one type of object. For
example, a store cannot contain both items and sales orders, unless the sales
orders are regarded as subordinates to the items.
You must set up stores before you can configure the server. You can create and
maintain stores in the Stores (danch3510m000) details session.

3-42
If you delete a store, all periods, changes, stores by subscription, and retrieval
runs that refer to the store are deleted. If the store does not contain any (net)
changes, you can edit the metadata text.
Figure 3-44 Stores (danch3510m000)
Stores (danch3510m000)
You can use this session to create and maintain stores. In the Store ID field,
specify a unique store identifier, and in the Store Description field, specify a
logical name or description of the store. In the Change Mode field, you can
select the store’s change mode. You have the following options:
n Changes.
Each change is logged separately. The advantage of the Changes options is
that all changes are logged separately, although this can affect the size of
the store and the performance of the system. The Change mode is useful if
you want to create one store, from which more than one client can retrieve
both changes and net changes.
n NetChanges.
Subsequent changes for the same store are merged with existing changes.
For example, if a value first changes from 100 to 300 and then to 150, the
net change tells you that the value changed from 100 to 150. Note that in
this mode only, one client can retrieve the net changes.

3-43
You must select the Meta Data check box to create net changes. The metadata
for the objects shows what tables, for example, business object and
subordinates, are involved, and what the primary key for each table is.
The store must be able to determine whether two changed entities actually are
the same. This check is performed by means of a comparison of the primary key
fields. The metadata text for the store contains the tables and primary key fields
in XML format. The structure of the metadata is specified as shown in
figure 3.46.
Figure 3-46 An example of the text editor with metadata structure
In the Change Folder field, you can enter the pathname of the directory that
contains the storage files. The Table Number field specifies the sequence
number of the table that must be used to store the changes. Note that multiple
stores can use the same table number. However, for large stores, for best results,
you must use separate tables, because as tables grow, performance can decrease.
You can only use the Freeze Time field if you select Changes in the Change
Mode field. The freeze time defines after what time a period must be frozen. If
you set a freeze time, take into account that purging of stores is carried out for
each period. In the Freeze Time Unit field, you can define freeze time units,
such as hours, days, or weeks that are valid for the Freeze Time field.
Note You can only specify a freeze time if the mode of the store is net changes. You
must then specify the length of the freeze time period in number of hours, days
or weeks. The default freeze time is one week.

3-44
Subscriptions (danch3120m000)
You can use this session to list and maintain subscriptions. A subscription is a
group of stores that contain interrelated data for which the retrieval must be
synchronized. If a store contains net changes, you can only use the store in one
subscription. If a store contains changes, you can use the store in multiple
subscriptions.
If you delete a subscription, the stores by subscription, requests, and retrieval
runs for that subscription are also deleted.
Figure 3-47 Subscriptions (danch3120m000)
In the Subscription ID field, you can define an identifier for the subscription,
and in the Subscription Description field, you can specify a logical name or
description for the subscription.
The Default Timeout for Requests field defines the default maximum time, in
milliseconds, that the process must wait for periods to be closed when the
process creates a new request.

3-45
Stores by Subscriptions (danch3125m000)

You can use this session to view the stores that are grouped in a subscription.
You can also use this session to link stores to a subscription.
Note A store that contains net changes can only have one subscription.
Figure 3-48 Stores by Subscriptions (danch3125m000)
The Subscription ID field shows the subscription to which you can add stores.
In the Store ID field, the stores are shown that are grouped in the subscription.
Servers (danch2510m000) overview session

You can use this session to list servers. To maintain servers, you can use the
Servers (danch2510m000) details session. A server reads transactions that
contain relevant changes, processes those changes, and sends the changes to a
store.
Figure 3-49 Servers (danch2510m000) overview
If you update the settings of a running server, changes to the store ID, scope, or
library are only effective when the server is stopped (or interrupted) and
continued, or restarted. If you change the server settings while the server is
running, you will receive a warning that explains the risks. If you change the
store ID while the server runs or has run, data is written into different stores. As
a result, each of the stores only contains a subset of the data, while no store
contains the complete data set.

3-46
Before you can use this session, you must set up the stores in the Stores
(danch3510m000) details session.
Note You can only delete servers that are not running. Deleting a server will also
delete the server runs, but will not affect the store.
Figure 3-50 Servers (danch2510m000) details
In the Server field, you can define a unique identifier for the server, and in the
Server Description field you must enter a logical name or description of the
server. The Used Store field specifies store to which the server’s output must be
sent.
The Scope field defines the store’s scope. You have the following options:
n Normal.
Only changes are processed and sent to the store.
n Complete Family.
Changes are processed, but subordinates that are not changed, such as order
lines, are also added. Only use the Complete Family mode if unchanged
parts of the business object are essential, because of the impact this mode
has on the performance of the NetChange Server.
The Server Library field defines the library that contains the server
functionality that is specific to the server. In other words, functions to select
data from the tables and columns that must be included, functions to read
related data, and functions to perform the filtering, formatting, or transforming
of data, if required. The Run Status field shows the status of the server.

3-47
Start/Stop Servers (danch2210m000)

Use this session to start or stop a range of servers that are created in the Servers
(danch2510m000) session. If you choose to start the server at a specified
commit time, the server can start at a point other than at the end of the previous
run, which can result in missing data or logging duplicate errors by the store.
You can start/stop the server immediately, or you can add the process to a job,
to run regularly. You can use jobs to run one or more servers using specified
intervals, or run the start command regularly to automatically continue
interrupted servers.
Figure 3-51 Start/Stop Servers (danch2210m000)
Under Selection Range, you can define a range of servers that must be started
or stopped. With options available in the Action Type field you can start or stop
the servers. In the Start Time field, the following options are available:
n Process transaction since.
Use this option to start the server for the first time.
n Continue from previous run.
Choose this option if you want to start the server automatically as part of a
job.
The Start Commit Time field defines the start commit time, which indicates
the start of the commit time interval specified for the server process. Note that
the NetChange Server only processes changes that are made to a business object
after the specific Start Commit Time. Importantly, for stores in the same
subscription, the servers that write to those stores must have the same Start
Commit Time.
The Polling Frequency field specifies the number of retries per second. The
value in this field indicates how often the server will retry to collect new data if
no data is available. Choose a low value to reduce system load.
The Log File field specifies the path to the directory of the log file.

3-48
3.6.2 Additional NetChange Server management sessions
This section describes additional sessions in NetChange Server management.

These sessions can be categorized in:
n Store-related sessions.
n Server-related sessions.
Store-related sessions
The following list describes the additional store-related sessions, and, where
required, includes a short explanation of the session:
n Print Stores (danch3410m000)
n Periods (danch3515m000)
This session provides an overview of the periods. You cannot make changes
in this session.
n Print changes (danch4400m000)
You can use this session to print the (net) changes for one store in a
specified range of period numbers, and commit times or transaction IDs.
The output is grouped by period.
n Print Periods (danch3415m000)
n Print Subscriptions (danch3420m000)
n Print Stores by Subscription (danch3425m000)
n Subscription by Store (danch3526m000)
This session provides an overview of the subscriptions in which a store is
used. You cannot make changes in this session.
n Requests (danch3530m000)
This session provides an overview of the requests grouped by subscription.
In a request, a client application indicates when the application wants to
retrieve the next set of (net) changes for a subscription. You cannot change
the requests. A details session is available to view more attributes of a
request.
n Print Requests (danch3430m000)
n Retrieval Runs (danch3535m000)
This session provides an overview of the retrieval runs. A retrieval run is
the actual retrieval of (net) changes from one store by a client application.
These changes are grouped by Subscription by Store. You cannot change
the retrieval runs. A details session is available to view more attributes of a
retrieval run.
n Print Retrieval Runs (danch3435m000)

3-49
n Purge Requests (danch3230m000)

You can start this session from the Requests (danch3530m000) session, and
you can use this session to purge the changes in periods of a store that is
used in a subscription.
n Purge Stores (danch3210m000)
You can start this session from the Stores (danch3510m000) session, and
you can use this session to purge the changes of periods for one store or a
range of stores.
Server-related sessions
The following list provides the additional server-related sessions, and, where
required, includes a short explanation of the session.
n Print Servers (danch2510m000)
n Server Runs (danch2520m000)
This session provides an overview of the server runs. You cannot change
the server runs. The following fields are displayed in this session:
− Server ID.
− Run Number.
− Status: Running, Stopped, or Interrupted.
− Run Start Time.
− Run End Time.
− A details session is available to view more attributes of a server run.
n Print Server Runs (danch2420m000)
n Purge Server Runs (danch2220m000)
You can use this session to purge the log of server runs for a range of
servers. Note that you cannot purge the last run of a server if the run has the
status Running. If you specify that the last run for servers must also be
purged, and the last run is within the range specified, a warning is given and
you are asked to confirm this action. However, note that confirming this
action can have negative consequences, because if you restart the server,
you can lose data or duplicate errors can be logged by the store.

3-50
3.7 Application Services Manager (ASM)

The ASM is an administrative tool that you can use to stop and/or start
BaanERP application services.
You predefine in XML files, the application services that the ASM can start,
and stop.
An application service defined to be stopped and/or started by the ASM is
called an instance. An instance can have one of the following occurrence types:
n Unique.
You can only run one occurrence of the instance’s application service at a
time. That is, if the instance’s application service is running, you must stop
the instance before you can restart the instance. However, you can define
any number of Unique instances that start, and stop the same application
service and run the instances simultaneously. For example, you can define
three instances that start job daemons (each for a different Baan company),
and run the instances simultaneously.
n Multiple.
You can have multiple occurrences of the instance’s application service
running at the same time.
For the Baan Software Environments (BSEs) installed on the server where the
ASM is running:
n You can use the ASM to start and stop BaanERP application services
defined for Unique occurring instances.
n The ASM can start BaanERP application services defined for Multiple
occurring instances when requested by external software module users. The
ASM does not stop these application services. The user, not the ASM, uses
the external software module to stop the application service. For example,
the ASM can start Baan OpenWorld Adaptors on request for any number of
Baan OpenWorld users. Baan OpenWorld stops the Baan OpenWorld
adaptor when commanded by the user.
3.7.1 To define the ASM’s XML Files
You must use the following BaanERP sessions (location: BAAN Tools
Application Configuration Application Services Manager) to create XML
files that define the instances of BaanERP application services the ASM can
start, and, for unique instances only, stop. For more detailed descriptions of
these sessions refer to Chapter 16 “Application Services Manager (ASM),” in
the BaanERP 5.0c Administrator’s Guide (U7189B US).
Note n On a UNIX server, the Baan Software Environment (BSE) whose Baan
sessions you use to create the ASM’s XML definition files must be the
same BSE where the server’s BaanLogin is located. However, with that
BSE’s sessions, you can still define instances for any BSE on the server.

3-51
n On an NT server, you can use any BSE’s sessions to create the ASM’s
XML definition files. However, to avoid duplication of instances, and to
avoid having to redefine data (templates and BSEs), you must use the same
BSE. With one BSE’s sessions, you can define instances for all BSE’s on
the server.
Baan Software Environments (ttaad0570m000)

Use this session (see Figure 3-52) to define the Baan Software Environments
(BSE) in which the ASM can start and stop application services.
Figure 3-52 Baan Software Environments (ttaad0570m000)
For the BSEs you define in this session, you can define instances in the ASM
Services Instance (ttaad0574m000) session.
ASM Service Templates (ttaad0573m000)

Use this session to define templates that can:
n Start and stop a BaanERP application service for Unique occurring
instances, or:
n Start a BaanERP application service for Multiple occurring instances.
Figure 3-53 ASM Services Templates (ttaad0573m000) overview

3-52
In the details session (see Figure 3-54), you can define data to start and stop an
application service. In the ASM Service Instances (ttaad0574m000) session,
you select a template from this session, which provides default data on starting
and stopping an instance’s application service. If you maintain a template’s
data, the fields that default to the ASM Services Instance (ttaad0574m000)
session of instances that use the template also change.
Figure 3-54 ASM Services Templates (ttaad0573m000) details
ASM Services Instance (ttaad0574m000)

Use this session to define the instances of application services the ASM can
start, and, for Unique instances only, stop.
Figure 3-55 ASM Service Instances (ttaad0547m000) overview

3-53
On the General tab of the details session (see Figure 3-56) you can define
whether an instance’s occurrence is Unique, or Multiple, select a BSE from the
Baan Software Environments (ttaad0570m000) session, and select a template
from the ASM Service Templates (ttaad0573m000) session. For Unique
instances, you must define the Start up mode, which can be Automatic (started
automatically when you start the ASM), or Manual (started manually by a user).
Figure 3-56 ASM Services Instance (ttaad0574m000) details, General tab

3-54
The fields on the Start and Stop Command tab of the details session (see
figure 3-57), contain data on starting and stopping the instance’s application
service. The defaulted data on this tab comes from the template you selected in
the Template field of the General tab.
Figure 3-57 ASM Services Instance (ttaad0574m000) details, Start and Stop Command tab

3-55
Convert ASM to Runtime (ttaad0270m000)

Use this session to convert your newly defined data into the XML definition
files, asmtypedef.xml for the template data, and asminsdef.xml for the instance
data. The files are located in the directory $BSE/lib. You must also run this
session if you have maintained existing instances, and templates.
Figure 3-58 Convert ASM to Runtime (ttaad0270m000)
Note At startup, the ASM reads the XML files from the $BSE/lib directory, and
stores the files in memory. While running, the ASM uses the XML files in
memory to start and stop the defined instances, although not the XML files, in
the $BSE/lib directory. As a result, if you use the Baan sessions to make
changes to the XML definition files in the $BSE/lib directory with the ASM
running, you must stop and start the ASM for your changes to take affect.

3-56
3.8 Exchange through the Data Access Layer (DAL)

To enable Exchange through the Data Access Layer (DAL), you can use the
following new check boxes in the Table Relations (Import) (tuxch0121s000)
session:
n Import via Data Access Layer.
n DAL Property Checks.
Figure 3-59 Table Relations (Import) (tusch0121s000)
To enable the data import through the Data Access Layer, you must select the
Import via Data Access Layer check box. If you import data through the
DAL, you carry out the additional checks or actions, which are specified in the
DAL, for each row that is imported.
If you select the Import via Data Access Layer check box, you enable the
DAL Property Checks check box. You can select the DAL Property Checks
check box to carry out the property checks of the Data Access Layer. Running
the property checks is a safe option, however the property checks also affect
performance. Not using the DAL property checks can be used as a performance
booster.
Note Selecting or deselecting the DAL related check boxes is an aspect of run time
that you can change without having to regenerate the import program. For that
reason, the DAL settings are also logged in the log table at batch line level, to
be able to check the DAL settings as the settings appeared at the moment the
import was run.

3-57

3-58
4. Procedures related to BaanERP Tools
This chapter describes the new or changed procedures related to the following
new concepts in BaanERP Tools for BaanERP 5.0c.
n Integration of Microsoft Office applications in BaanERP.
n The BaanERP eMessage Connector.
n Application Response Measurement ARM.
n Baan NT Management.
n The Microsoft Management Console (MMC).
n Active Directory Services (ADS).
n NetChange Server Management.
n Application Services Management.
4.1 BaanERP Office integration solution

Before you can use the Office integrations in BaanERP, you must install several
components on the BaanERP server and the client.
4.1.1 BaanERP Office integration solution installation on the

BaanERP server
Before you can use the Office integrations in BaanERP, you must take the
following steps on the Baan Server:
n Set the Baan Generic Automation Server parameters.
n Set the Microsoft Office Parameters.
n Copy the base template to the server directory (pre-Service Pack 6 versions
only).

4-1
Procedures related to BaanERP Tools
Set the Baan Generic Automation Server parameters

You must set the Baan Generic Automation Server parameters for each
company in your Baan environment. You can set these parameters in the Baan
Generic Automation Server Parameters (asint0100s000) session, as shown in
Figure 4.1.
Figure 4-1 Baan Generic Automation Server Parameter (asint0100s000)
Set the Microsoft Office parameters

You must set the Microsoft Office parameters for your Baan environment. The
Office parameters are applicable to all companies in your Baan environment
and can be set in the Office Parameters (ntint0500m000) session, as shown in
Figure 4.2.
Figure 4-2 Office Parameters (ntint0500m000)
Copy the base template to the server directory (pre-Service Pack 6

releases only)
The base template contains the customizations to the menu bar and toolbars that
you require to customize the Microsoft Office applications and to create your
own templates. The base template is delivered on the BaanERP CD-ROM in the
ServerBaseTemplate.zip file. You must unzip the ServerBaseTemplate.zip file
and copy the following base templates to the server directory that is specified in
the Office Parameters (ntint0500m000) session:
n Baan-Related Excel Template (Base.xlt).
n Baan-Related Word Template (Base.dot).
For the Service Pack 6 release, this procedure is not necessary, because the base
template is installed on the client.

4-2
4.1.2 The BaanERP Office integration solution installation on the

client
The Baan - MS Office Integration is supported on the following (client)

platforms:
n Windows 98.
n Windows NT 4.0.
n Windows 2000.
Two different client installations for the BaanERP Office integration solution
are available:
n Tools template designer (called Baan Field Mapper Setup in pre-Service
Pack 6 releases). Contains the whole toolkit for the template designer and
the components to create runtime Baan Excel workbooks based on the
designed templates.
n Tools end users (called Office Document Creator Setup in pre-Service Pack
6 releases). Contains only the components to create run time Baan Excel
workbooks based on the Baan-related templates designed by the template
designer.
As a template designer, you must complete the Tools template designer Setup
procedure (Baan Field Mapper Setup for pre-Service Pack 6 releases). End users
must complete the Tools end users Setup procedure (Office Document Creator
Setup for pre-Service Pack 6 releases).
Note n You must install the Baan Generic Automation Server on the client, before
you run the setup.
n You must close all running Microsoft Office applications, before you start
the installation.
n You can modify the configuration of Excel during installation.
n After installation you must reboot the client.
Tools Template Designer Setup (Baan Field Mapper Setup in

pre-Service Pack 6 releases)
The Tools template designer setup executable (Baan Field Mapper setup
executable) contains all the client components that the template designer needs
to design Baan-related Word and Excel templates. The end users use templates
to create Word documents and Excel workbooks that are based on the Baan-
related templates.
To install the Tools template designer (Service Pack 6 releases) application on
your client, on the BaanERP CD-ROM, locate the BaanERP –Microsoft Office
Integration folder and run the setup.exe.

4-3
To install the Baan Field Mapper (pre-Service Pack 6 releases) on the BaanERP
CD-ROM you must locate the BaanFieldMapper.zip file, which contains a
zipped Setup.exe. You must unzip the BaanFieldMapper.zip file and run the
Setup.exe to install the client application.
Both the Tools template designer Setup, and the Baan Field Mapper Setup also
run Microsoft Office Template Installer.exe, which checks the client.
The Office Template Installer also installs the following add-inns:
n Microsoft Excel - BaanBaseAddin.xla.
n Microsoft Word - New Baan Template.dot.
The Excel add-inn enables you to create Baan-related Excel templates and
Baan-related Excel workbooks in Excel. The Word add-inn to create Baan-
related Microsoft Word templates.
Tools End Users Setup (Office Document Creator Setup in pre-

Service Pack 6 versions)
The Tool End Users (Office Document Creator) setup executable contains all
the client components the end user needs to create Microsoft Word documents
based on the templates that are designed by the template designer.
To install the client application you must first run the setup.exe. Setup also runs
Word Template Installer.exe, which checks the client.
4.1.3 To transfer the BaanERP data to Word
Before the end users can create Word documents that contain BaanERP data,
the template designer, typically a key user with experience with the BaanERP
functionality, must define the Baan related template for Word.
In the Baan-related template, the template designer can specify the BaanERP
tables and table fields that must appear in the Word documents that are based on
the Baan-related template.
When the Baan-related templates are created, the template designer must
publish the templates to make them available to the end -users. The Baan-
related template is then available to all sessions that use the BaanERP tables
that are defined in the Baan-related template.

4-4
The steps in the procedure to transfer data to Word documents are shown in
Figure 4-3.
1. Create a Baan-related template

Template
• Create a new Microsoft Word template.
designer
• Relate the template to a Baan table.
• Specify the BaanERP table fields that must be used in the
template.
• Add formulas, text, and so on, to the template.
2. Publish the Baan-related template

• Make the templates available to all end-users.
• Specify the BaanERP sessions where the template must
be available.
End user
3. Generate documents based on the Baan-related template
• Select records in a session.
• Select the template.
• Generate documents based on the selected records, and
on the selected Baan-related template.
Figure 4-3 Procedure to transfer BaanERP data to Word
For a detailed description of the BaanERP Office integration procedures, refer

to the Microsoft Word Integration User Manual (U7193B US for pre-Service
Pack 6 versions, or U7193C US for service pack 6 versions).
4.1.4 To transfer the BaanERP data to Excel
Before the end users can create Baan/Excel workbooks that contain BaanERP
data, the template designer, typically a key user with experience with the
BaanERP functionality, must define the Baan related template. In the Baan-
related template, the template designer can specify the BaanERP tables and
table fields that must appear in the Excel/Baan workbooks that are based on a
Baan-related template.
When the Baan-related template is created, the template designer publishes the
templates to make them available to the end -users. The Baan-related template
is then available to all sessions that use the BaanERP tables that are defined in
the Baan-related template.

4-5
The template designer must also specify how the end user can create a new
workbook. The template designer can specify that end users can either use
BaanERP or Excel to create the workbook.
The steps in the procedure to transfer data to the Excel are shown in Figure 4-4.
1. Create a Baan-related template

• Create a new Microsoft Excel template.
Template • Specify the BaanERP table fields that must be used in
designer the template.
• Add formulas, text, and so on, to the template.
2. Publish the Baan-related template

• Specify where the template must be available for the end
users.
You can choose BaanERP and/or Excel.
• If the template must be available in BaanERP, you must:
- Specify the BaanERP sessions where the template must
be available.
- Make the template available to all end users in a company.
End user 3. Generate workbooks based on Baan-related templates
With BaanERP:
• Select records in a session.
• Generate the Baan/Excel workbooks based on the
selected records, and on the selected Baan-related
template.
With Microsoft Excel

• Generate workbooks based on the Baan-related
template.
Figure 4-4 Procedure to transfer BaanERP data to Excel
For a detailed description of the BaanERP Office integration procedures, refer

to the Microsoft Excel Integration - User Manual for End Users and Template
Designers (U7429A US for pre-Service Pack 6 versions, or U7429B US for
Service Pack 6 versions).

4-6
4.1.5 To work with the Excel Baan workbooks
The template designer must also specify the templates that are available to the
end users. The end users can use these templates to generate Excel/Baan
workbooks, in which you can add and modify BaanERP data. Typically, you
can use Excel or BaanERP to create Excel/Baan workbooks, which are based on
a Baan-related template.
When the workbook is generated, you can use all Excel functionality to
manipulate the data in BaanERP. You can write the changes that are made to
the BaanERP data back to BaanERP.
In Excel, the following options are made available if you work with an
Excel/Baan workbook:
n You can use the Read from Baan ( ) option on the Data menu in Excel
to load data from BaanERP into Microsoft Excel. The Undo Read from
Baan ( ) button on the Data Excel menu restores your workbook to the
workbook’s original settings before you read the data from Baan.
n You can use the Save to Baan ( ) option on the Data menu in Excel to
save the changes you made to the BaanERP data in Excel.
Note If errors occur when you save data to Baan, the Errors Saving to Baan dialog
box appears. In this dialog box, click Go to row to navigate to the row in the
workbook that produced the error.
n You can use the Delete on next Save to Baan ( ) option on the Data
menu in Excel to delete BaanERP data from the Excel environment. This
data is marked in the workbook and deleted the next time that you save to
Baan.
You can save a Baan workbook and open a Baan workbook as you usually do in
Excel. When you open a saved Excel/Baan workbook, the data in BaanERP can
change. Therefore, when you open a saved Excel/Baan workbook, you are
prompted to indicate whether you want to use the data of the Excel/Baan
workbook or whether you want to read the data from Baan into the workbook.

4-7
4.2 The BaanERP eMessage Connector procedures

Before you can use BaanERP’s message connector, you must complete the
following mandatory procedures:
n Set up the eMessage Connector repository.
n Define the address book data.
4.2.1 To set up the BaanERP eMessage Connector repository
You can use this procedure to create a repository for the BaanERP eMessage
Connector. The procedures describes how to set up:
n Service providers.
n Services.
n Address types for the services.
To define service providers

You can use this procedure to link each connector to a particular provider.
1 On the Baan Tools menu, select BaanERP eMessage Connector Ø
Repository Ø Service Providers. The Service Providers (ttcmf0110m000)
session starts.
Figure 4-5 Service Providers (ttcmf0110m000)
2 On the File menu, click New. In the Provider field and Description field,
enter the name and description of the new Outlook service provider.
3 In the 4GL Connector field, enter the session name of the BaanERP 4GL
connector process associated with the provider. In this example, use
ttcmfoutlook.

4-8
4 Select the new Outlook service provider and on the Specific menu, select
Provider Parameters. The Provider Parameters (ttcmf0120m000) session
appears.
Figure 4-6 Provider Parameters (ttcmf0120m000)
You must use the Provider Parameters (ttcmf0120m000) session to specify the
startup parameter for the Outlook service provider.
In the Parameter Value field, enter the service provider’s parameter value. In
this example, ${BSE}/bin/cmfuiadap.exe.
To define the services for the service providers

You must use this procedure to specify the available services and the providers
that support them. Only one provider for each service for each environment is
permitted.
BaanERP creates the message storage path directory and the inbox and outbox
subdirectories after you save each entry
Repository Ø Services. The Services (ttcmf0130m000) session appears.
Figure 4-7 Services (ttcmf0130m000)
2 On the File menu, click New. In the Service Name field and Description
field, enter the name and description of the service. In this example, you
create the Outlook service.
3 In the Provider field, type or select the name of a provider you have created
in the Service Providers (ttcmf0110m000) session.
4 Select the Enabled check box to enable the Outlook service.

4-9
5 In the Message Storage Path field, enter the path to the directory where
messages from this service must be stored. To enable logging, select the
Logging check box.
6 In the File Type field, type or select the default attachment file type for the
Outlook service. In this example, select PlainText Unicode. When
BaanERP sends a report with the eMessage Connector, the report is
converted to the format specified here.
To define the address types for the services.

Use this procedure to set up the link between an address type and a service. You
can also use this session to specify whether you see the message before
BaanERP forwards the message.
Repository Ø Address Types by Service. The Address Types by Service
(ttcmf0140m000) session appears.
Figure 4-8 Address Types by Service (ttcmf0140m000)
2 On the File menu, click New. In the Address Type column, enter a name
for the address type. In this example, e-mail and SMTP.
3 Select the UI Required check box if you want to be able to make changes
before the message is sent.
4 In the Service Name field, type or select the name of the service that must
be linked to the address type. Each service can have more than one address
type, which means that a service can appear on this list more than once.
Note In this session, the resolve capability option is optional.
At this point the BaanERP users can send messages that contain BaanERP data.
4.2.2 To set up the address book data
You can use this procedure to create the address book data. The procedures
describes how to set up:
n Address books
n Distribution lists

4-10
Address books
This procedure enables you to add and update entries in the address book. Use
the main session to add an entry and use the details session to fill in the
information or to update the entry.
Complete the following steps to enter a new address book entry.
Addressing Ø Address Books. The Address Book (ttcmf2100m000)
session appears.
Figure 4-9 Address Book (ttcmf2100m000)
2 On the File menu, click New. The Address Book Details (ttcmf2100s000)
session appears.
Figure 4-10 Address Book Details (ttcmf2100s000)
In this example, you add a new user, John Smith, to one of the BaanERP
supplied categories, the Baan user category.
3 In the Category field, enter the BAAN USER category.

4-11
4 In the Key field, you enter JSMITH, and in the Display Name field, you
enter the user’s name as it must be displayed. In this example, type John
Smith. Make sure that the combination category/key is unique.
4 Define John Smith’s e-mail data in the appropriate fields. In the E-mail
Type field, you can type or select SMTP, X400, ccMail, or Microsoft Mail.
5 Define John Smith’s telephone and fax data in the appropriate fields. For
the telephone number and fax number, enter the absolute telephone number,
including the country code. The format must be a plus sign (+), followed by
the country code, and then the telephone number. For European countries
and other countries with similar schemes, omit the zero at the beginning of
the number, for example, +31342428888.
6 Enter the telex, SITA, and SMS addresses if applicable.
7 In the Default field type or select John Smith’s default address type. In this
example, type email.
8 Click OK to return to the Address Book (ttcmf2100m000) session and save
the John Smith entry in the address book.
You can also build distribution lists from the entries in the address book. The
distribution lists enable you to easily set up multirecipient messaging.
Distribution Lists
You can use this procedure to create distribution lists to enable messages to be
sent to groups of users. You can also create nested distribution lists.
1 On the Baan Tools menu, click BaanERP eMessage Connector Ø
Addressing Ø Distribution lists. The Distribution lists (ttcmf2110m000)
session appears.
Figure 4-11 Distribution lists (ttcmf2110m000)

4-12
In this example, you create a list that can be used to send a message to a
group of developers.
2 On the Group menu, click New and in the List Name field, type
DEVELOPER as the distribution list identifier.
3 On the File menu, click New, and in the Display Name field, you can enter
the names of the persons that must be included in the developer list.
4 In the Address Type field, type or select the address type for the users. You
can choose more than one address type for each recipient
5 Continue adding users until the distribution list is complete and save the
distribution list.
NOTE To create a nested distribution list, create a new distribution list. In Display
Name, enter the name of the distribution list that you want to include. Continue
adding recipients until the distribution list is complete.
4.3 Application Response Measurement procedures

To use ARM, you must initialize the ART parameters. To enable or disable
ART for the entire Baan Software Environment (BSE), you must read the
environment variable BAAN_ART_ENABLE. The variable
BAAN_ART_ENABLE determines whether the ARM libraries are loaded at
bshell startup and, therefore, determines whether ART is enabled or disabled.
n To enable ART, set the variable to the number 1.
n To disable ART set the variable to the number 0.
You must adjust your BW Configuration properties and set the
BAAN_ART_ENABLE variable.

4-13
On the Bshell Environment tab, in the Command field, enter the following
command line: --set BAAN_ART_ENABLE=1.
Figure 4-12 BW Configuration Properties dialog box
4.3.1 To enable ART measurement for specific transactions
If a new Baan system is installed, ART is not enabled for any transaction. You
must add the transactions for which you want to activate ART. To activate the
ART parameters for a certain transaction, you must add the transaction to the
list of ART enabled transactions in the Standard Transactions Measured with
ART (ttaad6101m000) session.
NOTE The list shows only the transactions or form commands whose response times
are measured.

4-14
The following procedure describes how to fill in the various group boxes.
1 On the Baan Tools menu, select Application Configuration Ø
Parameters Ø ART parameters. The ART parameters (ttaad6102s000)
session appears.
Figure 2 ART Parameters (ttaad6102s000)
2 Under System Parameters, in the System Description field, enter the

name of the Baan system, as the system is known in the third-party ARM
tool. The default name is BaanSeries.
3 In the BSE Description field, enter the name of the current Baan Software
Environment (BSE), as the BSE is known in the third-party ARM tool. This
field enables you to distinguish between various BSE installations.
4 Under Measuring Preference, select the transaction level for which you
want to enable ART. You have the following options:
− Application transactions.
The 4GL developers in session scripts, DALs, BOIs and 3GL-programs,
build in these transactions. For more information about this transaction,
refer to the online Help.
− All Standard transactions.
These transactions are all transactions measured by the 4GL-Engine if a
specific form command is activated.
− Specific Standard Transactions
This transaction is the same as the All Standard Transactions, but the
System-administrator can choose which ones are measured.
Note If you select the Specific Standard Transactions check box, the Choose
button is enabled. This button enables you to turn individual 4GL
commands on or off.

4-15
5 If you click Choose, the Standard Transactions Measured with ART

(ttaad6101m000) session appears.
Figure 3 Standard Transactions Measured with ART (ttaad6101m000)
6 In the Standard Transactions Measured with ART (ttaad6101m000) session,

you must select the sessions and transaction types you want to measure.
You can activate ART for the following 4GL engine transactions:
− Form command
This command measures the time of the execution of specific form
commands when a user activates the commands. The time between the
start of before.choice (if available) until the end of the form command
function is measured.
In the Session/Function column, zoom to the Form Commands
(ttadv3518m000) session to activate ART for a specific form command.
− Read record(s)
The 4GL Engine reads a record set from the session main table, for
example, when starting a session when the grid in an overview session
is refreshed. This time is clocked when the option is activated.
− Update record(s)
If the user finishes modifying a record, the modification must be
checked and the record must be written to the database. This time will
be measured for all records together. The number of records is passed to
ARM as a metric.
− Insert record(s)
If the user finishes inserting a record, the modification must be checked
and the record must be written to the database. This time is measured
for all records together. The number of records is passed to ARM as a
metric.

4-16
− Delete record(s)
If the user deletes a record, the record must be deleted from the
database. This time will be measured for all records together. The
number of records is passed to ARM as a metric.
7 Restart BaanERP to activate the settings of the ART parameters.
4.4 Baan NT management procedures

The Baan NT manager provides the tools to manage and administer BaanERP
on your system. With the Baan NT manager, you can:
n Enable, disable, start, or stop the following BaanERP generic services for
each system:
− Baan Logic Service.
− Baan License Service.
n Enable, disable, start, or stop the Baan software environments (BSE), which
include the:
− Shared Memory service of the current BSE environment.
− Job Daemon of the current BSE environment.
n Configure the Baan Logic Service.
n Configure the shared memory parameters.
n Rename BSE environments.
n Edit the BSE variables.
The following procedure describes how to enable, disable, start, or stop a
service.

4-17
4.4.1 To enable and start a BaanERP service
You can only start or stop a BaanERP-specific service if the service is enabled.
If the service is disabled, you must enable the service before you can start the
service. In this example, you will enable the BaanERP Licensing Service.
1 Click Start Ø Programs Ø BaanERP Ø Baan MMC NT Manager. The
Baan NT Manager appears:
2 In the Tree pane, click BaanERP Licensing. The status of the BaanERP
licensing Service is shown in the details pane as disabled.
3 In the details pane, click Enable this Service. The BaanERP Licensing
Service is now enabled. You can now start the BaanERP Licensing Service.
4 In the details pane, click Start Service. The BaanERP Licensing Service is
now running.
NOTE To stop a Baan-specific service, in the Tree pane, select the service, and in the
details pane, click Stop Service. To disable the service, click Disable the
Service in the details pane.
The following procedures describe how to start or stop a Baan software
environment (BSE).

4-18
4.4.2 To start a Baan software environment (BSE)
In this example, you will start the Baan Corelli BSE.

1 Click Start Ø Programs BaanERP Ø Baan MMC NT Manager. The
2 In the Tree pane, select Baan Corelli, and on the toolbar, click the Start
Service ( ) button. The Baan Corelli BSE is now running.
NOTE To stop the Baan Corelli BSE, select the Baan Corelli BSE in the console tree,
and then on the toolbar, click the Stop Service ( ) button. The Baan Corelli
BSE is now no longer running.

4-19
4.4.3 To configure the Baan Logic Service
To configure the Baan logic Service of a Baan Software Environment (BSE),

complete the following procedure:
1 Select Start Ø Programs Ø BaanERP Ø Baan MMC NT Manager. The
2 To configure the connection protocol logic of the Baan Corelli BSE, click
Baan Logic Service in the console tree, and on the toolbar, click the
Properties ( ) button.

4-20
The Baan Logic Service Properties dialog box appears:
Figure 4-16 Baanlogic Service Properties dialog box
3 On the Logic Service Protocol Configuration tab, review and update any
of the following options:
− Rexec.
Select this check box to use the standard remote connection protocol to
connect the Baan Windows (BW) client to the BaanERP server.
− Baanlogin.
Select this check box to use the Baanlogin connection protocol to
connect the Baan Windows (BW) client to the BaanERP server. The
BaanLogin protocol encrypts the BaanERP password of the users.
− SSPI.
Select this check box to use the Security Support Provider Interface
(SSPI) connection protocol to connect the Baan Windows (BW) client
to the Baan server. SSPI is only available on Windows NT or later and
makes Single Sign-on (SSO) available for BaanERP.
− TCP Port.
Enter the Transmission Control Protocol (TCP) port through which the

4-21
Baan Windows (BW) client connects to the BaanERP server. The

default port is 512, which you can change to comply with your specific
situation.
− User.
You must enter the name of the user if the Windows NT Active
Directory Service (ADS) must be used. The format of the user is:
NTDOMAIN\user. The Logic Service must log on as a user with access
to ADS. If ADS is not used, you can skip this field.
− Password.
Enter the user’s password. If ADS is not used, you can skip this field.
− If you have reconfigured the logic Service, click Apply to accept the
changes, then click OK to close the dialog box. You are prompted to
restart the Logic Service for the changed Logic Service parameters to
take effect.
You are returned to the Baan NT Manager.
5 Click Stop Service to stop the Shared Memory Service, and then click
Start Service to restart the Shared Memory Service.
NOTE If you trust the user for delegation, you must set the trust delegation in the
user’s properties. The user can then connect to another system and use that
system to connect to yet another system. To set the delegation trust, see the
following section.

4-22
4.4.4 To set the delegation trust for the user
To enable the user to SSO for all systems in your network, you must set the
delegation trust for the user.
1 Click Start Ø Programs Ø Administrative Tools Ø
Active Directory Users and Computers.
The Active Directory Users and Computers dialog box appears.
Figure 4-17 Active directory Users and Computers dialog box
2 In the Tree pane, double-click Users, and then, in the details pane, select a
user and click the Properties ( ) button.

4-23
The user’s properties window appears.
Figure 4-18 User Properties dialog box
3 On the Account tab, under Account options, select the Account is trusted
for delegation check box.
4 Click Apply to accept the changed user properties, and then click OK to
return to the Active Directory Users and Computers dialog box.
The user can now use SSO. Only the user’s Windows NT authentication is
required to use all the systems in the environment. If you do not trust the user
for delegation, the user can connect to another system but cannot use that
system to connect to yet another system.

4-24
4.4.5 To configure the Baan Shared Memory Service
To configure the Baan Shared Memory Service of a Baan Software

Environment (BSE), complete the following procedure:
2 To configure the shared memory of the Baan Corelli BSE, in the console
tree, click Baan Shared Memory Baan Corelli, and on the toolbar, click
the Properties ( ) button.

4-25
The Baan Shared Memory Properties dialog box appears:
Figure 4-20 Baan Shared Memory Properties dialog box
3 On the Shared Memory Config tab, review and update any of the
following options:
− Start address.
Enter the start address for the shared memory. The start address value
can range from 0x20000000 to 0x7FFEFFFF.
− Maximum Size (MB).
Define the maximum shared memory size allocated for BaanERP
applications.
− Load Shared Memory at Start up.
Select this check box to automatically load the shared memory server at
start up.
− Load as User.
Enter the BaanERP user that must load the shared memory objects.
− Show all messages.
Select this check box to view error messages and other messages while
loading the shared memory.

4-26
− Show Errors Only.

Select this check box to view only the error messages while loading the
shared memory.
− Silent.
Select this check box to suppress all messages while loading the shared
memory.
− Maintain shared memory timer.
Select this check box to enable the shared memory server update the
shared memory timer.
4 If you have reconfigured the shared memory, click Apply to accept the
changes, then click OK to close the dialog box. You are prompted to restart
the Shared Memory Service for the changed shared memory parameters to
take effect.
You are returned to the Baan NT Manager.
5 Click Stop Service to stop the Shared Memory Service, and click
Start Service to restart the Shared Memory Service.
Note The Loaded Shared Memory tab shows the loaded shared memory objects.
The Shared Memory Areas tab shows a list of the available shared memory
areas and their addresses.
4.4.6 To rename BSE environments
You must make sure that the BSE environments on your system are unique.
You can therefore rename if necessary. In this example, you will rename the
Corelli BSE into Verdi BSE.
2 In the Tree pane, click Baan Corelli, and on the Action menu, click
Rename. You can now rename the BSE in the console tree.

4-27
The following message dialog appears:
Figure 4-22 Confirm Operation message
You are warned about the consequences of renaming a BSE environment.

All external references to the environment in the Baan Windows
configuration (BWC) files must be updated. If you click Yes, the
environment-specific services are stopped and removed, and the
environment-specific services are installed and started for the renamed
environment.
3 Click Yes to confirm the renaming. The Baan Corelli BSE in now named
Baan Verdi.
4.4.7 To edit the BSE variables
You can use the Baan NT manager to change the behavior of the Baan tools by
editing the BSE variables. In this example, you will specify the BSE_SORT
variable for the Baan Corelli BSE environment. With the sort program, you can
specify a directory where the temporary files are stored during the sort process.
For information about environment variables, refer to the BaanERP Tools
Technical Manual (U7040EUS).
2 In the console tree, click Baan Corelli, and then, on the toolbar, click the
Properties ( ) button.

4-28
The Baan Corelli Properties dialog box appears:
Figure 4-24 BSE properties dialog box
3 In the Variable field, on the Environment tab, enter the BSE_SORT

variable.
4 In the Value field, enter the path to the directory where the temporary data
must be stored during the sort process.
5 Click Set to accept the new variable and then click OK to save the changes
and to close the Baan Corelli Properties dialog box.

4-29
4.5 MS Windows Performance Monitor procedures

You can use the MS Windows Performance Monitor to:
n View BaanERP Performance Counters.
n Set Alerts for BaanERP Performance Counters.
4.5.1 To View BaanERP Performance Counters
To use the MS Performance Monitor to view BaanERP performance counters:

1 On the Start menu of:
n Windows 2000, click either:
− Settings Ø Control Panel Ø Administrative Tools Ø Performance.
− Run: and type perfmon in the dialog box , and click OK.
n Windows NT, click either:
− Programs Ø Administrative Tools Ø Peformance Monitor.
− Run: and type perfmon in the dialog box, and click OK.
The MS Windows Performance Monitor appears (see Figure 4-25).
Note The performance monitor’s appearance differs slightly between Windows
2000 and Windows NT, however the functionality is the same. The
following figures show the Windows 2000 versions.
Figure 4-25 MS Windows Performance Monitor

4-30
2 Click on System Monitor in the Tree pane, then at the top of the details
(right) pane, click the Add ( ) button. The Add Counters dialog box
opens:
Figure 4-26 Add Counters dialog box.
3 By means of the Use local computer counters option or the Select

counters from computer: option, and the following drop-down list, select
the computer whose BaanERP counters you wish to use. The computer you
select must have a BaanERP environment installed as a fat client.
4 In the Performance object field, you can select either of the following
Baan objects you want to monitor:
− Baan Environment.
− Baan System.
Note You can only select these options if the computer selected in Step 3 has a
BaanERP environment installed as a fat client.
5 By means of the All Counters option or the Select counters from list
option, and the list under the option button, select the counters you want the
performance monitor to display.
Note You can only select the Baan Shared memory objects when the Baan Logic
service, and the shared memory service is running on the computer you
selected in Step 3 in the current procedure.

4-31
6 Click Add to start your selected counters, and click Close to close the
dialog box. The right pane of the performance monitor displays your
selected counter(s) as a line graph(s) with the details at the bottom of the
pane (see Figure 4-27)
Figure 4-27 MS Performance monitor with BaanERP counters

4-32
4.5.2 To set an alert in the MS Windows Performance Monitor
With the MS Windows Performance Monitor, you can create an alert that is
activated if a BaanERP specific performance counter exceeds a predefined
limit. In this example, you will create an alert that is activated if more than 100
BaanERP users are logged on to your BaanERP environment.
1 Open the MS Windows Performance Monitor (refer to Step 1 in the
previous section).
2 Double-click Performance Logs and Alerts, and then click Alerts.
Any existing alerts will be listed in the details pane. A green icon indicates
that the alerts are running; a red icon indicates alerts have been stopped.
3 Right-click a blank area of the details pane and click New Alert Settings.
The New Alert Settings dialog box appears:
Figure 4-28 New Alert Settings dialog box
4 In the Name dialog box, type the name of the alert. In this example, enter
Alert – Too many licenses in use and then click OK.

4-33
A dialog box appears, which you can use to define a comment for your
alert, along with counters, alert thresholds, and so on:
Figure 4-29 Alert Settings dialog box
Use the General tab to define a comment for your alert, along with
counters, alert thresholds, and the sample interval.

4-34
5 Click Add to select the appropriate counters. The Select Counters dialog
box appears:
Figure 4-30 Select Counters dialog box

4-35
6 In the Performance object list, type or select Baan System. In the listed
counters, select BaanERP licenses in use and then click Add and Close to
return to the alert settings dialog box.
Figure 4-31 Alert Settings dialog box
7 Enter the maximum accepted BaanERP licenses. In this example, no more

than 100 licenses are permitted. You can also select an interval that must be
used to check the number of licenses. You can use the Action tab to define
the actions that must occur if the counter data triggers an alert. On the
Schedule tab, you can define when the service must begin scanning for
alerts.
8 Click Apply and then click OK. The alert will now appear as a green icon
in the Alerts details panel.

4-36
4.6 ADS procedures in BaanERP

In BaanERP, you can use the following ADS procedures:
n Find the BaanERP environment information in ADS.
n Publish a UNIX server in BECS.
n Maintain the Baan Windows configuration properties.
4.6.1 To find the BaanERP environment information in ADS
At startup, the Baan Logic service publishes the connection points in ADS for
each environment on the server with information such as the name of the server
to connect to and the name of the BSE-environment. BW uses this information
to set up a connection to the server. The Baan Logic Service publishes the
services without any user interaction. In this example the NTDEV.baan.com
domain is used to explain ADSs features in BaanERP.
To find the environments in ADS, take the following steps:
1 Logon as an Administrator. If you log on using an account that does not
have administrative privileges, you might not be able to view the directory
objects.
2 Click Start Ø Administrative Tools Ø Active Directory Users and
Computers. The Active Directory Users and Computers window appears:
Figure 4-32 Active Directory Users and Computers window
The scope pane shows the NTDEV.baan.com domain. The System folder
contains the Active Directory systems and services information. The System
folder also contains the Baan folder in which the Baan Logic Service stores the
connection points of the servers in the domain. The connection points are stored
for each server in a dedicated folder.
Note The server names in a domain must be unique.

4-37
4.6.2 To publish a UNIX server in BECS
Typically, ADS is used for Windows NT servers. However, you can use the
BaanERP Active Directory Service setup utility to publish UNIX servers in the
Baan Environment and Configuration Selector (BECS). In this example, you
will publish the UNIX server saturn as OurGreatBaanEnvironment in BECS.
Complete the following steps to publish UNIX servers:
1 Logon as an Administrator. If you log on using an account that does not
have administrative privileges, you might not be able to use the directory
objects.
2 Click Start Ø Accessories Ø Command Prompt.
The Command Prompt window appears:
Figure 4-33 Command Prompt window
3 Type dssetup –publish OurGreatBaanEnvrionment saturn

/usr/baan/bse.
4 Click Start Ø Programs Ø BaanERP Ø BaanERP. The BECS – Baan
Environment and Configuration Selector window appears:
Figure 4-34 BECS – Baan Environment and Configuration Selector window
BECS now shows the OurGreatBaanEnvironment on the saturn.

4-38
4.6.3 To maintain the Baan Windows configuration properties
You can use the Baan Environment and Configuration Selector (BECS) to run
various Baan Windows versions on a single client. You can also use BECS to
start the Baan Windows Configuration Properties dialog box, which you can
use to maintain the configuration settings of the BaanERP environments on the
client. To maintain the client’s BaanERP environment properties, take the
following steps:
1 Click Start Ø Programs Ø BaanERP Ø BaanERP. The BECS – Baan
Environment and Configuration Selector window appears:
Figure 4-35 BECS – Baan Environment and Configuration Selector window
2 Select an environment and click the Configuration ( ) button on the

menu bar. The BW Configuration Properties dialog box appears:
Figure 4-36 Baan Windows Configuration Properties window.

4-39
3 Under Baan Service, you can choose to use an environment for which the
connection points are published in ADS. You can also choose to use an
environment for which the connection points are not published in ADS.
4 Click Published to use an environment for which the Baan Logic Service
has published the connection points in the ADS database. In the Published
list, you can select an environment for which the connection points are
stored in the ADS database. The Hostname, BSE, Protocol, and Port
number fields are automatically filled with the information retrieved form
the ADS database.
5 Click Private to use an environment for which the connection points are not
published in ADS. You must now enter the data in the Hostname, BSE,
Protocol, and Port number fields yourself.
For more information about how to use the BW Configuration Properties
window, refer to the Installation Guide for BaanERP Windows Client
(U7434AUS).
4.7 Net Change procedures in audit management

Before you can use the Net Change functionality, you must have data from the
audit server. This section supplies both general information regarding how to
enable auditing on tables, as well as specific information about the audit_set file
for Net Change. This section describes:
n Table management.
Contains a step-by-step description of how to enable auditing. In addition,
this section explains how to store information regarding nonprimary key
columns that are not changed.
n Net Change server management.
Contains a step-by-step description of how to set up and run a Net Change
server.
4.7.1 Table management
You must enable auditing on tables to use Net Change. You must also include
the storage of unchanged columns of a record that are not primary key columns.
For general information about audit management, refer to Chapter 14 of the
BaanERP Tools - Technical Manual (U7040E US).

4-40
To switch audit on/off for a table

To switch the auditing on tables on or off, you must complete the following
steps:
1 On the BaanERP Tools menu, click Database Management Ø Data
Definition and Directories Ø Tables by Database. The Tables by
database (ttaad4111m000) session appears:
Figure 4-37 Tables by database (ttaad4111m000)
2 On the File menu, click New, and add the tables that must be audited. You
can specify specific tables or groups of tables, for example, Tables in
module and All (other) tables. Note that you must select the Audit on
check box for each of the tables that you want to be audited.
3 On the Specific menu, click Convert to Runtime. This command results in
an update of the $BSE/lib/tabledef6.2 configuration file. As a result, the
tables that must be audited are added to the tabledef6.2 file.

4-41
4 On the BaanERP Tools menu, click Database Management Data

Definition and Directories Ø Audit File Directories. The Audit File
Directories (ttaad4116m000) session appears:
Figure 4-38 Audit File Directories (ttaad4116m000)
5 On the File menu, click New, and add the pathnames of the directory that
contains the audit trail for the tables that must be audited. You can specify
files for specific tables or groups of tables, for example, Tables in module
and All (other) tables.
NOTE The disk that contains the directories for the audit files must have sufficient
free disk space, because the sequence files that contain the audit data will
potentially consume a lot of space. The audit-data is split across multiple
sequence files, because otherwise the file would become too large to
manage properly. The maximum size of a sequence file for a table is
defined in the $BSE/lib/audit_spec file. If the limit is exceeded, the audit
server tries to use the next sequence file.
In addition, you must make sure that sufficient table space is available for
the Transaction Notifications (ttaud110) table.
6 On the Specific menu, click Convert to Runtime. This command results in
an update of the $BSE/lib/auditdef6.2 configuration file with the new
pathnames to the directories in which the sequence files that contain the
audit-data are stored.
7 To use the new configuration, users must leave BaanERP by closing all
client sessions and restart BaanERP.

4-42
To log unchanged columns

In a traditional audit configuration only the primary key columns and those
columns that are changed are written to the audit files. However, you can also
choose to include columns of a record that are not changed. You must use the
$BSE/lib/audit_set file to specify the tables for which additional columns must
be logged.
When the audit server starts, the server reads the audit_set file and stores the file
in a fast-access structure, such as a hash list.
Later, at run time, if the audit server writes an updated record to the audit trail,
the audit server searches the fast-access structure for an entry that matches the
table on which the update was done. The audit server searches first the table
level, then the module level, then the package level, and finally the all-package
level until a matching entry is found.
You can use the audit_set file to specify columns of tables, which are always
logged with every update row.
Several levels of detail can be given, for example, specifications for all
packages, all modules in a package, or all tables in a module. You can make
specifications for one company or all companies. In addition, you can specify
the column names of a table, in this case, not all but only those columns
specified are logged in addition to the changed columns. For each entry, you
must specify Y for extra columns being logged or N for no extra columns.
This results in the following levels of detail:
Level Description Example
1 Table name with company and column tccom110:812:Y:colm
2 Table name for all companies and column tccom110:*:Y:colm
3 Table name with company tccom110:812:Y
4 Table name for all companies tccom110:*:Y
5 Module name with company tccom:812:Y
6 Module name for all companies tccom:*:Y
7 Package name with company tc:812:Y
8 Package name for all companies tc:*:Y
9 All-package with company *:812:Y
10 All-package for all companies *:*:Y
Level 1 and Level 2 are column levels. Levels 3 through 10 are table levels.
An audit_set file for Net Change can, for example, look like the following:
cprpd100:667:Y:item
whwmd215:667:Y:stoc
whwmd215:667:Y:hall

4-43
Audit_set file example

The order line table ppmmm999, has a primary key (columns ordr and line) and
further attributes (columns item, quan, and pric). In the Tables by Database
(ttaad4111m000) session, this table has the Audit on check box selected.
For Line 1 of order 1001, the quantity of item ITM001, is updated from 4 to 6.
The price of ITM001 is 17.50.
If the audit_set file is empty, only the primary key columns and the updated
column are logged. The audit trail will contain the following data for this
update:
ordr: 1001
line: 1
quan (old): 4
quan (new): 6
If the audit_set file contains ppmmm999:*:Y:item, the audit trail will

contain the following data for this update:
ordr: 1001
line: 1
item: ITM001
quan (old): 4
quan (new): 6
If the audit_set file contains one of the following lines:

− ppmmm999:*:Y:item,pric
− ppmmm999:*:Y
− ppmmm:*:Y
As a result, the audit trail will contain the following data for this update:
ordr: 1001
Line: 1
Item: ITM001
Quan (old): 4
Quan (new): 6
Pric: 17.50

4-44
4.7.2 Net Change Server management
This section describes how to set up the Net Change Server with the following
procedures:
n To set up the store.
n Define subscriptions.
n To set up the Net Change Server.
Before you start to configure the Net Change Server, you must set up the stores.
To set up a store
The store is the object that contains all changes or net changes on a business
object type. Note that a store can only hold one type of objects. For example, a
store cannot contain both items and sales orders, unless the sales orders are
regarded as subordinates for the items. To set up a store that is enabled for net
changes, you must complete the following procedure:
1 On the NetChange Server menu, click Stores. The Stores
(danch3510m000) session appears:
2 On the File menu, click New. The Stores (danch3510m000) details session
appears:

4-45
3 In the Store ID field, specify a unique store identifier and in the Store
Description field a logical name or description of the store. In this example
you create mystore.
4 In the Change Mode field, you can select the store’s change mode. In this
example, choose NetChanges.
5 Select the Meta Data check box to create net changes. The metadata for the
objects shows which tables, for example, business object and subordinates,
are involved and what is the primary key for each table.
6 In the Change Folder field, enter the pathname of the directory that
contains the storage files.
7 In the Table Number field, enter the sequence number of the table that
must be used to store the changes.
8 You can only use the Freeze Time field if you select Changes in the
Change Mode field. In the Freeze Time Unit field, you can define freeze
time units, such as hours, days, or weeks that are valid for the Freeze Time
field.
9 After you supply the required values, save and close the session.

4-46
To define subscriptions
A subscription is a group of stores that contain interrelated data for which you
must synchronize the retrieval. A client can have multiple subscriptions. You
are advised to keep subscriptions small, because a subscription that contains
stores for which data is not, or is not required to be, synchronized is of little use.
To group stores in a subscription, you must complete the following procedure:
1 On the NetChange Server menu, click Subscriptions. The Subscriptions
Figure 4-41 Subscriptions (danch3120m000)
2 On the File menu, click New. In the Subscription ID field, enter the
identification of the subscription.
3 In the Subscription Description field, enter a logical name or description
for the subscription.
4 In the Default Timeout for Requests field, enter the default maximum
time, in milliseconds, that the process must wait for periods to be closed
when the process creates a new request.
After you supply the subscription’s required values, you must link the store
to the subscription.

4-47
5 Select subscription in the grid and on the Specific menu, click Stores by
Subscriptions. The Stores by Subscriptions (danch3125m000) session
appears:
Figure 4-42 Stores by Subscriptions (danch3125m000)
6 On the Group menu, click New Group, and in the Subscription ID field,
type or select the subscription’s identification, which in this example is
mysbs for My Subscriptions.
7 On the File menu, click New, and in the Store ID field, enter the
identification of the store that you want to link to the subscription, which in
this example is mystore.
8 Save and exit the session. This completes the setup of the store.
To set up the NetChange Server

After you create the store, you can set up the NetChange Server. A NetChange
Server is a program that can run to read transactions that contain changes that
are relevant, process those changes, and send the changes to a store.
To set up a Net Change Server, take the following steps:
1 On the Net Change Server menu, click Servers. The Servers
(danch2510m000) session appears. On the File menu, click New. The
Servers (danch2510m000) details session appears:
Figure 4-43 Servers (danch2510m000)

4-48
2 In the Server field, enter a unique identifier for the server, and in the
Server Description field, enter a logical name or description of the server.
3 In the Used Store field, enter the identification of the store to which the
server’s output must be sent.
4 In the Scope field, you can type or select the store’s scope. In this example,
choose Normal.
5 In the Server Library field, enter the library that contains the server
functionality that is specific for the server. In other words, functions to
select data from the tables and columns that must be included, functions to
read related data, and functions to perform the filtering, formatting, or
transforming of data if required.
6 After you supply the required values, you must save and close the session
and return to the Servers (danch2510m000 overview session.
7 In the Servers (danch2510m000 overview session, on the Specific menu,
click Start/Stop Servers. The Start/Stop Servers (danch2210m000) session
appears:
8 Under Selection Range, in the Server field, enter the created myserv
server.
9 In the Action Type field, select Start, and in the Start Time field, you
must select Process transaction since to start the server for the first time.
10 In the Start Commit Time field, specify the start commit time, which
indicates the start of the commit time interval specified for the server
process.
11 In the Polling Frequency field, enter the number of retries per second,
which indicates how often the server will retry collecting new data if no
data is available.
12 In the Log File field, enter the path to the directory of the log file and click
Continue.
Note The run status of the myserv server in the Servers (danch2510m000) session
will change to Running.

4-49
To enable the Net Change Server to start automatically, you must restart the
Servers (danch2510m000) session. In the grid, select myserv, and on the
Specific menu, click Start/Stop Servers. The Start/Stop Servers
In the Start Time field, click Continue from previous run, and click Make
Job. If you run this job, for example, every five to ten minutes, you can ensure
that the server is restarted in case of interruptions.
4.8 BaanERP system policy procedures

This section describes the BaanERP system policy options to centralize the
following configuration actions on the network domain controller instead of on
the local client:
n Password storage.
n BaanERP Windows (BW) configuration editing.
4.8.1 Password storage procedure
The procedure to enable or disable the password storage and retrieval is related
to a registry key setting under HKEY_LOCAL_MACHINE. By default, on a
person with system administrators rights can update this section of the registry.
The system administrator can disable the local storage of BW clients by taking
the following steps:
1 Log on as user with admin rights on the Windows NT server that is the
domain controller of the Windows network.
2 Copy the C:\Program Files\Baan\Lib\bw.adm file (from a BW client) to the
directory C:\WINNT\INF on the domain controller.
3 Start the System Policy Editor.
4 Click Policy Template on the Options menu.
5 Click Add, and select C:\WINNT\INF\bw.adm.

4-50
6 Click Open. The C:\WINNT\INF\bw.adm is added in the Policy

Template dialog box. Select this entry and click OK.
7 Click the Open Policy command on the File menu in the System Policy
Editor dialog (or New Policy if you want to add a policy).
8 Select the systems (or groups of systems) for which you want to disable
local password storage, and click the Properties command on the Edit
menu.
9 Disable local storage as shown in the following figure and click OK.
Figure 4-46 Default Computer Properties dialog box
4.8.2 BaanERP Windows (BW) configuration edit procedure
The system administrator must complete the following steps to disable local
configuration editing:
1 Log on as user with admin rights on the Windows NT server that is the
domain controller of the Windows network.
2 Copy the C:\Program Files\Baan\Lib\bw.adm file (from a BW client) to the
directory C:\WINNT\INF on the domain controller.
3 Start the System Policy Editor.

4-51
4 Click Policy Template on the Options menu.

5 Click Add, and select C:\WINNT\INF\bw.adm.
6 Click Open. The C:\WINNT\INF\bw.adm is added in the Policy
Template dialog box. Select this entry and click OK.
7 Click the Open Policy command from the File menu in the System Policy
Editor dialog (or New Policy if you want to add a policy).
8 Select the user (or groups of users) for which you want to disable local
configuration editing, and click the Properties command on the Edit menu.
9 Disable local configuration editing as shown below and click OK.
Figure 4-47 Default User Properties

4-52
4.9 Application Services Manager (ASM) procedures

The ASM is an administrative tool that can start, and stop BaanERP application
services. You must use the following Baan sessions the to create XML files for
the ASM which define the application services the ASM can start and stop:
n Baan Software Environments (ttaad0570m000)
n ASM Services Templates (ttaad0573m000)
n ASM Services Instance (ttaad0574m000)
n Convert ASM to Runtime (ttaad0270m000)
For information on how to use these sessions to define the ASM’s XML files,
refer to “To define the ASM’s XML Definition Files,” in Chapter 3, “New
Functionality in Baan Tools.”
4.9.1 To run the ASM
To start or stop the ASM:

n On a Windows NT platform, use NT Service Manager.
n Unix platform, use the rc script for the BaanLogin, stored in the $BSE/etc
file. The ASM daemon starts when you start the BaanLogin.
When you start the ASM:
n The ASM starts all Unique occuring instances whose startup you defined as
Automatic in the ASM Sevice Instances (ttaad0574m000) session.
n The ASM awaits for, and executes, commands to start or stop the
application services defined for Unique occuring instances.
n The ASM awaits for, and executes, commands from users of external
software modules to start BaanERP application services defined for
Multiple occurring instances. The users (not the ASM) stop these BaanERP
application services, using their external software module.
When you stop the ASM:
n The ASM stops all Unique occuring instances that are still running.
n Any Multiple instances still running are not stopped. Multiple instances
must be stopped by the user of the external software module that requested
the ASM to start them.
The port number through which the ASM receives commands, and provides
responses, is determined by the search path:
n The Port Number you define when you start the ASM.
n If you do not define a Port Number at start-up, ASM uses the Port Number
defined for the logical name BaanLogin, in the etc/services file.

4-53
n If no Port Number is defined for the logical name BaanLogin, ASM uses
the default port number 7150.
4.9.2 ASM User Interface
n You can send commands to, and receive responses from, the ASM by
means of a:
− Microsoft Management Console (MMC) loaded with an ASM snap-in.
− Command prompt, which communicates with the ASM’s command line
interface.
n Through the ASM’s API interface, users of external software modules can
command the ASM to start a multiple occurring instance’s BaanERP
application service.
NOTE You cannot use the MMC, or the command prompt to start the ASM.
MMC loaded with an ASM snap-in

By means of the MMC loaded with an ASM Snap-in (see Figure 4-48), for any
BSE in your domain you can:
n View, start, or stop, the unique occurring instances defined for the ASM.
n View the multiple occurring instances defined for the ASM. You cannot
start, or stop any multiple occurring instances.
Figure 4-48 MMC with ASM snap-in
Note Any user with an ASM snap-in can command the ASMs in their domain. For
best results, you must restrict the availability of the ASM snap-in software to
trusted users.
For details of sending commands to the ASM by means of the MMC loaded
with an ASM snap-in, refer to “ASM User Interface,” in Chapter 16,
“Application Services Manager (ASM)” in the BaanERP 5.0c Administrator’s
Guide (U7189B US).

4-54
Command prompt
With a command prompt, you can send commands to the ASM by means of a
Command Line Interface. You can:
n Start, stop, and view the unique occurring instances defined for the ASM in
any of your domain’s BSEs.
n View the multiple occurring instances defined for a host.
Note n Do not start a multiple occurring instance with the command prompt.
Multiple occurring instances must only be started by (users of) external
software modules.
n Any user with a command prompt can send commands to the command line
interfaces of the ASMs in their domain. For every server in your domain
that has a BSE, you must restrict the access, and execute permissions in the
directory ${BSE}/bin, to trusted users.
For details of sending commands to the ASM by means of the command
prompt, refer to “ASM User Interface,” in Chapter 16, “Application Services
Manager (ASM)” of the BaanERP 5.0c Administrator’s Guide (U7189B US).

4-55

4-56

Difference Study BaanERP 5.0b - 5.0c

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Difference Study BaanERP 5.0b - 5.0c

Uploaded by

Copyright:

Available Formats

BaanERP 5.

Difference Study P3167A US

Check the PowerDOCS or CyberDOCS database to see if this document is

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