SET Ä«¼¼Æ®¿ë °è»ê¿ø ÇÁ·ÎÆÄÀÏ - ±¸¸Å Ä«µå µ¥ÀÌÅͰ¡ ÀÖ´Â MIA(Business Edition)

´ÙÀ½ XML ÄÚµå´Â SET Ä«¼¼Æ®¿¡ »ç¿ëÇϵµ·Ï WebSphere Commerce¿¡¼­ Á¦°øÇϴ ǥÁØ °è»ê¿ø ÇÁ·ÎÆÄÀÏÀÔ´Ï´Ù. ÀÌ °è»ê¿ø ÇÁ·ÎÆÄÀÏÀº MIA(Merchant Initiated Authorization) SET È®ÀåÀ» »ç¿ëÇϸç Ä«¼¼Æ®¿¡¼­ Áö¿øÇÏ´Â ÀϺΠ¼±ÅÃÀû ±¸¸Å Ä«µå µ¥ÀÌÅ͸¦ ÁöÁ¤ÇÕ´Ï´Ù. ±¸¸Å Ä«µå ¹æ¹ýÀ» »ç¿ëÇÏ¿© ½ÂÀÎó¿¡ Ãß°¡ ±¸¸Å Ä«µå µ¥ÀÌÅ͸¦ º¸³À´Ï´Ù. ±¸¸Å Ä«µå¿¡ ´ëÇÑ Ãß°¡ Á¤º¸´Â ¸ÖƼ Ç÷§Æû¿ë IBM WebSphere Payment Manager , SET Ä«¼¼Æ® Ãß°¡ Á¤º¸, ¹öÀü 3.1À» ÂüÁ¶ÇϽʽÿÀ.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Profile SYSTEM "../../../../xml/PaymentManager/profile.dtd">

<!--
//*==================================================================
//* Licensed Materials - Property of IBM
//*
//* 5724-A18
//*
//* (c) Copyright IBM Corp. 2001
//*
//* US Government Users Restricted Rights - Use, duplication or
//* disclosure restricted by restricted by GSA ADP Schedule Contract with IBM Corp.
//*
//*================================================================== -->

<!-- ==================================================================
This is the Standard WebSphere Commerce cashier profile for the Payment Manager 
Cassette for SET (for Merchant Initiated Authorization)

This Profile specifies the optional Purchase Card Data supported by the Cassette.

Note: If you change the DEPOSITFLAG parameter of the Profile to "1" you must move the 
$PCARD.* parameters to the <CollectPayment> element of the Profile.
================================================================== -->

<Profile useWallet="false" enableTrace="true" >

<!-- Note the following Limitations:
1) The Cassette supports QUANTITY column with integer values only. Fractional parts are dropped.
2) OrderItems.CatEntry_id must not be null and CatEntShip and CatEntDesc entries for the CatEntry_id 
must exists with CatEntDesc.SHORTDESCRIPTION non null for the specified language_id.
3) The TAXAMOUNT, SHIPCHARGE and SHIPTAXAMOUNT Columns of OrderItems must not be null. 
-->
<!-- Note about the following 2 SelectStatement.
* ACTION REQUIRED FOR ORACLE USER *

Top SelectStatement is for DB2,
Buttom SelectStatement is for Oracle.

