Oracle Integration (v25.04) – One from the archives I know! my post is here: NEW FEATURES in Oracle Integration 3! (25.04) – introduced a number of enhancements, but one that caught my attention was the ability to generate iCal schedules using natural language. To be honest, it might not sound an overly exciting topic as we see with some of the larger AI announcements coming from Oracle at the moment (hence, it’s taken me a long time to get around to this post!), but for anyone who spends time building and maintaining integrations, this is one of those features that can remove a surprising amount of friction from day-to-day development and operations.

Scheduling integrations has always been an interesting area within Oracle Integration. Creating a simple schedule is straightforward enough of course but once business users start including requirements which call for integrations to run on the first Monday of the month, every 30 minutes during office hours or only on weekdays excluding public holidays, it can become much more complicated. At that point, you either need to remember the correct iCal syntax or spend time searching documentation and validating the recurrence patterns.

A new natural language scheduling capability looks to address this issue. Rather than manually constructing an iCal expression, a developer can now simple describe the schedule in natural terminology and allow Oracle Integration to generate the underlying recurrence rule for them… but, as you will read… there are trials and tribulations contained.

What is iCal?

Before looking at the new feature, it is worth understanding what iCal actually is and why Oracle uses it for integration scheduling.

iCal (or iCalendar) is an open standard for defining calendar and scheduling information. Most people encounter it through calendar applications like MS Outlook, Google Calendar, etc where recurring meetings and events are represented using iCalendar rules behind the scenes. What make the standard particularly useful is the ability to describe highly complex recurrence patterns in a consistent and globally understood format.

Oracle Integration leverages this same standard when scheduling integrations. Whenever a scheduled integration runs, OIC evaluates an iCal recurrence rule to determine whether the current date and time match the defined execution pattern. This means that Oracle can support everything from very simple schedules to extremely complex or nuanced business requirements without needing a separate scheduling engine.

The reality is that many OIC developers use iCal expressions regularly without ever really thinking about them… until an integration schedule attracts attention by way of a complicated business requirement and the standard scheduling options are no longer sufficient.

The Hidden Complexity of Integration Scheduling

When we agree integration schedules with stakeholders, an initial request is usually quite simple. Something like “Can we run this every 15 minutes?“, “can we run this once each morning?“, “can we run this every weekday?“.

Generally, those simple requirements are quite easy to satisfy. The challenge comes later when the organisation starts relying on the integration and true operational requirements begin to emerge. A requirement that sounds straightforward can very quickly become something much more sophisticated, like:

• Run every 30 minutes between 8am and 8pm
• Only execute on Monday to Friday, but ignore public holidays
• Don’t execute on the weekends, unless its the last weekend in a month
• End the schedule at the end of the financial year
• Trigger it on the first business day or the payroll day of each month

Once you get here, scheduling cannot be satisfied by simple out of the box options. Historically, this meant that understanding the underlying iCal syntax and validating that the resulting expression reflects accurately the true business requirement.

Generating iCal Rules from Natural Language

With the new functionality of Oracle Integration, initially made available in v25.04, developers can now describe the scheduled using the same language they would use when speaking to a business stakeholder.

For example, “Run every weekday at 9am”. OIC can now convert this easily into an iCal recurrence rule:

FREQ=DAILY;BYHOUR=9;BYMINUTE=0;BYDAY=MO,TU,WE,TH,FR;

Or, “Run on the first Monday of every month”. OIC can now convert this easily into an iCal recurrence rule:

FREQ=MONTHLY;BYDAY=1MO;

This generated expressions look pretty simple in the above examples, but the real advantage is when schedules become more complex.

Putting it to the Test

As with anything, new features always look best during a product demo. The question does always come back to whether or not they solve a genuine problem when you actually start using them day-to-day. To get a better feel for the natural language scheduling capability, I tried a mixture of simple to increasingly complex scheduling requirements (that actually represent real-world business requirements).

Example 1: Every 15 minutes

Let’s start with the simplest possible scenario

Natural Language Prompt: Run every 15 minutes

Generated iCal Expression:

FREQ=MINUTELY;INTERVAL=15

