TriCoron
spacer

Your Relational Databases as a Web Service

Contents
Executive Summary
Important PRO-SOA Capabilities to Achieve SLR
  Present your relational databases as Web Services
  Programming Language Independence
  Deploy to the desktop client and server...
  Visual Studio.NET Clients/Web Sites And Middleware...
Persistent Relational Objects for SOA
  PRO-SOA Capabilities
  PRO-SOA Enables Web Services Integration...
Compatibility and Interoperability Matrix
  PRO-SOA Interoperability with the Technology...
Evaluate PRO-SOA Now
  .NET EXE
  VS .NET SLN
  ARCHIVE
  PRO-Objects-TRIAL
  PRO-Objects CE

Abstract: Service Data Objects are proving to be a necessary component for any successful Service Oriented Architecture. Specifically, the ability to access relational databases as industry standard and interoperable web services is proving critical for any business to implement a coherent and practical Service Oriented Architecture.

Executive Summary

What is PRO-SOA?

PRO-SOA combines multiple Microsoft and Oracle databases into one logical, transactional web service. There is no practical limit as to the number of databases and tables that can be combined into a web service.

What does PRO-SOA do?

PRO-SOA allows your application developers to access and update your relational databases as objects though SOAP (Simple Object Access Protocol). Your application developers can use any programming language they want and their favorite development tools.

Can I use PRO-SOA?

Probably. PRO-SOA uses a lightweight database and access and update algorithm that does not interfere with existing applications that are currently using the databases. PRO-SOA automatically supports all character sets and languages, including East Asian character sets such as SJIS, Kanji, Katakana and Hiragana. PRO-SOA will operate and integrate well into your existing production environments as PRO-SOA runs on anything: Windows, Linux or RISC and Mainframe architectures.

How do I use PRO-SOA?

Easily, as it happens. If you can connect to a database and use a mouse, you can use the three-step wizard interface to scan the schema tables of your relational databases to automatically acquire database metadata, and then generate a persistent object web service. PRO-SOA is designed for anyone, at any level of technical expertise, to immediately be productive with web services technologies.

Important PRO-SOA Capabilities to Achieve Service Level Requirements

Present your relational databases as Web Services
Performance, Reliability, Scalability, Extensibility and Maintainability

An industry-standard and best practices method to integrate new or existing relational databases into a Service Oriented Architecture:

