TIBCO iProcess® Web Services

Server Plug-in
Release Notes
Version 11.9.0
August 2022

Copyright © 2003-2022. TIBCO Software Inc. All Rights Reserved.

2 | Contents

Contents
Contents 2

New Features 4
Release 11.9.0 4
Release 11.8.0 4
Release 11.3.0 5

Changes in Platform Support 7

Release 11.9.0 7
Release 11.8.0 8

Changes in Functionality 9
Release 11.9.0 9
Release 11.8.0 9
Release 11.3.0 9

Deprecated Features 10
Release 11.9.0 10
Release 11.8.0 10
Release 11.3.0 10

Migration and Compatibility 11

Examples 11

Closed Issues 12

Restrictions 14

Known Issues 20

Other Information 26

TIBCO iProcess® Web Services Server Plug-in Release Notes

3 | Contents

TIBCO Documentation and Support Services 27

Legal and Third-Party Notices 29

TIBCO iProcess® Web Services Server Plug-in Release Notes

4 | New Features

New Features
This section lists features added in the following releases of the product.

Release 11.9.0
No new features have been added in this release of TIBCO iProcess® Web Services Server
Plug-in.

Release 11.8.0
The following new features are added in this release:

New Version of Java Supported

This release adds support for Java 11 for all platforms and Java 8 for AIX. See also, the
Changes in Platform Support section.
New Version of Jetty Used
This release uses a new version of Jetty (9.4.35).
Migration from 32-bit to 64-bit
In this release, 32-bit platforms have been migrated to 64-bit mode.
DB2 Configuration
In this release, you can set the following new configuration parameter:
SWDBUtil.removeConnectionsOnException = true/false (Default: false)

Setting this parameter resolves a problem in DB2 that sometimes means a JDBC
connection can become invalid after a genuine SQL exception is thrown.
System to Manually (Within the Plug-in) Move "Poisonous" Messages (For
WebSphere/WebSphere MQ)
WebSphere/WebSphere MQ does not automatically move "poisonous" messages to a
named Poison queue after a certain number of retries. So, for WebSphere/WebSphere
MQ, now you can implement a system to manually (within the plug-in) move messages
which have been retried x times to the Poison queue. For details, see the "What to do"

TIBCO iProcess® Web Services Server Plug-in Release Notes

5 | New Features

section in "WebSphere/WebSphere MQ Does Not Automatically Move "Poisonous"

Messages" of TIBCO iProcess Web Services Server Plug-in Installation.

Release 11.3.0
The following new features are added in this release:

New Platforms Supported

This release adds support for the following new platforms:
l Microsoft Windows (x86 or x64):
o Windows 7 Professional
o Windows Server 2008 R2 Standard

l Solaris:
o Sun SPARC Solaris 10

l HP-UX on Itanium:
o HP-UX 11i Version 3

l AIX:
o AIX Version 6.1

l Linux:
o Red Hat Enterprise Linux Server 5.x
o Red Hat Enterprise Linux Advanced Platform 5.x
o SUSE Enterprise 10.x.
o SUSE Enterprise 11.x
(Other Linux implementations may be compatible; see the iProcess Engine
documentation.)

l Databases:
o Oracle 10g release 10.2.0.4 or above
o Oracle 11g

TIBCO iProcess® Web Services Server Plug-in Release Notes

6 | New Features

o Oracle 11g release 2

o DB2 Universal Database 9.5
o DB2 Universal Database 9.7
o SQL Server 2008 R2 Service Pack 1 or later
o SQL Server 2008 Service Pack 1 or later
o 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.

TIBCO iProcess® Web Services Server Plug-in Release Notes

7 | Changes in Platform Support

Changes in Platform Support

This section lists changes in platform support in the following releases of this product.
From 10.0.0 to 11.9.0 release, this information is included either in the New Features or
Changes in Functionality sections of the release notes. Only from version 11.8.0 onwards,
changes in platform support are listed here.

