2003
DOI: 10.1007/978-3-540-45189-1_10
|View full text |Cite
|
Sign up to set email alerts
|

Providing Highly Automated and Generic Means for Software Deployment Process

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
9
0

Year Published

2003
2003
2011
2011

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 11 publications
(9 citation statements)
references
References 3 publications
0
9
0
Order By: Relevance
“…1 All names of products are trademarks, service marks or registered trademarks of the respective companies. The lower left quadrant of the portfolio contains tools that automate all deployment activities (ORYA [12], Software dock [8]) or only installation (ADAGE [10]); the unlabeled bubbles represent proprietary tools. In this paper, these approaches are neglected as they do not satisfy the modeling requirement [Rq6].…”
Section: Existing Approaches In the Field Of Deploymentmentioning
confidence: 99%
“…1 All names of products are trademarks, service marks or registered trademarks of the respective companies. The lower left quadrant of the portfolio contains tools that automate all deployment activities (ORYA [12], Software dock [8]) or only installation (ADAGE [10]); the unlabeled bubbles represent proprietary tools. In this paper, these approaches are neglected as they do not satisfy the modeling requirement [Rq6].…”
Section: Existing Approaches In the Field Of Deploymentmentioning
confidence: 99%
“…6. While there are various options to manage a federation, its nodes and the distributed resources [23], our approach does neither rely on a particular organization nor communication protocol as long as there is an appropriate plugin to enable the module controller to interact with the federation or a single repository and shield the logical application composition from the physical module deployment. As an example, the discovery of available module repositories could be managed by manually edited local configuration files, well-known directory services or peer-topeer approaches.…”
Section: Fig 6 Module Repositories and Module Federationmentioning
confidence: 99%
“…We will primarily focus on how to work with modules regarding development, deployment, composition and configuration issues. The tasks of how to implement and synchronize a federation are not covered in detail since they have been already addressed in other works [23]. In fact, the interaction with the module federation and the participating nodes is actually performed by module controller plugins which hide the details of discovering module repositories, querying modules and downloading them onto the requesting Internet node.…”
Section: Realizationmentioning
confidence: 99%
“…In this situation, the deployment process is not so straightforward, and automated tools and techniques are required for this purpose. Consequently, the software deployment process has been given special attention both in research and industry in recent years and it is possible to find many tools and papers addressing different activities of the software deployment process from different perspectives [1,2,3,4,5]. However, to our knowledge, few if any of these deployment approaches notices the characteristics (e.g., behavior, cost, speed, security, etc.)…”
Section: Introductionmentioning
confidence: 99%