Free jenoptik jd 3.3 xz3 software for linux

ntop is a network traffic probe that shows the network usage, similar to what the popular top Unix command does.
The project is based on libpcap and it has been written in a portable way in order to virtually run on every Unix platform and on Win32 as well.
ntop users can use a a web browser (e.g. netscape) to navigate through ntop (that acts as a web server) traffic information and get a dump of the network status.
In the latter case, ntop can be seen as a simple RMON-like agent with an embedded web interface. The use of:
a web interface
limited configuration and administration via the web interface
reduced CPU and memory usage (they vary according to network size and traffic)
make ntop easy to use and suitable for monitoring various kind of networks.
Main features:
- Sort network traffic according to many protocols
- Show network traffic sorted according to various criteria
- Display traffic statistics
- Store on disk persistent traffic statistics in RRD format
- Identify the indentity (e.g. email address) of computer users
- Passively (i.e. withou sending probe packets) identify the host OS
- Show IP traffic distribution among the various protocols
- Analyse IP traffic and sort it according to the source/destination
- Display IP Traffic Subnet matrix (whos talking to who?)
- Report IP protocol usage sorted by protocol type
- Act as a NetFlow/sFlow collector for flows generated by routers (e.g. Cisco and Juniper) or switches (e.g. Foundry Networks)
- Produce RMON-like network traffic statistics
Additional features of "ntop":
- Network Flows
- Local Traffic Analysis
- Multithread and MP (MultiProcessor) support on both Unix and Win32
- Perl/PHP/Python lightweight API for accessing ntop from remote
- Support of both NetFlow andsFlow as flow collector. ntop can collect simultaneously from multiple probes.
- Traffic statistics are saved into RRD databases for long-run traffic analysis.
- Internet Domain, AS (Autonomous Systems), VLAN (Virtual LAN) Statistics
- Network assets discovery and categorization according to their OS and users
- Protocol decoders for most of known P2P (Peer to Peer) protocols
- Advanced per user HTTP password protection with encrypted passwords
- RRD support for persistently storing per-host traffic information
- Passive remote host fingerprint (Courtesy of ettercap)
- HTTPS (Secure HTTP via OpenSSL)
- Virtual/multiple network interfaces support
- Graphical Charts (via gdchart)
- WAP support

Ovidentia is a professional collaborative/groupware portal generator featuring an administrable management tool with a workflow for the approval to publish articles, comments, files, or vacation requests.
It also features an agenda (shareable), an integrated directory, charts, an LDAP directory interface, add-ons support, a mail interface, and a WYSIWYG HTML editor to publish articles, news, posts, or write email. The project supports LDAP, Ovidentia, and Active Directory authentication.
Enhancements:
- Bugs correction
- Security corrective measures
- Vacation requests management evolutions

KSynaptics is a control center module that enables users to take full advantage of their mobiles synaptics touch pad. KSynaptics project depends on the XFrees synaptics driver.
Main features:
- adjustable pressure sensitivity
- tapping configuration / smart tapping
- mouse button emulation
- circular scrolling
- smart mode
Enhancements:
- new mouse button icons
- syndock would run in smart mode even if disabled in ksynaptics

Sashenka is aJ2EE Servlet container and framework for IRC bots and clients.

Much of it is incomplete and it only handles basic incoming and outgoing messages but it is enough to build trivial bots with.

Bots are written as Servlets following the
Sun J2EE servlet model which are loaded by the container.

The container dispatches messages to and through the modules so that they may respond (if they so wish).

You could even build a functional IRC client with the utility classes in sashenka but there are enough of those out there already so I dont recommend that you try.

What sashenka does offer is an object oriented framework for managing IRC traffic. My only use for it is the bot framework built on top of the IRC framework.

The distro comes with the j2ee.jar from the 1.2.1 j2ee sdk. I include this for convenience, if you have the j2eesdk I encourage you to use your own copy as mine may not jive with your runtime.

NodeMon is a visualization tool for monitoring system resource utilization. It allows distributed resource monitoring via the Growler software infrastructure.

It is modular, with existing modules for monitoring of CPU, memory, network, and numalink activity. Its most notable feature is its composition of large amounts of statistics into a single graphical window. This project was originally designed for monitoring NASAs Columbia supercomputer.

Openfire is a leading Open Source, cross-platform IM server based on the XMPP (Jabber) protocol.

Openfire server has great performance, is easy to setup and use, and delivers an innovative feature set.

Openfire is an enterprise instant messaging (EIM) server dual-licensed under the Open Source GPL and commercially. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber).

Openfire is incredibly easy to setup and adminster, but offers rock-solid security and performance.

Use Openfire in your organization as a more secure and feature-rich alternative to the consumer IM networks. Or, replace your existing EIM server with a more open, easier to use, and much less expensive solution.

Enterprise Grade

Openfire supports SSL/TLS encrypted connections out of the box as well as packet auditing to meet compliance requirements. Optionally tie Openfire into your organizations existing authentication system such as LDAP and then handle thousands of concurrent users on a single server.

Open Source and Open Protocol

Openfire is available under the Open Source GPL or a commercial license. It supports the open XMPP (Jabber) IM protocol and popular extensions. XMPP is supported by dozens of IM clients and allows for easy federation between IM servers. Openfire is among the most compliant XMPP servers available.

