Oracle B2B: Concepts and Implementation Volume I Student Guide

Transcription

1 Oracle B2B: Concepts and Implementation Volume I Student Guide D17343GC20 Edition 2.0 March 2008 D54328

2 Authors Jeffrey Hutchins Cliff Wright Deirdre Matishak Technical Contributors and Reviewers Ramesh Anantharamaiah Krishnaprem Bhatia Ted Hong Eng Khor Shub Lahiri Sankar Mani JK Nair Sundararaman Shenbagam Juilan Trotman Editors Aju Kumar Raj Kumar Susan Moxley Copyright 2008, Oracle. All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California USA. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Government s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract. Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Graphic Designers Steve Elwood Satish Bettegowda Publishers Joseph Fernandez Veena Narasimhan

3 Contents Preface I Introduction Objectives I-2 Course Target Audience I-3 Course Objectives I-4 Suggested Class Schedule I-5 Use Cases for Practices I-7 Practice Configuration Basic Flow I-8 Practice Configuration Directory Structure I-9 Summary I-10 1 Overview Objectives 1-2 Requirements for E-Commerce 1-3 Oracle Fusion Middleware: Addressing E-Commerce Requirements 1-4 Oracle Integration and Process Management Components 1-6 Benefits of an E-Commerce Solution with Oracle SOA 1-7 Oracle B2B Concepts 1-8 Complete Picture: Outbound Purchase Order Use Case 1-9 Document Management 1-11 Oracle B2B: Document Editor Powered by EDIFECS 1-12 Oracle B2B: Trading Partner Management 1-13 Supported Messaging Systems 1-14 Management and Reporting Options 1-15 Oracle B2B: A Typical Topology 1-16 Oracle B2B: Three-Tier Topology Example 1-17 Oracle B2B: High Availability Topology Example 1-18 Summary B2B Standards Objectives 2-2 What Do B2B Standards Address? 2-3 B2B Standards Considerations 2-4 Comparison of B2B Common Standards 2-5 E-Commerce: B2B in a Real-World Context 2-7 E-Commerce: Acknowledgement Types 2-8 Document 2-9 iii

4 Packaging 2-10 Transport 2-11 Messaging Systems 2-12 Trading Partner Profile and Agreement 2-13 Process 2-14 Identifying Inbound Documents or Transaction Sets 2-15 Identifying the Trading Partner Based on the Messaging System 2-16 Identifying the Trading Partner Based on Transport 2-17 Identifying the Trading Partner Based on the Envelope 2-18 Identifying the Document 2-19 Identifying a Custom Document 2-20 Identifying a Valid Document and Envelope by Using EDI X Identifying a Valid Document and Envelope by Using EDI UN/EDIFACT 2-22 Identifying a Valid Document and Envelope by Using Health Level 7 (HL7) 2-23 Identifying a Valid Document by Using RosettaNet 2-24 Identifying a Valid Document by Using ebms 2-25 Common B2B Acronyms 2-26 Summary 2-28 Practice 2 Overview: Preparing the Practice Environment Oracle B2B Concepts Objectives 3-2 Oracle B2B Implementation Methodology 3-3 Identifying Trading Partner Business Protocol Capabilities 3-5 Documents Concepts 3-6 Defining the Business Action 3-7 Document Revision 3-8 Document Type 3-9 Document Definition 3-10 Trading Partners 3-11 Trading Partner Profiles: General Information 3-12 Trading Partner Profiles: Organization and User Information 3-13 Trading Partner Capabilities: Internal Delivery Channels 3-14 Trading Partner Profile: Operational Capabilities 3-15 Trading Partner Profile: Communication Capabilities 3-16 Creating Trading Partner Agreements 3-19 Defining a Deployment Configuration 3-20 Stages of Deploying a Configuration 3-21 B2B Reports 3-22 B2B Reports: Advanced Options 3-23 B2B Administration 3-24 Recap: How the Pieces Go Together 3-25 iv

5 Most Common Errors 3-26 Summary Implementing 1Sync over AS2 Objectives 4-2 What Is 1Sync? 4-3 What Are the Benefits? 4-4 How Does It Work? 4-5 UCCnet Elements 4-6 What Is Applicability Statement 2 (AS2)? 4-7 AS2 Messaging System Functionality 4-8 AS2 Message Processing: Closed Loop Security 4-9 AS2 Document Exchange Security 4-10 Identifying Inbound Documents over AS Identifying the Trading Partner 4-12 Identifying the Document 4-13 Implementation Methodology 4-14 Document Definition Involving a Complex XML Schema Sync over AS2 Process Flow 4-16 Summary Implementing XML over ebms Objectives 5-2 What Is ebms? 5-3 Oracle B2B Support 5-4 Identifying Inbound Documents over ebms 5-5 Identifying the Trading Partner 5-6 Identifying the Document 5-7 Alternative Way to Identify the Document 5-8 Implementation Methodology 5-9 XML over ebms Process Flow 5-10 Summary 5-11 Practice 5 Overview: Implementing Custom Document over ebms Implementing RosettaNet over RNIF Objectives 6-2 What Is RosettaNet? 6-3 RosettaNet: Key Concepts 6-4 Partner Interface Process (PIP) 6-5 RosettaNet Dictionaries 6-6 RosettaNet Implementation Framework 6-7 PIP Business Documents and 2 Action PIPs 6-9 v

