Create or Import a Project

You can create a project in which to design, manage, and monitor integrations. You can also import user-developed, accelerator, or recipe projects into an instance.

Create or Import a Project

  1. In the navigation pane, click Projects.
  2. Click Add.
  3. Select an option:
    • Create a new project.
    • Import an existing project.
  4. To create a new project, perform the following steps.
    1. Click Create.
    2. Enter the following information.
      Field Description

      Name

      Provide a meaningful name so that others can understand the project. You can include English alphabetic characters, numbers, underscores, and dashes in the identifier.

      Note: You cannot create a project name containing -BA- or _BA_. These conventions are reserved for accelerator projects.

      Identifier

      Accept the default identifier value. The identifier is the same as the project name you provided, but in upper case.

      Keywords Enter keywords (tags) to identify the project. You can search for projects on the Projects page using keywords. Keywords are useful for filtering and discovery.

      Description

      Provide a meaningful description so that others can understand the project.

      Anyone can edit, view, and monitor

      • Select this option to allow anyone to edit, view, and monitor resources in the project.

        You can always restrict access at a later time.

      • Don't select this option if you want to restrict access to editing, viewing, and monitoring resources in this project. After project creation, you can select the specific groups and users to which to provide access. See Control Who Can Edit, View, and Monitor in a Project.
    3. Click Create.

      Your new project page is displayed. You can now add integrations, connections, lookups, and JavaScript libraries to the project.

  5. To import an existing project (.CAR file), perform the following steps. This enables you to import a project with all assets and metadata from one system to another. You can import user-developed, accelerator, or recipe projects.

    Ensure that you understand connection behavior when importing a project. See Export a Project.

    1. Click Import.
    2. Click the field to browse for a project or drag and drop a project into the field.
    3. With the Anyone can edit, view, and monitor check box, select the level of access you want to provide to other users:
      • Select this option to allow anyone to edit, view, and monitor resources in the project.

        You can always restrict access at a later time.

      • Don't select this option if you want to restrict access to editing, viewing, and monitoring resources in this project. After import, you can select the specific groups and users to which to provide access. See Control Who Can Edit, View, and Monitor in a Project.
    4. Click Import.

      The project connections contain information that is specific to the processing environment. Connections in the imported project omit this potentially sensitive data. You must reconfigure connections before they can operate properly.

Understand an Imported Oracle Accelerator Project

If you import an Oracle accelerator project into your project, the project includes the labels Accelerator and Oracle on the Projects page. The Type column also includes the Accelerator label.


The Name, Type, Last updated, and Status columns are shown. The integration in the Name column has labels for Accelerator and Oracle. The Type column says Accelerator.

Note the following accelerator project restrictions:
  • You cannot edit the details that were specified when the project was created, such as name, project identifier, description, and keyword selections. These details are in read-only mode.
  • The Edit, Clone, and Delete tasks are not visible under the Actions Actions icon menu on the Deploy tab. The only task visible under this menu is View.
  • You can extend (customize) an integration in the accelerator project by selecting Actions Actions icon, then Extend. See Extend an Integration in an Accelerator Project.

Note the following restrictions for individual assets in accelerator projects

Integrations Connections Lookups JavaScript Libraries Deployments Certificates

Allowed:

  • View
  • Activate
  • Deactivate
  • Override default property values

Restricted:

  • Add
  • Delete
  • Clone
  • Create new version

Allowed in extended accelerator:

  • Add a scope or stitch action before an invoke
  • Merge a scope or stitch action from the next lower version of the integration

Restricted in extended accelerator:

  • Update primary information

Allowed:

  • View
  • Test
  • Refresh metadata
  • Edit and save
  • Save and reactivate

Restricted:

  • Add connections
  • Delete connections
  • Update primary information

Allowed:

  • View
  • Edit and save
  • Add or remove rows and update values in rows

Restricted:

  • Add lookups
  • Delete lookups
  • Update domain name
  • Add or remove domain
  • Update primary information

Allowed:

  • View

Restricted:

  • Add libraries
  • Delete libraries

Allowed:

  • Uninstall
  • View
  • Export **
  • Activate
  • Deactivate

Restricted:

  • Create, update, or delete the deployment

No restrictions.

** Export as an accelerator or extended accelerator only.

Add a Newer (Extended) Version of an Accelerator Project

Assume a newer version of an accelerator project becomes available for you to import.

For this example, assume the first version of the accelerator project included integrations Oracle ERP 1 and Oracle ERP 2, each with versions of 1.0.0.
The Integrations section shows two integrations, Oracle ERP 1 and Oracle ERP 2, each with versions of 1.0.0. Both are labeled as Configured. An Actions (…) menu is shown for each. An Add icon appears in the upper right corner.

The two integrations and their versions are included in a project deployment named 1.0.0 that you previously imported into your instance.
The Design, Deploy (which is selected), and Observe tabs are shown. To the right are the Export, Activate, and Deactivate links. Below is a table with columns for Name, Identifier, Integrations, and Last updated. One deployment named 1.0.0 is shown.

A newer version of the accelerator project then becomes available. This version now includes two versions of the two integrations: Oracle ERP 1 versions 1.1.0 and 1.0.0 and Oracle ERP 2 versions 1.1.0 and 1.0.0.
The Integrations section shows two integrations, Oracle ERP 1 and Oracle ERP 2, each with versions of 1.0.0 and 1.0.1. Both are labeled as Configured. An Actions (…) menu is shown for each. An Add icon appears in the upper right corner.

All four integrations and versions are included in a project deployment named 1.1.0.
The Design, Deploy (which is selected), and Observe tabs are shown. To the right are the Export, Activate, and Deactivate links. Below is a table with columns for Name, Identifier, Integrations, and Last updated. Two deployments, named 1.0.0 and 1.0.1, are shown.

  1. In the navigation pane, click Projects.
  2. Click Add.
  3. Click Import and upload the latest accelerator project.
    The following message is displayed:
    Project has been successfully imported.


    The Name, Type, Last updated, and Status columns are shown. The integration in the Name column has labels for Accelerator and Oracle. The Type column says Accelerator. The Status column says Configured.

  4. Click the project name or click Edit icon.

    Note that the latest accelerator project includes Oracle ERP 1 versions 1.1.0 and 1.0.0 and Oracle ERP 2 versions 1.1.0 and 1.0.0.
    The Integrations section shows two integrations, Oracle ERP 1 and Oracle ERP 2, each with versions of 1.0.0 and 1.1.0. Both are labeled as Configured. An Actions (…) menu is shown for each. An Add icon appears in the upper right corner.

Understand an Imported Recipe Project

When you import a recipe project, it is displayed as Developed in the Type column on the Projects page.


The Name, Type, Last updated, and Status columns are shown. The Type column says Developed. The Status column says Configured.