Example: Typical Processor Call Sequence

The proxy:

The proxy creates the input, the output, and the exit type classes.
The proxy populates the exit type classes and initializes them.
The proxy creates the processor that will be called and initializes it.
If the logger needs to be used by the processor, the proxy provides this during the init method call.
The proxy invokes the processor by calling the execute method with the input, output, connection, and exit type.
The processor obtains parameters from the InputBean to compose a message or command to be sent to a device.
The processor calls the send request to send that message to the device.
The processor sets the exit type based on the response.
The processor sets output parameters based on the response.

The processor may parse the response to obtain additional values for populating the output parameters.
The proxy cleans up the processor.
The proxy looks at the exit type that was set and populates it for return to the NEP, and cleans up the exit type.
The proxy extracts all output parameters for return to the NEP and to populate the work order.

The proxy then cleans up this class and (16) the remaining classes.

Note:

The developer is only responsible for the items related to the processor (steps 6 through 9); the proxy handles all other items.