...
The next step is to add your web plugins to the deployment assembly of the Crm project and your ejb plugins to the deployment assembly of the CrmEAR project as demonstrated below.
Cache Properties File
...
5.Deploy CRM.COM with plugins to Wildfly
The last step to run your plugins, is to deploy the application to your application server.
To do that, you should add the CrmEAR project to your Wildfly server by right-click on it and then start it.
That's it! As soon as your server is started, you can go to the login page of CRM.COM by using the following URL.
| Info | ||
|---|---|---|
| ||
Remember to always use the secure port of the Wildfly application server. CRM.COM works only over HTTPS for maximum security. |
CRM.COM Java Projects
The CRM.COM .ear consists of 3 main Java projects, Crm.war, CrmAPI.war and CrmEJB.jar.
For each one of these projects, there is a corresponding custom Java project available in sample projects.
Depending on the custom to be implemented, the corresponding custom project should be modified.
Crm.war
This project includes all the files and code required to implement the View layer such as:
- Pages
- Reports ( WebContent/WEB-INF/reports )
- Printouts ( WebContent/WEB-INF/printouts )
- Dashboard components ( WebContent/WEB-INF/dashboards )
A detailed explanation of the view layer can be found at Developing the View layer
CrmAPI.war
This project includes all the code required to implement the CRM.COM Web API, that is, all the controller classes and Java classes required to parse the data in Web API requests and construct the data included in Web API response.
CrmEJB.jar
This project includes all files and code required to implement the Model and Controller layer.
More specifically, this project includes the Data object classes, the Business object classes and Service (process) classes.
In addition, this project includes all the metadata required for the application to function correctly.
- Application metadata
- Module metadata
- Menu options metadata
- Entity metadata
- Entity fields metadata
- Variable metadata
- Label translations to specific languages
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
Property Files
Cache Properties File
CRM.COM uses Hibernate second-level caching to cache configuration records for maximum performance.
To enable this caching and set its parameters, you can use cache.properties file located in your CRM_HOME directory.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
#enable/disable caching - true/false
enabled=true
#multicast address | multicast host name
multicastGroupAddress=224.0.0.251
#Multicast port
multicastGroupPort=4446
#0-255
#0 is restricted to the same host
#1 is restricted to the same subnet
#32 is restricted to the same site
#64 is restricted to the same region
#128 is restricted to the same continent
#255 is unrestricted
#The default value in Java is 1, which propagates to the same subnet. Change the timeToLive property to restrict or expand propagation.
timeToLive=1
#the hostname or IP of the interface to be used for sending and receiving multicast packets
hostName=cyn1lnx007
#Mandatory - the port the listener listens on.
port=40001
#Optional - the number of seconds client sockets will wait when sending messages to this listener until they give up. By default this is 2000ms.
socketTimeoutMillis=2000 |
CRM.COM Java Projects
The CRM.COM .ear consists of 3 main Java projects, Crm.war, CrmAPI.war and CrmEJB.jar.
For each one of these projects, there is a corresponding custom Java project available in sample projects.
Depending on the custom to be implemented, the corresponding custom project should be modified.
Crm.war
This project includes all the files and code required to implement the View layer such as:
- Pages
- Reports ( WebContent/WEB-INF/reports )
- Printouts ( WebContent/WEB-INF/printouts )
- Dashboard components ( WebContent/WEB-INF/dashboards )
A detailed explanation of the view layer can be found at Developing the View layer
CrmAPI.war
This project includes all the code required to implement the CRM.COM Web API, that is, all the controller classes and Java classes required to parse the data in Web API requests and construct the data included in Web API response.
CrmEJB.jar
This project includes all files and code required to implement the Model and Controller layer.
More specifically, this project includes the Data object classes, the Business object classes and Service (process) classes.
In addition, this project includes all the metadata required for the application to function correctly.
- Application metadata
- Module metadata
- Menu options metadata
- Entity metadata
- Entity fields metadata
- Variable metadata
- Label translations to specific languages
...