0 Static IP for UNIX machines

Static IP for red hat Linux:

·         Use setup/neat to configure static IP on the machine. Command is # setup or # neat

·         This will pop up a new screen with various options to configure IP. Choose the appropriate one.

Static IP for SuSe Linux:

·         Use yast to change the IP address of the machine. Command is # yast

·         Configure the IP with the given options

Static IP for Solaris:

You should have all the required information regarding the new IP like IP address, subnet mask, Default gateway and name. Modify the following files with the new entry.

·         # vi /etc/hosts. Enter the host name and IP address of the machine.

·         # vi /etc/netmasks. Enter the subnet mask for the IP.

·         # vi /etc/defaultrouter. Enter the default gateway.

Static IP for IBM AIX:

·         Use smit to change the IP address. Command is # smitty tcpip

·         Configure the IP with the given options

Static IP for HP UX:

·         Modify the entries in the file /etc/rc.config.d/netconf

·         Give the command # vi /etc/rc.config.d/netconf

·         Configure the IP with the given options and reboot the system by command # reboot

·         You can also use SAM to change the IP Address of the machine by command #sam and select appropriate options to configure IP Address

0 FEATURES OF OWB (Oracle Warehouse Builder)

FEATURES OF OWB (Oracle Warehouse Builder)

¢  Data Quality

¢  Data Auditing

¢  Fully integrated, rational and relational data modeling

¢  Full cycle management of data and metadata

¢  Create data warehouses

¢  Data Consolidation and Integration

¢  Clean and transform data to provide quality information

Earlier Versions of OWB (Oracle Warehouse Builder)

¢  Oracle9i Warehouse Builder v9.2.0.2.8 for Solaris

¢  Oracle Warehouse Builder 10g Release 1 (10.1.0.4)

¢  Oracle Warehouse Builder 10g Release 2 (10.2.0.1)

¢  Oracle Warehouse Builder 11g Release 1 (11.1.0.6.0) Standalone Software  

What’s new in OWB (Oracle Warehouse Builder)

¢  Enhancements to Warehouse Builder Architecture: One Unified Repository

In previous Warehouse Builder releases, the runtime environment and the design environment resided in separate repositories: the runtime repository and the design repository. Beginning in this release, both environments share a single Warehouse Builder repository. If you prefer to separate the environments, you can achieve this by creating multiple repositories.

¢  User Interface Enhancements

In previous releases of Warehouse Builder, editing different types of objects required using different editors. This release provides one common look and feel for all editors, including automatic layout, dockable panels, bird's eye view, and zoom capabilities. A new property inspector standardizes the properties interface for all objects.

¢  Enhancements to Accessing Non-Oracle Data and Metadata

—  Creating Flat file Targets

In previous releases, you used the Mapping Editor when you wanted to create a new flat file target for which there was no existing metadata to import. You added an unbound flat file operator to the mapping canvas and then used the operator editor to add and define fields for the flat file. Beginning in this release, the preferred method is to use the Create Flat File Wizard. Compared to the previous method, the Create Flat File Wizard enables a wider range of functionality such as specifying the character set and defining single or multiple record types. 

—  Introducing Non ASCII Flat files

In previous releases, importing binary files into Warehouse Builder was difficult or not possible, depending on the complexity of the file. Beginning in this release, you can use the Create Flat File Wizard to introduce non ASCII files into Warehouse Builder 

—  Sampling ASCII flat files

This release introduces enhancements to the Flat File Sample Wizard that include sampling and importing new data types such as GRAPHIC, RAW, and SMALLINT.

—  Custom Metadata Interface

Beginning with this release of Warehouse Builder, you can define and use SQL- or XML-based custom metadata stores to retrieve definitions of source and target objects such as tables and views

—  Deploying to Remote and Non-Oracle Targets

Beginning with this release, you can deploy objects to a remote or a non-Oracle database. This means that you can configure a target operator in a mapping to refer to a remote Oracle location or a non-Oracle location.

¢  Enhancements to Accessing Non-Oracle Data and Metadata

—  Impact Analysis and Change Management

Warehouse Builder now provides graphical tools for analyzing the possible outcomes to proposed metadata changes. Determine the potential costs of your proposed changes

—  Defining User Defined Properties (UDP’s)

