Vous êtes sur la page 1sur 36

TIBCO™ BusinessWorks

Release Notes
Software Release 2.0.0
November 2002
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
TIBCO BUSINESSWORKS CONCEPTS). 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.
Technologies described herein are covered by existing patents and pending patent applications.
TIBCO technology is protected under US patent number 6,003,011.
TIB, TIBCO, Information Bus, The Power of Now, TIBCO Rendezvous, TIBCO AlertServer, TIBCO
Adapter SDK, TIBCO AdapterAdministrator, TIBCO Repository, and TIBCO Hawk are either
registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other
countries.
EJB, J2EE, JMS and all Java-based trademarks and logos are trademarks or registered trademarks of
Sun Microsystems, Inc. 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 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.
Copyright © 2001-2002 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information


| iii

Contents

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
BusinessConnect Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
BusinessWorks Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Deployment Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
FTP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
General Palette. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
HTTP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
JDBC Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Mail Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Manual Work Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Publishing Activities (TIBCO Rendezvous and ActiveEnterprise Adapter Palettes). . . . . . . . . . . . . . . . . . . . 6
Rendezvous Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Shared Configuration Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
SOAP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
TIBCO BusinessWorks Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
TIBCO Rendezvous Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Parse Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
XML Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
TIBCO BusinessWorks Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
BusinessConnect Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
JDBC Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Rendezvous Transport Shared Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Parse Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Mapping from Input tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
XML Schema Parsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Known Issues—Deployment Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Migrating Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
JDBC Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Java Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Internationalization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

TIBCO BusinessWorks Release Notes


iv
| Contents
Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Using Non-Default TIBCO Rendezvous Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Adapter Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Replacing a Pre-GA Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

TIBCO BusinessWorks Release Notes


|1

Release Notes

These release notes list issues according to topic area. Since TIBCO BusinessWorks
2.0.0 is a major release, release information about previous releases has been
removed from this document.

TIBCO Designer, TIBCO Administrator, and TRA are now shipped as separate
products, each with release notes of their own. The release notes for these
products are no longer included with these TIBCO BusinessWorks Release Notes.

When you first start TIBCO Administrator, each screen takes a noticeable amount
of time to display the first time. Afterwards, display is not delayed.
If you click on individual items too quickly, an error results.

Check the TIBCO Product Support web site at http://support.tibco.com for


product information that was not available at release time. Entry to this site
requires a username and password. If you do not have one, you can request one.
Your web browser must support cookies and you must have a valid maintenance
or support contract to use this site.

Topics

• New Features, page 2


• Changes in Functionality, page 10
• Known Issues, page 14
• Known Issues—Deployment Palette, page 21
• Closed Issues, page 23
• Migration, page 25
• Internationalization, page 26
• Using Non-Default TIBCO Rendezvous Parameters, page 30

TIBCO BusinessWorks Release Notes


2
| Release Notes

New Features

This section lists features added since the 1.1.2 release of this product. See
Changes in Functionality for a listing of changes, which includes enhancements of
existing functionality.
The new features are organized alphabetically on a per-palette basis.
• BusinessConnect Palette
• Deployment Palette
• FTP Palette
• General Palette
• HTTP Palette
• JDBC Palette
• Manual Work Palette
• Publishing Activities (TIBCO Rendezvous and ActiveEnterprise Adapter
Palettes)
• Shared Configuration Palette
• SOAP Palette
• TIBCO BusinessWorks Engine
• TIBCO BusinessWorks Engine
• TIBCO Rendezvous Palette
• Parse Palette
• XML Palette
Note that you can view Changes in Functionality separately.

BusinessConnect Palette
• Receive Response resource. The Receive Response process starter resource
has been added to make it possible receive a response from TIBCO
BusinessConnect asynchronously.
• Receive Misc Message activity. The Receive Misc Messages process starter
resource has been added to receive error/info and other miscellaneous
messages from TIBCO BusinessConnect.
• Send Misc Message activity. The Send Misc Messages activity has been
added to send miscellaneous messages to TIBCO BusinessConnect.

TIBCO BusinessWorks Release Notes


New Features 3
|

BusinessWorks Engine
See TIBCO BusinessWorks Engine on page 8

Deployment Palette
• Specify Log File Size and Number. TIBCO BusinessWorks generates log files
and used to overwrite the oldest log file after a preset size had been reached.
In TIBCO BusinessWorks 2.0, users can set the maximum size of the log file
(default is 1,000,000 bytes) and the maximum number of log files (default is
10).
• Storing process engine information. You can now specify that process engine
information is stored in a file or a database.
• Fault Tolerance setup. Any process engine can now be a member of a fault
tolerant group. Different group setup options are supported.
• Controlling process instance execution. Two new options, Max Jobs and
Activation Limit, are available:
— Max Jobs—The number of process instances for this process starter that can
be in memory concurrently. When the threshold is reached, the data for
new or paused process instances is paged out and will not consume
memory resources.
— Activation Limit—Specifies that process instances should remain in
memory until they are completed. Normally, process sentences are paged
out if they are waiting for incoming events. Checking this option keeps the
process instance active and in memory until it reaches its End activity.
See TIBCO BusinessWorks Process Design Guide for more information about
controlling process instance execution.

FTP Palette
The FTP Put and FTP Get activities can now transfer a file directly, without the
need for a separate file read or write activity. The file name can be specified as an
input value to the FTP activities. This direct file transfer mode should be used for
large files, because, unlike the file activities, it does not require that the entire file
be read into memory at once.

TIBCO BusinessWorks Release Notes


4
| Release Notes

General Palette

Execute External Command Activity


This activity executes a user-specified external program. Input data can be passed
to the program, and the program’s output can be retrieved as a string or written
directly to a file.

Java Code Activity


You can now pass a Java object from one Java Code activity to another by way of
the Input and Output parameters.

