server
easy to use backup tool for linux
Create an incremental backup of a debian-linux server with an easy to use tool. The backup-server is reachable via ftp and sftp. The backup should be encrypted and compressed to be space and bandwidth efficient. There should be an easy way to either restore parts of the backup or the full system after a failure.
Protégé Server
<p>To enable an access for a community to develop an ontology a server based solution is required. WebProtégé offers such a solution but must be installed on an application server.</p>
Connect remotely located Java applications and database
<p>A library has a management software implemented by Java. This software is going to be used as a server application which is located in Vienna. A database including all book informations of the same library is located in London. Find out an appropriate technology by which a client Java application located in Paris can search the book informations of the library remotely.</p>
Synchronize large amounts of Files in heterogeneous (home-) networks
Many people are using notebooks and workstations with different operating systems and want to have all user files perfectly synchronized. There are several options to archive this, which is the best in regards of performance and usability.
Taggings:
Managing courses and providing a registration System
The registration system should offer a specified number of courses and a limited number of possible registrations. The system has to ensure that no further registrations are possible if the places are limited. It should be possible to integrate the system into an existing website, including adaptions concerning layout and design.
The registration process is limited to a specific time and registered users should be able to change their registrations. The users should be able to log on and view as well as change their current registrations.
The backend should provide facilities to add and remove users and should offer registration lists which could be used to check attendance. In addition, collected e-mail addresses could be used to inform audience on time or location change.
The technology used should be widespread and easy to use. It should be used for a Website for company fairs (www.discovery.jku.at) and is therefore used only occasionally. It is of major importance that the system is easy to use and to maintain because the organizing team of the fair and also the maintaining team of the website change a lot.
The existing infrastructure is an Apache server and a mysql database which ideally should be used for this project as well. Nevertheless, other open source technologies could be integrated.
Correctly configuring a Jetty Java Servlet container to be used through an Apache Web server via mod_jk
When deploying a JVM-based Web app usually so-called Java Servlet containers resp. application servers are used for the produciton system/environment. Probably the most popular and common Java server in this field is Apache Tomcat (and other even more feature-rich ones like JBoss or GlassFish). Apart from that, there's also Jetty which can be seen as a somewhat lightweight alternative. Nevertheless, there are some subtle differences to be taken into consideration when configuring it as opposed to Tomcat. The usual way to setup such a production system for a Java Web app is to use the Servlet container to serve the Web app and put so to speak in front of it an Apache Web server which handles the requests, hands them over to the container instance (e.g., Jetty or Tomcat) and receives its responses then (to say it in an a bit simplified way). Usually this is done via Apache's mod_jk module which enables communication between app server and Web server through the AJP13 protocol. What should be described and explained now is how to setup such a Java Web app production system ready for deployment in detail (mainly from a configuration perspective). The main focus shall be put at differences which are to be taken into account here between Jetty and Apache Tomcat.
Setting up a Subversion repository and corresponding Trac app on a (Debian/Apache) server
So the basic problem here is how to best work together productively in a programming/development project and the question which are good tools providing capabilities to potentially support and improve this.
One such tool is a version control systems (VCS) which basically helps to keep the code and especially its progress under (version) control in a code repository (transparently).
A specific such VCS is Subversion (a.k.a. SVN). This is at the time one of the most popular and up-to-date systems of its kind (i.e., centralized VCS). Its basic slogan is "CVS done right" (which consequently can be seen as Subversion's indirect predecessor system).
There are many tools available to work with Subversion from a client/user perspective like stand-alone client apps, integration in editors, e.g., via special plugins or also complete integration in a full-blown IDE (integrated development environment).
Now, what's up to do is to actually setup a Subversion system on a server and to create a code repository for a programming/development project. In this case a Debian-based OS with an Apache Web server is chosen as infrastructure.
Additionally a Trac app should be installed which among other things offers nice and convenient Web visualization of the code repository (and its progress) to users.
When all this is in place users can take the benefits of using Subversion for version control of the code of the project.
Pages
- « first
- ‹ previous
- 1
- 2
- 3
