porterk wrote:Hi Wilder,

To clarify, which documentation are you referring to?

Could you please test adding the Security IP as the Cluster IP in SMGR for your Context Store node.

Also, could you please confirm that the Connection Settings for the CS SDK have been configured?

Regards,
Kezzia

I attached a screenshot of the documentation. The connection settings only requires the IP address, since it is an unsecured connection. by security address, I am refering to the "SIP Entity IP Address" for the Avaya Breeze Instance which is dedicated for the context store. so, If i put a fake IP or the context store breeze instance security IP, the sample client hangs for a few seconds then times out with that generic error.

one thing I noticed in the engagement designer log was this line
Max Retry time to get db connection: 20


also when I look at the Sample Java Client log when I click Run Operation it times out after 21 seconds everytime

Add Context without contextId
Invalid request, response = ERROR
Operation took 21031 milliseconds

Unsecured connection selected, Key Store Settings are not required
Creating Context Store connection

Add Context without contextId
Invalid request, response = ERROR
Operation took 21028 milliseconds

Hi Wilder,

I believe the documentation refers to the fact that there is no need to add a seperate Cluster IP, the security IP of the single node should be fine.

Could you please run the following commands on your Context Store node to confirm the Security IP and hostname:
hostname
ifconfig

Please confirm that the returned values are the same as the values entered for your single node under Cluster Administration->Edit cluster.

Also, please attach the requested ED log from the test I described last week that involves a slightly different ED test. It should provide more useful information that the generic error that you are seeing through the SDK client.

Thanks,
Kezzia

porterk wrote:Hi Wilder,

I believe the documentation refers to the fact that there is no need to add a seperate Cluster IP, the security IP of the single node should be fine.

Could you please run the following commands on your Context Store node to confirm the Security IP and hostname:
hostname
ifconfig

Please confirm that the returned values are the same as the values entered for your single node under Cluster Administration->Edit cluster.

Also, please attach the requested ED log from the test I described last week that involves a slightly different ED test. It should provide more useful information that the generic error that you are seeing through the SDK client.

Thanks,
Kezzia

The hostname and security ip are the same. I think I need to put engagement designer on the side as I think I found the main issue. I ran a debug on the SDK source and I found that the SDK is attempting to send this REST request: http://contextstorenodeip/services/ContextStoreRest/cs/contexts/
This request fails in postman. so, I am unable to work with the context store using plain http.

but https on the other hand works.
https://contextstorenodeip/services/ContextStoreRest/cs/contexts/

The cause of the generic error:
when the http request is sent to the server, it is not accepted and the request hangs until it times out returning this generic error. so, I need to allow the context store to accept http requests as it seems that it only accepts https requests to the security ip. I looked through the settings and I found http securiy configuration and it looks fine there, so I am not sure if allowing http will need to be done at the server level.

Hi Wilder,

Please check the value of 'Only allow secure web communications' in SMGR->Cluster Attributes ->select your cluster.
I'm on a training course this week, however we could arrange an online session next week to try to resolve this issue?

Regards,
Kezzia

porterk wrote:Hi Wilder,

Please check the value of 'Only allow secure web communications' in SMGR->Cluster Attributes ->select your cluster.
I'm on a training course this week, however we could arrange an online session next week to try to resolve this issue?

Regards,
Kezzia

This setting solved the http issue, so now both http and https requests work, but the context store task in ED still returns the error. I will get those logs and post them soon. Thanks

Wilder wrote:

porterk wrote:Hi Wilder,

Please check the value of 'Only allow secure web communications' in SMGR->Cluster Attributes ->select your cluster.
I'm on a training course this week, however we could arrange an online session next week to try to resolve this issue?

Regards,
Kezzia

This setting solved the http issue, so now both http and https requests work, but the context store task in ED still returns the error. I will get those logs and post them soon. Thanks

Now i am able to add context using postman and Get context using ED context store task. I am unable to add a context through ED but I think that has to do with the parametesr (ContextId, GroupID, and key/value pairs) being passed as a context.


