This is a free 8 page sample. Access the full version at http://infostore.saiglobal.com.

HB 3112006

Handbook
HB 3112006

B2B registry serviceDetailed specification

HB 3112006

Handbook
This is a free 8 page sample. Access the full version at http://infostore.saiglobal.com.

B2B registry serviceDetailed specification

First published as HB 3112006.

COPYRIGHT Standards Australia All rights are reserved. No part of this work may be reproduced or copied in any form or by any means, electronic or mechanical, including photocopying, without the written permission of the publisher. Published by Standards Australia, GPO Box 476, Sydney, NSW 2001, Australia ISBN 0 7337 7541 1

HB 3112006

PREFACE
This handbook was prepared by Standards Australia in consultation with the Nation Office for the Information Economy (NOIE) (now the Department of Communications, Information Technology and the Arts), project subcontractors Red Wahoo and an industry based advisory panel. It is an historical record of the outputs of two projects conducted by the project team which developed a national e-business framework, registry and toolkit concepts, collectively known as BizDex. A working group managed by Standards Australia, consisting of representatives from the vendor, service provider, government agencies, standards and end-user communities provided strategic direction and oversight for the projects.
This is a free 8 page sample. Access the full version at http://infostore.saiglobal.com.

These concepts were further demonstrated in a further project in which a large buyer in the wheat industry automated the grain ticket business process between its enterprise management software application (SAP) and an office management software application (Quicken) used by many of the 40,000 small businesses it trades with. It successfully demonstrated how the BizDex infrastructure could be used to connect a trading community. This document forms part of a series consisting of: HB 310BizDexA framework for registry operations. HB 311B2B registry service Detailed specification (this Handbook). HB 312B2B registry serviceProduct business requirements. HB 313National registry and toolkit projectFinal project outcomes report. HB 314BizDexA national framework. HB 315BizDexA national frameworkROI calculator user guide. HB 316Interoperability infrastructure governance requirements. HB 317Grain ticket delivery receipt POC process implementation guidelines. HB 318B2B integration toolkitBusiness requirements. HB 319BizLinkThe B2B integration toolkit technical specification. Standards Australia wishes to acknowledge the following stakeholders who have contributed to the development of the BizDex Framework through the industry based advisory panel: Australian Information Industry Association Australia Post Australian Wheat Board Boral EAN Australia Marketboomer Microsoft Quicken Australia SAP Australia Software AG Australia Sun Microsystems Australia Tradegate Australia SuperEC

HB 3112006

While the information contained in this handbook is the latest at the time of printing, the BizDex Framework is constantly evolving under a changing standards landscape. It is intended that this handbook will be updated regularly and feedback from users would be welcome to assist in improving successive editions. To receive e-mail notification of any new or updated handbooks concerning the BizDex Framework you are able to register with Standards Watch at www.standards.org.au or visit the BizDex website at www.bizdex.com.au

This is a free 8 page sample. Access the full version at http://infostore.saiglobal.com.

HB 3112006

FOREWORD
The objective of the BizDex Framework is to enable enterprises irrelevant of their business specialization and size to readily engage with trading partners through a B2B framework, which supports low cost and scaleable interoperability. This vision is underpinned by a three-axis strategy:

S IMP LIF Y the Standards Landscape

This is a free 8 page sample. Access the full version at http://infostore.saiglobal.com.

AU T O MA T E B2B Set - Up

S PR E A D B2B compliance costs

HB 3112006

CONTENTS
Page FOREWORD .............................................................................................................................. 4 SECTION 1 INTRODUCTION 1.1 THE NATIONAL INTEROPERABILITY FRAMEWORK................................................ 6 1.2 UDDI OR ebXML? ....................................................................................................... 7 1.3 ABOUT THIS DOCUMENT .......................................................................................... 8 SECTION 2 USE CASE ANALYSIS 2.1 GENERAL.................................................................................................................. 10 2.2 STANDARDS DEVELOPMENT ................................................................................. 10 2.3 PARTNER DISCOVERY AND INTEGRATION USE CASE ....................................... 10 SECTION 3 CLASSIFICATIONS AND IDENTIFIERS 3.1 GENERAL.................................................................................................................. 13 3.2 CONTEXT CLASSIFICATIONS ................................................................................. 13 3.3 OTHER CLASSIFICATIONS...................................................................................... 19 3.4 GENERAL IDENTIFIERS........................................................................................... 25 3.5 CODE-LISTS ............................................................................................................. 28 3.6 AGLS CONTEXT ....................................................................................................... 29 SECTION 4 REPOSITORY OF REUSABLE COMPONENTS 4.1 REFERENCE STANDARDS ...................................................................................... 34 4.2 STORAGE MODEL.................................................................................................... 37 4.3 DISCOVERY.............................................................................................................. 48 SECTION 5 B2B REGISTRY SERVICE 5.1 DATA MODEL............................................................................................................ 52 5.2 ORGANIZATIONS ..................................................................................................... 57 5.3 USERS ...................................................................................................................... 59 5.4 SERVICE PROFILE ................................................................................................... 60 5.5 TECHNICAL SPECIFICATIONS ................................................................................ 62 5.6 UDDI, WSDL AND WS-I ............................................................................................ 66 5.7 BACK-OFFICE INTEGRATION.................................................................................. 70 SECTION 6 SECURITY MODEL 6.1 BACKGROUND ......................................................................................................... 75 6.2 REUSABLE COMPONENT REPOSITORY (EBXML-RR) .......................................... 75 6.3 B2B REGISTRY (WASP UDDI) ................................................................................. 76 SECTION 7 REPLICATION and FEDERATION 7.1 REPLICATION TECHNICAL SCENARIOS ................................................................ 83 7.2 REPLICATION ISSUES ............................................................................................. 85 7.3 REPLICATION BUSINESS SCENARIOS .................................................................. 90

