Last updated on JULY 22, 2016
Applies to:Siebel Mobile Applications - Version 220.127.116.11 [IP2014] and later
Siebel Remote - Version 18.104.22.168 [IP2014] and later
Information in this document applies to any platform.
Siebel Remote / Mobile Disconnected - on version: 22.214.171.124 [IP2014]
Since IP2014, TxnProc and TxnRoute components are part of MobileSync compgrp - and these comps are used and required for both Remote users and Disconnected Mobile users to process and route txns to offline.
In such environment, where there were some servers for running the comps to support Disconnected Mobile users (running on Windows OS) and other for Remote users (on Unix - AIX) along with other AIX servers in the Enterprise, at some point a significant transactions backlog was observed.
No matter if the Txn* comps are used to support Remote or Disconnected Mobile users, the txns should be processed and routed properly - and backlogs should not accumulate in normal operating conditions.
The issue has the following business impact:
Due to this issue, Mobile users in this case would receive data changes from server with big delays.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms