Software Delivery and Lifecycle Patterns for Pure Application System Workbook - Preview

Authors: TingHuiLi , RobbieMinshall, MaryYost, ZhiChengLiu, VictorSosa
Build basis: Products, editions and versions as applicable

Overview

The following page is a preview and the full lab is also attached below for download. The objective of this Hands-On Workshop is to provide the customers with an opportunity to discover how to deploy and experience the IBM Software Delivery and Lifecycle Patterns on IBM PureApplication System; moreover, Rational License Key Server is deployed as a License server shared service.

IBM Software Delivery and Lifecycle Patterns are available for the following applications:

• Rational solution for Collaborative Lifecycle Management

• Rational Application Developer

Introduction

The most problematic stage of any Application Development Lifecycle is configuration and integration process. The IBM Software Delivery and Lifecycle Patterns focus on a simple user experience and time to value by removing configuration and integration pain. Customers can deploy this pattern within 35-40 minutes (as against 2-5 business days to set up an equivalent physical environment) and get access to a fully functioning Collaborative Lifecycle Management (CLM) environment.

This workshop will take the participant through a series of labs. IBM Software Delivery and Lifecycle Patterns allow users to use the virtual systems patterns to deploy fully configured and functioning applications to IBM private cloud platforms. The deployed instances of the applications are ready to use. Each pattern includes all related software needed for the solution, including an operating system, databases, application servers, and other IBM software.

The general flow of the workshop will be:

• Deploy the Rational solution for collaborative lifecycle management pattern.

• Access the Rational solution for collaborative lifecycle management.

• Deploy the Rational solution developer pattern.

• Access the Rational solution developer.

• Demonstrate MONEY THAT MATTERS sample project.

The workshop will concentrate on deploying IBM Software Delivery and Lifecycle Patterns and demonstrating a sample application referred to as JKE -Money That Matters, created for a fictional bank called JKE.

The following symbols appear in this document at places where additional guidance is available.

Icon	Purpose	Explanation
	Trouble-shooting	This symbol indicates that you can fix a specific problem by completing the associated troubleshooting information.
	Important!	This symbol calls attention to a particular step or command. For example, it might alert you to type a command carefully because it is case sensitive.
	Information	This symbol indicates information that might not be necessary to complete a step, but is helpful or good to know.

Lab 1 Building an instance with the Rational® solution for Collaborative Lifecycle Management (CLM) pattern

1.1 Introduction to the CLM pattern

This solution connects analysts, developers, and testers through tools. The pattern includes a fully configured multi-tier department-scale topology. It is configured and tuned based upon best practices discovered through testing. The included reverse proxy server allows for future scaling flexibility. The following products are included, along with the RedHat(r) Enterprise Linux(r) version6.3 (Santiago) operating system. See Rational solution for Collaborative Lifecycle Management pattern for the full list of software and tools included in the pattern:

• IBM Rational Team Concert

• IBM Rational Quality Manager

• IBM Rational Requirements Composer

• IBM WebSphere® Application Server

• IBM DB2® ESE

1.2 Deploying the Rational® solution for Collaborative Lifecycle Management (CLM) pattern

1. Log on to IBM PureApplication™ System (Workload Console tab).
2. Open Patterns > Virtual Systems.
3. Select IBM Collaborative Lifecycle Management 4.0.2.0 Departmental Topology 1.0.0.0. You can use a filter to constrain your search.
4. Click Deploy
5. Enter a name for the deployed instance in the prompt dialog.
6. Configure the environment and schedule.
7. Click Configure virtual parts.
8. Click Standalone server. A list of deployment parameters is displayed.
9. Specify deployment parameter values.
10. Click DB2 Enterprise. A list of deployment parameters is displayed.
11. Specify deployment parameter values. The following parameter is required and normally has no default value.
12. Click IBM HTTP servers. A list of deployment parameters is displayed.
13. Click OK to close the deployment parameters list.
14. Click OK to close the deploy dialog.
15. Check the CLM instance deployed successfully