Release 11.9.0
The following table lists the features that have been removed in the version 11.9.0 of
TIBCO iProcess® Web Services Server Plug-in.

Platform Support Removed

Platform Status As of Notes
Release

Solaris Removed 11.9.0 TIBCO iProcess® Web Services Server Plug-in no

longer supports Solaris platform.

AIX Removed 11.9.0 TIBCO iProcess® Web Services Server Plug-in no

longer supports AIX platform.

In line with TIBCO's Platform Support Policy, the 11.8.x release of iProcess (iProcess
Engine, iProcess Workspace, and iProcess Developer) is the last release to support the
Oracle Solaris and IBM AIX platforms.
The following product components are directly affected by this change:
• TIBCO iProcess Engine (Oracle)
• TIBCO iProcess Engine (DB2)
• TIBCO iProcess Technology plug-ins
• TIBCO iProcess Webservices Server plug-in
• TIBCO iProcess Server Objects (Java)
• TIBCO iProcess Workspace (Browser)

TIBCO iProcess® Web Services Server Plug-in Release Notes

8 | Changes in Platform Support

For a complete list of supported platforms, see the Readme file.

Release 11.8.0
In this release, platform support for iProcess® Web Services Server Plug-in has changed as
follows:

Supported Features
Platform Status As of Notes
Release

Linux Added 11.8.0

l Red Hat Enterprise Linux (RHEL) Server 7.6(64

Bit) on AWS

l Red Hat Enterprise Linux (RHEL) Server 7.6 (64

Bit) on Azure

Oracle Solaris Added 11.8.0

l Solaris SPARC 11.4 (64 Bit)

Oracle Solaris x86 Removed 11.8.0

Microsoft Windows Added 11.8.0

l Windows Server 2016 on AWS

l Windows Server 2016 (64 Bit) on Azure

Goggle Cloud Platform Added 11.8.0

HP-UX Removed 11.8.0

For a complete list of supported platforms, see the Readme file.

TIBCO iProcess® Web Services Server Plug-in Release Notes

9 | Changes in Functionality

Changes in Functionality
This section lists changes in functionality in the following releases of the product.

Release 11.9.0
No functionality changes have been made in this release of TIBCO iProcess® Web Services
Server Plug-in.

Release 11.8.0
No functionality changes are included in this release of iProcess® Web Services Server
Plug-in.

Release 11.3.0
The following change in functionality is included in this release:

New Version of Jetty

A new version of Jetty (6.1.25) is now used.

TIBCO iProcess® Web Services Server Plug-in Release Notes

10 | Deprecated Features

Deprecated Features
This section describes deprecated features in the following releases of the product 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.9.0
No features have been deprecated in this release of TIBCO iProcess® Web Services Server
Plug-in.

Release 11.8.0
The following features are deprecated or removed in this release of iProcess® Web
Services Server Plug-in.

Deprecated Features
Affected Description Deprecated
Component Release

Server Plug-in Version 11.8.0 uses the current version of Apache Rampart 11.8.0
that has a configuration model based on WS-Policy and
WS-Security Policy, so the Apache Rampart 1.0 style
configuration (using InflowSecurity and OutflowSecurity
parameters) is deprecated in this release.

Release 11.3.0
The following feature is removed in this release.
• Support for AXIS 1.

TIBCO iProcess® Web Services Server Plug-in Release Notes

11 | Migration and Compatibility

Migration and Compatibility

For migration information, and for information on the versions of software compatible
with this release, see TIBCO iProcess™ Web Services Server Plug-in Installation.

Note: 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 iProcess® Web Services Server Plug-in. The schemas,
iProcess procedures, and BusinessWorks processes can all be found in the examples
folder along with TIBCO iProcess Engine Web Services Server Plug-in product. The
examples provided with this version of the 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 iProcess® Web Services Server Plug-in.

TIBCO iProcess® Web Services Server Plug-in Release Notes

12 | Closed Issues

