Welcome to Atomikos
By purchasing, asking for and/or using customer support you agree to be bound by the following terms and conditions. You are not required to sign these terms, however if you do not agree to these conditions then you should not buy, ask for or use support. The general conditions (available at http://www.atomikos.com/Main/GeneralConditions) are an integral part of this document; if you agree to the present document then you are also assumed to agree to our general conditions. Should this document contain any clauses that are incompatible with the general conditions then the content of this document prevails.
An issue (or ticket) is defined as a problem caused by an ATOMIKOS product and experienced by you. A support incident is a single, specific, issue–based request for support. A request that raises multiple issues will generate the need for and use of multiple support incidents.
A bug is a special type of issue where the behavior of an ATOMIKOS product is different from what is advertised in our documentation.
An incident is considered closed (resolved) when any of the following occur:
The following table defines the severity and performance related to an issue.
Business days are counted as Monday to Friday.
Support is limited to 12 months from your purchase date of an Atomikos support subscription or until the date mentioned during purchase. A response to an issue/incident may consist of the acknowledgement by ATOMIKOS of your incident report, and may not necessarily resolve your incident.
ATOMIKOS warrants itself to be the legal owner of the software and to have the right to all royalties originating from it. Consequently, ATOMIKOS warrants that no part of the present contract interferes with the rights of any third party and that you may make full use of the license granted to you in the full knowledge of the above.
The software is protected by Belgian intellectual property laws, other intellectual property laws and international treaty provisions. The software and all associated intellectual rights remain either the exclusive property of ATOMIKOS or that of certain licensors to ATOMIKOS.
The intellectual property rights on the software and its documentation, any feedback provided by you as well as all copies, updates or possible extensions, including new functions that may be developed by ATOMIKOS for you, remain the sole property of ATOMIKOS, or of certain licensors to ATOMIKOS, unless otherwise agreed in writing.
Support is only given for issues that arise from the correct usage of the software, as specified in the ATOMIKOS documentation. In particular, not included are new features that you request, modifications to features that are not causing problems when using the software or ports to unsupported platforms or environments. When a newer version of the software is available then you should upgrade first before asking support. Also excluded is custom coding (i.e., writing customer-specific code outside the ATOMIKOS product boundaries).
All support is remote unless otherwise indicated in the formula you have purchased. Remote problem cases are to be reported by the named dedicated persons (who must be certified by Atomikos) as indicated in your support purchase order and emailed to email@example.com where they will be pulled into the Atomikos ticketing system.
You agree to supply the following minimum information for each issue:
Upon receipt, ATOMIKOS will generate a timestamp and ticket (number) to identify the problem. This ticket should be used by you for all further communications related to the case.
To speed up performance for production down support outside Atomikos business hours, you may optionally call +3215613055 after you have received your support ticket via email. However, this requires that you also guarantee 24/7 availability of a named dedicated contact person (who must be certified by Atomikos) on your end to follow up. Do not call us if this is not the case.
In no event will ATOMIKOS be liable for any damages whatsoever including – but not restricted to – lost revenue or profits or other direct, indirect, special, incidental, cover, or consequential damages, even if advised of the possibility of such damages, except to the extent applicable law, if any, provides otherwise.
This is the full and final agreement between you and ATOMIKOS, and it supersedes any promises, representations or agreements relating to the subject of this agreement. This agreement may be changed only if you and an ATOMIKOS authorized representative do so in writing. No inconsistent, additional, or pre-printed terms on your purchase order or other business form apply.
We don't want unhappy customers. If you are not satisfied then we may choose to (in certain cases at our discretion) refund all or part of your money. However, unfortunately, we can never refund in the following scenarios:
Redistribution of Atomikos ExtremeTransactions® and any bug fixes is restricted to OEM subscribers. Unless your subscription explicitly mentions an OEM nature, this does not apply to you. See TermsAndConditionsForSoftwareVendors for the detailed terms and conditions for OEM subscribers.
In general, we follow the semantic versioning strategy outlined in http://semver.org and with backward compatibility we mean compatibility at the Atomikos API and configuration level.
Release numbers are of the form x.y.z[Mi]:
Identified by x.y.z-SNAPSHOT, a snapshot release is meant for internal development purposes only, and definitely not for production use.
Example: 3.7.0-SNAPSHOT means an ongoing development build for what should become release 3.7 at some point in time.
A milestone release is any release identified by x.y.zMi (i.e., with Mi suffix). Milestone releases are not supported: we do not guarantee that maintenance releases will be published at any time. Rather, milestone releases represent public early access releases (beta releases).
Example: 3.7.0M2 indicates a milestone release for what should become release 3.7 at some point in time.
A release x.y becomes stable as soon as it is no longer made available as a milestone or snapshot release. In general, there will be one or more maintenance releases for each stable release.
Example: 3.5 is a stable release because we have released 3.5.0
By maintenance release, we mean any release identified by x.y.z.
Example: 3.5.1 is a maintenance release (usually fixing one or more bugs in the prior release 3.5.0).
The following table summarizes when our current and past releases expire in terms of support; from those dates on it is highly recommended that you upgrade to a newer release.
Extended support may optionally be available beyond the expiry dates (at a higher fee) - contact firstname.lastname@example.org to find out more.
Support in 3 StepsMake sure to plan carefully, to avoid delays: