installation and configuration guide for the baan ... and... · baanerp, and includes the...

Baan OpenWorld 2.1

Installation and Configuration Guidefor the Baan OpenWorld Adapter forBaanERP

A publication of:

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

Printed in the Netherlands

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

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

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

Document Information

Code: U7520A USGroup: User DocumentationEdition: ADate: August, 2001

i

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERP

1 Introduction 1-1Overview 1-1Prerequisites 1-2Installation and configuration � overview 1-3

2 To install and configure the Adapter for BaanERP 2-1Installation 2-1Install the Tools Middleware (TM) package 2-1Install include files 2-3Add the TM package to the package combination 2-3Install Java components for ERP 2-6Install MSMQ DLL 2-6Configuration 2-6About the Adapter properties file 2-6To move the property file to the correct directory 2-7To edit the property file 2-7To update the Directory Service 2-8To test your installation 2-8

3 To start and stop BaanERP XML Handlers 3-1Overview 3-1tmboaserver GUI interface 3-2To start the GUI interface 3-2To start and stop bus components 3-2Information on the GUI interface 3-3tmboaserver command line interface 3-4To start a GUI-less bshell 3-4To use the tmboaserver command line interface 3-4To stop a bus component 3-6Automatically starting Server (ASM) 3-7Overview 3-7Configuration of BusComponent 3-8Configuration ASM for OpenWorld 3-8Troubleshooting 3-8

Appendix A bshell/JVMI configuration and administration 1Configuration 1Resource options 1

Table of contents

Table of contents

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPii

Command line options 2Troubleshooting 2

Appendix B Baan OpenWorld 2.1 Adapter property file � syntax andproperties 1Sample property file 1Properties 2General settings 2Directory settings 3Log settings 3Advanced settings 3

Appendix C Configuration of ASM for OpenWorld 1

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPiii

This guide describes configuration and administration issues specific to runningBaanERP as a Baan OpenWorld 2.1 client or server application.

This document is intended for system managers responsible, to set up andmaintain BaanERP in a Baan OpenWorld 2.1 environment. Users of thisdocument must be familiar with BaanERP and with the Baan OpenWorld 2.1architecture.

This document does not describe the general procedures required to install andconfigure either BaanERP or Baan OpenWorld 2.1 Adapter. Only the additionalconfiguration and administration issues relevant to running BaanERP as a clientor server application in a Baan OpenWorld 2.1 environment are described.

Chapter 1, �Introduction,� provides a short introduction to the Baan OpenWorld2.1 Adapter for BaanERP and outlines the steps involved when you install andconfigure the software.

Chapter 2, �To install and configure the Adapter for Baan,� describes theprocedures to install and configure the Baan OpenWorld 2.1 Adapter forBaanERP and to update the Directory Service.

Chapter 3, �To start and stop BaanERP XML Handlers,� describes how to startand stop XML Handlers with the use of the tmboaserver session.

Appendix A, �bshell/JVMI configuration and administration,� describes thefacilities available for you to configure and troubleshoot the bshell/JVMI.

Appendix B, �Baan OpenWorld Adapter property file � syntax and properties,�presents the full syntax of the Baan OpenWorld 2.1 Adapter properties file anddescribes the individual properties.

Related documents� Baan OpenWorld Integration Framework Deployment Guide (U7303 US).� Baan OpenWorld Adapter Installation and Configuration Guide (U7304 US).� MQSeries for Baan OpenWorld Adapter Configuration Guide (U7307 US).� MSMQ for Baan OpenWorld Adapter Configuration Guide (U7308 US).

About this document

About this document

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPiv

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERP1-1

This chapter provides an overview of the Baan OpenWorld 2.1 Adapter forBaanERP, and includes the installation and configuration procedure.

OverviewThe Baan OpenWorld 2.1 Adapter for BaanERP supports BaanERP as both aclient and a server in the Baan OpenWorld 2.1 environment. The client side isreferred to as the BaanERP Client Adapter. The server side is referred to as theBaanERP Server Adapter or the XML Handler.

The Baan OpenWorld 2.1 Adapter for BaanERP is implemented in Java in thebshell. The Java VM Integration (JVMI) in the bshell enables communicationbetween Baan 4GL and Java programs and is used for communication betweenBaanERP and the Baan OpenWorld 2.1 Adapter.

OpenWorld connectivity is available for release BaanERP 5.0c and BAAN IVc.

The OpenWorld release for BAAN IVc is limited, and does not support updateswhen the Data-Oriented Model (SQL) is used.

1 Introduction

NOTE

Introduction


PrerequisitesThe JVMI requires a Java VM. Java VM must be available on the machine onwhich you run BaanERP and its Adapter. A Java VM is not delivered withBaanERP, so you must install it yourself.The minimal Java version needed for OpenWorld is:

Platform Minimal Java versionNT JVM 3165IBM RS6000 JDK 1.1.6SUN SPARC JDK 1.1.7IBM AS 400 JDK 1.1.7HP JDK 1.1.7DEC ALPHA JDK 1.1.8IBM OS390 JDK 1.1.8SIEMENS RM10000 JDK 1.2.1

The minimum system requirements for BaanERP are:

for BAAN IVc:

� Tools version ttB40_c4.� 6.1c05 porting set.

(For ASM & Activation, the porting set is unknown)

for BaanERP 5.0c:

� Tools version tt7.0_a1 (tt SP3 build).� 7.1b porting set.

(For ASM & Activation, the 71c porting set)

Introduction


Installation and configuration � overviewThe following are the main steps required, to install, configure, and administerthe Baan OpenWorld 2.1 Adapter for BaanERP:

1 Install the Tools Middleware package. For more information on theinstallation of the Tools Middleware package, refer to Chapter 2, �To installand configure the Adapter for BaanERP.�

2 Install the OpenWorld Adapter. For more information on the installation ofOpenWorld Adapter, refer to Chapter 2, �To install and configure the Adapterfor BaanERP.�

3 Configure the Adapter settings. For more information on the configuration ofthe Adapter settings, refer to Chapter 2, �To install and configure the Adapterfor BaanERP.�

4 Add the required entries to the Baan OpenWorld 2.1 Directory. For moreinformation, on how to add the required entries to the Baan OpenWorldDirectory, refer to Chapter 2, �To install and configure the Adapter forBaanERP.�

5 Start the required XML handlers. For more information on how to start therequired XML handlers, refer to Chapter 3, � To start and stop BaanERPXML handlers.

If the default bshell/JVMI configuration does not suit your requirements, you canuse various resource options and command line options to modify theconfiguration. Refer to Appendix A for details.

If you have problems with the JVMI, you can use JVMI logging to determine thecause of the problems. Refer to Appendix A for more details.

Baan OpenWorld 2.1 Adapter logging on is also supported; you can use thebus.properties file (adapter configuration) to enable logging on and to specifythe level(s) of logging on required. Refer to Appendix B for more details.

Introduction



This chapter describes the procedures to install and configure the BaanOpenWorld 2.1 Adapter for BaanERP.

InstallationInstall the Tools Middleware (TM) packageNote that the following procedure to create a package combination does notcover all possible details and issues. Screens in the instructions can look differentdue to your current setup.

You must carry out these steps as super user.

Follow these steps to install the Tools Middleware (TM) package for theOpenWorldBaanERP adapter.

1 Use the browser to navigate to BaanTools, Import Data Dictionary.

BAAN IVc:

2 To install and configure the Adapterfor BaanERP

NOTE

To install and configure the Adapter for BaanERP


BaanERP 5.0c:

2 Start the Import Data session.

For BAAN IVc, the Import Data (ttiex1285m000) session:



For BaanERP 5.0c, the Import Data (ttiex1285m000) session:

3 Install the dumps located in theBaan<version>/all_platforms/dump_tm_2.1_a with the import datadictionary. (where < version > is �ERP� or �4).

− Set overwrite to Yes.− Set Delete dumps to No.

4 Click Import.

Install include files� For BAAN IVc:

Copy AdapterForErp/Baan4c4/all_platforms/include6.1/bic_tmboa to$BSE/include6.1.

� For BaanERP 5.0c:Copy AdapterForErp/BaanERP/all_platforms/include6.2/bic_tmboa to$BSE/include6.2.

Add the TM package to the package combinationNote that the following procedure to create a package combination does notcover all possible details and issues. Screens in the instructions can look differentdue to your current setup.

You must carry out these steps as super user.

Follow these steps to create a package combination for the OpenWorldBaanERPadapter.

1 Use the browser to navigate to BaanTools, Packages by PackageCombination.

NOTE



BAAN IVc:

BaanERP 5.0c:

2 Start the Packages by Package Combination session.



For BAAN IVc, the Packages by Package Combination (ttaad1121m000)session:

For BaanERP 5.0c, the Packages by Package Combination (ttaad1121m000)session:

3 Insert in the row of a package tm, in the Version - 2.0 column and in theRelease �a column.

4 Rebuild the Data Dictionary.



Install Java components for ERPThe following Java components must be installed.

� $BSE/java/b3.jar.� $BSE/java/com.ibm.mq.jar.� $BSE/java/*.properties.� $BSE/java/bus.properties.

These files are located on the CD-ROM, the following steps describe how tocopy the files to the BaanERP system.

1 Create a $BSE/java directory and copy the content of theBaanERP/all_platforms/bsejava directory to it.

2 Copy the bus.properties file from the BaanERP\<platform>\defconfigdirectory to the $BSE/java directory (where <platform> is NT or Unix).

Install MSMQ DLLOn Windows NT only, the following DLL must be installed:

1 Copy the file eibmsmq.dll file from the BaanERP\nt\lib directory to the$BSE\bin directory.

2 Ensure that the $BSE\bin directory is included in the PATH environmentvariable. To include the $BSE\bin directory, alter the System Variables in theEnvironment tab of the System Properties dialog. To access SystemProperties, right-click on My Computer, select Properties.

ConfigurationAbout the Adapter properties fileThe runtime configuration settings of Baan OpenWorld 2.1 Adapter are stored inthe bus.properties file on the computer on which Baan OpenWorld 2.1 Adapterruns. The Baan OpenWorld 2.1 Adapter for BaanERP uses the same propertiesfile as the Java Adapter.

There can be multiple property files for each Baan OpenWorld 2.1 Adapter. Oneis a generic property file (bus.properties). The others are user-specific(<username>_bus.properties). If there is a user-specific property file for thelogged on user, Baan OpenWorld 2.1 Adapter uses this to determine the runtimeproperties. Otherwise, Baan OpenWorld 2.1 Adapter uses the generic propertyfile.



On MS Windows systems, the order in which Baan OpenWorld 2.1 Adaptersearches for the property file to use is as follows:

� Windows directory (for example, C:\WINNT on Windows NT systems)− user-specific bus.properties file.− generic bus.properties file.

On UNIX systems, the order in which Baan OpenWorld 2.1 Adapter searches forthe property file to use is as follows:

� Home directory− user-specific bus.properties file.− generic bus.properties file.

� /etc directory− user-specific bus.properties file.− generic bus.properties file.

To move the property file to the correct directoryIn the previous step, a default property file was copied to the $BSE/java/directory.

For the OpenWorld Adapter to access this file on Windows systems, you mustcopy the file to the Windows directory. On Unix systems, you must copy the fileeither to the home directory or the /etc directory. The previous section describesthe order in which the Adapter searches for the property file to use.

To edit the property fileOnly two properties must be changed in the default property file delivered withthe Baan OpenWorld 2.1 Adapter for BaanERP. These two properties specify theaddress of the directory server and the root element of the directory service. Allother properties can be left unchanged. As the property file is an ASCII file, youcan edit the file with any ASCII editor.

On Windows platforms, you can use the Adapter Configuration tool, to changeany of the settings in the bus.properties file.

� To specify the address of the directory server, set the following property:bus.services.directory.ServerURL=ldap://<your LDAP directory location>

For example:bus.services.directory.ServerURL=ldap://directory.baan.com

� To specify the root of the Directory Service, set the following property:bus.services.directory.root=<o=yourSuffix>



For example:bus.services.directory.root=o=baan.com

Refer to Appendix B for the full syntax of the property file and a description ofthe available properties.

To update the Directory ServiceCreate one or more bus component entries in the Directory Service for the BaanOpenWorld 2.1 Server Adapter (that is, XML Handler). For information on howto create one or more entries in the Directory Service, refer to the BaanOpenWorld 2.1 Adapter Installation and Configuration Guide (U7304D US).The directory entries must include the following properties:

Parameter ValueCategory BaanERPCompany number The BaanERP company number that will be used for this

component. Do not check to use the default companynumber of the user that started the XML Handler.

The Directory Service entry used by BaanERP when acting as a client does notrequire any BaanERP-specific options.

To test your installationOnce you have installed and configured the Baan OpenWorld 2.1 Adapter forBaanERP and added the relevant entries to the Directory Service, you can testyour installation as described in this section.

� To test whether java can find your classes:

java -classpath$BSE/java:$BSE/java/b3.jar:$BSE/java/com.ibm.mq.jar:$JAVAHOME/lib/classes.zip com.eibus.version.Version


This chapter describes how you can use the BaanERP session tmboaserver tostart and stop XML Handlers.

OverviewThe BaanERP Server Adapter or XML Handler must handle incoming requestsfrom other enterprise applications.

In the Directory Service you can define:

� The transport service that the XML Handler uses to exchange messages withother applications.

� The properties of the connection to the transport service, address, messagequeues, ports and so on.

The entry in the Directory Service is referred to as a bus component. So, to startan XML Handler, you basically select an appropriate bus component from theDirectory Service and start it.

To reduce the number of bshells required, you can run multiple XML Handlers inthe same bshell. You can start multiple bus components in the bshell to reducethe number of bshells required. For performance reasons, you can increase ordecrease the number of bus components started by a bshell. For example, it ispreferable to start bus components that are frequently used (that is, buscomponents that receive large database queries) in separate bshells.

You cannot start the same bus component more than once.

The BaanERP tmboaserver session provides the facilities to start and stop buscomponents. This session has both a GUI and a command line interface. Thischapter describes both interfaces.

3 To start and stop BaanERP XMLHandlers

NOTE

To start and stop BaanERP XML Handlers


tmboaserver GUI interfaceTo start the GUI interfaceThe GUI interface for the tmboaserver is a BaanERP session which can bestarted by running Program/Session

tmboaserver [-usermode <securitymode>]

The security mode can be either of the following:

�� Free.This option enables OpenWorld Client Adapters to communicate with thisserver without specifying user name and password.

�� Checkuser.With this option the user name and password combination is checked. Userswho use this server must be known for this BaanERP installation.

�� Thisuser.With this option, only the user who has started this BaanERP session cancommunicate with it.

To start and stop bus componentsTo start a bus component, select the bus component in the Available BusComponents list and click Start.

To stop a bus component, select the relevant bus component from the Started BusComponents list and click Stop.



Information on the GUI interfaceThe GUI interface for the tmboaserver session displays the following options:

� Statistical information about the number of requests handled, the processingtime for these requests, and also statistical information about errors.

� A list of all bus components defined in the Directory Service (Available BusComponents).

� A Start button to start the bus component currently selected in the AvailableBus Components list. You can only start bus components that are configuredfor the machine that you are currently connected to.

� A Stop button to stop the component currently selected in the Started BusComponents list.

� An Info button to display the information held by the Directory Service forthe component currently selected in the Available Bus Components list box.

� Statistical information about the number of requests handled, the processingtime for these requests, and also statistical information about errors.

� A Reset button to reset the statistical information.

� A string indicating in which security mode this OpenWorld Server is started.This can be Free, ThisUser, or CheckUser.



� A Close button to close this session and stop all the started bus components.

� An About button to display information about the versions of the installedOpenWorld Adapter for BaanERP code. The versions of the installed TMpackage and the Java Implementation must be the same.

tmboaserver command line interfaceTo start a GUI-less bshellYou can start the bshell without the GUI by specifying the -server flag.

On Windows systems, use the following command:

ntbshell.exe �server

Make sure that the environment settings are correctly set. You can use the$BSE\bin\fillenv.bat batch file to check the correct environment settings.

On HPUX use the following command:

bshelljava6.x �server

On other Unix systems, use the following command:

bshell6.x �server

To use the tmboaserver command line interfaceThe GUI-less tmboaserver session has a bshell command line interface thatprovides similar functionality to the GUI interface. The available argumentsprovide the following functionality:

� Start XML Handlers for multiple bus components automatically.� Log error messages to a specified log file.� Log statistical information to the log file.



Syntax

The syntax of the bshell command line interface is as follows:

tmboaserver [-f <componentfile> [-d]] [-l <logfile> [-s]]

Options

Flag Description-f<componentfile>

Specifies the file that contains the components to bestarted automatically. Each line in the file must be thename of a bus component defined in the DirectoryService. For example:cn=cnl06825,o=baan.comcn=My_Bus_Component,o=baan.comIf the tmboaserver session is run by a Bshell without auser interface then this flag is mandatory.

-d Do not display a user interface.This flag is valid only in combination with the -f flag. If the-f flag is not specified, the user interface is alwaysstarted. If it is specified, then display of the user interfacedepends on whether or not the -d flag is specified.If the bshell is started without a user interface (using the -server option) this flag is overruled.

-s If specified, statistics are logged to a logfile. This requiresthe -I flag to be set.

-l <logfile> Specifies the file in which error messages and statisticsare logged.

Example

The following example illustrates how to start multiple GUI-less bshells and howto use the tmboaserver session to start a number of bus components in thesebshells. Make sure that your bshell environment settings are correctly set beforeyou perform these tasks.

To create a batch file or shell script that starts three GUI-less bshells and startstwo bus components in each, follow the steps described here:

1 Create a file that contains the command lines to start each of the bshells. OnWindows NT, use a batch file. On UNIX, use a shell script.



2 Add the following entries to the file:

Start.batc:\baan\bin\ntbshell -server otmboaserver -f c:\Buscomp1 -d -s -l c:\stat1.logc:\baan\bin\ntbshell -server otmboaserver -f c:\Buscomp2 -d -s -l c:\stat2.logc:\baan\bin\ntbshell -server otmboaserver -f c:\Buscomp3 -d -s -l c:\stat3.log

Each of these commands starts a GUI-less bshell and specifies the file thatcontains the list of bus components to be started by that bshell. Thesecommands also indicate statistics that are required and specify the name ofthe log file in which error messages and statistics must be logged.

3 Create the files that contain the list of bus components to be started by eachbshell. For example:

c:\Buscomp1cn=BusComponent01,o=baan.comcn=BusComponent02,o=baan.com



4 Run the batch file or shell script.

You can add code to your scripts in order to have them restart the bshell after acrash.

In UNIX, you can add your script to the end of your rc.start script so that thesystem starts the bshell(s) automatically.

To stop a bus componentPress CTRL+C to stop the bus component(s).

NOTE

NOTE



Automatically starting Server (ASM)OverviewThe automatic starting OpenWorld Server is a special server which can interactwith the Baan ASM Service. The Client Adapter for Java can also interact withthe ASM Service with the proper ASM and OpenWorld configuration. ThisOpenWorld server for BaanERP can automatically start and stop. TheOpenWorld Server that is started must have access to the correct directoryinformation.

Syntax

The syntax of the command line which can start the ASM OpenWorld Server:

otmboaasmserver -busc <buscomponent> -asmp <socket port no>

[ -logf <logfilename> -stat ]

Options

Flag Description-busc <bus component> Specifies which bus component to read from the

directory. This bus component is used to start theOpenWorld Server for ASM. Note that this buscomponent should have activation enabled.

-asmp <portNr> This is the socket port number on the ASMdeamon to which the OpenWorld Server send itsstart information.

-logf <logfile> Specifies the file in which error messages andstatistics are logged.

-stat Enables Logging on every request to this Server

When the ASM Deamon starts this OpenWorld Server the bus component andthe port number are filled in by the ASM Deamon. To start the OpenWorldServer by ASM, the ASM configuration would look as follows:

sessioncode="otmboaasmserver" sessionparameters="-busc "%USERDATA%" -asmp%PORT% -logf \tmp\ow.log -stat" />

The ASM service is part of the BaanERP BaanLogon deamon, and therefore partof the BaanERP installation. From an OpenWorld point of view, this deamonruns on the server side.



Configuration of BusComponentBusComponents that are used in client application, with automatic start of thebackend, contains some extra information. The BusComponent Editor that isdelivered with the Adapter for Java 2.1 contains the BusComponent Editor thatyou can use to create Activation enabled BusComponents.

Configuration ASM for OpenWorldThe ASM Application Service Manager is a generic Service that is deliveredwith BaanERP. For detailed information on this service, refer to the ASMDocumentation of BaanERP.

For OpenWorld, you must enter some specific information in the twoconfiguration files of ASM. These two files are asminstdef.xml andasmtypedef.xml. For an example on configuring the ASM for OpenWorld, referto AppendixC "Configuration of ASM for OpenWorld."

TroubleshootingThe company number specified in the Directory Service entries for buscomponents used by the BaanERP Server Adapter must match the currentpackage combination. If the current package combination does not match, thefollowing error occurs:

ERROR: Current package combination (sss) does not match with package combination(sss) of company (nnn)

There are a number of possible solutions to this problem:

� Start the XML Handler in the same package combination as defined for thecompany. To check the current package combination, start Change Companyfrom the Menu Browser.

� Define another package combination for the company. This is notrecommended and must be performed only by system administrators.

� Define a different company number in the Directory Service entries for thebus components.

The company data for a particular package combination is defined in theCompanies (ttaad1100m000) session.

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPbshell/JVMI configuration and administration - Page 1

This appendix describes the facilities available to configure and to troubleshootthe bshell/JVMI integration.

ConfigurationThe bshell provides a Java VM Integration (JVMI) that enables communicationbetween Baan 4GL applications and the Baan OpenWorld 2.1 Adapter forBaanERP. Resource options and command line options are available to configurethe bshell/JVMI integration.

Resource optionsYou can configure the following options with the use of the $BSE/lib/defaults/allfile:

Resource name Default DescriptionOverride_java_signals 1 When the Java VM is started, signal

handlers are reassigned from the bshell tothe Java VM. If you set this flag to 1, thesignal handlers are reassigned to the bshellafterwards. If you set this value to 0, theyremain assigned to the Java VM.

Override_java_sigusr1 0 (AIX)1 (other)

If override_java_signals is set to 1, this flagspecifies whether or not the bshell mustalso handle SIGUSR1 signals.On platforms other than AIX, the default is 1(the bshell handles SIGUSR1 signals). OnAIX platforms, the Java VM requiresSIGUSR1 in order to work correctly, so thedefault is 0.

Java_queue_size -1 Specifies the maximum number ofmessages supported by a Java queue. Bydefault (-1), the number of messages isunlimited. For Java VM load balancingpurposes, the number of messages on theJava queue can be limited to a valuebetween 1 and 128.

Appendix A bshell/JVMI configuration andadministration

bshell/JVMI configuration and administration

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPPage 2 - bshell/JVMI configuration and administration

Command line optionsYou can enable logging on for JVMI actions with the use of the followingcommand line option:

-dbgjvmi

This is useful to trace JVMI problems in the bshell (see below).

TroubleshootingThis section outlines problems that can occur with the JVMI and the possiblesolutions. To detect the listed problems, you must enable JVMI logging on byspecifying the following options in the Baan Windows (BW) startup command:

-dbgjvmi �logfile /tmp/jvmiproblems.txt �keeplog

Problem Possible cause anddetection

Solution

JVMI doesnot work

Cause: bshell does notsupport JVMI.How to detect: Themessage 'JavaVMintegration not available inthis bshell' appears in thelog file.

HP-UX platform:Two bshells are delivered for thisplatform � bshell6.2 (without JVMIintegration) and bshelljava6.2 (withJVMI). Make sure that you are usingbshelljava6.2.Also, the bshell entry in the$BSE/lib/ipc info file must be set asfollows:bshell s 0 0 p ${BSE}/bin/bshelljava6.2Other platforms:On platforms other than HP-UX, thismessage in the log file indicates thatJVMI is not supported for theparticular platform.

JVMI doesnot work

Cause: Incorrect or noJava VM.How to detect: A messagesimilar to the followingappears in the log file:�Incorrect JavaVM version(minimum version x.y.z)�or �Java not installed(minimum version x.y.z)�.

Install the minimum (or higher)required version of the Java VM. Youcan obtain this free from the hardwarevendors or from Microsoft.


Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPbshell/JVMI configuration and administration - Page 3

Problem Possible cause anddetection

Solution

Javaexceptionsare nothandledcorrectly

Cause: Incorrect signalhandlers are used.How to detect: Log fileentries.

Change the override_java_signals andoverride_java_sigusr1 resources. Ifthis does not solve the problem,contact the next support level.

Other How to detect: Log fileentries.

Send the generated log file to the nextsupport level.


Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPPage 4 - bshell/JVMI configuration and administration

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPBaan OpenWorld 2.1 Adapter property file � syntax and properties - Page 1

This appendix presents the full syntax for the bus.properties file and describesthe available properties, their valid values, and their default values.

Sample property fileThe following is an example of a bus.properties file:

[General settings]bus.bdf.iterator.size=10bus.bdf.manager.timeout=10000bus.default.backend=user.name=bus.component=

[Directory settings]bus.services.directory.Directory=com.eibus.services.directory.ldap.LDAPDirectorybus.services.directory.ServerURL=ldap://srv-nld-interb0.baan.combus.services.directory.Root=o=baan.com

[Log settings]bus.log.file=c:\\buslog.xmlbus.log.mask=0x1801e

[Advanced settings]bus.default.protocol=socketbus.connection.max.readers=org.xml.sax.parser=com.jclark.xml.sax.Driverbus.num.xml.parse.threads=1bus.services.guid.GuidFactory=com.eibus.services.guid.win32.COMGuidFactory

Any line that begins with the character �;� is treated as a comment line.

When entering back-slashes ( \ ) in a property value, make sure that you enterthem twice, since Java uses the backslash as an escape character. If, for exampleyou want c:\temp\buslog.txt to be your log file, you must enterc:\\temp\\buslog.txt.

Appendix B Baan OpenWorld 2.1 Adapterproperty file � syntax and properties

NOTE

NOTE

Baan OpenWorld 2.1 Adapter property file � syntax and properties

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPPage 2 - Baan OpenWorld 2.1 Adapter property file � syntax and properties

PropertiesThis section describes the most commonly used properties in the bus.propertiesfile.

General settingsbus.bdf.iterator.sizeThe default number of records that are received in one fetch, enables you to limitthe data that is transferred to the client in each message. You can override thisdefault value in your application code.

The amount of data delivered depends not only on the number of recordsdelivered but also on the number of fields in a record and the number ofassociated tables. For smaller records, you can increase the number of recordsretrieved per fetch. For larger records, you can decrease the number of recordsretrieved.

Default value: 250

bus.bdf.manager.timeoutThe default time (in milliseconds) that Baan OpenWorld 2.1 Adapter waits for areply when performing a request to a server. You can override this timeoutperiod in your application code.

Default value: 30000

bus.default.backendThe backend that your programmed Manager connects to by default. You canoverride this default setting in your application code with the manager.initializemethod.

Default value: n.a.

user.nameThis property is not currently used.

bus.componentThe name of the local Baan OpenWorld 2.1 component, as registered in theDirectory Service. You do not need to specify this parameter for anonymousclients that use a socket transport service. For all servers and named clients, andfor anonymous clients that use MQSeries as their transport service, set this to therelevant component name.

Default value: Fully qualified machine name.


Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPBaan OpenWorld 2.1 Adapter property file � syntax and properties - Page 3

Directory settingsbus.services.directory.DirectoryContains the name of the directory server class. This can be either:

com.eibus.services.directory.file.FileDirectory orcom.eibus.services.directory.ldap.LDAPDirectory

Default value: n.a.

bus.services.directory.ServerURLThe name of the directory server to use.

If you use an LDAP-compliant Directory Service, specify the URL of thedirectory server. If you use an XML file Directory Service, specify the full pathfor the file. The required syntax is:

ldap://<ip_address or computer_name>

<file_name>

Default value: n.a.

bus.services.directory.RootThe name of the domain in the directory server to use; that is, the root element ofthe Directory Service. This property is required for both LDAP and XML flat fileDirectory Services. The syntax is:

o=<server_root>

Default value: n.a.

Log settingsbus.log.fileCan contain the path to a specific log file. If null, then messages are logged toSystem.out.

Default value: n.a.

bus.log.maskBit pattern to activate logging on for specific categories of activity. The defaultvalue (0) specifies no logging on. The value FFFFFF specifies full logging on.

Default value: 0 (no logging)

Advanced settingsbus.default.protocolThis can be MQSeries, msmq, or socket


Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPPage 4 - Baan OpenWorld 2.1 Adapter property file � syntax and properties

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPConfiguration of ASM for OpenWorld - Page 1

The ASM deamon is part of the Baan Logon deamon of the BaanERPinstallation. The ASM deamon can be configured with two files:

asminsdef.xml and asmtypedef.xml

these files are in $BSE/lib, and can also been configurated with a Baan session.For more details on this Baan Session look in the BaanERP Documentation.

Example of an asminsdef.xml file configured for OpenWorld;

<?xml version="1.0" ?><InstanceDef>

<environment name="ASM Test" system="orbix" directory="/usr3/baancor/bse">

<instance servicename="DedicatedOpenWorldServer"servicetype="DedicatedXMLMapper" occurance="multiple"startup="manual">

<start />

</instance>

</environment>

</InstanceDef>

Note that the service name is DedicatedOpenWorldServer, this is the servicename used in OpenWorld.

Appendix C Configuration of ASM forOpenWorld

Configuration of ASM for OpenWorld

Installation and Configuration Guide for the Baan OpenWorld Adapter for BaanERPPage 2 - Configuration of ASM for OpenWorld

Example of an asmtypedef.xml file that starts a bshell and the ASM OpenWorldserver.

%USERDATA% is the serialized BusComponent that is send to the server.

%PORT% is the port number that the ASM server uses to send the startedserialized BusComponent back to the ASM deamon.

<?xml version="1.0" ?><ServiceTypeDef>

<environment name="ASM Test" system="orbix" directory="/usr3/baancor/bse">

<service type="DedicatedXMLMapper">

<start executable="/usr3/baancor/bse/bin/bshell6.2"exeparameters="-server" sessioncode="otmboaasmserver"sessionparameters="-busc "%USERDATA%" -asmp%PORT% -logf $BSE/log/server.log -stat" />

</service>

</environment>

</ServiceTypeDef>

For more information on ASM and the configuration of this service you can referto ASM BaanERP documentation.

installation and configuration guide for the baan ... and... · baanerp, and includes the...

Documents