Cross-Platform

As a 100% Java application, Openfire supports Windows, Unix/Linux, and Mac OSX. The server can be deployed as a standalone application or service, or deployed in any J2EE compliant application server (Tomcat, Resin, etc) as a WAR (Web Application Archive).

Easy to Use

Get Openfire up and running within ten minutes. Then, administer the server using the web-based admin console.

Plugins

The server is easily extensible with a full plugin architecture. Visit the plugin library for a full list of available plugins.

Spark IM Client

Openfire works great with the cross-platform, feature-rich Spark IM client. Use the Spark Manager server plugin to manage the Spark clients on your server.

Server-Managed Contact Lists

Define groups of users in the server and then use the shared-group feature to automatically push those groups into users contact lists. This makes it very easy for people to start using the system and find the people they work with.

TrafIP provides a small solution for monitoring traffic and bandwith.
TrafIP - its a small solution(3 files) for monitoring your traffic and bandwidth. Its available for using with PHP and Linux(or any type of unix/bsd etc).
Unlike other programs you will have all data updated at 6 seconds. The graphs are generated when you access them. Oh, its FREE!
Options:
- the name of file wich contains colected data
- ip address filtered/of interface
- the maximum speed than the line can download in 6 seconds. if you see black lines without interface to be down, then increase this value, it is just to detect line up/down
- the color for upload traffic
- the color for download traffic
- image type png recomended for small size and look(can be png, gif or jpg)
Installation is easy. Just add those lines to your firewall or put somewhere to start allways.
After this modify the collect.sh script with the result from your iptables -L -n. And of course put the .php files somewhere to access via www :) and make the directory writeable.
The output file must be in the directory where are the php files. By default without selecting anything will show last hour traffic. Its pretty live(update at 6 seconds, not like other programs).
Quick example:
[root@lair trafip]# iptables -A OUTPUT -s 0.0.0.0/0 -d 127.0.0.1
[root@lair trafip]# iptables -A INPUT -d 0.0.0.0/0 -s 127.0.0.1
[root@lair trafip]# iptables -L -n|grep 127|grep -v ACCEPT|grep -v LOG|grep -v DROP
all -- 127.0.0.1 0.0.0.0/0
all -- 0.0.0.0/0 127.0.0.1
Get the strings "127.0.0.1 0.0.0.0/0" and "0.0.0.0/0 127.0.0.1" and put in collect.sh. Must be exact like iptables shows(better you copy paste that part). The script collect.sh must be allways running to count.
In img.php modify:
$target variable with the name where you redirect the output from collect.sh(ex: $target="local";)
$ip variable with the IP(ex: $ip="127.0.0.1";)
$maxspeed variable with the maximum maxim traffic can be done in 6 seconds(ex: $ip="115200";). If you have black lines on your graph without stopping the interface/traffic the increase the value.
$upload variable with red or green(ex: $upload="red";)
$download variable with red or green(ex: $download="green";)
$imagetype variable with png, gif or jpg, if for output format of graph(ex: $imagetype="gif")
The output file must be something like:
11/12/02 05:57:26 10782702 149477806
11/12/02 05:57:32 10783170 149489806
11/12/02 05:57:38 10783810 149509426
(format: month/day/year[space]hour:minutte:second[space]INPUT_counter[space]OUTPUT_counter
Enhancements:
- New output formats
- an interface to see detailed traffic.

Jameleon project is an automated testing framework that can be used by technical and non-technical users alike.
One of the main concepts behind it is to create a group of keywords or tags that represent different screens of an application. All of the logic required to automate each particular screen can be defined in Java and mapped to these keywords.
The keywords can then be organized with different data sets to form test scripts without requiring an in-depth knowledge of how the application works. The test scripts are then used to automate testing efforts and to generate manual test case documentation.
Jameleon was designed to test many kinds of applications. To make this possible, Jameleon was designed with a plug-in model. Currently, there are five plug-ins offered;
- A JUnit plug-in which can be used to test at a white box level. All JUnit function tags can be used in conjunction with other plug-ins.
- A Jiffie plug-in which drives Internet Explorer and can therefore only be run on Windows. Most testers like this plug-in the most.
- An HttpUnit plug-in which emulates a browser. Most developers like this plug-in the most.
- A 3270 (Jagacy) plug-in which is used to automate mainframe applications.
- A jWebUnit plug-in which is the most basic among the provided plug-ins and currently has no generic tags other than a session tag.
If Jameleon doesnt have some feature or plug-in, please feel free to request it as a feature via the Request a Feature link. Implementing Jameleon plug-ins is simple and can usually be done in less than a hour.
Even though it would be possible to write unit tests using Jameleon, Jameleon was designed with integration, regression, functional, and acceptance-level testing in mind. Most bugs are found and fixed by good unit tests. However, this does not eliminate the need to test the application as a whole.
Enhancements:
- This release includes four new features and fixes four bugs.
- A notable new feature is an experimental Selenium plug-in.
- One of the fixed bugs includes a fix to a performance slow-down in the Jiffie plug-in introduced back in the 3.3-M2 release.