IBM BS029ML Self Help Guide - Page 27

The System Context Diagram, System Component / Roles, Description

Page 27 highlights

The following recommendations are made with regards to the selection of the most appropriate connectivity technology: Use Web Services when portability or interface standardization is a prime concern. Use Messaging when high QoS constraints and loose coupling or asynchronous invocation is needed. Use JCA when high QoS constraints and synchronous invocation are needed. 2.1.4 The System Context Diagram If there is one diagram that can simplistically represent a WebSphere Portal Server implementation, or for that matter any other generic software implementation, then it is the System Context Diagram, as shown in Figure 2-1. Authenticated Users PDM Anonymous Users Administrators Content Authors Content Developers Portal Implementation WCM TAM System A System B .... .... .... Figure 2-1 System Context Diagram Figure 2-1 illustrates the various system components and most significant roles of the system. Besides that, it helps to identify in high level terms the systems to which a deployment interfaces. Table 2-2 further explains the various system components and roles. Table 2-2 System Context Diagram System Component / Roles Description Anonymous Users An Anonymous User has access to the limited external Portal pages, but never signs into the Portal. Anonymous users can become authenticated users by logging in. Authenticated Users An Authenticated User is a user that has logged into the Portal during their current user session. Chapter 2. Architecture and planning 13

  • 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

Chapter 2. Architecture and planning
13
The following recommendations are made with regards to the selection of the most
appropriate connectivity technology:
±
Use Web Services when portability or interface standardization is a prime concern.
±
Use Messaging when high QoS constraints and loose coupling or asynchronous
invocation is needed.
±
Use JCA when high QoS constraints and synchronous invocation are needed.
2.1.4
The System Context Diagram
If there is one diagram that can simplistically represent a WebSphere Portal Server
implementation, or for that matter any other generic software implementation, then it is the
System Context Diagram, as shown in Figure 2-1.
Figure 2-1
System Context Diagram
Figure 2-1 illustrates the various system components and most significant roles of the
system. Besides that, it helps to identify in high level terms the systems to which a
deployment interfaces. Table 2-2 further explains the various system components and roles.
Table 2-2
System Context Diagram
System Component / Roles
Description
Anonymous Users
An Anonymous User has access to the limited external Portal
pages, but never signs into the Portal. Anonymous users can
become authenticated users by logging in.
Authenticated Users
An Authenticated User is a user that has logged into the Portal
during their current user session.
Portal
Implementation
Authenticated
Users
Anonymous
Users
Administrators
Content
Authors
Content
Developers
….
PDM
WCM
TAM
System B
….
….
System A