Saturday, October 18, 2014

system-jazn-data.xml : Security issues issues




Symptoms:



You are unable to deploy SOA composites due to permission problem.

When a manged server was stopped you are no longer able to start it.
The Admin console shows the server state as 'FAILED_NOT_RESTARTABLE' and the following exception is seen in the server log:


java.security.AccessControlException: access denied (oracle.security.jps.service.credstore.CredentialAccessPermission context=SYSTEM,mapName=SOA,keyName=KeystorePassword read)



Cause:

Check of the system-jazn-data.xml shows that it is missing all preseeded roles such as SOAAdmin






Location : DOMAIN_HOME/config/fmwconfig


Solution:


Copy system-jazn-data.xml from a working installation into non-working installation.





Below will be error's u can see in front end logn, b2bconsole and soa composer




Tuesday, September 23, 2014

Caused by java.lang.UnsupportedOperationException: Remote JDBC disabled

Caused by java.lang.UnsupportedOperationException: Remote JDBC disabled

Caused by java.lang.UnsupportedOperationException: Remote JDBC disabled.
; nested exception is: BINDING.JCA-11622
Could not create/access the TopLink Session.

This session is used to connect to the datastore.


Above issue happening at OSB Calls 

Solution for this issue  is need to Enable Remote JDBC 

Shut Down OSB Managed Servers.

Please find below parameter  in setDomainEnv.sh and set it to true. It will be false by default

-Dweblogic.jdbc.remoteEnabled=true 


Thursday, September 11, 2014

weblogic.ldap.EmbeddedLDAP.validateVDEDirectories

Error/Issue: AdminServer is shutting down with below error in log file

<Sep 9, 2014 1:14:25 AM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NumberFormatException: null
java.lang.NumberFormatException: null
        at java.lang.Integer.parseInt(Integer.java:417)
        at java.lang.Integer.parseInt(Integer.java:499)
        at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1104)
        at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:242)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace
>
<Sep 9, 2014 1:14:25 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 9, 2014 1:14:25 AM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 9, 2014 1:14:25 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>



Solution:  Move data,cache,tmp under AdminServer directory and start AdminServer.

Or you can move ldap directory under data directory 

Bottom line is LDAP was corrupted need to recreate.


"class java.lang.NoClassDefFoundError : sun/awt/X11GraphicsEnvironment"

"class java.lang.NoClassDefFoundError : sun/awt/X11GraphicsEnvironment"

While opening EM Console will see that error in AdminServer log file.

Issue: We can open EM Console but we cant expand soa_infra, not only soa_infra we cant open any thing in em console except tropology.
  

Solution:
Please include below parameter in startup parameters of adminserver.


-Djava.awt.headless=true

Please mail me if required any help to implement solution bonams@gmail.com

Monday, September 8, 2014

Com.bea.console.exceptions.DeploymentConfigurationInitIncompleteException

Com.bea.console.exceptions.DeploymentConfigurationInitIncompleteException

  and module is defined DTD based description and cannot be edited using the console

U will see above errors at db adapter and other adopters configuration tab.

 Check which plan file is   configured for respective adapter and provide read and write and bounce services 

==========
also check free space


Error like below 



Wednesday, August 13, 2014

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

Hi,

       We are not able to start SOA Managed serve due to error MDS-00054.

Reason is : One of SOA Composit not able to load dut to MDS corrupted.

Solution is we can un deploy that composite and we can start  SOA ms using wlst.

Issue is:  We can not un deploy soa composite as its is not stating.

We have a solution via oracle note:1380835.1


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

2. cd to $MIDDLEWARE_HOME/oracle_common/common/bin

run wlst.sh

3.
connect()

provide the 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" ('/fmw11g/fmw1115/Middleware' is some location path on SOA machine)

