Preparation and deployment to Message Broker
Having built an assembly file from the C# code, you can drag and drop the assembly file from a Windows Explorer window directly onto a .NETCompute node in a message flow in order to associate the node with the code. This technique results in a hard-coded absolute location for the assembly. This approach saves time when developing, testing, and hot-swapping the .NET code that the Broker is executing. For production situations, a more typical approach is to define a Message Broker Configurable Service that specifies to a .NETCompute node where to locate the assembly file. If a Configurable Service is used, it will override a hard-coded absolute location for the assembly. Here is the drag and drop technique for the configuration of the current scenario:
- To prepare for the drag and drop, return to the WebSphere Message Broker Toolkit, where the message flow
MyFlow.msgflowthat you created earlier should still be open. Open a Windows Explorer window in front of the Toolkit and navigate to the location where you built the assembly file in the previous section. If you have followed the default naming so far, the location will be:
C:\student\DOTNET\lab_msword\visual studio 2010\Projects\MSWordDotNetProject\ MSWordDotNetProject\bin\Debug\MSWordDotNetProject.dll
Drag and drop the assembly on top of the .NETCompute node in the flow, as shown by the red arrow:
- Inspect the properties of the .NETCompute node and you should see that the Assembly name property has now been configured, as shown below.
Save the message flow by pressing Ctrl-S:
- In order to deploy the application (which contains the message flow and Web service definition) you have created, simply drag and drop it onto a runtime execution group,
such as the default configuration shown below. The red arrow shows the drag and drop movement:
The next section of the tutorial shows you how to test the scenario.