Manage Your Published Extensions

When working with multiple environments (say, Development1, Development2, Test, and Production), you can use the Manage Extension Lifecycle page to centrally manage published extensions across environments (and across projects). Use this page to deploy a published extension to a new Oracle Cloud Applications instance, and delete them when no longer needed.

Before you can deploy an extension to another instance from this page, make sure the extension is already published to your default Oracle Cloud Applications instance. You must also have a valid user name and password for the target instance you want to deploy to.

1. Access the Manage Extension Lifecycle page:
   • From the menu in the Designer's header, click Extension Lifecycle.
     
     
     Description of the illustration mel-ui-menu.png
     
     
   • Or, from the VB Studio left navigator, click Environments, then click Extension Lifecycle. (If you're in the Designer, click at the top left of the header to get to the VB Studio navigator.)

     You won't see the Extension Lifecycle button if you haven't yet added an Oracle Cloud Applications instance to your environment.

     
     
     Description of the illustration mel-ui-envts.png
     

   You should now see the Manage Extension Lifecycle page, which lists all the environments that are available for you to deploy to.
   

   
   Description of the illustration mel-ui-full-project.png

   
   

   You can work with an environment on this page as long as the authentication method for its Oracle Cloud Applications instance is OAuth. If there's an environment listed whose authentication method isn't OAuth, then you'll first need to add a new environment with the same base URL, but using OAuth as the authentication method, before you can work with it.

   Note:

   If you see a Provide Credentials button next to an environment, you must first sign in before you can deploy your changes to it.

   Expand each environment to view a list of the extensions already deployed. Each entry includes the extension name plus additional details, such as extension version, deployment date, who deployed the extension, and project name.

   Use the Only Show Extensions for My Project checkbox to toggle between viewing extensions deployed only from the current project, or from all projects.

2. To deploy an extension to another Oracle Cloud Applications instance:
   1. Find the extension that you want to deploy and click .
   2. Choose the environment that points to the instance you want to deploy to.

      Note:

      Your project administrator should have already created any additional environments you might need to deploy to. If you don't see an expected Oracle Cloud Applications instance or if that instance is unavailable, check with your project administrator or add a new environment right from this page (see step 3).
   3. Click Deploy.

      Deployments made from this page bypass any CI/CD pipelines previously set up.

      IMPORTANT: To see the newly published extension, your users will have to sign out of their Oracle Cloud Applications instance, then sign back in again to be certain they're seeing the latest.
3. If you'd like to deploy to an Oracle Cloud Applications instance but it's not listed on this page, you can add it.
   1. Click Add Environment.
   2. In the Add Environment panel, enter basic environment details, such as the environment's base URL, environment name, and user name and password for the target Oracle Cloud Applications instance.
      You can add any environment as long as the authentication method for its Oracle Cloud Applications instance is OAuth.
   3. Click Add.
   You also have the option to add an environment from the Environment's page. See Add the Oracle Cloud Application's Production Instance to an Environment.
4. To delete an extension from an Oracle Cloud Applications instance, click .
   Deleting an extension restores your application to its original state.