Difference between revisions of "NATS3 to NATS4 Going Live Checklist"
TMMStephenY (talk | contribs) m |
|||
| Line 40: | Line 40: | ||
*Program/Site relations are correct (e.g. ''Site A belongs to Programs 1, 2, and 3 only'') | *Program/Site relations are correct (e.g. ''Site A belongs to Programs 1, 2, and 3 only'') | ||
*Your affiliates are active for the correct programs | *Your affiliates are active for the correct programs | ||
| + | *You have create the proper Account Rep payout program(s). Without this, your Account Reps will not be paid out. | ||
*Your payout changes are correctly set up | *Your payout changes are correctly set up | ||
**Affiliate-specific payouts | **Affiliate-specific payouts | ||
| Line 45: | Line 46: | ||
**Disabled payouts for in-house accounts (if applicable) | **Disabled payouts for in-house accounts (if applicable) | ||
**Priority levels set up in the correct order (the payout change at the top of the list will get highest priority) | **Priority levels set up in the correct order (the payout change at the top of the list will get highest priority) | ||
| + | |||
=== Join Option information === | === Join Option information === | ||
*Descriptions match up properly | *Descriptions match up properly | ||
Revision as of 16:10, 28 November 2011
Congratulations! You're almost done with your NATS v3 to NATS v4 migration. Before you go live, you should make sure the following is completed:
Checking Your Imported Information
Member information
- Members are associated to the proper affiliate/campaign/site/program/biller
- All active members have at least one subscription
- Member information such as email address shows up correctly
Affiliate information
- Affiliate information matches the username/password
- Affiliates can login
- Affiliate Payvia information is correct
- Affiliates belong to the proper programs
- Make sure your affiliates can see/change their info properly in the affiliate area
Payvia Information
- Make sure all your payvia types are present
- Make sure the dump format you each payvia using the proper smarty variables (Note: they will be different between v3 and v4)
- Make sure your affiliates are all associated with a payvia in v4
Site information
- Make sure the URL to all of your tours are correct
- Your Join Options exist for all of your sites
- Your sites belong to the proper program(s)
- Any site/tours that you want to hide are either deleted or marked as hidden
- The biller info for each tour is filled in correctly
- Your special join options are set up correctly
- Your site partners are properly linked to their site(s) and their payout(s) are set correctly
Biller information
- Account information is accurate
- Biller fees are properly set up
Cascade information
- Your active cascades have at least one SHOW rule active
- Verify that rules are properly set up for all cascades
- Billers in your cascades are in the proper order
- All the steps in your cascade have a processing type (eg, 'cc', 'check', 'web900', etc.)
Program information
- Programs are properly shown/hidden
- Program/Site relations are correct (e.g. Site A belongs to Programs 1, 2, and 3 only)
- Your affiliates are active for the correct programs
- You have create the proper Account Rep payout program(s). Without this, your Account Reps will not be paid out.
- Your payout changes are correctly set up
- Affiliate-specific payouts
- Tiers (if applicable)
- Disabled payouts for in-house accounts (if applicable)
- Priority levels set up in the correct order (the payout change at the top of the list will get highest priority)
Join Option information
- Descriptions match up properly
- Rules are set up properly for each of your join options
- Option-specific biller information is accurate
Cross Sell information
Outgoing
- Check that the rule(s) for each of your outgoing cross sales are set up properly
- Verify that the account info and ref code for each of your cross sells are filled out completely and correct
(NOTE: Some billers in v4 require require additional information in order for xsells to work in v4! See the individual billers below for details)
Incoming
- Make sure each incoming xsell is associated with the proper site/program
- Make sure the biller info is correct AND complete
(NOTE: Some billers in v4 require require additional information in order for xsells to work in v4! See the individual billers below for details)
Ad Tool information
- Make sure your adtools display properly on the affiliate area
- Make sure your adtools are assigned to the proper group
- Make sure that the rule(s) for each adtool are set up properly
Things to Check Before Going Live
- Your v4 templates are working and functioning properly
- This includes everything affiliate area AS WELL AS all of your join pages
- NATS v3 TEMPLATE VARIABLES WILL NOT WORK IN V4!
- Your linkdomains point to your v4 install as soon as you "go live"
- Check the currency exchange rates in your v4 install before going live
- The currency is different between NATS3 and NATS4.
- For example if currency is .79 for NATS3 then it would be 1/.79 for NATS4
- In NATS3 it's USD to Currency.
- In NATS4, it's Currency to USD
- Just take do 1/exchange rate like the example above.
How to Check your Nats 4 Join pages before you "go live"
Note: the "Default Join Link" found in your Sites admin will point to your Nats 3 installation and not your Nats 4 templates
- Copy the desired Join form link found in your sites admin and paste it into your preferred text editor
http://nats3.myoldlinkdomain.com/signup/signup.php?nats=<?=$_REQUEST['nats']?$_REQUEST['nats']:'MC4wLjEuMS4wLjAuMC4w'?>&step=2
- Use the default nats code to build a track link which will point directly to the nats join page
NATS CODE:
MC4wLjEuMS4wLjAuMC4w
- Your track link will be based upon your Nats 4 installations domain (eg. nats4.mynewnatsinstall.com ) which will include the default Nats code which you have just copied
http://nats4.mynewnatsinstall.com/track/MC4wLjEuMS4wLjAuMC4w/join
- Copy and paste this new URL into your browser
This URL will be how you will test out your Nats 4 join page functionality and check your join page design.
Postback Information
If you were having NATS v3 post information to outside scripts using one of our various postback features, you may have to alter your postbacks to handle the new format we send our information in. Details on what get sent on v4 postbacks can be found here:
Member Authentication
If you authenticate your members area directly off of the NATS database, you must change your authentication software to check the member table instead of the members table when going live.
Biller-Specific Instructions
Normally, you won't have to change much on your biller's end of things to make them work in NATS v4. However, in certain cases you'll need to make some slight adjustments with your billers to get them to work with v4. We've listed a few of the common things that we'd like to point out. Please refer to the v4 setup instructions for each of your billers (found on this wiki) for complete details.
Note that this normally done AFTER you've gone live in v4.
WTS
- Make sure WTS has the new path to the "work" directory so they can send their transaction files to the proper NATS install
- WTS cross sells require additional information in v4. Make sure you fill in that additional information in the Upsells Admin before going live
Epoch
- Make sure epoch is posting transactions to the EpochTransStats and MemberCancelStats found in your v4 database before going live.
Other Special Cases
If you use process_gateway.php...
You need to make sure your IP and the IP of anyone sending you cross sales is added to the proper configuration variable in your includes/config_override.php file. The format is...
$config['PROCESS_GATEWAY_SECURE_IPS'] = array(
"0" => "111.222.333.444",
"1" => "555.666.777.888"
);
Improperly formatting your config_override.php can BREAK YOUR INSTALL COMPLETELY. Any changes you make this file are done so at your own risk. If you do not feel comfortable changing this file, please submit a support ticket and one of our techs can make the change for you.
If You Do Cross Sells With a Gateway Biller...
You need to make sure your IP and the IP of anyone sending you cross sales is added to the proper configuration variable in your includes/config_override.php file. The format is...
$config['XSELL_$billershort_SECURE_IPS'] = array(
"0" => "111.222.333.444",
"1" => "555.666.777.888"
);
... replacing $billershort with the shortname of the gateway biller you are using (e.g. NETBILLING or JETINTGATE).
Improperly formatting your config_override.php can BREAK YOUR INSTALL COMPLETELY. Any changes you make this file are done so at your own risk. If you do not feel comfortable changing this file, please submit a support ticket and one of our techs can make the change for you.
Gateway Biller Cross-Sales
If any Gateway biller is doing a cross-sale to process_gateway.php you will need to go to the Configuration Admin -> Biller section and turn on ALLOW_*biller*_PROCESS_GATEWAY
Replace *biller* with the billers name.
Example configuration for NetBilling would be ALLOW_NETBILLING_PROCESS_GATEWAY
If you are using Member logging log in NATS3
Please re-setup the logging log path for NATS4 as follow: http://wiki.toomuchmedia.com/index.php/Nats4_Member_Logging
Things to Remember
- NATS v3 linkcodes will always work in v4! If your affiliates are still attached to their old linkcodes, they can still use them without issue.
- NATS v4 is now tour-based instead of site-based. This means that if you make a change to the details on the default tour, It will apply to all other tours unless a different value is already set for the other tour. (Example: Let say on the Default Tour for siteid 7, you change the Rebill Post URL to http://test.com/mypost.php. This change will apply to all tours in siteid 7 expect for those who already have a different Rebill Post URL set already)
- The database structure in v4 is vastly different from v3. Therefore, if you have your own outside system querying the NATS database in v3, chances are it won't work in v4. If you need help finding certain information in the database, please let us know via the ticket system, and we'll do our best to point you in the right direction without violating the terms of your support contract.
- When reading a wiki article, make sure it applies to v4.
