apsc database dependencies and descriptions of tables.
The following dumps for '
psa ' and '
apsc ' databases only contain records for one application. They were created in the following way: create a dump of the '
psa ' and '
apsc ' databases before and after application installation, then diff these dumps.
diff psa.sql_before psa.sql_after
diff apsc.sql_before apsc.sql_after
Contains information about all application resources:
urlPrefix, isSiteRoot, phpMinVersion
Information about application paths:
- application root
Information about databases
Information about database users
These two tables connect the '
Subscription ' and '
domains ' tables and the '
apsc.aps_registry_object ' table.
smb_apsInstances, smb_apsContexts, smb_serviceInstances, smb_apsMetas, smb_serviceEntryPoints, smb_servicePermissions, smb_userServicePermissions
These tables contain information about:
- The package from which the application was installed
- URL links to the CMS administrative interface, blogs, upload theme and upload plugin
- User permissions
Contains information about the package:
id, name, version, release, registryUid and others.
Contains information about the application:
registry_object_idof this application
package_idfrom which this application was installed
Contains the UID for applications, packages, application resources and creation time.
The resource UID connects (3 resource records for one application):
psa.apsResources(two records with pleskType = 'hosting' and 'urlMapping')
psa.apsResources(two records with pleskType = 'db' and 'db_user')
Contains information about this application (a CMS), made up of 5 records:
Two records with the same value. This connects the two
aps.resource . It is easy to find required APS resources by selecting the 3-4 lines after
aps.application in the
Contains a description of these resources:
Contains full information about the application package:
content_root_path , etc.
apsc.aps_package.id = psa.smb_apsPackages.id
Useful MySQL queries
package_name by the domain:
select app.id as application_id, regob.id as application_registry_object_id, app.package_id, pack.name as package_name
from apsc.aps_application app, apsc.aps_package pack, apsc.aps_registry_object regob
where regob.id = app.registry_object_id and
app.package_id = pack.id and
regob.uid = ( select conapp.registryApplicationId
from psa.apsContextsApplications conapp, psa.apsContexts cont, psa.domains dom
where cont.id=conapp.apsContextId and dom.id=cont.pleskId and dom.name like 'domain.tld');
Get all records that are present in the
psa.smb_apsInstances but which are absent in the
select smb_apsInstances.registryResourceId from smb_apsInstances left JOIN apsc.aps_registry_object on apsc.aps_registry_object.uid = smb_apsInstances.registryResourceId where apsc.aps_registry_object.uid is NULL;