SDSS Subscription Server v.2
HELP

Remote Content Server Configuration Information

[FAQ][TroubleShooting][HowTo][Login]
[Legal]

SDSS Introduction and Getting Started

The SDSS is an online, Java-Based e-commerce service application designed to give you the ability to:

  1. Provide free, paid or private online subscription services for siteDirector infobase access.
  2. Provide free, paid or private online subscription services for file downloads.
  3. Provide shopping cart and online payment mechanism for shipped or downloaded information products.
  4. Configure and maintain, online via browser, all service information.
  5. Generate comprehensive reports, online via browser, on all service activity.

General Requirements: To get started with SDSS:

  1. siteDirector 4.2 running and accessible over the Internet.  This is required if you intend to provide secure infobase access and is NOT required for File Download subscriptions or Shopping Cart.
  2. SDSS Softpages (supplied by us).  These are the replacements to the default siteDirector 4.2 Softpages.  If you use customized Softpages, we will need to update SDSS to recognize them.  The cost for this is $25 per Softpage.  Again, these are only necessary for infobase subscriptions.
  3. Internet Access via a browser.
  4. An Online Merchant Account.  This is required if you wish to utilize online credit card clearing and on-the-fly fee-based subscriptions.  By "on-the-fly"   we mean that a user can pay for a subscription by credit card, the card is authorized on the spot, and the user gains, if a successful authorization,  immediate access.  If you do not have a merchant account, you can still sign up for SDSS and use ours temporarily until yours is issued.  We charge, however, a 25% per transaction fee for all transactions cleared using our merchant account -- so we highly recommend you get yours ASAP!

    SDSS is currently set up to integrate with CyberCash online credit card clearing services.  CyberCash charges between $400 and $800 for the setup fee, and around $40 to $70 a month with a $.10 to $.20 per transaction fee.   If you have an online merchant account with another company, we will consider creating a clearing link to them.  However, there may be a fee involved in doing so as each company has a completely different set of requirements.

top

Provide free, paid or private online subscription services for siteDirector infobase or file download access.

sdss1.gif (3864 bytes)

SDSS is designed to allow you to set up your siteDirector infobases for secure online subscriptions.  This means that a user cannot access a SDSS-secured infobase or download file without having first logged in with a username and a password.  The username and password assigned can be selected by the end-user at signup, or generated by you.  The signup process for end-user access can be based on providing demographic information (free), or on a fee-basis.  The fees for access to your infobases or files are based upon hourly, daily, weekly, monthly and annual rates, or any combination of these.  All of these options, and end-user pricing, are determined by you.

Using the "subscription" mechanism for file downloads means that you intend to update the file in question over time, whether it be an infobase or some other software product.  If you are only interested in one-time purchases of your file download, you should use the SDSS "shopping cart" described below.  Click here for a brief description of the differences between the two file download mechanisms.

Online Subscription Getting Started: The process for using SDSS to provide secure subscriptions for your infobases or file downloads is as follows:

  1. Sign up for an SDSS Client Account at our website: http://www.scbbs.com/sdss.html.  This will give you an administrative "Client"  login username/password, and a "Source" code used to maintain your company-specific information.  You will select the number of "Subscriptions" and "Infobases" you desire to create under SDSS. 
  2. Log into the SDSS Client website at: http://dns.scbbs.com/~client and define your Subscription Record(s) (SDSUB) . There four types of subscriptions: Paid, Free, Private and File Download.  Paid, Free and Private are always infobase subscriptions (i.e., access to siteDirector Infobases).   File Download is always for paid file download subscriptions.

    Every SDSS secured infobase must belong to a subscription.  You can have multiple subscriptions, and you can have multiple infobases for each subscription.

    sdss2.gif (2325 bytes)

    The Subscription Record consists of: the subscription title and description, the URL location of a complete description of the subscription, the currency, the hourly, daily, weekly, monthly and/or annual rates, the URL where a successful login should begin, the subscription type (Download, Free, Private or Paid), the duration of the login period, the message to be sent to new signups, and the download directory if this is a file download subscription (we will provide this information).  You will receive a "Subscription Code" once this information is initially stored. 
  3. Next, if this is an infobase subscription, you need to define the "Infobase(s)" which will be secured under this subscription.  This is the Infobase Record(s) (SDNFO) . We need to know the infobase alias (what your siteDirector 4.2 recognizes the infobase as), the title and description, and the Subscription Code created in step number 2.
  4. If the subscription is for file downloads, you need to e-mail the administrator sysop@scbbs.com to advise of such. ALL SDSS controlled file downloads must be defined in the File Download table. The administrator will let you know the ftp site where you should upload your files, the URL you should point your customers to, and the download directory information for your File Download records.  You will need to enter all download files associated with this subscription into the File Download table.
  5. Download the SDSS Softpages and assign them as the default Softpages for your infobase(s) to be secured.

That's it.  For infobase subscriptions, once your Softpages are installed on your siteDirector server, and you have set up the Subscription and Infobase records correctly, your infobase is now secured under SDSS.  Users will have to sign up, based upon the parameters you have chosen, to access them.  for download subscriptions, you will be able to provide secured access to your files as soon as we assign you your ftp site.

If you intend to charge for access,  remember that the system is e-commerce ready as soon as you enter your subscription information.  It will use our merchant account (at a fee of 25% per transaction) until we have set it up to use your merchant account.   This does not apply to non-pay subscriptions.

Download and Install SDSS Softpages

The SDSS Softpages are specifically designed to interact with SDSS.  You cannot secure an infobase with SDSS without using the default or customized SDSS Softpages.   If you do not install the SDSS Softpages correctly, your infobases may NOT be entirely secured under SDSS. 

If you don't understand anything else about this process, please understand this: Every sD Frame Softpage that can be used to access your infobase in an intelligible way MUST point to an SDSS Softpage.

This is the list of default SDSS Softpages with the siteDirector 4.2 Softpages they replace:

SDSS Softpage Name Replaces sD 4.2 Frame Softpage
securej_Doc_Frame_Pg42.htm Doc_Frame_Pg42.htm
securej_Browse_Frame_Pg42.htm Browse_Frame_Pg42.htm
securej_All_Frame_Pg42.htm All_Frame_Pg42.htm
securej_Search_Frame_Pg42.htm Search_Frame_Pg42.htm
securej_Toc_Frame_Pg42.htm Toc_Frame_Pg42.htm
securej_Document42.htm Document42.htm
securej_ref_BrowseView42.htm ref_BrowseView42.htm
securej_ref_SearchView42.htm ref_SearchView42.htm
securej_ref_MainView42.htm ref_MainView42.htm
securej_Login.htm Does not replace any page.  This is NOT a softpage.  It is an HTML page you need to place in a directory where it can be read by your HTTPD server and freely accessed over the Internet..  Be sure to rename  it to anything you please.  Do not tell others what the name is, or where it is located.  You will, however,  need to put the URL to this page in the Subscription Record Login URL.   Please check and double check that you can reach this page over the Internet before entering the URL into the Subscription Record.  Failure to do so may result in major login problems for your end-users.

IMPORTANT: If you use a "Frame" page which is not on the list above, you must either replace it with an SDSS Softpage which is on the list, or SDSS must be updated to display your page.  SDSS can NOT secure sD Frame Softpages it does not know about.   We charge $25 per Softpage for customizations.

To download the SDSS Softpages:

  1. Log into the SDSS Client website at: http://dns.scbbs.com/~client
  2. From the Client Top Menu you will see an option to "Download SDSS Softpages".  Select this option. 
  3. You will see a link to download the SDSS Softpages.  Right click on this link and select "Save As" option to download the following file to your computer: SECUREJ.EXE.  This is a self-extracting PKzipped archive of the default SDSS Softpages listed above. 
  4. Once downloaded, simply "run SECUREJ.EXE" and you will be prompted for the directory to store the archived files.  Select your siteDirector Softpages subdirectory.  It should extract at a minimum the files you see on the list above.   If any file from that list is missing, please contact the SDSS System Administrator immediately.

To install the SDSS Softpages.  Essentially, you want to use the SDSS Softpages where you would normally use the sD Softpages.  The following assumes you are replacing the sD default Softpages listed above.  After successful completion of the following, URL requests using the default sD Softpage names will now use the SDSS Softpages (i.e., an sD URL request to an infobase using "softpage=Doc_Frame_Pg42.htm" will now execute "securej_Doc_Frame_Pg42.htm"):

  1. Log into your siteDirector configuration program.
  2. Create a "Settings Group" called "SECUREJ".
  3. Drag the following default sD Softpages from "Default Configuration, Softpage Aliases" to "SECUREJ, Softpage Aliases":

    Doc_Frame_Pg42.htm
    Document42.htm
    Browse_Frame_Pg42.htm
    All_Frame_Pg42.htm
    Search_Frame_Pg42.htm
    Toc_Frame_Pg42.htm
    ref_BrowseView42.htm
    ref_SearchView42.htm
    ref_MainView42.htm

  4. In "SECUREJ, Softpage Aliases", edit the following Sofpages to point to new values:

    Doc_Frame_Pg42.htm -> securej_Doc_Frame_Pg42.htm
    Document42.htm -> securej_Document42.htm
    Browse_Frame_Pg42.htm -> securej_Browse_Frame_Pg42.htm
    All_Frame_Pg42.htm -> securej_All_Frame_Pg42.htm
    Search_Frame_Pg42.htm -> securej_Search_Frame_Pg42.htm
    Toc_Frame_Pg42.htm -> securej_Toc_Frame_Pg42.htm
    ref_BrowseView42.htm -> ref_BrowseView42.htm
    ref_SearchView42.htm -> ref_SearchView42.htm
    ref_MainView42.htm -> ref_MainView42.htm

    *Remember to create a new secret web page alias for securej_Login.htm.

  5. Add the "infobase alias" of each infobase you wish to secure to the SECUREJ settings group.

