Go from installation to integration without costly training or services
There are a wide range of integration products to choose from. But only Neuron ESB is built on the simplicity of Microsoft's .NET platform. That means any .NET developer already has the tools and skills to quickly install and connect Neuron ESB to all common .NET systems and applications in the cloud or on-premises for a fraction of the cost of other Java-based products.
Easy to install
Easy to connect
Easy to adapt
I need a simple, reliable way to connect my .NET systems and applications
Most Java-based integration products claim to have all the features you need to connect your .NET applications. But you’ll likely need to hire an expensive consultant to help adapt your new Java-based infrastructure. Even Microsoft’s own BizTalk – which is difficult and costly to develop, deploy and manage – isn’t a pure .NET integration solution.
Neuron ESB is the only product built specifically for .NET integration
Built for .NET developers by .NET developers, Neuron ESB’s familiar .NET features and drag-and-drop graphical designer enable you to quickly and easily orchestrate and connect all your external systems, databases, transports and protocols, reducing the need for costly services.
Neuron ESB offers a vast array of integration capabilities that you can quickly configure without having to write a bunch of code. Once configured, Neuron ESB applications are auto-compiled .NET artifacts that support in-place debugging. And you’ll be able to set breakpoints to peer into memory and the environment as applications execute.
Messaging applications, service broker and connectors are hosted in Neuron ESB’s main hosting environment, isolated within dedicated .NET app domains. Workflows have dedicated hosts specifically designed to extend Windows Workflow Foundation and provide the business resiliency enterprises require. For flexibility, different Neuron ESB applications, or even different pieces of the same application, can be separated into their own hosts, giving you full control over application deployment architecture.
Neuron ESB deployment methodology is also very flexible. You can deploy applications by copying their file trees to another Neuron ESB server (XCopy deployment). Or you can use Neuron ESB Explorer to create deployment packages the can be dropped into another installation. And Neuron ESB supports deployment from source controls such as Microsoft Team Foundation Server or Git.
For added convenience and security, Neuron ESB’s rich environment variable features enable you to change things like connection strings and account names between development and production. You don’t need to know security details about the production environment to quickly prepare a new application for deployment. Just load a new set of default environment variables, and you're ready to go.
From instantiating .NET assemblies built in Visual Studio to coding C# directly in the Neuron Explorer interface, Neuron ESB’s unmatched extensibility makes it easy to:
- Build custom connectors for home grown systems and applications
- Add .NET assemblies to applications by reference
- Type .NET code directly into process and workflow shapes
- Leverage connector framework and samples to build new connectors
- Use Neuron ESB’s .NET debugger to see inside artifacts as they execute
Connect your business critical infrastructure as soon as Neuron ESB is installed, using built-in connectors for:
- TCP and Named Pipes for real-time messaging
- MSMQ and Rabbit MQ for durable messaging
- Service protocols (e.g. SOAP, REST any WCF Binding)
- Email protocols (POP3, SMTP and Microsoft Exchange)
- Databases (e.g. ODBC, DB2, Oracle, SQL)
- File systems (e.g. SMB, SFTP/FTP/FTPS, Dropbox)
- Line of Business Systems (e.g., Dynamics, SharePoint, NetSuite, Salesforce, SAP)
Neuron ESB leverages .NET infrastructure, operations and management techniques to ensure your applications quickly plug into your existing.NET processes. It supports Windows Management Interface reporting and raises execution events and errors in the Windows event log.