Applying Thoughts

"Sometimes I Win, Other times I learn. but I never lose."
Showing posts with label Study Material. Show all posts
Showing posts with label Study Material. Show all posts

April 13, 2014

BSS vs OSS

OSS stands for Operational Support Systems.
BSS stands for Business Support Systems.

What are Operational Support Systems?
Software (occasionally hardware) applications that support back-office activities which operate on telecom’s network, provision and maintain customer services.
OSS is traditionally used by network planners, service designers, operations, architects, support, and engineering teams in the service provider. Increasingly product managers and senior staff under the CTO or COO may also use or rely on OSS to some extent.
What are Business Support Systems?
Software applications that support front office activities such as customer interactions. Billing, order management, customer relationship management, call centre automation, are all BSS applications.
BSS may also encompass the customer-facing veneer of OSS application such as trouble-ticketing and service assurance – these are back-office activities but initiated directly by contact with the customer.
This basic relationship between OSS and BSS, where OSS is passed service orders and supplies service assurance information to the BSS layer is often referred to as ‘Orders Down, Faults Up’.

above. Super simple relationship between OSS and BSS

Is the integration between OSS and BSS clear?
In the past, OSS/BSS had a clearer separation. A common job like capturing a customer order and provisioning it required a simple BSS-to-OSS interface. “Deliver product X to customer Y”. BSS would capture the order, set-up the billing and pass the order to OSS for fulfillment.
Now, networks and services are more complicated, more flexible, and telcos offer a range of differentiated products. OSS and BSS must liaise over what could be ordered by the customer, based on what service they already had, based on the network they would use, based on current available resources, based on how far they were from the telephone exchange… and so on. Offering a customer a service is now a negotiation between the commercial products managed by BSS and the ability of OSS (and the local network) to deliver certain products.

As a result, a number of systems now straddle OSS/BSS:
·         Service Assurance systems are now integrated across OSS/BSS in order to track service performance and ensure customer service-level agreements (SLA) are met. Service Assurance may also pro-actively identify network failures, initiating resolution action and notifying high-priority customers.

·         Service Catalogs (a.k.a. Product Catalogs) give the telco one place to list products offered to customers and define what network resources can be used to deliver the service. Service Catalogs offer product managers a tool that joins-up the service offering and fulfillment processes across BSS and OSS.

·         Service Management applications allow greater interaction between OSS and BSS processes when the service order and fulfillment process is complex. If a service order comprises multiple technical resources, which are delivered by multiple OSS systems, Service Management is responsible for orchestrating the fulfilment process and keeping the customer-facing team informed about progress, changes or deliver issues.

For more information, please refer to below links:

ConceptWave Order Care

ConceptWave, now part of Ericsson, is a leading telecom product and order lifecycle management solutions that enable rapid delivery of communication products to new markets and empower superior customer experience. It provides an end-to-end catalog-driven suite of order fulfillment automation software with ConceptWave Order Care and Rapid CRM. ConceptWave helps communication service providers to address competitive requirements and simplify the management of products and orders on any network across any geography using any communication channel.

ConceptWave Order Care® 

ConceptWave Order Care® automates product and service lifecycles, from initial product conception, through design and rollout, to eventual retirement. Once a product is created, ConceptWave’s out-of-the-box solutions manage individual customer orders, from order entry and validation through to the decomposition of that order as it interacts with downstream systems like inventory, delivery, and billing. 

The ConceptWave Order Care portfolio includes these modules: 

Ø  Catalog Management: A comprehensive product and service catalog solution that reduces time-to-market for new product launches and provides a consistent and high-quality customer experience.

Ø  Order Negotiations: A fully customization order entry system that lowers the cost per order, speeds time-to-revenue, and improves cross- and up-sell. 

Ø  Order Management: An order management solution that increases customer satisfaction and loyalty, and decreases costs and revenue leakage through accurate, successfully fulfilled orders.

Ø  Order Analytics: An analytics engine that maximizes order-to-cash with a 360° real-time view of the order lifecycle.