If any of the above is unclear in any way, please contact the SDSS System Administrator for assistance.  This is the most critical portion of the SDSS system.  It only needs to be done once, but if it's not done correctly you may experience quite a few problems down the road.

Important Note: Before you assign infobase aliases to the new SECUREJ settings group, you should first create the SDSS Infobase Record(s) for each alias to make sure they are not duplicated in SDSS.

Very Important Note: Please do not replace your Default Softpage Aliases for your siteDirector Site with SDSS Softpages.  You should only use SDSS Softpage aliases in settings groups, such as SECUREJ.

top

Provide shopping cart and online payment mechanism for shipped or downloaded information products.

For information products such as CD's, books and one-time file downloads, we provide a shopping cart mechanism integrated into our e-commerce system.  The shopping cart allows users to pick and choose items they wish to purchase for shipping or download, and calculates a final total for an itemized credit card purchase.  Upon successful authorization of the credit card, the user is given immediate download access or notified of intent to ship the items ordered.  You, our client, are sent a copy of the receipt as well as either a notice to ship requested items or notification of file(s) downloaded.

Access to the shopping cart  requires an SDSS Subscription for at least one Subscription Record, even if you do not intend to offer infobase or file download subscriptions.

The difference between a File Download Subscription and a File Download Purchase using the shopping cart is as follows:  A File Download Subscription gives end-users access to a file over a period of time.   It is intended as a mechanism for delivering updates to infobase or other software products on an on-going basis.  A File Download Purchase via the shopping cart is intended as a one-time purchase of the file in question.

Shopping Cart Getting Started: The process for using the SDSS Shopping Cart   for your shipped or downloaded products:

  1. Sign up for an SDSS Client Account at our website: http://www.scbbs.com/sdss.html.  This will give you an administrative "Client"  login username/password, and a "Source" code used to maintain your company-specific information.  If you only intend to use the shopping cart, you can use the default number of   "Subscriptions" and "Infobases".  Yes, we know you don't need them, but this is a requirement for access to the cart. 
  2. Log into the SDSS Client website at: http://dns.scbbs.com/~client and define your Subproduct Record(s) (SUBPRODUCT).  The Subproduct Record describes the item you are selling.  The Subproduct Record consists of: the name of the physical file to be downloaded if this is a download product, the title of the product, a description of the product, the currency (always "usd" for now), the price, the main product code (we will give you this), the URL which contains detailed info on the product, the size of the file if it is a download product, the shipping type (ship or download), shipping weight per unit for US, Canada and outside US and Canada, and the source code (this is assigned to you when you sign up as an SDSS Client).  If you need to calculate shipping, you will need to create a Shipping Table.  If you need to calculate taxes, you will need to create a Tax Table.
  3. If you are selling file downloads, you need to e-mail the administrator sysop@scbbs.com to advise of such.  The administrator will let you know the ftp site where you should upload your files.  The administrator will also give you the information necessary to enter the download file information into the File Download table.  ALL SDSS controlled file downloads must be defined in the File Download table.  Successful file download purchases  notify the end-user at the time of purchase of the location of the file and how long it can be downloaded from that location (normally 24 hours).
  4. The URL to point to items in the shopping cart from your website is as follows:  http://dns.scbbs.com/client-cgi-bin/cart.pl?<source code>+<subproduct code>+<product code>+<shipping type>.   So, for example, if your source code is: A1, and your subproduct code is: NA1003, and the product code is: NA, and the shipping type is "D" for download, then you would point to the following shopping cart entry:  http://dns.scbbs.com/client-cgi-bin/cart.pl?A1+NA1003+NA+D

That's it.  Once the files are uploaded to the correct directory, the Subproduct Record entries created, and the appropriate links added to your website, you are online and ready to go.

Again, remember that the system is e-commerce ready as soon as you enter your Subproduct information.  It will use our merchant account (at a fee of 25% per transaction) until we have set it up to use your merchant account.

top

Configure and maintain, online via browser, all service information

Whether you select infobase subscriptions, download subscriptions and/or shopping cart, you can completely control the operation of your SDSS application with a simple web browser.

Once you have purchased an SDSS Client Account, all service information maintenance options can be accessed by logging in at: http://dns.scbbs.com/~client

Once logged in, you will see the "Client Top Menu" which will display the following options:

Customer Maintenance

Options:

Here is where you can see Customer Transaction, Accounts Payable  and Product Code records.  You also enter SubProduct Records  here for the items you wish to sell with the shopping cart.

SD Security Maintenance

Options:

Here is where you maintain Subscription, Infobase and File Download records.  You can also maintain your sD Customer (end-user) records here as well as view the sD Customer Log to see who is logged in.  sD Customer Accounts are created to allow end-users to access subscription services you have set up.  In Paid, Free and Download subscriptions, sD Customer Accounts are created on the fly.  With Private subscriptions, they have to be created manually.  However, you can create/update/delete sD Customer Account records at any time for any subscription service under your Client Source Code.   Also, you can use the option to "add" an sD Customer Log record to "login" an sD Customer Account, or create a perpetually logged in account (by IP number).

sdss3.gif (1991 bytes)

Source Record Maintenance

Here you maintain basic information on your Client Account such as name, address, phone, etc...  You also indicate here the name and phone of the contact person to appear on subscription/shopping cart CC order pages.

The only option is the Source Record.

top

Generate comprehensive reports, online via browser, on all service activity.

Once you have purchased an SDSS Client Account, all service information maintenance options can be accessed by logging in at: http://dns.scbbs.com/~client

You can list on your browser screen, all Customer Transactions, SubProducts, AP Records, Subscription Records, Infobase Records, sD Customer Log Records and sD Customer Account Records which are tied to your Client  Source Code.  The Customer Transaction and AP Record online listings also display total amounts.  The "Subscription" display also gives you an option to create a download file in Standard Data Format (SDF) of all customers signed up for the subscription.  However, SDSS has one of the most powerful database query tools available:

SD SQL Query

From the SD SQL Query screen, you can submit SQL queries to the following database files ("tables"):

  1. Customer Transaction (CUSTOMER)
  2. sD Access Log (SDLOG)
  3. Accounts Payable (AP)
  4. sD Customer (SDCUST)
  5. Shipping Table (SHIPPING)
  6. Tax Table (TAXES)
  7. Purchase Order Table (PO)
  8. sD Customer Login Log (SDCUSTLOG)

You can optionally select the results of your query to be displayed to your screen, or stored in a SDF (Standard Data Format) file which you can download to your computer.   The Standard Data Format is ASCII, comma delimited fields contained within quotation marks with each line terminated by a carriage return/line feed pair.

For example, let's say we have a database file (or "table") called: NAMES.   Let's say further that the table contains three fields (or "columns"): NAMES_NAME, NAMES_PHONE, NAMES_FAX.  You can enter the SQL query: "SELECT * FROM NAMES".  If you select your output to "Download", a file will be created with SDF record lines resulting from this query of all records and all fields from NAMES.  The file would would look like this:

"name1", "phone1", "fax1"
"name2", "phone2", "fax3"
"name3", "phone3", "fax3"

If you do not know SQL, there are default queries set up for each file, which will by default print all records from the the past 30 days.  All you have to do is click on the selection you wish.  You can get to the SD SQL Query module from the Client Top Menu, which appears after logging in as a Client at: http://dns.scbbs.com/~client

siteDirector Access Log Record (SDLOG)

Log records are recorded automatically by SDSS each time a logged in user accesses a secured infobase. Log records are also created each time a user logs in and each time a change is made to a user account using SDSS Client Utilities. The sD Access Log cannot be updated manually. The only place you can access this log is from the "SD SQL Query" option from the "Client Top Menu".

Field Title Desc Type/
MaxSize
SQL Hint
SDLOG_IP IP Address IP address of user accessing infobase (ISP). char/15  
SDLOG_HOST Host Name Host name of computer user accessing infobase is logged into (ISP) char/60  
SDLOG_USERNAME Username sD Customer username. char/20  
SDLOG_SOURCECODE Source Code Client Source Account of subscription of infobase user is accessing. char/20  
SDLOG_QUERY Query This is the query portion of the URL returned by siteDirector.  Please note that this is NOT the string submitted by the user, but the string submitted by your sD server to SDSS.  This query contains all the sub-frame queries as well. If this is a login then this field contains the login query. char/900  
SDLOG_TIME Date/Time The date, in seconds, this log record was recorded. integer  
SDLOG_NFO Infobase The sD infobase alias of the infobase being accessed. char/20  
SDLOG_SUBCODE Subscription Code The subscription code of the subscription for the infobase being accessed. char/10  
SDLOG_LOGIN Login (Y/N)? Is this an SDSS login record? 'Y' for yes. 'N' for no. '0' for failed login (not yet implemented). Also: U = Account Update (such as Changed Username or Custom Subscription Created / Updated) char/1  

SD Security Maintenance

Subscription Record (SDSUB)

This record is used to define an infobase or file download description.  If this is an Infobase Subscription, you must also define an Infobase Record.  If this is a File Download subscription, or an Infobase Subscription which contains file downloads, you must define a File Download Record for each file to be downloaded.

Once a subscription is set up, end-users can be pointed to the Subscription Login screen using this URL:

http://dns.scbbs.com/client-cgi-bin/secure_login.pl?<source code>+<subscription code>
Ex: http://dns.scbbs.com/client-cgi-bin/secure_login.pl?A1+O1006

To purchase/signup for the subscription, please point users to:

http://dns.scbbs.com/client-cgi-bin/secureord.pl?<source code>+<subscription code>
Ex: http://dns.scbbs.com/client-cgi-bin/secureord.pl?A1+O1006

SDSS has a mechanism to e-mail the username and password to users who have fogotten them.  This URL is:

http://dns.scbbs.com/client-cgi-bin/secureord.pl?<source code>+<subscription code>+lost
Ex: http://dns.scbbs.com/client-cgi-bin/secureord.pl?A1+O1006+lost

The "MaxSize" is the maximum number of characters you can enter for the field.  Please refrain from entering single or double quotation marks (""", "'") in any fields, except for single quotation marks in SQL query character fields.

Field Title Desc Type/
MaxSize
SQL Hint
SDSUB_CODE Subscription Code Automatically assigned. char/10  
SDSUB_TITLE Subscription Title Title for subscription. char/200  
SDSUB_DESC Subscription Description Description for subscription. char/200  
SDSUB_DESCURL Subscription Description URL URL to page which contains detailed information on the description. char/100  
SDSUB_SOURCECODE Royalty (Source) Code Your (or one for which you are authorized) Client Source Code.  This is also the Source to which royalties are paid if the Source Account company does not have a merchant account. char/10  
SDSUB_CURRENCY Currency Currently this should always be "usd" for US Dollars.  Always 3 characters, lower case. char/5  
SDSUB_HOURLY Hourly Subscription Rate Enter "0" if not applicable. numeric  
SDSUB_DAILY Daily Subscription Rate Enter "0" if not applicable. numeric  
SDSUB_WEEKLY Weekly Subscripton Rate Enter "0" if not applicable. numeric  
SDSUB_MONTHLY Monthly Subscription Rate Enter "0" if not applicable. numeric  
SDSUB_ANNUAL Annual Subscription Rate Enter "0" if not applicable. numeric  
SDSUB_STARTURL Subscription Start URL This is the URL to the page that a user is sent to once he/she successfully logs into this subscription.  This is the start point for either infobase or file download access.   When the user logs in, this is the page you want to come up on his browser after the login process has completed.  If it is a Download subscription, this page should probably be the index of all the files the user can download.  If it is an Infobase subscription, then this page should probably be the directory of infobases the user can access, or the first infobase the user should access. Be sure to test this URL to make sure you can get to it. char/100  
SDSUB_LOGINURL Subscription Login URL This is the URL to the "securej_Login.htm" page you received. This is NOT an sD Softpage, but rather an HTML page you should install on your HTTPD server where it can be accessed freely over the Internet.You should give this page an unusual alias because this page is used to temporarily "login" users with a cookie.   Place the URL to this page here.   Do NOT tell others the name of this page or where it is located.  Be sure to test this URL to make sure you can get to it. char/100  
SDSUB_TYPE Subscription Type "P" if signup requires payment.  "F" if signup is free.   "N" if no signup available (Private).  "D" if signup is for File Download Subscription. If File Download Subscription, files which are accessed via this subscription must be defined in the FILES table. char/1  
SDSUB_EXPIRETIME Subscription  Length If this is an "F" type, enter the amount of time, in seconds, before the subscription should expire (and the Customer Account deleted). integer  
SDSUB_LOGIN Subscription Login Time Amount of time, in seconds, a user can stay logged in during one session. integer  
SDSUB_MESSAGE Subscription Message Message sent to new signups. char/900  
SDSUB_DLDIR Download Files (Y/N) If this is not a File Download subscription, but contains links to files which should only be accessed if someone is logged into this subscription, then enter "Y" here.  Files which are accessed via this subscription must be defined in the FILES table. char/1  
SDSUB_DEPENDENT Subscription Signup Dependent (Y/N)? Is signup for this subscription dependent upon user being logged into another subscription (Y/N)? Enter 'Y' or 'N'. This allows for a control of free signups. In order to sign up, user must first be logged into another 'control' subscription. char/1  
SDSUB_DEPENDENT_SUBCODE Subscription Signup Dependent upon what Subscription Code If the answer to SDSUB_DEPENDENT is Y, then place here the Subscription Code ('control' subscription) of the Subscription user must be logged into before user can signup for this subscription. char/10  
SDSUB_SP1 Replace Softpage Alias (Y/N)? If you wish to replace a softpage alias which normally comes up for an infobase in this subscription, enter 'Y'. If you enter 'Y', you will need to enter the name of the name of the softpage alias to replace, and the name of the alias which will replace it. char/1  
SDSUB_SPSRC1 Source Softpage Alias (to replace) If the answer to SDSUB_SP1 is Y, then place here the name of the softpage alias you wish to replace when the infobase screen is drawn by SDSS. You must enter here the name of a valid softpage alias as it appears in SDSS. char/20  
SDSUB_SPDST1 Destination Softpage Alias (replacement) If the answer to SDSUB_SP1 is Y, then place here the name of the softpage alias which is replacing the softpage alias in SDSUB_SPSRC1. When the infobase screen is drawn by SDSS, the softpage alias entered here will be used instead of the one normally used which you identified in SDSUB_SRC1. You must enter here the name of a valid softpage alias as it appears in SDSS. char/20  
SDSUB_SUBEXPIRE Subscription Expires (Y/N) If this subscription record is to expire, enter "Y" here, otherwise, enter "N" here. If you enter "Y" here, then this record will be deleted after the date entered below in "SDSUB_SUBEXPIRETIME". char/1  
SDSUB_SUBEXPIRETIME Subscription Expiration Date Date (time), in seconds, when this record will expire. Only valid if "Y" is entered above in SDSUB_SUBEXPIRE". integer  
SDSUB_EXPNOTICE Subscription Expiration Notice Code Expiration Notice Code (EXP_CODE) from EXPNOTICES table.  This code determines the message and frequency of expiration notices sent for this subscription. char/5  

SD Security Maintenance

Infobase Record (SDNFO)

This record is used to define what infobases are to be secured by SDSS, and what subscriptions they belong to.  Remember that the name here always refers to the infobase "alias" as defined in your siteDirector implementation, and not the actual physical infobase filename.

The "MaxSize" is the maximum number of characters you can enter for the field.  Please refrain from entering single or double quotation marks (""", "'") in any fields, except for single quotation marks in SQL query character fields.

Field Title Desc Type/
MaxSize
SQL Hint
SDNFO_NAME Infobase Alias The infobase alias for the infobase.  This is the name used in the "infobase=" section of the siteDirector request URL for the infobase. This alias must be unique to SDSS, so if someone else is using this alias name, you must select another (SDSS will advise you of such if you attempt to insert an infobase alias name which already exists).

If this is a "Folio Infobase" and this infobase needs to belong to more than one Subscription Record, then you should have a unique infobase alias for each additional subscription it will be a part of.  The same alias can only be used in ONE Folio Infobase subscription at a time.  Other content types can belong to multiple Subscription Records, which are identified in the Infobase Subscription table.

char/20  
SDNFO_TITLE Infobase Title Title for the Infobase. char/200  
SDNFO_DESC Infobase Description Brief description of contents of infobase. char/200  
SDNFO_SUBCODE Infobase Subscription Code Code of Subscription Record for subscription this infobase belongs to.  This is used for "Folio Infobases".  Other content types utilize the Infobase Subscription table to determine what Subscription(s) they belong to. char/10  
SDNFO_SP1 Replace Softpage Alias (Y/N)? If you wish to replace a softpage alias which normally comes up for this infobase, enter 'Y'. If you enter 'Y', you will need to enter the name of the name of the softpage alias to replace, and the name of the alias which will replace it. char/1  
SDNFO_SPSRC1 Source Softpage Alias (to replace) If the answer to SDNFO_SP1 is Y, then place here the name of the softpage alias you wish to replace when the infobase screen is drawn by SDSS. You must enter here the name of a valid softpage alias as it appears in SDSS. char/20  
SDNFO_SPDST1 Destination Softpage Alias (replacement) If the answer to SDNFO_SP1 is Y, then place here the name of the softpage alias which is replacing the softpage alias in SDNFO_SPSRC1. When the infobase screen is drawn by SDSS, the softpage alias entered here will be used instead of the one normally used which you identified in SDNFO_SRC1. You must enter here the name of a valid softpage alias as it appears in SDSS. char/20  

Infobase Subscription Record (SDNFOSUB)

This record is used to define what Subscription Records a particular Infobase Record belongs to.  Note that "Folio Infobases" Infobase Records can only belong to one subscription identified in the SDNFO_NAME field of the Infobase Record, but other content types can belong to multiple Subscription Records, and those Subscriptions are identified in this table.

The "MaxSize" is the maximum number of characters you can enter for the field.  Please refrain from entering single or double quotation marks (""", "'") in any fields, except for single quotation marks in SQL query character fields.

Field Title Desc Type/
MaxSize
SQL Hint
SDNSUB_NAME Infobase Subscription Alias The infobase alias (name) for the Infobase Record.   char/20  
SDNSUB_SUBCODE Infobase Subscription Code Code of Subscription Record this infobase belongs to.  char/10  

 

SD Security Maintenance

SD Customer Log (SDCUSTLOG)

The sD Customer Log records each end-user login.  When the login period has expired, the log record is deleted.  Generally, the records you see in this log at any particular time reflect users who are actually logged in.  The only exception to this are users you have logged in or for whom you have created a "IP Recognition" login.  A "IP Recognition" login is a Customer Log record created with an extended expiration time and designed to allow a user or group of users from an IP or IP range to be logged in automatically.  For example, if you wish to allow an end-user to access your SDSS protected content at any time without logging in, you would create a Customer Log record with that end-user's IP address, and give it an expiration time way into the future (like 6 months or a year or more).  This user's accesses would still be recorded in the siteDirector Access Log (SDLOG), but the user would not have to log in to access secured SDSS protected content such as infobases or file downloads.

In addition to single IPs, you can also enter IP networks or ranges.

If this is an IP Recognition record, you must enter "Y" into the "Auto-Recognize" SDCLOG_RECOGNIZE field, meaning you wish this IP to be automatically recognized and logged in using the SDSS Customer name in the "SDCLOG_USERNAME" field. field.

If this is an SDSS Verification Server IP Record, please refer to the SDSS Verification Server Process help file "Customer Log (SDCUSTLOG) IP Record" for setup instructions.

The "MaxSize" is the maximum number of characters you can enter for the field.  Please refrain from entering single or double quotation marks (""", "'") in any fields, except for single quotation marks in SQL query character fields.

Field Title Desc Type/
MaxSize
SQL Hint
SDCLOG_IP Log IP Address The IP address of the user logged in.  

For IP Recognition, to accommodate login for an entire network, please use network IP terminated by "*".  For example, "199.182.110.*".  To accommodate logins for an IP range, use "-".  For example: "199.182.110.0-255" or "199.182.110-112.*".  If you want this IP or network or range automatically recognized for login, don't forget to enter "Y" into "Auto-Recognize" field below.  

If this is an SDSS Verification Server IP Record, then you enter the IP of your Web Server (the one which will contact the SDSS Verification Server) here.  IP networks and ranges are NOT accepted for SDSS Verification Server records.

char/35  
SDCLOG_USERNAME Log Username The sD Customer Account record username of the user logged in.

If this is an SDSS Verification Server IP Record, enter the Customer (SDCUST) record to be used for the this Verification Server IP record. The username of this customer record must be the same as the name of the SOURCE (CLIENT).  Instructions for this setup are found in the SDSS Verification Server Process help file.  The calling Web Server cannot access the SDSS Verification Server if the username entered here is not correct.

char/20  
SDCLOG_EXPIRETIME Log Expiration Date Date (time), in seconds, when this record will expire.

If this is an SDSS Verification Server IP Record, note that when it expires, the Web Server at this IP will no longer be able to use the Verification Server from this IP address.

 

integer  
SDCLOG_SUBCODE Log Subscription Code Code of Subscription Record for subscription that user is logged in for.  

If this is an SDSS Verification Server IP Record, it doesn't matter what is entered here, but it should be a valid Subcription Code.

char/10  
SDCLOG_SOURCECODE Log Source Code Client Source Code for subscription user is logged in for.  This will typically be yours or one for which you have authorization.  

If this is an SDSS Verification Server IP Record, this must be Source Code of Client who is making requests to the Verification Server.  Every request to Verification Server MUST include Source Code.

char/10  
SDCLOG_RECOGNIZE Log Auto-Recognize (Y/N/V) Client Auto-Recognize IP address. Enter "Y" if you want the IP address automatically recognized and logged in for access. Enter "N" if not. If "Y", the username entered in SDCLOG_USERNAME must be a valid SDCUST account for the subscription the user from this IP or network or range is attempting to access.  

If this is an SDSS Verification Server IP Record, then you enter "V" here.

char/1  

SD Security Maintenance

SD Customers (SDCUST)  

sD Customers are end-users who have signed up for one or more subscriptions.  For simplicity's sake, we include File Download Subscriptions in this file as well.  Note: Please do not confuse the sD Customer file with the Customer Transaction (CUSTOMER) file.  The sD Customer Record is created, generally, by the end-user subscribing to a subscription service.  If the end-user pays for access, that transaction is recorded in the Customer Transaction (CUSTOMER) file.  Only the end-user subscription signup information is recorded here.

You may create sD Customer Records manually.  Generally, if your subscription type is "Private", you may pre-generate customer records to assign manually.   You may also want to create demonstration account records, or accounts that you may want to give to end-users without them having to sign up.  Finally, you may also wish to edit information in an account -- in particular the expiration date.

Click here to see the Subscription Login URL (also URL for obtaining lost/forgotten password).

The "MaxSize" is the maximum number of characters you can enter for the field.  Please refrain from entering single or double quotation marks (""", "'") in any fields, except for single quotation marks in SQL query character fields.

Field Title Desc Type/
MaxSize
SQL Hint
SDCUST_ORDERID OrderID If the subscription this record is being created for is type "P" (Paid) or "D" (Download), then the "Order ID" will be the Customer Transaction Record (CUSTOMER) Order ID

If this record is for an "F" (Free) subscription type, then the Order ID will be the Source Code followed by a period "." and the Username (i.e., "A1.username").  Note: If you create sD Customer Records manually, we request that you enter the Order ID this manner.

char/15  
SDCUST_EMAIL Email E-mail address. char/60  
SDCUST_EXPIRETIME Expiration Date Date this customer record is due to expire, in seconds.  Expiration notices are automatically sent out at the following number of days prior to this date: 15 days, 7 days, 3 days and 1 day. integer  
SDCUST_USERNAME Username Login username.  No spaces or other punctuation, please. char/20  
SDCUST_PASSWORD Password Login password.  No spaces or other puctuation, please. char/20  
SDCUST_SUBCODE Subscription Code Subscription Record code of subscription this customer account will have access to. char/10  
SDCUST_SOURCECODE Source Code Client Source Account record code. This will come from the Subscription Record char/10  
SDCUST_NAME Name Name of the end-user. char/50  
SDCUST_COMPANY Company End-user's company name. char/50  
SDCUST_TITLE Title End-user's job title. char/50  
SDCUST_ADDRESS Address End-user's street address. char/50  
SDCUST_CITY City End-user's city. char/50  
SDCUST_STATE State End-user's state or province. char/30  
SDCUST_ZIP Zip End-user's zip or postal code. char/20  
SDCUST_COUNTRY Country End-user's country. char/50  
SDCUST_PHONE Phone End-user's phone number. char/20  
SDCUST_FAX Fax End-user's fax number. char/20  
SDCUST_INDUSTRY Industry If subscription type "F" only: End-user's selected industry.  This is from pulldown menu. char/50  
SDCUST_OTHER Industry Other If subscription type "F"only: If user selects "other" from industry pulldown menu, then enter here name of other industry. char/20  
SDCUST_RECEIVE Receive Info If subscription type "F" only: If user checks box to "Receive Information" from you. char/3  
SDCUST_INPUTDATE Date Input The date, in seconds, this account was created. integer  
SDCUST_SUSPEND Suspend Suspend this account?  Enter "Y" or "N".  This will prevent end-user from logging in with this accout without actually deleting it. char/1  
SDCUST_LOGINALL Log Into All Subscriptions Log this account into all subscriptions it has access to?  Enter "Y" or "N".  This will log end-user into all Subscriptions when he logs into one. This is "N" by default. char/1  
SDCUST_CHANGEPW View Customer Account Allow this this account to log into the View Customer Account Screen?  Enter "Y" or "N".  This will allow end-user to access the View Customer Account Screen upon login. Here, the customer can change certain information in this account, including the password. This is "Y" by default. char/1  
SDCUST_COMMENTS Additional Comments.    

SD Security Maintenance

SD File Download (FILES)

SDSS has the ability to control access to files outside of Infobases.  These can be graphic files, text files, HTML pages, PDF files or program files.  All file downloads, whether for File Download Subscription or Infobase Subscription or Shopping Cart purchases must be defined in the File Download Table here.  

Once the file is entered, you will see a button to add subscriptions to it at the bottom of the page.  You must add all subscription(s) that this file belongs to.  If you do not, people who purchase the subscriptions will not be able to see or download the files.

If the file will ONLY be downloaded via Shopping Cart purchase, then it is not necessary to add a subscription to it.

Please note that if the file is part of an infobase subscription, but it is not important that people can access it outside of the subscription, then it is not necessary to define it here.  This database is only for files which you want secured by subscription login or purchase.  And, the file "hostpath" is the only way to get to SDSS-defined files.

The "MaxSize" is the maximum number of characters you can enter for the field.  Please refrain from entering single or double quotation marks (""", "'") in any fields, except for single quotation marks in SQL query character fields.

Field Title Desc Type/
MaxSize
SQL Hint
FILE_FILENAME File Name The name of the file or eBook identifier.  This file name serves as a key name for the file in the SDSS File Database.  It can be the actual name of the file, or a name used to reference the file in links you will create to it.  The actual file name is entered in the File Path.  

If this is an eBook, then enter the identifier code here. 

No spaces or slash characters allowed.

char/25  
FILE_SOURCE Source Code Client Source Code for subscription user is logged in for.  This will typically be yours or one for which you have authorization. char/10  
FILE_CONTENTTYPE Content Type The MIME Content Type for the file to be downloaded. For example, ZIP files are stored as "application/x-zip".  EXE files as "application/octet-stream".  You will be presented with a list:

(application/msword) .doc
(application/octet-stream) .exe
(image/gif) .gif
(text/html) .html
(text/xml) .xml
(image/jpeg) .jpg
(application/pdf) .pdf
(application/x-mspowerpoint) .ppt
(image/tif) .tif
(text/plain) .txt
(application/x-msexcel) .xls
(application/x-zip-compressed) .zip
(video/quicktime) .mov
(audio/x-pn-realaudio) .rm

char/50  
FILE_PATH File Path The path to the file on the computer.  This is physically where the file is located on the computer's file system.  For example, "c:\downloadfiles\file.ext" (Windows) or "/home/downloadfiles/file.ext" (Unix).  The path MUST include the file name.  Your SDSS Administrator will provide you with this information.  Please note that if this path is incorrect or off by one character, SDSS will not be able to locate the file.  

Also note that if you answer "Y" to "FILE_REMOTE", then the file path you enter here must reflect where the file is located on the server identified in "FILE_REMOTEPATH".  If you enter "N" to "FILE_REMOTE", or leave it blank, then the path you enter here must reflect where the file is located on the server identified in "FILE_HOSTPATH".

If this is an eBook, then enter the eBook identifier type here; i.e., "ISBN", "SKU", etc...

char/80  
FILE_TEXTFILE Text File This is the URL to a Web page (SDSS secured or anywhere on the Internet) which can be displayed to list detailed information on this file. char/100  
FILE_TYPE File Type SDSS file type: D = download file, H = HTML, T = description text, I = image, E = eBook. char/10  
FILE_TITLE File Title Brief title for the file. char/80  
FILE_DESCRIPTION File Description Brief description of the file. char/200  
FILE_REMOTE File Remote File Server Is this file located on a remote server (i.e., a server other than the one identified in "FILE_HOSTPATH")?  Enter "Y" or "N".

If this is an eBook, then enter "Y" here.

char/1  
FILE_REMOTEPATH File URL to Remote Server/Servlet If you answered "Y" to "FILE_REMOTE", then enter here the URL to the server/servlet which will serve this file.  For example: "http://test.scbbs.com/servlet/sdssFileServer".  Note that the path to the file identified in "FILE_PATH" must reflect where the file is located on THIS ("FILE_REMOTEPATH") server (as opposed to server identified in "FILE_HOSTPATH").  Also note that the IP for this server MUST be entered into SDCUSTLOG as an SDSS Verification Server IP Record as per SDSS Verification Server Process instructions (see #5, "Customer Log IP Record).  The reason for this is because this server must access the SDSS Verification Server to verify that the user has access to the file he is attempting to view.

If this is an eBook, enter the URL to the sdssEBookServer servlet here.  For example: "http://test.scbbs.com/servlet/sdssEBookServer"

char/100  
FILE_HOSTPATH File Hostpath URL used to get to the file once secured by SDSS.  Your SDSS administrator will give you the root path to use.  This URL will use the File Name entered in this record.  Example: "http://client.scbbs.com/servlets/sdssfile/filename.ext".  The "Hostpath" is the only way for end-user's to access this file.  If this URL is incorrect or off by one character, SDSS will not be able to provide the file to the end-user.  Note that even though the file may be physically located on and served by server identified in "FILE_REMOTEPATH", the entry here MUST be the URL used by the end user to access the file once successfully logged in. char/100  

 

 

FILESUB Table  

This table determines what Subscriptions each file belongs to.  This is maintained under SD Download Files (File Maintenance) in SD Security Maintenance).

Field Title Desc Type/
MaxSize
SQL Hint
FILESUB_FILENAME Filename Name of the file as stored in the FILES table. char/25  
FILESUB_SOURCE Source Code Code of SDSS Client. char/10  
FILESUB_SUBCODE Subscription Code Subscription Code that this file belongs to. char/10  

SD Security Maintenance

SD Referer (REFERER)

SDSS has the ability to allow automatic logins to subscritions based upon the referer URL -- that is, based upon the URL which refers the login link.  In order to have automatic logins from a referer URL, you must have the following:

  1. A referer page which contains a link to secure_login.pl.  The link must be constructed as follows:

    secure_login.pl?feed_action=loginr&subscription_code=<code>

    So, in order to automatically log in a user who is referred from this referer page into subscription code O1021, your link would be constructed as follows:

    <a href="http://dns.scbbs.com/client-cgi-bin/secure_login.pl?feed_action=loginr&subscription_code=O1021">Your text here</a>

    This file name of this referer page should be created in lower case letters ONLY.  Ex: thispage.html and NOT ThisPage.html.
  2. The exact URL of the referer page above (Step #1) entered into the Referer File section of  the SDSS Security Maintenance module. This is the URL entered into a browser to get to the page which contains the referer login links. For example:

    http://www.testsite.com/thispage.html

    The URL should be entered into the Referer File along with the SD Customer Login Username (SDCUST_USERNAME) to be used for the subscriptions to be accessed, the Source Code of the SDSS Client under which the username is a customer, and a default Subscription Code to be accessed from the referer (the actual subscription code to be accessed is sent in the referer link to secure_login.pl).

Once the referer page is created, and its URL entered into the referer file, users who follow login links from this referer URL are automatically logged into the subscriptions identified in the links.

Please note that the referer link can only log in users using the username identified for the referer URL in the Referer File.  So, any subscription that you wish to log a user into from the referer URL MUST be attached to the SD Customer Login Username inserted into the Referer File record for this URL..  If you do not do this, the automatic login will fail for any subscription that is not attached to the Referer File Username used for this particular URL.

The "MaxSize" is the maximum number of characters you can enter for the field.  Please refrain from entering single or double quotation marks (""", "'") in any fields, except for single quotation marks in SQL query character fields.

Field Title Desc Type/
MaxSize
SQL Hint
REFERER_URL Referer URL  The URL of the referer.  Must be entered in all lower caps and spelled exactly as it is entered into a browser.  Ex: "http://www.refererurl.com/referer.html". char/125  
REFERER_USERNAME SDCUST Username Login username, SDCUST_USERNAME, from SDCUST SD Customers file.  No spaces or other punctuation, please.  Only one username per unique URL. char/20  
REFERER_SUBCODE Default Subscription Code This is the default subscription code to use for this referer URL.  The actual subscription code is supplied in the referer link to secure_login.pl. char/10  
REFERER_SOURCE Source Code SDSS Client Source Code for this referer URL. char/10  

SD Security Maintenance

Customer Maintenance

Customer Record (CUSTOMER)

This file contains the Customer Credit Card Transaction information.  All CC transactions processed through SDSS, regardless of whose merchant account is used, are recorded here.  Currently, SDSS only stores successful CC transactions.

Customer Records can only be created as a result of Credit Card transactions.    They can only be updated by the SDSS System Administrator.  You may only view transactions under your Source Code authorization.

Field Title Desc Type/
MaxSize
SQL Hint
CUST_ORDERID Cust OrderID The "Order ID" is the number used to identify each particular CC transaction char/15  
CUST_PRODUCT Main Product Code The Product Code or SubProduct Code for the item purchased with this transaction char/10  
CUST_EMAIL EMail Email address supplied by individual making this purchase. char/60  
CUST_CUSTTXN Transaction Number The number returned by our processor (CyberCash) for this transaction char/20  
CUST_DATE Order Date The date, in seconds, that this transaction took place. integer  
CUST_EXPIRETIME Expiration Date The date, in seconds, that the subscription purchased by this transaction will expire.   If it is a file download purchase, it is normally 24 hours after the order date.   For shipped products, the date here is usually the same as the order date. integer  
CUST_AMT Amount Amount of the transaction, preceeded by monetary code (i.e., "usd").   Because it contains "usd" it is NOT a numeric field. char/20 Note that this is NOT a numeric field.
CUST_NAME Billing Name Name on credit card. char/50  
CUST_COMPANY Billing Company Company on credit card. char/50  
CUST_ADDR Billing Address Street address on credit card. char/50  
CUST_CITY Billing City City on credit card. char/50  
CUST_STATE Billing State State/Province on credit card. char/50  
CUST_ZIP Billing Zip Zip/Postal Code on credit card. char/20  
CUST_COUNTRY Billing Country Country on credit card. char/50  
CUST_PHONE Phone Number Contact phone number. char/20  
CUST_FAX Fax Number Contact fax number. char/20  
CUST_URL URL Contact URL (for company) char/80  
CUST_MT_NAME ShipTo Name Name of individual to receive purchased item(s). char/50  
CUST_MT_COMPANY ShipTo Company Company to receive purchased item(s). char/50  
CUST_MT_ADDR ShipTo Address Address of company to receive purchased item(s). char/50  
CUST_MT_CITY ShipTo City City of company to receive purchased item(s). char/50  
CUST_MT_STATE ShipTo State State/Province of company to receive purchased item(s). char/50  
CUST_MT_ZIP ShipTo Zip Zip/Postal Code of company to receive purchased item(s). char/20  
CUST_MT_COUNTRY ShipTo Country Country of company to receive purchased item(s). char/50  
CUST_REMOTE_HOST Remote Host Name Name of the host computer identified in this user's browser. char/60  
CUST_REMOTE_ADDR Remote  Host Address IP address of host computer identified in this user's browser. char/15  
CUST_AVSCODE AVS Code Address Verification Code returned by our processor. char/10  
CUST_CARDTYPE Card Type Type of credit card used if credit card transaction.  Use "PO" if Purchase Order transaction. char/10  
CUST_SOURCE Source Code Client Source Code for item(s) purchased. char/10  
CUST_PRODUCT_DESC Product Description Description of the item(s) purchased. char/50  
CUST_AUXMSG Aux Message Auxiliary message sent by our processor.  Normally describes results of transaction. char/150  
CUST_MSTATUS Status Status of the transaction.  "success" is good.   "failure" is not. char/20  
CUST_MERRMSG Merchant Message Message returned by our processor for merchant.  Usually for failed transaction, indicating reason for decline. char/150  
CUST_CARDNUM Card Number The first 6 digits and last 4 of credit card. char/15  
CUST_COMMENTS Comments Comments entered by user. char/100  
CUST_ORDERAMT Order Amount Amount of order (not including currency code) numeric  
CUST_ORDERNET Net Amount Amount of ordered items (not including shipping or taxes) numeric  
CUST_SHIPPING Shipping Amout Shipping charged on this order. numeric  
CUST_TAXES Tax Amount Tax charged on this order. numeric  
CUST_PO Purchase Order Number PO Number for this order, if PO transaction. char/20  

Customer Maintenance

SubProduct Record (SUBPRODUCT)

You should speak to the SDSS Administrator before entering SubProduct Records.   You should know what Product Code to use, as well as file download information.

If you intend to sell products (shipped or downloaded) via the SDSS Shopping Cart, then you must define those products here.  Once the product is entered, you link to it for Cart access in the following manner: 

http://dns.scbbs.com/client-cgi-bin/cart.pl?<source code>+<subproduct code>+<product code>+<shipping type>
ex: http://dns.scbbs.com/client-cgi-bin/cart.pl?A1+NA1003+NA+D

The "shipping type" will either be "S" for shipped via mail or "D" for file download.

If you are selling file downloads, please make sure you have the correct file name defined here, and the correct download directory name defined in your Client Source Account Record.   You are also responsible for making sure the actual files are in the correct directory at the correct FTP site.  If you do not have this information, you should contact the SDSS System Administrator before making any products available for download.

The "MaxSize" is the maximum number of characters you can enter for the field.  Please refrain from entering single or double quotation marks (""", "'") in any fields, except for single quotation marks in SQL query character fields.

Field Title Desc Type/
MaxSize
SQL Hint
SP_CODE SubProduct Code This is entered by the you.  The prefix of this code "must" contain the main product code. char/30  
SP_FILE File Name Name of the physical file to be downloaded, if this is a "D" download type. char/20  
SP_TITLE Title Title of this product. char/60  
SP_DESC Description Brief description of this product. Please be precise.  char/300  
SP_CURRENCY Currency Currency code.  Enter "usd" for US Dollars.  This is the only currency currently recognized by SDSS. char/5  
SP_PRICE Price The price for this product as described in title and description.  numeric  
SP_CATEGORY Category (User-Defined) A code used to categorize this product. User-defined. Useful for sorting products by type.  char/10  
SP_NONXTDAY Disallow 2nd and Next Day Shipping? (Y/N) Use this field to prevent customer from selecting option to have item shipped overnight or by 2nd day air. In other words, this item can only be shipped by regular ground delivery.  char/1  
SP_PRODCODE Main Product Code The main product code from the PRODUCT file. char/10  
SP_INFOBASE Description URL URL which contains detailed description of this product.  There will be a link to this URL on the order page when a user selects this product. char/100  
SP_PHOTOFRONT Front View Image URL URL which contains front view image of product.  char/100  
SP_PHOTOSIDE Side View Image URL URL which contains side view image of product.  char/100  
SP_PHOTOREAR Rear View Image URL URL which contains rear view image of product.  char/100  
SP_TYPE Shipping Type Enter "D" if this is a file download.  Enter "S" if it is to be shipped via mail. char/1  
SP_SOURCE SubProduct Source Client Source for this SubProduct (you). char/10  
SP_FILESIZE File Size If file download, the approximate size of the file.  Example: ".5MB". char/10  
SP_SHIPUS Shipping Cost: US The weight of this item, in pounds, for shipping to any destination in the United States.  Please enter 0 here if this is not used. Do NOT enter "lbs" or other such adjectives. Just the weight number (1, 1.2, .3, etc...). numeric  
SP_SHIPCA Shipping Cost: Canada The weight of this item, in pounds, for shipping to any destination in Canada.  Please enter 0 here if this is not used. Do NOT enter "lbs" or other such adjectives. Just the weight number (1, 1.2, .3, etc...). numeric  
SP_SHIPOT Shipping Weight: Outside US and Canada The weight of this item, in pounds, for shipping to any destination outside the United States and Canada.   Please enter 0 here if this is not used. Do NOT enter "lbs" or other such adjectives. Just the weight number (1, 1.2, .3, etc...). numeric  

Customer Maintenance

Accounts Payable Record (AP)

Payments due to a particular Source Account as a result of SDSS credit card transactions are recorded in the AP file.  These records can only be created by credit card transactions.  They can only be updated by the SDSS System Administrator, who will normally update them to reflect payments made or cancelled.

Field Title Desc Type/
MaxSize
SQL Hint
AP_KEY Key This is generated automatically.  It is a combination of the OrderID and the Product/SubProduct Code char/50  
AP_ORDERID Order ID Order ID for the transaction this AP record is created from. char/30  
AP_SOURCE Source Code Client Source Account for the product/subscription purchased resulting in the transaction which creates this AP record. char/10  
AP_PRODUCT Product/SubProduct Code Product or SubProduct Code for item purchased.  If subscription, the Subscription Code is inserted. char/10  
AP_DATE Date Date this record was created. numeric  
AP_CURRENCY Currency Currency of transaction.  Currently always "usd". char/5  
AP_AMT Amount AP amount due. numeric  
AP_AMT_PAID Amount Paid Amount of AP amount due which is paid. numeric  
AP_PAY_DATE Pay Date Date, in seconds, the amount in "Amount Paid" field was paid. integer  
AP_CHECK_NO Check No. Check number for amount paid. char/10  
AP_AMT_CANCELLED Amount Cancelled Amount of AP amount due which is cancelled. numeric  
AP_CANCEL_DATE Cancel Date Date, in seconds, the amount in "Amount Cancelled" was cancelled. integer  
AP_NOTES Notes Notes on this transaction.    

Customer Maintenance

Product Record (PRODUCT)

This file lists all Product Codes which can be used.  Only the SDSS Administrator can add or update these records. 

Field Title Desc Type/
MaxSize
SQL Hint
PR_CODE Product Code The code for this product. char/10  
PR_TITLE Product Title The title for this product. char/30  
PR_DESC Product Description The description for this product. char/100  

Customer Maintenance

Shipping Record (SHIPPING)

If you are selling products via the Shopping Cart which require calculation of shipping charges, here is where you enter the shipping table.

When an end-user requests a "shipped" SUBPRODUCT from the Shopping Cart, the weight of the item is matched against this table.  If you make no entries to this table for your Source Code, no shipping is calculated.  If the weight of the item does not match any record configuration (combinarion of shipping destination, shipping method and shipping weight), then no shipping is calculated.

Currently, SDSS only calculates shipping against Subproduct items marked as "shipped".  It only handles three shipping regions: United States, Canada, and anywhere outside of the US and Canada.  And, it only provides for three shipping "types" or methods: Standard, 2nd Day Air, and Next Day.

Please note that the SHIP_EQUALTO column is the weight equal to value. The SHIP_LESSTHAN column is the weight less than. If we put "3" in the EQUALTO column and "4" in the LESSTHAN column, and we have an item which is 3 lbs or 3.1 lbs or 3.9 lbs, it would under

= (equal to) 3  and  (less than) < 4

Field Title Desc Type/
MaxSize
SQL Hint
SHIP_CODE Shipping Code The code for this shipping record.  It is automatically created by combining the SHIP_SOURCE, SHIP_REGION, SHIP_TYPE, AND SHIP_EQUALTO values. char/25  
SHIP_SOURCE Shipping Source Code The source code of the company this table is used for.  Any shipped product purchased using this source code will use this shipping table. char/10  
SHIP_REGION Shipping Region The destination region to which the product will be shipped.  This is one of the following: "us" (for United States), "ca" (for Canada) or "intl" (for Outside US and Canada). char/5  
SHIP_TYPE Shipping Type The shipping method.  There are only three options: "regular" (Standard), "2day" (Second Day Air) and "overnight" (Next Day). char/10  
SHIP_EQUALTO Shipping EqualTo Weight The equal to or greater than weight (in pounds) used to create a price record.   This will determine the minimal (equal to or greater than) weight for an item to qualify for this shipping price. numeric  
SHIP_LESSTHAN Shipping LessThan Weight The less than weight (in pounds) used to create a price record.  This will determine the weight that the item must be LESS THAN in order to qualify for this shipping price. numeric  
SHIP_PRICE Shipping Price This is the price to ship an item purchased under the source code in SHIP_SOURCE, to the destination region in SHIP_REGION, using the shipping method in SHIP_TYPE, and which weighs at least the weight in SHIP_EQUALTO, but less than the weight in SHIP_LESSTHAN. numeric  
SHIP_COMMENTS Shipping Comments Comments for this record. char/100  

Customer Maintenance

Tax Record (TAXES)

If you are selling products via the Shopping Cart which require calculation of   taxes, here is where you enter the tax table.

Currently, SDSS only calculates taxes against Subproduct items marked as "shipped".  It does NOT calculate taxes against Subscriptions or File Downloads.  Furthermore, SDSS only calculates taxes for States and Provinces within the United States and Canada.  It does NOT calculate taxes for any region outside of the United States or Canada.

When an end-user requests a "shipped" SUBPRODUCT from the Shopping Cart and fills out the Payment Form, the state/province code of the BILL TO address is checked against the tax table for the source code indicated on the form.   If the there is a tax record which matches the state/province code AND source code on the Payment Form, tax is calculated against the total amount of the Subproduct items listed on the form. 

If you make no entries to this table for your Source Code, no tax is calculated.   If the source code and the state/province code entered by the end-user on the Payment Form does not match any record entered in this table, then no tax is calculated.   Again, only Subproduct items marked as "shipped" can be taxed within SDSS at this time.

Field Title Desc Type/
MaxSize
SQL Hint
TAX_CODE Tax Code The code for this tax record.  It is automatically created by combining the TAX_SOURCE and TAX_PROVINCE values. char/15  
TAX_SOURCE Tax Source Code The source code of the company this table is used for.  Any shipped product purchased using this source code will use this tax table. char/10  
TAX_PROVINCE Tax Province The BILL TO state/province (filled out by the end-user on the Payment Form) to match this tax record against.  State/Province can only be in United States or Canada. char/5  
TAX_PERCENT Tax Percent The tax percent rate.  (i.e., 3, 7.5, 10, etc...) numeric  
TAX_COMMENTS Tax Comments Comments, if any, for this record. char/100  

Customer Maintenance

Purchase Order Record (PO)

If you accept purchase orders, and mark SRC_ALLOWPO as "Y" in your SOURCE Record, then you need to fill out a PO Record for each organization you will allow to purchase items via Purchase Order.

If an end-user wishes to purchase an item via Purchase Order:

  1. A PO Record must be created here, with a unique username and password for the user's organization.
  2. You must make sure your Source Record has SRC_ALLOWPO marked as "Y".
  3. When the user fills out the Payment Form for the items, he/she must use enter the username/password you supply here for the transaction to process successfully.
  4. Successful transactions will record PO number in CUST_PO field of CUSTOMER transaction record.
Field Title Desc Type/
MaxSize
SQL Hint
PO_USERNAME PO Username The login username for the organization allowed to purchase by PO. No spaces. char/20  
PO_PASSWORD PO Password The login password for the organization allowed to purchase by PO.  No spaces. char/20  
PO_SOURCE PO Source The Source Code for the items this end-user is allowed to purchase via PO. char/10  
PO_ORGANIZATION PO Organization The name of the organization allowed to submit Purchase Orders. char/60  
PO_CONTACT PO Contact Contact for organization. char/60  
PO_ADDRESS1 PO Address1 First line of address. char/50  
PO_ADDRESS2 PO Address2 Second line of address. char/50  
PO_CITY PO City Organization city. char/50  
PO_STATE PO State Organization state/province. char/30  
PO_ZIP PO Zip Organization zip/postal code. char/20  
PO_COUNTRY PO Country Organization country. char/50  
PO_PHONE PO Phone Organization phone. char/20  
PO_FAX PO Fax Organization fax. char/20  
PO_EMAIL PO Email Organization contact e-mail. char/60  
PO_COMMENTS PO Comments Comments for this organization. char/900  

Customer Maintenance

Source Record Maintenance

Source Record (SOURCE)

The Client Source Account record is used to provide information about you, the SDSS Client.  There are certain fields you can update, and others you cannot.

The "MaxSize" is the maximum number of characters you can enter for the field.  Please refrain from entering single or double quotation marks (""", "'") in any fields, except for single quotation marks in SQL query character fields.

Field Title Desc Type/
MaxSize
SQL Hint
SRC_CODE Source Code The Source Code for this Client.  This is automatically generated by SDSS upon successful client signup. char/10  
SRC_NAME Name Name of Client.  Use company name.  This name appears on all end-user pages generated by SDSS for this Client. char/50  
SRC_ADDRESS Address Address of Client. char/50  
SRC_CITY City City of Client. char/50  
SRC_STATE State/Province State/Province of Client. char/50  
SRC_ZIP Zip/Postal Code Zip/Postal Code of Client. char/20  
SRC_COUNTRY Country Country of Client char/50  
SRC_PHONE Phone Client phone number. char/20  
SRC_FAX Fax Client fax. char/20  
SRC_CONTACT Contact Public contact name for Client.  This is the name which goes on bottom of credit card order and pay pages for special contact.  It is also the name given to contact in case of problem with transaction.  Default is: "Software Creations Support Hotline" char/50  
SRC_CONTACTPHONE Contact Phone Public contact phone for Client. This is the phone number which goes on bottom of credit card order and pay pages for special contact.  It is also the phone number given to contact in case of problem with transaction.  Default is: "+1 310 324 7045" char/20  
SRC_CONTACTFAX Contact Fax Public contact fax for Client. This is the fax number which goes on credit card order and pay pages. It also the fax number to be used by end-users for faxing orders. It is also the fax number given to contact in case of problem with transaction. Default is: "+1 310 324 9577" char/20  
SRC_EMAIL E-Mail Email address for Client. This is the email address which is displayed on all SDSS end-user pages. char/60  
SRC_URL URL URL for Client. This is the URL which is displayed on all SDSS end-user pages. char/80  
SRC_LOGO Logo URL URL for Client logo. This is the logo which is displayed on all SDSS end-user pages. char/80  
SRC_WHOSHIPS Who Ships "0" if Software Creations ships the product.  "1" if the Client ships. char/10  
SRC_CLIENT_USERNAME Client Username Client username used for logging into SDSS for administration/maintenance. char/20  
SRC_DOWNLDDIR Download Directory Name The name of the subdirectory where files are stored for File Download Purchases (NOT File Download Subscriptions).  This will be supplied by the SDSS System Administrator. char/20  
SRC_NFOMAX Maximum Infobases Allowed Maximum number of infobases allowed.  The basic concept of SDSS Infobase Subscriptions is that they consist of groups of infobases.  You select the maximum number you wish when you subscribe.  You can always increase this number when you extend your subscription. integer  
SRC_NFOS Number Infobases Used Number of infobases currently used.  This is the number of infobases you have set up for use in SDSS. integer  
SRC_SUBMAX Maximum Subscriptions Allowed Maximum number of subscriptions allowed. A subscription, in SDSS, is normally considered the grouping of a set of infobases or one infobase.  The maximum number you are allowed depends upon the maximum number you selected when you subscribed.   You can always increase this number with an extended subscription. integer  
SRC_SUBS Number Subscriptions Used Number of subscriptions currently used.  The subscriptions you have set up under your Client Account. integer  
SRC_EXPIRES Does this record expire (Y/N)? "Y" if this record will expire. char/1  
SRC_EXPIRETIME If record expires, expiration date If record expires, this is the date, in seconds, it will expire. integer  
SRC_DISCOUNT Discount Percent If this Client Source has an across the board discound rate, it is entered here.   Currently not implemented. numeric  
SRC_SUSPEND Suspend (Y/N) "Y" if this record is suspended. char/1  
SRC_COMMENTS Comments Comments char/200  
SRC_SOURCE Source for this Source This is the Source Code of the company responsible for the creation of this Source Code. char/10  
SRC_ALLOWPO Allow Purchase Orders (Y/N) Does this source code allow end-users to enter Purchase Orders to pay for online transactions?  Enter "Y" or "N" as appropriate. char/1  
SRC_DOWN Down (Y/N) Use this option to disallow all payment transactions.  By entering "Y" here, end-users will not be able to get to the Payment Form to process a payment transaction for any items under this source code. Additionally, no new account signups will be allowed. char/1  
SRC_PROCESS Remote Order Processing (Y/N) Do you wish to have details of orders processed for this source code sent to a remote system for further processing? char/1  
SRC_PROCESSURL URL for Remote Processing If the SRC_PROCESS = "Y", you enter here the URL which will process remote order transactions. char/100  
SRC_PROCESSPW Password for Remote Processing If the SRC_PROCESS = "Y", you enter here the password which will be used by the remote system at SRC_PROCESSURL to accept order data. char/20  

Remote Order Processing 

Remote Order Processing sends a file to your server each time a transaction for one of your SDSS Products or Subscriptions occurs.  This allows you to do order processing locally as credit card or PO transactions occur.

The following describes the format in which the remote order processing info is sent.  Each transaction sends a minimum of 4 records.  Record #4, "Line Items", is duplicated for each separate product (SDSS "SubProduct") in the transaction.  This process requires:

  1. The Perl cgi-bin program "processorder.pl" is installed and running correctly on your web server.  See SDSS Administrator for details on this.
  2. SRC_PROCESS = "Y".
  3. SRC_PROCESSURL = the URL at which the Perl cgi-bin program "processorder.pl" is available on the remote machine.  For example: "https://www.yourserver.com/cgi-bin/processorder.pl".  This should run on a secured web server.
  4. SRC_PROCESSPW = the password you have hard coded into the "passwordVerify" field of "processorder.pl". 

File format for order processing program

This is the layout in which information sent using Remote Order Processing is saved on your local hard disk.  

File Lay Out: Uppercase all, ‘|’ separated, ‘size’ indicates maximum length not fixed length

Record 1 (CC / PO Info):

Field Name                 Size        Default Values

Record Type                    02            H1
Batch_no                       09            Unique No for Order
Email Address                  40               
Phone                          12
Shipping Method                04
Payment_method                 02            PO or CC
PO Number                      15
Credit Card Type               06
Credit Card Number             20            No spaces or blanks
Name ON CC First Name          08
Middle Init                    02
Last Name                      18
Expiration month               02
Expiration Year                04
Comment                        60
Alternate Phone                12            Text
Fax                            12            Text
Source Code                    06                       
Customer Number                10
Order Method                   02            ‘EW’

Record 2 (Bill To Info):

Field Name                 Size        Default Values

Record Type                    02            H2
Batch_no                       09            Unique No for Order
Bill To First Name             08
Middle Init                    02
Last Name                      18
Title                          05
Company/Institution            35
Address 1                      35
Address 2                      35
City                           25
State                          02
Zip                            15
Country                        06

Record 3 (Ship To Info):

Field Name                 Size        Default Values

Record Type                    02            H3
Batch_no                       09            Unique No for Order
Ship To First Name             08
Middle Init                    02
Last Name                      18
Title                          05
Company/Institution            35
Address 1                      35
Address 2                      35
City                           25
State                          02
Zip                            15
Country                        06
 

Record 4 (Product Purchase Line Items):

Field Name                 Size       Default Values

Record Type                    02           L1
Batch_no                       09           Unique No for Order
Batch SeqNo                    04           Seq. No. for items
Quantity                       09
Code                           16           SDSS Product / SubProduct Code
Title                          75           SDSS Subproduct / Subscription Title
Author                         23           Not Used.
Price                          8+2

Source Record Maintenance

top

SDLOGIN

This is a mechanism whereby users may access your infobase(s) via other sites.   When a user accesses an infobase using this method, the user sees only the banner and contact information of the site from which he linked to the infobase.  This is useful if you wish other sites to be able to host demonstrations of your infobases; you can give the site managers the assurance that they won't lose their users by referring them to your infobase(s).

To utilize this mechanism:

  1. You must contact your SDSS System Administrator.  In addition to having your infobase and subscriptions set up correctly, an SDLOGINURL record must be created for you.   This record will identify your siteDirector server.  Once this is set up, you will be assigned a special SDLOGINURL Code to use in the URL you give to other sites to connect to your infobase(s).
  2. Your SDSS System Administrator must set up an SDSS Source Code for the site which will be linking to your infobase(s).  There may be a set-up fee involved here.

The format of the URL used to access your infobase(s) by other sites is:

http://dns.scbbs.com/client-cgi-bin/sdlogin.pl?your_sd_details+site_source_code+SDLOGINURL_code

Where:

your_sd_details = Your sD infobase query string (URL details on other side of "?").
site_source_code = The SDSS Source Code assigned to the linking site.
SDLOGINURL_code = The SDSS SDLOGINURL code assigned to your sD server.

So, if your infobase URL is:

http://yoursite.com/cgi-bin/om_isapi.dll?infobase=your.nfo&softpage=Browse_Frame_Pg42

...and, we assign the site linking to your infobase a source code of "D100", and we assign your sD server an SDLOGINURL Code of "W1", then the URL you will give to the site to link to your infobase is:

http://dns.scbbs.com/client-cgi-bin/sdlogin.pl?infobase=your.nfo&softpage=Browse_Frame_Pg42+D100+W1

By following this link, users will be logged into our SDLOGIN database as coming from that site (Source Code).  All banners and contact information displayed will be displayed for that site (Source Code), and NOT your Source information.

SDLOGIN Table (Maintained directly by direct SQL commands by Sys Admin only)

Field Title Desc Type/
MaxSize
SQL Hint
SDLOGIN_IP IP IP address of user accessing infobase. char/15  
SDLOGIN_EXPIRETIME Expiration Expiration time for this record.  3 hours. integer  
SDLOGIN_SOURCECODE Source Code Source Code of site from which this user linked to infobase. char/10  

SDLOGINURL Table (Maintained directly by direct SQL commands by Sys Admin only)

Field Title Desc Type/
MaxSize
SQL Hint
SDLOGINURL_CODE Code Code for this record.  This is used in URL link from remote site to let SDSS know what sD server to re-direct request to. char/10  
SDLOGINURL_HOST Host Host name of sD server on which infobase to be connected to resides. char/50  
SDLOGINURL_ROOT Root This is the Query String portion of the sD URL for the infobase to be connected to.   In other words, everything which follows the question mark ("?") in the URL which would normally be used to access this infobase. char/50  

 

SDLOGINURL_TITLE Title Title, for internal reference, for this record. char/50  

top

REFERERLOG

Each time someone who is NOT logged in attempts to access an infobase secured under SDSS, a record is stored in REFERERLOG which contains:

  1. The user's IP address.
  2. The URL of the page the user was attempting to access.
  3. The time (in seconds) that the request took place.

REFERERLOG  is searched by the following program:

http://dns.scbbs.com/client-cgi-bin/referer.pl

This program is designed to search the REFERERLOG for the IP which matches that of the user accessing this program, and link the user to the page stored in the last matching record.

REFERERLOG Table (currently not available for access via SQL)

Field Title Desc Type/
MaxSize
SQL Hint
REFERER_IP IP IP address of user accessing infobase. char/15  
REFERER_TIME Time Time (in seconds) when request was made. integer  
REFERER_QUERY Request URL  URL of page that user requested when bounced out of infobase to Login Screen. text  

top

SDDLLOG

Each time someone:

  1. Logs into File Download Subscription;
  2. Purchases File Download;
  3. Executes SDSS SQL command that stores results;

An SDDLLOG log record is created.  This record tells SDSS that the username and/or IP stored in the record has access to the file or Subscription Code file(s) that are defined in the record.

SDDLLOG  is maintained by the following internal programs which delete expired records.  These programs are run as daemons and are not required to be ran manually:

http://dns.scbbs.com/client-cgi-bin/secure_log_remove.pl
http://host3.scbbs.com/cgi-bin/sddl_log_remove.pl

SDDLLOG Table (currently not available for access via SQL)

Field Title Desc Type/
MaxSize
SQL Hint
SDDLLOG_IP IP IP address of user allowed to access file. char/15  
SDDLLOG_USERNAME Username SDCUST Username allowed to access file. char/20  
SDDLLOG_EXPIRETIME Expiration Date Time (in seconds) when this record expires.  For Type 1 and 2, this is typically 24 hours.  For Type 3, this is the expiration period defined in the Subscription Code entered here. integer  
SDDLLOG_TYPE Type Download Log Type:

1 = File Download Purchase
2 = SDSS SQL Temporary Directory
3 = File Download Subscription

char/1  
SDDLLOG_FILENAME Filename Name of file that SDCUST user above can download (if this is Type 1).  Type 2 and 3 records do not require a filename. char/25  
SDDLLOG_SUBCODE Subscription Code Subscription Code of file(s) that SDCUST user above can download (if this is Type 1 or 3). char/10  
SDDLLOG_SOURCECODE Source Code Client Source Code of file that SDCUST user above can download (if this is Type 1 or 3). char/10  
SDDLLOG_DIR Download File Directory This is the name of the directory where file(s) are temporarily stored (if Type 2). char/60  

top

SDSSDbBeanRemote

This is a Java Bean designed to run on remote servers (outside the SDSS Network) and provides the following methods:

getSubCount(String source, String infobase)

Return the integer count (countLimit) of subscriptions that a particular infobase belongs to.

getSubList(String source, String infobase, int countLimit)

Returns an Array[x][3] which contains the list of subscriptions that a particular infobase belongs to.

Array[x][0] - Subscription Code
Array[x][1] - Subscription Start URL
Array[x][2] - Subscription Title

getUserIPCount(String source, String ip)

It returns an integer count (username count) of usernames that are IP recognized using the IP you send.

getUserIPList(String source, String ip, int count)

This returns an Array[username count] of usernames that are IP recognized using the IP you send. You must also send the count which is returned by getUserIPCount() above. The array is: Array[username count].

ipRecognizeNFO(String source, String iaAddress, String infobase)

Checks to see if the IP address (iaAddress) of the browser accessing this program has access to this infobase.  Returns an Array[7] which contains the following:

Array[0] - "y" or "n" (IP Found?)
Array[1] - "Y" or "N" (File Download Subscription? -- Yes, case matters)
Array[2] - Subscription Start URL (URL Encoded)
Array[3] - Subscription Login URL (URL Encoded)
Array[4] - Subscription Code 
Array[5] - Sublogin URL Base (URL to program which processes Sublogin URL elements, i.e. "http://dns.scbbs.com/client-cgi-bin/sublogin.pl")
Array[6] - Error Message

userSubsCount(String source code, String username) 

Returns an integer which contains the number of subscriptions (subscription count) a user has access to.

userNFOsCount(String source code, String username) 

Returns an integer which contains the number of infobases (infobase count) a user has access to.

userSubs(String source code, String username, int subscription count): Returns an Array[subscription count][3] containing the following:

Array[x][0] - Subscription Code
Array[x][1] - Subscription Start URL
Array[x][2] - Subscription Title

userNFOs(String source code, String username, int infobase count): Returns an Array[infobase count][5] containing the following:

Array[x][0] - Infobase Name
Array[x][1] - Infobase Title
Array[x][2] - Subscription Code
Array[x][3] - Subscription Start URL
Array[x][4] - Subscription Title

userLoggedInNFO(String source, String userName, String ip, String infobase)

Check to see if this username is logged in with this IP for access to this infobase.  Returns an Array [2] containing the following:

Array[0] - "y" or "n" (Infobase Found?)
Array[1] - Error Message

verifyPassword(String source, String username, String password)

It returns "y" or "n" (lower case). 
This method verifies that an SDSS customer account exists with the username and password you send.

top