Technical Notes Porting Set 7 notes porting set 7.1c.pdf · Group: Product Information Edition: B...

BaanERP 5.0c

Technical Notes Porting Set 7.1c

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: U7592B USGroup: Product InformationEdition: BDate: April, 2001

i

Technical Notes Porting Set 7.1c

1 Porting set contents 1-1

2 To install the porting set 2-1What is a porting set? 2-1Installation description 2-1Installation in a UNIX environment 2-2Installation in a Windows NT environment 2-4Installation on IBM eServer iSeries (AS/400) 2-6Important Note on porting set 7.1c 2-7

3 Informix related topics 3-1Supported Informix versions 3-1Problem in Informix 9.20 (Level 2 mode) 3-1Required workaround for Level 2 mode 3-1Do not use KEYSTART optimizations in Informix 9.20 or later 3-2Workaround for Informix 7.31 on Windows NT 3-2Workaround for Informix on UNIX 3-3Create DBusers in BaanERP with Informix 7.31 Level 1 3-4Error 2222 in session "Initialize parameters" 3-4Problems with DataBase Access: error 25596 3-4

4 Oracle related topics 4-1Expand the shared library search path 4-1Actions for existing Oracle 8.0 environments 4-1Oracle 8.0 to 8.1 migration on UNIX 4-2Baan/Oracle/NT installation: Manual action needed after Oracle software

upgrade 4-2Upgrade BaanERP5.0b to BaanERP5.0c SP03 tools 4-3Oracle 8 on Unix 4-3

5 DB2 related topics 5-1Use latest DB2 fixpacks 5-1DB2 parameters 5-1DB2 Level 1 not shipped on Sparc_Solaris 5-1DB2 Level 1 not shipped on HP platform 5-2Link between BaanERP and RDBMS users 5-2

Table of contents

Table of contents

Technical Notes Porting Set 7.1cii

6 SQL7 related topics 6-1Use latest SQL7 fixpacks 6-1

7 Platform related topics 7-1Siemens platform 7-1Siemens platform: How to install and configure JAVA for the

BaanERP5.0c bshell on Reliant UNIX. 7-1Workaround in the �Oracle method� 7-3Compile C source with embedded JAVA 7-3Sequent platform: No JAVA support 7-4DEC platform: To prepare the unix system for installation 7-4Compaq C++ on Compaq Tru64 UNIX version 4.0F or later 7-4Compaq C++ on DIGITAL UNIX version 4.0E or earlier to link and run

programs 7-5AS/400 platform: OpenWorld 7-5S/390 platform 7-5

8 Other important remarks, known problems and workarounds 8-1Java Virtual Machine Integration (JVMI) 8-1Workaround to check if all mandatory tables are being audited (Windows

NT only) 8-1Upgrade BaanERP5.0b to BaanERP5.0c SP03 tools 8-3Shared memory (Unix) 8-3Import Data Dictionary (ttiex1288) session 8-3New BW-Client with new SSPI Login 8-4Blogin daemon 8-4BaanLogin 8-5Application Services Manager (ASM) 8-5BDBPRE and BDBPOST 8-6

Appendix A: Supported databases per platform in Porting Set 7.1c 1

Technical Notes Porting Set 7.1ciii

These technical notes contain last minute release information about the BaanERPporting set 7.1c

The following chapters are available:

� Chapter 1, �Porting set contents,� lists the contents of the porting-setdistribution CD-ROM.

� Chapter 2, �To install the porting set,� provides installation instructions forthe porting set.

� Chapter 3, �Informix related topics� describes the Informix related topics

� Chapter 4, �Oracle related topics,� describes Oracle-related topics.

� Chapter 5, �DB2 related topics,� describes DB2 related topics.

� Chapter 6, �SQL7 related topics,� describes SQL7 related topics.

� Chapter 7, �Platform related topics,� describes platform related topics.

� Chapter 8, �Other important remarks, known problems and workarounds,�describes other known problems and workarounds.

� Appendix A, �Supported databases per platform in Porting Set 7.1c�describes which databases are supported on which platform.

About this document

About this document

Technical Notes Porting Set 7.1civ

Technical Notes Porting Set 7.1c1-1

You can find the following directories and their respective contents on thedistribution CD-ROM:

� The Documents directory contains the PDF version of these technical notes.

� The I386/I386 directory contains the setup files for the 7.1c porting set forMicrosoft Windows on Intel architecture.

� The Unix directory contains subdirectories for the various hardware or UNIXoperating system combinations. In each <hardware>/<operating system>subdirectory you will find a compressed tar archive that contains the portingset.

� The BW directory contains the new Baan Windows client for machines withIntel architecture. The subdirectories are sorted on <language>/<platform>.

The 7.1c porting sets for AS/400 and S/390 are available on separate CD-ROMS.

1 Porting set contents

NOTE:

Porting set contents



What is a porting set?A porting set is a set of binaries that are operating system dependant. It is thelayer between the operating system and the application software. Baan regularlyreleases a new porting set. A mailfix number recognizes every modificationmade in the porting set.

Every porting set has a port number. Initially, all binaries have the same portnumber. If a fix is made on a binary before the next porting set is delivered, thatbinary will have another (higher) port number.

Installation descriptionBefore you start the installation of this porting set, read solution 113796 on theBaan Global Support website www.support.baan.com for the latest informationabout known installation problems or important solutions that were created afterthe release of this porting set.