This comprehensive, integrated, catalog-driven approach to product and order life cycle management enables service providers to accelerate the time from product conception to customer order to revenue. 

ConceptWave’s catalog-driven order management solution enables cost-effective, automated order management and exceptional customer care as well as customized product roll outs and service delivery within days rather than months. This flexibility also simplifies partner management, which is so important in M2M solutions. 

Order Care’s catalog-driven approach speeds time-to-market, reduces costs, and increases customer satisfaction. 

What business leaders say about the conceptWave, refer the below link for details
http://www.tmforum.org/Conceptwave/12844/home.html

ConceptWave is Now Part of Ericsson which further strengthened the industry’s most comprehensive BSS/OSS portfolio

Zarar Rana, President & Co-Founder of ConceptWave, says: “Joining Ericsson today adds great value to ConceptWave, as we become part of their global organization and leverage their industry-leading technology and services competence.“

http://wireless.sys-con.com/node/2376475

March 17, 2012

Codd's Rules

Dr. E.F. Codd, an IBM researcher, first developed the relational data model in 1970. In 1985, Dr. Codd published a list of 12 rules that concisely define an ideal relational database, which have provided a guideline for the design of all relational database systems ever since.

I use the term "guideline" because, to date, no commercial relational database system fully conforms to all 12 rules. They do represent the relational ideal, though. For a few years, scorecards were kept that rated each commercial product's conformity to Codd's rules. Today, the rules are not talked about as much but remain a goal for relational database design.

Following is a list of Codd's 12 rules, including his original name for each rule and a simplified description. I also have included a note where certain rules are problematic to implement. Don't worry if some of these items are confusing to you, as we move further through this newsletter series we will fill in the details.

Rule 1: The Information Rule

All data should be presented to the user in table form. Last week's newsletter already discussed the basics of this rule.

Rule 2: Guaranteed Access Rule

All data should be accessible without ambiguity. This can be accomplished through a combination of the table name, primary key, and column name.

Rule 3: Systematic Treatment of Null Values

A field should be allowed to remain empty. This involves the support of a null value, which is distinct from an empty string or a number with a value of zero. Of course, this can't apply to primary keys. In addition, most database implementations support the concept of a nun- null field constraint that prevents null values in a specific table column.

Rule 4: Dynamic On-Line Catalog Based on the Relational Model A relational database must provide access to its structure through the same tools that are used to access the data. This is usually accomplished by storing the structure definition within special system tables.

Rule 5: Comprehensive Data Sublanguage Rule

The database must support at least one clearly defined language that includes functionality for data definition, data manipulation, data integrity, and database transaction control. All commercial relational databases use forms of the standard SQL (Structured Query Language) as their supported comprehensive language.

Rule 6: View Updating Rule

Data can be presented to the user in different logical combinations, called views. Each view should support the same full range of data manipulation that direct-access to a table has available. In practice, providing update and delete access to logical views is difficult and is not fully supported by any current database.

Rule 7: High-level Insert, Update, and Delete

Data can be retrieved from a relational database in sets constructed of data from multiple rows and/or multiple tables. This rule states that insert, update, and delete operations should be supported for any retrievable set rather than just for a single row in a single table.

Rule 8: Physical Data Independence

The user is isolated from the physical method of storing and retrieving information from the database. Changes can be made to the underlying architecture ( hardware, disk storage methods ) without affecting how the user accesses it.

Rule 9: Logical Data Independence

How a user views data should not change when the logical structure (tables structure) of the database changes. This rule is particularly difficult to satisfy. Most databases rely on strong ties between the user view of the data and the actual structure of the underlying tables.

Rule 10: Integrity Independence

The database language (like SQL) should support constraints on user input that maintain database integrity. This rule is not fully implemented by most major vendors. At a minimum, all databases do preserve two constraints through SQL.

• No component of a primary key can have a null value. (see rule 3)

• If a foreign key is defined in one table, any value in it must exist as a primary key in another table.

Rule 11: Distribution Independence

A user should be totally unaware of whether or not the database is distributed (whether parts of the database exist in multiple locations). A variety of reasons make this rule difficult to implement; I will spend time addressing these reasons when we discuss distributed databases.


