DeploymentWorkshopsAndReviewsDetail < Deployment

Engineering Lifecycle Management Wiki - Deployment
Community information and contribution guidelines
TWiki > Deployment Web > DeploymentPlanningAndDesign > DeploymentPlanning > DeploymentWorkshopsAndReviewsDetail
Revision 6 - 2025-02-06 - 18:27:16 - TimFeeney
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! Deployment Workshops and Reviews in Detail 
%DKGRAY% Authors: Main.TimFeeney, Main.RickRakich <br>
Build basis: N/A
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

---++ Deployment workshops and reviews

A typical 2 day deployment workshop or review for an enterprise scale Rational development environment:

<style> 
   table.equalDevide tr td { width:50%; } 
</style> 

<table class="equalDevide" cellpadding="0" cellspacing="15" width="100%" border="0">
   <tr>
      <td valign="top">
__Day 1__

*09:00 - 09:30:* Give introductions and present the scope and agenda. <br>
*09:30 - 10:00:* Present and discuss the key considerations for designing a Rational development environment. <br>
*10:00 - 11:30:* Understand general requirements, constraints, and usage for the environment. <br>
*11:30 – 12:30:* Review the current development environment (Rational or third party). <br>

*12:30 – 13:00:* Lunch 

*13:00 – 14:30:* Understand the current infrastructure services and preferred middleware/platforms. Make key platform, OS, and middleware decisions. <br>
*14:30 – 16:30:* Discuss deployment topology options based on the preferred technology and common services. <br> 
*16:30 – 17:00:* Review and refine Day 2 agenda, and wrap-up Day 1.
      </td>
      <td valign="top">
__Day 2__

*9:00 - 10:00:* Review of Day 1

Hold sessions to discuss and agree on the approach to and design for these tasks: 

   * Capacity planning, performance, and monitoring
   * High-availability and disaster-recovery
   * Security
   * Audit and control
   * Compliance
   * Administration, configuring, and tuning

*16:30 – 17:00:* Overall wrap-up and discuss next steps 

   * Determine who is going to document the detailed deployment design, and by when.
       </td>
   </tr>
</table>

IBM Rational software supports deployment workshops and reviews pre- and post-sales.

---++ Sample Agenda

*[CLIENT] Technical Deployment Review Workshop* </br>
*[Location]* </br>
*[Date(s)]* </br>

This workshop focuses on technical rather than organizational deployment: 

   * Technical deployment of Rational products and solutions which includes: planning, designing, installing, configuring, integrating, upgrading and administering Rational development environments that are: flexible, scalable, performance, available, resilient, secure and supportable. 
   * Organizational deployment which includes technical deployment, but also includes the business change, adoption, best practices, enablement and the whole Rational field engagement need to improve an organizations development capability. 

However, technical deployment needs to be mindful of the requirements and constraints imposed by organizational deployment. 

The workshop would start by reviewing the existing deployment at [CLIENT] and by understanding the business and technical requirements, and constraints that the environment must support now and in the future as they roll it out to more development teams.

This workshop is conducted as a face-to-face in person meeting, and will investigate all relevant aspects of technical deployment in a structured way. For each aspect we will: 

   * Clarify the requirement and constraints 
   * Understand [CLIENT]'s preferred approach and technology 
   * Understand what has been deployed to date and what challenges or issues [CLIENT] has
   * Discuss options and make key recommendations to meet [CLIENT]'s requirements, constraints and needs.

*Note*: Times in this agenda are based upon local time [EST].

*Note*: Topics and links listed are examples of material that will be discussed. There may be other topics that will be discussed which aren’t listed here. Similarly not all topics listed here may in actuality be discussed. Frequent checkpoints during the actual workshop will refine and adjust the agenda and required topics as necessary.

*Location*:
[CLIENT] or IBM location

*Attendees*:
[CLIENT]
|Name|Role|
||(Executive Sponsor)|
||(Program/Project Architect)|
||(Tools Administrator)|
||(DBA)|
||(IT Administrator)|
||(Business Owner)|
||role|	
||role|

IBM
|Name|Role|
||Facilitator|
||Facilitator|
||role|
||role|
||role|
	
Agenda Day 1, [Date]: Understand current situation, future strategy and plans

   * 09:00 - 09:30 Introductions, review agreed scope, focus and agenda 
      * Introductions, roles
      * This agenda document and any specific required scope and focus will be reviewed
      * Finalize topics, times and breaks

   * 09:30 - 10:00 Present and discuss key consideration when designing the technical deployment of IBM Rational environments
      * IBM to present using the [[https://jazz.net/wiki/bin/view/Deployment/DeploymentPlanning][Deployment planning: Where to start?]] topic in the [[https://jazz.net/wiki/bin/view/Deployment/WebHome][Deployment wiki]].

   * 10:00 – 12:00 Review existing technical deployment and understand general requirement, constraints and usage; Review current development environment
      * [CLIENT] to present with active discussion:
      * Current #users, location distribution, roles
      * Future #users, location distribution, roles
      * Required and current Availability requirements
      * Required Mean Time to Recovery, Recovery Point Objective, Recovery Time Objective etc.
      * Development disciplines that need to be supported
      * 3rd part integration and migration we need to support
      * Security, audit and compliance requirements
      * Review future strategy and plans.
      * [CLIENT] to lead discussion and reference the background documentation given to IBM Rational

   * 12:00 – 13:00 Lunch

   * 13:00 – 14:30 Understand in detail [CLIENT]'s existing infrastructure services and preferred middleware/platforms – review and make key platform, OS and middleware decisions/recommendations
      * Database, platform, virtualization, HA/DR including back-up etc.
      * [CLIENT] to outline their existing infrastructure services
      * Start confirming topics to be discussed on Day 2 in greater depth

   * 14:30 – 16:00 Discuss deployment topology, technology and platform options based upon [CLIENT]'s preferred approach and technology, and available common services
      * [[https://jazz.net/wiki/bin/view/Deployment/StandardTopologiesOverview][Standard deployment topologies overview]] wiki topic and sub-topic pages will be the guidance and best practice this session is based upon:
      * [[https://jazz.net/wiki/bin/view/Deployment/CLMArchitectureOverview][Collaborative Lifecycle Management architecture overview]]
      * [[https://jazz.net/wiki/bin/view/Deployment/PlanForMultipleJazzAppInstances][Planning for multiple Jazz application server instances]]
      * [[https://jazz.net/wiki/bin/view/Deployment/PrinciplesOfGoodVirtualization][Principles of good virtualization]]
      * [[https://jazz.net/wiki/bin/view/Deployment/UnderstandingReverseProxy][Understanding reverse proxy]]
         * [[https://jazz.net/wiki/bin/view/Deployment/InstallProxyServers][Proxy server installation landing page]]
      * [[https://jazz.net/wiki/bin/view/Deployment/ContentCachingProxyJazzSCM][Using content caching proxies for Jazz Source Control]] – Improve SCM read performance from remote locations
      * [[https://jazz.net/wiki/bin/view/Deployment/CLMSystemRequirements602][System Requirements for IBM Rational Collaborative Lifecycle Management (CLM) 6.0.2]]
      * [[https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.0.3?topic=servers-managing-licenses-in-engineering-lifecycle-management-elm][Jazz licensing explained]] – Discuss license and license server options for an Enterprise development environment 
   * Continue confirming topics to be discussed on Day 2 in greater depth
	
   * 16:00 – 17:00 Review progress, refine Day 2 agenda
      * Review surfaced issues, recommendations and actions
      * Refine Day 2 agenda
      * Adjust topics, timeslots as needed
      * Wrap-up Day 1

Agenda Day 2, [Date]: Detailed discussion of decisions to be made; in-depth topics

   * 09:00 – 10:00 Review and refine Day 2 agenda
      * Review surfaced issues, recommendations and actions
      * Refine Day 2 agenda
      * Adjust topics and timeslots

   * 10:00 – 12:00 Capacity planning, performance and monitoring 
      * [[https://jazz.net/wiki/bin/view/Deployment/CLMSizingStrategy][!CLM Sizing Strategy]] wiki topic will be used as the guidance and best practice for capacity planning
      * [[https://jazz.net/wiki/bin/view/Deployment/PerformanceDatasheetsAndSizingGuidelines][Performance datasheets]] wiki page and containing topic pages will be used as the guidance and best practice for performance 
         * [[https://jazz.net/wiki/bin/view/Deployment/UsingWebSphereDynaCacheWithRTC][Improving the performance of Rational Team Concert by using the dynamic cache service in !WebSphere Application Server]]
      * Discuss developing a production development environment wide monitoring configuration, which combines user and automated usage with CLM Server Monitoring, database, application server and systems monitoring information for the production development environment to produce a correlated dashboard. Ultimately the key monitoring that needs to be combined to produce a correlated dashboard includes:
         * Concurrent user usage via licensing monitoring from the JTS, IBM Rational License Key Server or preferably the Rational License Key Server Administration and Reporting tool 
         * !CLM Server Monitoring 
         * WAS monitoring 
         * Database server monitoring 
         * !VMware monitoring
         * General systems performance monitoring
      * [[https://jazz.net/wiki/bin/view/Deployment/MonitoringWhereToStart][Monitoring: Where to Start?]] Wiki topic and [[https://jazz.net/wiki/bin/view/Deployment/DeploymentMonitoring][Monitoring]] section of the wiki will be used as the guidance and best practice for monitoring

   * 12:00 – 13:00 Lunch

   * 13:00 – 14:00 High availability and disaster recovery 
      * [[https://jazz.net/wiki/bin/view/Deployment/ApproachesToImplementingHAAndDR][Approaches to implementing high availability and disaster recovery for Rational Jazz environments]] wiki topic and sub-topic pages will be the guidance and best practice this session is based upon:
         * [[https://jazz.net/wiki/bin/view/Deployment/BackupStrategies][Strategies for backup of the Rational Collaborative Lifecycle Management Solution and Environment]]
         * [[https://jazz.net/wiki/bin/view/Deployment/JazzManualFailoverTechniques][Understanding how to install manual failover techniques with the Jazz solution]]
         * [[https://jazz.net/wiki/bin/view/Deployment/ImplementingApplicationRecoveryExampleScript][Implementing application recovery: Example script for a Jazz deployment on !WebSphere]]

   * 14:00 – 15:00 Administration, configuring, tuning and over-flow topics
      * Roles and responsibilities of Rational Tools Administration Team
      * How to provide an enhanced development environment service 
      * [[https://jazz.net/wiki/bin/view/Deployment/ImplementationPlanningAndDeploymentRoadmap][Implementation planning and deployment roadmap]] wiki topic and sub-topic pages will be the guidance and best practice this session is based upon:
         * [[https://jazz.net/wiki/bin/view/Deployment/DeploymentEstablishingACenterOfExcellence][Establishing a systems and software engineering ecosystem center of excellence]]
         * [[https://jazz.net/wiki/bin/view/Deployment/DeploymentAcceleratingAdoption][Accelerating adoption of software tools and practices]]
         * [[https://jazz.net/wiki/bin/view/Deployment/DeploymentMonitoringAndTracking][Deployment monitoring and tracking]]
      * [[https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.repository.web.admin.doc/topics/c_patch_svc_clm_app_svrs.html][Patch service for CLM applications]]
      * [[https://jazz.net/wiki/bin/view/Deployment/UpgradePlanning][Upgrade planning]]
      * [[https://jazz.net/wiki/bin/view/Deployment/UpgradeBestPracticeBasedUponIBMExperience][Upgrade best practice based upon IBM experience]]

   * 15:00 – 16:00 Review and wrap-up workshop
      * Review surfaced issues, recommendations and follow-on actions
      * Review format of final deliverable

Prerequisites, constrains and background for the workshop

   1. [CLIENT] to provide existing Rational technical deployment planning and design documentation for review prior to the workshop 
   1. The local IBM Rational Team will support all activities prior, during and after the workshop for business and technical understanding and continuity 
   1. [CLIENT] and IBM Rational will ensure that the right Tools and Infrastructure Administrators, Architects and Specialists can fully support the workshop sessions. 
   1. IBM Rational will produce a short review report with key recommendations after the workshop.

---+++++!! Related topics: [[DeploymentWebHome][Deployment web home]], [[DeploymentWebHome][Deployment web home]]

---+++++!! External links:          

   * [[https://www.ibm.com][IBM]]

---+++++!! Additional contributors: Main.TWikiUser, Main.TWikiUser

<sticky></div></sticky>
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.