Issue 7279: ExternalReferneceEndpoint (deployment-ftf) Source: Raytheon (Mr. Gerald Lee Bickle, Gerald.L.Bickle(at)raytheon.com) Nature: Uncategorized Issue Severity: Summary: For ExternalReferneceEndpoint add a navigable association to Requirement with multiplicity being "*". Rationale for change is to allow for PSMs to qualify the requirements needed for an ExternalReferenceEndpoint. An example is a SWRadio use cases for this are: a. To be able to specify a service needed that the domain is aware of. b. To be able specify a device that deployment machinery used for the deployment of a component. c. To be able to specify a service that was chosen by the deployment machinery that was specified for a component deployment requirement. Resolution: Revised Text: Actions taken: April 30, 2000: received issue Discussion: During the RTF meetings and telephone conferences the RTF agreed that further information from the poster of this issue is needed. Thus, this issue is deferred to the next Deployment RTF. End of Annotations:===== ubject: Deployment & Configuration Issues To: issues@omg.org Cc: deployment-ftf@omg.org, sbc@omg.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 From: Gerald_L_Bickle@raytheon.com Date: Fri, 30 Apr 2004 16:40:10 -0500 X-MIMETrack: Serialize by Router on NotesServer3/HDC(Release 5.0.12 |February 13, 2003) at 04/30/2004 04:40:19 PM X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id i3ULgY3J008981 AssemblyConnectionDescription Definition changes and issues discussed at the OMG St. Louis meeting. Not all these were discussed. 1. For ExternalReferneceEndpoint add a navigable association to Requirement with multiplicity being "*". Rationale for change is to allow for PSMs to qualify the requirements needed for an ExternalReferenceEndpoint. An example is a SWRadio use cases for this are: a. To be able to specify a service needed that the domain is aware of. b. To be able specify a device that deployment machinery used for the deployment of a component. c. To be able to specify a service that was chosen by the deployment Date: Wed, 20 Oct 2004 10:04:31 -0400 From: James Kulp Organization: Mercury Computer Systems, Inc. User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en,pdf To: Deployment RTF Subject: Issue 7279 - more external reference endpoint features - discussion X-Virus-Scanned: by ClamAV at mailsnare.net Here is the For ExternalReferneceEndpoint add a navigable association to Requirement with multiplicity being "*". Rationale for change is to allow for PSMs to qualify the requirements needed for an ExternalReferenceEndpoint. An example is a SWRadio use cases for this are: a. To be able to specify a service needed that the domain is aware of. b. To be able specify a device that deployment machinery used for the deployment of a component. c. To be able to specify a service that was chosen by the deployment machinery that was specified for a component deployment requirement. Assemblies are work products of development and represent a functional decomposition implementation of a component, as in hierarchical schematic design. External Reference Endpoints are ways of connecting to external "signals" that are outside the scope of the component being implemented. The analogies are like global "reset, vcc, ground" signals in a circuit schematic, or "extern" statements in the code of a C program - bind this reference to the outside world. The existing spec allows for binding to URLs. (using the attribute whose name is "location"). The spec says that "location" attributes reference entities outside the model, and thus anything expressible in a URL can be "requested" by the deployment system, assuming that the deployment system supplies the protocol in the URL. CORBA already implies support for some URL scheme (corbaloc, and corbaname). Thus the CCM PSM already implies that these external references can be satisfied by any of these, and further requires http scheme support in some cases (section 9.6.5). So, the "problem" inferred from this issue is that the URL mechanism is insufficient to support some other patterns. Clearly any PSM can clarify requirements on these URLs, and can further specialize or define this class with new behaviors. A different solution, suggested by Gerry, is to attach a list of requirements to the endpoints. This would require some notion of the algorithm used by the deployment environment to satisfy the requirements. The target model provides the information used to satisfy requirements, and so this would imply a new aspect to the target environment in general for service registration. Because this is such a large change to the model, I would recommend the simpler solution: suggest that other PSMs simply specialize the external reference endpoint... Jim machinery that was specified for a component deployment requirement.