Baan connection types

BSE

This is the path to the Baan Software Environment. For example:

USER

Enter the Baan user through which OnePoint Diagnostics must logon to Baan.

Please note that this Baan user must be linked to the OS user under which OnePoint Diagnostics was installed.

In many situations the OS user is equal to the Baan user. So if OnePoint Diagnostics was installed under OS user "bsp" (for example), the Baan user to be filled in is likely to be "bsp" as well. If in doubt, further instructions are as follows:

The link between Baan user and OS user is laid via Baan session "Maintain user data" (in most Baan versions this is session ttaad2100m000 - if in doubt, refer to your Baan help files). The OS user is linked to the Baan user in session "Maintain user data" through field "System Login".

To know what value to fill in in the USER field, proceed as follows:

1. Determine the System account that was used to install OnePoint Diagnostics.
2. Logon to Baan and start session "Maintain user data".
3. In that session, from the "Tools" menu, click "Query... (Ctrl+Z)".
4. Search for the "System Login" user under which OnePoint Diagnostics was installed.
5. Take the corresponding "BAAN User" and fill it in as value for the USER field in OnePoint Diagnostics Connection Details.

Note: It is even more accurate to check the BSE/lib/u<user> files, because the settings visible in Baan session "Maintain user data" may not have been converted to Runtime Data Dictionary.

If you have installed OnePoint Diagnostics by means of a user account which does not exist in Baan, you need to re-install OnePoint Diagnostics or else create a new user in Baan. To summarize, the following criteria must be met:

The criterion for Baan user account "AnyUser" is, that it has enough privileges to access all Baan tables. Also the database user linked to Baan user "AnyUser" must have privileges to access all tables, including system tables. See Baan session "Maintain Links between Baan Users and Database Users".

PACKAGE_COMB

Enter a package combination, e.g. OPER_001. The choice of Package Combination depends on the company you want to scan (see next field).

BSE_COMPNR

Some of the Baan questions operate on Baan tables, for which the company must be filled in here.

E.g. if your want to scan your operational company, and the company number is 100, fill in "100".

You can only fill in one company number, i.e. only one company can be scanned at a time. If you want to have more companies scanned: Fill in one value, run a scan, then change the value and rerun a scan etc.

There is no need to fill in company 000 because company 000 is scanned by default.

BSE_LANG

The Baan application supports several user languages. The OnePoint Diagnostics scan collects information (such as table names, parameter values, field labels etc.) in the English language by default (if available on your system).

If you want the scan to collect information in another language besides English, fill in the language code here. You are advised to enter the language you are most comfortable with.

Supported languages with their code are:

LIBRARY_PATH

Normally you leave this field blank. The field exists as a safety measure. In the event that OnePoint Diagnostics cannot run certain Baan components because linked dlls are placed in a specific library folder, the path to that folder can be entered here. Only do so if explicitly instructed by a support engineer.

BAANHOME

Normally you leave this field blank. However, if BCLM is used (namely on Baan Reger platforms), the path to the license server components can be entered in this field.

Default values for the BAANHOME directory (if BCLM is used):

If the BCLM license server is active, and you do not enter a value for BAANHOME, on Windows platforms the event logging will contain many error messages that the license file could not be found.

DS_AS

Normally you leave this field blank. However, if you want to use another bshell component than the default one, you can enter a value in this field, just as you would set environment variable DS_AS.

There are 2 types of settings, DS_AS=<bshell> and DS_AS=<machine>!<bshell> (values between angular brackets must be substituted). If the <machine> is specified, the machine name must be the name of the server where both Baan and OnePoint Diagnostics are installed. The value for <machine> may not point to a remote server.

Note that the value you enter here must exist in the bse/lib/ipc_info configuration file.