The CDR resource adaptor comes with the CDR Generation example service. To deploy the example:
1 |
Start Rhino: $RHINO_HOME/start-rhino.sh |
|||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2 |
Unpack the CDR resource adaptor distribution package into
|
|||||||||||||||
3 |
The properties in
|
|||||||||||||||
4 |
To deploy the examples, using Ant, execute the $ cd $RHINO_HOME/cdr-ra-VERSION/examples $ ant deploy-all This copies the archive script to the cdr folder, deploys the CDR Resource Adaptor, example (Telnet) resource adaptor, and the CDR Generation example service. |
|||||||||||||||
5 |
Use a Telnet utility to connect to the example resource adaptor: telnet localhost 9999 |
|||||||||||||||
6 |
Try these commands:
|
Source code for the example service can be found in the examples/src subdirectory of the CDR Resource Adaptor
package. This code may be freely altered and reused. It is made available under a BSD-style license.
|
Example: processing binary CDR files
The CDR Generation example service is accompanied by example code that processes the resulting binary CDR files.
The examples are custom extensions of cdrpipeline
tool.
The cdrpipeline tool is part of the CDR Resource Adaptor package, described in
Extendable binary CDR file processing tools.
|
To run the binary CDR file processing examples:
1 |
Deploy the example service by following the steps in Example Service. |
||
---|---|---|---|
2 |
Use the example service to generate one or more completed binary CDR files.
|
||
3 |
To display the content of generated CDR files on the console, execute these commands: $ cd $RHINO_HOME/cdr-ra-VERSION/examples $ ant run-sysout-cdr-processor This invokes the |
||
4 |
To create a temporary $ cd $RHINO_HOME/cdr-ra-VERSION/examples $ ant run-db-insert-cdr-processor This invokes the
|
Source code for the example CdrProcessor (s) can be found in the examples/src subdirectory of the CDR Resource
Adaptor package.
Reviewing the Ant targets run-sysout-cdr-processor and run-db-insert-cdr-processor in examples/build.xml is also
recommended.
|