Programming Language Independence (C++, Java, Basic, C#, J#, COBOL, many others)
Portability, Extensibility and Maintainability

Reusing existing information technology assets more cost effective than replacing working, reliable and dependable business software.

Deploy to the desktop client and server platform of your choice.
Performance, Portability, Extensibility, Manageability and Maintainability

Give architects and engineers the ability to craft client-server Web Services enabled business applications for Windows clients while simultaneously distributing and deploying the web service server code on Windows, UNIX RISC, Linux, midrange and mainframe servers. Web services are also a great way to build online, high availability web applications.

Visual Studio.NET Clients / Web Sites And Middleware Server Platforms
Portability, Extensibility, Manageability, Maintainability and Security

The popular and pervasive Visual Studio.NET is an effective tool to build applications for Windows platforms, both client and server. Windows.Forms have dramatically simplified the process of building open, XML-based software applications for Windows desktops while hiding the complexities of the win32/MFC/AFX APIs that .NET managed code replaces.

The .NET framework, in addition to simplifying the API to Windows, provides integrated XML programming and data interchange interfaces. The most practical of these .NET XML APIs in Visual Studio.NET is an open, standard interface from Windows to the Service Oriented Architectures of other vendors, such as IBM, BEA, and Sun. Yet, curiously, SOA products from IBM, BEA, Sun, and others do not offer an easy, seamless, interoperable way to immediately use relational databases in a Service Oriented Architecture, as does PRO-SOA. PRO-SOA gives architects, business analysts and programmers the ability to craft client server business applications for Windows clients, where the server code is distributed over Windows, UNIX RISC, Linux, Mainframe and other servers.

What would it mean to you if there were a way to take your relational databases (on any platform) and wrap those databases into a Web Service that could be instantly inspected, assimilated, and used by Visual Studio.NET? Could you achieve a practical and useful methodology to build adaptable graphical business applications using your organization’s relational enterprise data, wherever it resides?

PRO-SOA: Persistent Relational Objects for Service Oriented Architectures

PRO-SOA Capabilities

PRO-SOA can distill any number of databases into a common set of operations, as set forth by Sun's well-known Enterprise Blueprints[1]. In Visual Studio.NET, for example, you will see your databases through these concise and coherent web service operations:

PersistentObject Web Service
This web service view of your relational data is a DYNAMIC INTERFACE. Meaning this web service view of your relational databases is the same, no matter the vendor of the database, and is independent of the physical relational schemas and table organization. [2]

PRO-SOA Enables Web Services Integration Between .NET and J2EE

It's not uncommon to find both .NET and J2EE in today's enterprises. Integration between the .NET and J2EE is most easily accomplished with Web Services. PRO-SOA assists in making your database information web service enabled in a standard way that seamlessly interoperates between .NET and J2EE.

Compatibility and Interoperability Matrix

PRO-SOA Interoperability with the Technology You Use Today and Desire for Tomorrow

PRO-SOA has been certified with the following technologies. Choices are not mutually exclusive. For example, you can use PRO-SOA to create a transactional web service that accesses any number of Oracle and SQL Server databases concurrently. Choose your software engineering software and deploy to production deployment using commercial and Open Source enterprise solutions, or use your current, familiar engineering and production software and utilities.

Environment Microsoft .NET J2EE Tech Notes The PRO-SOA Advantage
Platform & Operating
Systems
Intel, AMD x86, RISC
Windows XP Pro
Windows 2000
Windows 2003
Windows 2000
Windows 2003
UNIX (Solaris 7, 8, 9
HP UX 10)
Linux
All PRO-SOA server code is platform neutral and vendor independent. You can also mix platforms within a deployment. Seamlessly integrate the mixture of desktop and server platforms that are best in meeting Service Level Requirements and deploy systems on the most cost-effective hardware and software.
Databases
SQL Server 2000
Oracle 7, 8i, & 9i
(SE & EE)
SQL Server 2000
Oracle 7, 8i, & 9i
(SE & EE)
Multiple Microsoft and Oracle databases may be combined into one logical web service. There is no practical limit as to the number of databases that can be combined into a web service. Combine mixed and multiple database environments into a single, accessible and adaptable enterprise Service Database Object to reduce transaction costs and increase sales.
Programming
Languages
Visual Basic
C#
C, C++
J#
Java 1.3 and up Other languages that can communicate via SOAP are also accommodated. XML & SOAP data communications for reusing software written in various programming languages. Reusing existing software is almost always more economical than rewriting from-scratch.
Application
Servers
JBoss
IBM WebSphere
BEA WebLogic
JBoss
IBM WebSphere
BEA WebLogic
Other J2EE application servers can be easily accommodated, as PRO-SOA service code is vendor independent. Please see the release notes for details. Immediately utilize Oracle and/or SQL Server databases as scalable, reliable, and high performance transactional Web Services.
Integrated
Development
Environments
Visual Studio.NET Eclipse
IBM WSAD
BEA WebLogic Workbench
Borland JBuilder
Any other WSDL-compliant IDE will communicate with PRO-SOA web services. No additional XML schemas are introduced into your environment. Software Engineers select and use their tools of choice so there is no new learning curve to absorb and no productivity drains. Get the most from what you already have!

Evaluate PRO-SOA Now

We offer several no cost, time efficient options to you to explore the extensive capabilities of PRO-SOA.

The starting point is to run a prebuilt C#.NET client you can download and run on your local workstation against TriCoron servers, using SOAP over the Internet. We send you all of the source code for you to inspect and recompile, if you so desire. This .NET client is very intuitive, works with any database schema and will look like this on your 32-bit Windows desktop:

.NET SOAP client interface.

Please take a moment to examine the following evaluation options that correlate to the amount of time you have to invest and the level of detail you require.

.NET EXE

Description:
Precompiled .NET Managed Code .EXE with source code
Why/Eval Action:
Execute interactive C#.NET persistent object SOAP client over Internet to TriCoron servers.
Expected Result:
Run a pre-built C# object access and update web service client.
Intercommunicate to TriCoron's servers to access and update the familiar Northwind database over SOAP using the Internet.
Prerequisites:
Windows 2000, XP, 2003
.NET Runtime
Internet connection, any speed
Information Required:
Valid e-mail address, we'll email you a download password at once.
Estimated Time Commitment:
.NET Runtime download (25 MB) and installation: 5 minutes
.NET persistent object SOAP client download and installation: 3 minutes
Run persistent object SOAP client: 3-5 minutes
Examine SOAP XML messages using SOAP monitor (optional): 3-5 minutes.

VS .NET SLN

Description:
Visual Studio.NET Project Workspace
Why/Eval Action:
Recompile C#.NET SOAP client on your workstation, run client against TriCoron web service servers, step through code
Expected Result:
Visual Studio .NET C# project workspace and build this C# SOAP client yourself with one stroke of the F5 key
Prerequisites:
Windows 2000, XP, 2003
Visual Studio .NET IDE with C# compiler
Internet connection, any speed
Information Required:
Valid e-mail address to receive download credentials.
Estimated Time Commitment:
Above steps in .NET EXE
+ Rebuild .EXE from source (3 seconds)
+ Time examining source code and stepping through, 10 minutes recommended
+ Optional: Source code review and Q&A with TriCoron engineering: 15 minutes

ARCHIVE

Description:
Multiplatform Enterprise Archive / EAR for JBoss
Why/Eval Action:
Run C# SOAP client against your servers, using your database.
Test with the C# SOAP client described above.
Expected Result:
Same result as above two steps, except much faster without SOAP Internet packet latency.
Prerequisites:
Client: 32 Bit Windows with VS.NET or .NET runtime
Server: 32 bit Windows or Linux w/ JDK 1.4
Database: SQL Server 2000 with Northwind database
Information Required:
Valid e-mail address, Name, Role, Company Name
Estimated Time Commitment:
Before above steps in VS .NET SLN:
+ JBoss Download and installation: 10 minutes
+ SQL Server 2000 download and installation, setup, apply service packs: 25 minutes
+ Download and installation of PRO-SOA web service: 5 minutes

PRO-Objects TRIAL

Description:
Full Function PRO-Objects release that includes both PRO-SOA and also PRO-JSP
Why/Eval Action:
Rebuild above archives by generating all source code, recompiling, and rebuilding EAR deployment from scratch.
Test with the C# SOAP client described above.
Expected Result:
Same as previous step in ARCHIVE, using Oracle DEMO and/or SQL Server 2000 Northwind
Prerequisites:
Same as above in ARCHIVE.
Information Required:
Valid e-mail address, Name, Role, Company Name
Estimated Time Commitment:
In addition to above steps:
+ Download and install PRO-Objects (5 minutes)
+ Generate Service Data Objects, support classes and web service using MSFT Northwind and/or ORCL DEMO databases (5-8 minutes)
+ Run Apache Ant build and deployment scripts (3 minutes)

PRO-Objects CE

Description:
Community Edition (No Charge)
Access, aggregate and update up to 12 tables and inter-table relationships within a single database schema.
No Charge Support:
Web-based and two priority phone incidents 90 days complimentary.
Why/Eval Action:
Using your databases, rebuild above archives by generating all source classes, recompiling, and rebuilding EAR deployment from scratch.
Test with the C# SOAP client described above, build and deploy an operational, commercial web service for your firm.
Expected Result:
Any Oracle and/or SQL Server DB
Generate, build, deploy and run a persistent object web service using your servers and your data.
Prerequisites:
JBoss, IBM WebSphere, and/or BEA WebLogic (see above technology comparability matrix).
Questions? Please feel free to discuss your goals and needed capabilities of PRO-SOA with a TriCoron Technical Consultant.
Information Required:
JBoss, IBM WebSphere, and/or BEA WebLogic (see above technology comparability matrix).
Questions? Please feel free to discuss your goals and needed capabilities of PRO-SOA with a TriCoron Technical Consultant.
Estimated Time Commitment:
Same as above, add 3 minutes to review auto-normalization of your Database metadata into meaningful Object and Attribute/Member names.

Evaluate now.

If you have any questions, would like to learn more, or would just like to give some feedback, please contact service@tricoron.com or call TriCoron Service at 1-866-SOATODAY.

[1] Sun's Enterprise Blueprints are online at http://java.sun.com/blueprints/enterprise
[2] A relevant exception is the two execSQL() web service operations. Direct SQL is used sparingly in the web service clients (if at all) and is typically reserved for very complex queries where object-based queries through a generalized object-based interface prove cumbersome. The SQL passed to a database is, and always will be, vendor dependent. However, the object-oriented load(), store(), create() and remove() web service operations are vendor independent and dynamic, by design. Run the example C# client and see first-hand.

 

Copyright © TriCoron 2004 All Rights Reserved Worldwide

Valid XHTML 1.0!