Willkommen im CURSOR eKIOSK!

Hier finden Sie Anwenderberichte und Informationsmaterial rund um die CRM-Lösungen der CURSOR Software AG.

CURSOR ist seit mehr als 35 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.

Aufrufe
vor 2 Jahren

System Requirements Version 2021.1

  • Text
  • Crm
  • Software
  • Requirements
  • Cursor
System requirements for version 2021.1 of the CRM solutions by CURSOR Software AG

provided by CURSOR, this

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! Cluster Operation To ensure high availability, it is recommended to set up an Active Passive Cluster. The JBoss server can be made highly available via a Windows cluster. If the main application server fails, the second JBoss server, intended as failover, is started and notified to the CRM clients via DNS entry. With such a construct, the JBoss server would have to be mirrored regularly. If, due to high user numbers (significantly more than 1000 users), a JBoss cluster with load balancing is required, some requirements must be fulfilled, e.g: ■ Make sure that the ports for the TCP and UDP protocol are activated between the cluster nodes. ■ A separate JBoss server is used as load balancer. ■ The CURSOR-CRM application server cluster currently only works on the Windows platform, which means that all cluster nodes must be installed on Windows Server basis. ■ Database configuration: Make sure that the database parameter "processes" is scaled up to a matching value when using an Oracle database in cluster operation. In a two-node cluster with max. 300 sessions each in the JBoss session pool, the value for "processes" must be set to around 650. Final observations In case of doubt, the use of an Active Passive Cluster construct is preferable to a JBoss cluster. If a tendency towards Active Active Cluster exists, consultation is requested. 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. System Requirements | Author: Gebriyel Varli |Date: 27.04.2021 | 13

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 additional ports are required for an operation of the JBoss application server in an Active Active Cluster to allow the individual cluster nodes to establish a connection to each other: ■ 14712 (Transaction Recovery Manager), ■ 14713 (Transaction Status Manager), ■ 15520 (JBoss JGroups Service, UDP protocol), ■ 17600 (JBoss JGroups Service, TCP protocol). Where port range 2 is preferred over e.g. port range 1, the port numbers will then be 24712, 24713, 25520 and 27600. ■ 45688 (JBoss JGroups Multicast, UDP protocol), ■ 45700 (JBoss JGroups Multicast Ping, UDP protocol), ■ 23364 (JBoss Web LoadBalancer, UDP protocol). 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. Overview of JasperReports advantages: ■ Very good performance ■ Free (except the manuals) ■ Design templates in commonly used XML standard ■ Additionally contains complete Java API System Requirements | Author: Gebriyel Varli |Date: 27.04.2021 | 14

EVI

TINA

Aktuelles

Crm Software Requirements Cursor