P. 1
Overview

Overview

|Views: 4|Likes:
Published by Ron Martinez

More info:

Published by: Ron Martinez on Sep 28, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

09/28/2010

pdf

text

original

Transactor System Overview

Version 1.0
Oct-98

Inc. Ltd. JavaSoft.S.. registered trademarks of Symantec Corporation. Sun. Symantec and the Symantec logo are U. SUFFERED BY LICENSEE AS A RESULT OF USING. Netscape(TM) and Netscape Navigator(TM) are trademarks of Netscape Communications Corporation. export control laws. Oracle7 is a trademark of Oracle Corporation.S. By accepting. Products bearing an authorized "Transactor" Logo are based upon Transactor Networks' Transactor technology. CA. TRANSACTOR NETWORKS MAKES NO REPRESENTATIONS OR WARRANTIES. CA 94110. Printed in the U.0 Copyright Information Transactor™ system products are owned exclusively by Transactor Networks. a copy of which is available at Transactor Networks.. UNIX is a registered trademark in the United States and other countries exclusively licensed through X/Open Company. JavaServer. and all other applicable laws of the U. and refer to Transactor Networks' Transactor Technologies.S. Java.Copyright © 1998 Transactor Networks. SPARC is a trademark of SPARC International. Transactor and all Transactor-based names and logos. San Francisco. Windows and Windows NT are registered trademarks of Microsoft Corporation. Symantec Visual Cafe and dbANYWHERE are trademarks of Symantec Corporation.. 2650 18th Street. TRANSACTOR NETWORKS SHALL NOT BE LIABLE FOR ANY DAMAGES. 94110 All rights reserved.S. in the United States and other countries. FITNESS FOR A PARTICULAR PURPOSE. STATUTORY OR OTHERWISE.A. San Francisco. InstallShield® Java™ Edition is a registered trademark and InstallShield is a service mark of InstallShield Corporation. Ownership of the software shall remain solely in Transactor Networks. SQL*Net are registered trademarks of Oracle Corporation. INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY. Release 1. Solaris and Ultra. Licensee agrees to comply strictly with all such regulations and acknowledges that it has the sole responsibility to obtain such licenses to export. JDK. Transactor™ Server System. Inc. JDBC. using or copying this Software. including the U. Inc. CONSEQUENTIAL OR SPECIAL DAMAGES. MODIFYING OR DISTRIBUTING THE BINARY SOFTWARE OR ITS DERIVATIVES. are trademarks of Transactor Networks. Other brands and products are trademarks of their respective holder/s.S. and the terms of the License agreement dated November 19. ORACLE. are trademarks or registered trademarks of Sun Microsystems. . Inc. re-export or import this documentation and software as may be required after delivery to Licensee. Export Administration Act and its associated regulations. INCIDENTAL. Inc. Licensee agrees to abide by the intellectual property laws. WITHOUT LIMITATION. including LEDO. Sun Microsystems. 1996. EITHER EXPRESS OR IMPLIED. INCLUDING. 2650 18th Street. Inc. JavaBeans. and may be subject to export or import regulations in other countries. and are compatible with the API's for such technology. in the United States and other countries. Licensee shall notify and inform its employees having access to this documentation and software of Licensee's obligation to comply with the requirements stated in this paragraph. This documentation and software is subject to U. Inc. Microsoft. Web Server. OR NON-INFRINGEMENT.

............................................................................................................................................................Table of Contents Preface............................1 Related Documentation ........5 ..............3 Relationships ..........................................................1 Audience............................................................................................1 How to Use This Book ..............................................................................2 System Components.................3 Responsibilities.......................................................................................................................................................................................................................................................................................................................................1 Introduction .................................................................4 Relationships .............2 Relationships ............................................................................................................................................................................................................................2 Responsibilities................................................................................................................................4 Transactor Client.......................................................................3 Biz Framework ...............................................................................................................................................................................................................................................................................................................................................................................................................................4 Responsibilities....................................1 Terminology................................2 Transactor Server .........................................................................................................................................................................................

components and use Transactor TxOwner Developer Guide. • • • • • Related Documentation Transactor Biz-Framework Developer Guide. Terminology This document uses the following terminology and conventions: • The term Transactor server refers to the components of the Transactor system that provide encryption. Describes the Biz Framework model. How to Use This Book Consult this document for introductory information on the Transactor system components. responsibilities and relationships. and ownership verification services. Audience This document is for general audiences seeking an introduction to the Transactor system. The descriptions assume only a basic understanding of client-server systems. components and use Transactor System Overview 1 10/16/98 . The term Application server refers to the server-resident portion of a third party client-server application. Describes the client-side model. T-server is a shortened form of the term Transactor server. The term Application client refers to the client-resident portion of a third party clientserver application. The Transactor server consists of two portions. their roles. validation. These two terms are used interchangeably throughout this document. The term Biz Framework refers to a framework of software components which a developer can use to create an Application server program. the Transactor engine written in the JAVAª programming language. and the Transactor database that resides in an Oracleª database.Preface This is an introduction to the Transactor system and its three primary components. The term Transactor client refers to the components of the Transactor system which interface with application clients and provide a communication channel with a Biz Framework.

