IBM Support

PI60839: ENVIRONMENT TEMPLATE DOES NOT SEEM TO TAKE INTO ACCOUNT AGENT PROTOTYPE NAMES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Problem:
    When creating an Environment based on the environment template,
    agent prototype names are not honored: the matching agents are
    not automatically added to the Environment.
    
    Steps to reproduce:
    
    Scenario A, based on Blueprint, succeeds:
    
    - create a Resource Template
    - add a Agent Name Pattern to the Agent Prototype, using the
    exact Agent name
    - create an Application, a Blueprint based on the resource
    template
    - create an environment based on the blueprint: the environment
    got the agent added 3
    
    Scenario B, based on Environment Template, fails:
    
    - create an application template with an environment template
    based on the above resource template
    - create an application based on the application template
    - in the wizard, try to create an environment. You see a dialog
    where you can map the agent to the prototype, but unless you
    manually map them, the agent will not be added to the
    environment
    
    - After the application is created, try to add a new environment
    to it, based on the environment template
    - again the agent is not added to the environment, and in this
    case you also have no wizard to map it manually
    
    The expectation is that the environment template will offer the
    same functionality of the Blueprint with regards to using the
    agent prototype names to identify matching agents.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Problem:                                                     *
    * When creating an Environment based on the environment        *
    * template,                                                    *
    * agent prototype names are not honored: the matching agents   *
    * are                                                          *
    * not automatically added to the Environment.                  *
    *                                                              *
    * Steps to reproduce:                                          *
    *                                                              *
    * Scenario A, based on Blueprint, succeeds:                    *
    *                                                              *
    * - create a Resource Template                                 *
    * - add a Agent Name Pattern to the Agent Prototype, using the *
    * exact Agent name                                             *
    * - create an Application, a Blueprint based on the resource   *
    * template                                                     *
    * - create an environment based on the blueprint: the          *
    * environment                                                  *
    * got the agent added 3                                        *
    *                                                              *
    * Scenario B, based on Environment Template, fails:            *
    *                                                              *
    * - create an application template with an environment         *
    * template                                                     *
    * based on the above resource template                         *
    * - create an application based on the application template    *
    * - in the wizard, try to create an environment. You see a     *
    * dialog                                                       *
    * where you can map the agent to the prototype, but unless you *
    * manually map them, the agent will not be added to the        *
    * environment                                                  *
    *                                                              *
    * - After the application is created, try to add a new         *
    * environment                                                  *
    * to it, based on the environment template                     *
    * - again the agent is not added to the environment, and in    *
    * this                                                         *
    * case you also have no wizard to map it manually              *
    *                                                              *
    * The expectation is that the environment template will offer  *
    * the                                                          *
    * same functionality of the Blueprint with regards to using    *
    * the                                                          *
    * agent prototype names to identify matching agents.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fixed in version 6.2.6.1                                     *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 6.2.6.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI60839

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    611

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-14

  • Closed date

    2017-10-27

  • Last modified date

    2017-10-27

  • 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

  • R600 PSN

       UP

  • R600 PSY

       UP

  • R601 PSN

       UP

  • R601 PSY

       UP

  • R610 PSN

       UP

  • R610 PSY

       UP

  • R611 PSN

       UP

  • R611 PSY

       UP

  • R612 PSN

       UP

  • R612 PSY

       UP

  • R613 PSN

       UP

  • R613 PSY

       UP

  • R620 PSN

       UP

  • R620 PSY

       UP

  • R621 PSN

       UP

  • R621 PSY

       UP

  • R622 PSN

       UP

  • R622 PSY

       UP

  • R623 PSN

       UP

  • R623 PSY

       UP

  • R624 PSN

       UP

  • R624 PSY

       UP

  • R625 PSN

       UP

  • R625 PSY

       UP



Document information

More support for: IBM UrbanCode Deploy

Software version: 6.1.1

Reference #: PI60839

Modified date: 27 October 2017