Release 2.1.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, 10, 11 |
| 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) |
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 | 7.1, 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.
| 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 | 7.1.1, EAP 6.2 |
| Jakarta Tomcat | 7.0.41, 7.0.50, 7.0.54 |
The following new features and bug fixes have been introduced with this release:
Multiple enhancements have been introduced in the Stardust Portal with this release, most importantly:
The Process Manager view in the Business Control Center perspective allows a controlling of all running process instances on a very high level. With this release the view is enhanced to also display interrupted process instances in an additional column showing a count of the interrupted processes for each row in the table. This provides the option to access interrupted process instances to restart the according activity instances.
For details refer to chapter Viewing Activity and Process Instances categorized by Priorities in the End User Handbook.
The Authorization Manager view of the Administration Perspective is extended with a new permission for managing deputies. Participants with this authorization are able to manage deputies for all users.
For details refer to chapter Managing Authorization in the End User Handbook.
The Business Process Modeling perspective is enhanced with the option to set the model ID when you create a new model. A model dialog opens where you specify a model name and a unique model ID.
For details refer to chapter Model Operations in the Business Process Modeling Handbook.
With this release, a predefined access point that provides the total count of documents attached to a process instance is provided. Once set you can view this count in all process tables in the according descriptor columns.
For details refer to section Providing the total count of attached documents as descriptor of chapter Working with Process Definitions in the Business Process Modeling Handbook.
The Business Process Modeler perspective is enhanced to provide filtering for models and model elements in the outline tree.
For details refer to section Filtering Elements of chapter Panels in the Business Process Modeling Handbook.
The Resource Performance view is extended with an additional column to
provide the average wait time of activities for each process definition.
The average wait time displays the sum of all time intervals an activity
instance has spent in state Suspended during its lifecycle from
creation to completion.
For details refer to chapter Viewing the Performance of Participants in the End User Handbook.
The Cost and Controlling and Resource Performance views in the Business Control Center perspective are enhanced with the option to add additional columns with custom time frames. This allows you for example to compare process performance from cost or time perspective in specific time frames and to analyze recent changes for a given process.
For details refer to chapters Viewing Cost and Controlling and Viewing the Performance of Participants in the End User Handbook.
The Process Search view of the Business Control Center is enhanced with the option to view the timestamp of the oldest audit trail entry.
The Selected Activities tables in the Postponed Activities and Pending Activities views in the Business Control Center perspective are enhanced to provide an additional column to display resubission time for each activity. The Pending Activities - Overview table additionally provides sub-columns for each participant to display the number of hibernated activities.
E-mail correspondence is enhanced to be be created via templates.
With this release Stardust provides the option to enable re-authentication for the Web Service Session Factory. For details refer to chapter Web Service API in the Programming Guide.
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 main features and bug fixes have been introduced with this release:
| Bug-ID | Description |
|---|---|
| Bug 454527 | Re-authentication option for Web Service Session Factory |
| Bug 454526 | E-Mail correspondence via templates |
| Bug 454525 | Resubmission Information available in Postponed Activities and Pending Activities Views |
| Bug 454524 | Option to view the timestamp of the oldest audit trail entry in the Process Search view |
| Bug 454523 | Option to add columns with custom time frames for Cost Controlling and Resource Performance views |
| Bug 454522 | Additional column to provide average wait time in the Resource Performance view |
| Bug 454521 | Filtering capabilities for the Outline Tree in the Business Modeler |
| Bug 454520 | Support for a predefined access point providing the total count of attached documents |
| Bug 454519 | Support for editing the model ID during model creation |
| Bug 454518 | Declarative Security Authorization for Managing Deputies |
| Bug 454517 | Additional column for interrupted process instances in the Process Manager View |
To view all bug fixes, refer to our Bugzilla list for version 2.1.0 accordingly.
The following API methods are deprecated:
| Method | Return Value | Parameter |
|---|---|---|
| getModel | DeployedModel | - |
AdministrationService
| Method | Return Value | Parameter |
|---|---|---|
| deployModel | DeploymentInfo | String model, int predecessorOID |
| overwriteModel | DeploymentInfo | String model, int modelOid |
| deployModel | DeploymentInfo | String model, String configuration, int predecessorOID, Date validFrom, Date validTo, String comment, boolean disabled, boolean ignoreWarning |
| overwriteModel | DeploymentInfo | String configuration, int modelOID, Date validFrom, Date validTo, String comment, boolean disabled, boolean ignoreWarnings |
QueryService
| Method | Return Value | Parameter |
|---|---|---|
| getAllModelDescriptions | List<DeployedModelDescription> | - |
| getAllAliveModelDescriptions | List<DeployedModelDescription> | - |
| getActiveModelDescription | DeployedModelDescription | - |
| getActiveModel | DeployedModel | - |
| findFirstDocument | Document | DocumentQuery query |
| getAllDocuments | Documents | DocumentQuery query |
UserService
| Method | Return Value | Parameter |
|---|---|---|
| isInternalAuthentified | boolean | - |
| invalidate | User | String account |
DocumentManagementService
| Method | Return Value | Parameter |
|---|---|---|
| versionDocument | Document | String documentId, String versionLabel |
| updateDocument | Document | Document document, boolean createNewRevision, String versionLabel, boolean keepLocked |
| updateDocument | Document | Document document, byte[] content, String encoding, boolean createNewRevision, String versionLabel, boolean keepLocked |
| findDocumentsByName | List<Document> | String namePattern |
| findDocuments | List<Document> | String xpathQuery |
Activity
| Method | Return Value | Parameter |
|---|---|---|
| getDefaultPerformerID | String | - |
| getDefaultPerformerName | String | - |
AttributeOrder
| Method | Return Value | Parameter |
|---|---|---|
| getAttribute | String | - |
DmsPrincipal
| Method | Return Value | Parameter |
|---|---|---|
| DmsPrincipal | constructor | String name |
ExternalUserConfiguration
| Method | Return Value | Parameter |
|---|---|---|
| getGrantedModelParticipants | Collection | - |
HistoricalState
| Method | Return Value | Parameter |
|---|---|---|
| getPerfomer | Participant | - |
| getOnBehalfOf | Participant | - |
LoginProvider - Interface is deprecated
Note
| Method | Return Value | Parameter |
|---|---|---|
| getUserOid | long | - |
Participant
| Method | Return Value | Parameter |
|---|---|---|
| getPartitionOID | short | - |
| getPartitionId | String | - |
| getModelOID | int | - |
| getElementOID | int | - |
| getAllSuperOrganizations | List | - |
| getNamespace | String | - |
ParticipantAssociationFilter
| Method | Return Value | Parameter |
|---|---|---|
| forModelParticipant | ParticipantAssociationFilter | String participantID |
| forModelParticipant | ParticipantAssociationFilter | String participantID, boolean recursively |
| inUserGroup | ParticipantAssociationFilter | String groupID |
| forUser | ParticipantAssociationFilter | String account |
| forTeamLeader | ParticipantAssociationFilter | String roleId |
PerformingInBehalfOfFilter
| Method | Return Value | Parameter |
|---|---|---|
| forModelParticpants | PerformingOnBehalfOfFilter | Set<String> participantIDs |
| forModelParticpant | PerformingOnBehalfOfFilter | String participantID, boolean recursively |
| forModelParticpant | PerformingOnBehalfOfFilter | String participantID |
| forUserGroup | PerformingOnBehalfOfFilter | String groupID |
PerformingParticipantFilter
| Method | Return Value | Parameter |
|---|---|---|
| USER_ROLES_AND_ORGANIZATIONS | static field | - |
| forModelParticipant | PerformingParticipantFilter | String participantID |
| forModelParticipant | PerformingParticipantFilter | String participantID, boolean recursively |
| forUserGroup | PerformingParticipantFilter | String groupID |
| PerformingParticipantFilter | constructor | String participantID |
| PerformingParticipantFilter | constructor | String participantID, boolean recursively |
| PerformingParticipantFilter | constructor(private) | Kind filterKind, final String participantID, boolean recursively |
ProcessInstanceQuery
| Method | Return Value | Parameter |
|---|---|---|
| STARTING_DOMAIN_OID | static field | - |
| CURRENT_DOMAIN_OID | static field | - |
UnsupportedFilterException
| Method | Return Value | Parameter |
|---|---|---|
| UnsupportedFilterException | constructor | String message |
| UnsupportedFilterException | constructor | String message, FilterCriterion filter |
User
| Method | Return Value | Parameter |
|---|---|---|
| getRealmOID | long | - |
| getRealmID | String | - |
| addGrant | void | String id |
| removeGrant | void | String id |
WorkflowExceptiom
| Method | Return Value | Parameter |
|---|---|---|
| getRootCause | PublicException | - |
The following API changes have been performed with this release:
ExceptionHandlingInterceptor ensuring
that exceptions from embedded service factory services are unwrapped
and raised exceptions properly honor an existing transaction rollback
policy.The following breaking changes have been introduced with version 2.1.0:
Exception handling for embedded service factory services changed to return unwrapped exceptions as with regular API calls. Additionally, raised exceptions now properly honor an existing transaction rollback policy. See section API Changes for according API changes.
Note
This change might potentially break existing workarounds you have applied.
The support for the following platforms or platform versions has been dropped with this release:
The following platform versions are supported since this release:
For general known issues and restrictions, please refer to the Troubleshooting section in the online documentation.
If you expand a repository folder having a number of child nodes that exceeds a maximum number of about 500 and you are using a JBoss server, the following Exception might occur:
JBWEB000065: HTTP Status 500 - JBWEB002004: More than the maximum number of request parameters (GET plus POST) for a single request (512) were detected. Any parameters beyond this limit have been ignored. To change this limit, set the maxParameterCount attribute on the Connector.
To resolve this issue, add the following property to your JBoss configuration:
<system-properties> <property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="1000"/> </system-properties>
A client side error occurs in case you deploy a process model from the Console command in an EJB with DB2 environment.
To resolve this problem, set the following system property:
-Djavax.xml.stream.XMLInputFactory="com.ctc.wstx.stax.WstxInputFactory"
This forces to use the shipped woodstox implementation wstx-asl-3.2.8.jar.
The modern skin has the following issues in Mozilla FireFox or Google Chrome:
Colon (":") characters are not supported in user names as this leads to misinterpretations in a WebService environment.
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.
Using the Business Process Reporting perspective in IE9 currently has the following restrictions:
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:
The following modifications need to be applied in the JBoss 7.1 server:
Due to an issue, the JBoss default JSF implementation cannot be
changed as parameter
WAR_BUNDLES_JSF_IMPL
is not working in JBoss 7.1.1. (WAR file
using WAR_BUNDLES_JSF_IMPL embedded in an EAR file fails
deployment). This is caused by the issue: JSF
Version retrieved from deployment unit instead of top level
deployment unit.
As a workaround, in
com/sun/jsf-impl/main
module in
jsf-impl-2.1.7-jbossorg-2.jar/META-INF
: the
.tld
files have to be renamed to e.g.
*-tmp.tld
.
While deploying JBoss 7.1 for EJB 3, the following exception may
occur:
org.jboss.msc.service.ServiceNotFoundException: Service
service jboss.ejb.default-resource-adapter-name-service not
found
For a successful deployment, add the following under
<subsystem xmlns="urn:jboss:Domain:ejb3:1.4">
in the
standalone.xml
file.
<mdb> <resource-adapter-ref resource-adapter-name="hornetq-ra"/> <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/> </mdb>
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.