Issue 8979: Distinguish Node vs. Component Exec Parameters in Deployment Plan                                                                                                                                       (deployment-rtf)
Source: Mercury Computer Systems (Mr. Frank Pilhofer, fpilhofe@mc.com)
Nature: Uncategorized Issue
Severity: 
Summary: The resolution for issue 6435 split the former "execution
parameters" into "node execution parameters" and "component
execution parameters" within the Component Data Model, by
extending the MonolithicImplementationDescription element
to have separate "nodeExecParameter" and "componentExec-
Parameter" property lists.


However, the resolution neglected to make a similar change
to the Execution Data Model -- the MonolithicDeployment-
Description element in the Deployment Plan only has a single
list of "execParameter" properties.


This should be changed to be in sync with the Component
Data Model.


Proposed resolution:


In section 6.8.3.3 (MonoliticDeploymentDescription
associations), remove the "execParameter" association.


Instead, add the following two associations:


  nodeExecParameter: Property[*]
    Execution parameters that are passed to the target
    environment. Copied from the MonoliticImplementation-
    Description.
  componentExecParameter: Property[*]
    Execution parameters that are passed to the primary
    artifact. Copied from the MonoliticImplementation-
    Description.
Resolution: 
Revised Text: In section 6.8.3.3 (MonolithicDeploymentDescription associations), remove the "execParameter" association.

Instead, add the following two associations:

  nodeExecParameter: Property[*]
    Execution parameters that are passed to the target
    environment. Copied from the MonolithicImplementation-
    Description.

  componentExecParameter: Property[*]
    Execution parameters that are passed to the primary
    artifact. Copied from the MonolithicImplementation-
    Description.


Disposition:	Resolved

Actions taken:
August 26, 2005: received issue
June 7, 2006: closed issue
Discussion: 
Resolution:
Split the "execution parameters" in the Execution Data Model into two sets of parameters to be in sync with the Component Data Model.

End of Annotations:=====
ubject: Distinguish Node vs. Component Exec Parameters in Deployment Plan
Date: Fri, 26 Aug 2005 13:12:07 -0400
Thread-Topic: Distinguish Node vs. Component Exec Parameters in Deployment Plan
Thread-Index: AcWqYUij6fO6jy6PTLq/pQ+q1WzhKw==
From: "Pilhofer, Frank" <fpilhofe@mc.com>
To: <issues@omg.org>
Cc: <deployment-rtf@omg.org>
X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id j7QHTohh025218


This is a new issue for the Deployment RTF.


The resolution for issue 6435 split the former "execution
parameters" into "node execution parameters" and "component
execution parameters" within the Component Data Model, by
extending the MonolithicImplementationDescription element
to have separate "nodeExecParameter" and "componentExec-
Parameter" property lists.


However, the resolution neglected to make a similar change
to the Execution Data Model -- the MonolithicDeployment-
Description element in the Deployment Plan only has a single
list of "execParameter" properties.


This should be changed to be in sync with the Component
Data Model.


Proposed resolution:


In section 6.8.3.3 (MonoliticDeploymentDescription
associations), remove the "execParameter" association.


Instead, add the following two associations:


  nodeExecParameter: Property[*]
    Execution parameters that are passed to the target
    environment. Copied from the MonoliticImplementation-
    Description.
  componentExecParameter: Property[*]
    Execution parameters that are passed to the primary
    artifact. Copied from the MonoliticImplementation-
    Description.