PI14540: SA 8.5.1: Structured Data Importer issue

Rational Software Architect 9.1
Rational Software Architect for WebSphere Software 9.1
Rational Software Architect Fix Pack 2 (8.5.5.2) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 2 (8.5.5.2) for 8.5.5
Rational Software Architect 9.1.1
Rational Software Architect for WebSphere Software 9.1.1
Rational Software Architect Fix Pack 3 (8.5.5.3) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 3 (8.5.5.3) for 8.5.5
Rational Software Architect for WebSphere Software 9.1.2
Rational Software Architect 9.1.2
Rational Software Architect Fix Pack 4 (8.5.5.4) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 4 (8.5.5.4) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 1 (9.1.2.1) for 9.1.2
Rational Software Architect Fix Pack 1 (9.1.2.1) for 9.1.2
Rational Software Architect Fix Pack 2 (9.1.2.2) for 9.1.2
Rational Software Architect Fix Pack 3 (9.1.2.3) for 9.1.2
Rational Software Architect for WebSphere Software Fix Pack 1 (9.1.2.3) for 9.1.2

APAR status

• Closed as program error.

Error description

• The RSA topology documentation states:
  
  By default, the template tag creates new units in the topology.
  However, you can reuse units from the topology by setting the
  use Existing Units attribute to true. In this case, instead of
  creating new units, the template tag accesses and updates the
  matching units.The template tag matches units first by the unit
  name; if no units match by name, it matches units by the
  caption.
  
  The APIs do not work as per the documentation and IBM has
  acknowledged this.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  While reusing the existing units from the topology by using
  the useExistingUnits attribute in  tag, it does not work as
  per documentation while matching units by the caption.
  

Problem conclusion

• When useExistingUnits attribute is set to true in the  tag,
  it matches units first by the unit name; if no units match
  by name, it matches units by the caption (applicable for
  templates that instantiates single unit only). For the
  templates that instantiates more than one unit, the matching
  by caption is NOT applicable. E.g.
  os.OperatingSystemUnit.W2K.infra,
  was.WasStandaloneBundle.7.infra etc. Also, a new boolean
  attribute called preferDisplayNameMatch (default value is
  false) is added to  tag. 1) When the unit tag is nested
  within the template tag, the unit tag behaves as follows: If
  there is more than one unit of the specified type in the
  template and a) preferDisplayNameMatch is false, the
  behavior of the unit tag depends on the names of those units
  and the name attribute of the unit tag. If the name
  attribute matches the name of one or more of the units in
  the template, the unit tag accesses the first unit with a
  matching name. If the name attribute does not match the name
  of any of the units, the unit tag creates a unit. b)
  preferDisplayNameMatch is true, the behavior of the unit tag
  depends on the displayNames of those units and the
  displayName attribute of the unit tag. If the displayName
  attribute matches the displayName of one or more of the
  units in the template, the unit tag accesses the first unit
  with a matching displayName. If the displayName attribute
  does not match the displayName of any of the units, the unit
  tag creates a unit. 2) When the unit tag is not nested
  within the template tag, the unit tag behaves as follows: a)
  If the preferDisplayNameMatch is false, both type and name
  attributes of the unit tag are matched against the type and
  name of an existing unit in the topology. If no unit match
  is found, new unit will be created. b) If the
  preferDisplayNameMatch is true, both type and displayName
  attributes of the unit tag are matched against the type and
  displayName of an existing unit in the topology. If no unit
  match is found, new unit will be created.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL APP DEV WI

• Fixed component ID

  5724J1901

Applicable component levels

• R851 PSN

     UP