This is a free 8 page sample. Access the full version at http://infostore.saiglobal.com.

HB 3112006

STANDARDS AUSTRALIA Australian Handbook B2B registry serviceDetailed specification

S E CT ION

I NT R O D U C T I O N

1.1 THE NATIONAL INTEROPERABILITY FRAMEWORK The objective of the NOIE registry and toolkit projects is to reduce B2B integration setup costs to the point where genuine application-to-application B2B integration can be justified even for small business and low transaction volumes. The pilot project must not just demonstrate that a message can be exchanged between a small business application (e.g. Quickbooks) and any other business (e.g. an enterprise running SAP) but must demonstrate a framework that can automate: Dozens of business processes. Using hundreds of different software applications. Between thousands of enterprises. And millions of small businesses.

This is a free 8 page sample. Access the full version at http://infostore.saiglobal.com.

To meet these goals, the national interoperability framework as described in Figure 1 will provide an infrastructure that includes: A public repository of re-usable standard message components together with a methodology and governance framework that promotes the harmonization of existing standard messages. This reduces the cost of integration by simplifying the standards landscape. A private repository of integration components such as transformation schema and web-forms that permit specific applications to comply with standards defined in the public repository. This reduces the cost of integration by spreading the cost of integration work over all users of the same business software application. A public registry of business partner profiles that includes contact information (white pages), classification information (yellow pages) and business service interface specification (green pages). This reduces cost by providing a partner discovery framework and single point of maintenance of partner information. A private registry of bilateral business relationships that computes and maintains an agreement profile from two partner profiles. The agreement profile contains all the technical information necessary to setup an integration. This reduces cost because the agreement profile can be used to automate middleware configuration. A small business integration toolkit that is designed to be embedded by application software vendors and is fully compatible with the registry and repository components of the framework described above. The toolkit reduces cost by spreading the cost of development of reusable infrastructure components across several application vendors. An architecture that is built on open, non-proprietary standards and is available to all existing standards bodies, organizations, software applications, and middleware products. This reduces cost by making the framework open to competitive pressures and eliminating any risk of royalty charges for proprietary standards.

Standards Australia

www.standards.org.au

7
Pu b li s h "pr i vate" t r a n s fo r m at i o n s Pu b li s h "publi c" s t a n d ar d s Pu b li c Re p o s i tor y

HB 3112006

S er v i c e prov i d er

S t a n d ar d s Body

3 Pu b l i s h b u s i n e s s "par t ner profile"

Pr i vate R e p o s i to r y

D ow n l o ad t r a n s fo r m at i o n s

Pu b li c Re g i s tr y

Pr i vate Re g i s tr y C o m p u te & d ow nl oad "par t ner agree me nt " Busin e s s Tr ans a c t ions 6

This is a free 8 page sample. Access the full version at http://infostore.saiglobal.com.

Enter pr i s e M i d d l eware

S M E To o l k i t

E nt e rp ris e F M I S

LEGEN D : = Fre e p u b l i c i n fr a s t r u c ture = Pr i vate s er v i c e o n p u b li c i nfr a s tr u c ture = Pr i vate i n fr a s t r u c t ur e

S M E A p p li c a t io n

FIGURE 1 FRAMEWORK ARCHITECTURE The first document in the registry stream HB 312 defines registry requirements from a product perspective. This document builds on that document to define the framework for population and control of the registry and repository content. 1.2 UDDI OR ebXML? There are two use-cases for the registry and repository. The first is as a standards development platform (i.e. a place to store reusable components etc). The second is as a trading partner discovery and integration platform. There are also two well established standards for B2B registries: UDDI (Universal Description, Discovery and Integration) and ebXML RIM/RSS (the registry / repository specifications from the UN/CEFACT and OASIS ebXML community). A key decision iswhich one to use? The key issues faced are: UDDI has significant vendor traction (Microsoft, IBM, etc) and is likely to be supported by most middleware vendors and enterprise application vendors. However UDDI has a very specific data model that is not easily used for anything except discovery of organizations and their web services. UDDI also has no associated repository that provides lifecycle management. The limited flexibility of UDDI is also an advantage it is much easier to replicate data between registries when the data model is consistent. This is very good for the wide user community that need to discover and bind to trading partner profiles; and

www.standards.org.au

Standards Australia

This is a free preview. Purchase the entire publication at the link below:

HB 311-2006, B2B registry service - Detailed specification

This is a free 8 page sample. Access the full version at http://infostore.saiglobal.com.

Looking for additional Standards? Visit SAI Global Infostore Subscribe to our Free Newsletters about Australian Standards in Legislation; ISO, IEC, BSI and more Do you need to Manage Standards Collections Online? Learn about LexConnect, All Jurisdictions, Standards referenced in Australian legislation Do you want to know when a Standard has changed? Want to become an SAI Global Standards Sales Affiliate? Learn about other SAI Global Services: LOGICOM Military Parts and Supplier Database Metals Infobase Database of Metal Grades, Standards and Manufacturers Materials Infobase Database of Materials, Standards and Suppliers Database of European Law, CELEX and Court Decisions

Need to speak with a Customer Service Representative - Contact Us