Article Content
Article Number | 000032681 |
Applies To | RSA Product Set: Identity Management and Governance RSA Product/Service Type: Enterprise Software RSA Version/Condition: 6.9.1 Platform: UNIX Hosted by: MyAccessLive |
Issue | Account Collectors with the Data Source Type of Active Directory are no longer testing or collecting in the production environment under MyAccessLive (MAL), but other Account Collectors for Database are working perfectly fine. It only happens to Account Data Collectors for Active Directory, as in the screenshot below:![]() Also found the following details of errors from the aveksaServer.log: 02/09/2016 10:40:18.179 ERROR (JMS SessionPool Worker-92) [com.aveksa.server.utils.NodeMessageBroker] |
Resolution | The solution is try to reinstall the remote agent on-premises for the production environment. To reinstall the remote agent follow the steps below: Downloading the collection agent 1. Login to the RSA Via L&G SaaS application at https://<your_instance_name>.myaccesslive.com/aveksa/main. 2. Click on Collector > Agent. 3. Select Remote Agent then click on Download Agent. Deploying the collection service
1. Copy the AveksaAgent.zip to your Windows server. 2. Extract to create an AveksaAgent folder. 3. Verify that JAVA_HOME is set as a system variable and points to Java Runtime installed on your Windows server. 4. Navigate to the AveksaAgent/bin sub folder. 5. Right-click on the installAvAgent-NT.bat and select Run as Administrator to set up the service. 6. Navigate to Administrative Tools > Services. 7. Select AveksaAgent and invoke Start.
1. Create an unprivileged account for the agent to run in (the agent account). 2. For the agent account, export JAVA_HOME and put $JAVA_HOME/bin on the path. 3. Copy AveksaAgent.zip to the agent account and extract to create an AveksaAgent directory. Note: The readme.txt in the AveksaAgent directory contains instructions to start/stop the agent. 4. Change permissions of all files to the agent account. 5. Make all files in the AvekasaAgent/bin directory executable cd <path-to-AveksaAgent> 6. As root create a link to the startup script: ln -s path-to-AveksaAgent/bin/aveksa_agent /etc/init.d/aveksa_agent 7. Add the service and enable it: chkconfig --add aveksa_agent 8. Start the service: service aveksa_agent start 9. Stop the service: service aveksa_agent stop Verifying the Collection Service 1. Login to the RSA Via L&G SaaS application. 2. Go to Collector > Agents. 3. The RemoteAgent will show Yes as its running status. |
Notes | Please review the article on accessing the aveksaServer.log file for RSA Lifecycle and Governance (L&G) for information on gathering the aveksaServer.log file in your environment. |