Creating a Business Operation to Use the Adapter

To create a business operation to use the EnsLib.EMail.OutBoundAdapter, you create a new business operation class. Later, add it to your production and configure it.

You must also create appropriate message classes, if none yet exist. See Defining Messages.

The following list describes the basic requirements of the business operation class:

Your business operation class should extend Ens.BusinessOperationOpens in a new tab.
In your class, the ADAPTER parameter should equal EnsLib.EMail.OutboundAdapterOpens in a new tab.
In your class, the INVOCATION parameter should specify the invocation style you want to use, which must be one of the following.
- Queue means the message is created within one background job and placed on a queue, at which time the original job is released. Later, when the message is processed, a different background job will be allocated for the task. This is the most common setting.
- InProc means the message will be formulated, sent, and delivered in the same job in which it was created. The job will not be released to the sender’s pool until the message is delivered to the target. This is only suitable for special cases.
Your class should define a message map that includes at least one entry. A message map is an XData block entry that has the following structure:
```
XData MessageMap
{
<MapItems>
  <MapItem MessageType="messageclass">
    <Method>methodname</Method>
  </MapItem>
  ...
</MapItems>
}
```
Your class should define all the methods named in the message map. These methods are known as message handlers. Each message handler should have the following signature:
```
Method Sample(pReq As RequestClass, Output pResp As ResponseClass) As %Status
```
Here Sample is the name of the method, RequestClass is the name of a request message class, and ResponseClass is the name of a response message class. In general, these methods will refer to properties and methods of the Adapter property of your business operation.
For other options and general information, see Defining a Business Operation Class.

The following example shows the general structure that you need:

Class EEMA.NewOperation1 Extends Ens.BusinessOperation 
{
Parameter ADAPTER = "EnsLib.EMail.OutboundAdapter";

Parameter INVOCATION = "Queue";

Method SampleCall(pRequest As Ens.Request,
                  Output pResponse As Ens.Response) As %Status
{
  Quit $$$ERROR($$$NotImplemented)
}

XData MessageMap
{
<MapItems>
  <MapItem MessageType="Ens.Request">
    <Method>SampleCall</Method>
  </MapItem>
</MapItems>
}
}

Creating Message Handler Methods

Overall Behavior