Standards for Technology in Automotive Retail

 
 Home -  News Feed 
Transport Guidelines
   Next

Transport Guidelines

2009v2

Jason Loeffler

Karmak

Russell Shephard

T-Systems

Copyright © 2009 Standards for Technology in Automotive Retail

Table of Contents

I. Preface
I.I. STAR Organization
I.II. Publications Roadmap
I.III. Summary of Changes From 2009 Release 1
I.IV. Scope
I.V. The Difference Between Guidelines, Standards and Recommendations
I.VI. Overall Requirements
I.VII. Message Based Routing
II. Executive Summaries
II.I. Overview
II.II. Message Handling
II.III. Security
II.IV. Management and Functionality
Part I. Requirements
1. Transport Methods
1.1. The Two Recommended Transport Methods
1.1.1. STAR ebMS Stack
1.1.2. STAR Webservices Stack
2. Reliable Message Delivery
2.1. Overview
2.2. Requirements
2.2.1. Delivery Assurance Profiles
2.2.2. Delivery Assurance Features
2.2.3. Intermediaries
2.2.4. Intermediary Authentication and Authorization
2.2.5. Standardized Error Handling and Monitoring
2.3. Discussions
2.3.1. Message Sequencing
2.3.2. Per Message or Per Sequence
2.3.3. WS-Policy Framework
2.4. Decisions
2.4.1. Intermediary Issues
2.4.2. Routing Intermediaries
3. Collaboration
3.1. Requirements
3.1.1. Large Message Handling
3.1.2. Bi-Directional Messaging
3.1.3. Delayed Response
3.1.4. Immediate Response
3.1.5. Message Ordering
3.1.6. Pull Message
3.2. Discussions
3.2.1. Very Large Messages
3.2.2. Immediate Response
3.2.3. Long Running Conversations and Supporting Conversational State
3.2.4. Push Messaging
3.2.5. Lite Clients; Mobile and PDA
3.2.6. Long Running Conversations and Business Process Management
3.3. Best Practices
3.3.1. Long Running Conversations and Business Process Management
3.4. Decisions
3.4.1. Large Message Handling
3.4.2. Bi-Directional Messaging
3.4.3. Delayed Response
3.4.4. Immediate Response
3.4.5. Message Ordering
3.4.6. Pull Message
4. Performance
4.1. Background
4.2. Requirements
4.2.1. Benefits of Compression
4.2.2. Issues with Compression
4.3. Discussions
4.3.1. Payload Compressions
4.3.2. gzip Compression
4.3.3. Using Payload Compression
4.3.4. Issues with Payload Compression
4.3.5. Payload Content
4.3.6. HTTP Compression
4.3.7. Issues with HTTP Protocol Compression
4.3.8. Decisions
5. Auditing
5.1. Requirements
5.1.1. Non-Repudiation
5.1.2. Security
5.1.3. Logging
5.1.4. Timestamps
5.2. Discussions
5.2.1. Trusted Timestamp Services
5.2.2. Timestamp Format
5.2.3. Key Data Fields
5.2.4. Associating Messages with Business Transactions
5.2.5. Message IDs through Intermediaries
5.3. Best Practices
5.3.1. Associate Transport MessageIDs with Business Transactions
5.3.2. Saving Messages for Non-Repudiation
5.4. Decisions
5.4.1. Message Logging
5.4.2. Timestamp Format
5.4.3. MessageID Format
5.4.4. Key Data Fields
Part II. Security
6. Security
6.1. Business Messaging Security
6.2. Requirements
6.3. STAR Security Issues: Scope
6.4. Message-Level Security Versus Infrastructure Security
7. Infrastructure Level Security
7.1. Requirements
7.2. Discussions
7.2.1. SSL over HTTP
7.2.2. Virtual Private Network
7.2.3. Decisions
8. Message Level Security
8.1. Requirements
8.1.1. Applying STAR Transport Requirements to Message-Level Security
8.1.2. Using Digital Certificates for Identification and Authentication
8.1.3. Using Username/Passoword for Identification and Authentication
8.1.4. Message-Level Source, Target and System Authentication
8.2. Discussions ebMS Message-Level Security
8.2.1. Digtally Signing a STAR ebMS Message
8.2.2. STAR ebMS Message-Level Encryption
8.3. Discussion Web Services Message-Level Security
8.3.1. Web Services Authentication Options
8.3.2. Digital Signature
8.3.3. Username/Password Hash
8.3.4. Username/Password Clear-text over HTTPS
8.3.5. Binary Token Shared Secret
8.3.6. Security Assertion Markup Language (SAML)
8.3.7. Web Services Message-Level Privacy with Data Encryption
8.4. Discussion Digital Certificate Format
8.5. Decisions
Part III. Compliance and Testing
9. Internet Connectivity
9.1. Background
9.2. Requirements
9.2.1. Message Handshaking and Feature Set
9.2.2. Flexibility of Implementation Cost and Footprint
9.2.3. The Ability to Support Open Standards Based Messaging Solutions
9.2.4. Internet Connectivity Types
9.3. Internet Connectivity Implementation Patterns
9.3.1. Addressable Hub
9.3.2. Addressable Endpoint
9.3.3. Non-Addressable Endpoint
9.4. Discussions
9.4.1. Endpoint Addressing
9.5. Decisions
10. Management
10.1. Background
10.2. Requirements
10.2.1. Administration
10.2.2. Monitoring and Diagnostics
10.2.3. Synchronized System Time and Consistent Timestamps
10.2.4. Message Logging
10.2.5. Message Status
10.3. Discussions
10.3.1. Security Token Management
10.3.2. ebMS Ping/Pong
10.3.3. Network Time Protocol (NTP)
10.3.4. Message Logging
10.4. Decisions
10.4.1. General
10.4.2. ebMS v2.0
10.4.3. Web Services Management
10.4.4. Logging
11. Registry
11.1. Requirements
11.1.1. Discovery
11.1.2. Service Transparency
11.1.3. Location Transparency
11.1.4. Versioning
11.2. Discussions
11.2.1. Universal Business Registry (UBR)
11.2.2. Generic Repository
11.2.3. CPPA
11.2.4. Digital Certificates
11.3. Decisions
11.3.1. UDDI is the Registry standard for STAR Web Services
11.3.2. Universal Business Registry (UBR)
12. STAR Transport Testing
12.1. Overview
12.2. STAR Conformance
12.3. STAR Testing Approach
12.3.1. STAR Checklists
12.4. How to Use the STAR Checklists
12.5. STAR Transport Guidelines - Testing Checklist
A. Resources / References
B. Technical Summary
C. Ranking Summary

List of Figures

1. System Migration
1.1. STAR ebMS Stack
1.2. STAR Web Services Stack
6.1. Infrastructure Level Security
6.2. Message Level Security
   Next
   Preface