Hier finden Sie Anwenderberichte und Informationsmaterial rund um die CRM-Lösungen der CURSOR Software AG.
CURSOR ist seit mehr als 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. Ob on-premise oder aus der CURSOR Cloud: 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 (Produkt: CURSOR-CRM) profitieren so von exakt an ihren Anforderungen ausgerichteten Geschäftsprozessen.
An implementation of interfaces with other applications is possible only if a procedural supplement exists for the SQL language that comes close to the functional scope of PL/SQL for Oracle or Transact SQL for MS SQL servers. We urgently recommend foregoing the use of database collectors. A database collector is a server, on which the databases of all kinds of software products are stored centrally. The usage of a DB collector is possible in principle, but can lead to global effects on all involved applications, as long as one (or more) of the databases are used for longer running, performance-heavy actions (e.g. batch interfaces, maintenance jobs for re-indexing, compression or DB statistics). 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.4 (currently: 7.4.4) JBoss EAP 7.4 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. Caution => 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. Therefore, our systems also require the use of their own certificate. In addition, the Rich Client login procedure was revised in newer versions 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 Subject Alternative Name property (cf. rfc5280) must be set or present correctly. 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) System Requirements | Author: Gebriyel Varli |Date: 14.10.2022 | 13
Our application server supports TLS versions 1.3 and 1.2. When it comes to cipher suites, we adhere to the Modern Compatibility specifications in the case of TLS 1.3 and the Intermediate Compatibility specifications in the case of TLS 1.2. See also https://wiki.mozilla.org/Security/Server_Side_TLS. Windows Server (2022, 2019, 2016 or 2012) or one of the Linux variants SuSE Linux (for Enterprise Server 12.x - 64 bit and higher), CentOS (for 9.x - 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 move the VM in question automatically to another host that is still available in the virtualization cluster. So, the virtualization software catches this case directly. If, however, the host machine is all right and the failure is within the application server VM itself (e.g. Windows file system failure), a failover mechanism can be provided via corresponding onboard means of the hypervisor cluster (e.g. Proactive High Availability at 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 case of a failure of the primary application server, the second application server VM, which is intended as failover, is booted and the JBoss application server is started there, which is made known to the CURSOR-CRM clients via DNS entry. As part of this process, the production application server VM would need to be regularly mirrored to the failover VM. Log files can be stored on the SAN if a nightly backup is not sufficient. Final note 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, only when monitoring or interested in metrics). 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) System Requirements | Author: Gebriyel Varli |Date: 14.10.2022 | 14