BCI Nodes - Suites
<Suites> - In BBj 11.00 and higher, this node specifies the name, version, and company name of children <Suite> nodes.
Attribute | Description | Possible Values | Default Value |
---|---|---|---|
name | Specifies the name. | Any string | None |
version | Specifies the version of the suites. | Any string | BBj version |
company | Specifies the company of the suites. | Any string | None |
url | Specifies the url of the suites. | Any string | None |
Common Attribute | Description | Possible Values | Default Value | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
bit |
Specifies the Java bit level for which the BCI node will be active. |
In BBj 19.21 and higher, the following values may also be used:
|
0 = All bit levels |
||||||||||
osbit |
Specifies the OS bit level for which the BCI node will be active. |
In BBj 19.21 and higher, the following values may also be used:
|
0 = All bit levels |
||||||||||
osname | In BBj 24.10 and higher, specifies the OS for which the BCI node will be active. Multiple OS's are comma separated. |
|
All | ||||||||||
portid |
Specifies the port ID for which the BCI node will be active. Multiple port IDs are comma separated. As of BBj 24.10, the portid attribute has been removed. Use osname instead. |
See Platform Availability for possible port IDs. |
All port IDs |
Note
The company attribute value will be used to set the OEM company name property in the BBj.properties file. Alternatively, you can set the set the property (com.basis.oem.company) directly in the BBj.properties file, or programmatically as shown in the following sample:
|
Example
|