Next you have to read the section �Important Note on porting set 7.1c� on page2-7.

Before you start doing further steps, first read Chapters 3, 4, 5 or 6 (dependant onyour database) and then Chapter 7 and 8.

Which of the following sections you must follow, depends on your softwareenvironment:

� �Installation in a UNIX environment�If you want to install this porting set in a BaanERP environment on a UNIXoperating system.

� �Installation in a Windows NT environment�If you want to install this porting set on a Windows NT operating system.

� �Installation on IBM eServer iSeries (AS/400)�If you want to install this porting set on an AS/400 system.

2 To install the porting set

To install the porting set


Installation in a UNIX environmentThe following procedure is technical in nature, and therefore you must read itcarefully before your perform the procedure or ask your system administrator toperform the installation.

Take following steps to install the new porting set:

1 Log on as user root.

2 Check if all users have logged off by typing the UNIX command:

ps -ef |grep bshell

If the grep command does not return a bshell entry, all users logged off.

3 Open the directory $BSE/etc, and stop Baan by carrying out the command:

./rc.stop

4 Stop the license daemon (if this process is not stopped by the rc.stop command)with the command licmon6.2 -k.

5 Transfer the compressed tar archive that corresponds with your hardware andoperating system from the Unix directory on the CD-ROM to an emptytemporary directory on your UNIX system.

You must possibly use a machine with a Microsoft Windows operating system toread the CD-ROM. Transfer the tar archive to a UNIX system. The files on theCD-ROM are stored on a Joliet file system.

6 Extract the files from the compressed tar archive to the temporary directory onthe UNIX system:

# cd <path># compress -d *# tar xvf *

where <path> is the temporary directory to which you copied the compressed tararchive that contains the porting set.

7 Remove the tar archive from the temporary directory on the UNIX system:

# cd <path># rm *.tar


NOTE:



8 Backup all environment directories that will be updated if you install the portingset. With the ls command in the temporary directory you can list the directoriesthat will be updated:

# cd <path># ls

where <path> is the temporary directory to which you copied the compressed tararchive that contains the porting sets.

9 Copy all files from the temporary directory to the Baan software environment:

# cd <path># cp -r -p * ${BSE}


The syntax of the cp command can vary. In this example above, the -r optionwill copy files recursively and the -p option will preserve permissions whilecopying. Refer to your system documentation for the correct cp syntax.

10 To ensure that the permissions are set correct, you must run the binperm6.2script. This script automatically corrects permissions in the $BSE/bin directory.

Change directorie to $BSE/bin and run the following command:

sh binperm6.2 .

11 You must generate a new $BSE/lib/shm_param file. Do the following:

Backup the �old� shm_param file.

#mv shm_param shm_param.old

Generate a new shm_param file:

$BSE/bin/shmvalues6.2>$BSE/lib/shm_param#chown bsp:bsp $BSE/lib/shm_param

12 Change directories to $BSE/etc and start Baan:

#cd $BSE/etc#./rc.start

Perform a final test before the system is released to the Baan users. For example,start a Baan session to check if you can access the Baan environment.

NOTE:



Installation in a Windows NT environment

Installation procedure

Before you install this new porting set verify that:

� No one is logged on to Baan.� No long-time running Baan jobs are active.

To install this new porting set, take the following steps:

1 Log on to the Windows NT Server that runs Baan.

2 Close all Baan related programs on the server, like Baan (MMC) NT managerand BECS.

3 Start the Task Manager, and click the Processes tab. Check if there are stillntbshell.exe processes running:

� If a ntbshell.exe process is running, check if everybody is logged off of Baan.

� If no one is logged on to Baan and any ntbshell.exe processes are stillrunning, select them and click End Process to stop these processes.

� Check if any database driver processes are still running:

for Informix: inf_srv.exefor Oracle: ora7_srv.exe (version 7) or ora8_srv.exe (version 8)for MS SQL Server: msql7_srv.exe (version 7.0)

If any Baan database driver processes are running, you must stop them. Selectthe process and click End Process to stop the process.

� Check if any other Baan processes are still running, such as BW, BECS, andBaan NT Manager.

The Baan NT Manager is the bentman.exe process.

If any Baan processes are still running, close these programs. If this is notpossible, select a process and click End Process to stop these processes.

4 Close the Event Viewer, if open, before you proceed.

5 a. Copy the current %BSE%\bin directory to %BSE%\bin.old.

b. Copy \winnt\baan\bin directory to \winnt\baan\bin.old.

To do this, you can select the folder bin, copy and paste to create a copy of thefolder bin, with the name Copy of bin (rename this folder to bin.old).

6 Run the setup.exe program from folder I386 on the distribution CD-ROM.

NOTE:



7 When the Welcome dialog box appears, click Next.

8 When the Software Licence Agreement dialog box appears, click Yes.

9 When the Select Environment dialog box appears, you have two options:

� Install new environment.� Select existing environment.

If you choose to install a new environment, select this option, type in the nameyou want to use, and proceed with the installation.

You can also select Select existing environment to select an environment whichneeds to be updated with this new porting set.

Once you have made your choice, click Next.

10 When the Setup Information dialog box appears, check if all information iscorrect. Verify the environment name and the target directory. If you wish tomake a change, click Back until you reach the desired dialog box, make thechanges, and click Next to return.

