- Install Microsoft Visual Studio 2010 or
2012. Some restrictions, for example .NET debugging,
apply if you use the Express edition.
- Create a message flow that contains a .NETInput node.
Tip: If the IBM® Integration Toolkit is
installed after Microsoft Visual Studio,
the broker Project templates will be automatically installed ready
for you to use. However, if the IBM Integration Toolkit is
installed first, you must manually install the Microsoft Visual Studio templates. This installation
can be achieved by running the file IBM.Broker.DotNet.vsix and
stepping through the wizard, accepting the license file as part of
the process. If the default installation location was used for IBM Integration Toolkit, the file can be found at
the location C:\Program
Files (x86)\IBM\IntegrationToolkit90\wmbt.
You write and compile your code in
Microsoft Visual Studio. The following
IBM Integration Bus templates are provided for
C#, Visual F#, and Visual Basic:
- Create a polling-based IBM Integration input node.
- Create an event-driven IBM Integration input node.
- Double-click the .NETInput node. Alternatively,
right-click the node and select Open Microsoft Visual Studio. If there is a Microsoft Visual
Studio project or solution name on the Visual Studio panel,
the project or solution automatically loads when Microsoft Visual Studio opens.
- In Microsoft Visual Studio, select New
Project. You can then select an IBM
Integration project from beneath the language of your
choice; C#, F# and Visual Basic.
- Select a project from the list. For the .NETInput node, you can choose:
- Create a polling-based IBM Integration input node
- Create an event-driven IBM Integration input node
The project then generates skeleton code that matches
the selected type. This skeleton code then displays in the corresponding
.NET language editor, for example; C#.
- Expand the UserCode region, and write
your code. Content assist is available in this region.
Press Ctrl+Space to invoke it.
- Optional: Use the methods available for your .NETInput node. See Methods for a .NETInput node.
- Save the class and build the solution, making a note of
the path to the assembled file.
Next: - You might want to debug your .NET code.
To debug a.NETInput node that is running
inside the integration server, place the .pdb file
for the assembly that implements the node in the same directory as
the assembly for the node, and attach Microsoft Visual Studio to the DataFlowEngine.exe process.
You can then place breakpoints in your code and examine variables,
for example; when the breakpoint is hit.
- Associate your code with the .NETInput node.
Last updated Friday, 21 July 2017