If you are running with ORACLE, please uncomment the second SelectStatement,
and comment out the first SelectStatement instead.
-->
<SelectStatement id="1" allowMultiples="true" >
SELECT PARTNUMBER, SHORTDESCRIPTION, integer(QUANTITY) as INT_QUANTITY, RTRIM(QUANTITYMEASURE) as QTYMEASURE, integer(PRICE*{currency_factor}) as UNITCOST,
integer( (TOTALPRODUCT+TAXAMOUNT+SHIPCHARGE+SHIPTAXAMOUNT+TOTALADJUSTMENT) * {currency_factor}) as TOTALCOST
FROM orderitems, catentry, catentship, catentdesc
WHERE orders_id = {orderId} 
AND orderitems.catentry_id = catentry.catentry_id
AND orderitems.catentry_id = catentship.catentry_id
AND orderitems.catentry_id = catentdesc.catentry_id
AND catentdesc.language_id = {buyer_language_id}
</SelectStatement>
<!--
<SelectStatement id="1" allowMultiples="true" >
SELECT PARTNUMBER, SHORTDESCRIPTION, round(QUANTITY) as INT_QUANTITY, RTRIM(QUANTITYMEASURE) as QTYMEASURE, round(PRICE*{currency_factor}) as UNITCOST,
round( (TOTALPRODUCT+TAXAMOUNT+SHIPCHARGE+SHIPTAXAMOUNT+TOTALADJUSTMENT) * {currency_factor}) as TOTALCOST
FROM orderitems, catentry, catentship, catentdesc
WHERE orders_id = {orderId} 
AND orderitems.catentry_id = catentry.catentry_id
AND orderitems.catentry_id = catentship.catentry_id
AND orderitems.catentry_id = catentdesc.catentry_id
AND catentdesc.language_id = {buyer_language_id}
</SelectStatement>
-->


<CollectPayment>

<!-- ==================================================================
Parameters required by Payment Manager for order creation
================================================================== -->
<Parameter name="PAYMENTTYPE"><CharacterText>SET</CharacterText></Parameter>
<Parameter name="MERCHANTNUMBER"><CharacterText>{storeId}</CharacterText></Parameter>
<Parameter name="ORDERNUMBER"><CharacterText>{orderId}</CharacterText></Parameter>
<Parameter name="CURRENCY"><CharacterText>{CURRENCY}</CharacterText></Parameter>
<Parameter name="AMOUNT"><CharacterText>{AMOUNT}</CharacterText></Parameter>
<Parameter name="AMOUNTEXP10"><CharacterText>{AMOUNTEXP10}</CharacterText></Parameter>



<!-- Indicates how automatic approval of the order should be attempted
Supported values are:
0 - no automatic approval
1 - synchronous automatic approval - Payment Manager attempts approval as
part of order creation operation
2 - asynchronous automatic approval - Payment Manager schedules an approval
operations after order is created

WCS works best with APPROVEFLAG set to 2. When the APPROVEFLAG is set to 1, the WCS 
DoPayment command is blocked until Payment Manager completes the approval of the order. 
Until this approval is complete, any commands wanting to read/update the same inventory 
records modified by the DoPayment command will be blocked. This will affect the throughput
of the other commands.
-->
<Parameter name="APPROVEFLAG"><CharacterText>2</CharacterText></Parameter>

<!-- The amount which should be used when approving an order. Usually
this will be the same as the order amount. This field is required
if the APPROVEFLAG is set to 1 or 2. -->
<Parameter name="PAYMENTAMOUNT"><CharacterText>{approval_amount}</CharacterText></Parameter>

<!-- The payment number which should be used when approving an order.
Usually this will be 1. This field is required if the APPROVEFLAG
is set to 1 or 2. -->
<Parameter name="PAYMENTNUMBER"><CharacterText>1</CharacterText></Parameter>

<!-- Indicates whether the deposit should be attempted automatically. 
This flag is only valid if APPROVEFLAG is set to 1 or 2.
Supported values are:
0 - Funds should not be automatically deposited. 
1 - Funds should be automatically deposited. 
The default value is 0.

Note: If you change the DEPOSITFLAG parameter to "1" you must move all the 
optional Purchase Card Data parameters from the <Command name="DEPOSIT">
element to the <CollectPayment> element for the parameters to be sent.
-->
<Parameter name="DEPOSITFLAG"><CharacterText></CharacterText></Parameter>

<!-- The following two parameters are optional. Either one could be used to pass the 
Buyer Purchase Order number to the Payment Manager. The first Parameter takes only 
ASCII Text. If Buyer Purchase Order numbers on your system may contain non-ASCII 
Strings, use parameter ORDERDATA2 instead. 
-->
<Parameter name="TRANSACTIONID" maxBytes="128" encoding="ASCII"><CharacterText>{PONumber}</CharacterText></Parameter>
<Parameter name="ORDERDATA2"><CharacterText></CharacterText></Parameter>


<!-- ==================================================================
Parameters required by the cassette
================================================================== -->

