BEA WebLogic
`Collaborate
`A Component of BEA WebLogic Integration
`
`Introducing
`BEA WebLogic Collaborate
`
`B E A W e b L o g i c C o l l a b o r a t e R e l e a s e 2 . 0
`D o c u m e n t E d i t i o n 2 . 0
`J u l y 2 0 0 1
`
`001
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Copyright
`
`Copyright © 2001 BEA Systems, Inc. All Rights Reserved.
`
`Restricted Rights Legend
`
`This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems
`License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against
`the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or
`in part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable
`form without prior consent, in writing, from BEA Systems, Inc.
`
`Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems
`License Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause
`at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at
`DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR
`supplement 16-52.227-86; or their equivalent.
`
`Information in this document is subject to change without notice and does not represent a commitment on 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, and Jolt are registered trademarks of BEA Systems, Inc. How Business Becomes
`E-Business, Operating System for the Internet, Liquid Data, BEA WebLogic E-Business Platform, BEA Builder,
`BEA Manager, BEA eLink, BEA WebLogic Commerce Server, BEA WebLogic Personalization Server, BEA
`WebLogic Process Integrator, BEA WebLogic Collaborate, BEA WebLogic Enterprise, BEA WebLogic Server,
`BEA WebLogic Integration, E-Business Control Center, BEA Campaign Manager for WebLogic, and Portal
`FrameWork are trademarks of BEA Systems, Inc.
`
`All other trademarks are the property of their respective companies.
`Introducing BEA WebLogic Collaborate
`
`Document Edition
`
`Date
`
`Software Version
`
`2.0
`
`July 2001
`
`2.0
`
`002
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Contents
`
`About This Document
`What You Need to Know ......................................................................................v
`e-docs Web Site ................................................................................................... vi
`How to Print the Document................................................................................. vi
`Contact Us!.......................................................................................................... vi
`Documentation Conventions .............................................................................. vii
`
`1. Overview
`Feature Highlights for WebLogic Collaborate .................................................. 1-2
`Meeting the Requirements of Your E-Business ................................................ 1-4
`Connecting Trading Partners...................................................................... 1-4
`Defining Conversations and Roles............................................................. 1-7
`Managing Business Processes .................................................................. 1-10
`Supporting Business Protocols................................................................. 1-13
`Ensuring the Security of Transactions ..................................................... 1-22
`Defining Collaboration Agreements ........................................................ 1-23
`Managing Conversations.......................................................................... 1-26
`Managing Systems and Applications ....................................................... 1-28
`Documentation Roadmap for WebLogic Collaborate..................................... 1-32
`
`2. Getting Started Using WebLogic Collaborate
`Configuration Models........................................................................................ 2-1
`Peer-to-Peer Configuration ........................................................................ 2-2
`Hub-and-Spoke Configuration ................................................................... 2-3
`Using WebLogic Collaborate: The End-to-End View ...................................... 2-7
`Create Conversation Definitions ................................................................ 2-9
`Create Workflow Templates .................................................................... 2-10
`
`Introducing BEA WebLogic Collaborate
`
`iii
`
`003
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Create Trading Partners and Delivery Channels ...................................... 2-12
`Create Collaboration Agreements ............................................................ 2-15
`Send and Receive Business Messages...................................................... 2-17
`Export and Import Repository Information.............................................. 2-19
`Start Business Collaboration .................................................................... 2-21
`
`Index
`
`iv
`
`Introducing BEA WebLogic Collaborate
`
`004
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`About This Document
`
`This document explains how to get started using the BEA WebLogic Collaborate™
`software:
`
`n Chapter 1, “Overview,” provides an overview of the features of the WebLogic
`Collaborate software, a summary of the requirements of business-to-business
`e-commerce, and a description of how you can meet the needs of your
`e-commerce business using WebLogic Collaborate.
`
`n Chapter 2, “Getting Started Using WebLogic Collaborate,” provides an
`architectural overview of the WebLogic Collaborate software, and an end-to-end
`example of the tasks you need to complete to get your WebLogic Collaborate
`environment ready to exchange business messages with business partners.
`
`What You Need to Know
`
`This document is written for managers, system administrators, and programmers who
`are interested in understanding the architectural requirements for implementing and
`administering e-commerce collaborations based on WebLogic Collaborate. It is
`assumed that you have a working knowledge of the BEA WebLogic Server™ system,
`XML, Enterprise Java Beans, and Java programming.
`
`Introducing BEA WebLogic Collaborate
`
`v
`
`005
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`e-docs Web Site
`
`The WebLogic Collaborate product documentation is available on the BEA Systems,
`Inc. corporate Web site. From the BEA Home page, click Product Documentation or
`go directly to the Product Documentation page at http://e-docs.bea.com.
`
`How to Print the Document
`
`You can print a copy of this document from a Web browser, one file at a time, by using
`the File—>Print option on your Web browser.
`
`A PDF version of this document is available on the WebLogic Collaborate
`documentation Home page on the e-docs Web site (and also on the documentation
`CD). You can open the PDF in Adobe Acrobat Reader and print the entire document
`(or a portion of it) in book format. To access the PDFs, open the WebLogic Enterprise
`documentation Home page, click the PDF Files button, and select the document you
`want to print.
`
`If you do not have Adobe Acrobat Reader installed, you can download it for free from
`the Adobe Web site at http://www.adobe.com/.
`
`Contact Us!
`
`Your feedback on the WebLogic Collaborate documentation is important to us. Send
`us e-mail at docsupport@bea.com if you have questions or comments. Your comments
`will be reviewed directly by the BEA professionals who create and update the
`WebLogic Collaborate documentation.
`
`In your e-mail message, please indicate that you are using the documentation for
`WebLogic Collaborate Release 2.0.
`
`vi
`
`Introducing BEA WebLogic Collaborate
`
`006
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`If you have any questions about this release of WebLogic Collaborate, or if you have
`problems installing and running WebLogic Collaborate, contact BEA Customer
`Support through BEA WebSUPPORT at http://www.bea.com. You can also contact
`Customer Support by using the contact information provided on the Customer Support
`Card, which is included in the product package.
`
`When contacting Customer Support, be prepared to provide the following information:
`
`n Your name, e-mail address, phone number, and fax number
`
`n Your company name and company address
`
`n Your machine type and authorization codes
`
`n The name and version of the product you are using
`
`n A description of the problem and the content of pertinent error messages
`
`Documentation Conventions
`
`The following documentation conventions are used throughout this document.
`
`Convention
`
`Item
`
`boldface text
`
`Indicates terms defined in the glossary.
`
`Ctrl+Tab
`
`Indicates that you must press two or more keys simultaneously.
`
`italics
`
`Indicates emphasis or book titles.
`
`Introducing BEA WebLogic Collaborate
`
`vii
`
`007
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Convention
`
`Item
`
`monospace
`text
`
`Indicates code samples, commands and their options, data structures and
`their members, data types, directories, and file names and their extensions.
`Monospace text also indicates text that you must enter from the keyboard.
`Examples:
`#include <iostream.h> void main ( ) the pointer psz
`chmod u+w *
`
`\tux\data\ap
`
`.doc
`
`tux.doc
`
`BITMAP
`
`float
`
`monospace
`boldface
`text
`
`Identifies significant words in code.
`Example:
`void commit ( )
`
`monospace
`italic
`text
`
`Identifies variables in code.
`Example:
`String expr
`
`UPPERCASE
`TEXT
`
`Indicates device names, environment variables, and logical operators.
`Examples:
`LPT1
`SIGNON
`OR
`
`{ }
`
`[ ]
`
`|
`
`Indicates a set of choices in a syntax line. The braces themselves should
`never be typed.
`
`Indicates optional items in a syntax line. The brackets themselves should
`never be typed.
`Example:
`buildobjclient [-v] [-o name ] [-f file-list]...
`[-l file-list]...
`
`Separates mutually exclusive choices in a syntax line. The symbol itself
`should never be typed.
`
`viii
`
`Introducing BEA WebLogic Collaborate
`
`008
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Convention
`
`Item
`
`Indicates one of the following in a command line:
`n That an argument can be repeated several times in a command line
`n That the statement omits additional optional arguments
`n That you can enter additional parameters, values, or other information
`The ellipsis itself should never be typed.
`Example:
`buildobjclient [-v] [-o name ] [-f file-list]...
`[-l file-list]...
`
`Indicates the omission of items from a code example or from a syntax line.
`The vertical ellipsis itself should never be typed.
`
`...
`
`. . .
`
`Introducing BEA WebLogic Collaborate
`
`ix
`
`009
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`x
`
`Introducing BEA WebLogic Collaborate
`
`010
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`CHAPTER
`
`1 Overview
`
`Enterprises strive to integrate, automate, and streamline core internal and external
`business processes to improve their performance in today’s dynamic
`business-to-business (B2B) electronic commerce (e-commerce) environment. These
`business processes drive a company’s e-commerce interactions with their customers,
`partners, distributors, and suppliers; they can also streamline the company’s internal
`business. Among the target business processes for B2B integration and automation are
`design and specification, manufacturing and testing, procurement, sales, fulfillment,
`customer service, and planning. To support these processes, B2B integration must
`support workflow processing, messaging and routing, and enterprise application
`integration.
`
`The BEA WebLogic Collaborate™ product is an XML- and Java-based e-commerce
`platform that enables you to implement complex e-commerce systems on the Web. It
`helps you to quickly deploy e-commerce systems that link existing back-end
`applications, databases, customers, and partners into automatic and flexible electronic
`collaborations.
`
`WebLogic Collaborate is a software framework and a set of services built on top of
`BEA WebLogic Server™. It builds upon the WebLogic Server foundation by adding
`a framework for messaging, connectivity, and business protocols. It also integrates the
`WebLogic Process Integrator workflow capability for designing and managing
`business processes.
`
`WebLogic Collaborate is implemented entirely in Java and leverages the J2EE
`standard APIs. XML is used as a standard format for documents exchanged by
`business partners. WebLogic Collaborate supports HTTP because the World Wide
`Web is the ubiquitous communication medium for e-business.
`
`WebLogic Collaborate simplifies the implementation and development of
`business-to-business trading networks, providing opportunities to integrate internal
`business processes with inter-enterprise business message exchange. A variety of
`deployment models are supported.
`
`Introducing BEA WebLogic Collaborate
`
`1-1
`
`011
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`1
`
`Overview
`
`The following sections provide an overview of the WebLogic Collaborate product:
`
`n Feature Highlights for WebLogic Collaborate
`
`n Meeting the Requirements of Your E-Business
`
`n Documentation Roadmap for WebLogic Collaborate
`
`Feature Highlights for WebLogic Collaborate
`
`WebLogic Collaborate provides an infrastructure platform for integrating business
`processes that can span multiple corporate departments, multiple enterprises across the
`Internet, or both. The WebLogic Collaborate platform supports the building of
`mission-critical, scalable, real-world e-commerce collaborations. Its features include:
`
`n An open, nonproprietary architecture that leverages Java, J2EE, XML, HTTP,
`HTTPS, and other industry standards to allow rapid system and cross-platform
`integration, with low barriers to entry.
`
`n Support for multiple business protocols, including XOCP, RosettaNet, and
`cXML, thus providing the ability to exchange business documents in a secure
`manner with a variety of trading partners, accommodating the complexity of
`heterogeneous platforms, different message structures, and different processes in
`various e-business environments.
`
`n A variety of connectivity options, allowing rapid connectivity among many
`trading partners for both automated and semi-automated interactions.
`Connectivity and subsequent business collaborations between trading partner
`applications are possible entirely within an enterprise or a company, between
`trading partner applications across company firewalls and over the Internet, or in
`a combination of the two.
`
`n Support for rapidly enabling trading partners through no-cost lightweight client
`connectivity, using browser-based interfaces and file-sharing mechanisms.
`
`n Peer-to-peer and mediated messaging models: peer-to-peer messaging allows
`direct messaging between partners, and mediated messaging supports tasks such
`as message routing, message content filtering, and value-added services.
`
`1-2
`
`Introducing BEA WebLogic Collaborate
`
`012
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Feature Highlights for WebLogic Collaborate
`
`n Tools and processes for the effective management of dynamic and diverse
`trading partner relationships.
`
`n Robust support for secure, high-volume business transaction levels based on
`BEA’s award-winning WebLogic Server™ technology. BEA’s proven,
`high-availability, 24x7-managed application server technology, with dynamic
`load-balancing, multithreading, and failover without processing interruption, has
`delivered industry-leading results in thousands of the world’s most demanding
`application environments.
`
`n Reliable, role-based XML messaging that supports enhanced send and receive
`capabilities, including support for large messages.
`
`n Conversation coordination to manage the execution and interaction of trading
`partner applications within a conversation and to manage conversation life
`cycles.
`
`n Integration with BEA WebLogic Process Integrator, the BEA workflow
`automation tool, providing a flexible and dynamic process-based approach to
`integrate public and private business processes.
`
`n An SSL-based secure platform for conducting collaborations that supports digital
`signatures, digital receipts, nonrepudiation, and mutual (two-way) authentication
`using digital certificates among trading partners.
`
`n A data repository and a set of design and configuration tools to define and
`manage the metadata and conversation definitions of WebLogic Collaborate.
`
`WebLogic Collaborate also offers a number of features inherited from WebLogic
`Server, including:
`
`n Ability to build custom portals by leveraging BEA WebLogic Personalization
`Server™ components
`
`n Portal backbone
`
`n Controlled and secure Web access to existing business data and applications
`
`n Support for existing applications based on CORBA, EJB, BEA Tuxedo®, and
`COM+
`
`Introducing BEA WebLogic Collaborate
`
`1-3
`
`013
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`1
`
`Overview
`
`Meeting the Requirements of Your
`E-Business
`
`WebLogic Collaborate manages enterprise-to-enterprise collaborations, allowing
`heterogeneous enterprises to interact in diverse business transactions, which can be
`complex and long-running. The following sections describe requirements for the
`framework to build such a B2B e-commerce environment, and they explain how
`WebLogic Collaborate meets these requirements:
`
`n Connecting Trading Partners
`
`n Defining Conversations and Roles
`
`n Managing Business Processes
`
`n Supporting Business Protocols
`
`n Ensuring the Security of Transactions
`
`n Defining Collaboration Agreements
`
`n Managing Conversations
`
`n Managing Systems and Applications
`
`Connecting Trading Partners
`
`A trading partner joins one or more other trading partners to form an e-commerce
`community with a specific business purpose. Business partners in an e-commerce
`community can range in size from large enterprises to small divisions within an
`enterprise. One of the basic building blocks of B2B e-commerce is the trading partner,
`specifically, the trading partner applications that form the nodes in system-to-system
`interactions among business partners. An e-commerce community formed by a group
`of trading partners can:
`
`n Exist entirely within a company, spanning multiple corporate departments (the
`business purpose for such a community might be inventory management, for
`example)
`
`1-4
`
`Introducing BEA WebLogic Collaborate
`
`014
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Meeting the Requirements of Your E-Business
`
`n Span multiple companies across firewalls and over the Internet (the business
`purpose might be supply chain management or multistep purchasing interactions,
`for example)
`
`n Include trading partners both within a company and in other companies (one or
`more of the trading partners within a company communicates with trading
`partners in other companies across the Internet)
`
`A trading partner must have a special identity that defines where it fits with the
`business purpose of the e-community. In the WebLogic Collaborate environment, a
`trading partner refers specifically to an entity that has an agreement with another entity
`to participate in a specific business exchange, or conversation, in a specific role that is
`defined for the conversation.
`
`To meet the requirements of today’s diverse B2B e-commerce activities, an enterprise
`must be able to use a variety of connectivity options. Such flexibility is necessary if a
`company wants to participate in business transactions with a large set of trading
`partners with diverse processes and protocols.
`
`To that end, a WebLogic Collaborate trading partner application can be configured to
`communicate directly with other trading partners in a peer-to-peer mode, or through an
`intermediary in the hub-and-spoke mode, or both. These different configuration modes
`allow for either direct or mediated messaging between trading partners. An
`intermediary in the message flow can perform tasks such as routing and filtering of
`messages, or it can provide services to the trading partners in the conversation. For
`more details about modeling your WebLogic Collaborate configurations, see
`“Configuration Models” on page 2-1.
`
`Some business partners may have modest back-end integration requirements, or may
`need to participate in collaborative processes without installing the WebLogic
`Collaborate software. WebLogic Collaborate supports lightweight clients to give small
`and medium-size enterprises, or enterprises with little or no back-end integration
`requirements, a simple integration path through which they can participate in
`e-business communities. Such enterprises can use a Web browser or a file-sharing
`client to communicate with business partners who deploy WebLogic Collaborate as
`their trading partner server. The instance of WebLogic Collaborate to which they
`connect acts as a server for their needs. For details about setting up and configuring
`trading partner lightweight clients, see Using BEA WebLogic Collaborate Samples.
`
`Introducing BEA WebLogic Collaborate
`
`1-5
`
`015
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`1
`
`Overview
`
`The following figure illustrates a simple scenario in which WebLogic Collaborate is
`deployed in peer-to-peer relationships between customers and suppliers in a value
`chain. A customer or supplier trading partner can support multiple peer-to-peer
`business partnerships with other trading partners.
`
`Figure 1-1 Peer-to-Peer Messaging Among Trading Partners
`
`1-6
`
`Introducing BEA WebLogic Collaborate
`
`016
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Meeting the Requirements of Your E-Business
`
`The following figure illustrates a scenario in which WebLogic Collaborate is deployed
`as a Net Market, providing intermediary services to several trading partners. For
`example, this might be an auction service, in which the Net Market is the auction
`broker.
`
`Figure 1-2 Mediated Messaging in a Net Market
`
`Defining Conversations and Roles
`
`When trading partners join other trading partners to form an e-community with a
`specific business purpose, they participate in a conversation. In WebLogic
`Collaborate, a conversation:
`
`n Is a series of business messages exchanged between trading partners
`
`n May be complex and long-running, or short-lived
`
`Introducing BEA WebLogic Collaborate
`
`1-7
`
`017
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`1
`
`Overview
`
`n Has a unique conversation name
`
`The business messages that can be exchanged between participants in the conversation
`are determined by the roles the trading partners play in the conversation. The roles and
`other details of a conversation are specified in a conversation definition using the
`WebLogic Collaborate Administration Console. A conversation is an active instance
`of a conversation definition.
`
`A conversation definition:
`
`n Has a unique name and version.
`
`n Defines two or more roles to be used by trading partners in a conversation. The
`kinds of messages trading partners may send and receive are dictated by their
`roles in the conversation.
`
`n Is linked to a business protocol.
`
`n Typically references a WebLogic Process Integrator collaborative workflow
`template for each role. The message choreography for a conversation is
`described in these collaborative workflow templates.
`
`Note: Using BEA WebLogic Process Integrator is the recommended approach to
`composing business messages and choreographing their exchange in
`conversations. Alternatively, you can write Java WebLogic Collaborate
`messaging applications that use the WebLogic Collaborate Messaging API
`or the cXML API. When you use such messaging applications,
`conversation definitions do not reference a workflow template.
`
`For details about writing messaging applications using the WebLogic Collaborate
`Messaging API and the cXML API, see Programming BEA WebLogic Collaborate
`Messaging Applications and Implementing cXML for BEA WebLogic Collaborate,
`respectively.
`
`When you use WebLogic Process Integrator to compose business messages and
`manage their exchange in a conversation, each trading partner who participates in the
`conversation in a given role must implement the collaborative workflow required for
`its role. Collaborative workflows encapsulate the processes required to handle the right
`business messages at the right time for a given trading partner’s role in a conversation.
`
`For example, the following figure represents a simple conversation with two
`participating roles, buyer and supplier, and hypothetical workflows for the two roles.
`
`1-8
`
`Introducing BEA WebLogic Collaborate
`
`018
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Meeting the Requirements of Your E-Business
`
`Figure 1-3 Collaborative Workflows in a Query Price and Availability
`Conversation
`
`In this figure, note the following:
`
`n The business messages—Two business messages,
`PriceAndAvailabilityQuote and PriceAndAvailabilityResponse, are
`exchanged between trading partner applications.
`
`n The buyer and supplier roles—The implication of being in a role in a given
`conversation is that you send and receive only the business messages defined for
`your role. For example, the buyer:
`
`l Starts the conversation
`
`l Sends the business message PriceAndAvailabilityQuote
`
`l Receives the business message PriceAndAvailabilityResponse and
`processes it
`
`Introducing BEA WebLogic Collaborate
`
`1-9
`
`019
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`1
`
`Overview
`
`By contrast, the supplier:
`
`l Receives and processes the business message
`PriceAndAvailabilityQuote
`
`l Sends the business message PriceAndAvailabilityResponse
`
`n The collaborative workflows—Each role has its own set of tasks required to
`send and receive the right business messages at the right times. In the WebLogic
`Collaborate environment, a trading partner implements a collaborative workflow
`for a particular role in a conversation.
`
`Managing Business Processes
`
`Using BEA WebLogic Process Integrator™ is the recommended approach to
`composing business messages and choreographing their exchange in conversations.
`Alternatively, you can write Java WebLogic Collaborate messaging applications that
`use the WebLogic Collaborate Messaging API or the cXML API. This section
`discusses the approaches to developing and managing messaging applications in
`WebLogic Collaborate.
`
`Workflows are business processes. Business processes can span multiple applications,
`corporate departments, and business partners (trading partners) behind a firewall and
`over the Internet. An enterprise’s business processes can be divided into two broad
`categories: public and private.
`
`Public and Private Business Processes
`
`Business processes can be designed as public or private processes.
`
`Public processes are interface processes. Their definitions and designs are known,
`understood, and agreed upon by the organizations using them, and may be customized
`or standardized across an industry or industry segment, as in the case of RosettaNet
`Partner Interface Processes (PIPs). They are part of a formal contract between trading
`partners that specifies the content and semantics of message interchanges. These
`processes can be implemented in different ways by different trading partners.
`
`In the context of WebLogic Collaborate, when collaborative workflows are intended
`to be reused in multiple conversations with different business partners, they should be
`designed as public processes.
`
`1-10
`
`Introducing BEA WebLogic Collaborate
`
`020
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Meeting the Requirements of Your E-Business
`
`Participants in a conversation can also implement private, noncollaborative
`workflows, which can integrate their back-end processing. Private processes are the
`business processes conducted within an organization. Their definitions and designs are
`specific to that organization and are not visible outside it. Within trading partner
`enterprises, private processes interface with public processes and with back-end
`business systems. In the context of public processes, private processes can be thought
`of as subworkflows or subprocesses that implement tasks that are part of the public
`workflow. For example, a trading partner may implement a private workflow that
`works in conjunction with a collaborative workflow and that implements the processes
`that occur locally to a trading partner, but that are not necessarily dictated by the
`conversation definition.
`
`Using BEA WebLogic Process Integrator
`
`WebLogic Process Integrator is a workflow automation tool. It automates and
`integrates a business process by managing the sequence of activities in the process and
`invoking the appropriate resources required by the activities or steps in the process.
`The components of WebLogic Process Integrator include a workflow design tool (the
`WebLogic Process Integrator Studio), a GUI monitoring tool (the WebLogic Process
`Integrator Worklist), and the Process Engine that monitors and controls workflows.
`
`In the WebLogic Collaborate environment, a WebLogic Process Integrator
`collaborative workflow is a workflow that implements a role in a conversation
`definition for a trading partner. The message choreography for a WebLogic
`Collaborate conversation is defined by collaborative workflow templates: one
`template is defined for each role in the conversation definition, as described in
`“Defining Conversations and Roles” on page 1-7.
`
`WebLogic Collaborate provides a plug-in to the WebLogic Process Integrator Studio
`tool that extends the already powerful business process design tool with functionality
`that allows you to create collaborative workflows. Using the plug-in functionality, you
`can compose and extract the contents of business messages, specify the message
`delivery Quality of Service (QoS), handle message tokens, and so on.
`
`For details about how to use WebLogic Process Integrator, and how it is integrated in
`the WebLogic Collaborate environment, see Creating Workflows for BEA WebLogic
`Collaborate.
`
`Introducing BEA WebLogic Collaborate
`
`1-11
`
`021
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`1
`
`Overview
`
`In summary, business processes in the WebLogic Collaborate environment are defined
`and managed using WebLogic Process Integrator, which provides the following:
`
`n A visual design tool for creating workflows
`
`n Functionality in the design tool for associating the workflows with a WebLogic
`Collaborate conversation definition
`
`n A run-time process engine for executing workflows
`
`n Integration with back-end applications via the use of workflow actions
`
`n Worklist: A utility for running workflows interactively
`
`n Process monitoring capabilities
`
`Using the WebLogic Collaborate Messaging API
`
`As an alternative to using WebLogic Process Integrator, a trading partner can
`implement Java-based XOCP messaging applications based on the WebLogic
`Collaborate Messaging API. This API was available as the C-Enabler API in
`WebLogic Collaborate Release 1.0. You can use WebLogic Collaborate Messaging
`API with WebLogic Collaborate Release 2.0. For details about migrating your
`C-Enabler API applications from WebLogic Collaborate Release 1.0 to Release 2.0
`and for information about using the WebLogic Collaborate Messaging API with
`Release 2.0, you should see Programming BEA WebLogic Collaborate Messaging
`Applications and Migrating BEA WebLogic Collaborate to Release 2.0.
`
`Using the cXML API
`
`WebLogic Collaborate supports multiple business protocols for sending and receiving
`messages (see “Supporting Business Protocols” on page 1-13). For the cXML
`(Commerce eXtensible Markup Language) protocol, WebLogic Collaborate provides
`a cXML API which provides classes that allow the sending and receiving of cXML
`messages, the creation and manipulation of cXML documents, the mapping of a
`collaboration agreement to a message, and so on. For details, see Implementing cXML
`for BEA WebLogic Collaborate.
`
`1-12
`
`Introducing BEA WebLogic Collaborate
`
`022
`
`ServiceNow, Inc.'s Exhibit 1004
`
`

`

`Meeting the Requirements of Your E-Business
`
`Supporting Business Protocols
`
`A business message is the basic unit of communication among trading partners and is
`exchanged as part of a conversation. A business message contains one or more XML
`business documents, one or more attachments, or a combination of both. The contents
`and format of a business message depend on the business protocol chosen for the
`conversation (see “Business Messages” on page 1-17 for details).
`
`A business pro