13 Deploying Partner Applications to Customer's Test and Production Environments

This section describes how to install and deploy partner applications to a customer's test and production environments.

Topics:

Installation and Deployment Scenarios

Topics:

This section introduces the installation and deployment scenarios for partner applications with Oracle Sales Cloud customizations, per-tenant deployed Java connectors, or database customizations.

Scenario 1: Partner Application with Only Oracle Sales Cloud Customizations

Partner's Development Environment

In this scenario, the partner uses an Oracle Sales Cloud development instance in their development environment. The partner extends or builds Oracle Sales Cloud customizations using Application Composer, Page Composer, Global Menu, and so on. The partner packages such customizations and distributes to Oracle Sales Cloud customers.

Customer's Test Environment

The customer uses an Oracle Sales Cloud test instance in their test environment. In this test environment, the customer deploys or creates partner customizations. The customer also performs functional and integration testing to verify that the partner application integrates with other customizations and partner applications deployed in their test environment.

Customer's Production Environment

The customer uses an Oracle Sales Cloud production instance in their production environment. After completing the necessary testing, the customer rolls out the new partner application to their production environment by installing and deploying the partner application in the production environment.

Description of crm_one.gif follows
Description of the illustration crm_one.gif

Scenario 2: Partner Application with Only Oracle Java Cloud Service and Oracle Database Cloud Service Customizations

Partner's Development Environment

In this scenario, the partner uses an Oracle Sales Cloud development instance, an Oracle Java Cloud Service development instance, and an Oracle Database Cloud Service development instance in their development environment. The partner extends and builds the following:

  • A Java application (.ear or .war) that contains a per-tenant deployed Java connector

  • SQL scripts that include database customizations, such for custom tables, PL/SQL Procedures and Functions, creating database REST interfaces, and APEX applications

    Note:

    Some database extensions do not require database SQL scripts. For example, an Oracle Java Cloud Service ADF or Java EE application using JPA persistence does not require database SQL scripts for any objects that are managed through the Object Relational Mapping (ORM).

    In some scenarios, database SQL scripts are required for custom tables, PL/SQL Procedures and Functions, creating database REST interfaces, and APEX applications.

The partner distributes these applications to Oracle Sales Cloud customers.

Customer's Test Environment

The customer uses an Oracle Sales Cloud test instance, an Oracle Java Cloud Service test instance, and an Oracle Database Cloud Service test instance in their test environment. In this test environment, the customer installs and deploys the Java application and the SQL scripts provided by the partner. The customer also performs functional and integration testing to verify that the partner applications integrate with other customizations and partner applications deployed in their test environment.

Customer's Production Environment

The customer uses an Oracle Sales Cloud production instance, an Oracle Java Cloud Service instance, and an Oracle Database Cloud Service instance in their production environment. After completing the necessary testing, the customer rolls out the new partner application to their production environment by installing and deploying the partner applications in the production environment.

Description of crm_two.gif follows
Description of the illustration crm_two.gif

Scenario 3: Partner Application with Oracle Sales Cloud, Oracle Java Cloud Service and Oracle Database Cloud Service Customizations

Partner's Development Environment

In this scenario, the partner uses an Oracle Sales Cloud development instance, an Oracle Java Cloud Service development instance, and an Oracle Database Cloud Service development instance in their development environment. The partner extends and builds the following:

  • Oracle Sales Cloud customizations using Application Composer, Page Composer, Global Menu, and so on

  • A Java application (.ear or .war) that contains a per-tenant deploy Java connector

  • SQL scripts that include database customizations, such for custom tables, PL/SQL Procedures and Functions, creating database REST interfaces, and APEX applications

    Note:

    Some database extensions do not require database SQL scripts. For example, an Oracle Java Cloud Service ADF or Java EE application using JPA persistence does not require database SQL scripts for any objects that are managed through the Object Relational Mapping (ORM).

    In some scenarios, database SQL scripts are required for custom tables, PL/SQL Procedures and Functions, creating database REST interfaces, and APEX applications.

The partner distributes these applications to Oracle Sales Cloud customers.

Customer's Test Environment

The customer uses an Oracle Sales Cloud test instance, an Oracle Java Cloud Service test instance, and an Oracle Database Cloud Service test instance in their test environment. In this test environment, the customer installs and deploys the Java application and the SQL scripts provided by the partner. The customer also performs functional and integration testing to verify that the partner applications integrate with other customizations and partner applications deployed in their test environment.

Customer's Production Environment

The customer uses an Oracle Sales Cloud production instance, an Oracle Java Cloud Service instance, and an Oracle Database Cloud Service instance in their production environment. After completing the necessary testing, the customer rolls out the new partner application to their production environment by installing and deploying the partner applications in the production environment.

Description of crm_three.gif follows
Description of the illustration crm_three.gif