11 Click Next to copy files, create folders and icons, and complete the installationas prompted by the installer.

12 Once the installation has completed, check if the Baan services have startedagain. These are:

� BaanLicensing Service.� BaanLogic Service.� BaanSharedMemory Service.

Also, if used, start the BaanJobDaemon Service again.

Because the BaanJobDaemon Service is reregistered by the setup of the portingset, you must check the configuration settings of the BaanJobDaemon Service(Control Panel➤➤➤➤Services➤➤➤➤BaanJobDaemon service➤➤➤➤Startup). Reset thesettings. Remove Application lock on the Job Daemon (log on to Baan and runsession ttstpdellocks) and restart the BaanJobDaemon service.

13 Perform a final test before the system is released to the Baan users. For example,start a Baan session to check if you can access the Baan environment.

If you are running Baan in an Client-Server mode (separate Application Serverand Database Server), the setup procedure contains some additional steps; forexample, you are asked to supply the name of the other server and some log oninformation

NOTE:

NOTE:



Installation on IBM eServer iSeries (AS/400)1 Create a backup of your environment (including IFS)

2 Stop the Baan environment, which you want to install the new porting set for:

ENDBAAN BSE(�<BSE>�)

3 Insert the 7.1c porting set CD-ROM into the CD drive of your AS/400.

4 Sign on to the system as user QSECOFR.

5 From the command line issue the following command:

LODRUN DEV(*OPT)

6 Choose option 4. �Replace existing porting set�, and press Enter.

7 On the next screen specify the BSE path of your environment and press Enter.

8 Follow the instructions of the installation program.

9 If the porting set installation is finished, than a message �Installation completedsuccessfully� will appear on the screen. Press F3 to exit the installation program.



Important Note on porting set 7.1cPorting set 7.1c contains a modification in the execution of database queries,which verifies certain queries more strictly. The consequence is that someerroneous coding constructions in database queries are detected now and maycause SQL error messages followed by termination of the application session.

In order to prevent these problems from occurring, two strategies are available:

1 Install BaanERP5.0c Service Pack 6, when it becomes available, as itcontains all fixes required. In this situation also the other already availableBaanERP5.0c Service Packs (SP3 tools patch, SP4 and SP5) must beinstalled.

or, if you have no intention to install BaanERP5.0c Service Pack 6 (andprevious Service Packs):

2 Install a number of individual solutions created specifically for this purpose,which are listed in solution nr. 113357.

Recommendation: install BaanERP5.0c SP3 tools patchIt is strongly recommended to install BaanERP5.0c SP3 tools patch wheninstalling porting set 7.1c.

The installation is described in document U7531B US. Please read also theinstructions in solution 106071. After installation of the tools patch users maynot be able to login after convert user to runtime.

The following steps should be executed to fix this problem:

� Login as bsp

� If it is not possible to login, restore the userfile in $BSE/lib/user (copy ubsp-to ubsp)

� Install solution 113648

�� Create runtime DD

� Login again

Now the problem should be fixed.




Supported Informix versionsIn porting set 7.1c we have the following situation:

Informix 7.24: Only possible in Level 1 mode, this Informix version does notsupport Level 2. (Informix already stopped support for this version).

Informix 7.30: Only possible in Level 1 mode, this Informix version does notsupport Level 2.

Informix 7.31: Can be used both in Level 1 and in Level 2 mode.

Informix 9.20: Can only be used in Level 1 mode. (Level 2 does not work welldue to an Informix problem, see below).

Informix 9.21: Is not yet verified and released for BaanERP5.0c.

Problem in Informix 9.20 (Level 2 mode)During benchmarks Baan found some problems in Informix 9.20 using Level 2mode. Due to these technical issues IDS 9.20 Level 2 cannot be supported.

The problem has been fixed by Informix in versions IDS 9.21 UC5 /TC5 /FC5which are the minimum versions to be used for Level 2. The verification of IDS9.21 at Baan is going on but not yet completed.

If you want to use Level 2 mode now, you can only make use of Informix 7.31.

Required workaround for Level 2 modeIf you want to use the driver in Level 2 mode, perform this procedure on themachine where the Informix database driver will run.

1 After you install the porting set, make the following change to the db_resourcefile with a text file editor:

inf_use_prepare_cache:0

3 Informix related topics

Informix related topics


In Windows NT, db_resource is located in the directory %BSE%\lib\defaults,where %BSE% refers to the directory where the BaanERP software environmentis installed.

In UNIX, db_resource is located in the directory $BSE/lib/defaults where $BSErefers to the directory where the BaanERP software environment is installed.

2 You can now run the Informix database driver in Level 2 mode.

Do not use KEYSTART optimizations inInformix 9.20 or laterDo not use KEYSTART optimizations in Informix 9.20. In Informix 9.20 UC4,this problem will be solved by Informix. If you switch KEYSTARToptimizations on, you can experience error �874.

It is recommended to use iterative. The following is an example entry for${BSE}/lib/defaults/db_resource:

concat_expr:iterative

Workaround for Informix 7.31 on Windows NTThere is a known problem that occurs when you install BaanERP 5.0c withInformix Dynamic Server (IDS) version 7.31. This was verified on 7.31 TC2. Ifyour IDS installation is any other 7.31 TCx and this problem occurs, use thefollowing workaround.

