Remote Deployment

If the Neuron ESB Client API (i.e. Party) is hosted in remote .NET applications, several Neuron ESB assemblies must be deployed. Generally, if hosting the Neuron ESB Client API in .NET applications, developers should ensure that all dependent assemblies are included in their respective BIN directories or in the search path of their application. The Neuron ESB Client API can be installed directly from the installer. Alternatively, Microsoft Visual Studio developers can use NuGet to download the latest Neuron ESB SDK (Client API):

• NeuronEsb.ClientApi: The Neuron ESB client assemblies This should contain all assemblies required for any Business Process.

If manually deploying dependent assemblies, the base Neuron ESB client assemblies are required:

• Neuron.Esb.dll
• Neuron.Esb.resources.dll
• Neuron.Esb.XmlSerializers.dll
• Neuron.dll

All Business Processes attached to a Party require the following assemblies:

• Neuron.Pipelines.dll
• Neuron.Scripting.dll
• Newtonsoft.Json.dll

If a Business Process is using a Publish Process Step to forward messages to a Rabbit MQ based Topic, the following is required:

• RabbitMQ.Client.dll

If a Business Process is using the Service Endpoint Process Step, the following are required:

• Microsoft.ServiceModel.Channels.dll
• Microsoft.ServiceBus.dll

If a Business Process is using the Compression Process Step, the following are required:

• Xceed.Compression.Formats.v5.8.dll
• Xceed.Compression.v5.8.dll
• Xceed.FileSystem.v5.8.dll
• Xceed.Zip.v5.8.dll

If custom Process Steps or third party assemblies are referenced within a Business Process, those assemblies must be deployed as well.

Tracing and Reporting

When using the Neuron ESB Client API hosted in custom .NET applications, all warnings and exceptions will be reported in the Windows Application Event Log. Additionally, the Neuron ESB TraceSwitch flag can be added to the custom .NET applications app.config file to control the level of logging for the Neuron ESB Client API. Following is an example of the configuration. Any Verbose, Informational, Warning or Error will be written to the default Trace Listener.

<configuration>
<system.diagnostics>
<switches>
<!-- This switch controls ESB trace messages. -->
<!-- Value Meaning -->
<!-- ===== ======= -->
<!-- 0 No tracing -->
<!-- 1 Trace errors -->
<!-- 2 Trace errors + warnings -->
<!-- 3 Trace errors + warnings + info -->
<!-- 4 Trace errors + warnings + info + verbose -->
<add name="esbTraceSwitch" value="3"/>
</switches>
</system.diagnostics>

Read more about tracing in the Tracing APIs section of this document.