TIBCO iProcess Web Services Server Plug-in Release Notes

TIBCO iProcess Web Services Server Plug-in Release Notes
TIBCO iProcess® Web Services
Server Plug-in
Release Notes
Software Release 11.3
October 2011
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIB, TIBCO, Information Bus, The Power of Now, TIBCO Adapter, TIBCO iProcess BusinessWorks Connector,
TIBCO iProcess are either registered trademarks or trademarks of TIBCO Software Inc. in the United States
and/or other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
This software may be available on multiple operating systems. However, not all operating system platforms for
a specific software version are released at the same time. Please see the readme.txt file for the availability of this
software version on a specific operating system platform.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 2003-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
|i
Contents
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2
3
4
4
5
5
Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6
6
6
6
6
6
7
Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 10.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
8
8
8
8
8
Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Axis 1 Legacy Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issues with WS Policies and Custom Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issues with WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trademark Symbol Displays Incorrectly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Custom Header Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manually Constructed XSLTs and getNodeName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signature Confirmation Works Inconsistently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manually Constructed XSLTs and Custom Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Jetty Server Startup Issues with Certain Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Errors During Installation on Some Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generated SOAP Requests Not Reflecting WSDL Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
22
22
22
22
22
22
23
23
24
24
TIBCO iProcess Web Services Server Plug-in Release Notes
ii
| Contents
Some Symmetric Encryption Algorithms do not Work Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Headers Are Not Signed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signature Parts Fail in Inbound Outflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Migration Error Sometimes Ocurrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inflow and Outflow Usernames and Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security Profile Creation Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signature Key Identifier and Inflow Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EncryptBeforeSigning and Security Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supporting Tokens and Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unsupported Key Transport Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Invalid Data Mapping not Logged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iProcess Field Deletion not Logged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Errors Using TIBCO Workspace Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SOAP/HTTP with SSL WSDL Generation Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console/Silent Installation not Supported on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
25
25
25
26
26
26
26
27
27
27
27
27
28
28
Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
TIBCO iProcess Web Services Server Plug-in Release Notes
|1
Release Notes
Check the TIBCO Product Support web site at http://support.tibco.com for
product information that was not available at release time. Entry to this site
requires a username and password. If you do not have a username, you can
request one. You must have a valid maintenance or support contract to use this
site.
Topics
•
New Features, page 2
•
Changes in Functionality, page 6
•
Deprecated Features, page 8
•
Migration and Compatibility, page 9
•
Closed Issues, page 10
•
Restrictions, page 15
•
Known Issues, page 22
•
Other Information, page 29
TIBCO iProcess Web Services Server Plug-in Release Notes
2
|
Release Notes
New Features
This section lists features added since the last major (10.0) release of this product.
Release 11.3
The following new features have been added:
New Platforms Supported
This release adds support for the following new platforms:
Microsoft Windows (x86 or x64)
•
Windows 7 Professional
•
Windows Server 2008 R2 Standard
Solaris:
•
Sun SPARC Solaris 10
HP-UX on Itanium:
•
HP-UX 11i Version 3
AIX:
•
AIX Version 6.1
Linux:
•
Red Hat Enterprise Linux Server 5.x
•
Red Hat Enterprise Linux Advanced Platform 5.x
•
SUSE Enterprise 10.x.
•
SUSE Enterprise 11.x
(Other Linux implementations may be compatible; see the iProcess Engine
documentation.)
TIBCO iProcess Web Services Server Plug-in Release Notes
New Features 3
|
Databases:
•
Oracle 10g release 10.2.0.4 or above
•
Oracle 11g
•
Oracle 11g release 2
•
DB2 Universal Database 9.5
•
DB2 Universal Database 9.7
•
SQL Server 2008 R2 Service Pack 1 or later
•
SQL Server 2008 Service Pack 1 or later
•
SQL Server 2005 Service Pack 1 or 2
Not all platform/database combinations are supported - see the TIBCO iProcess
Engine Installation guides for more information.
Using Security Profiles to Send iProcess Field Data
Using the Security Profile Administrator, you can include iProcess field data in
your SOAP header to outbound web services at runtime. For example, you could
use custom headers to send context-sensitive iProcess field data that could be
used in the web service at runtime. This is achieved by inserting a token into any
field in the main dialog of the Security Profile Administrator. The fields can
contain both SOAP and security information. Refer to the TIBCO iProcess Web
Services Plug-in User Guide for more information.
Correlation ID Now Included in JMS Correlation ID Field
If the inbound call contains a correlation ID, the iProcess Web Services Server
Plug-in includes the correlation ID in the JMS Correlation ID field in the response
message that it sends. This enables you to use a single, permanent response queue
if required, and use the correlation ID to match request messages to response
messages.
Release 10.6.1
Sun x86 Platform Supported
This release adds support for the Sun x86 platform.
TIBCO iProcess Web Services Server Plug-in Release Notes
4
|
Release Notes
Release 10.6
The following are new features in this release:
•
Enhancements to support Web Services transport layer security (SSL) and
SOAP security such as installer changes, changes to the database to support
security profiles, and architectural changes. The following security
mechanisms are supported:
— Transport Layer Security HTTPS and digital certificates
— SOAP Security XML Signatures, XML Encryption, Basic Authentication,
Timestamps, and WS Policy files
•
Simplified installation procedure with a reduced number of dialogs and
options, as well as better default values.
•
Configuration of multiple JMS Providers now supported.
•
Websphere 6.1 is now supported as an external and internal JMS provider for
use with the TIBCO iProcess Web Services Plug-in.
•
New timeout capability for XML/JMS and SOAP/HTTP messages.
•
The Web Services configuration file (wsconfig.properties) allows you to
perform most of the ongoing administration and configuration tasks related to
the iProcess Web Services Server Plug-in. It is located in:
webservices_server_location\jetty-6.1.1\staffware
Release 10.5
The following are new features in this release.
XML Mapping Capabilities (18444)
XML mapping capabilities allow you to map iProcess Engine field data to Web
Service data. This generates an Extensible Stylesheet Language Transformation
(XSLT) that previously had to be created manually. Refer to the TIBCO iProcess
Web Services Plug-in User’s Guide for more information.
Configurable URL Aliases (18560)
When you design your iProcess Engine Web Services step, instead of having to
specify explicit URLs for the WSDL location you can now use aliases instead. This
means that the URLs can be changed/maintained without modifying the iProcess
procedure (for example, when moving from a test to a production environment).
Refer to the TIBCO iProcess Web Services Plug-in User’s Guide for more information.
TIBCO iProcess Web Services Server Plug-in Release Notes
New Features 5
|
High Availability Configuration (18689)
A High Availability configuration is supported. This type of configuration uses
multiple Jetty servers to provide redundancy in case one Jetty Server fails. Refer
to the TIBCO iProcess Web Services Plug-in Installation Guide and the TIBCO iProcess
Web Services Plug-in User’s Guide for more information.
Release 10.3
None.
Release 10.2
Refactor the iProcess Web Services Plug-in Architecture to Remove the Need for an
Application Server (16541)
The iProcess Web Services Plug-in architecture has been refactored so that an
application server is no longer needed. The application server platform has now
been replaced with a combined JMX and JMS server platform. The Weblogic
SOAP component has been replaced with Axis. Refer to the TIBCO iProcess Web
Services Plug-in User’s Guide for more information.
TIBCO iProcess Web Services Server Plug-in Release Notes
6
|
Release Notes
Changes in Functionality
This section lists changes in functionality since the last major (10.0.0) release of
this product.
Release 11.3
New Version of Jetty
A new version of Jetty (6.1.25) is now used.
Release 10.6.1
TIBCO Enterprise Message Server (EMS)
TIBCO Enterprise Message Server (EMS) client libraries are no longer distributed
with the TIBCO iProcess Web Services Server Plug-in. TIBCO EMS must be
purchased and installed separately.
Release 10.6
This version includes the following changes in functionality:
•
There is a new Security Profile Administrator that allows you to define
security settings that are saved as a profile in the database. These settings can
subsequently be reused at design time.
•
Axis2 now used instead of Axis 1.
•
You can now configure a timeout for XML/JMS and SOAP/HTTP messages.
•
A new version of Jetty (6.1) is now used.
Release 10.5
None.
Release 10.3
None.
TIBCO iProcess Web Services Server Plug-in Release Notes
Changes in Functionality 7
|
Release 10.2
Refactor the iProcess Web Services Plug-in Architecture to Remove the Need for an
Application Server (16541)
The iProcess Web Services Plug-in architecture has been refactored so that an
application server is no longer needed. The application server platform has now
been replaced with a combined JMX and JMS server platform. The Weblogic
SOAP component has been replaced with Axis. Refer to the TIBCO iProcess Web
Services Plug-in User’s Guide for more information.
TIBCO iProcess Web Services Server Plug-in Release Notes
8
|
Release Notes
Deprecated Features
This section describes deprecated features and lists equivalent features that
accomplish the same result, if relevant. Any use of a deprecated feature should be
discontinued as it may be removed in a future release. You should avoid
becoming dependent on deprecated features and become familiar with the
equivalent feature.
Release 11.3
The following features have been removed in this release.
•
Support for AXIS 1.
Release 10.6.1
The following features are deprecated in this release.
•
None.
Release 10.6
The following features are deprecated in this release:
•
Asynchronous with Reply invocation style has been replaced by Automatic
Delayed Release as the default invocation style.
Release 10.5
The following features are deprecated in this release.
•
None.
Release 10.3
The following features are deprecated in this release.
•
None.
TIBCO iProcess Web Services Server Plug-in Release Notes
Migration and Compatibility 9
|
Migration and Compatibility
For migration information, and for information on the versions of software
compatible with this release, please refer to the TIBCO iProcess™ Web Services
Server Plug-in Installation Guide.
If you only need to define iProcess Web Services steps in procedures (you do not
run cases on your machine), you only need to install the iProcess Web Services
Client plug-in - refer to the TIBCO iProcess Web Services Client Plug-in
Installation Guide. If you are running cases containing Web Services steps, you
must also install the iProcess Web Services Server Plug-in.
Examples
Some examples are included with the TIBCO iProcess Web Services Server
Plug-in. The schemas, iProcess procedures, and BusinessWorks processes can all
be found in the examples folder on the TIBCO iProcess Engine Web Services
Server Plug-in product physical media. The examples provided with this version
of the TIBCO iProcess Web Services Server Plug-in are not compatible with earlier
versions of the product. Earlier versions of the product should use the examples
provided with their version of the TIBCO iProcess Web Services Server Plug-in.
TIBCO iProcess Web Services Server Plug-in Release Notes
10
|
Release Notes
Closed Issues
The table in this section lists issues that were closed in the named releases.
Closed in
Release
MR #
Summary
11.3.0
40380
Threading issues when using Bouncycastle to decrypt.
11.3.0
43258
Accented characters may cause either a fatal error or corrupted data
when running the Web Services Plug-in.
11.3.0
43272
Outbound web service calls failed when using Weblogic 9.2 XML/JMS.
11.3.0
43182
Web service calls were processed slowly under certain circumstances.
11.3.0
41590
A Web Services call fails if the data returned contains the < character.
11.3.0
39812
The SOAP Envelope Body stripping code has a bug in it which means if
you have body within the XML payload it will truncate incorrectly.
10.6.1
39207
Port TIBCO iProcess Web Services Server Plug-in to Sun x86 Solaris 10
and unbundle TIBCO Enterprise Message Server (EMS) client libraries.
Implemented.
10.6.0
30259
TIBCO Enterprise Message Service (EMS) can be auto configured during
installation.
Implemented.
10.6.0
30188
The Web Services Server Plug-in has hardcoded values for date/time
conversion formats.
Implemented. The ability to configure this has been added to the
wsconfig.properties file (for more information, see TIBCO iProcess Web
Services Plug-in User’s Guide.
10.6.0
30158
Add support for WS Policy files in a security profile.
Implemented.
10.6.0
30144
Add support for WebSphere 6.
Implemented.
TIBCO iProcess Web Services Server Plug-in Release Notes
Closed Issues 11
|
Closed in
Release
MR #
Summary
10.6.0
30099
Add support for multiple JMS providers.
Implemented.
10.6.0
30041
Implement changes to simplify the installer, especially when using
TIBCO EMS as the default JMS provider.
Implemented.
10.6.0
19972
Modify installer to allow the configuration of multiple JMS providers
with TIBCO Enterprise Message Service (EMS) as the default.
Implemented.
10.6.0
19780
XML over JMS messages do not time out and wait indefinitely for a
response.
Corrected. Timeout facility implemented.
10.6.0
19727
Need to remove decrypted password from log files.
Corrected.
10.6.0
19726
Upgrade to Axis2 to make use of security features.
Implemented.
10.6.0
19684
Web Services Plug-in cannot connect to JMS provider when
authorization is enabled on the JMS server.
Corrected.
10.6.0
19639
When using XML over JMS for WebService calls we could set the
CorrelationID in the JMS message to match the iProcess unique message
key for the request.
This means that if a request is retried multiple times (for instance if the
receiver cannot respond to the request so the request fails) the receiver
has a way of identifying the messages as duplicates.
Corrected.
10.6.0
19034
Suspending a sub-procedure does not work.
Corrected.
TIBCO iProcess Web Services Server Plug-in Release Notes
12
|
Release Notes
Closed in
Release
MR #
Summary
10.6.0
16339
The Timed Out work queue can grow very large as old items are not
timed out.
Corrected; timeout implemented.
10.5.0
18763
The Webservices Server Plug-in generates an exception when accessing a
queue using Websphere MQseries. This is because the queue alias name
is used but no JNDI lookup is done first.
Corrected.
10.5.0
18689
Modify the Web Services plug-in to support High Availability.
Implemented.
10.5.0
18637
Modify the WebServices Server Plug-in to use a JMS-based design time
cache rather than a disk-based one. When multiple Jetty installations
access one set of JMS queues, this means that a given message can always
get at the design-time cache even if it is on a different machine to the
initial call.
Implemented. Files are now written to a JMS queue.
10.5.0
18560
Add configurable WebService URLs to the WebServices client and server
plug-ins.
Implemented.
10.5.0
18444
The Web Services client plug-in requires a graphical XML mapping tool
to facilitate the creation of XSLT.
Implemented.
10.5.0
18387
For each Web Service outbound call from the iProcess Engine, a memory
leak occurs proportional to the size of the cached wsdl in the
jetty/staffware/cache/ directory. This is because the Axis library is
caching WSDL data (because it believes the URL is remote rather than
local file system) and never removes it from the cache.
Fixed.
TIBCO iProcess Web Services Server Plug-in Release Notes
Closed Issues 13
|
Closed in
Release
MR #
Summary
10.5.0
18287
Reader threads on the JMS queues are handled by a pool manager which
adjusts the number of active threads dependant on the number of
outstanding messages in a queue. If the maximum thread count is
reached, the number of threads is never reduced, even after the system
load decreases. The threads continue to check the queues for messages
periodically.
Fixed.
10.5.0
18126
If installing a new Business Works Connector product or modifying an
existing installation when using Java 5 (1.5) the encryption of passwords
is performed incorrectly and the server plug-in reports fatal errors when
the iProcess Engine is started - that the plug-in failed to initialize.
Fixed.
10.3.0
17889
The installer has been modified so that if the DB test and/or JMS test fail,
you cannot progress with the installation.
10.3.0
13798
In automatic mode, the installer fails to register the EAI plug-in with the
server. No error is reported to the user but the error is reported in the log
file.
Corrected.
10.2.0.1
17621
Implemented support for DB2.
10.2.0
16838
Version 10.2.0 of the TIBCO Staffware EAI Rules Manager Plug-in is the
first release of this product on the Linux platform.
10.2.0
16541
Refactor the iProcess Web Services Plug-in architecture so that an
application server is no longer needed. See New Features on page 2 for
more information.
i10.0-o(4.0)
16339
The timed out work queue can grow very large as old items are not
timed out.
Corrected. A new parameter has been added to the timed out web
service calls handler with a default of 1 hour. A warning message is sent
to the Web Services.log file.
16331
Implement support for Oracle8i.
TIBCO iProcess Web Services Server Plug-in Release Notes
14
|
Release Notes
Closed in
Release
MR #
Summary
16311
The log file default settings need to be improved.
Corrected. The log file now only outputs errors, warnings and info
messages. The log file will grow to 100Mb at which point it is rolled over.
Two backup files are also stored bringing the total disk space required for
log files to 300Mb.
16258
The EAI step callout fails if values are used for the Web Services input
values rather than Staffware fields.
Corrected.
15365
Implement support for WebSphere.
TIBCO iProcess Web Services Server Plug-in Release Notes
Restrictions 15
|
Restrictions
This section lists restrictions for the current version.
MR #
Summary/Workaround
IPWS-476
Summary An outbound call over XML/JMS must use a queue. Topics are not
supported using the XML/JMS data transport mechanism
Workaround None.
35056
Summary Web Service calls do not support mixed content. For example,
<xs:complexType mixed="true">
is not supported.
Workaround You should use an alternative construct like the one below:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:element name="root">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="code" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:schema>
TIBCO iProcess Web Services Server Plug-in Release Notes
16
|
Release Notes
MR #
32169
Summary/Workaround
Summary Using SSL in an AIX environment generates errors similar to the
following:
2007-10-09 15:58:15.305::INFO: Started SslSocketConnector @
0.0.0.0:8443
Exception in thread "btpool0-3" java.lang.NoClassDefFoundError:
javax.crypto.b initialization failure)
Workaround One way of correcting this is as follows:
1. Install the unlimited strength JCE policy files. These JARs are available from
the IBM web site, and should be installed in the <JRE>/lib/security directory:
— local_policy.jar
— US_export_policy.jar
2. Add the following line to the <JRE>/lib/security/java.security file:
security.provider.6=org.bouncycastle.jce.provider.Bouncy
CastleProvider
Note that this provider entry must appear at the end of the list.
3. Create the certificate keyfile on Windows, not on AIX.
4. Install the Bouncy Castle JAR (bccprov13-133.jar) in <JRE>/lib/ext.
5. Run Jetty as the root user.
32116
Summary When using the Security Profile Administrator on AIX systems to
create a new profile, selecting either Encryption or Signatures changes the
screen color surrounding these fields.
Workaround None.
32100
Summary When using SSL, if you use the IP address of a machine instead of the
machine name as key common name, at design time you will not be able to
access the WSDL to select an operation.
Workaround Specify the machine name instead of the IP address as a key
common name.
32019
Summary The iProcess Web Services Server Plug-in does not support Java 1.4 in
AIX environments.
Workaround None.
TIBCO iProcess Web Services Server Plug-in Release Notes
Restrictions 17
|
MR #
Summary/Workaround
32004
Summary AIX Jetty installations cannot co-exist with non-AIX Jetty installations
in an High Availability environment (they must NOT share the same database).
Similarly, you cannot migrate security profiles between AIX and other
platforms.
Workaround None.
32002
Summary In an AIX environment, you must manually create the JMS queues;
the installer does not do this automatically. For more information, see the TIBCO
iProcess Web Services Server Plug-in Installation Guide.
31528
Summary If a step is withdrawn while the Web Service call is in process, a
sw_warn error is created when the Web Service responds. This is because there
is an attempt to release a step that no longer exists
Workaround None.
31511
Summary Because of the way the pooling model used by the TIBCO iProcess
Web Services Server Plug-in works, if low numbers of Web Service steps are
processed, and some of these steps are causing errors, there can be delays in the
processing of other steps
Workaround None.
31461
Summary Only basic authentication can be used for message level security
when using RPC based Webservice calls.
Workaround None.
31286
Summary The password of the outbound truststore is not encrypted in the
sec.properties file.
Workaround None.
31259
Summary Sometimes when installing remotely using programs such as Exceed,
if a popup appears (for example, after the database test), you cannot edit the
fields in the dialog. This does not happen when performing the installation
locally.
Workaround , Return to the previous dialog, then re-display the original dialog.
You can then edit the fields.
TIBCO iProcess Web Services Server Plug-in Release Notes
18
|
Release Notes
MR #
Summary/Workaround
31179
Summary Sometimes the endpoints on a WSDL accessed using HTTPS are not
pointing to the HTTPS protocol or the correct port.
Sometimes when accessing the WSDL file for the TIBCO iProcess Web Services
Plug-in using the HTTPS protocol, the WSDL does not include a port with an
endpoint that includes this protocol. For example, the WSDL file is accessed at
https://localhost:8443/axis2/services/WebIPE?wsdl, yet all the ports refer to
http://localhost:8090/axis2/services/WebiPE.
Workaround None.
31163
Summary The UNIX scripts are included with the Jetty installation for Windows
although they do not need to be provided. Similarly, on Windows platforms,
UNIX scripts are provided as well.
Workaround None.
30964
Summary There can be problems calling the TIBCO iProcess Web Services
Plug-in from WebSphere Rapid Application Developer (RAD). These are caused
by the SOAP 1.2 entries in the WSDL that are not currently supported by RAD
Workaround None.
30838
Summary After a JMS timeout, when there are no messages in the queue to be
processed, the following message is displayed:
"QueueReader - Null message received - throwing it away"
This text of this message should be reworded to be clearer, and the error
downgraded to an informational message.
Workaround None.
30806
Summary When you restart the TIBCO EMS server you also must restart the
Jetty server; otherwise Web Services calls fail and the following error is reported
in the Jetty logs.
2007-07-16 15:19:23,205 [FATAL] [Thread-6] PooledQueueBrowser Unable to create browser on queue: queue.SWOutbound
javax.jms.IllegalStateException: Session is closed
Workaround None.
TIBCO iProcess Web Services Server Plug-in Release Notes
Restrictions 19
|
MR #
Summary/Workaround
30552
Summary At runtime, encryption fails with an error about an unsupported key
algorithm.
Workaround Add BouncyCastle to the JRE Security providers for Rampart
encryption/signing as follows
1. Copy JETTY_HOME\ext\bcprov-jdk13-133.jar into the
JRE_HOME\lib\ext directory.
2. Edit JRE_HOME/lib/security/java.security and add Bouncy Castle as a
security provider. For example:
security.provider.7=org.bouncycastle.jce.provider.Bouncy
CastleProvider
30522
Summary The timeout period for a timestamp security token is 5 minutes and
cannot be changed.
Workaround None.
30511
Summary When selecting a client WSDL, SSL security does not work with client
authentication for a WebSphere server.
Workaround None.
30199
Summary When using the Asynchronous with Reply invocation method,
messages can be lost if Jetty is restarted.
Workaround None.
28260
Summary During the Server Plug-in installation, pressing the Alt key to use a
hot key does not work correctly.
Workaround None.
28258
Summary During the Server Plug-in installation, in the Configure iPE Server
Information dialog, you can select an iProcess Engine node for the installation.
If you make a selection other than the default iProcess Engine node, click Next,
and then click Back, the default selection is displayed rather than the node you
selected.
Workaround None.
TIBCO iProcess Web Services Server Plug-in Release Notes
20
|
Release Notes
MR #
Summary/Workaround
27173
Summary There are three bindings displayed for calling iProcess Engine Web
Service operations:
•
WebiPESOAP11port_http
•
WebiPESOAP12port_http
•
WebiPEHttpport1
Do not use the WebiPEHttpport1 binding; it is unsupported.
Workaround None.
24785
Summary If you install the TIBCO iProcess Web Services Server Plug-in over an
existing installation an error occurs.
Workaround Delete any previous version of the TIBCO iProcess Web Services
Server Plug-in before installing this version.
18389
Summary You cannot install this version of the iProcess Web Services Server
Plug-in on AIX using Java 1.5. The product can be run using Java 1.5 but not
installed using it. This is a restriction in the InstallShield product.
Workaround None.
16757
Summary You can only install the TIBCO iProcess Web Services Server Plug-in
in graphical mode. The options given for silent or console mode do not work.
Workaround None.
16617
Summary A Windows installation will fail if the environment path for the
%TEMP% directory contains spaces.
Workaround None.
16311
Summary The log file is restarted every time you re-start your Jetty server.
Workaround If you keep your Jetty server running, then TIBCO recommend that
you keep track of the size of the log file and periodically archive it, if it grows too
large.
16306
Summary Passing null values into Web Services that require parameters can
cause the step to never return to Staffware.
Workaround None.
TIBCO iProcess Web Services Server Plug-in Release Notes
Restrictions 21
|
MR #
Summary/Workaround
16302
Summary Web Services can present multiple methods which have the same
name but different parameters (called overloaded methods). The Web Services
integration server is not able to call these Web Services at this time, a "duplicate
method" error will be returned.
Workaround None.
No MR
Summary If you install the TIBCO iProcess Web Services Server Plug-in and you
select Websphere as the JMS provider, you must provide a JNDI username and
password on the JMS Authentication dialog. You must do this even if your
Websphere application server is unauthenticated. If you do not do this, it causes
a Null Username exception when you perform the JMS test from the JMS
Provider Resource Details dialog. The actual username and password you enter
is irrelevant. This means you can enter whatever you like.
Workaround None.
No MR
Summary When a boolean value is submitted to Web Services, on its return an
additional decimal place is added. For example, 1 is returned as 1.0.
Workaround None.
TIBCO iProcess Web Services Server Plug-in Release Notes
22
|
Release Notes
Known Issues
This section lists known issues for the current version.
Issues with WS Policies and Custom Headers
WSPolicy files cannot be used with custom headers.
Issues with WebLogic
If you have the following scenario:
•
Your external web services are deployed through HTTPS
•
WebLogic is your JMS provider
then the calls to web services through HTTPS can fail at run-time.
Trademark Symbol Displays Incorrectly
On some Unix platforms the trademark logo for TIBCO products is displayed as
"?"
Custom Header Validation
It is not possible validate all custom headers easily. This only happens when
TIBCO iProcess Web Services Server Plug-in makes the web service call.
Therefore, sometimes errors in the custom header, such as undeclared XML
prefixes, are not encountered until the web service call is made.
Manually Constructed XSLTs and getNodeName
Calling TIBCO iProcess Web Services Server Plug-in's getNodeName fails using
manually constructed XSLT.
Signature Confirmation Works Inconsistently
Signature confirmation works inconsistently as illustrated by the following
scenarios:
TIBCO iProcess Web Services Server Plug-in Release Notes
Known Issues 23
|
Scenario 1
1. Configure TIBCO iProcess Web Services Server Plug-in to call an external web
service.
2. From the TIBCO iProcess Web Services Server Plug-in, configure
authentication, encryption and timestamp for outflow.
3. Configure authentication, signature, encryption and timestamp for inflow.
4. Specify that TIBCO iProcess Web Services Server Plug-in confirm signature
confirmation in inflow.
5. Configure the external web service correctly, generating no signature
confirmation. The process works, even though it should fail as there is no
signature confirmation in the SOAP response.
Scenario 2
1. Configure an external web service to call TIBCO iProcess Web Services Server
Plug-in's inbound call.
2. From TIBCO iProcess Web Services Server Plug-in's, configure no security for
inflow.
3. Configure authentication, signature, encryption and timestamp for outflow.
4. Specify that TIBCO iProcess Web Services Server Plug-in confirm signature
confirmation in outflow.
5. Configure the external web service correctly. There is no signature
confirmation in the SOAP response from the TIBCO iProcess Web Services
Server Plug-in.
Manually Constructed XSLTs and Custom Headers
Using manually constructed XSLT, custom headers fail to be sent. However, cases
are processed successfully.
Jetty Server Startup Issues with Certain Platforms
Although installation on Red Hat Enterprise Linux AS 5.x using Weblogic as the
JMS Provider is successful, the Jetty server fails to start.
TIBCO iProcess Web Services Server Plug-in Release Notes
24
|
Release Notes
Database Errors During Installation on Some Platforms
On the following platforms with a DB2 Database, errors are generated during
installation:
•
Red Hat Enterprise Linux AS 5.x
•
SUSE Enterprise 10.x
•
AIX 5.3
•
AIX 6.1
•
Solaris 9
•
Solaris 10
The errors are similar to the ones below:
Connecting to: jdbc:db2://192.168.68.131:50000/pra3v...
Schema owner: swpro
Core: Failed to close JDBC connection:
com.ibm.db2.jcc.a.SqlException: [jcc][t4][10251][10308][3.51.90]
java.sql.Connection.close() requested while a transaction is in
progress on the connection.
The transaction remains active, and the connection cannot be
closed. ERRORCODE=-4471, SQLSTATE=null
Located Nodename: prwsa3v
Core: Failed to close JDBC connection:
com.ibm.db2.jcc.a.SqlException: [jcc][t4][10251][10308][3.51.90]
java.sql.Connection.close() requested while a transaction is in
progress on the connection.
The transaction remains active, and the connection cannot be
closed. ERRORCODE=-4471, SQLSTATE=null
Database tested successfully (Nodename: prwsa3v, Webservice tables:
pre10.5).
However, installation is still performed successfully.
Generated SOAP Requests Not Reflecting WSDL Style
It does not matter if a web service is deployed of style RPC/Encoded, or
RPC/Literal, the SOAP request that is generated by the TIBCO iProcess Web
Services Server Plug-in is the same.
Some Symmetric Encryption Algorithms do not Work Correctly
The following Symmetric Encryption Algorithms do not work correctly:
•
For inbound outflow, even if you select 3DES, AES128/192/256, AES128 is
always used.
•
For outbound outflow, when AES192/256 is selected, outbound call fails.
TIBCO iProcess Web Services Server Plug-in Release Notes
Known Issues 25
|
Headers Are Not Signed
If you select Sign headers and body, only the body is signed, not the sign headers.
Signature Parts Fail in Inbound Outflow
If you define Signature Parts in inbound outflow, it fails to sign the specified
parts at run-time and no error is reported.
Process Migration Error Sometimes Ocurrs
A navigator error may be received when migrating an EAI web services
procedure from a development to a live environment. You should manually edit
the .xfr file and change the name of the alias server name to the live environment
server.
TIBCO iProcess Web Services Server Plug-in Release Notes
26
|
Release Notes
Inflow and Outflow Usernames and Passwords
When defining a security policy, in which a username and password is sent in
outflow messages but not received in inflow messages, you can specify a
username and password in either inflow or outflow. In both situations, the
username and password is sent correctly.
Security Profile Creation Failures
On Red Hat Enterprise Linux AS 5.x and SUSE Enterprise 10.x with a DB2
Database, if you follow the steps below, creating a security policy will fail:
1. Install a new TIBCO iProcess Web Services Server Plug-in.
2. Register the TIBCO iProcess Web Services Server Plug-in correctly.
3. Start the TIBCO iProcess Engine.
4. Start TIBCO iProcess Web Services Server Plug-in.
5. Start Security Profile Administrator.
6. Create an empty security profile.
7. Modify the security policy to have all security policies except custom headers.
8. Save the security policy.
9. From this security policy, create a new security profile. On clicking Create,
errors are generated.
Repeat step 9 again and the security profile is created correctly.
Signature Key Identifier and Inflow Messages
Regarding signature key identifiers and inflow messages, note the following:
•
You must select one signature key identifier in inflow messages according to
the SOAP request.
•
It does not matter if the signature key identifiers do not match.
EncryptBeforeSigning and Security Policies
You must not enable EncryptBeforeSigning when defining security policies. It
causes the following error message to be displayed in the logs:
security processing failed (actions mismatch)
TIBCO iProcess Web Services Server Plug-in Release Notes
Known Issues 27
|
Supporting Tokens and Encryption
When a web services security policy is used, Supporting Tokens are always
encrypted if AsymmetricBinding is enforced and signing is performed before
encryption.
Unsupported Key Transport Algorithm
The Key transport algorithm:
http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p is not supported and
should not be used.
Invalid Data Mapping not Logged
If you design a call to a TIBCO BusinessWorks process that has an invalid field
mapping, like mapping an iProcess string field to a BusinessWorks Integer field,
for example, the field in the iProcess process is blank and no errors are reported in
the log.
iProcess Field Deletion not Logged
This applies to the XML/JMS data transport mechanism. If you delete an iProcess
field from a step, the Jetty log should report that the field is missing when making
an outbound call. Instead, the process continues without the missing field.
Errors Using TIBCO Workspace Aliases
When using aliases in TIBCO Workspace, errors are generated in the log files,
despite the aliases being created successfully.
TIBCO iProcess Web Services Server Plug-in Release Notes
28
|
Release Notes
SOAP/HTTP with SSL WSDL Generation Problem
Using the SOAP/HTTP data transport mechanism with SSL enabled, the WSDL is
generated with incorrect endpoints, similar to that shown below:
<wsdl:port name="WebiPESOAP11port_http1"
binding="axis2:WebiPESOAP11Binding">
<soap:address
location="<http://192.168.68.72:8090/axis2/services/WebiPE>" />
</wsdl:port>
You must manually modify the endpoints in the WSDL as follows:
•
Change http to https.
•
Change the port number to the one specified for HTTPS during installation
(by default, 8443).
Console/Silent Installation not Supported on UNIX
Installing the TIBCO iProcess Web Services Server Plug-in on UNIX in Console
Mode and in Silent Mode is not supported.
TIBCO iProcess Web Services Server Plug-in Release Notes
Other Information 29
|
Other Information
Understanding the Return Values from iProcess Functions
When requesting iProcess functions, the values that are returned indicate whether
or not the function requests have been successful. They do not indicate that the
functions have performed successfully. This means, for example, that you may
receive a successful return value from a request to the iProcess function
doCaseStart but the case does not start successfully.
Understanding the Return Values from the doActivateSub Function
When using the iProcess function doActivateSub to activate a case of a
sub-procedure, the following return values indicate whether or not the request to
activate the case has been successful:
If the case number or 0 is returned, the request has been successful.
If -1 is returned, this means an error has occurred and the request has not been
successful.
TIBCO iProcess Web Services Server Plug-in Release Notes
30
|
Release Notes
TIBCO iProcess Web Services Server Plug-in Release Notes
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement