Developing Web applications using the Rational Lifecycle management tool

To achieve these promises of cloud computing, developers must think in a broader way. In this article, the authors describe how to use the Application lifecycle management tools provided by Rational to extend the scope of the developer's process. They provide scenarios and outline the tools and artifacts that developers need to reach their goals. Finally, they demonstrated how to use the ibm®rational® tool and SmartCloud Enterprise in an end-to-end development scenario.

Today, cloud computing combines application development, business, and system operations closer together. This means that software developers need to understand business processes and system operations better than before. This also means that business stakeholders and operators must consume more custom software.

The promise of cloud computing is that centralization, standardization, and automation simplify the user experience and reduce costs. To achieve these benefits, however, a new mindset is needed, in which developers must take into account business processes and system operations to build and deploy the most efficient cloud applications.

This article is intended to cover a wider range, including various aspects of application development and operations, and provides examples of Rational tools that are helpful in this process.

One of the most interesting aspects of cloud computing is that it implements new tools and collaboration levels. It supports team members ' reuse of work products, especially images. For example, there is an operating system expert who builds a base operating system image, where software developers add a software product image that business users use to get an image snapshot that fits their business needs. This article focuses on how you can use this tool to develop applications on the cloud.

Public Cloud Business Scenario

Let's start with a discussion of some use-case scopes that drive cloud computing:

Many of the benefits of

cloud computing may be more important for stand-alone use cases. The virtualization of the infrastructure also presents a number of new possibilities, as well as a variety of new IT assets that are completely out of use in traditional computing. Operations in the public Internet environment provide new collaboration possibilities, and at the same time new security challenges are created.

Several operators collaborate in cloud use cases:

Cloud Services developers develop software and other assets for consumers to consume on the cloud. Cloud services Consumers request cloud resources and approve business expenses. Cloud service consumers may include users, administrators, and business executives. Cloud service providers provide cloud services to consumers.

Consider a concept proof (POC) use case. Companies often establish proof-of-concept or pilot studies before deciding to use new technologies. Companies tend to hire external IT consultants to do the job, and it consultants are typically under a lot of pressure to deliver a challenging amount of functionality in a very short time. Normally, if a consultant has no experience in this field, he will not be able to provide the information he needs.

Assets that can be reused in different jobs are critical. Cloud computing can directly reuse a saved image and allow consultants and enterprise users to easily share the same network space, helping to make this easier. It would be much easier to have a consultant with a physical computer anywhere, or to install all the software on her laptop, or to try to install all the software in a very short time on the enterprise site.

The use case diagram for this scenario is shown in Figure 1.

Figure 1. A case diagram of proof of concept on the cloud

In order for an enterprise to add a consultant account, working in a public cloud environment that provides user management support is critical. In addition, consultants can use their own account space and simply allow access through network protocols such as HTTP.

If the enterprise approves a proof of concept, then it may want to use the POC for a long time. It can save the image and initiate an instance on the virtual LAN to migrate the POC to the private network of the enterprise.

Table 1 compares the traditional concept proofs with the concept proofs on the cloud.

Table 1. The POC in the traditional setting is compared with the POC on the cloud

Traditional cloud Advisor to client site consultants provide access to the corporate network through an approval workflow for consultants through an account or a specific virtual machine with an encryption key the customer provides the cloud access to the advisor through the accounts or a particular VM with cryptographic keys create an instance of hardware through the self-service interface for POC The consultant completes all work consultants to invite experts on high availability, performance, security, and so on as needed for several hours of collaboration advisor cannot connect his notebook computer to the corporate network. He must use only the tools provided by the customer the preferred Application Lifecycle management tool that customers can use on their laptops or on the cloud to install everything from scratch the advisor starts the instance from the pre-build image after completion, the purpose of the server is to reschedule the server instance to be saved as an image, The instance being run is deleted

For this use case, the main advantage of the cloud is resilient scalability, access from the Internet, and the ability to save and reuse project assets.