jXchange Connector User Manual
Introduction
Service Gateway is a set of .NET web services that reside on Windows servers that enable the exchange of information between the various software products. These web services provide the entry point for real-time integration to JH’s core banking systems. Aspire Systems Inc developed a personalized MuleSoft connector that facilitates seamless integration with the jXchange gateway service, responsible for hosting JH core banking services.
Aspire Systems is a global technology services firm serving as a trusted technology partner for our customers. The changing landscapes of enterprises bring in dynamic integration requirements and need an ecosystem where different systems seamlessly talk to each other and remain connected. Aspire helps enterprises cruise through their data integration journeys without facing any hiccups along the way. Our Cloud Integration Services & Solutions connect your systems and applications for seamless data sharing and better connectivity in dynamic business environments.
MuleSoft Connector for jXchange - Overview
Upon commencing the development of a MuleSoft application aimed at integrating with the Service Gateway through the connector, financial institutions or third-party entities will initially acquire the zip file encompassing the TPG contracts. These contracts are accessible via the jackhenry.dev portal. This procedure of obtaining the contracts is a customary practice for any entity seeking to establish integration with the Service Gateway independently of the MuleSoft environment. The application should incorporate the connector, which will be accessible through the MuleSoft Public Exchange.
Setting up the connector will involve specifying the location of the XSD zip file and providing additional details outlined in the section below, which outlines the connector’s prerequisites. The connector will automatically extract the contracts and internally store them within the application. Upon integrating the connector into the application, users will be able to choose the contract container from a dropdown menu. After selecting a container, an additional dropdown will appear, allowing users to pick the desired operation.
The request mapping will take place external to the connector and will be included as the payload. Depending on the configuration, the connector will encapsulate the request in the suitable SOAP envelope before transmitting it to the designated Service Gateway endpoint. The response, as received from the Service Gateway, will be sent back to the application. Any adjustments required to the response payload will occur external to the connector.
Prerequisites
This document assumes you are familiar with Mule, Anypoint Connectors, and Anypoint Studio.
This document describes implementation examples within the context of Anypoint Studio, Mule ESB’s graphical user interface, and, in parallel, includes configuration details for doing the same in the XML Editor.
Dependencies
- Access to jXchange Service Gateway
- Mule Enterprise runtime or Anypoint Studio
Compatibility Matrix
| Application/Service | Version |
|---|---|
| Mule Runtime | 4.3.0 or higher |
| Anypoint Studio | 7.14 or higher |
| jXchange Gateway Service | 2022.0 or higher |
Installing and Configuring
Installation instructions
To install the connector, open the pom.xml file in the project root folder, and add the following dependency:
JH Core Extension
<dependency>
<groupId> com.mulesoft.connectors</groupId>
<artifactId>mule-jx-connector</artifactId>
<version>1.0.0</version>
<classifier>mule-plugin</classifier>
</dependency>
After that you should be able to find JH Core Extension connector in the Mule Palette window.
Configuring the Connector
As described in the usage overview, developers engaged in constructing a Mule application to link with JHA core banking systems have the option to utilize the jXchange Mule connector accessible through the MuleSoft exchange. This segment outlines the prerequisites for employing this jXconnector. Follow these steps to configure jXchange connector in a Mule application.
Setting up the connector entails specifying the location of the XSD zip file, along with additional details outlined in the section below that elaborate on the connector prerequisites.
| Parameter | Description | Mandatory | Default Value |
|---|---|---|---|
| Location | This field can accommodate both Mule expressions and free-form text. It is designed to receive either the absolute or relative path indicating the location of the WSDL file. | Required | AS400_Config |
| Service Gateway URL | This field accepts both Mule expression and free text. This field will accept the service gateway endpoint. | Required | — |
| Username | Enter the username for authenticating to gateway service | Required | — |
| Password | Enter the password for authenticating to gateway service | Required | — |
| Notes Tab | This is an empty text box that allows the storage of any information the developer deems relevant. | Optional | — |
| Help Tab | This will display links and/or resources where additional help can be found. | — | |
| Test Connection | Upon clicking this button, a test connection action will be triggered using the provided credentials. | ADD_FIRST | |
| Contracts | This drop-down menu populates with the names of all WSDL files located in the specified file location as configured in the connector. | Required | False |
| Operation | This dropdown menu displays a list of all operations present in the consumer-selected WSDL file. | Required | as400-license.lic |
| Payload | This field accommodates both Mule expressions and unrestricted text input. It is designated to receive the SOAP body payload from the workflow related to the specific operation. | Required | False |
| TLS Configuration | Reference to a TLS config element. This will enable secure connection for this config. | Required | — |
- Click OK to save the global connector configurations.
- Return to the Message Flow tab in Studio.
TLS Configuration
| Parameter | Description | Mandatory | Default Value |
|---|---|---|---|
| TrustStore | Trust store is used to store certificates from Certified Authorities (CA) that verify the certificate presented by the server in SSL connection. | Required |
Trust Store
| Parameter | Description | Mandatory | Default Value |
|---|---|---|---|
| Type | Mule supports many types of trust stores. | Optional | |
| Path | The location (which will be resolved relative to the current classpath and file system, if possible) of the trust store. | Required | — |
| Password | The password used to protect the trust store. | Required | — |
Contact Us
Contact us for support questions.