|
|
| Q |
I have my own ASN.1 syntax. Can I use OneViewer? |
| A |
Yes. One of the primary design requirements for OneViewer was the ability
to work with any custom ASN.1 Syntax. The configuration of this syntax is
done by the user at run time.
|
| Q |
Which encoding rules does the application support? |
| A |
OneViewer supports BER, CER, DER, PER, UPER, XER,
and CXER encoding.
|
| Q |
I need to create many messages that are very similar
to each other (only one or two values different). How does OneViewer cope with
this? |
| A |
Use OneViewer to create and save the first message. To create the subsequent
messages, open the first message, modify the one or two items to the desired
values, and then save to a different file.
|
| Q |
In my application, I need to dynamically modify the
contents of a message. Can I still use OneViewer? |
| A |
Yes, OneViewer can help you with the initial creation of the messages. Some
ASN.1 messages are very large. Creating these messages by hand is a non-trivial
and error-prone task. OneViewer can help you create the "static" part or
structure of your messages. Your application can read them and modify the few
fields that need to change dynamically. OneViewer can also examine the contents
of the received messages.
|
| Q |
Once I have built a message how do I use it with my
System? |
| A |
The answer to this question will depend on your system and its requirements.
Some systems are already configured to process files as messages. If this is
the case, you simply need to point your system to the files created by
OneViewer. Other systems will need to have some code created in order to read
the message at the appropriate time. Given that the file format used by
OneViewer is very simple, this task should not be difficult for an average
programmer.
|
| Q |
In log file mode how does OneViewer get access to
the messages? |
| A |
OneViewer reads the messages from a log file. This log file needs to be created
by the application under test. The application puts all the transmitted and
received messages into the log file. For each message, along with the encoded
data, the message name, syntax name, direction, encoding rule, and timestamp
need to be saved. These values are saved in a comma separated ASCII format. A
sample log file can be supplied on request.
|
| Q |
How do I configure OneViewer to work with my ASN.1
syntax? |
| A |
New ASN.1 syntaxes can be loaded at run time. You configure OneViewer for
the location and name of the ASN.1 syntax.. When the log file is read, the
syntax of each message is compared against the list of installed syntaxes. If
there is a match, the message is decoded.
|
| Q |
Can I run OneViewer while my application is creating
the log file? |
| A |
Yes. OneViewer can operate in one of two modes. In one mode it will read the
log file once from start to end and then display the contents. In the other
mode, it will initially read the whole log file then continuously read the
file, updating the display as new messages are found.
|
| Q |
OneViewer is very close to what I need but it does
not exactly meet my requirements. How can this be dealt with? |
| A |
OneViewer is an evolving application. New features
are being planned. Your input can influence its future capabilities and
direction. Depending on the impact and size of your requirements it may be
possible for Red Packet Technologies to modify OneViewer to suite your specific
needs. For more information, contact Red Packet Technologies.
|
| Q |
How do I get more information about OneViewer? |
| A |
Send your request, indicating your name, company, and application to
info@redpackettech.com.
|
