Note: depending on your system, you might have to use the endorsed mechanism to overwrite the JVM JAXP/Xerces/Xalan libraries. Situations were that might be needed include JDK1.4.2 + JWSDP 1.6, or even older versions of JDK1.4.2 + JWSDP 1.5. In those cases, you need to copy JAXP libraries from JWSDP to <JDK_HOME>/jre/lib/endorsed. If the directory does not exist, you have to create it. Tomcat should also require the libs to be copied to <TOMCAT_HOME>/common/endorsed directory.
To obtain the latest stable releases you need to download source packages from the download section:
tar -xzf omar-<release_version>-src.tar.gz
The directory containing the extracted files will be called omar.basedir for the rest of this document.
IMPORTANT: do not confuse omar.home and omar.basedir.
The source package includes all other dependecies (libraries) that are required, except for libraries provided by the JWSDP and the application server itself.
Binary packages are not available currently. However, the source distribution comes ready to be built and deployed.
Alternatively, you may check out the latest source tree from the CVS repository CVS checkoutprovides you with latest bug fixes and features. However latest CVS bits may be less stable than a packaged release. You may use the following command:
cvs -z3 -d:pserver:email@example.com:/cvsroot/ebxmlrr co -P omar
Yet another option is to use NetBeans to get the files from CVS for you. Check here how to configure it.
|JAVA_HOME||The home directory for JDK installation.||/usr/java/j2sdk1.4.2_08||c:\j2sdk1.4.0_08|
Make sure the Java runtime environment executable (e.g. <JAVA_HOME>/jre/bin/java.exe for Windows) and Java compiler executable (e.g. <JAVA_HOME>/bin/javac.exe for Windows) are in the environment variable PATH.
There are several configuration properties within several configuration files for omar. They are described in details here. Each property file is self documenting and describes each property within it.
While there is a large number of configuration properties, fortunately the defaults suffice in most cases. Here are some properties you might want to change:
||omar.properties||The properties are used to connect to the database via JDBC. The default
configuration is for Derby database, you don't need to change it if you want
to use it. Property sets for other databases are available in build.properties.|
** This porperties will be set from build.properties at build time.
|Registry Administrator Role Assignment:
||omar.properties||Configures the set of users that should be assigned the role of RegistryAdministrator and its associated "superuser" like privileges. This is useful if you are a registry administrator and want to add addition registry administrator.|
|Configuring a test user:||jaxr-ebxml.properties||The properties used to configure a user that is used by the automated regression tests. This is necessary only if you run automated regression tests. You should run regression tests if you are making code changes and submitting a patch to the project team for a bug fix or RFE.|
||build.properties||JWSDP home directory (e.g. /opt/jwsdp-1.6).|
|Tomcat (servlet container) configuration
||build.properties||Tomcat's home directory. In Windows environment, Tomcat path may include white spaces (e.g. c:\\Program Files\\Apache Tomcat 5.0.19\\) and things will still work if you leave spaces. Note that you MUST use either '/' or '\\' instead of '\'.|
The properties are used to connect to the database via JDBC. The default configuration is for Derby database, you don't need to change it if you want to use it. Example property sets for other databases are available in build.properties.
There are a few JDBC drivers in misc/lib directory (for source distribution or checkout from CVS), or you can get an updated copy of the driver for your database. You may need to consult the documentation of your database to find out the syntax of the URL.
Search the FAQ for database specific entries.
You need to build the source distribution in order to deploy OMAR. It can also be built directly from the CVS repository. Apache ant is used as scripting language and these are the steps to use it:
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog. You can set the variable e.g. in the Tomcat startup script. See SimpleLog and Commons Logging for more options that you can configure.
If you just want to try it out, you can use OMAR with preconfigured Derby database. For a production environment, you are recommended to use PostgreSQL version 7.1 or above as the database. There are (old) instructions on this page to setup PostgreSQL on Windows, although newer PostgreSQL should install in windows without any extra complications. Setup a database with name "omar_registry".
Open the text file <omar.basedir>/build.properties, which is created in section 6. Note that build.properties only takes effect at installation time (the runtime parameters are specified by omar.properties, omar-common.properties, repository.datasource.cfg and omar.xml deployment description in the AppServer). You should be able to find the following properties:
Change them accordingly. The meaning of the properties in the above
lines are as follows:
|jdbcDriver||Path of the JDBC driver jar|| PostgreSQL: |
|dbURL||URL for connecting the database via JDBC|| PostgreSQL: |
|dbUsername||Username for connecting the database||dbUsername=omar|
|dbPassword||Password for connecting the database||dbPassword=omar|
|jdbcClassName||The fully qualified name of the JDBC driver|| PostgreSQL: |
Now we are going to submit a request to your own installation.
In <omar.basedir>/build.xml, we can see a target "test":
If the registry server is installed in somewhere other than localhost or port, replace url=http://localhost:8080/omar/registry/soap accordingly. It will send a AdhocQueryRequest to the server. The request file, SQLQuery_1.xml, is located in <omar.basedir>/misc/samples.
Type "build test". Open <omar.basedir>/response.xml. It is the response from your registry server. You can see the content of response.xml similar to this:
If your installation is successful, you can see that the responses
<AdhocQueryResponse> element with
which is the code for status of "Success".
Finally you should subscribe to the mailing list
firstname.lastname@example.org by filling the form at
http://lists.sourceforge.net/lists/listinfo/ebxmlrr-tech . Any
update will be sent to this mailing list.