Release 2.0.0 is a combined feature and maintenance release.
The following tables list all supported micro versions for:
Note
We do not expect any problems in all micro versions covered in the following tables
of supported platforms, but we cannot strictly guarantee correct end-to-end system functionality in other platform
versions than the Reference Test Platforms, as bugs in the platform code and problems
introduced by combining different unforeseen micro-level versions of the different platform components could in
rare cases introduce incorrect system behavior that is beyond our control. Refer to section Reference
Test Platforms for a list of fine grained version information for our regression test platforms.
The Stardust portals are currently supported on the following user agents:
| User Agents | Supported Versions |
|---|---|
| Internet Explorer (except Web Modeler and Rules Management perspectives) | 9.0 |
| Mozilla Firefox | 26, 27 (note that future browser releases are not tested with Stardust yet and might cause issues) |
| Google Chrome | 32, 33 (note that future browser releases are not tested with Stardust yet and might cause issues) |
The following database servers are currently supported by Stardust:
| Server | Supported Versions |
|---|---|
| Oracle | 10g, 11g R1 (11.1.0.6.0), 11g R2 (11.2.0.1.0) |
| DB2 UDB | 9.5, 9.7 |
| Derby | 10.8.2.2 |
| MySQL | 5.0, 5.1 |
| Sybase ASE | 15.0 |
| SQL Server | 2008, 2012 |
The following application servers are currently supported by Stardust:
| Server | Supported Versions |
|---|---|
| IBM WebSphere | 7, 8 (8.0.0.5 or later) |
| Oracle WebLogic | 10.3.3, 10.3.6, 12.1.2 (12c) |
| JBoss | 5.1, 7.1 (for Spring) |
| Jakarta Tomcat | 7 |
If you don't see your favorite database or application server in this list, please send a request to us. We continuously update the list of supported databases and application servers.
| Vendor | Supported Version |
|---|---|
| Oracle, Sun | Java SE 6 |
| Oracle | JDK 7 |
| IBM | 32 Bit JRE 6.0 (together with WebSphere 7) |
| Oracle | JRockit 6 (together with Oracle 11g application server) |
| Vendor | Supported Version |
|---|---|
| Spring | 3.2.4 |
| Jackrabbit | 2.6.1 |
| Hazelcast | 2.4 |
The following tables provide fine grained version information for our regression test platforms.
The following database servers are currently tested as reference:
| Server | Supported Versions |
|---|---|
| Oracle | 10.2.0, 11.2 R2 |
| DB2 UDB | 9.7.5 |
| Derby | 10.8.2.2 |
| MySQL | 5.1.59 |
| Sybase ASE | 15.7 |
| SQL Server | 2012 |
The following application servers are currently tested as reference:
| Server | Supported Versions |
|---|---|
| IBM WebSphere | 7.0.0.21, 8.0.0.3 |
| Oracle WebLogic | 10.3.3, 10.3.6, 12.1.1 |
| JBoss | 5.1, 7.1.1 (for Spring) |
| Jakarta Tomcat | 7.0.41, 7.0.50 |
The following new features and bug fixes have been introduced with this release:
Since this release, Stardust supports multiple instance activities in the Eclipse and Business Process Modeler and for execution. Please refer to chapter Using Multiple Instance Activities in our Concepts handbook for details.
The Stardust Portal now provides a Business Process Reporting perspective, where you can create ad-hoc reports with an easy-to-use report wizard.
Refer to section Defining and Running Reports in the Stardust Portal documentation for details.
With this release, Stardust provides a mobile user interface to use the Stardust Portal from a mobile device. It contains support for a subset of Portal functionality and is provided for the following devices:
With this release, Stardust supports the inclusive OR gateway semantics.
Refer to chapter Control Flow for details on the concept of using inclusive gateways in Stardust.
Stardust provides support for Federated Document Repositories. This feature allows to instantiate an arbitrary number of document repositories. The current DocumentService API was enhanced to reflect locations in the Repository Instance.
A newly introduced Rules Management perspective provides an easy way for business analysts to define business rules as rule sets, containing decision tables or technical rules.
Refer to chapter Managing Business Rules in the End User Handbook for details.
Security Context Propagation for UI Mashup HTTP Calls and REST Calls is supported since this release.
Since this release, Enumeration types are supported as data types for primitive types. Enumerators can be set as initial values for these Primitive Data.
The following functionality of the Business Process Modeler has been introduced as or is still customer technology preview only. Note that these previews may not be functionally complete and are not intended for production use.
The Stardust Portal provides a configuration switch to show or hide features that are provided as technology preview.
The following Business Process Modeler features have changed from technology preview into production ready functionality:
The following new features and bug fixes have been introduced with this release:
| Bug-ID | Description |
|---|---|
| Bug 435268 | Rules Management Support in the Stardust Portal |
| Bug 435266 | Provide support for Federated Document Repositories. |
| Bug 435265 | Provide support for Inclusive OR gateway semantics. |
| Bug 435264 | Provide a Mobile Client for Stardust. |
| Bug 435263 | Implement Reporting Perspective for defining and running Reports in the Stardust Portal. |
| Bug 435260 | Provide Support for Multiple Instance Activities. |
| Bug 434405 | Disable Reporting plugins |
| Bug 426420 | Provide Simple Lock Protection for Process Models in the Browser Modeler. |
| Bug 426244 | XSD/MTA improvements |
| Bug 426242 | Alternative behavior of NotInList predicate on InList predicate result. |
| Bug 426233 | Provide support for Enumerations as Primitive Types. |
| Bug 426232 | Support Security Context Propagation for UI Mashup HTTP Calls and REST Calls |
| Bug 426231 | Display Data Structures Nested in Grids (multi-cardinality structures) in Dialog |
| Bug 420784 | Add SMTP AUTH support to Email application type and Email event Action. |
| Bug 416487 | Business Control Center loads preferences of all users upon login |
For general known issues and restrictions, please refer to our Troubleshooting section in the online documentation.
Running process instance queries or reporting requests against an audit
trail containing process instances having descriptors on uninitialized
structured data values may be very slow for Derby databases. In that case we
recommend to use prepared statements to improve the performance. To use
prepared statements, set the property
AuditTrail.UsePreparedStatements in your carnot.properties
file to true. For details on using this property refer to section
Using Prepared Statements of chapter
Database Access Tuning of the
Operation Guide.
Note that single instances belonging to a multiple instance activity, regardless of whether they are sequential or parallel will be executed in separate transactions. Alternative transaction handling patterns for sequential multiple instances may be added in a subsequent release.
The output list for multiple instance activities may not be shown correctly you don not move the mouse pointer out of the entered field.
Currently, imported structured data types cannot be accessed in the Eclipse modeler. Note that this also affects multiple instance activities when trying to select list values from an imported structured data type.
The limit of the list size which can be used with the new feature without running into transactional errors or performance issues depends on the layout of the runtime environment. For the standard setup on a small machine (4 cores) list sizes up to 10000 entries have been tested before running into transactional problems.
Some functionality and elements supported in the Eclipse modeler are not supported in the Business Process Modeler yet. Please refer to chapter Compatibility and Analogy of Models of the Business Process Modeling Handbook for details.
Note that you need a lifecycle management environment to be able to run and test a Rule Task implementing a Rule Set. Please contact our Sales Support Team for details.
For the time being, you need to append _field to each variable in the code
editor of a technical rule in the Rules Management perspective. Refer
to chapter
Defining Technical Rules for details.
In case you use a formal parameter of primitive data type Java bound Enumeration
in a Process Interface, the WSDL generator fails to create a WSDL document.
UI Mashup applications have the following restrictions:
Failing of a server restart when working with referenced models might happen in the following case:
The following breaking changes have been introduced with version 8.0:
The support for the following platforms or platform versions has been dropped with this release:
The following platforms versions are supported since this release:
This section covers upgrading necessary for upgrading from releases earlier than 1.1. For other upgrading issues introduced with earlier releases, please refer to chapter Upgrading to Later Versions. You will find all upgrading steps necessary for your specific version.
Compatibility with audit trails created with an earlier Stardust version is provided via a runtime upgrade job that performs all necessary database conversions. Refer to section Runtime Upgrades of chapter Upgrading to Later Versions for details on how to upgrade an audit trail to a later version.
A runtime upgrade against audit trails created with earlier versions adds the new predefined process instance link type SPAWN to the audit trail. The SPAWN link type describes the case for just creating a new root process instance from an existing one with optionally copying data. This runtime upgrade job is optional if you are not using the spawn functionality.
Note that this upgrade job is a trivial one and can be applied without any risk!