Description:
You can download this HotFix from the TIBCO Product Support FTP server using your eSupport username and password, at
            ftp://support-ftp.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under
            available_downloads/ActiveMatrix/ActiveMatrixServiceGrid/2.1.0/TIB_amx_tap_020100_3/

Important note: This hotfix requires TIBCOUniversalInstaller_250v24, and another hotfix "TIB_amx_rp_020100_1" if you want to address CR#1-8J213R.

Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.

======================================================================
This hotfix is cumulative of previous TIB_amx_tap_020100 hotfixes.

Closed Issues in TIB_amx_tap_020100_3 (This Release)

  1-9GSGI7:
  ANT command-line script for changing authentication realm
  configuration no longer fails on a machine without an Internet
  connection.

  1-9JWAHT:
  When using LDAP Authentication Realm, it is now possible to configure
  a different LDAP attribute (such as 'sAMAccountName' in case of
  Microsoft Active Directory) to display as Username in the Users tab
  of Enterprise Assets. Previously, the value for 'CN' attribute would
  always be used for Username.

  Note that some manual configuration must be done, as explained in the
  Installation section, to configure this attribute name.
  
  1-9JWAJ8:
  When using LDAP Authentication Realm used with Microsoft Active
  Directory, LDAP Root search (Domain Component) no longer fails if
  the subtree (OUs) have users with comma character(,) in the first or
  last names, or when there are LDAP referral entries present. Note that
  the fix for issue 1-9JWAHT provides a more desirable behavior in case
  of Microsoft Active Directory, because typically, 'sAMAccountName'
  attribute is used to identify users, and not the 'CN' attribute. It is
  the value for 'CN' attribute that has comma characters, but not the
  'sAMAccountName'. You will need to perform some manual configuration
  steps to set 'sAMAccountName' as the username attribute instead of the
  default attribute 'CN'.

  1-9HAT9D:
  When using LDAP Authentication Realm, user details, such as the group memberships
  for a user, now get displayed correctly when the user's CN attribute, first or
  last name attributes contains a comma character(,).
  Note that the fix for issue 1-9JWAHT provides a more desirable behavior in case of
  Microsoft Active Directory, because typically, 'sAMAccountName' attribute is used to
  identify users, and not the 'CN' attribute. It is the value for 'CN' attribute that has
  comma characters, but not the 'sAMAccountName'. You will need to perform some manual
  configuration steps to set 'sAMAccountName' as the username attribute instead of the
  default attribute 'CN'.


  1-9IUXZ6, 1-9IRPP9:
  When using LDAP Authentication Realm, adding additional LDAP users as superusers
  works properly for granting of full privileges, when a different LDAP attribute
  (such as 'sAMAccountName' in case of Microsoft Active Directory), other than 'CN'
  is used in the user search filter. Also, user permissions now work properly.
  Note that the fix for issue 1-9JWAHT provides a more desirable behavior in case of
  Microsoft Active Directory, because typically, 'sAMAccountName' attribute is used to
  identify users, and not the 'CN' attribute. It is the value for 'CN' attribute that has
  comma characters, but not the 'sAMAccountName'. You will need to perform some manual
  configuration steps to set 'sAMAccountName' as the username attribute instead of the
  default attribute 'CN'.


  1-9KRGBZ:
  The default node created from Administration Server Creation Wizard no longer
  needs the property 'java.property.teneo.mapping=SINGLE_TABLE' to be added manually.
  It is automatically added by the Wizard. This was a regression in TIB_amx_tap_020100_2.
  Also, dbscriptgenerator.properties will also use SINGLE_TABLE property by default,
  so no manual editing is necessary in this file after hotfix installation.

  Please refer to LBN1-9MXVHS for additional important information related to this issue.

  1-9BS65H:
  TIBCO ActiveMatrix Runtime UDDI Server 1.0 and TIBCO ActiveMatrix Service
  Grid 2.1 installed in the same TIBCO Home directory no longer cause conflicts
  that make the ActiveMatrix Administrator ANT command-line task to fail.


Closed Issues in TIB_amx_tap_020100_2 (Previous Release)

  1-9GSIK5:
  Administrator scripts no longer fail to launch on an AIX machine that
  has 64-bit ActiveMatrix installation, but a 32-bit JRE directory had
  been declared in the system's LIBPATH environment variable.


  1-8J213R:
  Performance degradation in Administrator when used with Oracle, as
  compared with other databases, is no longer an issue.
  However, certain performance optimizations required changes to the
  underlying Database table schema. For backward compatibility, this
  schema change is not enabled for an existing Administrator cluster.
  The schema change is applied automatically for a new Administrator
  cluster only.

  If you plan to create a new Administrator cluster after applying this
  hotfix, then you must also install the hotfix "AMX-RP-020100-1".
  The database schema change impacts ActiveMatrix nodes, and for them to
  continue to function, that hotfix is required.

  Certain other performance improvements were made in the command line
  scripting framework. An increasing performance degradation seen while
  deploying several service assemblies is now fixed. This fix applies
  to all platforms and databases, and it is not schema related.



  1-9GT8TS:
  admincmdline no longer terminates with the rarely seen error:
  "XFireException (socket closed)" while running a batch of ANT
  commands. This symptom   was caused because of an incorrect
  detection of a denial-of-service condition on the Administration
  server, which is now fixed.


  1-9GT9A1:
  Fixed an issue seen with Sybase, where many operations, such as viewing
  details of a node in Administrator UI, failed with the database error
  "Implicit conversion from datatype 'VARCHAR' to 'NUMERIC' is not allowed.
   Use the CONVERT function to run this query.". This issue was specifically
  related to very large numbers generated by the database sequence generator.
  Generation of such large sequence ID numbers in Sybase server was seen
  rarely in some Sybase instances. Such large sequence ID numbers are now
  handled correctly in Administrator.

  

Closed Issues in TIB_amx_tap_020100_1 (Previous Release)

  1-8UH6XZ:
  The ActiveMatrix Administrator server no longer reports the error
  "LDAP Error 12 Unavailable Critical Extension" when connecting to
  Sun Java System Directory Server version 6.3 for the LDAP
  Authentication Realm.

  1-9AGELV:
  A null pointer exception is no longer reported when deleting a node.
  This was a regression from ActiveMatrix 2.0.2-hf1

TIBCO ActiveMatrix(R) Service Grid 2.1.0 Hotfix "TIB_amx_tap_020100_3" is now available.

Product: TIBCO ActiveMatrix Service Grid Version: 2.1.0 OS: --------------------