This feature is provided as a jar (use Save link target as...) file ready to use with Oracle JDeveloper 9.0.3+. To install it, you need to follow these steps:

1. Copy AddinCms.jar to [JDEV_HOME/jdev/lib/ext] directory.
2. Configure the CmsConfig.xml file.
3. Test it.

This directoy is located under the [JDEV_HOME]/jdev/lib/ext. Copy AddinCms.jar file to this directory

Unix:

	cp [CMS_HOME]/deploy/AddinCms.jar [JDEV_HOME]/jdev/lib/ext

Windows:

	copy [CMS_HOME]\deploy\AddinCms.jar [JDEV_HOME]\jdev\lib\ext

This is actually telling JDeveloper to include the addin jar file in its classpath and register it to the system.

Once the jar is copied you should restart JDeveloper to view the Addin.

CmsConfig.xml file is a simplified version of CMS Config file which tells to the CMS Addin Upload which repository is used for storing the pages, the upload path and so on.

This file is located under the Project Directory, directory where ProjectName.jpr file resides.

To create or edit this file, DBPrism CMS 2.0.1+ includes a new JDeveloper Wizard which provides the creation facilities of this file by selecting a database node into the System Navigator.

First you has to select a node into System Navigator configured with the database connection information for the CMS repository.

Then, after the welcome page, this wizard will ask you for the information about the CMS user's credentials. It means the username and password used by the CMS Security system to validate the access.

Finally you has to specify some upload parameters such as the upload path (originally is configured to the HTML root directory of your Project, Verbose functionality and so on.

This wizard will create a CmsConfig.xml file into the project root directory and will add it to the list of files includes into the project.

An XML file added into the the project root directory will showed by the System Navigator into the Miscellanous files of the HTML sources nodes.

The generated XML file is automatically opened into the the IDE XML Editor, check for the values stored and close it.

Depending on the node to be imported this Addin takes different behaviour. That is:

1. Document of type XML, parsed as document-v10.dtd syntax and then upload to the CMS.
2. Document of type Text, imported directly (without parsing) to the CLOB column of the CMS.
3. OpenOffice 1.x Writer Documents, transformed with the default stylesheet defined in the CmsConfig.xml file, then parsed as document-v10.dtd, and finally upload to the CMS (DBPrism CMS includes an stylesheet named sxw2document-v10.xsl which provides a traslation templates of sxw files to DBPrism CMS format). Documents which include images are splited into the content XML file, stored into the CMS, and the images stored into the DBPrism upload repository, this repository is available using mod_plsql emulation zone.
4. Document of type HTML, transformed with the default stylesheet defined in the CmsConfig.xml file, then parsed as document-v10.dtd, and finally upload to the CMS.
5. Project nodes (bulk upload), for every node into the project import it using the previous rules.

Only documents which reside into the LoadPath defined on CmsConfig.xml file are taken into account. It mean, a node (Document) does not start with the pathname defined in the parameter LoadPath will not be evaluated, if this file resides into the load path this path is extracted and then saved into the CMS repository with the relative path. For example if LoadPath is file:/home/oracle8i/cms/dbprism/xdocs a document which phisically resides into file:/home/oracle8i/cms/dbprism/xdocs/docs/Readme.xml will be stored into the CMS system as /docs/Readme.xml

Documents with path starting with TemplatePath will also marked as documents templates, these templates are used by the frontend application to create documents using templating mechanism.

To upload OpenOffice 1.0 Writer documents (.sxw), its necessary to configure Oracle JDeveloper whith the correct mapping for this file type. Go to the menu Tools->Preferences...->File Types and, in the column Recognized file types: choose JarNode, then press the button Add... and type .sxw extension, confirm this extension, restart your JDeveloper and add your OpenOffice Writer document to the desired project.