📄 c-upload3.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> Configuring Data Upload </title></head><body bgcolor="FFFFFF"><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-upload.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-upload.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-upload2.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-upload4.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h3 class="H2"><i><a name="87227">4.3 Upload Path and Destination</a></i></h3></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="85853"> </a>The upload path is the route used to upload your event data from the target to the host. The upload destination is where the data is put when it is uploaded. The options presented in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Upload Path</font></b> section of the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Control Properties</font></b> dialog box (see <a href="c-upload3.html#85860">Figure 4-3</a>) combine a path and a destination. <div class="frame"><h4 class="EntityTitle"><a name="85860"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 4-3: Upload Path and Destination </font></a></h4><dl class="margin"><div class="Anchor"><a name="85865"> </a><img class="figure" border="0" src="images/c-upload5.gif"></div></dl></div></p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="85869">4.3.1 Alternative Upload Paths</a></i></h4></font><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84947">Target Server </a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84951"> </a>WindView, like other Tornado tools, allows you to upload data through the target server. This is done using a new feature called TSFS, which is described in detail in the <i class="title">VxWorks Programmer's Guide: Local File Systems</i>. TSFS uses the VxWorks virtual I/O facility to send data to the host. (For information about the VxWorks VIO facility, see the <i class="title">Tornado API Guide: The WTX Protocol</i>.) TSFS implements the standard I/O commands. In addition, TSFS supports a socket as a special file type. Thus TSFS can upload data either to a file or to the WindView display or another destination.</p><dd><p class="Body"><a name="88166"> </a>TSFS uses the same path as your WDB agent to communicate to the target server. Thus you must define <b class="symbol_UC">INCLUDE_WDB</b> in order to use TSFS. If you configured WDB to use a serial interface, TSFS will use the serial interface. If you configured WDB to use a network connection, TSFS will use the network connection. Note that when you include WindView and do not specify an upload path, the TSFS paths to both files and the WindView display are included (see <a href="c-start4.html#86105"><i class="title">Upload Path</i></a>).</p></dl></dl><dl class="margin"><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/note.gif"></td><td><hr><div class="CalloutCell"><a name="88780"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE: </font></b></a>Remember that you must also configure your target server to support TSFS (see <a href="c-start4.html#93215"><i class="title">Configuring the Target Server for TSFS</i></a>).</div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout><dl class="margin"><dd><p class="Body"><a name="88170"> </a>The advantage of using TSFS is that it does not require extra facilities. If you have chosen to use network facilities for other reasons, TSFS takes advantage of the bandwidth you have already configured to upload WindView data. If you have decided not to configure network facilities, TSFS uses the serial connection. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="85893">Network Facilities</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="85895"> </a>The advantage of a network connection over a WDB connection is that it is separate from the WDB messages flowing between your target and the Tornado target server. The disadvantage is that using this path requires that your target contain at least the network stack (TCP/IP) and possibly also the Network File System (NFS). If you plan to configure these facilities anyway, you may choose to use these paths. If you do not need these facilities, and if you need to minimize the size of your VxWorks kernel, you might choose to use TSFS over a serial line. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="85896">4.3.2 Alternative Destinations </a></i></h4></font><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="85897">View Graph</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="85912"> </a>Sending your event data directly to the view graph means you can eliminate the step of opening a file. On the other hand, the parser element within the WindView host tool must process the data before it can be displayed, which may slow the data transfer rate. You can save any event log to a file from the view graph. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="85913">File</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="85914"> </a>Sending your event data to a file means that the log is saved on the host before you begin analysis. The data can be written to a file more rapidly than to the view graph because the data is written in its raw format. The parser does not process the data until you open the file to display it in the view graph.</p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="85898">4.3.3 Choosing the Path and Destination</a></i></h4></font><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="88217">Direct to Graph</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="88219"> </a>When you select <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Direct to Graph</font></b> from the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Upload Path</font></b> drop-down combo box, the event log is uploaded directly into the WindView view graph on the host where the target server is located. The only configuration steps you must take to use this path are to include TSFS in your VxWorks image (see <a href="c-start4.html#86067"><i class="title">2.4.2 Configuring VxWorks</i></a>) and to configure the target server to support TSFS (see <a href="c-start4.html#93203"><i class="title">2.4.3 Starting a Target Server</i></a>). When you upload data, a view graph opens and the data streams into it. </p></dl></dl><dl class="margin"><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/note.gif"></td><td><hr><div class="CalloutCell"><a name="88802"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE: </font></b></a>If you use <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Direct to Graph</font></b> with continuous upload mode, you can use the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Track incoming events</font></b> button (<img class="figure" border="0" src="images/c-uploada1.gif">) to pause the display so that you can look at a particular section without it continually changing. Data continues to stream into the view graph, and when you click the <img class="figure" border="0" src="images/c-uploada4.gif"> button again, the display updates to show the whole log.</div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84936">File via TSFS </a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="85932"> </a>When you select <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">File via TSFS</font></b> from the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Upload Path</font></b> drop-down combo box, the default path presented is <b class="file">/tgtsvr/eventLog.wvr</b>. When you upload data, the root you specified in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Target Server Configuration</font></b> dialog box is substituted for <b class="file">/tgtsvr</b>. Data is written to this file when upload is requested, either by the target (in continuous upload mode) or by you (in deferred upload mode). To view and analyze the data, you must load the log file into WindView using <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Open</font></b> from the main <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">File</font></b> menu. For more information on configuring this path, see <a href="c-xfer3.html#86744"><i class="title">TSFS to a File</i></a>. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="83944">Socket via TSFS </a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="88075"> </a>When you select <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Socket via TSFS</font></b> from the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Upload Path</font></b> drop-down combo box, the default path presented is <b class="file">/tgtsvr/TCP:</b><i class="textVariable">hostname</i><b class="file">:6164</b> where <i class="textVariable">hostname</i> is the name of the machine where the target server is located. Using this default path sends the data to the WindView view graph just like <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Direct to Graph</font></b>. However, if you select this option you must open the view graph using <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">New</font></b> on the main <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">File </font></b>menu before starting data collection, which is unnecessary with <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Direct to Graph</font></b>. The port number indicated on the view graph must match the port number in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Control Properties</font></b> dialog box. In addition, selecting this option allows you to modify the defaults to send the data to an alternate destination, such as a remote machine or <b class="symbol_lc">evtRecv</b>. Data is uploaded either continuously or when you request it, but when it is uploaded, it streams to the specified destination. For more information on configuring this path, see <a href="c-xfer3.html#86994"><i class="title">TSFS Sockets</i></a>. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="83946">Socket via TCP/IP </a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="83947"> </a>When you select <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Socket via TCP/IP</font></b> from the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Upload Path</font></b> drop-down combo box, the default path presented is <i class="textVariable">hostname/</i><b class="file">6164</b>. When upload occurs, it goes from the socket on the target to the socket connection on the host which you have configured. You can configure the host socket by opening the view graph using <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">File>New</font></b> on the main <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Tools</font></b> menu or by starting <b class="symbol_lc">evtRecv</b>. The port number indicated on the view graph or used by <b class="symbol_lc">evtRecv</b> must match the port number in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Control Properties</font></b> dialog box. Data is uploaded either continuously or when you request it, but when it is uploaded, it streams to the specified destination. For more information on configuring this path, see <a href="c-xfer3.html#86890"><i class="title">TCP/IP</i></a>. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="88273">NFS to File </a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="88275"> </a>When you select <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">NFS to File</font></b> from the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Upload Path</font></b> drop-down combo box, the default path presented is <b class="file">/eventLog.wvr</b>. You must configure NFS on your target so it can find this file. Data is uploaded either continuously or when you request it, but when it is uploaded, it is written to this file. To view and analyze the data, you must load the log file into WindView using <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Open</font></b> from the main <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">File</font></b> menu. For more information on configuring this path, see <a href="c-xfer3.html#87159"><i class="title">Using NFS</i></a>. </p></dl></dl><a name="foot"><hr></a><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-upload.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-upload.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-upload2.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-upload4.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p></body></html><!---by WRS Documentation (), Wind River Systems, Inc. conversion tool: Quadralay WebWorks Publisher 4.0.11 template: CSS Template, Jan 1998 - Jefro --->⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -