Use the rational build forge to automate the application of WebSphere application Server

Automated building of WebSphere Application server applications with rational build forge

IBM Rational Build Forge (RBF) is a client/server-mode based Process execution framework that provides functionality such as task scheduling and custom run steps. This article describes how to use RBF to automate the construction of applications based on WebSphere application Server (WAS), and describes in detail the RBF functional modules involved. With this article, you can also learn about Ant and WebSphere Java Management Extensions (JMX).

Knowledge Preparation

To better understand this article, you need to know the following:

Java EE application Development platform IBM Rational application Developer (RAD) is used.

ANT tool for building Java EE applications.

WebSphere Application Server Deployment and JMX programming.

Basic use of Rational build Forge.

1. Application Scenarios

When we encounter a complex problem, we need to refine the problem and implement it gradually. For example, we can break a complex task into several simple tasks to complete. There is also a lot of work in software development, construction, and testing that can be automated through a series of execution processes. The Rational build Forge supports flexible process customization, which can be useful in simplifying and streamlining complex issues.

During iterative incremental development, development and testing are alternately performed. After the new code implantation is applied, it needs to be ported to the test environment for testing. To develop and test the B/s architecture of the Java application as an example, we now have two of the same version of the Windows system, one is the developer's use of the development environment, the other is the test environment. The same version of the WebSphere server is installed on both Windows systems, and when the development is complete, the application in the development environment is packaged and then deployed to the tester after the deployment is complete, and the tester is notified of the test work. The traditional way of working is shown in the following illustration:

Figure 1. Traditional ways of working