IBM
Rational Synchronization Server 1.4.0.5 readme
|
IBM Corporation
March 12, 2014
|
© Copyright IBM Corporation 2006, 2014
U.S. Government Users Restricted Rights - Use, duplication, or disclosure restricted
by GSA ADP Schedule Contract with IBM Corp.
This file contains last-minute product information and updates to the IBM
Rational® Synchronization Server™ 1.4.0.5
It is divided into the following sections:
For the latest news and information on Rational Synchronization Server,
visit the Web site at http://www.ibm.com/software/rational/support/.
System
requirements
To run Rational Synchronization Server, you will need:
- One of the following operating systems installed on
your computer:
- Windows® 2003
- Windows Vista Enterprise
SP1
- Redhat Linux Enterprise
5.0
- Solaris 10
- SUSE Linux Enterprise Server
11
- One of the following Web browsers:
- Internet Explorer® 8 and 10
- Firefox® ESR 10 and 17
At the time of writing, the third party products tested with Rational
Synchronization Server are:
- Apache Tomcat™ 5.5.x and 6.0.x – 32-bit only if using
the Change-ClearQuest synchronizer
- Java runtime
environment (JRE) 6.0
Operating system
locales supported by Rational Synchronization Server
The Rational Synchronization Server is certified
only in the following locales:
- Japanese
- Korean
- PRC/Simplified/GBK
Chinese
- Traditional/Big-5
Chinese
- Chinese
- Taiwanese
IBM supports use in any locale using the Latin-1 character set or the
Windows extension CP 1252; however, such locales have not been tested.
Compatible products
Rational Change for Focal Point Interface
- Rational® Focal Point™ 6.4, 6.5 and 6.6
- Rational® Change™ 5.2 and 5.3
Note: Rational Change for Focal
Point Interface does not support use of remote Change databases.
Rational Focal Point for Focal Point Interface
- Rational® Focal Point™ 6.4, 6.5 and 6.6
Rational Focal Point for DOORS Interface
- Rational® Focal Point™ 6.4, 6.5 and 6.6
- Rational® DOORS® 9.3, 9.4 and 9.5
Note: Rational
Focal Point for DOORS Interface is only supported when Rational Synchronization
Server is installed on Windows.
Rational Change for Change Interface
- Rational® Change™ 5.2 and 5.3
Note: Rational Change for Change
Interface does not support use of remote Change databases.
Rational Change for
Rational Team Concert Interface
- Rational® Change™ 5.2, 5.3 and 5.3.1
- Rational® Team Concert 4.0.1, 4.0.2, 4.0.3, 4.0.4 and
4.0.5
Note: Rational Change for Rational
Team Concert Interface does not support use of remote Change databases.
Rational Change for ClearQuest Interface
- Rational® Change™ 5.2 and 5.3
- Rational® ClearQuest 7.1 and 8.0
Note: Rational Change for ClearQuest
Interface does not support use of remote Change databases.
Installing Rational
Synchronization Server
Note: If you have Rational
Synchronization Server already installed, you must uninstall it before
installing this version. Uninstalling Synchronization Server will not remove
links, templates or log files.
Prior to installation, ensure that you have the following
environment variables set correctly:
·
JAVA_HOME – path to a Java 6 JDK
OR
·
JRE_HOME – path to a Java 6 Runtime Environment
·
CATALINA_HOME – path to your Tomcat installation
·
DOORSHOME – path to a DOORS client installation. This variable is only
required if you will be installing the Rational DOORS for Focal Point
Interface.
After you have verified your environment, run the correct
binary for your platform. For windows, run sync_server_install.exe.
Note: Do not install the
Synchronization Server on the same Tomcat installation where Focal Point is
installed.
After the installation program initializes, you will be
presented with a welcome screen. Click Next to continue.
Next you will be asked to accept the license agreement.
Accept the terms and click Next.
You will be asked to choose the type of installation.
Choosing Typical will install the
Synchronization Server along with the Rational Change for Change Interface,
Rational Change for Focal Point Interface, Rational DOORS for Focal Point
Interface, Rational Focal Point for Focal Point Interface, Rational Change for
Rational Team Concert Interface, and Rational Change for ClearQuest
Interface. Choosing Custom will
allow you to determine which components you’d like to install. Choosing Minimal will install by default only
the Synchronization Server.
The components that will be installed will have a checked
checkbox next to the Synchronizer’s name. You may change the components that
you want installed by clearing the checkbox next to the name.
Click Next when you are satisfied with the components that will be
installed.
Next, you will see a summary of what will be installed.
Click Install to continue the
installation.
When the installation is complete, you will see a summary
dialog. Click Done.
Note: If you are installing
Synchronization Server on Solaris and you wish to use an IBM Java Runtime
Environment (JRE), you must follow these additional steps:
- Go to $CATALINA_HOME/bin
- Open setclasspath.sh in a text editor
- Find this line:
JAVA_ENDORSED_DIRS="$BASEDIR"/common/endorsed
- Change the line to:
JAVA_ENDORSED_DIRS="$BASEDIR"/common/endorsed:"$JRE_HOME"/lib/endorsed
- Restart your Tomcat server
Rational Synchronization Server
Administration
To configure the Synchronization Server, you can use the
web-based admin interface. You can access the admin interface by pointing your
web browser at http://localhost:<port>/TlogicIntegration/admin/SyncFramework.html,
where <port> is the port number
your Tomcat server is running on. You will be required to login to access the
admin interface. Any user that has
“administrator” role in Tomcat is valid.
Tomcat users are defined in CATALINA_HOME/conf/tomcat-users.xml.
For more details refer to Rational Synchronization Server
Help available from the admin interface.
Uninstalling Rational
Synchronization Server
Before uninstalling the integration, you should stop your
Tomcat server to ensure that all synchronizers are stopped.
On Windows, open Add/Remove
Programs from the Control Panel. Find Rational
Synchronization Server and click Remove.
On Linux and Solaris, run the following command: $CATALINA_HOME/webapps/TlogicIntegration/_uninst/Uninstall_IBM_Rational_Synchronization_Server_1.4.x.x
New Features
Improved Attachment Handling
If an attachment is removed from one of the synchronized
objects, then it shall be re-attached again until and unless it is removed from
both the objects. This behavior has been changed such that, if an attachment is
removed from one of the synchronized objects, instead of re-attaching the
attachment, it shall be removed from the other object as well.
Note: If an
object has more than one attachment with the same name, than attachments
handling does not work properly as there are technical limitations in handling
multiple attachments with same name.
Stoppable Synchronizers
The synchronizers hosted on the Rational Synchronization
Server can stop processing immediately and gracefully exits when a stop signal
is received from Tomcat server. The stop signal can be either passed by
stopping the Rational Synchronization Server application from Tomcat’s manager
page of the Tomcat UI or shutting down the Tomcat server.
If there is a synchronizer actively running and a stop
signal is received, then it shall gracefully process the current object
completely before stopping the process. The objects which are not processed
shall be picked in the subsequent runs, once the synchronizer is started again.
Problems Fixed
Rational Synchronization Server
1.4.0.5 fixes the following problems:
- PI05361 (R45569): Wrong
user getting used by the RSS synchronizers
- PI06392 (R45459): Memory
leak observed in RTC client library v3.0, so need to upgrade RTC client
libraries.
- PI06397 (R45461): RSS
crashes when multiple synchronizers are turned on
- PI08512 (R45535): RSS
Console Displays Wrong Timezone
- PI08642 (R45540): When
the stop button of a particular synchronizer is clicked, the RSS stops
logging for other actively running synchronizers.
- PI11704 (R45676): In
certain cases failed objects are not added to pending list
- R44275: When selecting
RTC link file, rtc template file and template
file name from RSS UI path is not picked correctly.
- R45669: Migrated RTC workitem holds HTTP url of the change-request instead of OSLC url.
- R45789: Synchronization
server is unable to create new elements in Focal Point from Change.
- R45794: Possible memory
leak in handling RTC work-items.
Rational Synchronization Server
1.4.0.5 also includes all fixes from Rational Synchronization Server 1.4.0.4
iFix001
- PM87289 (R44468):
Rational Synch Server Hangs 1.4.0.3 -1.4.0.4
- PM94800 (R44959):
Rational Synchronization Server is not handling rtc_target_date
properly resulting in potential incorrect sync.
- R44501: Request for
Enhancement: Attachment Deletion/Recreation
- R44205: Client would
like attachment caching directory configurable.
- R45072: Support to stop
the synchronizers gracefully when a stop request is notified from tomcat.
- R44233: If sync fails
during synchronizing the attachments, then the object is not considered as
failed sync.
- R44751: Attribute
values shown for Task links in RTC should be configurable.
- R45021: Attachment name
is prefixed with the temp folder name.
- R45073: Pending sync
list not getting updated for "migrated" records.
- R45112: Task is not
re-associated to Change from RTC, when deleted from Change.
Rational Synchronization Server
1.4.0.5 also includes all fixes from Rational Synchronization Server 1.4.0.4
- PM71993 (R43548): Loss
of mappings during project area change.
- PM82909 (R44206):
Document the behavior of attachment synchronization which downloads the
file to user's home directory temporarily.
- R27560: Change-Change
Synchronizer 1.0: Some fields are not visible in Link Settings.
- R28655: Delete the view
rule of the module in Focal Point and perform the synchronization process;
displaying exception errors in link log file details.
- R34484: Update the
Synchronizer option (Time Unit) for a sync process, the modifications are
not picking up even after the sync process is stopped and restarted.
- R35078: Can't set a
RATLC CR to Fixed in Change.
- R36360: RTC-Change:
'Rational' is misspelled as ‘Ration’ in link setting configuration page of
IBM Rational synchronizer server 1.4
- R36361: RTC-Change: The
CRID and CR URL fields displays other details apart from the ID and URL in
RTC work item
- R36363: RTC-Change:
"Release" field displays other details apart from the Release
Version in Change CR
- R36390: Note added to
CR repeated thousands of times
- R40568: Problem
Communicating with DOORS 9.3 using Synchronization Server
- R40790: Rational
Synchronizer Server support on SUSE 11
- R41381: Product version
mentioned in help document is wrong
- R41565: Intermittently
encountering error while clicking on "refresh" button.
- R42090: Upgrade GWT to
2.4.0
- R42523: There should be
a way to limit the size of sync log file.
- R42553: Update docs to
explain RTC server rename issue
- R43234: Link Synergy
tasks associated with CR to the work item
- R43348: Not able to
create a synchronizer through Mozilla Firefox browser.
- R43787: Associated
text/images missing for multiple pushbuttons.
- R43789: Rendering
issues in IE and FF browsers.
- R43803: Support OSLC-url instead of HTTP-url on
URL mapping attribute of adapter-items.
- R43808: Synchronization
does not handle the associated tasks.
- R43828: RSS application
name needs to be displayed in the web-server where it is hosted.
- R43830: RTC related jar
file is missing in the build.
- R43834: Rational
Synchronization Server fails to connect to DOORS.
- R43839: Include the jar
file in RSS which is related to Synergy-RTC integration.
- R43843: Rational
Synchronization Server fails to connect to DOORS 9.5 release.
- R43844: Rendering issue
on Focalpoint related synchronizers.
- R43885: Rational
Synchronization Server fails to connect to FP.
- R43905: Using OSLC url instead of http url of a change request should be restricted to
Change-RTC synchronizer.
- R44049: After RSS is
installed, tomcat startup reports some warnings.
- R44069: Not able to
choose/select the template or links in the change-fp
integration.
- R44111: Change-FP sync
fails when no query is given
- R44120: Error reported
in log when Sync State
is turned off in RTC Change state mapping.
- R44156: Update readme
document with specific information about synchronizing synergy tasks.
- R44260: Add more debug
messages to RTC api layer.
Rational Synchronization Server
1.4.0.5 also includes all fixes from Rational Synchronization Server 1.4.0.3
iFix001
- R42720: Synchronization
and migration fail when a mapped attribute in Rational Change contains unicode characters and has more data than the
allowable number of bytes for the attribute in Rational Team Concert
- R43322: Synchronization
and migration fail when transition-log in Rational Change has huge data
than the allowed number of bytes for the comment history in Rational Team
Concert.
- R43347: Only half of
32kb (transition-log) data is getting migrated/synchronized.
- R43516: Failed objects
should be picked up by next immediate run of synchronization.
- R43564: Not able to
migrate existing workitems from RTC to Change if the id map attribute is
created newly.
Rational Synchronization Server
1.4.0.5 also includes all fixes from Rational Synchronization Server 1.4.0.3
- PM49155 (R41508): Not
all failed updates are recorded as failures to be synchronized again
- R41402: New Change
database is not listed on Change-RTC synchronizer.
- R41509: Mechanism to
selectively synchronize record/field changes that would not be normally be
identified by the sync process
- R41563: Change-RTC
synchronizer Shows null pointer exception when login to Change fails
- R41574: User logs
should mention that user has no admin privileges when mirating between
Change and RTC
- R41583: Sync server log
does not say that Change or RTC servers are stopped
- R41616: Mapping of RTC
attribute "Type" must not be allowed.
- R41923: Change-RTC sync
fails if there is an attribute of type 'boolean'
included in the attribute mapping.
- R42013: Update docs to
explain filtered attribute behavior
- R42030: Change-RTC
synchronizer throws NotLoggedInException when multiple synchronizers are
created and run concurrently
- R42039: Focal Point
6.5.1.0 and DOORS 9.4 synchronizer seems broken.
- R42170: The
synchronizer is not able to pick up new Work Item changes made to the
Process Template without requiring a synchronization server restart.
- R42678: Migration fails
with Out of memory exception.
- R42720: Attribute value
truncation fails if the value contains unicode characters which is more
than a byte in length.
Rational Synchronization Server
1.4.0.5 also includes all fixes from Rational Synchronization Server 1.4.0.2
- PM49096 (R41487):
Uppercase state ID after mapping causes sync failures
- PM49098 (R41488):
Having a state label in Change that contains parenthesis causes issues
during mapping in sync server
- PM49100 (R41491): The
RTC Planned For attribute cannot be set properly during sync
- PM49101 (R41493):
Tomcat does not exit cleanly on linux when sync
server is installed
- PM49104 (R41494): NullPointerException happens in ChangeGenericSync
when login to Change fails
- PM49147 (R41503): RTC
has 32K limit on attributes and comments which breaks sync
- PM49148 (R41504): CR
comments don't get migrated if CR matches migrate query after first sync
- PM49149 (R41505): Sync
stops working due to file handles being left open
- PM49151 (R41506): There
is no way to refresh the attribute lists in the Change-RTC synchronizer UI
- PM49153 (R41507):
Attribute lists in the Change-RTC synchronizer UI are not updated when you
change project area
- R41502: Sync server
Start button can timeout and make the UI non-responsive
- R41186: Change-RTC
synchronizer UI does not let users select preferred Change database
- R41492: CATALINA_HOME
environment variable should not be hardcoded inside Sync Server
- R41443: Link file is
shown under link name column on the synchronization server
Rational Synchronization Server
1.4.0.5 also includes all fixes from Rational Synchronization Server 1.4.0.1
- R33492: Change-FP- Drop
down boxes appear bigger in size
- R33497: Change-FP- No
Alert Message for invalid FP connection details
- R33696: 2 different
error messages appearing when attempting to an empty URL Change server
- R33698: The 'Map'
button remains active even if no RTC attribute is available in the listbox
- R33740: Incorrect info
in the help document about the retention of the xml files when a
synchronizer is deleted
- R33736: Change-RTC : The State mapping must mention that the default submit
states are being used for creating Work Item as well.
- R33735: The attributes
shouldn't be removed from the list of available attributes once they have
been mapped.
- R33742: CR's attribute overwrites WI's
mapped attribute when WI's attribute value was changed last and another
attribute mapping direction has been set to ’changetoadapter'
- R33761: The installer name is "sync_server_install" whereas it has been
documented as “setupwin32”
- R33785: Sync fails when
sync interval is not set
- R39603: Change-RTC – CRs are not getting migrated from Change to RTC Server
- R40126: Uninstallation steps for uninstalling sync server on
Unix are not documented in the sync server help
- R40428:
Change-ClearQuest – Cannot connect to CQ server from Synchronization
Server
- R40305: URL with
incorrect syntax is able to open the sync server login interface
- R40418: Multiple
attachments of same file are synchronized from Change to ClearQuest
multiple times.
- PM01574 (R38018):
DOORS_HOME in the installation guide should be changed to DOORSHOME
- PM36851 (R40308):
Rational Synchronization Server to RTC integration does NOT support custom
enumeration
- PM36852 (R40309): Rational Synchronization Server
to RTC integration only supports RTC workitem
- Synchronizer picks
wrong CR if there are several Crs with same
number but different dcm
delimiters.
- Fix the condition when
sync fails because of no comments were supplied.
- Update the comment sync
feature to sync comments without state change. Capture the comments passed
during WaitingInfo. In this mode, the state of
the CR is not changed.
- Synchronize transition
log comment
- Add feature to prevent
circular state transitions
- Fix for sync un-mapped
state. It should not cause sync to fail
- Fix for synchronizing
attributes that have sync direction changetoadapter.
- Increase timeout to 2
minutes when calling Change API
- Add feature to prevent
double sync state transitions
- Add feature to
Change-Change adapter to preserve changes made to CR during sync
- Add feature to GenericChangeSync to preserve changes made to CRs during sync
- Add feature to CQ
adapter to preserve changes made to CQ Records during sync
- Change the CCS to pass
all mapped attributes when submitting Crs during
migrate
- Fix the CCS problem of
synchronizing null attributes
- Modify GenericChangeSynchronizer to handle out of memory
errors coming from adapter
- Create synchronization
direction persistency in case of tomcat shutdown in the middle of sync
- Improve sync
performance by fetching record mapped attribute values on modified sync query
- Ensure that mappings
labeled adaptertochange are never considered for
updating the adapter side
- Remove warning if CR
attribute doesn't have an adapter mapping
Known problems
General
- If you install
additional Synchronizers or uninstall any of the installed Synchronizers,
Rational Synchronization Server may not display the pages properly unless
you restart your Tomcat server.
- If you update any of
the Synchronizer options (Sync Time Interval, Time Unit, or Server
Startup) for a sync process, the sync process may not pick up any
modifications unless the sync process is stopped and restarted.
- After starting the
Rational Change server, you must login to Rational Change at least once
before attempting to synchronize or create a template using the Rational Focal
Point for Rational Change Synchronizer.
- If you delete an
attachment, the Rational Change for Change Interface will re-attach it
unless you delete it from both Change Requests.
- If you delete an
attachment, the Rational Focal Point for Change Interface will re-attach
it unless you delete it from both Change Request and Element.
- If you disassociate an
associated task, the Rational Team Concert for Change Interface will
associate the task again unless you delete it from both Change Request and
WorkItem.
- The Rational DOORS for
Focal Point Interface requires that the Rational DOORS server, the
Rational Focal Point server, and the Rational Synchronization Server be
located in the same time zone.
- Asian characters cannot
be used in the name of a link in the Rational DOORS for Focal Point
Interface.
- When Starting
or Stopping a Synchronizer from the Start/Stop page, the Status may not
get updated. When this happens,
click on the Refresh button to update the Status displayed on the page.
- The Rational Change for
ClearQuest Interface limits the number of records that can be migrated at
a time from Rational ClearQuest to Rational Change to 50. It also limits
the number of change requests that can be migrated at a time from Rational
Change to Rational ClearQuest to 50.
- The Change for Focal
Point interface does not get loaded properly in Internet Explorer due to
some rendering issues. The same gets loaded properly in Firefox browser.
Contacting Support
Please visit our Telelogic support overview site at: http://www.ibm.com/software/rational/support/telelogic/
You will find a one-sheet reference guide about how to best contact support
in you geography.
Notices for
Rational Synchronization Server, version 1.4.0.5 documentation
© Copyright IBM Corporation 2006, 2014.
U.S.
Government Users Restricted Rights - Use, duplication or disclosure restricted
by GSA ADP Schedule Contract with IBM Corp.
Programming interfaces: Intended programming interfaces allow the
customer to write programs to obtain the services of Rational Synchronization
Server.
This information was developed for products and services offered in
the U.S.A.
IBM may not offer the products, services, or features discussed in
this document in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or
imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product,
program, or service.
IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document does not
grant you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information,
contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom
or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS
IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this
statement may not apply to you.
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the information herein;
these changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.
Any references in this information to non-IBM websites are provided
for convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for
this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any
way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for
the purpose of enabling: (i) the exchange of
information between independently created programs and other programs
(including this one) and (ii) the mutual use of the information which has been
exchanged, should contact:
Intellectual Property Dept. for Rational
Software
IBM Corporation
5 Technology Park Drive
Westford, MA 01886
U.S.A.
Such information may be available, subject to appropriate terms and
conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed
material available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Program License Agreement or any equivalent
agreement between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments
may vary significantly. Some measurements may have been made on
development-level systems and there is no guarantee that these measurements
will be the same on generally available systems. Furthermore, some measurements
may have been estimated through extrapolation. Actual results may vary. Users
of this document should verify the applicable data for their specific
environment.
Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or other publicly
available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed
to the suppliers of those products.
All statements regarding IBM's future direction or intent are
subject to change or withdrawal without notice, and represent goals and
objectives only.
This information is for planning purposes only. The information
herein is subject to change before the products described become available.
This information contains examples of data and reports used in daily
business operations. To illustrate them as completely as possible, the examples
include the names of individuals, companies, brands, and products. All of these
names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
Copyright license
This information contains sample application programs in source
language, which illustrate programming techniques on various operating
platforms. You may copy, modify, and distribute these sample programs in any form
without payment to IBM, for the purposes of developing, using, marketing or
distributing application programs conforming to the application programming
interface for the operating platform for which the sample programs are written.
These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function
of these programs. The sample programs are provided "AS IS", without
warranty of any kind. IBM shall not be liable for any damages arising out of
your use of the sample programs.
Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:
© (your company name) (year). Portions of
this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp.
2006, 2014.
If you are viewing this information in softcopy, the photographs and
color illustrations may not appear.
Privacy policy considerations
IBM Software products, including software as a service solutions,
(“Software Offerings”) may use cookies or other technologies to collect product
usage information, to help improve the end user experience, or to tailor
interactions with the end user or for other purposes. In many cases no
personally identifiable information is collected by the Software Offerings.
Some of our Software Offerings can help enable you to collect personally
identifiable information. If this Software Offering uses cookies to collect
personally identifiable information, specific information about this offering’s
use of cookies is set forth below.
Depending upon the configurations deployed, this Software Offering
may use session cookies that collect each user’s name for purposes of session
management. These cookies can be disabled, but disabling them will also
eliminate the functionality they enable.
If the configurations deployed for this Software Offering provide
you as customer the ability to collect personally identifiable information from
end users via cookies and other technologies, you should seek your own legal
advice about any laws applicable to such data collection, including any
requirements for notice and consent.
For more information about the use of various technologies,
including cookies, for these purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy
and IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details/us/en
sections entitled “Cookies, Web Beacons and Other Technologies” and “Software
Products and Software-as-a Service”.
Trademark acknowledgments
IBM, the IBM logo, and ibm.com are trademarks or registered
trademarks of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be trademarks of
IBM or other companies. A current list of IBM trademarks is available on the
web at http://www.ibm.com/legal/copytrade.shtml.