Best practices

Last Updated : Jun 05, 2026 |

Experience Portal supports Axis 2.0 Application Logging web service.

When using the Application Logging web service, keep in mind that:

  • The Axis 2.0 Application Logging web service use Basic Authentication to authenticate web service client requests and only support HTTPS protocol.

  • When the HTTPS protocol is used in the Web Service client, the Web Service client needs to handle to accept the certificate from the EPM server. No certificate needs to be installed on the Application Server. It is one-way SSL authentication.

  • When calling the Axis 2.0 Application Logging web services, ensure to turn HTTP Chunking off.

  • When you submit a request to the web service, you need to specify the user name and password which are specified in the Application Reporting section of the Web Service Authentication group on the EPM Settings page. If you need to change this user name or password, you must do it through the EPM. For details, see Configuring the Application Logging web service. For Axis 2.0 Application Logging web service requests, you can also use the Experience Portal web user name and password. The web user has to have the Web Services role with Application Reporting feature enabled.

  • You must send all of the log entries for one or more session blocks at the same time. Do not send each log entry as it occurs or you may adversely affect Experience Portal system performance.

  • You must use the logApplicationEventAlarm web service method with utmost caution. You should implement a throttling mechanism on the client side to limit flooding the EPM with the application events and alarms.

  • You should have a proper queuing mechanism or sampling rate control method in place if you are sending a large number of log entries to the database. Otherwise this may adversely affect Experience Portal system performance.

  • You should save all log entries in case the EPM is unavailable when the Application Logging web service is called. That way you can resend the log entries when the EPM becomes available.

  • If your Experience Portal EPM software runs on a dedicated server machine, you should configure a auxiliary EPM server to handle Application Logging web service requests if the primary EPM server is unavailable.

  • The Avaya Experience Portal Application Detail report and Application Summary report expect the report data to be in a particular format. For details about what Application Detail Records (ADRs) are stored in the vpapplog table, see Generating custom reports using third-party software in Administering Avaya Experience Portal.