These instructions are for setting up Oracle JDeveloper 9.0.3 or above for Oracle 9i. If you are using any other version, contact HiT Software Technical Support, xml-support@hitsw.com.
Copy the jar files jAlloraJDeveloper.jar
and jAlloraJDeveloperMapper.jar from
jallora-3.1-x/lib/jdeveloper to JDEV_INSTALL_DIR\jdev\lib\ext.
Edit the jallora-3.1-x/bin/jdbc-config.xml file to add your JDBC driver and connection URL.
Make a backup copy of the file JDEV_INSTALL_DIR\jdev\bin\jdev.conf.
Add the following 3 lines to the jdev.conf
file, replacing C:/jAllora-3.1-x
with the directory in which jAllora was installed.
Make sure all pathnames use the "/" character as the file
separator, even when using the Windows operating system.
AddVMOption -Dcom.hitsw.mapper.jAlloraHomeDirectory=C:/jAllora-3.1-x
AddVMOption -Dcom.hitsw.mapper.jdbcConfigFile=C:/jAllora-3.1-x/bin/jdbc_config.xml
AddJavaLibPath C:/jAllora-3.1-x/lib
Optionally, append the
following to the jdev.conf file
to generate traces for both jAllora Mapper and jAllora engine activity.
For jAllora Mapper traces, append:
AddVMOption -Dcom.hitsw.mapper.debugLevel=1
For jAllora engine traces (activated when running wizards you have
created or when marshalling/unmarshalling in the Mapper), append and edit
ENGINE_TRACE_FILE_NAME:
AddVMOption -Dcom.hitsw.xml.databinding.traceFlag=true
AddVMOption -Dcom.hitsw.xml.databinding.traceStream=ENGINE_TRACE_FILE_NAME
Start (or restart) JDeveloper.
Three menu items have been added to the "Tools" menu:
Marshal Data from RDB to XML
Unmarshal Data from XML to RDB
Start the jAllora Mapper