1 Perform the IDS installation as described in BaanERP 5.0c Installation Guidefor Informix on Windows NT (U7343C US).

2 Make sure that you select I-Connect for installation when you install IDS. Donot install I-Connect as described in the manual.

3 Install BaanERP 5.0c as described in BaanERP 5.0c Installation Guide forInformix on Windows NT (U7343C US). In 5 to 10 minutes the install failswith the following timeout error:

4 Click OK, then click OK again to exit the installation.



5 Delete the directory you specified for Baan during the Baan installation, forexample, BaanERP50c.

6 Run regedit. Find the name of the Baan directory (for example,BaanERP50c) located in this registry section: HKEY_LOCAL_MACHINE,Software, Baan.

7 Delete the registry entry that has the name of the Baan directory (forexample, BaanERP50c).

8 Go to Control Panel, Services. Click on the Informix Dynamic Serverservice and click Start. Make sure it is also set to Automatic.

9 Reinstall BaanERP 5.0c as described in BaanERP 5.0c Installation Guide forInformix on Windows NT (U7343C US).

10 When the Enter Informix Parameters dialog box appears, change the Baandatabase dbspace value to a name different from the one used during theprevious BaanERP 5.0c installation. For example, if you used the defaultsetting of baandb.dbs, change it to baandb1.dbs.

11 Click Next. The installer displays the message �Dbspace baandb_dbs exists.Do you want to remove and recreate it?� The value baandb_dbs is the defaultname.

12 Click Yes. The next message is �Dbspace baandb_plog exists. Do you wantto reuse the existing dbspace?� The value baandb_plog is the default name.

13 Click Yes.

14 Click Next to finish the installation.

Workaround for Informix on UNIXThe following workaround applies to every Informix installation on UNIX.

To avoid the error Connection with Database lost, BW will exit, add thefollowing strings to the $BSE/lib/defaults/db_resource file immediately after theinstallation:

� inf_init:0400.� inf_session_pool_length:0.� nf_connection_pool_length:0.



Create DBusers in BaanERP with Informix7.31 Level 1In some cases there is a problem with converting users to the Database. Newlycreated users cannot login and get Bdb_errno1951 on ttadv999.

The problem can be solved by using the binary inf_maint to create the databaseusers and link them to the Baan users.

Error 2222 in session "Initialize parameters"If you run the session "Initialize parameters" you will receive the following BW-Messages:

1 : process 7 - Fatal error : Error 2222 (database error 1222) on

tdsls000902 in select

2 : process 7 - Fatal error : Can not continue in tcmcs0295m000 in

DLL:otcmcsdll0095 (tcmcs.dll.0095.create.table)[retry.point]

3 : process 7 - Error : tcmcs0295m000: A not terminated transaction

is aborted

Database error: Error: 1222 Value will not fit in a SMALLFLOAT

This problem is related to the problem with Informix 9.20 on the the DEC Unixplatform

An Informix patch should solve this problem.

To get this patch please contact Informix.

Problems with DataBase Access: error 25596In some cases you will get Informix error 25596 (Baan error 26596) whileconnecting as a new created user. There is workaround to solve this problemtemporarily. Add the concering user to the os group Informix and the problem isgone. An official solution will be available soon.


Expand the shared library search pathDuring the installation on UNIX systems of Oracle 8.x, you must sometimesexpand the shared library search path by adding the $ORACLE_HOME/libdirectory. If the shared library search path is not extended, Oracle tools such assqlplus cannot find the used shared Oracle libraries.

Note that the variable that contains the shared library search path has differentnames on different platforms.

On Fujitsu Siemens Reliant Unix, you must specify the following forOracle 8.0.5:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/CDS++/lib:/home/oracle/8.0.5/lib

Actions for existing Oracle 8.0 environmentsExisting Oracle8.0 environments with porting set 7.1a.01 or older must takesome actions before they upgrade the porting set to porting set 7.1c.

Specify ora_column_formatSpecify the ora_column_format:7 resource value in the$BSE/lib/defaults/db_resource file. This will force the new Oracle8 driver tocomply with Oracle7 data dictionary constraints instead of Oracle8 constraints.(If you do not specify this, you will experience error BDB_512). This appliesboth to UNIX and NT.

The old Oracle8 driver used the Oracle7 constraints. Since the Oracle8i project,the Oracle8 constraints are used by default, which causes some inconveniencesfor existing installations.

Check if $BSE/lib/ora/oracle_home existsThis only applies to UNIX installations. After the installation is complete, checkif $BSE/lib/ora/oracle_home exists, if not, run the ora_update script (located in$BSE/bin) to generate it. If you perform an official upgrade, the directory mustexist. If you must replace the porting set you must take notice.

4 Oracle related topics

EXAMPLE:

Oracle related topics


Oracle 8.0 to 8.1 migration on UNIXUse Oracle tools for your migration and refer to the Oracle documentation

When $ORACLE_HOME has been changed, check and update the followingtwo files:

� $BSE/lib/tabledef6.2� $BSE/lib/defaults/db_resource

Specify ora_column_formatWhen upgrading an existing environment to oracle 8.1.x add"ora_column_format:7" to the dbresource file.

After the upgrade run ora_update (in $BSE/lib/ora)

Baan/Oracle/NT installation: Manual actionneeded after Oracle software upgradePlease note that this issue only applies to Baan installations on Windows/NTusing Oracle as RDBMS.