Wait/Notify Activities
TIBCO BusinessWorks 2.0 supports a wait-notify mechanism, which allows one
process instance (job) to synchronize operation with another process instance.
In this release, the mechanism is implemented by the following activities:
• Notify Configuration shared resource
• Wait activity (General Activities palette)
• Notify activity (General Activities palette)
• Receive Notification process starter (General Activities palette)
For additional information on these activities, see the TIBCO BusinessWorks
Process Design Guide.

HTTP Palette
Authentication: You can set up the activities in the HTTP palette to use
authentication. The HTTP client and server activities support basic HTTP
authentication as defined in RFC 2617.
• The HTTP Receiver and Wait for HTTP Request activities have a checkbox
that enables HTTP authentication. When HTTP authentication is enabled,
clients must provide a valid TIBCO Administrator user name and password
to receive data.
• The Send HTTP Request activity has a checkbox that enables authentication.
The user name and password must be provided in the Send HTTP Request
activity’s configuration panel.
Proxy Server. The Send HTTP Request activity now allows you to specify a proxy
server for outgoing requests.

TIBCO BusinessWorks Release Notes


New Features 5
|

HTTPS: You can now use the activities in the HTTP palette to set up HTTPS
communications.
• The HTTP Connection shared resource allows you to select Use Secure
Socket, then specify Trusted Certificate Location, Server Key Store,
Key Password, and Client Authentication Required.

• In the Send HTTP Request activity, you can select Use Secure Socket
(HTTPS) and then specify Trusted Certificate Location, Client
Identity, and Client Identity Password.

HTTPS is included as a technology preview feature.

JDBC Palette
• New drivers. The JDBC palette now supports Data Direct (bundled), Oracle
thin and thick drivers for Oracle, and Data Direct driver (bundled) for
Microsoft SQL Server.
• NULL. A new option in the JDBC Query activity allows you to expose
database NULLs either as nilable or as optional elements. For other changes
involving NULLs, see also NULL under Changes in Functionality on page 10.
• SQL Direct activity. A new SQL Direct activity allows you to execute
dynamic SQL statements.
• BLOBs and CLOBs. BLOBs and CLOBs. BLOBs and CLOBs are now
supported with the Data Direct 3.1 driver for Oracle. They are NOT supported
with any other driver.

Mail Activity
In the Receive Mail activity’s Output tab, there is now an item encoding, which
must be a string. The value of this item is used to decode text data with the
specified encoding after the mail has been received. In the context of a MIME
message header, it is the charset parameter that may be specified in the
Content-Type field for text/plain data.

In the Send Mail activity’s Input tab, there is now an item encoding, which must
be a string. The value of this item is used to encode text data with the specified
encoding before mail is sent. In the context of a MIME message header, it is the
charset parameter that may be specified in the Content-Type field for
text/plain data.

TIBCO BusinessWorks Release Notes


6
| Release Notes

Manual Work Palette


The new Manual Work palette works in conjunction with TIBCO InConcert to
provide some workflow capabilities. When you add activities from this palette to
your process, they become available by a custom web interface that has been
added to TIBCO BusinessWorks 2.0.
The functionality is implemented by these new resources:
• Assign Work creates a manual work task and assigns it to a specified pool of
users. An Assign Work activity creates a standard TIBCO InConcert task that
can be worked on with TIBCO InConcert APIs or tools, or with the Manual
Work web interface.

• Download Document downloads any documents that have been uploaded to


an InConcert manual task created with the Assign Work activity.
• Get Work Status can be used to retrieve the current status of a specified
manual task from the TIBCO InConcert server.
• Modify Work is used to change the status of a manual task.
• Wait for Completion is used to wait for an existing manual task to
complete.
• Manual Work Schema defines a schema that can be used by activities in the
Manual Work palette.
For more detailed information, including an example scenario, see the TIBCO
BusinessWorks Palette Reference.

Publishing Activities (TIBCO Rendezvous and ActiveEnterprise Adapter


Palettes)
The TIBCO Rendezvous and ActiveEnterprise publishing activities (e.g. Publish
Rendezvous Message) can now preregister multiple certified listeners. These
activities allow multiple listener names to be specified in the preregister listener
configuration fields. If multiple listener names are specified, they must be
separated with commas, e.g. "listener1,listener2".

Rendezvous Palette
See TIBCO Rendezvous Palette on page 8.

Shared Configuration Palette


Most new activities in the Shared Configuration palette are discussed together
with the activities that use them under that palette’s heading. There are, however,
the following standalone shared configuration resources.

TIBCO BusinessWorks Release Notes


New Features 7
|

XSLT File Activity


XSLT File is a new activity which is used to edit and manipulate XSLT files. It
supports three modes of editing a valid XSLT file.
• Stylesheet mode gives a top-level view of the file.
• Template mode allows one to edit the templates that are contained with in the
style sheet.
• Source mode allows one to edit the XSLT source directly. Any modifications
made here are reflected elsewhere in the XSLT File activity.
In order to use the XSLT File activity, you should use the new Transform XML
activity, discussed in XML Palette on page 9.

SOAP Palette
• Authentication: You can set up the activities in the SOAP palette to use
authentication. The SOAP client and server activities support basic HTTP
authentication as defined in RFC 2617.
— The SOAP Event Source has a checkbox that enables HTTP
authentication. When HTTP authentication is enabled, clients must
provide a valid TIBCO Administrator user name and password to receive
data.
— The Send SOAP Request activity has a checkbox that enables
authentication. The user name and password must be provided in the Send
SOAP Request activity’s configuration panel.

• SOAP Fault.
— A new SOAP Send Fault activity allows you send exception information
from a web service.
— Incoming SOAP faults are presented in an Errors tab in the SOAP Request
Reply activity.

• SOAP Headers. The palette now supports SOAP headers on both client and
server side.
• RPC. SOAP Request Reply activity supports RPC service invocation
• Proxy support. Proxy support for the SOAP Send Receive activity
• Dynamic endpoint URLs. Support for dynamic endpoint URL.
• SSL. SOAP event sources allow you to specify HTTPS connections so the web
service uses a secure channel.
• UDDI. When you import an WSDL File shared configuration resource and
use the Import URL option, you can now specify a URL or choose a UDDI
button to bring up a UDDI browser. The information you specify will then be

