Index_S | Architecting Portal Solutions: Applications Development

< Day Day Up >

S

sales 42

role 29

support 15

Sametime

See Lotus Instant Messaging

SAP viii, 26, 239, 253, 339, 343, 405

portlet builder 405

R/3 viii, 225, 232

scalability 17, 45, 54, 62, 95, 211, 218

scaling

horizontal 358

techniques

aggregate user data 160

batch requests 160

cache data and requests 160

Content Delivery Services 160

create machine cluster 160

local distribution across sites 160

minimize connections 160

segment the workload 160

use

a special machine 160

faster machine 160

schema mapping 339

SCL 291

(also see SOAP Contract Language)

SCM

See supply chain management

SDL 291

(also see Service Description Language)

for Content

use case 91

for People

use case 91

and navigation 24

and taxonomy 16

services 47

security 11, 16-17, 57, 81

and access control services 47

management tools 379

model

enterprise-level 211

patch deployment 376, 382

proxy 140, 196

requirements 194

servers 163

segmented workloads 159

SEI 302, 304

(also see Service Endpoint Interface)

self care 392

self-configuring 363, 370

components 349

environment 372

IT infrastructure

implementation levels 371

self-healing 363, 370

and availability management

implementation levels 374

capabilities 7

components 349

IT infrastructure 373

self-management technologies

structure 366

self-managing systems

components 348

self-optimizing 363, 370

actions 378-379

components 349

IT infrastructure

optimizing workloads and transaction performance across multiple resources 377

self-protecting 363, 370

components 349

IT infrastructure implementation levels 380

self-service 42, 44

human resource systems 167

portal 15

Self-Service business pattern 33, 75, 103-105, 110, 113

self-syndication 388

Sell-Side Hub composite pattern 35

Send Order to Warehouse use case 115

server

programming model 302

reconfiguration 376, 382

virtualization 270

Server Management Services 12

Service

Description Language 291

Endpoint Interface 302

Web 282, 287-288

service implementation bean 302

Servlet API 307

servlet-based implementation bean 302-303

servlets 25-26, 48, 275, 305, 386, 408, 414, 422

container 409

containers 296

engine 358

session EJB lifecycle 303

setSessionContext method 302

setting the agenda for the industry 8

SGML 272

(also see Standard Generalized Markup Language)

Siebel 405

Simple

Mail Transport Protocol 290

Object Access Protocol 62, 282

Simple Object Access Protocol 400

single

authentication point for user interactions 140

point

of access 12, 18, 20, 39, 41, 45, 62-63, 167, 425

of integration 43

of personalized interaction 231

sign-on 16-17, 35, 40, 53-54, 75-76, 89, 177, 222, 228, 381, 384, 391, 393, 403, 406

user interface 43

versus multi-tier Portal server design 149

site

analytics 16, 384

design 12

skins 44, 308-309, 407, 414, 418

SLAs

compliance monitors 355

effectively meeting 378

small and medium business 27

SMB

See small and medium business

SMS messaging 113

SMTP 290

(also see Simple Mail Transport Protocol)

SNMP traps 376

SOAP 282, 288, 296, 339, 345, 400

(also see Simple Object Access Protocol) 1.1

specification 290

standard 289

1.2 specification 290

Contract Language 291

Toolkit 290-291

Web service 293

with Attachments 295

SOAP/HTTP 289, 291

SOAP4J 291

software

components 96

nodes 71

structure and modularity 80

distribution 57, 81

placement 81

product requirements 95

server 96

six-stage process for deployment 359

Solaris viii

solution 39

design

logical 97

development methodology

Step 1 - Develop solution requirements 68, 84

Step 1A - List users/existing systems and Functional Requirements 68, 85, 171

Step 1B - Derive actors and use cases 68, 86

Step 1C - Inventory large reusable assets 68, 89, 174

Step 1D - Match solution use cases with generic use cases 68, 90, 174

Step 1E - Identify delta use cases 68, 93, 175

Step 1F - Identify and document NFRs 68, 94, 176

Step 1G - Validate requirements with customer 68, 97

Step 2 - Develop the logical design 69, 97

Step 2A - Derive initial AOD 69, 98, 177

Step 2B - Seed the AOD with large reusable assets 69, 101, 179

Step 2B1 - Validate the AOD 69, 111

Step 2B2 - Capture chosen patterns into Architecture Decisions 69, 115

Step 2C - Identify and apply patterns for each AOD delta requirement 69, 116, 182

Step 2C1 - Identify delta requirements that need to be addressed in the AOD 69, 116

Step 2C2 - Identify and apply Business and Integration patterns for the delta requirements 69, 118

Step 2C3 - Identify and apply Application patterns for delta Business and Integration patterns 69, 118

Step 2C4 - Capture chosen patterns into Architecture Decisions 69, 127

Step 2D - Transition the AOD from sub- system view to logical node view 69, 128, 185

Step 2D1 - Seed the AOD (Logical Nodes) 69, 128

Step 2D2 - Identify and apply Runtime patterns for the delta Application patterns 70, 130

Step 2D3 - Integrate Runtime pattern for the Application patterns into the AOD 70, 133

Step 2D4 - Capture chosen patterns into Architecture Decisions 70, 135

Step 2E - Review and apply logical design guidelines to the AOD (Logical Nodes) 70, 139

Step 2F - Conduct technical walkthroughs to ensure that functional requirements are met 70, 140, 188

Step 3 - Develop the Physical Design 71, 142

Step 3A - Build the Component Model 71, 142, 190

Step 3B - Apply design guidelines (application level) from matched large reusable assets 71, 149, 190

Step 3C - Conduct technical walkthrough of component interaction 71, 150, 190

Step 3D - Develop the Operational Model 72, 150, 192

Step 3E - Seed the Operational Model 153, 192

Step 3F - Address operational NFRs in the Operational Model 72, 157, 194

Step 3G - Conduct technical walkthroughs to ensure that NFRs are met 72, 161, 194

work AOD

associated use cases

Generate Incident 99

work product 115

Architecture Decisions 69-70, 81, 97

Architecture Overview Diagram 69, 81, 97-98

(Subsystem) 103-105, 108-111, 113-114, 116-118

Also see AOD

Component Model 71, 98

Relationship Diagram 144

Current System Context 85

Envisioned Goals and Issues 80-81

Functional Requirements 84

High Level Project Description 68, 85

Non-Functional Requirements 68, 84, 97

Operational Model 72, 98, 157

Project Description 81, 84-85

System Context Diagram 68, 81, 83-85

Use Case Model 68, 85-86, 89, 94

development methodology activity

Demonstrate Business Benefits

and Capabilities 68

Develop

Customer Interest 67

Plan Linked to Customer's

Business Initiatives 67

Solution with Customer 68

Establish Buying Vision with the Customer 67

Evaluate Customer's Environment 67

Monitor Solution Implementation and

Ensure That Expectations Are Met 73

Qualify Opportunity 68

Refine Solution, Resolve Concerns, Close Sale 73

development methodology phase

Execute 66-67, 73, 80, 169

(develop solution requirements) 170

(develop the logical design) 177

(develop the physical design) 190

Implement 65-66, 73, 165

Plan 66-67, 77, 169

development methodology task

Analyze Current IT Infrastructure 67

Assess

Business Impact 73

Initial Viability 68

Define Business Context 67

Describe Current Organization 67

Develop

High-level

Component Model 71

project description and

System Context Diagram 81

Operational Model 72

Solution Architecture 69

Document

Envisioned goals and issues 77

IT Standards 67

Ensure Client Commitment 73

Evaluate

Integrated Solution 73

Success 73

Gain Sponsorship 68

Harvest Assets 73

Identify Business Issues and Goals 67

Monitor Pilot 73

Obtain or Develop Business Roadmap 67

Outline Solution Requirements 68

Refine Viability Assessment 73

steps in designing 81

use cases that match Portal composite pattern

generic use cases

Author and Approve Bulletin 92

Authorize and Authenticate User 91

Establish Team and Environment 91

Find SMEs 92

Manage and Track Incident

and Resolve Incident 92

Publish Bulletin 92

Request Entry 92

Spanish 396, 423

Specified Operational Model 152

SQL 327, 333, 335, 340, 343

dialect 323

Server 405

statements 295

SQLMM 344

SQLX 337, 340-341, 343, 345

SSO 164, 177, 194, 393

(also see single sign-on)

account information 149

best practices 149

guidelines 155

interface 149

usage guidelines 149

standalone availability 357

Standard Generalized Markup Language 272

standards 24

bodies 61

Starburst 336

Start Now

Collaboration Solutions 12

Infrastructure Management Solutions 12

static stub 304

Stellant 389

stock management system 169

StockQuoteService.java 294

StockQuoteServiceSoapBindingStub.java 294

storage virtualization 270

Store and Retrieve application pattern 113, 184

storyboards 97

stovepipes 83, 119

applications 107

structured data 44

Struts 310

framework 387

portlet framework 412

page sequences extension 412

Website 412

WML tags 413

struts-config.xml 412

subsystem view 69

Sun

Microsystems viii, 155

ONE 424

supply

chain 7, 14

management 22, 41, 384

performance management 14

systems 168

support

alerting 14

for mobile devices 384

Sybase 322, 390, 425

Synchronous

Chat use case 91

Collaboration delta use case 214

syndicated content 44

feeds 386, 409

Sysplex Timer and coupling facilities 376

System

Context Diagram 171

for e-government 84

work product 68, 81, 83-85

Sequence Diagram 150

Topology Diagram 150

system

interoperability 59

management 57, 81

organization 57, 81

requirements

documenting 66

systems architecture diagram 31

< Day Day Up >