Depending on the version of the Baan software installer that was used to setupthe installation, some connection problems can arise after upgrading the Oraclesoftware version. These problems can arise after upgrading the Oracle softwareby using the tools delivered by Oracle. The symptoms are often quite vague, andare caused by the mix up of different Oracle versions that are not fullycompatible.

The problems are caused by the fact that the Baan/Oracle installer added someinformation to the Windows/NT registry and Baan configuration files that aredependent on the Oracle installation. When the actual installation of Oracle onyour computer changes, these registry entries still contain the old, and thuspossibly outdated, information.

Check the settings of ORACLE_HOME in the %BSE%\lib\tabledef6.xfile. This environment variable should be set to the directory path of the newOracle version.

To prevent problems, some Baan registry settings must be checked, and possiblychanged, after upgrading the Oracle version.



Check the following registry entries for all installed %BSE% environments:

HKEY_LOCAL_MACHINE SOFTWARE Baan %BSE% Environment PATH

When the registry entry PATH does not exist in this tree, you must not make anychanges. You probably used an installer version that did not yet generate thisentry.

When the registry entry PATH does exist, the value must be checked andpossibly changed. When the value of PATH contains the directory path to theprevious Oracle version, the value must be edited. The path of the previousOracle version must be replaced by the path to the new Oracle version.

HKEY_LOCAL_MACHINE SOFTWARE Baan %BSE% Environment ORACLE_HOME

If the registry entry ORACLE_HOME exists, the value must be checked andpossibly changed. It should contain the directory path to the Oracle softwareinstallation that you will use.

Upgrade BaanERP5.0b to BaanERP5.0c SP03tools

Oracle 8 on UnixYou must run script ora_update. Solve this problem by running script$BSE/bin/ora_update after the Unix part of the installation, and before startingBW with ottiex1287.




Use latest DB2 fixpacksDuring tests, problems arose that were solved by installing the newest DB2fixpacks. Check with IBM for the latest DB2 fixpacks for your hardwareplatform. This information can be found at:

<http://www-4.ibm.com/software/data/db2/db2tech/indexsvc.html>

DB2 parametersBefore you start the installation of DB2v5_inst6.2, the following DB2parameters must be set from the db2 prompt:

� update db cfg for baan using DBHEAP 10000

� update db cfg for baan using LOGBUFSZ 128

� update db cfg for baan using LOCKLIST 500

� update db cfg for baan using APPLHEAPSZ 4096

� update db cfg for baan using LOCKTIMEOUT 20

� update db cfg for baan using NUM_IOCLEANERS 6

� update db cfg for baan using LOGFILSIZ 4096

� update db cfg for baan using LOGPRIMARY 8

� update db cfg for baan using SOFTMAX 400

DB2 Level 1 not shipped on Sparc_SolarisAlthough you can find the DB2 database driver for Sparc_Solaris in the portingset, you must not use Level 1 mode. Both on SUN and Fujitsu Siemens hardwarea severe error still occurs on the Sparc_Solaris Operating system. Baan isworking on the problem, but has not yet resolved it.

5 DB2 related topics

DB2 related topics


DB2 Level 1 not shipped on HP platformAlthough you can find the DB2 database driver for the HP platform in theporting set, you must not use Level 1 mode. Baan is working on the problem, buthas not yet resolved it.

Link between BaanERP and RDBMS usersCheck if the user bsp is registered as �Created in RDBMS�.

� Start session ttdba0515m000

� Double click on the system user (bsp on Unix, baan on Windows NT orWindows 2000)

� Check if the Status is �Created in RDBMS�. If not click on �Convert User� toconvert the user to the database.

This action is needed to make a connection as baan user with another system useraccount. If the user baan or bsp is not registered as RDBMS user you will geterror 514 while connecting via another system user. In fact each baan user mustbe a member of the database group (default name: baandb)


Use latest SQL7 fixpacksIf you intend to use the SQL database driver provided with this porting set, youmust meet the following software requirements:

� Install the latest Service Packs for SQL version 7. You must at least haveinstalled Service Pack 1 if you want to use the porting set 7.1c and later.

6 SQL7 related topics

SQL7 related topics



Siemens platformThe LD_LIBRARY_PATH settings:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/java/jdk12/jre/lib/mip

s/native_threads:/opt/java/jdk12/jre/lib/mips/classic/native

_threads

Siemens platform: How to install andconfigure JAVA for the BaanERP5.0c bshellon Reliant UNIX.1 Install JRE (Java Runtime Environment) and JENV (Java Application

Environment). Both are part of the JDK (Java Development Kit). For moreinformation see /opt/readme.

JRE and JENV can be found on CD-SYS-MI 1 which belongs to the standardCD set.

default path JRE = /opt/java/jre121default path JENV = /opt/java/jdk12

2 Install DCE-THR (Threads) for Reliant UNIX 5.43 or SIthreads (Threads) forReliant UNIX 5.44 or higher.

DCE-THR or SIthreads can be found on Reliant UNIX OS which belong tothe standard CD set.

default path DCE-THR = /opt/threaddefault path SIthreads = /opt/thread

7 Platform related topics

Platform related topics


3 Take care that the Operating System is able to find all the libraries. Foraccessing the right libraries during execution of the software, the system mustbe able to find these libraries.

There are 2 ways to fix this:

− Add JENV path info to LD_LIBRARY_PATH as follows:LD_LIBRARY_PATH=$LD_LIBRARY_PATH:

− /opt/java/jdk12/jre/lib/mips/classic/native_threads:/opt/java/jdk12/jre/lib/mips/native_threads:/opt/thread/lib

export LD_LIBRARY_PATH

Because Oracle also extends LD_LIBRARY_PATH we will call this the�Oracle method".

Within this method the "rexec" connection with the BW won't work, becauseprofile�s are not read and LD_LIBRARY_PATH is not set. Therefor youhave to use a "baanlogin" connection.

− Create symbolic links for the necessary libraries:ln -s /opt/java/jdk12/jre/lib/mips/native_threads/libhpi.so.1.2 /usr/lib/libhpi.so.1.2

ln -s /opt/java/jdk12/jre/lib/mips/native_threads/libjava.so.1.2 /usr/lib/libjava.so.1.2

ln -s /opt/java/jdk12/jre/lib/mips/classic/native_threads/libjvm.so.1.2 /usr/lib/libjvm.so.1.2

Because Informix also create symbolic links we will call this the �Informixmethod�.

Within this preferred method both the "rexec" and the �baanlogin� connectionwith the BW will work.



Workaround in the �Oracle method�1 Edit $BSE/lib/ipc_info

Change line �bshell s 0 0 p ${BSE}/bin/bshell6.2�

into �bshell s 0 0 p ${BSE}/bin/bshell6.2.sh�

2 Create $BSE/bin/bshell6.2.sh

#!/bin/ksh

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/java/jdk12/jre/lib/mips/classic/native_threads:/opt/java/jdk12/jre/lib/mips/native_threads


exec $BSE/bin/bshel6.2 $*

Compile C source with embedded JAVA1 Set LD_LIBRARY_PATH

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:

/opt/java/jdk12/jre/lib/mips/classic/native_threads:/opt/java/jdk12/jre/lib/mips/native_threads:/opt/thread/lib


2 all C compiler with extra options:

Example:

cc program.c -o program -FX4y -Kthread

-I/opt/java/jdk12/include

-I/opt/java/jdk12/include/reliantunix

-lhpi

-L/opt/java/jdk12/jre/lib/mips/native_threads

-L/opt/java/jdk12/jre/lib/mips/classic/native_threads

-ljvm

-lsocket -lnsl -ldl



Remarks:� flag "-lc" is not needed anymore.� flag "-Kthread" is able to find �libc_r� instead of �libc�.

JENV V1.2A requires CDS++RTS (Version 1.0C32 or higher). An updateinstallation from JAE/JDEV 1.0 or 1.1 to JENV 1.2A is not possible. IfCDS++RTS was not installed under �/opt/CDS++�, you must assign �<CDS++installation directory>/lib/� in the LD_LIBRARY_PATH. Read/opt/readme/jre12.GB/readme and /opt/readme/jenv12.GB/readme for moreinfo.

Sequent platform: No JAVA supportJava Virtual Machine Integration is not implemented in porting set 7.1c onSequent.

DEC platform: To prepare the unix system forinstallationTo avoid problems, Baan used a newer version of the compiler (the 6.n compiler)for the porting set for DEC Unix. In some cases (this depends on the currentversion of your operating system, as described in the following sections) youmust install a patch in your operating system.

If you plan to use the Bshellxma you must install the patch. In all other cases,Baan recommends you to install the patch.

Code generated by the version 6.n compiler requires a newer version of the C++Run-Time library (libcxx) than is provided by Compaq Tru64 UNIX versionsearlier than 4.0F.

Compaq C++ on Compaq Tru64 UNIX version 4.0F orlaterOn Compaq Tru64 UNIX 4.0F or later, the version of libcxx.so that is requiredfor use with Compaq C++ version 6.n is installed by the operating system; nospecial actions are required.

NOTE:



Compaq C++ on DIGITAL UNIX version 4.0E or earlier tolink and run programsOn version 4.0E or earlier, you must install the following subset from theCompaq C++ version 6.n kit before you can link or carry out programs:

Compaq C++ Run-Time Library (libcxx) for DIGITAL UNIX V4.0E and earlier

If you attempt to link code generated by Compaq C++ version 6.n before youinstall the compiler or this subset, the link can fail because of unresolvedsymbols.

You must also install this subset (or the compiler kit) on any version 4.0E orearlier system on which you want to carry out code generated by Compaq C++version 6.n. If you attempt to carry out a program without having installed thesubset or compiler, the image activator displays error messages about unresolvedsymbols.

You can install the libcxx subset without installing the base compiler subset. Ifyou need this libcxx., you can order it from Compaq and install it. You can alsoget these libraries at:

ftp://ftp.support.baan.com/updates/port/DEC_LIB/CXXREDIST621V01.tar

AS/400 platform: OpenWorldIf using Baan Open World Adapter on AS/400, then the following line must beadded to file ${BSE}/lib/bse_vars:

BSE_CLASSPATH=<BSE>/java/b3.jar

e.g. if your BSE is /baanERP/bse, than this line would be:

BSE_CLASSPATH=/baanERP/bse/java/b3.jar.

Alternatively you can also set BSE_CLASSPATH in the Baan Windows (BW)configuration by adding the following command to it the 'Command' field on theBshell environment tab:

