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 4 Jahren

System Requirements Version 2020.2

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

A pre-installed database

A pre-installed database software is prerequisite for a CURSOR-CRM installation. The database structure (tables, indices, etc.) will be uploaded in the form of a database dump. DB parameter configuration is done beforehand in agreement with the customer or during the on-site installation. Some database systems furthermore offer the option of providing the database software in the form of OEM licenses; please confirm such cases with CURSOR consultants. The following releases should be used for the respective DB systems: ■ Oracle: Version 19c, 18c or 12c (R2) with the latest patches ■ MS SQL server: Version 2019, 2017, 2016, 2014 or 2012 (optionally also "R2"); with the correspondingly latest Service Pack ■ For new installations, please use the latest supported version of MS SQL Server database. While Oracle can be implemented on the Windows platform, as well as Linux (e.g. SuSE Linux, Red Hat Linux) and Unix derivatives (e.g. IBM AIX, Sun Solaris), the MS SQL server is in general only available for the Windows platform. Final observations The Standard Edition of the database software is sufficient for a use of the application. If you have a large number of users, very large amounts of data or a general interest in enterprise features, you can consider using the Enterprise Edition. Two factors play an important role here: on the one hand, there is an automated tuning of the SQL run schedules and on the other, the existing hardware is optimally utilized for all routine database operations. That is where the above hardware recommendations come to their full effect. When using an Oracle database, the character set "WE8MSWIN1252" must be used. Unicode capability is ensured by the use of N data types. Latin1_General_CI_AS should be selected as the sort order for the MS SQL Server. Where a SQL server is used, a setup of the SNAPSHOT transaction level is required to prevent exclusive lock or deadlock. The "SQL server and Windows authentication mode" must be enabled as part of the server authentication configuration. 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). 9. 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! System Requirements | Author: Gebriyel Varli |Date: 14.10.2020 | 11

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 16.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: 14.10.2020 | 12

EVI

TINA

Aktuelles

Software Requirements System Crm