<Parameter name="$PAN" sensitive="true"><CharacterText>{card_number}</CharacterText></Parameter>
<Parameter name="$BRAND"><CharacterText>{cardBrand}</CharacterText></Parameter>

<!-- The expiry date in format YYYYMM -->
<Parameter name="$EXPIRY"><CharacterText>{card_expiry}</CharacterText></Parameter>



<!-- Used to specify the value of the TransMethod field passed in the MIA 
(Merchant Initiated Authorization) extension. The WCS Extension 
specifies one of the two values dependent on the protocol used.
0 (MIA_channelEncryption - if HTTPS was used)
1 (MIA_unencryptedWWW - if HTTP was used) 
--> 
<Parameter name="$TRANSMETHOD">
<ExtensionValue name="com.ibm.commerce.payment.extensions.GenericExtension" />
</Parameter>


<!-- The encoding attribute indicates to the Cashier that the bytes for the 
OrderDescription can be obtained from the returned String using the 8859_1 
character encoding because that was how the GenericExtension class encodes 
the bytes. The resulting bytes are in the language of the requester. -->
<Parameter name="$ORDERDESCRIPTION" encoding="8859_1" >
<ExtensionValue name="com.ibm.commerce.payment.extensions.GenericExtension" />
</Parameter>

<!-- ==================================================================
Optional parameters for the cassette
================================================================== -->

<!-- The cardholder's street address. 1 to 128 ASCII characters. -->
<Parameter name="$AVS.STREETADDRESS" maxBytes="128" encoding="ASCII"><CharacterText>{billto_address1}</CharacterText></Parameter>

<!-- The cardholder's city. 1 to 50 ASCII characters. -->
<Parameter name="$AVS.CITY" maxBytes="50" encoding="ASCII"><CharacterText>{billto_city}</CharacterText></Parameter>

<!-- The cardholder's state or province. 1 to 50 ASCII characters. -->
<Parameter name="$AVS.STATEPROVINCE" maxBytes="50" encoding="ASCII"><CharacterText>{billto_state}</CharacterText></Parameter>

<!-- The cardholder's postal/zip code. 1 to 14 ASCII characters. -->
<Parameter name="$AVS.POSTALCODE" maxBytes="14" encoding="ASCII"><CharacterText>{billto_zipcode}</CharacterText></Parameter>

<!-- The cardholder's ISO 3166 (3 digits) country code. This field is
required if any other AVS data is passed. -->
<Parameter name="$AVS.COUNTRYCODE"><CharacterText>{billto_country_code}</CharacterText></Parameter>

<!-- An identifier that the merchant uses to specify one of its locations. 
The value is specified as a String. 1 to 10 ASCII characters. -->
<Parameter name="$AVS.LOCATIONID" maxBytes="10" encoding="ASCII"><CharacterText></CharacterText></Parameter>



<!-- Some payment cards are issued with a verification code. The verification
code is generated by the issuing bank and can be verified by the bank. 
The account number followed by the three or four digit verification code 
is printed on the signature panel of the card. The value must be a 3 or 4 
character numeric string. Example values: 1234 or 321. -->
<Parameter name="$CARDVERIFYCODE"><CharacterText>{cardVerificationCode}</CharacterText></Parameter>

<!-- Indicates the content type and character set of the $ORDERDESCRIPTION 
parameter. -->
<Parameter name="$CHARSET"><CharacterText></CharacterText></Parameter> 

<!-- One of two fields in the merchData structure; when specified, the 
Cassette will use it. Value must be a 4-character numeric string. 
Note: The requirement to use this field will come from the acquirer. -->
<Parameter name="$MERCHCATCODE"><CharacterText></CharacterText></Parameter> 

<!-- One of two fields in the merchData structure; when specified, 
the Cassette will use it. Value must be a numeric string between 
"1" and "8". Semantics for possible values are described in the SET
specification. Note: The requirement to use this field will come 
from the acquirer. -->
<Parameter name="$MERCHGROUP"><CharacterText></CharacterText></Parameter> 

