Sponsored Content
Special Forums UNIX and Linux Applications Oracle Updates (RSS) Using Business Architecture to Drive IT/Business Alignment Post 302491522 by Linux Bot on Thursday 27th of January 2011 04:45:04 PM
Old 01-27-2011
Using Business Architecture to Drive IT/Business Alignment

"Making the transformation from a technology-centric to a business-centric approach can be quite challenging-mainly because most companies are overly focused on IT architecture," says Roy Hunter.

More...
 

We Also Found This Discussion For You

1. Red Hat

Cron entry for every 10 mints on business day business hour

Could you “crontab” it to run every 10 minutes on work days (Mo - Fr) between 08:00 and 18:00 i know to run every 10 mints but can any one guide me how to achieve the above one (2 Replies)
Discussion started by: venikathir
2 Replies
FraudDetect(3pm)					User Contributed Perl Documentation					  FraudDetect(3pm)

NAME
Business::FraudDetect - A cohort to Business::OnlinePayment SYNOPSIS
my %processor_info = ( fraud_detection => 'preCharge', maximum_fraud_score => 500, preCharge_id => '1000000000000001', preCharge_security1 => 'abcdef0123', preCharge_security2 => '3210fedcba', ) my $transaction = new Business::OnlinePayment($processor, %processor_info); $transaction->content( type => 'Visa', amount => '49.95', cardnumber => '1234123412341238', expiration => '0100', name => 'John Q Doe', ); $transaction->submit(); if($transaction->is_success()) { print "Card processed successfully: ".$transaction->authorization()." "; } else { print "Card was rejected: ".$transaction->error_message()." "; } DESCRIPTION
This is a module that adds functionality to Business::OnlinePayment. See Business::OnlinePayment. The user instantiates a Business::OnlinePayment object per usual, adding in three processor directives o fraud_detection Which Fraud Detection module to use. o maximum_fraud_score FraudDetection drivers are expected to return a numeric "risk" factor, this parameter allows you to set the threshold to reject the transaction based on that risk. Higher numbers are "riskier" transactions. o other driver-specific parameters. Consult the specific Fraud Detection module you intend to use for its required parameters. The $tx->submit() method is overridden to interpose a FraudDetection phase. A subordinate object is created using the same content as the parent OnlinePayment object, and a Fraud Detect action is run against that subordinate object. If the resulting fraud score is less than or equal to the maximum_risk parameter, the parent transaction will be allowed to proceed. Otherwise, a failure state will exist with a suitable error message. METHODS
This module provides no new methods. It does, however override the submit method to interpose an additional Fraud Detection phase. AUTHORS
Original author: Lawrence Statton <lawrence@cluon.com> Current maintainer: Ivan Kohler <ivan-bop@420.am> as part of the Business::OnlinePayment distribution. DISCLAIMER
THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. SEE ALSO
Business::OnlinePayment, http://420.am/business-onlinepayment perl v5.12.4 2007-06-13 FraudDetect(3pm)
All times are GMT -4. The time now is 02:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy