Skip to main content
The Jack Henry Symitar integration is delivered as several outbound (synchronous) runtime connectors that call the SymXChange API. Each connector is configured in its own values.yaml file. For setup steps, see Get started.

Configuration properties

Values to obtain from Jack Henry Symitar

Obtain the following values from Jack Henry Symitar and set them in values.yaml. These values are environment-specific, so they have no default.
The connectors authenticate to the SymXChange API with credentials stored in a SOPS secret referenced by existingSecretName. For details, see Get started.

Common properties

Set these properties in values.yaml. They apply across all Jack Henry Symitar connectors. The deposit, deposit transaction, loan, loan transaction, and party connectors also set the following thread pool properties. The payment connector doesn’t use them.

gc-symitar-party-connector

The party-v0.values.yaml file holds the basic party configuration. The party-v2.values.yaml file adds account type mappings and error-code mappings, in addition to the common properties.

gc-symitar-deposit-connector

Set these properties in deposit-v0.values.yaml, in addition to the common properties. The bundled configuration uses the single-field mapping style (shareCode, shareType, productId, secondaryProductId); the combined fieldsToBeReplaced style is also supported.

gc-symitar-loan-connector

Set these properties in loan-v0.values.yaml, in addition to the common properties.

gc-symitar-deposit-transaction-connector and gc-symitar-loan-transaction-connector

The deposit transaction and loan transaction connectors use the common properties. They have no additional connector-specific mapping properties.

gc-symitar-payment-connector

Set these properties in payment-v0.values.yaml. The payment connector uses the common properties except the thread pool properties, and defines the following connector-specific error-code overrides.
The ShareCode, LoanCode, and product ID mapping values are environment-specific. Contact your Jack Henry Symitar administrator for the full list of account types.

Supported operations

The Jack Henry Symitar connectors expose the Grand Central Unified API. For the operation-to-endpoint tables per domain (deposit, loan, payment, party), see Overview. For the full contract, see the unified API specifications.

Events

These connectors are synchronous and do not publish or consume events.

Error mapping

The connector maps Jack Henry Symitar error codes to Grand Central status codes. For the full list, see Error codes. You can configure connector-specific overrides as core-to-Grand Central code pairs in the connector’s values.yaml; the payment connector ships with overrides for several SymXChange error codes (see gc-symitar-payment-connector).

Dependencies

  • Jack Henry Symitar SymXChange API (outbound), reachable at symxchange.baseUrl.
  • The shared symitar-connector-sdk library.