Click Data Collection Node in the navigation tree and verify that the node is running correctly.
To view the data loader properties, right-click each loader controller instance and select Loader Properties.
Click Scheduled Tasks in the navigation tree and modify the times that the scheduled tasks are running, if necessary.
Click Events in the navigation tree and verify that there are no ERROR or FATAL events.
Verify the email notification settings.
While in Events, click Action > Notification to open the Event Notification dialog.
If you intend to use the aysnchronous data loading mode, enable and configure the remoting server.
You should only use the asynchronous data loading mode for sending data from the Platform Analytics node to the database over a slow or unstable network.
Navigate to the ANALYTICS_TOP/conf/ directory.
Rename the remotingserver.TMPL file to remotingserver.xml.
Edit the remotingserver.xml file and change the IP address to the IP address of the Platform Analytics server host.
Edit the log4j.properties file and uncomment RemotingServer line.
Rename the wsm/pars.TMPL file to wsm/pars.conf.
Start up the remoting server.
perfadmin start pars
If you are on a Windows host and want the remoting server to start up automatically when Windows starts up, change the startup type of the pars Window service from Manual to Automatic.
LSF 8 users who have not applied the LSF 8 add-on data solution
Follow these steps only if you have LSF 8 installed and if you have not applied the LSF 8 add-on data solution (Oct Qpk).
Log into the Platform Analytics server host.
Edit the $ANALYTICS_TOP/conf/pi.conf file, navigate to the line:
LSF_VERSION =
Change 8.0 to 7.0 only if it is defined as 8.0. If not, then it is 7.0 by default.
Note:
If you do not change the version, the data you see may not be accurate.