Application of E-commerce System Based on ebXML

Document Sample
Application of E-commerce System Based on ebXML Powered By Docstoc
					Application of E-commerce System
        Based on ebXML


                       電子商務期中報告
                        報告者:林汝怡


  HUANG Jianni
  School of Economics and Management,Jiaying University
  2009 Second International Conference on Future Information Technology and Management Engineering
Outline
   Introduction
   Background
     • What is EDI?
   ebXML Architecture
     • Message delivery
     • Business processes
     • The draft trading partners and agreements
     • The registry / repository
     • Core components
   ebXML trading system model
   Test case
   Conclusion
     2010/4/12             電子商務期中報告                2
Introduction
   While EDI over the years has provided an available
    approach for the e-commerce, but this approach is
    expensive, ebXML now offers a more convenient
    way to integrate the process.

   In this paper, application of ebXML architecture,
    based on the proposed construction of e-business
    model and to achieve the online bookstore for the trial
    cases of e-commerce systems.


     2010/4/12            電子商務期中報告                   3
Background - What is EDI?
   Electronic data interchange (EDI) is the structured
    transmission of data between organizations by
    electronic means.

   It is used to transfer electronic documents from one
    computer system to another, i.e. from one trading
    partner to another trading partner.




     2010/4/12            電子商務期中報告                  4
ebXML Architecture
   Message delivery
   Business processes
   The draft trading partners and agreements
   The registry / repository
   Core components




     2010/4/12          電子商務期中報告                5
ebXML Architecture - Message delivery
   ebXML messages using the SOAP specification.

   SOAP is an XML application, to define a header that
    with the sender, receiver, routing and security details
    of the message format.




     2010/4/12            電子商務期中報告                    6
ebXML Architecture - Business
processes
   An essential feature which is also associated with
    other XML framework for different places.

   It does this by modeling language and graphics tools,
    allows the system to capture business data between
    trading partners and use the standard format possible.

   Through the definition of business processes to have a
    interoperability capabilities.



     2010/4/12            電子商務期中報告                   7
ebXML Architecture - The draft trading
partners and agreements
   Via the use of CPP of the file system to describe what
    companies can provide electronic commerce services.

   First of all enterprises to use XML format, it supports
    are listed in industry, business processes, messages
    and data exchange technology.

   Secoond, use this information to generate a CPP to
    CPA documents, automatically provide the agreement.



     2010/4/12            電子商務期中報告                   8
ebXML Architecture - The registry /
repository




  2010/4/12     電子商務期中報告              9
ebXML Architecture - Core components
   Provides industry-leading interoperability and
    business performance, acting on a single data element
    level.

   Identify the core components of most businesses use
    and cross-industry data items, giving them a neutral
    name and assigned a unique identifier.

   Through the core components, enterprises can one
    industry to another industry data with similar data
    corresponding to up.
     2010/4/12            電子商務期中報告                  10
ebXML trading system model
                 1.Get ebXML                                      3.Search the registry
                 specification                                    and get CPP
Company A




                                                                                      (Client)
                                                                                      Company B
                2.Create the
                CPP and posted to           ebXML
                the registry          registry / repository



                        4.send a commercial contract to the enterprise B


               5.two companies are on the CPA consultation and reached a consensus



            2010/4/12                       電子商務期中報告                                      11
Test case
   1. <? Xml version = '1 .0 'encoding =' gb2312 '?>
   2. <Members of Order xmlns =" x-schema:
   OrderSchema.xml ">
   3. "Membership Number" 2 "/ Member ID"
   4. "Orders"
   5. "Ordered the project title =" play with OfficeXP
   "ISBN =" O01001 ">
   6. "Pricing" 580 "/ price"
   7. "Quantity" 3 "/ Quantity"
   8. "/ Order Project"
   9. "Ordered the project title =" play with Excel2002
   "ISBN =" E01001 ">
   10. "Pricing" 490 "/ price"
   11. "Quantity" 2 "/ Quantity"
   12. "/ Order Project"
   13. "/ Order"
   14. "/ Member Order"


      2010/4/12                        電子商務期中報告            12
OrderSchema.xml
   1. <?xml version="1.0" encoding="gb2312"?>
   2. <Schema name=" Membership Order"
   xmlns="urn:schemas-microsoft-com:xml-data"
   3. xmlns:dt="urn:schemas-microsoftcom:
   datatypes">
   4. <AttributeType name="book name"
   dt:type="string" />
   5. <AttributeType name="book number"
   dt:type="string" />
   6. <ElementType name=" Membership Order "
   content="eltOnly">
   7. <group order="seq">
   8. <element type=" Membership Number" />
   9. <element type="Order" />
   10. </group>
   11. </ElementType>
   12. <ElementType name=" Membership Number "
   content="textOnly" dt:type="int" />
      2010/4/12                   電子商務期中報告        13
OrderSchema.xml(cont.)
   13. <ElementType name="Order" content="eltOnly">
   14. <element type=" Order Project " minOccurs="1"
   maxOccurs="*" />
   15. </ElementType>
   16. <ElementType name=" Order Project "
   content="eltOnly">
   17. <attribute type="book name" />
   18. <attribute type="book name" />
   19. <element type="price" />
   20. <element type=" Quantity " />
   21. </ElementType>
   22. <ElementType name="pricing" content="textOnly"
   dt:type="number" />
   23. <ElementType name=" Quantity "
   content="textOnly" dt:type="int" />
   24. </Schema>



      2010/4/12                    電子商務期中報告              14
Conclusion
   ebXML is not only defines a complete architecture,
    but also defines new ways to reflect on the business
    and, more importantly, it documented.

   In this paper, test results show that the system can
    solve the EDI to build Web services across multiple
    applications and vendors to communicate problems.




     2010/4/12           電子商務期中報告                   15

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:25
posted:6/15/2012
language:English
pages:15