1. APPkey can realize the communication between programs through the process (or task) acting on the * * * data cache.

2. APPkey can realize data sharing through direct communication between programs.

3. APPkey can realize data sharing between applications through the database.

4. file transfer of APPkey can realize data sharing between applications by sending formatted files.

Extended information:

Note:

1. When defining message types, saving message types from the platform actually configures the configuration information of the message types into an xml file, and the storage address of the xml file is under the apphome directory. However, in order to successfully run on the web and find the defined message type, the corresponding xml file must be copied to the corresponding publishing directory of tomcat before it can be successfully loaded

Second, the xml file generated by the configuration information of the sending port should also be saved to the corresponding publishing directory of tomcat

Third, the adapter configuration cannot be directly added from the component configuration in the platform, and the adapter class is not stored in the xml file after configuration. Instead, it is configured in the extension point file in advance, and the eunmAdaptor method is switched when the platform starts to load all adapter classes from the extension point file.

fourth, the corresponding services are also configured in xml files, and the configuration files generated after the platform configuration are also copied to the corresponding publishing directory of tomcat to run successfully.

fifth, when configuring bis message type mapping information in the extension point file, tags with similar messages cannot be renamed, otherwise only the message type corresponding to the first duplicate tag can be loaded in the memory.