app.telemetry - How to map Fabasoft Folio object addresses to names or references

Last update: 4 August 2017

app.telemetry - How to map Fabasoft Folio object addresses to names or references

Information

Fabasoft Folio object addresses (a.k.a. COO-addresses) are exact but quite meaningless in respect to the character of the object they represent. It is mainly for the sake of optimization that the Fabasoft app.telemetry instrumentation of Fabasoft Folio uses the 64-bit integer representation of the addresses to pass object identity information. Whereas the conversion to the "COO-Address" format has been coded into Fabasoft app.telemetry, a more user friendly way of presenting Fabasoft Folio objects is still available.

Solution

Mapping of addresses to Names and References

Providing an XML file containing a mapping from object address to names or references Fabasoft app.telemetry can represent Fabasoft Folio addresses in human readable format to help users to interpret recorded request information more easily.

Generating the mapping file

In order to generate the mapping file the "Integration for app.telemetry Software-Telemetry" Software Component provides the XSL Transformation file FSCAPPTELEMETRY@1.1001:GenerateLogAnalyzerData. Calling this XSL Transformation by a script or by a Fabasoft Expression you receive an XML file containing the addresses and names of the following object classes:

  • Software Product
  • Software Component
  • Component Object (and all derived object classes)
  • User
  • Group
  • Domain

To generate the mapping file execute the following command on a Fabasoft Folio Server (call the command in one line):

fsceval.exe -eval "coouser.COOXML@1.1:XSLTransformObject(coouser,
FSCAPPTELEMETRY@1.1001:GenerateLogAnalyzerData, 'fscdata.xml')"

Note: In earlier Fabasoft Folio or Fabasoft eGov-Suite installations the component name was FSCAPPLSTRUDL@1.1001 instead of FSCAPPTELEMETRY@1.1001. In that case you have to use the following execution command:

fsceval.exe -eval "coouser.COOXML@1.1:XSLTransformObject(coouser,
FSCAPPLSTRUDL@1.1001:GenerateLogAnalyzerData, 'fscdata.xml')"
Where to store the mapping file

Whereas in the combination with the Fabasoft app.strudl Java Client this file had to be provided in a user settings folder on the client machine running the java application, the Fabasoft app.strudl Browser Client receives the formatted values from the Fabasoft app.telemetry Webservice, which is therefore responsible for the formatting of the addresses. This implies, that the mapping file has to be stored in the configuration folder on the webservice under the following path:

  • Linux /etc/app.telemetry/fscdata.xml Make sure, that the apache user may read the file.
  • Windows Server 2003 C:\Documents and Settings\All Users\Application Data\Fabasoft app.telemetry\fscdata.xml Make sure, that the everyone may read the file. You have to restart IIS (or recycle the application pool) to apply the changes.
  • Windows Server 2008 C:\ProgramData\Fabasoft app.telemetry\fscdata.xml Make sure, that the everyone may read the file. You have to restart IIS (or recycle the application pool) to apply the changes.