If your company has an order number 500+ it is possible to install a standalone mail server. Advantages of this server:
- If you do not establish the server, there is a posibility that the program will have a slower operation.
- Uploading updates and corrections within the working hours with by prior arrangement.
- Read-only access to the base.
The service includes :
- Renting and maintaining a server at Amazon WEB services (AWB)
- Data recording in two seperate databases and daily backup to two seperate providers
- Daily instalation of new versions of MetaKocka
- Performance monitoring
A standalone server in a separate region (Fail over)
If you use a shared MK server or a standalone server, your data is already protected by the paraller operationa enabled by the Amazon AWS evironment. All data and files are stored in seperate data centers, which are physically seperated from each other, but only these are located within one so-called region - Frankfurt, Ireland, Milano, Paris etc. If there are problems with the operation in the entire region, this will also effect the operation of the application.
If your bussiness processes require even greater operational availability. We can place the stand-alone server for you in a seperate region. For example, if the primary is now Frankfurt, then the server would still be in the Milan region. In this way, in the event of a majon autage (AWS) infrastructure and an unknown time to restore the primary evironment, we can switch the application to a new invironment, which will have practically all the data from the previous evironment. And you will be able to continue your work without interruption.
Common questions - Standalone server
If we have a standalone server, do we still have to pay the subscription of MetaKocka?
Yes, the standalone server is not included in MetaKocka subscription. They are two seperate items to pay.
Is it possible to install the application into our server?
No, this is not possible, the service is modified to working in the use of AWS Amazon, which are key in the operation of the application.
What happens to the data in the existing MetaKocka account?
All the data is transfered (in the transfer - around 4h) MetaKocka is not available for your account, you continue to proceed as normally.
What happens to orders and notifications during data transfer (by failure of MetaKocka)?
- Orders from online stores: if you have a set order frequency (say every hour), then they will be transferred later. Otherwise, it is necessary to transfer orders manually at each store,
- Orders via the API interface: the interface is not available, so the customer must ensure that orders are not sent during the transfer and that only these are sent again after a successful transfer,
- Request via the API interface: the interface is not available during the download,
- Mandrill email and SMS messages: if you have configured scenarios, e.g. "send e-mail / SMS 2 hours after receiving the order" and the order was just written before the migration, the e-mail / SMS messages will be sent accordingly after the migration with a time delay. However, they will be sent.
If we transfer a MetaKocka account to a standalone server, is it possible to transfer back to a shared server?
No, it is not possible to transfer back, for technical reasons.
What happend to the sand-alone server, if we stop working for the company?
Za razliko od običajne MetaKocke (kjer imate še vedno dostop do podatkov), se v tem primeru dogovorimo za plačilo minimalnega mesečnega zneska, ki nam pokrije najem minimalne AWS instance in vzdrževanje, da aplikacija lahko še deluje. In tako aplikacija ostane še aktivna in lahko dostopate do podatkov. Vendar se ne izvajajo tehnične posodobitve ter se ne izvaja nameščanje novih verzij MetaKocka.
What happend to the stand-alone server, if I don't pay the monthly subscription invoice?
We turn off the server. The data still exists and are available again the next time the server is started.
We use MK API - is it necessary to change URL address and secret key?
Secret key can stay the same. URL address will definetly change. Now it has the form ''main.metakocka.si'', then it will have ''mycompany.metakocka.si''
We use connections to online stores. Is it necessary to change anything during the move?
No, in principle it is not necessary. Except in cases:
- the integration was done by an external company via an API interface. Then the above answer applies,
- Shopama stores. It is necessary to report new URLs.
We use connections to delivery services. Is it necessary to change anything during the move?
No, you don't need to change anything.
We use Mandrill connections to send emails. IS it necessary to change anything during the move?
Yes, Mandrill has a webhook URL and only that will change.
If I choose a standalone server in a separate region, can I stop the service after a while and just use the standalone service?
Yes, you can. In this case we charge you 4h additional work for canceling the server.
If I have a standalone server in a seperate region, can I use tha data base in the seperate region to read data?
Da, lahko nastavimo, da imate do te baze dostop in da izvajate branje podatkov. Na enaki način kot do samostojne naze. Yes, we can modify as much, so you have access to the server and perform data reading.
Is running a seperate server always faster than running on production?
No, it isn't as long as the production is not to busy, will work a lot faster than a seperate server. Because much more powerful servers and databases are available there.
But it will run consistently fast (because only the app for your app is running it)
Access the database
If you have an independent server, you can also access the database directly. The functionality is useful in cases where you want to preform additional analyzes on the data. The following restrictions must be taken into account.
- access is the so-called read-only and the data cannot be changed. As a result, the database cannot be used for any other operations or data storage,
- for the time being, access to external file storage (Amazon S3, logs, etc.) is not possible,
- the data is stored in a MySQL 5.7.x database,
- there is no public documentation for the data model. For the way to get certain data, it is best to send a more detailed description of the query to podpora@metakocka.si and we will answer you about the procedure / SQL statement.
- there is a list of useful SQL statements.
For access, a request must be sent to podpora@metakocka.si, where it is also necessary to indicate from which IP addresses access should be enabled. We will return your username / password.
Common questions - Database access
If MetaKocka changes the data model, will it also change on our layout? Will we be notified about this?
In the company, we upgrade the application daily and also install patches on all layouts. Which means your data model will change too. Unfortunatly, we currently have no mechanism to notify users who has access to the database.
