Introduction

 

Java Bean API provides a flexible wrapper over XML API to ease the development of Document Management System.

Java Bean APIs encapsulates the complexities of XML and provides parameterized functions for

·          Generating InputXml

·          Executing InputXml

·          Using OutputXml

API for XML generation

InputXml can be generated using class DMSInputXml in package com.newgen.dmsapi. Functions are exposed for each call. These functions take values for tags that are to be appended in InputXml as input parameters. All input parameters are of String type and the output of all these functions is always a String, which is in standard XML format.

                                               

§          Class Name: DMSInputXml

§          Package:  com.newgen.dmsapi

API for Execution

Execution of OmniDocs API through JTS

 

Class DMSCallBroker communicates with JTS over the socket and returns the OutputXml.

 

§                      Class Name: DMSCallBroker

§                      Package:  com.newgen.dmsapi

 

The API provides static overloaded execute function in class DMSCallBroker to communicate with JTS.  Invocation of this function is as follows.

 

First prototype takes 4 parameters viz. InputXml, Java Transaction Server Ip and OmniDocs Transaction Server Port and debug level.

Debug level signifies the generation of log. For value 0 of debug level no log is generated and for value 1 of debug level all input xml are dumped in a file named inputxml.log

 

The second prototype takes 3 parameters viz. InputXml, Socket connection to Java Transaction Server, and debug level. Applications can develop Connection pooling logic of their own and use this function.

 

Execution of OmniDocs API through JNDI

           

Class DMSCallBroker have overloaded method that communicates with JTS over the RMI-IIOP and returns the Output XML as String Object.

 

·          Class Name: DMSCallBroker

·          Package:  com.newgen.dmsapi

 

The API provides static overloaded execute function in class DMSCallBroker to communicate with JTS.  Invocation of this function is as follows.

 

Method takes only one parameter viz. InputXML, which is of type String.

API for Using OutputXml

The outputXML received from OmniDocs will have to be parsed to retrieve information.

DMSXmlResponse and DMSXmlList simplify parsing.

 

·          Class Name: DMSOutputXml

·          Package:  com.newgen.dmsapi