Weblogic and SOA Administrator

Friday, 30 September 2016

Backing up the MDS Repository Artifacts - Oracle SOA Suite 11g

In Oracle SOA Suite 11g, all the common artifacts , the deployed composites and the common configurations are stored in the MDS database schema. Sometimes there is a possibility of MDS schema getting corrupted (the best example is the composites getting corrupted frequently)those scenario we will not be able to bring up the soa-infra and also we may loose all the deployments.

Backing up the MDS artifacts is the the solution for these kind of issues.

In this post i will be explaining some of the different options to back up the MDS artifacts.

The best approach is do a full back up of MDS repository schema using database backup utilities(dbexp).The backup can be restored if there is any issue with the MDS schema.

EM console - MDS configuration Page :
Right click on soa-infra and click on Administration and MDS Configuration.
Click Export on MDS Configuration page.

This will export the MDS artifacts to local machine as zip file.

WLST script:

The MDS artifacts also can be exported through WLST script, the exportMetaData command will help us to export the MDS artifacts.

Steps:-
Login to SOA server through putty
Execute $ORACLE_HOME/common/bin/wlst.sh then execute connect() and provide the server details.

After successful connection to ServerConfig execute the below command - Change the export path accordingly.

exportMetadata(application='soa-infra', server='AdminServer',toLocation='/reuters/oracle/as01/mds/soa_mds.jar',docs='/**')

This will export the MDS artifacts as jar file to the specified location.

Increasing the performance of EM console in Oracle SOA Suite 11g

Increasing the performance of EM console in Oracle SOA Suite 11g - Part1

Increasing the performance of EM console in Oracle SOA Suite 11g - Part1

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.

1. Login to the Oracle SOA Suite 11g EM Console

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

3. 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 11g (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"

Friday, April 18, 2014

Increasing the performance of EM console in Oracle SOA Suite 11g - Part2

The post http://www.albinsblog.com/2012/04/increasing-performance-of-em-console-in.html#.U1D_JvmukdQ explains some of the steps to improve the EM console performance in Oracle SOA Suite 11g .

Here some more additional steps to improve the EM console performance.

The EM conolse uses the Dynamic Monitoring System(DMS) module to collect the metrics from all the DMS enabled targets.
If the frequency of the DMS collection is to fast then the EM console will become slow.

To increase the frequency of the DMS collection, increase the value of intervalSeconds in the $MIDDLEWARE_HOME/oracle_common/modules/oracle.dms_11.1.1/server_config.xml file to higher value.

to

Target the DMS application only to the SOA servers.

Creating a Trust Keystore Using the keytool Utility for weblogic server

Follow these steps to create the Trust Keystore in weblogic server.

Copy the standard java keystore to create the new trust keystore since it already contains most of the root CA certificates needed. Oracle does not recommend modifying the standard Java trust keystore directly. Copy the standard Java keystore CA certificates located under the $WLSHOME/server/lib directory to the same directory as the certificates.

For example:

cp $WLSHOME/server/lib/cacerts $WLSDOMAIN/certs/appTrustKeyStore.jks

The default password for the standard Java keystore is changeit. Oracle recommends always changing the default password. Use the keytool utility to do this. The syntax is:

keytool -storepasswd -new -keystore -storepass

For example:

cd $WLSDOMAIN/certs

keytool -storepasswd -new welcome1 -keystore appTrustKeyStore.jks -storepass changeit

The CA certificate CertGenCA.der is used to sign all certificates generated by the utils CertGen tool and is located at $WLSHOME/server/lib directory. This CA certificate must be imported into the appTrustKeyStore.jks using the keytool utility. The syntax is:

keytool -import -v -noprompt -trustcacerts -alias -file -keystore -storepass

For example:

keytool -import -v -noprompt -trustcacerts -alias clientCACert –file $WLSHOME/server/lib/CertGenCA.der -keystore appTrustKeyStore.jks –storepass welcome1

Thursday, February 19, 2015

The Admin console is not up/accessible – Oracle SOA Suite

We were facing a strange issue in our Oracle SOA Suite production server in Solaris, we could not able to access the admin console even though the server is started properly and there is no error in the log file.

We were able to telnet the admin server listen address from Admin server node but not able to do it from other nodes.

The root cause of the issue is with Gateway server, the admin server listen address is not listed on the Gateway - the gateway server is not online (the servers listen address is configured in Gateway).

After Solaris admin team made the Gateway server online, we were able to see the admin server listen address listed on the gateway.

After restarting the admin server we were able to access the console page.

The following command can be used for checking the Gateway server status

netstat –r

java.net.ConnectException,Bootstrap to server failed while deploying the compoite - Orace SOA Suite

Sometimes we may receive the following exception while deploying the composite to Oracle SOA Suite server using even though the sever is running fine and reachable.

oracle.rc.asadapter.connection.ConnectionException
at oracle.rc.asadapter.weblogic.connection.spi.Weblogic10JndiProvider.getPresentation(Weblogic10JndiProvider.java:86)

Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://127.0.0.1:8000: Bootstrap to localhost/127.0.0.1:8000 failed. It is likely that the remote side declared peer gone on this JVM]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)

Caused by: java.net.ConnectException: t3://127.0.0.1:8000: Bootstrap to localhost/127.0.0.1:8000 failed. It is likely that the remote side declared peer gone on this JVM

Caused by: java.rmi.ConnectException: Bootstrap to localhost/127.0.0.1:8000 failed. It is likely that the remote side declared peer gone on this JVM
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:334)

