Like all third party commercial products, Miva Empresa and Miva Merchant
are purchased and installed separately from H-Sphere.
Miva Merchant
requires Miva Empresa
for web server XML scripting, e-commerce and database capabilities.
- MivaMerchant starting from 4.14 requires Miva Empresa 4.02 and higher
(Virtual machines or 'mivavm').
- Supported starting from H-Sphere 2.3 RC4 and higher.
- MivaMerchant 4.12 and earlier can't work with MivaEmpresa Virtual machines
and require MivaEmpresa 3.91 or earlier ('miva.cgi' machines).
- Supported starting from H-Sphere 2.3 RC3 and higher.
- MivaMerchant 4.13 is not supported with H-Sphere!
This document explains how to install and configure Miva Empresa 4.02 and higher and Miva
Merchant 4.14 and higher to work with H-Sphere 2.3 RC4.
For extensive coverage of Miva products, please visit
www.miva.com/products.
Requirements:
- Installed and properly configured H-Sphere system.
- One valid Miva Empresa license.
- At least one valid Miva Merchant license.
Miva Empresa Installation
- Log into the web server as root.
- Change directory to /hsphere/shared/miva. If you don't have this directory,
create it first and set ownership to root:root and permissions to 755:
mkdir /hsphere/shared/miva
chown root:root /hsphere/shared/miva
chmod 755 /hsphere/shared/miva
- Download Miva virtual machine distribution file
from here
to /hsphere/shared/miva.
Linux: mivavm-v4.02-linux_glibc2.tar.gz
FreeBSD: mivavm-v4.06-freebsd_45.tar.gz
Here, mivavm is the product name, vX.XX its version name, linux_glibc2 is the Linux glibc2 package,
freebsd_45 is FreeBSD 4.5 operation system.
- Untar the unloaded file:
tar xfz <DistributionFileName>
- Move the content of the directory /mivavm-v4.02 to /hsphere/shared/miva:
mv mivavm-v4.02/* .
rm -rf mivavm-v4.02
- Move file cgi-bin/mivavm-v4.02 to directory /hsphere/shared/miva:
mv cgi-bin/mivavm-v4.02 mivavm
- If you need to use commerce libraries you got from Miva, copy them to directory lib/commerce,
then create links to them as follows:
ln -s /hsphere/shared/miva/lib/commerce/uupsrss-v4.02-linux-glibc2.so /hsphere/shared/miva/lib/commerce/uupsrss.so
ln -s /hsphere/shared/miva/lib/commerce/cybercash-v4.02-linux-glibc2.so /hsphere/shared/miva/lib/commerce/cybercash.so
ln -s /hsphere/shared/miva/lib/commerce/ics2-v4.02-linux-glibc2.so /hsphere/shared/miva/lib/commerce/ics2.so
ln -s /hsphere/shared/miva/lib/commerce/linkpoint-v4.02-linux-glibc2.so /hsphere/shared/miva/lib/commerce/linkpoint.so
ln -s /hsphere/shared/miva/lib/commerce/authnet-v4.02-linux-glibc2.so /hsphere/shared/miva/lib/commerce/authnet.so
- If you have more than one web server, repeat the above steps for all web servers where you want to have Miva installed.
Miva Merchant Installation
- Log into the web server as root.
- Copy file Merchant-v4.16-bundle.tar.gz to /hsphere/shared/miva
- Create a link to Merchant-v4.16-bundle.tar.gz:
ln -s /hsphere/shared/miva/Merchant-v4.16-bundle.tar.gz Merchant-bundle
- In the admin control panel, select Global Resources in the INFO menu
and make sure Miva Empresa Engine and MIVA Resource are enabled.
- Select L.Servers in the E.Manager menu, then click
the web server, and at the bottom of the page that appears select the version of Miva Merchant:
- If you have more than one web server, repeat the above steps for all web servers where you want to have Miva installed.
- Log into your admin Control Panel, select Miva Merchant Lic. in the 3rd party Tools
menu and enter your Miva Merchant licenses:
Notes:
- Login and Password for Miva admin interface are the same as for
FTP unless a user has activated the original Miva Merchant setup.
- If Miva is enabled, the user can't remove the cgi-bin
directory and CGI handler with .cgi extension in H-Sphere.
- mivadata and all its content is not removed
when Miva resource is removed.
- To make Miva work via SSL (htpps), an SSL certificate is required.
If a user cannot connect to Miva site by SSL (https://),
log into your Miva Merchant control panel via http, go to
the Domain Settings page -> Site configuration tab and check
secure URLs.
- You can install two instances of Miva on one logical server,
one version 4.12 and older, the other 4.14 or later.
- To enable Miva Merchant Follow Symlinks in mivaroot
and stddatadir, you need to add the following line into the miva.conf file:
securityoptions=15
How does it work?
- A user logs into the control panel and activates the Miva resource.
- H-Sphere finds an available license in the database and allocates it to this user.
- The cgi-bin and mivadata directories
are created inside the user's site directory, if only they haven't
been created earlier.
- miva.cgi is copied into the cgi-bin directory.
- miva.cgi is registered in the config file, in which the mivaroot
and mivadata variables are defined. mivaroot is configured
to be the same as DocumentRoot for Miva-enabled site. mivadata
is defined as the mivadata directory inside this user's site.
- Permissions to these directories along with their content
are changed.
- Now the user can activate Miva Merchant.
Miva Merchant is created using a web-based form containing the fields
required by Miva Merchant, though a user can activate the original
Miva Merchant installer by entering his site URL followed by
/cgi-bin/mivavm?/Merchant2/setup.mvc
or his site URL followed by
/Merchant2/setup.mvc.
|