Search Engine: Elastic

Article ID: 113700, created on Apr 13, 2012, last review on Jul 23, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5


Provider registered Plesk Panel 10.x server in OBAS. Provider installed applications from APS catalog in Plesk and configured them as available for customers.

A customer with Plesk Domain/Client subscription logged into their OBAS Control Panel in hope to install applications which Provider imported in Plesk. However, customer does not see some applications in control panel under System > Hosting Management > Applications > All Available Applications despite of the fact that Provider imported applications and marked them as available for customers.


The customer does not see applications in OBAS CP because they are not included into their subscription in OBAS.

After Plesk Panel server is registered in OBAS, OBAS is considered as a management tool for Plesk. All APS applications are resources which should be sold from OBAS.


To make applications available in OBAS CP Provider has to add them in hosting plan the customer's subscription is based on and upgrade subscription to the latest version of the plan. Thus, applications will be available it the customer subscription and customer will be able to add them into their subscription (if application is not marked as included into hosting plan) and manage applications in OBAS control panel.

Provider may add applications into hosting plan in OBAS PCC under Top > Billing Director > Product Manager > Hosting Plans > select plan > Applications.

If applications in question are not listed there it means they should be registered first in OBAS PCC:

  • Go Top > Service Director > Plesk Manager > Applications
  • Click the button Get Site Applications from Plesk Nodes
  • Select the needed applications
  • Click the button Register Selected Site Applications Then, after hosting plan is adjusted customers' subscriptions may be upgraded to the latest version of plan on the tab Subscriptions in the hosting plan properties.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF