Get started

Follow the steps in Getting started before proceeding. Jack Henry Symitar access: An active account in the Jack Henry Symitar production or test environment. Network connectivity: Verify that your network routes traffic between the Jack Henry Symitar environment and Grand Central iPaaS. For supported options, see Network connectivity. Environment details: You need the following environment details from Jack Henry Symitar to configure the connector:

Parameter	Description
`symxchange.baseUrl`	The SymXChange API endpoint URL for your environment
`symxchange.deviceNumber`	Device number for SymXChange API requests
`symxchange.deviceType`	Device type identifier for SymXChange
`symxchange.version`	SymXChange API version

Configuration guide

Follow these steps to initialize and authorize your Jack Henry Symitar Connector.

1. Establish connectivity

Share connectivity details between Grand Central and Jack Henry Symitar as described in Network connectivity.

VPN connectivity to the Jack Henry Symitar environment must be established before proceeding with configuration.

2. Jack Henry Symitar authentication

The Jack Henry Symitar Connector uses SymXChange API authentication for API access. To configure authentication, create a Secrets Operations (SOPS) secret. For more information, see How to create SOPS.

To share credentials between Jack Henry Symitar and Grand Central, consider using 1Password.

3. Environment configuration

To initialize the Jack Henry Symitar Connector, define the required environment variables in your gc-applications-live repository. These variables are stored in values.yaml for common configuration across all connectors and in the following files for connector-specific configuration:

Connector	Property	Description
`gc-symitar-deposit-connector`	`deposit-v0.values.yaml`	Outbound deposit connector for deposit account operations
`gc-symitar-deposit-transactions-connector`	`deposit-transactions-v0.values.yaml`	Outbound deposit transactions connector for transaction operations
`gc-symitar-loan-connector`	`loan-v0.values.yaml`	Outbound loan connector for loan account operations
`gc-symitar-loan-transactions-connector`	`loan-transactions-v0.values.yaml`	Outbound loan transactions connector for transaction operations
`gc-symitar-payment-connector`	`payment-v0.values.yaml`	Outbound payment connector for payment operations
`gc-symitar-party-connector`	`party-v0.values.yaml`, `party-v2.values.yaml`	Outbound party connector for party management operations

Define common parameters

These variables are stored in values.yaml and are used across all Jack Henry Symitar connectors:

Parameter	Description	Example value
`existingSecretName`	Reference to SOPS secret containing Jack Henry Symitar credentials.	`symitar`
`symxchange.baseUrl`	Target API endpoint for the Jack Henry Symitar SymXChange environment.	`https://symxchange-api.yourbank.com/SymXchange/`
`symxchange.basePortUrl`	Base port URL for SymXChange API requests.	`https://symxchange-api.yourbank.com`
`symxchange.deviceNumber`	Device number for SymXChange API requests.	`12345`
`symxchange.deviceType`	Device type identifier for SymXChange.	`GRANDCENTRAL`
`symxchange.version`	SymXChange API version.	`2022.01`

The following example shows the values.yaml configuration:

# Common Jack Henry Symitar Configuration
# Place this in: values.yaml
connector:
  existingSecretName: symitar
  traits:
    knativeservice:
      minScale: 0
      enabled: true
    logging:
      level: INFO
    jvm:
      enabled: true
      options:
        - -XX:+UseContainerSupport
        - -XX:+UseParallelGC
        - -XX:MinRAMPercentage=50
        - -XX:MaxRAMPercentage=80
  properties:
    # SymXchange Connection Settings
    # symxchange.baseUrl: <SymXchange_API_Endpoint>
    # symxchange.basePortUrl: <SymXchange_Base_Port_URL>
    # symxchange.deviceNumber: <Device_Number>
    # symxchange.deviceType: <Device_Type>
    # symxchange.version: <API_Version>

Place the values files at the following paths:

iPaaS/azure/runtimes/{runtime}/values/gc-symitar/
├── values.yaml
├── deposit-v0.values.yaml
├── deposit-transactions-v0.values.yaml
├── loan-v0.values.yaml
├── loan-transactions-v0.values.yaml
├── payment-v0.values.yaml
├── party-v0.values.yaml
└── party-v2.values.yaml

Define party-v0 connector parameters

The party-v0.values.yaml file contains the basic configuration for the party v0 connector.

connector:
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define party-v2 connector parameters

The party-v2.values.yaml file contains advanced configuration including account type mappings, CXF client settings, thread pools, retry configuration, and error code mappings.