TIBCO BusinessWorks Release Notes


8
| Release Notes

used to find the appropriate WSDL file. This feature is included as a


technology preview feature.
• WSIL. When you import an WSDL File shared configuration resource, using
the Import URL option, you can now specify a URL or choose a UDDI button
to bring up a UDDI browser, which also supports WSIL. The information you
specify will then be used to find the appropriate WSDL file.
TIBCO BusinessWorks can also generate WSIL files for a WSIL client. See the
Retrieve Resources activity discussed in TIBCO BusinessWorks Palette
Reference.

TIBCO BusinessWorks Engine


• Checkpointing to database. During deployment configuration, users can now
specify that checkpoint recovery storage is a database. This is required if you
want for multiple engines running on different machines to run in
fault-tolerant more. See the TIBCO BusinessWorks Process Design Guide for
additional information.
• Fault Tolerant mode. Users can now configure their deployment to use
multiple engines in fault tolerant mode. When the engine is started, the other
engines are run in standby mode. When the engine stops, the engine in
standby mode is started. If the engine has performed checkpointing to a
database (see bullet above), it can start at the last checkpoint. See the TIBCO
BusinessWorks Process Design Guide for additional information.

TIBCO Rendezvous Palette


All TIBCO Rendezvous activities now include an Encode as XML checkbox. By
default, it is unchecked.
If checked, the message will be sent as a single TIBCO Rendezvous message field
named xml with type rvXml. Otherwise, the message will be sent as a normal
TIBCO Rendezvous message.

Parse Palette
The new Parse palette provides two activities, Parse Activity and Render
Activity, for parsing and rendering formatted text. The activities can be used to
transform formatted lines of text into a data schema. The text lines can be
formatted either by delimiters separating each field or by offsets that determine
where each field begins and ends. These activities are also useful if you wish to
transform a data schema into a formatted text string.
For additional information, see the TIBCO BusinessWorks Palette Reference.

TIBCO BusinessWorks Release Notes


New Features 9
|

XML Palette
• Transform activity. The Transform activity uses an XSLT style sheet in order
to transform some input (see XSLT File Activity on page 7).
The input document must appear as a base-64 data. The output document will
appear as base-64 as well. Your XML source determines whether the input is
already base-64 or is in XML string format.
In order to use this activity with other TIBCO BusinessWork activities, it is
recommended that one transforms the input into base-64 format (via
string-to-base64 and a Render XML activity). In addition, if the output is to be
used by other activities it must be transformed from base-64 to a tree. This can
be done via the Parse XML activity (and base64-to-string). In the future, the
render and parse operations will be built into the Transform activity.

TIBCO BusinessWorks Release Notes


10
| Release Notes

Changes in Functionality

This section lists changes to product functionality in the following sections:


• TIBCO BusinessWorks Engine
• Palettes:
— BusinessConnect Palette
— JDBC Palette
— Parse Palette
• Mapping from Input tab
• Publishing Activities (TIBCO Rendezvous and ActiveEnterprise Adapter
Palettes)
• XML Schema Parsing
• Documentation

TIBCO BusinessWorks Engine

Test Mode
In test mode, you can now do the following:
• Test multiple processes and multiple jobs at the same time
• Set breakpoints before and after each activity
• Set conditional breakpoints
• Modify process data at a breakpoint
• Persist test setup.
— Breakpoints are now saved automatically.
— If you wish, you can save input setup by clicking a Save button. See the
TIBCO BusinessWorks Process Design Guide for more information.
Test mode also includes capabilities to deal with activities from the Manual Work
palette.

Faults
The TIBCO BusinessWorks engine supports faults
• Some activities now generate faults. Faults are displayed in the Input tab of
TIBCO Designer during design or testing.
• You can use a Generate Error activity to pass specific fault data.

TIBCO BusinessWorks Release Notes


Changes in Functionality 11
|

• The process can return specific fault data.


For additional information, see the TIBCO BusinessWorks Process Design Guide.

BusinessConnect Palette

Send Request Activity


• The Send Request activity now supports asynchronous request reply
• The Send Request activity no longer supports the Generate Transaction
IDoption. The user has to specify the transaction ID in the Input tab.

BusinessConnect Shared Configuration Resource


The BusinessConnect resource (Shared Configuration palette) displays a new
button Refresh Config Data, in the configuration panel. You can click the button
to refresh the resource by retrieving data from the TIBCO BusinessConnect server.

JDBC Palette

NULL
• For Insert and Delete commands, the JDBC update activity supports two
states (Null and not set). For update statement, it now supports three states
for fields at runtime: NULL, not set, and a value. This makes sense because
you may want to update only some fields in a table.
• The JDBC Query activity supports NULL or a value for input. For output the
same values are supported. Use the Use NIL checkbox to view a tree that
mirrors what you saw in TIBCO BusinessWorks 1.1.2

If you used NULL values in a project saved with TIBCO BusinessWorks 1.1.2, you
must select the Use NIL checkbox to see the display your are used to.

• Call Procedure activity now supports NULL input and output for
parameters

Tracing
If you turned on tracing for any JDBC activity using TIBCO Administrator, the
trace that results is much more detailed than it used to be.

TIBCO BusinessWorks Release Notes


12
| Release Notes

Schema Caching
In previous releases, TIBCO Designer refreshed whenever any activity in the JDBC
palette was asked to configure itself. This could potentially slow down the design
process significantly if the database included a large number of schema.
In this release, the JDBC Query activity now supports manual and automatic
refresh modes (check box in configuration panel).
• Automatic refresh goes to the database whenever the developer does
something that might affect schema. When using this mode, you can always
cache all schema by opening them in TIBCO Designer.
• Manual refresh never performs updates unless explicitly instructed.
For both JDBC Query and Call Procedure activities, a Refresh button has been
added to allow you to force a refresh from the database.

