12c SOA - Modification of existing ESS scheduler

Sometimes we may need to modify the existing ESS schedulers due to Job execution time changes or day light saving time adjustment.

A scheduler can be modified in following 3 steps.

Step 1: Modification of existing scheduler.
Target navigation⇾Scheduling services⇾ESSAPP

Go to Scheduling services⇾Job requests⇾Define Schedules

Type the Job definition name and click go.

Your job will appear, select he job and click edit.

 Edit Schedule page will open. Click Change Frequency. It will display a warning message. Click yes.

Go to start date⇾click the select date time button.

Here in this example we have increased 5 min.

Note: After modification of time always select next day else it will trigger all schedulers from the start day till current day.

In this example we have selected 14^th because current day is 13^th . If we select 13^th and only change time then it will trigger all schedulers from 12^th till 13^th .

Click ok.

 Step 2: Submit the job request.
Now go to scheduling services⇾job reques⇾Submit job request.

Select the use existing schedule radio button. Enter the name of the schedule and click search icon.

Again enter the name of the schedule and click forward arrow to search. Your schedule will appear. Select your schedule and click ok.

Your schedule will appear with all its details⇾click ok to submit the schedule.

 Step 3: Delete the old parent of the scheduler.
Go to Scheduling service⇾job request⇾search job request

Select the All scheduling services sharing ESS repository radio button, enter your job definition name and un-check the succeeded checkbox in submitted tab.

Else it will give all the schedulers and we won’t find our specific scheduler.

Here our scheduler appears in the first line of search. The last line is n/a. n/a means parent of current scheduler. A scheduler can have only one parent. So select the old parent and cancel it.

In the following screen shot we have cancelled the old parent.

NOTE: It is a good practice to keep the definition name of the job different from schedule name.

Ex: Definition name: ApplicationName_AutomaticTrainingWelcomeEmail

       Scheduler name: ApplicationName_AutomaticTrainingWelcomeEmail_daily

12c SOA BPEL - Set and Get Preference Property

By adding Preference property in composite.xml, we could get the value as variable into our BPEL process and later we can change the value from the EM console.

<component name="Helloworld">
    <implementation.bpel src="Helloworld.bpel"/>
    <property name="bpel.preference.MyPreference">Value</property>
</component>

Now we can use this MyPreference value in our BPEL process by using the following function
ora:getPreference(MyPreference)

Implementation steps:
Create a SOA Project

 Choose Synchronous BPEL Process

Open Composite.xml file in source mode and add Preference property in inside Component section.

Here I am using it for Email so my property name is "bpel.preference.Email", you can give it any name as per your requirement.

                 bpel.preference.{CustomName}

<component name="PreferenceBPELProcess" version="2.0">

    <implementation.bpel src="BPEL/PreferenceBPELProcess.bpel"/>

    <componentType>

<service name="preferencebpelprocess_client" ui:wsdlLocation="WSDLs/PreferenceBPELProcess.wsdl">

<interface.wsdl interface="http://xmlns.oracle.com/SOAApplication/PreferenceProject/PreferenceBPELProcess#wsdl.interface(PreferenceBPELProcess)"/>

      </service>

    </componentType>

    <property name="bpel.config.transaction" type="xs:string" many="false">required</property>

    <property name="bpel.preference.Email">test1@test.com</property>

  </component>

Use this preference property inside BPEL.

To use this property inside BPEL you need to use ora:getPrefernce("CustomName") function.

ora:getPreference('Email')

 Deploy and Test from EM console

