SymXchange Implementation Blueprints for Jack Henry ISO Wires
This blueprint is used to configure SymXchange Jack Henry ISO Wires for credit unions. The minimum Symitar release currently supported is 2020.01.
SYSTEM Web Console
Certificate Configuration
Network traffic between Symitar and JH ISO Wires uses the SymXchange HTTPS protocol. This requires a certificate to be generated and exchanged between the client systems.
Create a Key configuration and certificate to be used for your JH ISO Wires SymXchange instance.
- Log in to System Web Console.
- Navigate to Key Management > Key Store Configuration.
- Click the New Configuration button.
- At the
Nameprompt, enter a name for the new key configuration.- Ex: JHProxyService_SYMxxx (where xxx is the SYM number)
- At the
Descriptionprompt, enter a description for the new key configuration. - At the
Host SYMprompt, select the SYM under which SymXchange runs. - Click Save.
- The new key configuration now appears in the key store configuration list.
- From the list, select the new key configuration.
- Click the Key Stores tab.
- Click the Open Key Store icon next to the key store.
- Click Create Key.
- At the
Aliasprompt, enter an alias.- Ex: jhproxyservice_symxxx (where xxx is the SYM number)
- At the
Days of Validityprompt, type 3650. - At the
Key Sizeprompt, select 2048 bits. - At the
Common Name (CN)prompt, enter a name.- Ex: symx.<CU_Name>.local
- Ex: symx.<CU_Name>.local
- Remaining fields are not required but can be filled in if desired.
- Click Create.
- The new key alias now appears in the key store.
Export the Public Key from the JHProxyService Key Configuration
- Log in to the System Web Console.
- In the System Web Console window, select Key Management from the menu list and click on Key Store Configuration.
- The Key Store Configuration List pane appears.
- In the Configuration Name column, select the key configuration created for JHProxyService.
- Select the Key Stores tab, and then click the Open Key Store icon.
- The Key Management pane appears.
- Click the Export icon.
- The Export Key dialog box appears.
- Leave the
Private Key Passwordprompt blank. - At the
File Nameprompt, type a relevant name. - At the
File Formatprompt, click the drop-down arrow, and then select PEM. - Click the Export button to save the .pem file to your local drive.
- Upload the certificate to the JH ISO Wires Implementation/Update jSource case.
- Important: You must upload the file to a secure internal access point. Send the file using a secured method. Do not use email.
Import a Certificate for ECAAS
- Banno will supply the .p12 certificate needed for the following steps in the For Clients case that we opened where setup was requested.
- Log in to System Web Console.
- Navigate to Key Management > Key Store Configuration.
- From the list, click the Banno key configuration created previously.
- Click the Key Stores tab.
- Click the Open Key Store (folder) icon to the right of the key store.
- Click Import.
- Choose the .p12 certificate to import
- The Alias must be ecaas_id_provider. ID cannot be changed to the sym number.
- Enter the password for the certificate(if you forget the password the certificate will not import)
- Click Import
- Click the button in the Trust column for the ecaas_id_provider entry.
- The following message appears:
Trust key result: Successfully copied certificate.
- The following message appears:
- Navigate back to Key Management Trust Store, you should now see the ecass_id_provider certificate listed.
Import Banno’s Public Certificate into Key Store
- Log in to System Web Console.
- Navigate to Key Management > Key Store Configuration.
- From the list, click the JHProxyService key configuration created previously.
- Click the Key Stores tab.
- Click the Open Trust Store (folder) icon to the right of the key store.
- Click Import.
- Click Choose, and then navigate to the file containing the Banno-provided certificate.
- Click Upload.
- A dialog box appears with the public key in .pem format.
- At the
Aliasprompt, enter service_banno.- The alias must be service_banno.
- The alias should be all lowercase without spaces.
- Click Import.
- The public certificate now appears as part of the trust store.
SymXchange Web Services Configurations
Enable services for SymXchange Instance Services Configuration:
| Service | Version |
|---|---|
| AccountService | |
| EcaaService | |
| EpisysInformationService | |
| FindByService | |
| GeneralLedgerService | |
| InformationService | |
| TransactionsService |
| SymXchange Instance Device Mapping Configuration | |
|---|---|
| Device Type | JHWIRESISO |
| Device Number | 20 + CU 3-digit # |
| Client Number | Use first available for Instance, usually 0 |
| SymXchange Instance Web Server Configuration | |
|---|---|
| HTTP(s) Port Number | Any available |
| Protocol+++ | https |
| Key Configuration Name+++ | Select from dropdown |
| Key Alias+++ | Select from dropdown |
| Add White List IPv4 Addresses |
+++ Requires Certificate Configuration to be completed first in order to make selection.
| SymXchange Instance Details Configuration | |
|---|---|
| Number of SymXchange Web Service Posters | 15 |
SymXchange Parameters
SymXchange Client Parameters
The following SymXchange Client Parameters are a small list of parameters that should be set, however, it is the CU’s responsibility to ensure remaining SymXchange parameters are reviewed to confirm that they’re set up according to their policies:
| Parameter Name | Setting |
|---|---|
| Client System User Number | Set accordingly |
| Client System Name | SymXchange – JHWires ISO |
| Report Title | SymXchange – JHWires ISO |
| Administrative Password | CU Preference |
| Transaction Source Code | Set accordingly |
| FM in Posting Journal | Yes |
| Review ALL Past Due Days Parameters | Set accordingly |
| Review ALL GL Parameters | Set accordingly |
| Services for Transfer In, Out, Withdrawal and Deposit | Set accordingly |
| Maximum Response Fields | 10,000 |
| Maximum Specfile Lines | 10,000 |
| Maximum All Field Count | 10,000 |
| ODT/ODP settings | Set accordingly |
Service Operations
Enable the specified credential(s) for the SymXchange per Operation Credentials Parameters for each method(s):
| Service | Record | Operation | Credential(s) |
|---|---|---|---|
| Account | Account | getAccount | |
| Account | Account | getAccountSelectFields | |
| Account | Account | getAccountSelectFieldsFilterChildren | |
| Account | Share | getShare | |
| Account | Share | getShareListSelectFields | |
| Account | Share | getShareSelectFieldsFilterChildren | |
| Account | ShareTransaction | searchShareTransactionSelectFields | |
| Account | ShareAnalysis | searchShareAnalysisPagedSelectFields | |
| Account | ShareAnalysis | updateShareAnalysisByID | |
| Account | ShareHold | createShareHold | |
| Account | ShareHold | updateShareHoldByID | |
| EpisysInformation | getGeneralEpisysInformation | ||
| FindBy | findByHomeUser | ||
| FindBy | findByShortName | ||
| FindBy | findByMICR | ||
| GeneralLedger | GlAccount | getGlAccountSelectFields | |
| Information | getGeneralInformation | ||
| Transactions | Deposit | ||
| Transactions | GLToGLPost | ||
| Transactions | withdraw | ||
| Transactions | withdrawFee |
JH ISO Change Log
| Date | Changes | Updated by |
|---|---|---|
| 02/19/2026 |
|
|
| 02/11/2025 |
|
|
| 01/22/2025 |
|
|
| 01/15/2025 |
|