Engine
Engine information includes Configuration, Storage, and Version Detail.
Configuration
The Configuration page is divided into tabs for Engine Properties and URN Mappings
Engine Properties
You can make engine property changes without stopping and restarting the engine. When you make a change and select Update the changes are in effect immediately as well as persisted to the engine configuration file.
View and update engine configuration settings as shown in the following table. Note that some of these properties are the same as the ActiveBPEL Designer Simulation preferences.
Property Name |
Description |
---|---|
Auto create target path for Copy/To (BPEL 1.1 only) |
Applies only to processes that are validated against the BPEL4WS 1.1 specification. For WS-BPEL 2.0 processes, this property can be added as an extension on a per process basis. Refer to Extensions help topic in ActiveBPEL Designer Online Help. Determines if the ActiveBPEL engine is allowed to create a location path for a non-existent node in a complex variable in a process instance document. When an assignment refers to a non-existent node (or to more than one node), the standard BPEL fault, bpws:selectionFailure, must be thrown, according to the BPEL specification. Enabling this option allows selections to be created on-the-fly. This means an assign copy TO operation can refer to a non-existent node and assign a value to it. This option is disabled by default. |
Disable bpws:selectionFailure fault (BPEL 1.1 only) |
Applies only to processes that are validated against the BPEL4WS 1.1 specification. For WS-BPEL 2.0 processes, this property can be added as an extension on a per process basis. Refer to Extensions help topic in ActiveBPEL Designer Online Help. Enabling this option allows a null value to be returned from a function or assignment that contains an XPath query string. You can enable this to override XPath behavior, for cases that handle data samples with optional elements. By default, this option is not enabled, and if the query string returns an empty selection from an assign copy FROM, the process throws a bpws:selectionFailure fault, which is the standard response described in the BPEL4WS specification. |
Logging Level |
By default the ActiveBPEL engine does not generate an execution log for running processes. Logging is turned off to enhance engine performance. You can enable this setting, and then view or download an execution log for a running or completed process. An execution log provides start/end times for activity execution and helps you troubleshoot faulted processes. The logging levels are:
|
Replace existing resources on deployment |
Overwrites the current WSDL or schema definition, or other resource. By default, resources are not replaced. However, if you enable this setting, ActiveBPEL allows you to replace a WSDL definition or schema file currently in cache without restarting the server. You can deploy a new version of a BPR file containing updated resources. BPEL developers who are testing and modifying processes may find this option useful. Note that you can add this setting to an individual BPR file in the ActiveBPEL Designer Export Wizard. The Deployment Log shows whether or not the resources are being replaced. |
Validate input/output messages against schema |
Validates the data loaded into process variables against the WSDL schema. Enable this option to validate data before execution starts. Disable this option for faster execution. This option is enabled by default. |
Resource Cache |
The number of WSDL and other resource files in stored cache. The default is 100. Modifying the cache size may improve engine performance. A value of -1 means unlimited caching, but is not recommended. |
Unmatched Correlated Receive Timeout |
Set the amount of time to wait (in seconds) for a correlated message to be matched to a receive, in the case that the message arrives before the receive becomes active. If this value is exceeded, a message is discarded so that the process can complete normally. The default is 300. Specifying 0 indicates that unmatched correlated messages are immediately discarded. |
Web Service Invoke/Reply Timeout |
For performance reasons, a reply activity matching a receive, as well as synchronous invokes, are timed out if they do not execute within 10 minutes. If you are receiving timeout errors, you can specify a greater amount of time to wait before a process is timed out due to a reply or synchronous invoke activity not executing within 10 minutes. The default is 600 seconds. |
Work Manager Thread Pool Min |
Set the minimum number of execution threads the engine allocates for its Work Manager. The default is 10. |
Work Manager Thread Pool Max |
Set the maximum number of execution threads the engine can spawn simultaneously. The default is 50. A value of -1 means that there is no maximum number of threads. |
Work Manager Threads Per Alarms Max |
Set the maximum number of threads the engine will use from the work manager to dispatch work scheduled by an alarm in a process. If there are 100's of alarms firing concurrently, it is possible that all of the threads in the work manager could be used just to dispatch the alarms. If you experience performance issues or deadlocks due to all of the threads being used by the alarm manager, you can increase this value. The default is 5. |
Work Manager Threads Per Process Max |
Set the maximum number of execution threads the engine can spawn simultaneously for an individual process. The default is 10. |
Retention Days for Closed Tasks |
Set the number of days to keep closed tasks in users’ Inboxes for a BPEL for People task. This setting does not affect the BPEL process storage settings. |
URN Mappings
URN mappings provide a flexible and dynamic way to define target endpoint references. Use URN mappings to specify the physical address of a partner link endpoint reference in the Administration Console instead of specifying an address in a process deployment descriptor (.pdd) file or WSDL file. By mapping an URN to an URL, you do not have to rely on invoking a statically defined endpoint address. URN mappings give you flexibility, for example, to deploy the same BPR files for testing and production environments.
Instead of using the default invocation, you can specify a logical or physical address for a static endpoint reference in the .pdd. If you specify a logical address, or URN, you can then map the URN to the physical address in the URN Mappings page of the Administration Console. If you specify an URL, you can replace the URL by mapping it to a different URL.
The following example illustrates one type of URN to URL mapping:
urn:localhost = http://localhost:8080/active-bpel/services/${urn.3}
This mapping might be used when a process is deployed with the following partner link address information:
<partnerLink name="assessor">
<partnerRole endpointReference="static"
invokeHandler="default:Address">
<wsa:EndpointReference xmlns:assessor="http://
tempuri.org/services/loanassessor">
<wsa:Address>urn:localhost:AssessRisk</wsa:Address>
<wsa:ServiceName PortName=
"SOAPPort">assessor:LoanAssessor</wsa:ServiceName>
</partnerRole>
</partnerLink>
The ActiveBPEL invocation framework resolves the URN as follows:
urn:localhost:AssessRisk = http://localhost:8080/active-bpel/services/AssessRisk
Here are some ways you can map URNs to URLs. Note that each segment of the URN is separated by a colon. This means you can use a variable, such as ${urn.4} shown in the third example below, to indicate a replacable token in the fourth segment.
URN |
URL |
---|---|
urnSegment1:urnSegment2 |
http://localhost:8080/active-bpel/services/MyService |
http://ServerA:8080/active-bpel/services/MyService |
http://ServerB:8081/active-bpel/services/MyService |
urn:localhost:service |
http://localhost:${AE-NODE1-PORT}/activebpel/services/${urn.4} |
The last example in the table above shows how you can use variable substitution in an URL.
The URL values can optionally contain variables. The variables
can be environment variables accessible through java.lang.System.getProperties()
or a segment from the URN itself. The Apache Ant style variable
declaration of ${property}
is used to identify
a property within the URL. Segments from the input URN value can
be referenced by using a special property naming convention of ${urn.offset}
where offset is
a one-based offset identifying the segment from the input URN value
to use for substitution.
The URL in the mapping above contains two variables. The ${AE-NODE1-PORT}
variable
pulls the port number from an environment variable. This variable would
need to be set as a -D parameter on the Java runtime environment
(e.g., java -D ${AE-NODE1-PORT}=8080 ...
)
or populated externally to the ActiveBPEL server.
The ${urn.4}
variable in the above
mapping references the fourth segment from the input URN value.
Notice that the URN contains only three segments. The URN in the
.pdd file should contain at least one other segment. A sample URN might
be:
urn:localhost:service:StoreService
.
The value of the fourth segment of this URN is StoreService
.
The resulting URL is:
http://localhost:8080/activebpel/services/StoreService/
.
To update an URN mapping, select the URN. The URN and URL values appear in the text boxes where you can edit them and select Update. Editing the URN results in a new URN mapping, it does not update the existing one. Only the URL can be updated.
To delete a mapping, select the check box next to the mapping and select Delete.
Storage
By default the ActiveBPEL engine is not configured for persistent storage. If you set up database storage, you can view storage configuration settings as well as delete old processes that are stored. The engine supports both relational databases and XML databases.
See Persistence Storage Setup.
For relational databases, the following storage configuration settings are displayed.
JNDI |
Java Naming and Directory Interface (JNDI) context that specifies where to look for the database. For example, jdbc/ActiveBPEL |
Database Type |
The type such as |
User Name |
Username and password, if they are required for database access |
For XML databases, the following configuration settings are displayed.
Database Type |
The type such as |
Tamino URL |
The path to the tamino database
where |
Database Name |
Name provided in the ActiveBPEL persistence setup file |
Collection |
For tamino databases, this is the name that matches the collection name specified in the database schema file (.tsd file). If the collection name was modified in the ActiveBPEL persistence setup file, it must also be modified in the schema file that ActiveBPEL provides for database set up. |
Connection Pool Size |
Number of simultaneous connections allowed to the database. The default size is 30. |
Domain |
Network domain for host computer |
Username |
Username if required for ActiveBPEL’s access to the database |
Password |
Password associated with the Username |
You can delete completed processes stored in the database. Select a Completed By date and select Delete.
Version Detail
The Version Detail page shows the build number and date of the ActiveBPEL engine libraries. This information may be useful for troubleshooting purposes.
Back to ActiveBPEL® Engine Administration Console Help
Copyright (c) 2004-2008 Active Endpoints, Inc.