Rendezvous Transport Shared Configuration


For a Rendezvous Transport resource (Shared Configuration palette) that has
been set to use RVCMQ, the Worker Tasks field now defaults to 10. It used to be set
to 1, which is a very inefficient setting.

Parse Palette
• The Parse activity has been renamed to Parse Data.

• The Render activity has been renamed to Render Data.

Mapping from Input tab


• When mapping from the Input tab, you now have the option to turn inline
mapping on or off.
• XPath formulas now display namespace prefixes, which were previously
hidden. The mapping and conditions work as before.

XML Schema Parsing


Beginning with TIBCO BusinessWorks 2.0, XML Schema and DTD resource error
checking is stricter than in TIBCO BusinessWorks 1.1.x. As a result, errors that
were not picked up in TIBCO BusinessWorks 1.1.x are now flagged on resource
creation or, at the latest, on process loading time (for existing resources).

TIBCO BusinessWorks Release Notes


Changes in Functionality 13
|

These XML Schema and DTD errors would often cause hard-to-track runtime
errors in TIBCO BusinessWorks 1.1.x. With TIBCO BusinessWorks 2.0, the location
of the error is provided so that the user can correct the schema or DTD resource.

Documentation
• TIBCO Administrator documentation is no longer included with TIBCO
BusinessWorks. You can access TIBCO Administrator documentation from
TIBCO Administrator by clicking the Online Help (?) button. You can also find
it in the TIBCO_HOME\administrator\doc folder. The documentation set
includes three documents:
— TIBCO Administrator User’s Guide
— TIBCO Administrator Server Configuration Guide
— TIBCO Administrator Release Notes
• TIBCO BusinessWorks documentation now includes both a TIBCO
BusinessWorks Process Design Guide and a TIBCO BusinessWorks Palette
Reference.

TIBCO BusinessWorks Release Notes


14
| Release Notes

Known Issues

This section lists known issues for the current release. The information is
organized alphabetically on a per-palette basis.

Description
Adapter Palettes

Association Lists You cannot use association lists in any custom adapter. While there will be no
errors during configuration, you will encounter errors at runtime because association lists are not
supported in TIBCO BusinessWorks.

Error Transition

Error transitions in parallel tracks Currently, the $_error process data produced by an error
transition is global to the process.
This means the result of $_error may be unpredictable if there are error transitions in two or more
parallel tracks.
Workaround Use the transition group to isolate the tracks with error transitions from each other.

General Activities Palette (Call Process)

Changing icon If you change the icon for a Call Process resource and apply the change, it is not
possible to undo the change.
Workaround Delete the Call Process and add a new one.

HTTP Palette

• TIBCO BusinessWorks does not perform key store validation. i.e. expired keys.
• TIBCO BusinessWorks validates the certificate when user imports it, but if certificate expires
after that, it becomes an invalid certificate and TIBCO BusinessWorks does not trust it.
• The key store password must be the same as the keys inside it.
• TIBCO BusinessWorks does not encourage the use of self-signed certificates. If a self-signed
certificate is used, TIBCO BusinessWorks assumes it is coming from a trusted trading partner.
• In this release, TIBCO BusinessWorks only supports Java key stores. P12 key stores are not
currently supported.

TIBCO BusinessWorks Release Notes


Known Issues 15
|

Description
Installation

Domain Inventory not up to date At times, the Domain Inventory is not up to data after
installation. For example:
1. Install TIBCO Administrator only from TIBCO BusinessWorks 2.0.0 on an Windows NT machine.
2. Install TIBCO Designer from TIBCO BusinessWorks 2.0.0 on another Windows NT machine.
3. Install BW Process Engine from TIBCO BusinessWorks 2.0.0 on another Windows NT machine.
4. Install a Siebel Adapter 4.2 (GA) on another Windows NT machine.
When you click on Inventory in the browser, you do not see the components installed in Step 2., 3. &
4.
Workaround Stop and restart the TIBCO Administration Server.

JDBC Palette

DataDirect 3.1 Regression Issue DataDirect 3.1 drivers are bundled with BusinessWorks 2.0 (with
a prefix of tibcosoftwareinc).
If an older version of TIBCO BusinessWorks has been used to access a SQL server stored procedure
with numeric or decimal type output parameters, an input value must be provided for such
parameters in order to use them in TIBCO BusinessWorks2.0.
Case # 15003461 has been filed with DataDirect to fix this regression.

Optional Standard Procedure arguments Optional standard procedure arguments are not
supported. If one of the arguments is missing, the standard procedure cannot be executed.

For Oracle, calling arguments or return values of the PL/SQL types TABLE (now known as
indexed-by tables), RESULT SET, RECORD, or BOOLEAN is not supported. For more information,
please visit http://otn.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm

Inserting large BLOBs If inserting / updating a huge BLOB fails, activity timeout may need to be
adjusted to allow sufficient time to finish the operation

DML statements. If DML statements are used with SQL Direct activity, using 8.x versions of Oracle
thin / thick drivers doesn’t work in some cases.
Workaround Upgrade to 9.x drivers. Note that 9.x drivers work with 8.x and 7.x databases, so only
the driver must be changed.

TIBCO BusinessWorks Release Notes


16
| Release Notes

Description

The UnresolvedResultsets output parameter can be used to utilize the result sets returned by
stored procedures. It represents records in return result sets as an XML string. Since the structure of
the XML string is unknown at design time and no mapping can be done if the schema is unknown,
use the workaround to overcome the problem.
Note: At this time, only stored procedures that always generate a fixed schema can be utilized
Workaround
1. Configure the Call Procedure activity.
2. Add a Write File activity
3. Configure a Write File activity to write a text file, provide a local file name with .xml
extension.
4. Map unresolved result sets from call activity’s output to textContent input field in the Write
File activity.

