官术网_书友最值得收藏!

Chapter 2. Installing RTC and WebSphere

Simplicity is prerequisite for reliability

--Edsger W.Dijkstra

In this chapter, we will see different download offerings from Rational Team Concert and the features that distinguish them. Once you are familiar with these offerings, we will download the Enterprise edition and install the server and client parts.

Afterwards, we will do an initial setup and check the basic functionality. We will install WebSphere and do a basic configuration so that the Rational Team Concert server runs in the WebSphere environment. Jazz provides a sandbox mechanism that allows users to play with the full featured projects. From the Eclipse client we will connect to the Jazz sandbox and play with JUnit Project. This will give us an opportunity to set up the example and get introduced to different aspects of the system.

In this chapter, we will look at the following:

  • Rational Team Concert Enterprise Edition Installation
  • WebSphere Application Server configuration
  • Setting up the Jazz Team Server
  • Setting up the Eclipse Client
  • Play with the JUnit Project from Sandbox

Installing Rational Team Concert

Before we install, let's first, explore the different editions available as of this book's publication. Currently there are four versions offered for a variety of operating systems including Windows, Linux, and Solaris as well as other IBM operating systems such as AIX, IBM i, z/OS, and Linux on System z. These differences between these editions is shown in the following feature matrix:

Tip

How can I install Jazz?

Jazz is a technology platform and not a product. Therefore, whichever edition of Rational Team Concert, you get Jazz with it as a server component. No separate installation is necessary (unless you choose to install each component individually).

Understanding RTC editions

IBM RTC is available in four editions, as follows. Each of the editions offer different features, and receive varying levels of support from IBM .The following link helps you get a better understanding:

https://jazz.net/downloads/rational-team-concert/releases/2.0.0.2iFix2

  • Express-C edition: If you are a small team of 10 users or less , Express-C edition is the right one for you. A Tomcat application server and a Derby database are embedded by default. This is available as an all-in-one package with the server, client, and build system and is very easy to install.
  • Express edition: The basic feature set in Express edition is similar to Express-C. However, Express edition has licenses for 50 clients and a limitation on the number of Derby users. Unlike Express-C, which is available only as a ZIP, Express-C can also be installed from the IBM Installation Manager. In both the editions—Express C and Express—some advanced features such as work item customization, LDAP Imports, ClearCase, and ClearQuest bridges are not available.
  • Standard edition: This edition supports 250 users. In addition to Derby, DB2 or Oracle can be used for the Jazz repository.
  • Enterprise edition: This edition supports unlimited users on the server and has many more configuration features, including a mechanism for configuring a second copy of the server to support failover mode.

In this book, we will use the Enterprise edition of Rational Team Concert running with the following configuration:

  • Derby database
  • WebSphere Application Server
  • Eclipse as IDE (client)

Note that this book uses the examples and screenshots from a PC on a Windows XP 32-bit version of Rational Team Concert. The ideal hardware configuration suggested by IBM is the following:

  • Intel Pentium Xeon (32 or 64 bits)
  • 1024 x 786 screen resolution
  • 2 GB RAM
  • 1 GB disk space

Installing Enterprise edition

You can get the Enterprise version of Rational Team Concert from either the IBM or Jazz websites. There are different ways to download the required pieces; choose the method suitable for your download speed and required flexibility:

  • IBM Installation Manager lets you download only the selected components from the web. It manages future updates and gives you the flexibility to manage when you want to download.
  • You can also download the individual server, client, and build system components as ZIP files or with the help of the IBM Installation Manager Local that downloads all the components before install.

We will download the individual ZIP file for the client (client for Eclipse IDE), server, and build system toolkit components for the Windows x86 architecture. Once downloaded, you can expand the contents into a single directory to maintain consistency. If you want to connect the ClearCase and ClearQuest applications to Rational Team Concert, you must also download the individual connectors for each.

Note

The installation directory for Rational Team Concert is now referred to as <root>.

Unless you choose to expand the ZIP files into different locations, the contents typically have the build system, client, repository tools, Source Control Management (SCM) tools, and server components. Let's see a quick overview of what each of these modules does.

Installing Enterprise edition

Build system

Build system is responsible for the build integration in Rational Team Concert, providing the link between the builds, work items, and change sets. It provides the "build engine" and "build tools" modules. Build engine processes build requests from Jazz and executes build scripts; build tools are a set of utilities that communicate the build progress to Jazz repository.

Client

Rational Team Concert client is based on Eclipse. This client module is the window for the developer to work on the project sources, create work items and source code management, and much more. From Rational Team Concert's client, you can work on the build, reports, source code management, collaboration tools, and work items.

Note

Rational Team Concert offers MS Visual Studio client too. However, this book does not use the Visual Studio client.

SCM tools

The Source Control System is accessible through Web UI and client modules. While these modules concentrate on the rich user interface experience for you, the SCM tools provide the command line access to the repository. This is extremely helpful when you want to provide an automation and scripting environment.

