Implementation > Electronic Signature > Integration with Interchange > Inline processing for Interchange/Electronic Signature integration

Inline processing for Interchange/Electronic Signature integration

About inline processing

How to format PeSIT metadata for Electronic Signature

Copying the JAR file

Configuring Interchange for inline processing

Only read this topic if you are using Interchange as the communication layer for Electronic Signature.

This topic is related to the configuration of Interchange for Electronic Signature. It provides information about Inline processing for Interchange/Electronic Signature integration.

About inline processing

Payment files are sent to the Electronic Signature application, through Interchange, using the PeSIT protocol for example.

Inline processing ensures that Electronic Signature parses the most recent version of the payload. It also enables Electronic Signature to obtain the path of the payload in case of integration different from MMD (Message Metadata Document).

Inline processing performs the following functions:

The general workflow for payment files is explained in Overview of Axway Electronic Signature.

In this figure, inline processing takes place inside Interchange between steps 1 and 2.

How to format PeSIT metadata for Electronic Signature

The PeSIT PI 99 metadata must be formatted as follows:

key = value

Each part of the data is separated by the semi-colon character ( ; )

Example:

ebics.action=send; ebics.orderType=FUL.pain.xxx.cfonb160.dco; message.waitUpdate=true; ebics.domain=Geopost; ebics.sender=FI-AP; PayloadId=IDYZ1234;message.comment=Business Data

Where:

message.comment is optional metadata that might help treasurers to sign a payment.

Copying the JAR file

The inline processing jar file is <Electronic_Signature_install_dir>\devKit\inline\fex-es-inline.jar.

Copy the jar file into the Interchange jars folder: <Interchange_install_dir>\jars.

Configuring Interchange for inline processing

Configuring PeSIT inline

This section explains how to configure a community in Interchange to use inline processing with Electronic Signature for PeSIT.

  1. Click Message handler on the navigation graphic at the top of the community summary page.
  2. Click the task Add a new message processing action.
  3. Choose an attribute for the condition and click Next.
  4. Specify an operator and value that is always true. This ensures that the inline processing is always performed. Example: "From exists"
  5. Select Perform inline processing via a Java class.
  6. Complete the fields:
  7. Parameter Description
    Class name

    Enter the following name: com.axway.fex.es.inline.PesitIntegration
    Parameter

    Enter the name of the temporary directory where the payload file is to be copied.

    Example: c:\my_temporary_folder\

    The inline process creates a file name with syntax "file_coreID" for each payload. This ensures that files are unique and cannot be overwritten.
  8. Click Finish.

Now, continue with the configuration of Interchange.

Configuring Payment Status Report inline

This section explains how to configure a community in Interchange to use inline processing with Electronic Signature for updating the payment status.

  1. Click Message handler on the navigation graphic at the top of the community summary page.
  2. Click the task Add a new message attribute definition with criteria.
  3. Click Add attribute.
  4. Enter ebics.orderType in the text field and click Add.
  5. Click Cancel to go back to the Message handler processing page. The previous action added the required attribute to the list of available attributes.
  6. Click the task Add a new message processing action.
  7. Choose the attribute ebics.orderType for the condition and click Next.
  8. Leave the Operators as "Equals" and "Constant" and specify in the text field of the value, the payment status report order type. Example: "FDL.camt.002.001.02.ara" and click Next.
  9. Select Perform inline processing via a Java class
  10. Complete the fields:
  11. Parameter Description
    Class name

    Enter the following name: com.axway.fex.es.inline.PsrIntegration
    Parameter

    Enter the name of the Electronic Signature PSR Incoming directory where the fetched payment status report file is to be copied

    Example: c:\Axway\ElectronicSignature\psr\incoming
  12. Click Finish.

Modifying the default inline

The default inline implementations can be modified. The samples located in <Electronic Signature_install_dir>\devKit\inline are delivered for custom development:

  1. Ensure that you have maven installed and the command line mvn is on the system path environment variable.
  2. Enter: mvn clean install.
  3. The build creates a target directory where the compiled class and a new fex-es-inline-sample-{version}.jar file are generated.
  4. Copy the newly-generated jar file into the Interchange jars folder: <Interchange_install_dir>\jars.

Related topics

Configuring Interchange for Electronic Signature