5. Execute the process definition. Upon successful execution, all records are written to the specified
XML file in a predefined format
6. Open the XML file in XML Authority as a schema. XML Authority generates a schema based on
the contents of the XML file (or create the schema manually using the structure provided in the
XML file)
7. Create a schema definition resource using the newly generated schema.
8. Add a Parse XML activity. In the Configuration tab, select the newly created schema definition
and type Resultsets in the Element field
9. Map unresolved result sets from the Call Process activity’s output to the Parse XML activity’s
xmlString input field.

Result sets can now be utilized at design time from the output of the Parse XML activity.

Stored procedure custom exceptions A JDBC Call Procedure activity throws a generic exception
for any custom exceptions raised in stored procedures. The exception thrown is driver specific.
Below are the error messages thrown for each combination of database and driver:
Data Direct Oracle: JDBC error reported (SQLState = HY000)
Thin Oracle: JDBC error reported (SQLState = 72000)
Data Direct MSSQL: JDBC error reported (SQLState = HY000)

Max rows not supported While working with Oracle stored procedures, the max rows property is
not supported by the Oracle thin driver.
Workaround Use the Data Direct driver included with the release.

TIBCO BusinessWorks Release Notes


Known Issues 17
|

Description
JMS Activity

When using TIBCO Enterprise for JMS, the user must define user name and password and same
user ID for JNDI user and same password for JNDI because TIBCO Enterprise for JMS is asking for
it and using it.

Mail Palette

Receive Mail attachments (Japanese) When email is received that was sent by Netscape
Navigator on a Japanese machine, the content of any attachments is corrupt in the Receive Mail
activity.

Manual Work Browser GUI

Returning to login screen. The GUI sometimes returns you to the login screen. For example, When
you select a document in the Manual Work TIBCO Administrator GUI, then click to open the
document, you may be returned to the login screen. This issue is rare and not reliably reproducible.
It is under investigation.
Creating new browsers You are logged in as userA (in TIBCO Administrator or the Manual Work
browser GUI) in browser window windowA. You then open a new window from the browser
(File->New Window menu option). The new window displays an error that the page has expired.
The exact message depends on the browser.
If you now type the url http://machine:8080 in the window and then log in as userB, windowA’s
session is also switched to have user B as the user. WindowA still displays the fact that userA is
logged in. However, in the Acquired, Ready and Completed lists, you will see userB’s tasks in
windowA.
Workaround If you open a new browser window by running the program again (Microsoft
Internet Explorer or Netscape Navigator) this problem does not occur.

Manual Work activities are not supported on AIX because the IC Java JNI library is available. As a
result, errors result. For example, if the user tries to drag and drop a Manual Work activity into the
design panel.

Mapper

Design-time validation The mapper does not support design-time validation of string length
constraints. It also does not validate maximum and minimum (inclusive and exclusive) constraints
on numbers.

TIBCO BusinessWorks Release Notes


18
| Release Notes

Description
Schema Datatypes

The following XML schema are supported but not currently being validated:
• gYearMonth, gMonthDay, duration, time, gYear, gDay, gMonth.

This means that illegal values may be allowed when parsing XML and propagated through
bindings or in XML output.

Shared Resources

XSLT File activity


• For each individual mapping in the template input tab, you must click Apply for the mapping
to take effect.
• A name is required when creating a new template. It is not enforced however.
• The stylesheet configuration form toggles back to configuration tab as soon as a parameter is
added.
• The Cardinality field available in the parameter editor is not used.
• There are some valid XSLT's that the editor cannot handle. In that case, the editor displays a
warning. You need to select the source tab and edit them manually.

Java Custom Functions will only work with the following restrictions:
• Only static methods are available.
• Only methods with the primitive types (int, String, Boolean, etc) are available.
• Only methods that do not throw exceptions are available.
• Loaded classes can not refer to any other classes (including inner classes).
• A class file, once loaded and saved as part of a project, does not point to the original file. In
order to change the class file in the project, it must be reloaded.
• Two class files which represent the same class (i.e. they have the same package name and class
name) cannot be loaded into the same repository.
• Xalan does not use the Java Custom Function activities. If the mapping you create requires
Xalan, then all calls to custom functions will fail.
• Java Custom Function does not support copy/paste.
• A Java Custom Function created with the pre-release versions of the product will not load into
the 1.1 version of the product.
• If you create a Java Custom Function with the same prefix as any other Java Custom
Function in the repository, the new Java Custom Function will not be available.

See the TIBCO BusinessWorks Process Design Guide for information on using Java Custom Function
activities.

TIBCO BusinessWorks Release Notes


Known Issues 19
|

Description
Connection Shared Resource.
When you open a saved project, the Repository Name, Installation Name, and Protocol Name
fields in the Configuration tab do not contain the original list of choices. They contain only the
saved selection.
Workaround To refill the list of choices, press the Load Repository List, Load Installation List,
and Load Protocol List buttons (in that order). The list of choices refilled will be based on the values
of local and remote repository discovery fields (i.e. fields below the Show Advanced check box).

Schema Definition Shared Resource


When a Schema Definition resource is exported, not all the schemas which it may reference are
exported.

SOAP Palette

Certain SOAP features are not supported (some because the standard is moving away from them):
• Document style soap-encoded operations.
• WSDL ArrayType.
• SOAP 1.2 is not currently supported.
• SOAP attachments are not supported.
• SOAP RPC with literal
• The server cannot act as an RPC-style SOAP server.
• The server does not allow implementation of WSDL using message parts as type.
• The server cannot implement multiple operations in a single service.
• The client cannot call faults with type defined in WSDL
• Document style SOAP-encoded operations are not supported

• The input/output/faults/headers types cannot be specified using type any.


• The SOAP palette does not support PRE-CR XSDs.
• The SOAP palette does not support services which use document encoding and specify their
input/output type using multipart messages.

A message with a required empty complex type part throws a validation error.
Workaround Bind with a complexType data e.g., _globalVariable

