Using JBI Components: Runtime Property Descriptions

Configuring JBI Components

Configuring WSDL Extensibility Elements

HTTP WSDL Extensibility Elements

HTTP Connectivity

SOAP WSDL Extensibility Elements

SOAP Connectivity

Configuring JBI Runtime Properties

Configuring the BPEL Service Engine Runtime Properties

Starting the Application Server

Viewing Service Engine Properties

Runtime Property Descriptions

HTTP Binding Component Runtime Properties

Configuring BPEL Service Engine Clustering and Failover

Clustering/Failover Considerations

Configuring the HTTP Binding Component for Clustering

Administering JBI Components for Java CAPS

Using the Java EE Service Engine in a Project

Using the Java EE Service Engine to Create a Composite Application

Using the BPEL Designer and Service Engine

Using the HTTP Binding Component

Processing an Order in a Purchase Order System

Designing Custom Encoders

Using the XSLT Editor

XSLT Designer: Simple Transformation Tutorial

Using the File Binding Component

Using the File Binding Component in a Project

Using the JMS Binding Component

Understanding the FTP Binding Component

Using the FTP Binding Component in a Project

Understanding the LDAP Binding Component

Using the LDAP Binding Component in a Project

Using the JMS JCA Wizard

Using the JAXB Wizard and Code-Seeder Pallete

Understanding the Database Binding Component

Using the Database Binding Component

Using the WSDL Editor

Migrating From eTL to Sun Data Integrator

Designing Intelligent Event Processor (IEP) Projects

Designing Data Integrator Projects

Using the Sun Data Mashup Engine

Runtime Property Descriptions

The following tables include descriptions for the BPEL Service Engine runtime properties

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

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>

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

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