To make your adapter available on the Integration Store, you must join the Oracle Partner Network, submit your adapter proposal to Oracle, develop and test your adapter, and obtain the final approval from Oracle.

Before you begin the adapter development process, you must perform the following tasks.

1. Register as a Partner on the Oracle Partner Network. Choose the build track.
2. Submit a proposal to Oracle with the details of the adapter you intend to develop. You should include the following details in your proposal:
   • The application for which you plan to build the adapter.
   • The business use cases for the adapter.
   • The support model for the adapter.

     Specify if you are adhering to the Oracle Support service level agreements (SLAs). Ensure that you provide detailed information in the terms and conditions.

   • The test plan for the adapter.

     Indicate if you plan to test the adapter for each new release of Oracle Integration.

   • The documentation plan for the adapter.

     You must adhere to the adapter documentation standards and templates shared by Oracle.

   • The monetization plan for the adapter.
3. After the proposal is approved by Oracle, you can begin the development process.

This section lists the guidelines to build an adapter for the Integration Store.

1. Build your adapter from an OpenAPI document or a Postman collection of an application’s APIs. See Build and Test an Adapter.
2. Adhere to the adapter-development best practices. See Best Practices for Building an Adapter.
3. Design and execute automation tests for your adapter.

After you finish building and testing your adapter, follow the steps provided here to publish the adapter.

1. Send the adapter artifacts to Oracle for approval.
   You must send the .rab file to Oracle, adhering to the following guidelines:
   1. In the adapter definition document, enter the value for the id field (in the info section) as follows:
      • <OPNID>:<adapterId>

        Where OPNID is your Oracle Partner Network ID; this should not contain the hyphen (-) character.

   2. Use only the RAB: Create RAB Bundle command in VS Code to create the .rab file. See Create or Import Adapter Bundles.
   3. Ensure that the folder structure of your adapter bundle is according to the following illustration:

      <OPNID>_<adapterId>-<xx.xx.xx>
      |-->logo.svg
      |-->definitions
         |-->main.add.json
      |-->api

   4. Name the adapter bundle as: <OPNID>_<adapterId>-<xx.xx.xx>.rab.
      Where OPNID is your Oracle Partner Network ID; this should not contain the hyphen (-) character. Example name: 4712203150920_auraplayer-1.0.23.rab.
   5. Along with the adapter bundle, share the terms and conditions document, containing the following details:
      • The support model and the plan to address customer issues.
      • The amount of time you plan to provide support.

        For example: 24*7, or limited hours in a day, or limited days in a week, and so on.

      • The partnership plan with Oracle.

        For example, provide an estimate of how long you plan to continue partnering with Oracle and supporting the adapter.

      • The termination plan for the adapter.

        For example, if you terminate the partnership with Oracle, provide a plan to mitigate the issues for customers.

2. In addition to submitting the artifacts for a review, stage your adapter on the Integration Store, test it, and inform Oracle if the adapter can be made generally available (GA). Perform the following checks while staging your adapter:
   1. Verify if your instance has the following feature flag enabled: oic.common.enable.staging-accelerators. If not, please log an SR with the following information to enable it.
      • FF: oic.common.enable.staging-accelerators
      • region : <your instance's region>
      • URL: <your Oracle Integration URL>
      • OCID: <your Oracle Integration OCID>
   2. For the staged adapter to show up on your instance immediately, perform the invalidate cache operation on your instance. Otherwise, it may take around eight hours for the adapter to appear. An example URL to perform the invalidate cache operation is as follows:
      https://<OICDomainName>/ic/api/integration/v1/accelerators?integrationInstance=<InstanceName>&invalidateCache=true
   3. Ensure that you don't reuse an existing adapter ID. To set your adapter ID, see Step 1a above.
3. After the adapter artifacts are reviewed, Oracle makes your adapter GA on the Integration Store. Here are a few tasks related to the GA release:
   1. Export all the integrations (IAR or CAR files) that you created with the staged adapter, uninstall the adapter from your instance, and confirm the same to Oracle.
      This ensures that you don't lose any of the integrations you've built.
   2. Now, Oracle makes your adapter generally available and notifies you.
   3. To immediately view the adapter, perform the invalidate cache operation. Otherwise, the adapter appears on your instance after an auto refresh, which happens after eight hours.
   4. You can now import back the earlier integrations into your instance.

This section lists the support and maintenance guidelines for an adapter published to the Integration Store.

1. You must adhere to the support model you have mentioned in the terms and conditions document.
2. If the adapter is restricted to a customer or set of customers, you must create a separate contract with that particular customer or set of customers. Oracle will not be involved in such contracts.
3. For each new Oracle Integration release, patch the release to your development environment and run automation tests for all the use cases of your adapter.
4. Follow the best practices while fixing bugs or making enhancements to your adapter.
5. In case you identify an issue in Oracle Integration, create an SR with detailed logs and information.