Creating an Application Instance

For customers to be able to use a multi-tenant application, the provider must create an instance of the application. The application API end-point of an instance may be deployed in:

• the provider's infrastructure,
• the ISV's infrastructure, or
• the Ingram Micro Connect infrastructure.

Refer to the application's deployment guide for the corresponding application instructions.

To create an application instance, use the following instructions:

1. Go to Services > Applications.
2. In the APS Connectors tab, click a name of the required application.
3. In the Instances tab, click Add Instance.
4. Into the Application API end-point URI field, type the deployed application's end-point.

   Note: A value of an application API end-point URI looks like:
   https://<endpoint_domain_name>/<path-to-app-base-endpoint>/
   - If the application is deployed in the provider's infrastructure, the provider will have information about the application's endpoint after its deployment.
   - If the application is deployed in the ISV's infrastructure, the provider receives information about the application's endpoint from the ISV.
   - If the application is deployed in the Ingram Micro Connect infrastructure, the provider will have information about the API end-point in the Provider Portal of Ingram Micro Connect.

5. Select the Authentication Type:
   • Certificate: select this type if the API end-point of the given instance is deployed in the provider’s internal infrastructure
   • OAuth: select this type if the API end-point of the given instance is deployed in the ISV or Ingram Micro Connect infrastructure
6. Specify the Network Access parameter:
   • Backnet: (default for Certificate) select this parameter if the API end-point of the given instance is deployed in the provider’s internal infrastructure, and the APS API of the provider’s CBC installation is accessible through BackNet
   • Public: select this parameter if the API end-point of the given instance is deployed in the ISV or Ingram Micro Connect infrastructure, and the APS API of the provider’s CBC installation is accessible from the Internet
   • Proxy: (default for OAuth) select this parameter if the API end-point of the given instance is deployed in the ISV or Ingram Micro Connect infrastructure, and the APS API of the provider’s CBC installation is enabled through proxy
7. If you want CloudBlue Commerce to automatically create Resource Types, Service Templates, and, optionally, Service Profiles together with the new application instance, in the Initialization Settings section, select the necessary option (the objects will be created with default configurations provided by the application):
   • Automatically create Resource Types and Service Templates
   • Automatically create Resource Types, Service Templates, and Service Profiles
   • Do not automatically create Resource Types, Service Templates, and Service Profiles
8. For deployment in the Ingram Micro Connect or ISV infrastructure, provide the OAuth Key and OAuth Secret values received from the Provider Portal of Ingram Micro Connect.
9. Select the Accept the impersonation level check box and click Next.
10. Specify any application settings values necessary for instance creation and click Next.
11. Check the provisioning parameters carefully and click Finish.