#1046 - OIC Integration Basics Lab 12 Multi-Verb Support

Use of multiple verbs can help reduce the number of integrations you have, e.g. instead of having a getOrder integration and a createOrder integration, combine these into 1.

Here's a simple example of such.

First verb we implement is GET - 

I could add more verbs, e.g. PUT for order update, but these 2 will suffice.

Note the use of Pick to differentiate between the 2 operations.

They are both marked as incomplete, as I need to define tracking fields for each verb.

I do the same for getOrders - 

I now implement the 2 map actions - 

I activate the integration and click Run - 

Check out the endpoint metadata - 

 

 

#1045 - OIC Integration Basics Lab 11 File Server

File Server is an sftp conform file server that ships with OIC3. 

Each OIC instance gets 500GB space.

You can access the File Server admin page via Settings --> File Server

Check out the following post which discusses the initial File Server setup.

Note the Host, IP and Port information - you can use this to connect to the file server via an ftp client, such as FileZilla.

The user / password you use on signing in via FileZilla will determine which folders you see.

Also note the ability to stop/start the file server -

Let's look at the other File Server menu options -

Users - 

Per default, users are not enabled for file server, however, it takes jus one click to enable user accounts for File Server.

Groups -

Users can belong to groups and thus get access to File Server and certain folders etc.

Folders -

As you see, a default folder has been created for my group; now to add permissions. 

Net, net - check the settings here, if you have permissions issues with accessing File Server folders and files.

Working with File Server is easy -

  

 

 

1044 OIC Integration Basics - Lab 10 Integration Variables

Simple Variables

We have already created some variables in OIC via the Assign action - 

These variables are available throughout the lifespan of the integration flow. 

I now add a scope to my integration and add an Assign to it - 

This variable is only visible within this scope.

Schedule Parameters

These parameters "live" beyond the execution of a flow. So they can be used to "push" values from one flow to another.

The parameters are visible when you run a scheduled integration - 

They can also be set during the execution. e.g. I include a new parameter, dateLastRun and set this at the end of the integration - 

I run the integration - 

I run again, and see this parameter has been set - 

Property Values

Use properties to allow runtime overrides of properties defined at designtime. For example - I have a property adminEmail, which I use in Notification actions. This is set to niall@commiskey.com. I now need to send the emails to my new admin johanna@commiskey.com, so, instead of having to edit the integration, I just change the property.

Integration properties can be defined for scheduled and app-driven integrations -

I can update the property values, while the integration is not activated - 

I can only view the property, once the integration has been activated - 

Global Variables

These variables are available throughout the life of the integration flow. As opposed to the simple string variables created via Assign, these can also be of complex type. The types available are those attached to the integration trigger or invokes.