Headers and faults have limited support for SOAP encoding. For example, the Href attribute is not
supported for fault details or header elements.

The SOAP event source allows only one header to be specified for an operation’s input or output

TIBCO BusinessWorks Release Notes


20
| Release Notes

Description
The basic HTTP authentication feature available via the Use Basic HTTP Authentication check
box works only with server-based projects. It does not work with local file projects.

SOAP UDDI is included as a technology preview feature.

SOAP over HTTPS is included as a technology preview feature.

XML Palette

Some of the input and output for the XML Transform activity is of type binary. If you are passing a
string to the activity’s input, use the string-to-base64 function. If you are retrieving the activity
output, you must use the base64-to-string function if you wish to manipulate the output as a
string.

XPath

TIBCO BusinessWorks is fully compliant with the XPath 1.0 specification for comparing booleans.
The resulting behavior is counter-intuitive.
Here is an example for writing expressions comparing boolean data values. Assume this is part of
your process data:
$MyResult/
aBooleanValue
... so aBooleanValue is a boolean inside of the variable $MyResult.
The cleanest expression for a boolean condition based on this input is:
$MyResult/aBooleanValue = ’true’
The expressions:
$MyResult/aBooleanValue = true()
boolean($MyResult/aBooleanValue) = true()
string($MyResult/aBooleanValue)=true()
$MyResult/aBooleanValue
will, according to the XPath specification, always return true. Specifically:
• In the first two cases the test is if the element aBooleanValue exists.
• In the third case, the test for comparing a string to a boolean is if the length(string)>0, so this
is true for both true and false values.
• The fourth case is equivalent to boolean($MyResult/aBooleanValue) and, like the first two,
tests for the existence of aBooleanValue rather than its string value.
There is no workaround. This is how the specification defines the behavior.

TIBCO BusinessWorks Release Notes


Known Issues—Deployment Palette 21
|

Known Issues—Deployment Palette

This section lists issues that are open in the named releases and provides
workarounds where known.

Description
Reset button The Reset button for certain fields in the deployment palette does not function as it
should. Clicking the Reset button should return to the previous applied state. However, in the
configuration panel, when you add an engine to an FT group, or when you change the password
and click on Reset, these fields are not reset.

Duplicate process engine names Process Engine resource names must be unique across all
machines within a deployment configuration. Previous versions of TIBCO BusinessWorks allowed
you to create Process Engine resources with the same name on different machines.
When you attempt to rename a Process Engine resource, this release will prevent you from
renaming the resource if the resource with the same name exists within a different machine and if
you attempt to rename the resource on the Configuration tab. If however, you attempt to rename
the resource in the project tree panel, no warnings or errors are given and the renaming succeeds,
however, deployment will fail.
Workaround Ensure that all Process Engine resources have unique names across all machines
within your deployment configuration.
Do not attempt to rename a Process Engine resource so that it has the same name as another
Process Engine resource on a different machine.

Non-English characters You can use only English characters for TIBCO BusinessWorks Process
Definition names.

Otherwise, they may not display correctly on TIBCO Administrator.


Workaround Use English characters.

CPU tab In the TIBCO Designer Deployment palette, the Monitor resource’s CPU tab does not
include the Processor field that is available on other platforms.

Deleting machine If you delete a machine that has deployed components in the Deployment
Configuration from TIBCO Designer, you can no longer modify or undeploy these components.

Workaround Add the machine back to the Deployment Configuration and recreate components
using the same names as the deployed components. You can now undeploy and redeploy.

Wrong value in Advanced tab If you enter a wrong value in the Advanced tab of the Deployment
palette and click Apply, an error is correctly thrown but the Apply button becomes disabled even
though no changes were made.
Workaround Correct the value(s), then click Apply again.

TIBCO BusinessWorks Release Notes


22
| Release Notes

Description
Select All In the Process Definition tab of Deployment palette, even if the Select All button is
checked, the grid is not updated to show the processes.
Workaround If all the process definitions need to be added and selectively enabled or disabled,
you have to add the processes one by one to be able to see them in the grid.

Installing Administration Components By default, the TIBCO Business Works installer has the
Administration Components option checked in the list of components to be installed, even if that
component already exists in the TIBCO administration domain. If you fail to uncheck this option on
a machine that is already part of an existing domain, the machine is added to two domains and
deploying an running components no longer works properly.
Workaround Be sure to deselect the Administration Components option if the machine is already
joined to an administration domain.

Microagent service The TIBCO Runtime Agent (TRA) uses the TIBCO Microagent for monitoring
of component instances. By default, the Microagent service is started when the TRA is started,
however, if you encounter problems, check that the Microagent is running.
Workaround Check your Microsoft Windows Services panel and make sure the TIBCO
Microagent service has been started.

Multiple deployment configurations Multiple deployment configurations for the same project are
not supported.
Workaround Rename the project before you test a second deployment configuration.

Machine resource When you drag a machine resource into the design panel, it may take up to 10
seconds for the machine to appear. Do not to move the mouse out of the range of the panel during
this period.
Workaround Do not move the mouse out of the panel.

Orphaned services Undeploy your project before you delete projects or uninstall TIBCO
BusinessWorks, as this will remove the services gracefully. If you have orphaned services, contact
customer support.
Workaround Undeploy the project.

TIBCO BusinessWorks Release Notes


Closed Issues 23
|

Closed Issues

This section lists issues that were closed in the TIBCO BusinessWorks 2.0.0. The
information is organized alphabetically on a per-palette basis, even though many
issues refer to the runtime behavior of the activities. General TIBCO
BusinessWorks engine issues are listed under.

Closed in
Description of Fix
Release
File Palette

The Include Existing Files option in the File Poller resource did not work
properly. The File Poller created events even if the option was not checked.
This has been fixed.

General Palette

The Java Code activity used to delete class files when you viewed the source, then
closed the editor. This has been fixed.

JDBC Palette

2.0.0 When using an Oracle driver, applications experienced retry issues with certain
situations. This problem has been fixed.