set BSE_CLASSPATH=<BSE>/java/b3.jar

S/390 platformThe 7.1c porting set for S/390 is not yet available (status middle of April 2001).The porting set will be shipped as soon as possible.

NOTE:




Java Virtual Machine Integration (JVMI)Check the file flags of file libjvm2bvm.so for using JVMI

ls �l $BSE/shlib/libjvm2bvm.soThe right file flags are �rwxr-x---

To set this flags type:

chmod 750 $BSE/shlib/libjvm2bvm.so

Workaround to check if all mandatory tablesare being audited (Windows NT only)After the installation, if you open the file tabledef6.2 in the ${BSE}/lib directory,you will notice that audit is not on for the mandatory tables. At the end of eachentry an N is placed.

cfcec000:*:msql7:Ncfcmc000:*:msql7:Ncfcmd000:*:msql7:Ncfcms000:*:msql7:Ncfcvm000:*:msql7:Ncfint000:*:msql7:Ncpcom000:*:ms

8 Other important remarks, knownproblems and workarounds

Other important remarks, known problems and workarounds


However, if you start the Tables by Database (ttaad4111m000) session, as shownin Figure 1, you will see that the audit is on:

Figure 1 Tables by Database (ttaad4111m000)

You cannot run the Create Runtime Database Definitions (Tabledef)(ttaad4113s000) session to solve this because, as you will notice, the tabledef6.2file will not change.

You can solve this problem if you carry out the following steps:

1 Start the Database Definitions (ttaad4510m000) session.2 Select the definition of database 001 by double-clicking its entry.3 Clear the System Name field.

From the Specific menu, select Convert to Runtime. The Create RuntimeDatabase Definitions (Tabledef) (ttaad4113s000) session starts.

Click the Convert button. A new tabledef6.2 file is created. You will notice thatthe file is updated, and the N is changed to Y (in the following example, Oracleis used as the RDBMS).

cfcec000:*:oracle7(ORACLE_HOME=D:\ORANT,ORACLE_SID=BAAN,NLS_SORT=BINARY):Ycfcmc000:*:oracle7(ORACLE_HOME=D:\ORANT,ORACLE_SID=BAAN,NLS_SORT=BINARY):Ycfcmd000:*:oracle7(ORACLE_HOME=D:\ORANT,ORACLE_SID=BAAN,NLS_SORT=BINARY):Ycfcms000:*:oracle7(ORACLE_HOME=D:\ORANT,ORACLE_SID=BAAN,NLS_SORT=BINARY):Ycfcvm000:*:oracle7(ORACLE_HOME=D:\ORANT,ORACLE_SID=BAAN,NLS_SORT=BINARY):Y