This issue can be resolved by configuring valid machine IP or complete name of the machines, including the domain extension as listen address in weblogic server.

On client side, enter the host entry for the server in the hosts file -C:\Windows\System32\drivers\etc

SOA-INFRA Application is in unknown Type - Oracle SOA Suite 11g

SOA-INFRA Application is in unknown Type - Oracle SOA Suite 11g:

I was facing a strange issue,the Type of the soa-infra application was unknown but the state and the health of the application is looking fine(Active and OK) in admin console.

Because of this the SOA node is not displayed in the em console.

Tried restarting the server without any luck and also updated(redeployed) the soa-infra application but still the type of the application is unknown.

I could not able to find any exception related to this issue in the log files and also there is no issue related to the database schema's.

Followed the below steps to resolve this issue.

Delete the soa-infra application from the admin console deployments.

Install the soa-infra application(soa-infra-wls.ear) from the location SOA_HOME\soa\applications as Enterprise Application.

Change the application name as soa-infra.

Ignore the errors displayed while installing the application, after the successful installation the application will be in Failed state but the Type will be properly displayed as Enterprise Application.

Update(redeploy) the application by changing the Plan file path

Ignore the errors displayed while redeploying the application, once the application redeployed successfully then delete the tmp and cache folders from the server and restart the server.

Now the state, health and the Type of the soa-infra application is displayed properly and also the SOA folder is visible in the EM console.

Installing the patches to weblogic server using Oracle Smart Update

Installing the patches to weblogic server using Oracle Smart Update:

Oracle Smart Update tool help us to apply and manage the patches for weblogic server.

As of Smart Update 3.3.0, the Get Patches tab has been removed, and you can no longer use Smart Update to download patches, service packs, maintenance packs, or version upgrades. You must first download the appropriate patch or patches directly from My Oracle Support. Once downloaded, you can use Smart Update to apply the patches.

Smart Update 3.3.0 no longer prompts you to register for security updates from Oracle Configuration Management (OCM).

The version can be verified from Help -> About.

This blog will explain the steps to install the patches to a weblogic server using Oracle Smart Update.

Download the patch through metalink using the patch id or bug no.
Uncompress patch zip file to $MWHOME/utills/bsu/cache_dir (If the cache_dir folder is not available then create the same)

Launch the Oracle Smart Update Tool (bsu.cmd) from $MWHOME\utils\bsu, this will list all the applied patchs and all those patches that are ready for installation.

Click on Apply to install the corresponding patch, the tool verify the environment for the conflicts.

Click on OK once the patch validation is completed.Once the patch is applied successfully the patch will be listed under applied patches

Restart the servers

· Oracle WebLogic Server Patch Set Update 10.3.6.0.160419 README

· =========================================================

· This README provides information about how to apply Oracle WebLogic Server

· Patch Set Update 10.3.6.0.160419. It also provides information about reverting to

· the original version.

· Released: April, 2016

· Smart Update Details of Oracle WebLogic Server Patch Set Update 10.3.6.0.160419

· --------------------------------------------------------------------------

· PATCH_ID - DEM4

· Patch number - 22505423

· Preparing to Install Oracle WebLogic Server Patch Set Update 10.3.6.0.160419

· -----------------------------------------------------------------------

· - WebLogic Server Patch Set Update (PSU) can be applied on a per-domain basis

· (or on a more fine-grained basis), Oracle recommends that PSU be applied on an installation-wide basis.

· PSU applied to a WebLogic Server installation using this recommended practice

· affect all domains and servers sharing that installation.

· - Login as same "user" with which the component being patched is installed.

· - Stop all WebLogic servers.

· - Remove any previously applied WebLogic Server Patch Set Update and associated overlay patches

· Installing Oracle WebLogic Server Patch Set Update 10.3.6.0.160419

· -------------------------------------------------------------

· - unzip p22505423_1036_Generic.zip to {MW_HOME}/utils/bsu/cache_dir or any local directory

· Note: You must make sure that the target directory for unzip has required write and executable permissions

· for "user" with which the component being patched is installed.

· - Navigate to the {MW_HOME}/utils/bsu directory.

· - Execute bsu.sh -install -patch_download_dir={MW_HOME}/utils/bsu/cache_dir -patchlist={PATCH_ID} -prod_dir={MW_HOME}/{WL_HOME}

· Where, WL_HOME is the path of the WebLogic home

· Reference: BSU Command line interface

· http://docs.oracle.com/cd/E14759_01/doc.32/e14143/commands.htm

· Post-Installation Instructions

· ------------------------------

· a) Restart all WebLogic servers.

· b) The following command is a simple way to determine the application of WebLogic Server PSU.

· $ . $WL_HOME/server/bin/setWLSEnv.sh

· $ java weblogic.version

· In the following example output, 10.3.6.0.160419 is the installed WebLogic Server PSU.

· WebLogic Server 10.3.6.0.160419 PSU Patch for BUG22505423

· Uninstalling Oracle WebLogic Server Patch Set Update 10.3.6.0.160419

· ---------------------------------------------------------------

· - Stop all WebLogic Servers

· - Navigate to the {MW_HOME}/utils/bsu directory.

· - Execute bsu.sh -remove -patchlist={PATCH_ID} -prod_dir={MW_HOME}/{WL_HOME}

· Post-Uninstallation Instructions

· --------------------------------

· a) Restart all WebLogic Servers.

· Oracle recommends that you see following key notes

· --------------------------------------------------

· - My Oracle Support NOTE: 1306505.1 Announcing Oracle WebLogic Server PSUs (Patch Set Updates)

· https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1306505.1

· - My Oracle Support NOTE: 1470197.1 Master Note on WebLogic Server Patch Set Updates (PSUs)

· https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1470197.1

· - My Oracle Support NOTE: 1471192.1 - Replacement Patches for WebLogic Server PSU Conflict Resolution

· https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1471192.1

· - SSL Authentication Problem Using WebLogic 10.3.6 and 12.1.1 With JDK1.7.0_40 or Higher

· https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1607170.1

· - Smart Update Applying Patches to Oracle WebLogic Server

· http://docs.oracle.com/cd/E14759_01/doc.32/e14143/intro.htm

· ==============================

· Interim Patch for Bug: 13801175

· ==============================

· Date: Tue Feb 25 18:03:46 2014

· ---------------------------------

· Platform Patch for : Generic

· Product Patched : Oracle SOA Suite

· Product Version : 11.1.1.6.0 + patch 16702086(mandatory)

· Auto Enabled : No

· This document describes how to install the interim patch for

· bug # 13801175. It includes the following sections:

· Section 1, "Prerequisites"

· Section 2, "Pre-Installation Instructions"

· Section 3, "Installation Instructions"

· Section 4, "Post-Installation Instructions"

· Section 5, "Deinstallation Instructions"

· Section 6, "Post Deinstallation Instructions"

· Section 7, "Bugs Fixed by This Patch"

· 1 Prerequisites

· ----------------

· Ensure that you meet the following requirements before you install or

