Issue in SOA Suite Installation - prerequisite for AIA 3.0 Installation

We are facing an issue in SOA Suite Installation which is prerequisite for AIA 3.0 Installation. As per AIA 3.0 Installation Guide, the Web Logic Server version to be used is “Web Logic Server 11g R1 10.3.1“ for Linux86 32bit Version.
After Installation of SOA Suite on Linux Environment, the em console page is not opening.
Error Message :
<Feb 1, 2010 5:21:50 PM IST> <Warning> <Connector> <BEA-190110> <Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.>
<Feb 1, 2010 5:21:50 PM IST> <Warning> <J2EE> <BEA-160140> <Unresolved optionalpackage references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.soa.fabric, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /app/oracle/weblogic/user_projects/domains/SOADomain/servers/soa_server1/tmp/_WL_user/worklistapp/r8n7fr]. Make sure the referenced optional package has beendeployed as a library.>
<Feb 1, 2010 5:21:50 PM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'worklistapp' due to error java.lang.NoSuchMethodError: weblogic.application.ApplicationLifecycleEvent.getDeploymentOperation()Lweblogic/application/DeploymentOperationType;.
We have faced such issue during SOA 11g Installation on Windows Operating System, and installed latest version of Web logic Server and the issue was resolved.
Can AIA Linux Installable work on Web Logic Server 11g R1 10.3.2?
If any one has faced similar issues, Kindly provide inputs.

The same person has reported issues on further steps i.e. AIA Installation. Hence closing this

