Hier finden Sie Anwenderberichte und Informationsmaterial rund um die CRM-Lösungen der CURSOR Software AG.
CURSOR ist seit 30 Jahren auf Software und Beratung für das Kunden- und Geschäftsprozessmanagement – CRM und BPM – spezialisiert. Mit Softwareentwicklung, Beratung, Softwareeinführung, Schulung und Support erhalten Sie ein umfassendes Leistungsspektrum aus einer Hand. Herausragendes Merkmal ist die Flexibilität der Anwendungen: Branchenspezifische und individuelle Anforderungen werden exakt abgebildet, Anpassungen können jederzeit umgesetzt werden.
Unternehmen der Energiewirtschaft (Produkte: EVI für Energieversorger, Stadtwerke und Energiedienstleister und TINA für Netzbetreiber), Banken und Finanzdienstleister sowie Dienstleistungs- und Industrieunternehmen (Produkte: CURSOR-CRM Web und CURSOR-CRM) profitieren so von exakt an ihren Anforderungen ausgerichteten Geschäftsprozessen.
8. Application server software Our applications are developed in such a way as to allow the use of basically any application server that complies with the Java EE specification. However, he full functional scope can currently only be guaranteed for the following product: ■ JBoss EAP 7.2 (currently: 7.2.4) JBoss EAP 7.2 is delivered with active SSL encryption. In the release version, a self-signed certificate is used that is classified as insecure by the Internet browser, for example. => It is therefore required to use a customer-specific valid certificate! Background: Our systems use secure connection routes for cross-technology communication to comply with current IT standards. That requires e.g. the use of certificates to ensure the authenticity, integrity and encryption in all communication. While it used to be sufficient to work with a certificate provided by CURSOR, this is no longer permitted due to latest security guidelines. Third party systems now require the mandatory use of custom certification for safe communication. Our systems therefore also require the use of its own certificate. In newer versions the Rich Client login procedure was revised with the result that individual security improvements were implemented and the objective that the Single Sign-On process will be easier to implement in future. The change in login procedure has made the implementation of individual certificates a must due to security reasons. The following certificate files are required for server and client encryption: ■ An SSL certificate for server authentication, which references the server FQDN, on which the application server is installed ■ When creating the certificate, make sure that all DNS invocation names are included in the server certificate (public key), which are used for the CURSOR clients (Web Client, Rich Client, CURSOR app). ■ The private key associated with the SSL certificate ■ The certificates (public keys) provided by the certification authority and their parent certification authorities (where applicable) [root and intermedia CAs] (i.e.the certification chain must be complete) Windows Server (2019, 2016 or 2012) or one of the Linux variants SuSE Linux (for Enterprise Server 12.x - 64 bit and higher), Ubuntu Linux (for 18.x LTS - 64 bit and higher) or Red Hat Linux (for 7.x - 64 bit or higher) can be used as the OS platform. Other Linux derivatives should only be used after consultation! High Availability In the event that the host computer on which the application server VM is running fails, the virtualization platform (e.g. VMware) can automatically move the VM in question to another host that is still available in the virtualization cluster. The virtualization software intercepts this case directly. However, if the host machine is OK and the failure is within the application server VM itself (e.g. error in the Windows file system), a failover mechanism can be implemented using the on-board tools of the hypervisor cluster (e.g. Proactive High Availability with VMware) or via operating system components. At the operating system level, the application server VM could be made highly available via a Windows cluster, for example. In the event of a failure of the primary application server, the second application server VM, which is intended as a failover, is started up and the JBoss application server is started there, which is made known to the CURSOR-CRM clients via DNS entry. As part of this System Requirements | Author: Gebriyel Varli |Date: 22.10.2021 | 13
process, the productive application server VM would have to be regularly mirrored in the failover VM. Log files can be saved on the SAN if a nightly backup is not sufficient. Final observation The name of the server on which the JBoss application server is installed must be a valid domain name, i.e. the name must contain only letters, numbers and dashes, but no other characters like underscores. 9. Required port activations The following ports will be needed for CRM Client operations when a JBoss application server is used: ■ 18443 (web port https), ■ 19993 (JBoss Management https). Where port range 2 is preferred over e.g. port range 1, the port numbers will then be 28443 and 29993. The following database-side ports must be included for standard implementations: ■ Oracle: 1521 ■ MS SQL server: 1433 The following ports must be activated on the Groupware server for the server-side Groupware connection: ■ Mail reception: 143 (IMAP) or 993 (IMAPS with SSL) ■ Mail dispatch: 25 (SMTP) ■ Exchange calendar connection: 443 (https) 10. Report engine Report creation is based on the Open Source tool JasperReports. JasperReports is a Java library, which can be implemented in any project. The API allows the creation, manipulation and execution of report designs. The report engine is integrated on the application server, which facilitates and speeds up access to reporting data. A runtime installation on clients is not required. The client should, however, have an Acrobat Reader installation to view the reports supplied by the server in PDF format. Where other formats are required, the matching apps should also be installed. Designers of new reports must have access to the REPORT database scheme, which should be implemented either on the central database server or on another computer that is accessible for report designers (poss. based on the free Express Edition). A CURSOR-CRM client and the named access (via JDBC) to the REPORT database/instance must also be provided. System Requirements | Author: Gebriyel Varli |Date: 22.10.2021 | 14