ASULPUNTO Magento unicenta opos integration extension Version 1.0.0

Transcription

1 ASULPUNTO Magento unicenta opos integration extension Version Magento unicenta opos Integration Extension Version Page 1

2 Table of Contents Requirements...3 A working copy of unicenta opos on Mysql database...3 Magento 1.7, Magento 1.8, Magento Valid Mysql connection between Magento database and unicenta opos database...3 Magento server's cron service active...3 Installation of the Extension...4 Get Extension key...4 Magento Admin...4 Clear the Magento Cache...4 Logoff from the Admin and login again...4 Configuration...5 Test the integraton...8 Test 1 Product Creation:...8 Test 2 Stock change in unicenta opos:...8 Test 3 Order in Magento:...8 Magento unicenta opos Integration Extension Version Page 2

3 Requirements A working copy of unicenta opos on Mysql database Install unicenta opos from Important: The unicenta table names must be all in uppercase It is very important that unicenta opos is installed on Mysql database or the Magento extension will not work. Magento 1.7, Magento 1.8, Magento 1.9 The extension has been tested on these versions of Magento. It might work on 1.5 or 1.6 but it was never tested. The extension has also been tested on the Enterprise editions, 1.12 and 1.13 Valid Mysql connection between Magento database and unicenta opos database Magento should be able to connect to the unicenta opos database. Make sure the connection is working. All installation problems are always due to an invalid connection. Possible reasons for the connection to fail are: Using invalid credentials Invalid user permissions on unicenta opos database. Example: The user is set as unicenta@ and Magento requires the user to be unicenta@% Using internal IP for a remote unicenta opos database. Example, Magento is on Shared Hosting while unicenta opos is installed on a shop's computer. Firewall or security on the servers where Magento or unicenta opos Mysql is installed Unicenta database table names must be in Uppercase. Sometimes when transferring a database dump from windows to unix/linux, you might loose the casing of the table names. Magento server's cron service active Magento's cron schedule should be working. The table in the Magento schema called cron_schedule is empty or has old entries, it means that the cron is not working. Refer to Magento forum on how to setup a cron job for Magento. You can transfer products and stock manually from the Admin module configuration. However, this is Magento unicenta opos Integration Extension Version Page 3

4 only suggested on small catalog as the server might time-out or run out of memory. The synchronisation support resume, so if it fails during the transfer, it will resume from the next record when it is activated again. Installation of the Extension Get Extension key Get an extension key from the Magento Community: Magento Admin Login to the Magento Admin. System / Magento Connect / Magento Connect Manager. Login again using your login and password. In the Install New Extensions paste the key you obtained. Click on Install. If there are any errors, it is a problem with the installation of Magento. Most likely there are problems with php version or with folder permissions. These problems have to be solved before attempting to install the extension. Clear the Magento Cache This can be done easily from the Magento Admin console. Logoff from the Admin and login again This will reset the Magento permissions and will allow you to configure unicenta opos extension. Magento unicenta opos Integration Extension Version Page 4

5 Configuration Login to Magento Admin System / Configuration Asulpunto / unicenta opos Unicenta Connection Configuration Section unicenta opos Hostname: This is the host name of the unicenta opos database. If unicenta opos database. If the database is installed on shared hosting, try to obtain this from the hosting admin panel or by contacting the hosting support. unicenta opos Database Name: The database name / schema name of the unicenta opos database. unicenta opos Database Login: The login name to the database of the unicenta opos database. unicenta opos Database Password: The password to the database of the unicenta opos database for the supplied user. Magento unicenta opos Integration Extension Version Page 5

6 Once database details are configured, Click on Save Click on Test Connection If you cannot 'Save' the details, probably there is an error with a required field. Normally this is Default Product Attribute Set in the Configuration section If there is an error try to troubleshoot using the following log file: [magentoinstallation]/var/log/asulpunto_unicentaopos.log Hint: After entering new connection details, press the Save button. The Test Connection button picks up only saved connection details. If the connection is successful, proceed to change the other configuration details and press on save. Configuration Section Stock Location: The location of the stock Magento will synchronise with. Currently this extension supports a single unicenta location, you have to select the location from the configuration of the extension. Default Product Attribute Set: The attribute set Magento product will be created in. Currently the extension supports only one attribute set. Note that this is a required attribute and you cannot save settings unless this is selected. Magento unicenta opos Integration Extension Version Page 6

7 Order Status for Stock Synchronisation: Only orders with this status will have stock deducted in unicenta. This prevents unpaid and unshipped orders from deducting stock from unicenta automatically. Synchronisation Section These buttons are useful if you want to trigger product or stock updated immediately without waiting for cron jobs to run. Note that the functionality of these buttons depends on you server configuration, you might get errors if you have low timeout / low memory and have a large catalog. Initially it is suggested to let the cron job import the products by itself as it has auto-resume functionality. You can use these buttons safely with a small test catalog. Advanced Section Last Order No: By default, the last order id from Magento is picked up. Only order ids larger than this saved number will be deduct stock from unicenta. This will prevent orders prior to the installation from reducing stock immediately when the extension is installed. Attribute Settings Section: In this section you select the behavior of the Name, Description, Short Description, Price. Update & Create: Will always update Magento whenever these attributes change in unicenta. Create Only: The attribute will change only when the product is created in unicenta. This is useful if you want to have a richer name / description / price in Magento from unicenta but you want it to be created with the unicenta defaults the first time. Never Transfer: Will leave the attribute blank and never update them. Magento does not have a default barcode attribute, you can choose which attribute unicenta will map to here. Magento unicenta opos Integration Extension Version Page 7

8 Test the integraton If the Test Connection was successful, you can proceed to test unicenta opos extension. Test 1 Product Creation: On unicenta opos, create a new product. Wait 10 minutes. Assuming cron is working properly, the product will created in Magento. Beware that Magento sometime takes longer to schedule new jobs, so the first time it might take longer than 10 minutes. Test 2 Stock change in unicenta opos: On unicenta opos Stock Diary, update the products stock. Assuming cron is working properly, the stock for the product will be reduced from Magento. Test 3 Order in Magento: Create an order on Magento. Invoice the order and ship it. Assuming cron is working properly, the stock for the product will be reduced from unicenta opos Stock Diary. Magento unicenta opos Integration Extension Version Page 8