Free chief architect software for linux

Data Architects, DBAs, Analysts and Designers rely on Data Modeling tools to facilitate and simplify their data Modeling efforts, while maximizing the use of their resources. The Power*Architect allows these busy highly technical resources to perform this most intricate part of their job in a fraction of the time.
Power*Architect project is an innovative Java-based data modeling tool geared specifically for Data Warehouse and Data Mart design. It allows the designer to open multiple concurrent source Database connections, create and explore profiles of the source data, drag and drop source schemas, tables and columns into the data modeling playpen, and forward engineer the resultant target database and its associated ETL template.
Main features:
- Access any JDBC or ODBC accessible source database
- Quickly create profiles of source data, including information about the size of the data in each column, maximum and minimum values, frequency distribution of values in a column, and more.
- Profile information is saved with the project, so profile data can still be used to aid off-site design sessions when it is not possible to access the source databases.
- Design the target database Data Model (Data Warehouse)
- Compare the database structure of any two databases highlighting the structural differences and generating the required DDL to synchronize
- Compare the Data Model data structures to an existing target database
- Save a snapshot of all source systems data structures in the project file, allowing data warehouse designers to evolve their target data model remotely
- Forward engineer to Oracle, SQL Server, DB2, and PostgreSQL and more.
- Forward engineer ETL Templates containing source-to-target data mappings
- Invoke ETL Engine to load initial set of data into the target database
- Enable easy centralized installation and updates to many end users (Supports Java WebStart technology).
- The Power*Architect can open multiple source databases concurrently, even if they are from competing database vendors. Another key feature of the Power*Architect, that sets it apart from other data modeling tools, is that it remembers the origin of each column, and is capable of automatically generating the source-to-target data mappings.
- Whether youre building or maintaining your Data Warehouse data model, the Power*Architect will provide you a complete view of all required database structures and will expedite every aspect of your data warehouse design.
- Design your Data Warehouse in a fraction of the time with the Power*Architect.
- We look forward to showing you how!
- The Power*Architect is available now for download! The product is available for free to individuals for personal use. Commercial licensing and support are available at competitive prices. Please call us at 1-866-SQL-POWR to purchase.
Enhancements:
- This release fixes a bug that caused corrupt project files to be saved.
- The handling of automatic cascading primary keys in multi-level identifying relationships now works better.
- The profile manager is now even more stable.
- It is now possible to add new database connection types from within the GUI.

Business Process Visual ARCHITECT is a full-featured business process modeler that supports the latest OMG Business Process Modeling Notation (BPMN).
Business Process Visual ARCHITECT provides an easy-to-use diagramming environment for you to model your business process, and is a proven solution for bridging the gap between business analysts and IT professionals.
Main features:
- Frictionless business modeling environment
- On-the-fly syntax check and correction according to BPMN specification
- Advanced printing facility for outputting large business process diagram
- Share business process diagram among your company with Teamwork Server
- Incorporate user-defined images to the business process diagram to increase the readability.
Enhancements:
- Branch and tag capabilities were added to the VP Teamwork Server, including Subversion and CVS repository integration.
- This allows different modeling projects to be run in parallel while keeping the release quality project stable in the trunk.
- There were also a number of enhancements for various other features.

Chebyshev application allows someone to set up a spam filtering email forwarding service.

Chebyshev is an engine for an email forwarding service similar to those "bitdiddle@alum.college.edu" email forwarding services that some schools provide. Combine email forwarding with spam filtering, and you have something useful. The chief design goal for this engine is simplicity.

Installation:

This software expects to be installed on my computer which is a stock Intel based Red Hat Linux 5.1 machine, with apache-ssl installed and configured. Also, the machine assumes you have configured your mail transfer agent to utilize the Realtime Black Hole list; otherwise you just get forwarding without filtering.

For apache-ssl, please consult the web for installation instructions. My favorite source of cryptographically strong software is ftp://ftp.replay.com, a distribution site located in Holland. Please note that there may be patents, export regulations, and other legalities surrounding the use of cryptographic software in your location. Consult your local government for more information.

As for configuring your mail transfer agent, several agents are supported including Sendmail and Exim. Paul Vixie heads the Realtime Blackhole List; consult the web page at http://maps.vix.com/rbl/ for more details. Make sure you understand the implications of joining the Realtime Blackhole List; i.e. it can potentially block legitimate mail on occasion.

Once the preliminaries are in place, installation is fairly straightforward. Because this software is new, look over the Makefile before attempting installation. Then, as root, type "make install".

RefactorIT project is a tool for Java developers. A developer can take source code of any size and complexity and rework it into well-designed code by means of over 30 automated refactorings.
In addition, it provides a comprehensive set of smart query functions, a graphical dependency analyzer, and over 100 quality metrics and audits that make it possible to analyze and track large volumes of code.
It may be used as a stand-alone tool or installed as an add-in to NetBeans, Sun ONE Studio, JDeveloper, and JBuilder.
Speed and flexibility, innovativeness and aesthetics, power and appeal - todays developers and software architects expect a lot from their software development tools.
Spontaneity is especially important: we all want to be able to put our plans into action quickly.
RefactorIT is the ideal development tool for people who enjoy their freedom - it is the first comprehensive refactoring and code analyses tool that goes everywhere you want to take it - no matter...
- what IDE your team is working with - by choice or force,
- what kind of Java technologies you are developing with,
- how daring your refactoring project may seem.
RefactorIT provides
- Automatic Refactoring Operations,
- Code Searches and Analysis,
- Audits and Corrective Actions,
- Metrics,
- IDE integrations,
- Full JSP support.

mpgedit is an MPEG 1 layer 1/2/3 (mp3), MPEG 2, and MPEG 2.5 audio file editor that is capable of processing both Constant Bit Rate (CBR) and Variable Bit Rate (VBR) encoded files.
Since no file decoding / encoding occurs during editing, there is no audio quality loss when editing with mpgedit.
When editing VBR files that have a XING header, mpgedit updates the output files XING header information to reflect the new file size and average bit rate.
mpgedit operates in two modes: a command line and a curses-based, full-screen interactive shell. All editing functionality is available in both modes. The chief advantage of the interactive mode comes when using the playback feature for selection and verification of edit begin and end times, which is more rapidly performed interactively.
xmpgedit provides most of the same editing capabilities as the curses-mode mpgedit, but adds a graphical representation of the volume levels of mp3 file being being edited.
Enhancements:
- This release fixes an occasional crash in xmpgedit when adjusting the volume after playback has stopped.
- mpgedit playto start time is fixed, which would play beyond the specified edit time in some circumstances.
- The command "Copy start time" has been added to the xmpgedit edit menu.
- mpgedit playback and editing with the -I option is fixed, which would frequently repeat up to a second of material at the start of the edit.