I am passing ContextId, Group ID, and key/value data. The sample workflow is attached. Get Context works fine, but not Add Context


2018-09-13 18:00:29,911 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Store WFD in data grid: wfdName = debug_1536876025534 wfdVersion = 1; date = 2018/09/13 18:00:29
2018-09-13 18:00:29,916 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Adding debug_1536876025534_1_customer com.avaya.app.entity.WFDSvar@cc0c605d
2018-09-13 18:00:29,979 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Adding 1413 com.avaya.app.entity.Instance@e6da570c
2018-09-13 18:00:29,979 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Publishing event for create instance with payload: null
2018-09-13 18:00:32,247 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - eval is: {"key2_name":"asdfsa3234","key1_name":"asdfas3343","key3_name":"asdfas12312"}
2018-09-13 18:00:32,249 [WebContainer : 1] rest.ContextStoreHttpsRESTClientService INFO - [M:postContext][T:null]. Request URI = https://11.242.143.53:443/services/ContextStoreRest/cs/contexts/?lease=7200&rules=false
2018-09-13 18:00:32,255 [WebContainer : 1] response.ResponseDataUtilsForHttpsClient ERROR - [M:processHttpResponseStatusCode][T:null]. BAD_REQUEST request error when running the http request, statusLineCode = 400
2018-09-13 18:00:32,255 [WebContainer : 1] EngagementDesigner ERROR - EngagementDesigner-3.4.0.0.32008 - Invalid request, BAD_REQUEST
2018-09-13 18:00:32,255 [WebContainer : 1] EngagementDesigner ERROR - EngagementDesigner-3.4.0.0.32008 - The request failed response = BAD_REQUEST
2018-09-13 18:00:32,256 [WebContainer : 1] rest.ContextStoreHttpsRESTClientService INFO - [M:getData][T:test3242]. Request URI = https://11.242.143.53:443/services/ContextStoreRest/cs/contexts/test3242
2018-09-13 18:00:32,276 [WebContainer : 1] response.ProcessHttpResponseUtils ERROR - [M:processHttpResponseForGetData][T:test3242]. Exception: Error occurred extracting data - "No data found."
2018-09-13 18:00:32,277 [WebContainer : 1] EngagementDesigner ERROR - EngagementDesigner-3.4.0.0.32008 - Invalid request, ERROR
2018-09-13 18:00:32,277 [WebContainer : 1] EngagementDesigner ERROR - EngagementDesigner-3.4.0.0.32008 - The request failed response = ERROR
2018-09-13 18:00:32,294 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Removing 1413
2018-09-13 18:00:32,313 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Adding 1413 com.avaya.app.entity.Instance@b63d0b29

Hi Wilder,

Great to hear there has been progress with this issue.

In the ED flow attached, the first Context Store Task that is attempting to 'Add Context' however the input mapping is incorrect.
The contextId and groupId inputs need to be also mapped to the csDataInput of this task, not just the data object.

The correct usage of the 'Add Context' ED Task operation is available in the Appendix of the 3.4 Context Store Developer Guide and a a sample workflow is also available through the 3.4 Context Store DevConnect Downloads page called 'Create Context Sample Engagement Designer Workflow':
https://www.devconnectprogram.com/fileMedia/download/e137e3f4-3c60-4916-9e55-78b885002758

Regards,
Kezzia

Hi Wilder,

I just posted a response but for some reason cannot see it!
Here it is again.

The input mapping of the 'Add Context' ED Task is incorrect.
Please refer to the 3.4 Context Store Developer Guide or the sample workflow 'Create Context Sample Engagement Designer Workflow' available here for the correct input mapping:
https://www.devconnectprogram.com/fileMedia/download/e137e3f4-3c60-4916-9e55-78b885002758

Regards,
Kezzia

Hi Wilder,

Could you please confirm if this issue has now been resolved?

Thanks,
Kezzia

porterk wrote:Hi Wilder,

Could you please confirm if this issue has now been resolved?

Thanks,
Kezzia

Yes. Thank you very much.

You're very welcome, thank you for confirming.