Configuring and Launching Analytics
You must configure Oracle WebCenter Analytics to store
events from custom applications by modifying the database.properties
and openusage.xml files.
The instructions below are simplified for example purposes
only. For a list of ports used by Analytics and details on configuring
the Analytics database, see the Installation and Upgrade Guide
for Oracle WebCenter Analytics.
- Open the openusage.xml file and enter the Analytics server
port:
<UNICAST_MODE>YES</UNICAST_MODE>
<UNICAST_IP>$analytics_server_host$|port=31314</UNICAST_IP>
- Open the database.properties file and enter database information
for the Analytics Server. (Use the appropriate driver and URL for
your configuration.)
jdbc.driver=com.plumtree.jdbc.sqlserver.SQLServerDriver
jdbc.url=jdbc\:plumtree\:sqlserver\://$analytics_database_server$\:1433;DatabaseName\=$analytics_database_name$
jdbc.user=$analytics_database_user$
jdbc.password=$analytics_database_password$
- Place both configuration files in the appropriate config
location. You can place the openusage.xml file anywhere, but your
code must reference this file when initializing OpenUsage. This is
done by calling the following method, where configDirectory is the path to the folder where openusage.xml is located. (This
method only needs to be called once during your application run, normally
during startup).
ASEventFactory.setConfig("configDirectory", "openusage.xml");
In the sample application, the OpenUsageDemoServlet class calls setConfig in the init() method. The configDirectory parameter is defined in web.xml as .\openusage-demo\config\settings.
To change this location, open the .war file and modify the configDirectory init-param in web.xml.
- Deploy the application .war file to any Java Servlet Container.
- On the Analytics server, make sure the Analytics Collector
Service is started.
To view the events from your custom application, query the
Analytics database. For details, see the next page, .
