September 10th, 2024 - Intermittent Connection Issues

Throughout the dates of September 10-13th, 2024, a consumer may momentarily experience one of the following errors: “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.” or “Function not available during nightly updates.”

This is due to the processing of the core to bring it up to current date on end of day processing. Please wait for a minute or two and try your attempt again.

Reported Issues

We are aware of the following issues with the refresh and are working to correct.

September 2nd, 2024 - Refresh Complete

The data refresh for the DMZ SilverLake bank has been completed.

August 15th, 2024 - Development Environment Changes

We’re pleased to announce an upcoming SilverLake DMZ development sandbox bank enhancement! On September 2, 2024, we will refresh the dataset with entirely new and improved information - something that hasn’t been done in several years.

This refresh is a significant step in providing high quality data for your development and testing needs. It also lays the groundwork for more frequent data updates in the future.

If you have questions or concerns, please feel free to open a For Clients Portal (bank)/Vendor Portal (third parties) case and ask for it to be routed to Developer Relations or post a question on our StackOverflow channel.

When?

September 2, 2024

What is changing?

Service provider data: DMZ SilverLake bank (InstRtId: 011001276 and InstEnv: TEST)

Will my current test data continue to work?

No. You will need to replace it with information from the refreshed dataset. You can start with the provided sample accounts below or search for new data using the search and inquiry APIs.

The data within the SilverLake bank will be entirely brand new, meaning the following will be changing:

• Any value returned by a ParmValSrch or SvcDictSrch APIs (Example values: ProdCode, TranCodeCode, OffCode, CollatCode, BrCode, PmtCod).
• Customers that were created will no longer be in place. Creating a new customer will potentially assign a new unique CustId.
• Loan/Demand Deposits/Savings/Club/Time Deposits/Safe Deposit Box/Tracking accounts and all related information that was created will no longer be in place. There could be accounts with the same account numbers but the information they contain will be different.

What is NOT changing with this data refresh

The following items will not be changing:

• The URL used for accessing the DMZ, domain jxdmz.jackhenry.com. This also includes the URL for JX-RL (REST)
• Any value in the SOAP security header and the or the jXchangeHdr complex.
• For example:
  • InstRtId
  • InstEnv
  • ValidConsmName
  • ValidConsmProd

Sample Accounts

Below is a small sample of accounts to help with getting started once the refresh occurs. Feel free to use the APIs to create new or search for other customer records and accounts. For a larger list of accounts and related data, please download our SilverLake Refresh Sample Accounts spreadsheet.

Deposit

Loan

Time Deposit

EFT Cards