Monday, September 24, 2012

Steps To ensure WF_DEFERRED AGENT LISTENER to be UP and RUNNING on Target Instance!


Use the following steps to ensure that the WF_Deferred Agent Listener is running on the target database.

1.      Log in to Oracle Applications with the System Administrator responsibility.
2.      On the Oracle Applications home page, select the Workflow Administrator Web Applications responsibility. Select Oracle Applications Manager > Workflow Manager from the menu.
3.      On the Applications Manager page, click the Agent Listeners icon. The Service Components page appears, containing a list of the installed agent listeners.
4.      In case if Agent Listener is down which could be because any service component failing and giving status “STOPPED WITH ERROR”, check for Workflow Agent Listener Service
5.      Workflow Agent Listener Service contains the service instances which are Workflow Mailer Service, Workflow Document Web Services Service, Workflow Agent Listener Service in either deactivated, verifying or aborted status.Restart ALL to activate them.
6.      In case a message that "Internal manager is down" is shown on restarting these instances ,check for the Internal Manager configuration .Login as sysadmin goto System Administrator>Concurrent:Manager>Administer. For the Internal Manager to be up and running,ACTUAL COLUMN must not be 0.
7.      If Actual column is 0 then Concurrent Manager is not running
8.      Ideally Concurrent Manger needs to be restarted and reconfigured so do the following:
         1.Shutdown the Concurrent Manager
    Goto the folder containing adcmct.cmd(windows)  or adcmct.sh script(on linux)

$Oracle_home\install\EBS\12i\inst\apps\VIS_xyz-ora\admin\scripts>adcmctl stop apps/apps
->We can manually kill processes FNDLIBR.EXE
->It can be stopped using CONSCUB utility as well
CONCSUB apps/apps SYSADMIN 'System Administrator' SYSADMIN WAIT=Y CONCURRENT FND FNDSM START=<start time> Y 0 0
9.      GOTO Services.msc and Enable the appropriate service OracleConcMgrVIS_xyz-ora.

MEDIATOR Vs BPEL Vs OSB


Differences
MEDIATOR/ESB
BPEL
OSB
Routing & mediation
Process Orchestration
Service virtualization
Used with SOA suite
Used with SOA Suite
Can be independently used without SOA suite
Development through jdeveloper IDE
Development through jdeveloper IDE
Development through Eclipse IDE or Web console
Stateless Messaging
Primarily for stateful and long running processes
Stateless messaging.It can b synchronous/asynchronous.
Intra-composite mediation to connect components within a given composite


Inter-composite mediation, that is to say that it connects different
composites together and while doing that it even does service virtualization, protocol translation, service pooling,message throttling
Not present
Instance Monitoring present
Not present
Value Mapping and cross reference tables for supporting canonical datamodels
Integration of Rules Engine and Human Workflow
Value Mapping and cross reference tables for supporting canonical datamodels
Implementation of VETRO pattern
->Validate
->Enrich
->Transform
->Route
->Operate
Implementation of composite services
Includes VETRO pattern apart from extended functionality for enterprise-wide integration like
->Message throttling
->Service Pooling
->Reliable Messaging
->Split-Join
Message Transformation with XSLT
Message Transformation with XSLT
Message Transformation over Xquery and with XSLT
Can be used and deployed as a SCA component
Can be used and deployed as a SCA component
OSB specific deployment. Not yet integrated with SCA

SIMILARITIES
1.All of them provide XA Support
2.Message Filter and Message Validation
3.Asynchronous Messaging
4.Message Transformation using XSLT
5.Have Adapter framework
6.Message Routing

SCA?


·         Service component architecture.It must be
                        ->Language neutral
                        ->Component model
                        ->Assembly model
·         http://www.OSOA.org (http://www.oasis-opencsa.org/)

SCA Terminology
Composite :Deployment Unit
Service :Entry-point into composite
Component: Provides Logic
Reference:  refers to external services
Wire :connects services, components and references

Integration Challenges


A lasting integration solution should address the top integration challenges and offer
• Better compatibility between applications
• Agility i.e the ability to adapt—the essential attitude to embrace change
• Integrated business processes that give you visibility into information across multiple systems
• Integrations that are easy to maintain and less risky to evolve, and that doesn’t break with upgrades
• Support for open industry standards, along with product functionality, operational (administration) effort, and maturity
• More-flexible configurability with less customization
• Lower ongoing maintenance and support costs
• Speed deployment by reusing components
• More responsiveness & faster service

Organizations adopting SOA will typically carry out frequent changes in response to business requirements. These changes can consist of reorganizing business processes, assembling new applications from existing business services or rewiring existing business services or applications, changing the logic of (potentially heavily reused) elementary services