connector:
  properties:
    # Account Type Mappings
    # fieldsToBeReplaced: ShareCode@Type,LoanCode@Type
    # deposit.productTypes: <DepositProductType1>,<DepositProductType2>,...
    # loan.productTypes: <LoanProductType1>,<LoanProductType2>,...
    # typeConversion.skipAttributes: <Attribute1>,<Attribute2>,...
    
    # ShareCode mappings
    # ShareCode.<Code>@Type.<Type>: <GC_ProductId>@<GC_SecondaryProductId>
    
    # LoanCode mappings
    # LoanCode.<Code>@Type.<Type>: <GC_ProductId>@<GC_SecondaryProductId>
    
    # CXF Client Settings
    # cxf.client.connect.timeout: <Timeout_Ms>
    # cxf.client.receive.timeout: <Timeout_Ms>
    # cxf.client.proxy.activate: <true|false>
    
    # Thread Pool Configuration
    # thread.profile.core.pool.size: <Pool_Size>
    # thread.profile.max.pool.size: <Max_Pool_Size>
    
    # Retry Configuration
    # retryFlag: <true|false>
    # retryStatuses: <Status1>,<Status2>,...
    # redeliveryDelay: <Delay_Ms>
    # maximumRedeliveries: <Max_Retries>
    # backOffMultiplier: <Multiplier>
    
    # coreMessageVisibility: <true|false>
    # quarkus.cxf.path: <CXF_Path>
    
    # Error code mappings
    # <CoreErrorCode>: <GC_ErrorCode>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define deposit connector parameters

The deposit-v0.values.yaml file contains configuration for deposit account operations including ShareCode mappings and product ID mappings. Account type mapping patterns:

Pattern	Description
`ShareCode.{X}@Type.{Y}`	Maps Symitar ShareCode/Type to Grand Central product type
`product.productId.{KIND}@product.secondaryProductId.{TYPE}`	Maps product ID combinations

connector:
  properties:
    # Account Type Mappings
    # fieldsToBeReplaced: ShareCode@Type,product.productId@product.secondaryProductId
    # deposit.productTypes: <DepositProductType1>,<DepositProductType2>,...
    
    # ShareCode mappings
    # ShareCode.<Code>@Type.<Type>: <GC_ProductId>@<GC_SecondaryProductId>
    
    # Product ID mappings
    # product.productId.<Kind>@product.secondaryProductId.<Type>: <Code>@<Value>
    
    # typeConversion.skipAttributes: <Attribute1>,<Attribute2>,...
    
    # CXF Client Settings
    # cxf.client.connect.timeout: <Timeout_Ms>
    # cxf.client.receive.timeout: <Timeout_Ms>
    # cxf.client.proxy.activate: <true|false>
    
    # Thread Pool Configuration
    # thread.profile.core.pool.size: <Pool_Size>
    # thread.profile.max.pool.size: <Max_Pool_Size>
    
    # Retry Configuration
    # retryFlag: <true|false>
    # retryStatuses: <Status1>,<Status2>,...
    # redeliveryDelay: <Delay_Ms>
    # maximumRedeliveries: <Max_Retries>
    # backOffMultiplier: <Multiplier>
    
    # coreMessageVisibility: <true|false>
    # quarkus.cxf.path: <CXF_Path>
    
    # Error code mappings
    # <CoreErrorCode>: <GC_ErrorCode>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define deposit-transactions connector parameters

The deposit-transactions-v0.values.yaml file contains configuration for deposit transaction operations.

connector:
  properties:
    # CXF Client Settings
    # cxf.client.connect.timeout: <Timeout_Ms>
    # cxf.client.receive.timeout: <Timeout_Ms>
    # cxf.client.proxy.activate: <true|false>
    
    # Thread Pool Configuration
    # thread.profile.core.pool.size: <Pool_Size>
    # thread.profile.max.pool.size: <Max_Pool_Size>
    
    # Retry Configuration
    # retryFlag: <true|false>
    # retryStatuses: <Status1>,<Status2>,...
    # redeliveryDelay: <Delay_Ms>
    # maximumRedeliveries: <Max_Retries>
    # backOffMultiplier: <Multiplier>
    
    # coreMessageVisibility: <true|false>
    # quarkus.cxf.path: <CXF_Path>
    # quarkus.camel.servlet.url-patterns: <URL_Pattern>
    # quarkus.native.resources.includes: <Resource_Pattern>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define loan connector parameters

The loan-v0.values.yaml file contains configuration for loan account operations including LoanCode mappings and product arrangement mappings. Account type mapping patterns:

Pattern	Description
`LoanCode.{X}@Type.{Y}`	Maps Symitar LoanCode/Type to Grand Central product type
`productArrangement.productId.{KIND}@productArrangement.secondaryProductId.{TYPE}`	Maps product arrangement combinations

