Baan OpenWorld 2.2. Installation and Configuration Guide for Adapter for BaanERP

Transcription

1 Baan OpenWorld 2.2 Installation and Configuration Guide for Adapter for BaanERP

2 A publication of: Baan Development B.V. P.O.Box AC Barneveld The Netherlands Printed in the Netherlands Baan Development B.V All rights reserved. The information in this document is subject to change without notice. No part of this document may be reproduced, stored or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Baan Development B.V. Baan Development B.V. assumes no liability for any damages incurred, directly or indirectly, from any errors, omissions or discrepancies between the software and the information contained in this document. Document Information Code: U7520B US Group: User Documentation Edition: B Date: April, 2003

3 Table of contents 1 Introduction 1-1 Overview 1-1 Prerequisites 1-2 Installation and configuration overview To install and configure the Adapter for BaanERP 2-1 Installation 2-1 Install the Tools Middleware (TM) package 2-1 Install include files 2-3 Add the TM package to the package combination 2-3 Install Java components for ERP 2-6 Install MSMQ DLL 2-6 Configuration 2-6 About the Adapter properties file 2-6 To move the property file to the correct directory 2-7 To edit the property file 2-7 To update the Directory Service 2-8 To test your installation To start and stop BaanERP XML Handlers 3-1 Overview 3-1 tmboaserver GUI interface 3-2 To start the GUI interface 3-2 To start and stop bus components 3-2 Information on the GUI interface 3-3 tmboaserver command line interface 3-4 To start a GUI-less bshell 3-4 To use the tmboaserver command line interface 3-4 To stop a bus component 3-6 Automatically starting Server (ASM) 3-7 Overview 3-7 Configuration of BusComponent 3-8 Configuration ASM for OpenWorld 3-8 Troubleshooting 3-8 i

4 Table of contents Appendix A bshell/jvmi configuration and administration 1 A.1 Configuration 1 A.2 Resource options 1 A.3 Command line options 2 A.4 Troubleshooting 2 Appendix B Baan OpenWorld 2.2 Adapter property file syntax and properties 1 B.1 Properties file example 1 B.2 Properties 2 General settings 2 Directory settings 3 Log settings 3 Advanced settings 3 Appendix C Configuration of ASM for OpenWorld 1 ii

5 About this document This guide describes configuration and administration issues specific to running BaanERP as a Baan OpenWorld 2.2 client or server application. This document is intended for system managers responsible to set up and maintain BaanERP in a Baan OpenWorld 2.2 environment. Users of this document must be familiar with BaanERP and with the Baan OpenWorld 2.2 architecture. This document does not describe the general procedures required to install and configure either BaanERP or Baan OpenWorld 2.2 Adapter. Only the additional configuration and administration issues relevant to running BaanERP as a client or server application in a Baan OpenWorld 2.2 environment are described. Chapter 1, Introduction, provides a short introduction to the Baan OpenWorld 2.2 Adapter for BaanERP and outlines the steps involved when you install and configure the software. Chapter 2, To install and configure the Adapter for Baan, describes the procedures to install and configure the Baan OpenWorld 2.2 Adapter for BaanERP and to update the Directory Service. Chapter 3, To start and stop BaanERP XML Handlers, describes how to start and stop XML Handlers with the use of the tmboaserver session. Appendix A, bshell/jvmi configuration and administration, describes the facilities 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.2 Adapter properties file and describes the individual properties. Appendix C, Configuration of ASM for OpenWorld, shows how the Application Service Manager (ASM) of BaanERP must be configured for Baan OpenWorld 2.2. iii

6 About this document Related documents Baan OpenWorld Deployment Guide (U7303 US). Baan OpenWorld Installation and Configuration Guide for Adapter (U7525 US). Baan OpenWorld Configuration Guide for MQSeries for Baan OpenWorld Adapter (U7307 US). Baan OpenWorld Configuration Guide for MSMQ for Baan OpenWorld Adapter (U7308 US). Baan OpenWorld 2.2 Deployment Guide for BCLM (U7652 US). iv

7 1 Introduction This chapter provides an overview of the Baan OpenWorld 2.2 Adapter for BaanERP, and includes the installation and configuration procedure. Overview NOTE The Baan OpenWorld 2.2 Adapter for BaanERP supports BaanERP as both a client and a server in the Baan OpenWorld 2.2 environment. The client side is referred to as the BaanERP Client Adapter. The server side is referred to as the BaanERP Server Adapter or the XML Handler. The Baan OpenWorld 2.2 Adapter for BaanERP is implemented in Java in the bshell. The Java VM Integration (JVMI) in the bshell enables communication between Baan 4GL and Java programs and is used for communication between BaanERP and the Baan OpenWorld 2.2 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 updates when the Data-Oriented Model (SQL) is used. 1-1

8 Introduction Prerequisites The JVMI requires a Java VM. Java VM must be available on the machine on which you run BaanERP and its Adapter. A Java VM is not delivered with BaanERP, so you must install it yourself. The minimal Java version needed for Baan OpenWorld 2.2 is: Platform Minimal Java version NT JVM 3165 IBM RS6000 JDK SUN SPARC JDK IBM AS 400 JDK HP JDK DEC ALPHA JDK IBM OS390 JDK SIEMENS RM10000 JDK The minimum system requirements for BaanERP are: for BAAN IVc: Tools version ttb40_c4. 6.1c06 porting set. (For ASM & Activation, the porting set is unknown) for BaanERP 5.0c: Tools version tt7.0_a1 (tt SP3 build). 7.1c porting set. (For ASM & Activation, the 71c porting set) In Baan OpenWorld 2.2, the servers of Adapter for BaanERP are licensed by the BaanCIT License Manager (BCLM). This implies that each Adapter server must have access to a properly configured BCLM server (with a valid key for the required licenses), and that on each Adapter server the BCLM client software must be installed. For more information about the BCLM refer to the Baan OpenWorld 2.2 Deployment Guide for BCLM (U7652A US) and the Installation and Configuration Guide for the BaanCIT License Manager (U7631A US). 1-2

9 Introduction Installation and configuration overview The following are the main steps required, to install, configure, and administer the Baan OpenWorld 2.2 Adapter for BaanERP: 1 Install and configure the BaanCIT License Manager (BCLM). The BCLM must have predefined Server licenses for each server of Adapter for BaanERP. For more information on the installation and configuration of the BCLM, refer to the Baan OpenWorld 2.2 Deployment Guide for BCLM (U7652A US). 2 Install the Tools Middleware package. For more information on the installation of the Tools Middleware package, refer to Chapter 2, To install and configure the Adapter for BaanERP. 3 Install the OpenWorld Adapter. For more information on the installation of OpenWorld Adapter, refer to Chapter 2, To install and configure the Adapter for BaanERP. 4 Configure the Adapter settings. For more information on the configuration of the Adapter settings, refer to Chapter 2, To install and configure the Adapter for BaanERP. 5 Add the required entries to the Baan OpenWorld 2.2 Directory. For more information, on how to add the required entries to the Baan OpenWorld Directory, refer to Chapter 2, To install and configure the Adapter for BaanERP. 6 Start the required XML handlers. For more information on how to start the required XML handlers, refer to Chapter 3, To start and stop BaanERP XML handlers. If the default bshell/jvmi configuration does not suit your requirements, you can use various resource options and command line options to modify the configuration. Refer to Appendix A for details. If you have problems with the JVMI, you can use JVMI logging to determine the cause of the problems. Refer to Appendix A for more details. Baan OpenWorld 2.2 Adapter logging is also supported; you can use the bus.properties file (adapter configuration) to enable logging on and to specify the level(s) of logging on required. Refer to Appendix B for more details. 1-3

10 Introduction 1-4

11 2 To install and configure the Adapter for BaanERP This chapter describes the procedures to install and configure the Baan OpenWorld 2.2 Adapter for BaanERP. Installation NOTE Install the Tools Middleware (TM) package Note that the following procedure to create a package combination does not cover all possible details and issues. Screens in the instructions can look different due to your current setup. You must carry out these steps as a BaanERP super user. Follow these steps to install the Tools Middleware (TM) package for the OpenWorldBaanERP adapter. 1 Use the browser to navigate to BaanTools, Import Data Dictionary. BAAN IVc: 2-1

12 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: 2-2

13 To install and configure the Adapter for BaanERP For BaanERP 5.0c, the Import Data (ttiex1285m000) session: 3 Install the dumps located in the Baan<version>/all_platforms/dump_tm_2.2_a with the import data dictionary. (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. NOTE Add the TM package to the package combination Note that the following procedure to create a package combination does not cover all possible details and issues. Screens in the instructions can look different due to your current setup. You must carry out these steps as super user. Follow these steps to create a package combination for the OpenWorldBaanERP adapter. 1 Use the browser to navigate to BaanTools, Packages by Package Combination. 2-3

14 To install and configure the Adapter for BaanERP BAAN IVc: BaanERP 5.0c: 2 Start the Packages by Package Combination session. 2-4

15 To install and configure the Adapter for BaanERP 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 column and in the Release a column. 4 Rebuild the Data Dictionary. 2-5

16 To install and configure the Adapter for BaanERP Install Java components for ERP The 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 to copy the files to the BaanERP system. 1 Create a $BSE/java directory and copy the content of the BaanERP/all_platforms/bsejava directory to it. 2 Copy the bus.properties file from the BaanERP\<platform>\defconfig directory to the $BSE/java directory (where <platform> is NT or Unix). Install MSMQ DLL On 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 environment variable. To include the $BSE\bin directory, alter the System Variables in the Environment tab of the System Properties dialog. To access System Properties, right-click on My Computer, select Properties. Configuration About the Adapter properties file The runtime configuration settings of Baan OpenWorld 2.2 Adapter are stored in the bus.properties file on the computer on which Baan OpenWorld 2.2 Adapter runs. The Baan OpenWorld 2.2 Adapter for BaanERP uses the same properties file as the Java Adapter. There can be multiple property files for each Baan OpenWorld 2.2 Adapter. One is a generic property file (bus.properties). The others are user-specific (<username>_bus.properties). If there is a user-specific property file for the logged on user, Baan OpenWorld 2.2 Adapter uses this to determine the runtime properties. Otherwise, Baan OpenWorld 2.2 Adapter uses the generic property file. 2-6

17 To install and configure the Adapter for BaanERP On Windows systems, the order in which Baan OpenWorld 2.2 Adapter searches 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.2 Adapter searches for the 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 directory In 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 must copy the file to the Windows directory. On Unix systems, you must copy the file either to the home directory or the /etc directory. The previous section described the order in which the Adapter searches for the property file to use. To edit the property file Only two properties must be changed in the default property file delivered with the Baan OpenWorld 2.2 Adapter for BaanERP. These two properties specify the address of the directory server and the root element of the directory service. All other properties can be left unchanged. As the property file is an ASCII file, you can edit the file with any ASCII editor. On Windows platforms, you can use the Adapter Configuration tool, to change any 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> 2-7

18 To install and configure the Adapter for BaanERP For example: bus.services.directory.root=o=baan.com Refer to Appendix B for the full syntax of the property file and a description of the available properties. To update the Directory Service Create one or more bus component entries in the Directory Service for the Baan OpenWorld 2.2 Server Adapter (that is, the XML Handler). For information on how to create one or more entries in the Directory Service, refer to the Baan OpenWorld Installation and Configuration Guide for Adapter (U7525B US). The directory entries must include the following properties: Parameter Category Company number Value BaanERP The BaanERP company number that will be used for this component. Do not check to use the default company number of the user that started the XML Handler. The Directory Service entry used by BaanERP when acting as a client does not require any BaanERP-specific options. To test your installation Once you have installed and configured the Baan OpenWorld 2.2 Adapter for BaanERP and added the relevant entries to the Directory Service, you can test your 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.zi p com.eibus.version.version 2-8

19 3 To start and stop BaanERP XML Handlers This chapter describes how you can use the BaanERP session tmboaserver to start and stop XML Handlers. Overview NOTE The BaanERP Server Adapter or XML Handler must handle incoming requests from other enterprise applications. In the Directory Service you can define: The transport service that the XML Handler uses to exchange messages with other applications. The properties of the connection to the transport service, address, message queues, ports and so on. The entry in the Directory Service is referred to as a bus component. So, to start an XML Handler, you basically select an appropriate bus component from the Directory Service and start it. To reduce the number of bshells required, you can run multiple XML Handlers in the same bshell. For performance reasons, you can increase or decrease the number of bus components started by a bshell. For example, it is preferable to start bus components that are frequently used (that is, bus components 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 bus components. This session has both a GUI and a command line interface. This chapter describes both interfaces. 3-1

20 To start and stop BaanERP XML Handlers tmboaserver GUI interface To start the GUI interface The GUI interface for the tmboaserver is a BaanERP session which can be started 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 this server without specifying user name and password. Checkuser. With this option the user name and password combination is checked. Users who use this server must be known for this BaanERP installation. Thisuser. With this option, only the user who has started this BaanERP session can communicate with it. To start and stop bus components To start a bus component, select the bus component in the Available Bus Components list and click Start. To stop a bus component, select the relevant bus component from the Started Bus Components list and click Stop. 3-2

21 To start and stop BaanERP XML Handlers Information on the GUI interface The GUI interface for the tmboaserver session displays the following options: A list of all bus components defined in the Directory Service (Available Bus Components). A Start button to start the bus component currently selected in the Available Bus Components list. You can only start bus components that are configured for the machine that you are currently connected to. A Stop button to stop the component currently selected in the Started Bus Components list. An Info button to display the information held by the Directory Service for the component currently selected in the Available Bus Components list box. Statistical information about the number of requests handled, the processing time 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. 3-3

22 To start and stop BaanERP XML Handlers An About button to display information about the versions of the installed OpenWorld Adapter for BaanERP code. The versions of the installed TM package and the Java Implementation must both start with 2.2. tmboaserver command line interface To start a GUI-less bshell You 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 interface The GUI-less tmboaserver session has a bshell command line interface that provides similar functionality to the GUI interface. The available arguments provide 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. 3-4

23 To start and stop BaanERP XML Handlers Syntax The syntax of the bshell command line interface is as follows: tmboaserver [-f <componentfile> [-d]] [-l <logfile> [-s]] Options Flag -f <componentfile> Description Specifies the file that contains the components to be started automatically. Each line in the file must be the name of a bus component defined in the Directory Service. For example: cn=cnl06825,o=baan.com cn=my_bus_component,o=baan.com If the tmboaserver session is run by a Bshell without a user 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 always started. If it is specified, then display of the user interface depends 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 requires the -I flag to be set. -l <logfile> Specifies the file in which error messages and statistics are logged. Example The following example illustrates how to start multiple GUI-less bshells and how to use the tmboaserver session to start a number of bus components in these bshells. Make sure that your bshell environment settings are correctly set before you perform these tasks. To create a batch file or shell script that starts three GUI-less bshells and starts two bus components in each, follow the steps described here: 1 Create a file that contains the command lines to start each of the bshells. On Windows NT, use a batch file. On UNIX, use a shell script. 3-5

24 To start and stop BaanERP XML Handlers 2 Add the following entries to the file: NOTE NOTE StartOW.bat start c:\baan\bin\ntbshell -server otmboaserver -f c:\buscomp1 -d -s -l c:\stat1.log start c:\baan\bin\ntbshell -server otmboaserver -f c:\buscomp2 -d -s -l c:\stat2.log start c:\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 that contains the list of bus components to be started by that bshell. These commands also indicate statistics that are required and specify the name of the 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 each bshell. For example: c:\buscomp1 cn=buscomponent01,o=baan.com cn=buscomponent02,o=baan.com c:\buscomp2 cn=buscomponent03,o=baan.com cn=buscomponent04,o=baan.com c:\buscomp3 cn=buscomponent05,o=baan.com cn=buscomponent06,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 a crash. In UNIX, you can add your script to the end of your rc.start script so that the system starts the bshell(s) automatically. To stop a bus component Press CTRL+C to stop the bus component(s). 3-6

25 To start and stop BaanERP XML Handlers Automatically starting Server (ASM) Overview The automatic starting OpenWorld Server is a special server which can interact with the Baan ASM Service. The Client Adapter for Java can also interact with the ASM Service with the proper ASM and OpenWorld configuration. This OpenWorld server for BaanERP can automatically start and stop. The OpenWorld Server that is started must have access to the correct directory information. Syntax The syntax of the command line which can start the ASM OpenWorld Server: otmboaasmserver -busc <buscomponent> -asmp <socket port no> Options [ -logf <logfilename> -stat ] Flag -busc <bus component> -asmp <portnr> -logf <logfile> -stat Description Specifies which bus component to read from the directory. This bus component is used to start the OpenWorld Server for ASM. Note that this bus component should have activation enabled. This is the socket port number on the ASM deamon to which the OpenWorld Server send its start information. Specifies the file in which error messages and statistics are logged. Enables Logging on every request to this Server When the ASM Deamon starts this OpenWorld Server the bus component and the port number are filled in by the ASM Deamon. To start the OpenWorld Server by ASM, the ASM configuration needs to be modified (see appendix C). The ASM service is part of the BaanERP BaanLogon deamon, and therefore part of the BaanERP installation. From an OpenWorld point of view, this deamon runs on the server side. 3-7

26 To start and stop BaanERP XML Handlers Configuration of BusComponent BusComponents that are used in client application, with automatic start of the backend, contains some extra information. The BusComponent Editor that is delivered with the Adapter 2.2 for Java contains the BusComponent Editor that you can use to create Activation enabled BusComponents. Configuration ASM for OpenWorld The ASM Application Service Manager is a generic Service that is delivered with BaanERP. For detailed information on this service, refer to the ASM Documentation of BaanERP. For OpenWorld, you must enter some specific information in the two configuration files of ASM. These two files are asminstdef.xml and asmtypedef.xml. For an example on configuring the ASM for OpenWorld, refer to Appendix C "Configuration of ASM for OpenWorld." Troubleshooting The company number specified in the Directory Service entries for bus components used by the BaanERP Server Adapter must match the current package combination. If the current package combination does not match, the following 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 the company. To check the current package combination, start Change Company from the Menu Browser. Define a different company number in the Directory Service entries for the bus components. Define another package combination for the company. This is not recommended and must be performed only by system administrators. The company data for a particular package combination is defined in the Companies (ttaad1100m000) session. 3-8

27 Appendix A bshell/jvmi configuration and administration This appendix describes the facilities available to configure and to troubleshoot the bshell/jvmi integration. A.1 Configuration The bshell provides a Java VM Integration (JVMI) that enables communication between Baan 4GL applications and the Baan OpenWorld 2.2 Adapter for BaanERP. Resource options and command line options are available to configure the bshell/jvmi integration. A.2 Resource options You can configure the following options with the use of the $BSE/lib/defaults/all file: Resource name Default Description override_java_signals 1 When the Java VM is started, signal handlers are reassigned from the bshell to the Java VM. If you set this flag to 1, the signal handlers are reassigned to the bshell afterwards. If you set this value to 0, they remain assigned to the Java VM. override_java_sigusr1 0 (AIX) 1 (other) If override_java_signals is set to 1, this flag specifies whether or not the bshell must also handle SIGUSR1 signals. On platforms other than AIX, the default is 1 (the bshell handles SIGUSR1 signals). On AIX platforms, the Java VM requires SIGUSR1 in order to work correctly, so the default is 0. java_queue_size -1 Specifies the maximum number of messages supported by a Java queue. By default (-1), the number of messages is unlimited. For Java VM load balancing purposes, the number of messages on the Java queue can be limited to a value between 1 and 128. bshell/jvmi configuration and administration - Page 1

28 bshell/jvmi configuration and administration A.3 Command line options You can enable logging on for JVMI actions with the use of the following command line option: -dbgjvmi This is useful to trace JVMI problems in the bshell (see below). A.4 Troubleshooting This section outlines problems that can occur with the JVMI and the possible solutions. To detect the listed problems, you must enable JVMI logging on by specifying the following options in the Baan Windows (BW) startup command: -dbgjvmi logfile /tmp/jvmiproblems.txt keeplog Problem JVMI does not work JVMI does not work Possible cause and detection Cause: bshell does not support JVMI. How to detect: The message 'JavaVM integration not available in this bshell' appears in the log file. Cause: Incorrect or no Java VM. How to detect: A message similar to the following appears in the log file: Incorrect JavaVM version (minimum version x.y.z) or Java not installed (minimum version x.y.z). Solution HP-UX platform: Two bshells are delivered for this platform bshell6.2 (without JVMI integration) and bshelljava6.2 (with JVMI). Make sure that you are using bshelljava6.2. Also, the bshell entry in the $BSE/lib/ipc info file must be set as follows: bshell s 0 0 p ${BSE}/bin/bshelljava6.2 Other platforms: On platforms other than HP-UX, this message in the log file indicates that JVMI is not supported for the particular platform. Install the minimum (or higher) required version of the Java VM. You can obtain this free from the hardware vendors or from Microsoft. Page 2 - bshell/jvmi configuration and administration

29 bshell/jvmi configuration and administration Problem Java exceptions are not handled correctly Other Possible cause and detection Cause: Incorrect signal handlers are used. How to detect: Log file entries. How to detect: Log file entries. Solution Change the override_java_signals and override_java_sigusr1 resources. If this does not solve the problem, contact the next support level. Send the generated log file to the next support level. bshell/jvmi configuration and administration - Page 3

30 bshell/jvmi configuration and administration Page 4 - bshell/jvmi configuration and administration

31 Appendix B Baan OpenWorld 2.2 Adapter property file syntax and properties This appendix presents the full syntax for the bus.properties file and describes the available properties, their valid values, and their default values. B.1 Properties file example The following is an example of a bus.properties file: [General settings] bus.bdf.iterator.size=10 bus.bdf.manager.timeout=10000 bus.default.backend= user.name= bus.component= [Directory settings] bus.services.directory.directory=com.eibus.services.directory.ldap.ldapdirectory bus.services.directory.serverurl=ldap://srv-nld-interb0.baan.com bus.services.directory.root=o=baan.com [Log settings] bus.log.file=c:\\buslog.xml bus.log.mask=0x1801e NOTE NOTE [Advanced settings] bus.default.protocol=socket bus.connection.max.readers= org.xml.sax.parser=com.jclark.xml.sax.driver bus.num.xml.parse.threads=1 bus.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 enter them twice, since Java uses the backslash as an escape character. If, for example you want c:\temp\buslog.txt to be your log file, you must enter c:\\temp\\buslog.txt. Baan OpenWorld 2.2 Adapter property file syntax and properties - Page 1

32 Baan OpenWorld 2.2 Adapter property file syntax and properties B.2 Properties This section describes the most commonly used properties in the bus.properties file. General settings bus.bdf.iterator.size The default number of records that are received in one fetch, enables you to limit the data that is transferred to the client in each message. You can override this default value in your application code. The amount of data delivered depends not only on the number of records delivered but also on the number of fields in a record and the number of associated tables. For smaller records, you can increase the number of records retrieved per fetch. For larger records, you can decrease the number of records retrieved. Default value: 250 bus.bdf.manager.timeout The default time (in milliseconds) that Baan OpenWorld 2.2 Adapter waits for a reply when performing a request to a server. You can override this timeout period in your application code. Default value: 60,000 bus.default.backend The backend that your programmed Manager connects to by default. You can override this default setting in your application code with the manager.initialize method. Default value: n.a. user.name This property is not currently used. bus.component The name of the local Baan OpenWorld 2.2 component, as registered in the Directory Service. You do not need to specify this parameter for anonymous clients that use a socket transport service. For all servers and named clients, and for anonymous clients that use MQSeries as their transport service, set this to the relevant component name. Default value: Fully qualified machine name. Page 2 - Baan OpenWorld 2.2 Adapter property file syntax and properties

33 Baan OpenWorld 2.2 Adapter property file syntax and properties Directory settings bus.services.directory.directory Contains the name of the directory server class. This can be either: com.eibus.services.directory.file.filedirectory or com.eibus.services.directory.ldap.ldapdirectory Default value: n.a. bus.services.directory.serverurl The name of the directory server to use. If you use an LDAP-compliant Directory Service, specify the URL of the directory server. If you use an XML file Directory Service, specify the full path for the file. The required syntax is: ldap://<ip_address or computer_name> <file_name> Default value: n.a. bus.services.directory.root The name of the domain in the directory server to use; that is, the root element of the Directory Service. This property is required for both LDAP and XML flat file Directory Services. The syntax is: o=<server_root> Default value: n.a. Log settings bus.log.file Can contain the path to a specific log file. If null, then messages are logged to System.out. Default value: n.a. bus.log.mask Bit pattern to activate logging on for specific categories of activity. The default value (0) specifies no logging on. The value FFFFFF specifies full logging on. Default value: 0 (no logging) Advanced settings bus.default.protocol This can be MQSeries, msmq, or socket Baan OpenWorld 2.2 Adapter property file syntax and properties - Page 3

34 Baan OpenWorld 2.2 Adapter property file syntax and properties Page 4 - Baan OpenWorld 2.2 Adapter property file syntax and properties

35 Appendix C Configuration of ASM for OpenWorld The ASM deamon is part of the Baan Logon deamon of the BaanERP installation. 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 service name used in OpenWorld. Configuration of ASM for OpenWorld - Page 1

36 Configuration of ASM for OpenWorld Example of an asmtypedef.xml file that starts a bshell and the ASM OpenWorld server. %USERDATA% is the serialized BusComponent that is send to the server. %PORT% is the port number that the ASM server uses to send the started serialized 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 refer to ASM BaanERP documentation. Page 2 - Configuration of ASM for OpenWorld