In the previous release, you could assign UDPs only to existing Warehouse Builder repository objects. You defined UDPs using the OMB Plus scripting command OMBDEFINE and prefixed the new property name with UPD_. Beginning in this release, you can define new objects in addition to new properties. Prefix all user defined objects and properties with UD_. Any properties you defined in the previous release using the UDP_ prefix are still valid; however, UD_ is now the preferred prefix for both properties and objects.

—  New User Defined Objects

Beginning in this release, you can define new folders, first class objects, and second class objects. For each object you can define properties and associations, manage them in the Warehouse Builder repository, and assign custom icons for unique recognition. Because user defined objects are repository objects, you can access metadata reports and lineage and impact analyses.

—  User Defined Icons

You can import custom icons for unique representation in the user interface of any of the existing objects and user defined objects.

—  Enhancements to Metadata Security

Beginning in this release, Warehouse Builder offers a user interface for defining and implementing metadata security policies. 

¢  ETL Design and Performance Enhancements

—  Scheduled Process Executions

In previous releases, you were required to use Oracle Workflow to schedule the execution of Warehouse Builder mappings and process flows. Beginning in this release and when using Oracle database release 10g or higher, you can create schedules to plan when and how often to execute mappings and process flows. You can define schedules to execute once or to execute repeatedly based on an interval you define in the user interface

—  High Performance Data Extraction from Remote Sources

In previous releases, if you designed mappings that extracted data from remote sources, you could expect performance to be slow as data was accessed via database links. Beginning in this release, you can use Transportable Modules to replicate remote Oracle databases to the local Oracle database and thereby achieve rapid data extraction

—  Pluggable Mappings

This new feature in Warehouse Builder increases your design productivity through reusable logic that you can incorporate into various ETL processes or share between many designers.

—  Set Based Updates

In previous versions, when you set an Oracle target operator to load using an UPDATE loading type, Warehouse Builder updated the target in row based mode. Beginning with this release, if you configure the Oracle target module to generate 10g PL/SQL code, Warehouse Builder performs UPDATES in set based mode. For modules configured to generate 9i and earlier versions of PL/SQL code, Warehouse Builder performs UPDATES on targets in row based mode.

—  User Defined Data types

Beginning in this release, Warehouse Builder offers a user interface for creating user defined data types and using them for mapping in Warehouse Builder. You can use the user defined types to model real-world entities such as customers and purchase orders as objects in the database.

¢   Enhancements to Enable Quality Information

—  Slowly Changing Dimensions

Warehouse Builder now provides support for designing, deploying, and loading relational Type 1, 2, and 3 SCDs. For information on defining SCDs

—  New Sources and Targets

You can now read data from any source or write data to any target using PL/SQL and Java APIs. You can also read data from or write data to table functions and Oracle streams.

—  Data Profiling

This new feature in Warehouse Builder enables you to discover the structural content of your data, capture its semantics, and identify any anomalies or outliers prior to loading it in your BI system. With data profiling, you can automatically derive business rules and mappings to clean data, derive quality indices such as Six Sigma, and use auditors to continuously monitor data quality. You can integrate data profiling into your ETL process.

¢  Enabling Business Intelligence

—  Dimensional Objects

In the previous release, you had to use the OLAP bridge to deploy dimensional objects to an analytic workspace. Beginning with this release, the logical design of the dimensional object is separated from the storage. You can use the same metadata to create and manage both your relational and multidimensional data stores. You define the dimensional object and can then deploy them directly either to a relational schema or to an analytic workspace.

—  Business Intelligence Objects

Beginning with this release, you can define or derive business intelligence objects that can be integrated with analytical business intelligence tools such as Oracle BI Discoverer and Oracle BI Beans. You can deploy business intelligence objects defined using Warehouse Builder to these tools and then perform adhoc queries on the warehouse data.

¢  Enhancements to Enable Expertise Capture

Beginning with this release, you can create experts that enable you to build your own applications by reusing Warehouse Builder components. Experts are solutions that enable advanced users to design solutions that simplify routine or complex tasks that can be performed by end users.

¢  Terminology Changes

—  Synchronize replace Reconcile

For an operator such as a source and target operator or a key lookup, Warehouse Builder maintains a version of the object in the repository. Propagating changes between an operator and its repository object is known as synchronizing. In previous releases, this process was known as reconciling or reconciliation. These terms are no longer used.

—  Refresh replace Synchronize

When multiple users access the same repository, use the refresh command to update the Design Center display. In previous releases, this command was called synchronize. Synchronize now refers to the action of updating an operator with an associated repository object.

—  User Defined Process replace External Process

In previous releases, an activity that you defined in a process flow to launch an external process was known as an External Process activity. In this release, the term is now User Defined Process.

 

¢  Improvements to the Documentation Set

The documentation set has been reorganized and revised.

The book formerly entitled the Oracle Warehouse Builder Installation and Configuration Guide is now entitled the Oracle Warehouse Builder Installation and Administration Guide and includes administration information such as implementing security.

Oracle Warehouse Builder User's Guide now includes enhanced introductory and conceptual information.

Oracle Warehouse Builder API and Scripting Reference now include information on using experts and the Expert Editor, which was formerly contained in the User's Guide.

0 Running ANT

Command Line
If you've installed Ant as described in the Installing Ant section, running Ant from the command-line is simple: just type ant.

When no arguments are specified, Ant looks for a build.xml file in the current directory and, if found, uses that file as the build file and runs the target specified in the default attribute of the <project> tag. To make Ant use a build file other than build.xml, use the command-line option -buildfile file, where file is the name of the build file you want to use

If you use the -find [file] option, Ant will search for a build file first in the current directory, then in the parent directory, and so on, until either a build file is found or the root of the filesystem has been reached. By default, it will look for a build file called build.xml. To have it search for a build file other than build.xml, specify a file argument.

Note: If you include any other flags or arguments on the command line after the -find flag, you must include the file argument for the -find flag, even if the name of the build file you want to find is build.xml.

You can also set properties on the command line. This can be done with the -Dproperty=value option, where property is the name of the property, and value is the value for that property. If you specify a property that is also set in the build file (see the property task), the value specified on the command line will override the value specified in the build file. Defining properties on the command line can also be used to pass in the value of environment variables - just pass -DMYVAR=%MYVAR% (Windows) or -DMYVAR=$MYVAR (Unix) to Ant. You can then access these variables inside your build file as ${MYVAR}. You can also access environment variables using the property task's environment attribute.

Options that affect the amount of logging output by Ant are:
-quiet, which instructs Ant to print less information to the console;
-verbose, which causes Ant to print additional information to the console;
-debug, which causes Ant to print considerably more additional information.
It is also possible to specify one or more targets that should be executed. When omitted, the target that is specified in the default attribute of the project tag is used.
The -projecthelp option prints out a list of the build file's targets. Targets that include a description attribute are listed as "Main targets", those without a description are listed as "Subtargets", then the "Default" target is listed.

Command-line Options Summary
ant [options] [target [target2 [target3] ...]]

Options:

-help, -h	print this message
-projecthelp, -p	print project help information
-version	print the version information and exit
-diagnostics	print information that might be helpful to diagnose or report problems.
-quiet, -q	be extra quiet
-verbose, -v	be extra verbose
-debug, -d	print debugging information
-emacs, -e	produce logging information without adornments
-lib <path>	specifies a path to search for jars and classes
-logfile <file>	use given file for log
-l <file>	use given file for log
-logger <classname>	the class which is to perform logging
-listener <classname>	add an instance of class as a project listener
-noinput	do not allow interactive input
-buildfile <file>	use given buildfile
-file <file>	use given buildfile
-f <file>	use given buildfile
-D<property>=<value>	use value for given property
-keep-going, -k	execute all targets that do not depend on failed target(s)
-propertyfile <name>	load all properties from file with -D properties taking precedence
-inputhandler <class>	the class which will handle input requests
-find <file>	(s)earch for buildfile towards the root of
-s <file>	the filesystem and use it

Ant tasks

The following tables provide a short description of each task.

