lib/mnesia/doc/src/Mnesia_chap8.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE chapter SYSTEM "chapter.dtd">

<chapter>
  <header>
    <copyright>
      <year>1997</year><year>2013</year>
      <holder>Ericsson AB. All Rights Reserved.</holder>
    </copyright>
    <legalnotice>
      The contents of this file are subject to the Erlang Public License,
      Version 1.1, (the "License"); you may not use this file except in
      compliance with the License. You should have received a copy of the
      Erlang Public License along with this software. If not, it can be
      retrieved online at http://www.erlang.org/.
    
      Software distributed under the License is distributed on an "AS IS"
      basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
      the License for the specific language governing rights and limitations
      under the License.
    
    </legalnotice>

    <title>Combine Mnesia with SNMP</title>
    <prepared>Claes Wikstr&ouml;m, Hans Nilsson and H&aring;kan Mattsson</prepared>
    <responsible></responsible>
    <docno></docno>
    <approved></approved>
    <checked></checked>
    <date></date>
    <rev></rev>
    <file>Mnesia_chap8.xml</file>
  </header>

  <section>
    <title>Combine Mnesia and SNMP</title>
    <p>Many telecommunications applications must be controlled and
      reconfigured remotely. It is sometimes an advantage to perform
      this remote control with an open protocol such as the Simple
      Network Management Protocol (SNMP). The alternatives to this would
      be the following:</p>
    <list type="bulleted">
      <item>Not being able to control the application remotely
      </item>
      <item>Using a proprietary control protocol
      </item>
      <item>Using a bridge that maps control messages in a
       proprietary protocol to a standardized management protocol and
       conversely
      </item>
    </list>
    <p>All these approaches have different advantages and
      disadvantages. <c>Mnesia</c> applications can easily be opened to
      the SNMP protocol. A direct 1-to-1 mapping can be established
      between <c>Mnesia</c> tables and SNMP tables. This means
      that a <c>Mnesia</c> table can be configured to be <em>both</em>
      a <c>Mnesia</c> table and an SNMP table. A number of functions to
      control this behavior are described in the Reference Manual.</p>
  </section>
</chapter>