Contents

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To run any of the sample program, make sure that the .dll "fmq-csharp-native.dll", which is present under %FMQ_DIR%\clients\nativecsharp\assembly, should be present locally or should be present in the Global Assembly Cache.

FioranoMQ NativeCSharp Client Logging

To perform FioranoMQ NativeCSharp ClientRTL logging, the logger levels have to be mentioned in the configuration file "NLog.config". By default, the logger level for all the services is set to "Trace" as below, and the logs are printed to a file named "Log.out" into the same location from where the sample is running.

Code Block
<logger name="Fiorano.FMQ.Services.ClientRootLoggerServices.FMQClientLoggerServices.*" minlevel="Trace" writeTo="logfile" />

There is also a provision to specify the logger level on a particular service by uncommenting that service in the configuration file itself. By default, all the services are commented under the <rules> section in this configuration file. The logger levels can be "Fatal, Error, Warning, Info, Debug, Trace".

Note

All the Logger configuration files are present in the %FMQ_DIR%\clients\nativecsharp\assembly\Logging directory.

In order to enable Client Logging, make sure that these logger files, should be present/copied locally where the sample is running or should be present in the Global Assembly Cache.

Warning

Do not rename any of these Logger files, which may throw an exception on the client console.

PTP Samples

AdminAPI

Following example illustrates the use of FioranoMQ Administration APIs for creation of JMS, administered objects such as Destinations and ConnectionFactories:

...

Adaptavist ThemeBuilder EngineAtlassian Confluence