Similar Messages

  • Installation issue- Oracle SOA Suite 10g Release 3 (10.1.3.x)

    Hi,
    I am installating (basic installation) Oracle SOA Suite 10g Release 3 (10.1.3.x), I have Vista OS. Configuration assisstant ran successfully till (App server, ESB, BPEL prcoess manager) it reached to Web Services Manager. It threw up following error-
    BUILD FAILED
    C:\product\10.1.3.1\OracleAS_3\owsm\scripts\install.xml:1971: The following error occurred while executing this line:
    C:\product\10.1.3.1\OracleAS_3\owsm\scripts\dataload.xml:199: java.sql.SQLException: Internal Error:Invalid Connect String
    I have JDeveloper installed on my system. Let me know if you need the log file.
    Any help is greatly appreciated.

    Andre,
    I am a newbee in this field and I could not understand your question. Can you please explain? I downloded Oracle JDeveloper to design BPEL processes and trying to install Oracle SOA suite for BPEL process manager, that is where I hit this road block.
    Thanks

  • BPEL Composite compilation issues in SOA Suite 11.1.2

    I imported a SOA Composite BPEL project developed on SOA Suite 11.1.1 in SOA Suite 11.1.2. When compiling the project through ant using the "ant-sca-compile.xml" generated through JDev in 11.1.1 I am getting the following exception
    java.lang.NoClassDefFoundError: oracle/fabric/common/FabricException
    Caused by: java.lang.ClassNotFoundException: oracle.fabric.common.FabricException
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
    Could not find the main class: oracle.soa.scac.ValidateComposite. Program will exit.
    Exception in thread "main"
    Have checked all my classpaths and jar's which are found to be in order. What can be the problem?

    I changed some of the paths in the build file but now I am having compilation issues. It says the classpath is not set correctly. But I have included all the jar's properly in the build.xml.
    Any pointers to where I might be going wrong?
    D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\build\ant-sca-compile.xml
    detokeniser:
    scac:
    [scac] Validating composite : 'D:/CommonTechServices/INT_ARCH/Construction/src/soa/CommonServices/NotificationServiceBpel/composite.xml'
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:14: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:15: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:16: package com.collaxa.cube.engine.core.map does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:21: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:100: package com.collaxa.cube.engine.core.ICubeProcess does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:107: package com.collaxa.cube.engine.core.ICubeProcess does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:148: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:148: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:148: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:390: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:390: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:401: package com.collaxa.cube.engine.core.map does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:401: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:401: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.util does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.util does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:857: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:900: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:900: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:930: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:941: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:941: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:990: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1044: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1044: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1089: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1089: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1105: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1122: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1122: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1122: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1300: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1404: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1404: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1449: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1449: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1465: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1509: package com.collaxa.cube.engine.types.bpel does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1526: package com.collaxa.cube.engine.types.bpel does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1553: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1607: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1607: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1652: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1652: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1668: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1685: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1685: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1685: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1780: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1797: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1797: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1797: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1964: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1981: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1981: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:1981: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2154: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2208: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2208: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2253: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2253: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2269: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2286: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2286: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2286: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2381: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2398: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2398: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2398: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2565: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2582: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2582: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2582: package com.collaxa.cube does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2755: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2859: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2859: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2904: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2904: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2920: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2964: package com.collaxa.cube.engine.types.bpel does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:2981: package com.collaxa.cube.engine.types.bpel does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:3008: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine.core does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine does not exist
    [scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
    l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine.core does not exist
    [scac] Note: D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\
    orabpel\notificationservicebpel\BPEL_BIN.java uses unchecked or unsafe operations.
    [scac] Note: Recompile with -Xlint:unchecked for details.
    [scac] FATAL_ERROR: location {ns:composite/ns:component[@name='NotificationServiceBpel']}(30,45): Failed to compile bpel generated classes.
    [scac] failure to compile the generated BPEL classes for BPEL process "NotificationServiceBpel" of composite "default/NotificationServiceBpel!1.0
    [scac] The class path setting is incorrect.
    [scac] Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL pr
    ocess is depending on are deployed correctly. Also verify that the run time is using the same release/version.
    [scac]
    BUILD FAILED

  • Oracle SOA Suite integration vs Oracle AIA

    HI,
    Oracle soa suite provides the environment to make use of existing service by providing oracle adapters including Legacy,package and application adapters. futher which suituation and why need to use oracle AIA in order to make use existing resources. am little bit confuse both of this approach over integration.
    can anyone clear my doubt
    regards
    ashok.v

    Hi,
    You can find the answer in AIA white paper in below link.
    www.oracle.com/us/products/applications/057018.pdf
    'The Oracle Application Integration Architecture Foundation Pack heralds a new approach to integrating your application portfolio based on composite business processes. It combines the power of Oracle’s Fusion Middleware along with a set of best in class application Enterprise Business Objects and Services that form the building blocks for a new generation of composite applications that leverage your existing investments to fulfill mission critical business processes.'

  • Different OID's supported in SOA Suite 11 g for Bpel

    any one tell like what are the different OID's supported in soa suite 11g for Bpel for managing users and roles.
    Thanks & Regards
    Naga

    Try changing this
    <xsl:output method="text" indent="yes" encoding="ISO-8859-1"/>
    to
    <xsl:output method="text" indent="yes" encoding="ASCII"/>

  • Issue w/SOA Suite Install 10.1.3.1

    I'm trying to install the SOA suite on Vista. I ran the install in admin mode and it was fine withe deploying the objects, however during the configuration part, I got an error on teh BPEL config.
    Failed at "could not get deployment manager"
    This is typically the result of an invalid URI format being supplied. the target server not bing in started state or incorrect authentication details being supplied.
    Any thoughts?
    Thanks in advance

    Hi,
    There are some Vista specific install instructions for installing SOA. Did you happen to follow them?
    I'm wondering if you don't have some network settings that need to be changed?
    Thanks.

  • Installation prerequisites for MDM 5.5

    Hi all,
    Is it possible to download MDM 5.5 sp06?
    If yes,what are the prerequisites for that?
    What configuration should maintained in my desktop?
    how much space will it take in my computer memory?
    Regards,
    Vijay

    Hi Vijaybabu,
    The hardware requirements for installing the MDM.
    Hardware Requirements -- See MDM 5.5 - Sizing Guide at service.sap.com/installMDM
    Operating Systems -- See Product Availability Matrix (PAM) on SAP Service Marketplace at
    service.sap.com/pam -> SAP NETWEAVER-> SAP MDM
    Minimum Database -- Versions
    MaxDB 7.7.01
    IBM DB2 8.2
    IBM DB2 for z/OS 8 in New Function Mode
    IBM DB2 for i5/OS V5R4
    Oracle 9i: 9.2.0.7
    Oracle 10g: 10.2
    MS SQL 8 SP3
    Software to be installed along with the SAP MDM.
    Client software for the DBMS you want to use.
    MS XML Parser 4.0 with SP 2 or higher (available for free download from Microsoft)
    MS MDAC u2013 Version 2.7 or higher (available for free download from Microsoft).
    MS Access® (Office 2000, Office XP, Office 2003) and/or MS Excel® (Office 2000, Office XP, Office 2003)
    Adobe Acrobat® Reader Version 4.0 or higher
    Adobe Acrobat® Standard or Professional Version 4.0 or higher
    Adobe Photoshop® version CS2
    Adobe InDesign® versions CS2 or CS3
    Oracle Provider for OLEDB
    MS Visio® 2003 standard
    Hope this inforamtion helps you.
    Cheers
    Santosh.

  • FTP Adapater issues in SOA Suite 11g- ResourceDeadException..

    We are losing the process and had to manually re-start the process because of below ResourceDeadException. We are having the FTP adapter connection pool to connect to external FTP server which we are going through the internet. Intermittently some of the connections becoming stale and geting rejected. I appreciate any inputs... Thanks, Saagi
    oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
    Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'execute' failed due to: JCA Binding Component connection issue.
    JCA Binding Component is unable to create an outbound JCA (CCI) connection.
    STC_PROV_INS_SM_CS:WRITE_SM [ execute_ptt::execute(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: javax.resource.spi.ApplicationServerInternalException: Unable to get a connection for pool = 'eis/FTP/STC', weblogic.common.resourcepool.ResourceDeadException
    The invoked JCA adapter raised a resource exception.
    Please examine the above error message carefully to determine a resolution.
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.EndpointInteractionException.getFabricInvocationException(EndpointInteractionException.java:75)
         at oracle.integration.platform.blocks.adapter.AdapterReference.getFabricInvocationException(AdapterReference.java:286)
         at oracle.integration.platform.blocks.adapter.AdapterReference.post(AdapterReference.java:272)
         at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler.doPost(AsynchronousMessageHandler.java:142)
         at oracle.integration.platform.blocks.mesh.MessageRouter.post(MessageRouter.java:194)
         at oracle.integration.platform.blocks.mesh.MeshImpl.post(MeshImpl.java:204)
         at sun.reflect.GeneratedMethodAccessor1149.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:296)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
         at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy192.post(Unknown Source)
         at oracle.fabric.CubeServiceEngine.postToMesh(CubeServiceEngine.java:770)
         at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:251)
         at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1009)
         at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:512)
         at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:123)
         at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:63)
         at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:157)
         at com.collaxa.cube.engine.CubeEngine._performActivity(CubeEngine.java:2585)
         at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2444)
         at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1121)
         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:322)
         at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4497)
         at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4428)
         at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:685)
         at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:682)
         at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:356)
         at sun.reflect.GeneratedMethodAccessor1170.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:88)
         at java.security.AccessController.doPrivileged(Native Method)
         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.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61)
         at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106)
         at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
         at sun.reflect.GeneratedMethodAccessor1125.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:55)
         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 $Proxy179.handleInvoke(Unknown Source)
         at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:409)
         at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:142)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:82)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: BINDING.JCA-12563
    Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'execute' failed due to: JCA Binding Component connection issue.
    JCA Binding Component is unable to create an outbound JCA (CCI) connection.
    STC_PROV_INS_SM_CS:WRITE_SM [ execute_ptt::execute(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: javax.resource.spi.ApplicationServerInternalException: Unable to get a connection for pool = 'eis/FTP/STC', weblogic.common.resourcepool.ResourceDeadException
    The invoked JCA adapter raised a resource exception.
    Please examine the above error message carefully to determine a resolution.
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:432)
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:541)
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeAsyncJcaReference(JCAInteractionInvoker.java:501)
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performAsynchronousInteraction(JCAEndpointInteraction.java:479)
         at oracle.integration.platform.blocks.adapter.AdapterReference.post(AdapterReference.java:235)
         ... 72 more
    Caused by: BINDING.JCA-12511
    JCA Binding Component connection issue.
    JCA Binding Component is unable to create an outbound JCA (CCI) connection.
    STC_PROV_INS_SM_CS:WRITE_SM [ execute_ptt::execute(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: javax.resource.spi.ApplicationServerInternalException: Unable to get a connection for pool = 'eis/FTP/STC', weblogic.common.resourcepool.ResourceDeadException
    Please examine the log file for any reasons. Enable FINEST adapter logging via Enterprise Manager.
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAConnectionManager$JCAConnectionPool.createJCAConnection(JCAConnectionManager.java:1372)
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAConnectionManager$JCAConnectionPool$JCAConnection.init(JCAConnectionManager.java:1041)
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAConnectionManager.obtainJCAConnection(JCAConnectionManager.java:694)
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:175)
         ... 76 more
    Caused by: javax.resource.spi.ApplicationServerInternalException: Unable to get a connection for pool = 'eis/FTP/STC', weblogic.common.resourcepool.ResourceDeadException
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:394)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
         at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
         at oracle.tip.adapter.ftp.FTPConnectionFactory.getConnection(FTPConnectionFactory.java:98)
         at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAConnectionManager$JCAConnectionPool.createJCAConnection(JCAConnectionManager.java:1355)
         ... 79 more
    Caused by: weblogic.common.resourcepool.ResourceDeadException
         at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1540)
         at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:375)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
         at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
         ... 83 more

    This is issue with File and Ftp Adapters in the soa installation 11.1.1.2. These adapters not able to recycle the dead connections in the connection pool. Process are receiving the dead connections from the pool. Oracle provided the patch for it. In the patch ftp adapter is throwing out the dead connection pool instead of keeping them.

  • Transaction Rollback Issue in SOA Suite

    Hi All,
    We have been facing the transaction rollback issue very frequently and looking for a concrete solution on this. We have a Asynchronous BPEL process which calls a webservice in a loop of say 20 iteration. In the loop sometimes we face this transaction rollback issue and apparently the CatchAll block doesn't capture this.
    In many blogs and oracle metalink we have seen few settings for this and made as per below :
    1. JTA Transaction timeout increase : we have it 10000 sec.
    2. The Data Source settings : 2.1 : XA transaction timeout check-box selected
    2.2 : The Initial Capacity : 10, Maximum Capacity : 200 and Capacity Increment = 5
    3. soa-infra -> EJBs -> set the transaction timeout to 1200 for many of the recommended BPELs
    4. DISTRIBUTED_LOCK_TIMEOUT = 120 sec.
    In short, all the recommended settings are in place. But still, we are facing this issue. Does anyone know if anything is missing in the setting ? Or any other solution to the issue?
    Any help is truly appreciated.
    Thanks,
    Ashwini

    I think, even if you change the setting you may not get rid of this problem permanently. Try to avoid call to the webservice in a loop and look for any other alternate solution like JMS (thread should not block for the response of the webservice).

  • Http post issue in soa suite 11g  with 10g wsdl

    I have 10g process that has http post wsdl as below. When I'm trying to create a project in 11g 11.1.1.4 with same wsdl, getting the following error at building the project. "Error(12,61): Parse of component type files failed, check the adf-config.xml file : "Error at line 34 char 64: Malformed WS Binding port. Missing # between namespace URI and service/port names."
    I'm sure that http post mechanism is changed in 11g, but can you please help what exactly is wrong ?
    <?xml version="1.0"?>
    <definitions name="HTTPPostService"
    targetNamespace="http://services.otn.com"
    xmlns:tns="http://services.otn.com"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
              xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
              xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    >
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    TYPE DEFINITION - List of types participating in this BPEL process
    The BPEL Designer will generate default request and response types
    but you can define or import any XML Schema type and use them as part
    of the message types.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <types>
    <schema attributeFormDefault="qualified" elementFormDefault="qualified"
    targetNamespace="http://services.otn.com"
    xmlns="http://www.w3.org/2001/XMLSchema">
    <element name="Postreq">
    <complexType>
    <sequence>
    <element name="Order_Update_Request">
    <complexType>
    <sequence>
    <element name="ORD_ID" type="string"/>
    <element name="E_MAIL" type="string"/>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    </element>
    <element name="Postresp">
    <complexType>
    <sequence>
    <element name="Order_Update_Response">
    <complexType>
    <sequence>
    <element name="RETURN_STATUS" type="string"/>
    <element name="MESSAGE_TEXT" type="string"/>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    </element>
    </schema>
    </types>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    MESSAGE TYPE DEFINITION - Definition of the message types used as
    part of the port type defintions
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <message name="HTTPPostServiceRequestMessage">
    <part name="payload" element="tns:Postreq"/>
    </message>
    <message name="HTTPPostServiceResponseMessage">
    <part name="payload" element="tns:Postresp"/>
    </message>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    PORT TYPE DEFINITION - A port type groups a set of operations into
    a logical service unit.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <!-- portType implemented by the HTTPPostService BPEL process -->
    <portType name="HTTPPostService">
    <operation name="IScript_Update_Order">
    <input message="tns:HTTPPostServiceRequestMessage" />
    <output message="tns:HTTPPostServiceResponseMessage"/>
    </operation>
    </portType>
    <binding name="HTTPPost" type="tns:HTTPPostService">
    <http:binding verb="POST"/>
    <operation name="IScript_Update_Order">
    <http:operation location="/PSIG/HttpConnector?From=PSFT_XINBOUND&amp;MessageName=ABC_ORD_UPDORDER&amp;MessageType=sync&amp;MessageVersion=v1"/>
    <input>
    <mime:mimeXml part="payload"/>
    <mime:content type="text/xml"/>
    </input>
    <output>
    <mime:mimeXml part="payload"/>
              <mime:content type="text/xml"/>
    </output>
    </operation>
    </binding>
    <service name="HTTPPostService">
    <port name="HTTPPost" binding="tns:HTTPPost">
    <http:address location="http://myserver.mycompany.com"/>
    </port>
    </service>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    PARTNER LINK TYPE DEFINITION
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <plnk:partnerLinkType name="HTTPPostService">
    <plnk:role name="HTTPPostServiceProvider">
    <plnk:portType name="tns:HTTPPostService"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>

    Can you make sure your helloworld is using adf bindings as mentioned in thread Re: Urgent :: 11g Invoking Composite from Java/From Webservice Proxy

  • Installing AIA 11g on top of SOA Suite 11g

    I have installed SOA Suite 11g (11.1.1.5) as per Oracle Installation Guide. The installation is successful and SOA Suite 11g is working fine!
    Now I need to installa AIA 11g.
    1) Currently I have Oracle XE database. Do I need to uninstall it and install Oracle 11g DB?
    2) If yes, do I need to uninstall SOA Suite and install it again after DB installation?
    Please advise.
    Thanks

    Its always better to have Oracle 11g database, against XE database.
    You dont need to uninstall the SOA 11g, just make sure you have the Compatible Oracle 11g database version, create the RCU, then you have to point all the JNDI which is available in SOA 11g to new database.
    Check in metalink.oracle.com. You should get a note explaining, about how to change the RCU pointing.
    Thanks,
    Vijay

  • Installation of 11g SOA Suite

    Hello All,
    I have installed the
    ORacle 11g DB
    RCU to create schema
    Oracle 11g SOA suite
    Two Domains for BAM and SOA suite (without) selecting the Admin Option as referred in QUick install guide.
    I have query on these two weblogic domains as both of them have the same port 7001, how can I run both the domains ?
    Have you found the .xml files as mentioned in page no. 49. of the guide ?

    Hello Baskar,
    I did refer Quick installation while installing and followed the steps, hence created two domains with the understanding that BAM component probably needs a separate domain (BEA) as it could be bit heavy weight component.
    I believe if BAM, SOA and EM can run in a single domain, even now it is NOT too late, there is a option to configure domain and I will use the SOA domain create to check the BAM component also into it and start only this domain. But the quick installation guide seems to have a conflicting guidance steps.
    http://download.oracle.com/docs/cd/E12839_01/install.1111/e14318/qisoa.htm
    Refer the Installation Guide and the steps for configuring BAM and configuring SOA, they had been given in two step activity with different domains.

  • Proxy settings for SOA Suite 10.1.3.1.0

    Hi,
    after migrating my processes into the new SOA Suite 10.1.3.1.0, one of my processes won't run anymore. This is due to missing proxy configuration.
    I followed this explanation[1] which worked for the process manager 10.1.2xx but not for the SOA Suite.
    I really appreciate your help and any suggestions.
    thanks,
    Gregor
    [1] how to config the proxy of Bpel process manager(with password)

    You need to go to the AS Control pages (Enterprise Manager). Click on the container that runs SOA suite (typically "home" for simple install, or "OC4J_SOA" for advanced install).
    On the OC4J page, click on the "Administration" tabsheet. Click on "Server Properties".
    You should find the commandline options for OC4J.
    You will need to set the following options:
    -Dhttp.useProxy=true
    -Dhttp.proxyHost=<your proxyserver>
    -Dhttp.proxyPort=<your proxyport>
    -Dhttp.nonProxyHosts=<any servers like localhost you don't want to run via the proxy>
    Marc

  • SOA suite licensing for production use

    Hi,
    I have been toying around with JDeveloper 11g and Oracle SOA Suite 11g and finally I can now say I am in a position to recommend to start moving the organisation's business processes and enterprise integration gradually to this framework. However I am slightly confused what the Oracle SOA Suite license would cover.
    It is not clear what components are covered with the SOA Suite 11g license (for example: is the OSB also included? it is a separate download. Is CEP included?)
    Also, will we need a separate Oracle database license for it to really work? If yes what database is needed (Enterprise, Standard etc.)? or does the SOA Suite license cover the use of a database too in some way, as long as it is used for SOA and BPEL etc.?
    I presume that for a reliable framework we would need at least 2 nodes with clustering at both application level and database level, so we really need to do our homework well with regards to the costs required.
    thanks.

    Oracle SOA Suite 11g licence includes full use license for Oracle Service Bus(even though it is available as separate download) and so is true for CEP.
    Refer to [http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10223/01_components.htm]
    Yes, SOA Suite will require a database and does not include any kind of database license related to SOA Suite license. For development purposes free Oracle DB XE will suffice.

  • OSB Development in 11g 11.1.1.3 / Oracle SOA Suite Installation (11.1.1.3)

    Hello,
    Is the latest OSB available as SCA Component in Jdeveloper ? If we want to develop services in OSB, should we use the browser or we have eclipse support for the latest release.
    Looks like now we can use the same version of weblogic server 10.3.3 to host both SOA suite 11g 11.1.1.3 and Oracle Service Bus 11.1.1.3. I believe we need two different domains (1 for SOA Suite and another for Oracle Service Bus).
    Kindly confirm.
    Edited by: user8387065 on 27-May-2010 03:06
    Edited by: user8387065 on 10-Jun-2010 05:22

    Is the latest OSB available as SCA Component in Jdeveloper ?No. Not yet in OSB 11gR1
    If we want to develop services in OSB, should we use the browser or we have eclipse support for the latest release.For OSB 11gR1 any option can be used based on your requirement.
    Looks like now we can use the same version of weblogic server 10.3.3 to host both SOA suite 11g 11.1.1.3 and Oracle Service Bus 11.1.1.3Yes.
    I believe we need two different domains (1 for SOA Suite and another for Oracle Service Bus). You can run SOA and OSB in same domain (same JVM) with OSB 11gR1.
    Thanks
    Manoj