wCMF is a lightweight MDA approach to application development based on the MVC pattern. It allows the creation of any kind of PHP Web application such as CRM or a CMS from a UML model. The project features an object persistence layer, a SOAP interface, and standard views and controllers.
Main features:
- Enhanced view template that generates a view
- Stereotype for modeling system properties
- Database upgrade system
- The framework and the application template are now auto deployed to the target directory
Enhancements:
BUGS
- fixed bug 1691278 (inherited values cant be referenced by subclasses)
- Corrected standard application
- fixed soap update method
- fixed bug (1676550), soap methods were always created (is_soap was ignored)
- fixed typo (assoziation -> association)
- default application model (removed all old wcmf stereotypes), rebuild generator
- fixed 1693598 (attributes were multiplied in inheritance)
- - fixed radio button template (showed duplicated entries, when none selected)
- fixed handling of null values in database mapping
- Tutorials: changed de.bmiag.genfw.instantiator.xmlmap generator property in hello world tutorials (old config caused bug #1741294)
- Generator: fixed bug #1741296 (exception, when trying to zip empty directory)
- Generator: fixed column ids in tables.sql (id of an fk pointing to the own table, was not unique)
- Framework: fixed advanced search in wCMF default application (ignores empty values now)
ENHANCEMENTS
- new start page in Enterprise Architect default project
- added Soap Search. exposes the search controller to the soap interface.
- added Soap advancedSearch. exposes the search controller to the soap interface.
- added added orderby tagged value to WCMFNode to allow default sorting in node lists
- implemented simple (->) association type (does not allow create/delete), so we support composite, shared and simple now
- added WCMFSystem stereotype for modeling system properties
- Added displayName to soapList method.
- Added parentoids, childoids to soapRead method.
- Added depth parameter to soapRead method.
- added PrimitiveType to auto-generated WCMFValues.
- Enhanced view template (View.tpl) to render a special form if a WCMFNode is associated with the WCMFView.
- Added WCMFReference values to custom view.
- First version of database update script (application/install/dbupdate.php)
- changed display value calls in order to allow entities to override default behavior
- removed tagged value is_ordered from WCMFNode stereotype. use orderby = none|sortkey|[value] instead
- added xslt documentation generation to the generator
- added TargetDirectory und ProjectName properties to Identifier class (maybe used in XPand on every identifier)
- Development page generated by Generator
- added template override feature
- added framework/application template auto deployment to generator
- Framework: added log directory creation if directory does not exist
- Framework: update script now ignores not null changes for pks
- made StringQuery more robust (checks the type to search for first)
- Framework: added alternating rows to resource browser
- changed localization to accept language definitions without country (e.g. de defaults to de_DE)

Rocks Cluster is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters.
Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....

DBI::FAQ is a Perl module for the Frequently Asked Questions of the Perl5 Database Interface.

What is DBI, DBperl, Oraperl and *perl?

To quote Tim Bunce, the architect and author of DBI:

``DBI is a database access Application Programming Interface (API)
for the Perl Language. The DBI API Specification defines a set
of functions, variables and conventions that provide a consistent
database interface independant of the actual database being used.

In simple language, the DBI interface allows users to access multiple database types transparently. So, if you connecting to an Oracle, Informix, mSQL, Sybase or whatever database, you dont need to know the underlying mechanics of the 3GL layer. The API defined by DBI will work on all these database types.

A similar benefit is gained by the ability to connect to two different databases of different vendor within the one perl script, ie, I want to read data from an Oracle database and insert it back into an Informix database all within one program. The DBI layer allows you to do this simply and powerfully.

DBperl is the old name for the interface specification. Its usually now used to denote perl4 modules on database interfacing, such as, oraperl, isqlperl, ingperl and so on. These interfaces didnt have a standard API and are generally not supported.

Heres a list of DBperl modules, their corresponding DBI counterparts and support information. Please note, the authors listed here generally do not maintain the DBI module for the same database. These email addresses are unverified and should only be used for queries concerning the perl4 modules listed below. DBI driver queries should be directed to the dbi-users mailing list.

However, some DBI modules have DBperl emulation layers, so, DBD::Oracle comes with an Oraperl emulation layer, which allows you to run legacy oraperl scripts without modification. The emulation layer translates the oraperl API calls into DBI calls and executes them through the DBI switch.

Heres a table of emulation layer information:

Module Emulation Layer Status
------ --------------- ------
DBD::Oracle Oraperl Complete
DBD::Informix Isqlperl Under development
DBD::Ingres Ingperl Complete?
DBD::Sybase Sybperl Working? ( Needs verification )
DBD::mSQL Msqlperl Experimentally released with
DBD::mSQL-0.61

The Msqlperl emulation is a special case. Msqlperl is a perl5 driver for mSQL databases, but does not conform to the DBI Specification. Its use is being deprecated in favour of DBD::mSQL. Msqlperl may be downloaded from CPAN via:

http://www.perl.com/cgi-bin/cpan_mod?module=Msqlperl