Rule 12: Nonsubversion Rule

There should be no way to modify the database structure other than through the multiple row database language (like SQL). Most databases today support administrative tools that allow some direct manipulation of the datastructure.

February 21, 2011

ISRO Application Details & Previous papers

Centralised Recruitement to the Post of SCIENTISTS/ENGINEERS 'SC' in the diciplines of ELECTRONICS, MECHANICAL and COMPUTER SCIENCE, ISRO HQ:ICRB:02:2011 dated 08-02-2011



ISRO has given recruitment notification for the recruitment of Scientists/Engineers vacancies 2011 through online application process. For complete details pls click on below link…

ISRO Recruitment 2011 – Online Application – Vacancies in ISAC: Indian Space Research Organisation (ISRO) has been released a recruitment notification for the recruitment of Administrative Officer, Accounts Officer and Purchased and Stores Officer vacancies for eligible candidates. The information regarding age limit, educational qualification and other details of ISRO 
Recruitment is mentioned below.


ISRO Recruitment Vacancy details:


Total no of vacancies: 19 vacancies
Vacancy details of Group A Gazetted Posts at Various ISRO Centers/Units:


Name of the post:
1. Administrative Officer: 07 vacancies
2. Accounts Officer: 05 vacancies
3. Purchase and Stores Officer: 05 vacancies
Vacancy details of Group A Non Gazetted Posts at North Eastern Space Applications Centre (NE-SAC)
4. Administrative Officer: 01 vacancy
5. Accounts Officer: 01 vacancy


Age limit: 35 years as on 11-02-2011 age relaxation for specified reserved categories as per rules.
Selection procedure: Selection should be based on the written test, interview.


Application fee: Rs 100/- (Fee exemption for SC-ST-PWD-Woman Candid dates) DD from any of the Nationalized Bank in favour of the Sr. Accounts Officer, ISRO HQ, Bangalore, payable at Bangalore.


How to apply: The interested candidates are apply only through online www.isro.gov.in from 20-01-2011 to 11-02-2011 after applying online the print out copy of the application and DD accompanied with required enclosures and essentials send to the following address by post on or before 18-02-2011 , Senior Administrative Officer (ICRB), ISRO Headquarters, Antariksh Bhavan, New BEL Road, Bangalore 560231.


Important dates:
Opening date for online registration: 20-01-2011
Closing date for online registration: 11-02-2011
Last date for receipt of application: 18-02-2011
Written test date: 17-04-2011


For more details about age limit, educational qualification and experience, how to apply, pay scale, selection procedure, online apply details, written test date, centers and other details of ISRO Recruitment 2011 is available at the following link.

October 11, 2010

Send mail from PL/SQL

Send mail without attachments using the UTL_SMTP package: 

DECLARE
  v_From      VARCHAR2(80) := 'oracle@mycompany.com';
  v_Recipient VARCHAR2(80) := 'test@mycompany.com';
  v_Subject   VARCHAR2(80) := 'test subject';
  v_Mail_Host VARCHAR2(30) := 'mail.mycompany.com';
  v_Mail_Conn utl_smtp.Connection;
  crlf        VARCHAR2(2)  := chr(13)||chr(10);
BEGIN
 v_Mail_Conn := utl_smtp.Open_Connection(v_Mail_Host, 25);
 utl_smtp.Helo(v_Mail_Conn, v_Mail_Host);
 utl_smtp.Mail(v_Mail_Conn, v_From);
 utl_smtp.Rcpt(v_Mail_Conn, v_Recipient);
 utl_smtp.Data(v_Mail_Conn,
   'Date: '   || to_char(sysdate, 'Dy, DD Mon YYYY hh24:mi:ss') || crlf ||
   'From: '   || v_From || crlf ||
   'Subject: '|| v_Subject || crlf ||
   'To: '     || v_Recipient || crlf ||
   crlf ||
   'some message text'|| crlf || -- Message body
   'more message text'|| crlf
 );
 utl_smtp.Quit(v_mail_conn);
