Article ID: 112906, created on Nov 28, 2011, last review on Oct 7, 2016

  • Applies to:
  • Operations Automation 5.5
  • Business Automation 5.5
  • Business Automation 5.4
  • Plesk Automation 11.5


Two kinds of APS applications are published in the Application Catalog on the website

  • Applications published by Odin
  • Applications published by application vendors

Applications published by Odin are fully supported by the Odin Support Team. This means problems related to application installation/removal/upgrades are handled by the Odin Support Team.

Applications not published by Odin are supported by the corresponding publisher (in many cases, the application's vendor). This means problems with application installation/removal/upgrades must be reported to the support team of the corresponding application vendor.

General questions about APS architecture or development should be forwarded to

How to find an APS application publisher

There are two ways to find an APS application publisher:

  1. Use the APS Application Catalog

    • Open the Application Catalog
    • Find the required APS package in the catalog and click on it
    • In the application properties, you will see the application Vendor and Publisher as in the screenshot below (in this case, the publisher is PinnacleCart): alttext
  2. Use the XML metafile "APP-META.xml" in the APS package:

    • Download the APS application package archive from the Application Catalog
    • Decompress it
    • Open the "APP-META.xml" file
    • Find the packager section of the file, which looks like this:

          <name xml:lang="en"></name>
          <homepage xml:lang="en"></homepage>
          <icon path="images/pinnacle-icon.png" />

In the example above, the application's publisher is PinnacleCart.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e 198398b282069eaf2d94a6af87dcb3ff 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07 210d017ddc3a076d22f0f865b1cf0730 33a70544d00d562bbc5b17762c4ed2b3 e0aff7830fa22f92062ee4db78133079

Email subscription for changes to this article
Save as PDF