Symitar - Partner connector
Partner connectors are built, maintained, and supported by the partner that publishes them. Boomi provides Level 1 support for this connector; Solutions Metrix provides Level 2 support and is responsible for the connector code, its documentation, and its releases. Contact Solutions Metrix for functional questions, defects, and license requests. The connector is a Solutions Metrix product: Jack Henry & Associates does not build, publish, or support it.
The Symitar — Partner connector brings member data from the Symitar® core processing platform, the core system credit unions run on, into the Boomi Enterprise Platform. It talks to the credit union's SymXchange™ web services over SOAP. A Boomi process can use it to read a member account together with its shares, loans, names, and cards, to read the transaction history of a share or a loan, and to pick up the files that PowerOn® programs on the core write, for example a list of accounts that changed since the last run.
The connector is meant for credit unions and their integration partners who move core data into other systems, such as a CRM, a data warehouse, or a member portal. It reads from the core and does not write member data back. The only change it makes on the core is deleting a set of letter files after a process has read it.
The request and response profiles ship with the connector as XML Schema, so the Boomi mapping editor shows the SymXchange document shape as soon as you browse an object type. For an account, you choose in the operation which parts of the record come back (account fields, shares, loans, names, cards, tracking records, comments, notes), and SymXchange returns only those.
Benefits
- Whole member account in one call. One Get returns the account and every related record you selected, nested under it, from a single SymXchange request. The process needs no separate call per share or loan.
- Only the fields you map. The field selection on the operation limits the response to what the process uses, which keeps documents small for accounts with many shares, loans, and names.
- Transaction history without paging logic. For share and loan transactions the connector calls the paged SymXchange search operations and follows the continuation token itself, returning the whole history as one document. The operation sets the page size and an upper limit on the number of transactions; when the limit cuts a history short, the response says so.
- Change discovery through PowerOn® letter files. A PowerOn program on the core can write the numbers of changed accounts to a letter file; Solutions Metrix provides one on request. The connector reads that file, or a numbered set of files as one document, and deletes the set once the process has handled it, so the next run starts from a fresh file.
- Failures you can act on. Test Connection sends one real request to SymXchange and, when it fails, names the connection field to check. At run time a SymXchange fault fails the document with the SymXchange message, and a delete that the core rejects fails the document instead of being reported as done.
- Runs close to the core. The connector is built for Java 8 and has no runtime dependency that the Boomi Cloud security policy blocks, so it runs on a local runtime, a runtime cluster, or a Boomi runtime cloud.
Connector configuration
To configure the connector to communicate with a Symitar core, set up two components:
- Symitar — Partner connection: holds the SymXchange Account Service URL, the SymXchange administrative password, the device type and device number assigned to this integration, and the Solutions Metrix customer ID and license key. The file management endpoint used for letter files is derived from the Account Service URL and has no field of its own. Reuse one connection for every operation against the same core and environment. You can test the connection from the Boomi user interface before you save it.
- Symitar — Partner operation: represents one action on one object type. A Get on accounts carries the field selection; a Get on share or loan transactions carries the page size, the transaction limit, and an optional search filter.
This design gives you reusable components: create one connection, reuse it across operations, and override the connection settings per environment with environment extensions.
Supported actions:
| Action | Object type | Description |
|---|---|---|
| Get | Account | Reads one member account by account number, with the related records selected in the operation. |
| Get | Share Transaction, Loan Transaction | Reads the transaction history of one share or loan of an account across all pages, optionally narrowed by a search filter. |
| Get | Letter File | Downloads one letter file from the core by file name and returns its content. |
| Get | Letter File Set | Downloads a numbered set of letter files (.001, .002, and so on) that share a base name and returns their content as one document. |
| Execute | Letter File Set | Deletes every file of a letter file set from the core. The base name comes from the incoming document, so the output of a Get on Letter File Set can be passed straight in. A single letter file cannot be deleted. |
Create, Update, Upsert, Delete, and Query actions are not supported. The connector does not write member data to the core, and reads are covered by Get. The Operation document describes each object type and its fields.
Prerequisites
To use the Symitar — Partner connector, you need the following:
- A Symitar core with the SymXchange Account Service enabled, and the URL of that service. Access to SymXchange is arranged between the credit union and Jack Henry.
- The SymXchange administrative password, and a device type and device number that the credit union's Symitar administrator has authorized for the operations the connector calls: getAccountSelectFields, and the paged transaction searches searchShareTransactionPagedSelectFields and searchLoanTransactionPagedSelectFields.
- For the Letter File and Letter File Set object types: the SymXchange file management service at the same base address as the Account Service, and a PowerOn program on the core that writes the letter files the process reads. Solutions Metrix provides a PowerOn program for account change discovery on request.
- A Customer ID and a License Key, both issued by Solutions Metrix. Get and Execute refuse to run without a valid license. Browsing object types and testing the connection do not require one, so a process can be built while the license is being issued.
- A Boomi Runtime (Cloud, Basic runtime, or Runtime cluster) that can reach the SymXchange endpoint. When the core is reachable only inside the credit union's network, run the connector on a basic runtime or runtime cluster in that network.
Tracked properties
This connector has no predefined tracked properties. Refer to the topic Adding tracked fields to a connector operation to learn how to add a custom tracked field.
Symitar® and PowerOn® are registered trademarks of Jack Henry & Associates, Inc.® SymXchange™ is a trademark of Jack Henry & Associates, Inc.®