EXCEPTION
 WHEN utl_smtp.Transient_Error OR utl_smtp.Permanent_Error then
   raise_application_error(-20000, 'Unable to send mail: '||sqlerrm);
END;
/


Send mail with attachments using the UTL_SMTP package: 

DECLARE
   v_From       VARCHAR2(80) := 'oracle@mycompany.com';
   v_Recipient  VARCHAR2(80) := 'test@mycompany.com';
   v_Subject    VARCHAR2(80) := 'test subject';
   v_Mail_Host  VARCHAR2(30) := 'mail.mycompany.com';
   v_Mail_Conn  utl_smtp.Connection;
   crlf         VARCHAR2(2)  := chr(13)||chr(10);
BEGIN
  v_Mail_Conn := utl_smtp.Open_Connection(v_Mail_Host, 25);

  utl_smtp.Helo(v_Mail_Conn, v_Mail_Host);

  utl_smtp.Mail(v_Mail_Conn, v_From);

  utl_smtp.Rcpt(v_Mail_Conn, v_Recipient);

  utl_smtp.Data(v_Mail_Conn,
    'Date: '   || to_char(sysdate, 'Dy, DD Mon YYYY hh24:mi:ss') || crlf ||
    'From: '   || v_From || crlf ||
    'Subject: '|| v_Subject || crlf ||
    'To: '     || v_Recipient || crlf ||

    'MIME-Version: 1.0'|| crlf || -- Use MIME mail standard
    'Content-Type: multipart/mixed;'|| crlf ||
    ' boundary="-----SECBOUND"'|| crlf ||
    crlf ||

    '-------SECBOUND'|| crlf ||
    'Content-Type: text/plain;'|| crlf ||
    'Content-Transfer_Encoding: 7bit'|| crlf ||
    crlf ||
    'some message text'|| crlf || -- Message body
    'more message text'|| crlf ||
    crlf ||

    '-------SECBOUND'|| crlf ||
    'Content-Type: text/plain;'|| crlf ||
    ' name="excel.csv"'|| crlf ||
    'Content-Transfer_Encoding: 8bit'|| crlf ||
    'Content-Disposition: attachment;'|| crlf ||
    ' filename="excel.csv"'|| crlf ||
    crlf ||
    'CSV,file,attachement'|| crlf || -- Content of attachment
    crlf ||

    '-------SECBOUND--'   -- End MIME mail
  );

  utl_smtp.Quit(v_mail_conn);
EXCEPTION
  WHEN utl_smtp.Transient_Error OR utl_smtp.Permanent_Error then
    raise_application_error(-20000, 'Unable to send mail: '||sqlerrm);
END;
/

October 7, 2010

What is RAID & Its Levels

RAID is a technology that is used to increase the performance and/or reliability of data storage. The abbreviation stands for Redundant Array of Inexpensive Disks. A RAID system consists of two or more disks working in parallel. These disks can be hard discs but there is a trend to also use the technology for solid state drives.
The software to perform the RAID-functionality and control the hard disks can either be located on a separate controller card (a hardware RAID controller) or it can simply be a driver. Some versions of Windows, such as Windows Server 2003, as well as Mac OS X include software RAID functionality. Hardware RAID controllers cost more than pure software but they also offer better performance.
RAID-systems can be based with an number of interfaces, including SCSI, IDE, SATA or FC (fibre channel.) There are systems that use SATA disks internally but that have a FireWire or SCSI-interface for the host system.
There are different RAID levels, each suiting specific situations. RAID levels are not standardized by an industry group. This explains why companies are sometimes creative and come up with their own unique implementations.
Sometimes disks in a RAID system are defined as JBOD, which stands for ‘Just a Bunch Of Disks’. This means that those disks do not use a specific RAID level and are used as if they were stand-alone disks. This is often done for disks that contain swap files or spooling data.
Below is an overview of the most popular levels:

RAID 0: striping

In a RAID 0 system, data are split up in blocks that get written across all the drives in the array. By using multiple disks (at least 2) at the same time, RAID 0 offers superior I/O performance. This performance can be enhanced further by using multiple controllers, ideally one controller per disk.