Update preference property value in EM console.
We can update this property from System MBean Browser inside EM console.
 Go to EM console (http://host:7001/em)⇾Navigate to "Farm_base_domain"⇾"Weblogic Domain" folder⇾ Right click on your domain⇾"System MBean Browser"

Go to Application defined MBean Browser⇾"oracle.soa.config"⇾"soaserver"⇾"SCAComposite"⇾Choose your composite

 Then navigate to "SCAComposite.SCAComponent"⇾your component name⇾Click on "properties"

 Now you can see all the preference properties that you defined in your composite. You can change preference property value here.

Notes:

• If you restart the servers or re-deploy the composite then it will take the default preference value set to the composite.xml.

12c SOA XSLT - Use of Template Rules or apply-templates

Template Rules or apply-templates: 
Template rules are xsl:template statements with match attributes. Template rules are supported by the XSLT Map Editor. <xsl:apply-template> tag signals the XSLT processor to find the appropriate template to apply, based on the type and context of each selected node.

<xsl:apply-templates> is a little different with named template and it is the real power of XSLT: It takes any number of XML nodes (whatever you define in the select attribute), iterates them (this is important: apply-templates works like a loop!) and finds matching templates for them:

A concept to understand with XSLT is that of the "current node". With <xsl:apply-templates> the current node moves on with every iteration, whereas <xsl:call-template> does not change the current node. I.e. the . within a called template refers to the same node as the . in the calling template. This is not the case with apply-templates.
There are some other aspects of templates that affect their behavior: Their mode and priority, the fact that templates can have both a name and a match. It also has an impact whether the template has been imported (<xsl:import>) or not. These are advanced uses and you can deal with them when you get there.

Use case:
Here i will concatenate the employee names with a space from a set of employess input xml using apply template.
Input XML:

<Employees>

 <Employee>

  <Id>1ws</Id>

  <Name>test1</Name>

 </Employee>

 <Employee>

  <Id>2ws</Id>

  <Name>test2</Name>

 </Employee>

</Employees>

Output expected: test1 test2

Implementation steps:

Create a SOA project

 Choose synchronous BPEL process

 Change the XSD as required.

 Choose the source and target payloads

 Add the apply templates

<xsl:template match="/">

    <ns0:processResponse>

      <ns0:result>

        <xsl:apply-templates select="/ns0:Employees/ns0:Employee/ns0:Name"/>

      </ns0:result>

    </ns0:processResponse>

  </xsl:template>

  <xsl:template match="/ns0:Employees/ns0:Employee/ns0:Name">

    <xsl:value-of select="concat(' ',.)"/>

  </xsl:template>

 Deploy and Test

12c SOA - Generate a random/unique number in XSLT ?

A unique ID needs to be assigned to every asynchronous request for tracking the status/uniquely identifying the request message. The ID needs to be universally unique (UUID) that is generated by the Oracle SOA Systems (ESB/BPEL) to correlate the request for future reference. You can take advantage of the XPath Extension Function orcl:generate-guid() that comes out-of-the box and format it accordingly like this: 

In XSLT:
<xsl:variable name="RandomNum">
    <xsl:value-of select="orcl:generate-guid()"/>
   </xsl:variable>

In BPEL:
   <variables>
        <variable name="correlationID" type="xsd:string">
          <from>oraext:generate-guid()</from>
        </variable>
      </variables> 
  

12c SOA - Use of call template

Call template is usually called named templates to the XSLT map. These templates can be edited within the XSLT Map Editor. We can invoke named templates by using the xsl:call-template instruction.

Use case:
Here I will show you how to get the time Zone Hour AM PM as "9:00AM" from the input as orientationStartDateTime "2019-11-11T09:00:00" using the call template.

Create a SOA Project

 Select composite with BPEL Process

 Select Synchronous BPEL Process

 Modify the schema

 <?xml version="1.0" encoding="UTF-8"?>

<schema attributeFormDefault="unqualified"

                elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/SOAApplication/Project1/CallTemplateBPELProcess"

                xmlns="http://www.w3.org/2001/XMLSchema">

                <element name="process">

                                <complexType>

                                                <sequence>

                                                                <element name="orientationStartDateTime" type="string"/>

                                                </sequence>

                                </complexType>

                </element>

                <element name="processResponse">

                                <complexType>

                                                <sequence>

                                                                <element name="timeZoneHourAMPM" type="string"/>

                                                </sequence>

                                </complexType>

                </element>

</schema>

 Drag and drop a Transformation activity from Components pallet

 Select the source and Target payloads

 Open the XSLT

 Add the call template

<?xml version="1.0" encoding="UTF-8" ?>

<xsl:stylesheet version="1.0" xmlns:ns0="http://xmlns.oracle.com/SOAApplication/Project1/CallTemplateBPELProcess"

                xmlns:socket="http://www.oracle.com/XSL/Transform/java/oracle.tip.adapter.socket.ProtocolTranslator"

                xmlns:oracle-xsl-mapper="http://www.oracle.com/xsl/mapper/schemas"

                xmlns:dvm="http://www.oracle.com/XSL/Transform/java/oracle.tip.dvm.LookupValue"

                xmlns:mhdr="http://www.oracle.com/XSL/Transform/java/oracle.tip.mediator.service.common.functions.MediatorExtnFunction"

                xmlns:oraxsl="http://www.oracle.com/XSL/Transform/java"

                xmlns:oraext="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"

                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"

                xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"

                xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

                xmlns:xref="http://www.oracle.com/XSL/Transform/java/oracle.tip.xref.xpath.XRefXPathFunctions"

                exclude-result-prefixes="oracle-xsl-mapper xsi xsd xsl ns0 socket dvm mhdr oraxsl oraext xp20 xref"

                xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"

                xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

  <oracle-xsl-mapper:schema>

    <!--SPECIFICATION OF MAP SOURCES AND TARGETS, DO NOT MODIFY.-->

    <oracle-xsl-mapper:mapSources>

      <oracle-xsl-mapper:source type="WSDL">

        <oracle-xsl-mapper:schema location="../WSDLs/CallTemplateBPELProcess.wsdl"/>

        <oracle-xsl-mapper:rootElement name="process"

                                       namespace="http://xmlns.oracle.com/SOAApplication/Project1/CallTemplateBPELProcess"/>

      </oracle-xsl-mapper:source>

    </oracle-xsl-mapper:mapSources>

    <oracle-xsl-mapper:mapTargets>

      <oracle-xsl-mapper:target type="WSDL">

        <oracle-xsl-mapper:schema location="../WSDLs/CallTemplateBPELProcess.wsdl"/>

        <oracle-xsl-mapper:rootElement name="processResponse"

                                       namespace="http://xmlns.oracle.com/SOAApplication/Project1/CallTemplateBPELProcess"/>

      </oracle-xsl-mapper:target>

    </oracle-xsl-mapper:mapTargets>

    <!--GENERATED BY ORACLE XSL MAPPER 12.2.1.0.0(XSLT Build 151013.0700.0085) AT [WED NOV 13 11:17:16 IST 2019].-->

  </oracle-xsl-mapper:schema>

  <!--User Editing allowed BELOW this line - DO NOT DELETE THIS LINE-->

  <xsl:template match="/">

    <xsl:variable name="orientationStartDateTime" select="/ns0:process/ns0:orientationStartDateTime"/>

    <xsl:variable name="hour" select="xp20:hours-from-dateTime($orientationStartDateTime)"/>

    <xsl:variable name="amPm"

                  select="substring(xp20:format-dateTime($orientationStartDateTime, '[D] [MNn] [Y] [h]:[m01][PN,*-2]'),string-length(xp20:format-dateTime($orientationStartDateTime, '[D] [MNn] [Y] [h]:[m01][PN,*-2]'))-1)"/>

    <ns0:processResponse>

      <xsl:variable name="timeZoneHourAMPM">

<!-- Call template -->

        <xsl:call-template name="timeZoneHour">

          <xsl:with-param name="hour" select="$hour"/>

          <xsl:with-param name="startDateTime" select="$orientationStartDateTime"/>

          <xsl:with-param name="amPm" select="$amPm"/>

        </xsl:call-template>

      </xsl:variable>

      <ns0:timeZoneHourAMPM>

        <xsl:value-of select="$timeZoneHourAMPM"/>

      </ns0:timeZoneHourAMPM>

    </ns0:processResponse>

  </xsl:template>

<!--Called template definition-->

  <xsl:template name="timeZoneHour">

    <xsl:param name="hour"/>

    <xsl:param name="startDateTime"/>

    <xsl:param name="amPm"/>

    <xsl:variable name="minutes">

      <xsl:choose>

        <xsl:when test="xp20:minutes-from-dateTime($startDateTime) &lt; 10">

          <xsl:value-of select="concat(xp20:minutes-from-dateTime($startDateTime),'0')"/>

        </xsl:when>

        <xsl:otherwise>

          <xsl:value-of select="xp20:minutes-from-dateTime($startDateTime)"/>

        </xsl:otherwise>

      </xsl:choose>

    </xsl:variable>

    <xsl:choose>

      <xsl:when test="$hour > 12">

        <xsl:value-of select="concat($hour -12,':',$minutes,'PM')"/>

      </xsl:when>

      <xsl:when test="$hour = 0">

        <xsl:value-of select="concat(12,':',$minutes,'AM')"/>

      </xsl:when>

      <xsl:when test="$hour &lt; 0">

        <xsl:value-of select="concat($hour + 12,':',$minutes,'PM')"/>

      </xsl:when>

      <xsl:when test="$hour &lt; 12">

        <xsl:value-of select="concat($hour ,':',$minutes,'AM')"/>

      </xsl:when>

      <xsl:otherwise>

        <xsl:value-of select="concat($hour,':',$minutes,$amPm)"/>

      </xsl:otherwise>

    </xsl:choose>

  </xsl:template>

</xsl:stylesheet>

Deploy and test from EM console

Another call template sample code to get the following date format from Datetime format.
Input: orientationStartDateTime "2019-11-11T09:00:00
Output: Date: Monday, November 11th, 2019

Call Template:
<xsl:call-template name="date-format">
<xsl:with-param name="yyyy-mm-dd" select="concat(xp20:year-from-dateTime($OrientationStartDateTime),'-',xp20:month-from-dateTime($OrientationStartDateTime),'-',xp20:day-from-dateTime($OrientationStartDateTime))"/>
</xsl:call-template>
Called template:
<xsl:template name="date-format">
      <xsl:param name="yyyy-mm-dd"/>
      <xsl:variable name="yyyy" select="substring-before($yyyy-mm-dd, '-')"/>
      <xsl:variable name="mm-dd" select="substring-after($yyyy-mm-dd, '-')"/>
      <xsl:variable name="mm" select="substring-before($mm-dd, '-')"/>
      <xsl:variable name="dd" select="substring-after($mm-dd, '-')"/>
      <xsl:variable name="Y">
         <xsl:choose>
            <xsl:when test="$mm &lt; 3">
               <xsl:value-of select="$yyyy - 1"/>
            </xsl:when>
            <xsl:otherwise>
               <xsl:value-of select="$yyyy + 0"/>
            </xsl:otherwise>
         </xsl:choose>
      </xsl:variable>
      <xsl:variable name="y" select="$Y mod 100"/>
      <xsl:variable name="c" select="floor($Y div 100)"/>
      <xsl:variable name="d" select="$dd+0"/>
      <xsl:variable name="m">
         <xsl:choose>
            <xsl:when test="$mm &lt; 3">
               <xsl:value-of select="$mm + 12"/>
            </xsl:when>
            <xsl:otherwise>
               <xsl:value-of select="$mm + 0"/>
            </xsl:otherwise>
         </xsl:choose>
      </xsl:variable>
      <xsl:variable name="w" select="(($d + floor(($m + 1) * 2.6) + $y + floor($y div 4) + floor($c div 4) - $c * 2 - 1)+70) mod 7"/>
      <xsl:variable name="www">
         <xsl:choose>
            <xsl:when test="$w = 0">Sunday</xsl:when>
            <xsl:when test="$w = 1">Monday</xsl:when>
            <xsl:when test="$w = 2">Tuesday</xsl:when>
            <xsl:when test="$w = 3">Wednesday</xsl:when>
            <xsl:when test="$w = 4">Thursday</xsl:when>
            <xsl:when test="$w = 5">Friday</xsl:when>
            <xsl:when test="$w = 6">Saturday</xsl:when>
         </xsl:choose>
      </xsl:variable>
      <xsl:variable name="mmm">
         <xsl:choose>
            <xsl:when test="$mm =  1">January</xsl:when>
            <xsl:when test="$mm =  2">February</xsl:when>
            <xsl:when test="$mm =  3">March</xsl:when>
            <xsl:when test="$mm =  4">April</xsl:when>
            <xsl:when test="$mm =  5">May</xsl:when>
            <xsl:when test="$mm =  6">June</xsl:when>
            <xsl:when test="$mm =  7">July</xsl:when>
            <xsl:when test="$mm =  8">August</xsl:when>
            <xsl:when test="$mm =  9">September</xsl:when>
            <xsl:when test="$mm = 10">October</xsl:when>
            <xsl:when test="$mm = 11">November</xsl:when>
            <xsl:when test="$mm = 12">December</xsl:when>
         </xsl:choose>
      </xsl:variable>
      <xsl:variable name="th">
         <xsl:choose>
            <xsl:when test="$dd = 1">st</xsl:when>
            <xsl:when test="$dd = 21">st</xsl:when>
            <xsl:when test="$dd = 31">st</xsl:when>
            <xsl:when test="$dd = 2">nd</xsl:when>
            <xsl:when test="$dd = 22">nd</xsl:when>
            <xsl:when test="$dd = 3">rd</xsl:when>
            <xsl:when test="$dd = 23">rd</xsl:when>
            <xsl:otherwise>th</xsl:otherwise>
         </xsl:choose>
      </xsl:variable>
      <xsl:value-of select="concat($www, ', ', $mmm, ' ', $d,$th,', ',$yyyy)"/>
   </xsl:template>

12c SOA - Dehydrate activity in BPEL to commit transaction

By default, dehydration points are set on activities such as a receive, onMessage, onAlarm, and wait. The dehydrate activity enables you to explicitly specify a dehydration point. This activity acts as a dehydration point to automatically maintain long-running asynchronous processes and their current state information in a database while they wait for asynchronous callbacks. Storing the process in a database preserves the process and prevents any loss of state or reliability if a system shuts down or a network problem occurs. This feature increases both BPEL process reliability and scalability.

The bpelx:dehydrate extension implements dehydration. For BPEL projects that
support BPEL version 1.1, the syntax is as follows:
<bpelx:dehydrate name="DehydrateInstance"/>
For BPEL projects that support BPEL version 2.0, the syntax is as shown in the
following example:
<extensionActivity>
<bpelx:dehydrate name="DehydrateInstance"/>
</extensionActivity>

Use Case:
TBD

For a use case click here dehyrate

12c SOA - Oracle BPEL Dehydration

BPEL dehydration process:

• BPEL dehydration process is the action from the BPEL engine to compress and store the BPEL instances into the database. The incoming messages are stored in the database for processing later by worker threads.
• Storing the current status of the BPEL process(i.e. long running process, asynchronous process) into the database tables is known as dehydration.
• SOA_INFRA schema is the dehydration store which contains tables to hold the meta data of the process.

Why Dehydration

• Long running process or processes waiting for response consumes memory and CPU While waiting for the response the bpel engine can store the process, thus freeing up server resources.
• To increase both Reliability and Scalability of the BPEL process.
• You can also use it to support clustering and failover.
• Over the life cycle of the BPEL instance, the instance with the current state of execution may be saved in database.

Note: BPEL Activity is dehydrated immediately after execution and recorded in the dehydration store. It provides better failover protection, but may impact performance if the BPEL process accesses the dehydration store frequently.

Synchronous Process

• Process gets dehydrated only at the end of the process.
• Using Dehydrate activity we can explicitly dehydrate process state if required.

Asynchronous Process

• Automatically dehydrated the process based on the activities used.

When dehydration occurs:

When the BPEL instance encounters a mid-process breakpoint activity (not including the initial receive). The activities are used : 

• a mid-receive activities(without create instance). 
• Pick (onMessage & onAlarm) activity
• just before wait activity (depends on the duration)
• Dehydrate(11g) / Checkpoint(10g)
• Commit(Java embedded)
• a (implicit) transaction is committed

That is where an existing BPEL instance must wait for an event, which can be either a timer expiration or message arrival. When the event occurs (the alarm expires or the message arrives), the instance is loaded from the dehydration store and execution is resumed. This type of dehydration occurs only in durable processes, which have mid-process breakpoint activities. A transient process does not have any mid process breakpoint activities.

When the BPEL instance encounters a non-idempotent activity

When Oracle BPEL Server recovers after a crash, it retries the activities in the process instance. However, it should only retry the idempotent activities. Therefore, when Oracle BPEL Server encounters a non-idempotent activity, it dehydrates it. This enables Oracle BPEL Server to memorize that this activity was performed once and is not performed again when Oracle BPEL Server recovers from a crash.

Idempotent activities are those activities where the result is the same irrespective of no. of times you execute the process.

Repeated invocations have the same effect as one invocation.

E.g. Read only services, Receive activity

When RequiresNew BPEL transaction is completed or When the BPEL instance finishes

At the end of the BPEL process, Oracle BPEL Server saves the process instance to the dehydration store, unless you explicitly configure it not to do so. This happens to both durable and transient processes.

Note: A BPEL invoke activity is by default (true) an idempotent activity, meaning that the BPEL process does not dehydrate instances immediately after invoke activities. Therefore, if idempotent is set to true and Oracle BPEL Server fails right after an invoke activity executes, Oracle BPEL Server performs the invoke again after restarting. This is because no record exists that the invoke activity has executed. This property is applicable to both durable and transient processes. If idempotent is set to false, the invoke activity is dehydrated immediately after execution and recorded in the dehydration store. If Oracle BPEL Server then fails and is restarted, the invoke activity is not repeated, because Oracle BPEL Process Manager sees that the invoke already executed.

Idempotent vs non idempotent activities
Idempotent:Activities which can be retried are called idempotent activities. Examples are : assign activity, invoke activity etc. So if the BPEL process is recovered from the dehydration store , then these activities are retried again (idempotent activities are not stored in dehydration store if there is no dehydration activity like checkpoint() ) .
Non idempotent: Activities are those which causes the BPEL process to dehydration and so there state is saved into dehydration store. If the BPEL process is recovered from the dehydration store, these activities are not retried . Examples are : wait activity, mid point receive activity, pick activity , checkpoint() etc.

So when you specify the idempotent property as "false" in the partner link of a BPEL process , this becomes non idempotent and cause the BPEL process for dehydration and so a commit occurs . This is another way of ending the current transaction of a BPEL process and start a new one.

Types of BPEL Process
When and how dehydration occurs differ based on process types. Based on the dehydration we can categorize process in to 2 categories

Transient Process: Oracle BPEL server dehydrates the process instance only at the end of the process. If server crashes in middle of the running process instance, the instances will not be visible in EM
Durable Process: Oracle BPEL Server dehydrates the process instance in-flight at all midprocess breakpoint and non-idempotent activities, plus the end of the process. When the server crashes, this process instance appears in Oracle BPEL Control up to the last dehydration point (breakpoint activity) once the server restarts. If the server crashes before the process instance reaches the first midprocess breakpoint activity, the instance is not visible in Oracle BPEL Control after the server restarts.

Important Notes:

• Remember that theses dehydration statement must be avoided in synchronous BPEL process.
• Idempotence is a mathematical term that basically means that calling a function multiple times doesn’t change the result for example f(f(x))=f(x).
• What does it mean for messaging service system ? If a service receives the same message again, it should be able to handle it without changing the state of the system. For example; in a bank scenario you wouldn’t want that withdraw message to be processed more than once !
• An idempotent activity in BPEL (for example, an assign activity or an invoke activity) is an activity that can be retried
• To ensure data consistency, the dehydration database is done using the same transaction context in which the BPEL process is executed. However, BPEL engine use a separate transaction context for the audit logging information, which aids (a lot) for debugging failed instance.

Skipping dehydration

• Skipping dehydration will increase performance with a cost of auditing.
• By Default, all BPEL processes are dehydrated regardless of whether they are Synchronous or Asynchronous process.
• For Synchronous processes that do not need to be durable, you can turn off the dehydration mechanism by setting the following properties at process or engine level:

1. Set inMemoryOptimization to true.
2. Set completionPersistPolicy property to faulted or Off.

• Asynchronous process invocation messages are always saved to the dehydration store.
• Durable process are always dehydrated regardless of the settings of the persistence properties.

Dehydration Tables
Cube_Instance: Stores the information about the composite instance that gets created.
Cube_scope: Stores information about the scopes and variables declared and used.
DLV_Message: All the incoming payload details are stored.
Invoke_Message: All the outgoing message payload details are stored.
Audit_Trail: Used to store information of the xml that is rendered in EM console.