Neuron ESB 3.0 Release - Neuron ESB User Network2024-03-28T13:22:22Zhttp://forum.neuronesb.com/forum/categories/neuron-esb-3-0-release/listForCategory?feed=yes&xn_auth=noWhere is the product documentation?tag:forum.neuronesb.com,2014-10-14:2748813:Topic:264002014-10-14T19:31:04.740ZDavid Solivanhttp://forum.neuronesb.com/profile/DavidSolivan
<p>I clicked the link on the Neuron ESB resources page and came to this user group. I don't see a link to the product documentation. Am I missing something?</p>
<p>I clicked the link on the Neuron ESB resources page and came to this user group. I don't see a link to the product documentation. Am I missing something?</p> Facing Object reference set to null issue, with rabbitmqtag:forum.neuronesb.com,2014-08-05:2748813:Topic:257622014-08-05T15:16:03.459Zvikas yadavhttp://forum.neuronesb.com/profile/vikasyadav
<p>I am facing weird issue with Neuron. When I try to publish(multicast) a message with RabbitMQ as transport, I am getting "Object reference null" error. But When I tried same code from the machine where Neuron is installed, Its working fine.</p>
<p></p>
<p>I am getting following exception:</p>
<p>System.NullReferenceException: Object reference not set to an instance of an object.<br></br> at Neuron.Esb.Channels.Amqp.AmqpChannel.Send(ESBMessage message)<br></br> at…</p>
<p>I am facing weird issue with Neuron. When I try to publish(multicast) a message with RabbitMQ as transport, I am getting "Object reference null" error. But When I tried same code from the machine where Neuron is installed, Its working fine.</p>
<p></p>
<p>I am getting following exception:</p>
<p>System.NullReferenceException: Object reference not set to an instance of an object.<br/> at Neuron.Esb.Channels.Amqp.AmqpChannel.Send(ESBMessage message)<br/> at Neuron.Esb.Channels.ESBChannelManager.SendMessage(ESBMessage message)<br/> at Neuron.Esb.Channels.ESBChannelManager.PublishInternal(ESBMessage message)<br/> at Neuron.Esb.Channels.ESBChannelManager.Publish(ESBMessage message)<br/> at Neuron.Esb.Channels.ESBTopicContext.Publish(ESBMessage message)<br/> at Neuron.Esb.Party.SendMessage(ESBMessage message, Boolean duplicateMessage)<br/> at Neuron.Esb.Party.SendMessage(ESBMessage message, SendOptions options, String targetId, String action, String schema)<br/> at Neuron.Esb.Party.Send(String topic, Object obj, SendOptions options, String targetId, DateTime expires, String action, String schema)<br/> at Neuron.Esb.Party.Send(String topic, Object obj, SendOptions options, String targetId, DateTime expires, String schema)<br/> at Neuron.Esb.Party.Send(String topic, Object obj, SendOptions options, String targetId)<br/> at Neuron.Esb.Party.Send(String topic, Object obj, SendOptions options)<br/> at Neudesic.EnterpriseServiceBus.Samples.Sender.Main(String[] args) in </p>
<p> </p> Change file name in Process feedtag:forum.neuronesb.com,2013-10-25:2748813:Topic:218222013-10-25T19:31:54.137ZFred Berhhardthttp://forum.neuronesb.com/profile/FredBerhhardt
<p>We are on Neuron 3.0.3.242. I need to change the input file name two different times in order to put out files in the name format expected by one of our vendors. What I've done is save the input file name in the file_in.Name property. Then ina later step get the name from the property into a string append a few characters to it and do a set property for file_out.Name. I also use the file_out.Type to change the file extension.</p>
<p>When I run the process I get the original file name…</p>
<p>We are on Neuron 3.0.3.242. I need to change the input file name two different times in order to put out files in the name format expected by one of our vendors. What I've done is save the input file name in the file_in.Name property. Then ina later step get the name from the property into a string append a few characters to it and do a set property for file_out.Name. I also use the file_out.Type to change the file extension.</p>
<p>When I run the process I get the original file name without my changes but with the new file type. When I look at the custom properties on the message in the Activities - Failed Message screen I can see that the file_out Name is what I changed the file name to, but the file name part is not changed. I get an error saying the file name already exists when trying to write the file.</p>
<p> </p>
<p>Not sure what I'm doing wrong or leaving out. </p> Upgrading to Neuron ESB 3.0tag:forum.neuronesb.com,2013-02-26:2748813:Topic:182942013-02-26T01:02:00.289ZMartin Wasznickyhttp://forum.neuronesb.com/profile/MartyWasznicky
<h1>Upgrading From a Previous Neuron Release</h1>
<p>The procedures in this topic show you how to upgrade from Neuron 2.6, to Neuron ESB 3.0. For assistance with upgrades from earlier versions of Neuron ESB, please contact support for guidance.</p>
<p> </p>
<p>Upgrading from a previous release of Neuron ESB is fairly straight-forward. The basic steps are below. This sequence of steps needs to be repeated for each instance of Neuron ESB on the same server. The only exception would be step 6,…</p>
<h1>Upgrading From a Previous Neuron Release</h1>
<p>The procedures in this topic show you how to upgrade from Neuron 2.6, to Neuron ESB 3.0. For assistance with upgrades from earlier versions of Neuron ESB, please contact support for guidance.</p>
<p> </p>
<p>Upgrading from a previous release of Neuron ESB is fairly straight-forward. The basic steps are below. This sequence of steps needs to be repeated for each instance of Neuron ESB on the same server. The only exception would be step 6, upgrading the Neuron Auditing Server. If multiple instances are using the same auditing database you only need to upgrade it once. Note, however, that if multiple instances are utilizing the same auditing database, you will need to complete each of the steps below for every one of those instances before moving to the next step. This is because once you upgrade the database, other instances utilizing that database will stop running.</p>
<p>Upgrading Neuron ESB:</p>
<p></p>
<ol>
<li>Download Neuron ESB 3.0</li>
<li>Complete message processing</li>
<li>Backup configuration files</li>
<li>Uninstall previous version</li>
<li>Upgrade Dependencies for Neuron 3.0</li>
<li>Install new version</li>
<li>Replace backed-up files</li>
<li>Upgrade Neuron Auditing Database (optional, only required if using features that require the use of a database)</li>
<li>Migrate Neuron ESB Configurations</li>
<li>Upgrade considerations</li>
</ol>
<p> </p>
<p>Once you complete step 4 - Install New Version, do not start the ESB Service until you've completed all the steps.</p>
<h2>Download Neuron ESB 3.0</h2>
<p>You can download Neuron ESB 3.0 from here: <a href="http://support.neuronesb.com/downloads/NeuronInstall_Latest.zip">Neuron ESB 3.0</a></p>
<h2>Complete Message Processing</h2>
<p>Before taking the steps to upgrade a Neuron ESB Server, make sure all in-flight messages have completed processing. This typically involves making sure all of the publishers stop publishing messages to the ESB, and if you're using MSMQ-based topics, letting all of the queues empty. </p>
<h2>Backup Configuration Files</h2>
<p>Any Neuron ESB configuration files you have modified should be backed up prior to upgrading. One reason for this is that the uninstall process will remove any standard configuration files that are normally installed (i.e. esbservice.exe.config). Some of the files to back-up are any application configuration files (esbservice.exe.config, neuronpipelines.config), any custom assemblies (adapters, processes or other assemblies you've copied to the installation folder) and all Neuron ESB Configuration folders you've created for your solutions. You can copy these files back to the installation directory after reinstalling Neuron ESB.</p>
<h2>Uninstall Previous Version</h2>
<p>The Neuron ESB installer does not perform an in-place upgrade. You have to uninstall the current version prior to installing the new version. Use Add/Remove Programs to uninstall Neuron ESB.</p>
<h2>Upgrade Dependencies for Neuron 3.0</h2>
<h3>Prerequisites</h3>
<p>In order to install and run Neuron ESB 3.0, the following software needs to be installed on your computer. The Neuron ESB 3.0 installer will attempt to locate these software packages on your computer. Please use the hyperlinks below to download the software packages and install them on your computer prior to installing Neuron ESB 3.0.</p>
<ul>
<li><a href="http://www.microsoft.com/en-us/download/details.aspx?id=17718">Microsoft .NET Framework 4</a></li>
<li><a href="http://www.microsoft.com/en-us/download/details.aspx?id=8483">Windows Installer 4.5</a></li>
</ul>
<h3>Additional Software</h3>
<p>Neuron ESB 3.0 introduces a new channel type that is based on RabbitMQ Server. Installation of RabbitMQ Server is optional and is not required to use Neuron ESB 3.0. If RabbitMQ Server is not installed, the Neuron ESB 3.0 installer will give you the option of automatically downloading and installing Erlang and RabbitMQ Server. If you want to use the new AMQP channel type, but your computer does not have Internet access, please download and install the following software packages before installing Neuron ESB 3.0.</p>
<ul>
<li><a href="http://support.neuronesb.com/downloads/neuron30/prereqs/otp_win32_R15B01.exe">Erlang</a></li>
<li><a href="http://support.neuronesb.com/downloads/neuron30/prereqs/rabbitmq-server-2.8.5.exe">RabbitMQ Server</a></li>
</ul>
<h2>Install New Version</h2>
<p>Neuron ESB 3.0 is now installed using a new bootstrapper installer, Setup.exe. This installation wraps the “old” .msi and includes the installations of RabbitMQ and Erlang. Setup.exe also gives you the ability to install multiple instances. To install Neuron ESB 3.0, run Setup.exe. Do not start the Neuron ESB Service yet!</p>
<h2>Replace Backed-Up Files</h2>
<p>Replace all of the files you previously backed-up.</p>
<h2>Upgrade The Neuron Auditing Database</h2>
<p>You must upgrade your Neuron Auditing Database before starting the Neuron ESB Service. There is a SQL script you can use to upgrade a 2.6 version of the database to 3.0. After installing Neuron 3.0, that script will be found at C:\Program Files\Neudesic\Neuron ESB v3\Sql\Updates\Update_To_3.0.sql. </p>
<h2>Migrate Neuron ESB Configurations</h2>
<p>Before configuring and starting the Neuron ESB 3.0 service, your ESB Configurations need to be migrated. In Neuron ESB 3.0, the Neuron ESB Configurations are now saved in a folder structure instead of a single .esb file. Instructions on how to migrate your current Neuron ESB Configurations can be found here : <a href="http://forum.neuronesb.com/forum/topics/migrating-from-2-6-to-neuron-esb-3-0">http://forum.neuronesb.com/forum/topics/migrating-from-2-6-to-neuron-esb-3-0</a></p>
<p><span style="font-size: 1.5em;">Upgrade Considerations</span></p>
<h3>Side-by-Side Support</h3>
<p>Neuron ESB 3.0 and 2.6 is supported when installed side-by-side. However, some precautions need to be taken into consideration before configuring this scenario. </p>
<ul>
<li>Discovery Services – When you install either version of Neuron ESB, a Discovery Service is also installed for that version. The Discovery Services are used by Neuron ESB Explorer to discover the various instances of that version of Neuron. By default the 2.6 version of the discovery service is configured to use a different TCP port than the 3.0 version. There should be no issues when running side by side.</li>
</ul>
<ul>
<li>ESB Configurations – ESB Configurations are created with a set of default port values which are defined in the Zones. When you install Neuron 2.6 and 3.0 for side-by-side execution, one of the ESB configurations will need to be modified to change these port values. If you fail to do this, the first ESB Instance you start will start just fine. The second instance will fail to start and report port conflicts.</li>
</ul>
<p> </p> Migrating from 2.6 to Neuron ESB 3.0tag:forum.neuronesb.com,2013-02-26:2748813:Topic:182922013-02-26T01:00:50.506ZMartin Wasznickyhttp://forum.neuronesb.com/profile/MartyWasznicky
<h1>Migrating Neuron ESB Configurations to 3.0</h1>
<p>The procedures in this topic show you how to migrate your existing Neuron 2.6 configurations to the mew Neuron ESB 3.0 format. In Neuron ESB 3.0, the Neuron ESB Configurations are now saved in a folder structure instead of a single .esb file. </p>
<p> </p>
<p>Migrating your Neuron ESB configurations:</p>
<ol>
<li>Migrate the ESB Configuration</li>
<li>Configure and Start the Neuron ESB Service</li>
<li>Migration…</li>
</ol>
<h1>Migrating Neuron ESB Configurations to 3.0</h1>
<p>The procedures in this topic show you how to migrate your existing Neuron 2.6 configurations to the mew Neuron ESB 3.0 format. In Neuron ESB 3.0, the Neuron ESB Configurations are now saved in a folder structure instead of a single .esb file. </p>
<p> </p>
<p>Migrating your Neuron ESB configurations:</p>
<ol>
<li>Migrate the ESB Configuration</li>
<li>Configure and Start the Neuron ESB Service</li>
<li>Migration Considerations</li>
</ol>
<h2>Migrate the ESB Configuration</h2>
<ol>
<li>Open the Neuron ESB Explorer and create a new configuration</li>
<li>From the menu, click File->Import...</li>
</ol>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036247?profile=original" target="_self"><img width="750" src="http://storage.ning.com/topology/rest/1.0/file/get/104036247?profile=RESIZE_1024x1024" width="750" class="align-center"/></a> 3. From the Import ESB Configuration dialog, browse for you .esb file (or .xml), select it and click the Open button</p>
<p></p>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036389?profile=original" target="_self"><img width="750" src="http://storage.ning.com/topology/rest/1.0/file/get/104036389?profile=RESIZE_1024x1024" width="750" class="align-center"/></a></p>
<p> 4. In the Import Configuration dialog, select the artifacts you want to import (usually all of them for a migration), and click the Import button in the toolbar:</p>
<p></p>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036334?profile=original" target="_self"><img src="http://storage.ning.com/topology/rest/1.0/file/get/104036334?profile=original" width="544" class="align-center"/></a></p>
<p></p>
<p> 5. You may receive an Import Conflict warning that an artifact already exists. You have the option to Click Yes for each warning, or, if you want to disable the remaining warnings, check the box to not show additional warnings.</p>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036238?profile=original" target="_self"><img src="http://storage.ning.com/topology/rest/1.0/file/get/104036238?profile=original" width="490" class="align-center"/></a></p>
<p></p>
<p> 6. Save the new Neuron Configuration by clicking File->Save As from the menu:</p>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036508?profile=original" target="_self"><img width="750" src="http://storage.ning.com/topology/rest/1.0/file/get/104036508?profile=RESIZE_1024x1024" width="750" class="align-center"/></a></p>
<p></p>
<p></p>
<p> 7. In the Save ESB Configuration dialog, click the "New Folder" button (in red below) to create a new folder for you ESB configuration:</p>
<p></p>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036392?profile=original" target="_self"><img src="http://storage.ning.com/topology/rest/1.0/file/get/104036392?profile=original" width="571" class="align-center"/></a></p>
<p></p>
<p></p>
<p> 8. You Must navigate into the new folder before clicking the Select button:</p>
<p></p>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036348?profile=original" target="_self"><img src="http://storage.ning.com/topology/rest/1.0/file/get/104036348?profile=original" width="571" class="align-center"/></a></p>
<p></p>
<p></p>
<p>The Neuron ESB Configuration is now saved in the new file format!</p>
<h2>Configure and start the Neuron ESB Service</h2>
<p>Now that the ESB Configuration has been saved in the new format, you need to reconfigure</p>
<p>the Neuron ESB Service to use the new configuration.</p>
<p></p>
<ol>
<li>Click "Configure Server" from the toolbar:</li>
</ol>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036245?profile=original" target="_self"><img width="750" src="http://storage.ning.com/topology/rest/1.0/file/get/104036245?profile=RESIZE_1024x1024" width="750" class="align-center"/></a></p>
<p></p>
<p> 2. In the Configure Server dialog, click the ellipsis next to the ESB Configuration Folder text box:</p>
<p></p>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036242?profile=original" target="_self"><img src="http://storage.ning.com/topology/rest/1.0/file/get/104036242?profile=original" width="582" class="align-center"/></a></p>
<p></p>
<p> 3. In the Select ESB Configuration dialog, browse to the folder containing your newly saved ESB Configuration. Remember to browse INTO the folder before clicking the Select button. Then click Save and OK.</p>
<p></p>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036400?profile=original" target="_self"><img src="http://storage.ning.com/topology/rest/1.0/file/get/104036400?profile=original" width="571" class="align-center"/></a></p>
<p></p>
<p></p>
<p> 4. From the toolbar, click Start from the Start/Stop/Restart dropdown:</p>
<p></p>
<p><a href="http://storage.ning.com/topology/rest/1.0/file/get/104036385?profile=original" target="_self"><img width="750" src="http://storage.ning.com/topology/rest/1.0/file/get/104036385?profile=RESIZE_1024x1024" width="750" class="align-center"/></a></p>
<p></p>
<p>Your Neuron ESB Configuration has now been migrated and successfully started!</p>
<h2>Migration Considerations</h2>
<h3>Business Processes</h3>
<p>The Audit Step has been updated to provide the following options:</p>
<ul>
<li>Whether or not to audit the message body</li>
<li>Whether or not to audit custom message properties</li>
</ul>
<p>When migrating an ESB Configuration that includes business processes with Audit Steps, the migration will set these two properties to False. You will need to revisit these processes to set these two properties to their appropriate values.</p>
<p></p>