Changes to the BPEL Service Engine runtime properties are made from within NetBeans.
This section contains information on the following topics for the BPEL Service Engine runtime properties:
Configuration of BPEL Service Engine runtime properties requires first starting the Sun Java System Application Server in the NetBeans IDE Services window.
To start the Sun Java System Application Server:
Select the Services window.
Right-click the Servers > Sun Java System Application Server 9 node and select Start.
After you have started the application server, you can access the service engine properties.
To view BPEL Service Engine properties:
In the Services window, expand the following nodes: Sun Java System Application Server 9 > JBI > Service Engines.
Right-click sun-bpel-engine and select Properties.
The sun-bpel-engine Properties window appears.
The following tables include descriptions for the BPEL Service Engine runtime properties
Table 1–11 General Properties
Property Name |
Description |
Default Value |
Description |
Description of the JBI Component. |
This is a bpel service engine. |
Name |
Name of the JBI Component. Specifies a unique name in the JBI environment. If you are installing more than one BPEL Service Engine in a JBI environment, make sure that each is unique. This can be changed in the descriptor (jbi.xml) for the component. When the service unit deploys the component, it is matched with target component name defined in its descriptor – jbi.xml. |
sun-bpel-engine |
State |
State of the JBI Component. Started, Stopped, or Shutdown. |
Started |
Type |
Type of the JBI Component (service-engine or binding-component) |
service-engine |
Table 1–12 Identification Properties
Property Name |
Description |
Default Value |
Build Number |
Date and time stamp for the current build. |
<build_number> |
Spec Version |
BPEL specification fully supported by this build. |
<spec_version> |
Table 1–13 Configuration Properties
Property Name |
Description |
Default Value |
DatabaseJNDIName |
Attribute exposed for management. Enter the database JNDI name. For more information, see PersistenceEnabled. |
jdbc/bpelseDB |
DebugEnabled |
Attribute exposed for management. When set to true, you can attach the debugger and debug the business process flow. |
false |
DebugPort |
Attribute exposed for management. Specifies the port number at which the debug server listener listens for the debugger UI to connect. The default value is sufficient for most cases. Make sure that this port is not used by other applications. If you are running more than one instance of BPEL Service Engine on this computer, make sure that you assign non conflicting unique ports. |
3343 |
EngineExpiryInterval |
Attribute exposed for management. An integer that specifies the frequency (in seconds) that the BPEL Service Engine registers itself as available. Use this attribute primarily for configuring BPEL Service Engine failover. Set this attribute so that it registers itself as available frequently enough to meet the demands of your system. Optimizing this attribute might require some testing. This attribute also applies to the interval for the recovery of dangling instances. The default setting is 15. |
15 |
MaxThreadCount |
Attribute exposed for management. An integer that specifies the number of threads executing BPEL definitions. This is the number of computers needed for maximum throughput. Note that you must set associated binding components with same number of threads. This combination is the optimal configuration for most cases. |
10 |
PersistenceEnabled |
Attribute exposed for management. When set to true, the BPEL Service Engine persists critical data to a database. Upon restart after a system failure, the BPEL Service Engine resumes processing from the point at which service engine processing was interrupted. |
false |
Table 1–14 Class Loggers
Class Name |
Description |
Default Logging Level |
sun-bpel-engine |
|
INFO |
BPELSEDeployer |
|
INFO |
BPELSEHelper |
|
INFO |
BPELSEInOutThread |
|
INFO |
BPELSELifeCycle |
|
INFO |
BPELSERuntimeConfiguration |
|
INFO |
DeploymentBindings |
|
INFO |
EngineChannel |
|
INFO |
BPELInterpreter |
|
INFO |
EngineImpl |
|
INFO |