Advantages

  • RAID 0 offers great performance, both in read and write operations. There is no overhead caused by parity controls.
  • All storage capacity can be used, there is no disk overhead.
  • The technology is easy to implement.

Disadvantages

RAID 0 is not fault-tolerant. If one disk fails, all data in the RAID 0 array are lost. It should not be used on mission-critical systems.

Ideal use

RAID 0 is ideal for non-critical storage of data that have to be read/written at a high speed, e.g. on a Photoshop image retouching station.

RAID 1: mirroring

Data are stored twice by writing them to both the data disk (or set of data disks) and a mirror disk (or set of disks) . If a disk fails, the controller uses either the data drive or the mirror drive for data recovery and continues operation. You need at least 2 disks for a RAID 1 array.
RAID 1 systems are often combined with RAID 0 to improve performance. Such a system is sometimes referred to by the combined number: a RAID 10 system.

Advantages

  • RAID 1 offers excellent read speed and a write-speed that is comparable to that of a single disk.
  • In case a disk fails, data do not have to be rebuild, they just have to be copied to the replacement disk.
  • RAID 1 is a very simple technology.

Disadvantages

  • The main disadvantage is that the effective storage capacity is only half of the total disk capacity because all data get written twice.
  • Software RAID 1 solutions do not always allow a hot swap of a failed disk (meaning it cannot be replaced while the server keeps running). Ideally a hardware controller is used.

Ideal use

RAID-1 is ideal for mission critical storage, for instance for accounting systems. It is also suitable for small servers in which only two disks will be used.

RAID 3

On RAID 3 systems, datablocks are subdivided (striped) and written in parallel on two or more drives. An additional drive stores parity information. You need at least 3 disks for a RAID 3 array.
Since parity is used, a RAID 3 stripe set can withstand a single disk failure without losing data or access to data.

Advantages

  • RAID-3 provides high throughput (both read and write) for large data transfers.
  • Disk failures do not significantly slow down throughput.

Disadvantages

  • This technology is fairly complex and too resource intensive to be done in software.
  • Performance is slower for random, small I/O operations.

Ideal use

RAID 3 is not that common in prepress.

RAID 5

RAID 5 is the most common secure RAID level. It is similar to RAID-3 except that data are transferred to disks by independent read and write operations (not in parallel). The data chunks that are written are also larger. Instead of a dedicated parity disk, parity information is spread across all the drives. You need at least 3 disks for a RAID 5 array.
A RAID 5 array can withstand a single disk failure without losing data or access to data. Although RAID 5 can be achieved in software, a hardware controller is recommended. Often extra cache memory is used on these controllers to improve the write performance.

Advantages

Read data transactions are very fast while write data transaction are somewhat slower (due to the parity that has to be calculated).

Disadvantages

  • Disk failures have an effect on throughput, although this is still acceptable.
  • Like RAID 3, this is complex technology.

Ideal use

RAID 5 is a good all-round system that combines efficient storage with excellent security and decent performance. It is ideal for file and application servers.

RAID 10: a mix of RAID 0 & RAID 1

RAID 10 combines the advantages (and disadvantages) of RAID 0 and RAID 1 in a single system. It provides security by mirroring all data on a secondary set of disks (disk 3 and 4 in the drawing below) while using striping across each set of disks to speed up datatransfers.

What about RAID 2, 4, 6 or 7?

These levels do exist but are not that common, at least not in prepress environments. This is just a simple introduction to RAID-system. You can find more in-depth information on the pages of ACNC or storage.com.

October 5, 2010

Oracle Database XE Administration

