Use this window to specify the interaction between the KANA Response Server and the KANA Response database. You can view information and certificates and set parameters for the partition in which you are working. You can make changes to the entries on this page. To display this window, click the Partition icon in System Administration.
This window has the following sections:
The partition name, primary and KAB nodes, and database information including database host, port, name, user, and type, are all listed here. You cannot make any changes to this information. This information is stored in KANA Response's system configuration file.
The partition-specific certificate number is listed here, followed by the maximum number of departments, licensed products, and maximum number of concurrent users allowed by your certificate. The certification number is specified in KANA Response's system configuration file.
This is to remove the customer information completely. With the given email address, customer information will be pulled and application will execute a procedure to make sure that the customer information is deleted completely from the database.
Debug for Transfer Mail To Inbox |
Indicates whether debug will be written to the logs, for the transfer process of messages in to a user's inbox. |
Debug for State Manager |
Indicates whether debug will be written to the logs by the State Manager process. |
Debug download of message |
Indicates whether debug will be written to the logs, for the download of message process. |
Debug for Javamail download of messages from POP server |
Indicates whether debug will be written to the logs for Javamail message downloads from a POP server. |
Debug Add request and Wait for Response Errors |
Indicates whether debug will be written to the logs when Add request and Wait for Response Errors are encountered by Response. |
KANA LDAP is enabled |
Indicates LDAP is enabled for the partition or not |
KANA LDAP Authorization is enabled |
Indicates LDAP authorization is needed for LDAP communication or not |
KANA LDAP is Read only
|
Indicates KANA LDAP API is read only |
KANA should create LDAP object if they do not exist |
Indicates whether Response server create Users and Groups in LDAP on Save if they do not exist |
Dummy password to be used by KANA LDAP |
KANA LDAP dummy password stored in KC_KANAUSER |
Kana stores a dummy password in response database instead of real password. Real password is in LDAP |
Indicates whether Kana stores a dummy password in response database instead of real password.
If LDAP is enabled KANA should store dummy password in KC_KANAUSER table |
KANA LDAP is using MD5 Encryption |
Indicates KANA LDAP is using MD5 algorithm for encryption |
Enable HTML Editor in Admin Client |
Indicates HTML Editor is enabled for Admin Client |
Logging level |
You can adjust the logging level (Brief, Detailed, or Very Detailed). Setting the logging level to Detailed or Very Detailed can result in a large number of log files requiring significant disk space. Setting the logging level to Brief is usually sufficient. Using the Very Detailed logging level may affect system performance, so only use it for short periods of time to help troubleshoot a specific issue. The directory where your server log files are saved to depends on your install. By default, they are saved in Program Files\KANA\Response Server\shareddir\logs. |
Embedded Browser |
Client applications display portals or integrated components Response Live, IQ Knowledge using Java Embedded browsers JDIC,Native Swing. Clients can be configured to use either JDIC, Native Swing. For JDIC, it uses Internet Explorer only. For Native Swing, the Embedded browser can be configured as Internet Explorer or Mozilla or Webkit. |
Message custom field |
This option provides system-wide control over whether KANA Response users can edit message custom field data. When you select this option, KANA Response adds the Edit Custom Fields icon to the Incoming Message or Contact Record pane of the Outgoing Message window. Users can click this icon and edit information in custom fields for the message. |
Message custom field (completion) |
This option provides system wide control over whether KANA users with administrator privileges can view and edit custom fields on a completed message. When Enable editing is checked, administrators can review and edit messages with custom fields after the messages are sent. |
Disable content editing |
This option prevents content from being added on the Response server. When you select this option, KANA Response disables all the Create, Save, and Delete buttons in the Content Administration windows for all the entities such as users, e-mail queues, rules, categories, address book, standard phrases, acknowledgements, Response templates, and custom fields. |
Universal History URLs |
Enter the URLs for the universal history. To see the email sent from Connect, enter http://servername:port/kana/connect/resp/messagesxml.jsp |
Smart URL |
URL used to execute SmartURL macro for IQ server. |
Chat Implementation |
Choose the chat implementation integrated with Response. |
Chat Agent URL |
Required for SEM chat implementation only. URL that Agent will get in engage Tab. |
Chat URL |
URL that administrator will get in Chat Admin Tab. |
Allow chat users to logout in integrated environment |
This option provides system-wide control over whether chat users can logout in Response-Chat integrated environment |
Show partition name in Client window title |
This option determines whether to show partition name on Agent Mail Client, Content Administration Client, System Administration Client and Report Client. The default value is false, so it doesn't show partition name by default. |
Drop and reconnect DB connections after specified time in minutes |
Enter the maximum time that DB connection can be idle, thereafter the DB connection will be dropped and new connection is created 0 means - No maximum time for DB connection, so connection don't expire based on time. |
Full Text Indexer sleep time (in minutes) |
Interval to update Microsoft SQL Server Full Text Index (please note this will only display if Response is using a Microsoft SQL Server database). |
Query timeout (in seconds) |
Enter the maximum time that Find queries can run. This limits the impact that complex or wide-ranging Find operations have on the database server. Set this value to 0 if you do not want Find operations to time out. The maximum value for this parameter is 100000. Typical values range between 5 and 60 seconds. |
Default cache size |
It is recommended that you do not change the default cache settings unless you understand how a particular change may affect the KANA Response system. In general, the more memory your system has, the larger the cache sizes can be. |
Case cache size |
Enter the number of active cases to cache. This cache is not seeded with any cases when the server starts up. |
Consumer cache size |
Enter the number of consumers to cache including those associated with address book entries. This cache is seeded with all the Address Book consumers. |
E-mail cache size |
Enter the number of e-mail addresses to cache including those associated with Address Book entries. This cache is seeded with all the Address Book e-mail addresses. |
Message cache size |
Enter the number of active messages to cache (all but completed messages). This cache is not seeded. |
Preference cache size |
Enter the number of preferences to cache. Preferences are internal objects that are used to store the state users have the application in. This cache is not seeded. |
Raw text cache size |
Enter the number of message body texts to cache. This cache is not seeded. |
Raw text cache length |
Enter the maximum length of a message body that will be cached. |
NOTE: It is recommended that you do not change the default cache settings unless you understand how a particular change may affect the KANA Response system. In general, the more memory your system has, the larger the cache sizes can be.