Jul 25

So much database types as well as system weared. Where the system have to support execution of work but in other matter will very complicate in the case of reporting system, because possibly one of the problem of datas amount which so much, disagree with used systems. It is of course become dilemma in making of reliable report and data integration which earn to be trusted.


Challenging from qualified management data is a[n critical component concerning business guarantee. In this time many technologies supporting from various aspect of " extract, transform, load and ( ETL) process, is but designed especially for the examination of, authentication, and sweeping for the things assuring qualified data. Technology like that have to can access and refine / tapping data of any source, including former data and data system of non-relational. That have to provide a[n step make an audit of when testing data to ascertain the integrity of and identify all and anomalies of inconsistencies. That Thing have to convert, cleaning, readjusting, and strengthening data is such as needed. Also have to can unite and clean ( data cleansing) in final repository, providing analysis and give report detailedly and summary. Finally, can walk very efficient, timely, costeffective in processing data.

Trust of data which do not consistence, complete ketidak or mistake of data can become " Risk Business" unacceptable. Data quality is a[n vital component as guarantee of[is continuity of company business. Quality of bad data can endanger attainment of efficiency and target of operational system. That Thing also can erod value of business information system, above of him entrust to make decision. based on decision is bad data, can cause monetary loss directly, destroy network, and destroy company credibility. Some companies recognize data as strategic asset, leader of business hold responsibility to ascertain correctness, quality of, and reliability of information.

In a Data Base figuring in more than 20 million data archives, prima facie strength [is] efesiensi shortened process time, delivery of data ( Extract), Transfer of into other form ( Transform) and Inclusion / Import ( Load) – ( ETL Process). The same as sweeping of effective data, conversion, and authentication is important for the success of than equipment of Data Base.

Data of Cleansing is covering some processes as follow:

1. Data Definition

Intake process ( Extract) Data of Database and or from other system, from various format type and data base type like Oracle, AS400, Dbase, Foxpro, SQL, Excel, Text, and others). Data Extract can be conducted by 2 methods:

• Direct Method
Data taken by connect is direct the than Database, with snapshot technique – only read henceforth to process.

• Indirect Method
Data taken indirectly from Database conducted process degradation of Data beforehand to format . txt henceforth to process.

2. Verification and Data Integration

Process Verification Data is process inspection of data per record pursuant to the data type and field of like format of date, ascii, numeric. etc
Target of process the data verification is to ascertain entire/all data to be processed have as according to format of Source got Data of Text / Database..

3. Data Cleansing

Process Data of Cleansing, in this case that is doing standardization in entire/all database to be content than the data base as a whole according to the format form or standard of [is] same, like determination :

• Writing of Block letters / Lower Case
• Writing of title
• Uniforming of Abbreviation word
• Tanda baca (Ex : – _ . , ; and etc)
• Conversion Letter of Romawi (ex: V = 5)
• etc

4. Data Identification

Process identify can be done by using some conditions pursuant to fringe which have been determined. As for obtained result from identifying data earn like.:

• Active Customer number
• Customer Non Active (based on criteria)
• Data Duplication
• Single Data

5. Data Matching

Adjustment process or adaptation of data ( ” Match” or ” Note of Match”) pursuant to some alternatives like :Nama Customer dan Alamat Customer
• Customer Number
• etc

I’m just a simple human being, trying to be different from others. In fact, why should I have been same. For 6 years until now, I am a application developer.

Article Source: http://www.articlesbase.com/

Jul 21

JMS or Java Message Service is the basis and standard API for asynchronous, reliable messaging.

After 10 years, a new (2nd) edition of the book “Java Message Service” was recently published. Mark Richards reworked the original edition by David Chappell (ex-Sonic, now Oracle) and Richard Manson-Haefel.

Having just skimmed through the book, it did look very intersting. Obviously an extensive treatment of the API (and thus specification). But nice to see code samples based on ActiveMQ, some explanation of character encoding, use of non-JMS clients (.Net, C++), dynamic vs. administered queues, message driven beans (MDB) and Spring and Security.

Some topics that did not seem to be addressed:SOAP over JMS, REST-like access tot JMS providers, persistence mechanisms (database or file based),

Messaging solutions are still the core backbone for many ESB’s and integration solutions. The JMS API remains the standard abstration layer for both Java (ActiveMQ, SonicMQ, OpenMQ, Fiorano) and non-Java based messaging (Tibco , WebSphereMQ, SoftwareAG WebMethods, Oracle AQ) solutions.

Mar 07

Enjoyed 2 days off in the Ardennes in the woods around Saint-Hubert, I took a book along that was already a couple of months on my bookshelf: Oracle Essentials 4th Edition. Triggered also by a customer looking into Oracle Advanced Queueing (AQ).

Nice book, giving a good overview of all the features available in and around the Oracle database. Obviously the book doesn’t go into every detail, but it does give a good overview or “refresh”.

While reading the book, I came to realize that the Oracle database is 28 years old! I still remember starting my career in September 1987, developing with the Informix database and 4GL on NCR Unix servers. Informix, together with Progress, was a major competitor of Oracle at that time.

Only in 1995 I really worked with Oracle. Oracle 7 with ESQL/C (embedded SQL) in C on Sun Solaris.

At that time, I learned about the distinguishing feature of Oracle: multiversion read consistency. The fact that Oracle will not fail when reading a row updated by another transaction. Instead, Oracle will retrieve the row as it looked like when the transaction started from its transaction logs. This avoids locking all the rows being read, as opposed to all the other databases, including Informix. Obviously, an update of such row will fail as it was already updated by another transaction.