6 Identifying Inbound Documents by Using RosettaNet 6-10 Identifying the Trading Partner 6-11 Identifying the Document 6-12 Implementation Methodology 6-13 RosettaNet over RNIF Process Flow (PIP3A4 2 Action PIP) 6-14 Summary 6-15 Practice 6 Overview: Implementing PIP 3A4 Document over RNIF Oracle B2B Document Editor Objectives 7-2 Document Editor Basics 7-3 Document Editor Powered by EDIFECS 7-4 Document Editor Components 7-5 Why Create Custom Definitions 7-7 Creating a Document 7-8 Configuring Envelope Segment Settings 7-9 Guideline Editor User Interface 7-10 Guideline Structure 7-11 Printing and Publishing Guidelines 7-12 Published Guideline: Example 7-13 Exporting a Guideline 7-14 Writing Rules, Generating Test Data Files, and Running Analyzer 7-15 Why Create Rules 7-16 Adding Rules to the Guideline 7-17 Business Rule Types 7-18 Predefined JavaScript Objects 7-19 Generating Test Data 7-20 Data Dictionaries 7-21 Data Dictionaries and Macros 7-22 Dictionary Path Terminology 7-23 Adjusting Error Severity Based on Business Requirements 7-24 Customizing Severity Levels 7-25 Error Severity Configuration File Editor 7-26 Migrator and SpecGenerator 7-27 Migrator Use Cases 7-28 The Migration Process 7-29 The Migrator Interface 7-30 The Migrator Comparison Icons 7-31 SpecGenerator Use Cases 7-32 Summary 7-33 Practice 7 Overview: Using the Document Editor 7-34 vi

7 8 Implementing EDI X12 over AS2 Objectives 8-2 What Is EDI? 8-3 What Is X12? 8-4 EDI X12 and VICS Version Syntax 8-5 EDI Envelope for X EDI Data Hierarchy 8-7 Sample EDI X12 Message 8-8 Identifying Inbound X12 Documents over AS2 8-9 Identifying the Trading Partner 8-10 Identifying the Document 8-11 Validating Inbound X12 Envelope and Document 8-12 Implementation Methodology 8-13 X12 over AS2 Process flow 8-14 Commonly Used EDI TIP.PROPERTIES 8-15 Summary 8-17 Practice 8 Overview: Implementing EDI X12 over AS Implementing EDIFACT over File/FTP Objectives 9-2 What Is EDI? 9-3 What Is UN/EDIFACT? 9-4 UN/EDIFACT Version Syntax 9-5 EDI Envelope for UN/EDIFACT 9-6 EDI Data Hierarchy 9-7 Sample UN/EDIFACT Message 9-8 Identifying Inbound UN/EDIFACT Documents over File/FTP 9-9 Identifying the Agreement: Trading Partner Identification 9-10 Configuring for File or Directory Trading Partner Identification 9-11 Configuring for Interchange or Group Trading Partner Identification 9-12 Identifying the Document 9-13 Validating Inbound UN/EDIFACT Envelope and Document 9-14 Implementation Methodology 9-15 UN/EDIFACT over File/FTP Process Flow 9-16 Commonly Used EDI TIP.PROPERTIES 9-17 Summary 9-19 Practice 9 Overview: Implementing EDIFACT over File/FTP Implementing Health Level 7 over MLLP Objectives 10-2 What Is HL7? 10-3 HL7 Concepts 10-4 An HL7 Example: Event A vii

8 Anatomy of the Message 10-6 HL7 Data Hierarchy 10-7 Types of Acknowledgements 10-8 General Acknowledgement 10-9 Enhanced Acknowledgement Generic Acknowledgement Advanced Acknowledgement Controls What Is MLLP? MLLP Connection Types Single Delivery Channel Mode Configuring Retry Capability Document Protocol Parameter Lookup Performance Tuning Parameters MLLP Requirements Identifying Inbound Documents: HL7 over MLLP Identifying the Agreement: Trading Partner Identification Identifying the Agreement: Document Identification Validating Inbound HL7 Envelope and Document Implementation Methodology HL7 over MLLP Process Flow Summary Practice 10 Overview: Implementing: Health Level 7 over MLLP Administration Objectives 11-2 Purging the B2B Repository 11-3 Purging Run-Time Messages 11-4 Exporting and Importing Repository Metadata 11-5 Importing from the Command Line 11-6 The b2b_instancemessage View 11-7 Java Callouts 11-9 B2B Reports Security with Oracle B2B Application Server Control: General Tab Application Server Control: B2B Page Application Server Control: B2B Server Properties Changing Session Timeout Summary Oracle B2B Interoperability Objectives 12-2 Review: Outbound Purchase Order Use Case 12-3 Component Interoperability: B2B, ESB, and BPEL Process Manager 12-5 viii

9 Component Interoperability: Adapter Service 12-6 Component Interoperability: Routing ID 12-7 Component Interoperability: Technology Adapters 12-8 Component Interoperability: IP_MESSAGE_TYPE 12-9 Component Interoperability: Setting the IP_MESSAGE_TYPE Component Interoperability: Vertical Required Data Component Interoperability: Message Correlation Within a BPEL Process Error Diagnostics Error Handling Structures Error Handling: IP_EXCEPTION and IP_MESSAGE_TYPE Diagnostics: General Diagnostics: Report and Log Debug Level Typical Errors: Message Sent from Oracle B2B to ESB or BPEL Typical Errors: Message Sent from ESB or BPEL to Oracle B2B Typical Errors: Oracle B2B Communication with Trading Partner Review: Most Common Errors Summary Appendix A: Practices and Solutions for Acme, Inc. (Initiator Role) Appendix B: Practices and Solutions GlobalChips, Inc. (Responder Role) Appendix C: Troubleshooting the Practices Appendix D: Oracle B2B Installation Steps for the Classroom Appendix E: Continuing Your Education and Further Reading Index ix

10