Miva Resource From The Inside

I. Miva Empresa Virtual Machine

Miva Empresa (ME) is a Miva Corporation product that runs server-side scripts for online commerce.

Before version 4.02, Miva Empresa was a script interpreter run via CGI interface. Scripts were written in plain text and had the .mv extension.

Starting from version 4.02, ME became the Miva Empresa Virtual Machine. Since that time, Miva scripts should be pre-compiled into an intermediate byte code, much like in Java. This byte code is processed by Miva Empresa VM. This makes a Miva script run faster than an interpreted plain-text script. Compiled Miva scripts have the .mvc extension.

Miva Empresa On Unix Servers

When we turn on Miva Empresa resource:

Before v.4.02

1. In the domain home directory (/hsphere/local/home/<user_name>/<domain_name>/), the cgi-bin directory is created (if it wasn't created before);

2. the miva.cgi and miva.cgi.conf files are copied to this cgi-bin directory;

3. the libmivaconfig.so symlink to /hsphere/shared/miva/lib/config/3x.so is created there;

4. In the domain home directory, the mivadata directory is created;

5. In the Apache configuration file for this domain, the Miva script MIME type is added:
   application/x-miva .mv

Here,

- miva.cgi is a CGI application that interprets and executes Miva scripts;
- miva.cgi.conf is the Miva Empresa configuration file

The miva.cgi.conf file may look like this:

mivaroot=&[document_root]
stdmodedatadir=/hsphere/local/home/miva/miva.com/mivadata
securityoptions=15
<COMMERCE-LIB METHOD= "UPSCost" LIBRARY="/hsphere/shared/miva/lib/commerce/upsrss.so">
<COMMERCE-LIB METHOD= "CyberCash" LIBRARY="/hsphere/shared/miva/lib/commerce/cybercash.so">
<COMMERCE-LIB METHOD= "ICS2" LIBRARY="/hsphere/shared/miva/lib/commerce/ics2.so">
<COMMERCE-LIB METHOD= "LinkPoint" LIBRARY="/hsphere/shared/miva/lib/commerce/linkpoint.so">
<COMMERCE-LIB METHOD= "AuthorizeNet" LIBRARY="/hsphere/shared/miva/lib/commerce/authnet.so">

where:

mivaroot is the Miva Web root directory, the same as the domain's DocumentRoot directory;
stdmodedatadir is a directory where Miva Empresa data is stored;
COMMERCE-LIB METHOD is a Payment Instrument, a commercial library to support automatic payments from credit cards via merchant gateway;

Since v.4.02

1. In the domain home directory (/hsphere/local/home/<user_name>/<domain_name>/), the cgi-bin is created (if it wasn't created before);

2. the mivavm and mivavm.conf files are copied to this cgi-bin directory;

3. the libmivaconfig.so symlink to /hsphere/shared/miva/lib/config/3x.so is created there;

4. In the user home directory (/hsphere/local/home/<user_name>/), create the mivadata directory, and the <domain_name> subdirectory there, with the same name as the domain subdirectory in the user home directory.

5. In the Apache configuration file for this domain, the Miva compiled script MIME type is added:
   application/x-miva-compiled .mvc

Here,

- mivavm is a CGI application that executes complied Miva scripts;
- mivavm.conf is the Miva Empresa configuration file.

The mivavm.conf file may look like this:

mivaroot=&[document_root]
stdmodedatadir=/hsphere/local/home/miva/mivadata/miva.com
securityoptions=15
<COMMERCE-LIB METHOD= "UPSCost" LIBRARY="/hsphere/shared/miva/lib/commerce/upsrss.so">
<COMMERCE-LIB METHOD= "CyberCash" LIBRARY="/hsphere/shared/miva/lib/commerce/cybercash.so">
<COMMERCE-LIB METHOD= "ICS2" LIBRARY="/hsphere/shared/miva/lib/commerce/ics2.so">
<COMMERCE-LIB METHOD= "LinkPoint" LIBRARY="/hsphere/shared/miva/lib/commerce/linkpoint.so">
<COMMERCE-LIB METHOD= "AuthorizeNet" LIBRARY="/hsphere/shared/miva/lib/commerce/authnet.so">
<BUILTIN-LIB LIBRARY = "/hsphere/shared/miva/lib/builtins/crypto.so">
<BUILTIN-LIB LIBRARY = "/hsphere/shared/miva/lib/builtins/system.so">
<BUILTIN-LIB LIBRARY = "/hsphere/shared/miva/lib/builtins/file.so">
<BUILTIN-LIB LIBRARY = "/hsphere/shared/miva/lib/builtins/math.so">
<BUILTIN-LIB LIBRARY = "/hsphere/shared/miva/lib/builtins/string.so">
<BUILTIN-LIB LIBRARY = "/hsphere/shared/miva/lib/builtins/time.so">
cadir=/hsphere/shared/miva/certs
openssl=/usr/lib/libssl.so
openssl_crypto=/usr/lib/libcrypto.so

where:

mivaroot is the Miva Web root directory, the same as the domain's DocumentRoot directory;
stdmodedatadir is a directory where Miva Empresa data is stored;
BUILTIN-LIB LIBRARY is a standard (built-in) library that contains basic system functions;
cadir is a directory with SSL certificates;
openssl is the path to the OpenSSL library;
openssl_crypto is the path to encryption libraries;

Miva Empresa On Windows Servers

During Miva Empresa installation on a Windows server for a certain domain, all domain settings are applied to IIS configuration by changing registy keys.

For this domain, the Miva script MIME types are added:
application/x-miva .mv for ME versions prior to 4.02;
application/x-miva-compiled .mvc for ME version 4.02 and higher;

II. Miva Merchant

Miva Merchant (MM) is an online store application developed by Miva Corporation. Miva Merchant is written in Miva Empresa script language and requires Miva Empresa to work.

Regardless of version, Miva Merchant is installed as follows:

1. A user activates Miva Merchant resource on his/her domain; upon the resource activation, a license is provided for this domain;

2. The Miva Merchant archive (e.g., Merchant-v4.19-bundle.tar.gz) is untarred in the domain home directory. Here, v4.19 is the MM version.

3. After the package is untarred, launch Miva Merchant Setup from Control Panel.

4. If setup is done successfully, the Merchant2 subdirectory appears in the mivadata directory. Here, you may run the admin.mvc script (or admin.mv for ME earlier than 4.02) in your browser:

   This URL is not accessible before the setup.