The CDR Resource Adaptor comes packaged in a deployable unit,
The CDR resource adaptor type is packaged in
The resource adaptor has two dependencies, both delivered as part of distribution package, in the
the CDR Stream Configuration profile, with profile deployable unit
the Google Protocol Buffers library, with protobuf deployable unit
VERSION represents the version of the CDR resource adaptor.
The CDR resource adaptor does not come with a deployment script. Instead, an example service, distributed as part of the CDR resource adaptor package, includes a script that installs and configures the resource adaptor for that example. Developers and administrators should refer to the example script for the exact steps and adjust them to their own needs.
Basic deployment procedure
Deploying the CDR Resource Adaptor includes these steps:
A CDR resource adaptor entity can be configured to produce either binary or text CDR files.
|Binary output format||Text output format|
Defined in the Google Protocol Buffers definition
The format of a text CDR file consists of:
All lines end with the platform-default line ending (LF
The format of an individual CDR is controlled by the calling service.
When deactivated, a CDR resource adaptor entity remains in the
STOPPING state until all pending CDRs are written and
the CDR files are completed and archived.
If you need a faster shutdown, you can administratively remove the "CDR deactivation guard activities" (listed using
findactivities rhino-console command), to force the resource adaptor to transition to the
|If the node exits for any reason before the write/archive process completes, partial CDR files needing manual recovery may be left behind.|