Avaya Context Store Snap-in Release Notes
Release 3.0
Issue 1
August 2014
Page 1
Release Notes for Avaya Context Store Snap-in 3.0
Approved Software Combination
Version or
Approved
Combination
Product
Version
PLDS ID & Checksum
CSManager SVAR
3.0.0.0.145
ID: CS000000001
MD5 Sum 5a6061d96769e883851bf9bcb8dde8ae
CSRest SVAR
ID: CS000000002
3.0.0.0.145
MD5 Sum 1139dde968d3c66e5999664b9b6f3b40
CSScreenPop SVAR
ID: CS000000003
3.0.0.0.145
MD5 Sum e7a1e02dfaa2a2029211003cfe9c9e6e
CSNotifications SVAR
ID: CS000000004
3.0.0.0.145
CS Pluggable Data
Connector (PDC) JAR
CS SDK ZIP
ingensg-cs-pdc-plugin-1.45.1
CE Platform OVA
300010
CE Platform ISO
300010
ingensg-cs-sdk-zip-1.45.1-SDK
(for CE server upgrades)
System Manager OVA
6.3.0.8.5682-e50-64
System Manager patch
R6.3_FP4_SP9_4602474
MD5 Sum d4c6526425501b4e6a49bc551a199266
MD5 Sum 4798555bd67a7b2e654ab75f7b53f68a
MD5 Sum 7ada2ad670c056d7dc329e507fea7252
MD5 Sum 2ae0dd71342412c12e5c5fd5eba321fe
MD5 Sum 1fd3b0f7303e38ef8d67cfe666b199da
MD5 Sum 582af87e5f96acfcafe393968b3578c1
MD5 Sum fd774403b9942d1739c30845907df0e3
Collaboration Environment Interoperability
Avaya Aura Collaboration Environment 3.0 supports Context Store 3.0 GA software.
Please refer to the CE 3.0 documentation for platform information.
1.
2.
3.
4.
Go to support.avaya.com
Choose Documents
Enter Collaboration Environment in the product search field
Select the type of document you want and hit Search
Upgrade Compatibility and Sequence
It is not possible to upgrade from the Context Store Alpha or Beta versions to GA.
Page 2
Release Notes for Avaya Context Store Snap-in 3.0
Pre Install Steps
In addition to the setup steps documented in Context Store Guide the following setup instructions should be
completed before creating the Context Store cluster.
Configure the Datagrid Cluster Manager (DCM) Script
Before creating a Cluster, to prevent potential latency issues relating to the grid configuration, it is necessary to
update the /opt/Avaya/dcm/scripts/dcmFunctions.sh script on each CE Node in the cluster:
Remove the last variable, ${gsMaxConnPool}, from the following argument on Line 374 of the script:
export EXT_JAVA_OPTIONS=" ${gsRequestTimeout} ${gsConnectTimeout}
${gsInspectTimeout} ${gsMulticastEnabled} ${gsSecurityEnabled}
${gsDiscoveryPort} ${gsInitialUnicastDiscoveryPort} ${gsHttpPortStart}
${gsRegistryPort} ${gsLRMIBindPort} ${gsIPAddress} ${gsMaxConnPool}"
Updated argument:
export EXT_JAVA_OPTIONS=" ${gsRequestTimeout} ${gsConnectTimeout}
${gsInspectTimeout} ${gsMulticastEnabled} ${gsSecurityEnabled}
${gsDiscoveryPort} ${gsInitialUnicastDiscoveryPort} ${gsHttpPortStart}
${gsRegistryPort} ${gsLRMIBindPort} ${gsIPAddress}"
NB: If the Cluster already exists, it will be necessary to redeploy the Cluster for this change to take effect.
Page 3
Release Notes for Avaya Context Store Snap-in 3.0
Context Store: Known issues and workarounds
Please refer to the CE 3.0 documentation for known platform issues and workarounds.
1. Problem:
Workaround:
ESM fails to balance grid correctly when cluster member is missing/lost.
Restarting the ESM component will clear the exception state it’s in. This can be
achieved by killing the process of the container hosting the ESM component. ESM
will automatically be restarted in a new container.
 Login to all CE servers in the CS cluster as root user

Run the command ps –ef | grep ESM on each of the servers to find the
applicable server and process id.