2.0.0 SQL TIMESTAMP is now supported.

2.0.0 When the update activity was configured to delete/insert/update all rows, it used to
only affect one row. It now correctly affects all rows.

2.0.0 Oracle 8.0.5 stored procedures are now supported.

JMS

If the JMS server went down and is restarted, the TIBCO BusinessWorks activities did
not recover. This has been fixed.

TIBCO BusinessWorks Release Notes


24
| Release Notes

Closed in Description of Fix


Release
Rendezvous Palette

• RVCM Confirm activity can now confirm messages received by RVCM subscribers
that use wildcard subject names.
• RVCM preregistration is now possible for subject provided as runtime input (in
addition to subject in configuration).
• RVCM name and sequence number are available as runtime output from
Rendezvous process starter and wait activities for RVCM and RVCMQ transports.

Shared Configuration Palette

2.0.0 If the BusinessConnect Connection resource has no changes to apply, reloading of


the protocols does not update the operation details of the shared configuration in the
project.
Users can now click the Refresh Config Data button at any time for an update.

2.0.0 After a schema definition shared resource is created, it could be renamed or moved to
other folders after it was referenced by any activity or inline schema.
This has been fixed.

2.0.0 When a Schema Definition resource was exported, not all the schemas which it
referenced were exported. This has been fixed.

SOAP Palette

2.0.0 RPC SOAP encoding is now supported.

2.0.0 Href handling for SOAP encoding is now supported.

2.0.0 There is now support for attributes in operation’s input or output parts.

XML Renderer and Parser

2.0.0 When you load an XSD file with double-byte schema field names, some extra
characters appeared at the end of the Schema contents field. This has been fixed.

2.0.0 For already configured Parse XML activities, before you changed the input style from
text to dynamic or binary, had to remove the mapping in Input tab first. If you did
not remove the mapping, then the old values are erroneously kept.
This has been fixed.

TIBCO BusinessWorks Release Notes


Migration 25
|

Migration

When you upgrade TIBCO BusinessWorks and TIBCO Administrator to version


2.0, the upgrade does not uninstall earlier versions of TIBCO Administrator and
TIBCO BusinessWorks. The 1.x projects that are running will continue running
and can be monitored with TIBCO Administrator 1.1 until you redeploy them.

The version in the Domain Inventory will show as 2.0 because 2.0 was installed,
but the version used will be 1.x. This is a known issue.

To completely upgrade, upgrade each component in the domain inventory for the
TIBCO administration domain, then migrate all projects.

Migrating Projects
To migrate your projects to TIBCO BusinessWorks 2.0, follow these steps:
1. Stop all running projects
2. Undeploy all deployed projects.
3. Install TIBCO BusinessWorks 2.0.
4. Open TIBCO Designer and deploy projects you wish to deploy.
5. Open TIBCO Administrator and restart process engines and adapters.

You can also leave your projects running (and deployed) and stop and redeploy
them after you have installed TIBCO BusinessWorks 2.0.

JDBC Query
If your project includes a JDBC Query activity that queries for NULL, use the new
use NIL checkbox for a comprehensive tree view of the query in the Output tab.

Java Activity
When you migrate a project created with a 1.x version of TIBCO BusinessWorks,
you must manually edit all java activity classpaths. To do so, click on the
classpath button in the java activity configuration and replace all paths that start
with C:/tibco/bw/1.0/ with C:/tibco/bw/2.0/

TIBCO BusinessWorks Release Notes


26
| Release Notes

Internationalization

TIBCO BusinessWorks 2.0.0 supports double-byte characters in some of the


activities that customarily contain text strings. This section contains an overview
of requirements, things you can do, and known issues.
A TIBCO BusinessWorks Internationalization FAQ document is now available
from www.support.tibco.com.

Requirements
• Server-based projects—If you use double-byte characters, you need to change
the repo.encoding parameter in the file
$TIBCO_HOME$\administrator\version\config\administrator.propert
ies to UTF-8. This is required for saving server-based projects, deploying
projects, and running projects.
• Local File projects—For local file project, the encoding set in Repository
Finder is used for TIBCO Rendezvous encoding. By default, there is no
explicit value and the value ISO8859-1 is used. You can explicitly set the value
to UTF-8 to support sending and receiving double-byte characters via TIBCO
Rendezvous.

Usage Notes
• XML Renderer and XML Parser Activities
— Binary mode is recommended for parsing and rendering XML files that
contain non-ASCII data
— In the current release, the double-byte content in the output string of the
Render XML activity can not be viewed properly in text mode. This will be
fixed in a future release.
— In the text mode, the content of the output string of the Render XML activity
is encoded in UTF-8 and there is no way to change that. If you want to
encode content in an encoding other than "UTF-8", binary mode is
recommended.
— In an XML file, the valid encoding is Shift_JIS (with an underbar) not
Shift-JIS (with a hyphen).
• File Activities
— File Poller and Wait for File Change activities

TIBCO BusinessWorks Release Notes


Internationalization 27
|

If the value for the Content as: field is text, the user can now select the
encoding in the Encoding field. This encoding value is used to read the file
contents. The Output tab will then show the encoding for the file contents in
the encoding subelement of the fileContent element.
— Read File and Write File activities
For text files, the encoding to read/write the file can be specified in the Input
tab in the optional Encoding field. The Output tab will then show the
encoding for the file contents in encoding subelement of the fileContent
element.
• File names
Note the following about double-byte file name support
— Project name (.dat) — not supported
— Names used in file activities — supported
— XML file name (.xml, .xsd) — supported
• XPath Expression
The TIBCO Designer GUI allows you to use XPath expressions in many
locations (process parameters, return values, conditions in conditional
transitions, etc.) Double-byte characters are supported in all these locations.
• Java Code
Hard-coded double-byte data is now allowed in Java source code. Besides
this, most Java locale-sensitive classes and methods are also supported.
• TIBCO Designer Display Font
In the TIBCO Designer Edit > Preferences > View tab, there are two kinds of
fonts, UI Font type and Script Font type
Script Font type is used for display characters in the configuration panel
and XPath Formula Editor. If double-byte characters are displayed as
rectangles in that area, choose an appropriate Script Font, then exit and
re-open TIBCO Designer for the change to take effect.