Jazz server instance URI : This lab has created the Jazz server instance URI: https://fit-lab4-3.rtp.raleigh.ibm.com/ccm. You can use this URI to deploy the Rational Application Developer pattern in later Lab.

1.3 Summary

In this lab you deployed an instance of the virtual system pattern to the cloud using IBM® PureApplication™ System. After deployment, you can access the CLM applications. Administrators and end users each have unique URLs to use for access through the web in the next lab. Administrators can also access the application components by using a VNC client. To help new users, a sample project called Money That Matters is included and available from the console.

At the conclusion of the deployment process, customers deploy this pattern within 35-40 minutes and get access to a fully CLM environment. This instance will be used to demonstrate the CLM applications later in the workshop.

Lab 2 Using Rational® solution for Collaborative Lifecycle Management in the cloud

2.1 Introduction

Users and administrators use a web browser to access a deployed instance of CLM in the cloud. Access the desired application in the desired role. On the other hand, Access CLM, the Money that Matters sample application, and administrative consoles for CLM components from the workload console.

Applications are abbreviated as follows:

• CCM: Change and Configuration Management, Rational® Team Concert
• JTS: Jazz™ Team Server
• QM: Rational Quality Manager
• RM: Rational Requirements Composer

2.2 Accessing Rational solution for Collaborative Lifecycle Management using a web browser

Administrators log in to the administrative site using the CLM_ADMIN_USERNAME and CLM_ADMIN_PASSWORD set when the instance was deployed.

• CCM: https://ihs_hostname/ccm/admin
• JTS: https://ihs_hostname/jts/admin
• QM: https://ihs_hostname/qm/admin

End users log in to the end-user site.

• CCM: https://ihs_hostname/ccm/web
• QM: https://ihs_hostname/qm/web
• RM: https://ihs_hostname/rm/web

Important: For ihs_hostname above, use the host name of the reverse proxy server. Do not use an IP address or access the application server without going through the reverse proxy server.

1. Using a web browser, you access the deployed instance and you obtain the host name of the reverse proxy server from the CLM instance.It is located in the IHSOnlyNode. Users must use this host name in the access URLs.
2. Open a web browser and log in the CCM administrative site: https://ihs_hostname/ccm/admin with Administrators(CLM_ADMIN_USERNAME)
3. Log in the CCM administrative site successfully
4. Open a web browser and log in the JTS administrative site: https://ihs_hostname/jts/admin with Administrators (CLM_ADMIN_USERNAME)
5. Log in the JTS administrative site successfully
6. Open a web browser and log in the QM administrative site: https://ihs_hostname/qm/admin with Administrators (CLM_ADMIN_USERNAME)
7. Log in the QM administrative site successfully

2.3 Accessing Rational solution for Collaborative Lifecycle Management from the deployed instance

1. Log on to IBM PureApplication™ System (Workload Console tab).
2. Open Instances > Virtual Systems.
3. Select the instance you deployed.
4. In the Details pane, expand Virtual Machines and your instance information.
5. Scroll down to the Consoles section.
6. Click a link VNC: when you click this link, a new browser tab is opened with the VNC viewer.
7. Click a link Jazz Team Server Administration: Goes to the administration page.
8. Click a link Change and Configuration Management: Goes to the administration page.
9. Click a link Quality Management: Goes to the administration page.
10. Click a link Money That Matters Sample Project: This is a sample project that is provided with CLM.

Go to ‘Change and Configuration Management, Rational® Team Concert’ logon page of the a fictitious banking company, JKE Banking sample project

2.4 Summary

In this lab, you use a web browser to access a deployed instance of CLM in the cloud and access the applications of CLM. You do not need to implement any additional configuration and integration steps and can use functionalities, which CLM provides integrations across the Change and Configuration Management, Requirements Management, and the Quality Management Jazz-based applications, to connect the work of analysts with development and test teams. CLM enables you to link artifacts for traceability.

In the next lab you will use the Jazz URI of The Rational® solution for Collaborative Lifecycle Management (CLM) in this lab to deploy the Rational Application Developer (RAD) pattern.

Lab 3 Building an instance with the Rational Application Developer pattern

3.1 Deploying the Rational® Application Developer from the Virtual System Pattern makes an instance of it available in the cloud.

1. Log on to IBM PureApplication™ System (Workload Console tab).
2. Open Patterns > Virtual Systems.
3. Select IBM Rational Application Developer Pattern v8.5.1 iFix 1 1.0.0.0. You can use a filter to constrain your search.
4. Click Deploy
5. Enter a name for the deployed instance in the prompt dialog.
6. Configure the environment and schedule.
7. Click Configure virtual parts.
8. Click Rational Application Developer. A list of deployment parameters is displayed.
9. Specify deployment parameter values.
10. Click OK to close the deployment parameters list.
11. Click OK to close the deploy dialog.
12. Check the instance deployed successfully.

The following parameters are required in step 9 above. The password parameters have no default values and should be left blank.

• Password (root), plus verification

• Password (virtuser), plus verification

• Jazz server instance URI, https://fit-lab4-3.rtp.raleigh.ibm.com/ccm

Important! Please ensure that the name is entered exactly as shown above using Lab1 Jazz server instance URI. This will be important for later labs.

• Jazz user name

• Jazz password

• Password (VNC user), plus verification

3.2 Accessing Rational Application Developer using VNC through a deployed instance

1. Log on IBM PureApplication™ System (Workload Console tab).
2. Open Instances > Virtual Systems.
3. Select the instance you deployed.
4. In the Details pane, expand Virtual Machines and your instance information.
5. Scroll down to the Consoles section and click the VNC link to log in to the application. A new browser tab is opened with the VNC viewer.
6. Log in using the VNC password for virtuser.

3.3 Summary

In this lab, you created the instance of the Rational Application Developer (RAD) pattern. The Jazz URI of CLM and the CLM user (deb) were used to deploy RAD. In the next lab you will experience Money That Matters Sample Project with different project roles in the cloud and be familiar with CLM applications.

Lab 4 DEMONSTRATING MONEY THAT MATTERS SAMPLE PROJECT

4.1 Introduction of the Money That Matters sample

You can experience all functionalities directly, which are demonstrated by the Money That Matters sample after the instances of CLM and RAD are deployed in the cloud. Collaborative Lifecycle Management comes with the Money That Matters sample that is based on a fictitious banking company, JKE Banking.

The detailed scenario and supporting lifecycle project and assets enable you to step through the practices, activities, and collaboration that occur in Sprint 2 of the CLM lifecycle. The Money that Matters sample includes the following artifacts:

• The Money that Matters Lifecycle scenario that sets the context for the Money That Matters initiative and provides a detailed description of the scenario workflow.

• The JKE Banking lifecycle project with associated artifact containers for requirements management, change and configuration management, design management, and quality management.

You will experience two roles (development lead and Scrum Master: Marco and Developer: Deb) to understand a specific CLM usage example, and highlights lifecycle collaboration and key CLM integration points in this lab.

The whole flow of the demonstration will be:

• Plan Development Effort

• Explore the lifecycle collaboration from development perspective
• Prepare for Sprint Shutdown

4.2 Plan Development Effort

The development lead and Scrum Master (Marco) completes a sprint plan that contains developer story work items that are linked to requirements and test cases.

1. Go to https://fit-lab4-3.rtp.raleigh.ibm.com/ccm/web
2. Log on by entering marco as the user name and password.
3. Use the quick search feature to find a plan. In the Quick Search, click Search All Work Items icon.
4. Select Plans > Current Plans and specify the following filter backlog.
5. Click Product Backlog [Product Backlog].
6. View the product backlog as Ranked List, which is the default view.
7. Add the story to the release plan, from the Plan For list, select Release 1.0.
8. Click the action menu to the left of the Allocate Dividends To Multiple Causes story and set Assign To Owner to Deb.
9. Save the plan. The story is automatically saved when you save the plan
10. Open the Release 1.0 Backlog plan
11. Drag the Allocate Dividends To Multiple Causes story from Release 1.0 to Sprint 2.
12. Click the Filter icon, and select Execution Items to exclude non-plan work item types such as tasks and defects.
13. Click the action icon to the left of the Allocate Dividends To Multiple Causes story and click Add Link > Tested By Test Case.
14. Select Create new to create a test case and then click OK.
15. Create the test case Allocate Dividends To Multiple Causes and Click Save
16. Verify that the link was created by using the rich hover for the story. Tested By Test Case points to the new test case.
17. Marco then creates a child development task by using the action menu in the plan, from the View As list, select Work Breakdown.
18. Click the action icon next to the Allocate Dividends To Multiple Causes story, and click Create Child Work Item > Task.
19. Use the inline editor to enter this summary Implement - Allocate Dividends To Multiple Causes. Then, press Enter.
20. From the Plan For list, select Sprint 2 and From the Plan For list, select Sprint 2 and Set Assign To Owner as Deb then Click Save.
21. Marco also creates a child task for a tester to implement the test case.
22. Click Save and Log out and close the browser.

4.3 Explore the lifecycle collaboration from development perspective

When the instance was deployed, the RTC connection was automatically configured in the specified workspace. To verify the repository connection do the following:

1. Open Work Items perspective. Go to Window > Open Perspective > Work Items.
2. Open Team Artifacts view.
3. Expand Repository Connections.

Even though the RTC connection was configured at deployment time by specifying the Jazz server URI and Jazz credentials, the workspace has no Project Area configured. This means that you cannot collaborate to any project yet. This is a really simple task though. Follow these steps:

• Right click on the repository in Repository Connections.
• Select Manage Connected Project Areas.
• Select JKE Banking.
• Click Finish.

Note JKE Banking Project Area is created in the workspace.

Now that the Project Area is created in the workspace, you can load the source code from the repository into the workspace.

1. Open Team Artifacts view.
2. Expand My Repository Workspaces.
3. Expand Deb BRM Stream Workspace.
4. Right click on Deb BRM Stream Workspace and select Load...
5. The Load Repository Workspace dialog will come up.
6. Select Find and load Eclipse projects.
7. Click Next.
8. Verify all projects are selected.
9. Click Finish.

The download process will start. It may take a while depending on your network capabilities.

To see the downloaded artifacts, follow these steps:

1. Open Java EE perspective.
2. Open Enterprise Explorer view.

To open the list of work items assigned to the logged user, you can use the queries that are pre-configured for every user account. You can also create your own queries and share them with anyone in the team.

To open the current work assigned to the current user, do the following:

1. Open Work items view.
2. Expand JKE Banking Project Area.
3. Drill down to Work Items > Shared Queries > Predefined.
4. Double click on My current work.

This will open a list of work items in the Work Items view. You can double click on any of them to see the content of the work item.

After a code change has happened, it can be associated to a work item so that work can be tracked. These changes can be seen in Pending Changes view and then can be associated and delivered to the main stream. In this example, work done for work item “Some messages are not externalized” has been done and it is waiting to be delivered. Follow the next steps to check in and deliver code.

1. Open Pending Changes view.
2. Drill down to Deb BRM Stream Workspace > Java UI > Unresolved > JKEJavaUI/src/com/jke/ui.
3. Double click on each of the changes to review them.
4. Right click on JKEJavaUI/src/com/jke/ui and select Check In > New Change set.
5. The decorators of the changes will look different with an Outgoing parent node.
6. Right click on node.
7. Select Associate Work Item...
8. Select the desired work item, “Some messages are not externalized” in this scenario.
9. Click OK.

The change set is now related to a work item, so it can be delivered to the stream.

1. Right click on the change set.
2. Select Deliver.

This action will put the changes directly into Deb BRM Stream Workspace making it available to all team members. Locally, the RTC component will not show that change anymore.

Now the work item can be resolved.

1. Open Work Items view.
2. Open the work item by double-clicking on it.
3. Locate the status of the work item.
4. Change it to Resolved.
5. Click on Save.

If you run “My current work” query, you should not see this work item anymore.

4.4 Prepare for Sprint Shutdown

Increased the emphasis on closing new development work and improving the quality of the planned features

1. Go to https://fit-lab4-3.rtp.raleigh.ibm.com/ccm/web

2. Log in by entering marco as the user name and password

3. Explore the Planning tab

• The Current Plans widget indicates how much of Sprint 2 is complete. Sprint 2 has many open stories. Considering that the sample assets assume you are at the start of the sprint, this isn't a surprise to us. If this was a real life situation, the ScrumMaster would be concerned.
• Note the Open Impediments widget. As ScrumMaster, you might want to address this now, or plan to address it for the next release as part of your retrospective.
• Note the Resolved (current iteration) widget. This widget indicates what is complete, but it does not indicate what is left to do.

4. Explore the Requirements tab

• Work toward closing the items in the Open Requirement Change Requests widget.
• Watch the Defects affecting Requirements widget to ensure that you understand which defects to prioritize or triage.
• Work toward closing any items in the Open Impact Analysis Tasks widget.

5. Explore the Development tab

• Note the Open Stories (current iteration), Owned By widget. The ScrumMaster must address all of those unassigned stories. Five stories are assigned and still open. This area needs attention.
• Note the Open Work Items (current iteration), Severity widget. Before the sprint can be declared complete, many stories must be closed.

6. Explore the Testing tab

• The Defects blocking Tests widget is empty, which is a good thing. This widget applies to the entire release, not only the current sprint. Keep this widget empty. The ScrumMaster must vigilantly check this widget.
• The Defects affecting Tests (current iteration) widget ideally should be empty, which is a good thing. This widget applies to the current sprint. As you move from sprint to sprint, manage the amount of debt you are incurring.
• The Stories tested successfully widget contains the story that you completed in the earlier lesson. In this widget, you want to see that all the stories for this sprint are tested successfully.

7. On the Trends tab, explore the Sprint Burndown chart. Ideally, the chart trends downward to 0 by following the planned line.

8. Explore the Stabilization tab

4.5 Summary

In this lab, you experience the Money That Matters sample. The development lead and Scrum Master created tasks and test cases based on the project plan. The task and test case were assigned to corresponding developer and tester. Developer worked on work items, changed the code, and delivered the code using the RTC client. After the task and test cases were completed, the team leads steer the iteration toward closure. The final scenario explores how a team uses dashboards, release plan views, and lifecycle traceability queries to determine the status of the application that is being developed. By customizing the feature and release team dashboards, team members, product owners, testers and executives, can easily see what work remains. You can explore on your own to see the entire set of queries, charts, and reports that the team uses to manage the end game.

Lab 5 Building Rational License Key Server

5.1 Introduction of Rational License Key Server

This product is deployed as a License server shared service. A shared service provides common services for use by other deployments in the cloud environment. After it is deployed, deployments of Rational solution for Collaborative Lifecycle Management and IBM Rational Application Devel-oper look up the service, which provides automated license management for them. Administrators can manage a single pool of licenses for all applications in the cloud. Users can access the de-ployed applications without searching for a license to use.

5.2 Importing the shared service pattern type

1. Log into IBM PureApplication System, and click Workload Console.
2. Click Cloud > Pattern Types.
3. Press the green plus (+) symbol to open the Install a pattern type dialog box.
4. Press Browse to locate the file, which must have a .tgz extension.
5. Press OK to begin the importing process.

5.3 Accepting the license agreement & enabling the pattern