cfint000:*:oracle7(ORACLE_HOME=D:\ORANT,ORACLE_SID=BAAN,NLS_SORT=BINARY):Ycpcom000:*:oracle7(ORACLE_HOME=D:\ORANT,ORACLE_SID=

Upgrade BaanERP5.0b to BaanERP5.0c SP03tools

Shared memory (Unix)This problem occurs when you run the Import Data Dictionary 1 (ttiex1287 )session during the BW part of installation.When you start BSE a core dump isgenerated and a message is displayed saying that shared memory is full. Solvethis problem by moving $BSE/lib/shm_param to shm_param_bak and creating anew shm_param file using �shmvalues6.2 > shmparam�.

Import Data Dictionary (ttiex1288) sessionWhen you run the Import Data Dictionary 2 (ttiex1288m000) session the illegalobject message is displayed, as is shown in the figure 2 . Solve this problem bylogging in as user bsp and running the Configure Application (ttiex3225m000)session . Error message

Figure 2 illegal Object error message



New BW-Client with new SSPI LoginPorting set 7.1c contains the new BW version 7.1c.137. This version containscombined functionality for Unified Logon and SSPI on Windows NT andWindows 2000. In this version the Connection protocol �Unified Logon� is notlonger available as a choice field. All existing configuration files with UnifiedLogon settings will be converted to SSPI automatically. It is not necessary tochange a setting manually.

You can get a description of Unified Logon and SSPI in solution 70306�Information about Rexec, BaanLogin, Unified Logon, SSPI functionality� onthe Baan Support Site.

Blogin daemonIn this porting set new functionality is added: �Application Services Manager� -ASM.

ASM is provided by the BaanLogin Service. For Unix platforms this is handledby the blogin daemon. Under NT and Windows 2000 the Baan Logic Servicehandles the ASM requests.

When the blogind6.2 (or when rc.start, both on Unix ) is started the followingmessage can be displayed:

blogind6.2: Cannot open Type Definition file:

/usr1/baan5/bse/lib/asmtypedef.xml

In case of NT or Windows 2000 and starting the BaanLogin Service this errormessage may appear in the Event Viewer.

The ASM feature requires two XML files. This files will not be delivered withthe porting set. The two files will be generated with the ASM sessions which willbecome available in BaanERP5.0c Servicepack 5 and PMC solution 111579.

This means that the message can be ignored or the ASM functionality can bedisabled by:

Unix: Edit the $BSE/etc/rc.start_blogind script and add the �-a� option to thelines where the blogind is started (below �Initializing BaanLoginDaemon�).

NT: Add a new registry key in:HKEY_LOCAL_MACHINE\Software\Baan\Services\Protocols. Thename of the key is �ASMEnabled�, the type should be DWORD and thevalue should be 0 to disable ASM.



BaanLoginWhen connecting from BW, running on your client, to the BaanERP server, aservice (also called a daemon) is needed at the server to authenticate theincoming request and to start the required Baan Virtual Machine (bshell). Thedaemon that was used by the Baan implementation for this purpose is a standardsystem service: the rexec daemon. This daemon accepts the username, passwordand the command to start from BW and will start the requested command afterauthenticating the username/password combination.

The drawback of the rexec protocol is that the password of the user is sent inplain text over the network connection. Intruders could analyze the TCP/IPtraffic and in that way get hold of user passwords.

To solve this security leak, in the last few porting sets the BaanLoginfunctionality is delivered. The BaanLogin protocol is a Baan proprietary protocolin which the user password is send encrypted from the client to the server. TheBaanLogin daemon is part of the porting set and is started as follows.

Unix: There is a new rc.start_blogind script in the $BSE/etc directory that isexecuted by the $BSE/etc/rc.start script. In this way the BaanLogindaemon is started automatically at system startup.

NT: The BaanLogin functionality is build into the already existingBaanLogicService. This service is made a NT service when BaanERP isinstalled. This way, the BaanLogin functionality is started automaticallywhen the NT server comes up.

In the BW configuration, a choice can be made to connect to the server via therexec protocol or the BaanLogin protocol. Baan strongly advises to use theBaanLogin protocol to protect passwords from intruders on the network.

Application Services Manager (ASM)Within BaanERP there is sometimes the need to have a 3GL or 4GL session thatalways runs on the system. An example of this is the jobdaemon, which is a 4GLapplication service that should always run on the system, independent of anyuser.

Until now, the jobdaemon was started on Unix by a rc.start script and on NT wedeveloped a dedicated NT service to get the jobdaemon running. This was not avery extensible architecture and therefore Baan felt the need to have a genericframework where you can easily configure, start and stop these kind ofapplication services. This is what the Application Services Manager (ASM) isdesigned for.



Using some Baan 4GL sessions (can be found in BAAN Tools ➤➤➤➤ ApplicationConfiguration ➤➤➤➤ Application Services Manager), the system administratorcan configure application services (also called �Instances�). This configuration isconverted to two XML runtime files ($BSE/lib/asmtypedef.xml and$BSE/lib/asminsdef.xml). These configuration files are read by the ASMdaemon, so the daemon knows which instances are available. The daemon thenwaits for incoming requests to start or stop instances. Possible clients of theASM daemon are:

� ASM MMC snapin. This is a administrative tool, where you can list alldefined instances and start/stop the instances.

� Command Line Interface. The functionality of the CLI is comparable with thesnapin, but can be started directly on the Operating System command promptof the BaanERP server system. The CLI is part of the porting set and thuslocated in $BSE/bin. The name is �asm_cli6.2� for Unix and �asm_cli.exe� forNT.

� Other software components (like Baan OpenWorld) can have an integrationvia ASM, using the ASM client API. In these cases, the usage of ASM istransparent to the end-user.

For details about configuring ASM and how to deal with the snapin or thecommand line interface, we refer to the System Administrators Guide,chapter 16.

BDBPRE and BDBPOSTBdbpre and bdbpost are supporting long file and directory names includingspaces within their names. Because the program parameters are seperated byspaces you must define the import and export file parameter with double quoteslike �<path and file name>�

Example (use bdbpre6.2 and bdbpost on Unix)

Bdbpre �q d:\export files\baan �Nttaad100 �C000Result: No output

Bdbpre �q �d:\export files\baan� �Nttaad100 �C000Result: Works Fine!

Technical Notes Porting Set 7.1cAppendix A: Supported databases per platform in Porting Set 7.1c - Page 1

Supported OS Oracle 7.3.4 Ora 8.04-8.1.7 Inf 7.24 - 9.20 DB2 V5.0 - 7.1 SS 7.0

L1 L2 L1 L2 L1 L2 L1 L2 L1

DEC_ALPHA\True64_Unix 4.0d - 5.0 X X X X

FUJITSU-SIEMENS_MIPS(R10\Reliant UNIX)

5.44.C10 -5.44Cx

X X X X

HP9000_PA8000\HPUX 11.00 X X X X 6.1-7.1

HP9000_PA_RISC\HPUX 10.20 - 11.00 X X X X 6.1-7.1

IBM_AS400\OS400 V4R3 - V4R5 Integrated

IBM_RS6000\AIX 4.3 X X X X 5.2-7.1 6.1-7.1

IBM_S390\OS390 V2R6-V2R10 5.1-6.1 6.1

INTEL\WIN NT 4.0 X >=8.1.6 X X 5.2-7.1 6.1-7.1 X

INTEL\WINDOWS 2000 Windows 2000 >=8.1.6 6.1-7.1 6.1-7.1 X

SEQUENT_INTEL\DYNIX_PTX 4.4.6 - 4.4.7 X X X X

SUN_SPARC\SOLARIS 2.6 - 2.7 X X X X 6.1-7.1

Appendix A: Supported databases perplatform in Porting Set 7.1c

Appendix A: Supported databases per platform in Porting Set 7.1c

Technical Notes Porting Set 7.1cPage 2 - Appendix A: Supported databases per platform in Porting Set 7.1c

Date post:	01-Oct-2020
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times