TIBCO BusinessWorks Release Notes


28
| Release Notes

• HTTP Activities
— HTTP Receiver—Both the HTTP request URL (including attributes) and
post data could be non-English data. This activity will look to the
Content-type header of the incoming HTTP request for the encoding
information; if there's no Content-type header in the incoming HTTP
request, it will use the system default encoding to decode the non-English
data.
— Wait for HTTP Request -- the same as HTTP Receiver.

— Send HTTP Request—Allows users to send HTTP URL and Post data
containing non-English data. You must specify the encoding (charset) in
the Content-Type header, otherwise, a default Content-type header will
be generated and UTF-8 will be used as the encoding of the outgoing HTTP
request.
Non-ASCII data in HTTP Request URL (including attributes) are not
%HH-escapedyet (the URL encoding).
— Send HTTP Response—Allows users to send an HTTP response in
double-byte characters. You must specify the encoding (charset) in both the
charset field and the Content-type header for the response, otherwise,
UTF-8 will be used by default
— A defect about the default behavior of the Send HTTP Request activity
reported for release 1.1.2 has been fixed. This activity used UTF-8 to decode
a reply from an HTTP server, even when no charset information was
included with the reply. In Release 2.0, the system locale encoding is used
as the default encoding.
• FTP Activities
— FTP Put—Allows users to transmit a double-byte file to an FTP server
using non-binary mode. Users must specify the encoding for the file; this
could be the encoding of the original local file.
— FTP Get—Allows users to retrieve a double-byte file from an FTP server
using non-binary mode. The user must specify the encoding of the file on
the server.
• JDBC Activities
— JDBC Query and JDBC Update now support double-byte data in table
name, column name, and value.
The DataDirect Oracle JDBC driver, which is available if you choose
tibcosoftwareinc.jdbc.oracle.OracleDriver as the JDBC ID has problems in
some circumstances. For example, if the database’s encoding is EUC-JP,
even ASCII data cannot be inserted correctly.

TIBCO BusinessWorks Release Notes


Internationalization 29
|

• SOAP Activities
— Allow users to send and receive non-ASCII data using UTF-8 encoding in
both DOC mode and RPC mode. This is transparent to the user; nothing
needs to be set for SOAP activities.
• JMS Palette
— This release of TIBCO BusinessWorks was tested only using the TIBCO JMS
Server 2.0.1.
Manually copy /tibco/jms/java/jms.jar and
tibco/jms/java/tibjms.jar (from the TIBCO JMS 2.0.1 installation) to
bw/1.1/lib/ext.

JAR files from TIBCO JMS 1.1 installation do not support double-byte
characters.
The TIBCO JMS server does not support topic name in double byte.
• Deployment Palette
— You can use only English characters for TIBCO BusinessWorks Process
Definition names. Otherwise, they may not display correctly in TIBCO
Administrator.

Documentation
• The TIBCO BusinessWorks Concepts document is now available in Japanese.
The Japanese version is included in the release tree.
• Additional documents are being translated.
• For additional information on setting up your system to support
internationalization, contact support@tibco.com.

Issues
On the CJK Solaris platform, CJK characters are not allowed to be input directly
into the SQL Statement window. You can use space holder (question mark)
instead, and input CJK characters in the Input tab.

TIBCO BusinessWorks Release Notes


30
| Release Notes

Using Non-Default TIBCO Rendezvous Parameters

When you install TIBCO BusinessWorks 2.0.0, you can specify non-default TIBCO
Rendezvous parameters for the TIBCO administration domain during
installation.
• If you keep the default parameters, already installed adapter can join the
TIBCO Administration Domain with no problems because both TIBCO
Administrator and the adapter will then use the default TIBCO Rendezvous
parameters.
• If you change the TIBCO Rendezvous parameters, you can use TIBCO
BusinessWorks standalone with the new settings. Any adapters you install
afterwards on the same machine will use the same settings.
If adapters need to join an administration domain using non-default TIBCO
Rendezvous parameters, it is recommended you proceed as follows:
1. Install TIBCO Administrator and the adapter using the default TIBCO
Rendezvous parameters.
2. Using the domain utility, change the TIBCO Rendezvous parameters for
TIBCO Administrator to the desired settings.
3. Using the domain utility, change the TIBCO Rendezvous parameters for the
adapter to the desired settings.
The domain utility and associated documentation is available in the
tra/version/tools folder.

TIBCO BusinessWorks Release Notes


Adapter Compatibility 31
|

Adapter Compatibility

TIBCO BusinessWorks 1.1.1 and 1.1.2 require version 4.1.0_02 (or later) of
adapters. You need to install TIBCO Designer 4.1.2, which includes all the
infrastructure upgrades to work with Deployment and Monitoring in TIBCO
BusinessWorks 1.1.1
Do not use version 4.1.0 adapters. Version 4.1.0 adapters will NOT join the
domain on UNIX systems. There were also other installation issues with 4.1.0 and
4.1.0_02 resolves these installation issues.
Please contact support if you have any questions about the version to use.

Replacing a Pre-GA Version

If you installed releases of TIBCO BusinessWorks before the 1.1.0 GA version (e.g.
the 1.0.0 CA version), delete all files after you uninstall the product. Be sure that
all files in tibco_home/bw/1.0/lib and in tibco_home/tra/1.0/lib have been
removed. Some pre-release versions included library files that can cause problems
with TIBCO BusinessWorks 1.1.1 or 1.1.2.

TIBCO BusinessWorks Release Notes


32
| Release Notes

TIBCO BusinessWorks Release Notes

Vous aimerez peut-être aussi