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.
■ Database system Oracle or MS SQL Server (more information in chapter "Database system software") 2.7 Important hints The hardware and software equipment for installations with more than 800 users must be designed individually. The read cache must be activated (performance) and the write cache must be deactivated (database consistency) for installations with a separate hardware cache for read/write operations. The latter must always be activated for installations, where the caches are not separated. The above software components for database system and application server have proven effective with our customers, which is why installation and maintenance costs for this exact configuration is budgetable and therefore affordable. Alternatively, other database systems and application servers can be implemented based on platforms other than those listed above (see chapter "Database system software" and "Application server software"). That will, however, mean higher installation and maintenance costs, and specifically for the provision of interface programs for the integration of other applications. The above hardware requirement applies exclusively for the operation of applications from our Javabased product line. The hardware equipment must be relevantly adjusted if other products will be installed on one of the servers. That applies specifically for installations in virtual environments, where the resources listed above must have a dedicated assignment to the relevant VM. The CPU component is a main concern here, because the hardware emulation process can reduce CPU performance in a virtual environment by up to 25%. It has proven advantageous to run the VMs for the database system and application server on one and the same host in a virtual environment. The latency of a network line between the database server and the JBoss application server should not exceed 1 ms, which is why both servers must be located in the same network segment. It can happen that the server’s CPU may fail to cycle up correctly, which would then negatively impact system performance. Enabling the Windows power option "High Performance" will help with that. This doesn't, however, apply for virtual environments, because there the cycle rate is at 100%. For more information on his topic, please see https://support.microsoft.com/en-us/kb/2207548. In the following, we will have a look at the example "topology 11 to 75 users" and the main storage requirement of 16-24 GB on the server: ■ Approximately 100 MB will be needed for users on the application server for Rich Clients and around 130 MB per user on the Web Client. Since JBoss will use another 500 MB heap internally, a heap storage requirement of another approx. 3.5 GB will be needed for 30 parallel Rich Client users. ■ ■ Code cache, Metaspace and JVM will need another approx. 700 MB internally, so that this results in a total of 4.2 GB. A minimum of 5 GB is generally recommended for operating a JBoss application server. ■ In this topology, a main storage allowance of 4-5 GB must be reserved for the database server process. ■ In a server-based CTI integration, the CTI application server will require min. 2 GB of storage space (see chapter "CTI interface"). Another application server may have to be added for larger reporting tasks (CSV export, serial letters, serial mails, Excel and mass data evaluations), which will be configured with a heap storage between System Requirements | Author: Gebriyel Varli |Date: 22.10.2021 | 7
4 and 8 GB depending on data volumes. For reasons of system load, it is recommended to install this additional application server on a separate machine (or VM). Notes In the course of a multi-system landscape, it is recommended that not only the productive system, but also the development and test / acceptance system be well equipped (e.g. "topology 11 to 75 users"), since user training courses or the acceptance of new software version take place on test systems in terms of quality and performance. 3. File server Application documents, their backups and thumbnails for the document preview are stored on the file server. For several years of operation without archiving, usually >= 200 GB of free hard disk space is required. Here, a similar load behavior as that of the application and database servers applies, but the number of accesses is not as important as is the size of the transferred documents. The network structure in particular will therefore be affected by the volume of data, where higher user numbers are involved; a system with 500-600 users might therefore benefit from a very high performance file server. The application server could also act as file server for the topologies described above. In this case, free hard disk space (>= 200 GB) would have to be made available on the application server. Where a separate server is implemented, it should be equipped as follows: ■ 4 CPU cores with min. 2 GHz ■ >= 4 GB RAM ■ SAS hardware RAID 5/10 ■ Note: A Solid State Disk (SSD) is recommended for storing the full-text search index. ■ Volume by data quantity: >= 200 GB (for application documents, document backups, thumbnails for document previews and full-text search index, for operation over several years without archiving) ■ Network connection to the application server: >= 1 GBit/s (LAN) ■ Windows server 2012 R2, 2016 or 2019 (each in Standard Edition) 4. Clients 4.1 Web Client ■ The internet browser will require a main storage between 300 and 500 MB depending on version and system customizing. ■ Network connection (per client) to the application server: Download >= 1.5 MBit/s, Upload >= 750 KBit/s ■ >= 500 MB hard disk space for downloaded documents ■ Java Runtime is not required System Requirements | Author: Gebriyel Varli |Date: 22.10.2021 | 8