SOA – LUXOUG – LUXEMBOURG ORACLE USERS GROUP

SOA

MDS-00054: Undeploying SOA Composite when Soa-Infra is Down

Category: Middleware Author: Cassio Mariani Date: 5 years ago Comments: 0

MDS-00054: Undeploying SOA Composite when Soa-Infra is Down

Goal

Undeploying SOA Composite while soa-infra is down.

Mainly this task is required when starting soa server, soa-infra application wont come up due to corrupt composite which stops the soa-infra to be in active state. The solution also applies in the case where the server itself is failing to come up / stay up due to a bad deployment.

Fix

Check the soa logs and determine which composite is causing the problem and then follow the below process to Undeploy SOA composite by editing deployed-composites.xml

1. Download and copy the ShareSoaInfraPartition.ear file to $MIDDLEWARE_HOME/oracle_common/common/bin

2. cd to $MIDDLEWARE_HOME/oracle_common/common/bin and run wlst.sh

3.

connect()

provide username, password and server URL

4. run the below command to deploy ShareSoaInfraPartition.ear

deploy(‘ShareSoaInfraPartition’,’ShareSoaInfraPartition.ear’,upload=’true’)

5. Now run the below command by changing the “toLocation” (‘/fmw12c/fmw12213/middleware’ is some location path on SOA machine)

exportMetadata(application=’ShareSoaInfraPartition’,server=’AdminServer’,toLocation=’/fmw12c/fmw12213/middleware’,docs=’/deployed-composites/deployed-composites.xml’)

6. A deployed-composites folder will be created at “toLocation” path with deployed-composites.xml in it

7. Delete the composite which is causing the problem and save the file

For example i am MediatorTest composite like below

<composite-series name=”default/MediatorTest” default=”default/MediatorTest!1.0″>
<composite-revision dn=”default/MediatorTest!1.0″ state=”on” mode=”active” location=”dc/soa_58b98be8-9ec8-41af-bb83-590f6004d1aa”>
<composite dn=”default/MediatorTest!1.0*soa_58b98be8-9ec8-41af-bb83-590f6004d1aa” deployedTime=”2019-03-17T09:01:54.750+05:30″/>

8. Now run the below command by changing the “fromLocation” (this should be the same location as previous)

importMetadata(application=’ShareSoaInfraPartition’,server=’AdminServer’,fromLocation=’/fmw12c/fmw12213/middleware’,docs=’/deployed-composites/deployed-composites.xml’)

9. Now bounce your server and the composite will not be deployed by SOA when it comes up and hence that should bring your soa-infra up.

Download ShareSoaInfraPartition from here: (Need an Oracle valid Account) – Click Here

All the best,

Cassio Mariani

INCREASING THE PERFORMANCE OF EM CONSOLE IN ORACLE SOA SUITE 12C

Category: Middleware Author: Cassio Mariani Date: 5 years ago Comments: 0

INCREASING THE PERFORMANCE OF EM CONSOLE IN ORACLE
SOA SUITE 12C

EM console is very slow when accessing to view the composite/component details or the instance details.

We can try to improve the performance by little by following the below steps.

Login to the Oracle SOA Suite 12c EM Console

Right Click on SOA-INFRA and go to SOA Administration->Common properties

Set the Data Display Options as shown below.

Select the option “Disable fetching of instance and fault count metrics. Each metric can still be retrieved on demand”.

Set the Duration Details to 1 hour (based on your requirement) as shown below.

This will enable to fetch the instance and fault count metrics based on the demand also the default search criteria will display the last one hour data, this will improve the performance of the em console.

Enable fmwctl discovery cache:

Logging into Enterprise Manager Fusion Middleware Control 12c (fmwctl) takes a long time. Sometimes as long as 45-60 seconds. This is often viewed as slow response time, performance or hanging issues, fmwctl discovery is always performed as part of login.

For installations with thousands of targets, fmwctl discovery may take 45-60 seconds. This delay is expected because EM discovery mbeans need to be invoked for every target.

Solution is to cache the discovery results in the servlet context and use it for subsequent logins. This discovery result will be shared by all the fmwctl users. This will still require the entire discovery to be done at least once.

Follow the metalink note 1423893.1 to enable the discovery caching.

If the caching is enabled, fmwctl will use the cached discovery results and login to the em console will be fast.The default setting is “not use the cached results”.