PM92644: BuildForge Server default port is used by the Cloud Service Archive and RAFW publisher

Rational Software Architect 8.5.5
Rational Software Architect for WebSphere Software 8.5.5
Rational Software Architect Fix Pack 1 (9.0.0.1) for 9.0
Rational Software Architect for WebSphere Software Fix Pack 1 (9.0.0.1) for 9.0
Rational Software Architect Fix Pack 1 (8.5.5.1) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 1 (8.5.5.1) for 8.5.5
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 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 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

APAR status

• Closed as program error.

Error description

• The Cloud Service Archive and IBM Rational Automation Framework
  for WebSphere (RAFW) Publisher generate the Tivoli Service
  Automation Manager (TSAM) export information using the IBM
  Rational BuildForge/RAFW default server port '3966' in the
  'buildplan.xml' instead of using the port of the BuildForge
  connection.
  
  If none of your BuildForge/RAF installations use the default
  port, but rather a custom one for security reasons, your
  workflow deployment in TSAM will fail with the error:
  
  'RAF authentication failed as the RAF instance is not running at
  the port specified in the workflow.'
  
  The workaround is to manually run the workflow in TSAM in order
  to to manually specify the correct port.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When user creates a BuildForge connection with a non-default
  port, while publishing the Cloud Service Archive, always the
  default port (i.e. 3966) of the BuildForge connection will
  be published in the "buildplan.xml" file.
  

Problem conclusion

• Now, while publishing the Cloud Service Archive, appropriate
  port of the BuildForge connection will be published in the
  "buildplan.xml" file.
  

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 SW ARCHITE

• Fixed component ID

  5725A3000

Applicable component levels

• R851 PSN

     UP