In this tutorial we’ll present BP-Switch features that help to set up a simple message flow in BP-Node for ISO8583 rev.93 message type.
In this scenario, following BP-Node components will be used:
and Pipeline components:
The first thing we’ll need is to create the listening connection which will serve as the entry point for receiving payments data. In our scenario a component called NbyteHeaderTCP class will be used.
Open your BP-UI and navigate to Components. There click the green button which says “Add Component”. From the Class options available pick the bp::eftlab::node::ipc::NbyteHeaderTCP and name it: Downlink_ISO8583_1993_1.
When clicking the Add button new options will appear, related to the class selected. Fill in the following values:
Click the Save button.
Now we can add a connection. A connection is the actual entry point so we need to fill the IP and port on which the BP-Node will be listening.
Press the “Add Connection” button.
Fill in the form with following connection values:
Save the configuration changes by clicking the “Save” button.
We also need a target connection – a client which will connect to the acquirer, for this we’ll use the NbyteHeaderTCP component class again.
Open the components menu and add a new NbyteHeaderTCP component (bp::eftlab::node::ipc::NbyteHeaderTCP).
Select the bp::eftlab::node::ipc::NbyteHeaderTCP component class and name the new component as: Uplink_ISO8583_1993_1
Save the component.
Note that following Message Destination and Message Type fields have to match the From Remote Message Destination and From Remote Message Type we’ll be configuring in a moment in withing the Iso8583MessageExchange component.
Fill the following:
Click Save.
Click “Add Connection” button.
Set Connection values as followed:
Save the component.
Note the Component Id (e418808c-816a-4f3b-b9ef-31cb3a34697f) as it will be needed for further configuration.
Now we can create a Message Bus Component that will handle the message exchange with the Host (matches requests and responses & processes timeouts).
Open the components menu, add a new Iso8583MessageExchange component (bp::eftlab::node::ipc::Iso8583MessageExchange) and name it Exchange_ISO8583_1993_1.
Select the bp::eftlab::node::ipc::Iso8583MessageExchange component.
Save the component, additional fields will pop up.
Fill in the following:
Save the Component.
Save the component.
Your Components screen should now look very close to the picture below.
Now when we have all the critical components configured we need to bind those with a processing logic through the Pipelines. Pipeline configuration will then tell how to interact with each other and can implement a dynamic business logic.
Go to the main menu and select Pipelines > Add Pipeline.
Fill the Label field with the previously selected pipeline name ISO8583_1993_Pipeline and click the “Save” button to store it.
After having the Pipeline created there we’ll tick it Enabled and start filling it with the Pipeline Components. By repeated clicking “Add Component” fill in added forms for components CommandToIsoMessage and SendMesageOnline:
This component will convert data input to an Iso8583 object BP-Node can work with.
Click on Add Component and select the CommandToIsoMessage component (bp::eftlab::node::pipeline::basic_components::CommandToIsoMessage).
Fill any Label you wish, e.g. CommandToIsoMessage.
Save the pipeline, additional fields are revealed for this component.
Save the pipeline.
This component will send the constructed message object to the BP-Node message bus.
Click on Add Component and select the SendMesageOnline component (bp::eftlab::node::pipeline::basic_components::SendMessageOnline).
Fill the label field with some name, e.g. SendMesageOnline.
Save the pipeline, additional fields are revealed for this component.
Now we need to fill the Message Destination and Type, this information pair defines uniquely the data that will the Message Bus work with.
Fill the following data:
Save the pipeline.
Go to the Tracing menu
Open Listeners, fill the Destination field with ISO8583_1993_Out and click “+ Create”. New listener will be added.
Run a ISO8583 rev.93 message against BP-Node on socket 7001.
If properly configured the message goes through BP-Node and ends on your Host, the response will be returned to your source. The message was parsed by the BP-Node into its ISO20022 internal format and compiled back to ISO8583-1993 on a request and also on the response.
You can check it in the Tracing view.
The diagram below explains what has been achieved and provides a good overview on reasonably complex configuration above.
In this tutorial, we went through a part of the ISO8583-1993 pass-through functionality for EFTlab’s BP-Switch.