wsgi middleware
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 48
wsgi_intercept 0.4
Installs a WSGI application in place of a real URI for testing. more>>
wsgi_intercept 0.4 is yet another excellent utility for programmers. It is actually a library which lets you intercept calls to any specific host/port combination and redirect them into a WSGI application importable by your test program instead of normally starting a server at a local host and port, then pointing your test code to that address. Thus, you can avoid spawning multiple processes or threads to test your Web app. Installs a WSGI application in place of a real URI for testing.
This package works by replacing httplib. HTTPConnection with a subclass, wsgi_intercept. WSGI_HTTPConnection. This class then redirects specific server/port combination into a WSGI application by emulating a socket. If no intercept is registered for the host and port requested, those requests are passed on to the standard handler.
The functions add_wsgi_intercept (host, port, app_create_fn, script_name=) and remove_wsgi_intercept (host, port) specify which URLs should be redirect into what applications. Note especially that app_create_fn is a function object returning a WSGI application; script_name becomes SCRIPT_NAME in the WSGI apps environment, if it is set.
Requirements:
- Python
Added: 2009-01-07 License: MIT/X Consortium Lic... Price: FREE
14 downloads
Secure Storage service for the gLite middleware 1.1.2-1
Secure Storage service for the gLite middleware provides users with a set of tools to store data in a secure way. more>>
Secure Storage service for the gLite middleware project provides users with a set of tools to store in a secure way and in an encrypted format confidential data (e.g. medical or financial data) on the grid storage elements.
The data stored using the tools provided will be accessible and readable only by authorized users. Moreover, it solves the insider abuse problem preventing also the administrators of the storage elements to access the confidential data in a clear format.
The service has been designed and developed for the grid Middleware of the EGEE infrastructure, gLite, in the context of the TriGrid VL Project.
Secure Storage documentation generated with Doxygen are available.
Enhancements:
- A minor bug was fixed.
<<lessThe data stored using the tools provided will be accessible and readable only by authorized users. Moreover, it solves the insider abuse problem preventing also the administrators of the storage elements to access the confidential data in a clear format.
The service has been designed and developed for the grid Middleware of the EGEE infrastructure, gLite, in the context of the TriGrid VL Project.
Secure Storage documentation generated with Doxygen are available.
Enhancements:
- A minor bug was fixed.
Download (0.088MB)
Added: 2007-07-24 License: The Apache License 2.0 Price:
823 downloads
Other version of Secure Storage service for the gLite middleware
gLite middleware 1.0.0-4 (Keystore Server)Secure Storage service for the gLite middleware 1 ... gLite middleware. Secure Storage service for the gLite middleware project provides users withLicense:The Apache License 2.0
mod_libpq 0.1a3
mod_libpq is an Apache 1.3 Web server module which maintains persistent connections to one or more PostgreSQL databases. more>>
mod_libpq is an Apache 1.3 Web server module which maintains persistent connections to one or more PostgreSQL databases, eliminating the need for cumbersome middleware "glue".
Millions of complex pages can be fully or partially pre-rendered, stored in a database, and then served directly to the Web.
One database can be associated with the main Apache server and an additional database can be associated with each virtual host defined in httpd.conf.
Requests are converted into a pair of user configurable queries which are sent directly to the database via PostgreSQLs libpq API. The first query processes the request headers and the second query returns the document content.
Enhancements:
- This release added support for specifying the content type of returned documents.
- The content type and the content and header queries can now be associated with specific directories and locations in the Apache configuration file, allowing much more complex Web sites to be defined.
- Database connections can be deferred until the first request or disabled entirely to reduce resource requirements.
- More advanced examples were provided.
- The license has been changed to the BSD license.
<<lessMillions of complex pages can be fully or partially pre-rendered, stored in a database, and then served directly to the Web.
One database can be associated with the main Apache server and an additional database can be associated with each virtual host defined in httpd.conf.
Requests are converted into a pair of user configurable queries which are sent directly to the database via PostgreSQLs libpq API. The first query processes the request headers and the second query returns the document content.
Enhancements:
- This release added support for specifying the content type of returned documents.
- The content type and the content and header queries can now be associated with specific directories and locations in the Apache configuration file, allowing much more complex Web sites to be defined.
- Database connections can be deferred until the first request or disabled entirely to reduce resource requirements.
- More advanced examples were provided.
- The license has been changed to the BSD license.
Download (0.015MB)
Added: 2006-06-20 License: BSD License Price:
1221 downloads
GRIDportal 0.5.4
GRIDportal is a Web-based application portal that acts as a frontend to GRID computing. more>>
GRIDportal is a Web-based application portal that acts as a frontend to GRID computing. GRIDportals aim is to make common GRID applications like Abaqus, Matlab, or BLAST more accessible to the user.
Use of GRIDportal does not require any knowledge of Unix nor GRID computing whatsoever. All the user needs to know is how to use the given application, so the step from desktop computing to GRID computing should thus become a much smaller one than it otherwise would be.
GRIDportal, written in Python and based on Webware for Python, is meant to be modular, which allows quick development of plugins for new applications.
GRIDportal is built on top of NorduGrid/ARC middleware and depends on the middleware to function. This relationship between GRIDportal and NorduGrid/ARC also allows a user to access the entire NorduGrid network through GRIDportal (provided the user has the necessary credentials), thus making GRIDportal a gateway to a whole range of different GRID sites.
GRIDportal was born from Jonas Lindemanns LUNARC Application Portal and is distributed under the GPL licence.
<<lessUse of GRIDportal does not require any knowledge of Unix nor GRID computing whatsoever. All the user needs to know is how to use the given application, so the step from desktop computing to GRID computing should thus become a much smaller one than it otherwise would be.
GRIDportal, written in Python and based on Webware for Python, is meant to be modular, which allows quick development of plugins for new applications.
GRIDportal is built on top of NorduGrid/ARC middleware and depends on the middleware to function. This relationship between GRIDportal and NorduGrid/ARC also allows a user to access the entire NorduGrid network through GRIDportal (provided the user has the necessary credentials), thus making GRIDportal a gateway to a whole range of different GRID sites.
GRIDportal was born from Jonas Lindemanns LUNARC Application Portal and is distributed under the GPL licence.
Download (1.5MB)
Added: 2006-07-26 License: GPL (GNU General Public License) Price:
1185 downloads
OpenChronicle 1.0 RC1
OpenChronicle is a real world blogging application with basic functionality similar to websites such as Blogger, WordPress. more>>
OpenChronicle is a real world blogging application with basic functionality similar to websites such as Blogger, WordPress, LiveJournal and MySpace.
OpenChronicles purpose is to demonstrate how to use individual subsystems available as part of OpenSubsystems project when developing Java applications. It is an excellent learning resource for those who want to master the available subsystems or maybe just want to quickly lookup how to use some particular feature.
The detailed tutorials document every step of design and development process that is required to quickly create fully featured application that is portable and easily maintainable. Each successive version expands the previous one with desirable features that are implemented easily by integrating another available subsystem or some aspect of its functionality.
Enhancements:
- OpenChronicle is a comprehensive tutorial to development of Java applications using Open Core middleware abstraction layer.
- The tutorial walks the developer through the design and implementation of a real world blogging application.
- It describes how to easily implement the application data model, code persistence working with any of the supported databases, make the application work as a POJO or EJB using any of the supported J2EE application servers, and how to design a flexible, skinnable Web user interface with basic security features.
<<lessOpenChronicles purpose is to demonstrate how to use individual subsystems available as part of OpenSubsystems project when developing Java applications. It is an excellent learning resource for those who want to master the available subsystems or maybe just want to quickly lookup how to use some particular feature.
The detailed tutorials document every step of design and development process that is required to quickly create fully featured application that is portable and easily maintainable. Each successive version expands the previous one with desirable features that are implemented easily by integrating another available subsystem or some aspect of its functionality.
Enhancements:
- OpenChronicle is a comprehensive tutorial to development of Java applications using Open Core middleware abstraction layer.
- The tutorial walks the developer through the design and implementation of a real world blogging application.
- It describes how to easily implement the application data model, code persistence working with any of the supported databases, make the application work as a POJO or EJB using any of the supported J2EE application servers, and how to design a flexible, skinnable Web user interface with basic security features.
Download (0.17MB)
Added: 2006-09-07 License: GPL (GNU General Public License) Price:
1142 downloads
Eidetic 2.3.3
Eidetic is a middleware library for creating database applications in Perl. more>>
Eidetic project is a middleware library for creating database applications in Perl.
Eidetic is a middleware library for building database driven applications with Perl and Template::Toolkit. It provides handlers for displaying, editing, searching, and administrating data.
It provides an interface-generic way of building db apps allowing Web, command line, or daemon styles of interfaces.
It is currently used by several applications, including STP, docsys, and rackview.
<<lessEidetic is a middleware library for building database driven applications with Perl and Template::Toolkit. It provides handlers for displaying, editing, searching, and administrating data.
It provides an interface-generic way of building db apps allowing Web, command line, or daemon styles of interfaces.
It is currently used by several applications, including STP, docsys, and rackview.
Download (0.091MB)
Added: 2007-01-22 License: GPL (GNU General Public License) Price:
1007 downloads
Castore 1.1.2
Castore takes place in a user-centered design approach to build an open archive platform. more>>
Castore comes from CApitalization & STORagE and takes place in a user-centered design approach to build an open archive platform, planned to create institutional repositories, managed by librarians in their respective institutions.
With this system, the authors are able to store, convert (XML), fully index, manage, perpetuate, valorize, and distribute their digital documents.
It uses an assembly of components (Tomcat, OO, JDO, Saxon, Lucene, etc.) to build middleware applications, relying on XML and any relational database.
The system has been developed with a component architecture (J2EE) to be able to integrate the platform with any intranet environment with the minimum cost of development.
<<lessWith this system, the authors are able to store, convert (XML), fully index, manage, perpetuate, valorize, and distribute their digital documents.
It uses an assembly of components (Tomcat, OO, JDO, Saxon, Lucene, etc.) to build middleware applications, relying on XML and any relational database.
The system has been developed with a component architecture (J2EE) to be able to integrate the platform with any intranet environment with the minimum cost of development.
Download (18.3MB)
Added: 2006-02-02 License: CeCILL (CeCILL Free Software License Agreement) Price:
1359 downloads
Sequoia 2.10.9
Sequoia is a transparent middleware solution for offering clustering, load balancing and failover services for any database. more>>
Sequoia is a transparent middleware solution for offering clustering, load balancing and failover services for any database. Sequoia is the continuation of the C-JDBC project.
Sequoia database is distributed and replicated among several nodes and C-JDBC balances the queries among these nodes. Sequoia handles node failures and provides support for checkpointing and hot recovery.
C-JDBC is a database cluster middleware that allows any Java application (standalone application, servlet or EJB container, ...) to transparently access a cluster of databases through JDBC.
C-JDBC handles node failures and provides support for checkpointing and hot recovery.
Main features:
- No modification of existing applications or databases,
- High availability provided by advanced RAIDb technology,
- Performance scalability with unique load balancing and query result caching features,
- Integrated JMX-based administration and monitoring,
- 100% Java implementation allowing portability across platforms,
- Open source licensed under LGPL,
- Professional support, training and consulting available from C-JDBC professional services.
Whats New in 2.10.9 Stable Release:
- This release fixes a compatibility problem between Appia and Hedera that was introduced by the previous release.
- The 2.10.8 release was delivered with an incorrect appia.jar (3.2.3).
Whats New in 3.0 Beta 2 Development Release:
- This release includes a long list of feature improvements and bugfixes.
- A new embedded recovery log has been implemented for a transactional log without configuration.
- New demos are based on these new features.
- Other usability improvements and performance enhancements are also part of this release.
<<lessSequoia database is distributed and replicated among several nodes and C-JDBC balances the queries among these nodes. Sequoia handles node failures and provides support for checkpointing and hot recovery.
C-JDBC is a database cluster middleware that allows any Java application (standalone application, servlet or EJB container, ...) to transparently access a cluster of databases through JDBC.
C-JDBC handles node failures and provides support for checkpointing and hot recovery.
Main features:
- No modification of existing applications or databases,
- High availability provided by advanced RAIDb technology,
- Performance scalability with unique load balancing and query result caching features,
- Integrated JMX-based administration and monitoring,
- 100% Java implementation allowing portability across platforms,
- Open source licensed under LGPL,
- Professional support, training and consulting available from C-JDBC professional services.
Whats New in 2.10.9 Stable Release:
- This release fixes a compatibility problem between Appia and Hedera that was introduced by the previous release.
- The 2.10.8 release was delivered with an incorrect appia.jar (3.2.3).
Whats New in 3.0 Beta 2 Development Release:
- This release includes a long list of feature improvements and bugfixes.
- A new embedded recovery log has been implemented for a transactional log without configuration.
- New demos are based on these new features.
- Other usability improvements and performance enhancements are also part of this release.
Download (10.67MB)
Added: 2007-07-31 License: The Apache License 2.0 Price:
514 downloads
libEtPan! 0.51
libEtPans purpose of this mail library is to provide a portable, efficient middleware for different kinds of mail access. more>>
libEtPans purpose of this mail library is to provide a portable, efficient middleware for different kinds of mail access.
When using the drivers interface, the interface is the same for all kinds of mail access, remote and local mailboxes.
libEtPan! project can read mbox, MH format, and Maildir mailboxes, and does MIME parsing.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- This release is just a bugfix release for the compile errors in 0.50, namely with enabled SASL, GnuTLS, and BIOs handling with openSSL.
<<lessWhen using the drivers interface, the interface is the same for all kinds of mail access, remote and local mailboxes.
libEtPan! project can read mbox, MH format, and Maildir mailboxes, and does MIME parsing.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- This release is just a bugfix release for the compile errors in 0.50, namely with enabled SASL, GnuTLS, and BIOs handling with openSSL.
Download (1.0MB)
Added: 2007-08-05 License: LGPL (GNU Lesser General Public License) Price:
811 downloads
KMLDonkey 0.10.1
KMLDonkey is an advanced GUI frontend for the MLDonkey P2P core. more>>
KMLDonkey is an advanced GUI frontend for the MLDonkey P2P core.
Main features:
- A flexible, powerful and KDE Style Guide compliant graphical interface.
- A complete implementation of the MLDonkey GUI protocol, meaning KMLDonkey can do everything the original GUI does, and more.
- Advanced configurable search forms.
- A convenient and configurable on-demand MLDonkey launcher.
- Real-time graphical bandwidth and network statistics.
- MobileMule middleware for controlling your MLDonkey using your Java enabled mobile phone.
- Embedded previewing of all downloads using KParts viewers.
- Embedded web browser providing P2P related web services such as availability and fake checks.
- KDE panel applet and system tray icon for statistics and easy access to the GUI.
- KIOSlave for opening current and complete downloads in all KDE applications (eg. "mldonkey:/Default/downloading/")
- Setup wizard for easy installation of the MLDonkey core.
Enhancements:
- Updated to support the latest MLDonkey features.
- Minor GUI improvements.
<<lessMain features:
- A flexible, powerful and KDE Style Guide compliant graphical interface.
- A complete implementation of the MLDonkey GUI protocol, meaning KMLDonkey can do everything the original GUI does, and more.
- Advanced configurable search forms.
- A convenient and configurable on-demand MLDonkey launcher.
- Real-time graphical bandwidth and network statistics.
- MobileMule middleware for controlling your MLDonkey using your Java enabled mobile phone.
- Embedded previewing of all downloads using KParts viewers.
- Embedded web browser providing P2P related web services such as availability and fake checks.
- KDE panel applet and system tray icon for statistics and easy access to the GUI.
- KIOSlave for opening current and complete downloads in all KDE applications (eg. "mldonkey:/Default/downloading/")
- Setup wizard for easy installation of the MLDonkey core.
Enhancements:
- Updated to support the latest MLDonkey features.
- Minor GUI improvements.
Download (0.95MB)
Added: 2005-07-26 License: GPL (GNU General Public License) Price:
1552 downloads
Hibernate Core for Java(Linux) 3.2.5.ga
An object/relational persistence and query service for Java more>> <<less
Download (19.35MB)
Added: 2009-04-25 License: Freeware Price: Free
188 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
DREAM Tool 0.7 Beta
DREAM Tool is a generic framework that aims at providing a common semantic domain. more>>
DREAM Tool is a generic framework that aims at providing a common semantic domain which can express several (real-time, power consumption, resource) constraints.
The semantic domain has an executable C++ model which has been semantically anchored to the hybrid automata formalism. Although the model of computation corresponds to hybrid automata, so far we have been successful in analyzing the models by conservative approximation using timed automata on moderate size systems.
To deal with large-scale examples the user has the ability to use the simulation/testing interface on the executable C++ model before implementing the system. We plan to extend the genetic algorithms to solve a large number of problems.
DREAM is a simulation and verification framework which provides a formal model and analysis of your system in less than a day. Systems in DREAM are specified using XML in a straightforward way. I hope you find it useful.
Real-time middleware provides dependable and efficient platforms supporting key functional and quality of service (QoS) needs of distributed real-time embedded (DRE) systems.
Key challenges in DRE system developments include safe composition of system components and mapping the functional specifications onto the target platform. Model-based technologies help address these issues by enabling design-time analysis and providing the means for the rapid evaluation of design alternatives with respect to end-to-end QoS properties, predictability and performance measures before committing to a specific platform.
The Distributed Real-time Embedded Analysis Method DREAM is an open-source tool and method for optimizing multiple quality of service (QoS) properties of distributed real-time embedded (DRE) systems. The project focuses on the practical application of formal analysis methods to real-time middleware to automate the verification, development, configuration, and integration of middleware-based DRE systems.
Enhancements:
- This version implemented several optimizations for improved model checking performance, resulting in impressive performance gains of at least 2-3 times.
- There are no known memory leaks present in the current release.
- Balanced AVL trees are now used, resulting in exponential speedups in several steps of the model checking method.
- XML Schema validation was implemented.
- Verification time reporting was upgraded to include data on the simulation speeds.
- Random simulation-based testing now provides an execution trace when a deadline is missed.
<<lessThe semantic domain has an executable C++ model which has been semantically anchored to the hybrid automata formalism. Although the model of computation corresponds to hybrid automata, so far we have been successful in analyzing the models by conservative approximation using timed automata on moderate size systems.
To deal with large-scale examples the user has the ability to use the simulation/testing interface on the executable C++ model before implementing the system. We plan to extend the genetic algorithms to solve a large number of problems.
DREAM is a simulation and verification framework which provides a formal model and analysis of your system in less than a day. Systems in DREAM are specified using XML in a straightforward way. I hope you find it useful.
Real-time middleware provides dependable and efficient platforms supporting key functional and quality of service (QoS) needs of distributed real-time embedded (DRE) systems.
Key challenges in DRE system developments include safe composition of system components and mapping the functional specifications onto the target platform. Model-based technologies help address these issues by enabling design-time analysis and providing the means for the rapid evaluation of design alternatives with respect to end-to-end QoS properties, predictability and performance measures before committing to a specific platform.
The Distributed Real-time Embedded Analysis Method DREAM is an open-source tool and method for optimizing multiple quality of service (QoS) properties of distributed real-time embedded (DRE) systems. The project focuses on the practical application of formal analysis methods to real-time middleware to automate the verification, development, configuration, and integration of middleware-based DRE systems.
Enhancements:
- This version implemented several optimizations for improved model checking performance, resulting in impressive performance gains of at least 2-3 times.
- There are no known memory leaks present in the current release.
- Balanced AVL trees are now used, resulting in exponential speedups in several steps of the model checking method.
- XML Schema validation was implemented.
- Verification time reporting was upgraded to include data on the simulation speeds.
- Random simulation-based testing now provides an execution trace when a deadline is missed.
Download (3.3MB)
Added: 2007-07-28 License: GPL (GNU General Public License) Price:
821 downloads
Multi-Protocol Remote Login 0.3.0
Multi-Protocol Remote Login provides a middleware allowing SSH, telnet, and local logins from the login: prompt. more>>
Multi-Protocol Remote Login provides a middleware allowing SSH, telnet, and local logins from the login: prompt.
MPRL is a middleware application between a *getty program and SSH, telnet, and other such remote-login protocols. It allows a user at a Linux terminal to log into other systems without needing a valid local user-id. It currently supports telnet, ssh, and /bin/login.
It syntax follows the [protocol:]user[@host][:port] fashion.
These are valid logins:
- buanzo - Normal local login: /bin/login gets called.
- buanzo@linux.org.ar - SSH protocol by default: /usr/bin/ssh gets called
- ssh:buanzo@webserver.algo.net
<<lessMPRL is a middleware application between a *getty program and SSH, telnet, and other such remote-login protocols. It allows a user at a Linux terminal to log into other systems without needing a valid local user-id. It currently supports telnet, ssh, and /bin/login.
It syntax follows the [protocol:]user[@host][:port] fashion.
These are valid logins:
- buanzo - Normal local login: /bin/login gets called.
- buanzo@linux.org.ar - SSH protocol by default: /usr/bin/ssh gets called
- ssh:buanzo@webserver.algo.net
Download (0.022MB)
Added: 2007-02-28 License: GPL (GNU General Public License) Price:
971 downloads
ACE 5.5.9
ACE is an object-oriented (OO) C++ framework. more>>
ACE short from ADAPTIVE Communication Environment is an object-oriented (OO) C++ framework that can help you develop and deploy high-performance software systems faster and better.
ACE is especially useful for systems that use network and/or inter-process communications and that take advantage of multithreading. While the ACE source code is free, thats not the only way you save money with ACE.
ACEs wrappers and higher-level patterns help you develop your software quickly and portably, helping you to complete your projects on time and within budget.
Over the past decade, my research group has worked with many collaborators on large-scale distributed application R&D projects in diverse domains, including command and control systems, telecom, datacom, medical engineering, distributed interactive simulations, and financial services.
Regardless of the domain and application requirements, weve found that software developers wrestle with the same core infrastructure challenges. Key challenges focus on OS platform portability, connection management and service initialization, event demultiplexing and event handler dispatching, multi-threading and synchronization, fault detection and fault tolerance, and various quality-of-service (QoS) issues, such as controlling latency, throughput, and jitter end-to-end.
Unfortunately, its very costly, time consuming, and error-prone for researchers and developers companies to independently rediscover and reinvent ad hoc solutions to these core distributed application software development challenges.
Fortunately, we have identified a relatively concise set of patterns and framework components that can be applied systematically to eliminate many tedious, error-prone, and non-portable aspects of developing and maintaining distributed applications.
A decade of intense R&D on these topics has yielded ACE, which is an object-oriented framework that implements many core patterns for concurrent communication software. We have applied the patterns and components in the ACE framework to develop The ACE ORB (TAO), which is our standards-based, CORBA middleware framework that allows clients to invoke operations on distributed objects without concern for object location, programming language, OS platform, communication protocols and interconnects, and hardware.
TAO is designed using the best software practices and patterns that we have discovered in our work on ACE in order to automate the delivery of high-performance and real-time QoS to distributed applications.
Enhancements:
- This release adds support for Intel C++ specific optimizations for Linux on IA64.
- It improves support for ACE_OS::fgetc, and adds support for other low-level I/O.
- Shared library builds on AIX now produce a libxxx.so file.
- A workaround has been added for a bugfix in GCC in Fedora Core 7.
- The footprint has been reduced on some platforms.
- Major improvements have been made to IPv6 support.
- TAO DDS enhancements have been added.
- There are assorted bugfixes and other minor enhancements.
<<lessACE is especially useful for systems that use network and/or inter-process communications and that take advantage of multithreading. While the ACE source code is free, thats not the only way you save money with ACE.
ACEs wrappers and higher-level patterns help you develop your software quickly and portably, helping you to complete your projects on time and within budget.
Over the past decade, my research group has worked with many collaborators on large-scale distributed application R&D projects in diverse domains, including command and control systems, telecom, datacom, medical engineering, distributed interactive simulations, and financial services.
Regardless of the domain and application requirements, weve found that software developers wrestle with the same core infrastructure challenges. Key challenges focus on OS platform portability, connection management and service initialization, event demultiplexing and event handler dispatching, multi-threading and synchronization, fault detection and fault tolerance, and various quality-of-service (QoS) issues, such as controlling latency, throughput, and jitter end-to-end.
Unfortunately, its very costly, time consuming, and error-prone for researchers and developers companies to independently rediscover and reinvent ad hoc solutions to these core distributed application software development challenges.
Fortunately, we have identified a relatively concise set of patterns and framework components that can be applied systematically to eliminate many tedious, error-prone, and non-portable aspects of developing and maintaining distributed applications.
A decade of intense R&D on these topics has yielded ACE, which is an object-oriented framework that implements many core patterns for concurrent communication software. We have applied the patterns and components in the ACE framework to develop The ACE ORB (TAO), which is our standards-based, CORBA middleware framework that allows clients to invoke operations on distributed objects without concern for object location, programming language, OS platform, communication protocols and interconnects, and hardware.
TAO is designed using the best software practices and patterns that we have discovered in our work on ACE in order to automate the delivery of high-performance and real-time QoS to distributed applications.
Enhancements:
- This release adds support for Intel C++ specific optimizations for Linux on IA64.
- It improves support for ACE_OS::fgetc, and adds support for other low-level I/O.
- Shared library builds on AIX now produce a libxxx.so file.
- A workaround has been added for a bugfix in GCC in Fedora Core 7.
- The footprint has been reduced on some platforms.
- Major improvements have been made to IPv6 support.
- TAO DDS enhancements have been added.
- There are assorted bugfixes and other minor enhancements.
Download (29.8MB)
Added: 2007-06-28 License: GPL (GNU General Public License) Price:
1664 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above wsgi middleware 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
