Installing Oracle JDeveloper 11.1.1.6.0 (Oracle JDeveloper 11g R1 Patch Set 5)

Installing Oracle JDeveloper 11.1.1.6.0 (Oracle JDeveloper 11g R1 Patch Set 5)


For Installing Oracle JDeveloper 11.1.1.7.0 Studio Edition (Oracle JDeveloper 11g R1 Patch Set 6), refer to the blog post here.

This patchset contains some new features mostly on the ADF Faces area and they include:

- Support for HTML 5 rendering for the data visualization components
- Support for touch gestures when accessing ADF Faces from an iPad
- Better support for search engines and Web crawling.

This version also includes the infrastructure for Oracle JDeveloper deployment to the upcoming Oracle Cloud.


Depending on the type of installer you are using, you can begin the installation process in one of the following ways:

■ To launch the platform-independent installer, enter: java -jar 
jdevstudio11116install.jar.

■ To launch the Windows installer, double-click the 
jdevstudio11116install.exe file. 

■ To launch the Linux installer, follow these steps:

1. Ensure that the jdevstudio11116install.bin file is executable: chmod 
+x jdevstudio11116install.bin.

2. Execute the file: ./jdevstudio11116install.bin.
You can also launch the installer in silent mode, to ensure that no configuration options are displayed during the installation process

Download Oracle JDeveloper 11.1.1.6.0

Oracle JDeveloper 11.1.1.6.0 Install Guide



Installation
============

1. Welcome
Click Next to begin the installation process.

2. Choose Middleware Home Directory

3. Choose Install Type

Select either Complete or Custom depending on the type of installation you want to perform.

4. Choose Products and Components (Custom Install only)

5. JDK Selection (Generic Installer only)

6. Confirm Product Installation Directories

7. Choose Shortcut Location (Windows systems only)

8. Installation Summary

9. Installation status

10. Installation Complete

AIAReadJMSNotificationProcess [1.0] in unknown state in SOA 11g EM Fusion Middleware Console

AIAReadJMSNotificationProcess [1.0] in unknown state in SOA 11g EM Fusion Middleware Console


Are you seeing AIAReadJMSNotificationProcess [1.0] composites in unknown states in your SOA enterprise manager console?


Errors as below:

<Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "AIAReadJMSNotificationProcess" failed: Error in getting XML input stream: http://soa.localhost.com:port/soa-infra/services/default/AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess.wsdl: Connection reset.>
====> CubeEngine load AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess took 476 ms

AIAReadJMSNotificationProcess appears in unknown state on SOA cluster nodes

Composite is in Failed state because it may not have got deployed when soa_server has been started. This may be because you have dependencies between your SOA Composites and AIAReadJMSNotificationProcess that has been deployed before AIAErrorTaskAdministrationProcess it depends on. 

For quick fix:

- restart soa_servers but it may happen again because deployment order of SOA Composites cannot be configured

or 

- redeploy AIAReadJMSNotificationProcess composite


For long term fix, follow:

Doc ID 1151973.1 Boot Order Of The Composites Upon Soa Suite Restart


Doc ID 1369101.1 SOA Server With AIA Unable to Look Up WSDL's At Startup

associated with bug: 12979076 - SOA11G MANAGED SERVER WITH AIA FAILS LOOKING UP WSDL AT STARTUP

Webcenter Content Imaging (Imaging and Process Management) Index Collection needs to be synchronized, a full collection rebuild is required. Please rebuild the index collection

Webcenter Content Imaging (Imaging and Process Management) Index Collection needs to be synchronized, a full collection rebuild is required. Please rebuild the index collection

Few errors seen in the Oracle IPM logs when trying to check in documents in UCM



<Mar 19, 2013 4:56:53 PM GMT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
 javax.ejb.EJBException: nested exception is: oracle.imaging.ImagingException: TCM-00787: A repository error occurred.
        faultType: SYSTEM
        faultDetails:
          ErrorCode = oracle.stellent.ridc.protocol.ServiceException, ErrorMessage = Unable to execute service CHECKIN_NEW_SUB and function addFiles.
The error was caused by an internally generated issue. The error has been logged. .
javax.ejb.EJBException: nested exception is: oracle.imaging.ImagingException: TCM-00787: A repository error occurred.
        faultType: SYSTEM
        faultDetails:
          ErrorCode = oracle.stellent.ridc.protocol.ServiceException, ErrorMessage = Unable to execute service CHECKIN_NEW_SUB and function addFiles.
The error was caused by an internally generated issue. The error has been logged.
        at oracle.imaging.inputagent.InputFilingMDB.onMessage(InputFilingMDB.java:203)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        Truncated. see log file for complete stacktrace
>


When logged in to content server, a message displayed.

"Index Collection needs to be synchronized, a full collection rebuild is required. Please rebuild the index collection"

Workaround tried was to rebuild indexes 


In the WebCenter Content UI:

1. On the left pane, go to "Administration"

2. Select "Admin Applets"

3. Pick the "Configuration Manager" applet

4. The button "Rebuild Search Index" should be clickable - click on it to rebuild the index.

Please Note: Rebuilding the index may take quite a while. It is advisable to do so during the server's low peak time.

Exception occured during invocation of JCA binding. The invoked JCA adapter raised a resource exception

Exception occured during invocation of JCA binding. The invoked JCA adapter raised a resource exception 

Observed JCA resource exception for one of the connection pools in our SOA 11.1.1.5.0 environment.

The errors in the logs were similar to a documented note for SOA Composites Fails With java.util.ConcurrentModificationException Error.

Fix was to download and apply patch 13976065 

It includes fixes for the following bugs: 13360039, 11924578, 12797505, 11812911


