Knowledge base: Apia 
|
Language: English
|
History
|
 |
|
 |
|
|
|
 Aspects to consider when using ACM
Different items that must be considered when exporting/importing with Apia Configuration Manager in order to follow the procedure properly.
Process status in user queries
GENERIC PROCESS VIEW view is modified so that it contains information on the status of processes instances.
Apia compatibility sheet
Different elements that are compatible with Apia are described, as well as the different requirements that are necessary to run Apia, forthe Server as well as for the client.
Shutdown threads started by Apia
Apia's behavior is modified to hear notifications of context shutdown sent by Web Server, allowing to stop all running threads and performing the actions necessary to stop the system.
Requested columns for "User's queries"
Views' requirements to generate any type of "User's queries" are detailed.
MySQL support in ApiaConfigurationManager
In ApiaConfigurationManager's new release, 1.8.0, support for import and export Apia databases in MySQL has been implemented.
Parameter to implement database by API
Allowing access through API Java programming to a method that allows determining on which database Apia is being run.
Requirements to install and/or update Apia
Requirements needed to perform an installation and/or update of Apia in any database engine supported by Apia, at a database level, are detailed.
Methods to obtain information of relations between entities by API
com.dogma.busClass.object.def.EntityDef class is modified to obtain information on the entities related to a particular entity.
Entity instance data in Apia's views
GENERIC PROCESS VIEW and GENERIC PROCESS MONITOR VIEW views native of Apia are modified, to include information on entity instances.
|
|
||||||||||||||||||