1. Go to Cloud > Pattern Types.
2. Look for Rational License Key Server Pattern 1.0.0.0. You can filter out the patterns for a quick search.
3. Select the pattern and wait for the details in the pane at the right.
4. You will see License Agreement: Not Accepted [License...] and Status: Not Accepted [En-able All...].
5. Press [License...].
6. Once the License agreement dialog box opens, press Accept to accept the agreement.
7. Once that has processed, press [Enable All...] to enable the pattern type.

5.4 Deployment of the pattern

1. Go to Cloud > Shared Services.
2. Look for License Server Shared Service 1.0.0.0. You can filter out the patterns for a quick search.
3. Click on License Server Shared Service 1.0.0.0 and wait for the details in the pane at the right.
4. Click on Deploy.
5. The Configure and deploy a shared service dialog box will open.
6. Press OK on the Configure and deploy a shared service dialog box to open the Deploy Vir-tual Application dialog box.
7. On the Deploy Virtual Application dialog box, you may configure the Virtual Application.
8. Once done configuring, press OK to start the deployment of the shared service.

5.5 Summary

In this lab you deployed an instance of the Rational License Key Server Shared Service to the cloud using IBM® PureApplication™ System. In the next lab you will learn how to use and manage the Rational License Key Server Shared Service.

Lab 6 Using Rational License Key Server

6.1 Accessing the management console

1. Go to Instances > Shared Services.
2. Look for License Server Shared Service 1.0.0.0. You can filter out the patterns for a quick search.
3. Select the pattern and wait for the details in the pane at the right.
4. Press Manage.
5. Once a new window opens, you will see the Virtual Application Console.

6.2 Operations

1. Once in the Virtual Application Console, press the Operations tab.
2. Press SS.RLKS and wait for the details in the pane at the right.
3. Press the twisty to expand an operation.
4. If parameters are required, they will appear with a red asterisks before the parameter name.
5. Press Submit to launch an operation.
6. Results of operations appear in the Operation Execution Results pane at the bottom.

6.2.1 Start RLKS Instance

This operation has no parameters. The operation starts Rational License Key Server. It does not start the shared service instance.

6.2.2 Stop RLKS Instance

This operation has no parameters. The operation stops Rational License Key Server. It does not stop the shared service instance.

6.2.3 Add License File

1. Press Edit to open the Select File dialog box.
2. On the Local tab, press Browse to open the Choose File to Upload dialog box. (Even though the HTTP/HTTPS tab appears on the Select File dialog box, HTTP/HTTPS transfer is not supported.)
3. Once the file is located press OK on both the Choose File to Upload dialog box and then the Select File dialog box.
4. Destination File Name is the name to save the license file as on the shared service. This name is the only reference to license files once on the shared service. Only use alphanu-meric characters as special characters can cause issues during file upload or server start.

6.2.4 Activate License File

This operation requires one parameter. File Name is the name of the file saved on the shared service to activate.

6.2.5 Delete License File

This operation requires one parameter. File Name is the name of the file saved on the shared service to delete. The active license file cannot be deleted.

6.2.6 Get a List of License Files

This operation has no parameters. It will return a list of license files saved on the shared ser-vice.

6.2.7 Get Status

This operation has no parameters. It returns a simple message stating if Rational License Key Server is running. Additional details and the log file from RLKS (lmgrd.log) are printed in trace.log.

6.2.8 Viewing the logs

1. Once in the Virtual Application Console, press the Logging tab.
2. Press the twisty on the name of the shared service instance. It will begin with SS.
3. Press the twisty on IWD Agent.
4. Press the twisty which ends in .RLKS.
5. Press trace.log and wait for the details in the pane at the right.

6.3 Summary

In this lab, you use a web browser to access a deployed instance of Rational License Key Server Shared Service and perform a serial of operations which helps to manage the Rational License Key Server.

The full lab is attached below for download

External links:

• IBM
• Learn more about IBM Software Delivery and Lifecycle Patterns v1.0
• Learn more about IBM PureApplication System.
• Learn more about Rational License type definitions.
• Learn more about Rational Application Developer 8.5.1.
• Learn more about Rational Team Concert client 4.0.2.