BEA WebLogic Collaborate

Transcription

1 BEA WebLogic Collaborate A Compoet of BEA WebLogic Itegratio Itroducig BEA WebLogic Collaborate BEA WebLogic Collaborate Release 2.0 Documet Editio 2.0 July ServiceNow, Ic.'s Exhibit 1004

2 Copyright Copyright 2001 BEA Systems, Ic. All Rights Reserved. Restricted Rights Leged This software ad documetatio is subject to ad made available oly pursuat to the terms of the BEA Systems Licese Agreemet ad may be used or copied oly i accordace with the terms of that agreemet. It is agaist the law to copy the software except as specifically allowed i the agreemet. This documet may ot, i whole or i part, be copied photocopied, reproduced, traslated, or reduced to ay electroic medium or machie readable form without prior coset, i writig, from BEA Systems, Ic. Use, duplicatio or disclosure by the U.S. Govermet is subject to restrictios set forth i the BEA Systems Licese Agreemet ad i subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR ; subparagraph (c)(1)(ii) of the Rights i Techical Data ad Computer Software clause at DFARS , subparagraph (d) of the Commercial Computer Software--Licesig clause at NASA FAR supplemet ; or their equivalet. Iformatio i this documet is subject to chage without otice ad does ot represet a commitmet o the part of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. Trademarks or Service Marks BEA, WebLogic, Tuxedo, ad Jolt are registered trademarks of BEA Systems, Ic. How Busiess Becomes E-Busiess, Operatig System for the Iteret, Liquid Data, BEA WebLogic E-Busiess Platform, BEA Builder, BEA Maager, BEA elik, BEA WebLogic Commerce Server, BEA WebLogic Persoalizatio Server, BEA WebLogic Process Itegrator, BEA WebLogic Collaborate, BEA WebLogic Eterprise, BEA WebLogic Server, BEA WebLogic Itegratio, E-Busiess Cotrol Ceter, BEA Campaig Maager for WebLogic, ad Portal FrameWork are trademarks of BEA Systems, Ic. All other trademarks are the property of their respective compaies. Itroducig BEA WebLogic Collaborate Documet Editio Date Software Versio 2.0 July ServiceNow, Ic.'s Exhibit 1004

3 Cotets About This Documet What You Need to Kow...v e-docs Web Site... vi How to Prit the Documet... vi Cotact Us!... vi Documetatio Covetios... vii 1. Overview Feature Highlights for WebLogic Collaborate Meetig the Requiremets of Your E-Busiess Coectig Tradig Parters Defiig Coversatios ad Roles Maagig Busiess Processes Supportig Busiess Protocols Esurig the Security of Trasactios Defiig Collaboratio Agreemets Maagig Coversatios Maagig Systems ad Applicatios Documetatio Roadmap for WebLogic Collaborate Gettig Started Usig WebLogic Collaborate Cofiguratio Models Peer-to-Peer Cofiguratio Hub-ad-Spoke Cofiguratio Usig WebLogic Collaborate: The Ed-to-Ed View Create Coversatio Defiitios Create Workflow Templates Itroducig BEA WebLogic Collaborate 003 ServiceNow, Ic.'s Exhibit 1004 iii

4 Create Tradig Parters ad Delivery Chaels Create Collaboratio Agreemets Sed ad Receive Busiess Messages Export ad Import Repository Iformatio Start Busiess Collaboratio Idex iv Itroducig BEA WebLogic Collaborate 004 ServiceNow, Ic.'s Exhibit 1004

5 About This Documet This documet explais how to get started usig the BEA WebLogic Collaborate software: Chapter 1, Overview, provides a overview of the features of the WebLogic Collaborate software, a summary of the requiremets of busiess-to-busiess e-commerce, ad a descriptio of how you ca meet the eeds of your e-commerce busiess usig WebLogic Collaborate. Chapter 2, Gettig Started Usig WebLogic Collaborate, provides a architectural overview of the WebLogic Collaborate software, ad a ed-to-ed example of the tasks you eed to complete to get your WebLogic Collaborate eviromet ready to exchage busiess messages with busiess parters. What You Need to Kow This documet is writte for maagers, system admiistrators, ad programmers who are iterested i uderstadig the architectural requiremets for implemetig ad admiisterig e-commerce collaboratios based o WebLogic Collaborate. It is assumed that you have a workig kowledge of the BEA WebLogic Server system, XML, Eterprise Java Beas, ad Java programmig. Itroducig BEA WebLogic Collaborate 005 ServiceNow, Ic.'s Exhibit 1004 v

6 e-docs Web Site The WebLogic Collaborate product documetatio is available o the BEA Systems, Ic. corporate Web site. From the BEA Home page, click Product Documetatio or go directly to the Product Documetatio page at How to Prit the Documet You ca prit a copy of this documet from a Web browser, oe file at a time, by usig the File >Prit optio o your Web browser. A PDF versio of this documet is available o the WebLogic Collaborate documetatio Home page o the e-docs Web site (ad also o the documetatio CD). You ca ope the PDF i Adobe Acrobat Reader ad prit the etire documet (or a portio of it) i book format. To access the PDFs, ope the WebLogic Eterprise documetatio Home page, click the PDF Files butto, ad select the documet you wat to prit. If you do ot have Adobe Acrobat Reader istalled, you ca dowload it for free from the Adobe Web site at Cotact Us! Your feedback o the WebLogic Collaborate documetatio is importat to us. Sed us at docsupport@bea.com if you have questios or commets. Your commets will be reviewed directly by the BEA professioals who create ad update the WebLogic Collaborate documetatio. I your message, please idicate that you are usig the documetatio for WebLogic Collaborate Release 2.0. vi Itroducig BEA WebLogic Collaborate 006 ServiceNow, Ic.'s Exhibit 1004

7 If you have ay questios about this release of WebLogic Collaborate, or if you have problems istallig ad ruig WebLogic Collaborate, cotact BEA Customer Support through BEA WebSUPPORT at You ca also cotact Customer Support by usig the cotact iformatio provided o the Customer Support Card, which is icluded i the product package. Whe cotactig Customer Support, be prepared to provide the followig iformatio: Your ame, address, phoe umber, ad fax umber Your compay ame ad compay address Your machie type ad authorizatio codes The ame ad versio of the product you are usig A descriptio of the problem ad the cotet of pertiet error messages Documetatio Covetios The followig documetatio covetios are used throughout this documet. Covetio boldface text Ctrl+Tab italics Item Idicates terms defied i the glossary. Idicates that you must press two or more keys simultaeously. Idicates emphasis or book titles. Itroducig BEA WebLogic Collaborate 007 vii ServiceNow, Ic.'s Exhibit 1004

8 Covetio moospace text moospace boldface text moospace italic text UPPERCASE TEXT Item Idicates code samples, commads ad their optios, data structures ad their members, data types, directories, ad file ames ad their extesios. Moospace text also idicates text that you must eter from the keyboard. Examples: #iclude <iostream.h> void mai ( ) the poiter psz chmod u+w * \tux\data\ap.doc tux.doc BITMAP float Idetifies sigificat words i code. Example: void commit ( ) Idetifies variables i code. Example: Strig expr Idicates device ames, eviromet variables, ad logical operators. Examples: LPT1 SIGNON OR { } Idicates a set of choices i a sytax lie. The braces themselves should ever be typed. [ ] Idicates optioal items i a sytax lie. The brackets themselves should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list]... Separates mutually exclusive choices i a sytax lie. The symbol itself should ever be typed. viii Itroducig BEA WebLogic Collaborate 008 ServiceNow, Ic.'s Exhibit 1004

9 Covetio Item... Idicates oe of the followig i a commad lie: That a argumet ca be repeated several times i a commad lie That the statemet omits additioal optioal argumets That you ca eter additioal parameters, values, or other iformatio The ellipsis itself should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list] Idicates the omissio of items from a code example or from a sytax lie. The vertical ellipsis itself should ever be typed. Itroducig BEA WebLogic Collaborate 009 ServiceNow, Ic.'s Exhibit 1004 ix

10 x Itroducig BEA WebLogic Collaborate 010 ServiceNow, Ic.'s Exhibit 1004

11 CHAPTER 1 Overview Eterprises strive to itegrate, automate, ad streamlie core iteral ad exteral busiess processes to improve their performace i today s dyamic busiess-to-busiess (B2B) electroic commerce (e-commerce) eviromet. These busiess processes drive a compay s e-commerce iteractios with their customers, parters, distributors, ad suppliers; they ca also streamlie the compay s iteral busiess. Amog the target busiess processes for B2B itegratio ad automatio are desig ad specificatio, maufacturig ad testig, procuremet, sales, fulfillmet, customer service, ad plaig. To support these processes, B2B itegratio must support workflow processig, messagig ad routig, ad eterprise applicatio itegratio. The BEA WebLogic Collaborate product is a XML- ad Java-based e-commerce platform that eables you to implemet complex e-commerce systems o the Web. It helps you to quickly deploy e-commerce systems that lik existig back-ed applicatios, databases, customers, ad parters ito automatic ad flexible electroic collaboratios. WebLogic Collaborate is a software framework ad a set of services built o top of BEA WebLogic Server. It builds upo the WebLogic Server foudatio by addig a framework for messagig, coectivity, ad busiess protocols. It also itegrates the WebLogic Process Itegrator workflow capability for desigig ad maagig busiess processes. WebLogic Collaborate is implemeted etirely i Java ad leverages the J2EE stadard APIs. XML is used as a stadard format for documets exchaged by busiess parters. WebLogic Collaborate supports HTTP because the World Wide Web is the ubiquitous commuicatio medium for e-busiess. WebLogic Collaborate simplifies the implemetatio ad developmet of busiess-to-busiess tradig etworks, providig opportuities to itegrate iteral busiess processes with iter-eterprise busiess message exchage. A variety of deploymet models are supported. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

12 1 Overview The followig sectios provide a overview of the WebLogic Collaborate product: Feature Highlights for WebLogic Collaborate Meetig the Requiremets of Your E-Busiess Documetatio Roadmap for WebLogic Collaborate Feature Highlights for WebLogic Collaborate WebLogic Collaborate provides a ifrastructure platform for itegratig busiess processes that ca spa multiple corporate departmets, multiple eterprises across the Iteret, or both. The WebLogic Collaborate platform supports the buildig of missio-critical, scalable, real-world e-commerce collaboratios. Its features iclude: A ope, oproprietary architecture that leverages Java, J2EE, XML, HTTP, HTTPS, ad other idustry stadards to allow rapid system ad cross-platform itegratio, with low barriers to etry. Support for multiple busiess protocols, icludig XOCP, RosettaNet, ad cxml, thus providig the ability to exchage busiess documets i a secure maer with a variety of tradig parters, accommodatig the complexity of heterogeeous platforms, differet message structures, ad differet processes i various e-busiess eviromets. A variety of coectivity optios, allowig rapid coectivity amog may tradig parters for both automated ad semi-automated iteractios. Coectivity ad subsequet busiess collaboratios betwee tradig parter applicatios are possible etirely withi a eterprise or a compay, betwee tradig parter applicatios across compay firewalls ad over the Iteret, or i a combiatio of the two. Support for rapidly eablig tradig parters through o-cost lightweight cliet coectivity, usig browser-based iterfaces ad file-sharig mechaisms. Peer-to-peer ad mediated messagig models: peer-to-peer messagig allows direct messagig betwee parters, ad mediated messagig supports tasks such as message routig, message cotet filterig, ad value-added services. 1-2 Itroducig BEA WebLogic Collaborate 012 ServiceNow, Ic.'s Exhibit 1004

13 Feature Highlights for WebLogic Collaborate Tools ad processes for the effective maagemet of dyamic ad diverse tradig parter relatioships. Robust support for secure, high-volume busiess trasactio levels based o BEA s award-wiig WebLogic Server techology. BEA s prove, high-availability, 24x7-maaged applicatio server techology, with dyamic load-balacig, multithreadig, ad failover without processig iterruptio, has delivered idustry-leadig results i thousads of the world s most demadig applicatio eviromets. Reliable, role-based XML messagig that supports ehaced sed ad receive capabilities, icludig support for large messages. Coversatio coordiatio to maage the executio ad iteractio of tradig parter applicatios withi a coversatio ad to maage coversatio life cycles. Itegratio with BEA WebLogic Process Itegrator, the BEA workflow automatio tool, providig a flexible ad dyamic process-based approach to itegrate public ad private busiess processes. A SSL-based secure platform for coductig collaboratios that supports digital sigatures, digital receipts, orepudiatio, ad mutual (two-way) autheticatio usig digital certificates amog tradig parters. A data repository ad a set of desig ad cofiguratio tools to defie ad maage the metadata ad coversatio defiitios of WebLogic Collaborate. WebLogic Collaborate also offers a umber of features iherited from WebLogic Server, icludig: Ability to build custom portals by leveragig BEA WebLogic Persoalizatio Server compoets Portal backboe Cotrolled ad secure Web access to existig busiess data ad applicatios Support for existig applicatios based o CORBA, EJB, BEA Tuxedo, ad COM+ Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

14 1 Overview Meetig the Requiremets of Your E-Busiess WebLogic Collaborate maages eterprise-to-eterprise collaboratios, allowig heterogeeous eterprises to iteract i diverse busiess trasactios, which ca be complex ad log-ruig. The followig sectios describe requiremets for the framework to build such a B2B e-commerce eviromet, ad they explai how WebLogic Collaborate meets these requiremets: Coectig Tradig Parters Defiig Coversatios ad Roles Maagig Busiess Processes Supportig Busiess Protocols Esurig the Security of Trasactios Defiig Collaboratio Agreemets Maagig Coversatios Maagig Systems ad Applicatios Coectig Tradig Parters A tradig parter jois oe or more other tradig parters to form a e-commerce commuity with a specific busiess purpose. Busiess parters i a e-commerce commuity ca rage i size from large eterprises to small divisios withi a eterprise. Oe of the basic buildig blocks of B2B e-commerce is the tradig parter, specifically, the tradig parter applicatios that form the odes i system-to-system iteractios amog busiess parters. A e-commerce commuity formed by a group of tradig parters ca: Exist etirely withi a compay, spaig multiple corporate departmets (the busiess purpose for such a commuity might be ivetory maagemet, for example) 1-4 Itroducig BEA WebLogic Collaborate 014 ServiceNow, Ic.'s Exhibit 1004

15 Meetig the Requiremets of Your E-Busiess Spa multiple compaies across firewalls ad over the Iteret (the busiess purpose might be supply chai maagemet or multistep purchasig iteractios, for example) Iclude tradig parters both withi a compay ad i other compaies (oe or more of the tradig parters withi a compay commuicates with tradig parters i other compaies across the Iteret) A tradig parter must have a special idetity that defies where it fits with the busiess purpose of the e-commuity. I the WebLogic Collaborate eviromet, a tradig parter refers specifically to a etity that has a agreemet with aother etity to participate i a specific busiess exchage, or coversatio, i a specific role that is defied for the coversatio. To meet the requiremets of today s diverse B2B e-commerce activities, a eterprise must be able to use a variety of coectivity optios. Such flexibility is ecessary if a compay wats to participate i busiess trasactios with a large set of tradig parters with diverse processes ad protocols. To that ed, a WebLogic Collaborate tradig parter applicatio ca be cofigured to commuicate directly with other tradig parters i a peer-to-peer mode, or through a itermediary i the hub-ad-spoke mode, or both. These differet cofiguratio modes allow for either direct or mediated messagig betwee tradig parters. A itermediary i the message flow ca perform tasks such as routig ad filterig of messages, or it ca provide services to the tradig parters i the coversatio. For more details about modelig your WebLogic Collaborate cofiguratios, see Cofiguratio Models o page 2-1. Some busiess parters may have modest back-ed itegratio requiremets, or may eed to participate i collaborative processes without istallig the WebLogic Collaborate software. WebLogic Collaborate supports lightweight cliets to give small ad medium-size eterprises, or eterprises with little or o back-ed itegratio requiremets, a simple itegratio path through which they ca participate i e-busiess commuities. Such eterprises ca use a Web browser or a file-sharig cliet to commuicate with busiess parters who deploy WebLogic Collaborate as their tradig parter server. The istace of WebLogic Collaborate to which they coect acts as a server for their eeds. For details about settig up ad cofigurig tradig parter lightweight cliets, see Usig BEA WebLogic Collaborate Samples. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

16 1 Overview The followig figure illustrates a simple sceario i which WebLogic Collaborate is deployed i peer-to-peer relatioships betwee customers ad suppliers i a value chai. A customer or supplier tradig parter ca support multiple peer-to-peer busiess parterships with other tradig parters. Figure 1-1 Peer-to-Peer Messagig Amog Tradig Parters 1-6 Itroducig BEA WebLogic Collaborate 016 ServiceNow, Ic.'s Exhibit 1004

17 Meetig the Requiremets of Your E-Busiess The followig figure illustrates a sceario i which WebLogic Collaborate is deployed as a Net Market, providig itermediary services to several tradig parters. For example, this might be a auctio service, i which the Net Market is the auctio broker. Figure 1-2 Mediated Messagig i a Net Market Defiig Coversatios ad Roles Whe tradig parters joi other tradig parters to form a e-commuity with a specific busiess purpose, they participate i a coversatio. I WebLogic Collaborate, a coversatio: Is a series of busiess messages exchaged betwee tradig parters May be complex ad log-ruig, or short-lived Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

18 1 Overview Has a uique coversatio ame The busiess messages that ca be exchaged betwee participats i the coversatio are determied by the roles the tradig parters play i the coversatio. The roles ad other details of a coversatio are specified i a coversatio defiitio usig the WebLogic Collaborate Admiistratio Cosole. A coversatio is a active istace of a coversatio defiitio. A coversatio defiitio: Has a uique ame ad versio. Defies two or more roles to be used by tradig parters i a coversatio. The kids of messages tradig parters may sed ad receive are dictated by their roles i the coversatio. Is liked to a busiess protocol. Typically refereces a WebLogic Process Itegrator collaborative workflow template for each role. The message choreography for a coversatio is described i these collaborative workflow templates. Note: Usig BEA WebLogic Process Itegrator is the recommeded approach to composig busiess messages ad choreographig their exchage i coversatios. Alteratively, you ca write Java WebLogic Collaborate messagig applicatios that use the WebLogic Collaborate Messagig API or the cxml API. Whe you use such messagig applicatios, coversatio defiitios do ot referece a workflow template. For details about writig messagig applicatios usig the WebLogic Collaborate Messagig API ad the cxml API, see Programmig BEA WebLogic Collaborate Messagig Applicatios ad Implemetig cxml for BEA WebLogic Collaborate, respectively. Whe you use WebLogic Process Itegrator to compose busiess messages ad maage their exchage i a coversatio, each tradig parter who participates i the coversatio i a give role must implemet the collaborative workflow required for its role. Collaborative workflows ecapsulate the processes required to hadle the right busiess messages at the right time for a give tradig parter s role i a coversatio. For example, the followig figure represets a simple coversatio with two participatig roles, buyer ad supplier, ad hypothetical workflows for the two roles. 1-8 Itroducig BEA WebLogic Collaborate 018 ServiceNow, Ic.'s Exhibit 1004

19 Meetig the Requiremets of Your E-Busiess Figure 1-3 Collaborative Workflows i a Query Price ad Availability Coversatio I this figure, ote the followig: The busiess messages Two busiess messages, PriceAdAvailabilityQuote ad PriceAdAvailabilityRespose, are exchaged betwee tradig parter applicatios. The buyer ad supplier roles The implicatio of beig i a role i a give coversatio is that you sed ad receive oly the busiess messages defied for your role. For example, the buyer: l Starts the coversatio l l Seds the busiess message PriceAdAvailabilityQuote Receives the busiess message PriceAdAvailabilityRespose ad processes it Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