exportMetadata(application='ShareSoaInfraPartition',server='AdminServer',toLocation='/fmw11g/fmw1115/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


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

importMetadata(application='ShareSoaInfraPartition',server='AdminServer',fromLocation='/fmw11g/fmw1115/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.




Tuesday, August 12, 2014

Action Plan for EM Console or Admin Url Taking LongTime to load pages or Switch Pages




Navigate to :DOMAIN_HOME/BIN

(Example:C:\Oracle\Middleware\user_projects\domains\base_domain\bin)

• Edit - for windows setDomainEnv.cmd  for linux setDomainEnv.cmd

•Search for the following string - set JAVA_OPTIONS=%JAVA_OPTIONS%
%JAVA_PROPERTIES% -Dwlw.iterativeDev=%iterativeDevFlag%
-Dwlw.testConsole=%testConsoleFlag%
-Dwlw.logErrorsToConsole=%logErrorsToConsoleFlag

• Append -DchangeSessionIdOnAuthentication=false to the string

-Dwlw.iterativeDev=%iterativeDevFlag%
-Dwlw.testConsole=%testConsoleFlag%
-Dwlw.logErrorsToConsole=%logErrorsToConsoleFlag%
-DchangeSessionIdOnAuthentication=false

• Restart all managed servers on this machine including the Admin server.

I have found an Oracle note that explain this issue.

Friday, June 13, 2014

Upgrade SOA 11.1.1.4 to 11.1.1.7 weblogic 10.3.4 to 10.3.6


High Level up Gradation Steps to upgrade SOA 11.1.1.4 to 11.1.1.7.

Please perform the below steps for upgrading SOA from 11.1.1.4.0 to 11.1.1.7.0.

1.      Upgrade Weblogic server from 10.1.3.4 to 103.6 by applying the Patch: 13529623.
Shut down all WebLogic processes you want to upgrade such as:
Node Manager
Admin Server
All Managed Servers
Download a new version of JDK 1.7+.
Download this patch set for Oracle WebLogic 10.3.6.0: Patch 13529623 (p13529623_1036_Generic.zip)
Unzip the file in a temporary location and confirm the extracted contains this file:
wls1036_upgrade_generic.jar
Installing and Verifying the JDK Version
Java –version
Running OUI to Upgrade an Existing WebLogic Server to 10.3.6

  1. Open a Command window with Run as Administrator option and run this command from the prompt:
>java -jar wls1036_upgrade_generic.jar
Upon execution, the installer starts preparing the OUI install program.
  1. On Choose Middleware Home Directory, select the existing Middleware home you wish to upgrade.
  2. Click the Next button.
  1. On Register for Security Updates, the Email address and/or the My Oracle Support Password fields as applicable.
  2. Click the Next button.
  1. On Choose Products and Components, verify the components.
Note:
The OUI installer automatically selects the Oracle Coherence component. You can choose to select or deselect this component, keeping in mind that this server type has not yet been verified with Oracle JD Edwards EnterpriseOne.
  1. Click the Next button.
  1. On Choose Product Installation Directories, verify the directory locations for the previously selected products and components.
Note:
A new version of Oracle Coherence_3.7 will be installed.
  1. Click the Next button.
OUI begins copying the files and performs the upgrade.
  1. On Installation Complete, click the check box for Run Quickstart to continue with the upgrade of the Oracle WebLogic domains.
  2. Click the Done button to complete the installation and exit OUI.
The Quickstart configuration screen appears.
  1. On the QuickStart links panel, select this link:
Upgrade domains to version 10.3.6
An Upgrade Wizard is launched.
  1. On the Welcome panel of the Upgrade Wizard, review and complete the tasks listed in the Prerequisites section of the above screen.
  2. When the Prerequisite tasks are complete, click the Next button.
  1. On Select WebLogic Version, select this radio button:
9.0 or higher
  1. Click the Next button.
  1. On Select a Domain to Upgrade, drill down through the Oracle\Middleware\user_projects\domains directory structure and select the Oracle JD Edwards domain. For example:
E1_Apps
  1. Click the Next button.
  1. On Inspect Domain, review the upgrade configuration selections.
  2. Click the Next button.
  1. On Select Upgrade Options, select this check box:
Back up current domain (recommended)
Caution:
The wizard advises you that if you choose the check box or Add log files to backup zip, the resultant zip file can be extremely large.
  1. On Domain Backup, review the message.
  2. Click the Next button.
  1. On Select Directory for Domain Backup, you can accept or change location and filename of the backup zip file.
  2. The wizard shows the progress of the domain backup.
  3. When the backup is complete, click the Next button.
  1. On Finalize Domain Upgrade, review the message.
  2. Click the Next button to begin the Upgrade.
  1. On Upgrade Complete, click the Done button to exit OUI.
Note:
As a result of this domain upgrade, you do not need to individually upgrade any Managed Server.
  1. Start the WebLogic NodeManager.
  2. Start the WebLogic Administration Console.
  3. Start the existing Managed Server such as the Oracle JD Edwards EnterpriseOne HTML server.
  4. Test and verify the upgrade.

2. Upgrade SOA 11.1.1.4.0 to 11.1.1.7.0 by applying the Patch: 16471502.

Downloading the Oracle Fusion Middleware Repository Creation Utility

You use the Oracle Fusion Middleware Repository Creation Utility to install the database schemas that are required by specific Oracle Fusion Middleware products.

For Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0), download one of the following:

Repository Creation Utility 11g Release 1 (11.1.1.7.0) from OTN or Oracle Software Delivery Cloud

Patch 16471709 (for Windows and Linux 32-bit systems) from My Oracle Support


If you are currently using Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0), then you must first update your environment to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) before applying 11g Release 1 (11.1.1.7.0).