Closed Issues
The table in this section lists issues that were closed in the following releases.

Closed in MR # Summary
Release

11.9.0 IPWS-633 The log4j JAR file is upgraded to 2.17.2 version.

11.9.0 IPWS-629 When correlating items from the timeout queue,

SWTimedOutWorkHandlerService does not release QueueSession
it uses to view the SWInbound queue.

11.9.0 IPWS-628 A system is implemented to manually (within the plug-in) move

messages, which have been retried x times to the Poison queue.

11.9.0 IPWS-627 When an SQL Exception occurs, a JDBC connection can

sometimes become invalid in DB2.

11.8.1 IPWS-626 Addressed the Apache Log4J vulnerability (CVE-2021-44228).

11.8.0 IPWS-522 Resolve a problem with Database Connections becoming invalid

on DB2.

Implemented.

11.8.0 IPWS-521 Add the ability to internally manage moving retried messages to
a Poison queue rather than having the JMS Provider do it.

Implemented.

11.8.0 IPWS-517 Axis.SOAPTimeout configuration setting is not respected, so the

default cannot be modified.

Corrected.

11.8.0 IPWS-516 SWTimedOutWorkHandlerService can leave QueueSessions

open if there is more than one item in the SWTimeout queue.

TIBCO iProcess® Web Services Server Plug-in Release Notes

13 | Closed Issues

Closed in MR # Summary
Release

Corrected.

11.8.0 IPWS-495 When installing the TIBCO iProcess Web Services Plug-in as the
"pro" user, the installation fails and the installer displays an
error stating that you must be logged in as "root" to complete
the installation.

Corrected.

11.3.0 40380 Threading issues occasionally observed when using

Bouncycastle to decrypt.

Corrected.

11.3.0 43258 Accented characters may cause either a fatal error or corrupted
data when running the Web Services Plug-in.

Corrected.

11.3.0 43272 Outbound web service calls failed when using Weblogic 9.2
XML/JMS.

Corrected.

11.3.0 43182 Web service calls were processed slowly under certain
circumstances.

Corrected.

11.3.0 41590 A Web Services call fails if the data returned contains the <
character.

Corrected.

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.

Corrected.

TIBCO iProcess® Web Services Server Plug-in Release Notes

14 | Restrictions

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>

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.

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

TIBCO iProcess® Web Services Server Plug-in Release Notes

15 | Restrictions

MR # Summary/Workaround

Workaround None.

31511 Summary Because of the way the pooling model used by the 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.

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

TIBCO iProcess® Web Services Server Plug-in Release Notes

16 | Restrictions

MR # Summary/Workaround

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.

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

TIBCO iProcess® Web Services Server Plug-in Release Notes

17 | Restrictions

MR # Summary/Workaround

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.

27173 Summary There are three bindings displayed for calling iProcess Engine Web
Service operations:

TIBCO iProcess® Web Services Server Plug-in Release Notes

18 | Restrictions

MR # Summary/Workaround

• 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.

16757 Summary You can only install the 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.

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

TIBCO iProcess® Web Services Server Plug-in Release Notes

19 | Restrictions

MR # Summary/Workaround

method" error will be returned.

Workaround None.

No MR Summary If you install the 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

20 | Known Issues

Known Issues
This section lists known issues for the current version.

Exception Stating That MBean Is Not Compliant

During Jetty start if you receive the following message, you can ignore it.
javax.management.NotCompliantMBeanException: MBean is not compliant

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

21 | Known Issues

Scenario 1
1. Configure iProcess® Web Services Server Plug-in to call an external web service.
2. From the 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 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 iProcess® Web Services Server Plug-in's
inbound call.
2. From iProcess® Web Services Server Plug-in's, configure no security for inflow.
3. Configure authentication, signature, encryption and timestamp for outflow.
4. Specify that 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 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.

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

TIBCO iProcess® Web Services Server Plug-in Release Notes

22 | Known Issues

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 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.

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.

