23.12 is is yet another compelling release of OIC. Without further ado, let's look at some of the new features -
Global OIC New Features
Import / Export Support
This feature allows you to do global exports/imports of all OIC artefact metadata. This feature is heavily used by OIC Gen2 customers, so this is a must in respect of feature parity. The modus operandi is analogue to Gen 2 -
Step 1 is set up the connection to your OCI Object Storage bucket -
Defining an export job is easy - instance storage defaults to what you have set up. The job name defaults to Export of instance yourInstance.
You can choose whether or not to export security artifacts (secrets).
Self-explanatory, I assume.
Now back in OIC --> Settings - Storage -
Let's try this out - I begin by creating a Bucket -
https://swiftobjectstorage.yourDatacenter.oraclecloud.com/v1/yourTenancy/yourBucket
I click on Export -
Again, this is extremely useful for existing OIC customers who want to adopt projects.
The password you enter is not your OCI password, rather it is based on an Auth token you generate at OCI User level -
Save the token and use as the password, when defining the storage connection in OIC -
Note the format of username - oracleidentitycloudservice/niall.commiskey@oracle.com
Now to the Import/Export page in OIC Settings -
I check in Object Storage -
I check back in OIC -
Project Enhancements
Ability to copy integrations into a project
This is a very useful feature, especially for OIC gen2 customers uptaking projects. This feature allows you to copy projects from the global context (i.e. those not in a project), or from another project and "paste" into your target project.
Here's a simple example - my integration - AA-Netsuite-CreateCustomer - this leverages a "global" Netsuite connection, as well as an OIC Lookup to set the Netsuite subsidiary id.
I create a new Project - AA-Netsuite-CustomerMgt -
Note the ability to search Projects. I de-select the checkbox, in this case.
I select my source integration and then click Copy -
The integration and its dependencies has been imported.
Publishing OIC APIS to OCI API Gateway
A major new feature of 23.12. However, this gives us more than just OIC Gen2 parity. Publishing is a feature within OIC Projects. Integrations need to be activated, before they can be published.
The publish UI is as follows -
Note the following -
1. the ability to choose which endpoints to publish. Unfortunately, I only have the one, but you get the idea.
2. Choose the compartment which hosts the api gateway.
3. Select the gateway
4. Select an existing deployment on that gateway or create a new deployment. A word or two on deployments - a deployment can host from 1 to 50 endpoints. Each gateway currently supports up to 20 deployments. That allows for up to 1000 endpoints per gateway. You can decide yourself how you want to split the apis over deployments, e.g. create a "Netsuite" deployment for all your Netsuite related apis.
So think of the deployment as a folder for related apis/OIC endpoints.
I publish -
Note the ability to Undo publish - giving you full lifecycle control. If you create a deployment and have published only the api(s) from a single integration, clicking Undo publish will delete the routing rule and the deployment.
There are some pre-requisites you need to do in order to publish from OIC to the OCI API Gateway.
This connectivity is RPST based and you need to do some setup in your identity domain to make this work.
I will document these in a separate post.
New Notification Center
The Notifications center shows the status of asynchronous operations (such as installing a project from the Integration Store). This eliminates the need to click the refresh icon to see the status.
The Announcements page, formerly accessible via the bell icon, can now be accessed via the megaphone icon.
No comments:
Post a Comment