3. You may also upgrade your JDK to JDK 1.7_07+ as pointed in certification matrix and change the JDK in the domain by going through the Note:1058804.1 "How To Change The JDK Type (Sun / JRockit) for a Given FMW 11g Domain"



Java Issue in linux 6

JAVA ISSUE in LINUX 6


Please set below parameter if you see jvm crash in linux 6

This also fix below errors: 

error code = 134

Error Message: Illegal memory acess. [54]

export LD_BIND_NOW=1

High Level Steps to Installing ADF 11.1.2.4.0 on Red Hat 6




High Level Steps to Installing ADF 11.1.2.4.0 on Red Hat 6


Download and Install ofm_appdev_generic_11.1.1.6.0


Apply Below patchs using Opatch

p16546129_111160_Generic.zip (ADF 11.1.2.4.0)

p16546157_111160_Generic.zip (ADF 11.1.2.4.0 – EM)


Create an ADF domain



Upgrade ADF in the domain using below Commands


/u01/app/oracle/product/adf/oracle_common/common/bin/wlst.sh
upgradeADF('/u01/app/oracle/domains/adf')

wls:/offline> upgradeADF('/u01/app/oracle/domains/adf')
Target Library "jsf#2.0@1.0.0.0_2-0-2" to JRF "AdminServer"

Apply the JRF template to a Managed Server via WLST



/u01/app/oracle/product/adf/oracle_common/common/bin/wlst.sh
applyJRF(target='ms01', domainDir='/u01/app/oracle/domains/adf')

If Required any details please contact me on bonams@gmail.com

Thursday, June 12, 2014

Different ways to take thread dumps in WebLogic Server

Different ways to take thread dumps in Weblogic Server

From OS
========

kill -3 <pid> 2>&1

From weblogic.wlst:
======================

setDomain.cmd or setDomain.sh depending on the OS
java weblogic.WLST
connect("<username>","<password>","t3://<url>:<port>")
threadDump()

From Command line
==================

setDomain.cmd or setDomain.sh depending on the OS
java weblogic.Admin <url>:<port> -username <username> -password <password> THREAD_DUMP

From JRockit
=============

jstack <pid> or jstack -l <pid> to print additional information about locks

jrcmd <pid> print_threads

jcmd <pid> Thread.print

From Admin Console also we can take thread dump