Free reporting services software for linux

Logging Services project is intended to provide cross-language logging services for purposes of application debugging and auditing.
We should also mention that thanks to the relentless efforts of many developers, we have a basic level of interoperability between the following projects:
- Log4Cxx (c++)
- Log4j
- Log4Net
- Log4Perl
- Log4PHP
- Log4PLSQL
- JDK1.4s util.logging framework
There is still much work ahead bringing in the various projects to work together within the Logging Services Project. The process is likely to take a little while. In the mean time, we will continue to do what we like best, that is developing open source software.
This is a project of the Apache Software Foundation (ASF). Like all Apache projects, we encourage a collaborative, consensus-based development process. We offer an open and pragmatic software license, and we strive to create software of the highest quality. The ASF is organized into several projects, which like Logging Services project may contain multiple sub-projects.

Yahoo::Marketing::Service is a base class for Service modules.

SYNOPSIS

This module is a base class for various Service modules (CampaignService, AdGroupService) to inherit from. It should not be used directly.

There are some methods common to all Services that are documented below.

See also perldoc Yahoo::Marketing::AccountService ...::AdGroupService ...::AdService ...::BasicReportService ...::BidInformationService ...::BudgetingService ...::CampaignService ...::ExcludedWordsService ...::ForecastService ...::KeywordResearchService ...::KeywordService ...::LocationService ...::MasterAccountService ...::UserManagementService

Please see the API docs at
http://ysm.techportal.searchmarketing.yahoo.com/docs/gsg/index.asp#services
for details about what methods are available from each of the Services.

Peco::Service is a Perl module with service specifications for Peco IoC containers.

SYNOPSIS

use Peco::Service;

$service = Peco::Service->new( $class, @depends, $create, %attrs );
$service = Peco::Service::Factory->new( ⊂routine, @depends );
$service = Peco::Service::Constant->new( $value );

SERVICE TYPES

Peco::Service

A generic service registration class.

Peco::Service::Factory

Factory service registration class. Takes a coderef which is called each time this service is accessed.

Peco::Service::Constant

For constant or scalar values.

epstools service menu is used to create a tiff preview inside an eps file.

If a preview exists, it is replaced by the created one.

Configuration with no services supported script is for a single host firewall configuration with no services supported by the firewall machine itself.

Sample:

# USER CONFIGURABLE SECTION

# The name and location of the ipchains utility.
IPTABLES=iptables

# The path to the ipchains executable.
PATH="/usr/local/sbin"

# Our internal network address space and its supporting network device.
OURNET="10.5.0.0/24"
OURBCAST="10.5.0.255"
OURDEV="eth0"

# The outside address and the network device that supports it.
ANYADDR="0/0"
ANYDEV="ppp0"

# The TCP services we wish to allow to pass - "" empty means all ports
# note: comma separated
TCPIN="ssh,ftp,ftp-data"
TCPOUT="smtp,www,ssh,telnet,ftp,ftp-data,irc,http"

# The UDP services we wish to allow to pass - "" empty means all ports
# note: comma separated
UDPIN="domain"
UDPOUT="domain"

# The ICMP services we wish to allow to pass - "" empty means all types
# ref: /usr/include/netinet/ip_icmp.h for type numbers
# note: comma separated
ICMPIN="0,3,11"
ICMPOUT="8,3,11"

# Logging; uncomment the following line to enable logging of datagrams
# that are blocked by the firewall.
# LOGGING=1

# END USER CONFIGURABLE SECTION
####################################
# Flush the Input table rules
echo -n Flushing forward... && {
$IPTABLES -F FORWARD
} && echo done

# We want to deny incoming access by default.
# echo -n Denying incoming access... && {
# $IPTABLES -P FORWARD drop
# } && echo done

# Drop all datagrams destined for this host received from outside.
echo -n Dropping incoming datagrams... && {
$IPTABLES -A INPUT -i $ANYDEV -j DROP
} && echo done

# SPOOFING
# We should not accept any datagrams with a source address matching ours
# from the outside, so we deny them.
echo -n Preventing spoofing... && {
$IPTABLES -A FORWARD -s $OURNET -i $ANYDEV -j DROP
} && echo done

# SMURF
# Disallow ICMP to our broadcast address to prevent "Smurf" style attack.
echo -n Preventing SMURFs... && {
$IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET -j DROP
} && echo done

# We should accept fragments, in iptables we must do this explicitly.
echo -n Accepting fragments... && {
$IPTABLES -A FORWARD -f -j ACCEPT
} && echo done

# TCP
# We will accept all TCP datagrams belonging to an existing connection
# (i.e. having the ACK bit set) for the TCP ports were allowing through.
# This should catch more than 95 % of all valid TCP packets.
echo -n Accepting valid incoming tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -d $OURNET --dports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done
echo -n Accepting valid outgoing tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -s $OURNET --sports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done

# TCP - INCOMING CONNECTIONS
# We will accept connection requests from the outside only on the
# allowed TCP ports.
echo -n Accepting incoming tcp connections on allowed ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $ANYDEV -d $OURNET --dports $TCPIN --syn -j ACCEPT
} && echo done

# TCP - OUTGOING CONNECTIONS
# We will accept all outgoing tcp connection requests on the allowed TCP ports.
echo -n Accepting outgoing traffic on allowed tcp ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $OURDEV -d $ANYADDR --dports $TCPOUT --syn -j ACCEPT
} && echo done

# UDP - INCOMING
# allow UDP datagrams in on the allowed ports and back.
echo -n Allowing UDP datagrams in on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -d $OURNET --dports $UDPIN -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -s $OURNET --sports $UDPIN -j ACCEPT
} && echo done

# UDP - OUTGOING
# We will allow UDP datagrams out to the allowed ports and back.
echo -n Allowing UDP datagrams out on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -d $ANYADDR --dports $UDPOUT -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -s $ANYADDR --sports $UDPOUT -j ACCEPT
} && echo done

# ICMP - INCOMING
# We will allow ICMP datagrams in of the allowed types.
# echo -n Allowing ICMP datagrams in of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET --icmp-type $ICMPIN -j ACCEPT
# } && echo done

# ICMP - OUTGOING
# We will allow ICMP datagrams out of the allowed types.
# echo -n Allowing ICMP datagrams out of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $OURDEV -d $ANYADDR --icmp-type $ICMPOUT -j ACCEPT
# } && echo done

# DEFAULT and LOGGING
# All remaining datagrams fall through to the default
# rule and are dropped. They will be logged if youve
# configured the LOGGING variable above.
#

# DoS
# enabling Syn-flood protection
echo -n Enabling Syn-flood protection... && {
iptables -A FORWARD -p tcp --syn -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling Furtive port scanner protection
echo -n Enabling Furtive port scanner protection... && {
iptables -A FORWARD -p tcp --tcp-flags SYN,ACK,FIN,RST RST -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling ping of death protection
echo -n Enabling ping of death protection... && {
iptables -A FORWARD -p icmp --icmp-type echo-request -m limit --limit 1/s -j ACCEPT
} && echo done


if [ "$LOGGING" ]
then
# Log barred TCP
$IPTABLES -A FORWARD -m tcp -p tcp -j LOG
# Log barred UDP
$IPTABLES -A FORWARD -m udp -p udp -j LOG
# Log barred ICMP
$IPTABLES -A FORWARD -m udp -p icmp -j LOG
fi
#
# end.

The KeyIntegrity family of products is intended for the service of the whole life cycle of program services and management of a Service-Oriented Architecture (SOA) based on any platform and technology, including Java and .NET.

KeyIntegrity allows the creation of crucially important business-applications for distributed heterogeneous spaces. KeyIntegrity ServiceHub also integrates people, systems, and applications with external and internal resources of the enterprise.

Keyinyegrity ServiceHub (SHB) is a midware package for Service-Oriented Architecture (SOA). Servicehub consists of:

Web container.
WS Engine. This module carries out the basic functions of Web-service management. Web-services are intended for creation of the distributed applications. Those applications function in the Internet environment (and its variations like - the intranet and the extranet) and their components interact on the basis of standard Web-protocols.
CSUL Engine. This module organizes GUI component model. Form and Report generators are parts of its structure. CSUL Engine is constructed on the basis of XML technologies.
Security Engine. This module provides a Single Sign-On. Single Sign-On allows a user who once passed the authentication to gain access to all the systems he has authorization for immediately, including the client/server and Web-resources. Security Engine supports the basic user authentication technologies and allows administrators to intensify the security of the protected resourses.
BPEL Engine. This module organizes Web-services orchestration. By means of BPEL typical business processes can be characterized as executable and capable of modelling the actual behavior of a business interaction participant. BPEL is focused on the Web services orchestration in the course of a business flow.
DATA Engine. This module organizes work with data pools. It describes the uniform interface for displaying Java objects to any storehouse of data. It is constructed on JDO basis and supports work with great volumes of data, transactions, and use of inquiries. It also allows to save objects in relational and objective databases, in files, etc. It grants independence from a data source.
Unified console for control and administration.

Plone Error Reporting is a project which facilitates the submission of useful bug reports to Plone.
PloneErrorReporting replaces default_error_message and prefs_error_log_showEntry with pages that facilitate the submission of useful bug reports to Plone.
It is designed with the goal of improving the information provided by bug reporters.
To see PloneErrorReporting in action, first install the product, then create a python script called imabug in the ZMI that contains the single line
raise AttributeError, bad attribute
Now, while still authenticated, load the page http://mysite/imabug. You should see a step-by-step procedure for reporting bugs at the bottom of the error page as long as you are logged in as a Manager. Similarly, when you view bugs in the Plone error log, you will see the bug submitting procedure.
Enhancements:
- Moved the product to use its own translation domain. This fixes an issue were half-translated sentences showed up in the templates.