1. Oracle Migration Tool On Demand Guide
  2. Elements and Sections in the Integration Event Queue XML Output File

Elements and Sections in the Integration Event Queue XML Output File

The following table describes the elements and sections in the integration event queue XML output file.

Table Elements and Sections in the Integration Event Queue XML File

Description Element or Section

The <IntegrationEventQueue> section contains all of the information for a single integration event queue.

 
<data:IntegrationEventQueue>
. . .
</data:IntegrationEventQueue>

<QueueName> contains the name of the integration event queue.

 
<data:IntegrationEventQueue>
  <data:QueueName>TestQueue</data:QueueName>
. . .
</data:IntegrationEventQueue>

<Description> contains the description of the integration event queue.

 
<data:IntegrationEventQueue>
. . .
  <data:Description>MyTestQueue
  </data:Description>
. . .
</data:IntegrationEventQueue>

<Disabled> specifies whether the integration event queue is disabled (true) or is not disabled (false).

 
<data:IntegrationEventQueue>
. . .
  <data:Disabled>false</data:Disabled>
. . .
</data:IntegrationEventQueue>

<Created> contains the user name of the user who created the integration event queue, with the date and time that the queue was created. This element is read-only and is ignored for upsert requests.

 
<data:IntegrationEventQueue>
. . .
  <data:Created>SysAdmin, 05/21/2017 
   04:40:52</data:Created>
. . .
</data:IntegrationEventQueue>

<Modified> contains the user name of the user who last modified the integration event queue configuration, with the date and time that the queue configuration was last modified. This element is read-only and is ignored for upsert requests.

 
<data:IntegrationEventQueue>
. . .
  <data:Modified>SysAdmin, 06/19/2017 
   06:26:52</data:Modified>
. . .
</data:IntegrationEventQueue>

<FileLimit> shows the total number of events that your company can store for all queues. If the combined size of the existing queues matches this number, then you cannot create a new queue. This element is read-only and is ignored for upsert requests.

 
<data:IntegrationEventQueue>
. . .
  <data:FileLimit>500</data:FileLimit>
. . .
</data:IntegrationEventQueue>

<UnassignedQueueCapacity> shows the remaining capacity for all integration event queues. This element is read-only and is ignored for upsert requests.

 
<data:IntegrationEventQueue>
. . .
  <data:UnassignedQueueCapacity>70
  </data:UnassignedQueueCapacity>
 . .
</data:IntegrationEventQueue>

<QueueSize> specifies the size of the queue. When you create a new queue, the size of the queue cannot exceed the remaining capacity, which is shown in the <UnassignedQueueCapacity> element.

 
<data:IntegrationEventQueue>
. . .
  <data:QueueSize>10</data:QueueSize>
. . .
</data:IntegrationEventQueue>

<NumberOfTransactions> shows the number of transactions currently in the queue. This element is read-only and is ignored for upsert requests.

Note: For information about clearing integration events from queues, see About Clearing Transactions from Integration Event Queues. 
<data:IntegrationEventQueue>
. . .
  <data:NumberOfTransactions>0
  </data:NumberOfTransactions>
. . .
</data:IntegrationEventQueue>

<NotificationEmailAddress> is the email address to which a warning email is to be sent when the queue is full or when the queue reaches a certain size, if a warning email is to be sent.

 
<data:IntegrationEventQueue>
. . .
  <data:NotificationEmailAddress>
  jane.doe@company.com
  </data:NotificationEmailAddress>
. . .
</data:IntegrationEventQueue>

<WarningMailQueueSize> specifies the size that the queue is allowed to reach before a warning email is sent to the address specified in the <NotificationEmailAddress> element.

 
<data:IntegrationEventQueue>
. . .
  <data:WarningMailQueueSize>5
  </data:WarningMailQueueSize>
. . .
</data:IntegrationEventQueue>

<TimeZone> specifies how the dates and times are recorded in the integration events that are created using the Web Services v1.0 Schema and written to this queue. The valid values are:

  • UTC Format. If this value is specified, then the date and time in the GMT time zone are recorded, in the format specified by the W3C standard for Coordinated Universal Time (UTC), as follows:

    YYYY-MM-DDTHH:MM:SSZ

    For example, 2017-06-12T09:44:15Z, which corresponds to June 12th 2017, 9:44:15 GMT.

    Note: Fractions of seconds are not recorded.

  • UTC. If this value is specified, then the date and time in the GMT time zone are recorded, in the following format:

    MM/DD/YYYY HH:MM:SS

    For example, 06/12/2017 09:44:15, which corresponds to June 12th 2017, 9:44:15 GMT.

  • User Time Zone. If this value is specified, then the date and time in the time zone of the user who updated the record are recorded, in the following format:

    MM/DD/YYYY HH:MM:SS

    For example, 06/12/2017 09:44:15, which corresponds to June 12th 2017, 9:44:15, in the user’s time zone.

    Note: You can set the Time Zone field for the Default Queue only. All other queues inherit the setting that is selected for the Default Queue. 
<data:IntegrationEventQueue>
. . .
  <data:TimeZone>User Time Zone</data:TimeZone>
</data:IntegrationEventQueue>

<PicklistFormat> specifies the format for recording picklist field values in the integration events, as follows:

  • LIC. If this value is specified, then the picklist values are recorded as language-independent code (LIC) values.

    Note: The LIC values in picklists are usually the same as the values in the English-United States (ENU) locale.

  • User Language. If this value is specified, then the picklist values are recorded in the language of the user whose action causes the integration event to be created.

    Note: After a queue is created, the Picklist Format field becomes read-only and you cannot change it, either in the UI or through an upsert operation. If you want to change the picklist format of an integration event queue, then contact Oracle CRM On Demand Customer Care, and ask them to change it for you. 
<data:IntegrationEventQueue>
. . .
  <data:PicklistFormat>User Language
  </data:PicklistFormat>
. . .
</data:IntegrationEventQueue>

<W3CFormat> specifies the format in which the field values are recorded in the integration events that are created using the Web Services v2.0 Schema and written to this queue, as follows:

  • If this element is set to true, then the values in all fields are recorded in the format specified by the W3C for Web Services v2.0 Schema integration events.
  • If this element is set to false, then the values in Date and Boolean field types are recorded in the format that was used in releases earlier than Release 41 of Oracle CRM On Demand. The values in all other fields are recorded in the format specified by the W3C for Web Services v2.0 Schema integration events.

The default value is false. If you set the value to true when inserting or updating the integration event queue data, then after the queue is created or updated, the <W3CFormat> field becomes read-only and it cannot be changed.

 
<data:IntegrationEventQueue>
. . .
  <data:W3CFormat>false</data:W3CFormat>
. . .
</data:IntegrationEventQueue>