Neuron ESB User Network

The Service Bus for the Connected Business

Updating from the 2.5.10 release to 2.5.13 is relatively easy.  It only requires an update to the ESB configuration file and installation of the new binaries.  This assumes of course that any existing Neuron Audit databases were updated with the 2.5.10 release. No modifications to the Neuron Audit database were made in this release. To update, perform the following steps:

  1. Uninstall the existing version of Neuron ESB
  2. Install the 2.5.13 release of Neuron ESB
  3. Open the Neuron ESB Explorer.
  4. Open (do select Connect) the existing Neuron ESB configuration file to update. You should receive the following prompt:

 

  1. Press the close button
    NOTE: If you did not see a dialog similar to the one above, confirm the version of the Neuron ESB installed.
  2. Press the Save button on the toolbar of the Neuron ESB Explorer to commit the new changes.

It is now safe to configure the Neuron ESB service to load the updated configuration file.

As with all updates, if you are using the Neuron ESB client API on remote machines, you must update all Neuron assemblies on those remote machines.

If the Neuron ESB Auditing Database was not updated with the previous 2.5.10 release, then it must be with this release.

To update the database, the easiest approach is simply create a new database using either the Neuron ESB Explorer or by manually running the Neuron Audit database create script (CreateNeuronDb.sql) in the Sql directory located at the root of the Neuron ESB installation directory.

If using the Neuron ESB Explorer, use the following steps:

  • Select the Deployment navigation bar
  • Select Resources -> Databases within the navigation pane. This will present the database management screen.
  • Select the New button; enter the database server name as well as a new name for a database (it should NOT already exist). Also enter the deployment group it should be associated with.
  • Select Apply. This should display a prompt requesting to create the database. The following dialog box will be displayed indicating that the database was created.

 

  • Select Save from the Neuron ESB Explorer toolbar to commit the changes.

Once the new database is created, existing data from both the MessageAudit_AllTopics, and MessageAudit_Fail database tables within the old Neuron Audit database can be imported into their respective tables within the newly created Neuron Audit database by using the data export tool that ships with SQL Server 2005/2008

Views: 78

Reply to This

Neuron ESB Product Support Forums and Communities

Latest Activity

Profile Icon

Service Connector with transactional messaging

I'm attempting to create a Service Connector with transactions enabled. The point being I would like messages only to be popped from Neuron queues when a 200 is received from the Service Endpoint.At the moment, i can only set the binding setting Message Pattern to Datagram with its corresponding service endpoint configured for one-way - with this however as you can image there is no transactional integrity. If i set it to Request-Reply the message never gets delivered.I'd like to set my Service…See More
Discussion posted by John Ryan yesterday
Profile Icon

Sending messages to a Client Connector from an C# Console App

I have an issue with sending messages to a Client Connector from a C# test app. The main issue is that  i never receive a response from Neuron and the Connection Times out. I'm using the sample code from the Scatter-Gather Pattern sample included in the documentation If anybody has any hints on what i'm missing, it would be appreciated.static class Utility {const string _propName = "NeuronServiceList";const string _ns = "urn:xmlns:neuronesb-com:soapheaders";const string _msg = @"…See More
Discussion posted by John Ryan Feb 10
Profile Icon
ThumbnailThumbnail
AMS and John Ryan joined Neuron ESB User Network Feb 10
Profile Icon

Scalability MSMQ & Deployment Groups

I have been trying to work out how to configure MSMQ for high availaibility. I think that I need to use Zones, & Deployment Groups to configure the server deployment.  But I am unsure how  I would go about this and what the perfromance impacts are. So let me give you the scenario that I am looking at and you can then point me in teh direction of resources that I need to be able to resolve it. I have 3 High throughput topics that need reliable messaging Service1Service2Service3 Each of these…See More
Discussion posted by Alixx Skevington Feb 7
Profile Icon
Alixx Skevington is now a member of Neuron ESB User Network Feb 6
Profile Icon
Umesh Kumar Maurya is now a member of Neuron ESB User Network Jan 24
Profile Icon
David Gnabasik is now a member of Neuron ESB User Network Dec 16, 2011
Profile Icon

Explanation of Pipelines

Hi Guys,               I need more documentation/info on how pipelines work. It appears that a context is the message that is passing though the pipeline. I want to use a code step to generate a new message to that will be passed to a service step. But I can not find any detail on how to use the context object. Regards,                   AlistairSee More
Discussion posted by Alistair Rigney Dec 7, 2011

Badge

Loading…

© 2012   Created by Neuron Admin.   Powered by .

Badges  |  Report an Issue  |  Terms of Service