Reference:
Keywords:
2. Problem:
Workaround:
Reference:
Keywords:
Page 4
Run the command kill –sigterm process_id on the applicable server
After the component has been restarted, find the applicable gs-esm.log file and
verify there are no 'Unhandled Exception' errors being logged
INGENSG-5447, GigaSpaces case 00009017
High Availability
Sensitive data cannot be updated or deleted via the Context Store PDC
There is no workaround available for this issue – a fix has been implemented for the
next release of Context Store.
Note, it is still possible to create data containing sensitive keys using the PDC – they
just can’t be modified or removed after creation.
INGENSG-5463
Pluggable Data Connector (PDC)
Release Notes for Avaya Context Store Snap-in 3.0
Solution: Known issues and workarounds
1. Problem:
Workaround:
Reference:
Keywords:
Page 5
Collaboration Designer SSO-based security policy conflicts with the certificate based
authentication used for other CE 3.0 snap-in services.
Incoming HTTP requests to Collaboration Designer from a business analyst browser
should NOT be challenged for a client certificate: the users authenticate with their
SMGR credentials.
For all other Collaboration Environment snap-ins services, their only means of
authentication is based on certificates. This means that they MUST have client
certificate challenge enabled.
For further information and workaround guidance please refer to the platform issue
number referenced below.
ZEPHYR-2729
Security, Collaboration Designer, Collaboration Environment
Release Notes for Avaya Context Store Snap-in 3.0
Post Install Steps
In addition to the setup steps documented in Context Store Guide the following setup instructions should be
completed post Snap-In installation.
Context Store Snap-In Services Log Configuration
It is necessary to verify and, if necessary, manually update the log4j.properties file to ensure adequate logs
are stored for all Context Store snap-ins. This is attributable to an intermittent CE defect (ZEPHYR-2559)
which will be fixed in the 3.0.1 patch release of CE.
Note: These updates should be done on all CE nodes in the cluster before starting any traffic.
1. Login to each CE node as root user
su sroot
2. Open the log4j properties for editing
vi /opt/Avaya/Common/conf/log4j.properties
3. Find the section containing the log configuration for Context Store snap-in services; this should exist
at the end of the configuration file (after the snap-ins have been installed)
4. For each snap-in, verify that MaxFileSize=100MB and MaxBackupIndex=200. If these values are
incorrect, update the numbers to the correct values
log4j.logger.CSManager=INFO, CSManager
log4j.additivity.CSManager=false
log4j.appender.CSManager.Threshold=INFO
log4j.appender.CSManager=org.apache.log4j.RollingFileAppender
log4j.appender.CSManager.File=/var/log/Avaya/services/CSManager/CSManager.log
log4j.appender.CSManager.Append=true
log4j.appender.CSManager.layout=org.apache.log4j.PatternLayout
log4j.appender.CSManager.layout.ConversionPattern=%d [%t] %c{2} %-4p - %m%n
log4j.appender.CSManager.MaxFileSize=100MB
log4j.appender.CSManager.MaxBackupIndex=200
log4j.logger.CSRest=INFO, CSRest
log4j.additivity.CSRest=false
log4j.appender.CSRest.Threshold=INFO
log4j.appender.CSRest=org.apache.log4j.RollingFileAppender
log4j.appender.CSRest.File=/var/log/Avaya/services/CSRest/CSRest.log
log4j.appender.CSRest.Append=true
log4j.appender.CSRest.layout=org.apache.log4j.PatternLayout
log4j.appender.CSRest.layout.ConversionPattern=%d [%t] %c{2} %-4p - %m%n
log4j.appender.CSRest.MaxFileSize=10MB [update this to 100MB]
log4j.appender.CSRest.MaxBackupIndex=10 [update this to 10]
5. Save the changes made to the log properties file
Page 6
Release Notes for Avaya Context Store Snap-in 3.0
External Data Mart Log Configuration
When the EDM feature is enabled, its log configuration file is only created on the server on which it is first
deployed. Is necessary to manually copy this file to the other two servers in the cluster to ensure this
configuration information is available on any server in the cluster to which this component may be moved.
1. Login to each CE node as root user
su sroot
2. Locate the following log configuration file used by EDM
/opt/Avaya/dcm/pu/conf/pu-log4j.properties
3. Create the /pu/conf/ directory structure on each of the other servers in the cluster
4. Copy the pu-log4j.properties file to the newly created /conf/ directory
Page 7
Release Notes for Avaya Context Store Snap-in 3.0
Configuration and Usage Recommendations
NB: Context Store snap-in services must be the only snap-in services deployed on your CE cluster for
the configuration recommendations below to hold true. The memory resources of the CE servers in
the cluster cannot be shared with any other services.
Host Recommendations
As with a full-scale deployment, the CE servers should be deployed as thick provisioned VMs and hyper
threading should be turned off on the host server.
Recommended Context Store space settings
If deploying Context Store on a CE Cluster with inadequate resources, the following settings must be
applied before the CSManager snap-in service is installed.
 The CS Reserved Memory Capacity Per Machine attribute should be lowered to free up extra
memory on the system. This sets the amount of memory that the grid is not allowed to use.The size
of the CS data grid should be modified in the Context Store Spaces list attribute as per the table
below. The total memory required by the grid must be less than the total memory available across all
the machines in the grid
CE Servers
Context Store Spaces list
*64GB x 3
16GB x 3
ContextStoreSpace,8,118,1|ContextStoreManagerSpace,1,2,1
ContextStoreSpace,4,24,1|ContextStoreManagerSpace,1,2,1
CS Reserved Memory
Capacity Per Machine
14
5
* This is the default configuration for the Context Store data grid – given for reference purposes
NB: Recommendations listed above are for a default CS deployment only i.e. EDM feature is not enabled.
 If you wish to enable the EDM feature, the memory for ContextStoreSpace (second number) must be
reduced by 8GB: ContextStoreSpace,8,110,1|ContextStoreManagerSpace,1,2,1
Total memory available across all CE servers in the cluster must be greater than
ContextStoreSpace memory
+ ContextStoreManagerSpace memory
+ (Reserved memory x Number of machines)
+ Mirror Service memory if applicable
Restrictions on a reduced deployment
Context store uses an in-memory data grid; if running on a small capacity cluster, system memory can get
used up very quickly. There are a number of important variable inputs which must considered 1. the number of requests submitted to Context Store per second
2. the average size of the context data that is being stored
3. the average lease time of stored contexts

Page 8
Note: the default lease time is configurable through CS Default Lease Time attribute of
CSManager. The default lease time out-of-the-box is 7200 seconds (i.e. 2 hours); this attribute
can be modified at runtime.
Release Notes for Avaya Context Store Snap-in 3.0