This slide provides information offered at the July 12, 2019 Free Friday Tech Huddle that highlighted the RSA Archer Release 6.6 performance enhancement highlights.
Questions and Answers:
Q: Does the 'technology updates' on community speak to all 6.6 improvements in more detail?
A: You can find all of the release 6.6 related blogs on this subspace: https://community.rsa.com/community/products/archer-grc/archer-customer-partner-community/platform/66. This is the specific blog Brian references: https://community.rsa.com/community/products/archer-grc/archer-customer-partner-community/blog/2018/11/13/technology-updates-that-you-need-to-know. It talks about Caching in addition to SQL support, .NET support and ElasticSearch.
The FFTH from June 28, which covered the RSA Exchange Release 8, included a presentation by ScaleOut if anyone has further interest.
Q: Is there any plan to release Data Gateway development to users in the future?
A: Data Gateway still requires Professional Services. Our goal is to make that self-configurable in the future, but that timeline is not yet defined.
Q: Where can I find documentation and configuration detail on the Data Gateway SQL connector?
A: Documentation is not yet available at this point because PS is required for Data Gateway. We are working on this documentation for upcoming releases when we have a user interface that will enable the Data Gateway capabilities.
Q: Is there an official guide outlining what versions of Elasticsearch should be used with which versions of Archer (eg. Archer 6.6 / ES version 2.x)?
A: RSA Archer 6.6.x requires ElasticSearch Version 6.61. While it is noted in the release documentation, here is a Knowledge Based article written by Customer Support regarding Elastic implementation. https://community.rsa.com/docs/DOC-104094
Q: Does Archer 6.4 P2 supports SQL 2017?
A: Yes, SQL 2017 is supported in 6.4.x (which includes patch 2).
Q: Can I ask a question related to Elastic search- Issue when search in GLobal search window with special character - like suffix - number it cant search.
A: If you're trying to search for an a record ACT-1234, unfortunately keyword search treats that as ACT 1234. So it finds both.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.