"Deployment is an important part of the software-development life cycle. After all, software must reach the end user to be of value. Two traditional deployment models are the "foot-and-hand" model (someone runs around on foot and installs the software by hand) and the "self-service" model (the user installs the software himself). For large deployments, both models are time-consuming and expensive. Therefore, for many managers and software developers, the Web browser and the Java applet provide a promising alternative."
"In Part 2 of this series on deployment methods, I present an alternative technique that uses applets in an unconventional manner. This method melds some of applets' best features with those of traditional deployment techniques and creates a foundation upon which powerful deployment tools can be built."
"The release of the 1.3 version of the Java 2 Platform, Enterprise Edition (J2EE) represents the evolution of Sun Microsystems' server-side development platform into a more mature and sophisticated specification. Servlets 2.3 gain events and filtering; JavaServer Pages (JSP) 1.2 gain a new XML syntax and enhancements to the custom tag mechanisms; and Enterprise JavaBeans (EJB) 2.0 has some significant changes to its container-managed persistence model, as well as support for asynchronous processing with the new message-driven beans."
"Your use of this page (http://java.sun.com/docs/books/tutorial (Last Updated 2/14/2008)) and all the material on pages under "The Java Tutorials" banner is subject to the Terms of Use. Additionally, (i) any example code contained in any of these Java Tutorials pages is also licensed under the Code Sample License, and (ii) the entire Java Tutorials content is available for download under the Java Tutorials Limited Non-Commercial License for limited, non-commercial individual and/or research and instructional use at Sun Download Center."
"In an earlier Automation for the people installment, "Speed deployment with automation," you learned a technique for remotely deploying software into multiple target environments. This two-part article takes the automated-deployment discussion to a higher level. Just as there are patterns for software development, there are patterns for deployment, and I've been cataloging them over the past few years. Here in Part 1, I'll introduce eight deployment patterns and provide examples for them:"
"In an earlier Automation for the people installment, "Continuous Integration anti-patterns, Part 2," you learned why cleaning up a "polluted" environment helps prevent falsely positive or negative builds. The Disposable Container reduces many of the problems that can occur when you rely on persistent containers. The Disposable Container pattern is based on two principles: completely remove all container components and separate the container installation from its configuration. This seems like a radical concept to some, particularly systems engineers, because it no longer assumes that containers should be managed, and obfuscated, by a separate team, never to be touched by developers or others. However, considering the common and costly problems that occur during deployments, it can be an area where all team members can realize the most benefit."
"Apache Axis2 (one of the key open source Web services platforms) benefits from a number of new features, and judiciously, most of these have resulted in giving developers a more user-friendly approach. In previous versions of Axis, user friendliness had not been a priority. For example, in Axis1, users had to invoke the admin client manually and update the server class path, and then restart the server to apply the changes. This burdensome deployment model was a definite barrier for beginners. Thus, Axis2 was engineered to overcome this drawback and provide a more flexible, easily configurable deployment model."
"Have you ever noticed that for many teams, moving software from development environments into production is often an afterthought? I've run across teams with deployment timelines that range anywhere from weeks to even months ? time wasted, in my opinion. Why not leverage the same automation that's found in automated builds and drastically reduce the time spent on deployment configuration issues and thus, reduce those infrastructure inefficiencies?"
"With the business fundamentals covered in Hour 3, “Business Basics: Developing a Roadmap for Deploying SAP” behind us, it’s now time to turn our attention to the infrastructure technologies that underpin SAP. In this hour, we take a closer look at the three broad infrastructure technologies that come into play when deploying SAP—hardware, operating systems, and databases. In later hours, we examine the SAP-specific application and integration technologies as well."
"Installation is, in fact, a very interesting area that presents unique challenges. For a start, it requires a broader overview of the software being deployed than would be the case for an application developer. An install engineer must have a reasonable grasp of most of the elements that make up the software: servers, GUI, clients, database, and so on. To work in deployment requires moving up the value chain [1]."
"In this article, we will see a simple theoretical model for software deployment. We will focus on deploying software over the Web, but what is said here can be applied to other situations as well. For concreteness, we will use the Java platform as an example. Here, instead of providing practical advice, we will discuss some basic concepts in a simple intuitive way. A definition of software deployment is also provided."
