|author||imesha <email@example.com>||Tue Feb 04 14:36:58 2020 +0530|
|committer||imesha <firstname.lastname@example.org>||Tue Feb 04 14:36:58 2020 +0530|
[OODT-1034] Updated XmlRpcResourceManager to statup resmgr within main() method.
Apache Object Oriented Data Technology (OODT) is the smart way to integrate and archive your processes, your data, and its metadata. OODT allows you to:
OODT also allows for remote execution of jobs on scalable computational infrastructures so that computational and data- intensive processing can be integrated into OODT’s data processing pipelines using cloud computing and high-performance computing environments.
Traditional processing pipelines are commonly made up of custom UNIX shell scripts and fragile custom written glue code. Apache OODT uses structured XML-based capturing of the processing pipeline that can be understood and modified by non-programmers to create, edit, manage and provision workflow and task execution.
It is being used on a number of successful projects at NASA's Jet Propulsion Laboratory/California Institute of Technology, and many other research institutions and universities, specifically those part of the:
OODT is a Top Level project of the Apache Software Foundation http://www.apache.org/.
OODT is primarily written in Java, with some components available in Python. It requires Java 8 and uses the Maven 3 http://maven.apache.org/ build system. To build the Java components of OODT, use the following command in this directory:
mvn clean install
For the Python components, see the agility subdirectory.
OODT isn’t an out of the box solution, but we do try to make it as easy as possible. For that, OODT provides the RADIX build system which will compile a fully operational OODT platform ready for development and deployment. Building the RADIX distribution is as simple as running the following commands:
export JAVA_HOME=/usr/lib/jvm… (adjust for your own JAVA_HOME) curl -s "https://git-wip-us.apache.org/repos/asf?p=oodt.git;a=blob_plain;f=mvn/archetypes/radix/src/main/resources/bin/radix;hb=HEAD" | bash mv oodt oodt-src; cd oodt-src; mvn install mkdir ../oodt; tar -xvf distribution/target/oodt-distribution-0.1-bin.tar.gz -C ../oodt cd ../oodt; ./bin/oodt start ./resmgr/bin/batch_stub 2001
Navigate to http://localhost:8080/opsui, you should see the default OPSUI system which provides system oversight and interrogation
To contribute a patch, follow these instructions.
File JIRA issue for your fix at https://issues.apache.org/jira/browse/OODT. you will get issue id OODT-xxx where xxx is the issue ID.
Fork the repo on which you're working, clone your forked repo to your local computer, and set up the upstream remote:
git clone https://github.com/<YourGitHubUserName>/oodt.git git remote add upstream https://github.com/apache/oodt.git
Go into oodt directory
Checkout out a new local branch based on your master and update it to the latest.The convention is to name the branch after the current JIRA issue, e.g. OODT-xxx where xxx is the issue ID.
git checkout -b OODT-xxx
Do the changes to the relavant files and keep your code clean. If you find another bug, you want to fix while being in a new branch, please fix it in a separated branch instead.
Add relevant files to the staging area.
git add <files>
For every commit please write a short (max 72 characters) summary of the change. Use markdown syntax for simple styling. Please include any JIRA issue numbers in your summary.
git commit -m “[OODT-xxx] Put change summary here ”
NEVER leave the commit message blank! Provide a detailed, clear, and complete description of your commit!
Before submitting a pull request, update your branch to the latest code.
git checkout master git pull --rebase upstream master git checkout OODT-xxx git rebase -i master
Push the code to your forked repository
git push origin OODT-xxx
In order to make a pull request,
If you encounter errors in OODT or want to suggest an improvement or a new feature, please visit the OODT issue tracker https://issues.apache.org/jira/browse/OODT. There you can also find the latest information on known issues and recent bug fixes and enhancements.
You can find an enormous amount of useful documentation/resources related to OODT in OODT Confluence Wiki.
You can build a local copy of the OODT documentation including JavaDocs using the following Maven 2 command in the OODT source directory:
You can then open the OODT Documentation in a web browser:
Note: all OODT source files are encoded with UTF-8. You must set your MAVEN_OPTS environment variable to include “-Dfile.encoding=UTF-8” in order to properly generate the web site and other artifacts from source.
Note: generating the documentation requires enormous amounts of memory. More than likely you'll need to add to the MAVEN_OPTS environment variable in order to set the Java heap maximum size with “-Xmx512m” or larger before attempting to run “mvn site”.
Collective work: Copyright 2010-2012 The Apache Software Foundation.
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Apache OODT includes a number of subcomponents with separate copyright notices and license terms. Your use of these subcomponents is subject to the terms and conditions of the licenses listed in the LICENSE.txt file.
This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org/ for more information.
The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.
The following provides more details on the included cryptographic software:
Apache OODT uses Apache Tika which uses the Bouncy Castle generic encryption libraries for extracting text content and metadata from encrypted PDF files. See http://www.bouncycastle.org/ for more details on Bouncy Castle.
Discussion about OODT takes place on the following mailing lists:
email@example.com - About using OODT and developing OODT
Notification on all code changes are sent to the following mailing list:
The mailing lists are open to anyone and publicly archived.
You can subscribe the mailing lists by sending a message to -firstname.lastname@example.org (for example dev-subscribe@oodt...). To unsubscribe, send a message to -email@example.com. For more instructions, send a message to -firstname.lastname@example.org.