Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > DPA online activation requirements

DPA online activation requirements

Table of contents



For a sync to the DPA license server to be possible as online activation, the DPA server must be able to establish communication with the SolarWinds license server. This article outlines the items needed for this communication.

Note: There are many environmental factors that may come into play depending on environment security. Proxy servers and firewalls on your environment are outside of the scope of support. 


All DPA versions later than 9.0


  • Communication to the license server must be open from the DPA application server to and port 443 is used ( This is in the default trust store for DPA but also needs to exist on any proxy server and if the trust store was replaced in DPA, the certificate trust must exist in the Java trust store.
  • The GeoTrust certificate can be retrieved from or from the standard Java trust store that is shipped with DPA ([DPA Home]/iwc/jre_linux/lib/security/cacerts).


If the trust store was changed and you are not able to sync licenses, it may require reimporting:

  1. Run the following command:
    openssl version
    It should return something like this:
    OpenSSL 1.0.1f 6 Jan 2014
  2. Run the following commands:
    • echo -n | openssl s_client -connect | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > swilicense.crt
      This will export the SolarWinds licensing server certificate to a current directory and file swilicense.crt
    • [dpa home]/iwc/jre_linux/keytool -importcert -keystore /home/jan/dpa_9_5_306/iwc/tomcat/conf/.keystore -file swilicense.crt
      This will prompt for a keystore password and confirmation if you want to trust the certificate. Enter the password and select yes to accept the certificate.
  3.  Restart DPA.

If more troubleshooting is needed the logging level can be increased with the following steps:

a. Update file <installation_folder>/iwc/tomcat/webapps/iwc/WEB-INF/classes/log4j.xml.
b. Backup the file before modifying it, so it can be easily restored to original configuration.
c. Add new logger & appender to the file (will contain communication with license server)
<logger name="org.apache.axis.transport.http.HTTPSender">
<level value="DEBUG"/>
<appender-ref ref="axisLogger"/>
<appender name="axisLogger" class="org.apache.log4j.FileAppender">
<param name="File" value="logs/axis.log" />
<param name="MaxFileSize" value="20480KB"/>
<param name="MaxBackupIndex" value="10"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%c] %m%n" />

d. Update level value for following loggers to TRACE (will log additional details to license & gen3 log files)
<logger name="com.solarwinds.licensing">
<logger name="com.confio.license.audit" additivity="false">

e. Save the file and restart DPA.



Last modified