20 1 Overview By cotrast, the supplier: l Receives ad processes the busiess message PriceAdAvailabilityQuote l Seds the busiess message PriceAdAvailabilityRespose The collaborative workflows Each role has its ow set of tasks required to sed ad receive the right busiess messages at the right times. I the WebLogic Collaborate eviromet, a tradig parter implemets a collaborative workflow for a particular role i a coversatio. Maagig Busiess Processes Usig BEA WebLogic Process Itegrator is the recommeded approach to composig busiess messages ad choreographig their exchage i coversatios. Alteratively, you ca write Java WebLogic Collaborate messagig applicatios that use the WebLogic Collaborate Messagig API or the cxml API. This sectio discusses the approaches to developig ad maagig messagig applicatios i WebLogic Collaborate. Workflows are busiess processes. Busiess processes ca spa multiple applicatios, corporate departmets, ad busiess parters (tradig parters) behid a firewall ad over the Iteret. A eterprise s busiess processes ca be divided ito two broad categories: public ad private. Public ad Private Busiess Processes Busiess processes ca be desiged as public or private processes. Public processes are iterface processes. Their defiitios ad desigs are kow, uderstood, ad agreed upo by the orgaizatios usig them, ad may be customized or stadardized across a idustry or idustry segmet, as i the case of RosettaNet Parter Iterface Processes (PIPs). They are part of a formal cotract betwee tradig parters that specifies the cotet ad sematics of message iterchages. These processes ca be implemeted i differet ways by differet tradig parters. I the cotext of WebLogic Collaborate, whe collaborative workflows are iteded to be reused i multiple coversatios with differet busiess parters, they should be desiged as public processes Itroducig BEA WebLogic Collaborate 020 ServiceNow, Ic.'s Exhibit 1004

21 Meetig the Requiremets of Your E-Busiess Participats i a coversatio ca also implemet private, ocollaborative workflows, which ca itegrate their back-ed processig. Private processes are the busiess processes coducted withi a orgaizatio. Their defiitios ad desigs are specific to that orgaizatio ad are ot visible outside it. Withi tradig parter eterprises, private processes iterface with public processes ad with back-ed busiess systems. I the cotext of public processes, private processes ca be thought of as subworkflows or subprocesses that implemet tasks that are part of the public workflow. For example, a tradig parter may implemet a private workflow that works i cojuctio with a collaborative workflow ad that implemets the processes that occur locally to a tradig parter, but that are ot ecessarily dictated by the coversatio defiitio. Usig BEA WebLogic Process Itegrator WebLogic Process Itegrator is a workflow automatio tool. It automates ad itegrates a busiess process by maagig the sequece of activities i the process ad ivokig the appropriate resources required by the activities or steps i the process. The compoets of WebLogic Process Itegrator iclude a workflow desig tool (the WebLogic Process Itegrator Studio), a GUI moitorig tool (the WebLogic Process Itegrator Worklist), ad the Process Egie that moitors ad cotrols workflows. I the WebLogic Collaborate eviromet, a WebLogic Process Itegrator collaborative workflow is a workflow that implemets a role i a coversatio defiitio for a tradig parter. The message choreography for a WebLogic Collaborate coversatio is defied by collaborative workflow templates: oe template is defied for each role i the coversatio defiitio, as described i Defiig Coversatios ad Roles o page 1-7. WebLogic Collaborate provides a plug-i to the WebLogic Process Itegrator Studio tool that exteds the already powerful busiess process desig tool with fuctioality that allows you to create collaborative workflows. Usig the plug-i fuctioality, you ca compose ad extract the cotets of busiess messages, specify the message delivery Quality of Service (QoS), hadle message tokes, ad so o. For details about how to use WebLogic Process Itegrator, ad how it is itegrated i the WebLogic Collaborate eviromet, see Creatig Workflows for BEA WebLogic Collaborate. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

22 1 Overview I summary, busiess processes i the WebLogic Collaborate eviromet are defied ad maaged usig WebLogic Process Itegrator, which provides the followig: A visual desig tool for creatig workflows Fuctioality i the desig tool for associatig the workflows with a WebLogic Collaborate coversatio defiitio A ru-time process egie for executig workflows Itegratio with back-ed applicatios via the use of workflow actios Worklist: A utility for ruig workflows iteractively Process moitorig capabilities Usig the WebLogic Collaborate Messagig API Usig the cxml API As a alterative to usig WebLogic Process Itegrator, a tradig parter ca implemet Java-based XOCP messagig applicatios based o the WebLogic Collaborate Messagig API. This API was available as the C-Eabler API i WebLogic Collaborate Release 1.0. You ca use WebLogic Collaborate Messagig API with WebLogic Collaborate Release 2.0. For details about migratig your C-Eabler API applicatios from WebLogic Collaborate Release 1.0 to Release 2.0 ad for iformatio about usig the WebLogic Collaborate Messagig API with Release 2.0, you should see Programmig BEA WebLogic Collaborate Messagig Applicatios ad Migratig BEA WebLogic Collaborate to Release 2.0. WebLogic Collaborate supports multiple busiess protocols for sedig ad receivig messages (see Supportig Busiess Protocols o page 1-13). For the cxml (Commerce extesible Markup Laguage) protocol, WebLogic Collaborate provides a cxml API which provides classes that allow the sedig ad receivig of cxml messages, the creatio ad maipulatio of cxml documets, the mappig of a collaboratio agreemet to a message, ad so o. For details, see Implemetig cxml for BEA WebLogic Collaborate Itroducig BEA WebLogic Collaborate 022 ServiceNow, Ic.'s Exhibit 1004

23 Meetig the Requiremets of Your E-Busiess Supportig Busiess Protocols A busiess message is the basic uit of commuicatio amog tradig parters ad is exchaged as part of a coversatio. A busiess message cotais oe or more XML busiess documets, oe or more attachmets, or a combiatio of both. The cotets ad format of a busiess message deped o the busiess protocol chose for the coversatio (see Busiess Messages o page 1-17 for details). A busiess protocol is associated with a busiess process, which govers the exchage of busiess iformatio betwee tradig parters. It specifies the structure of busiess messages, how to process the messages, ad how to route them to the appropriate recipiets. A busiess protocol may also specify characteristics of messages related to persistece ad reliability. You bid a busiess protocol to a coversatio defiitio ad a delivery chael for a tradig parter. A busiess protocol is boud idirectly to a collaboratio agreemet through both the associated coversatio defiitio ad associated tradig parter's delivery chael (see Defiig Collaboratio Agreemets o page 1-23). WebLogic Collaborate supports the followig busiess protocols: XOCP (extesible Ope Collaboratio Protocol) RosettaNet l RosettaNet Implemetatio Framework (RNIF) 1.1 l RosettaNet Implemetatio Framework (RNIF) 2.0 cxml (Commerce extesible Markup Laguage) By providig the ability to sed ad receive messages accordig to these stadard protocols, WebLogic Collaborate gives a eterprise a great deal of flexibility ad opportuity i orgaizig its B2B e-commerce by reducig the eed for tradig parters to stadardize o ay sigle protocol. You ca also customize ad exted the supported busiess protocols beyod their out-of-the-box fuctioality by usig WebLogic Collaborate s logic plug-is. Logic plug-is are Java classes that ca itercept ad process busiess messages at ru time. WebLogic Collaborate provides system logic plug-is, which you ca supplemet by writig custom logic plug-is. The system logic plug-is for XOCP iclude XOCP Router ad XOCP Filter. They are directly ivolved i the processig of message recipiets based o Xpath expressios i the repository. Custom logic plug-is ca Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

24 1 Overview XOCP perform a wide rage of services that are urelated to routig or filterig, as well as routig ad filterig operatios. For example, a custom logic plug-i might be used, for billig purposes, to track the umber of messages set from each tradig parter. For details about admiisterig both system ad custom logic plug-is, see Admiisterig BEA WebLogic Collaborate ad BEA WebLogic Collaborate Admiistratio Cosole Olie Help. If you wat to write custom logic plug-is, see Programmig BEA WebLogic Collaborate Logic Plug-Is. The extesible Ope Collaboratio Protocol (XOCP) is a BEA-specific busiess protocol. The XOCP busiess protocol supports the stadards-based ebxml Trasport, Routig, ad Packagig (TRP) protocol. XOCP provides the followig messagig characteristics: Message multicastig Message multicastig is the ability of the XOCP messagig service to multicast a message from oe tradig parter to may tradig parters, withi the costraits of a existig coversatio. For example, cosider the followig sceario: WebLogic Collaborate is deployed i a hub-ad-spoke cofiguratio, where 10 tradig parters, cofigured as spokes, commuicate via a itermediary (that is, through a tradig parter cofigured as a hub). The busiess purpose of this e-commuity is participatio i a Query Price ad Availability coversatio that has two roles: buyer ad supplier. Oe tradig parter is i the role of the buyer, ad ie are suppliers. The buyer tradig parter ca, through the itermediary, multicast the Query Price ad Availability message to all the tradig parters who have agreemets to be suppliers i a Query Price ad Availability coversatio with the itermediary. Message payload defiitio idepedece XOCP provides the flexibility for you to specify both the vocabulary ad busiess processes for your messages for a give coversatio so that they are a exact fit for your busiess requiremets. Coversatio life cycle maagemet E-commerce coversatios ca be complex ad log-lived. XOCP is desiged to maage log-lived coversatios. Whe a coversatio termiates, all tradig 1-14 Itroducig BEA WebLogic Collaborate 024 ServiceNow, Ic.'s Exhibit 1004

