vault 4.100
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 8
DVD-Vault 4.100
DVD-Vault provides an achive software to manage DVD jukeboxes (SCSI medium changers). more>>
DVD-Vault provides an achive software to manage DVD jukeboxes (SCSI medium changers).
DVD-Vault is an implementation of a filesystem archive that makes a DVD SCSI library with multiple pieces of DVD-R or DVD-RAM media look like a single large file system.
A library with 1000 pieces of 4.7Gbyte media can be addressed as a 4700GByte file system with SCSI-robotic mounting and unmounting of media as required.
Users of UniTree (HPSS), AMASS, METIOR, and MagnaVault may recognize how this program works.
It has been tested with an ASACA 250 and 1450 and the Sony/Kubota 64-slot PD (blu-ray) library.
Enhancements:
- Binary and source code have been broken apart into two different files.
- DMAPI code now "punches" holes in files, rather than truncating the files. This makes file sizes transparent, which is really helpful for Windows clients.
- disk_scrub has been implemented to reclaim optical disk space when files are deleted.
- The MCLIB routines have support for Qualstar tape libraries.
- Batch_migration is in the binary RPM to support WORM media (BD-R, DVD+R).
- Tape stage support is in the stage program
- Purge is replaced with purgefile to support the new DMAPI code.
<<lessDVD-Vault is an implementation of a filesystem archive that makes a DVD SCSI library with multiple pieces of DVD-R or DVD-RAM media look like a single large file system.
A library with 1000 pieces of 4.7Gbyte media can be addressed as a 4700GByte file system with SCSI-robotic mounting and unmounting of media as required.
Users of UniTree (HPSS), AMASS, METIOR, and MagnaVault may recognize how this program works.
It has been tested with an ASACA 250 and 1450 and the Sony/Kubota 64-slot PD (blu-ray) library.
Enhancements:
- Binary and source code have been broken apart into two different files.
- DMAPI code now "punches" holes in files, rather than truncating the files. This makes file sizes transparent, which is really helpful for Windows clients.
- disk_scrub has been implemented to reclaim optical disk space when files are deleted.
- The MCLIB routines have support for Qualstar tape libraries.
- Batch_migration is in the binary RPM to support WORM media (BD-R, DVD+R).
- Tape stage support is in the stage program
- Purge is replaced with purgefile to support the new DMAPI code.
Download (MB)
Added: 2007-07-18 License: GPL (GNU General Public License) Price:
829 downloads
Rsync Vault Manager 1.01
Rsync Vault Manager uses rsync to manage archives of clients across multiple logical partitions. more>>
Rsync Vault Manager is an archive manager that uses rsync to manage backups of multiple clients across multiple logical partitions (vaults).
Rsync Vault Manager has some features that some other rsync-based backup schemes lack, such as being written in C++, needing no scripts or other programs than rsync and any binaries on which rsync depends (such as SSH), the ability to manage multiple instances of rsync connections to separate clients in parallel, the ability to use multiple logical partitions (vaults) in a configurable fashion for purporses of redundancy and added reliability, and the use of hard links for files that have not changed from one archive to the next.
Rsync Vault Manager was developed on an x86 platform using Linux RedHat 9.0 w/ GCC 3.2.2 and an UltraSPARC platform using Solaris 8 w/ GCC 2.95.5.
Rsync Vault Manager uses GNU autoconf/automake scripts for compilation and installation.
Enhancements:
- Minor bugs fixed: a wildcard resolution bug, incorrect archive directory names, empty job IDs in reports, and this release checks that a vault is writable before running rsync.
- A vault locking option prevents multiple instances of rvm from using the same vault, there is a separate error logging level to be used when retrying an rsync command, and there is an option to delete old log files along with old archives.
<<lessRsync Vault Manager has some features that some other rsync-based backup schemes lack, such as being written in C++, needing no scripts or other programs than rsync and any binaries on which rsync depends (such as SSH), the ability to manage multiple instances of rsync connections to separate clients in parallel, the ability to use multiple logical partitions (vaults) in a configurable fashion for purporses of redundancy and added reliability, and the use of hard links for files that have not changed from one archive to the next.
Rsync Vault Manager was developed on an x86 platform using Linux RedHat 9.0 w/ GCC 3.2.2 and an UltraSPARC platform using Solaris 8 w/ GCC 2.95.5.
Rsync Vault Manager uses GNU autoconf/automake scripts for compilation and installation.
Enhancements:
- Minor bugs fixed: a wildcard resolution bug, incorrect archive directory names, empty job IDs in reports, and this release checks that a vault is writable before running rsync.
- A vault locking option prevents multiple instances of rvm from using the same vault, there is a separate error logging level to be used when retrying an rsync command, and there is an option to delete old log files along with old archives.
Download (0.73MB)
Added: 2006-07-18 License: GPL (GNU General Public License) Price:
1196 downloads
Plesk 8.0.0
Plesk is a multi-platform, Web-based software solution that simplifies and automates the administration of Linux servers. more>>
Plesk is a multi-platform, Web-based software solution that simplifies and automates the administration of Linux, FreeBSD, and Windows servers.
Innovative Ease of Use
Plesk has a redesigned cleaner and easier to use interface. Plesk comes with many additional skins and even gives users the ability to design custom skins and manage them in the browser-based interface. In particular, the new desktop feature increases the usability and flexibility of the software significantly.
Highest Stability
Plesk has been specifically designed to be the most stable and secure control panel available. Plesk has been proven under fire managing 5 million plus domains globally and can support thousands of accounts per server increasing profitability.
Most Secure
Not only does Plesk contain new security measures but also, existing security features have been improved. The softwares redesigned subsystem improves overall system security as well as support for 3rd party FTP servers that make secure uploads possible.
Comprehensive
As the next step in SWsofts OPEN FUSION strategy, Plesk and Virtuozzo are seamlessly integrated. Also, Plesk users will benefit from a new level of integration with other SWsoft products, including HSPcomplete, SiteBuilder and PEM. The completely customizable "Application Vault" can manage dozens of integrated applications including Ecommerce, Chat, and Bulletin Board.
Fully Automated
Plesk for Windows and Plesk for UNIX reload your control panel and keep it reloaded. With 100+ new enhancements the software delivers a new ease of management through features like our key auto-update mechanism, auto-component updater, migration manager and a Web-based installation for quick deployment and dedicated need for support.
Advanced Linux/Windows Platform Support
Plesk for UNIX and Windows now have many common features, skins, application packs, language packs and documentation. Operating systems supported are RedHat, SuSE, Fedora Core, FreeBSD, Debian and Windows.
Plesk project helps Web hosting companies and their reseller clients deliver better, faster service to domain owners by sharing server management with them.
Enhancements:
- Major UI improvements include a quick and efficient task-oriented desktop interface, customizable interface templates, and information about new features.
- New versions of Autoinstaller, Watchdog, Backup, and Migration components are included.
- Support was added for MySQL 4.1, PostgreSQL 7.3, mod_jk, PAM auth, APOP, domain aliases, qmail queue management, and remote database servers.
<<lessInnovative Ease of Use
Plesk has a redesigned cleaner and easier to use interface. Plesk comes with many additional skins and even gives users the ability to design custom skins and manage them in the browser-based interface. In particular, the new desktop feature increases the usability and flexibility of the software significantly.
Highest Stability
Plesk has been specifically designed to be the most stable and secure control panel available. Plesk has been proven under fire managing 5 million plus domains globally and can support thousands of accounts per server increasing profitability.
Most Secure
Not only does Plesk contain new security measures but also, existing security features have been improved. The softwares redesigned subsystem improves overall system security as well as support for 3rd party FTP servers that make secure uploads possible.
Comprehensive
As the next step in SWsofts OPEN FUSION strategy, Plesk and Virtuozzo are seamlessly integrated. Also, Plesk users will benefit from a new level of integration with other SWsoft products, including HSPcomplete, SiteBuilder and PEM. The completely customizable "Application Vault" can manage dozens of integrated applications including Ecommerce, Chat, and Bulletin Board.
Fully Automated
Plesk for Windows and Plesk for UNIX reload your control panel and keep it reloaded. With 100+ new enhancements the software delivers a new ease of management through features like our key auto-update mechanism, auto-component updater, migration manager and a Web-based installation for quick deployment and dedicated need for support.
Advanced Linux/Windows Platform Support
Plesk for UNIX and Windows now have many common features, skins, application packs, language packs and documentation. Operating systems supported are RedHat, SuSE, Fedora Core, FreeBSD, Debian and Windows.
Plesk project helps Web hosting companies and their reseller clients deliver better, faster service to domain owners by sharing server management with them.
Enhancements:
- Major UI improvements include a quick and efficient task-oriented desktop interface, customizable interface templates, and information about new features.
- New versions of Autoinstaller, Watchdog, Backup, and Migration components are included.
- Support was added for MySQL 4.1, PostgreSQL 7.3, mod_jk, PAM auth, APOP, domain aliases, qmail queue management, and remote database servers.
Download (MB)
Added: 2006-04-05 License: GPL (GNU General Public License) Price: $199
1330 downloads
Dirvish 1.2.1
Dirvish project is a fast, disk based, rotating network backup system. more>>
Dirvish project is a fast, disk based, rotating network backup system.
With dirvish you can maintain a set of complete images of your filesystems with unattended creation and expiration. A dirvish backup vault is like a time machine for your data.
<<lessWith dirvish you can maintain a set of complete images of your filesystems with unattended creation and expiration. A dirvish backup vault is like a time machine for your data.
Download (0.048MB)
Added: 2006-05-10 License: GPL (GNU General Public License) Price:
1262 downloads
Project Elevate 0.1.0
Project Elevate is an attempt to free users from the desktop metaphor. more>>
Project Elevate is an attempt to free users from the desktop metaphor.
Project Elevate offers a fixed set of applications which allow casual users to perform the most usual tasks with their computer.
I dont like the way current desktop environments look and feel. I find them too complicated and too annoying. Computers "can" have simple interfaces similar to videos, mp3 players and mobile phones (at least the old ones). Many people argue that this is not possible since a computer has multiple roles, so the User Interface (UI) should be complicated. I disagree.
Multitasking is a myth. Only power users exploit it. Casual users do one thing at a time. They only read their email, or browse the web or work on office applications. The only other application 99% of casual users use in parallel is their music player to have background music. So yes, the computer can actually look and act in a simple way. We need one application per role.
Project Elevate is an experiment to support this claim. I am developing it for my own personal use but I am also making the code public so that other developers can help if they find it useful. Read the manifesto pages it you still wondering what is my motivation. The whole user environment consists of 4 distinct applications. New functionality comes from new application modules and not complete applications. Modules are NOT plugins or dynamically loaded libraries like in other frameworks.
These applications are:
- Central Hub - a starting place constitutes 5% of Project Elevate
- Vault - a place to store files 30% of Project Elevate
- Elevate - the all-singing-all-dancing task based environment 50% of Project Elevate
- Syndesis - a place to interface with external media 15% of Project Elevate
<<lessProject Elevate offers a fixed set of applications which allow casual users to perform the most usual tasks with their computer.
I dont like the way current desktop environments look and feel. I find them too complicated and too annoying. Computers "can" have simple interfaces similar to videos, mp3 players and mobile phones (at least the old ones). Many people argue that this is not possible since a computer has multiple roles, so the User Interface (UI) should be complicated. I disagree.
Multitasking is a myth. Only power users exploit it. Casual users do one thing at a time. They only read their email, or browse the web or work on office applications. The only other application 99% of casual users use in parallel is their music player to have background music. So yes, the computer can actually look and act in a simple way. We need one application per role.
Project Elevate is an experiment to support this claim. I am developing it for my own personal use but I am also making the code public so that other developers can help if they find it useful. Read the manifesto pages it you still wondering what is my motivation. The whole user environment consists of 4 distinct applications. New functionality comes from new application modules and not complete applications. Modules are NOT plugins or dynamically loaded libraries like in other frameworks.
These applications are:
- Central Hub - a starting place constitutes 5% of Project Elevate
- Vault - a place to store files 30% of Project Elevate
- Elevate - the all-singing-all-dancing task based environment 50% of Project Elevate
- Syndesis - a place to interface with external media 15% of Project Elevate
Download (MB)
Added: 2006-11-02 License: GPL (GNU General Public License) Price:
1090 downloads
FAangband 0.2.3
FAangband is a first age Tolkien-based variant of Angband. more>>
FAangband is a first age Tolkien-based variant of Angband.
A roguelike game set in the wilderness and dungeons of Middle Earth in the first age. Fight your way through plains, mountains, forests, swamps, deserts and dungeons to face Morgoth, Lord of Darkness. Not a short game.
Here are the big changes:
- Races have been significantly changed. Half-Orcs, Half-Trolls, Half-elves and Shadow Fairies have gone; there are new varieties of Elves, Dwarves and Men. Dwarves as a whole tend to have better Intelligence than Wisdom; the reverse is true for (most) Elves and Hobbits. Different races also have significantly different starting conditions.
- There is wilderness. Wilderness is like and unlike dungeon. On the similar side, it is randomly generated in rectangular pieces; the "level" still only goes up or down by one in going from one piece to the next; there is a structured way of advancing through the wilderness. On the other hand, it looks different (no rooms); there are sometimes choices as to how to advance (north or west, maybe, rather than just down); and tactics become quite different. There are five basic types of wilderness - open plains, dense forests, rocky mountains, harsh deserts and pathless swamps. It also has day and night, which affects light-hating monsters and the players need for light.
- There are multiple towns, small and large, spread throughout the wilderness. Each race starts in its natural town. This means that the starting towns for some races are in the middle of quite dangerous wilderness. In order to reduce extreme effects of this (instant death, or instant growth of 15 levels), some races have improved starting equipment, and several races start with some experience already (advancing them in character level up to a maximum of level 5). High elves are no longer the easy option, at least at first. You can move your house to a different town, but only once you have walked there.
- There are multiple dungeons (five, to be precise). At the bottom of each is a guardian, who can only appear there or in special circumstances (which you may be able to guess...) be summoned. The first specialist ability (and second as well for warriors) is still learned at the beginning, but the two others each become available on killing a dungeon guardian. It is possible to ignore the other dungeons and head straight for Angband, but theres a heavy price to pay.
- Word of Recall works differently. Read away from your home town, it still takes you back there. Read in your home town, you are given a list of up to four points to recall to. When you recall back to town, you get the choice of which of your recall points you wish to update.
- Anything from later than the First Age has been removed. No more Rings of Power, Grishnakh, Anduril, Saruman, Witch-King, etc. There are some new uniques, artifacts and ego-items (and some just renamed). There are also new item sets, and some reworked artifacts.
- There is no savefile compatibility with Oangband or Angband. Savefiles had to change at least to accommodate changes to data structures (particularly the player data), and the big changes to races meant that any translation would be rather artificial. Anyone with an Oangband savefile should keep playing it in Oangband; anyone with an Oangband compatible Angband savefile (version 2.9.1 or older) should be congratulated and, well, upgrade.
Enhancements:
- large reduction in wilderness monsters
- better handling of savefile paths
- increase in wilderness vaults
- some extra dungeon vaults
- several bugfixes
<<lessA roguelike game set in the wilderness and dungeons of Middle Earth in the first age. Fight your way through plains, mountains, forests, swamps, deserts and dungeons to face Morgoth, Lord of Darkness. Not a short game.
Here are the big changes:
- Races have been significantly changed. Half-Orcs, Half-Trolls, Half-elves and Shadow Fairies have gone; there are new varieties of Elves, Dwarves and Men. Dwarves as a whole tend to have better Intelligence than Wisdom; the reverse is true for (most) Elves and Hobbits. Different races also have significantly different starting conditions.
- There is wilderness. Wilderness is like and unlike dungeon. On the similar side, it is randomly generated in rectangular pieces; the "level" still only goes up or down by one in going from one piece to the next; there is a structured way of advancing through the wilderness. On the other hand, it looks different (no rooms); there are sometimes choices as to how to advance (north or west, maybe, rather than just down); and tactics become quite different. There are five basic types of wilderness - open plains, dense forests, rocky mountains, harsh deserts and pathless swamps. It also has day and night, which affects light-hating monsters and the players need for light.
- There are multiple towns, small and large, spread throughout the wilderness. Each race starts in its natural town. This means that the starting towns for some races are in the middle of quite dangerous wilderness. In order to reduce extreme effects of this (instant death, or instant growth of 15 levels), some races have improved starting equipment, and several races start with some experience already (advancing them in character level up to a maximum of level 5). High elves are no longer the easy option, at least at first. You can move your house to a different town, but only once you have walked there.
- There are multiple dungeons (five, to be precise). At the bottom of each is a guardian, who can only appear there or in special circumstances (which you may be able to guess...) be summoned. The first specialist ability (and second as well for warriors) is still learned at the beginning, but the two others each become available on killing a dungeon guardian. It is possible to ignore the other dungeons and head straight for Angband, but theres a heavy price to pay.
- Word of Recall works differently. Read away from your home town, it still takes you back there. Read in your home town, you are given a list of up to four points to recall to. When you recall back to town, you get the choice of which of your recall points you wish to update.
- Anything from later than the First Age has been removed. No more Rings of Power, Grishnakh, Anduril, Saruman, Witch-King, etc. There are some new uniques, artifacts and ego-items (and some just renamed). There are also new item sets, and some reworked artifacts.
- There is no savefile compatibility with Oangband or Angband. Savefiles had to change at least to accommodate changes to data structures (particularly the player data), and the big changes to races meant that any translation would be rather artificial. Anyone with an Oangband savefile should keep playing it in Oangband; anyone with an Oangband compatible Angband savefile (version 2.9.1 or older) should be congratulated and, well, upgrade.
Enhancements:
- large reduction in wilderness monsters
- better handling of savefile paths
- increase in wilderness vaults
- some extra dungeon vaults
- several bugfixes
Download (2.7MB)
Added: 2007-04-22 License: Freeware Price:
915 downloads
Storage Resource Broker 3.4.2
Storage Resource Broker is a network data storage middleware. more>>
Storage Resource Broker is client-server middleware that provides a uniform interface for connecting to heterogeneous data resources over a network and accessing replicated data sets.
SRB, in conjunction with the Metadata Catalog (MCAT), provides a way to access data sets and resources based on their attributes and/or logical names rather than their names or physical locations.
Starting with SRB 2.1.1 we now have an install script, install.pl, that can do a complete Postgres, MCAT and SRB installation. See README.MCAT.INSTALL. With SRB 3.0.0, this script can run on Solaris too, as well as the original Linux and Mac OS X.
The SEA authentication system is no longer recommended; for the secure authentication use either the ENCRYPT1 form of MDAS_AUTH authentication, or GSI. It should be noted that if the SEA authentication scheme is to be used and if the SEA library (libsea.a) does not already exist on your build platform, the SEA software that can be downloaded at the
URL must be built first.
1) Build configuration.
This version uses the configure script to configure the build. Most of the configurable parameters for building the SRB server and client can be configured using the "./configure" script. Run "./configure --help" for more information.
All configurable parameters for building the SRB server and the client library, including those set by the configure script, are defined in the mk/mk.config.in file. (The configure script automatically generates a third file, mk/mk.config, using mk/mk.config.in as a
template.)
Those parameters that cannot be modified via the configure script (because flags for those parameters have not yet been implemented) are set by directly editing the mk/mk.config.in file prior to running "./configure". Comments in the mk/mk.config.in file make it clear whether or not a particular parameter can be set through the configure
script, and if so, how to do so.
NOTE: The configure script does a number of self tests before the configuration is carried out. One of the test it does is the compiler test which it assumes "gcc" as the default compiler. If "gcc" is not installed or if the test of "gcc" failed (which happened on an AIX platform), the configure script should be re-run with the env variable CC set to cc or other compilers. This will override the default in the compiler test.
If the configure script still failed, do the following:
a) cd SRB2_0_0rel
b) ./config.rescue
c) edit the mk/mk.config file
2) Configure examples
a) Non-MCAT-enabled server and client, type in
configure
This will configure the mk.config file to build a non-MCAT enabled
server and client with the default settings.
b) Non-MCAT-enabled server and client with java enabled, type in
configure --enable-javagui=yes --enable-jdkhome=/usr/local/apps/jdk1.4.1
where /usr/local/apps/jdk1.4.1 is the directory where the JAVA JDK 1.4.1
is installed.
c) MCAT-enabled server with Oracle 8.1.5 MCAT, type in
configure --enable-oramcat --enable-oraver=815
--enable-orahome=/usr/local/apps/oracle/product/8.1.7
where /usr/local/apps/oracle/product/8.1.7 is the Oracle home
directory.
2) Parameters in the mk/mk.config file
The SRB architecture supports multiple SRB servers running on various hosts. Each SRB server may be built with different options, as set by the configure script and/or defined in the mk/mk.config.in file. For example, the SRB server on host A may include the driver for accessing HPSS and the SRB server on host B may include the driver for accessing the Lobj stored in DB2, etc.
The parameters are self-explanatory through the comments given in this file. Some of the more important parameters are discussed below:
installDir - The absolute path of the SRB install directory.
PORTNAME - The OS platform of this SRB port. Currently, the SRB software runs on 8 platforms. i.e., valid PORTNAMEs are :
PORTNAME_solaris, PORTNAME_sunos, PORTNAME_linux, PORTNAME_osx,
PORTNAME_aix, PORTNAME_alpha, PORTNAME_c90 and PORTNAME_sgi.
SRB_LARGEFILE64 - defines whether the 64 bit file size is supported by the underlining driver of this SRB server. Current, 64 bit file size is supported by the ORTNAME_solaris, PORTNAME_aix, PORTNAME_linux and PORTNAME_c90 platforms.
ORAMCAT - defines that this SRB server being built is MDAS enabled and the MCAT is stored in Oracle DBMS. Normally, only one SRB server is MDAS enabled.
DB2MCAT - defines that this SRB server being built is MDAS enabled and the MCAT is stored in Oracle DBMS. Normally, only one SRB server is MDAS enabled.
NOTE : Both ORAMCAT and DB2MCAT cannot be defined at the same time.
ADDR_64BIT - defines whether to compile for 64 bits address. This option has only been tested for the the Solaris and Linux platforms.
PARA_OPR - defines whether this SRB server support parallel operation API.
MDAS_AUTH - defines whether the plain text and encrypted password MDAS authorization scheme will be supported. If used, the user/passwd pair registered with the MDAS catalog will be used to authenticate a user. Comment it out if the SRB server does not support MDAS authorization.
NOTE : A server can be built to support either MDAS_AUTH (plain or encrypted (ENCRYPT1)) or GSI_AUTH, or both.
SEA_AUTH - defines whether SEA authorization scheme will be supported. The software can be configured to support both SEA_AUTH and MDAS_AUTH. (SEA is no longer recommended.)
LIB_SEA - Is needed only if SEA_AUTH is defined. LIB_SEA specifies where the SEA client library is located.
GSI_AUTH - defines whether the GSI authentication scheme is supported. This is set when --enable-gsi-auth is included on the configure line.
NOTE : A server can be built to support either MDAS_AUTH or GSI_AUTH,
or both.
LIB_GSI_AUTH - Set by configure when --enable-gsi-auth is included (i.e. GSI_AUTH is defined). LIB_GSI_AUTH specifies where the GSI client libraries are located. The optional configure --enable-globus-location=path can also be used specify the parent
location of the GSI libaries, and will cause LIB_GSI_AUTH to be adjusted.
JAVA_GUI and javaDir - JAVA_GUI defines whether the srbBrowser should be built. javaDir specifies the directory where the JDK software is installed. (e.g. /usr/local/apps/Java). See README.srbBrowser for more details.
3) "cd" to the main SRB directory and type in "gmake clean" and then "gmake" to make the SRB software. The Makefile contains various options to make and clean all or a subset of the build.
- gmake --- build all.
- gmake clean --- clean all.
- gmake srb --- build only the SRB server and client.
- gmake clean_srb --- clean only the SRB server and client.
- gmake util --- build only the utilities (S commands). See README.utilities for more details.
- gmake clean_util --- clean only the utilities.
- gmake browser - build only the java srbBrowser GUI. See README.srbBrowser for more details.
- gmake clean_browser - clean only the java srbBrowser.
4) (Optional) Type in "gmake install" to install the software in the $(installDir) directory. This procedure installs the following modules in the $(installDir) directory:
bin/runsrb - The script that starts the SRB
bin/srbMaster2_0_0 - The frontend server.
bin/srbServer - The backend server (forked by the srbMaster1_0 for each client connection).
bin/libSrbClient.a - The client library.
data/hostAuthConfig - The optional (needed only if HOST_BASED_AUTH in the mk.config file is set) host based authorization configuration file.
data/mcatHost - This file identifies the host on which the MCAT enabled SRB server is running.
data/hostConfig - This is the optional SRB host configuration file. It is only needed when when you want to add aliases to your local hostName.
data/hpssCosConfig - This is the optional HPSS Class of Services configuration file. It is only needed if HPSS in the mk.config file is set.
data/hpssNodceAuth - The file contains authentication info for non-dce HPSS. It is only needed if the HPSS and NO_DCE flags in the mk.config file are set.
data/MdasConfig - The MDAS configuration file.
data/metadata.fkrel - This file defines the foreign key relationship between the MDAS catalog tables and is used internally by the SRB for query generation. This file should not be changed between releases.
data/LobjConfig - The database configuration file for the DB Large Object driver. Basically, it contains the userID and password for accessing each database server.
Enhancements:
- Three vulnerabilities that allow SRB users to read/write non-Vault files that are readable/writable by the the srbadmin user were fixed.
- A bug that causes the GridFTP driver to use the wrong credential to connect to GridFtp server was fixed.
- A file descriptor lock bug was fixed.
- Uploading files larger than 2 gigabytes into GridFtp resources now works.
- Timeout bugs that could arise when sending large numbers of files were fixed.
- A core dump problem for HPSS type resources involving parallel I/O on Linux servers was fixed.
- A new option -o was added to show collection ownership in SgetColl.
<<lessSRB, in conjunction with the Metadata Catalog (MCAT), provides a way to access data sets and resources based on their attributes and/or logical names rather than their names or physical locations.
Starting with SRB 2.1.1 we now have an install script, install.pl, that can do a complete Postgres, MCAT and SRB installation. See README.MCAT.INSTALL. With SRB 3.0.0, this script can run on Solaris too, as well as the original Linux and Mac OS X.
The SEA authentication system is no longer recommended; for the secure authentication use either the ENCRYPT1 form of MDAS_AUTH authentication, or GSI. It should be noted that if the SEA authentication scheme is to be used and if the SEA library (libsea.a) does not already exist on your build platform, the SEA software that can be downloaded at the
URL must be built first.
1) Build configuration.
This version uses the configure script to configure the build. Most of the configurable parameters for building the SRB server and client can be configured using the "./configure" script. Run "./configure --help" for more information.
All configurable parameters for building the SRB server and the client library, including those set by the configure script, are defined in the mk/mk.config.in file. (The configure script automatically generates a third file, mk/mk.config, using mk/mk.config.in as a
template.)
Those parameters that cannot be modified via the configure script (because flags for those parameters have not yet been implemented) are set by directly editing the mk/mk.config.in file prior to running "./configure". Comments in the mk/mk.config.in file make it clear whether or not a particular parameter can be set through the configure
script, and if so, how to do so.
NOTE: The configure script does a number of self tests before the configuration is carried out. One of the test it does is the compiler test which it assumes "gcc" as the default compiler. If "gcc" is not installed or if the test of "gcc" failed (which happened on an AIX platform), the configure script should be re-run with the env variable CC set to cc or other compilers. This will override the default in the compiler test.
If the configure script still failed, do the following:
a) cd SRB2_0_0rel
b) ./config.rescue
c) edit the mk/mk.config file
2) Configure examples
a) Non-MCAT-enabled server and client, type in
configure
This will configure the mk.config file to build a non-MCAT enabled
server and client with the default settings.
b) Non-MCAT-enabled server and client with java enabled, type in
configure --enable-javagui=yes --enable-jdkhome=/usr/local/apps/jdk1.4.1
where /usr/local/apps/jdk1.4.1 is the directory where the JAVA JDK 1.4.1
is installed.
c) MCAT-enabled server with Oracle 8.1.5 MCAT, type in
configure --enable-oramcat --enable-oraver=815
--enable-orahome=/usr/local/apps/oracle/product/8.1.7
where /usr/local/apps/oracle/product/8.1.7 is the Oracle home
directory.
2) Parameters in the mk/mk.config file
The SRB architecture supports multiple SRB servers running on various hosts. Each SRB server may be built with different options, as set by the configure script and/or defined in the mk/mk.config.in file. For example, the SRB server on host A may include the driver for accessing HPSS and the SRB server on host B may include the driver for accessing the Lobj stored in DB2, etc.
The parameters are self-explanatory through the comments given in this file. Some of the more important parameters are discussed below:
installDir - The absolute path of the SRB install directory.
PORTNAME - The OS platform of this SRB port. Currently, the SRB software runs on 8 platforms. i.e., valid PORTNAMEs are :
PORTNAME_solaris, PORTNAME_sunos, PORTNAME_linux, PORTNAME_osx,
PORTNAME_aix, PORTNAME_alpha, PORTNAME_c90 and PORTNAME_sgi.
SRB_LARGEFILE64 - defines whether the 64 bit file size is supported by the underlining driver of this SRB server. Current, 64 bit file size is supported by the ORTNAME_solaris, PORTNAME_aix, PORTNAME_linux and PORTNAME_c90 platforms.
ORAMCAT - defines that this SRB server being built is MDAS enabled and the MCAT is stored in Oracle DBMS. Normally, only one SRB server is MDAS enabled.
DB2MCAT - defines that this SRB server being built is MDAS enabled and the MCAT is stored in Oracle DBMS. Normally, only one SRB server is MDAS enabled.
NOTE : Both ORAMCAT and DB2MCAT cannot be defined at the same time.
ADDR_64BIT - defines whether to compile for 64 bits address. This option has only been tested for the the Solaris and Linux platforms.
PARA_OPR - defines whether this SRB server support parallel operation API.
MDAS_AUTH - defines whether the plain text and encrypted password MDAS authorization scheme will be supported. If used, the user/passwd pair registered with the MDAS catalog will be used to authenticate a user. Comment it out if the SRB server does not support MDAS authorization.
NOTE : A server can be built to support either MDAS_AUTH (plain or encrypted (ENCRYPT1)) or GSI_AUTH, or both.
SEA_AUTH - defines whether SEA authorization scheme will be supported. The software can be configured to support both SEA_AUTH and MDAS_AUTH. (SEA is no longer recommended.)
LIB_SEA - Is needed only if SEA_AUTH is defined. LIB_SEA specifies where the SEA client library is located.
GSI_AUTH - defines whether the GSI authentication scheme is supported. This is set when --enable-gsi-auth is included on the configure line.
NOTE : A server can be built to support either MDAS_AUTH or GSI_AUTH,
or both.
LIB_GSI_AUTH - Set by configure when --enable-gsi-auth is included (i.e. GSI_AUTH is defined). LIB_GSI_AUTH specifies where the GSI client libraries are located. The optional configure --enable-globus-location=path can also be used specify the parent
location of the GSI libaries, and will cause LIB_GSI_AUTH to be adjusted.
JAVA_GUI and javaDir - JAVA_GUI defines whether the srbBrowser should be built. javaDir specifies the directory where the JDK software is installed. (e.g. /usr/local/apps/Java). See README.srbBrowser for more details.
3) "cd" to the main SRB directory and type in "gmake clean" and then "gmake" to make the SRB software. The Makefile contains various options to make and clean all or a subset of the build.
- gmake --- build all.
- gmake clean --- clean all.
- gmake srb --- build only the SRB server and client.
- gmake clean_srb --- clean only the SRB server and client.
- gmake util --- build only the utilities (S commands). See README.utilities for more details.
- gmake clean_util --- clean only the utilities.
- gmake browser - build only the java srbBrowser GUI. See README.srbBrowser for more details.
- gmake clean_browser - clean only the java srbBrowser.
4) (Optional) Type in "gmake install" to install the software in the $(installDir) directory. This procedure installs the following modules in the $(installDir) directory:
bin/runsrb - The script that starts the SRB
bin/srbMaster2_0_0 - The frontend server.
bin/srbServer - The backend server (forked by the srbMaster1_0 for each client connection).
bin/libSrbClient.a - The client library.
data/hostAuthConfig - The optional (needed only if HOST_BASED_AUTH in the mk.config file is set) host based authorization configuration file.
data/mcatHost - This file identifies the host on which the MCAT enabled SRB server is running.
data/hostConfig - This is the optional SRB host configuration file. It is only needed when when you want to add aliases to your local hostName.
data/hpssCosConfig - This is the optional HPSS Class of Services configuration file. It is only needed if HPSS in the mk.config file is set.
data/hpssNodceAuth - The file contains authentication info for non-dce HPSS. It is only needed if the HPSS and NO_DCE flags in the mk.config file are set.
data/MdasConfig - The MDAS configuration file.
data/metadata.fkrel - This file defines the foreign key relationship between the MDAS catalog tables and is used internally by the SRB for query generation. This file should not be changed between releases.
data/LobjConfig - The database configuration file for the DB Large Object driver. Basically, it contains the userID and password for accessing each database server.
Enhancements:
- Three vulnerabilities that allow SRB users to read/write non-Vault files that are readable/writable by the the srbadmin user were fixed.
- A bug that causes the GridFTP driver to use the wrong credential to connect to GridFtp server was fixed.
- A file descriptor lock bug was fixed.
- Uploading files larger than 2 gigabytes into GridFtp resources now works.
- Timeout bugs that could arise when sending large numbers of files were fixed.
- A core dump problem for HPSS type resources involving parallel I/O on Linux servers was fixed.
- A new option -o was added to show collection ownership in SgetColl.
Download (16.5MB)
Added: 2006-07-07 License: Free For Educational Use Price:
1207 downloads
Mergence HL7 Integration Engine 1.1
Mergence is a high performance, open source HL7integration engine and application platform. more>>
Mergence is a high performance, open source HL7integration engine and application platform. It was developed to fill the need for an open source, fully transactional healthcare integration system capable of handling millions of messages per day, and thousands of concurrent LLP connections. Mergence is based on Apache ServiceMix, a lightweight enterprise service bus which conforms to the JBI standard, and HAPI, an excellent opensource HL7v2 API. We plan to support HL7v3 in the next release.
Mergence is still in heavy development, and documentation is still lacking, but the current release is already production-ready if you dont mind working with some XML. We have a well-tested and solid core in place, which is fully usable. Development of an AJAX administration console is underway and is the main focus of the 2.0 release.
We hope to have more complete documentation available in the next week.
Main features:
- Fully open source, under the GNU General Public License
- Built on standards-based technologies.
- End-to-end persistence with global transactions so no message can ever be lost.
- High-throughput, asynchronous architecture.
- Message vault with encrypted storage (embedded or external DB).
- Flexible message routing and transformation.
- Scriptable using Groovy
- Extensive logging, monitoring, and alerting system.
- Supports active clustering.
- Many bundled connectors, and compatible with any ServiceMix JBI component.
- NIO TCP connectors which can support thousands of concurrent connections.
- Support for processing/transforming flat files of unlimited size.
- Hot deployment of new components and configurations.
- JBI extensions for easily developing new HL7 components.
<<lessMergence is still in heavy development, and documentation is still lacking, but the current release is already production-ready if you dont mind working with some XML. We have a well-tested and solid core in place, which is fully usable. Development of an AJAX administration console is underway and is the main focus of the 2.0 release.
We hope to have more complete documentation available in the next week.
Main features:
- Fully open source, under the GNU General Public License
- Built on standards-based technologies.
- End-to-end persistence with global transactions so no message can ever be lost.
- High-throughput, asynchronous architecture.
- Message vault with encrypted storage (embedded or external DB).
- Flexible message routing and transformation.
- Scriptable using Groovy
- Extensive logging, monitoring, and alerting system.
- Supports active clustering.
- Many bundled connectors, and compatible with any ServiceMix JBI component.
- NIO TCP connectors which can support thousands of concurrent connections.
- Support for processing/transforming flat files of unlimited size.
- Hot deployment of new components and configurations.
- JBI extensions for easily developing new HL7 components.
Download (30.9MB)
Added: 2007-06-07 License: GPL (GNU General Public License) Price:
533 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above vault 4.100 search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
