| PrintNumber | ErrorLocation | Error | Correction | DateAdded |
|---|---|---|---|---|
| 1 | pviii | printline and possibly CIP update | 1/9/2009 | |
| 1 | p2 | The challenges in WebSphere engineering practice and system stability had their root in the technical management of WebSphere Application Server engineering or, rather, the lack of it. | The challenges in WebSphere engineering practice and system stability had their root in the technical management of WebSphere Application Server deployment or, rather, the lack of it. | 1/9/2009 |
| 1 | p2 | Instead, it is based on industry experiences and, sometimes, the author’s and technical reviewers’ painful lessons of WebSphere Application Sever engineering practices. | Instead, it is based on industry experiences and, sometimes, the author’s and technical reviewers’ painful lessons of WebSphere engineering practices. | 1/9/2009 |
| 1 | p2 | This section may provide a systematic study of WebSphere engineering or useful references for on-the-spot solutions. | delete sentence | 1/9/2009 |
| 1 | p4 | Chapter 10, “WebSphere Application Server System Upgrade and Product Maintenance Management,” | Chapter 10, “System Upgrade and Product Maintenance Management,” | 1/9/2009 |
| 1 | p7 | As a leader of WebSphere Application Server engineering, the first challenging task that you have is to either build a new WebSphere organization1 or to streamline an existing one. | As a leader of WebSphere engineering, the first challenging task that you have is to either build a new WebSphere organization1 or to streamline an existing one. | 1/9/2009 |
| 1 | p8 | Dedicated WebSphere Application Server Engineering Support Organization | Dedicated WebSphere Support Organization | 1/9/2009 |
| 1 | p8 | The second dimension of the term “dedicated” refers to a WebSphere Application Server engineering team or WebSphere team that works only to support its assigned LOB. | The second dimension of the term “dedicated” refers to a WebSphere team that works only to support its assigned LOB. | 1/9/2009 |
| 1 | p10 | Categorizing WebSphere Application Server engineering functions helps conceive and design the structures of a WebSphere organization. The enumeration of engineering tasks makes it easier to think through the convergence of WebSphere Application Server engineering support life cycles, WebSphere Application Server environments and their components, and the product and service delivery. This category of engineering function and the classification of engineering tasks are necessary elements that comprise an engineering framework. They make it possible to systematically deal with WebSphere Application Server engineering tasks in concrete terms. Chapter 3, “WebSphere Operations Framework,” introduces the WebSphere engineering framework. Although planning engineering and process engineering functions have different engineering tasks, they do have one similarity. These WebSphere Application Server engineering functions have no direct contacts with the customers. |
Categorizing WebSphere engineering functions helps conceive and design the structures of a WebSphere organization. The enumeration of engineering tasks makes it easier to think through the convergence of engineering support life cycles, WebSphere Application Server environments and their components, and the product and service delivery. This category of engineering function and the classification of engineering tasks are necessary elements that comprise an engineering framework. They make it possible to systematically deal with WebSphere engineering tasks in concrete terms. Chapter 3, “WebSphere Operations Framework,” introduces the WebSphere engineering framework. Although planning engineering and process engineering functions have different engineering tasks, they do have one similarity. These WebSphere engineering functions have no direct contacts with the customers. |
1/9/2009 |
| 1 | p11 | For a mature IT organization with an effective engagement process and a transparent IT infrastructure engineering cost model, use a dedicated WebSphere Application Server engineering support organization built on a product-based support model. | For a mature IT organization with an effective engagement process and a transparent IT infrastructure engineering cost model, use a dedicated WebSphere support organization built on a product-based support model. | 1/9/2009 |
| 1 | p12 | It is more challenging to depict a clear picture to your customer of WebSphere Application Server engineering costs. | It is more challenging to depict a clear picture to your customer of WebSphere engineering costs. | 1/9/2009 |
| 1 | p12 | There are two different ways to implement a LOB-based WebSphere Application Server engineering support model. | There are two different ways to implement a LOB-based WebSphere engineering support model. | 1/9/2009 |
| 1 | p12 | The same goes for a small, separate WebSphere team dedicated to a LOB. | delete sentence | 1/9/2009 |
| 1 | p14 | A small support team of multiple products can better provide a single point of contact that helps simplifying the engagement process for technical services, and therefore is a major advantage of this support model. | A small support team of multiple products can better provide a single point of contact that helps simplify the engagement process for technical services, and therefore is a major advantage of this support model. | 1/9/2009 |
| 1 | p17 | It is costly to support many WebSphere Application Server systems that are fundamentally different. | It is costly to support many WebSphere systems that are fundamentally different. | 1/9/2009 |
| 1 | p18 | These engineering practices differences and system inconsistencies make system integration and system interconnection extremely difficult. System standards, such as server naming conventions, can become deeply rooted second nature for WebSphere engineers after years of usage. Therefore, system inconsistencies, such as different WebSphere Application naming conventions and the different assignment of transport ports, can become serious system stability traps and challenges to integrated or interconnected systems. | These engineering practice differences and system inconsistencies make system integration and system interconnection extremely difficult. System standards, such as server naming conventions, can become deeply rooted second nature for WebSphere engineers after years of usage. Therefore, system inconsistencies, such as different WebSphere application naming conventions and the different assignment of transport ports, can become serious system stability traps and challenges to integrated or interconnected systems. | 1/13/2009 |
| 1 | p19 | Without top-notch WebSphere talents focusing on an upgrade strategy, WebSphere Application Server standards, and process engineering, your WebSphere organization suffers. For example, if your WebSphere planning engineer fails to deliver a product road map for your company in a timely fashion, there is no effective guidance in managing a WebSphere Application Server product upgrade. As a result, your product currency program fails. WebSphere Application Server system configuration automation is another example testifying to the importance of WebSphere process engineering. The WebSphere Application Server system configuration is a resource-intensive and error-prone job if done manually because of the existence of many WebSphere configurable items. |
Without top-notch WebSphere talents focusing on an upgrade strategy, system standards, and process engineering, your WebSphere organization suffers. For example, if your WebSphere planning engineer fails to deliver a product road map for your company in a timely fashion, there is no effective guidance in managing a WebSphere product upgrade. As a result, your product currency program fails. WebSphere system configuration automation is another example testifying to the importance of WebSphere process engineering. The WebSphere system configuration is a resource-intensive and error-prone job if done manually because of the existence of many WebSphere configurable items. |
1/13/2009 |
| 1 | p20 | For example, the system design team may consistently recommend and produce a WebSphere topology that supports redundancy and failover for a critical WebSphere Application Server infrastructure in order to achieve high resiliency. | For example, the system design team may consistently recommend and produce a WebSphere topology that supports redundancy and failover for a critical WebSphere infrastructure in order to achieve high resiliency. | 1/13/2009 |
| 1 | p22 | However, serious WebSphere Application Server problems can still cause wide spread stability and availability issues and affect a large number of applications sharing mainframe system resources. | However, serious WebSphere Application Server problems can still cause widespread stability and availability issues and affect a large number of applications sharing mainframe system resources. | 1/13/2009 |
| 1 | p22 | A separate system team can be a good organization choice for a large shared environment, such as mainframe WebSphere Application Server systems. | A separate system team can be a good organization choice for a large shared environment, such as mainframe WebSphere systems. | 1/13/2009 |
| 1 | p23 | This separation of system work may add an extra layer of service delivery dependency for the WebSphere service team. | This separation of system work may add an extra layer of service delivery dependency. | 1/13/2009 |
| 1 | p23 | Can a separate system achieve a higher level of automation? | Can a separate system team achieve a higher level of automation? | 1/13/2009 |
| 1 | p25 | 9. WebSphere infrastructure refers to WebSphere technologies centered on IT infrastructure. | 9. WebSphere infrastructure refers to WebSphere technologies centered IT infrastructure. | 1/13/2009 |
| 1 | p26 | As a long-term strategy, the cost savings of offshore labor should be secondary. The focus of building a global WebSphere Application Server engineering organization should have other more sustainable objectives. | As a long-term strategy, the cost savings of offshore labor should be secondary. The focus of building a global WebSphere organization should have other more sustainable objectives. | 1/13/2009 |
| 1 | p26 | The WebSphere Application Server engineer has a project management perspective. A majority of change-management meetings, project meetings, and team huddles often occur during normal business hours. | The WebSphere engineer has a project management perspective. A majority of change-management meetings, project meetings, and team huddles often occur during normal business hours. | 1/13/2009 |
| 1 | p27 | This relationship ties the WebSphere Application Server system tightly with the JEE applications that execute within WebSphere JEE containers. | This relationship ties the WebSphere Application Server system tightly with the JEE applications that execute within WebSphere containers. | 1/13/2009 |
| 1 | p28 | As a practical consideration, the WebSphere team most likely would want to grant operator privileges to the application support team because this reduces the WebSphere team participation in production issues that the production support team12 is fully capable of managing. | Delete footnote #12 and reference at the bottom of page.. | 1/13/2009 |
| 1 | p29 | A large company may have thousands of large and complex WebSphere Application Server systems from different business divisions. | A large company may have thousands of large and complex WebSphere systems from different business divisions. | 1/13/2009 |
| 1 | p29 | Instead, large and complex WebSphere Application Server systems have a long history of evolution through mergers, acquisitions, business changes, and organization dynamics, and as a result, system differences and process inconsistencies exist. The WebSphere team must work in such reality. | Instead, large and complex WebSphere systems have a long history of evolution through mergers, acquisitions, business changes, and organization dynamics, and as a result, system differences and process inconsistencies exist. The WebSphere team must work in such reality. | 1/13/2009 |
| 1 | p29 | It may not be possible for one WebSphere engineer to learn a large number of complex WebSphere Application Server systems. | It may not be possible for one WebSphere engineer to learn a large number of complex WebSphere systems. | 1/13/2009 |
| 1 | p29 | WebSphere Level 2 support has a solid set of WebSphere Application Server engineering tasks to perform, such as, deep dive performance tuning, troubleshooting, and high-impact and high- visibility production problem resolution. |
WebSphere Level 2 support has a solid set of WebSphere engineering tasks to perform, such as, deep dive performance tuning, troubleshooting, and high-impact and high- visibility production problem resolution. |
1/13/2009 |
| 1 | p30 | Note that this is at a moment when the WebSphere engineers need to focus on solving a tough technical problem under the pressure to stabilize the WebSphere Application Server system and restore production operation. | Note that this is at a moment when the WebSphere engineers need to focus on solving a tough technical problem under the pressure to stabilize the WebSphere system and restore production operation. | 1/13/2009 |
| 1 | p32 | This is especially true for a large company with a large number of WebSphere Application Server systems. | This is especially true for a large company with a large number of WebSphere systems. | 1/13/2009 |
| 1 | p32 | A leveled resource pool model may be suitable for supporting a moderate number of WebSphere Application Server systems because it is possible for the WebSphere team members to learn a reasonable number of large systems, such as, supporting the WebSphere Application Server systems of one business division. | A leveled resource pool model may be suitable for supporting a moderate number of WebSphere systems because it is possible for the WebSphere team members to learn a reasonable number of large systems, such as, supporting the WebSphere systems of one business division. |
1/13/2009 |
| 1 | p33 | This model works well if the WebSphere Application Systems are standardized and the WebSphere applications are consistent in terms of architecture and operations. | This model works well if the WebSphere systems are standardized and the WebSphere applications are consistent in terms of architecture and operations. | 1/13/2009 |
| 1 | p35 | To prevent such inconsistency problems, you can assign a senior WebSphere engineer with both WebSphere Application Server system experience and JEE expertise to work with all the projects as the team system architect. The primary role of the team system architect is not to design every possible WebSphere Application Server topology and configuration document for all the projects for which your team is responsible. (Of course, the team system architect can always provide input for WebSphere Application Server architecture issues.) However, his primary function is to review every WebSphere Application Server topology and configuration document that your WebSphere team delivers to ensure that the documents conform to the enterprise WebSphere standards and generally accepted WebSphere engineering practice. | To prevent such inconsistency problems, you can assign a senior WebSphere engineer with both WebSphere system experience and JEE application expertise to work with all the projects as the team system architect. The primary role of the team system architect is not to deliver every possible WebSphere topology and configuration document for all the projects for which your team is responsible. (Of course, the team system architect can always provide input for architecture issues.) However, his primary function is to review every WebSphere topology and configuration document that your WebSphere team delivers to ensure that the documents conform to the enterprise WebSphere standards and generally accepted WebSphere engineering practice. | 1/13/2009 |
| 1 | p36 | Another effective means to ensure WebSphere Application Server system consistency is to periodically conduct a system audit. | Another effective means to ensure WebSphere system consistency is to periodically conduct a system audit. | 1/13/2009 |
| 1 | p36 | A reasonable partial rotation of WebSphere engineers for large and important IT projects can help achieve high WebSphere Application Server system consistency and standardized engineering practices. However, this rotation may also destabilize your critical WebSphere Application Server systems and disrupt work relationships. | A reasonable partial rotation of WebSphere engineers for large and important IT projects can help achieve high WebSphere system consistency and standardized engineering practices. However, this rotation may also destabilize your critical WebSphere systems and disrupt work relationships. | 1/13/2009 |
| 1 | p36 | When a WCoE functions as a virtual organization of WebSphere Application Server technology, its function is similar to that of WebSphere planning engineering. | When a WCoE functions as a virtual organization of WebSphere technology, its function is similar to that of WebSphere planning engineering. | 1/13/2009 |
| 1 | p40 | It must help build a highly technical engineering team, enhancing accountability, and improving the quality of WebSphere products and service delivery. | It must help build a highly technical engineering team, enhancing accountability, and improving the quality of WebSphere product and service delivery. | 1/13/2009 |
| 1 | p42 | It discusses the options, priorities, and balance in hiring WebSphere Application Server engineering talent. Hiring quality WebSphere Application Server practitioners is half of your team-building success story. |
It discusses the options, priorities, and balance in hiring WebSphere engineering talent. Hiring quality WebSphere practitioners is half of your team-building success story. |
1/13/2009 |
| 1 | p44 | From a training perspective, it is relatively easier to train IT professionals with JEE expertise in the role of WebSphere Application Server system engineers because the JEE expertise helps with understanding WebSphere Application Server technologies. For example, it is easier for a WebSphere engineer with JEE exposure to better understand the WebSphere Application Server implementation of the Enterprise JavaBeans (EJB) container. | From a training perspective, it is relatively easier to train IT professionals with JEE expertise into the role of WebSphere engineers because the JEE expertise helps with understanding WebSphere Application Server technologies. For example, it is easier for a WebSphere engineer with JEE exposure to better understand the WebSphere implementation of the Enterprise JavaBeans (EJB) container. | 1/13/2009 |
| 1 | p45 | Now, it’s time to look at the skills needed to build a WebSphere team, especially project management capabilities and system expertise. | Now, it’s time to look at other skills needed to build a WebSphere team, especially project management capabilities and system expertise. | 1/13/2009 |
| 1 | p45 | Among the many WebSphere Application Server engineering tasks listed in Chapter 1, “Organization Models and Choices,” WebSphere Application Server project management tasks are conspicuously missing. This is because project management tasks are common to all IT infrastructure technologies. However, project management performance by your team is a key factor for your team’s overall success. Your WebSphere team has a lot of critical project management work to do. You need WebSphere engineers that are good at managing large and complex infrastructure projects. Of course, all WebSphere engineers need to have an in-depth knowledge of WebSphere Application Server technologies. | Among many WebSphere engineering tasks listed in Chapter 1, “Organization Models and Choices,” project management tasks are conspicuously missing. This is because project management tasks are common to all IT infrastructure technologies. However, project management performance or your team is a key factor for your team’s overall success. Your WebSphere team has a lot of critical project management work to do. You need WebSphere engineers that are good at managing large and complex infrastructure projects. Of course, all WebSphere engineers need to have an in-depth knowledge of WebSphere technologies. | 1/13/2009 |
| 1 | p45 | For example, the IT project manager is in charge of an infrastructure project plan in which the WebSphere Application Server system build is a high-level task that is associated with a deadline. It usually does not and should not contain details as to, when, where, and how to build a WebSphere Application Server system, or which engineer will do so. Instead, it has the high-level information of the server build. The WebSphere team needs to work on a technical details-oriented plan for the WebSphere Application Server build job. | For example, the IT project manager is in charge of an infrastructure project plan in which the WebSphere system build is a high-level task that is associated with a deadline. It usually does not and should not contain details as to, when, where, and how to build a WebSphere system, or which engineer will do so. Instead, it has the high-level information of the server build. The WebSphere team needs to work on a technical details-oriented plan for the WebSphere build job. | 1/13/2009 |
| 1 | p46 | WebSphere Application Server engineering for a large company is never purely a technical job. Good technical project management capabilities and communication skills are necessary for the team to perform its normal functions. The WebSphere Application Server technical project management includes, but is not limited to, the following tasks. | WebSphere engineering for a large company is never purely a technical job. Good technical project management capabilities and communication skills are necessary for the team to perform its normal functions. The technical project management includes, but is not limited to, the following tasks. | 1/13/2009 |
| 1 | p46 | The success or failure of a large WebSphere project is decided before the first WebSphere Application Server environment is designed and built. | The success or failure of a large WebSphere project is decided before the first WebSphere environment is designed and built. | 1/13/2009 |
| 1 | p46 | Some of these are easier to quantify (for example, the number of servers, WebSphere Application Server system redundancy and failover, and service level agreements ([SLA]). | Some of these are easier to quantify (for example, the number of servers, system redundancy and failover, and service level agreements ([SLA]). | 1/13/2009 |
| 1 | p46 | It demands considerable WebSphere project experience, knowledge of WebSphere Application Server technology, understanding of WebSphere engineering processes, and the business acumen to do a good job at resource estimation. | It demands considerable WebSphere project experience, knowledge of WebSphere technology, understanding of WebSphere engineering processes, and the business acumen to do a good job at resource estimation. | 1/13/2009 |
| 1 | p46 | From system design to production code migration, a carefully made, and faithfully executed plan adjusted in a timely manner ensures the quality and the consistency of WebSphere Application Server product and service delivery. | From system design to production code migration, a carefully made, and faithfully executed plan adjusted in a timely manner ensures the quality and the consistency of WebSphere product and service delivery. | 1/13/2009 |
| 1 | p47 | What’s more, the WebSphere Application Server engineering work plan, when integrated with your change-management process and assignment scheduling mechanism, provides a desirable work rhythm for your team. | What’s more, the WebSphere engineering work plan, when integrated with your change-management process and assignment scheduling mechanism, provides a desirable work rhythm for your team. | 1/13/2009 |
| 1 | p47 | WebSphere Application Server environments are usually large and complex. | WebSphere environments are usually large and complex. | 1/13/2009 |
| 1 | p51 | In addition, highly visible behaviors cast a shadow on the business reputation of the WebSphere team. | In addition, highly visible behaviors as such cast a shadow on the business reputation of the WebSphere team. | 1/13/2009 |
| 1 | p54 | To hire a contractor to build a large number of WebSphere Application Servers, you do not have to consider advanced WebSphere project management capabilities or JEE expertise. | To hire a contractor to build a large number of servers, you do not have to consider advanced WebSphere project management capabilities or JEE expertise. | 1/13/2009 |
| 1 | p60 | For example, if the team needs highly advanced training, but you have a group of new engineers, they may be out of place in advanced training. | For example, if the team needs highly advanced training, but you have a group of new engineers, they may be out of place in an advanced class. | 1/13/2009 |
| 1 | p70 | ...long learning curve needed to become proficient for large WebSphere Application Server systems. | ...long learning curve needed to become proficient for large WebSphere systems. | 1/15/2009 |
| 1 | p71 | WebSphere process engineers working on automation may take the IBM WebSphere Application Server V7 Scripting and Automation (Remote Class) class. | WebSphere process engineers working on automation may take the IBM WebSphere Application Server V7 Scripting and Automation (Remote Class). | 1/15/2009 |
| 1 | p71 | There are as many as 11 mainframe foundational courses and mainframe classes to take. | There are as many as 11 mainframe foundational courses and mainframe WebSphere classes to take. | 1/15/2009 |
| 1 | p72 | Start new paragraph: Special training is frequently... |
fixed | 1/15/2009 |
| 1 | p75 | This important chapter provides critical information about a systematic approach to WebSphere Application Server engineering work: the WebSphere Operations Framework. This chapter carefully defines the WebSphere Operations Framework, which is a major component of WebSphere engineering. | This important chapter provides critical information about a systematic approach to WebSphere Application Server work: WebSphere engineering, as well as, the WebSphere Operations Framework. This chapter carefully explains what is WebSphere engineering and defines the WebSphere Operations Framework, which is a major component of WebSphere engineering. | 1/15/2009 |
| 1 | p76 | First, it’s time to further define WebSphere engineering. In this book, the terms WebSphere Application Server engineering and WebSphere engineering are interchangeable. These terms refer to the IT engineering work to design, build, and operate WebSphere Application Server infrastructure. (WebSphere engineering is sometimes used for the ease of reading.) | First, it’s time to further define WebSphere engineering. In this book, the terms WebSphere Application Server engineering and WebSphere engineering are interchangeable. (WebSphere engineering is sometimes used for the ease of reading.) These terms refer to the IT engineering work to design, build, and operate WebSphere Application Server infrastructure. | 1/15/2009 |
| 1 | p78 | The stability and availability of your WebSphere Application Server system depends on many critical factors (such as the engineering rigor of your team and your team’s work relationships with key business partners). | The stability and availability of your WebSphere system depends on many critical factors (such as the engineering rigor of your team and your team’s work relationships with key business partners). | 1/15/2009 |
| 1 | p79 | You need to understand that the WebSphere Application Server technical management is difficult and frequently counter-intuitive. | You need to understand that the WebSphere technical management is difficult and frequently counter-intuitive. | 1/15/2009 |
| 1 | p80 | You want to be aware that the WebSphere Application Server technical management is a learned skill and acquired capability that demands training, practice, and shared industry-strength experience. | You want to be aware that the WebSphere technical management is a learned skill and acquired capability that demands training, practice, and shared industry-strength experience. | 1/15/2009 |
| 1 | p82 | Classification of different phases of WebSphere Application Server engineering support. | Classification of different phases of WebSphere engineering support. | 1/15/2009 |
| 1 | p85 | All these activities serve to perform a specific engineering operation to accomplish the design, build, operation, and support of a stable and capable WebSphere Application Server system. | All these activities serve to perform a specific engineering operation to accomplish the design, build, operation, and support of a stable and capable WebSphere system. | 1/15/2009 |
| 1 | p88 | The WebSphere Application Server environments for this engineering life cycle typically include development, functional testing, system testing, and occasionally quality assurance. | The WebSphere environments for this engineering life cycle typically include development, functional testing, system testing, and occasionally quality assurance. | 1/15/2009 |
| 1 | p89 | After successful function, integration, stress and performance testing through the entire environment pipeline, it is time to reconfigure or start building the production environment. Then, you are ready to deploy the application code into the WebSphere JEE containers. | After successful function, integration, stress and performance testing through the entire pipeline, it is time to reconfigure or start building the production environment. Then, you are ready to deploy the application code into the WebSphere containers. | 1/15/2009 |
| 1 | p89 | WebSphere Application Server upgrade management includes planning and process engineering and service delivery. | WebSphere upgrade management includes planning and process engineering and service delivery. | 1/15/2009 |
| 1 | p90 | This section defines the attributes of operations involved in WebSphere Application Server engineering support. The operations are basic units of work that can be repeated and reused in the phases of the WebSphere Application Server engineering support life cycles. The WebSphere Application Server operations are at the core of WebSphere engineering because these operations provide a basic reference and framework to ensure that the products and services can be delivered in a consistent and predictable manner. | This section defines the attributes of operations involved in WebSphere engineering support. The operations are basic units of work that can be repeated and reused in the phases of the WebSphere engineering support life cycles. The operations are at the core of WebSphere engineering because these operations provide a basic reference and framework to ensure that the products and services can be delivered in a consistent and predictable manner. | 1/15/2009 |
| 1 | p115 | WebSphere engineering support covers WebSphere production servers, WebSphere testing environments, and development with multiple pipelines. | WebSphere engineering support covers WebSphere production servers, WebSphere testing environments, and development systems with multiple pipelines. | 1/15/2009 |
| 1 | p116 | With these WebSphere operations, you have a system of solid measurements for your WebSphere engineering work, helping achieve a predictable quality of the WebSphere products and service delivered. | With these WebSphere operations, you have a system of solid measurements for your WebSphere engineering work, helping achieve a predictable quality of the WebSphere product and service delivered. | 1/15/2009 |
| 1 | p121 | WebSphere Server Build Phase Issues | WebSphere Server Build Issues | 1/15/2009 |
| 1 | p123 | During a server build phase, inefficient practices may cause serious issues in business partner communication and education. | During a server build phase, inefficient and inexperienced practices may cause serious issues in business partner communication and education. | 1/15/2009 |
| 1 | p123 | The system specifications have been derived from nonfunctional requirements such as availability, redundancy, failover, capacity, scalability, and resiliency requirements, among others, balanced with budget constraints and technical infrastructureconsiderations. | The system specifications have been derived from nonfunctional requirements such as availability, redundancy, failover, capacity, scalability, and resiliency requirements, among others, balanced with budget constraints and technical infrastructure considerations. | 1/15/2009 |
| 1 | p128 | The system specifications have been derived from nonfunctional requirements such as availability, redundancy, failover, capacity, scalability, and resiliency requirements, among others, balanced with budget constraints and technical infrastructureconsiderations. | The system specifications have been derived from nonfunctional requirements such as availability, redundancy, failover, capacity, scalability, and resiliency requirements, among others, balanced with budget constraints and technical infrastructure considerations. | 1/15/2009 |
| 1 | p129-130 | Move Sign-Off Parties section to after Collaborating Teams | fixed | 1/15/2009 |
| 1 | p135 | Add: Sign-Off Parties • Application production support team • WebSphere team |
fixed | 1/15/2009 |
| 1 | p135 | Signed off by the production application support team and WebSphere manager. | Signed off by the application production support team and WebSphere manager. | 1/15/2009 |
| 1 | p138 | However, a good WebSphere topology itself is not good enough, and with no exception, the WebSphere engineering support team has to work well with a large number of other technical teams to do their job well. | However, a good WebSphere topology itself is not good enough, and with no exception, the WebSphere team has to work well with a large number of other technical teams to do their job well. | 1/15/2009 |
| 1 | p139 | However, the choices that you make for WebSphere support have a far-reaching effect on the WebSphere engineering support’s overall quality for a given enterprise WebSphere application. | However, the choices that you make have a far-reaching effect on the WebSphere engineering support’s overall quality for a given enterprise WebSphere application. | 1/15/2009 |
| 1 | p140 | The arrangement can be such that the WebSphere engineering support team manages the WebSphere production environment and stress-testing environments, and the application teams control development and other testing WebSphere environments. The WebSphere engineering support team also consults the application development and support team. | The arrangement can be such that the WebSphere team manages the WebSphere production environment and stress-testing environments, and the application teams control development and other testing WebSphere environments. The WebSphere team also consults the application development and support team. | 1/15/2009 |
| 1 | p140 | By doing so, you make the Functional and Integration Testing Environment WebSphere systems consistent with production and stress- testing environments before such differences cause production issues. |
By doing so, you make the Functional and Integration Testing Environment WebSphere systems consistent with production and stress- testing systems before such differences cause production issues. |
1/15/2009 |
| 1 | p141 | Therefore, carefully evaluate the resource needs for more pipeline build out and systematically carry out support before you make commitments to your technology or business partners. | Therefore, carefully evaluate the resource needs for more pipeline build out before you make commitments to your technology or business partners. | 1/15/2009 |
| 1 | p143 | (Chapter 10, “WebSphere Application Server System Upgrade and Product Maintenance Management,” discusses this topic in more detail.) | (Chapter 10, “System Upgrade and Product Maintenance Management,” discusses this topic in more detail.) | 1/15/2009 |
| 1 | p144 | In addition, providing application development tool support may not be considered the WebSphere engineering team’s core competence. | In addition, providing application development tool support may not be considered the WebSphere team’s core competence. | 1/15/2009 |
| 1 | p147 | External Teams | Collaborating Teams | 1/15/2009 |
| 1 | p148 | This process defines how to record the problem, the organization that generates the request for addressing problems, request dispatching, engagement of development resources, WebSphere resources, engagement of IBM technical support organization, and the tracking of defects in the end-to-end process of fixing those defects. | This process defines how to record the problem, the organization that generates the request for addressing problems, request dispatching, engagement of development resources, WebSphere resources, engagement of IBM technical support organization, and the tracking of defects in the end-to-end process for fixing those defects. | 1/15/2009 |
| 1 | p149 | Every team member must fully understand this document and diligently follow your company’s change-control processes and emergency change-management processes. | Every team member must fully understand this document and diligently follow your company’s change-control processes and emergency change-control processes. | 1/15/2009 |
| 1 | p149 | Mature development teams have a good grasp of the WebSphere application development tool suite and need little support from the WebSphere engineering support team. | Mature development teams have a good grasp of the WebSphere application development tool suite and need little support from the WebSphere team. | 1/15/2009 |
| 1 | p149 | The WebSphere engineering support team has to work with the development team and testing team on every new release, starting from the Functional and Integration Testing Environment all the way to the production environment in managing changes and resolving technical issues. | The WebSphere team has to work with the development team and testing team on every new release, starting from the Functional and Integration Testing Environment all the way to the production environment in managing changes and resolving technical issues. | 1/15/2009 |
| 1 | p150-1 | It is supported by a WebSphere engineering support team, called WebSphere Team 1, which focuses in customer-care applications. Now, you are moving the Functional and Integration Testing Environment WebSphere Network Deployment-based systems to a large shared WebSphere Virtual Enterprise environment that is managed by a WebSphere engineering support team called WebSphere Team 2, which specializes in large shared environments. | It is supported by a WebSphere team, called WebSphere Team 1, which focuses in customer-care applications. Now, you are moving the Functional and Integration Testing Environment WebSphere Network Deployment-based systems to a large shared WebSphere Virtual Enterprise environment that is managed by a WebSphere team called WebSphere Team 2, which specializes in large shared environments. | 1/15/2009 |
| 1 | p154 | This chapter focuses on the WebSphere Configuration Change Support Operation and the WebSphere Performance Tuning and Testing Support Operation. | This chapter focuses on the WebSphere Configuration Change Support Operation and the WebSphere Stress-Testing Support Operation. | 1/15/2009 |
| 1 | p156 | External Teams | Collaborating Teams | 1/15/2009 |
| 1 | p156 | • WebSphere production support team | • WebSphere team | 1/15/2009 |
| 1 | p156 | ...the change, and the verbiage of the due diligence and sharing of the responsibility for the change performed. | ...the change, and the verbiage of due diligence and sharing of the responsibility for the change performed. | 1/15/2009 |
| 1 | p160 | External Teams | Collaborating Teams | 1/15/2009 |
| 1 | p163 | For example, in the accountability clause, you can assert that because of the lack of stress testing, production instabilities occurred and need to be addressed by the application development organization, which decided to substantially reduce the time for stress testing. | For example, in the accountability clause, you can assert that because of the lack of stress testing, production instabilities need to be addressed by the application development organization, which decided to substantially reduce the time for stress testing. | 1/15/2009 |
| 1 | p169 | After all, the WebSphere engineering support team is not a software development organization. | After all, the WebSphere team is not a software development organization. | 1/15/2009 |
| 1 | p177 | A best practice is to use a consistent application code approach for the production environment, stress-testing environment, development, and other testing environments. | A best practice is to use a consistent application code deployment approach for the production environment, stress-testing environment, development, and other testing environments. | 1/15/2009 |
| 1 | p177 | WebSphere system configuration errors may damage the WebSphere engineering support team’s reputation. | WebSphere system configuration errors may damage the WebSphere team’s reputation. | 1/15/2009 |
| 1 | p186 | External Teams | Collaborating Teams | 1/15/2009 |
| 1 | p187 | Your WebSphere engineers’ performance at these operations may affect their reputation and management’s perception of them. | Your WebSphere engineers’ performance at this operation may affect their reputation and management’s perception of them. | 1/15/2009 |
| 1 | p189 | External Teams | Collaborating Teams | 1/15/2009 |
| 1 | p191 | External Teams | Collaborating Teams | 1/15/2009 |
| 1 | p192 | For example, you may have a WebSphere engineering support team and a DB2 engineering support team for your customer-care department that manages call centers and customer information for your company. | For example, you may have a WebSphere team and a DB2 team for your customer-care department that manages call centers and customer information for your company. | 1/15/2009 |
| 1 | p209 | ...serious and prolonged outage for an instability that is difficult to identify and mitigate. | ...serious and prolonged outage for an instability that is caused by a client application and difficult to identify and mitigate. | 1/15/2009 |
| 1 | p209 | add heading before sentence, “All capacity increase...” Test Capacity Increase Solutions |
fixed | 1/15/2009 |
| 1 | p212 | Cut section: Testing If you introduce system or application changes to production without testing, the outcome of such “fixes” is unpredictable. All proposed fixes must be tested, especially stress tested, when they can be validated and improved before going to production. By not following the proper process and testing of your solutions, your production WebSphere system may become even more unstable. (Chapter 6, “Functional and Integration Testing Environment Support,” and Chapter 7, “Stress-Testing Environment Support,” discuss testing.) |
fixed | 1/15/2009 |
| 1 | p217 | External Teams | Collaborating Teams | 1/15/2009 |
| 1 | p224 | When you feel that a high- severity production problem may be related to testing issues, keep the testing manager informed so that she is prepared to deal with the issues. | When you feel that a high-severity production problem may be related to testing issues, keep the testing manager informed so that she is prepared to deal with the issues. | 1/15/2009 |
| 1 | p226 | As a result, even four to five hours can be lost, with each hour accounting for a few million dollars lost to your company. | As a result, even four to five hours can be lost, with each hour accounting for many dollars lost to your company. | 1/15/2009 |
| 1 | p246 | The new WebSphere team member needs roughly three months of training and mentoring to safely provide production support to such key WebSphere systems, where two hours of unscheduled downtime may translate into tens of millions of losses for your company. | The new WebSphere team member needs roughly three months of training and mentoring to safely provide production support to such key WebSphere systems, where two hours of unscheduled downtime may translate into millions of losses for your company. | 1/15/2009 |
| 1 | p249 | For the WebSphere project support team in charge of the project, scheduling installations with a dedicated system team may be difficult because of different priorities coming from many peer WebSphere project-support teams needing the same service, resulting in disagreements about resource availability and build schedules. | For the WebSphere project support team in charge of the project, scheduling installations with a dedicated system team may be difficult because of different priorities coming from many peer WebSphere project support teams needing the same service, resulting in disagreements about resource availability and build schedules. | 1/15/2009 |
| 1 | p251-259 | cut bullet list: • Server build request • Software requirements • Hardware requirements • Server security access requests • OS requirements • WebSphere installation specifications • WebSphere global security requests • JEE security-enabling specifications • Web server specifications • Server port assignments • Infrastructure engineers assigned • Change-management information • Monitoring requirements |
fixed, rewrap | 1/15/2009 |
| 1 | p257 | Environment change-coordination team (in charging of scheduling) | Environment change-coordination team (in charge of scheduling) | 1/15/2009 |
| 1 | p258 | External Teams | Collaborating Teams | 1/15/2009 |
| 1 | p258 | • Set of well-rounded and balanced WebSphere system build standards | • A set of well-rounded and balanced WebSphere system build standards | 1/15/2009 |
| 1 | p273 | The relationship between the WebSphere team and the applicant development and production support team is not simple. | The relationship between the WebSphere team and the development and production support team is not simple. | 1/15/2009 |
| 1 | p280 | Will the capacity planning team provide a resource-utilization ceiling for service-level optimization for the overall WebSphere Virtual Enterprise systems or the upper limit details of fine granularities for each application executing in the WebSphere Extended Deployment? | Will the capacity planning team provide a resource-utilization ceiling for service-level optimization for the overall WebSphere Virtual Enterprise systems or the upper limit details of fine granularities for each application executing in the WebSphere? | 1/15/2009 |
| 1 | p281 | Both the WebSphere engineering support team and the capacity planning team face challenges in fulfilling the capacity planning service at the WebSphere Application Server level in an interconnected environment. | Both the WebSphere team and the capacity planning team face challenges in fulfilling the capacity planning service at the WebSphere Application Server level in an interconnected environment. | 1/15/2009 |