SENDSAFE ADVANCED CONFIGURATION
All robot (or backend) configuration information for SendSafe is contained in several; ASCII configuration files. All these files can be modified using a text editor. This section will explain each field, and show how to find and modify these configuration files.
The ASP GUI is configured by making changes to the database using Admin Pages and (or) by modifying the appropriate SendSafe.global.asa file.
SendSafe uses config files instead of the Window's Registry for some very good reasons. (1) You know exactly how the program is configured. (2) This makes mirroring SendSafe configurations a snap. (3) If you want to move SendSafe to a new machine, you can do so by just copying the configuration files.
None of these advantages would be there if the data was saved in the Registry. A program that uses the registry is inadvertently implementing a means of preventing you from moving that program to a new machine. We believe that SendSafe JSOF is an important business tool. Your business could suffer if SendSafe JSOF does not work right or cannot be Primarily moved from a broken computer to a working machine.
Before modifying any configuration file always make a backup copy of the file
Advanced configuration of the SendSafe system is accomplished by modifying the system's storefront config files. These files are modified by editing them with a standard ASCII text editor (notepad.exe works file). You must never modify any configuration files directly on the web server. You should only modify the files found in the default "..\SendSafe\<your store name>.Store\config" directory and the "..\SendSafe\<your store name>.store.config" file.
In this example layout of the configuration files, SendSafe has already been configured to have three different storefronts named: (1) BOBSFISH, (2) GIFTSRUS, & (3) CANDYPALACE.
The
jsof.config is the
global storefront file. Setting in this file are used as defaults when creating
new storefronts. Also some of the settings in this file are global and override
those settings found in a specific storefront config file.
The ServerSideFiles subdirectory is the default template of set of files used when creating new storefronts. Unlike the jsof.config, these files are used only as templates and do not contain any global settings.
In the follow sections you will find detailed information on modifying each of the configuration files (see also Directory Structure of Robot)
STOREFRONT BASKET CONFIGURATION
Each storefront is configured using the AdminStoreConfig.asp admin page.
(Example of Open Basket Config Page)
On this admin page you can configure:
Each ASP site (and storefront) has a global.asa file that is used to configure the site/storefront. SendSafe global.asa configurations are all entered into a seperate asa file that is included into the global.asa file. The global.asa file must be in the root directory of your web site.
If you do not have a global.asa file as part of your existing website then you can simply manually copy the provided global.asa file out to the root directory of your website. The global.asa file is located in the Robot Program subdirectory (..\SendSafe\ServerSideCode) and is named global.asa.
If you already have a global.asa file as part of your website then the following ASP code must be insterted into your global.asa file.
<SCRIPT LANGUAGE=VBScript RUNAT=Server>
Sub Application_OnStart
' DO NOT
REMOTE THE COMMENT TAG BELOW!!!
' <<#BEGIN
SENDSAFE DATA#>>
Application_SendSafe_OnStart
' <<#END SENDSAFE DATA#>>
' DO NOT REMOTE THE COMMENT TAG ABOVE!!!
End Sub
</SCRIPT>
<!--#include
file="SendSafe\SendSafe.global.inc.asa"-->
The name of the SendSafe global.asa include file is: SendSafe.global.asa. This file is located both on the Webserver in the ./root/SendSafe and in the robot's asp\SendSafe directory. This file should be modified in the SendSafe program directory located in a subdirectory named MyStore.store where MyStore = the name you gave your storefront (see Directory Structure of Robot)
|
Application("odbcAdmin_DSN") = "MYDB"
|
The name of the ODBC DSN used for basic access to the database for web admin pages. |
|
Application("odbcAdmin_USERID") = "Admin"
|
DEPRECIATED N/A: Was the Logon Id used for basic web access to the database for web admin pages. Set to same value as shopping ODBC below. |
Application("odbcAdmin_PASSWORD") = "Admin"
|
DEPRECIATED N/A: The Logon password used for basic web access to the database for web admin pages. Set to same value as shopping ODBC below. |
|
Application("odbcShopping_DSN") = "MYDB"
|
The name of the ODBC DSN used to access the core database for the shopping cart and admin pages pages. |
|
Application("odbcShopping_USERID") = "User"
|
The Logon Id used for general web access to the core database for the shopping cart pages and admin pages |
|
Application("odbcShopping_PASSWORD") = "User"
|
The Logon password used for general web access to the core database for the shopping cart pages and admin pages. |
|
Application("EnableDSNSODBC") = false
|
True/False enabled Multiple ODBC DSN mode. See: Multiple dsn db control |
|
Application("DSNSODBCDefaultPrefix") = "ABC"
|
This is the default DSN Prefix used for Multiple ODBC DSN mode. See: Multiple dsn db control |
|
Application("DSNSPermCookies") = false
|
True/False Save the DSNSODBCDefaultPrefix in a permanent cookie. If set false (default) then the prefix will be saved in a session cookie. See: Multiple dsn db control |
|
Application("StoreCode") = "MYSTORE" |
The name of the storefront. |
|
Application("ORDERQUEUEDIRECTORY") = "c:\program files\jsof\input"
|
This is the location on the server where the SendSafe Robot will for incoming orders. WARNING! Do not share this directory location or make this directory location accessible to any computer or logon.
This must be the same directory location defined in the storefront configuration file keyword = "EMSG INPUT PATH" |
|
Application("urlfor_ADDBASKET") = "Store.addbasket.asp" Application("urlfor_CHECKOUTSTEP1") = "Store.reviewbasket.asp" Application("urlfor_CHECKOUTSTEP2") = "Store.Checkout.asp" Application("urlfor_ERECEIPT") = "Store.EReceipt.asp" Application("urlfor_ITEMLINEEDIT") = "Store.EditBasketLine.asp" Application("urlfor_LOGON") = "Store.CustomerLogin.asp" Application("urlfor_BASEORDERINGPAGE") = "BuySendSafe.asp" Application("urlfor_ADMINORDERINGPAGE") = "Store.addbasket.asp" Application("urlfor_LOSTPASSWORDPAGE") = "Store.lostpswd.asp" Application("urlfor_PASTPURCHASELISTPAGE") = "Store.PurchaseList.asp" Application("urlfor_MYACCOUNTPAGE") = "Store.MyAccount.asp" |
These are the names of the ASP files which serve each specific "standard" function of the e-store. |
|
Application("urlfor_CHECKOUTSTEP1.1") = "" |
Optional intermediate step between STEP1 and STEP2. Leave empty if not used. |
|
Application("urlfor_CHECKOUTSTEP1.1OneWay") = false |
Set true if optional intermediate step is OnewWay i.e. it will be skipped over going backward (prior/back buttons). |
|
Application("AllowAdminImpersonationWOPwd") = false |
Allows Impersonation of customer (i.e. placing orders as a specific customer) without requiring the entry of an escalation password on the admin page. |
|
Application("ExtendDataCoupon") = false Application("ExtendDataCouponTableName") = "CouponExt" Application("ExtendDataCustomer") = false Application("ExtendDataCustomerTableName") = "CustomerExt" Application("ExtendDataDealer") = false Application("ExtendDataDealerTableName") = "DealerExt" Application("ExtendDataItem") = false Application("ExtendDataItemTableName") = "ItemExt" Application("ExtendDataLineItem") = false Application("ExtendDataLineItemTableName") = "LineItemExt" Application("ExtendDataOrder") = false Application("ExtendDataOrderTableName") = "OrderExt" |
Enables/Disables use of extended DB tables on each of the indicated admin pages.
This will allow a 2nd extended DB table to be relationally linked and managed within the single Admin form.
The true/false entry enables the function.
The TableName entry identified the 2nd table which will be linked. |
|
Application("CustomBottomOfBasketMessage") = ""
|
This message will be displayed at the bottom of the shopping cart basket on every page. |
|
Application("CustomCreditCardMessage") = "" |
This message will be displayed below the credit card entry field and type dropdown box on the billing information page. |
|
Application("CustomShippingAddressNotes") = "" |
This text will appear directly to the right of the address field on the shipping information page. |
|
Application("DisableShipRecalcOnReviewPage") = false |
Disables the display of shipping costs in the ReviewBasket page (Shipping Info). |
|
Application("FreeFormParamEnabled") = true |
Enabled Free-Form Parameter operation (see also FreeFormParams DB column) |
|
Application("FreeFormParamPreFix") = "__FFP__" |
Sets the prefix used to ID free-form item parameters and which enables FreeFormParams entry into the extended Order LineItems fields. (see also FreeFormParams DB column and Free-Form Params.) |
|
Application("DiscountSQLQualifier") = "" |
Set to empty to enable the discount plan for everyone. Set to an SQLQualifier string to selectively enable discount plans.
For example: Set to an invalid value to disable for all customers. see also Discount Pricing |
|
Application("SpecialCustomerDiscounts") = "" |
1/0 = Enable/Disable Special customer discount pricing.
see also Discount Pricing |
|
Application("enableSpecialAndRetailPricing") = true |
1/0 = Enable/Disable the use of special pricing in the wishlist and reorder pages.
see also Special Pricing in e-store framework |
| Enables the display of the Serializer number (instead of order number) on customer shopping pages. There are limitations. The serializer is not assigned until an order is approved; if and until that point, the order number will be displayed. (see Serializer DB Column and see also serializer robot settings) | |
|
Application("PEReceiptsSerializedLable") = "C/N" |
A label used for the Serializer Number (see Serializer DB Column)..) |
Application("OrderStatusSelect") = "distinct top 30 orders.transactionid, date, Shipmethod" OPTIONAL: |
This is SQL Select syntax used on the Order Status page. (see for more information) |
Application("OrderStatusSelectColLables") = "order#, date, Shipping status" |
These are the column labels displayed in the order status page. (see for more information) |
|
Application("OrderLineItemSKUList") = "" |
Enter an SQL Select statement for selecting a list of SKUs from the DB (i.e. select * from items where productType = 'RETAIL'). These SKUs will be used to populate a dropdown list of SKUs for the "Load Values from SKU" function on the AdminLineItem page. If this list is not filled in, SKUs will need to be entered by hand into the input field. This SQL statement is manually set because in most applications it cannot be used because there are just too many SKUs to place them in a dropdown list. Do not place more than a few hundred SKUs in the list or it will become unusable. |
Application("LogonMessage") = "Welcome to our store..."
|
Text message displayed when a customer successfully logs into the store. |
|
Application("securityDefaultRememberLogin") = true |
Selects whether the default is to remember (save) the customer’s logon in a cookie or not. |
|
Application("securityAllowDupPassword") = false |
Allow multiple customers to use the same password. The customer Id must always be unique but the password is optional. |
|
This allows a customer to NOT create an account. An account userid & password will be automatically assigned to the customer. You must also include a URL parameter NVector or GVector
It is recommended to leave this option turned off. | |
|
Application("DefaultCustomerLoginRedirect") = Application("urlfor_BASEORDERINGPAGE") |
This setting defines the default page which is vectored to after successful login or account creation. This vector will only be taken if a URL passed vector is not provoided. For more info see: Login Vectoring |
|
Application("securityDefaultHidePasswords") = true
|
If enabled then the password will be hidden (as a default)… i.e. the default state will be to hide the password with "****" while being entered.
The hide/unhide check box option is always available. |
|
Application("securityRequireLogon") = true |
This is a legacy option which requires that a customer logon and creates a customer account.
It is recommended that this option always be enabled. |
|
Application("requireShiptoEMail") = false |
Make the entry of an e-mail address on the shipping information page a required field.
This can be useful if customers are sending products to some else and you want to collect the e-mail address of the recipient.
This option is also important if multiple shipping addresses are enabled. |
|
Application("MyAccountSaveDialog") = "" |
Setting this string to a value will cause a YES/NO dialog box to open on the MyAccount page after a save has occured. This dialog box will display this message and take the vector specified by Application("MyAccountSaveDialogVector") |
|
Application("MyAccountSaveDialogVector") = "" |
Vector to take if OKAY is selected in the Application("MyAccountSaveDialog") dialog box. typical value: "browser.asp?TopList=subcat&ResetBrand=yes" |
|
Application("allowPurchaseListURLLogon") = false |
Allow logon to the past purchase list (page) by passing the password as a URL parameters.
It is strongly advised that this option remain disabled. |
This is the amount of time in minutes before the ZDI encrytor expires (TTL). This value times 2 equals the maximum amount of time that any ZDI logon token will be valid. This effectively sets the maxium amount of time that a user will be able to shop using thier current browsing session. As long as cookies are working for the visitor, they will transparently recieve login to a new session and never know it. This value should be set large enough so that customers do not experience excessive session transitions BUT also not so large that ZDI encryptors does not change atleast once every 24 hours. This value is also used for 2nd tier security in case of duplicate decryptor strings; to time expire any potentially invalid ZDI and EDI parameters. An ZDI/EDI 3 x Application("ZDIEncryptorTTL") or older will be discarded. See also Security Settings | |
| This is the amount of time in minutes after browsing activity ends before the EDI token expires (TTL). Browsing activity is monitored as any e-commerce activity in the SendSafe system or web pages which load the sendsafe.statecontrol.inc.asp file. If you have web pages which do not include basic sendsafe logic (statecontrol) then use the SendSafe.ActivityMon.inc.asp include to keep the activity monitor fresh. See also Security Settings and DB Maintenance | |
|
Application("LockTokensToIPAddr") = false |
Enables/Disables locking the LogonToken to a specific IP Address. |
|
Application("EnabledDynamicEReceipt") = true |
Enables dynamic e-receipt updating of the html e-receipt page. If this is enabled charge approval and other related information will not be updated as the order is processed |
|
Application("DynamicEReceiptReloadTime") = 8 |
This is the initial refresh time for the dynamic e-receipt (in seconds). |
|
Application("LockTokensWithEDI") = true |
This locks the EDI token to the ZDI token. If this is not set then EDI and ZDI tokens will not expire at the end of a session. |
|
Application("RecoverEDIFromSessCookie") = true |
This enables the use of coookies to recover an EDI if a chain of customy is broken. |
|
Application("UseSessEnd") = false |
Set true if you are not running the web site in a seperate memory space (i.e. pool memory). Setting this value true will provide an addition means of expiring E-Commerce Sessions using the ASP End Session event. |
|
Application("EReceiptMsg") = "For downloadable products a link will be provided on this page and in the e-mailed confirmation once your order has been approved." |
This is a text message that is displayed on the e-receipt (prior to a downloadable payload being made available). |
|
Application("idsSessionTimeout") = 10 |
Number of minutes before an IDS Session times out. |
|
Application("idsHelpEMailAddr") = "info@youbiz.com" |
Help e-mail address that is displayed if an IDS lockout occurs and a lockout message is displayed. |
|
Application("idsBlacklistBadCIDEnabled") = true |
Enable BAD CID Login checking and customer blacklisting by the IDS. CID logon is automatic logon using cookies OR URL parameter logon token.
If a customer is blacklisted they will be blocked from accessing the website for designated period of time (see below). |
|
Application("idsBlacklistBadCIDLoginTriggerCnt") = 5 |
Number of bad CID logins during sample before blocking (blacklisting) occurs |
|
Application("idsBlacklistBadCIDLoginTriggerInterval") = 240 |
The sample Period (in minute) during which bad CID logins are checked and accumulated.
If X bad CID logons occur from the same IP address in this number of minutes THEN a customer is blacklisted. |
|
Application("idsBlacklistPeriodBadCIDLogin") = 120 |
Number of minutes to block (blacklist) all bad CID logons from a given IP address.
Good CID logons will not be blocked from this IP address ONLY bad CID logons. |
|
Application("idsBlacklistBadPIDEnabled") = true |
Enable BAD Userid/Password (PID) Login checking and customer blacklisting by the IDS. Userid/Password logon is a logon where the customer keys in their Userid & password.
If a customer is blacklisted they will be blocked from accessing the website for designated period of time (see below). |
|
Application("idsBlacklistBadPIDLoginTriggerCnt") = 25 |
Number of bad PID logins per IP before black listing (blocking). |
|
Application("idsBlacklistBadPIDLoginTriggerInterval") = 10 |
The sample Period (in minute) during which bad PID logins are checked and accumulated.
If X bad PID logons occur from the same IP address in this number of minutes THEN a customer is blacklisted. |
|
Application("idsBlacklistPeriodBadPIDLogin") = 2 |
Number of minutes to block (blacklist) all bad PID logons from a given IP address.
Good PID logons will not be blocked from this IP address ONLY bad PID logons. |
|
Application("auditFileRootLocation") = "c:\project\jsof ssl\jsof\audit\" |
The physical address where Web Activity log files will be created.
This is the base directory. Actual log files will be created in date-stamped subdirectories which are automatically created as needed. For performance reasons, it is strongly recommmended that a physical hard disk different than the website (webserver) be used. |
|
Application("auditFileCurrentDateDir") = ""
|
This is a management variable used by the system and should not contain any value unless you understand the implications.
This value is the date of the currently created audit file date-stamp subdirectory. |
|
Application("auditEnabled") = true |
Enable basic information level auditing of web activity. |
|
Application("detailedAudit") = false
|
Enable detailed information level auditing of web activity. |
|
Application("cacheFolder") = "data_cache" |
Defines the folder which will be used for caching some page content (search results, tables, PastPurchaseLists, etc.). The folder will be created on the same drive as the audit files (as defined by Application("auditFileRootLocation") For performance reasons, it is strongly recommmended that a physical hard disk different than the website (webserver) be used. This folder will be automatically created if it does not exist. However, if this folder specification contains a path of multiple folders then you will need to manually create this path. |
|
Application("PayloadsLockedAtQty") = false |
If enabled this will disable the ability to change the quantity ordered on products which will be downloads (i.e. payloads). This is useful if digital documents or images are being purchased and it would make no sense for the customer to order duplicates of an item. |
|
If set to a value > 0 this will enable the display of thumbnails in the shopping cart. This number is the max value for thumbnails which will be displayed. Once this number is reached thumbnails will no longer be shown in the cart (to limit download times for carts with lots of products in them). | |
|
Application("ShippingMethodNames") = "Ground,SecondDay,NextDay,Saturday"
|
This is a comma delimited list of the descriptions of the shipping methods which are available for this storefront. |
|
Application("DirectAddToCart") = ""
|
This true/false flag enabled or disables DirectAddToCart mode. When in direct add to cart mode, a customer does not have to login before an item is added to the cart. If this mode is disabled, the customer will be prompted to login or create an account before the item is added to the cart. |
|
Application("MinOrderSize") = 0
|
Set to a min dollar amount that an order must total before checkout is allowed. Set to zero to disable testing. See also: Basket setup |
|
Application("MutuallyExclusiveProducts") = ""
|
This is a comma delimited list of ProductTypes which are mutually exclusive AND cannot be ordered with any other products i.e. the shopping cart can only contain these items. See also: MutuallyExclusive Products |
|
Application("fullNameSortPrefixRevLen") = ""
|
The the number of columns reserved for sorting control (default=0) This prefix must be used in combination with setting all display strings in the e-store framework to use FullName. see also: category sorting prefix |
|
Application("SalesTaxZipCodeMask") = 3
|
This value sets the number of sgnificant zip code digits which are checked for sales tax calculations. This value should never be set zero when zip code matching is used. Setting this value to zero combined with zip code match will result in a random selection of a tax rate for a given state. See also: setting up sales tax |
|
Application("StateShipString") = "XX,APO,AL, AK,AZ,AR,CA,CO,CT,DE,DC,FL,GA,HI,ID,IL, IN,IA,KS,KY,LA,ME,MD,MA,MI,MN,MS,MO, MT,NE,NV,NH,NJ,NM,NY,NC,ND,OH,OK,OR, PA,RI,SC,SD,TN,TX,UT,VA,VT,WA,WI,WV,WY" |
This is a comma delimited list of all States OR provinces OR territories which are to be listed in the State dropdown list for shipping and billing addresses. The number of entries in the table is not limited. You can have 50 entires or 500 entries (for performance reasons keep the list as small as possible). If you are using zone shipping cost calculations then there must be one entry made in the shipping cost table for every entry in this list. |
|
Application("AdminCustomerPgShowShoppingHist") = true |
Enabled/disables the display "Place order as" call center functions AND display of ordering history (Last Purchase Date, ordering preferences, etc.). |
|
Application("AdminLockedToStoreCode") = false |
Enabled/disables locking the orders and orderlineitem page to a fixed storecode specified by Application("StoreCode"). |
|
Application("DealerIDEntryLabel") = "Dealer ID" |
This is the label displayed on the Review Order and Edit LineItem entry pages. |
|
Application("DealerIDTracking") = false |
This entry will enable or disable functions used when tracking dealers (DealerID) on orders. When enabled the DealerID code can be entered into the Review Order and Edit LineItem pages. The system will also track (as a preference) the last used DealerId and automatically fill it in. See Also Dealer Database Columns and Overview. |
|
Application("BasketItemOrdering") = "RequiredShipDate, Category, NickName" |
This is the sort (ordering) which is applied to shopping cart displays and other displays of order line items. |
|
Application("BasketItemOrdering") = "RequiredShipDate, Category, NickName" |
This is the sort (ordering) which is applied to shopping cart displays and other displays of order line items. |
|
Application("SuppressAllOrderTallies") = false |
Supresses the display of Order total amount, shipping, tax, etc. on basket pages.. |
|
Application("SuppressBasketDisplay") = false |
Supresses the display of the shopping basket and order tallies (same as Application("SuppressAllOrderTallies") = true) on checkout pages. |
|
Application("SkipOverBasket") = false |
Causes the checkout process to skip basket and proceed directly to shipping or login. When enabled, returns button/actions from shipping page will go to Application("urlfor_BASEORDERINGPAGE") and browser back button will not work. |
|
Application("dbErrorNumberDupPrimaryKey") = -2147217900
Application("dbErrorMsgSignatureDupPrimaryKey") = "Cannot insert duplicate key"
|
Means of identifying
Duplicate Primary Key Errors. Both the error number & signature
(string snip) are required to ID the error since
Warning… This value is operating system specific. Changing this value will cause duplicate records in the database. |
|
Application("IAPHeapAllocRetryCntWarningThreashold") = 10 |
The DB Record Insert retry level which WHEN exceeded will generate warning displays in the shopping cart Admin page. |
|
Application("IAPHeapAllocRetryCnt") = 250
|
The number of times to retry a db RECORD INSERT operation |
|
Application("IAPTopOfHeap") = Clng( 2000000000 ) |
The maximum number of records in any INSET managed table. The default is 2 billion. |
|
Application("SessionCookieTimeout") = 0 |
This the the TTL in hours for session cookies.
The default value = 0 which results in session cookies that last for the entire active session.
If this value is set a fixed number of hours then the cookie will expire in that number of hours regardless the state of the session. |
|
Make this value unique for all servers. ID value for each web server. Used in some types of audit records to ID the web server when multiple servers are hosting a site. Also used by EDI decommissioning in system where there are mutiple http servers. This value is typically defined by the contents of the Application("SIDFileLoc") file. This value feeds into the SID column of logonsession records. | |
|
Application("SIDFileLoc") = "C:\sendsafe_sid.dat" |
(Optional) If a file location is specified and a file is found THEN the first line of the file will be used for the ServerID (over writting the value set by Application("ServerID"). This is useful for multiple http server system where replication of configuration and web site files is performed. This allows the same global.inc.asa file to be used on more than one server AND still maintain differen serverId's for each physcial box. See also: Replication job |
|
Application("MaintModeCtrl") = "127.0.0.1" |
The IP Address of clients which will not be blocked from viewing the site when in maintenance mode. |
|
Application("MaintModeSemFileName") = "c:\project\jsof ssl\jsof\sendsafemm.enabled"
|
Semaphore file name which is checked to enable maintenance mode.
If this file is present than maintenance mode is enabled. |
|
Application("MaintModeMessage") = "<H1><FONT FACE=ARIAL>MAINTENANCE IS IN PROGRESS.</H1><H3>E-COMMERCE OPERATIONS ON THIS SERVER ARE TEMPORALLY DISABLED.<BR>PLEASE CHECK BACK IN 15 MINUTES… THANK YOU.</H3></FONT>" |
The message which is displayed when in maintenance mode. |
|
Application("SendSafeSessions") |
System use… Contains the number of active sessions. This value is displayed on the Storefront admin page. |
|
Application("SendSafeSessionsLimiting") = 99999
|
This enables session limiting. If the number of customer sessions exceeds this value then the customer will see the Session limiting message below and not be allowed access until the number of active sessions falls below this level. |
|
Application("SendSafeSessionsLimitingMsg") = "<p><font face=arial>This website is temporarily experiencing heavy traffic. To make sure that the shopping experience is great for everyone we are limiting the number of people who can shop at one time.</font></p>" |
Message displayed when session limiting is occurring. |
|
Application("HelpFileLink") = "http://www.c-prompt-dev.com/JsofEntryHelp.asp"
|
Link to help information page which is displayed when the help button is pressed on the shopping cart pages |
|
Application("SupportEMail") = "support@yourbiz.com"
|
This is the help e-mail address which is displayed on both the session limiting message AND the failed browser tests message page(s). |
Items are added and updated using the AdminItem.asp admin page or by using these import tools. The Admin page modifies the Items Database table. Please review the documentation on each column in this table before adding any new items to the database.
If you are using the optional e-store framework, you do not need to add any items to the DB at this time. You can continue to use and experiment with the items imported from the \database\E-StoreFrameWorkDemoItems.mdb file.
You must have one item to the database for each product that you will sell in your e-store. If your items will be organized into lists and sublists then categories and sub-categories information should be entered and used to control list structure. If you did not purchase the SendSafe e-store framework, then display of product browsing lists such as drilldown browsing is something that you will have to program yourself when you develop your site.
Note: If you are not using the optional e-storefront infrastructure, then when setting up your storefront for the first time you should add four test products to the database. These four products will be used when modifying the SendSafe.BuySample.asp page. The modified SendSafe.BuySample.asp page will render Buy Buttons for these items you have added to the database (see for details). Do not worry about all the settings when adding these four test products; just make up names, prices, and shipping data for now.
MutuallyExclusiveProducts
Specific Products can be configured so that no other
products are allowed in the basket when that product is present. This can be
useful for selling mutually exclusive products such as subscriptions or
services. To configure a product to be mutually exclusive list the productTypes
as "MutuallyExclusiveProducts" in the SendSafe.global.asa
configuration file.
Application("MutuallyExclusiveProducts") = "MagazineSubscriptions,WholesaleAccounts"
Advanced Items Configuration and Related Topics:
These commands are implemented as functions, subroutines, or SendSafe system objects. Example of how to use these commands can be found in the SendSafe.*.asp files. These commands can be used to customize SendSafe.*.asp storefront pages.
| Page Command | Default Value or Common Value | Explanation |
| sub: disableBrowserTesingOnThisPage | n/a | This subroutine will disable browser testing on a SendSafe page. This should not be disabled unless you know what you are doing. |
| sub: SetProductListModeSQL | "Select * from Items" | This is demo code to show how to set ProductList mode. This mode will create a drop down list of products to pick from instead of a non-editable text item name. If this variable is empty THEN we are not in ProductList mode SetProductListModeSQL "Select * from Items" |
| sub: SetItemDisplayField | "NickName" | This is demo code to show how to control what is displayed for the product name. This OPTIONAL variable holds Items table column name which will be used to display the "Item Name" in the entry form. If this variable is empty THEN the name will be the FullName. SetItemDisplayField "NickName" |
| sub: SetItemDisplayField | "FullName" | This is demo code to show how to control what is displayed for the product name. This OPTIONAL variable holds Items table column name which will be used to display the "Item Name" in the entry form. If this variable is empty THEN the name will be the FullName. SetItemDisplayField "NickName" |
| function: setEnableNetscape4ArialFontBug | (true) | This flag enables handling of the Netscape 4.x Arial font bug. This bug causes Netscape 4.x to incorrectly calculate the entry field width needed to accomidate arial fonts. If you are using arial fonts and the forms are coming out too on Netscape 4.x, then enable this switch. setEnableNetscape4ArialFontBug(true) |
| sub: SetDealerId | Dealer Id Code | This is demo code to show how to set a dealer id. Typiclaly this value would come from a cookie. SetDealerId 1997 |
| function: SetshippingFunctionTitle | ( "Shipping" ) | This variable holds optional Page Funtional Description SetshippingFunctionTitle( "Shipping" ) |
| objects: sendSafeCfg.button xxx | sendSafeCfg.buttonReturnPriorIMG = "images/continueshopping.gif" sendSafeCfg.buttonReturnPriorHEIGHT = 27 sendSafeCfg.buttonReturnPriorWIDTH = 143 sendSafeCfg.buttonPressCompleteIMG = "images/proceedtocheckout.gif" sendSafeCfg.buttonPressCompleteHEIGHT = 27 sendSafeCfg.buttonPressCompleteWIDTH = 161 | This is an example of how to over-ride default buttons set in storefront DB records with buttons that will be unique for a signle page... be sure to reset these button overrides (see uses in sample files) |
CONFIGURATION OF THE SENDSAFE JSOF ROBOT
see also: B2B Configuration
When you use setup dialogs to make changes, the ASCII file(s) named "..\SendSafe\<your store name>.store.config" or jsof.config is one of the files that is modified. Advanced configuration of the SendSafe JSOF Robot can be accomplished by modifying this file using a text editor (notepad.exe works fine).
| FILE = "..\SendSafe\<your store name>.store.config" or
jsof.config (default) part 1 Before modifying any configuration file always make a backup copy of the file.
| ||
| Keyword | Default value | Explanation |
| START E-COMMERCE NUMBER | 1000 | This is a numeric "offset" from which e-commerce message tracking numbers will be assigned. This is sort of like the starting check number for a checking account. This offset number must be no larger than 999999999. |
| AUTORUN PERIOD | 0 | The elapse time that the Robot will automatically run (in minutes). Once this time expires the robot will self- terminate. To enable auto-run to NOT TIMEOUT and run forever set the time value to zero. If autorun is used then "EMSG UPDATE RATE" less than 1/4 the "AUTORUN PERIOD" and "CIPHER PAD UPDATE RATE" should be 1/2 the "AUTORUN PERIOD" (see also). |
| ASP GUI MODE | YES | YES/NO are you running the ASP GUI. This command will cause several small adjustments to be made to the operation of the system. |
| MIXED GUI MODE | NO | YES/NO are you running both the JavaGUI and the ASPGUI at the same time. This command will cause several small adjustments to be made to the operation of the system. |
| AUTORUN ENABLED | YES/NO Is auto-run enabled. This forces the Robot to start running as soon as it is loaded and it will continue to run for "AUTORUN PERIOD" length of time (see also). Autorun can also be enabled by placing a command line parameter of "-S" into the short-cut used to start the robot. | |
| AUDIT FILE LOC | AUDIT | Location to place all robot audit files. For performance reasons, it is strongly recommmended that a physical hard disk different than the website (webserver) be used. |
| PURGE AUDIT FILES | 10 | How many days old an audit file has to be before it is automatically purged.Set to a very large number to disable (something like 10,000 days works fine!). |
| DISPLAY ONLY TODAYS TRANSX | NO | Set Yes/No: "Yes" will display only today's transactions, No will display all transactions (for all transaction audit files that exist in the audit directory). |
| GENERATE EMAIL LIST FILE | YES | Generates a file named EMAILADDRESS.MM.DD.YY.TXT in the output directory. This file contains the email address and name from the billing information for each order. The file is in comma delimited format AND intended for importing into a mail list programs. |
| SOCKET OPEN TIMEOUT | 300 | Socket open timeout in seconds. |
| SOCKET READ TIMEOUT | 180 | Socket read timeout in seconds: applies to read and waitfor operations |
| MAKE CONNECTION | - | (Optional) Fully qualified (or PWD relative) batch or executable to be run which will start the Internet Connection. If no process is to be run then set this value to a "-" string... i.e. "MAKE CONNECTION = -" |
| MAKE PARAMS | - | (Optional) Parameters for the connection process. If no parameters are passed THEN use the "-" string as a null parameter indicator |
| MAKE TIMEOUT | 300 | The time in seconds to wait for a connection process to complete before aborting the operation. This timeout is NOT the amount of time the robot will wait for a connection when sharing connections between IC Verify and Internet (i.e. shared modem). The wait for a shared resource timeout is set by "MAKE WAIT SHARED TIMEOUT". |
| MAKE WAIT SHARED TIMEOUT | 300 | This is the amount of time that the robot will wait for shared connection to be freed before giving up and going on to some other task. This time is in seconds. This value does not need to be very large since the robot will come back to try all timed out process again. |
| BREAK CONNECTION | - | (Optional) Fully qualified (or PWD relative) batch or executable to be run which will stop the Internet Connection (leave empty to run nothing). If not process is to be run then set this value to a "-" string... i.e. "MAKE CONNECTION = -" |
| BREAK PARAMS | - | (Optional) Parameters for the disconnection process. If no parameters are passed THEN use the "-" string as a null parameter indicator |
| BREAK TIMEOUT | 300 | The time in seconds to wait for a disconnection process to complete before aborting the operation. This timeout is for the actual process AND NOT the time that the robot will wait for a disconnect when sharing resources. |
| MAX WEIGHT PER PACKAGE | 140 | This is the maximum shipping weight that you will be using per item. Limiting this number will speed applet load times (since the entire table will not have to be loaded and parsed). The max value for this entry is 150 pounds. This is a pass-through value that is filled into the shipper.config file. |
| SHIPPING EXCEPTION MSG | <SHIPPING EXCEPTION RULES APPLY> | Change this string to customize the message inserted into the printed order when a shipping exception occurs. |
| SERVER IP ADDRESS | x.x.x.x. | This is the IP Address that CGIGate will use to communicate with the Robot (a.k.a. Server) see also |
| SERVER PORT BLOCK START | 8000 | The starting port address for the server thread run by this robot. see also |
| SERVER PORT BLOCK SIZE | 10 | The number of server thread run by this robot. see also |
| CSV CODE | NO | Set to true to enable handling of the CSV code column in the DB column of {CreditCard} table of the database. | PAYLOAD ENABLED | NO | Set to true to enable handling (and processing) of automated downloads of digital payloads (downloadable products). The storage location of a product is defined in the Payloadloc column of {Items} table of the database. |
| PAYLOAD DIR ENCODING LEN | 40 | This value sets the character length
of the subdirectory that is used to obfuscate and encode the payloads. This number can be set higher for greater security or lower for reduced secruity. It is not recommend to set this value to less than 30 characters. Also, anothing beyound 80 characters may cause hyper link problems from some e-mail viewer which break links that wrap to more than one line into seperate pieces (such as AOL Web E-Mail). |
| PAYLOAD DOWNLOAD BASE DIR | PAYLOADS
Virtual or full paths are allowed... i.e. x:\mydir\payloads or payloads |
This is the location where the robot will build order fufilment payloads. It is can be either a full or relative path. This base directory is also the location from which the ftp or web server loads out product downloads (more info). More than one directory path can be specified were each path is delimited by semicolons. This is useful for reduntant server setups where you may want to save the payload to more than one location. This physical base directory MUST BE THE SAME directory configured as a virtual directory in the web server (or FTP server) and DEFINED BY PAYLOAD BASE URL. This enables the URL in the e-reciept to reference the payload created in this directory. No trailing "\"... allowed! Under this directory is where the robot will build temporary download directories which contain the payloads. For example: PAYLOAD DOWNLOAD BASE DIR =
x:\ourpayloads x:\ourpayloads\<temp download dir 1> |
| DB VALIDATION TEST MODES | IX | This keyword controls the types of
tests performed by the Integrtity Testing
Tool. Valid entries for this string are:
R = Report missing payloads only (does not effect
tests run) |
| PAYLOAD SOURCE BASE DIR | <none> | This is the full or relative base
directory from which the web server collects product files for
inclusion in a payload. (more
info). No trailing "\"...
The value of this keyword is set to the words <none> (enclosed in brackets) then digital payload collection "Option A" will be enabled. The value of this keyword is set to directory path (not <none>) then digital payload collection "Option B" will be enabled. |
| PAYLOAD BASE URL | http://yourserver/payloads | This is the full URL from which the web server provides product downloads (more info). No trailing "/"... |
| PAYLOAD TTL | 168 |
The time (in hours) that the payload will be available before it is removed from the web server (more info). Warning... If a single shared download directory is used, then the TTL value will end up being set globally for the entire web server. The lowest TTL value found in the jsof.config or any storefront, will be applied. |
| ENABLE ZIP PASSWORD | YES | YES/NO Enable or disable the addition of the User's password to the zip file. |
| PICTUREFILE BASE DIR | <none> |
This path identifies the base location for the website. This path is used to locate picture files specified in the database Items table (fields PictureFileA and PictureFileB). BASE LOC + PictureFileA = full path to file This value should be set to <none> if full paths are specified for picture files in the database fields, picture files are not used, or a database is not used. This keyword value is used during database testing (only). Example: C:\Inetpub\wwwroot\myWeb This field may contain a comma delimited list of locations. |
| WEBSITE BASE URL | http://www.mywebsite.com | This is the base URL for the website. This value is required. Failure to set this value correctly will result in the system not working correctly and / or operating unreliably. |
| IM INTEGRATED INSTALL PATH | "" | ImageMagick Installation directory. Not used at this time. Future expansion. |
| CLUB MEMBERSHIP ITEM | <none> | Identifies an ITEM for special handling. This item is used to sell membership in clubs, on-line discount
programs, and etc..
If a matching <ITEM CODE ID> is ordered and credit card charges are authorized, THEN the SendSafe robot will set the DiscountPlan field for this customer's record to the <FLAG> value specified in this configuration item. Contains <ITEM CODE ID> : <FLAG> WHEN ItemCodeId from database matches the item then the club membership flag is set for the customer. Set this keyword to <none> to disable club item checking and processing. Hint: You can use a zero cost item to automate people signing up for a free club membership! See also: discount pricing |
| PLACEHOLDER PRODUCT TYPES | <none> | Identifies placeholder products by
product type. All line items with PRODUCTTYPES
that match this list will have their value set to zero in each order as it
is processed by the robot. Example: PLACEHOLDER PRODUCT TYPES = BALLS,BATS,BIKES To disable this function set this keyword to "<none>". Some of the uses of placeholder products are: To allow gift lists to be imported. To allow entry of products that require manual handling. Notes: *PLACEHOLDER products must never include SalesTax or Shipping charges (since these costs are not deducted). *You must have Credit Card processing enabled for the PLACEHOLDER function to work. |
| CGIGATE OUTPUT LOC | X:\OUTPUT | This location is where the gateway will save copies of e-commerce messages that are not able to be sent to the robot (i.e. if the robot is off-line). This locattion must be extremely secure since credit card information will be found in it (in the case of error). see also |
| CGIGATE AUDIT LOC | X:\AUDIT | This is the location that the gateway will place it's audit files see also |
| DATABASE SETUP (see database tools for automated setup and test of a database). | ||
| ENABLE DATABASE | NO | Enabling this option will cause the robot to place orders, customer records, etc. in the database... and also to use the database to enable QuickBuy operations. |
| ODBC DSN | SendSafe | This is the name of the DSN setup using ODBC. This is how SendSafe connects to a database |
| DBSCHEMA | abo | This is the name of the database schema (or schema name). In SQL Server the Schema name is often by default the same as the owner of the database. If you are unsure run the SCHEMATA view from the master database table. This view will list all databases and their schema name (for other database servers refer to your manuals). |
| ODBC USERID | UserId | This is the user id used from access to the database |
| ODBC PASSWORD | password | This is the password used from access to the database. The clear text password cannot begin with a '#'. This value should be entered via the Primary Setup Dialog box; if you enter this value manually then it will not be encrypted. |
| SECURE ODBC DSN | SendSafe | This is the name of the DSN setup using ODBC for access to the credit card number database. THIS DATABASE MUST NEVER HAVE ACCESS OF ANY KIND FROM THE INTERNET. |
| SECURE ODBC USERID | UserId | This is the user id used from access to the database |
| SECURE ODBC PASSWORD | password | This is the password used from access to the database. The clear text password cannot begin with a '#'. This value should be entered via the Primary Setup Dialog box; if you enter this value manually then it will not be encrypted. |
| FILE = "..\SendSafe\<your store name>.store.config" or
jsof.config (default) part 2 Before modifying any configuration file always make a backup copy of the file.
| ||
| Keyword | Default value | Explanation |
| EMSG UPDATE RATE | 10 seconds | Update rate in seconds - how often do
we check the cache for e-commerce messages (orders).
This value can also effect the rate at which e-coupons are issued and other order processing related robot jobs such as checking for orders that may have been placed while the robot was not on-line. Recommend values are 5 to 15 seconds. This value is global. This means that the key word is only checked in the jsof.config (file). Entires in store front files are ignored. |
| JOB RATE | 15 seconds | Update rate in seconds - sets how often are queued jobs run.
This value can also effect the rate at which e-coupons are issued and other order processing related robot jobsRecommend values are 15 to 120 seconds. If you are not using functions such as giftlist processing which require rapid customer response, set this value 120 seconds to save system resources. This value is global. This means that the key word is only checked in the jsof.config (file). Entires in store front files are ignored. |
| EMSG INPUT PATH | INPUT |
Location where new e-messages are placed (this is where orders are initially held before it has been processed). Orders (*.emsg files) can be manually copied into this directory. Orders copied into this directory will be run in about 30 seconds. This value is global and only effective in the jsof.config file. All values in storefront files are ignored. You can have only one input path per system. This value must match the ORDERQUEUEDIRECTORY set in the SendSafe.global.asa file. |
| EMSG OUTPUT PATH | OUTPUT | Location where raw e-messages are placed once processed. |
| EMSG ARCHIVE PATH | ARCHIVE | Location to archive e-messages that have been completely processed or have experienced errors. |
| ADMIN EMSG HTML PATH | ADMINHTLM |
This is a location where the robot will store viewable administrator html copies of your order. If remote admin access to full viewable orders is required, then this directory should placed in a subdirectory under the inetpub directory and made accessible to browsers. This directory should be accessible via https only, and under password or personal digital certificate access control. To disable creation of these output files set the
value to <none> i.e. This output file is redundant when running the ASPGUI and using a database. The Admin.ASP files replace all functions of this file. WARNING! This copy of orders may contain unmasked credit card number information depending upon configuration setting ADMIN EMSG HTML CCMASK |
| ADMIN EMSG HTML CCMASK | YES | Setting this control to YES will cause
the credit card number displayed in the html copies of orders in the "ADMIN EMSG HTML PATH" to have the credit
card number masked (only showing 4 digits of the cc number).
For security reasons, it is recommended that if credit card numbers are unmasked, then there should be no web access to these Admin html files; at the very least if web access is allowed then the files should be secured with https and some type of strong password access control such as personal digital certificates. |
| CUSTOMER EMSG HTML PATH | CUSTHTML |
This is a location where the robot will store viewable customer html copies of your order. These order copies do not contain unmasked credit card numbers. This directory is typically placed in a subdirectory under the inetpub directory and made accessible with password control to customer. Access control is typically provided via ASP based queries of user identification (i.e. Userid/Password or User Name, Address, & zipcode). To disable creation of these output files set the
value to <none> i.e. This output file is redundant when running the ASPGUI and using a database. The Admin.ASP files replace all functions of this file. |
| EMSG FILE EXTENSION | .emsg | File extension to use for e-messages |
| EMSG FILE OUTPUT EXTENSION | .complete | Extension for deciphered e-msg including dot ".emsg" |
| EMSG PENDING PROC EXTENSION | .pending | Extension for emsg that are waiting for more information before being processed |
| EMAIL SERVER | Mailhost.yourisp.net |
Name of the primary e-mail server. Note: The e-mail server listed in the jsof.config file will be used for alert reporting (see CC ADMIN). In all other cases, each storefront can use a different e-mail server. |
| EMAIL BACKUP SERVER | Mailhost.yourisp.net |
Name of the secondary (or backup) e-mail server. If the primary e-mail server fails, the robot will use this secondary server for all e-mail (e-receipts, e-coupons, alerts, etc.) Note: The e-mail server listed in the jsof.config file will be used for alert reporting (see CC ADMIN). In all other cases, each storefront can use a different e-mail server. |
| EMAIL SMTP PORT | 25 | The port that the SMTP e-mail server is sent to (typically 25). |
| EMAIL POP3 PORT | 110 | The port that the POP3 e-mail server is sent to (typically 110). |
| EMAIL USERID | yourname (or sometimes yourname@yourbiz.com) |
E-mail account user id name used for ESMTP authentication / login or POP3 before
send security option. |
| EMAIL PASSWORD | yourpassword | Email account user password used for ESMTP authentication / login or POP3 before send security option. The clear text password cannot begin with a '#'. This value should be entered via the Primary Setup Dialog box; if you enter this value manually then it will not be encrypted. |
| EMAIL POP BEFORE SEND | NO |
Enable POP3 before send of any e-mail. If disabled (i.e. EMAIL POP BEFORE SEND = NO) then ESMTP authentication / login will be used. EMAIL USERID and EMAIL PASSWORD are the logon credentials that are used. Make sure that the same account is present on both the Primary and backup e-mail servers: EMAIL SERVER and BACKUP EMAIL SERVER |
| EMAIL TTL POP BEFORE SEND | 0 | This is the time in seconds that a
Pop3 authentication is valid for a specific e-mail server. If the time
between Pop Before send is set to 600 seconds on the e-mail server. This
value should be set to 600-10% = 540 seconds.
Setting this value to zero will force the robot to perform a Pop Before Send for every e-mail being sent. This can add unnecessary overhead to the systems. See also: POPSB.xxxx.audit files which contain a record of all successful POP3's sent to a server. |
| EMAIL POPBOX LOCKED MSG | maildrop already locked | This optional string specifies an
error message that can be ignored as part of "POP3 Before Send"
operations.
This message may be different for different servers. The contents of this message is irrelevant if: or EMAIL POP BEFORE SEND = NO |
| EMAIL IGNORE ERR POP BEFORE SEND | NO | During "POP3 Before send"
operations: If YES then Ignores any errors that occur as a result of
authentication of password OR afterwards. For example if the mail box is
locked or password is bad, then these errors will be ignored.
If the User Name is incorrect, then this error will not be ignored. This switch is good if you want to do a pop before send, but do not care about the status of this operation. This may be valid if more than one E-Mail Reader or Robot are sharing the same User Account. |
| ROBOT EMAIL ADDRESS | n/a | Depreciated and no longer in use. |
| ENABLE EMAIL PROCESSING | NO | Enabled special operations e-mail processing. Always leave sent to NO. |
| EMAIL DEBUG | NO | Enabled detailed tracing of e-mail
operations to the audit file xxx.email.audit.
This flag will cause detailed e-mail server dialogs to be saved to the audit file. This can be very useful in discoverying problems with e-mail SMTP and POP3 activities. |
| COMPANY EMAIL ADDRESS | sales@c-prompt-dev.com | EMail return address of the company doing biz on the web. This will be used for sending automated responses This address will appear in the "From:" part of the e-mail header. To disable automated e-mail responses set the e-mail address to blank (empty). |
| RECEIPT PAGE | Store.PEReceipt.asp | Webpage loaded to display e-receipt OR set to <none> to disable HTML Web base e-receipts. You must have the e-receipt OUTPUT FORMAT set to short for web based receipts to function. This entry is only the file name i.e. "Store.PEReceipt.asp" with the base URL coming from WEBSITE BASE. |
| RECEIPT ACKNOWLEDGMENT SUBJECT | Order Confirmation from SendSafe | e-mail "Subject" line for automated
receipt e-mail message. This is what will be inserted for the "subject" on
all e-commerce e-mail send by the SendSafe JSOF system. (for more details) |
| RECEIPT ACKNOWLEDGMENT MESSAGE | We will send you e-mail to confirm when your order has shipped \ngiving you the UPS tracking number and the ability to track \nthe shippment's "up-to-the-moment" progress and process!\n\nPlease come visit us again at http://www.c-prompt-dev.com |
EMail Message send as an automated e-receipt
message. This should be just a few sentences (limited to 1000
characters including spaces). The special formatting character "\n" and "\t" are processed
into a New Line (CRLF) and (TAB) respectively and special mail-merge like keywords can also be included.
|
| RECEIPT WRAP DESC | NO | If enabled this will cause longer lineitems to linewrap if they are too wide. The default will truncate descriptions. |
| RECEIPT SUPPRESS CC INFO | NO | If enabled this will suppress all information about credit card charges including sucess or failure. This is useful for sites which do not process credit cards on line. |
| RECEIPT QUICKBUY TEXT | 3. "Instant Checkout" - On future orders you will be able to use our exclusive "Instant Checkout" feature. Once you select the items you wish to purchase, click "Checkout" and you will see the "Instant Checkout" button. You can now shop and checkout in seconds! 1-Click and your done! | Text displayed in e-receipt describing instant checkout function. This should be just a few sentences (limited to 500 characters). |
| RECEIPT ORDER HISTORY TEXT | 2. "Order History" - View your order history and quickly re-order previously ordered products. http://www.mybiz.com/SendSafe.PurchaseList.asp | Text displayed in e-receipt describing order history function. This should be just a few sentences (limited to 500 characters). |
| RECEIPT MYACCOUNT TEXT | 1. "My Account" - You can change any of your website registration information such as address, email address, user id and password. https://www.mybiz.com/SendSafe.MyAccount.asp | Text displayed in e-receipt describing My Account function. This should be just a few sentences (limited to 500 characters). |
| ERECEIPT DOWNLOAD HELP LINK | http://www.mybiz.com/downloadHelp.asp | URL for help link inserted into the e-receipt. |
| ERECEIPT FOOTER | E-Commerce Processed by SendSafe (c) C Prompt. | E-receipt footer text. This should be just a few sentences (limited to 500 characters). |
| RECEIPT CONTACT LINK | http://www.mybiz.com/Contact.asp | URL for contact inserted into the e-receipt. |
| RECEIPT BUSINESS NAME | My Biz | Name of e-store business which is inserted into the e-receipt. This value must be set to your company name in the global config file jsof.config. In storefront files this value should be set to the name of the company for that storefront. Failure to enter this information correctly in the jsof.config file will result in error messages and the system refusing to process orders. |
| EMSG USER PASSWORD MASK | NO | If enabled this will mask the User Password which is included in the e-receipt sent to the customer. |
| UNLOCKCODE | 000000.000000 | The unlock code is found in the e-receipt you were e-mailed when SendSafe was purchased. Failure to enter this information correctly will result in error messages and the system refusing to process orders. |
| STORE CONTACT INFO | MyStore\n111 Sunny Rd.\nCity, State\n99999\nPhone: 222 333-4444 | This text string is appended to some
(not all) of the e-mail messages sent to customers. The purpose of
this string is to provide contact information. The string should contain
your company name, address, phone number, etc. (limited to 500
characters).
Example of this strings use:
The special formatting character "\n" and "\t" are
processed into a New Line (CRLF) and (TAB) respectively. |
| PASSWORD RECOVERY MESSAGE | Thanks for using MyBiz. Below is your userid and password. | This is the text is displayed in the body of the password recovery e-mail set out by SendSafe. |
| E-COUPON WEBSITES | http://www.mybiz.com | This is one or more URLs to the web sites where these coupons can be used. Seperate multiple web sites with a single space character. |
| E-COUPON CLOSING MESSAGE | Thanks for being our customer! We look forward to seeing you again soon! | This is the closing paragraph of the e-coupon e-mail. This text is used to personalize the e-coupon for your business. A single sentence is recommend. Limit the length to 500 characters. |
| E-COUPON SUBJECT | E-Coupon from MyBiz | This is the subject line of the e-mail that contains e-coupons. |
| E-COUPON MESSAGE | Here's a MyBiz E-Coupon! | This is the first paragraph of the e-coupon e-mail. This text is used to personalize the e-coupon for your business. A single sentence is recommend. Limit the length to 500 characters. |
| E-COUPON HELPLINK | http://www.c-prompt-dev.com/JsofEntryHelp.htm#Coupons | This is a URL that will be displayed in the e-coupon. It typically is used to pull up a web page that has e-coupon instructions or help. |
| E-COUPON FIELD LABEL | E-COUPON | This sets the label used for coupons in e-receipts and elsewhere. |
| E-COUPONS FRIENDLY | NO | Turning on "Friendly Coupon" numbers results in less secure e-coupon numbers which are easier for customers to work with. Friendly coupon numbers are limited to Uppercase Alphabetic characters only (no numbers or lower case). Character length of friendly coupons is the same as the more secure variant. |
| ORDER VIEWER | notepad.exe | Program used to view customer orders (default value is notepad.exe). Make sure a path is set to this program or the full path is specified. | ALLOW DUPSKUS | NO | Configures the system to allow for duplicate SKUs in the items table. |
| SERIALIZER | NO | Enable/Disable serializing orders by adding a serialization number to the orderpostproc table. (see Serializer DB Column and see also Serializer in Web Pages) |
| REP ORDERNUMBER WITH SERIALIZER | NO | Enables the display of the Serializer number (instead of order number) on e-receipts. If set to anything other than NO or <none> the serializer value will be used instead of an order# and this field will become the label for the serializer number (wherever it is used). There are limitations. The serializer is not assigned until an order is approved; if and until that point, the order number will be displayed. Orders that are not approved will not get a serializer number. (see Serializer DB Column and see also Serializer in Web Pages) |
| VOIDCLONE ALL ORDERS ENABLED | NO | Enable/Disable creating a voided clone of all orders processed by the robot. |
| ORDERLINEITEMSEXT TABLE ENABLED | NO | Enable/Disable handling of OrderLineItemExt DB table. |
| DEPLEX QUANTITY LINEITEMS | NO | Enable/Disable deduplex orders with a quantity > 1 (breaks up all order line items in descrete lineitems with quantity=1 each).
This deplexing occurs as a final step. It occurs after subscriptions are processed, orders are cloned, and everything else has been processed. This deplexing is not useful for subscriptions. This deplexing is useful for orders which need to be borken into descrete lineitems without and additional processing occuring on a line item. |
| CONDDEPLEX LINEITEMS | NO | Enable/Disable conditional deplex of flagged lineitems in an orders with a quantity > 1 (breaks up all flagged line items in descrete lineitems with quantity=1 each). This is very useful for subscription orders which may need a seperate LineItem record for each subscription. This deplexing occurs before subscriptions are processed (unlike DEPLEX QUANTITY LINEITEMS). Items are flagged for deplexing by including a $DF$ in the productType column for the item. |
| SUBSCRIPTIONS ENABLED | NO | Enable/Disable processing of subscription orders (see subscriptions). |
| SUBSCRIPTION TERMINAL COUNT | 5 | The number of times a refill charge must fail before a subscription is disabled. Minimum value = 5 (see subscriptions). |
| ONLYSERIALIZE B2B | YES | Enable/Disable serializing ONLY B2B orders by adding a serialization number to the orderpostproc table. see also: B2B Configuration |
| PRINTER DRIVER PRINTER DEVICE PRINTER PORT |
set by printer dialog or manually | These parameters are set by the
printer selection dialog AND should not be changed except by those
knowledgeable in NT or 95/98 system setup. You can have a different
printer for each storefront.
Note: Setting PRINTER DRIVER = <none> will disable automated printing for a specific storefront, while allowing for printing by other storefronts. |
| ENABLE ELIST PROCESSING | NO | Switched E-List processing On and Off. This causes the shopping basket to be bypassed and all shipping addresses left as undressed. This is used for handling gift lists. |
| ELIST EMAIL USERID | E-List E-mail account user id name. | |
| ELIST EMAIL PASSWORD | E-List Email account user password. The clear text password cannot begin with a '#'. This value should be entered via the Primary Setup Dialog box; if you enter this value manually then it will not be encrypted. | |
| ADDRESS LABEL STRING | This string is used to configure the printing of shipping address lables (see label printing) | |
| GIVER ADDRESS LABEL STRING | This string is used to configure the printing of giver/billing lables (see label printing). | |
| COURIER LABEL STRING | This string is used to configure the printing of courier address lables (see label printing). | |
| COURIER PRINTING EXCEPTION | YES | Yes/No If YES only shipto addresses that are in the exception file will be printed as courier labels |
| COMMENT LABEL STRING | This string is used to configure the printing of comment or gift card lables (see label printing). | |
| CC ADMIN LIST | <none> |
A list of e-mail addresses where SendSafe alerts will be sent. This is useful as a means of notifying admin personal that a SendSafe warning has occured. Each email address needs to be separated by a semicolon i.e. john@company.com; mary@company.com;fred@happytrails.com NOTE: Only the e-mail address in the jsof.config file will be used (storefront config file entries will be ignored). Also, the mail server listed in the jsof.config file (and not the storefront files) will be the e-mail server that is used. See also SendSafe Admin |
| CC ALERT LIST | <none> |
A list of e-mail addresses where SendSafe send Urgent Alerts. This list typically contains one or more SMTP Pager e-mail addresses. This is a way of notifying admin personal that an Urgnet SendSafe alert has occured. Each email address needs to be separated by a semicolon i.e. john@company.com; mary@company.com;fred@happytrails.com NOTE: Only the e-mail address in the jsof.config file will be used (storefront config file entries will be ignored). Also, the mail server listed in the jsof.config file (and not the storefront files) will be the e-mail server that is used. See also SendSafe Admin The current list of alerts going to this list are:
|
| CC DEALERS | NO | This flag is set to either YES or
NO. If set to yes, any dealers that get commission on this order will
recieve a copy of the order (the same as CC
EMAIL LIST). The e-mail address for the dealers is obtained by
searching the sendsafe database. If a database is not used, then this
function will not operate.
See Also Dealer Database Columns and Overview. |
| SUPPRESS DEALER CC |
This is a semicolon delimited list of ItemCodeIds for Items that if pressent in the order will then cause the Dealer CC for that order to be supressed. This config string over-rides all other settings. This is useful to supress CC's on items that are not relevent for a dealer. This flag only has effect of "CC DEALERS" is set to YES. See Also Dealer Database Columns and Overview. | |
| CC EMAIL LIST | <none> | A list of e-mail addresses that will be (carbon) copied all orders processed by the JSOF system. This is useful as a means of notifying certain personal that a SendSafe order has been processed. Each email address needs to be separated by a semicolon i.e. john@company.com; mary@company.com;fred@happytrails.com |
| CC ACKNOWLEDGEMENT MASK | 4 | Number of digit to display from the left side of the credit card max value = 4 |
| OUTPUT FORMAT | SHORT | The format of e-mail ack
message, printed reports, and html order receipts: SHORT, LONG, or DOMNAME
(see email messages, html orders, order printing for more
information).
Hint: Do not forget to set the Order Form Entry mode to match Long or Short formats. |
| ENABLE QTY PRICE | NO | This field enables quantity pricing and will cause the robot to load the qtyprice.config file and apply it to all effected items (see quantity pricing for details). |
| NSI SESSION STRING | This is the connection string used to setup an SSL encrypted RRPSession with the on-line NSI Registry. (See NSI Order FulFilment for more information). | |
| NSI PLUGIN LOC | NSIPlugin | This is the relative or full path location of the Optional NSIPlug (NSIPlugin.jar file). |
| NSI ENABLED | NO | Enables/Disables NSI Domain
Registration Order Fulfilment. This is used when the SendSafe storefront
is using the NSI Support Optional to sell
domain names.
If this option is enable, when an order for a domain name is processed, SendSafe will connect to the on-line NSI Registry System (using an SSL connection) and insert the Domain Name + Name Servers thereby completing the Domain Name order. This option can only be used by Certified Domain Name Registars. SSL Certificates and NSI Accounts are required. (See NSI Order FulFilment for more information) |
| FILE = "..\SendSafe\<your store name>.store.config" or
jsof.config (default) part 3 Before modifying any configuration file always make a backup copy of the file.
| ||
| Keyword | Default value | Explanation |
| SECURITY UPDATE RATE | 60 | Max Update rate in minutes - how often
do we check on the server-side data files. The actual security scans are
performed at random intervals with this value being the maximum.
Warning: Do not set this value to zero or negative values. System stalling may occur. The system will enforce a max value of 4 hours. |
| FTP SERVERNAME | yourwebserver.net | The name of the ftp server that will be used for file upload & security work OR <none> if direct file access will be used. |
| FTP USER NAME | username | User Account name for FTP site. |
| FTP PASSWORD | password | User Account password for FTP. The clear text password cannot begin with a '#'. This value should be entered via the Primary Setup Dialog box; if you enter this value manually then it will not be encrypted. site. |
| FTP RECOVERY PAUSE | 30 | In the event of ftp server errors, this is the time to wait in minutes (for the server to recover) before trying again. |
| FILE = "..\SendSafe\<your store name>.store.config" or
jsof.config (default) part 4 Before modifying any configuration file always make a backup copy of the file.
| ||
| Keyword | Default value | Explanation |
| VERIFICATION PERIOD | 240 | n/a |
| APPLET CONFIG FILES LOCAL LOC | ServerSideCode\config |
The source location of the applet's config files in the robot installation directory. |
| APPLET CONFIG FILES SERVER LOC | x:\inetpub\config | The location of the applet's config files on the web server. This is either a web directory or a file share location. |
| APPLET CLASS FILES LOCAL LOC | ServerSideCode\Java | The source location of the applet's class files in the robot installation directory. |
| APPLET CLASS FILES SERVER LOC | x:\inetpub\Java | The location of the applet's class files on web server. This is either a web directory or a file share location. |
| ASP FILES LOCAL LOC | ServerSideCode\asp | The source location of the applet's class files in the robot installation directory. |
| ASP FILES SERVER LOC | x:\inetpub | The location of the applet's class files on the web server. This is either a web directory or a file share location. |
| PERL ID SCRIPT SERVER URL | https://web2/Scripts/JSOFClientId.pl | The http URL of the Perl ClientID Script on the web server. (see also PERL ON NT SERVER). |
| SCRIPT FILES LOCAL LOC | x:\inetpub\Scripts | The source location of the Script files in the robot installation directory. |
| SCRIPT SERVER LOC | /Scripts | The location of the script files on the web server. This is either a web directory or a file share location. |
| HTML JSOFBASKET REL URL | JSOFOrderFormPart1.htm | This is the relative URL for the html page that will contain the SendSafe Basket applets. Typically this "Relative URL" is just the filename of the order form page. |
| HTML JSOFSHIPPER REL URL | JSOFOrderFormPart1.htm | This is the relative URL for the html page that will contain the SendSafe Shipper applets. Typically this "Relative URL" is just the filename of the order form page. |
| STOREFRONT | DEFAULT | There will be one storefront entry for each storefront supported by the robot. These storefront entries will only be placed in the jsof.config file and not the <storefront>.store.config files. |
Two or more robots can be configured to verify the operational status of each other using watchdog jobs. These jobs check for updates to audit file data. If audit file data is being updated then the robot is considered to be running. If not audit file data has not been updated for a specified period of time then the robot is considered to be not running and an e-mail alert is issued.
The SendSafe job scheduler has a built in watchdog job that is used for creating robot watchdogs. To create jobs that perform watchdog operations follow the steps below (see also jobqueue).