tec workbook template - jazz.net · web viewlog on to ibm pureapplication system (workload console...
TRANSCRIPT
IBM Software An IBM Hands-On Workshop
IBM Software Delivery and Lifecycle Patterns
WorkBook version 6.20.13
Contents Page 1
IBM Software An IBM Hands-On Workshop
© Copyright IBM Corporation, 2023
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software An IBM Hands-On Workshop
ContentsLAB 1 BUILDING AN INSTANCE WITH THE RATIONAL® SOLUTION FOR COLLABORATIVE
LIFECYCLE MANAGEMENT (CLM) PATTERN............................................................51.1 INTRODUCTION TO THE CLM PATTERN............................................................................................51.2 DEPLOYING THE RATIONAL® SOLUTION FOR COLLABORATIVE LIFECYCLE MANAGEMENT (CLM)
PATTERN.......................................................................................................................................51.3 SUMMARY....................................................................................................................................16
LAB 2 USING RATIONAL® SOLUTION FOR COLLABORATIVE LIFECYCLE MANAGEMENT IN THE CLOUD.......................................................................................................182.1 INTRODUCTION............................................................................................................................182.2 ACCESSING RATIONAL SOLUTION FOR COLLABORATIVE LIFECYCLE MANAGEMENT USING A WEB
BROWSER....................................................................................................................................182.3 ACCESSING RATIONAL SOLUTION FOR COLLABORATIVE LIFECYCLE MANAGEMENT FROM THE
DEPLOYED INSTANCE...................................................................................................................252.4 SUMMARY....................................................................................................................................34
LAB 3 BUILDING AN INSTANCE WITH THE RATIONAL APPLICATION DEVELOPER PATTERN353.1 DEPLOYING THE RATIONAL® APPLICATION DEVELOPER FROM THE VIRTUAL SYSTEM PATTERN
MAKES AN INSTANCE OF IT AVAILABLE IN THE CLOUD.....................................................................353.2 ACCESSING RATIONAL APPLICATION DEVELOPER USING VNC THROUGH A DEPLOYED INSTANCE....413.3 SUMMARY....................................................................................................................................45
LAB 4 DEMONSTRATING MONEY THAT MATTERS SAMPLE PROJECT................................464.1 INTRODUCTION OF THE MONEY THAT MATTERS SAMPLE................................................................464.2 PLANNING DEVELOPMENT EFFORT...............................................................................................464.3 EXPLORING THE LIFECYCLE COLLABORATION FROM DEVELOPMENT PERSPECTIVE...........................584.4 PREPARING FOR SPRINT SHUTDOWN............................................................................................714.5 SUMMARY....................................................................................................................................76
APPENDIX A. NOTICES...........................................................................................................77APPENDIX B. TRADEMARKS AND COPYRIGHTS........................................................................79
Contents Page 3
IBM Software
Overview 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.
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 Pat-terns allow users to use the virtual systems patterns to deploy fully configured and functioning applica-tions 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 demon-strating a sample application referred to as JKE -Money That Matters, created for a fictional bank called JKE.
Page 4 Innovate 2013 Session XXXX
IBM Software
Icons
The following symbols appear in this document at places where additional guidance is available.
Icon Purpose Explanation
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 neces-sary to complete a step, but is helpful or good to know.
Trouble-shooting
This symbol indicates that you can fix a specific problem by completing the associated troubleshooting information.
Overview Page 5
IBM Software
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) ver-sion6.3 (Santiago) operating system. See Rational solution for Collaborative Lifecycle Manage-ment 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 Lifecy-cle 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.
IBM Software
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.
IBM Software
8. Click Standalone server. A list of deployment parameters is displayed.
9. Specify deployment parameter values.
Parameters for the Standalone server part
Parameter Description
User running VNC process Default: virtuser
The VNC session is run by the specified user. It should al-ways be virtuser.
Password for VNC user Default: none
The password for the VNC user session. It is not the same as the operating system password. If the specified value is less that six characters long, zeroes are added to the right to make the value six characters long. Example: 123 be-come 123000.
Screen Resolution (VNC) Default: 1280x1024.
Screen resolution for the VNC remote desktop session.
VNC uses SSH Tunneling Default: False
SSH tunneling adds more security to the VNC session.
CLM_ADMIN_USERNAME Default: clmadmin
The user name of the CLM administrator. If LDAP is en-abled for use with the pattern, this user should be an exist-ing user registered with the LDAP server.
CLM_ADMIN_PASSWORD Default: none
The password for the CLM administrator
CONFIG_CLM_FOR_LDAP Default: N
If set to Y, the deployed instance use LDAP as the user reg-istry.
IBM Software
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.
Parameters for the DB2 Enterprise part
Parameter DescriptionPassword (db2inst1) Default: none
The password for db2inst1.
IBM Software
12. Click IBM HTTP servers. A list of deployment parameters is displayed.
Parameters for the IBM HTTP server part
Parameter DescriptionUser running VNC process Default: virtuser
The VNC session is run by the specified user. It should always be virtuser.
Password for VNC user Default: none
The password for the VNC user session. It is not the same as the op-erating system password. If the specified value is less that six char-acters long, zeroes are added to the right to make the value six char-acters long. Example: 123 become 123000.
Screen Resolution (VNC) Default: 1280x1024.
Screen resolution for the VNC remote desktop session.
VNC uses SSH Tunneling Default: False
SSH tunneling adds more security to the VNC session.
KEYDBPW Default: ecl11ipse
Password for the SSL keystore
13. Click OK to close the deployment parameters list.
IBM Software
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 SummaryIn 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. Administra-tors 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.
IBM Software
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 IntroductionUsers 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 work-load 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.
IBM Software
2. Open a web browser and log in the CCM administrative site: https://ihs_hostname/ccm/ad-min with Administrators(CLM_ADMIN_USERNAME)
3. Log in the CCM administrative site successfully
IBM Software
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
IBM Software
6. Open a web browser and log in the QM administrative site: https://ihs_hostname/qm/admin with Ad-ministrators (CLM_ADMIN_USERNAME)
7. Log in the QM administrative site successfully
IBM Software
2.3 Accessing Rational solution for Collaborative Lifecycle Management from the deployed instance1. Log on to IBM PureApplication™ System (Workload Console tab).
2. Open Instances > Virtual Systems.
3. Select the instance you deployed.
IBM Software
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.
Log in using the VNC password for virtuser
IBM Software
Log on successfully.
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.
IBM Software
9. Click a link Quality Management: Goes to the administration page.
IBM Software
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 SummaryIn this lab, you use a web browser to access a deployed instance of CLM in the cloud and ac-cess the applications of CLM. You do not need to implement any additional configuration and in-tegration 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.
IBM Software
Lab 3 Building an instance with the Rational Application De-veloper 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
IBM Software
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.
IBM Software
9. Specify deployment parameter values.
The following parameters are required. 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
10. Click OK to close the deployment parameters list.
11. Click OK to close the deploy dialog.
IBM Software
12. Check the instance deployed successfully.
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.
IBM Software
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.
IBM Software
3.3 SummaryIn 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 ex-perience Money That Matters Sample Project with different project roles in the cloud and be fa-miliar with CLM applications.
Lab 4 DEMONSTRATING MONEY THAT MATTERS SAMPLE PROJECT
4.1 Introduction of the Money That Matters sampleYou can experience all functionalities directly, which are demonstrated by the Money That Mat-ters sample after the instances of CLM and RAD are deployed in the cloud. Collaborative Lifecy-cle 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 Mat-ters 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 man-agement.
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 devel-oper 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.
IBM Software
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.
IBM Software
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
IBM Software
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
The development lead, Marco, creates a test case by using the action menu in the context of the plan.
IBM Software
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.
IBM Software
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 Multi-ple Causes. Then, press Enter.
20. From the Plan For list, select Sprint 2 and From the Plan For list, select Sprint 2 and Set As-sign To Owner as Deb then Click Save.
IBM Software
21. Marco also creates a child task for a tester to implement the test case.
Click the action icon next to the Allocate Dividends To Multiple Causes story, and then click Create Child Work Item > Task
22. Click Save and Log out and close the browser.
4.3 Explore the lifecycle collaboration from development per-spectiveWhen the instance was deployed, the RTC connection was automatically configured in the spec-ified 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.
IBM Software
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:
1) Right click on the repository in Repository Connections.
2) Select Manage Connected Project Areas.
3) Select JKE Banking.
4) 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.
IBM Software
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.
IBM Software
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.
IBM Software
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 <Enter a Comment> node.
7. Select Associate Work Item...
8. Select the desired work item, “Some messages are not externalized” in this scenario.
IBM Software
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.
IBM Software
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
IBM Software
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 con-cerned.
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.
IBM Software
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 ScrumMas-ter 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 ear-lier lesson. In this widget, you want to see that all the stories for this sprint are tested suc-cessfully.
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
IBM Software
4.5 SummaryIn this final 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 com-pleted, 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.
Appendix A. NoticesThis information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Con-sult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this docu-ment. The furnishing of this document does not grant you any license to these patents. You can send li-cense inquiries, in writing, to:
IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property De-partment in your country or send inquiries, in writing, to:
IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORA-TION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EX-PRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-IN-FRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without in-curring any obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore, the re-sults obtained in other operating environments may vary significantly. Some measurements may have
IBM Software
been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their pub-lished announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those prod-ucts.
All statements regarding IBM's future direction and intent are subject to change or withdrawal without no-tice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an ac-tual business enterprise is entirely coincidental. All references to fictitious companies or individuals are used for illustration purposes only.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing ap-plication programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all con-ditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
Appendix B. Trademarks and copyrightsThe following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
IBM AIX CICS ClearCase ClearQuest Cloudscape
Cube Views DB2 developerWorks DRDA IMS IMS/ESA
Informix Lotus Lotus Workflow MQSeries OmniFind Rational Team Concert
Rational Redbooks Red Brick RequisitePro System i uDeploy
System z Tivoli WebSphere Workplace System p
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trade-marks of Adobe Systems Incorporated in the United States, and/or other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of The Minister for the Cabinet Of-fice, and is registered in the U.S. Patent and Trademark Office.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
NOTES
NOTES
© Copyright IBM Corporation 2023.
The information contained in these materials is provided for
informational purposes only, and is provided AS IS without warranty
of any kind, express or implied. IBM shall not be responsible for any
damages arising out of the use of, or otherwise related to, these
materials. Nothing contained in these materials is intended to, nor
shall have the effect of, creating any warranties or representations
from IBM or its suppliers or licensors, or altering the terms and
conditions of the applicable license agreement governing the use of
IBM software. References in these materials to IBM products,
programs, or services do not imply that they will be available in all
countries in which IBM operates. This information is based on
current IBM product plans and strategy, which are subject to change
by IBM without notice. Product release dates and/or capabilities
referenced in these materials may change at any time at IBM’s sole
discretion based on market opportunities or other factors, and are not
intended to be a commitment to future product or feature availability
in any way.
IBM, the IBM logo and ibm.com are trademarks of International
Business Machines Corp., registered in many jurisdictions
worldwide. Other product and service names might be trademarks of
IBM or other companies. A current list of IBM trademarks is
available on the Web at “Copyright and trademark information” at
www.ibm.com/legal/copytrade.shtml.