EM Cannot Show Application Status After Restarting Admin Server On BPM Cluster

(Doc ID 1640923.1)

Last updated on JULY 25, 2017

Applies to:

Oracle Business Process Management Suite - Version to [Release 11gR1]
Information in this document applies to any platform.


 A BPM cluster environment is created as per the Enterprise Deployment Guide.

The Admin server and BPM servers are started in different domain folders or started on different physical machines.

After starting admin server and BPM managed servers, everything works well, however these situations might be encountered:

Symptoms 1

Keep BPM servers running, restart admin server only.
User cannot get deployed BPM application status via EM console, and got the following trace in emoms.log.

Symptoms 2

Inconsistent system-jazn-data.xml file in the aserver domain folder (/home/soa/user_projects/domains/aserver/config/fmwconfig/system-jazn-data.xml file)
and in the managed server domain folder


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms