×

IDMWORKS Blog

SOA-INFRA In A Warning State After BP06 Upgrade


If you upgrade Oracle Identity Manager 11gR2 to BP06 you may find that the soa-infra deployment on your SOA managed servers to be in a WARNING state.

SOA Warning

Further investigation into the deployment monitoring and you find that CaseEventMDB is not connected to the Messaging System.

CaseEventMDB

What has happened is that during the upgrade process certain JMS setting were not applied and need to be recreated.  

Steps To Resolve This

  1. First, login to Weblogic Admin Console and stop all SOA managed servers.



Create New JMS File Stores

  1. We first need to create a directory for each SOA managed server for the file stores on every SOA machine inside the SOA cluster config. This directory is ideally called “PS6SOAJMSFileStore_[SoaServerNumber]”. We have two SOA managed servers so our directories are as follows, yours may differ:

    /u01/app/oracle/admin/cluster_soa/PS6SOAJMSFileStore_1
    /u01/app/oracle/admin/cluster_soa/PS6SOAJMSFileStore_2

  2. In the Weblogic Admin Console go to the DOMAIN -> Services -> Persistent Stores and create a new Create a new Persistent Store that matches your directory names and targeted to its respective managed server. In our case:

    Persistent Store:  PS6SOAJMSFileStore_1
    Target: wls_soa1
    Directory: /u01/app/oracle/admin/cluster_soa/PS6SOAJMSFileStore_1

    Persistent Store: PS6SOAJMSFileStore_2
    Target: wls_soa2
    Directory: /u01/app/oracle/admin/cluster_soa/PS6SOAJMSFileStore_2

    You can leave the remaining settings as the default.

  3. Activate Changes



Create New JMS Servers

  1. In the Weblogic Admin Console go to DOMAIN -> Services -> Messaging -> JMS Servers
  2. Create new JMS Servers targeted to each of the SOA managed servers with their respective Persistent Store. Ours is as follows:

    JMS Server: PS6SOAJMSServer_1
    Persistent Store: PS6SOAJMSFileStore_1
    Target: wls_soa1

    Create a new JMS Server called: PS6SOAJMSServer_2
    Persistent Store: PS6SOAJMSFileStore_2
    Target: wls_soa2

    You can leave the remaining settings as the default.

  3. Activate Changes



Create New JMS Module

  1. In the Weblogic Admin Console go to [DOMAIN] -> Services -> Messaging -> JMS Modules
  2. Create a new JMS Module called: PS6SOAJMSModule
    Descriptor Filename: jms/soajmsmodule-ps6-jms.xml
    Targets: cluster_soa
    Leave the rest of the settings as default
  3. Under the new PS6SOAJMSModule click the Subdeployments tab
    1. Create a new Subdeployment called: PS6SOASubDeployment
      1. Target each of the new JMS Servers: PS6SOAJMSServer_1, PS6SOAJMSServer_2
        Leave the rest of the settings as default
    2. Return to the Configuration tab for PS6SOAJMSModule
    3. Create a new Connection Factory Resource called: CaseEventConnectionFactory
      JNDI Name: jms/bpm/CaseEventConnectionFactory
      Target: cluster_soa
      Leave the rest of the settings as default
  4. Create a New Distributed Queue called: CaseEventQueue
    JNDI Name: jms/bpm/CaseEventQueue
    Target:

    1. Go to Advanced Targeting and Select the Subdeployment: PS6SOASubDeployment
    2. Make sure PS6SOAJMSServer_1 and PS6SOAJMSServer_2 are selected
    3. Leave the rest of the settings as default
  1. Activate Changes

Redeploy SOA-INFRA

  1. Login to Weblogic Admin Console and go to the [DOMAIN] -> Deployments
  2. Select the checkbox next to soa-infra under Deployments and click the Update button at the top of the table
  3. Leave settings as is and Click finish
  4. Activate the changes



Restart Admin Server
Finally. Restart the Admin Server and all SOA Managed servers and SOA-INFRA will no longer be in a WARNING state!

Questions, comments or concerns? Feel free to reach out to us below, or email us at IDMWORKS to learn more about how you can protect your organization and customers.

Leave a Reply

Your email address will not be published. Required fields are marked *