Configuring the Experience Collector to support multiple AXA App Profiles

Document ID : KB000115859
Last Modified Date : 26/09/2018
Show Technical Document Details
Introduction:
By default, DXC snippets do not contain specific app and tenant information, so there is a process to include that information in the DXC snippets so that data can be viewed under specific apps in AXA.
Background:
This works for DXC reporting to AXA on-premise or AXA SaaS
Instructions:
  1. Create the App Profile in CA AXA
  2. Note the Tenant id, Collector URL and App ID from the web app snippet, find the relevant information in the following properties:
data-profileUrl=http(s)://<host>:port
data-tenantID=
data-appID=
  1. Go to ../ExperienceCollectorBundle-<version>/integration -folder
  2. Run ./apm-axa-integration.sh <AXA_TENANT_ID> <http/https>://<AXA_COLLECTOR_HOST>:<PORT> <AXA_APP_ID>
Example:
[axa@axa173 integration]$ ./apm-axa-integration.sh BCE31DE8-F84D-428B-80FA-25CA140C6142 https://collector-axa.cloud.ca.com dxc-test
  1. Once the script completes with no errors, check the new snippet:
../EC/dxc-test.basnippet
  1.     find file ../ExperienceCollectorBundle-<version>/EC/DxC/logstash/apm-axa-integration/apm-logstash-axa.conf -
  2.     Comment out line:
#replace => [ "[app][id]","dxc-test" ]
  1.     Restart Collector - Use the new dxc-test.basnippet with your web apps
Additional Information:
  • The apm-logstash-axa.conf will handle changing the tenant value from default-tenant to the specified tenant value.
 
  • The apm-axa-integration.sh creates a Logstash instance that sends the data to AXA. This is a separate Logstash instance to the one that sends DXC information to APM..
You can see both of them mentioned in DXC's startStopServices.sh script:
./startStopServices.sh  -lapm, -LAPM, --logstashAPM                             Will start or stop the Logstash plugin for APM
./startStopServices.sh  -laxa,  -LAXA, --logstashAXA                                Will start or stop the Logstash plugin for AXA