OmniDocs Transaction components follow the J2EE standards and can be deployed on any standard application server. An XML based client is available for easy interfacing with OmniDocs. OmniDocs JNDI client provides a simplified single point interface with OmniDocs engine. It takes the XML as an input argument and on success return the output xml. On any exception, error code XML is returned.
Sample call for using OmniDocs JNDI client
SupposeIf the youUser wants to perform a sSearch for document, then the User you
have has to follow the
following steps: given below
1. Make an object of the class NGOXMLCallBroker available in the ejbclient.jar.
For example,.g.
NGOXMLCallBroker xmlCallBroker = new NGOXMLCallBroker();
Class Name: NGOXMLCallBroker
Package Name: com.newgen.omni.jts.client;
2. In order to make any XML call to Server, use jumptofunction, of the NGOXMLCallBroker class by passing input XML as an argument. Which return String type output that is in standard XML format.
StrOutputXml=xmlCallBroker.jumpToFunction (strInputXml);
Where
StrInputXml is input xml
StrOutputXml is output xml
Parse the StrOutputXml for using results.
Note: Authentication is
the first step for using OmniDocs API. A call to NGOConnectcabinet can be made,
which results a session id, termed as UserDBId, unique for a session.
This id has to be passed in subsequent calls made to OmniDocs engine.