OTIF version 1.4.0 - the Open Tool Integration Framework
How to use the package
After successfully installing the OTIF framework you will have an OTIF item
in the Start Menu/Programs. There are couples of shortcuts in this
folder which you may click on to start, manage or work with the framework.
-
To start the Backplane server: click on the Start Backplane. It
will start the Backplane server process and the OTIF framework will be running.
Note: At the first run the Backplane server will find an open port to
listen on. It can be changed at any time by changing the backplane_server_url.config
file which will exist in the bin folder of the installation directory
after the first run. This file specifies the IP address and the PORT
number of the computer which runs the Backplane server. You may change
the PORT number at any time; just remember to restart the Backplane
server after it.
-
To check the status of the framework: click on the Manage Backplane.
It will show you the status of the Backplane server (registered paradigm,
translators, etc.). The manager application uses authentication. The default
password is blank.
Right after the first installation you could not do much with the framework
because there are no paradigms and translators registered. So our next step is
to register a workflow - a tool chain - which specifies some paradigms and
translators.
You may create your own workflow model or if you installed any of the OTIF
Extensions you may find a demo workflow files in the Workflows folder.
-
To register a workflow: click on any of the file in the Workflows folder
and interpret it in the GME application. The interpreter will send the workflow
configuration information into the running Backplane server.
You may find more information about designing and interpreting workflows in the
OTIF_Usage_Guide.pdf file in the Documents folder.
After successfully interpreting a workflow we are able to send, translate and
fetch some documents.
-
To work with documents: you may click on the Generic ToolAdaptor application.
You can publish or fetch with this application any kind of document which has a
paradigm registered in the Backplane server.
-
At the first screen you may specify a tool adaptor type to login into the
Backplane server. Your Generic ToolAdaptor will act like the specified tool
adaptor type.
-
Use the Publish
button to publish a document. You can select the appropriate paradigm and fill
out the parameters field.
-
Use the Subscribe
button to subscribe to a paradigm. After subscription you will be notified if a
document arrives.
-
Use the Unsubscribe button to unsubscribe a paradigm.
If you would like to play with the framework you may look at
Getting Started with Demo. This sample contains a
translators, sample files and a pre-defined workflow model to play with.
Other useful documentations
If you have installed any of the OTIF extensions you may find further Getting
Started documentations about specific information of the
extension module in your installation directory.
Dependencies
This package depends on (and fully compatible with):
-
GME 5 r5.9.21 application
-
UDM v3.00 library
-
Xalan version 1.8
-
Xerces version 2.5.0
Directory structure
/bin |
binary executables with DLL libraries |
/bin/paradigms |
paradigm files |
/bin/translators |
translator applications |
/bin/xsl_translators |
xsl translator files and the generic XSLT translator |
/Documents |
OTIF documentations and the workflow engine GME paradigm |
/Documents/icons |
icon files of the workflow engine GME paradigm |
/Include |
include files |
/Include/ToolAdaptor |
ToolAdaptor include file |
/Include/UdmCORBA |
UdmCORBA include files |
/Lib |
library files |
/Lib/tao |
ACE/TAO static libraries |
/Lib/ToolAdaptor |
ToolAdaptor static libraries |
/Lib/UdmCORBA |
UdmCORBA static libraries |
-
/bin directory: you may find the core applications and all the DLL files
which are used by the core and example applications.
-
/bin/paradigms directory: you may find here the uml.xml paradigm file.
Further paradigm files generated by the user should be stored in this directory
because the framework uses this directory to search for paradigm files. These
paradigm files are generated by the GME application.
-
/bin/translators directory: further translators implemented by the user
should be stored in this directory because the framework uses this directory to
search for the translator applications.
-
/bin/xsl_translators directory: you may find the generic xslt_translator
application which uses standalone xsl stylesheet files to translate documents
and an xsl stylesheet file called identity_transformation.xsl which implements
the identical transformation.
Further xslt translators implemented by the user should be stored in this
directory because the framework uses this directory to search for the xslt
translators.
-
/Documents directory: you may find all related documentation of the OTIF
project. However you may read the UDM documentation if you have difficulties to
understand the example source files.
There is the CORBA IDL files (otif.idl, udmcorba.idl) used by the framework and
the workflow engine GME paradigm and icons directory corresponding to the
paradigm.
-
/Include directory: you may find two subdirectories which contain the
ToolAdaptor and the UdmCORBA include files. These are used only if you
implement your own ToolAdaptor or Translator applications.
-
/Lib directory: you may find three subdirectories which contain the
ACE/TAO, the ToolAdaptor and the UdmCORBA debug and release mode static library
files. These are used only if you implement your own ToolAdaptor or Translator
applications.
Contact and support
If you have any question, please contact:
Zsolt Kalmar
Upgrades, accessories are posted to the
project website
Credits