TIBCO iProcess® Web Services Server Plug-in Release Notes

23 | Known Issues

Process Migration Error Sometimes Occurs

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.

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 iProcess® Web Services Server Plug-in.

2. Register the iProcess® Web Services Server Plug-in correctly.
3. Start the TIBCO iProcess Engine.
4. Start 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.

TIBCO iProcess® Web Services Server Plug-in Release Notes

24 | Known Issues

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)

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.

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>

TIBCO iProcess® Web Services Server Plug-in Release Notes

25 | Known Issues

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

26 | Other Information

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

27 | TIBCO Documentation and Support Services

TIBCO Documentation and Support Services

For information about this product, you can read the documentation, contact TIBCO
Support, and join TIBCO Community.

How to Access TIBCO Documentation

Documentation for TIBCO products is available on the TIBCO Product Documentation
website, mainly in HTML and PDF formats.
The TIBCO Product Documentation website is updated frequently and is more current
than any other documentation included with the product.

Product-Specific Documentation
Documentation for TIBCO iProcess® Web Services Server Plug-in is available on the TIBCO
iProcess® Web Services Server Plug-in Product Documentation page.
To directly access documentation for this product, double-click the following file:
TIBCO_HOME is the top-level directory in which TIBCO products are installed. On Windows,
the default TIBCO_HOME is C:\tibco. On UNIX systems, the default TIBCO_HOME is
/opt/tibco.

The following documents for this product can be found in the TIBCO Documentation site:
l TIBCO iProcess Web Services Server Plug-in Release Notes
l TIBCO iProcess Web Services Server Plug-in Installation

How to Contact TIBCO Support

Get an overview of TIBCO Support. You can contact TIBCO Support in the following ways:
l For accessing the Support Knowledge Base and getting personalized content about
products you are interested in, visit the TIBCO Support website.
l For creating a Support case, you must have a valid maintenance or support contract
with TIBCO. You also need a user name and password to log in to TIBCO Support
website. If you do not have a user name, you can request one by clicking Register
on the website.

TIBCO iProcess® Web Services Server Plug-in Release Notes

28 | TIBCO Documentation and Support Services

How to Join TIBCO Community

TIBCO Community is the official channel for TIBCO customers, partners, and employee
subject matter experts to share and access their collective experience. TIBCO Community
offers access to Q&A forums, product wikis, and best practices. It also offers access to
extensions, adapters, solution accelerators, and tools that extend and enable customers to
gain full value from TIBCO products. In addition, users can submit and vote on feature
requests from within the TIBCO Ideas Portal. For a free registration, go to
TIBCO Community.

TIBCO iProcess® Web Services Server Plug-in Release Notes

29 | Legal and Third-Party Notices

Legal and Third-Party Notices

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 FILE) 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 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.

TIBCO, the TIBCO logo, the TIBCO O logo, ActiveMatrix BusinessWorks, Administrator, TIBCO
Business Studio, Designer, Enterprise Message Service, Hawk, iProcess, Rendezvous, Runtime Agent,
and SmartSockets are either registered trademarks or trademarks of TIBCO Software Inc. in the
United States and/or other countries.

Java and all Java based trademarks and logos are trademarks or registered trademarks of Oracle
Corporation and/or its affiliates.

This document includes fonts that are licensed under the SIL Open Font License, Version 1.1, which
is available at: https://scripts.sil.org/OFL
Copyright (c) Paul D. Hunt, with Reserved Font Name Source Sans Pro and Source Code Pro.

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. See the readme file for the
availability of this software version on a specific operating system platform.

TIBCO iProcess® Web Services Server Plug-in Release Notes

30 | Legal and Third-Party Notices

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.

This and other products of TIBCO Software Inc. may be covered by registered patents. Please refer
to TIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.
Copyright © 2003-2022. TIBCO Software Inc. All Rights Reserved.

TIBCO iProcess® Web Services Server Plug-in Release Notes