Concert is a $10 billion start-up designed and built from the ground up to serve customers with a new approach to products and services. We are transforming the global communications landscape by redefining the way our customers do business. We needed to build a web-based traffic reporting system that allowed Concert customer reps to order different kinds of reports on behalf of the customer. The customer will then receive periodic reports on their call centers and their number of 1-800 calls received. The order for the reports are saved in our database and transferred through a CORBA interface to an external system. The architecture is Java clients, Java servlets communicating IIOP to the database server.
For the critical and complex task of relational database connectivity, we used JDX and built this system in record-time. We had used Roguewave before and it required a lot more coding to build a layer around the database. With JDX, we simply defined the object-relational mapping in an intuitive declarative way and used powerful JDX APIs to retrieve and save data in our database. JDX has proven to be a high-performance, scalable and reliable technology.
TeleMed is a component-based multimedia distributed electronic medical record system built on the CORBAmed interface standards. All of the components are written in Java for extreme portability and are available as open source. These include the Person Identification Service, Clinical Observation Access Service, a simple Lexical Query Service and an early implementation of the Resource Access Decision Service. Security is managed with public private key encryption using software and hardware keys. The software has been deployed in some rural clinics in Northern New Mexico and the client has been deployed over the internet to numerous users around the world.
Persistence in the various services is handled through an abstract interface which enables us to use object databases or relational databases. When connecting to relational databases, we utilize the JDX software from Software Tree. This hides the idiosyncrasies of the various relational databases so that we can switch databases at runtime without any recompilation. It has proven to be a powerful and simplifying tool for handling persistence. Using it we are able to work with very small footprint Java databases as well as MS SQL server and Oracle databases without any changes in our code. It has been very reliable and appears to have little performance penalty over connecting directly with the relational database.
Dr. Dave Forslund, Deputy Director, Advanced Computing Lab
We needed a simple yet industrial-strength way of reading and writing objects to our Enterprise Master Member Index database. JDX gave us both a simple API and a scalable solution that didn't require a large technology commitment (i.e. App Server, ORB, etc.).
What JDX allowed us to do is focus on the object design of our own internal objects and ignore the database constraints of the vendor's data model, knowing that we could map our objects back to their data model easily. It will also allow us the flexibility of mapping to another data model later, while maintaining the integrity of our object model. Additionally, technical support and additional assistance on more advanced connection management issues reduced our development time tremendously. The bottom line savings for us was in terms of efficient use of development time. JDX allowed developers to focus more on the contents of the object model and less on the mechanics of persisting that model. It also decreased our time to develop our product.
Kesmai brings multiplayer computer gaming to the Internet. We need the ability to track thousands of customers and to centrally configure our custom application gaming servers. Java and JDBC were selected for rapid application development around an Oracle8 database back end server. We chose JDX as our object-to-relational mapping product to further accelerate development and time to market.
JDX enables us to take advantage of JDBC without having to code to the JDBC API. This has accelerated our project development and time to market. I have found it relatively simple to evolve the data and object models, letting JDX do much of the query work internally. I did not encounter any modeling or query requirements in our complex application for which JDX did not have a solution.