Electronic Business: Concepts, Methodologies, Tools, and Applications (4-Volumes) P18

Business Networking Hermes B2B messaging server provides enterprises a standardized, reliable and secure infrastructure to exchange business data over the Internet. It supports secure messaging func-tions through security technologies such as XML signature, secure socket layer (SSL), and secure multipurpose internet mail extensions (S/MIME). Aiming at supporting different requirements from enterprises of all sizes, it implements reliable messaging, message packaging, message order-ing, error handling, security, synchronous reply, message status service, and supports transport protocols, such as HTTP and SMTP. Hermes DOVRVXSSRUWVWKHFRQFHSWRI³TXDOLW\RIVHUYLFH´ by respecting in-force agreements, which are expressed as CPA. ebMail is a GUI system. It makes use of open standards (ebXML), underlying GUI, in order to communicate with business partners. Business messages are composed and read in GUI form, so that enterprises do not need back-end integration. tion for a reliable exchange of messages between business partners. RosettaNet aims at aligning business processes of supply chain partners, a goal which is achieved E\WKHFUHDWLRQRI3,3V(DFK3,3GH¿QHVKRZ WZRVSHFL¿FSURFHVVHVUXQQLQJLQWZRGLIIHUHQW partner organizations) will be standardized and interfaced across the entire supply chain. PIPs LQFOXGH DOO EXVLQHVV ORJLF PHVVDJH ÀRZ DQG message contents to enable alignment of the two processes. The purpose of each PIP is to provide common business/data models and documents enabling system developers to implement Roset-taNet eBusiness interfaces. Each PIP includes: partner role descriptions (individuals/organiza-tions); business data involved (and corresponding XML documents); and business process activi-ties, a validation tool and implementation guide (http://www.rosettanet.org). RosettaNet’s standardization efforts refer to: The project is platform-neutral; it is developed by using Java, and the GUI part is using Java Swing. For ebXML Messaging Service, ebMail makes use of Hermes project. RosettaNet RosettaNet (http://www.rosettanet.org) is a VHOIIXQGHG QRQSUR¿W RUJDQL]DWLRQ DURXQG D consortium of major IT, electronic components, and semiconductor manufacturing companies aiming at aligning business processes between partners in a given supply chain: Partners agree on partner interface processes (PIPs) to use, and are then ready to start a business scenario. RosettaNet implementation framework (RNIF) SURYLGHVH[FKDQJHSURWRFROVIRUTXLFNDQGHI¿FLHQW LPSOHPHQWDWLRQRI3,3V51,)GH¿QHVWKHRYHUDOO • PIPs:GH¿QLQJEXVLQHVVSURFHVVHVEHWZHHQ trading partners • PIP directory: providing faster access to PIPs’ information • Dictionaries: which provide a common set of properties for PIPs. (e.g., RosettaNet Business Dictionary: designates the prop-erties used in basic business activities, and Technical Dictionary provides proprieties IRUGH¿QLQJSURGXFWV • RNIF:SURYLGLQJVSHFL¿FDWLRQVIRUSDFNDJ-ing, routing, and transport of all PIP mes-sages and business signals • Product and partner code: which expedites the alignment of business processes between trading partners RosettaNet does not provide a model for sup- RosettaNet business message format for business documents exchange, with elements to support authentication, authorization, encryption, and non-repudiation; details of the bindings for the WUDQVIHUSURWRFROVHJ+773DQGWKHVSHFL¿FD- ply chain arrangements as a whole, but a model for linking supply chain members’ information ÀRZVLQDXQLIRUPPDQQHUZLWKLQVSHFL¿FEXVL-ness processes. The RosettaNet model describes several business activities that can be mapped to 104 Business Networking RosettaNet XML-framework. These activities are collected inside PIPs. Web Services and BPEL4WS Web services (http://www.w3.org/2002/ws) aim at achieving universal interoperability among applications by using Web standards. They use ORRVHO\FRXSOHGLQWHJUDWLRQPRGHOWRDOORZÀH[LEOH integration of heterogeneous systems in a variety of domains, including B2B, B2C, and enterprise LQWHJUDWLRQDQGLQWHURSHUDELOLW\6SHFL¿FDWLRQV derived from Web services include: SOAP, WSDL, and UDDI. SOAP (http://www.w3.org/ TR/soapGH¿QHVDQ;0/PHVVDJLQJSURWRFROIRU basic service interoperability. WSDL (http://www. w3.org/TR/wsdl) introduces a common grammar for describing services, and UDDI (http://www. uddi.org) provides the infrastructure required to publish and discover services in a systematic ZD\$OOWKHVHVSHFL¿FDWLRQVDOORZDSSOLFDWLRQVWR ¿QGHDFKRWKHUDQGLQWHUDFWIROORZLQJDORRVHO\ coupled platform-independent model. However, system integration requires much more than the ability to conduct simple interactions by us-ing standard protocols. According to Andrews, Curbea, Dholakia, Goland, Klein, Leymann, Liu, Roller, Smith, and Thatte (2003), the full potential of Web services as an integrated platform will be achieved only when applications and business processes will be able to integrate their complex interactions by making use of a standard process integration model. Business Process Execution Language for Web Services (BPEL4WS, http://xml.coverpages. org/bpel4ws.html) provides an XML-based pro-FHVVGH¿QLWLRQODQJXDJHWKDWHQDEOHVWKHIRUPDO description of business processes and interaction protocols (Andrews, et al., 2003). BPEL4WS GH¿QHVDQLQWHURSHUDEOHLQWHJUDWLRQPRGHOWKDW facilitates the expansion of automated process integration in both intra-enterprise and B2B integration. BPEL4WS is meant to model the behavior of executable business processes (which are modeling the actual behavior of a participant in a business interaction), and abstract business processes (which are process descriptions for business protocols). In this way, BPEL4W extends Web services’ interaction model and enables it to support business transactions. BPEL4WS depends on the following XML-EDVHGVSHFL¿FDWLRQV:6`/;0/6FKHPD 1.0, XPath 1.0, and WS-Addressing. Among these, :6`/KDVWKHPRVWLQÀXHQFHRQ%3(/:633 interaction between services, described in WSDL, is at the core of BPEL4WS process model, and both the process and its partners are modeled as WSDL VHUYLFHV7KHGH¿QLWLRQRIEXVLQHVVSURFHVVHVDOVR follows the WSDL model of separation between the abstract message contents used by the business process and deployment information. CONCLUSION AND FURTHER RESEARCH Current market conditions and information and communication technology (ICT) developments determined enterprises to adopt new ways of un-dertaking business. As a consequence, new forms of collaboration emerged, such as collaborative networked organizations (CNO). In this context, the need to support enterprise integration and interoperability is increasing. Several conceptual frameworks, integration standards, technologies, and supporting infrastructures are being devel-oped. Despite the relevant developments in the area of enterprise integration and interoperability, DQGWKHQXPHURXVVFLHQWL¿FUHVXOWVLQWKHEXVLQHVV networking area, it is generally accepted that more work needs to be done, mainly concerning CNO creation or setting-up, support, and implementa-tions (Camarinha-Matos & Afsarmanesh, 2003). Most of the technologies and infrastructures supporting CNO currently available are at their beginnings, and require considerable implementa- 105 Business Networking WLRQDQGFRQ¿JXUDWLRQHIIRUWV,QJHQHUDOWKHUHLV a lack of an effective approach to interoperability (mainly concerning software inter-operation and information exchange integration), and a lack of VWDQGDUGGH¿QLWLRQVDQGPHFKDQLVPV 6LQFHLWLVYHU\GLI¿FXOWQRWWRVD\LPSRV-VLEOHWR¿QGDVWDQGDUGZKLFKLVYDOLGRUHDVLO\ FRQ¿JXUDEOHVXSSRUWLQJDZLGHUDQJHRIVHUYLFHV and operations concerning enterprise integration and interoperability, a convenient approach is WRGHYHORSVWDQGDUGVIRUVSHFL¿FLQGXVWU\VHF-tors (e.g., papiNet for paper and forest industry), considering also the fact that a single process and document standard for communicating business transactions is critical to companies buying and selling products from the same industry. Roset-taNet and papiNET are examples of successful standards developments supporting integra-WLRQDQGLQWHURSHUDELOLW\IRUDVSHFL¿FLQGXVWU\ sector: high-tech industry and paper industry, respectively. Although several standards (e.g., ebXML) provide support for different requirements regard-ing enterprise integration and interoperability, in a networked environment, it would be naïve to consider that it is possible to convert everybody to a single platform (e.g., ebXML). Each technology or standard has its advantages and disadvantages. No true technology or standard can work as an isolated island; different technologies are com-ELQHGRUDGDSWHGWRVSHFL¿FQHHGV,WLVWKHUHIRUH challenging to observe the rapid evolution of dif-ferent technologies, standards, frameworks, and the development of emerging projects aiming at combining these standards and technologies (e.g., the development of research projects combining both ebXML and RosettaNet frameworks). The questions that guided this work were DQVZHUHG0DMRUEHQH¿WVIRUHQWHUSULVHLQWHJUD-WLRQZHUHLGHQWL¿HG7KHPRVWUHOHYDQWVWDQGDUGV frameworks, technologies, and supporting in-frastructures aiming at enterprise integration and interoperability were analyzed, and relevant research projects in the area of enterprise net- ZRUNLQJZHUHEULHÀ\SUHVHQWHG)XUWKHUUHVHDUFK ZLOOEHSXUVXHGWRGH¿QHFULWHULDWREHXVHGWR compare the available standards and frameworks. However, in the context of CNO, as mentioned by Bussler (2003), the grander challenge will be: how to achieve self-forming collaborative networked organizations (SFCNO)—that is CNO where the detection of service provider, as well as their contracting, is automated. ACKNOWLEDGMENT The author, Claudia-Melania Chituc, would like to acknowledge Fundação para a Ciencia e a Tec-nologia for PhD grant SFRH/BD/19751/2004. REFERENCES Andrews, T., Cubera, F., Dholakia, H., Goland, Y., Klein, J., Leymann, F., Liu, K., Roller, D., Smith, D., & Thatte, S. (2003). Business Process Execution Language for Web Services—Version 1.1. White paper. Retrieved September 10, 2005, from http://ifr.sap.com/bpel4ws/BPEL%20V1-1%20May%205%202003%20Final.pdf BPEL4WS. (2005). Business Process Execution Language for Web Services Version 1.1. Retrieved September 10, 2005, from http://www-128.ibm. FRPGHYHORSHUZRUNVOLEUDU\VSHFL¿FDWLRQZV bpel/ Bussler, C. (2003). B2B integration—concepts and architectures. Springer. Camarinha-Matos, L. M. (2003).New collabora-tive organizations and their research needs in process and foundations for virtual organizations. Kluwer Academy Publishers. Camarinha-Matos, L. M., & Afsarmanesh, H. (2003). Elements of a base VE infrastructure. Computers in Industry, 51(2) 139-163. 106 Business Networking Campbell, S. (2001). ebXML—the global standard for electronic business. Retrieved March 17, 2006, from http://www.gca.org/papers/xmleurope2001/ papers/pdf/s03-2.pdf Chituc, C. M., & Azevedo, A. L. (2005a) (in press). Enablers and technologies supporting self-form-ing networked organizations. International Work-shop on Enterprise Integration, Interoperability and Networking (EI2N), Geneva, Switzerland. Hermes Publishing. Chituc, C. M., & Azevedo, A. L. (2005b, Sep-tember). Multi-perspective challenges on col-laborative networks business environment. In L. Camarinha-Matos, H. Afsarmanesh, & A. Ortiz (Eds.),Collaborative networks and breeding en-vironments: Proceedings of the 6th IFIP Working Conference on Virtual Enterprises, Spain (Vol. 186, pp. 25-32). Boston: Springer. CORDIS. (2005). Building grids for Europe—a crucial technology for science and industry. Re-trieved September 10, 2005, from http://www. cordis.lu/ist/grids Crargil, C. F. (1989).Information technology stan-dardization: Theory, process, and organization. Bedford: Digital Press. Dournaee, B. (2004). Introduction to ebXML. White paper. Retrieved September 10, 2005, from http://dev2dev.bea.com/pub/a/2004/12/ebXML. html ebXML. (2003). ebXML adoptation update. Re-trieved from http://www.ebxml.org European Commission. (2005). Strengthening competitiveness through production networks—a perspective from European ICT research projects LQWKH¿HOGRIHQWHUSULVHQHWZRUNLQJ IEEE. (1990). IEEE standard computer diction-ary: A compilation of IEEE standard computer glossaries. New York: Institute of Electrical and Electronics Engineers. IFAC/IFIP. (2000). GERAM: Generalized en-terprise reference architecture and methodol-ogy. IFAC/IFIP Task Force on Architectures for Enterprise Integration. Li, H., & Williams, T. J. (2000). The interconnected chain of enterprises as presented by the Purdue enterprise reference architecture. Computers in Industry, 42, 265-274. Li, H., & Williams, T. J. (2003). Interface design for the Purdue enterprise reference architecture (PERA) and methodology in e-work. Production Planning & Control, 14(8), 704-719. Nurmilaakso, J. M., & Kotinurmi, P. (2004). A review of XML-based supply-chain integration. Production Planning & Control, 15(6), 608-621 papiNet. (2004). papiNet from top to bottom—an introduction to papiNet. Retrieved September 10, 2005, from http://www.papinet.org/presenta-tions.asp Pusnik, M., Juric, M. B., Rozman, I., & Sumak, B. (2000).A comparison of ebXML and RosettaNet. White paper. Retrieved September 10, 2005, from http://www.ebpml.org/articles.htm SCOR—Supply Chain Operations Reference Model. (n.d.). Retrieved from http://www.sup-ply-chain.org SWWS—Semantic Web-Enabled Web Services. (2003). Analysis of B2B Standards and Systems: Deliverable D1.1 SWWS Project. Retrieved from http://swws.semanticweb.org Vernadat, F. (1996). Enterprise modeling and integration—principles and applications. Chap-man & Hall. :HEEHU`7KHEHQH¿WVRIHE;0/IRU e-business. In XML 2004 Conference. Retrieved September 10, 2005, from http://www.idealliance. org/proceedings/xml04/papers/44/webber.pdf :RUNÀRZ0DQDJHPHQW&RDOLWLRQThe ZRUNÀRZPDQDJHPHQWFRDOLWLRQVSHFL¿FDWLRQV 107 Business Networking Terminology and glossary. Retrieved from http:// www.wfmc.org Zachman, J. A. (1987). A framework for informa-tion systems architecture. IBM Systems Journal, 26(3), 276-292. Zarli, A, & Poyet, P. (2001). A framework for distributed information management in the virtual enterprise: The VEGA project. In L. M. Camarinha-Matos & H. Afsarmanesh (Eds.), Infrastructures for virtual enterprises—network-ing industrial enterprises (1st ed.), (pp. 293-306). Boston: Kluwer Academic Publishers. This work was previously published in Knowledge and Technology Management in Virtual Organizations: Issues, Trends, Opportunities and Solutions, edited by G. Putnik; M. Cunha, pp. 334-353, copyright 2007 by IGI Publishing (an imprint of IGI Global). 108 ... - tailieumienphi.vn