Support Sign in

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.

  1. Log in to System Web Console.
  2. Navigate to Key Management > Key Store Configuration.
  3. Click the New Configuration button.
  4. At the Name prompt, enter a name for the new key configuration.
    • Ex: JHProxyService_SYMxxx (where xxx is the SYM number)
  5. At the Description prompt, enter a description for the new key configuration.
  6. At the Host SYM prompt, select the SYM under which SymXchange runs.
  7. Click Save.
    • The new key configuration now appears in the key store configuration list.
  8. From the list, select the new key configuration.
  9. Click the Key Stores tab.
  10. Click the Open Key Store icon next to the key store.
  11. Click Create Key.
  12. At the Alias prompt, enter an alias.
    • Ex: jhproxyservice_symxxx (where xxx is the SYM number)
  13. At the Days of Validity prompt, type 3650.
  14. At the Key Size prompt, select 2048 bits.
  15. At the Common Name (CN) prompt, enter a name.
    • Ex: symx.<CU_Name>.local
  16. Remaining fields are not required but can be filled in if desired.
  17. Click Create.
    • The new key alias now appears in the key store.

Export the Public Key from the JHProxyService Key Configuration

  1. Log in to the System Web Console.
  2. 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.
  3. In the Configuration Name column, select the key configuration created for JHProxyService.
  4. Select the Key Stores tab, and then click the Open Key Store icon.
    • The Key Management pane appears.
  5. Click the Export icon.
    • The Export Key dialog box appears.
  6. Leave the Private Key Password prompt blank.
  7. At the File Name prompt, type a relevant name.
  8. At the File Format prompt, click the drop-down arrow, and then select PEM.
  9. Click the Export button to save the .pem file to your local drive.
  10. 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.
  1. Log in to System Web Console.
  2. Navigate to Key Management > Key Store Configuration.
  3. From the list, click the Banno key configuration created previously.
  4. Click the Key Stores tab.
  5. Click the Open Key Store (folder) icon to the right of the key store.
  6. Click Import.
  7. Choose the .p12 certificate to import
  8. The Alias must be ecaas_id_provider. ID cannot be changed to the sym number.
  9. Enter the password for the certificate(if you forget the password the certificate will not import)
  10. Click Import
  11. Click the button in the Trust column for the ecaas_id_provider entry.
    • The following message appears: Trust key result: Successfully copied certificate.
  12. 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

  1. Log in to System Web Console.
  2. Navigate to Key Management > Key Store Configuration.
  3. From the list, click the JHProxyService key configuration created previously.
  4. Click the Key Stores tab.
  5. Click the Open Trust Store (folder) icon to the right of the key store.
  6. Click Import.
  7. Click Choose, and then navigate to the file containing the Banno-provided certificate.
  8. Click Upload.
    • A dialog box appears with the public key in .pem format.
  9. At the Alias prompt, enter service_banno.
    • The alias must be service_banno.
    • The alias should be all lowercase without spaces.
  10. Click Import.
    • The public certificate now appears as part of the trust store.

SymXchange Web Services Configurations

Enable services for SymXchange Instance Services Configuration:

ServiceVersion
AccountService
  • 2020.01
  • Persistent
    • EcaaService
  • 2020.01
  • Persistent
    • EpisysInformationService
  • 2020.01
    • FindByService
  • 2020.01
  • Persistent
    • GeneralLedgerService
  • 2020.01
  • Persistent
    • InformationService
  • Persistent
    • TransactionsService
  • 2020.01
  • Persistent

    • SymXchange Instance Device Mapping Configuration 
    Device TypeJHWIRESISO
    Device Number20 + CU 3-digit #
    Client NumberUse first available for Instance, usually 0

    SymXchange Instance Web Server Configuration
    HTTP(s) Port NumberAny available
    Protocol+++https
    Key Configuration Name+++Select from dropdown
    Key Alias+++Select from dropdown
    Add White List IPv4 Addresses
  • 10.90.72.0-255
  • 10.90.86.0-255
  • 10.90.100.0-255

    • +++ Requires Certificate Configuration to be completed first in order to make selection.


    SymXchange Instance Details Configuration 
    Number of SymXchange Web Service Posters15

    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 NameSetting
    Client System User NumberSet accordingly
    Client System NameSymXchange – JHWires ISO
    Report TitleSymXchange – JHWires ISO
    Administrative PasswordCU Preference
    Transaction Source CodeSet accordingly
    FM in Posting JournalYes
    Review ALL Past Due Days ParametersSet accordingly
    Review ALL GL ParametersSet accordingly
    Services for Transfer In, Out, Withdrawal and DepositSet accordingly
    Maximum Response Fields10,000
    Maximum Specfile Lines10,000
    Maximum All Field Count10,000
    ODT/ODP settingsSet accordingly

    Service Operations

    Enable the specified credential(s) for the SymXchange per Operation Credentials Parameters for each method(s):

    ServiceRecordOperationCredential(s)
    AccountAccountgetAccount
  • Home Banking
  • Admin Password
    • AccountAccountgetAccountSelectFields
  • Home Banking
  • Admin Password
    • AccountAccountgetAccountSelectFieldsFilterChildren
  • Home Banking
  • Admin Password
    • AccountSharegetShare
  • Home Banking
  • Admin Password
    • AccountSharegetShareListSelectFields
  • Home Banking
  • Admin Password
    • AccountSharegetShareSelectFieldsFilterChildren
  • Home Banking
  • Admin Password
    • AccountShareTransactionsearchShareTransactionSelectFields
  • Home Banking
  • Admin Password
    • AccountShareAnalysissearchShareAnalysisPagedSelectFields
  • Home Banking
  • Admin Password
    • AccountShareAnalysisupdateShareAnalysisByID
  • Home Banking
  • Admin Password
    • AccountShareHoldcreateShareHold
  • Home Banking
  • Admin Password
    • AccountShareHoldupdateShareHoldByID
  • Home Banking
  • Admin Password
    • EpisysInformationgetGeneralEpisysInformation
  • Admin Password
    • FindByfindByHomeUser
  • Admin Password
    • FindByfindByShortName
  • Admin Password
    • GeneralLedgerGlAccountgetGlAccountSelectFields
  • Admin Password
    • InformationgetGeneralInformation
  • Admin Password
    • TransactionsDeposit
  • Home Banking
  • Admin Password
    • TransactionsGLToGLPost
  • Home Banking
  • Admin Password
    • Transactionswithdraw
  • Home Banking
  • Admin Password
    • TransactionswithdrawFee
  • Home Banking
  • Admin Password

    • JH ISO Change Log

    DateChangesUpdated by
    02/19/2026
    • Edited the ECAAS certificate portion to import certs instead of creating certs
    • Brian Frost
    02/11/2025
    • Removed unused services
    01/22/2025
    • Modified services
    • Added GeneralLedger record
    01/15/2025
    • Created

    Related