To get or set the application context override for a service, use the following sis-console commands, Ant task, or related MBean operations:

Tip This is a SIS feature for IN.
Note The default behaviour of the SIS is to trigger composition services using a dialog of the same application context as the network dialog. The application context override option allows a service to be instead triggered with a specific application context, typically different to the expected network dialog application context. For example, the service may only support a particular protocol.
Warning This option does not provide protocol translation. If protocol translation is required between the network dialog application context and the service dialog application context, then this must be provided via SIS interceptor components.

Console commands

getApplicationContext

Command

 
getapplicationcontext <ra-entity> <name>
    Get IN application context that the service will be invoked with

Example

To get the application context override for a service with reference name VPN in the SIS instance named sis:

$ ./sis-console getapplicationcontext sis VPN
IN application context for service reference VPN is cap_v2:cap-v2-gsmSSF-to-gsmSCF-AC

setApplicationContext

Command

 
setapplicationcontext <ra-entity> <name> <app-context>
    Set IN application context that the service will be invoked with. Use - to
    clear an existing setting

The list of supported application context names that can be used by this command is obtainable using the listSupportedApplicationContexts command as shown below.

Example

To set the application context override for a service with reference name VPN in the SIS instance named sis to cap_v3:capssf-scfGenericAC:

$ ./sis-console setapplicationcontext sis VPN cap_v3:capssf-scfGenericAC
Set IN application context for service reference VPN to cap_v3:capssf-scfGenericAC

To remove an existing application context override for the same service:

$ ./sis-console setapplicationcontext sis VPN -
Cleared IN application context for service reference VPN

listSupportedApplicationContexts

Command

 
listsupportedapplicationcontexts <ra-entity>
    List the set of supported application contexts that a service can be invoked
    with

Example

To list the application contexts supported by the SIS instance named sis:

$ ./sis-console listsupportedapplicationcontexts sis
The following application contexts are supported:
cap_v1:cap-v1-gsmSSF-to-gsmSCF-AC
cap_v2:cap-v2-assist-gsmSSF-to-gsmSCF-AC
cap_v2:cap-v2-gsmSRF-to-gsmSCF-AC
cap_v2:cap-v2-gsmSSF-to-gsmSCF-AC
cap_v3:cap3-sms-AC
cap_v3:capssf-scfAssistHandoffAC
cap_v3:capssf-scfGenericAC
cap_v3:gsmSRF-gsmSCF-ac
cap_v4:cap4-sms-AC
cap_v4:capssf-scfAssistHandoffAC
cap_v4:capssf-scfGenericAC
cap_v4:gsmSRF-gsmSCF-ac
etsi_inap_cs1:core-INAP-CS1-IP-to-SCP-AC
etsi_inap_cs1:core-INAP-CS1-SCP-to-SSP-AC
etsi_inap_cs1:core-INAP-CS1-SSP-to-SCP-AC
etsi_inap_cs1:core-INAP-CS1-assist-handoff-SSP-to-SCP-AC

Ant task

updateserviceref

Task

 
<updateserviceref name="..." inServiceApplicationContext="..."/>

Example

 
<sis-in-management>
    <updateserviceref name="VPN" inServiceApplicationContext="cap_v3:capssf-scfGenericAC"/>
</sis-in-management>

MBean operations

MBean

getApplicationContext

Operation

 
public String getApplicationContext(ServiceRefID serviceRefID)
    throws NullPointerException, UnrecognizedComponentException, ManagementException;

setApplicationContext

Operation

 
public void setApplicationContext(ServiceRefID serviceRefID, String appContextName)
    throws NullPointerException, UnrecognizedComponentException,
           InvalidArgumentException, ManagementException;

getSupportedApplicationContexts

Operation

 
public String[] getSupportedApplicationContexts()
    throws ManagementException;
Previous page Next page
SIS Version 2.7.0