Detailed errors in the logs were:

==========================


System Fault Error Message: {http://schemas.oracle.com/bpel/extension}bindingFault
Fault ID default/InvoiceProcessing!1.9*soa_9a7afc0a-a2b0-4f9f-82e9-c50202253d4e/InvoiceProcessing/430342-BpInv2-BpSeq4.10-2
Fault Time Feb 18, 2013 10:46:06 AM
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'XX_WC_REPORTING' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec due to: ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>null</detail></part><part name="code"><code>null</code></part></bindingFault></bpelFault>


<Feb 18, 2013 10:46:06 AM GMT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> InvoiceProcessing:XX_WC_REPORTING [ XX_WC_REPORTING_ptt::XX_WC_REPORTING(InputParameters) ] Could not invoke operation 'XX_WC_REPORTING' against the 'Database Adapter' due to: 
BINDING.JCA-12563
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec due to: ". 
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
> 
<Feb 18, 2013 10:46:06 AM GMT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> [default/InvoiceProcessing!1.9*soa_9a7afc0a-a2b0-4f9f-82e9-c50202253d4e.XX_WC_REPORTING]:XX_WC_REPORTING One-way operation XX_WC_REPORTING() failed> 
<Feb 18, 2013 10:46:06 AM GMT> <Error> <oracle.soa.bpel.engine.ws> <BEA-000000> <got FabricInvocationException
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:977)
at java.util.HashMap$KeyIterator.next(HashMap.java:1012)
at oracle.integration.platform.blocks.adapter.fw.wsdl.WSDLUtils.setCciSpecParameters(WSDLUtils.java:373)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.getJCAInteractionSpec(JCAInteractionInvoker.java:828)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:206)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:525)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeAsyncJcaReference(JCAInteractionInvoker.java:508)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performAsynchronousInteraction(JCAEndpointInteraction.java:491)
at oracle.integration.platform.blocks.adapter.AdapterReference.post(AdapterReference.java:247)
at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler.doPost(AsynchronousMessageHandler.java:142)
at oracle.integration.platform.blocks.mesh.MessageRouter.post(MessageRouter.java:197)
at oracle.integration.platform.blocks.mesh.MeshImpl.post(MeshImpl.java:214)
at sun.reflect.GeneratedMethodAccessor5519.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy341.post(Unknown Source)
at oracle.fabric.CubeServiceEngine.postToMesh(CubeServiceEngine.java:807)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:258)
at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1059)
at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:586)
at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:130)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:75)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:158)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2543)
at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1166)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1071)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:328)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4430)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4362)
at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:698)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:555)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:673)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:293)
at sun.reflect.GeneratedMethodAccessor2633.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:94)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:81)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:112)
at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
at sun.reflect.GeneratedMethodAccessor1092.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy324.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:65)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
at java.lang.Thread.run(Thread.java:662)
> 
<Feb 18, 2013 10:46:06 AM GMT> <Error> <oracle.soa.bpel.engine> <BEA-000000> <Unhandled exception for ComponentDN=default/InvoiceProcessing!1.9*soa_9a7afc0a-a2b0-4f9f-82e9-c50202253d4e/InvoiceProcessing CompositeInstanceId=160054 ComponentInstanceId=430342> 
<Feb 18, 2013 10:46:06 AM GMT> <Error> <oracle.soa.bpel.engine> <BEA-000000> <This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. Root cause : 
com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'XX_WC_REPORTING' failed due to: Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec due to: ". 
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
". 
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>null</detail>
,code=<code>null</code>}

at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:334)
at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1059)
at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:586)
at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:130)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:74)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:158)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2543)

==================================

Soa-Infra Log Configuration Screen Appears Blank in SOA 11g Enterprise Manager Console

Soa-Infra Log Configuration Screen Appears Blank in SOA 11g Enterprise Manager Console

In a SOA cluster environment when navigating in Oracle Enterprise Manager Fusion Middleware Control using this path: Farm_soadomain -> SOA -> soa-infra and right click 
Logs -> Log Configuration, the Log Level tab appears blank.

It appears blank in SOA standalone environments too.

In our case, we upgraded our SOA servers from 11.1.1.3.0 to 11.1.1.5.0 recently.

Log configuration Page appears blank

This may be caused because the WLST script upgradeJRF('/DOMAIN_HOME') command on the node or system where the Administration Server is located for each domain you want to update was not run.

Reference: Bug 12658557 - APPLY JRF TEMPLATE FOR SOA_CLUSTER AND ADMINSERVER SHOULD BE ADDED TO SOA EDG

To resolve this, apply the JRF Template to the SOA_Cluster as documented in EDG.

After the domain is created with the Configuration Wizard, you must target a number of resources not included in the WebLogic server installation to the SOA_Cluster.


To target these resources:

1. Log in to Oracle Enterprise Manager Fusion Middleware Control
2. On the navigation tree on the left, expand Farm_<domain_name>, WebLogic Domain, and then <domain_name>, and select SOA_Cluster.
3. Click Apply JRF Template button right below the SOA_Cluster Information banner in the EM Console's right pane, see screenshot below.
4. Wait for the confirmation message to appear on the screen.
This message should confirm that the JRF Template has been successfully applied to the SOA_Cluster cluster.
5. Restart the SOA server

We were facing this issue on our standalone SOA servers which were recently upgraded from 11.1.1.3.0 to 11.1.1.5.0.

Applied this workaround. However, we hit another error:


Unable to invoke applyJRF because the domain $MW_HOME/111/user_projects/domains/soa_domain has not been extended with JRF template.oracle.sysman.emSDK.app.exception.EMSystemException