InterSystems IRIS — Open Exchange

1. Decide what is public and what is licensed

1. Choose whether the Open Exchange entry is documentation-only, points to an approved public bootstrap repository, or also offers an optional IPM module.
2. Keep the optional IPM bootstrap limited to IRIS-side setup and metadata. State clearly that it does not install the commercial Spark JARs.
3. Prepare the authenticated Yanbor fulfillment link used after commercial authorization. The customer must receive the adapter and Spark JARs from that controlled channel.
4. Obtain legal approval for the listing title, descriptions, logo, screenshots, public repository contents, license URL, privacy/support URLs, and any claims about supported IRIS versions.

2. Prepare and validate the listing assets

1. Use a public GitHub or GitLab repository only if every committed file is approved for public release. Add a concise README, installation boundary, IRIS requirements, fictional sample, support link, public-license file for the bootstrap, and link to commercial fulfillment.
2. If publishing an IPM module, validate module.xml, use a semantic version, and confirm all referenced files are public. Do not declare proprietary JARs as public module files.
3. Load the module in an isolated IRIS namespace with zpm "load /path/to/module". Test a clean uninstall/reinstall and confirm that no customer configuration or credentials are embedded.
4. Where authorized, test publication in the IPM test registry using the current InterSystems procedure before requesting production registry publication.
5. Validate the separately fulfilled commercial bundle: compare SHA-256, run the Spark smoke test, run the isolated IRIS SQL setup, and require the documented live IRIS success marker using a customer-supplied compatible JDBC driver.

3. Create the Open Exchange application

1. Sign in to InterSystems Open Exchange with the Yanbor publishing identity.
2. Open Developer portal, select All applications, and choose New Application.
3. Enter the approved public GitHub/GitLab URL if one is used, then verify every field populated from the repository.
4. Complete the application name, logo, categories, InterSystems technologies, industries, call to action, About URL, public license URL, short description, full description, documentation, support, and demonstration fields.
5. State the integration accurately: DataAI runs in Spark, connects to IRIS through the adapter/JDBC path, and writes governed results; the public bootstrap is optional and does not contain the commercial libraries.
6. If the approved IPM module is eligible, select the current option to publish it through Package Manager and provide the exact module/repository details requested by Open Exchange.
7. Save the draft, preview it, check every public link from a signed-out browser, and verify that no production download bypasses commercial authorization.
8. Select Send for approval. Record the submission date, listing owner, repository commit, asset hashes, and reviewer communications.

4. Fulfill an approved customer

1. Complete the written Yanbor commercial agreement/order and verify the authorized customer identity and environments.
2. Grant time-bounded access to the licensed IRIS production ZIP and checksum manifest through the authenticated portal or private artifact repository.
3. Give the customer the production installation and usage guides, supported versions, JDBC-driver responsibility, license certificate/order reference, and support contact.
4. Confirm a clean customer download, matching checksum, private artifact installation, IRIS connection test, and successful governed output before closing fulfillment.

5. Maintain the listing

• Use a new semantic version and a new release record for changed public or commercial bytes.
• Update the listing when IRIS compatibility, URLs, screenshots, licensing, support, or package boundaries change.
• Do not call the package Open Exchange approved or IPM published until InterSystems actually approves it.

Official references

• InterSystems: submit an application to Open Exchange
• InterSystems: publish with IPM

Back to DataAI ETL Markets