10 Tips for Working with Projects
Ready to be an expert at projects? These tips will help you get started on the right path.
1. Allow Your Business Goals to Inform Your Strategy for Projects
With a project, you can create a custom solution that supports your business goals. See 4 Ways to Organize Projects.
2. Aim for No More Than Twenty Integrations per Project
The optimal number of integrations for each project is the number that makes sense for your business goals. Oracle recommends limiting the integrations in a project to about twenty, at least when you're starting out, so that the assets within a project are still easy to find and navigate at a glance. Whatever number you choose, make sure you stay within the service limits. See Service Limits in Provisioning and Administering Oracle Integration 3.
3. Remember That Organization Isn't Always About Separation
Managing related integrations in a project is useful, but what if you want to call a child integration from integrations that are in multiple projects? Not to worry, projects can accommodate this requirement, too. When you create an integration in a project, choose whether to make the integration available in other projects, in addition to its own project.
See Invoke Child Integrations Inside or Outside of Projects and Create an Integration.
4. Keep Everything Secure by Giving the Minimum Access Required
The tenancy administrator assigns application roles that grant people access to work in Oracle Integration. The tenancy administrator assigns these roles in the Oracle Cloud Infrastructure Console.
Additionally, the project owner, who is typically either a developer or an administrator, manages access to projects using role-based access control (RBAC). The project owner assigns these roles in a project in Oracle Integration.
To work in a project, a person must have both the required application roles and the required project roles. Project roles never override application roles. As a best practice, administrators and project owners should give people only the minimum access they need to do their jobs.
Reminder: You can control access to projects, but the control extends only to design time, not to runtime. Those with the endpoint, the credentials, and an OAuth token can run the integration at runtime.
5. Plan Your Working Times if You're Working with a Team
Your entire team can work in a project at the same time, but the same is not true of integrations. When a person opens an integration for editing, the integration is locked, and no one else can edit it. Make sure you plan your work accordingly so that everyone can complete their work in a timely way.
6. Be Descriptive When Versioning and Deploying
When you version an integration and when you create a project deployment, make sure you include information about the changes in the Description field. This information helps you select the right integration version when you create the project deployment and select the right project deployment to export.
7. Adopt a Versioning Strategy for Integrations
Version numbers for integrations use the following format: xx.yy.zzzz, where each x, y, and z is a number that you specify.
Typically in versioning, the xx numbers correspond to major versions, the yy numbers correspond to minor versions, and the zzzz numbers correspond to patch versions. You can increment version numbers however you want, but Oracle recommends establishing standard operating procedures for when you increment each number. For instance:
-
Increment the xx number by one when you add an integration to the project deployment.
The endpoint URLs for the integrations in the project deployment don't change when you increment the version number.
- Increment the yy number by one for significant changes to integrations.
- Increment the zzzz number by one for minor changes.
8. Choose Carefully When Creating Project Deployments
Deploying multiple integrations at the same time is easy, thanks to fine-grained deployment creations in a project. All you need to do is select the integrations to include and their versions. Just make sure you select the correct integrations and versions to include in the project deployment.
9. Update Your Workflows
Projects offer streamlined workflows for all your integration work, from designing to monitoring. Spend less time navigating from place to place in the user interface and more time meeting your organization's integration needs.
10. Monitor Integrations on the Observe Page
When you want to see what's happening with all the integrations in a project, go to the Observe page within a project. Here, you can see at-a-glance status and error information for all of the project's integrations.
Additionally, as long as you have access to a project, you can monitor the integrations on the Observability pages.