IBM BS029ML Self Help Guide - Page 231

later Fix Packs, Fix Central

Page 231 highlights

Table B-2 Distribution channels by fix type Fix type Delivered only by IBM support to specific customers Download linked from documentation on the product support page Fix delivered by Fix Centrala Delivered from the portlet catalog Integrated into later Fix Packs (or higher MDV) Test fix Yes No No No No Interim fix No Yes Yesb No Yes Cumulative fix No Yes Yesb No Yes Business Portlet No update Yes No Yes No (refer to the MDV's documentation for confirmation) a. Fix Central (http://www.ibm.com/support/fixcentral) is a new service available from IBM support. Fixes available from Fix Central are identified by APAR number, Fix ID, version, platform, and other means, and the downloads can also include a fix's entire prerequisite chain (if it exists). This enhanced function improves the way we provide fixes and reduces the trouble we find when a fix requires another to be installed before it can be applied, and in many cases, that fix also requires others before it. When getting the fix from Fix Central, this complexity is handled by IBM by putting all of the required fixes together in one package for easy retrieval and installation. b. WebSphere Portal is moving its entire fix repository over to Fix Central in the coming months, so until that is complete, we suggest that customers continue to use the product support page to locate and retrieve fixes to avoid having to look in multiple places. An announcement will be posted on the support page when the transition is complete. When a fix is needed to correct a problem you have encountered, it rarely happens at a good time. IBM continues to invest resources into ensuring that such a fix is well tested, installs properly, and does what it is intended to do: fix the problem without introducing more problems. Many times there is urgency associated with the need for a fix especially if it is affecting a production environment. Nearly all of WebSphere Portal's test, interim, and cumulative fixes are installed with the Portal Update Installer (PUI) utility, which is available with a command-line interface as well as a graphical interface. Administrators familiar with the PUI (http://www.ibm.com/support/docview.wss?rs=688&uid=swg24006942) and its documentation in Information Center Version 6.0 can save time by familiarizing themselves with the utility by practicing on a QA, development, or "sandbox" system before having to use it in an emergency. There is a variation in this design for the WebSphere Portal Enable for z/OS® editions, since it does not use the Portal Update Installer or installation routines designed for the other distributed platforms. Updates and fixes for the z/OS platform (OS/390®) are released as ++ APARs (for emergency fixes) and PTFs, both of which are SMP/E installables and made generally available to those customers through their normal ordering and distribution channels. This section does not cover WebSphere Portal deployed on OS/390. It does, however, apply to the portal installed on the supported distributions of Linux on System z™ (SUSE and Red Hat), because the operating system is so similar to the distributions installed on x86 or RISC platforms and hardware. Appendix B. Maintenance: Fix strategy, backup strategy, and migration strategy 217

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242

Appendix B. Maintenance: Fix strategy, backup strategy, and migration strategy
217
Table B-2
Distribution channels by fix type
When a fix is needed to correct a problem you have encountered, it rarely happens at a good
time. IBM continues to invest resources into ensuring that such a fix is well tested, installs
properly, and does what it is intended to do: fix the problem without introducing more
problems. Many times there is urgency associated with the need for a fix especially if it is
affecting a production environment. Nearly all of WebSphere Portal’s test, interim, and
cumulative fixes are installed with the Portal Update Installer (PUI) utility, which is available
with a command-line interface as well as a graphical interface.
Administrators familiar with the PUI
(
) and its
documentation in Information Center Version 6.0 can save time by familiarizing themselves
with the utility by practicing on a QA, development, or “sandbox” system before having to use
it in an emergency.
There is a variation in this design for the WebSphere Portal Enable for z/OS® editions, since
it does not use the Portal Update Installer or installation routines designed for the other
distributed platforms. Updates and fixes for the z/OS platform (OS/390®) are released as ++
APARs (for emergency fixes) and PTFs, both of which are SMP/E installables and made
generally available to those customers through their normal ordering and distribution
channels. This section does not cover WebSphere Portal deployed on OS/390. It does,
however, apply to the portal installed on the supported distributions of Linux on System z™
(SUSE and Red Hat), because the operating system is so similar to the distributions installed
on x86 or RISC platforms and hardware.
Fix type
Delivered only
by IBM support
to specific
customers
Download
linked from
documentation
on the product
support page
Fix delivered by
Fix Central
a
a. Fix Central (
) is a new service available from IBM support. Fixes
available from Fix Central are identified by APAR number, Fix ID, version, platform, and other means, and the
downloads can also include a fix’s entire prerequisite chain (if it exists). This enhanced function improves the way
we provide fixes and reduces the trouble we find when a fix requires another to be installed before it can be
applied, and in many cases, that fix also requires others before it. When getting the fix from Fix Central, this
complexity is handled by IBM by putting all of the required fixes together in one package for easy retrieval and
installation.
Delivered from
the portlet
catalog
Integrated into
later Fix Packs
(or higher MDV)
Test fix
Yes
No
No
No
No
Interim fix
No
Yes
Yes
b
b. WebSphere Portal is moving its entire fix repository over to Fix Central in the coming months, so until that is
complete, we suggest that customers continue to use the product support page to locate and retrieve fixes to
avoid having to look in multiple places. An announcement will be posted on the support page when the transition
is complete.
No
Yes
Cumulative fix
No
Yes
Yes
b
No
Yes
Business Portlet
update
No
Yes
No
Yes
No (refer to the
MDV's
documentation
for confirmation)