With the advent of ObjEx XMLQuery it is actually easier to write SOA based applications that utilize CA IDMS than it is to write them to use relational databases!
ObjEx XMLQuery for CA IDMS offers an entirely new capability for CA IDMS Integration. It provides the ability to directly utilize and update IDMS data from within .NET and JAVA applications and allows IDMS to be a full participant in your Service Oriented Architecture (SOA). XMLQuery eliminates the need to write complex, customized navigation programs, as that task is now handled by the ObjEx XML Query Engine. Any web service client can now take full advantage of your CA IDMS database content. And it can be done in minutes, not weeks or months.
ObjEx XMLQuery makes interfacing your .NET or JAVA applications to CA IDMS straightforward and simple. Too often, prior to XMLQuery, the need to interact with an IDMS database became an entire project rather than the technology footnote that it should be. Project teams have used screen scrapers, replication, hand-coded navigation procedures, and custom application logic at great expense. These techniques are no longer required. Now you can directly access and update your IDMS network data without compromising its CODASYL design.
An entire IDMS structure can be retrieved and subsequently updated using two web method invocations.
Your networked application developers call a simple web service method which returns a properly formed XML document containing the record and set content requested. At their option, they may update the document and return it. XMLQuery will automatically detect the changes and update IDMS accordingly. In addition, your developers may also choose to directly use XMLQuery in much the same way as they do for any other data source (Ingres, Oracle, etc.). This creates a natural experience leveraging the knowledge they already possess. Developers need very little understanding of IDMS concepts and facilities, as these are handled for them by the ObjEx XML Query Engine. You can develop and deploy new, modern applications, eliminating the need to convert existing applications to a new database. Throughout the process, your DBAs are in control of what goes into and out of your databases.
ObjEx has connected our well-established IDMS trigger technology to our XMLQuery Engine to create a powerful XML publishing facility for CA IDMS. It detects changes to IDMS data, uses XMLQuery to extract data related to the event from IDMS, and sends it to any web service on the cloud - all without writing IDMS extract programs.
ObjEx gives you more ways for you to leverage your investment in CA IDMS. ObjEx XMLQuery and ObjEx XML Publisher and Replicator allow you to, without compromise, fully leverage your IDMS investment today and well into the future.
How it Works
Your IDMS DBA downloads and stores an IDMS Schema into a local Meta Database. ObjEx XMLQuery is type-aware, so it is necessary to add some additional Metadata. Date fields are identified and the DBA chooses which COBOL elements and group elements will be made available to developers as XML elements. Depending on site preferences, either the DBA or the developer creates Query Plans using the Query Plan Builder. The Query Plans are named and stored into the Meta Database. Plans may begin with an OBTAIN using CALC, DBKEY, AREA SWEEP, SYSTEM OWNED INDEX (SOI) scan, partial SOI scan, or unique SOI read. From there the query plan may traverse the schema, iterating through set members and obtaining owners as needed. All of this occurs with the same high-level of performance that would occur in an IDMS application performing the same task. IDMS sees XMLQuery as an external rununit, just like a batch job, only better.
And with a single click, XMLQuery can deploy query plans to a web service server, instantly making IDMS access available to any Web Service client.
At runtime, your application executes these Query Plans. In a single call, XMLQuery returns a fully typed XML Document containing a collection of data tables and their relationships. This is an industry standard XML Document conforming to the schema (XSD) document generated at design time. In the .Net environment this XML may be used to construct a fully typed DataSet object. In the Java environment, tools like JAXB can be used to generate working Java classes conforming to the schema.
The resulting document is easily used directly in .NET, Java or SOA orchestration tools such as Ivory from GT Software, BizTalk from Microsoft and many others. There is one DataTable for each record type in the plan containing one row for each IDMS record retrieved. Each row contains the elements as specified by the IDMS DBA. The row also contains the IDMS dbkey for the records and the dbkeys of each parent record if any were selected by the plan. There is no fixed limit on the size of the returned XML document.
The application may change the data in the XML document and call the Update method. During update, XMLQuery determines what changed and applies those changes to IDMS. STORE, MODIFY, CONNECT, DISCONNECT and ERASE DML commands are executed automatically as required.
For the first time you can use your IDMS data more easily than you could if it was in a relational database!
Meet with the next distributed application team that needs IDMS data without fear because you can deliver.
Rapidly integrate CA IDMS with .NET, JAVA, etc. with less effort than ever before
- · Fetch an entire structured set of data with a single call
- · Apply multiple changes to the retrieved data using a single Update call.
Superior native performance
Build applications, web services, and web sites that directly access IDMS databases using the latest XML data technologies
Your IDMS databases can now fully participate in your Service Oriented Architecture without compromising their original network design
Expanded third-party integration options for your IDMS environment
- · Adapt to the latest XML Messaging systems
- · Direct to reporting tools, XSD, and document
- · Direct to web site XSL transformation
- · Forms the foundation for ObjEx XML Publisher for CA IDMS
Modern deliverables to your user community without rewriting existing applications
No cross-training required; distributed developers will intuitively understand