TIBCO ActiveMatrix BusinessWorks Release Notes ™

TIBCO ActiveMatrix BusinessWorks Release Notes ™
TIBCO ActiveMatrix BusinessWorks™ Release
Notes
Software Release 6.3.1
January 2016
Two-Second Advantage®
2
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 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 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.
TIBCO, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Enterprise Message Service,
TIBCO Business Studio, TIBCO Enterprise Administrator, TIBCO ActiveSpaces, TIBCO Runtime Agent,
TIBCO Designer, and Two-Second Advantage are either registered trademarks or trademarks of TIBCO
Software Inc. in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise
Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle Corporation in the U.S. and 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. SEE THE README 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 © 2001-2016 TIBCO Software Inc. All rights reserved.
TIBCO Software Inc. Confidential Information
TIBCO ActiveMatrix BusinessWorks™ Release Notes
3
Contents
Setting Context Sensitive Help Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
TIBCO ActiveMatrix BusinessWorks™ Release Notes
4
Setting Context Sensitive Help Preferences
This procedure explains how to change your help preferences in TIBCO Business Studio™ to access
context sensitive help from a local directory or from an internal web server, if you have placed the
documents under it.
Prerequisites
Before setting context help preferences you must download the documentation for your product from
the FTP site provided by your TIBCO representative. Copy the documentation zip file to a local
directory, or to an internal web server and then unzip the file.
Procedure
1. In TIBCO Business Studio, click Window > Preferences. On Mac OS X, click TIBCO Business
Studio > Preferences.
2. In the Preferences dialog, click BusinessWorks > Help.
3. Select Custom Location and then click Browse to select the html directory where you unzipped the
documentation, or provide the URL to the html directory on your internal web server.
4. Click Apply and then click OK.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
5
New Features
Here are the new features available in this release (6.3.x) of TIBCO ActiveMatrix BusinessWorks.
Release 6.3.1
Common Features
Support for Java Runtime Environment (JRE) 8
JRE has been upgraded for Business Studio,
Core Runtime and all the tools for
Administration.
Runtime Administration Framework
Unshared State Failover (UFO) support in JMS
This feature introduces a new check-box to
indicate the usage of Unshared State Failover in
JMS. This check-box appears only when the
option Direct is used in the Connection Factory
Type field. When using the unshared failover
setup, if a connection loss is detected on Server
(A), BusinessWorks will try to connect to Server
(B) as defined in the connection factory
configuration.
After enabling the check-box, you can pass the
provider URL in the form of UFO. For example,
tcp://serverA:7222+tcp://serverB:7222,
where Server A and Server B are two EMS
servers configured for sharing the Unshared
State Failover.
Release 6.3.0
Design-time
REST Consumption Improvements
With this release, we have introduced support
for REST reference bindings using Swagger
specifications. The path and query parameters
are fetched from the Swagger document.
Path parameter names and query
parameter names must be unique in a
resource service path.
If the Request Format for a REST
Binding is Form, the parameter name
must be different from all element
names in the referenced schema.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
6
Design-time
Business Studio upgraded to Eclipse 4.4.1.
TIBCO Business Studio now uses Eclipse 4.4.1 as
the underlying platform for design-time. This
brings significant improvements in user
experience and performance. In addition, from a
compatibility point of view, the upgrade also
provides better support for other plug-ins that
are used with Eclipse.
Support for Error Transitions for all activities
and groups.
Error transitions can now be created between
two activities, or a group and an activity.
Support for implementing selective operations
for a given port type.
Users can now choose to implement only a select
set of operations for given port type as part of
their process design.
Runtime Administration Framework
Swagger support upgraded from 1.2 to 2.0
specification.
BusinessWorks generates Swagger 2.0
specification as a standard for documenting
RESTful services. The associated Swagger UI has
also been upgraded to support the 2.0
specification.
Users can now create and consume RESTful
services defined using Swagger 1.2 and 2.0
specifications.
Ability to provide the prefix to be appended to
the appNode process (name).
The required prefix can be appended to the
appNode process (name) by setting the
environment variable bw_appnode_pid_prefix to
the desired value.
Support for Microsoft SQL server and TIBCO
Enterprise Messaging Server (EMS) for data
persistence and transport.
bwagent can now be configured to use Microsoft
SQL server and TIBCO Enterprise Messaging
Server (EMS) for data persistence and transport.
For additional details, refer to the section
"Configuring bwagent for Microsoft SQL Server
and TIBCO Enterprise Message Service" in the
Administration guide.
Ability to enable the governance agent on the
AppNode to ensure security is enforced on
ActiveMatrix BusinessWorks 6.x applications
deployed with policies.
To enable the governance agent, set the property
bw.governance.enabled to true. You can
modify this property in the AppNode settings
through the Admin UI, or in the AppSpace
template file, appspace_config.ini_ template,
located in <BW_HOME>\config\.
Job data is available in the main process though
the execution was suspended by the sub process.
In Business Studio, when a sub-process
suspends a main process, the job data can be
viewed in the main process.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
7
Release 6.2.2
Design Time
Ability to enforce security policies on new and
existing ActiveMatrix BusinessWorks 6.x
applications in Business Studio.
In Business Studio, you can create and manage
policies and related resources. In addition, you
can enforce security on ActiveMatrix
BusinessWorks 6.x applications by associating
policies with activities and bindings in
application processes.
Runtime Administration Framework
Ability to enable the governance agent on the
AppNode to ensure security is enforced on
ActiveMatrix BusinessWorks 6.x applications
deployed with policies.
To enable the governance agent, set the property
bw.governance.enabled to true. You can
modify this property in the AppNode settings
through the Admin UI, or in the AppSpace
template file, appspace_config.ini_ template,
located in <BW_HOME>\config\.
Release 6.2.1
Runtime Administration Framework
Ability to enable or disable process statistics
collection from the Admin CLI.
You can enable or disable process statistics
collection for an application from the Admin CLI
using the following commands:
●
enablestats
●
disablestats
See Process Statistics for details.
Improved Administrator user interface
A number of visual cues and aesthetic
enhancements to the Administrator UI have
been made including improvements to the
Process Viewer.
GET operation to obtain AppSpace configuration
The bwagent REST API now provides a GET
operation to obtain the AppSpace configuration.
Design-time
Improved wizard to create subprocesses
The wizard to create subprocesses has been
improved to create subprocesses with inline
schema and WSDL files. The wizard has also
been improved to make it easy to use and
consistent with the approach to create processes.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
8
Design-time
Swagger UI and Swagger Specification support
for Basic Authentication
The Swagger UI supports the use of endpoints
configured with Basic Authentication. The
Swagger UI has two new fields, User Name and
Password, which are always visible.
Basic Authentication support for REST Binding
and Invoke REST API activity
The REST Service Binding and the Invoke REST
API activity support Basic Authentication.
The REST Service Binding can be configured
using a check box in the Binding Configuration.
When the check box is selected, the REST
Binding uses the LDAP Shared Resource
configured on its HTTP Connector to perform
Basic Authentication.
The Invoke REST API activity automatically
adds the authorization header with the user
credentials if an Identity shared resource is
configured on the HTTP Client shared resource.
See REST Binding for details.
SSL Client and SSL Server resources default the
keystore implementation to JRE's certificate store
The SSL Client and SSL Server resources default
the trust keystore configuration to JRE's cacerts.
This eliminates the need to create trust stores
from default.
HTTP Authentication support for SOAP Binding
A new HTTP Authentication check box has been
introduced. When selected, specifies that the
Service Request sent by the Service Consumer
must be authenticated. Authentication is
successful, if the user name and password
specified in the Service Request exists in the
LDAP server configured on HTTP Connector.
Enhancements to JDBC activities
●
JDBC activities now support ThreadPool
shared resources that you can use to limit
thread creation.
●
JDBC activities now expose Activity Timeout
with a default value of 3 minutes. When the
timeout value is reached, the engine cancels
the activity and throws an ActivityTimedout
exception.
See JDBC Palette for details.
Samples and Scripts
New script, bw6env.sh, to print the environment
variable configurations
The script, bw6env.sh, prints the required and
optional environment variable configurations on
the screen. This script is available under the
<TIBCO_HOME>/bw/6.2/scripts/admin folder.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
9
Release 6.2.0
Runtime Administration Framework
bwagent supports an external datastore for
communication and TIBCO Enterprise Message
Server (EMS) for persistence
The bwagent now supports an external datastore
(PostgreSQL or MySQL) and TIBCO EMS for
persistence and communication in addition to
TIBCO ActiveSpaces. See Administrator and
Agent -> bwagent -> Configuring bwagent in the
Administration guide for details.
bwagent configuration
Two JSON files are provided for bwagent
configuration: bwagent_as.json and
bwagent_db.json. You can use the bwadmin
config command with one of these JSON files to
configure the bwagent.
See Administrator and Agent -> bwagent ->
Configuring bwagent -> ActiveSpaces
Configuration for bwagent and Administrator
and Agent -> bwagent -> Configuring bwagent > Database/EMS Configuration for bwagent in
the Administration guide for details.
bwadmin commands for viewing agent and
engine information
Remote AppNode debugging from TIBCO
Business Studio
There are new bwadmin commands for viewing
agent and engine information:
●
The show agentprocessinfo command
shows info about the agent.
●
The show bwengine command shows info
about the engine on an AppNode.
●
The bwenginedb command shows info about
the engine database.
You can debug a remote AppNode from TIBCO
Business Studio. To do so, select the AppNode in
the Deploy view and click the enable debug icon
in the Properties view before launching the
debugger.
See Deploying an Application -> Using the
Debugger -> Remote Debugging in the
Application Development guide for details.
Remote AppNode debugging enabled using the
bwadmin command or from the Admin UI
You can enable remote debugging for an
AppNode using the bwadmin command or from
the Admin UI. This is useful in secure
environments where only an administrator has
the access rights to enable or disable ports.
See Administration Tasks and Reference ->
Managing AppNodes -> Debugging an
AppNode in the Administration guide for details.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
10
Runtime Administration Framework
Application activity execution statistics and
process execution statistics collection
You can collect application activity execution
statistics and process execution statistics and
display the results as a text file, an HTML file, or
write to a database. See Logging -> AppNode
Logging -> Statistics Collection in the
Administration guide for details.
Domain backup and deletion in the Admin UI
The following operations are available on the
Domain Management page in the Admin UI:
View process diagrams in the Admin UI
●
Backing up and restoring an domain. See
Administration Tasks and Reference ->
Managing Domains -> Backing Up and
Restoring a Domain in the Administration
guide for details.
●
Deleting a domain. See Administration Tasks
and Reference -> Managing Domains ->
Deleting Domains in the Administration guide
for details.
From the Application page in the Admin UI for
a running application, you can view the
endpoints, components, and processes for a
running application. Furthermore, you can view
the process diagrams provided the application
archive file was generated using the current
version of the product.
See Administration Tasks and Reference ->
Managing an Application -> Viewing Endpoints,
Components, and Processes in the Administration
guide for details.
REST Doc URL in the Admin UI
From the Application page in the Admin UI for
a running application, you can view the REST
Doc URL for applications using REST services.
The links open the REST UI page where you can
test out the operations. See Administration Tasks
and Reference -> Managing an Application ->
Viewing Running Applications in the
Administration guide for details.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
11
Runtime Administration Framework
Unified Doc URL configuration
Documentation for all applications in an
AppSpace using REST services are now
available on a single REST Doc URL. See
Administration Tasks and Reference ->
Managing an Application -> Viewing Endpoints,
Components, and Processes -> Configuring a
Unified Doc URL in the Administration guide for
details.
Application properties and application instance
properties editing in the Admin UI
Application properties and application instance
properties can be edited from the Admin UI. See
Administration Tasks and Reference ->
Managing an Application -> Editing Application
and Application Instance Properties in the
Administration guide for details.
Application profile download from the Admin
UI
Application profiles can now be downloaded
from the Admin UI. This is the same as
exporting an application profile on the
command line using the bwadmin export
command. See Administration Tasks and
Reference -> Managing an Application -> Editing
Application and Application Instance Properties
-> Exporting an Application Profile in the
Administration guide for details.
AppSpace or AppNode configuration update
from the Admin UI
The AppSpace or AppNode configurations can
be viewed and updated from the Admin UI.
Updates to the AppSpace configuration made
from the Admin UI are applied to all the
AppNodes contained in that AppSpace. This is
the same as running the bwadmin config
command on the command line to update the
AppSpace or AppNode configurations.
See Administration Tasks and Reference ->
Managing AppSpaces -> Editing an AppSpace
Configuration and Administration Tasks and
Reference -> Managing AppNodes -> Editing an
AppNode Configuration in the Administration
guide for details.
Ability to iterate through a list of items in Level
2 entities in the Admin UI
You can now iterate through a list of items in
Level 2 entities (next and previous) in the Admin
UI. See Admin UI tasks in the "Administration
Tasks and Reference" section in the
Administration guide.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
12
Design-time
Compensation Handlers and Compensate
activity
Every scope can define a compensation handler,
which contains logic that gets executed to revert
the logic of the scope. A compensation handler
can be executed only if the scope that is belong
to has been successfully executed. A
compensation handler can be triggered in the
following ways:
●
implicitly, by an uncaught fault that is
thrown downstream in the process.
●
explicitly, by using the Compensate activity.
FTL Palette
The FTL palette allows ActiveMatrix
BusinessWorks applications to send and receive
®
messages using TIBCO FTL . See FTL Palette in
the Bindings and Palettes Reference guide for
details.
Inspector Activity
The Inspector activity is used to write the output
of any or all activities and module properties to
a file and/or standard output. This activity is
particularly useful to debug processes. See
Inspector in the Bindings and Palettes Reference
guide for details.
Deploy an application from TIBCO Business
Studio
You can deploy an application to an AppSpace
from TIBCO Business Studio. See Deploying an
Application in the Application Development guide
for details. For restrictions, refer to Known
Issues section in the Release Notes.
Generate ActiveMatrix BusinessWorks processes
in SVG format when generating archive file
When creating an archive file for an application,
the application packager also generates the
ActiveMatrix BusinessWorks processes in SVG
format, which can be rendered in the Admin UI.
When you deploy this archive file and start the
application, you can view the process diagrams
for the processes from the Applications page in
the Admin UI.
Support for partial responses in REST
Partial responses in REST helps the user to
request only those fields which are required as
part of response. See REST Binding in Bindings
and Palettes Reference guide for details.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
13
Design-time
Support for refactoring XSD schema and WSDL
entities
A new refactoring tool for renaming entities is
available as part of the Project Explorer menu.
When you right-click on a particular entity, if
that entity supports refactoring, a new Refactor
menu containing the refactoring tools that are
appropriate and available for that entity is
displayed. For example, when you right-click on
an XML Schema, the Refactor menu item lists a
Rename XSD Schema Namespace refactoring
tool.
Eclipse p2 installation for ActiveMatrix
BusinessWorks Plugins
ActiveMatrix BusinessWorks plugins can now
be installed from TIBCO Business Studio using
the Help > Install New Software menu. The
Eclipse p2 installation packages for the plugins
must be downloaded and made available on an
update site or directory beforehand. See
Installing TIBCO ActiveMatrix BusinessWorks
Plug-ins in the Installation guide for details.
Samples and Scripts
Core admin scripts support database/EMS
configuration
The core admin scripts now support the
bwagent configuration for PostgreSQL database
with TIBCO Enterprise Message Service.
New admin script to create a fault tolerant group
with cross-engine persistence.
A new admin script,
configureBWEngineGroup.sh,
to create a faulttolerant group with cross-engine persistence is
available. This script can be used the bwagent is
configured for TIBCO ActiveSpaces.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
14
Changes in Functionality
The following are the notable changes in functionality in this release (6.3.x).
Release 6.3.1
There are no changes in functionality in the version 6.3.1 of TIBCO ActiveMatrix BusinessWorks.
Release 6.3.0
Design-time
An error message is displayed if user attempts to
add a circular dependency.
When a Shared Module or a Service Descriptor
is added as a dependency to a separate Shared
Module that is already dependent on it, a
message is displayed warning the user that a
dependency loop will be created.
Module properties and Process Properties can
now be selected for the Schema and Catalog or
Package fields in the JDBC Call Procedure
activity.
Configure the Schema field to use a Process
Property or a Module Property if a schema has
been defined for the project, and you know the
schema name. To search for a schema, configure
the field to use a Literal Value, and click the
Browse button to select a schema from the
database that is using the specified JDBC
Connection.
Runtime Administration Framework
The existing statistics functionality has been
updated to pass the optional arguments
processname and activityname.
Optionally, to retrieve statistics for a particular
processname or activityname use the arguments
-bp or -ba, respectively.
If not provided, statistics for all processes and
activities will be retrieved
TIBCO ActiveMatrix BusinessWorks™ Release Notes
15
Release 6.2.2
Migration
Backwards compatiblity is disabled by default
for ActiveMatrix BusinessWorks 6.x applications
using TIBCO ActiveMatrix Policy Director 2.0 to
enforce security policies.
To reduce overhead when messages are
consumed, backwards compatibility is disabled
by default for ActiveMatrix BusinessWorks 6.x
applications using TIBCO ActiveMatrix Policy
Director 2.0.
To enable backwards compatibility, add the
property
bw.governance.pd.compatibility.mode=true
to the existing AppSpace configuration file
appspace_config.ini (located in the root of the
AppSpace folder), or the AppSpace
configuration template file,
appspace_config.ini_ template, located in
<BW_HOME>\config\.
Refer to "Applying Security Policies" in the
TIBCO ActiveMatrix BusinessWorks
Administration guide for instructions.
The Authentication check box on service side
activities and bindings was removed.
If the Authentication check box was selected on
activities or bindings that supported
authentication in TIBCO ActiveMatrix
BusinessWorks 6.2.1 or older, the
Authentication check box continues to display
and authentication remains enforced on the
activity or the binding.
If you clear the Authentication check box, a
warning message is displayed prompting you
for confirmation. Clicking OK causes the
Authentication check box to no longer display
and removes authentication from the activity or
the binding. To reapply authentication, associate
the Basic Authentication policy with the activity
or the binding.
Refer to the TIBCO ActiveMatrix BusinessWorks
Bindings and Palettes guide for additional details.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
16
Release 6.2.1
Runtime Administration Framework
The TEA Shell implementation of the backup
command has been updated to support the
creation of a zip archive only.
The backup command only supports the
creation of a zip archive. The -z option for the
backup command to create a zip archive is
obsolete.
If the argument '-s destination' is an existing
folder, you can choose a name.zip for the zip
archive. If the .zip qualifier is missing, the
command adds the qualifier to the archive
created.
The alias for path argument in the TEA Shell
command has been changed from '-p' to
'-pa'.
deploy
The alias for path argument in the TEA Shell
command has been changed to '-pa' to
avoid ambiguity with the '-p' alias for the
profileName argument.
deploy
Design-time
JDBC Query activity does not fetch the table
metadata to construct the Output schema
automatically.
The JDBC Query activity automatically fetched
the table metadata to construct the Output
schema based on the SQL query. This behavior
has been changed. Every time you want to
configure the JDBC Query activity, you must
fetch the table metadata manually using the
Fetch button. The new behavior is similar to the
behavior in TIBCO ActiveMatrix BusinessWorks
5.x version.
Release 6.2.0
Runtime Administration Framework
Changes in the file system location for the
default \domains folder
The default folder (domains) used to store
runtime artifacts in the file system used to be
located at TIBCO_HOME/bw/domains. This folder
is now located at folder.
You can change the location of the default folder
used to store the runtime artifacts by updating
the defaultdomain.domainHome property in the
TIBCO_HOME/bw/6.2/domains/
file. See section
Configuring the Location of the Default
Domains Folder in the Administration guide for
details.
DomainHomes.properties
TIBCO ActiveMatrix BusinessWorks™ Release Notes
17
Runtime Administration Framework
Changes to the OSGi commands
The OSGi commands have changed. For the full
list of commands, see Managing AppNodes ->
Enabling the OSGi Console for an AppNode ->
OSGi Runtime Statistics Commands in the
Administration guide.
Changes to the TIBCO Hawk MicroAgent
method names
The TIBCO Hawk MicroAgent method names
have changed. For the full list of methods, see
Monitoring using TIBCO Hawk -> TIBCO Hawk
MicroAgent Methods in the Administration
guide.
Archive paths in a backup archive are now
relative within the archive
When a backup is created as an archive file, the
archive file is generated as
<entity>_<name>.zip and contains relative
paths. The destination argument can be an
existing folder, or if the specified ends with a
forward-slash ('/') , a folder will be created (if it
does not exist already).
Persistent application state
Previously, applications did not retain their state
after an AppNode was restarted. This behavior
has changed and applications now retain their
state when an AppNode is restarted.
Samples and Scripts
Changes in the file system location
The core admin scripts are now available under
the BW_HOME/samples/core/admin folder. See
Core Admin Scripts in the Administration guide
for details.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
18
Samples and Scripts
Changes to the location of the admin scripts
shipped with the product
Previously, all the admin scripts were installed
under a single directory, BW_HOME/samples/
core/admin.
These scripts are now separated into two sets
and are installed under the following directories:
●
Sample scripts located at BW_HOME/samples/
core/admin.
●
Generic scripts located at BW_HOME/scripts/
admin.
As a consequence of this separation, the sample
scripts now rely on the PATH variable to find
the generic scripts available under BW_HOME/
scripts/admin.
The script, BW_HOME/scripts/bashrc.sh,
containing the environment variables is autogenerated after installation. To set the
environment variables required to run the
admin scripts, add the following statement to
your ~/.bashrc file to source the generated
script:
source
BW_HOME/scripts/bashrc.sh
TIBCO ActiveMatrix BusinessWorks™ Release Notes
19
Closed Issues
The following are the closed issues for the 6.3.x releases of TIBCO ActiveMatrix BusinessWorks.
The closed issues are grouped by components:
●
Administration
●
Bindings
●
General
●
Migration
●
Palettes
●
Policies
Administration
Release 6.3.1
Key
Description
AMBW-21654
Prior to 6.2.2 HF-004, users required AppArchive permission to upload archive
files and AppSpace permission to deploy an archive file. Now, users only
require AppArchive permissions to upload and deploy archive files.
AMBW-21653
The field diagramConfig was not available in the Oracle, Postgres and MySQL
database when the bash scripts under <BW_HOME>\scripts\admin were used.
Release 6.3.0
Key
Description
AMBW-20931
bwagent could not connect to the EMS server with authorization enabled with
obfuscated passwords.
AMBW-20890
The command mentioned to create an AppNode using bwadmin did not work
as documented.
AMBW-20885
If bwagent was configured to use an external database and EMS for transport
and persistence, an exception error was thrown while updating the application
module properties.
AMBW-20567
A large number of temporary queues were being created, but were not being
cleaned up when bwagent was configured to use an external database and EMS
for persistence and transport.
AMBW-20539
bwagent could not be configured to use SSL when connecting to an EMS server.
AMBW-20536
bwagent could not be started when the drivername was
oracle.jdbc.OracleDriver.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
20
Key
Description
AMBW-20318
After TIBCO ActiveMatrix BusinessWorks 6.2.2 Hotfix 1 was installed, the error
TIBCO-BW-TEAAGENT-500201: Domain [Domain_Name] is not present was
thrown when users tried to access an existing domain through the Admin UI.
AMBW-20159
The password parameter for EMS could not be updated in the
file with the key emsuserpassword.
bwagent_db.json
AMBW-19956
The bwadmin config command did not correctly update the
bw.agent.technology.as.remoteDiscoveryURL field in the bwagent
configuration file.
AMBW-19389
After upgrading from TIBCO ActiveMatrix BusinessWorks 6.2.1 to the newest
version, AppNodes did not automatically start after restarting the AppSpace.
AMBW-19751
If a large ear file was uploaded, or if multiple large ear files were uploaded
simultaneously through the Admin UI, the upload failed, and the error
java.lang. OutOfMemoryError: Java heap space was thrown.
AMBW-19749
If the EMS server is restarted in DB/EMS mode, bwagent also needed to be
restarted if it was configured to use an external database and EMS for
persistence and transport.
AMBW-18567
When a user deployed an application with a modified profile file, the deploy
command failed and an error was thrown.
AMBW-18448
The latest version of an application was not processed during the application
startup, and the status was displayed as Degraded in the Admin UI.
Release 6.2.2
Key
Description
AMBW-19397
If an uploaded profile has non-ASCII characters in the EAR file name, a Null
Pointer Exception error was thrown when a user attempted to download the
profile.
AMBW-14493
System module properties could be edited in the Admin UI.
Release 6.2.1
Key
AMBW-18292
Description
The backupDomains.sh and restoreDomains.sh scripts now support the parameter.
network
AMBW-18140
The bwadmin-logback and bwagent-logback files under /bw/6.2/bin now
contain the code required to append the date in the log files.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
21
Key
Description
AMBW-18097
The log file size and rotation for the bwappnode are now configurable. Edit the
logback.xml file to replace the existing appender with the following:
<appender name="FILE"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>../log/bwappnode.log</file>
<rollingPolicy
class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
<fileNamePattern>../log/bwappnode%i.log</fileNamePattern>
<minIndex>1</minIndex>
<maxIndex>10</maxIndex>
</rollingPolicy>
<triggeringPolicy
class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<maxFileSize>10MB</maxFileSize>
</triggeringPolicy>
<encoder>
<pattern>%d
{yyyy-MM-dd HH:mm:ss.SSS}
%-5level [%thread] %logger
{36}
- %msg%n</pattern>
</encoder>
</appender>
AMBW-17829
If a node crashed for some reason, the ActiveMatrix BusinessWorks engine was
unable to resume when checkpointing was used. This has been fixed.
AMBW-17828
Checkpointing created many locks at the database. In some cases, it escalated
and created many cascade locks which affected the performance. This has been
fixed.
AMBW-17719
The command bwadmin mode did not work after TIBCO ActiveMatrix
BusinessWorks 6.2.0 hotfix02 was installed. This has been fixed.
AMBW-17631
Starting appnode from command line failed with timed out error if the TIBCO
HOME contained space.
AMBW-17424
The '-p' alias for path argument in the TEA Shell deploy command has been
changed to '-pa' to avoid ambiguity with the '-p' alias for profileName argument.
AMBW-17373
The backup script was using the -version argument to back up AppSpaces. The
backup script for ActiveMatrix BusinessWorks 6.2.1 no longer uses this
argument.
AMBW-17321
The TEA shell implementation of the backup command has been improved.
The backup command only supports the creation of a zip archive. The -z option
to create a zip archive is obsolete. If the argument '-s destination' is an existing
folder, you can choose a name.zip for the zip archive. If the .zip qualifier is
missing, the command adds the qualifier to the archive created.
AMBW-17313
A backup of an AppSpace or domain now contains the TRA files of the
AppSpace (organized by agent name) and AppNodes (organized by AppSpace).
AMBW-17275
The status of an AppSpace without any AppNodes now report its status as
degraded, regardless of the start/stop/create operation.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
22
Key
Description
AMBW-16950
The create appnode command with -r or -lax options does not work when
run in a separate session of bwadmin. This has been fixed.
AMBW-16657
The -na or -noarchives options were ignored by the backup command from
TEA shell. As a result, the archives and applications were backed up even when
you ran the backup command with option-na (or -noarchives) from the TEA
shell. This has been fixed.
Release 6.2.0
Key
Description
AMBW-16775
On Microsoft Windows, an exception (Failed to write config file) was
thrown when configuring an AppNode if the config.ini file was not written
using UTF-8 encoding.
AMBW-14868
After deleting an AppSpace from the AppSpace level 2 page, the first operation
to delete (or create) an AppSpace in the AppSpace level 1 page was hanging.
AMBW-12126
Applications did not retain their state when an AppNode was restarted.
AMBW-8481
On Microsoft Windows, the bwagent listen port was not released when a process
was killed. As a result, when the bwappNodes were launched again by the
bwagent, the process continued to run.
Bindings
Release 6.3.1
Key
Description
AMBW-21786
The HTTP transport property header Set-Cookie was not available in SOAP
Reference binding.
AMBW-21723
When the element used to configure the REST service was a long, float, or double
type Number, incorrect datatypes were represented in the generated Swagger API
document.
AMBW-21647
If an Invoke activity timed out in an application configured to use SOAP/JMS
binding, JMS Resources were not released and a memory leak was observed.
AMBW-21422
If SOAP services contained complex unbound headers and multiple bindings,
SOAP headers were duplicated in the request message, which caused run time
fault generation.
AMBW-20757
The Render JSON activity incorrectly converted empty string values to Null
values. Empty string values are now properly converted to empty string("").
Release 6.3.0
TIBCO ActiveMatrix BusinessWorks™ Release Notes
23
Key
Description
AMBW-20231
Adding a new REST Service removed the custom HTTP header from the REST
schema.
AMBW-19998
If an external SOAP reference binding was configured to use a concrete WSDL
from a shared module, an error was thrown when trying to start the process.
AMBW-19915
When a SOAP/JMS request reply application was running, temporary queues were
not deleted after a response was successfully returned.
AMBW-19750
Due to an incomplete refactoring of the process service, binding validation errors
were not displayed in Business Studio. After the service was run, an exception was
thrown.
AMBW-19717
WSDLs from shared modules could not be used to configure an "Unbound Header"
for a service in the application module.
AMBW-19695
When a HTTP Client resource was configured with the Apache Commons
implementation library, the Basic Credential Mapping policy did not work for
SOAP Reference Binding and HTTP Activities.
AMBW-19612
If the Concrete WSDL referred to a schema that contained a complex type and an
element that were using the same name, only one of these was included in the
Concrete WSDL.
AMBW-19139
Service Reply did not propagate the CorrelationId present in the Service Request.
AMBW-19099
The Reply Fault activity faulted with the exception Reply
activity was unable
to send reply using partner link.
AMBW-19089
AMBW-18784
SOAP Service binding now exposes the remote address header value in the request
context.
The SOAP response from SOAP server (MFT) failed with the Cannot
find XML
data type: {http://schemas.xmlsoap.org/soap/encoding/}string
error.
AMBW-18232
Response context did not display the response code.
AMBW-18170
If a SOAP request is not well formed, the validation exception can now be caught at
the process level.
Release 6.2.2
Key
Description
AMBW-19523
WSDL generation for SOAP and JMS binding failed when module properties were
used in JMS Connection shared resources in the shared module.
AMBW-19320
A ClassCast exception was thrown when processing a SOAP request. This has been
fixed.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
24
Key
Description
AMBW-19152
The HTTP bindings were unable to handle flow control requests. This has been
fixed.
AMBW-19139
The SOAP/JMS service response did not propagate the JMS CorrelationId that was
present in the service request. This has been fixed.
AMBW-18657
When using Policy Director, the security context set after authentication in HTTP
can now be propagated to SOAP binding and a credential mapping policy can use
it for outbound requests.
AMBW-18543
Design time errors and run time errors were not thrown after you clicked Fetch.
AMBW-18517
The Invoke activity always timed out after 30 second irrespective of the value
specified in the Invocation Timeout field of the Invoke activity. This has been fixed.
AMBW-13999
Deleting a REST Component resulted in a permanent loss of the Bindings.
AMBW-4297
JDBC Activities did throw exceptions when unsupported queries were entered.
Release 6.2.1
Key
Description
AMBW-18076
Creating schema as part of creating REST Resource led to REST Service binding
configuration error.
AMBW-18059
When a service with no input was invoked using TIBCO ActiveMatrix
BusinessWorks 6.2, the SOAP request was sent as Document/Literal even though
RPC/Literal was used.
AMBW-18050
A 404 Not Found error was encountered if base path name is same in the Path
parameter and Query parameter in the Resource Service Path field. For example,
REST Resource having Resource Service Path as /books/{isbn} or /books?
isbn={isbn} in a project which already has resource with path as /books, threw
an error.
AMBW-17932
QName picker did not display "xsd:included" components.
AMBW-17804
Concrete WSDL could not be generated for SOAP Service binding if the associated
HTTP Connector shared resource was defined in a shared module, and had fields
that referenced module properties.
AMBW-17581
SOAP client using HTTP Client shared resource did not use the specified proxy
configuration to access the web service.
AMBW-17025
MTOM did not work where the root node of WSDL message's part was of "type"
base64binary.
AMBW-11965
REST Bindings tab values were not serialized correctly if they were edited from
Bindings tab of the REST service on the process.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
25
Key
Description
AMBW-17696
The generated concrete WSDL did not contain elements from the schema that was
defined in a shared module. As a result, some elements were reported to be
missing when this concrete WSDL was imported in a client.
AMBW-17427
The [Copy Of]option could not be used to map the output of the Mapper activity
to invoke a web service.
AMBW-17156
An error was thrown when the SOAP response received from a SOAP service
contained an incorrect namespace declaration.
AMBW-17090
The exported concrete WSDL did not include the schemas even when the "EMBED
SCHEMA" option was selected during export.
AMBW-16625
Refactoring the dependent WSDL namespace caused a TIBCO-BW-BINDINGSOAP-500020: Failed to initialize SoapServiceBinding error.
AMBW-16552
[17495]
A SOAP client can now directly send a request to an ActiveMatrix BusinessWorks
service with a WSS username token header. If the governance agent is enabled, it
enforces the policy.
AMBW-16317
REST services bypassed HTTP Basic Authentication even after LDAP
Configuration was provided on HTTP Connector shared resource. It did not
authenticate against the credentials.
AMBW-15931
When sending a REST request to invoke a REST resource using the Invoke REST
API activity, the authorization header was not added to the request.
Release 6.2.0
Key
Description
AMBW-16218
When using an inline WSDL schema for REST service, a TIBCO-BW-BINDINGREST-500008: Error Occurred while creating User Part. Responding to
client with error message.
exception was thrown at run time.
AMBW-14834
An error was thrown by the SOAP service if the SOAP address location contained
a question mark character ("?").
AMBW-14694
Model/Model Schema in Swagger UI did not show anonymous complex type
elements which refer to another anonymous complex type.
AMBW-13807
REST Service Binding and Swagger UI did not support Optional Query
Parameters at runtime even if they were defined as optional at design time.
AMBW-11344
When you moved a process from a shared module into an application module
using Drag and Drop mechanism, the application that contained the application
module was not updated to contain the shared module.
AMBW-14678
Service names, reference names, and binding names now support the use of Latin
extended and CJK characters.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
26
General
Release 6.3.1
Key
Description
AMBW-21937
When an application was deployed from Business Studio using the Deployment
servers option, deployment failed with an exception.
AMBW-21871
Applications did not start properly when Managed Fault Tolerance was
configured at the AppSpace level to use an external database and TIBCO
Enterprise Messaging Service for data persistence and transport. This has been
fixed. To recreate the database, use the updated database scripts at
<TIBCO_HOME>\bw\6.3\config\dbscripts\engine. For example, if you are
using an Oracle database, execute the updated database scripts at
<TIBCO_HOME>\bw\6.3\config\dbscripts\engine\oracle.
AMBW-21870
Corrected a race condition that under certain circumstances could cause a false
validation failure in the Parse XML activity.
AMBW-21868
When sending email with attachment failed, the Send Mail activity did not
release the lock on the file that was specified as the attachment.
AMBW-21847
Duplicate references forced the cache to require schema locations where they
were not needed. So, duplicate references to documents in the document cache
are no longer created.
AMBW-21806
Duplicate references forced the cache to require schema location attributes
where they were not needed. So, duplicate references to documents in the
document cache are no longer created.
AMBW-21649
Managed fault tolerance did not work if a schema used in an application
process did not have a targetnamespace. This has been fixed. To recreate the
database, use the updated database scripts at <TIBCO_HOME>\bw\6.3\config
\dbscripts\engine. For example, if you are using an Oracle database, execute
the updated database scripts at <TIBCO_HOME>\bw\6.3\config\dbscripts
\engine\oracle.
AMBW-21646
Failed to update the bundle when modifying a running application in Business
Studio.
AMBW-21587
Nested Coercions did not work in the Mapper. This has been fixed.
AMBW-21583
Documents which depend upon an imported document's included document's
components are now properly resolving those references. WSDL documents
with annotation and documentation elements are now also properly parsed.
AMBW-21577
When BusinessWorks applications used schemas with no target namespace, the
following error was thrown:
no xsd for this imported location
TIBCO ActiveMatrix BusinessWorks™ Release Notes
27
Key
Description
AMBW-21189
The Invoke activity can now be used with the Accumulate Output feature for
groups. Users can now select Invoke as output activity if it has just one
Message->PartName->XSDElement as its output.
AMBW-20698
BusinessWorks applications failed to start properly after a process was
modified and saved while the Debugger was running.
AMBW-20434
The bwagent resgistration URL provided in documentation was incorrect. It has
been updated to http://<TEA_HOST>:8777/tea/.
AMBW-2649
Error Transitions from an event source and group box are now supported
Release 6.3.0
Key
Description
AMBW-21352
When large project containing modifications was saved, the entire project was
rebuilt.
AMBW-21347
For large projects, Business Studio hangs at "Building Workspace" when
creating error markers.
AMBW-21256
Exceptions thrown by conditions on transitions were not handled by the
CatchAll activity and threw the ClassCastException.
AMBW-20851
The process launcher did not show the input request for all sub processes and
showed the incorrect input while adding a new sub process.
AMBW-20758
If an importing schema contained a targetNamespace that did not exist in a
formerly imported schema, the application failed and threw the following error:
No xsd for this imported location
AMBW-20699
A memory leak was observed when the XSLT processor processed schemas
with import statements.
AMBW-20590
If a WSDL contained nested schemas, an exception was thrown and the
application failed to start.
AMBW-20500
An exception was thrown when the XSD and WSDL schemas were not resolved
during design-time validation.
AMBW-20459
When BusinessWorks applications used schemas with no target namespace, the
following error was thrown:
no xsd for this imported location
AMBW-20453
The Issue of using XSD Include with chameleon schema has been resolved.
AMBW-20410
When the engine used the HTTP protocol to look up a namespace, there was a
significant delay when applications were started.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
28
Key
Description
AMBW-20374
For certain complex hierarchies of schema types, for example, circular type
references within a chain of schema types' content models, type references were
not resolved properly.
AMBW-20298
Running BusinessWorks Studio on Windows 8.1 threw the following error on
startup: com.tibco.bw.tpcl.org.hyperic.sigar, Missing native code
match sigar-x86-winnt.dll.
AMBW-20296
The custom fault data from nested sub-process invocation was not directly
propagated to the main process.
AMBW-20266
BusinessWorks Studio did not display complex items with an asterisk (*) icon
when the maxOccurs attribute was set to a finite number.
AMBW-20201
The element of a WSDL was being referred by incorrectly using the <include>
tag in the BusinessWorks process file.
AMBW-20148
A NULL pointer exception was reported repeatedly at design time. The error
was thrown when the existing schema from the input editor of an activity was
replaced, and the new schema mapping was configured.
AMBW-20009
When Business Studio used the HTTP protocol to look up a namespace, there
was a significant delay when applications were started.
AMBW-19992
A memory leak was observed when the engine mode set to Memory mode and
the application was redeployed multiple times.
AMBW-19982
Migrating large projects from BusinessWorks 5.x to BusinessWorks 6.x took a
long time to complete.
AMBW-19968
When a nested iterative group's variable list mapped with complex elements the
error Adding definition failed for process was thrown.
AMBW-19932
Given a scenario a shared resource referenced another shared resource in a
shared module, and that shared module was included in multiple applications
running on the same AppNode, lifecycling any of the applications changed the
state of other applications to be Impaired.
AMBW-19870
The application intermittently failed to start and its status changed to Impaired
after the AppSpace was stopped and the application was undeployed and redeployed.
AMBW-19863
Iterate group did not include the referred schema and threw the following
error:
java.lang.Exception: Unresolved reference
AMBW-19859
Business Studio hung when a large project was migrated in Business Studio,
and when the project was built in the workspace.
AMBW-19858
Business Studio is now able to build a project with complex sets of schemas and
does not show the StackOverflow error.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
29
Key
Description
AMBW-19844
Exceptions were observed in the log when a new WSS Provider policy was
created in Business Studio.
AMBW-19834
Process files that were created in TIBCO ActiveMatrix BusinessWorks 6.2.1 and
contained errors could not be opened in ActiveMatrix BusinessWorks 6.2.2.
AMBW-19810
The TIBCO ActiveMatrix BusinessWorks 6 schema resolver failed to properly
resolve referenced components when using the Swift plug-in.
AMBW-19685
When a user created a new Service in an existing process using an existing XSD,
the XSD was incorrectly modified.
AMBW-19677
The attribute fields modifiedOn and modifiedBy were updated after a change
was made to a process file. This behavior caused conflicts during file
synchronization when working with a revision control system.
AMBW-19664
When the option Refactor > Rename XSD Schema namespace was used to
modify the namespace of the XSD file, an exception was thrown.
AMBW-19654
If an Invoke activity had an ActivityContext element, but the PartnerLink of the
Invoke activity did not have a context parameter, the serialization of the Invoke
activity threw an exception, and the process could not be saved.
AMBW-19634
The bwdesign utility was unresponsive after generating EAR files for the
projects.
AMBW-19607
On Microsoft Windows 7, the AppNode would not start and the error
java.util.zip.ZipException: Exception in opening zip file:
thrown if the TIBCO_HOME directory name contained a space.
was
AMBW-19590
Shared module dependencies were not automatically added to the
Dependencies section if a shared resource was being used in the shared
application module.
AMBW-19557
Group accumulate failed when the same target namespace was found in
multiple schemas.
AMBW-19503
The CatchAll block did not handle exceptions or errors thrown by incorrect
expressions on transitions.
AMBW-19478
An option to add multiple coercions for an abstract element was not available in
BusinessWorks 6.x.
AMBW-19412
Using the user defined prefix to access the WSDL elements instead of the
default tns element caused errors during runtime.
AMBW-19407
The SOAP Reference binding was not properly updated if the HTTP Client
shared resource was renamed, deleted, or removed.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
30
Key
Description
AMBW-19379
If the location of module properties for a deployed application was updated,
and the AppNode that the application was running on was restarted and
redeployed, the application failed.
AMBW-19325
Starting a simple process containing a very complicated schema threw the error,
Failed to resolve Schema java.lang.AssertionError: provider
cannot be null.
AMBW-19199
When using a group, job data could not be viewed in the debug mode.
AMBW-19106
With the current implementation it was not possible to retrieve the statistics for
individual activities or processes.
AMBW-19041
The Stale Transition Warning message continued to be displayed even after
cleaning and re-factoring the project.
AMBW-18954
When a new process property was created from the General tab, an error
message incorrectly displayed.
AMBW-18982
In Business Studio, module property names and their values were truncated in
the Module Property Selection drop-down menu if they contained more than
64 characters. The number of characters that display in the Module Property
Selection drop-down menu was increased to 128.
AMBW-18901
Error transitions are now available for all activities and groups in Business
Studio.
AMBW-18900
In Linux, the parameter type could not be selected from the drop-down menu
when it was being configured in the properties view of a REST Service Binding.
AMBW-18898
Studio no longer throws error Selected schema element's target
namespace cant be empty! if the namespace in the target XSD was not
declared.
AMBW-18706
Migrated projects did not have the System Module properties.
AMBW-18586
Job data was missing from the Job Data view in the main process when the
calling subprocess reached to breakpoint in the debug mode.
AMBW-18566
After a project was migrated from TIBCO ActiveMatrix BusinessWorks 5 to
TIBCO ActiveMatrix BusinessWorks 6, the XML attribute in the process was
missing if the attribute in the Call Process activity used a constant value.
AMBW-18565
The migration tool threw an error if all the WSDL services in the project were
not implemented.
AMBW-18464
After migrating a project from BW 5.x to BW 6.x, a literal string with a value of
"true" was translated to a boolean function true().
AMBW-18448
If an application is redeployed, and the latest version of an application is not
processed during the application start up, the status displays as Degraded in
the Admin UI.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
31
Key
Description
AMBW-18305
When JDBC activity output changed, an iteration element did not update with
the new changes.
AMBW-18271
Activity timeout in the Invoke activity did not support Module Properties.
AMBW-18092
When the Copy-Contents-Of option was selected during mapping, the error
PVM-XML-106018: Expression Creation Error: '<?xml version="1.0"
encoding="UTF-8"?>
was thrown at runtime.
AMBW-18005
The Activity output configuration error was thrown when the Invoke activity
was renamed or a dummy change was done to the name.
AMBW-17870
The following error was shown in Business Studio when the EXISTS() XPath
function was used with the activity output to check if the activity was executed:
Effective boolean value of a required component is always true
AMBW-17082
Changing the reference in a process to use a new port type did not clean up the
old references inside the process.
AMBW-17033
JAXWSInterop sample (binding > soap > http > JAXWSInterop) threw 'Activity
[JavaInvoke] fault' when deployed in Admin.
AMBW-15253
The schema parser, when checking for cycles in model groups, did not properly
exclude the contents of element particles.
AMBW-13932
If a global variable name and the iteration group's Iteration Element field name
was the same, the migration tool generated a unique name for the iteration
element.
AMBW-12263
When a user defined a fault context variable at the Port Type level, that context
did not work at run time. Operations might define multiple faults, so it was
difficult to determine the fault that should be used for each operation.
Release 6.2.2
Key
Description
AMBW-19319
The execution statistics such as Total Elapsed Time, Minimum Elapsed Time,
and Maximum Elapsed Time were incorrect for completed jobs. For failed jobs,
default values were incorrect. This has been fixed.
AMBW-19150
Due to an error in the lookup of certain OSGi bundle entries, applications failed
to start and the following error was thrown: TIBCO-BW-SCHEMARESOLVER-500204: Failed to resolve WSDL. This has been fixed.
AMBW-19121
The XML model miscalculated prefixes when ancestor nodes contained two
different prefix mappings for the same namespace and the current node
remapped one of those prefixes. This has been fixed.
AMBW-19006
The circular reference inside the schema was invalid in TIBCO ActiveMatrix
BusinessWorks 6.x.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
32
Key
Description
AMBW-18891
The runtime behavior of a process was inconsistent if the process contained a
schema (schema A) with an element declaration whose substitutionGroup
members were in other schema (schema B and C) which included schema A.
This has been fixed.
AMBW-18966
The values computed for TotalElapsedTime and TotalExecutionTime were
incorrect. This has been fixed.
AMBW-18864
When Iterate group is configured with a local xsd element that contained the
@nill attribute, the @nill attribute had to be recognized and handled inside the
Process file.
AMBW-18863
A false design-time validation was reported when a process referred to a
schema embedded within a WSDL, and the target namespace of the schema and
the WSDL was different. This has been fixed.
AMBW-18795
Fixed the latency on the debugger GUI, which was observed to be greater than
usual.
AMBW-18698
An XSD with a null element was not resolved correctly when used in the output
editor. This has been fixed.
AMBW-18675
When an XSD with no namespace was imported, the following message was
observed on the Problems tab: "Unable to load model for the Process
[Process.bwp] due to error". Closing and reopening this project caused the
following error: "Could not open the editor:
org.eclipse.core.runtime.CoreException: The file is invalid on Business Studio."
This has been fixed.
AMBW-18659
The bwdesign utility failed to validate the sample BookStore project. This has
been fixed.
AMBW-18656
The XPATH expression within the variable list was being shortened after
migrating a project from BW5 to BW6. If the expression was modified to be the
correct value, it was shortened again and an error occured at run time when
users tried to run the project.
AMBW-18623
When using the Maven plugin, validation failed if an application contained a
shared module with activities or shared resources from the FTP Palette. This has
been fixed.
AMBW-18622
When using the Maven plugin, the generated POM (pom.xml) for a shared
module contained an incorrect TIBCO_HOME if a non-default TIBCO_HOME
was specified in the Maven Configuration Details dialog. This has been fixed.
AMBW-18191
An error, Cannot find XML element, was observed intermittently at runtime
if some specific namespaces are not imported in the WSDL. The intermittent
nature of this issue was caused by the changing order in which WSDL
documents were processed. This has been fixed.
AMBW-18094
An error was thrown when the user tried to start an application deployed to the
TEA server.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
33
Key
Description
AMBW-17082
If you removed an WSDL that was formerly referenced in a project, but
currently had no references in the project then you received an Import
Configuration Error.
AMBW-16038
A NullPointerException was thrown at runtime for projects that had
subprocesses referring to an external schema.
AMBW-13955
After a component containing REST binding was deleted, it was not possible to
re-create the component with the REST binding.
PER-2106
After decrypting an incoming SOAP message at the reference endpoint, the
decrypted message was not passed back in the message context. This has been
fixed.
PER-2095
A memory leak was observed when SAML authentication policies were
enforced. This has been fixed.
PER-2083
SAML 1.1 Token 1.1 option for SAML credentials mapping policy was unable to
generate SAML 1.1 assertion. This has been fixed.
Release 6.2.1
Key
Description
AMBW-18289
When a Test Connection failed, the error message displayed on the dialog
appeared truncated and the error message could not be copied using the click
and select option with the mouse. This has been fixed.
AMBW-18214
When assigning a value to a simple variable, the Assign activity failed with an
exception if either format-Date, format-Time, or format-DateTime functions
were used. This has been fixed.
AMBW-18198
The Mapper did not fully populate the choice groups with available
substitutions. This has been fixed.
AMBW-18185
TIBCO Business Studio hung when an XSD schema was imported in the
ActiveMatrix BusinessWorks project before the dependent XSD schema.
AMBW-18163
Adding conversation to a Reply activity threw a NullPointerException.
AMBW-18114
When an iteration was included into a transaction activity, the input properties
of the elements included in the iteration were not visible and could not be
changed.
AMBW-18057
NullPointerExceptions were thrown when the init method was called several
times with same conversation key and then followed by a join. This has been
fixed.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
34
Key
Description
AMBW-18005
The configuration of the Call Process activity reported errors when the
Reference PortType was lost. This has been fixed. However, the fix requires you
to reconfigure the Call Process and Reference activities with the appropriate
settings in order to save the updated configuration.
AMBW-17990
Validation error was thrown when "schemalocation" tag was removed from the
xsd.
AMBW-17979
Mapping from a Receive activity to a SetSharedVariable activity was lost and
validation errors were thrown when the focus was moved to some other activity
and then returned to the mapping. This has been fixed. However, the fix
requires you to remap the given SetSharedVariable activity's input once in
order to store the design and runtime XSLT of the updated mapping.
AMBW-17960
When Iterate group was created, the "Variable list" element used in other
activity displayed an Activity configuration Error.
AMBW-17824
References to schema elements were not resolved when projects were imported.
AMBW-17818
TIBCO Business Studio did not validate the restriction of a nested element at
design-time. This has been fixed.
AMBW-17792
The Render XML XSLT function now includes namespace definitions in its
output.
AMBW-17772
When upgrading from version 6.2.0 to version 6.2.1 of the software, the installer
replaced the existing configuration and .tra files. As a result, any custom
configurations in the configuration or .tra files were lost. This has been fixed
and the installer now creates a backup folder, <TIBCO_HOME>\bw\6.2\backup
to store the configuration and .tra files before upgrading.
AMBW-17743
CatchAll block using XPath expressions in transitions threw XSLT compilation
error at application init time.
AMBW-17716
When a Shared Resource was configured with a non-existing module property,
the runtime did not report an error.
AMBW-17728
The following issues caused by renaming a service or reference have been fixed:
●
Renaming a service or reference caused the context mechanism to fail at
runtime. This has been fixed and the appropriate context configuration is
now updated correctly.
●
Renaming context parameters resulted in a BPEL Variable that had no
element.
●
SetContext and GetContext activities lost their reference to a service or
reference when it is renamed. Now they are updated with the new name.
Any projects (prior to HF3) broken due to renaming a service or reference, can
be fixed by renaming the service or reference in HF3.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
35
Key
Description
AMBW-17695
When copying a scope with accumulation the old element appeared to be
copied, but was no longer used. Since the variable was now invalid, it caused a
runtime error.
AMBW-17608
When renaming an activity, there was a distinct pause between each keystroke.
AMBW-17607
Validation reported a false error when building an archive file if the application
contained a Java module.
AMBW-17606
When using coercions and substitutions in the Mapper, an element was
unresolved if it was not used elsewhere in the process. Now when a coercion or
substitution is done, an import for the element's namespace is added to the
process, which allows the element to be correctly resolved.
AMBW-17579
Mapping currentElement from Iterate group threw a validation error.
AMBW-17560
Summary: When debugging using step-into, the focus was lost when stepping
into a group within a group. This issue was observed when using the Debug
view.
Workaround: Use the BusinessWorks Jobs view to debug using step-into.
AMBW-17510
REST, SOAP, and HTTP now support Basic Authentication.
AMBW-17500
Import location with HTTP URL in WSDL was not supported.
AMBW-17479
The FaultDetails generated in the CatchAll block was incorrect for activities that
throw Data Validation Exception at run time.
AMBW-17462
The JDBC activities in a transaction group failed with a NullPointerException.
This has been fixed.
AMBW-17451
The source $Variable node could not be mapped to the target tree. This has been
fixed. You can now drag $Variables of type element to map to the target tree.
AMBW-17414
Incorrect reporting of cyclic type errors by the XML Schema Parser has been
fixed.
AMBW-17397
An error was reported when loading projects that contain huge embedded
schema if a process was loaded before all of its schemas were available.
AMBW-17390
A "Failed to set CLIENTID" error was thrown, if the JMS Connection used by
the deployed application was defined in a shared module.
AMBW-17330
When a Confirm activity was used inside an exception scope (like CatchAll), it
did not show the ConfirmEvent.
AMBW-17133
The addBooks operation in the REST Bookstore sample added only up to three
books at a time. This has been fixed.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
36
Key
Description
AMBW-17131
A design time validation error appeared on Set Shared Variable activities if they
used a web service element mapping directly. This mapping error persists in
the current product version, but you can resolve the error by re-mapping the
input manually.
Each activity with this problem will have an error marker which
needs to be resolved manually.
AMBW-17083
When configuring JMS or JNDI shared resources, the UI selection toggled to
"None" if you specified the username and password fields using module
properties. This has been fixed.
AMBW-17074
Changing the default value of a module property of type String from a
predefined string to an empty string resulted in validation errors.
AMBW-17071
A runtime error was thrown when an XPath expression contained the wildcard
character '*' (any element).
AMBW-17070
The application validator did not complain when there were module
dependencies that were not included as part of the application.
AMBW-17046
ActiveMatrix BusinessWorks 6.x design-time validation / build took a
significant amount of time for complex BW6 applications. For example,
applications that involved multiple modules and deeper inter-module
dependencies. Optimization has been introduced to reduce the validation and
build time.
AMBW-17041
Mapper showed validation error when mapped to an iteration group.
AMBW-17011
The bwadmin "show apps" command showed incorrect status in the local mode.
AMBW-16997
When running an ActiveMatrix BusinessWorks application on Microsoft
Windows 2012, an error message, com.tibco.bw.tpcl.org.hyperic.sigar,
was thrown during startup. This has been fixed. The error message no longer
appears and the OSGi command appnodeprocessinfo works properly.
AMBW-16912
The custom XPath function failed with an error if the implementation contained
a main method.
AMBW-16981
When running activities that have their input generated by an XPath expression
(and not by an XSLT), a validation error "Content is not allowed in prolog" was
thrown.
AMBW-16939
When schema A imports B which includes non-chameleon C, the schema parser
sometimes reported unresolved type errors. If it did report an error, then,
during process execution, validation errors for elements pointing to that
unresolved type were thrown. This has been fixed. Note: This behavior was
observed when the schemas were parsed in a certain order and may not be seen
with every import of a schema with a non-chameleon include.
AMBW-16923
A StackOverflow exception was thrown by unnecessary loading and reloading
of schema or WSDL components. This has been fixed.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
37
Key
Description
AMBW-16846
Refactoring the HTTP Shared Resource name or package did not update the
HTTP connector field in REST binding. This has been fixed.
AMBW-16831
Projects cannot be created with their names ending with .xsd or .wsdl. The
wizard prevents the creation of a project with such a name and prompts with an
"Unsupported characters" message.
AMBW-16791
The default TIBCO Rendezvous port to enable Hawk microagents has been
updated from 7500 to 7474.
AMBW-16759
The silent installation mode now supports the installation of the runtime
component alone over an existing installation of TIBCO ActiveMatrix
BusinessWorks 6.2.0.
AMBW-16677
When you renamed a partner link or an operation, the framework did not notify
the Confirm activity. This has been fixed.
AMBW-16625
Refactoring the dependent WSDL namespace caused an error "TIBCO-BWBINDING-SOAP-500020: Failed to initialize SoapServiceBinding".
AMBW-16536
Using empty values in Module/Process property caused error in the project.
AMBW-16325
An exception, The org.eclipse.osgi plug-in is missing from this
was thrown when running an application if ActiveMatrix
BusinessWorks release 6.1.1, ActiveMatrix BusinessWorks release 6.1.1 hot fix1,
and TIBCO Enterprise Message Server 8.1 were installed in the same
TIBCO_HOME. This has been fixed.
configuration,
AMBW-16213
In the Debug Launcher, only one application could be deselected. If you tried to
deselect a second application, the first application would be selected
automatically. This has been fixed and you can now deselect two or more
applications in the Debug Launcher.
AMBW-16209
Complex elements were not visible on the Input editor. This has been fixed.
AMBW-16191
An application status was Impaired if the application module, the application,
and the EAR file were at the same location with the same name. This has been
fixed.
AMBW-15396
During reload, the schema and wsdl caches failed to remove the stale versions
of their schema and wsdl resource files. Multiple cleans (or other operations
which result in cache reloads) of projects with sufficient numbers of schema and
wsdl resources resulted in a very, very large cache which took a very, very long
time to reload. That problem is fixed.
PER-2055
Basic and Username Token Credential Mapping are now supported. This fix
requires the use of ActiveMatrix Policy Director 2.0 with ActiveMatrix
BusinessWorks 6.2. For example, this enables BW6 users to invoke ActiveMatrix
BPM web services.
Release 6.2.0
TIBCO ActiveMatrix BusinessWorks™ Release Notes
38
Key
Description
AMBW-16642
Product installation failed on Mac OS X with a dialog box requesting to install
Java SE 6.
AMBW-16038
Summary: A NullPointerException is thrown at runtime for projects which
have subprocess referring to external schema.
Workaround: None. The NullPointerException can be ignored if the REST
application can be accessed from web browser, and the application can be
started and stopped as usual.
AMBW-15334
When a process contained two or more Error transitions, the input mappings
for all but one of the activities using the error transitions were broken and
caused incorrect problem markers.
AMBW-14958
Summary: During installation, if you choose not to download and install the
Oracle Elliptic Curve Cryptography Library, then projects containing a shared
resource configured with SSL fail at run time with the following error: A fatal
error has been detected by the Java Runtime Environment.
Workaround: If you have a different JRE installed in the system path and that
one has the library installed, remove the JRE from the system path and then
relaunch TIBCO Business Studio.
AMBW-14789
While debugging, the F6 key could not be used continuously to step through
the code as the focus was lost.
AMBW-14770
Creating a conversation for a process that included both a service or a reference
and a signal-in activity resulted in a corrupted process.
AMBW-14712
The size of the drop-down field for the Reply Activity's General Service was
minimal and did not show any content by default. To resize the window, you
had to select the drop-down field and enter the return key. This has been fixed.
AMBW-14577
Clicking on a process file in the Project Explorer and choosing "Launch
BusinessWorks Debugger" option did not start the ActiveMatrix BusinessWorks
process. This has been fixed.
AMBW-14442
You can now copy and paste activities from one group to another within a
process.
AMBW-13942
When uninstalling ActiveMatrix BusinessWorks and one or more of the
following plugins from a TIBCO_HOME all at once, if ActiveMatrix
BusinessWorks was uninstalled first, then the uninstallation of the remaining
plugin products failed. The affected plugins were:
●
ActiveMatrix BusinessWorks Plug-in for CICS
●
ActiveMatrix BusinessWorks Plug-in for Data Conversion
●
ActiveMatrix BusinessWorks Plug-in for WebSphere MQ
TIBCO ActiveMatrix BusinessWorks™ Release Notes
39
Key
Description
AMBW-13090
An exception,
com.tibco.bw.core.runtime.ActivityInputValidationException, was
thrown for a variable of long data type if the long value was greater than 6
digits.
AMBW-11595
A NullPointerException was thrown when an AE activity was added to an
ActiveMatrix BusinessWorks process.
AMBW-7677
Module shared variable did not build its initial value correctly from XSD
schema for the double-byte characters.
Migration
Release 6.3.1
Key
Description
AMBW-20791
While projects were migrated, schemas were not loaded properly and faced
encoding issues.
Release 6.3.0
Key
Description
AMBW-20762
When migrating a BusinessWorks 5.x project with Java Palette activities to
BusinessWorks 6.x, the migration wizard reported that the project being migrated
is a java project.
AMBW-20726
Migration was not successful in 6.3.0 when the project contained a global variable
of the password type.
AMBW-20034
SSL enabled JMS Connection references were lost after migration.
AMBW-19933
JMS Queue Requestor activities from BusinessWorks 5.x with message type set to
XML text were not migrated correctly in BusinessWorks 6.x.
AMBW-19861
An internal error occurred, and migration was aborted when large projects were
trying to be migrated from BusinessWorks 5.x to BusinessWorks 6.x.
AMBW-19559
After migration, projects in BusinessWorks 6.x failed at runtime as an additional
import namespace with an invalid schemaLocation was added in the inline schema
file.
AMBW-19180
While migrating JMS Queue Sender activities from BusinessWorks 5.x to
BusinessWorks 6.x, projects with message type Map and Stream were not migrated
correctly, and became empty activities in BusinessWorks 6.x.
AMBW-18706
System module properties were missing from migrated projects.
AMBW-18594
After migration, coerced activity inputs are migrated correctly.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
40
Key
Description
AMBW-18565
The migration tool did not implement all the WSDL services in a project.
AMBW-18472
Duplicate output transitions were created after using the migration script for
BusinessWorks 5.x projects.
AMBW-18293
For migrated BusinessWorks 5.x processes, the <bpel:import> element did not
contain the namespace attribute for schema or WSDL references that did not have
target namespace.
AMBW-15253
An error was encountered after migration if the schema has an import statement
that cannot be resolved and one for a namespace, that was never used in the
process.
Release 6.2.2
Key
Description
AMBW-18212
TIBCO ActiveMatrix BusinessWorks 6.x did not support sorting at the mapper
statement level. This has been fixed.
Release 6.2.1
Key
Description
AMBW-18233
An Invalid SQL Exception was thrown after migration if the SQL query began with
a space. This has been fixed.
AMBW-17476
Migrating TIBCO ActiveMatrix BusinessWorks 5.x projects using command line
failed if TIBCO_HOME name contained space.
AMBW-16744
An exception was thrown when you migrated a project that contained a folder with
a space in the folder name. This has been fixed.
AMBW-14688
When importing TIBCO ActiveMatrix BusinessWorks projects containing Java,
HTTP or SMTP activities in TIBCO Business Studio, some processes might have
been marked to be dirty (indicated by the * infront of the process name in Project
Explorer). If these processes were opened, the Save button was enabled although
the user had not made any changes to the process. When this project was run in
Debugger, the exception com.tibco.bx.debug.MismatchedModelException:
Node Definitions don't match BPEL Activities was thrown.
Release 6.2.0
Key
Description
AMBW-13832
After migration, the HTTP, JMS and Mail projects showed a duplicate header on
the Input tab.
AMBW-13566
XPath could not convert an integer to string automatically when the upstream
activity had multiple level schema. This has been fixed.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
41
Key
Description
AMBW-11189
The Java Custom Function activity did not migrate successfully.
AMBW-10891
Timer activity was not migrated and displayed as an empty activity after migration
on a non-English platform.
AMBW-10289
After migration, the Data Format shared resource reference was not generated
correctly for Parse or Render data activities.
Palettes
Release 6.3.1
FTL Palette
Key
Description
AMBW-18945
Users were unable to connect to or access FTL applications through the FTL
Realm Server Connection Shared Resource in Business Studio. TIBCO
ActiveMatrix BusinessWorks 6.3.1 now comes bundled with FTL 4.3.0 client
libraries.
General Activities Palette
Key
Description
AMBW-21374
Web services that accepted a multi-part request were not successfully invoked if
one of the request part was set to null ("").
JDBC Palette
Key
Description
AMBW-21878
When an Oracle stored procedure used an Oracle Struct with a DATE type field
inside, the JDBC Call Procedure activity failed with an output validation error.
This has been fixed.
Parse Palette
Key
Description
AMBW-21873
The Parse Data activity performance slowed down if placed in a repeat loop. To
avoid this, use filename as input for parsing with the Parse Data activity.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
42
Shared Resources Palette
Key
Description
AMBW-21648
If an Invoke activity timed out in an application configured to use SOAP/HTTP
binding, HTTP Resources were not released and a memory leak was observed.
Release 6.3.0
FTP Palette
Key
Description
AMBW-19462
A plain TCP connection was created despite the FTP connection being
configured with SSL. Now, when an FTP Connection is configured with SSL, a
secure connection is created, and the process executes successfully.
AMBW-12997
Process Property of type Password mapped to the Input schema parameter
returned an encrypted password value at runtime and caused activity
connection failure. This has been fixed and it returns a decrypted password and
executes the process successfully.
General Activities Palette
Key
Description
AMBW-19760
The Timer activity did not adjust the time interval for Daylights Savings Time.
This has been fixed.
AMBW-19011
The Activator Process for OnStartup did not work as expected, and other starter
processes began in parallel.
HTTP Palette
Key
Description
AMBW-19650
The Update SSL sample project SecuredRequestResponse exposed the private
keys at both the client end and server end.
AMBW-19440
The documentation for the HTTP Palette incorrectly stated that the dynamic
header is an additional header parameter to add runtime headers to the outgoing
HTTP messages.
AMBW-18705
Logging all attempts of HTTP access and requests is now supported.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
43
JDBC Palette
Key
Description
AMBW-20251
The JDBCUpdate activity was wrongly committing changes to the database
when the batch update option was used, the activity was inside a transaction
group, and the transaction failed.
AMBW-19820
The JDBC Update activity truncated the millisecond part when using a
parameter of TIMESTAMP data type.
AMBW-19639
The JDBC Call Procedure activity failed to fetch results when an output
parameter was used at the same time there was a cursor as return type.
AMBW-19247
A JDBCConnectionNotFound fault was incorrectly thrown when a login time
exception occurred.
AMBW-19082
The JDBC Update activity incorrectly listed all stored procedures for selection
after catalog was specified as a filter.
AMBW-18183
The Schema field and Catalog or Package field could not be configured to use a
Process Property or a Module Property.
JMS Palette
Key
Description
AMBW-20696
When an application contained multiple JMS Receiver activities, and the
connection to the EMS server was reset, some JMS Receiver activities did not
reconnect and start receiving messages.
AMBW-20566
When a JMS request reply activity was executing, the exception "Invalid
temporary destination" was intermittently thrown.
AMBW-20494
In TIBCO ActiveMatrix BusinessWorks 6.x, a stack overflow error was thrown at
runtime if the JMS Receiver activity was using XSD elements from TIBCO
Collaborative Information Manager™.
AMBW-20365
While using durable subscribers, each time a JMS connection is made to the JMS
Server, a new durable subscriber is created, and using a manually specified client
ID resolved the issue.
AMBW-20312
Cyclic includes in XSD files caused a stack overflow.
AMBW-20289
The JMS Send Message activity in a transaction group failed to send a message
to TIBCO Enterprise Messaging Service (EMS) but did not throw any exception.
AMBW-19975
After the TIBCO Enterprise Messaging Service (EMS) server was restarted, the
Get JMS activity threw the error javax.jms.IllegalStateException:
Trying to Reconnect to JMS Server, and messages were not being
processed until ActiveMatrix BusinessWorks 6.x was restarted.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
44
JMS Palette
Key
Description
AMBW-19752
TIBCO Business Studio now supports XSD's with cylical dependencies. When
XSD's containing cycles are imported, a StackOverflow error does not occur.
AMBW-19630
An ambiguous error message was thrown at runtime if the activities, JMS
Connection and JMS were not configured in sync.
AMBW-19334
The values for JMSProperties element were not being populated in the output of
JMS Receiver and GetJMSQueueMessage activities.
AMBW-17324
JMS test connection failed when the URL field in KeystoreProviderResource was
set using module property.
JAVA Palette
Key
Description
AMBW-18391
If generic Java class of type <E> was selected for the Java class such as
java.util.Collection<E>, then the Input tab for that Java activity showed no
data.
AMBW-12687
Using a two-dimensional Array as an input parameter to Java Method, throws
the following exception at design time in the Java Invoke activity:
Unable to obtain information for the method [analyze2DArray] from
the class [test2DArray].NoSuchMethodException
occurred.primitives.test2DArray.analyze2DArray([Z)
REST and JSON Palette
Key
Description
AMBW-20231
Adding a new REST Service removed the custom HTTP header from the REST
schema.
AMBW-20151
Design time validations were not available for REST/JSON activities, for
unsupported schema type.
Rendezvous Palette
Key
Description
AMBW-21245
Summary: RV activities in sub-processes with xmlCompliantFieldNames or
xmlFormat enabled fail after migration.
Workaround: New projects will work after migration. For old projects the RV
activities with these properties enabled should be deleted and re-created.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
45
Rendezvous Palette
Key
Description
AMBW-20030
When a WaitforRVMessage activity joined a conversation using a schema for the
key where elementFormDefault = qualified , the process failed at runtime.
AMBW-19997
RV activities in sub-processes with xmlCompliantFieldNames or xmlFormat
enabled failed while parsing the process file.
AMBW-19848
RV messages were not properly constructed in ActiveMatrix BusinessWorks 6.x
if the type of element was simple type.
AMBW-17918
For XML format RV messages, the RV Subscriber activity adds a namespace
when messages are received without a namespace to support interoperability
between ActiveMatrix BusinessWorks 5 and ActiveMatrix BusinessWorks 6.
AMBW-12042
RV subscriber activity did not subscribe the message if output schema created by
XSD schema editor was used. It worked fine if the output schema created
Rendezvous activity input or output editor was used.
XML Palette
Key
Description
AMBW-12999
For Schemas with mixed content, Render XML adds an extra new line to the
output after each string.
Release 6.2.2
HTTP Palette
Key
Description
AMBW-18868
The Socket Timeout and Connection Timeout fields on an HTTP Client shared
resource were not working when "Apache HttpComponents" was selected as the
Implementation Library. The HTTP Client Resource automatically used the
"chunked" form as Transfer-Encoding HTTP header value regardless of whether
content-length was set in the Input tab for Apache HTTP components or not.
AMBW-18824
The JDBC Call Procedure activity failed to fetch Resultset schema when
"ResultSets Use Schema" was enabled and DB2 database was used. This has been
fixed.
JDBC Palette
Key
Description
AMBW-19803
When a login time exception occured, a JDBCConnectionNotFound fault is
incorrectly thrown.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
46
JDBC Palette
Key
Description
AMBW-18811
The JDBC Call Procedure activity returned incorrect results when calling a
stored procedure that returns multiple resultsets in DB2. This has been fixed.
AMBW-18794
The schema used by UnResolvedResultsets output element in the JDBC Call
Procedure activity in version 5.x and version 6.x of the product were different.
This has been fixed.
AMBW-18543
If an application was run without using the Fetch button on the JDBC Query
activity, the application runs assuming "Record*" as a schema and did not throw
any error at design-time or runtime.
AMBW-18514
A NullPointerException was thrown when calling a stored procedure in DB2
mainframe. This has been fixed.
AMBW-16065
The Use NIL check box in JDBC Query activity's Advanced tab did not work as
expected and the output parameters of the JDBC Call Procedure were not
nillable.
AMBW-7535
While selecting the procedure or function in the JDBC Call Procedure activity,
Package functions displayed until a Package is provided in the Catalog or
Package field. This has been fixed.
AMBW-4297
JDBC activities did not validate unsupported queries.
AMBW-4071
Save button gets enabled after every click on "JDBC Query activity" , even when
no changes are made. This has been fixed.
JMS Palette
Key
Description
AMBW-18345
The JMS Receiver did not honor the cardinality of the XML Schema elements
passed as an application property and generated a fault if those properties were
not populated in the message received. This has been fixed.
REST and JSON Palette
Key
Description
AMBW-18224
Invoke REST API activity bypassed the proxy server configured on HTTP
Client shared resource. This has been fixed.
AMBW-18050
A "404 Not Found" error was encountered if base path name was same in the
Path and Query parameters in the Resource Service Path field. This has been
fixed.
Release 6.2.1
TIBCO ActiveMatrix BusinessWorks™ Release Notes
47
General Activities Palette
Key
Description
AMBW-17370
A NullPointerException was thrown by the Inspector activity when the
Inspect field was set to ALL.
JAVA Activities Palette
Key
Description
AMBW-18240
When a Java activity was modified, it did not refresh its signature correctly and
caused errors. This has been fixed.
To trigger the refresh of a Java activity's signature, select or reselect the Java
Class Name in the activity's General tab after the Java activity is modified.
AMBW-17374
When running the Java Invoke activity in a multi-threaded mode under load test,
an intermittent error was observed.
AMBW-6453
A runtime exception was thrown for Java to XML activity when trying to convert
java object containing Collections. For example, List, Set, Map, or its
implementations (ArrayList, and so on).
JDBC Palette
Key
Description
AMBW-18254
The SQLDirect activity has been fixed to participate in transactions.
AMBW-17745
Referring out parameter to CURSOR in store procedure, showed an error in
TIBCO Activematrix BusinessWorks 6.2.0 hotfix2 instead of showing
“UnresolvedResultSet”.
AMBW-17731
The JDBC Query activity did not refresh the Output schema automatically when
changes were made to the table in the database. To fix this, use the Fetch button
to refresh the output schema manually.
The Refresh button has been renamed to Fetch.
AMBW-17511
Calling an SQLServer stored procedure failed with an exception when the JDBC
Call Procedure activity was configured with a Catalog name.
AMBW-17008
Module property support added for Maximum Connections field in JDBC
Connection resource .
JMS Palette
Key
Description
AMBW-17433
The JMS Application Property displayed "Unresolved Element" in the Input tab
if the Application Property was defined in a shared module and the activity used
XML Text as Message Type.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
48
JMS Palette
Key
Description
AMBW-17155
The schema payload on the Input tab of a JMS activity failed to load and a
message "Unresolved reference in schema" was received if the Application
Properties Type on the Advanced tab was selected. Previously, we advised users
to close and re-open the project after such configuration for the activity signature
to display properly. This is no longer required with this fix.
REST and JSON Palette
Key
Description
AMBW-17005
"TIBCO-BW-PALETTE-REST-100014: An error occurred in render
activity: [no message for java.lang.NullPointerException]"
exception was thrown at run time for Complex Type element with
simpleContent.
AMBW-17599
The 'XML to JSON' activity has been fixed to allow it to be added, removed, and
modified without causing a configuration error.
AMBW-15931
When sending a REST request to invoke a REST resource and authentication is
enabled, the authorization header is not added to the request. As a result, the
request failed even though the authorization information was provided. This
issue was observed only with the Invoke REST API activity.
XML Palette
Key
Description
AMBW-17792
Render XML XSLT Function did not include namespace definitions in the
output.
AMBW-16925
An exception was thrown at runtime if the Stylesheet field in the Transform XML
activity was specified using a module property and the module property
contained an absolute path to the stylesheet.
Release 6.2.0
HTTP Palette
Key
Description
AMBW-14508
The HTTP Client Resource automatically used the "chunked" form as TransferEncoding HTTP header value regardless of whether content-length was set in the
Input tab for Apache HTTP components or not.
AMBW-11263
Parameters on the Send HTTP Request activity were automatically deleted when
Directory name was added on the Advance tab as Module Property.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
49
HTTP Palette
Key
Description
AMBW-9210
The HTTP Request activity always applied UTF-8 encoding to generate a URI
encoded string for the GET method, regardless of the content-type setting in the
HTTP Header.
AMBW-7757
The HTTP Receiver activity always applied UTF-8 encoding to get the parameter
data from URI encoded strings. The parsed parameter data in the HTTP Receiver
activity was garbled if native encoding was applied to URI encoded string.
JMS Palette
Key
Description
AMBW-15982
When configured with JMSApplicationProperties and XML Text payload, the
Body element clashed and mapping could not be done in the input field. This has
been fixed.
However, the UI is not refreshed automatically. You must close the project and
then re-open it to refresh the UI.
AMBW-14631
The package name of an existing JNDI configuration was deleted if a second JMS
Shared Resource of type JNDI was added with the following conditions:
●
the New button shortcut is used to create the JNDI Configuration.
●
a JNDI Configuration with the same name already exists.
This led to a validation error 'No JNDI Configuration specified' on all the
JMS Connection shared Resources that used the affected JNDI Configuration.
AMBW-7449
RequestTimeout input item is now available in the JMS Request Reply activity.
REST and JSON Palette
Key
Description
AMBW-14866
When using the BW JSON UTILS > Create Schema from JSON payload wizard,
the XSD schema was always created with the root element name even though a
different file name was specified.
For example, if the root element name was "Books" and the file name was
"Books1.xsd", then the schema was created as "Books.xsd" .
AMBW-13573
The REST Invoke activity now throws a design time validation error if
configured with an HTTP Client Resource which has an unsupported
Implementation Library.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
50
Shared Resources
Key
Description
AMBW-11984
When a Shared Resource field had a Module Property value, and that field was
changed to Literal and then immediately back to Module Property, the Module
Property choice had to be re-selected. The change to Literal Value removed the
Module Property value, but the combo box still retained the old value. The old
Module Property value was not saved in the Shared Resource.
XML Palette
Key
Description
AMBW-14283
An Activity output data validation error exception was thrown at
runtime for schemas that contained "any" element and processContents="strict".
AMBW-12860
After migration, problem markers were seen for "Render-PO-XML","Map-Data" ,
"Assign" and "Publish-CompletePO-Message". This has been fixed.
AMBW-11722
In the Input of the Render XML, if each element was mapped individually with a
corresponding output of Parse XML, every element was prepended with
"schemas:".
Policies
Release 6.3.0
Key
Description
AMBW-19814
If the name of an Identity Provider resource contained non-ASCII characters,
an exception was thrown when the project was ran in the Debugger. This has
been fixed.
AMBW-19666
If module properties used by a policy were updated, the changes did not take
effect when the application was stopped and then restarted or redeployed.
AMBW-19378
The Basic Credential Mapping policy was not supported on SOAP Reference
Binding.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
51
Known Issues
The following are the known issues in this release of TIBCO ActiveMatrix BusinessWorks.
The known issues are grouped by components:
●
Administration
●
Bindings
●
General
●
Migration
●
Palettes
●
Policies
Administration
Key
Description
AMBW-17562
Summary: The OSGi configuration properties have been aligned between the
debug environment launched from within TIBCO Business Studio and the
AppNode that is launched in an installation. However, a difference in behavior
of the osgi.compatibility.bootdelegation property in both the
environments has been observed.
Workaround: None.
Bindings
Key
Description
AMBW-21363
Summary: REST Call was failed on run-time under non-UTF8 locale
environment.
Workaround: Set the default encoding of the AppNode to UTF-8 by adding "Dfile.encoding=UTF-8" to java.extended.properties of "bw/6.3/config/
bwappnode-an. tra_template".
AMBW-21351
Summary: Query parameter data types default to string and cannot be
changed.
Workaround: None.
AMBW-21338
Summary: Swagger UI does not support fields for Basic Authentication.
Workaround: None.
AMBW-21091
Summary: If REST resources are implemented as Opaque, the Swagger
specification generated is incorrect.
Workaround: None.
AMBW-20990
Summary: The Connection Header field is not populated in a SOAP service
request.
Workaround: None.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
52
Key
Description
AMBW-18408
Summary: Swagger UI does not get the response for invoking POST/PUT
method for form parameter on Firefox browser.
Workaround: None.
AMBW-16039
Summary: Incorrect Swagger specification models are generated for REST
services when using the pass-through mechanism (Opaque mode).
Workaround: None.
AMBW-13607
Summary: REST Doc UI is not supported on Firefox browser.
Workaround: Use other browsers for the Doc UI.
AMBW-13572
Summary: For some use cases, REST Doc UI does not show the correct error
code in case of Internal Server errors on the Server side.
Workaround: Check the raw message that contains the correct error code.
AMBW-13485
Summary: REST Doc UI does not support browsers like Internet Explorer.
Workaround: Use Chrome browsers for the Doc UI.
AMBW-8982
Summary: Changing the Resource name in the REST service Bindings tab,
does not update the Resource Service Path.
Workaround: None.
General
Key
Description
AMBW-22053
Summary: A Shared Module is not added as dependency after a Module
Property, which is pointing to a Shared Resource from a Shared Module, is
referenced in the Application Module.
Workaround: Manually add the required Shared Module as a dependency.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
53
Key
Description
AMBW-22037
Summary: Users cannot create new projects in Business Studio if the region
and language format in your operating system is set to Thailand.
Workaround: Follow these steps:
1. Open the TIBCOBusinessStudio.ini file. This file can be found at <TIBCO
HOME>/studio/<Version>/eclipse.
2. Add the -Duser.language= field and set the value to en in the
TIBCOBusinessStudio.ini file.
The modified file should look like the following example:
C:/bw630/install/studio/4.0/eclipse
-vmargs
-Duser.language=en
-Dfile.encoding=UTF-8
-Dorg.osgi.framework.bootdelegation=javax.xml.*
3. Close Business Studio and re-open it.
AMBW-21498
Summary: When a Process Property is selected in the Process Property section
of a process, the process property is not displayed. This issue only occurs if
Business Studio 6.3.x is used in the Red Hat Enterprise Linux 7.0 or 7.1
versions.
Workaround: Upgrade Red Hat Enterprise Linux 7.0 or 7.1 to the latest version
of Red Hat Enterprise Linux 7.2.
AMBW-21497
Summary: When creating BusinessWorks Application Module, the "Set Special
Folders" page in the wizard does not display. This issue only occurs if Business
Studio 6.3.x is used in the Red Hat Enterprise Linux 7.0 or 7.1 versions.
Workaround: Upgrade Red Hat Enterprise Linux 7.0 or 7.1 to the latest version
of Red Hat Enterprise Linux 7.2.
AMBW-21489
Summary:Options in drop-down menus do not display. This issue only occurs
if Business Studio 6.3.x is used in the Red Hat Enterprise Linux 7.0 or 7.1
versions.
Workaround: Upgrade Red Hat Enterprise Linux 7.0 or 7.1 to the latest version
of Red Hat Enterprise Linux 7.2.
AMBW-21402
Summary: When the engine persistence mode is configured for datastore
mode, the duplicate key detection feature does not work with the PostgreSQL
database.
Workaround: Use an Oracle, MySQL, or SQL Server database instead.
AMBW-21363
Summary: REST Call failed on run time under a non-UTF8 locale environment.
Workaround: Set the default encoding of AppNode to UTF-8 by adding "Dfile.encoding=UTF-8" to java.extended.properties of "bw/6.3/config/
bwappnode-an.tra_template"
TIBCO ActiveMatrix BusinessWorks™ Release Notes
54
Key
Description
AMBW-21128
Summary: Flow limit does not work for REST Bindings.
Workaround: None.
AMBW-20900
Summary: The error java.lang.reflect.InvocationTargetException is
intermittently thrown in Business Studio if you configure an application
module to use a shared resource contained within an shared module.
Workaround: None.
AMBW-20456
Summary: Adding an operation in an existing service breaks the first
operation reply Input.
Workaround: Open the process, and perform the following steps:
1. Click the Service drop down, and select Add Request-Response
Operation.
A new operation is added.
2. Select the placeOrderOpOut activity.
3. From the General Tab, select the newly added operation in the Operation
combo of the Service section.
4. Select the placeOrderOp activity.
5. Save all.
6. Click on it and choose Implement Operation.
7. Connect placeOrderOpOut to operationIN.
8. Click Save.
Check the input of activity "placeOrderOpOut".
AMBW-20242
Summary: When editing a saved value for any activity in Business Studio, the
exception "Unhandled event loop exception" is thrown when you click on the
XPath Editor field from the Input tab.
Workaround: None.
AMBW-19789
Summary: Embedded policies are not enforced on the AIX platform, and the
exception NoClassDefFoundError is logged in the AppNode log when you
start the AppNode.
Workaround: None.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
55
Key
AMBW-19764
Description
Summary: An error Buildfile: /opt/bw622V12/bw/6.2/scripts/
is observed when you run the bwinstall utility
from the command line.
bwinstall.xml BUILD FAILED
Workaround: Follow these steps:
1. From the BW_HOME/bin prompt, open the bwinstall.tra file > vi
bwinstall.tra
2. Edit the following line:
tibco.class.path.extended=%TIBCO_HOME%/tools/lib/
antpackage.jar
3. At the end of the line tibco.class.path.extended=%TIBCO_HOME%/
tools/lib/antpackage.jar, add a colon and the directory path to the
xercesImpl.jar file. The line should look similar to the following:
tibco.class.path.extended=%TIBCO_HOME%/tools/lib/
antpackage.jar:%BW_HOME%/system/shared/
com.tibco.tpcl.org.apache.xerces_2.11.0.007/xercesImpl.jar.
4. Save the file and relaunch the bwinstall utitlity.
AMBW-19755
Summary: If you are using the AIX platform 7.1 for BW 6.2.2, the following
error is thrown if you run the bwinstall utility from the command line.
Buildfile: /opt/bw622V12/bw/6.2/scripts/bwinstall.xml
BUILD FAILED XML parser factory has not been configured
correctly: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl
not found
This package would typically be a part of the JRE (under rt.jar) but is missing
on the AIX platform
Workaround: Follow these steps:
1. From the BW_HOME/bin prompt, open the bwinstall.tra file > vi
bwinstall.tra
2. At the end of tibco.class.path.extended=%TIBCO_HOME%/tools/lib/
antpackage.jar, add a colon ( : ) and the path to the xercesImpl.jar file.
Refer to the following line for an example of what the modified line should
look like:
tibco.class.path.extended=%TIBCO_HOME%/tools/lib/
antpackage.jar:%BW_HOME%/system/shared/
com.tibco.tpcl.org.apache.xerces_2.11.0.007/xercesImpl.jar
3. Save the file.
4. Execute the bwinstall utility again.
The bwinstall utility executes successfully.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
56
Key
Description
AMBW-19540
Summary: When a project contain abstract and concrete WSDL using same
target namespace, a validation error is thrown.
Workaround: None.
AMBW-18680
Summary: BusinessWorks Launch configuration does not update Process data
cache information.
Workaround: When the application is running in the datastore persistence
mode, the applications/processes can be retrieved from the database.
Alternatively, uninstall the application with OSGi command manually from
the console before disconnecting the debugger(BW launcher).
Follow these steps:
1. Command "la" lists all the bundles.
2. Command "uninstall
AMBW-18469
bundleId"
uninstalls the indicated bundle.
Summary: The initial value of a Module Property is not a valid runtime value
for Boolean, Long, DateTime, and Password types. An initial value is required
for these types, but for Password the user must set and unset the value to make
it work at run time.
Workaround: Set and unset the password Module Property value if an empty
string is desired for the password value.
AMBW-18459
Summary: The ability to reference from a standalone (external) schema to an
inline schema is not supported. If your project contains such a reference, a
validation error is thrown.
Workaround: Externalize the WSDL-inline schema and change the import
statements to reference the newly created (external) schema.
AMBW-18312
Summary: An application fails to deploy if EAR file name contains non-ASCII
characters and a profile is uploaded instead of the default.
Workaround: None.
AMBW-18138
Summary: An application profile fails to download if application name
contains non-ASCII characters.
Workaround: None.
AMBW-17998
Summary: The EAR file generated using bwdesign utility does not support
non-ASCII characters.
Workaround: None.
AMBW-17807
Summary: (On Mac) XPath expression is not getting updated for the "Sequence
Key" field if OK is pressed in the XPath builder after making changes in the
expression.
Workaround: After writing the expression click anywhere else in the XPath
builder or press enter before clicking the OK button. The updated value gets
recognized.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
57
Key
Description
AMBW-17562
Summary: The OSGi configuration properties have been aligned between
debug environment launched from within TIBCO Business Studio and the
AppNode that is launched in an installation. However, a difference in behavior
of the "osgi.compatibility.bootdelegation" property in both the environments
has been observed.
Workaround: None.
AMBW-17089
Summary: TIBCO ActiveMatrix BusinessWorks project throws a warning
during validation when it is copied from an old workspace and imported to a
new workspace.
Workaround: None.
AMBW-17034
Summary: When an application with RVCM is stopped, the AppNode does
not release the RVCM ledger file handle. As a result, when you try to restart
the application, the RVCM ledger file cannot be opened and the application
fails to start.
Workaround: For applications with RVCM, restart the AppNode instead of
restarting the application.
AMBW-16633
Summary: TIBCO Business Studio fails to launch on Mac Yosemite OS as the
JAVA SE 6 runtime is not available by default.
Workaround: Download and install the Java for OS X 2014-001 from http://
support.apple.com/kb/DL1572.
AMBW-16256
Summary: The first attempt to change the data type of an Operator's input or
output schema element fails and the change is not committed. Subsequent
attempts complete without any failure.
Workaround: To commit the change, you must press the return key after every
change.
AMBW-15154
Summary: Large BusinessWorks 5.x projects take a long time to migrate to
BusinessWorks 6.x. After fixing errors in the migrated project and saving the it
the workspace take a long time to build.
Workaround: Ensure the heap memory is set to 4 gigabytes for large projects,
and complete the following steps:
1. Switch Auto Build off when importing the project.
2. After the project is imported, switch Auto Build on.
3. Repair the project using the Refactor > Repair BusinessWorks Project >
Refresh Projects Cache option.
4. Clean the project.
AMBW-14861
Summary: Unable to enter an XPath expression on a transition using the XPath
Builder. This issue is observed on Mac OS only.
Workaround: Enter the XPath expression directly in the Properties tab >
Expression field for the transition without using the XPath Builder.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
58
Key
Description
AMBW-14533
Summary: Mapper does not throw typecasting error, if the Integer data type is
mapped with String data type.
Workaround: None
AMBW-13823
Summary: Directory browser dialog in BW Context Sensitive Help preference
setting page does not consistently popup on Mac OS X 10.9.2
Workaround: Copy and paste the directory path into the configuration field
instead of using directory browser to pick it.
AMBW-13683
Summary: Shared resource module property references in the migrated TIBCO
ActiveMatrix BusinessWorks 5.x projects do not show up correctly on nonWindows platforms.
Workaround: Close and reopen the project.
AMBW-13673
Summary: Schema is not populated in Input Editor/Output Editor if there is no
targetNamespace in the schema.
Workaround: Provide targetNamespace in the schema.
AMBW-12785
Summary: When trying to exit TIBCO Business Studio before saving the
process, the error java.lang.NullPointerException is thrown.
Workaround: None.
AMBW-12490
Summary: Under certain circumstances, substitution types do not resolve
properly in the mapper. The mapper shows errors for them.
Workaround: Try closing and reopening the project. If that does not solve the
issue, try closing and reopening Eclipse. If the errors still persist, perform a
project clean (that is, go to the Project menu and click Clean...).
AMBW-11815
Summary: A module shared variable cannot initialized with an XML file that
contains double-byte characters.
Workaround: None.
AMBW-11624
Summary: TIBCO Business Studio hangs when opening SQL Builder if the
database details on the JDBC shared resource are changed from PostgreSQL to
MySQL after a query has been created using SQL builder.
Workaround: None.
AMBW-11534
Summary: TIBCO Business Studio crashes occasionally on Windows 2012 R2
platform when switching workspace from File > Switch Workspace.
Workaround: Retry by switching the workspace.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
59
Migration
Key
Description
AMBW-21089
Summary: When you migrate an ActiveMatrix BusinessWorks 5.x project
containing an HTTP Shared Resource with a space in its name, the HTTP
shared resource is not correctly mapped in the Transport configuration of Soap
Binding.
Workaround: Manually reselect the HTTP Shared Resource on the SOAP
Binding.
AMBW-20170
Summary: Validation errors occur after migration when an XML element from
an XSD schema, that does not have a target namespace, cannot be resolved.
Workaround: None
AMBW-16406
Summary: When you migrate a project using the command line, the output
schema in the migrated project is missing.
Workaround: To fix this issue, follow these steps:
1. In the Project Explorer view, select all the projects in your workspace.
2. Right-click and select Refactor > Reload Working Copy.
AMBW-14547
Summary: When you migrate an ActiveMatrix BusinessWorks 5.x project
containing in-built functions in the JDBC Query activity, an Invalid Column
name error is thrown at the JDBC Query activity.
Workaround: Use an Alias instead of the in-built functions in the ActiveMatrix
BusinessWorks 5.x project.
AMBW- 14533
Summary: Mapper does not throw typecasting error if Integer datatype is
mapped with String datatype.
Workaround: None
AMBW-14295
Summary: After migration, the output of project with Rest and JSON activities
does not match with the input of the other activities in the migrated project.
Workaround: None.
AMBW-14213
Summary: After migration, the Render XML activity gets an incorrect input
schema because of schema collision.
Workaround: Avoid schema collisions by declaring targetNamespaces in all
schema. When that is not possible, include only one of the conflicting schema
in each process.
AMBW-13823
Summary: Directory browser dialog in BW Context Sensitive Help preference
setting page does not consistently open on Mac OS X 10.9.2
Workaround: Copy and paste the directory path into the configuration field
instead of using directory browser to pick it.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
60
Key
Description
AMBW-11853
Summary: A process that has an XSLT with a substitution, throws a validation
exception at run time, unless the process is explicitly importing the XML
Schema.
Workaround: The user should explicitly import the XML Schema in the
process, by using the Add Process Import tool that is available in Process
Properties > Dependencies tab.
AMBW-11449
Summary: Mapping an anyType element to a XML Schema simple type value
results in an error.
Workaround: Coerce the anyType element with XML Schema simple type
element and map. The type of the element used for coercion is determined by
the value that is used in the mapping.
AMBW-9969
Summary: TIBCO ActiveMatrix BusinessWorks 5.x projects with SOAP
headers configuration in SOAP activities are not properly migrated to TIBCO
ActiveMatrix BusinessWorks 6.x.
Workaround: SOAP functionality in ActiveMatrix BusinessWorks 6.x is
achieved through SOAP Binding where its detail configuration is outside of
BusinessWorks Process. The SOAP headers definition are defined at the
Binding configuration and configured as generic context parameters for the
Process. In the Process, you can use the Get Context activity (from Basic
Palette) to retrieve and process the headers as context data. You can do this
manually to complete the migrated project.
Palettes
HTTP Palette
Key
Description
AMBW-12732
Summary: Dynamic Headers for HTTP send request activity are partially
migrated. The user after migration has to re-map these missing dynamic
header fields by using original ActiveMatrix BusinessWorks 5x mappings in
reference.
Workaround: Add missing headers manually after migration.
JAVA Palette
Key
Description
AMBW-22073
Summary: Java classes, which require Spring framework, do not load in TIBCO
ActiveMatrix BusinessWorks 6.3.1.
Workaround: None.
AMBW-13526
Summary: In Java To XML activity, the Output tab is not populated correctly,
if Java Class contains nested Object references in different classes.
Workaround: None.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
61
JAVA Palette
Key
Description
AMBW-6409
Summary: The exception Activity output data conversion error is
thrown for the Java to XML if the input has an ArrayList containing a JAVA
object.
Workaround: Use Java Generics and provide the "Type" information. For
example, use generics List<String> list = new ArrayList<String>();
instead of List
list = new ArrayList();
JDBC Palette
Key
Description
AMBW- 14547
Summary: When you migrate an ActiveMatrix BusinessWorks 5.x project
containing in-built functions in the JDBC Query activity, an Invalid Column
name error is thrown at the JDBC Query activity.
Workaround: Use an Alias instead of the in-built functions in the ActiveMatrix
BusinessWorks 5.x project.
AMBW- 11624
Summary: TIBCO Business Studio hangs when opening SQL Builder if the
database details on the JDBC shared resource are changed from PostgreSQL to
MySQL after a query has been created using SQL builder.
Workaround: None.
AMBW-11667
Summary: Using any in-built function in JDBC Query activity without "Alias"
fails to execute the application and throws an Invalid Column name error at
run time.
Workaround: Use "Alias" to work with any in-built function in JDBC Query
activity.
AMBW-14624
Summary: The Set Explicit Nil check box for Objects and Collections in JDBC
Call Procedure activity is disabled.
Workaround: None.
AMBW-8855
Summary: The localized error messages of JDBC connection are not displayed
correctly in Studio.
Workaround: None.
JMS Palette
Key
Description
AMBW-18213
Summary: When trying to deserialize a message, an error is encountered.
However, this message is not clear.
Workaround: None.
TIBCO ActiveMatrix BusinessWorks™ Release Notes
62
Parse Palette
Key
Description
AMBW-12473
Summary: Parse Data activity throws a NullPointerExeption for the XSD
namespace collision scenario.
Workaround: None.
Rendezvous Palette
Key
Description
AMBW-21245
Summary: RV activities in sub-processes with xmlCompliantFieldNames or
xmlFormat enabled fail after migration.
Workaround: New projects will work after migration. For old projects the RV
activities with these properties enabled should be deleted and re-created.
XML Palette
Key
Description
AMBW-14292
Summary: Parse XML activity displays blank ErrorCode and ErrorMessage for
activity output data validation error.
Workaround: None.
Policy
Key
Description
AMBW-19792
Summary: When the WSS Consumer policy is configured to verify decryption,
but not configured for authentication, an error message is incorrectly logged
instead of a debug message.
Workaround: None
AMBW-19513
Summary: If a SOAP binding is not configured with Transport, the Add New
Policy icon should be disabled, the Policy field should not be displayed in the
tree view, and a NULL pointer exception is thrown if you try to add a policy on
the binding.
Workaround: None.
TIBCO ActiveMatrix BusinessWorks™ 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