Installation requirements
The Baan Connector consists of the following objects:
| Object | Language | Location |
|---|---|---|
| BCSL - Business Connector Slave Listener | C | $BSE/ometa/BCSL |
| BCS_BAAN - Business Connector Slave interface program for Baan | C | $BSE/ometa/BCS_BAAN |
| BaanInterface.o | Baan 3GL | $BSE/ometa/BaanInterface |
There is also a configuration file for the Baan Connector:
| Config file | Configuration | Location |
|---|---|---|
| BCSL-config.txt |
|
$BSE/ometa/BCSL |
Important
The Ometa Framework server should be able to communicate with the BaaN server on the TCP port defined in BCSL_PortNr (2002 by default).
Connector Requirements
For the Baan Connector, there are a number of scripts used for starting and stopping BCSL:
| Script | Actions | Location |
|---|---|---|
| start_bcsl_scr |
|
$BSE/ometa/BCSL |
| stop_bcsl_scr |
|
$BSE/ometa/BCSL |
| start_BCSL |
|
$BSE/ometa/BCSL |
| stop_BCSL |
|
$BSE/ometa/BCSL |
| bcsl.mnu |
|
$BSE/ometa/BCSL |
Multiple package combinations
In case of multiple package combinations within one BSE environment, a subdirectory must be created in $BSE/ometa/PackComb for each package combination that will be used in the Ometa Business Connector.
This subdirectory for each package combination consists again of the subdirectories BCSL, BCS_BAAN and BaanInterface.
When setting up these directories, only the script bcsl.mnu and the config file for BCSL must be placed in the BCSL-directory.
So the objects of the Baan Connector and the actual start and stop scripts (start_bcsl_scr and stop_bcsl_scr) remain in the subdirectories of $BSE/ometa, and are used for each package combination.