Article ID: 111176, created on Apr 25, 2011, last review on Jun 3, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5

Question

  • Where can I find a list of supported plug-ins?
  • Does Odin support custom plug-ins?
  • Whom should I contact to get support for OBAS plug-ins?

Answer

Odin supports plug-ins developed by Odin only, custom or developed by third party plug-ins are not supported.

How do I determine if the plug-in is developed by Odin?

Supported plug-in types

Plugin type Path in Provider Control Center to manage plug-in
Domain plug-ins Top > Service Director > Domain Manager > Plug-ins
Payment plug-ins Top > Commerce Director > Online Payments > Payment Plug-ins Top > Commerce Director > Bank Transfers > Payment Plug-ins
Anti-Fraud plug-ins Top > Commerce Director > Anti-Fraud Manager > Anti-Fraud Plug-ins
Accounting plug-ins Top > Billing Director > Accounting Manager > Plug-ins Activation
License plug-ins Top > Service Director > License Manager > Plug-ins
SSL Certificate plug-ins Top > Service Director > SSL Manager > Plug-ins

There are two ways to determine whether the plug-ins was developed by Odin or not:

  1. The following link refers to a list of supported plug-ins shipped with OBAS.

  2. Another way is to check code of the plug-in on the OBAS server as follows:

    2.1. Login to the OBAS server via SSH, taking into account that you saw that plug-in is called “dnsbe” in PCC

    2.2. Retrieve exact name of plug-in from OBAS database:

    [root@obas ~]# mysql aspc -e "select template\_id from plugin where name='dnsbe'"
     +-------------+
     | template_id |
     +-------------+
     | DNSbe       |
     +-------------+
    

    2.3. All plug-ins are located in the folder /usr/lib/perl5/site_perl/5.8.8/HSPC/MT/Plugin on OBAS server in corresponding subfolders named by plug-in type:

    # ll /usr/lib/perl5/site_perl/5.8.8/HSPC/MT/Plugin
     total 5
     drwxr-xr-x 7 root root 1024 Jun  7 05:28 DM
     drwxr-xr-x 3 root root 1024 Mar  1 08:39 LM
     drwxr-xr-x 2 root root 1024 Apr 20 07:51 PM
     drwxr-xr-x 3 root root 1024 Apr 20 07:51 PP
     drwxr-xr-x 4 root root 1024 Mar  1 08:40 SSL
    

    Find the Perl module which corresponds to the plug-in:

     [root@obas ~]# locate DNSbe.pm
     /usr/lib/perl5/site\_perl/5.8.8/HSPC/MT/Plugin/DM/DNSbe.pm
     /usr/lib/perl5/site\_perl/5.8.8/HSPC/Plugin/DM/DNSbe.pm
    

    2.4. Find build information about RPM package the file with .pm extension belongs to using these commands:

     [root@obas ~]# rpm -qf /usr/lib/perl5/site\_perl/5.8.8/HSPC/MT/Plugin/DM/DNSbe.pm
     hspc-plugin-dm-dnsbe-4.1-49.swsoft
    
     [root@obas41beta ~]# rpm -qi hspc-plugin-dm-dnsbe-4.1-49.swsoft
     Name        : hspc-plugin-dm-dnsbe         Relocations: (not relocatable)
     Version     : 4.1                          Vendor: SWsoft
     Release     : 49.swsoft                    Build Date: Fri 13 May 2011 08:26:06 PM MSD
     Install Date: Mon 16 May 2011 03:55:18 PM MSD      Build Host: 30.c.sw.ru
     Group       : Applications/System          Source RPM: hspc-plugin-dm-dnsbe-4.1-49.swsoft.src.rpm
     Size        : 68910                        License: Parallels
     Signature   : (none)
    Packager    : SWsoft Linux Team <support@sw.com.sg>
     Summary     : Parallels Business Automation - Standard Domain Registration: DNS.be Plug-in
     Description :
     Parallels Business Automation - Standard Domain Registration: DNS.be Plug-in
    

    Pay attention to Vendor, Packager and Build Host. If the vendor value is SWsoft it means the plug-in is developed by Odin.

    2.5. Provider might modify plug-in source code (it is not crypted), so it is needed to check if RPM package was modified:

    # rpm -V hspc-plugin-dm-dnsbe-4.1-49.swsoft
    

    If you see plug-in vendor is SWSoft and RPM package was not modified then Provider may contact Odin for support.

Important: In other cases the plug-in is developed by third party company and is not supported by Odin.

Search Words

domain plug-in

payment plug-in

plug-ins list

tls 1.2

how to install a plug-in

400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75

Email subscription for changes to this article
Save as PDF