· deinstall the patch:

· 1. Before applying the non-mandatory patches, ensure that you have the

· exact symptoms described in the bug.

· 2. Review and download the latest version of OPatch 11.1.x via Bug 6880880.

· (OPatch version 11.1.0.8.2 or higher)

· a. Oracle recommends that all customers be on the latest version of OPatch.

· Review the My Oracle Support note 224346.1, and follow the instructions

· to update to the latest version if needed. Click the following link to

· view the note:

· Note 224346.1 - Opatch - Where Can I Find the Latest Version of Opatch?

· https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=224346.1

· b. For FMW Opatch usage, refer to the document at:

· http://download.oracle.com/docs/cd/E21764_01/doc.1111/e16793/opatch.htm

· 3. Verify the OUI Inventory.

· OPatch needs access to a valid OUI inventory to apply patches.

· Validate the OUI inventory with the following commands:

· $ opatch lsinventory

· If the command errors out, contact Oracle Support and work to validate

· and verify the inventory setup before proceeding.

· 4. Confirm the executables appear in your system PATH.

· The patching process will use the unzip and the OPatch executables. After

· setting the ORACLE_HOME environment, confirm if the following executables

· exist, before proceeding to the next step:

· - which opatch

· - which unzip

· If either of these executables do not show in the PATH, correct the

· problem before proceeding.

· 5. Create a location for storing the unzipped patch. This location

· will be referred to later in the document as PATCH_TOP.

· NOTE: On WINDOWS, the prefrred location is the drive root directory.

· For example, "C:\PATCH_TOP" and avoid choosing locations like,

· "C:\Documents and Settings\username\PATCH_TOP".

· This is necessary due to the 256 characters limitation on windows

· platform.

· 2 Pre-Installation Instructions

· -------------------------------

· - - Set the ORACLE_HOME environment variable to SOA Home,

· for example "[MW_HOME]/Oracle_SOA1" directory.

· 3 Installation Instructions

· ---------------------------

· 1. Unzip the patch zip file into the PATCH_TOP.

· $ unzip -d PATCH_TOP p13801175_111167_Generic.zip

· NOTE: In WINDOWS, the unzip command might not work as this zip has

· certain contents which passes the 256 characters limit.

· To overcome this problem, please use alternate ZIP utility like

· 7-Zip to unzip the patch.

· For example: To unzip using 7-zip, run the command:

· "c:\Program Files\7-Zip\7z.exe" x p14302931_111154_Generic.zip

· 2. Set your current directory to the directory where the patch is located.

· $ cd PATCH_TOP/13801175

· 3. Run OPatch to apply the patch.

· $ opatch apply

· When OPatch starts, it validates the patch and makes sure that there are no

· conflicts with the software already installed in the ORACLE_HOME.

· OPatch categorizes two types of conflicts:

· a. Conflicts with a patch already applied to the ORACLE_HOME

· In this case, stop the patch installation, and contact Oracle Support

· Services.

· b. Conflicts with subset patch already applied to the ORACLE_HOME

· In this case, continue the install, as the new patch contains all the

· fixes from the existing patch in the ORACLE_HOME.

· 4 Post-Installation Instructions

· ---------------------------------

· - ,

· - Restart all servers (Admin Server and all Managed Server(s))

· 5 Deinstallation Instructions

· ------------------------------

· If you experience any problems after installing this patch, remove the patch as

· follows:

· 1. Make sure to follow the same Prerequisites or pre-install steps (if any)

· when deinstalling a patch.

· This includes setting up any environment variables like ORACLE_HOME and

· verifying the OUI inventory before deinstalling.

· 2. Change to the directory where the patch was unzipped.

· $ cd PATCH_TOP/13801175

· 3. Run OPatch to deinstall the patch.

· $ opatch rollback -id 13801175

· 6 Post Deinstallation Instructions

· -----------------------------------

· - Restart all servers (Admin Server and all Managed Server(s))

· 7 Bugs Fixed by This Patch

· --------------------------

· The following are the bugs fixed by this patch:

· 13801175: LARGE BUSINESSEVENT PAYLOAD CAUSES ORA-19011 SYS.XMLTYPE SIZE ERROR