Understanding the Oracle Architecture As they say, you don’t have to know how a car’s antilock brakes work to drive a car, and you don’t need to be able to design a cell phone to call someone on a cell phone. The same could be said about the architecture of Oracle Database XE: you don’t necessarily need to know how Oracle stores data blocks on disk, but knowing the general disk and memory architecture model goes a long way to help you design and use the database efficiently. You also need to know the terminology surrounding Oracle components: tablespaces, datafiles, segments, and extents. Even if you’re only an occasional database administrator for your Oracle Database XE installation, the architectural overview in the next few sections will help you be an effective application developer as well.
An Oracle server contains both a database and an instance. The database consists of the files on disk. These files store the data itself; the state of the database, in a small, most likely replicated file called the control file; and changes to the database’s data, in files called redo log files. The instance refers to the Oracle memory processes and memory structures that reside in your server’s memory and access the database in the disk files. This distinction becomes more obvious when you are using Real Application Clusters (RAC), which is two or more Oracle instances sharing one database for performance, scalability, or availability.


Oracle Storage StructuresIt’s important to distinguish the logical database storage structure from the physical database structure. As with most computing paradigms, the logical version hides the implementation of the paradigm in the physical implementation, either to make application development easier or to help communicate the architectural details to managers who are not involved in the technical aspects of a database computing environment on a daily basis.
From a database perspective, then, the logical database structures represent components such as tables, indexes, and views—what you see from a user’s or a developer’s point of view. The physical database structures, on the other hand, are the underlying storage methods on the disk file system including the physical files that compose the database.

Oracle Database XE Administration - Logical Storage Structures

The Oracle database is divided into increasingly smaller logical units to manage, store, and retrieve data efficiently and quickly. Figure shows the relationships between the logical structures in an Oracle database: tablespaces, segments, extents, and blocks.
Figure   Oracle Database XE logical storage structures
The logical storage management of the database’s data is independent of the physical storage of the database’s physical files on disk. This makes it possible for changes you make to the physical structures to be transparent to the database user or developer at the logical level.
 
Tablespaces A tablespace is the highest-level logical object in the database. A database consists of one or more tablespaces. A tablespace will frequently group together similar objects, such as tables, for a specific business area, a specific function, or a specific application. You can reorganize a particular tablespace or back it up with minimal impact to other users whose data may be changing at the same moment in other tablespaces in the database.
All Oracle databases require at least two tablespaces: theSYSTEMtablespace and theSYSAUXtablespace. Having more than just theSYSTEMandSYSAUX tablespaces is highly recommended when creating a database; a default installation of Oracle Database XE includes five tablespaces. In the illustration of logical structures in Figure,  you can see the five default tablespaces:SYSTEM,SYSAUX,TEMP,USERS, andUNDO.
 

Segments A tablespace is further broken down into segments. A database segment is a type of object that a user typically works with, such as a table or an index. The USERStablespace in Figure consists of five segments, which could be tables, indexes, and so forth. It’s important to note that this is the logical representation of these objects; the physical representation of these objects in the operating system files will most likely not match the logical representation. For example, extents 1 and 2 in segment 3 will most likely not be adjacent on disk and may even be in separate datafiles. We discuss datafiles in the section titled “Physical Storage Structures.”

Extents
The next-lowest logical grouping in a database is the extent. A segment groups one or more extents allocated for a specific type of object in the database. Segment 3 in Figure,  consists of four extents. Note that an extent cannot cross segment boundaries. Also, a segment, and subsequently an extent, cannot cross tablespace boundaries.

Database Blocks
The most granular logical object in a database is the database block (also known as an Oracle block), the smallest unit of storage in an Oracle database. Every database block in a tablespace has the same number of bytes. Starting with Oracle9i, different tablespaces within a database can have database blocks with different sizes. Typically, one or more rows of a table will reside in a database block, although very long rows may span several database blocks.
A database block can have a size of 2KB, 4KB, 8KB, 16KB, or 32KB. Once any tablespace, including theSYSTEMandSYSAUX tablespaces, is created with a given block size, it cannot be changed. If you want the tablespace to have a larger or smaller block size, you need to create a new tablespace with the new block size, move the objects from the old tablespace to the new tablespace, and then drop the old tablespace.
 

Schemas A schema is another logical structure that can classify or group database objects. A schema has a one-to-one correspondence with a user account in the Oracle database, although you may create a schema to hold only objects that other database users reference. For example, in Figure, the HRschema may own segments 1 and 3, while theRJBschema may own segment 2.HR andRJBare both user accounts and schemas. Segments 1 and 3 may be the tables HR.EMPLOYEES and HR.DEPARTMENTS, while segment 2 may be the index RJB.PK_ACCT_INFO_IX.
A schema is not directly related to a tablespace or any other logical storage structure; the objects that belong to a schema may reside in many different tablespaces. Conversely, a tablespace may hold objects for many different schemas. A schema is a good way to group objects in the database for purposes of security, manageability, and access control.
 

July 7, 2010

CAPTCHA -- Work as Anti Spam

A CAPTCHA or Captcha (pronounced /ˈkæptʃə/) is a type of challenge-response test used in computing to ensure that the response is not generated by a computer. The process usually involves one computer (aserver) asking a user to complete a simple test which the computer is able to generate and grade. Because other computers are unable to solve the CAPTCHA, any user entering a correct solution is presumed to be human. Thus, it is sometimes described as a reverse Turing test, because it is administered by a machine and targeted to a human, in contrast to the standard Turing test that is typically administered by a human and targeted to a machine. A common type of CAPTCHA requires that the user type letters or digits from a distorted image that appears on the screen.



10 Free CAPTCHA scripts and services for websites


1. reCAPTCHA
reCAPTCHA is a free service which helps prevent automated abuse of your site (such as comment spam or bogus registrations) by using a CAPTCHA to ensure that only humans perform certain actions.

2. Securimage
Securimage is an open-source free PHP CAPTCHA script for generating complex images and CAPTCHA codes to protect forms from spam and abuse. It can be easily added into existing forms on your website to provide protection from spam bots. It can run on most any webserver as long as you have PHP installed, and GD support within PHP. Securimage does everything from generate complicated CAPTCHA images to making sure the code the user entered was correct.

3. WebSpamProtect
WebSpamProtect allows you to instantly add verification image (CAPTCHA) to your web site and protect your forms against spam robots. In order to protect your web form, this system requires that you install a small piece of code onto your web page. The code requires that your web site support PHP, Perl, ASP or ASP.NET. Basic plan is free but you can buy a Premium, Advanced or Professional paln with a little expense.

4. Cryptographp
Cryptographp is a PHP script for generate captchas. Cryptographp limit the robots bombarding spams and automating the forms: spaces members subscriptions, guestbooks, forums... This script is free and does not use any database. It is compatible with PHP >= 4.3.0. Cryptographp also exists into plugins for WordPress, wpMu for WordPress, Symfony and Guppy.

5. CAPTCHA-Service
captchas.net provides CAPTCHA images and audio files you can use in html-forms. To use this technology, your web pages have to be generated dynamically in any programming language PHP, ASP, Perl, Python, JSP, Ruby.

6. WP Captcha-Free
WP Captcha-Free blocks comment spam by using a combination of time-based hash (a.k.a. Time Based Tokens, TBT) and JavaScript (AJAX). When a comment is posted the plugin validates a hash based on time (and some other parameters). Comments posted via automated means will not have a hash or will have an expired hash and will be rejected. Unlike using a captcha, this does not place any burden on the commenter.

7. ProtectWebForm
ProtectWebForm is a service to add CAPTCHA images and audio files on your website. You have to create an account, generate your CAPTCHA type with all the desired parameters and include it on your web pages.You can also use it on your Wordpress template with this plugin.

8. ProtectWebForm
OpenCaptcha is a simple web service which requires no special configurations or modules. Basic installation is cut-and-paste, and requires no ability to program image manipuation scripts. New fonts, image algorithms, and distortions applied weekly.

9. Form-to-email script protected by Captcha
This form-to-email script is intended to collect data from an HTML form and send it to a specified email address using a CAPTCHA script to stop spam. It works with any kind of HTML form and you can use it multiple times on your pages.

10. freeCap
freeCap is a GPL CAPTCHA script to stop spam. It has been used on any form on any kind of website. It does require some knowledge of PHP to install, though there are several captcha plugins for forum and blog software listed below.



For the Normal JSP implementation (Which you can try):
http://captchas.net/sample/jsp/