Abstract: A plug-in framework is invoked within a plug-in, where the plug-in framework includes a software library configured to define, register, and configure plug-ins, where the plug-in includes a software module that extends or customizes functionality of a software application that is external to the plug-in, and where the plug-in includes a mapping name. A plug-in instance declaration is searched, by the plug-in framework, for a mapping that includes the mapping name, where the plug-in instance declaration is located within a plug-in file, and where the plug-in declaration comprises one or more mappings. When a mapping of the mapping name to the value is found, the value is returned, by the plug-in framework, to the plug-in based on the mapping. The plug-in framework also allows a plug-in provider to associate a plug-in with metadata.

Abstract: Applications, code modules, and other such software objects are able to be deployed and/or ported even when the corresponding configuration data is spread between a relational database management system (RDBMS) database and a meta data services (MDS) database, even where the configuration data is spread across any disparate databases. Configuration data also can be stored in a custom repository, such as a custom extensible markup language (XML) file. One approach involves detecting foreign keys, creating logical references to replace the foreign keys, and resolving the foreign keys to new references in the deployed environment by using the logical references. Code can be stored in the databases in order to help resolve the foreign keys.

Abstract: A plug-in framework is invoked within a plug-in, where the plug-in framework includes a software library configured to define, register, and configure plug-ins, where the plug-in includes a software module that extends or customizes functionality of a software application that is external to the plug-in, and where the plug-in includes a mapping name. A plug-in instance declaration is searched, by the plug-in framework, for a mapping that includes the mapping name, where the plug-in instance declaration is located within a plug-in file, and where the plug-in declaration comprises one or more mappings. When a mapping of the mapping name to the value is found, the value is returned, by the plug-in framework, to the plug-in based on the mapping. The plug-in framework also allows a plug-in provider to associate a plug-in with metadata.

Abstract: A method for a distributed deployment includes selecting a first feature module of an application to be deployed where the application includes multiple feature modules. A second feature module of an application to be deployed is selected. A first server and a second server to which to deploy the first selected feature module and the second selected feature module, respectively, are selected. A first archive file and a second archive file for the first selected feature module and the second selected feature module, respectively, are generated using deployment information, a deployment template for the application, and at least one feature module file. The first archive file contains a feature module not contained in the second archive file.

Abstract: Applications, code modules, and other such software objects are able to be deployed and/or ported even when the corresponding configuration data is spread between a relational database management system (RDBMS) database and a meta data services (MDS) database, even where the configuration data is spread across any disparate databases. Configuration data also can be stored in a custom repository, such as an custom extensible markup language (XML) file. One approach involves detecting foreign keys, creating logical references to replace the foreign keys, and resolving the foreign keys to new references in the deployed environment by using the logical references. Code can be stored in the databases in order to help resolve the foreign keys.

Abstract: A method for a distributed deployment includes selecting a first feature module of an application to be deployed where the application includes multiple feature modules. A second feature module of an application to be deployed is selected. A first server and a second server to which to deploy the first selected feature module and the second selected feature module, respectively, are selected. A first archive file and a second archive file for the first selected feature module and the second selected feature module, respectively, are generated using deployment information, a deployment template for the application, and at least one feature module file. The first archive file contains a feature module not contained in the second archive file.