Miva Empresa Virtual Machine Installation on Windows NT Server
Revision 1.0
This document and the software described by this document are copyright 2000 by Miva Corporation. All rights reserved. Use of the software described herein may only be done in accordance with the License Agreement provided with the software. This document may not be reproduced in full or partial form except for the purpose of using the software described herein in accordance with the License Agreement provided with the software. Information in this document is subject to change without notice. Companies, names and data used in the examples herein are fictitious unless otherwise noted.
Miva is a registered trademark of Miva Corporation. Miva Script, Miva Script Compiler, Miva Order, Miva Merchant, Miva Virtual Machine, Miva Mia, Miva Empresa, the Miva "blades" logo, and the Miva Engine are trademarks of Miva Corporation. Windows is the registered trademark of Microsoft Corporation. All other trademarks are the property of their respective owners. This document was developed and produced in San Diego, CA, USA.
MIVA CORPORATION WILL NOT BE LIABLE FOR (A) ANY BUG, ERROR, OMISSION, DEFECT, DEFICIENCY, OR NONCONFORMITY IN MERCHANT OR THIS DOCUMENTATION; (B) IMPLIED MERCHANTIBILITY OF FITNESS FOR A PARTICULAR PURPOSE; (C) IMPLIED WARRANTY RELATING TO COURSE OF DEALING, OR USAGE OF TRADE OR ANY OTHER IMPLIED WARRANTY WHATSOEVER; (D) CLAIM OF INFRINGEMENT; (E) CLAIM IN TORT, WHETHER OR NOT ARISING IN WHOLE OR PART FROM MIVA CORPORATION'S FAULT, NEGLIGENCE, STRICT LIABILITY, OR PRODUCT LIABILITY, OR (F) CLAIM FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES, OR LOSS OF DATA, REVENUE, LICENSEES GOODWILL, OR USE. IN NO CASE SHALL MIVA CORPORATION'S LIABILITY EXCEED THE PRICE THAT LICENSEE PAID FOR MERCHANT.
MVM-1002-01 (Rev 1.0) Miva Empresa Virtual Machine 4.00
Introduction
This manual is intended for NT system administrators. If you are not a system administrator, you will not be able to perform the installation as described below.
Installing Miva Virtual Machine enables you to run compiled Miva Script applications (.mvc) on your web site. These installation instructions provide only the basic information to allow you to get Miva Virtual Machine up and running quickly.
Install Preparation
- Place the ntxxx.exe (ISAPI distribution) file into a temporary directory and change to that directory. (xxx refers to the version number.)
- Run or double-click on the executable.
- Click Next.
- The License Agreement screen displays.
- Read the License Agreement. If you accept the agreement, select the I accept button, and click Next to continue.
- The Customer Information screen displays.
- Enter the information, and select whether the installation is for all users or only the current user, then click Next.
- This setting determines where the Program information is stored, and who will have access to it.
- Select Complete or Custom, then click Next.
- Complete: installs to C:\Program Files\Miva\Miva Empresa.
- Custom: allows you to select the installation folder.
- To change any previously entered information, click the Back button, otherwise, click Install.
- The installation process begins. When complete, click Finish.
Note: The Release Note is installed to Program Files\Miva\Miva Empresa\RELNOTE.txt.
Security Settings
As with all Internet applications, security is very important. We recommend that you set security properties to the highest standards. Since every system is different, the system administrator must implement the best security measures for the specific needs of the server and installed third-party software.
The minimum permission settings for Miva Merchant to function correctly are with the anonymous user, often called IUSR_<machinename>, with change permissions on the Merchant script and data directories.
Note: These permissions are for Miva Merchant. Permissions settings for other directories and applications should be implemented according to the recommendations in the manufacturer's documentation.
Run Microsoft Management Console
After the installation has been completed, go to the menu bar and select the following:
- Programs
- Windows NT 4.0 Option Pack
- Microsoft Information Server
- Internet Service Manager
This will open the Microsoft Management Console (MMC).
Use the following procedure to add the snap-in from the MMC.
- Click on the Console menu option from the main menu bar.
- Click on Add/Remove Snap-in option.
- On the Add/Remove snap-in screen, click on Extensions.
- Select the check box next to Miva VM).
- Click OK to all screens until you are back at MMC's main screen again.
- On MMC's main screen, check if you have a _vti_bin directory under the web or sub-web on the server, and open it. Perform the following procedure for the _vti_adm and _vti_aut directories.
- Right-click on _vti_adm or _vti_aut directory, and click Properties.
- Select the Directory Security tab.
- Click the edit button for Anonymous access and Authentication control.
- Ensure Allow Anonymous Access is not selected.
- Click OK.
- Repeat substeps a through e for the other directory (_vti_adm or _vti_aut).
- On MMC's main screen, right click on the website you wish enable from the list in the left screen and a menu is displayed.
- Select Properties and the site's Properties screen displays.
- Click the Miva VM tab.
- The configurations for the script directory and the data directory must be properly set before most scripts will function properly.
- Restrict scripts to the following directory and below.
- This is the directory where you want scripts to be placed on the web site in order to be run. We recommend that you use the same directory as the one where your HTML files are stored. So if your home directory for the site is C:\inetpub\wwwroot\somesite then use that as the script directory also.
- Store data in the following directory.
- This is the directory that all Miva Script files will, by default, save data. This would be the root data directory for the given web site. We recommend that you create a directory outside of any web accessible directories such as C:\inetpub and create a \mivadataroot\ directory there.
- If you want to add Commerce Libraries, see "Add Libraries" on pageÝ7. Otherwise, click OK, and proceed to "Set Permissions in Windows Explorer" on pageÝ8.
Add Libraries
If you are going to be using any Commerce, Database, or Configuration Library functionality such as payment gateways or UPS shipping, then you need to add in the Methods and assign them to the proper .dll file. Libraries that are part of Miva Merchant may be been downloaded from the Miva FTP site.
- In the Miva VM tab, click the Libraries button.
- The Libraries window opens.
- Click Add, or if you want to change a library item, double-click in the Type column for the associated Library you want to change.
- The Add/Edit window opens.
- Enter or change the library:
- Select the Library Type from the drop-down list.
- Enter the Method.
- Payment commerce libraries are listed below in the form:
Method, file (Service).
- AuthorizeNet, mcathnet.dll (Authorize.Net Payment Services)
- CyberCash, mccybcsh.dll (CyberCash Payment Services)
- ICS2, mcics2.dll (CyberSource ICSv2 Payment Services)
- LinkPoint, mclp.dll (Cardservice/LinkPoint)
- PNTransact, obtain file from vendor (Verisign Payflow Pro,
PaymentNet)
- Database libraries are listed below in the form: Method, file.
- MVDODBC, ODBC.dll (ODBC database API functions)
- MVDOracle, MVDOracle.dll (Oracle database API functions)
- Enter the full path and file name of the .dll, or click Browse to locate and select the library you wish to add.
- Click OK.
- When all the libraries you want are listed in the Libraries box, click OK.
Note: Not all of the commerce, database, and configuration libraries that Miva Empresa (VM) supports are available directly from Miva Corporation. Some libraries must be obtained directly from the Miva Technology partner, developer, or other company.
Set Permissions in Windows Explorer
Now, you will set the permissions for the Miva data and script directories. These Miva permissions should not propagate to other folders, such as the Front Page folders.
Set Permissions for Front Page Directories
Make sure you maintain these permissions and that the Anonymous access remains unchecked for the Front Page folders. These settings should not propagate to the Miva data and script directories
- For sub-sites, using Windows Explorer, open the _vti_bin directory within any web or sub-web on the server, (for example, under inetpub\wwwroot\somesite) and perform the following for each directory.
- Right-click on the _vti_adm or _vti_aut, and click Properties.
- Click the Security tab, and click Permissions.
- Remove the anonymous user from the list. (This user is usually named IUSR_<machinename>.
- Repeat substeps a, b, and c for the other directory (_vti_adm or _vti_aut).
Miva Data Directory
- On the Windows NT Explorer screen, right click the mivadata directory.
- Select Properties and the Properties window opens.
- Select the Security tab.
- Click the Permissions button.
- The Directory Permissions screen opens.
- Click Add from the Directory Permissions screen.
- The Add Users and Groups screen displays.
- Select the anonymous user, often called IUSR_<machinename>.
- In the properties for that directory, you need to set the security so that the IUSR has "Change" permissions on the directory.
- At the bottom of the screen, select Change.
- Click OK.
- Click OK on the Directory Permissions screen.
- Click Yes when you are prompted whether you wish to change the security information on the Windows NT screen.
- Your `Store data in the following directory' path should look similar to this example.
- You should then create a sub-directory for each separate web site to store its data in. For example, if the site's document root is C:\inetpub\wwwroot\somesite then use C:\inetpub\mivadataroot\somesite as its data directory.
Miva Script Directory
You need to set the same permissions for merchant2, under the Miva Script directory, as you just did for the Miva Data directory.
- In Windows Explorer, right click on merchant2 under the script directory (wwwroot, htmlscript, etc.), then select Properties.
- The Properties window opens.
- Select the Security tab.
- Click the Permissions button and the Directory Permissions screen opens.
- Click Add from the Directory Permissions screen.
- The Add Users and Groups screen displays.
- Select the anonymous user, often called IUSR_<machinename>.
- At the bottom of the screen, select Change to change the Access Type.
- Click OK.
- Click OK on the Directory Permissions screen.
- Click Yes when you are prompted whether you wish to change the security information on the Windows NT screen.
This completes the installation. Repeat this procedure for each site.