This section defines the problem
and its possible solution while installing Omnidocs component. It also explains
how a problem can be debugged while during development.
Installation and configuration
related problem
This section lists the problems
that can be faced by developers while installing Omnidocs component.
Java Transaction Server
1.
There can be error for
insufficient disk space. Create space in the drive in which you want to install
and then try again or install it in some other drive.
2.
If JRE is not installed error
will come, first install the JRE 1.3 and then install JTS.
3.
After installing JTS when you are
associating a database cabinet Cabinet it will be associated but when user User tests it a generic
error can come “Connection test failed. Reason for it can be
§
There is no physical connection
between the JTS machine and database serverServer machine. Make a
physical connection between two machines and try again.
§
In case of SQL Server, Check the
DSN name provided by user. Until and unless user changes it is same as that of
cabinet name. In case of oracle check The TSN Service configuration. Reason can
be that service name is wrong.
§
Cabinet name specified is wrong.
Such cabinet does not exist on the specified serverServer.
§
Username and password provided
for testing the connection is wrong.
§
Server specified is not running
or database service is not running on the serverServer.
§
Database Server already has
maximum no of connections and now it cannot create any other connections. First
kill the connections in the database and then try again
4.
While associating a cabinet Cabinet if user has
specified maximum connections allowed as less then minimum connections then
following error is generated “Maximum Database connection can’t be less then
minimum”. Check the maximum and minimum database connections provided by the userUser.
5.
When we start JTS following error
can come.
Unable to connect to database {Name of the database}: Java,SqlException, :SqlException:
Error in Innitializining the dDatabase managerManager. Reason for this
error is that there is no physical connection between the JTS machine and
Database serverServer machine.
6.
In general user should check the
version of ODBC also if some problem is there, it is recommended that user
should install the latest version of MDAC (Microsoft Data Access control).
7.
If some problem is coming after
associating a cabinet, user can delete the serverServer pProperties.ini from the
installation directory and associate the cabinet Cabinet again.
SMS
1. There can be error for insufficient disk space. Create space in the
drive in which you want to install and then try again or install it in some
other drive.
Cabinet Creation
Omnidocs
cabinet
Cabinet creation Creation utility Utility dumps every
error in error. Log file in the directory where OmniDocs cabinet Cabinet manager Manager is installed.
§
There can be error for
insufficient disk space to install OmniDocs cabinet Manager. Create enough
space in the driver or install in some another drive.
§
When user tries to create a
cabinet on some machine on which database serverServer is not installed.
For e.g. if user is creating a SQL database and gives serverServer name as “A”, in
case SQL serverServer is not installed on machine “A” then following
error can come “Specified SQL ServerServer not found”.
§
While creating a cabinet an error
can come as “Login failed for user ss”. Reason for it can be that username Username or password Password specified for
connecting to database is wrong.
§
While creating an oracle database
cabinet
Cabinet an
error can come as “Service not found: The network Adapter could not establish
the connection”. Reason for it can be that Oracle TNS service is not running on
specified Port. Check the TNS port specified.
§
While creating an oracle database
cabinet
Cabinet an
error can come as “Service not found: connection refused”. Reason for it is
that SID provided by user User is Invalid.
Development related problem
This
section lists the resources available and process to follow to debug any
problem while development process
For
debugging following information can be used.
1. InputXml – To view the InputXml being sent to Java Transaction
Server set the Debug parameter passed in execute method of DMSCallBroker. A log
file name inputxml.log is generated .All inputXml calls being sent to JTS
are dumped here. This is applicable only in case of Java Bean API, in case of
XML API Application has to dump the InputXml in some file, which can be used to
debug any problem.
2. OutputXml – To view the complete output Xml being received from
the serverServer. View the temp
folder in the folder where the JTS is installed. A file by the name of call
will be generated for each call.
3. Message corresponding to Error Codes - To find out the meaning
of error
Error codes Codes sent by Java
Transaction Server refers to the appendix.
Following
are the tips to debug in case some problem occurs during application
development.
§
OmniDocs Transaction serverServer console displays
all calls received together with the client name from which the call is
received and time taken to execute the call.
§
Image serverServer generates
jerr.log for any error that may occur when storing or retrieving documents.
In
order to debug any problem user User can follow the steps given below:
§
View InputXml logged by the
Application and compare it with sample Xml provided.
§
View outputXml logged by
Transaction serverServer and user can compare it with sample
xml provided. There can be a problem that some information is not returned in
the outputxml and client application is parsing for it.
§
User can see the description of
error with each call on the basis of error code received in OutputXML.
§
In case if there is any error
from Image serverServer user can see the log file generated by
Image serverServer client in
c:\\jerr.log.