You can perform the command line tasks such as listing the various types of files in repository, loading contents of workspace, checking the changes, delivering a change, and creating workspaces.

Repository tools

Rational Team Concert provides the tools to migrate repository from one version of the Jazz server to another one. Also, the repository tools aid you when moving from one database provider to other, either within the same version of Jazz server or across Jazz server versions.

Repository tools help you export the repository data to a TAR file format and import the TAR format file into another Jazz repository. TAR stores the data in an independent format and the importers would take care of how to import that data to a specific database.

Server

This is the heart of Rational Team Concert. The Server component provides all the infrastructure and APIs for the repository management, work item management, deliveries, release management, and build management. It manages the repository and the artifacts in it.

Now that we have the Enterprise edition of Rational Team Concert downloaded and installed, let's take a look at IBM WebSphere configuration.

Tip

What if I want to upgrade from older versions of RTC?

The installation folder of the Enterprise version of RTC has a "help" with instructions on how to upgrade. This help file will give you all the information you need to successfully migrate to a new version.

Configuring WebSphere

IBM WebSphere Application Server is an integrated platform that contains an application server, web development tools, a web server, and additional supporting software and documentation.

Note

In this book IBM WebSphere server is installed on a single machine and a standalone application server profile is created. The standalone application server profile has a server1 application server process. This is the simplest configuration on which WebSphere can be installed.

We also assume no major custom configuration is done for WebSphere server.

Before you start

Before we move to configure WebSphere to work with the Rational Team Concert server, we need to make a few configuration tweaks, as follows. Without these configuration changes, the RTC server on WebSphere may fail.

  • We installed the RTC server as a standalone and it has all the files to run completely independent in Tomcat. However, we need only a subset of the files to make it run on WebSphere. Copy the following files and folders to a directory (now called as <jazzWSRoot>) ready to be used by WebSphere Application Server:
    • The file <root>/server/tomcat/webapps/jazz.war
    • The directory <root>/server/update-site
    • The directory <root>/server/conf
    • The default repository database in <root>/repositoryDB
    • The repository tools in <root>/repotools
    • The directory <root>/server/license-update-site
    • The directory <root>/server/nl1-update-site
    • The directory <root>/server/nl2-update-site
  • We use the Derby database; therefore, make sure that the teamserver.properties file points to the correct database properties. This file is available in the <jazzWSRoot>\conf\jazz directory.

Tip

WebSphere version

At the time of writing this book, the latest version of WebSphere is 7.0.0.9. If you want to install previous versions of the WebSphere, then you need to make sure that you install the WebSphere Application Server Fixes and JVM updates and bring the Application Server version to a minimum of 7.0.0.7.

JVM custom properties

Rational Team Concert needs JVM configuration changes that will help Jazz to know its configuration files and other related settings, as shown in the following screenshot:

  1. Navigate to Servers | WebSphere Application Servers and select the server instance server1.
  2. In the Server Infrastructure section navigate to Administration | Custom Properties.
  3. Click on New, which would display the Name, Value, and Description details, as follows:
    • Name: java.awt.headless Value: true
    • Name: org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin Value: true
    • Name: JAZZ_HOME Value: file:///<jazzWSRoot>/server/conf
    JVM custom properties

Heap size settings

A typical configuration change would be to increase the memory allocation for the server instance of the Rational Team Server. WebSphere comes with the Derby database drivers by default. In case, you want to use different database drivers, then the path to the driver needs to be specified.

The WebSphere Application Server's default memory settings may not be enough for production applications to run. Set the server's initial and maximum virtual memory size from the Integrated Solution Console.

  1. Navigate to Servers | WebSphere Application Servers and select the server instance server1.
  2. From Server Infrastructure section navigate to Java and Process Management | Process Definition.
  3. From the Additional Properties navigate to Java Virtual Machine.
  4. Set the Initial Heap Size to 100.
  5. Set the Maximum Heap Size to 1000.
  6. Click on Apply.

Depending on the software choice and team size, the actual configurations on your production server might change. Remember that the configuration is primarily a function of database, team size, network connectivity, and server memory. The current configuration targets a Derby database, a team size of 10, and the server machine with 3 GB RAM. Except for the WebSphere Application Server and Rational Team Server, no other major application is running on this machine.

Note

By default the initial memory is set around 50 MB and maximum memory is set to 256 MB. Setting the values more than the default could greatly increase the system startup time.

Heap size settings

Changing log details

Rational Team Server uses the BIRT engine for report generation; the default settings produce a lot of verbose information. To prevent this, we need to perform the following:

  1. Navigate to Servers | WebSphere Application Servers and select the server instance server1.
  2. From the Troubleshooting section navigate to Change Log Detail Levels.
  3. Under the Configuration section add org.eclipse.birt.*=severe.
  4. Click Apply to save the configuration.
    Changing log details