This is a schedule that most OIC developers could very easily create manually in a matter of seconds. But, nevertheless, it does provide a good introduction to the feature because it demonstrates how it works quite nicely and easily. Enter a requirement in plain language, allow OIC to interpret that requirement and then review the resulting recurrence rule before saving the defined schedule.

For very straightforward examples like this, generating from natural language is more about convenience. It probably removes a few clicks and presents the recurrence expression in a format that is understandable by both technical and non-technical users. It is worth noting though, that generating this simple schedule is very easy to do with out of the box click and select capability already in OIC:

Example 2: Business Hours Processing

The next examples that I will try adds a small layer of complexity and it appears regularly in enterprise integration.

Natural Language Prompt: Run every 30 minutes between 8am and 8pm

Generated iCal expression:

FREQ=DAILY;BYHOUR=8,9,10,11,12,13,14,15,16,17,18;BYMINUTE=0,30;BYSECOND=0;

This requirement appears to be relatively simple still but in reality there are multiple conditions that have to be satisfied in order to get it right:

1. The integration must run every 30 minutes
2. The execution of the integration should only occur during business hours (8am to 8pm)

What I particularly like in this example is that the natural language approach kept the focus on the actual business requirement. it might have been a bit annoying to manually write out an expression.

Example 3: The 1st Monday of Every Month

Adding a further layer of complexity, the feature starts to show greater value.

Natural Language Prompt: Run at 8am on the first Monday of every month

Generated iCal Expression:

FREQ=MONTHLY;BYDAY=1MO;BYHOUR=8;BYMINUTE=0;

In my experience, business users ask for schedules like this all of the time to match their business process or reporting cycles. The requirement itself remains easy to understand but many developers would need to double check or recall the correct combination of BYDAY. Again, it’s not difficult syntax but it is also not something that many people use frequently enough to remember off the top of their heads. In my opinion, here we start to see effective removal of mental context switching.

Example 4: A Complex Scheduling Requirement

To really test the capability of the feature, I wanted to push the boundaries away from typical simple examples and see how OIC handled a more realistic enterprise requirement in large Oracle footprints.

Natural Language Prompt: Run every 15 minutes between 7am and 7pm on weekdays, but only during January, April, July and October

Unfortunately, Oracle Integration didn’t handle this well

So, I tried rewording.

Natural Language Prompt: Run every 15 minutes between the hours 7am and 7pm and Run only on Monday, Tuesday, Wednesday, Thursday, Friday and Run only in the following months: January, April, July and October

Unfortunately, OIC still struggled:

The more interesting part of this however, is that in both examples, OIC does actually get to the right answer! see screenshot below:

Breaking this down:

FREQ=MINUTELY; -- the recurrence is based on minutes
INTERVAL=15; -- executes every 15 minutes
BYHOUR=7,8,9,10,11,12,13,14,15,16,17,18; -- only run during hours 7am to 7pm
BYDAY=MO,TU,WE,TH,FR; -- only run on weekdays
BYMONTH=1,4,7,10; -- only run in January, April, July, October

A further unfortunate annoyance is that OIC doesn’t support the UNTIL parameter

So, in summary, I guess that there is still more work to do from the product development team to really improve this feature. I think I will raise an SR (for getting to the right answer but OIC being unable to validate it) and an enhancement request (for the UNTIL parameter).

Understanding What Oracle Integration Generates

One thing I particularly like about this feature within Oracle Integration is that it does not abstract away the underlying technology completely. As I mentioned, Oracle Integration is still using standard iCal expressions, which means that the resulting schedules remain transparent (and portable!). Even though with the natural language iCal definition doing the heavy lifting, It’s still worth understanding the core components:

Base Parameters

Filter & Timing Modifiers

Best Practices Still Apply (always!)

Whilst Natural language scheduling does make creating schedules easier, it doesn’t remove the need for good scheduling practices. This is especially important when operating in large integration footprints with 100s of integrations, all with their own schedule. Analysing the totality of the integration landscape is important to avoid performance challenges, overlapping executions or unnecessary resource consumption. Some key best practice principles are below::

• Avoid highly aggressive schedules unless they are absolutely necessary
• Make sure that integrations complete comfortably within their execution window
• Validate time zone settings carefully
• Test recurrence patterns before any production deployment
• Review recurrence schedules periodically as business requirements evolve and operational stress limits are understood