Neuron ESB Tip of the Day

Comment by John Petersen on April 9, 2015 at 6:56am

If you want to take advantage of using statements in C#. use the C# CLASS step in a business process. 

Comment by John Petersen on April 10, 2015 at 7:20am

Compliments of the guys from Dude Solutions:

Remember that Neuron ESB can host your SOAP and REST endpoints. You don't need to stand-up a separate service in Visual Studio!

Comment by John Petersen on April 13, 2015 at 8:11am

Use the XML Docs in the Repository to hold your templates. Then, you can reference them in code. For example, if we have an XML template called "CD Catalog" - in code, we can reference the xml (as a string) as follows: 

context.Configuration.XmlDocs["CD Catalog"].Xml;

This gets you out of having to manually concatenate long strings in your code. 

Instead, you can embed placeholders in the XML and use string operations as part of a micro-templating scheme. 

Comment by John Petersen on April 15, 2015 at 12:46pm

Neuron ESB has a rich RESTful management API. For more info on that, for your Neuron ESB Server, navigate to: http://servername>>:51002/help

Comment by John Petersen on April 17, 2015 at 10:15am

Be sure to check your service policies on how you are handling failures. Make sure you are not discarding failed messages. 

Comment by John Petersen on April 21, 2015 at 7:16am

Want an easy way to inspect SOAP Services that you wish to consume in Neuron ESB? Check out SOAP UI: http://sourceforge.net/projects/soapui/. 

Comment by John Petersen on April 22, 2015 at 6:07am

Often, when working with you to diagnose problems, the Neuron ESB Team may ask you for a process dump. To do this, you need the sysinternals suite from MS. It's a free download available here: https://technet.microsoft.com/en-us/sysinternals/bb842062.aspx.

To create a dump, enter this command in the command prompt:

Procdump -ma ESBService

The resulting file will be fairly large, so be sure to zip before sending. 

Comment by John Petersen on April 23, 2015 at 12:15pm

If you are experiencing issues with Neuron, one of the easiest things you can do to get a first, quick glance at potential causes is to go to the event viewer, delete the activity. Then, restart the server. Finally, open the event viewer in the Explorer and watch the events (hitting refresh). If you are not  seeing errors, then your next step is to consult the logs. 

Comment by John Petersen on April 27, 2015 at 5:54am

If you want to gain insight into what Neuron ESB is sending to an external service exposed via a Service Connector, use the Proxy Settings. For the given Service Endpoint, navigate to the Proxy Tab. If you are using something like Fiddler are working locally, click the custom option, enter 127.0.0.1 for the host and if the Fiddler Defaults are set, enter 8888 for the port. 

Comment by John Petersen on June 1, 2015 at 6:12am

In a Business Process, we often have to manually publish a message to a topic that could change from call to call. By default, the topic selector for the Publish Step is a constant. If you select the Code Selector Type instead, you can dynamically set the topic. If you need to simply publish the message to the same topic as the current message - issue this code: return message.Header.Topic;

Comment