<!-- The MerOrderNum field is in the SaleDetail structure of CapReq and 
AuthReq (with capture now) messages. Value must be a character string 
with a maximum length of 24 characters. -->
<Parameter name="$MERORDERNUM"><CharacterText></CharacterText></Parameter> 

<!-- Indicates whether or not a merchant may approve additional shipments. 
Supported values are:
0-Indicates that this is the final payment for the order.
1-Indicates that the merchant may approve additional split 
payments for the order. -->
<Parameter name="$SPLITALLOWED"><CharacterText>0</CharacterText></Parameter> 

</CollectPayment>



<Command name="DEPOSIT">
<!-- ==================================================================
Parameters required by Payment Manager for DEPOSIT Command
================================================================== -->
<Parameter name="MERCHANTNUMBER"><CharacterText>{storeId}</CharacterText></Parameter>
<Parameter name="ORDERNUMBER"><CharacterText>{orderId}</CharacterText></Parameter>
<Parameter name="PAYMENTNUMBER"><CharacterText>{payment_number}</CharacterText></Parameter>
<Parameter name="AMOUNT"><CharacterText>{AMOUNT}</CharacterText></Parameter>

<!-- ==================================================================
Optional Parameters for Purchase Card Data 
================================================================== -->
<Parameter name="$PCARD.TOTALTAXAMOUNT"><CharacterText>{total_tax_amount}</CharacterText></Parameter>
<Parameter name="$PCARD.SHIPPINGAMOUNT"><CharacterText>{total_shipping_amount}</CharacterText></Parameter>

<Parameter name="$PCARD.MERCHANTORDERNUMBER"><CharacterText>{orderId}</CharacterText></Parameter>
<Parameter name="$PCARD.CUSTOMERREFERENCENUMBER"><CharacterText></CharacterText></Parameter>

<!-- Note the limitations listed for the SelectStatement to work -->
<Parameter name="$ITEM.PRODUCTCODE" maxBytes="12" encoding="UTF8">
<DatabaseValue statementID="1" columnName="PARTNUMBER" />
</Parameter>
<Parameter name="$ITEM.DESCRIPTOR" maxBytes="35" encoding="UTF8">
<DatabaseValue statementID="1" columnName="SHORTDESCRIPTION" />
</Parameter>
<Parameter name="$ITEM.QUANTITY" encoding="ASCII">
<DatabaseValue statementID="1" columnName="INT_QUANTITY" />
</Parameter>
<Parameter name="$ITEM.UNITOFMEASURE" maxBytes="12" encoding="UTF8">
<DatabaseValue statementID="1" columnName="QTYMEASURE" />
</Parameter>
<Parameter name="$ITEM.UNITCOST" encoding="ASCII">
<DatabaseValue statementID="1" columnName="UNITCOST" />
</Parameter>
<Parameter name="$ITEM.TOTALCOST" encoding="ASCII">
<DatabaseValue statementID="1" columnName="TOTALCOST" />
</Parameter>

</Command>


</Profile>

WC51_SET_MIA_PCard.profileÀº ´ÙÀ½ À§Ä¡¿¡ ÀÖ½À´Ï´Ù.
drive:\WebSphere\CommerceServer\instances\instance_name\xml\payment\
drive:\Program Files\WebSphere\CommerceServer\instances\instance_name\xml\payment\
/usr/WebSphere/CommerceServer/instances/instance_name/xml/payment/
/opt/WebSphere/CommerceServer/instances/instance_name/xml/payment/
instance root path/xml/payment/

¿©±â¼­ instance root path´Â ÀνºÅϽº ÀÛ¼º Áß¿¡ ±¸¼º °ü¸®ÀÚÀÇ ÀνºÅϽº ÆÐ³Î¿¡¼­ ÀνºÅϽº ·çÆ® °æ·Î Çʵ忡 ÁöÁ¤µÈ °æ·ÎÀÔ´Ï´Ù. ±âº» °æ·Î´Â /QIBM/UserData/WebCommerce/instances/instance_name/ÀÔ´Ï´Ù.

PAYMENTTYPE ¸Å°³º¯¼ö´Â ÀÌ ÇÁ·ÎÆÄÀÏ Ä«¼¼Æ®ÀÇ À̸§À» ÁöÁ¤ÇÕ´Ï´Ù.

¼±ÅÃÀû ±¸¸Å Ä«µå µ¥ÀÌÅÍÀÇ °ªÀº ÇÁ·ÎÆÄÀÏ¿¡ ÁöÁ¤µÇ¾î ÀÖ´Â SelectStatement¸¦ »ç¿ëÇÏ¿© WebSphere Commerce Å×ÀÌºí¿¡¼­ ¼öÁýµÈ´Ù´Â Á¡¿¡ À¯ÀÇÇϽʽÿÀ. ¿©±â¿¡´Â ´ÙÀ½°ú °°Àº ƯÁ¤ Á¦ÇÑ»çÇ×ÀÌ ÀÖ½À´Ï´Ù.

  1. Ä«¼¼Æ®´Â Á¤¼ö°ª¸¸ »ç¿ëÇÏ´Â QUANTITY ¿­À» Áö¿øÇÕ´Ï´Ù. ºÐ¼ö ºÎºÐÀº ¹ö·ÁÁý´Ï´Ù.
  2. ORDERITEMS Å×À̺íÀÇ CATENTRY_ID ¿­Àº ³Î(Null)°ªÀÌ µÉ ¼ö ¾ø½À´Ï´Ù. CATENTSHIP ¹× CATENTDESC Å×À̺íÀÇ CATENTRY_ID Ç׸ñÀº ÁöÁ¤µÈ ¾ð¾î ID¿¡ ´ëÇØ CATENTDESC Å×ÀÌºí¿¡¼­ SHORTDESCRIPTION ³ÎÀÌ ¾Æ´Ñ ¿­·Î Á¸ÀçÇØ¾ß ÇÕ´Ï´Ù.
  3. ORDERITEMSÀÇ TAXAMOUNT, SHIPCHARGE ¹× SHIPTAXAMOUNT ¿­Àº ³Î(Null)°ªÀÌ µÉ ¼ö ¾ø½À´Ï´Ù.

WebSphere Commerce´Â °è»ê¿ø ÇÁ·ÎÆÄÀÏÀÇ <BuyPageInformation> ¿ä¼Ò¸¦ »ç¿ëÇÏÁö ¾Ê½À´Ï´Ù. µ¿µîÇÑ ±â´ÉÀÌ ÁöºÒ Á¤Ã¥ÀÇ attrPageName Ư¼º°ú ÇÔ²² Á¦°øµË´Ï´Ù.

ÀÌ °è»ê¿ø ÇÁ·ÎÆÄÀÏÀ» »ç¿ëÇϱâ Àü¿¡, »óÁ¡¿¡ ´ëÇØ ÀÌ ÇÁ·ÎÆÄÀÏÀ» ÁöÁ¤ÇÏ´Â(¿¹¸¦ µé¾î, policy_id°¡ 301°ú °°À½) ÁöºÒ Á¤Ã¥À» »ç¿ëÇÏ·Á¸é ¾à°£ÀÇ º¯°æÀ» ¼öÇàÇØ¾ß ÇÕ´Ï´Ù. Áö½Ã»çÇ׿¡ ´ëÇØ¼­´Â SET Ä«¼¼Æ®¿ë °è»ê¿ø ÇÁ·ÎÆÄÀÏ °»½Å - ±¸¸Å Ä«µå µ¥ÀÌÅͰ¡ ÀÖ´Â MIA(Oracle¿ë)¸¦ ÂüÁ¶ÇϽʽÿÀ.

SET Ä«¼¼Æ®¿¡ ÇÊ¿äÇÑ ¸Å°³º¯¼ö¿¡ ´ëÇÑ Ãß°¡ Á¤º¸´Â ¸ÖƼ Ç÷§Æû¿ë IBM WebSphere Payment Manager, SET Ä«¼¼Æ® Supplement, ¹öÀü 3.1À» ÂüÁ¶ÇϽʽÿÀ.

°ü·Ã °³³ä(1275¹ÙÀÌÆ®)

°ü·Ã ÂüÁ¶(1275¹ÙÀÌÆ®)

IBM copyright