PH45825: Updating an Application Template from another Deploy Server fails with: A notification scheme named <name> already exists

APAR status

• Closed as program error.

Error description

• 1) Create an Application Template to export on Server 1
  This Application Template should contain:
  - Non-Default Notification scheme  named 'nonDef-notScheme'
  - Resource Template
  - Component Template + Component (Template) Tag
  - Application Template
   added Non-Default Notification scheme
   created Environment Template based on the Resource Template
   Configured the Component (Template) tag
  
  
  2) Export the Application Template
  3) Imported the Application Template in Server 2
  Result:
  Application Template imported successfully.
  The Non-Default Notification scheme is created
  
  4) Modify the Application Template by adding an Application
  Process (or any other change) on Server 1
  5) Export the modified Application Template from Server 1
  6) Import the modified Application Template on Server 2
  
  Result:
   Alert
  Error importing application template: A notification scheme
  named nonDef-notScheme already exists.
  
  
  Cause:
  This is because the initial import of the Application Template
  resulted in the Notification Template to be created, but with a
  new notificationScheme ID instead of the one in the .json.
  The second import fails because the notificationScheme ID in the
  .json now conflicts.
  
  
  Workaround:
  Change the Notification Scheme to the 'Default Notification
  Scheme' before exporting, and change it to the correct
  Notification Scheme post-import.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Deploy Server Web UI Users                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Updating an Application Template from another Deploy Server  *
  * fails with: A notification scheme named <name> already       *
  * exists                                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Fix is provided in IBM UrbanCode Deploy 7.2.3.1              *
  ****************************************************************
  

Problem conclusion

• Fix is provided in IBM UrbanCode Deploy 7.2.3.1
  

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

  UC DEPLOY

• Fixed component ID

  5725M5400

Applicable component levels