JBoss.orgCommunity Documentation
The RA implementation is adoptation of Java Call Control API (JCC 1.1) for the requirements of Jain SLEE. Any specific JCC providers can be injected into the Resource Adaptor. The Mobicents development teams provides implementation of the JCC for Customised Applications for Mobile networks Enhanced Logic (CAMEL) based on Mobicents SS7 solution.
The Resource Adaptor supports configuration only at Resource Adaptor Entity creation time, the following table enumerates the configuration properties:
Table 3.1. Resource Adaptor's Configuration Properties
Property Name | Description | Property Type | Default Value |
---|---|---|---|
provider | Specifies JccPeer object given a fully qualified classname of the class which implements the JccPeer object or provider acronym. | java.lang.String | |
config | The name of the property file which contains vendor/protocol specific configuration | java.lang.String |
Configuration option(provider
) supports following values(aside class full name):
Following configuration options are available for this driver:
Table 3.2. config.properties values for TCP SCCP provider
Property Name | Description | Property Type | Default Value |
---|---|---|---|
driver | Configures stream driver of SCCP layer. Currently only TCP is supported. | java.lang.String | TCP |
server.ip | Driver configuration options. Specifies TCP address to which driver will connect. | java.lang.String | 127.0.0.1 |
server.port | Specifies server port to which driver will connect. | java.lang.String | 1345 |
sccp.opc | Default OPC used by SCCP layer for originating messages. | java.lang.String | 0 |
sccp.dpc | Default DPC used by SCCP layer for originating messages. | java.lang.String | 0 |
sccp.sls | Default SLS used by SCCP layer for originating messages. | java.lang.String | 0 |
sccp.ssi | Default SSI used by SCCP layer for originating messages. | java.lang.String | 0 |
JAIN SLEE 1.1 Specification requires values set for properties without a default value, which means the configuration for those properties are mandatory, otherwise the Resource Adaptor Entity creation will fail!
There is a single Resource Adaptor Entity created when deploying the Resource Adaptor, named JCCRA
. The JCCRA
entity uses the default Resource Adaptor configuration, specified in Section 3.1, “Configuration”.
The JCCRA
entity is also bound to Resource Adaptor Link Name JCCRA
, to use it in an Sbb add the following XML to its descriptor:
<resource-adaptor-type-binding>
<resource-adaptor-type-ref>
<resource-adaptor-type-name>JCC-1.1-RA</resource-adaptor-type-name>
<resource-adaptor-type-vendor>javax.csapi.cc.jcc</resource-adaptor-type-vendor>
<resource-adaptor-type-version>1.1</resource-adaptor-type-version>
</resource-adaptor-type-ref>
<activity-context-interface-factory-name>
slee/resources/jcc/1.1/acifactory
</activity-context-interface-factory-name>
<resource-adaptor-entity-binding>
<resource-adaptor-object-name>
slee/resources/jcc/1.1/provider
</resource-adaptor-object-name>
<resource-adaptor-entity-link>
JCCRA
</resource-adaptor-entity-link>
</resource-adaptor-entity-binding>
</resource-adaptor-type-binding>
Each Resource Adaptor Entity uses a single JAIN SLEE 1.1 Tracer, named JCCResourceAdaptor
. The related Log4j Logger category, which can be used to change the Tracer level from Log4j configuration, is javax.slee.RAEntityNotification[entity=JCCRA]