Miva Empresa Virtual Machine on my UNIX/Linux server
Posted by - NA -, Last modified by Wayne Smith on 13 June 2018 09:54 PM




How do I upgrade the Miva Empresa Virtual Machine on my UNIX/Linux server?


Upgrading Miva Empresa Virtual Machine on UNIX/Linux servers is usually simple. Please follow these steps:

1. Read the release notes for the latest release of Miva Empresa. Check these to see if there are any settings that may effect your installation or server OS. Release notes can be found at: CLICK HERE

2. Once you have read the release notes, download the Miva Empresa Virtual Machine distribution from the Miva Corporation FTP Site. You should have the FTP information from when you originally purchased the engine from Miva.

If you do not have this information, please contact Miva Technical Support. Include your Miva Empresa Virtual Machine license number. Once validated, we will supply you with the download information.

3. You may FTP using your Local Machine, or right from a TelNet/SSH session on the server. The FTP site will include a separate folder for each different operating system support by Miva. Open the folder that applies to your system. Each folder may contain a different packaging format; download the appropriate file. Save the files in a temporary location on your local machine, or on the server.


4. Expand the package in the temporary directory where it was downloaded. It will create a folder: "mivavm-v4.xx" which, in turn, contain the file(s) necessary for the upgrade.


5. Locate the "cgi-bin" subdirectory. It will contain a file: "mivavm-4.xx " (4.xx = version number). This is the Miva Empresa Virtual Machine binary.

6. Also, in the unpackaged distribution folder, locate the "lib" subdirectory. It will contain a folder: "builtins". This is the Builtins directory that contains libraries for the Miva Empresa Virtual Machine. This folder, and it's contents, will need to be uploaded to the server, along with the "mivavm-v4.xx" file.

7. In the same "lib" subdirectory, you will also see a folder called "config". Inside of this folder are two library files: "3x.so" and "env.so" . Upload both of these libraries to the same temporary folder as the "builtins" files and the "mivavm-v4.xx " file.

8. If the files are not already uploaded to the server, upload them to a temporary directory. Once uploaded on the server, rename the "mivavm-v4.xx" file to just "mivavm ":

mv mivavm-4.xx mivavm

9. Change to the ROOT User.

10. Then, copy this file to the location in which it will be run from and where the old Miva Binary is:
o Server-Safe Mode: The Miva Empresa Virtual Machine binary is run from the Global CGI-Bin. Once you have copied the file, reset the permissions and ownerships:

chmod 755 mivavm
o Standard Mode: The Miva Empresa Virtual Machine binary is run from each site's Individual CGI-Bin. Once you have copied the file, reset the permissions and ownerships:

chmod 755 mivavm
chown USER mivavm (USER = the user that owns most of the files, including Miva Merchant program and data files.)

11. Locate the Builtins directory on your server. It can be in a number of places, so it is best to look for where it is specified in the Miva Empresa Virtual Machine Configuration files.

o If using a mivavm.conf: Look in this file for six tags that start with . There will be a path in these tags to the location of the Builtins directory.
o If using the SetEnv tags in httpd.conf: Look in this file for the SetEnv MvCONFIG_DIR_BUILTIN tag. This will have the path to the Builtins directory.

12. Once the Builtins directory is located, overwrite the existing directory with the one from the distribution file.


13. Next, you need to determine which of the two configuration libraries, "3x.so" or "env.so", you are using. If you are using a mivavm.conf file for the Miva Empresa Virtual Machine configuration, then you are using the "3x.so".


If you are using the SetEnv tags in the httpd.conf, then you are using the "env.so". Once you've determined which library you are using, rename it to libmivaconfig.so and place it in the cgi-bin. This should overwrite the existing one.

14. Test the installation by executing a Miva Script on the server or by logging into your Miva Merchant administration.

Please Note: If you are using a separate Miva Binary for the SECURE server, you will need to perform this same upgrade for that file as well. You will not need a duplicate Builtins directory, though.


For more information on Installing Miva Empresa Virtual Machine on a UNIX/Linux server, please see the documentation located at: CLICK HERE

 Select the appropriate document for your Server operating system.

(229 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below. This is required to prevent automated registrations and form submissions.

Help Desk Software by Kayako support.miva.com/supportsuite/index.php?