BusComponent Configuration
This page describes the BusComponent Configuration settings. The
properties are divided in these categories:
General Properties
- Description
- This is a field which you can use to describe the BusComponent. The information is only used to display here,
in the Central Configuration Console.
- Connection Points
- You use this property to create, edit, and delete connection points assigned to the BusComponent.
The connection point is used to configure the transport for this BusComponent.
Each BusComponent must at least have one connection point.
- Owner
- This field is used to identify the owner or user of the
BusComponent. This information is not used by the Adapter.
- Administrator
- This field is used to identify the administrator of a
BusComponent. The Adapter does not use this information.
- Categories
- This field is used to set one or more BusComponent Categories.
Categories are selected from the full list of buscomponent categories.
For buscomponents that represent SSA ERP or SSA BaanIV servers, usually a category named BaanERP is defined.
The Adapter for BaanERP/BaanIV dialog will initially display buscomponents that have category BaanERP,
but it is possible to use a different category.
Default User Session Properties
- Default UserSession
- Enabling this field (and filling a correct username/password combination)
gives you the possibility to use features like security, activation and pooling without
having to code the UserSession logic. Another advantage is that the
client application does not have to store/ask for username and password.
Some things to keep in mind:
- The Adapter creates only one UserSession Object for each BusComponent that
has the Default UserSession enabled. So if you use one BusComponent to
initialize more managers pooling will occur.
- If UserSession or UserInfo is used from within a program, the Default UserSession will be ignored.
- Activation (pooling) will only occur if you have Activation enabled and configured in your BusComponent.
- Programming with UserSession can still be useful if you want to have more detailed control of activation and pooling.
- Username
- The user name for the default user session.
- Password
- The password for the default user session.
Activation Properties
A component can be started manually or automatically. Select an
Activation Service to start the component automatically. When doing so you must specify
the type of the activation service and its reference.
- Activation Type
- This specifies the type of the activation service and is a mandatory field.
Currently, the following types can be selected:
-
ASM
(Application Services Manager)
The activation mechanism delivered as a
seperate component together with SSA ERP. Can also be used through
APS.
-
ExecBaan
(Local Baan Activation)
The activation mechanism to start SSA Baan ERP
with an Adapter Server locally (on the same machine as the Client Adapter
(or APS))
The APS
Service can be used to turn this local activation into a remote one.
-
ExecCmd
(Local Process Activation)
A flexible activation service which allows to
start any command that starts any backend locally (on the same
machine as the Client Adapter (or APS))
The
APS Service can be used to turn this local
activation into a remote one.
-
InProc
(In-Process Activation)
The activation mechanism to start Adapter Servers
in the same process as the Adapter Clients (or APS).
-
ExecLX
(Remote SSA ERP LX Activation)
The activation mechanism to start SSA ERP LX
with an Adapter Server. Can also be used through
APS.
- Activation Service Reference
- The service reference identifies how a backend must be started for the specified activation type.
It contains all the required parameters and options to start the backend.
The Service Reference can be edited using the edit button.
This will start a dialog box which helps to fill in the parameters.
The Service Reference Edit windows:
- Pooling Policy
- The pooling policy defines how the activation service deals with connection pooling.
All Activation policies must use one of the following pooling policies:
- shared: With this policy a backend will be started when a Manager is initialized
for the first time. Next Managers that use that same backend and are in the
same UserSession, will use the same backend. When all managers are closed the backend will be stopped.

- Limitedshared: This policy is equal to shared, but has a limitation on the number of
References/Managers that use one backend. A new backend is started when the limit is
exceeded. If the number of Managers on a connection reaches 0, the connection
is closed.
See also: Activation Maximum References

- Limitedconnection : This policy is an extension of the
limitedshared policy. There are two additions. One is a limit on the
number of connections, and the other is a keep alive timer that keeps a
connection alive for some time after the number of references becomes 0.
If the max connections and max managers per connection is reached, the policy
starts overloading the number of references/managers per connection.
If the keep alive timer for releasing a connection is running (number of references/managers
on the connection drops to 0) and a request for a new reference/manager is done,
the timer is stopped and the connection is reused.
See also: Activation Maximum References,
Activation Maximum Connections,
Activation Keep Alive Time

- Activation Maximum References
- The maximum number of references (managers) per connection.
- Activation Maximum Connections
- The maximum number of connections to create.
- Activation Keep Alive Time
- Keep alive time in seconds before releasing the connection after the last connection is closed. This is when the number of references becomes 0.
- note
- Setting this value to 0 (zero) will keep the connection open forever
- Activation Pooling Service
- To enable APS select the BusComponent from the list
which is used by the APS Service.
Enable APS if you want to use one of the following features.
- Make an Inproc, ExecBaan or ExecCmd activation remote.
- Enable pooling across multiple client processes.
- Activation Server Timeout
- The server timeout in minutes. Backends have a timeout that causes the server
to stop when the timer expires. The server is stopped when no request has been handled within the timeout
value. Usually, a backend is stopped when all Managers that use that backend are closed.
The timeout mechanism is only used in abnormal situations to stop a backend.
For example: when a client program crashed, and did not stop in the usual
way. Therefore, set the timeout value to a long time.
The default value is 720 minutes (12 hours).
The value 0 set the timeout to infinite, this will disable the timeout.
SSAŽ ERP(ln) Properties
This property is only applicable if the buscomponent is defined to be running on a SSA ERP(ln)/BaanIV server.
- Company Number
- If the field is left empty,
the server will run in the company that is default for the user who started the buscomponent.
Alternatively, a value can be entered in the range 0 - 999.
In that case, the server will run in the specified company.
SSAŽ ERPlx Properties
These properties are only applicable if the buscomponent is defined to be running on a SSA ERPlx server.
- Environment Control Library
- Describes the iSeries based Library List (i.e. path on the iSeries) for SSAŽ ERPlx.
- WebTop URI
- Describes the URI where the WebTop for SSAŽ ERPlx can be reached.
- Screen Scraping Engine's Classpath
- Path to all classes, properties and process instructions needed for using the screen scraping engine at runtime.
WMS Properties
This property is only applicable for a WMS integration buscomponent.
- WMS System Id
- WMS System Id, which is basically a logical alias for the customer's warehouse instance.
Event Management Properties
- Event Publishing Polling Frequency
- This identifies the frequency of the event publishing polling activity in milliseconds.
- Error Handler BusComponent
- BusComponent to which the error events are sent in case of an error during processing of an event.
If not set errors are only logged.
- Persistent Queue Path
- Local path for creating a persistent event queue. If not set the persistent queue is disabled.
JDBC Properties
These properties are only applicable for a buscomponent that uses JDBC to access a database.
- JDBC Driver Name
- This identifies the used JDBC Driver. For example: net.sourceforge.jtds.jdbc.Driver .
- JDBC Database URL
- Database url. For example: jdbc:jtds:sqlserver://localhost:1433;TDS=8.0 .
- JDBC Database User
- The database user on whose behalf the connection is being made.
- JDBC User's Password
- The database user's password.