...
- Oracle Java SE Development Kit 8 (JDK)
- Eclipse IDE
- Maven
- Wildfly Application Server 10v10.1 or later
- The CRM.COM Enterprise Archive (.ear file) - Provided by CRM.COM
- The CRM.COM Plugin SDK - Provided by CRM.COM
...
Open Eclipse IDE and import the .ear file into your workspace.
Expand title Importing .ear file - Extract CRM.COM Plugin SDK to a location in your filesystem where Wildfly Application Server has permission.
- Set the CRM_HOME system variable in Wildfly's configuration file to the location the SDK was extracted.
- Create your plugin projects
- Register your plugins by updating the plugins.xml file.
Mpconfig Properties File
mpconfig.properties file should be placed in the same directory as your custom project(s). This file is used to define the organisation database each custom project will run on.
To achieve that, you must use the following structure: <organisation_name>=<custom_project_directory_name>
Note that you should use the organisation(data source) name as defined on your Websphere/Wildfly server. Only one custom project per organisation can be defined.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
organisation1=custom1
organisation2=custom2 |
Plugins XML File
From R13 onwards you are advised to use plugins.xml instead of mpconfig.properties file. Just as mpconfig.properties file, plugins.xml file is used to define the organisation database each custom project will run on and should be placed in the same directory as your custom project(s).
This file gives you the ability to define more than one custom project per organisation database.
...
Plugins Descriptor
The plugins.xml file is used to register your plugins. Using this file, you can define your plugins and the organisations that your plugins will be enabled for.
Note that the organisationid should be set to the same value as the MPID field of the MASTERPARTNERS table of the Ecenter database.
For a full list of plugins file attributes, go to Plugins File Documentation.
...
More specifically, this project includes the Data object classes, the Business object classes , the UI (User interface) and process flow controllers.
A detailed explanation of the model layer can be found at Developing the Model layer, and a detailed explanation of the controller layer can be found at Developing the Controller layer.