E2V - Fast. Reliable. Scaleable.

Moving to Version 3 from Version 2

It's strongly recommended before you convert your store to use version 3, that you first set up the supporting objects (such as the Inventory Server, Store Controller, Transaction and Delivery relays, and redelivery terminals) in private, and familiarize yourself with how these elements operate, and the various options available to you.

You will need to unpack the new software into your inventory before you get started. In the distribution box you'll find an object named [E2V-3] Installer HUD followed by a release number. Wear this HUD and click Install Folder.

Initial Steps

The first steps you'll be taking will not affect your current, live store.

They are:

  1. Set up the new Inventory Server
  2. Rez and configure required support objects



Step 1 - Set up the new Inventory Server

For simplicity, the remainder of this document will refer to your version 2 server as the white server, and your new version 3 server as the black server.

  1. Rez the [E2V-3] Inventory Server object, and click it to activate it (it's OK to have a live white server and black server at the same time). When the server starts up it will ask you for link permissions. Grant the object permissions so that you'll be able to add more storage boxes when needed.
  2. Copy inventory contents.
    1. Two utility scripts are provided in your product folder, called Copy prim contents - FROM HERE and Copy prim contents - TO HERE.
    2. Place the FROM HERE script into one of the storage boxes in the white server.
    3. Place the TO HERE script into one of the storage boxes in the black server.
    4. The contents of the white server's box will be copied to the black server's box, and both scripts will be automatically removed.
    To prevent specific items from being eligible for redelivery, mark the box they're in as being no redeliver by placing the text nr into the storage box prim's description field. (This is a change from version 2, where the text was "nocopy" - now it is more accurately "nr" for "no redelivery" since the perms of the contained items do no matter.) You can customize the look of each of the storage boxes by coloring the side textures, or replacing the front "E2V" texture (512x128).
  3. Set up a backup server (optional) A backup server is only useful if your primary server is not rezzed on the same region as your store. In the event the primary server's region goes down or is restarted, the system will attempt to locate and use a backup server. Here's how to create a backup server:
    1. After you finish making the main server, use your viewer's "Take a Copy" command.
    2. Go to the region where you'll keep the backup server, and rez it.
    3. Before you click the server to enable it, create a note card in your SL inventory, and name it backup. The contents of this note card do not matter, you can just type a single letter and save it.
    4. Place this note card into the root prim of the backup server.
    5. Click the server to enable it.
Frequently Asked Inventory Server Questions

Q: Do I still need the white server?
A: You need the white server as long as you have any version 2 vendor scripts or redelivery terminals on the grid. Both these items would need to deliver from the white server. Once you convert all your vendors (in all your locations) then you can take the white server into your inventory.
Q: Does the black server have to be with the white server?
A: No, the new black server is independent of the white server, so you can place it anywhere. Same goes for the backup server.
Q: Do I have to manually keep the two servers in sync?
The simplest answer is "yes." As long as you need to have a white server rezzed (see above), you should keep the contents of both servers syncronized. Do not use the "Copy contents" scripts to do this, as they will duplicate all the items already in the black server!



Step 2 - Rez and configure required support objects

The following must be done on each region where you have vendors:

  1. Rez a Store Controller object.

    You must make a decision at this point
    In Version 2, you've been putting buyer's rewards information onto each vendor, using the r: and the g: options. But if you use the same values on every vendor, then it's a hassle to have to repeat them everywhere. So version 3 makes it easy to have the same values for all your vendors, by putting those values into the Store Controller instead of on each individual vendor.

    So, do you want to have the Store Controller set the Buyer's Rewards rates for all your vendors?

    YES - Edit the "settings" note card inside the Store Controller. The first two lines are "n-reward" (buyer's rewards for non-group members) and "g-rewards" (for group members), and place your desired values on those lines. When you convert your vendors (in an upcoming step) be sure to tell the updater that you want to erase the buyer's reward values from your vendors.

    NO - Edit the "settings" notecard inside the Store Controller, and change the first two lines ("n-reward" and "g-reward") to 0.

    After you edit the settings note card, you will see the red floating text above the Store Controller, indicating that the settings have changed, and that you must click to reload them. Click once. Review the settings in local chat. If the settings look fine, click again to activate the new settings, but pick "None" from the restart menu.

  2. Rez a Transaction Relay object.
  3. Rez a Delivery Relay object.

Important
From here on, please be aware that you may be making changes to your live store. It's up to you to make sure that you have tested your setup so far, and that it's working as desired. Remember that you can always create a test vendor to expiriment with.



Upgrade vendors

You have two options when it comes to upgrading your existing vendors.

Upgrade All Vendors

You can use the [E2V-3] Convert v2 to v3 object to upgrade all the vendors in your store automatically. Click the object and pick Help for instructions. If you use the same buyer's reward values on all your vendors, you can make your life easier by putting those values into the Store Controller, and telling the convert object to erase the credit values. Try this on a single test vendor to see how it uses the store's default values when none are specified on the vendor itself.

Upgrade Single Vendors

If you would like to go a little slower, and perhaps take advantage of new features like Pricing Groups, you can instead use the [E2V-3] Upgade Vendor HUD HUD. To use it, you'll first set the options you want a vendor (or group of vendors) to use into the HUD itself, then simply drop the converter script on top of each vendor that you want to use the those options. You can then change the HUD's settings, and move onto to the next set of vendors. (Note that you do not need to edit the vendors to convert them. Simply drag the converter script from your inventory and drop it on top of the vendor object.)

You can find more information here.



Upgrade other store objects

There are new versions of the redelivery terminal and credit terminal scripts in the version 3 folder. Simply delete the ones from your existing terminals, and drop in the new scripts. No other changes are needed.

It is not a requirement to immediately replace your gift card system with the version 3 scripts, but there are some new features that you might want to take advantage of. For example, you can now place a notecard and/or a landmark into the gift card, and the owner of the card can click the card to get a menu offering those items. Note that when you do move to the version 3 scripts, you must update the gift card vendor(s), the gift card(s), and also the redemption terminal(s) all together at once.