connector:
  properties:
    # Account Type Mappings
    # fieldsToBeReplaced: LoanCode@Type,productArrangement.productId@productArrangement.secondaryProductId
    # loan.productTypes: <LoanProductType1>,<LoanProductType2>,...
    # productArrangement.productId.creditCardProductId: <CreditCardProductId>
    
    # LoanCode mappings
    # LoanCode.<Code>@Type.<Type>: <GC_ProductId>@<GC_SecondaryProductId>
    
    # Product arrangement mappings
    # productArrangement.productId.<Kind>@productArrangement.secondaryProductId.<Type>: <Code>@<Value>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define loan-transactions connector parameters

The loan-transactions-v0.values.yaml file contains configuration for loan transaction operations.

connector:
  properties:
    # CXF Client Settings
    # cxf.client.connect.timeout: <Timeout_Ms>
    # cxf.client.receive.timeout: <Timeout_Ms>
    # cxf.client.proxy.activate: <true|false>
    
    # Thread Pool Configuration
    # thread.profile.core.pool.size: <Pool_Size>
    # thread.profile.max.pool.size: <Max_Pool_Size>
    
    # Retry Configuration
    # retryStatuses: <Status1>,<Status2>,...
    # redeliveryDelay: <Delay_Ms>
    # maximumRedeliveries: <Max_Retries>
    # backOffMultiplier: <Multiplier>
    
    # coreMessageVisibility: <true|false>
    # quarkus.cxf.path: <CXF_Path>
    
    # Error code mappings
    # <CoreErrorCode>: <GC_ErrorCode>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define payment connector parameters

The payment-v0.values.yaml file contains configuration for payment operations.

connector:
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Configure complete ShareCode and product ID mappings based on your institution’s account types. Contact your Jack Henry Symitar administrator for the full list.

Testing your integration

To access the Unified API, include your Grand Central subscription key in the request header. If you don’t have a key, contact the Grand Central Support Team to request one.

Header	Value
`api-key`	`<your_subscription_key>`

Test the API using the Postman Collection.

For more information about the Grand Central Unified API endpoints that support these features, see Jack Henry Symitar Connector Overview.

Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.

5XX: Internal server error / Core system is down

Cause: The Grand Central gateway cannot establish a handshake with the Jack Henry Symitar endpoint. This typically indicates an upstream service outage at Jack Henry Symitar or a network routing failure.Solution: Verify the operational status of the Jack Henry Symitar environment. Check the Jack Henry status page or contact Jack Henry support. If the service is operational, contact Grand Central Support.

5XX: Timeout from core / Read timeout / SocketTimeoutException

Cause: The request to Jack Henry Symitar exceeded the configured timeout period. This may indicate performance issues at Jack Henry Symitar or network latency problems.Solution: Verify the operational status of the Jack Henry Symitar environment and check for any performance degradation. If the service is operational and performing normally, contact Grand Central Support.

VPN connectivity issues

Cause: VPN connectivity to the Jack Henry Symitar environment has not been established or has been interrupted.Solution: Verify VPN connectivity and ensure routing is properly configured between Grand Central and Jack Henry Symitar.

401: Invalid authentication credentials

Cause: The authentication credentials provided during setup are incorrect, expired, or the user lacks the required permissions in Jack Henry Symitar.Solution: Re-verify your credentials with your Jack Henry Symitar administrator and ensure the user has the required permissions. Contact the Grand Central team to update the connection credentials if needed.

429: Rate limit exceeded

Cause: The number of incoming requests exceeds the defined threshold for your subscription tier. This “429 Too Many Requests” response protects the stability of the Grand Central and Jack Henry Symitar infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact the Grand Central team to request a higher rate limit.

Need more help?

Contact support

Contact the Grand Central team for help with environment setup or rate limit increases.

Overview

Grand Central connectors

Release notes

Configuration guide

1. Establish connectivity

2. Jack Henry Symitar authentication

3. Environment configuration

Define common parameters

Define party-v0 connector parameters

Define party-v2 connector parameters

Define deposit connector parameters

Define deposit-transactions connector parameters

Define loan connector parameters

Define loan-transactions connector parameters

Define payment connector parameters

Testing your integration

Troubleshooting

Need more help?

Contact support

Overview

Grand Central connectors

Release notes

​Configuration guide

​1. Establish connectivity

​2. Jack Henry Symitar authentication

​3. Environment configuration

​Define common parameters

​Define party-v0 connector parameters

​Define party-v2 connector parameters

​Define deposit connector parameters

​Define deposit-transactions connector parameters

​Define loan connector parameters

​Define loan-transactions connector parameters

​Define payment connector parameters

​Testing your integration

​Troubleshooting

​Need more help?

Contact support

Configuration guide

1. Establish connectivity

2. Jack Henry Symitar authentication

3. Environment configuration

Define common parameters

Define party-v0 connector parameters

Define party-v2 connector parameters

Define deposit connector parameters

Define deposit-transactions connector parameters

Define loan connector parameters

Define loan-transactions connector parameters

Define payment connector parameters

Testing your integration

Troubleshooting

Need more help?