The Transactor system is written almost entirely in the JAVA language with only a small portion of the cryptography written in native C. Representing software components. the Transactor system provides its users. Each tier has its own role. responsibilities. it is responsible for: • • • keeping records of all users. validating ownership of objects before transactions take place. with a degree of confidence otherwise unavailable online. The Transactor system employs a combination of cryptographic algorithms within a secure three-tiered architecture to protect the rights and privileges of ownership in the digital realm. Its role may be seen as that of a records-keeper and manufacturer. the Transactor server performs a host of critical operations including: • • • • • creating new user accounts . the protecting purchase-related data from tampering. or valuable services. and relevance to application developers. By authenticating users.both end users and merchants creating new products or product groups (called universes) creating LEDO units (actual product instances produced at time of purchase) validating ownership of units (preventing misrepresentation of ownership) listing new products and used units for sale 2 . LEDO objects embody a new value model for online commerce. Transactor Server The Transactor server is the transactional authority within the system. the Transactor system is designed for integration into new and existing network-aware applications. Simplified API's at the client and server allow developers to access features without requiring low-level tinkering. Built as an enabling framework. customers and merchants alike. products and units throughout the system altering these records when appropriate responding to queries regarding these records Responsibilities With its authority and control of the records. Interfacing with the Transactor database.Introduction The Transactor system allows you to create. sell and resell safely and securely a new type of digital property called “limited edition digital object” (LEDO™) products. System Components The Transactor system is best described by dividing it along its hierarchical tiers. securing communication channels. digital receipts.

The Biz is a collection of behaviors and operations which can be customized to create the developer's envisioned online business. via an authenticated. via a Payment Gateway the Admin Tool. three entities: • • • a Biz Framework. encrypted protocol called a T-Channel a payment processor. The Biz allows end users to enter its environment (store. If the Biz is fraudulent. the Biz Framework is responsible for: • • • Authenticating and encrypting communication from Transactor clients Transferring Units into and out of Use within the Biz environment Placing Units for resale or removing them from resale 3 . LEDO products representing goods or services. digital service providers. and more. essentially shutting it down (or at least cutting off its Transactor functionality). Biz Framework The Biz Framework is essentially the online business. A Biz is authorized to do business by a Transactor server. application developers can commerce-enable almost any type of online business including virtual shopping malls. or responds to messages from. privileges or rights can be exchanged using the Biz Framework's operations. It acts as a forum or medium where commerce takes place. The Biz is modified to manage everything from end user perception of the space to the business rules and policies driving it. proceeds to conduct business. customer relationship services. Starting with the Biz Framework.• • transferring ownership of products or units Implementing Payment Schemes (interfacing with payment processors) Relationships The Transactor server communicates with. it authenticates the user's identity via a check with the Transactor server. the T-server may revoke its certificate. and if all is well. The Biz Framework is the single most important level of the Transactor system to application developers as it is the place where the business (application) is defined. the Transactor system administration tool The only part of the Transactor server that application developers will ever have to be concerned with is the T-Channel protocol. They will use this secure communication channel to request the T-server to perform its operations. online content sales and special events. game or other). Responsibilities In addition to requesting the Transactor server to perform the operations listed above. networked entertainment forums. website. The certificate allows the Biz to communicate with the T-server and make the queries essential to operate its business.

a web page or any networked application. The client stores specific user data such as digital keys. buy or use LEDO units. The Transactor client has a one-to-many relationship with Biz Frameworks. and confirm ownership of LEDO units 4 .• Listing available Previews of Products for sale to end-users Relationships The Biz Framework mediates between the Transactor client and the Transactor server. Transactor Client The client is the reciprocal of the Biz. It is the customer—or more precisely. the code on the client machine that represents the end user in conversations with a Biz. post LEDO units for resale. This is logical of course. The client can be built into a game. The Transactor client's primary functions are to manage a Transactor user's objects and information at the end user machines. depending upon the client request received. While every store has the right to control customers within their own store. see product lists. Application developers can however customize the appearance and context of the Transactor Client and how it is accessed. Application developers can integrate these operations into their own applications. as well as information about the Transactor system as a whole. The Biz Framework will either respond directly to requests received from the Client or ask the Transactor server to perform an operation. The Transactor system is driven by requests from the client. but cannot alter their functionality. Responsibilities The client provides a number of operations. and to initiate communication with Biz Frameworks. Whereas the Biz is deliberate flexible and open to modification by application developers. such as Biz network addresses and product advertisements. see what products are for sale. use a LEDO in an online space. The underlying operations will be the same. inventory. Every request is sent by the client to a Biz which then either responds directly or sends a request of its own to a Transactor server. they don’t have the right to control customers in other stores. buy a LEDO. Each end user need only have one client. and login data. Client operations include: • • • • • Logging in or out of user account Listing Owned Units (view inventory) Showing Locally Held Advertisements (previews) Authenticating and encrypting communication with Biz Frameworks Sending requests to create new user accounts. the client is a fairly fixed collection of operations that application developers integrate without changing. These requests are sent whenever an end user attempts to connect to a Biz. and so forth. certificates.

5 .Relationships The client resides on the end-user's machine and communicates with the Biz Framework via a proprietary secure protocol. Transactor clients never communicate directly with a Transactor server.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->