J2ee-jca-call

Description

This feature allows you to define an invocation to a JCA adapter that exposes the CCI interface.

VulCon / GV Console Configuration

There are no limitations on the structure of records that the JCA adapter can use. The body of GVBuffer must contain an XML structure that describes the JCA record, and in response the output record is converted in the same XML format.

The j2ee-jca-call Element is used by Channel and routed-call.

Its attributes are:

• type: call.
• class: it.greenvulcano.gvesb.virtual.j2ee.JCACallOperation.
• name: Operation name. Used in the 'Flow' section to associate workflow nodes to VCL operations.
• jndi-name-eis: JNDI name under which the resource adapter is installed. Is the JNDI name of connection factory.
• exec-type: Invocation description:
  • exec_in_out: GreenVulcano^® ESB uses the Interaction.execute() with the input and output records. If the method returns false, GreenVulcano^® ESB throws an exception.
  • out_exec_in: GreenVulcano^® ESB uses the method Interaction.execute() with the only input record, receiving the output record as a result of invocation.
  • exec_in: GreenVulcano^® ESB uses the method Interaction.execute() with the only input record, without expecting results. GreenVulcano^® ESB returns the input record.
    Refer to the documentation of particular JCA adapter to see which are the accepted methods.
• output-name: If you specify exec_in_out to attribute exec-type, you must specify the name of the output record.
  Refer to the documentation of particular JCA adapter to see which is the name to be used.
• output-type: If you specify 'exec_in_out' to attribute 'exec-type', specify the type of output record.
  Refer to the documentation of particular JCA adapter to see what kind of records is returned by invoked function.
  The attribute's admitted values are:
  • mapped
  • indexed
• byteArray-handling: Defines how to deal with returns of type byte[].
  • base64: The byte arrays are encoded in base64 strings.
  • string: The byte arrays are interpreted as strings. In the case of string you can define the encoding to be used with the attribute byteArray-encoding.
    If you do not specify the encoding will be used the platform default.
  • xml: The byte arrays are interpreted as serialized XML.
• byteArray-encoding: Defines the encoding to be used in case byteArray-handling is set to 'string'.
• namespace-prefix: The XML used to describe JCA records provides a particular namespace (http://www.eaisoftware.it/jca/xml). The default prefix used for namespace is jca.
  Warning: Changing this value will force a change of xpath

used in sub-elements xml-data and param-gvdata.

j2ee-jca-call has the following subelements:

• Description,
• JNDIHelper,
• jca-interaction-spec (see bellow),
• jca-connection-spec,
• xml-data,
• param-gvbuffer,
• ServiceAlias

jca-interaction-spec

The element jca-interaction-spec is used only by j2ee-jca-call and specifies the properties for the object javax.resource.cci.InteractionSpec. The InteractionSpec object must be a JavaBeans and its properties are used to provide the necessary parameters for JCA connector to complete the interaction with the EIS.

Refer to the documentation of particular JCA adapter for a list of properties supported by InteractionSpec. It has the attributes:

• class: Class that implements the InteractionSpec. Consult the documentation of particular JCA adapter for the value of this parameter.
• function-name: Many EIS provides different functions. This property allows you to specify the function to invoke.
  JCA specifications require implementation of this standard property only if applicable to the particular EIS. Refer to the documentation of the particular EIS for a list of available functions.
• interaction-verb: The functions exposed by an EIS can be invoked in a standard way:
  • SYNC_SEND_RECEIVE: Send data to the EIS, with synchronous waiting for a reply.
  • SYNC_SEND: Send data to the EIS, without reply.
  • SYNC_RECEIVE: Request of data to the EIS.
    JCA specifications require implementation of this standard property only if applicable to the particular EIS.
    Refer to the documentation of the particular EIS to check the verb for the various supported functions.
• execution-timeout: Timeout in milliseconds for a given interaction. Not all EIS support this parameter. JCA specifications require implementation of this standard property only if applicable to the particular EIS.

It has the following subelements:

• Description,
• spec-constructor,
• spec-property