You can reconfigure a SIS instance by:
-
changing its resource adaptor entity configuration properties using the SLEE’s
ResourceManagementMBeanor -
changing any other configuration property managed using a SIS MBean interface.
Changing resource adaptor entity configuration properties
The SIS supports limited active reconfiguration (see section 15.4.2 of the JAIN SLEE 1.1 specification). Changes to some configuration properties while the SIS instance is ACTIVE will not take effect until you deactivate and reactivate the SIS instance (see below).
|
A SIS IN instance raises an alarm if it’s in the ACTIVE state and you try to change any configuration property that does not support active reconfiguration. SIP network interfaces and network routes do not support active reconfiguration. IN network interfaces and network routes support active reconfiguration. |
Active reconfiguration with SIP
| Property | ACTIVE reconfiguration? |
|---|---|
configurationProfileID |
YES |
SISWorkerPoolSize |
YES |
SISWorkerQueueSize |
YES |
automatic100TryingSupport |
YES |
automaticRel100Support |
YES |
WorkerPoolSize |
NO |
WorkerQueueSize |
NO |
TCPIOThreads |
NO |
sessionReplicationMode |
NO |
replicateByDefault |
NO |
max-compositions |
YES |
rateLimitedResponseCode |
YES |
retryAfterPeriod |
YES |
Active reconfiguration with IN
| Property | ACTIVE reconfiguration? |
|---|---|
configurationProfileID |
YES |
enabledProtocols |
NO |
SISWorkerPoolSize |
YES |
SISWorkerQueueSize |
YES |
icaProxySccpAddress |
YES |
iddPrefix |
YES |
countryCode |
YES |
max-dialogs |
YES |
Changing MBean-managed configuration properties
If you change any MBean-managed configuration property of a SIS instance, generally before those changes take effect you must tell the instance to reload its configuration. The exceptions, when a forced configuration reload is not necessary, are:
-
any address or service key subscription provisioning changes (excluding changing the configured subscription profile table names)
-
any IN trigger address tracing provisioning changes (excluding changing the configured trigger address tracing profile table name)
-
changing any fine-grained tracing debug levels or component audit level settings.
