Namespace: |
|
Content: |
complex, 4 attributes, 1 element |
Defined: |
globally in ccapp.xsd, see XML source |
Includes: |
definitions of 4 attributes and 1 element |
Used: |
at 1 location |
XML Representation Summary | |||||
<... | |||||
numDigits | = |
xsd:int : "3" | |||
outputFileName | = |
xsd:string : "callTrace.log" | |||
sheetName | = |
xsd:string : "callTrace" | |||
tableName | = |
xsd:string : "callTrace" | |||
> | |||||
|
|||||
</...> |
The output file name for the trace is given using the attribute outputFileName which defaults to callTrace.log. The format of the trace is determine by the file's extension. Note that trace files can be huge, and take time to read with most text editor, including Microsoft Excel.
By default, when sending the trace to Excel spreadsheet, a sheet named callTrace is created, and filled with the data. If more than 65535 calls are processed, a second sheet named callTrace1 is created, because Microsoft Excel limits the number of rows in a sheet. The base name of the sheet might be changed using the sheetName attribute.
Element database is used to send the trace data to a database. This requires information about the connection to the database, established using JDBC. The trace is sent to the table with name given by the tableName attribute, which defaults to callTrace.
<xsd:complexType name="CallTraceParams"> <xsd:sequence> </xsd:element> </xsd:sequence> </xsd:attribute> </xsd:attribute> </xsd:attribute> </xsd:attribute> </xsd:complexType> |
Type: |
|
Use: |
optional |
Default: |
"3" |
Defined: |
<xsd:attribute default="3" name="numDigits" type="ssj:positiveInt"> </xsd:attribute> |
Type: |
xsd:string |
Use: |
optional |
Default: |
"callTrace.log" |
Defined: |
<xsd:attribute default="callTrace.log" name="outputFileName" type="xsd:string"> </xsd:attribute> |
Type: |
xsd:string |
Use: |
optional |
Default: |
"callTrace" |
Defined: |
<xsd:attribute default="callTrace" name="sheetName" type="xsd:string"> </xsd:attribute> |
Note that every record in the given table is deleted at the beginning of a simulation. The trace facility assumes that the table was created using a SQL query similar to CREATE TABLE callTrace (step INTEGER, type INTEGER, period INTEGER, arvTime DOUBLE primary key, queueTime DOUBLE, outcome VARCHAR(10), agentGroup INTEGER, srvTime DOUBLE). Note that one may need to adapt this query to its specific database management system.
Type: |
xsd:string |
Use: |
optional |
Default: |
"callTrace" |
Defined: |
<xsd:attribute default="callTrace" name="tableName" type="xsd:string"> </xsd:attribute> |
Type: |
ssj:DBConnectionParams, complex content |
Defined: |
<xsd:element maxOccurs="1" minOccurs="0" name="database" type="ssj:DBConnectionParams"> </xsd:element> |
XML Schema documentation generated with DocFlex/XML (Kit) v1.6.8 DocFlex/XML (Kit) is a freeware edition of DocFlex/XML, which is a powerful template-driven documentation and report generator from any data stored in XML files. Based on an innovative technology developed by FILIGRIS WORKS, this new tool offers virtuoso data querying and formatting capabilities not found in anything else! Need to convert your XML data into a clear nice-looking documentation or reports? Web-ready hypertext HTML or printable MS Word / OpenOffice.org friendly RTF? DocFlex/XML may be a cheap, quick and effective solution exactly for this task! Have questions? Not sure how to use it? Just send us e-mail to contact@filigris.com and we are always happy to help you! See also our services at www.filigris.com |