ISO 8583

Overview

This bundle of custom actions allows you to generate banking messages in accordance with ISO 8583. They are required to fully load test a banking system.
This bundle of actions:

  • Connect to a ISO 8583 interface
  • Send a message
  • Disconnect from ISO 8583 interface

To be able to send messages that will be accepted by the remote banking interface, these actions need to be properly configured.
Each banking controller could have their ISO 8583 format:

  • Specific size of fields
  • Number of bytes before each field
  • Header length
  • Encryption format to exchange with the bank

It will be necessary to configure each Basic .xml file related to each banking controller.

Once configured, you will be able to use this action with dataset defined in NeoLoad:

  • File variables containing banking accounts
  • Date variables

This action will require to:

  • Create an xml file for each banking controller. The xml file would have to be named: Basic_<controller code>.xml
  • Store the xml files in <neoload project>/custom-ressources
  • Store the genericpackager.dtd in the same folder

 

Type Advanced Action
Version 1.0.0
Maturity Experimental
Author Neotys Professional Services
License BSD Simplified
NeoLoad 5.1
NeoSense Compatible
Requirements JPOS library

The JPOS library needs to be stored in <NeoLoad installation folder>/extlib

Jpos license

Bundled in NeoLoad No
Download

jar:

Sources:

Resources required (templates):

Parameters

ISO 8583 connect:

  • Host: Hostname or IP address of the banking interface
  • Port: port of the banking interface
  • Controllercode: Code of the banking controller that allows to find the XML descriptor file that defines the format of ISO 8583 messages (Basic_<controller code>.xml).
  • TypeofChannel: Encryption format of the communication: ASCII, NCC, NACC, BASE24, HEX, RPB, VAP, CS, AMEX
  • AddMessageLengthIntoHeader: Boolean that will specify to the Advanced action if the message length has to be added or not as the first information of the headers.
    Possible value: true or false
  • IncludeHeaderinBitmap: Boolean that will specify to the Advanced action if headers have to be added in the bitmap of the message.
    Possible value: true or false

ISO 8583 send:

  • Host: Hostname or IP address of the banking interface
  • Port: port of the banking interface
  • Controllercode: Code of the banking controller that allows to find the XML descriptor file that defines the format of ISO 8583 messages (Basic_<controller code>.xml).
  • MTI: Message Identifier
  • Header: Header of the ISO 8583 message
  • Field2: Field #2 of the message
  • Field3: Field #3 of the message
  • …FieldX: where X is between 2 and 128
  • Timeout: duration in seconds to send a message and receive an answer from the banking interface

Each banking message could have different fields. So the user is free to add as many fields as wanted as described in the xml configuration file of the banking controller

ISO 8583 disconnect:

  • Host: Hostname or IP address of the banking interface
  • Port: port of the banking interface
  • Controllercode: Code of the banking controller that allows to find the XML descriptor file that defines the format of ISO 8583 messages (Basic_<controller code>.xml).

Status Codes

  • NL-ISO8583Connect_ACTION: Issue while trying to connect to the banking interface.
  • NL-ISO8583Send_ACTION: Error while sending the message to the banking interface.
  • NL-ISO8583disConnect_ACTION: Error while trying to disconnect from the banking interface.

Changelog

  • 1.0.0 – Initial release
Entdecken
Folge uns