• Archive Tasks (Jar, Ear, Tar, War, GZip, Zip etc.)
• Audit/Coverage Tasks (JDepend, JPorbe, MMetrics, etc. )
• Compile Tasks (javac, jspc, rmic etc.)
• Deployment Tasks (ServerDeploy)
• Documentation Tasks (Javadoc, Stylebook)
• EJB Tasks
• Execution Tasks (Ant, Antcall, Exec, Java, Sleep etc.)
• File Tasks (Attrib, Copy, Copydir, delete, Mkdir etc.)
• Java2 Extensions Tasks (Jarlib-available, Jarlib-display etc.)
• Logging Tasks (Record)
• Mail Tasks (Mail, MimeMail)
• Miscellaneous Tasks (Echo, GenKey, Script, Sql etc.)
• .NET Tasks
• Pre-process Tasks (ANTLR, AntStructure, Import, Xslt/Style etc.)
• Property Tasks (Available, Basename, BuildNumber, LoadFile etc.)
• Remote Tasks (FTP, Telnet etc. )
• SCM Tasks (Cvs, CvsChangeLog, CVSPass etc.)
• Testing Tasks (Junit, JunitReport, Test)
• Visual Age for Java Tasks

Core tasks

• Ant
• AntCall
• AntStructure
• Apply/ExecOn
• Available
• Basename
• BuildNumber
• BUnzip2
• BZip2
• Checksum
• Chmod
• Concat
• Condition
• Supported conditions
• Copy
• Copydir
• Copyfile
• Cvs
• CvsChangeLog
• CVSPass
• CvsTagDiff
• Defaultexcludes
• Delete
• Deltree
• Dependset
• Dirname
• Ear
• Echo
• Exec
• Fail
• Filter
• FixCRLF
• GenKey
• Get
• GUnzip
• GZip
• Import
• Input
• Jar
• Java
• Javac
• Javadoc/Javadoc2
• LoadFile
• LoadProperties
• Mail
• MacroDef
• Manifest
• Mkdir
• Move
• Parallel
• Patch
• PathConvert
• PreSetDef
• Property
• Record
• Rename
• Replace
• Rmic
• Sequential
• SignJar
• Sleep
• Sql
• Style
• Subant
• Sync
• Tar
• Taskdef
• Tempfile
• Touch
• TStamp
• Typedef
• Unjar
• Untar
• Unwar
• Unzip
• Uptodate
• Waitfor
• War
• WhichResource
• XmlProperty
• Xslt
• Zip

Ant command line arguments

Several tasks take arguments that will be passed to another process on the command line. To make it easier to specify arguments that contain space characters, nested arg elements can be used.

value - a single command-line argument; can contain space characters.
file - The name of a file as a single command-line argument; will be replaced with the absolute filename of the file.
path - A string that will be treated as a path-like string as a single command-line argument; you can use ; or : as path separators and Ant will convert it to the platform's local conventions.
pathref - Reference to a path defined elsewhere. Ant will convert it to the platform's local conventions.
line - a space-delimited list of command-line arguments.

It is highly recommended to avoid the line version when possible. Ant will try to split the command line in a way similar to what a (Unix) shell would do, but may create something that is very different from what you expect under some circumstances.

Examples
<arg value="-l -a"/>
is a single command-line argument containing a space character.
<arg line="-l -a"/>
represents two separate command-line arguments.
<arg path="/dir;/dir2:\dir3"/>
is a single command-line argument with the value \dir;\dir2;\dir3 on DOS-based systems and /dir:/dir2:/dir3 on Unix-like systems.

Command-line Options Summary
ant [options] [target [target2 [target3] ...]]

Options:

-help, -h	Displays help information describing the Ant command and its options
-projecthelp, -p	Print project help information
-version	Print the version information and exit
-diagnostics	Print information that might be helpful to diagnose or report problems.
-quiet, -q	Suppresses most messages not originated by an echo task in the buildfile
-verbose, -v	Displays detailed messages for every operation during a build.
-debug, -d	Print debugging information
-emacs, -e	Produce logging information without adornments
-lib <path>	Specifies a path to search for jars and classes
-logfile <file>	Use given file for log
-l <file>	Use given file for log
-logger <classname>	Specifies a class to handle Ant logging.
-listener <classname>	Add an instance of class as a project listener
-noinput	Do not allow interactive input
-buildfile <file>	Use given buildfile
-file <file>	Use given buildfile
-f <file>	Use given buildfile
-D<property>=<value>	Defines a property name-value pair on the command line.
-keep-going, -k	execute all targets that do not depend on failed target(s)
-propertyfile <name>	load all properties from file with -D properties taking precedence
-inputhandler <class>	the class which will handle input requests
-find <file>	Search for buildfile towards the root of the filesystem and use it