Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario descargar pdf (Pagina 185)

Common Configuration

# P0602477 Ver: 3.1.11 Page 185

If the zap.network.cfg file existed only on nodeA, and each LAN were its

own group, the reference node would have to update one MPS in each LAN, requiring

it to travel over a total of three slow links (one to nodeD, nodeE, and nodeF and

two to nodeG, nodeH, and nodeJ). With the example scenario in place, the

reference node updates one MPS on nodeB and nodeC, then tries one MPS on each

of the other nodes in the order they appear in its zap.network.cfg file. ZAP

detects that there is another zap.network.cfg file on nodeD (or nodeE or

nodeF if one of the other nodes fails): instead of nodeD updating one MPS for every

node in its group as defined on nodeA, it updates one MPS for every node in its group

and one from the other group as defined on nodeD (see nodeD, nodeE, and

nodeF on page 184). Initial processing time may be slower because the nodes in the

latter group are not updated until one MPS in that of nodeD completes (as opposed to

parallel processing ZAP normally uses): however, overall processing time and

network congestion are reduced substantially since the number of times ZAP would

have had to travel over the slow links is also reduced. Though this example uses a very

basic model, the savings becomes substantial on systems of greater complexity.

Updating a Specific Element

By default ZAP compares each target MMF with the designated MMF on the

reference node and transmits to each one those elements which are different. In

instances where the element that has changed is known, ZAP can be directed to update

only that element and ignore any other comparison of the file. This increases

significantly to the speed at which ZAP functions.

In this case, instead of updating one MPS per node and then executing other remote

instances, ZAP copies the file created from selected element(s) to the remote node and

executes a remote ZAP on all MPS’ on that node.

To update a specific element, use the -e option in the following manner from the

node that contains the updated element:

zap -e {@ <EAP_number> | <“Element Name”>} <mmf_name>

If specifying an element name that contains spaces, it must be enclosed in quotes. This

ensures that the variable is passed as one argument to ZAP. If there are no spaces in

the element name, the quotes may be omitted. Multiple element names and/or EAP

numbers are stipulated through multiple -e arguments.

As an example, an MMF file named Talk2Me contains the following elements:

EAP# Element Name

--------------------------

1 Welcome Message

2 Salutations

3 Goodbye Message

1 2 ... 180 181 182 183 184 185 186 187 188 189 190 ... 305 306

Sin comentarios

Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario Pagina 185