Security Settings

Security settings are a crucial part of the configuration and must be set carefully. The following settings specify how Jazz authenticates and authorizes users:

  1. Navigate to Security | Global Security from the Integrated Solution Console.
  2. Check the Enable administrative security option.
  3. Check the Enable the application security option.
  4. Check the disable the Java 2 security option.
    Security Settings

Finally, make sure that the WebSphere security setting Use available authentication data when an unprotected URI is accessed is checked. This can be done from Security | Global security | Web and SIP Security | General Settings.

Security Settings

With this, we have done all the necessary configuration changes and are ready to restart the server.

Deploying Jazz Team Server on WebSphere

Now that we've configured WebSphere and restarted, we will install the Jazz Team Server on to WebSphere Application Server server1.

From the Integrated Solutions Manager, navigate to Applications | New Applications. Click on the New Enterprise Application.

Deploying Jazz Team Server on WebSphere

You will be asked to enter a local or a remote file system path. Enter the jazz.war path from the directory that you previously copied to, for example, D:\RTC\jazz\server4WSA\jazz.war referred to as <jazzWSRoot>/jazz.war.

Click Next. In the next step, you can choose either the Fast Path or Detailed installation option. The Fast Path installation assumes several default values and you are asked for an input only when required. In this case, we will set up the WAR file with the Detailed installation option. In the latest version of the WebSphere application server there are 10 steps in the Detailed installation option.

Deploying Jazz Team Server on WebSphere

In the first step you can optionally change the name of the Application from jazz_war (set by default) to any meaningful name that you like. This is the application name that WebSphere knows our JTS by. You can continue the steps from 1 to7 without any modifications. In step 7, select the jazz.war web module to map the web module to a contained virtual host.

Deploying Jazz Team Server on WebSphere

In the next step (step 8) change the context root for the web module jazz.war from "/" to "/jazz". Click Next (step 9) to set up the Security roles to users and groups. Remember that all roles defined by a Rational Team Server application must map to users or groups defined by the WebSphere domain registry. You may have already imported the LDAP users and groups, or created users and groups in WebSphere Application Server. Select each of the user roles and map them to appropriate groups or users.

The final step (step 10) gives an overview of the configuration and click Finish to deploy the application. Integrated Solutions Console shows a high level deployment log on the screen. Once the deployment is finished successfully save the changes directly to master configuration by clicking Save directly to master configuration.

From the main menu, navigate to Applications | WebShpere enterprise applications. Select the name of the application you configured for Jazz and start the server. It will take couple of seconds to start the application and a green arrow is displayed next to the server for a successful startup.

Deploying Jazz Team Server on WebSphere

Testing the installation

Once the Rational Team Server (also called the Jazz Server) successfully starts, we should be able to access the Team Server URL https://localhost:9443/jazz/setup for the initial setup steps. If you would like to test it from another machine you should be able to substitute the localhost with the machine name or IP address to access the application.

In most cases, the installation should be successful and the application should start without any issues. In case you experience problems, check if prerequisites are missing. Typical problems are as follows:

  • Error 404: ProxyServlet: /jazz/setup
  • A blank screen appears with message as Loading
  • You are not authorized to access the Jazz Team Server Admin UI

In each of the previous scenarios, we really want to make sure that the following points are carefully checked and verified. Sometimes, uninstalling and reinstalling of the Jazz application may be required.

  1. Check if the relative path of the database is replaced with the absolute path in the <jazzWSRoot>/server/conf/jazz/teamserver.properties file.
  2. Make sure that the JAZZ_HOME property is set to file:///<jazzWSRoot>/server/conf without spaces in the path and the physical files exist.
  3. Make sure that the Security settings are done exactly as described.
    • Enable administrative security
    • Enable application security
    • Disable all Java 2 options
  4. Make sure that you enable the Use available authentication data when an unprotected URI is accessed option from Global Security Settings.
  5. In step 7 of the application war installation, ensure you selected the Web module mapping.
  6. In step 8, check if you have the application context as "/jazz".
  7. Finally, check if the application roles have been mapped to the domain user groups or users in step 9.

This check list can also be used before the final installation of the Rational Team Server application. Make sure that you can access the application and log into it. In the next section, we will set up the Team Server.

主站蜘蛛池模板: 黄骅市| 建阳市| 鄂伦春自治旗| 吐鲁番市| 望都县| 蓝田县| 阳信县| 沙雅县| 偃师市| 沁水县| 西充县| 和顺县| 通许县| 罗江县| 阳曲县| 宝应县| 靖西县| 拉萨市| 德安县| 怀仁县| 武汉市| 松潘县| 饶河县| 绍兴县| 潢川县| 城口县| 全州县| 安康市| 崇礼县| 页游| 桦甸市| 广昌县| 招远市| 宁安市| 辽阳市| 新疆| 利川市| 庆阳市| 尖扎县| 南部县| 洞口县|