Maybe you are looking for

  • Calendar Server Error: At least one sharee was not recognized by the server. New invitations have not been sent.

    I deployed a Mountain Lion Server with the calendar service active. Every time a user tries to share a calendar they have created under thier account to an external person using thier email address, the server gives the following error: "At least one

  • Searching word docs with verity - strange problem

    I am searching word documents using cfsearch. These documents are basically forms. Some of the fields such as name etc. are with back fill enable for user input. So if I search the names in this field with back fill I get 0 records. If it's a plain t

  • Unable to create spatial index

    I have a spatial table called ROAD11 in that table I have a MDSYS.SDO_GEOMETRY column named "GEOMETRY". after creating that table, I inserted a row, in the USER_SDO_GEOM_METADATA. Here is what is present in USER_SDO_GEOM_METADATA SQL> SELECT * FROM U

  • Video Out, is it possible?

    i'd like to hook up my TouchSmart 600 to a digital projector (for large movie showings). Is there a video out option or connector on the TouchSmart? any suggestions? thanks, Idan

  • Java Desktop System Release 3 - Login problems

    Hi all, This is my first post here so apologies if I'm in the wrong area. I've recently installed Solaris 10 (5.10 Generic_118833-36) onto a V245. I wanted to see if I could get the gui desktop to work so I downloaded/installed Hummingbird Exceed on