The SIP Servlet Resource Adaptor (RA) gets its configuration from several sources.

Like most SLEE RAs, it uses configuration properties — configured values that the SLEE passes to an RA entity when it is created, and when its configuration is updated (for example, by way of rhino-console’s updateRAEntityConfigProperties command).

Note Configuration Properties describes the available configuration properties.

The SIP Servlet RA also uses several profile tables for storing configuration settings that are not easily represented using standard configuration properties. These profile tables must be created before the SIP Servlet RA entity is created. The bundled deployment script deploy.xml does this automatically.

  • SLEE Profile Tables describes the required tables and their contents, which can be adapted for custom deployments.

  • Users are not expected to manipulate the profile tables directly, after they are created (unless otherwise noted). The SIP Servlet management commands will perform any configuration updates and apply changes to the underlying profile tables.

  • Modifying the profile tables directly is not supported, and the results of doing so are undefined.

Active reconfiguration

All configuration property updates or management operations may be invoked on an active SIP Servlet RA entity. For some properties, however, updates may not apply immediately. If a SIP Servlet RA entity cannot apply a configuration change immediately, it will raise a SLEE alarm saying that the RA entity must be restarted for the changes to take effect. These alarms will appear in Rhino’s logs, and can be viewed in REM or rhino-console (listactivealarms).

If a configuration update fails for any reason, the SIP Servlet RA entity will raise an alarm, and try to continue with its last successful configuration.

Previous page Next page