Stardust Release 2.0.1

Release 2.0.1 is a combined feature and maintenance release.

Supported Platforms

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.

Supported Portal 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, 10
Mozilla Firefox 29, 30 (note that future browser releases are not tested with Stardust yet and might cause issues)
Google Chrome 34, 35 (note that future browser releases are not tested with Stardust yet and might cause issues)

Supported Database Servers

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

Supported Application Servers

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), EAP 6.2
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.

Supported Java Runtime

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)

Other System Dependencies

Vendor Supported Version
Spring 3.2.4
Jackrabbit 2.6.1
Hazelcast 2.4

Reference Test Platforms

The following tables provide fine grained version information for our regression test platforms.

Reference Test Database Servers

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

Reference Test Application Servers

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), EAP 6.2
Jakarta Tomcat 7.0.41, 7.0.50, 7.0.54

Bug Fixes

The following bug fixes have been introduced with this release:

Bug-ID Description
Bug 444077 Prepare build script for 2.0.1 builds
Bug 444074 Move to new HIPP instance
Bug 444066 Summary of introduced bugfixes for stardust 2.0.1 related to IPP
Bug 443688 Web modeler: Values entered while creating structured data, data or application cannot be saved.
Bug 443098 Cheat Sheets has display error and other minor bugs
Bug 442597 IncompatibleAuditTrailException thrown during tests
Bug 441226 Prepare build scripts for 2.0.1 RC2
Bug 441224 Provide release notes for 2.0.1
Bug 441223 Upgrade Stardust to 2.0.1 - Adjust IPP-Stardust version mapping
Bug 441222 Upgrade Stardust to 2.0.1 - Adjust facet version
Bug 438806 Build: eclipse-collector project is using false org.eclipse.osgi Bundle version
Bug 437921 Start Event Message Icon not BMPN 2.0 conformant
Bug 426349 Building documentation should explicitly include "how to create a WAR"

Stardust API Changes

Deprecated API

The following API methods are deprecated:

API Changes

The following API changes have been performed with this release:

Known Issues and Restrictions with this Release

For general known issues and restrictions, please refer to the Troubleshooting section in the online documentation.

Known Issues

WebLogic 11g - client side error occurs when deploying a process model from Console command

A client side error occurs in case you deploy a process model from the Console command in an EJB with DB2 environment.

Uploading document data appends null on filename in WebLogic environment

When uploading a document data to a manual activity in a WebLogic environment, null is appended as prefix to the according file name. This happens due to a WebLogic limitation, which can be resolved by adding the following lines to the weblogic.xml file residing in your WEB-INF folder:

<container-descriptor>
   <show-archived-real-path-enabled>true</show-archived-real-path-enabled>
</container-descriptor>

Derby - Performance issues when running queries for process instances having uninitialized (structured) data values

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.

Known Restrictions

Business Processs Reporting perspective is not supported on the Internet Explorer browser

Note that following browsers are supported for Business Process Reporting perspective:

Reports can't be opened in Internet Explorer.

Note that reports created in Business Process Reporting perspective and saved in Document Repository, can't be opened in Internet Explorer.

Limitation for User Names

Colon (":") characters are not supported in user names as this leads to misinterpretations in a WebService environment.

Known Restriction in the Business Process Modeler

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.

Testing a Rule Set implementation

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.

Technical Rules editor code restriction

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.

Importing WSDL in SOAP UI fails with formal parameter of type Java Enumeration

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 application restrictions

UI Mashup applications have the following restrictions:

Upgrading from a Previous Release

A runtime upgrade is not required for this release. 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.

Previous Releases