unix and linux operating commands

An Introduction to Real-Time Data Integration


 
Thread Tools Search this Thread
# 1  
Old 04-06-2008
An Introduction to Real-Time Data Integration

Get an introduction to using Oracle Data Integrator, Java-based middleware that uses the database to perform set-based data integration tasks in an SOA.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Archiving or removing few data from log file in real time

Hi, I have a log file that gets updated every second. Currently the size has grown to 20+ GB. I need to have a command/script, that will try to get the actual size of the file and will remove 50% of the data that are in the log file. I don't mind removing the data as the size has grown to huge... (8 Replies)
Discussion started by: Souvik Patra
8 Replies

2. Shell Programming and Scripting

Converting real time to epoch time

# date +%s -d "Mon Feb 11 02:26:04" 1360567564 # perl -e 'print scalar localtime(1360567564), "\n";' Mon Feb 11 02:26:04 2013 the epoch conversion is working fine. but one of my application needs 13 digit epoch time as input 1359453135154 rather than 10 digit epoch time 1360567564... (3 Replies)
Discussion started by: vivek d r
3 Replies

3. Shell Programming and Scripting

Shell script to convert epoch time to real time

Dear experts, I have an epoch time input file such as : - 1302451209564 1302483698948 1302485231072 1302490805383 1302519244700 1302492787481 1302505299145 1302506557022 1302532112140 1302501033105 1302511536485 1302512669550 I need the epoch time above to be converted into real... (4 Replies)
Discussion started by: aismann
4 Replies

4. Shell Programming and Scripting

Piped open not real-time - How would one handle live data?

When I run "/etc/myApp" I am presented with continuous output, just about once per second. However when I try to get the information in Perl via a piped open, it waits till the end to give me anything... my code: open (OUTPUT,"/etc/myApp |"); while (<OUTPUT>){ print $_; }... (2 Replies)
Discussion started by: jjinno
2 Replies

5. UNIX for Dummies Questions & Answers

capturing real time

Newbie question: I wrote korn shell script that lets me connect to a cisco switch thru telnet from sun server. I'm wodering if or what command i would use to capture info that is being sent to standard output when the script is running. Putting part of my script below and results. #!/bin/ksh... (2 Replies)
Discussion started by: wisher115
2 Replies
Login or Register to Ask a Question
Data::Grove(3pm)					User Contributed Perl Documentation					  Data::Grove(3pm)

NAME
Data::Grove -- support for deeply nested structures SYNOPSIS
use Data::Grove; $object = MyPackage->new; package MyPackage; @ISA = qw{Data::Grove}; DESCRIPTION
"Data::Grove" provides support for deeply nested tree or graph structures. "Data::Grove" is intended primarily for Perl module authors writing modules with many types or classes of objects that need to be manipulated and extended in a consistent and flexible way. "Data::Grove" is best used by creating a core set of ``data'' classes and then incrementally adding functionality to the core data classes by using ``extension'' modules. One reason for this design is so that the data classes can be swapped out and the extension modules can work with new data sources. For example, these other data sources could be disk-based, network-based or built on top of a relational database. Two extension modules that come with "Data::Grove" are "Data::Grove::Parent" and "Data::Grove::Visitor". "Data::Grove::Parent" adds a `"Parent"' property to grove objects and implements a `"root"' method to grove objects to return the root node of the tree from anywhere in the tree and a `"rootpath"' method to return a list of nodes between the root node and ``this'' node. "Data::Grove::Visitor" adds callback methods `"accept"' and `"accept_name"' that call your handler or receiver module back by object type name or the object's name. "Data::Grove" objects do not contain parent references, Perl garbage collection will delete them when no longer referenced and sub- structures can be shared among several structures. "Data::Grove::Parent" is used to create temporary objects with parent pointers. Properties of data classes are accessed directly using Perl's hash functions (i.e. `"$object->{Property}"'). Extension modules may also define properties that they support or use, for example Data::Grove::Parent adds `"Parent"' and `"Raw"' properties and Visitor depends on `"Name"' and `"Content"' properties. See the module "XML::Grove" for an example implementation of "Data::Grove". METHODS
new( PROPERTIES ) Return a new object blessed into the SubClass, with the given properties. PROPERTIES may either be a list of key/value pairs, a single hash containing key/value pairs, or an existing "Data::Grove" object. If an existing "Data::Grove" is passed to `"new()"', a shallow copy of that object will be returned. A shallow copy means that you are returned a new object, but all of the objects underneath still refer to the original objects. AUTHOR
Ken MacLeod, ken@bitsko.slc.ut.us SEE ALSO
perl(1) perl v5.10.1 2003-10-21 Data::Grove(3pm)