25 Meetig the Requiremets of Your E-Busiess parters who are participatig i that coversatio receive a ed-of-coversatio message. Qualities of Service (QoS) capabilities The WebLogic Collaborate software offers a variety of settigs related to Quality of Service that allow you to set ad cotrol the characteristics of XOCP messages beig set, such as: l Note: l l l Message durability Specifies whether a durable message store is to be used to guaratee the delivery of messages i the case of etwork, machie, or software failures. Message durability is cotrolled at the message level by this QoS settig oly whe you deploy WebLogic Collaborate i opersistet mode. Whe you deploy WebLogic Collaborate i persistet mode, all state records, icludig messages, are read from ad writte to a persistet storage database ad are ot cached i memory. Therefore, all messages are persisted. I other words, whe WebLogic Collaborate is deployed i persistet mode, message durability is cotrolled by the database-based state maagemet mode rather tha by the message durability QoS settig. For details about persistet ad opersistet modes, see "Cofigurig Persistece ad Recovery" i Admiisterig BEA WebLogic Collaborate. Timeout Specifies how log a tradig parter applicatio waits before termiatig all processig related to the busiess message. Retry attempts Cotrols how may times a message should be reset i the presece of specific situatios, such as timeouts, etwork failures, ad so o. Correlatio ID Sets a additioal busiess message property that ca be used to correlate messages i a coversatio. WebLogic Collaborate allows you to establish Quality of Service settigs o a per-coversatio ad a per-message basis. RosettaNet WebLogic Collaborate supports sedig ad receivig RosettaNet messages accordig to both RNIF 1.1 ad RNIF 2.0. It also supports iteroperability with other RosettaNet parters. I additio, a WebLogic Collaborate plug-i to WebLogic Process Itegrator exteds the WebLogic Process Itegrator fuctioality with features that allow WebLogic Process Itegrator workflows to participate i RosettaNet Parter Iterface Processes (PIPs). Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

