Important Notices
The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor. By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor pursuant to a separate agreement (Purpose). In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above. Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause.
Trademark Acknowledgements
Infor and Infor Global Technology Solutions are trademarks or registered trademark of Infor in the United States and/or other countries. All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners.
Publication Information
Document code: U7434F US Release: Infor ERP Baan IV, Baan 5.0, LN 6.1 Publication date: October 07
Table of Contents
Chapter 1
Setup packages ......................................................................................................................... 1-1 Hardware and software requirements ........................................................................................ 1-2 Chapter 2 Install Infor BW using the MSI ............................................................................... 2-1
To install the Infor BW software ................................................................................................. 2-1 To upgrade the Infor BW software ............................................................................................. 2-4 To silently install the Infor BW software ..................................................................................... 2-6 Chapter 3 Miscellaneous administration tasks...................................................................... 3-1
The Infor BW Environment and Configuration Selector.............................................................. 3-1 Installation directory of Infor BW ................................................................................................ 3-7 Infor Worktop ............................................................................................................................. 3-8 How to determine version information........................................................................................ 3-8 To uninstall the Infor BW client ................................................................................................ 3-11 Chapter 4 Infor Global system policy options ....................................................................... 4-1
Password storage ...................................................................................................................... 4-2 BW configuration editing ............................................................................................................ 4-3 Chapter 5 Environment variables ........................................................................................... 5-1
-Set command............................................................................................................................ 5-1 Applicable for all Infor ERP versions.................................................................................... 5-1 Applicable for Infor ERP Baan 5.0c and later....................................................................... 5-1 Applicable for Infor ERP Baan 5.2 and later ........................................................................ 5-3 Applicable for Infor ERP LN 6.1 and later ............................................................................ 5-3
ii
| Table of Contents
Known Issues.......................................................................................................... 6-1 Server Busy message when starting a .bwl file.......................................................................... 6-1
Chapter 6
This document is an Installation Guide that describes how to install the Infor ERP Baan IV or ERP Baan 5.0c or ERP LN Windows Client software. The installation examples in this document use the description for the Infor ERP LN 6.1 version; however, the process for the Infor versions is the same. Note: For Infor ERP Baan 5.2a and ERP LN 6.1, you additionally need to install Infor Worktop afterwards. This document contains the following chapters: Chapter 1, Overview of Infor BW Installers, describes the different Infor BW Installer setup packages. In addition the hardware and software requirements for Infor BW are listed in this chapter. Chapter 2, Install Infor BW using the MSI package, describes how you can install the Infor ERP Baan Windows client software using the MSI based setup package. Chapter 3, Miscellaneous administration tasks, describes how you can perform miscellaneous administration tasks. Chapter 4, Infor Global system options, describes how you can use the Infor Baan ERP system policy options. Chapter 5, Environment variables, describes how you can use the environment variables in Infor BW. Chapter 6, Known Issues, describes the issues that were encountered.
iv
| Table of Contents
Send us your comments We continually review and improve our documentation. Any remarks/requests for information concerning this document or topic are appreciated. Please email your comments to documentation@infor.com. In your e-mail, refer to the document code and title. More specific information will enable us to process feedback efficiently.
Table of Contents
|v
This chapter describes: The different Infor BW Installer setup packages The hardware and software requirements for Infor BW Infor BW is a graphical user interface (GUI) program that runs on an Intelcompatible PC in a Windows XP or higher environment. BW displays the Infor software as an application with the same look and feel as a native Windows application.
Setup packages
The MSI based setup packages use the Microsoft Windows Installer feature. These packages are available for Infor ERP Baan IVc4, Infor ERP Baan 5.0 and Infor ERP LN6.1. You can find these setup packages on the locations shown in the following tables. Setup locations Infor ERP Baan IVc4 Medium Porting set CD for Unix Windows Master distribution CD ftp.support.baan.com Type MSI MSI MSI Location \Bw \Bw Refer to solution 13743
1-2
Setup locations Infor ERP Baan 5.0c Medium Porting set CD for Unix Windows Master distribution CD ftp.support.baan.com Type MSI MSI MSI Location \Bw \Bw Refer to solution 13743
1) The InstallShield 3 based package which is delivered with a Windows Master distribution CD, also contains the server components. During setup you can choose which components you want to install. Setup locations Infor ERP LN 6.1 Medium Enterprise Server CD ftp.support.baan.com Type MSI MSI Location \Clients\12347097_03_Infor_BW_xxx Refer to solution 13743
Close all running applications. In the directory where the MSI setup package is located, start the Setup.exe file. A Windows Installer progress indicator appears:
This dialog box closes automatically and the Welcome dialog box will appear.
2
Click Next.
2-2
Fill the User Name and Organization. Typically, Infor Baan ERP menu items appear on the menus of all users of this computer. If you want these menu items to appear only on the current users menus, select Only for me. Click Next. The Setup Type dialog box appears:
| 2-3
Select setup type Complete, click Next, and proceed to Step 10. For advanced options, select the setup type Custom and click Next to continue. The Custom Setup screen appears:
6 7
To defer the installation of the Infor Baan ERP Client software, click the small down arrow located immediately to the right of the hard drive icon ( . On the drop down menu that appears, select This feature will be installed when required, click Next, and skip the remainder of this step.
If you select the deferred installation option, any specifications you make to the Baan Environment or the installation location will be ignored. If preferred, change the name of the Baan Environment. The Baan Environment name is a way to identify different versions of Infor BW on a single system.
8
For some versions of Baan ERP, the MSI setup package contains both a DBCS and a Unicode variant of BW. See the section Setup packages for an overview of these packages. On NT based systems (Windows 2000 or higher versions), by default the Unicode variant of BW will be installed.
2-4
To enter another path, accept the default path or click Change To continue, click Next. The Ready to Install the Program dialog box will appear. To continue with the displayed setup, click Install. To change the displayed setup, click Back. After you install the software, to exit the installation script, click Finish. If you are prompted to restart your computer, do so before continuing. Proceed with the miscellaneous administration tasks in Chapter 3.
10 11 12
Close all running applications. In the directory where the MSI setup package is located, start the Setup.exe file. When you are upgrading to a new Infor BW version for the same backend version, the following dialog will appear:
| 2-5
When you have an Infor BW version for another backend version, or an InstallShield 3 based Infor BW package installed on your system, the following dialog will appear:
To keep your existing Infor BW installation and to install a new version of Infor BW next to the already installed version, select Install new environment. When you choose this option, the installation will proceed as described in section To Install Infor BW software, step 2. Choose Select existing environment for updating. To replace an existing Infor BW installation with a new version, select one of the environments shown in the list.
To continue the upgrade process, click Continue. The upgrade will proceed. When the upgrade is finished, the following dialog will appear:
To exit the installation script, when the setup is complete, click OK. You can use Infor BW with the existing configurations, or proceed with the miscellaneous administration tasks in Chapter 3.
2-6
SYNOPSIS
setup [/s [/u [environment]] [/d <directory>]]
DESCRIPTION
This command will install Infor BW on the system. When no options aregiven, the setup tool will communicate with the user through Windows dialogs. The /s option can be used to allow the setup to be performed in silent mode. In silent mode, the setup tool will not show any dialogs, progress bars, or failure messages. The /u option can be used to ask the setup program to replace an existing Infor BW installation when an Infor BW version was already installed. When no Infor BW version was installed on the system, this option is ignored. If the /s option is specified without the /u option, and there is already one or more Infor BW versions on the system installed, the setup will exit with an error code. To the /u option an <environment> name can be added. This instructs the setup tool to replace a named environment. This is needed when a system already has two or more InstallShield 3 variants of Infor BW installed. When an environment name is omitted while two or more InstallShield 3 variants of Infor BW are installed, the setup tool will exit with an error code. The /d <directory> option can be used to instruct the setup program to install a new version of Infor BW in the indicated directory. This option can only be used when no Infor BW version is already installed on the system.
EXIT CODES
The following exit codes are defined: Code 0: Installation was successful. Code 1: A version of this setup.exe is already running. Code 2: Operating System version could not be determined. Code 3: No admin rights. Code 4: Error installing MSI runtime files.
| 2-7
Code 5: Error installing Infor BW. Code 6: User Canceled installation. Code 7: Error un-installing Infor BW. Code 8: Missing update flag/environment name. Code 9: Wrong command line options used. Code 10: Option /d specified while a version of BW is already installed.
This chapter describes miscellaneous administration tasks and contains the following sections: The Infor BW Environment and Configuration Selector The installation directory of Infor BW Worktop The procedure to uninstall Infor Baan ERP Windows
Start the Infor BW environment and Configuration Selector (BECS). Depending on the version of Infor ERP a different program folder entry must be selected. See the following table: BECS Start program folder Version Infor ERP Baan IVc4 Infor ERP Baan 5.0c Infor ERP LN 6.1 Program Folder Start Start Start Programs Programs Programs BaanIV Baan ERP Infor ERP BaanIV BaanERP Infor BECS
3-2
Select the new environment (preceded with <empty>), and on the File menu, click New. The BW Configuration Properties dialog box appears:
Supply the following information: On the Application Server tab, you can select the following Baan services:
| 3-3
Published: This option uses the Active Directory Service (ADS) feature. The connection information will be retrieved from ADS if you select the appropriate environment name in the browse window. Private: You must fill in the following fields: Host Name: Enter the Infor Baan ERP server host name. BSE: Enter the path to the BSE environment on the Infor Baan ERP server, which is equal to the BSE environment variable on the Infor Baan ERP server. Protocol: Depending on the protocol that is installed and configured on the Infor Baan ERP server, you can select one of the following protocols: Rexec, BaanLogin, and SSPI Login. For more information about the protocol to be selected, refer to the relevant Infor Baan ERP server Installation Guide. Note: The Published feature only works in the following instances: You are actually logged on to the Windows domain. You have configured access to the Active Directory Server on your client system through the BECS options dialog. This option dialog can be started by the BECS menu entry Tools | Options. Your ERP backend has been published in the Active Directory. You can only use the SSPI Login if your Infor Baan ERP server is a Windows server and you are logged on to the Windows domain. Port number: To change the default port number, you must have selected BaanLogin as the protocol to be used. If you intend to change the default (7150), you must be sure that the supplied port number is the same as the port number on which the BaanLogin daemon on the server is listening. Enter a valid user name that is known on the Infor Baan ERP server. If you selected SSPI Login as the protocol to be used, you do not have to supply a username because your current Windows domain identity will be used. Password: If this option is enabled (not applicable if you use the SSPI Login), your password will be stored in the Baan configuration .bwc file. On the Bshell Environment tab, you must fill in the following fields: Bshell Name: Enter the application logic to use on the remote Infor Baan ERP host.
3-4
For a description of these environment variables, refer to Chapter 6, Environment Variables. On the NLS tab, you must fill in the Locale field, which enables you to select the character set to be used. The default character set is International [ISO]. The selected Locale must correspond with the Infor Baan ERP server locale. Note: For Infor ERP LN, porting set 7.6b and higher, BW will automatically use the same locale as the bshell. In this case, the settings of the Locale field on the NLS tab are ignored. On the Font tab, fill in the Font type field, which enables you to enter the desired font type. To change the setting, you can click the button on the right side of the font boxes.
Note: The property Standard BW Font can be used to change the font used by BW to show data in edit fields, labels etc. The default setting is the font set
| 3-5
in the Windows control panel for menus. (This property is not available for Infor ERP Baan IVc4 and Infor ERP Baan 5.0). The other two font settings only affect the BW character windows, for example, the display browser. On the Automation tab, you can review the information in the Class Name field, which contains the name of the Baan automation object Baan.Application.server, where server is the hostname of the Infor Baan ERP server you supplied on the Application Server tab.
4
To save the new configuration in a configuration file, click OK.. The BECS Infor BW Environment and Configuration Selector window appears again, and now shows the new configuration:
To start BW, select and double-click the entry for the new configuration. Note 1: To start an Infor Baan ERP logon procedure, double-click the icon that corresponds to the relevant .bwc file in the Explorer. You can also create a shortcut to a .bwc configuration file and store this shortcut in a Program Group Folder, or on the Windows Desktop. Note 2: The Windows operating systems register the Infor Baan ERP Configuration (.bwc) files. The location where the .bwc files are stored (the so-called Profile Storage Path) defaults to the directory lib\user under the installation directory of the Infor Baan ERP client software. On Windows Vista, the default Profile Storage Path is the directory: AppData\Local\Infor\BW\<environment name>\config under the user directory of the current user, typically C:\Users\<user name>. It is also possible to specify (per environment) a non-default Profile Storage Path for the .bwc files. In BECS, first select a .bwc file of the concerned environment and then choose menu item ToolsOptions. The following
3-6
By means of the radio buttons, a pre-defined alternative directory can be used, or a custom directory can be specified. In BECS, it is possible to copy (Ctrl+C, or use context menu item Copy) a .bwc file to the clipboard. Switch the Profile Storage Path as described above and paste (Ctrl+V or use context menu item Paste) the .bwc file from the clipboard into the new directory. In this way, for example, it is possible for an administrator to 'publish' a .bwc file by copying it from his Local directory and pasting it into the Public directory. The same procedure can be used by a normal user to 'import' a .bwc file by copying it from the Public directory and pasting it into his Local directory. For Infor ERP Baan IVc4 environments, the possibility to specify an alternative Profile Storage Path is only enabled on Windows Vista.
| 3-7
Note 3: BECS is shared by the various versions of Infor BW. It can happen, after several installations, upgrade and/or uninstall actions that an incorrect version of BECS (or no BECS at all) exists in: C:\Windows\Baan\bin In that case, remove or rename the incorrect becs.exe file by hand and run the installer of the Infor BW variant which contains the desired BECS version.
During the setup, you can change this installation directory. On Windows Vista, however, the default installation directories are as follows: Default Installation Directory Version Infor ERP Baan IVc4 Infor ERP LN 6.1 Type MSI MSI Installation Directory C:\Program Files\Infor\BW\Baan IV C:\Program Files\Infor\BW\ERPLN
The following subdirectories are created in this directory: bin: This directory contains the bw.exe program to start the Infor Baan ERP application, as well as other binaries. lib: This directory contains the files bw.tlb (type library information for OLE Automation) and tss_bw (language support).
3-8
Infor Worktop
If your Infor software version is Infor Baan ERP 5.2 or later, you must proceed with the Worktop installation. On Windows Vista, version 2.5 or later of Worktop is required. For version Infor ERP Baan IVc4 or Infor ERP Baan 5.0c, the installation of the Worktop is optional. You can find the worktop software on the Infor Enterprise Server (Tools) distribution Medium.
| 3-9
Especially the Porting Number (PA.3496 in this picture), but also other item values (like File Version and Product Version) are important. On Windows Vista, the Properties dialog is different and its Details tab does not show all the desired information
3-10
Therefore, an additional Infor Properties tab has been added (also available on non-Vista versions of Windows), which supplies all the desired information:
| 3-11
3-12
The current version of BW supports options to centralize the following configuration actions on the network domain controller instead of on the local client: Password storage BW configuration editing This chapter describes how you can centralize these configuration actions on the network domain controller. Apart from the method of using registry values as described in the following section, there is a second method: using the settings in the file bwcentral.ini in the directory lib under the installation directory of the Infor BW client. This file is read in two circumstances:
1 2
When Infor BW is started in Central Deployment mode (in other words: when it is not installed locally). When Infor BW is running on Windows Vista. Notice that on Windows Vista, the Central Deployment mode is not supported (in other words: on Windows Vista, Infor BW must be installed locally). The default content of the file bwcentral.ini is the following:
[policies] passwordstorage=yes configedit=yes
These two features can be switched off by changing the policy value from yes to no. If a registry key value and keyword in bwcentral.ini are both used but have conflicting values, the result will be to disable the functionality. So disabling outweighs enabling.
4-2
Password storage
With this BW version, each user can store and retrieve passwords, which are used to authenticate a user to a Infor Baan Application Server. Some secure environments do not want a BW password to be stored on the local client. This structure can allow unauthorized individuals to access the Infor Baan environment without logging on if for example the password file is stolen or accidentally placed on a shared directory. This potential problem is solved in this version of BW by means of an option to disable the local storage of the BW password. The enabling or disabling of the password storage and retrieval feature is related to a registry key setting under HKEY_LOCAL_MACHINE. By default, this section of the registry can only be updated by a person with system administrator rights. To disable the local storage of BW clients, the system administrator can take the following steps:
1 2 3 4 5 6 7 8 9 10
Log on as user with admin rights on the Windows server that is the domain controller of the Windows network. Copy the C:\Program Files\Baan\Lib\bw.adm file (from a BW client) to the directory C:\WINNT\INF on the domain controller. Start the System Policy Editor. On the Options menu, click Policy Template. Click Add, and select C:\WINNT\INF\bw.adm. Click Open. The C:\WINNT\INF\bw.adm is added in the Policy Template dialog box. Select this entry and click OK. In the System Policy Editor dialog box, on the File menu, click Open Policy. Alternatively, if you want to add a policy, click New Policy. Select the systems, or groups of systems, for which you want to disable local password storage, and on the Edit menu, click Properties. Disable local storage in the following figure and click OK:
| 4-3
BW configuration editing
In some environments, BW configuration files are stored on a shared drive and managed centrally by a system administrator. In this type of configuration, each individual user must not be able to create, delete, or modify BW configuration files. Therefore, an optional feature is added that allows only system administrators to perform these activities. To disable local configuration editing, the system administrator can take the following steps:
1 2 3 4 5 6
Log on as user with admin rights on the Windows NT server that is the domain controller of the Windows network. Copy the C:\Program Files\Baan\Lib\bw.adm file from a BW client to the directory C:\WINNT\INF on the domain controller. Start the System Policy Editor. on the Options menu, click Policy Template Click Add, and select C:\WINNT\INF\bw.adm. Click Open. The C:\WINNT\INF\bw.adm is added in the Policy Template dialog box.
4-4
Select this entry and click OK. In the System Policy Editor dialog box, on the File menu, click Open Policy. Alternatively, to add a policy, click New Policy. Select the user, or groups of users, for whom you want to disable local configuration editing. On the Edit menu, click Properties. Disable local configuration editing as shown in the following figure. Click OK:
You can use environment variables with the standard BW program. To set an environment variable, you must use the -- -set command. However, this command depends on which Infor version you have installed.
-Set command
In case of version Infor ERP Baan IVc4, you must use the first time -- -set. In case of version Infor ERP Baan 5.0c or later, you can use the command -set. Ignore the first --. You can use the following environment variables with the standard Infor BW program.
5-2
| Environment variables
-set BAAN_SCM_GRP= <value>: Sets the baan scm group, which is used in an .fd file of development systems. -set BSE_STD_PROGRAM= <program name>: Overrides the standard program, which Tools developers and support personnel use. -set BAAN_WIN_TITLE= <string>: Creates a string that contains the title for the window, depending on the formatting string set by environment variable BAAN_WIN_TITLE. The following formatting variables are supported. You can also remove the format variable and surrounding string if the value is considered empty. To suppress showing empty variables and the surrounding substring place the text between '<' and '>'. For example: <filter: %f> When no filter is active for a session, the title will not contain any filter information. When a filter is active for a session, the title will contain the string: filter: "name of the filter". The following table lists the variables and their description that are available with the BAAN_WIN_TITLE: Variable %h %c %C %f %s %S %I %u %p %o %d Description Hostname Company number Company description Name of current filter Session code Session description Name of current index Name of the user Package combination Window type No debug
Environment variables
| 5-3
If you run the ttadv2500m000 session in company 000 on host Saturn with filter Tools, this will result in the following window title: Saturn: ttadv2500m000: Sessions [000] (filter: Tools)
6-2
| Known Issues
Two scenarios are described in which this situation can occur. Scenario 1 The connection with BW can still be established. For example, the delay can be caused by a slow network connection or an intermediate login dialog which had to be filled in. When BW has established the connection with the backend, click the Retry button of the Server Busy dialog. Scenario 2 The connection with BW cannot be established. This can be caused by several reasons, two of which are discussed below, but the solution is always the same: stop the BW with which BECS tries to establish a connection, and click the Retry button of the Server Busy dialog. If it was a running BW, OLE will start a fresh BW. If establishing a connection with the fresh BW also fails, then stop that BW and click the Retry button of the Server Busy dialog. Finally, the following message dialog will appear:
One reason the connection with BW fails can be that the login at the backend fails. To stop BW in such a case, on the login dialog, click Cancel. Another reason can be that the .bwc file contains a session to be started in its Command field. In such a case, BW will start normally, but OLE is not able to establish a connection. Stopping the normally running BW needs no further explanation. When trying the next time with the same .bwl file, ensure you select a .bwc file without a session to be started in its Command field.
Known Issues
| 6-3