1. Developing Applications with Oracle Visual Builder in Oracle Integration Generation 2
  2. Develop Applications
  3. Work with Pages and Flows
  4. Work With Custom Web Components
  5. Import a Web Component Archive

Import a Web Component Archive

If you want to use a web component that's not available in your Component Exchange, you can import the component as a ZIP archive. For example, when your team member is developing a component, they can give it to you as an archive so you can try it in your application.

You also have the option of importing web components that allow you to:

To import a custom web component archive:

  1. Open the application into which you want to import the component.
  2. Open a page in your application in the Page Designer.
  3. Locate the Custom section in the Components palette and click Import Web Component ( Import Web Component icon ).
  4. Upload your ZIP archive in the Import Web Component dialog box. Click Import.

    You can add the ZIP archive by dragging it into the upload area or clicking the area and locating the file on your local system.


    Description of page-designer-component-import.png follows
    Description of the illustration page-designer-component-import.png

The imported web component is added to your app's resources/components folder and displayed in the Custom Components category of the Components palette or in the category specified by the component’s metadata. After importing the web component, you can position it in your page and configure its properties in the Properties pane as you would a standard component.


Description of page-designer-component-custom-imported.png follows
Description of the illustration page-designer-component-custom-imported.png

Note:

Importing web components makes them a part of your application. Because these components are not cached, you're likely to run into performance issues when they are downloaded each time you reload the Page Designer for preview, or at runtime when you publish an update to your app. As a best practice then, it helps to publish your components to a CDN (Content Delivery Network) or an external location that your browser can cache requests from. This is useful especially when you have multiple apps that use the same components. Talk to your administrator for site-specific information on how to publish these components externally.