26 1 Overview RosettaNet is a self-fuded, oprofit cosortium of major compaies (from the iformatio techology, electroic compoet, ad semicoductor maufacturig idustries) workig to create ad implemet idustry-wide, ope e-busiess process stadards. These stadards form a commo e-busiess laguage, aligig processes betwee supply chai parters o a global basis. (For complete details about the RosettaNet orgaizatio, see To support its missio, RosettaNet provides specificatios for the RosettaNet Implemetatio Framework (RNIF), the Parter Iterface Processes (PIPs), ad busiess ad techical dictioaries. RosettaNet ( defies its Parter Iterface Processes (PIPs) as follows: RosettaNet PIPs are specialized system-to-system XML-based dialogs that defie busiess processes betwee tradig parters. Each PIP specificatio icludes a busiess documet with the vocabulary, ad a busiess process with the choreography of the message dialog. PIPs fit ito seve clusters, or groups of core busiess processes, that represet the backboe of the supply chai etwork. Each cluster is further subdivided ito segmets, which are cross-eterprise processes ivolvig more tha oe type of supply chai parter. Withi each segmet are idividual PIPs. PIPs cotai oe or more Activities, ad Activities, i tur, specify Actios. PIPs apply to the followig core processes: Admiistratio Parter, Product, ad Service Review Product Itroductio Order Maagemet Ivetory Maagemet Marketig Iformatio Maagemet Service ad Support Maufacturig The RNIF provides exchage protocols for implemetatio of the PIPs. The RNIF specifies iformatio exchage betwee tradig parter servers usig XML, coverig trasport, routig ad packagig, security, sigals, ad tradig parter agreemets Itroducig BEA WebLogic Collaborate 026 ServiceNow, Ic.'s Exhibit 1004

27 Meetig the Requiremets of Your E-Busiess For details about RosettaNet support i WebLogic Collaborate, see Implemetig RosettaNet for BEA WebLogic Collaborate. cxml Busiess Messages WebLogic Collaborate provides a cxml API so that tradig parter servers ruig WebLogic Collaborate ca sed ad receive cxml messages accordig to the cxml stadard. The cxml API provides classes that allow the sedig ad receivig of cxml messages, the creatio ad maipulatio of cxml documets, the mappig of a collaboratio agreemet to a message, ad so o. The Web site defies cxml as follows: cxml is a streamlied protocol iteded for cosistet commuicatio of busiess documets betwee procuremet applicatios, e-commerce hubs, ad suppliers. cxml trasactios cosist of documets that are simple text files with well defied format ad cotet. Most types of cxml documets are aalogous to hardcopy documets traditioally used i busiess. The mai types of cxml documets are Catalogs, Puchouts, ad Purchase Orders. cxml defies a commo DTD for busiess messages. The cxml protocol is desiged to lik buyers ad suppliers i scearios where buyers browse catalogs ad submit purchase orders to suppliers. A buyer ca browse a supplier s catalog directly; alteratively, a Ariba exchage (Ariba Commerce Server Network) mediates messages betwee buyer ad supplier. For details about cxml support i WebLogic Collaborate, see Implemetig cxml for BEA WebLogic Collaborate. A busiess message is the basic uit of commuicatio amog tradig parters. It is exchaged as part of a coversatio. A busiess message cotais oe or more XML busiess documets, oe or more attachmets, or a combiatio of both. The cotets ad format of a busiess message deped o the busiess protocol chose for the coversatio. I WebLogic Collaborate, the primary method used to prepare a busiess message to be set to oe or more tradig parters is the WebLogic Process Itegrator collaborative workflow. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

28 1 Overview XOCP Busiess Messages This sectio describes the basic structure of busiess messages exchaged i the WebLogic Collaborate eviromet. For details about usig the WebLogic Process Itegrator Studio to compose ad maipulate busiess messages, see Creatig Workflows for BEA WebLogic Collaborate. The XOCP busiess protocol supports the ope stadard ebxml Trasport, Routig, ad Packagig (TRP) protocol (see for the ebxml Message Service Specificatio ). The ebxml TRP protocol defies a wire format ad protocol for a message service to support XML-based electroic messages. The followig figure represets the structure of a busiess message exchaged i a coversatio based o the XOCP protocol. Figure 1-4 XOCP Busiess Message Note the followig parts: Message evelope Logical cotaier for the XOCP busiess message that is added while the busiess message is i trasit through the WebLogic Collaborate messagig service software. The message evelope typically cotais data related to the seder of the message ad the recipiets, ad ca cotai other metadata. The evelope is visible i the messagig service oly (see Messagig Service o page 1-27). The evelope is ot part of the trasport protocol Itroducig BEA WebLogic Collaborate 028 ServiceNow, Ic.'s Exhibit 1004

29 Meetig the Requiremets of Your E-Busiess Message headers that iclude the followig: l l l Trasport, Security, ad Qualities of Service (QoS) headers Cotai the data required to deliver a message, such as seder ad recipiet idetities, cotet legth ad type, ad status code. Coversatio header Cotais coversatio iformatio, seder iformatio, message ID, creatio timestamp, ad other data. Message attributes ca be set by the origiatig tradig parter, or by logic plug-is, such as the XOCP router or XOCP filter (see Programmig BEA WebLogic Collaborate Logic Plug-Is). Routig header Cotais a expressio that idetifies a group of recipiets for a multicast message. Payload Icludes oe or more busiess documets, zero or more attachmets, or a combiatio of both. A busiess documet is a XML documet, ad a attachmet ca be ay biary (oxml) part of the message. I WebLogic Collaborate, the primary method used to prepare a busiess message payload to be set to oe or more tradig parters is the WebLogic Process Itegrator collaborative workflow. That workflow icludes a process that adds XOCP headers to a XOCP busiess message. RosettaNet Busiess Messages WebLogic Collaborate supports sedig ad receivig RosettaNet messages accordig to the RosettaNet Implemetatio Framework, versios 1.1 ad 2.0. A busiess message exchaged i a coversatio based o the RosettaNet 1.1 protocol is called a RosettaNet Object (RNO). The etity exchaged i a coversatio based o the RosettaNet 2.0 protocol is called a RosettaNet Busiess Message (RBM). A WebLogic Collaborate plug-i to WebLogic Process Itegrator exteds the WebLogic Process Itegrator fuctioality with features that simplify the developmet of RosettaNet busiess messages ad Parter Iterface Protocols (PIPs). Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

30 1 Overview The followig figure represets the structure of a RosettaNet Object exchaged i a coversatio based o the RosettaNet 1.1 busiess protocol. Figure 1-5 RosettaNet Busiess Message Note the followig parts: Headers A RosettaNet Object always cotais a Preamble Header ad a Service Header. Service Cotet The payload part of the message. The Service Cotet cotais either a actio or a sigal message. RosettaNet Versio, Digital Sigature, Cotet Legth, ad Digital Sigature Legth These parts of the message are i biary format. The RosettaNet Implemetatio Framework 2.0 itroduced the followig otable differeces i the compositio of a RosettaNet Busiess Message (RBM): Attachmets are supported for RosettaNet Implemetatio Framework 2.0 as a optioal part of the RosettaNet message. Attachmets are ot file type-specific, ad may cotai biary data. Oe or more attachmets may be icluded i the payload part of the message. The Service Header ad Cotet i RosettaNet Busiess Messages ca be ecrypted. Usig the WebLogic Collaborate Admiistratio Cosole, you ca 1-20 Itroducig BEA WebLogic Collaborate 030 ServiceNow, Ic.'s Exhibit 1004

31 Meetig the Requiremets of Your E-Busiess cofigure the system to ecrypt the Service Cotet, Service Header, ad ay attachmets whe a message is set. I additio to the Service ad Preamble Headers, the RosettaNet Implemetatio Framework 2.0 defies a Delivery Header. cxml Busiess Messages WebLogic Collaborate supports sedig ad receivig cxml messages. cxml request ad respose trasactios belog to oe of four geeral types: Profile, PuchOut, Order, or Subscriptio trasactios. The followig figure represets the structure of a XML request busiess message exchaged i a coversatio based o the cxml busiess protocol. Figure 1-6 cxml Busiess Message Note the followig parts: Header cotaiig From, To, ad Seder fields: l l l From Cotais iformatio about the origiator of the request (the buyer). To Cotais iformatio about the destiatio of the request (the supplier). Seder Cotais iformatio about the etity that is relayig the request. Typically, this etity is a Ariba exchage (Ariba Commerce Server Network), which mediates messages betwee buyer ad supplier. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

32 1 Overview Request cotaiig a Request Type A Request Type field cotais iformatio about the type of request cotaied i this message. For example, a request type may be PuchOutSetupRequest. Associated with each request type is oe if three operatio etities: create, edit, or ispect. Esurig the Security of Trasactios Reliable ad secure commuicatios are a crucial elemet i the B2B e-commerce eviromet. This is true whether e-busiess collaboratios are betwee parters withi a orgaizatio or betwee parters that spa multiple orgaizatios across firewalls ad over the Iteret. WebLogic Collaborate security is built o top of the security features provided by WebLogic Server; it provides advaced security support ad services. WebLogic Collaborate provides support for the followig security features: A SSL-based secure platform for B2B e-commerce coversatios Mutual, two-way autheticatio usig digital certificates WebLogic Collaborate provides support for certificate verificatio to autheticate the idetities of tradig parters. Usig the WebLogic Collaborate Admiistratio Cosole, admiistrators ca cofigure a certificate verificatio provider implemetatio to verify a digital certificate submitted by a tradig parter. Digital receipts A digital sigature ca be attached to a busiess documet by the parties i a busiess collaboratio. WebLogic Collaborate supports digital sigatures at the applicatio level; a trusted third party creates digital receipts. Norepudiatio Norepudiatio of origi ad orepudiatio of receipt is a legal requiremet for critical busiess messages. Norepudiatio of origi liks the message received ad the seder of the message, ad orepudiatio of receipt liks the message processed ad the recipiet of the message. To support orepudiatio, WebLogic Collaborate provides the followig services: 1-22 Itroducig BEA WebLogic Collaborate 032 ServiceNow, Ic.'s Exhibit 1004

33 Meetig the Requiremets of Your E-Busiess l l l Digital sigature Used to digitally sig a busiess documet before it is set to the recipiet. Secure timestamp Used to sequece the occurrece of evets i the busiess trasactio. Audit log Used to store digitally siged busiess messages with a secure timestamp. Audit loggig is ecessary for orepudiatio. Data ecryptio WebLogic Collaborate provides a data ecryptio service for busiess protocols that require this type of support. For a comprehesive discussio about WebLogic Collaborate security, ad details about cofigurig security services, see Usig BEA WebLogic Collaborate Security. Defiig Collaboratio Agreemets A critical compoet of B2B e-commerce is the establishmet ad maagemet of agreemets amog busiess parters. I the WebLogic Collaborate eviromet, these agreemets take the form of collaboratio agreemets betwee tradig parters. Usig collaboratio agreemets, tradig parters agree o the iteractios betwee them, i particular, the coversatios i which they participate, ad each tradig parter s message sedig ad receivig characteristics. Parties i Collaboratio Agreemets A coversatio defiitio defies two or more roles to be used by tradig parters i a coversatio. A party i a collaboratio agreemet bids a role from the coversatio defiitio to a tradig parter. For example, cosider a collaboratio agreemet based o the Query Price ad Availability coversatio described i Defiig Coversatios ad Roles o page 1-7. There are two parties i this collaboratio agreemet: oe buyer ad oe supplier (see Figure 1-7). Delivery Chaels i Collaboratio Agreemets A tradig parter s message sedig ad receivig characteristics are ecapsulated i a WebLogic Collaborate delivery chael. There is geerally oe delivery chael per tradig parter for each busiess protocol supported by the tradig parter. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

34 1 Overview Note: Tradig parters usig the XOCP busiess protocol require two delivery chaels: oe hub ad oe spoke. For details about cofigurig delivery chaels i hub-ad-spoke mode, see Hub-ad-Spoke Cofiguratio o page 2-3. A applicatio for a tradig parter commuicates, through its delivery chael, with aother tradig parter s delivery chael. The iteractios ca be direct, that is, peer-to-peer betwee tradig parters, or they ca be idirect, that is, they ca be coducted through a itermediary (routig proxy) delivery chael. For details about peer-to-peer ad hub-ad-spoke cofiguratios for WebLogic Collaborate compoets, see Cofiguratio Models o page 2-1. You cofigure ad moitor the compoets of delivery chaels usig the WebLogic Collaborate Admiistratio Cosole. A delivery chael icludes the followig iformatio: Busiess protocol bidig (XOCP, cxml, RosettaNet1.1, or RosettaNet2.0) Trasport protocol (HTTP) ad the target Uiform Resource Idetifier (URI) Security optios (digital sigatures, digital certificates, ad orepudiatio) Reliable messagig optios (timeout ad retries) Message ecodig (base64) Collaboratio Agreemets i Peer-to-Peer Cofiguratios Take the Query Price ad Availability coversatio described i Defiig Coversatios ad Roles o page 1-7 as a example. The delivery chaels for the participatig tradig parters isolate the commuicatio details betwee them. The followig figure illustrates the compoets of a collaboratio agreemet betwee two tradig parters participatig directly with each other i a busiess coversatio. The tradig parters are cofigured i a peer-to-peer cofiguratio. I this case, the target tradig parter for busiess messages is the other tradig parter i the collaboratio agreemet Itroducig BEA WebLogic Collaborate 034 ServiceNow, Ic.'s Exhibit 1004

35 Meetig the Requiremets of Your E-Busiess Figure 1-7 Compoets of a Collaboratio Agreemet The precedig figure illustrates how each tradig parter s delivery chael ad the coversatio defiitio (which defies the roles i the coversatio) relate to the collaboratio agreemet betwee the tradig parters. Collaboratio Agreemets i Hub-ad-Spoke Cofiguratios Whe WebLogic Collaborate is cofigured so that tradig parters participate i coversatios through a itermediary (or routig proxy), collaboratio agreemets are created betwee each tradig parter ad the itermediary. I this case, tradig parters idetify the itermediary tradig parter (that is, the routig proxy delivery chael) as the target for their busiess messages. If, for example, the Query Price ad Availability coversatio betwee Tradig Parter A ad Tradig Parter B goes through a itermediary tradig parter (Itermediary A), two collaboratio agreemets are created. The followig figure illustrates the collaboratio agreemets created betwee Tradig Parter A, Itermediary A, ad Tradig Parter B for a Query Price ad Availability coversatio i which Itermediary A is a itermediary tradig parter. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

36 1 Overview Figure 1-8 Collaboratio Agreemets Betwee Tradig Parters i a Hub-ad-Spoke Cofiguratio Note the followig i the precedig figure: The delivery chael for the tradig parter (Itermediary A) i the role of routig proxy has collaboratio agreemets with both the supplier ad buyer tradig parters. I the collaboratio agreemet amed QueryPrice_101, Tradig Parter A is the buyer ad Itermediary A is the supplier (i effect, the proxy supplier). I the collaboratio agreemet amed QueryPrice_202, Tradig Parter B is the supplier ad Itermediary A is the buyer (i effect, the proxy buyer). Maagig Coversatios Critical to maagig successful relatioships betwee tradig parters is the ability to provide robust services to esure the itegrity of busiess messages while they are beig exchaged i various types of tradig parter collaboratios. WebLogic Collaborate provides a messagig service ad a coversatio coordiatio service, as described i the followig sectios Itroducig BEA WebLogic Collaborate 036 ServiceNow, Ic.'s Exhibit 1004

37 Meetig the Requiremets of Your E-Busiess Messagig Service WebLogic Collaborate provides a flexible messagig service to facilitate iformatio trasfer betwee tradig parters. The messagig compoet relies o decoupled, deferred sychroous messagig capabilities to allow commuicatio flexibility. The WebLogic Collaborate messagig service offers the followig features ad characteristics: Support, i ative mode, for multiple XML-based busiess protocols, icludig XOCP, RosettaNet 1.1, RosettaNet 2.0, ad cxml Support for blockig ad oblockig message delivery Quality of Service (QoS) capabilities for XOCP-based messages, icludig the ability to establish durability, cofirm receipt, track messages, message timeout, retry, ad other settigs for messages exchaged amog tradig parters Routig ad filterig capabilities, cotrollig which tradig parters receive messages Accommodatio of the isertio of user-writte code to customize the hadlig of icomig or outgoig messages or to perform messagig-related operatios, thus extedig the fuctioality of stadard busiess protocols Coversatio Coordiatio Service Busiess coversatios ca be complex ad log ruig some coversatios may last several days. Coversatios always have life cycles, which are explicitly demarcated by a begiig ad a ed. The WebLogic Collaborate software provides a coversatio coordiatio service. The WebLogic Collaborate coversatio coordiatio service is busiess protocol-specific. Busiess protocols defie their coversatio termiatio protocols i differet ways. I the case of XOCP-based coversatios, the coversatio coordiator does the followig: Creates the coversatio o behalf of the tradig parter that iitiates the coversatio Elists ew tradig parters i the coversatio Removes tradig parters from the coversatio if they submit requests to leave the coversatio Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

38 1 Overview Seds coversatio termiatio otices to all coversatio participats whe the coversatio is termiated Allows moitorig of the active coversatios for a tradig parter Maagig Systems ad Applicatios Except for workflows, WebLogic Collaborate system compoets are cofigured ad maaged primarily through the WebLogic Collaborate Admiistratio Cosole, which works together with a repository service. Busiess process (workflow) maagemet is achieved through tight itegratio of WebLogic Collaborate with WebLogic Process Itegrator. The WebLogic Process Itegrator software provides busiess parters with a workflow process egie that cotrols the executio of local busiess processes ad maages the itegratio of back-ed eterprise applicatios with busiess processes. See Maagig Busiess Processes o page 1-10 for more details. This sectio describes the followig WebLogic Collaborate maagemet services: Repository Service Admiistratio Services l WebLogic Collaborate Admiistratio Cosole l Bulk Loader l Java Maagemet Extesios Maagemet Beas Loggig Service 1-28 Itroducig BEA WebLogic Collaborate 038 ServiceNow, Ic.'s Exhibit 1004

39 Meetig the Requiremets of Your E-Busiess The followig figure represets the WebLogic Collaborate services described here ad i Maagig Coversatios o page Figure 1-9 WebLogic Collaborate Services Repository Service The repository service stores data ito the repository. This data is required by tradig parters to egage i busiess-to-busiess collaboratios, ad icludes: Tradig parter-specific iformatio Coversatio defiitios Collaboratio agreemets Busiess protocol defiitios Documet defiitio (DTD) ames Documet ad cofiguratio iformatio Data used for message routig ad filterig operatios Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

40 1 Overview I additio, the repository: Is accessible through the WebLogic Collaborate Admiistratio Cosole for system admiistratio, creatio of collaboratio agreemets by busiess developers, ad moitorig of tradig parters, coversatios, collaboratio agreemets, ad so o Supports the import ad export of data usig the WebLogic Collaborate Admiistratio Cosole ad a Bulk Loader utility Supports Oracle, Microsoft SQL Server, ad Cloudscape as primary data stores Admiistratio Services For details about the repository ad the Bulk Loader, see Workig with the Repository ad Workig with the Bulk Loader i Admiisterig BEA WebLogic Collaborate. The WebLogic Collaborate admiistratio services support multiple system maagemet fuctios, icludig cofigurig, admiisterig, ad moitorig tradig parters, coversatios, collaboratio agreemets, ad more. Through these services, a WebLogic Collaborate admiistrator ca create, cofigure, ad maage the compoets of the WebLogic Collaborate system. Busiess developers ca set up collaboratio agreemets ad moitor system status. I additio, busiess parters ca use the admiistratio services to start ad ed tradig parter sessios, leave or ed coversatios, ad eable, disable, start, or shut dow delivery chaels. WebLogic Collaborate Admiistratio Cosole Primary access to the admiistratio services i WebLogic Collaborate is through the Web-based WebLogic Collaborate Admiistratio Cosole. All cofiguratio iformatio is stored i the WebLogic Collaborate repository, which is supported by a database maagemet system. The compoets of the WebLogic Collaborate system that you ca cofigure ad moitor iclude the followig: Tradig parters Coversatios Collaboratio agreemets 1-30 Itroducig BEA WebLogic Collaborate 040 ServiceNow, Ic.'s Exhibit 1004

41 Meetig the Requiremets of Your E-Busiess Busiess protocols Logic plug-is To facilitate data ad busiess process exchage amog tradig parters, the import ad export fuctios of the WebLogic Collaborate Admiistratio Cosole allow you to export repository data to a XML file, ad import data from a XML file to your WebLogic Collaborate repository. You ca select the scope of the exported data from the repository such that the XML file you create cotais either all the data i the repository, or oly data related to oe of the followig etities: tradig parters, coversatio defiitios, collaboratio agreemets, busiess protocol defiitios, or logic plug-is. For complete details about usig the WebLogic Collaborate Admiistratio Cosole, see Admiisterig BEA WebLogic Collaborate ad BEA WebLogic Collaborate Admiistratio Cosole Olie Help. Bulk Loader I additio to usig the WebLogic Collaborate Admiistratio Cosole to export ad import data from ad to your WebLogic Collaborate repository, you ca use the Bulk Loader facility (from the commad lie) to export ad import repository data. Like the import ad export fuctios of the WebLogic Collaborate Admiistratio Cosole, the Bulk Loader utility supports export of either all the data i the repository or oly a subset of the data to the XML file. For details about the Bulk Loader, see Usig the Bulk Loader i Admiisterig BEA WebLogic Collaborate. Java Maagemet Extesios Maagemet Beas For moitorig oly, WebLogic Collaborate supports user-writte applicatios that use Java Maagemet Extesios (JMX) Maagemet Beas (MBeas) to view data ad statistics maitaied by the admiistratio services. Tradig parters ca use the JMX MBeas through a MBea server (a repository for MBeas), which is icluded i the admiistratio services package, to sed ad receive messages to ad from the admiistratio services. For details about programmig maagemet applicatios, see Programmig BEA WebLogic Collaborate Maagemet Applicatios. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

42 1 Overview Loggig Service WebLogic Collaborate provides a loggig capability for error ad iformatio messages. All WebLogic Collaborate log messages are time-stamped, ad ca be set to the WebLogic Server log, or to a separate log file. For details, see Writig Messages to the BEA WebLogic Collaborate Log. Documetatio Roadmap for WebLogic Collaborate The followig table shows where, i WebLogic Collaborate documetatio, you ca fid more detailed iformatio about various features of your WebLogic Collaborate software. To lear more about... Cosult... Istallatio Istallig BEA WebLogic Collaborate BEA WebLogic Collaborate Release Notes Migratig from WebLogic Collaborate 1.0 to WebLogic Collaborate 2.0 WebLogic Collaborate termiology Migratig BEA WebLogic Collaborate to Release 2.0 BEA WebLogic Collaborate Glossary Admiistratio (cofiguratio ad moitorig) Admiisterig BEA WebLogic Collaborate BEA WebLogic Collaborate Admiistratio Cosole Olie Help Usig BEA WebLogic Collaborate Security Admiistratio (settig up tradig parter lightweight cliets) Tradig Parter Lightweight Cliet Sample i Usig BEA WebLogic Collaborate Samples 1-32 Itroducig BEA WebLogic Collaborate 042 ServiceNow, Ic.'s Exhibit 1004

43 Documetatio Roadmap for WebLogic Collaborate To lear more about... Cosult... Busiess processes ad collaborative workflows Creatig Workflows for BEA WebLogic Collaborate Implemetig RosettaNet for BEA WebLogic Collaborate Implemetig cxml for BEA WebLogic Collaborate Security Usig BEA WebLogic Collaborate Security Busiess protocol support (XOCP, RosettaNet, cxml) Creatig Workflows for BEA WebLogic Collaborate Implemetig RosettaNet for BEA WebLogic Collaborate Implemetig cxml for BEA WebLogic Collaborate Programmig BEA WebLogic Collaborate Logic Plug-Is Sample applicatios shipped with WebLogic Collaborate Browser ad file-sharig cliets Programmer referece ad APIs Usig BEA WebLogic Collaborate Samples Tradig Parter Lightweight Cliet Sample i Usig BEA WebLogic Collaborate Samples BEA WebLogic Collaborate Javadoc WebLogic Collaborate cofiguratio models ad architecture Chapter 2, Gettig Started Usig WebLogic Collaborate, i this documet Cofiguratio Tasks i Admiisterig BEA WebLogic Collaborate Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

44 1 Overview To lear more about... Cosult... BEA WebLogic Process Itegrator Message routig ad filterig usig logic plug-is The BEA WebLogic Process Itegrator documet set is available at the followig URL: processitegrator/idex.htm This set icludes the followig documets: Usig the BEA WebLogic Process Itegrator Studio explais how to use the Studio to desig workflows. Usig the BEA WebLogic Process Itegrator WorkList explais how to use the Worklist to view, perform, ad work with tasks that are curretly associated with the roles to which you are subscribed. Learig to Use BEA WebLogic Process Itegrator provides a tutorial o usig the busiess process maagemet software. Programmig BEA WebLogic Collaborate Logic Plug-Is Advaced programmig optios Programmig BEA WebLogic Collaborate Maagemet Applicatios Programmig BEA WebLogic Collaborate Logic Plug-Is Writig Messages to the BEA WebLogic Collaborate Log Programmig BEA WebLogic Collaborate Messagig Applicatios 1-34 Itroducig BEA WebLogic Collaborate 044 ServiceNow, Ic.'s Exhibit 1004

45 CHAPTER 2 Gettig Started Usig WebLogic Collaborate This sectio describes how the architecture of WebLogic Collaborate provides a robust framework supportig messagig, coectivity, busiess protocols, ad itegratio with the WebLogic Process Itegrator workflow automatio tool. It icludes the followig topics: Cofiguratio Models Usig WebLogic Collaborate: The Ed-to-Ed View Cofiguratio Models I order to participate i busiess trasactios with a large set of tradig parters who use diverse processes ad protocols, a eterprise requires a variety of coectivity optios. To that ed, a tradig parter usig WebLogic Collaborate ca be cofigured to commuicate i a umber of differet ways. Tradig parter applicatios commuicate through their delivery chaels either directly, i peer-to-peer mode, or through a itermediary delivery chael, i hub-ad-spoke mode, or both. WebLogic Collaborate ca simultaeously support multiple peer-to-peer relatioships, ad serve as a routig hub, mediatig messages amog other tradig parters that deploy WebLogic Collaborate as their tradig parter server. Multiple messagig models ca be overlaid o these cofiguratios. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

46 2 Gettig Started Usig WebLogic Collaborate The followig sectios describe cofiguratio ad messagig models for tradig parters deployig WebLogic Collaborate: Peer-to-Peer Cofiguratio Hub-ad-Spoke Cofiguratio Peer-to-Peer Cofiguratio I a peer-to-peer cofiguratio, applicatios for two tradig parters commuicate through their respective delivery chaels. A tradig parter s message sedig ad receivig characteristics are ecapsulated i a WebLogic Collaborate delivery chael (see Delivery Chaels i Collaboratio Agreemets o page 1-23). Multiple tradig parter applicatios ca be implemeted i ay of the followig cofiguratios: O a sigle istace of WebLogic Collaborate withi a compay O multiple istaces of WebLogic Collaborate withi a compay or orgaizatio O multiple istaces of WebLogic Collaborate across a firewall ad over the Iteret 2-2 Itroducig BEA WebLogic Collaborate 046 ServiceNow, Ic.'s Exhibit 1004

47 Cofiguratio Models The followig figure illustrates possible peer-to-peer cofiguratios. Figure 2-1 Peer-to-Peer Cofiguratio Models Peer-to-peer cofiguratios support the exchage of busiess messages usig the RosettaNet ad cxml busiess protocols. For details about specific cofiguratio tasks, see Cofiguratio Tasks i Admiisterig BEA WebLogic Collaborate. Collaboratio agreemets betwee tradig parters capture the iformatio ecessary for routig busiess messages amog tradig parters. I the case of peer-to-peer commuicatio, the target tradig parter for a busiess message is the other tradig parter i the collaboratio agreemet (or the role of the other tradig parter, if there are more tha two roles defied for the coversatio). Hub-ad-Spoke Cofiguratio I a hub-ad-spoke cofiguratio, a tradig parter applicatio commuicates via a itermediary (routig proxy) delivery chael to aother tradig parter s delivery chael (spoke delivery chael). The followig figure icludes illustratios of Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

48 2 Gettig Started Usig WebLogic Collaborate possible hub-ad-spoke cofiguratios for the delivery chaels, the tradig parter applicatios, ad the istaces of WebLogic Collaborate that host the tradig parter applicatios. Figure 2-2 Hub-ad-Spoke Cofiguratio Models For details about cofigurig WebLogic Collaborate, see Admiisterig BEA WebLogic Collaborate. Hub-ad-spoke models support the exchage of busiess messages usig the XOCP busiess protocol. XOCP busiess messages ca be uicast or multicast amog tradig parters. Message multicastig is the ability of the XOCP messagig service to broadcast a message from oe tradig parter to may tradig parters, withi the costraits of a existig coversatio. 2-4 Itroducig BEA WebLogic Collaborate 048 ServiceNow, Ic.'s Exhibit 1004

49 Cofiguratio Models Collaboratio agreemets betwee tradig parters capture the iformatio ecessary for routig busiess messages amog tradig parters. For busiess messages to be exchaged betwee tradig parters through a itermediary (hub), collaboratio agreemets are created betwee each tradig parter ad the itermediary. I cotrast to the exchage of busiess messages betwee tradig parters who commuicate directly (whe the target tradig parter for a busiess message is the other tradig parter i the collaboratio agreemet), tradig parters usig a itermediary idetify the itermediary tradig parter (that is, the routig proxy delivery chael) as the target for their busiess messages. The destiatio for the message is specified whe the message is set ad, i the case of XOCP busiess messages, ca be a sigle destiatio (a uicast message) or multiple destiatios (a multicast message). Recipiet tradig parters ca be represeted i a message by a XPath expressio. For a discussio of the XOCP protocol ad message multicastig, see Supportig Busiess Protocols o page Message Mediatio Models I the hub-ad-spoke model, WebLogic Collaborate is istalled at both the hub ad spoke odes, as described i the previous sectio. Messages ca be mediated i ay of the followig ways: Routig Destiatio tradig parters are kow to the message iitiator. WebLogic Collaborate, cofigured as a hub, acts as a routig proxy ad passes busiess messages to the recipiets idicated by the seder. Iterposed workflows Destiatio tradig parters are ot kow to the message iitiator. There are collaboratio agreemets betwee tradig parters ad the itermediary, but ot betwee the tradig parters themselves. The itermediary itercepts the messages with a workflow that ca do ay type of processig, icludig complex filterig ad routig, itegratio with back-ed systems, message validatio, loggig, ad so o. This model is commo i blid auctios, i which the hub is the auctio broker. Parallel workflows The message iitiator has collaboratio agreemets with the hub, a tradig parter collocated at the hub, ad other destiatio tradig parters routed by the hub. A message goes to all tradig parters, icludig the collocated parter at the hub. O the hub, messages are directed to parallel workflows: oe workflow passes messages o to their destiatio tradig parters; aother mediates messages by performig busiess processig. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

50 2 Gettig Started Usig WebLogic Collaborate Note: Whe you defie a coversatio i the WebLogic Collaborate Admiistratio Cosole, you ca mark a workflow for a role i the coversatio as a proxy workflow. The hub delivery chael uses this proxy flag to differetiate betwee collaboratio agreemets that apply to coversatios with a role local to the hub, ad collaboratio agreemets that require the hub to be i the role of routig proxy. Iterceptors Tradig parters kow about each other (either a routig model or a parallel workflows model is i place), but the hub uses logic plug-is to itercept messages ad do additioal processig. Logic plug-is are Java classes that ca itercept ad process busiess messages at ru time. WebLogic Collaborate provides system logic plug-is, which you ca supplemet by writig custom logic plug-is. The system logic plug-is iclude XOCP router, XOCP filter, ad RosettaNet logic plug-is, all of which are directly ivolved i the processig of message recipiets based o XPath expressios i the repository. Custom logic plug-is ca perform a wide rage of services that are urelated to routig or filterig, as well as routig ad filterig operatios. Multiple logic plug-is ca be istalled i chais. A chai of routig logic plug-is ca be ivoked whe messages are set, ad a chai of filterig plug-is ca be ivoked whe messages are received. Tradig Parter Lightweight Cliets As well as makig direct coectios betwee tradig parter applicatios, the WebLogic Collaborate software supports lightweight cliets to give small ad medium-size tradig parters, or tradig parters with little or o back-ed itegratio requiremets, ways to coect ad participate i e-busiess commuities. Such tradig parters commuicate with WebLogic Collaborate usig either a Web browser or a file-sharig cliet. Messages for these lightweight cliets are processed by the istace of WebLogic Collaborate to which they coect. I other words, message processig is hosted o WebLogic Collaborate o behalf of the tradig parter deployig the Web browser or file-sharig cliet. The followig figure represets a example cofiguratio i which two tradig parters are created o Compay A s istace of WebLogic Collaborate, oe of which hosts the Web browser or file-sharig cliet used by Compay C. 2-6 Itroducig BEA WebLogic Collaborate 050 ServiceNow, Ic.'s Exhibit 1004

51 Usig WebLogic Collaborate: The Ed-to-Ed View Figure 2-3 Hosted Tradig Parter Cofiguratio For details about cofigurig ad deployig tradig parter lightweight cliets, see Tradig Parter Lightweight Cliet Sample i Usig BEA WebLogic Collaborate Samples. Usig WebLogic Collaborate: The Ed-to-Ed View Usig a Query Price ad Availability coversatio as a example, this sectio describes: The approach for settig up the WebLogic Collaborate compoets to allow oe tradig parter to participate i a coversatio with aother tradig parter, which shows how the compoets work together for busiess-to-busiess collaboratios The exchage of busiess messages amog tradig parters participatig i a coversatio, which shows how WebLogic Collaborate works Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

52 2 Gettig Started Usig WebLogic Collaborate The Query Price ad Availability coversatio used i this example is described i Defiig Coversatios ad Roles o page 1-7, from which the followig figure, illustratig the coversatio, is take. Figure 2-4 Workflows i a Query Price ad Availability Coversatio For the purposes of this sceario, there are two busiess parters: Compay ABC the buyer Compay XYZ the supplier I this sceario, Compay ABC is resposible for preparig the WebLogic Collaborate eviromet to participate i this example busiess collaboratio. Before goig ito productio with Compay XYZ, Compay ABC tests the compoets of the collaboratio i its ow WebLogic Collaborate eviromet. 2-8 Itroducig BEA WebLogic Collaborate 052 ServiceNow, Ic.'s Exhibit 1004

53 Usig WebLogic Collaborate: The Ed-to-Ed View The followig sectios describe how Compay ABC sets up two tradig parters i its WebLogic Collaborate eviromet to participate i this busiess collaboratio. Next, the subsequet exchage of busiess messages amog tradig parters is described. Fially, the steps both busiess parters take to exchage the data required before they ca participate i the Query Price ad Availability coversatio is described: Create Coversatio Defiitios Create Workflow Templates Create Tradig Parters ad Delivery Chaels Create Collaboratio Agreemets Sed ad Receive Busiess Messages Export ad Import Repository Iformatio Start Busiess Collaboratio A detailed discussio of how to use the WebLogic Collaborate Admiistratio Cosole or the WebLogic Process Itegrator Studio for cofiguratio is beyod the scope of this sectio. For complete cofiguratio details, see Admiisterig BEA WebLogic Collaborate ad BEA WebLogic Collaborate Admiistratio Cosole Olie Help. Create Coversatio Defiitios To specify the roles ad other details of a coversatio, you defie a coversatio usig the WebLogic Collaborate Admiistratio Cosole. The etity you defie is kow as a coversatio defiitio. A coversatio amog tradig parters is a active istace of a coversatio defiitio. I this example, a admiistrator for Compay ABC uses the WebLogic Collaborate Admiistratio Cosole to create a coversatio defiitio by performig the followig steps: Name the coversatio defiitio. (I this example, the coversatio defiitio is Query Price ad Availability.) Defie the roles i the Query Price ad Availability coversatio: buyer ad supplier. Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

54 2 Gettig Started Usig WebLogic Collaborate Referece XOCP as the busiess protocol to be used i this coversatio. (The other choices are cxml1.1, cxml1.2, RosettaNet 1.1, ad RosettaNet 2.0.) Attach a collaborative workflow template ame to each role. Note: The workflow template ames you attach durig this step are those of the workflow templates you must defie i the WebLogic Process Itegrator Studio. For details, see Create Workflow Templates o page The followig templates are attached to the roles i this example Query Price ad Availability coversatio. Role i Coversatio Buyer Supplier Collaborative Workflow Template QueryPriceAvailability_Buyer QueryPriceAvailability_Supplier Create Workflow Templates Workflows that implemet the roles for tradig parters i a WebLogic Collaborate coversatio defiitio are referred to as collaborative workflows. To desig or edit workflow templates that implemet coversatio roles i a WebLogic Collaborate coversatio, you use the WebLogic Process Itegrator Studio, specifically, the WebLogic Collaborate plug-i to the Studio, which exteds the fuctioality of the Studio to support collaborative workflows. The Studio allows you to assig properties to the workflows. These properties make the workflows usable i the WebLogic Collaborate eviromet. I this example, a admiistrator from Compay ABC uses the WebLogic Process Itegrator Studio to create two collaborative workflow templates (oe for each role i the coversatio): QueryPriceAvailability_Buyer ad QueryPriceAvailability_Supplier. A tradig parter may also implemet private workflows that work i cojuctio with a collaborative workflow ad that implemet local processes for a tradig parter. Such processes are ot ecessarily dictated by the coversatio defiitio (see Create 2-10 Itroducig BEA WebLogic Collaborate 054 ServiceNow, Ic.'s Exhibit 1004

55 Usig WebLogic Collaborate: The Ed-to-Ed View Coversatio Defiitios o page 2-9). For example, i the case where a tradig parter starts a coversatio, that tradig parter s private workflow ca start the collaborative workflow to iitiate the coversatio. The followig figure displays example collaborative workflows for the buyer ad supplier roles i the Query Price ad Availability coversatio. Figure 2-5 Collaborative Workflows for Buyer ad Supplier Roles Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

56 2 Gettig Started Usig WebLogic Collaborate To prepare collaborative workflows to exchage busiess messages i the WebLogic Collaborate eviromet, you specify coversatio properties for the collaborative workflow templates. These coversatio properties are specified i the WebLogic Process Itegrator Studio usig workflow template defiitios. To specify coversatio properties for this example, you must complete the followig tasks: Idetify the QueryPriceAvailability_Buyer collaborative workflow template as the Exchage Iitiator. (This specifies that the QueryPriceAvailability_Buyer workflow starts the coversatio.) Lik the QueryPriceAvailability_Buyer template with the buyer role i the Query Price ad Availability coversatio. Lik the QueryPriceAvailability_Supplier template with the supplier role i the Query Price ad Availability coversatio. Set ru-time properties for workflow templates. Such properties iclude: l l Note: Geeral properties, such as template effective ad expiry dates Quality of Service properties, such as umber of retries, timeouts, ad cofirmatio of delivery optios At ru time, the Quality of Service properties assiged to workflows take precedece over Quality of Service properties that you defie whe you set up delivery chaels for tradig parters i the WebLogic Collaborate Admiistratio Cosole. For details about how to use the WebLogic Process Itegrator Studio to desig collaborative workflow templates, see Creatig Workflows for BEA WebLogic Collaborate. Create Tradig Parters ad Delivery Chaels Eterprises that wat to participate i a coversatio must first cofigure their eviromets. This task icludes creatig a tradig parter, ad defiig tradig parter-specific iformatio ad oe or more delivery chaels. A delivery chael describes a tradig parter s message sedig ad receivig characteristics, icludig the busiess protocol to be used i the coversatio, a trasport protocol, ad security parameters Itroducig BEA WebLogic Collaborate 056 ServiceNow, Ic.'s Exhibit 1004

57 Usig WebLogic Collaborate: The Ed-to-Ed View Create Tradig Parters for Compay ABC Usig the WebLogic Collaborate Admiistratio Cosole, a admiistrator for Compay ABC creates two tradig parters i the WebLogic Collaborate eviromet: Tradig Parter A i the buyer role for the coversatio Supplier-Test i the supplier role for the coversatio Supplier-Test is used for testig the coversatio ad workflows before brigig the system up for productio with a tradig parter (i the role of supplier) from Compay XYZ. The iformatio to create each tradig parter icludes: Name: Tradig Parter A ad Supplier-Test Type: Local Cotact iformatio: Address, , phoe, fax, ad so o Party ID: A uique ame that idetifies the tradig parter i a collaboratio agreemet (for example, DUNS A ) Delivery chaels for Tradig Parter A Tradig Parter A requires two delivery chaels: oe spoke ad oe routig proxy. They are defied as follows: l l Name: Spoke Delivery Chael cotais the followig elemets: Documet Exchage: Defies the busiess protocol (XOCP) ad ru-time parameters Trasport: Defies the trasport protocol (HTTP), ed poit URI (for example, ad security parameters Name: Routig Proxy Delivery Chael cotais the followig elemets: Documet Exchage: Defies the busiess protocol (XOCP) ad ru-time parameters Trasport: Defies the trasport protocol (HTTP), ed poit URI (for example, ad security parameters Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

58 2 Gettig Started Usig WebLogic Collaborate Delivery chael for Supplier-Test The Supplier-Test tradig parter requires oe spoke delivery chael. The delivery chael defiitio cotais the followig iformatio: l l Documet Exchage defies the busiess protocol for this tradig parter (XOCP) ad ru-time parameters Trasport defies the trasport protocol (HTTP), ed poit URI (for example, ad security parameters Create Tradig Parter for Compay XYZ After Compay XYZ istalls WebLogic Collaborate, a admiistrator uses the WebLogic Collaborate Admiistratio Cosole to create a tradig parter i the WebLogic Collaborate eviromet: Tradig Parter Z i the supplier role. The iformatio to create Tradig Parter Z icludes: Name: Tradig Parter Z Type: Local Cotact iformatio: Address, , phoe, fax, ad so o Party ID: A uique ame that idetifies the tradig parter i a collaboratio agreemet (for example, DUNS Z ) Delivery chael Tradig Parter Z requires oe spoke delivery chael. The delivery chael defiitio cotais the followig iformatio: l l Documet Exchage defies the busiess protocol for this tradig parter (XOCP) ad ru-time parameters Trasport defies the trasport protocol (HTTP), ed poit URI (for example, ad security parameters 2-14 Itroducig BEA WebLogic Collaborate 058 ServiceNow, Ic.'s Exhibit 1004

59 Usig WebLogic Collaborate: The Ed-to-Ed View The followig figure illustrates the cofiguratio of the three tradig parters ad their delivery chaels as defied for this sceario. Figure 2-6 Cofiguratio of Tradig Parters i Example Coversatio Compay ABC ca use the Supplier-Test tradig parter to test the collaboratio agreemet for the Query Price ad Availability coversatio before coectig with Compay XYZ s tradig parter, who will be the supplier i the real-life sceario. Create Collaboratio Agreemets A collaboratio agreemet bids the tradig parters delivery chaels to the coversatio defiitio. It is through this collaboratio agreemet that tradig parters agree o the iteractios betwee them, i particular, the coversatio i which they participate ad each tradig parter s message sedig ad receivig characteristics. A admiistrator uses the WebLogic Collaborate Admiistratio Cosole to create a collaboratio agreemet, with a specific ame ad versio, i its repository. A collaboratio agreemet defies a party for each tradig parter participatig i the agreemet, ad icludes the followig iformatio: A uique party idetifier for each party to the collaboratio agreemet. The delivery chael iformatio for each tradig parter, as described i Create Tradig Parters ad Delivery Chaels o page Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004

60 2 Gettig Started Usig WebLogic Collaborate The delivery chaels defie the busiess protocol for the collaboratio, the ru-time parameters for each tradig parter, the trasport protocol, the ed poit (URI) for each tradig parter s trasport, ad security parameters. The coversatio defiitio, as described i Create Coversatio Defiitios o page 2-9. The coversatio defiitio ames the busiess collaboratio (i this case, Query Price ad Availability), ad attaches the roles (for example, buyer ad supplier) to WebLogic Process Itegrator collaboratio workflow templates. Returig to the ed-to-ed view example: Compay ABC creates two collaboratio agreemets as follows: QueryPrice-A-A The parties are the Tradig Parter A routig proxy delivery chael ad the Tradig Parter A spoke delivery chael. QueryPrice-A-SpTest The parties are the Tradig Parter A routig proxy delivery chael ad the Supplier-Test spoke delivery chael. Note that each tradig parter has a collaboratio agreemet with the routig-proxy delivery chael. The routig proxy acts as a itermediary; that is, it acts as the proxy supplier i its collaboratio agreemet with Tradig Parter A, ad as a proxy buyer i its collaboratio agreemet with Supplier-Test. The collaboratio agreemets bid the delivery chaels to the coversatio defiitio, ad they referece the collaborative workflow templates that are associated with the roles i the coversatio defiitio. The followig figure represets the two collaboratio agreemets. Figure 2-7 Compoets i the Collaboratio Agreemets 2-16 Itroducig BEA WebLogic Collaborate 060 ServiceNow, Ic.'s Exhibit 1004

61 Usig WebLogic Collaborate: The Ed-to-Ed View Notice the followig i the precedig figure: The routig-proxy delivery chael is a party i both collaboratio agreemets. I the QueryPrice-A-A agreemet, the routig-proxy delivery chael is i the role of (proxy) supplier, ad i the QueryPrice-A-SpTest agreemet, it is i the role of (proxy) buyer. The parties i the collaboratio agreemets are associated with the roles i the coversatio defiitio. The coversatio defiitio associates the collaborative workflow template for each role i the coversatio with the parties i the collaboratio agreemet. Sed ad Receive Busiess Messages After the workflow templates, the coversatio defiitio, the tradig parters, the delivery chaels, ad the collaboratio agreemets have bee created, Compay ABC tests its collaboratio agreemets ad coversatio usig Tradig Parter A i the buyer role, ad Supplier-Test i the supplier role for the Query Price ad Availability coversatio. This sectio describes how busiess messages are set ad received durig the Query Price ad Availability coversatio. Figure 2-8 Sedig ad Receivig Busiess Messages Itroducig BEA WebLogic Collaborate ServiceNow, Ic.'s Exhibit 1004