Tasks to complete after generating the Service Facade to Microsoft .NET: request-response pattern

Tasks that you must complete after you have generated the pattern.

The pattern generates an application that uses an ESQL Compute node to invoke your Microsoft .NET assembly. The ESQL code defines the .NET methods as a sequence of EXTERNAL procedures. Each PROCEDURE points to the .NET assembly with an absolute path in an ASSEMBLY declaration. This approach of loading the .NET assembly from a file system location is useful when the assembly is being changed during development. For final testing and production it is recommended to deploy the .NET assembly as part of the BAR file along with the application. For more information on how to do this, see the .NET application domains overview topic, available in the Message Broker help.

Message Broker Deployment

  1. Create the broker archive (BAR) file. The message flow must be added to a broker archive file.
    1. Click File > New > BAR file.
    2. Enter the name of your application or select one from the displayed list. The list is filtered to show only projects in the active working set.
    3. Enter a name for the BAR file that you are creating.
    4. Click Finish. A file with a .bar extension is created and is displayed in the Navigator view, under the Broker Archives folder. The Content editor for the BAR file opens.
    5. On the Prepare tab, select the generated application to add it to your BAR file.
    6. Select Compile and in-line resources and then click Build and Save to create your BAR file.
  2. Configure the broker archive file. Further configuration of the message flow in the broker archive file is not required before you deploy the message flows for your Service Facade to Microsoft .NET: request-response pattern instance, but you might want to review some of the default options and configure changes for your environment. In the Manage page of the Broker Archive editor:
    1. Optional: Use the LoggingOn user-defined property to select whether logging is on or off for the web service message flow.
    2. Optional: Use the ErrorLoggingOn user-defined property to select whether error messages are generated.
    3. Optional: You can change any of the configurable properties in the broker archive, for example, properties for security or creating additional instances.

      You must ensure that any values that you change do not impact the behavior of the pattern instance.

  3. Create queues. WebSphere MQ queues must be created if they do not already exist for the error and log messages.
    1. Create WebSphere MQ resources. You can create WebSphere MQ resources either on the command line by using programs and utilities such as runmqsc, or by using the WebSphere MQ Explorer graphical interface. For more information about creating WebSphere MQ resources, see WebSphere MQ Intercommunication, available on the WebSphere MQ library web page.
  4. Deploy the BAR file to an execution group.

Back to the Service Facade to Microsoft .NET: request-response pattern specification