This discussion is archived
1 2 Previous Next 21 Replies Latest reply: Jun 11, 2012 2:20 AM by robert224810 RSS

Composite errors after upgrade to 11.1.1.5.0

robert224810 Explorer
Currently Being Moderated
Hi,
We have just upgraded from 11.1.1.2.0 to 11.1.1.5.0. I have an integration developed in 11.1.1.2.0 which I want to get working in 11.1.1.5.0.

It's a simple 5 stage fire and forget integration (reqTransport -> reqABCS -> EBS -> provABCS -> provTransport)

I am having problems with compiling the provABCS, I am getting errors as follows:

[scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(75): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}Sender" of variable "Sender" is not defined
[scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(77): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}EBMHeader" of variable "EBM_HEADER" is not defined
[scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(443): XML element "{http://schemas.xmlsoap.org/ws/2003/03/addressing}EndpointReference" of variable "EndpointReference" is not defined
[scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(620): XML element "{http://ic.ac.uk/AIAMetaData/AIAComponents/ApplicationObjectLibrary/IC_ABM_COMMON}ICXREF_LinkResult" of variable "LinkXRefReturn" is not defined
[scac] error: location {ns:composite/ns:wire/ns:target.uri[.='CreateInvoiceListEbizProvABCSImplProcess/CreateInvoiceListEbizProvABCSImpl']}(77,21): Source callback port type for "CreateInvoiceListEbizProvABCSImpl" does not match target callback port type for "CreateInvoiceListEbizProvABCSImplProcess".

I have checked the MDS library and verified that the elements are included in the xsd files.
In the case of the IC_ABM_COMMON reference I have verified that it is it's xsd file,
I then double checked the ABM's xsd file and it does import it correctly. (It expands when viewed in JDeveloper)
I made sure the ABM is imported into the transportProvidors WSDL and it is
I made sure the transportProvidors WSDL is imported into the transportProvidor's RefWSDL
I have double checked that the transportProvidor's RefWSDL is included in the composite and it is
and it is this composite that includes the bpel which is throwing the error.

This all used to work fine in 11.1.1.2.0, I can't understand what has changed.
Can anyone give me some suggestions as to other things I can check?
Thanks
Robert
  • 1. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    Also the ABCS requestor fails in exactly the same way:
    [scac] Validating composite "H:\JDev_ADF_SOA\mywork\RJMAIATEST101\CreateInvoiceListEbizOSSReqABCSImpl\composite.xml"
    [scac] error: in CreateInvoiceListEbizOSSReqABCSImplProcess.bpel(84): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}Sender" of variable "Sender" is not defined
    [scac] error: in CreateInvoiceListEbizOSSReqABCSImplProcess.bpel(86): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}EBMHeader" of variable "EBM_HEADER" is not defined
    [scac] error: in CreateInvoiceListEbizOSSReqABCSImplProcess.bpel(530): XML element "{http://schemas.xmlsoap.org/ws/2003/03/addressing}EndpointReference" of variable "EndpointReference" is not defined
    [scac] error: location {ns:composite/ns:wire/ns:target.uri[.='CreateInvoiceListEbizOSSReqABCSImplProcess/CreateInvoiceListEbizOSSReqABCSImpl']}(66,21): Source callback port type for "CreateInvoiceListEbizOSSReqABCSImpl" does not match target callback port type for "CreateInvoiceListEbizOSSReqABCSImplProcess".
  • 2. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    I still havn't resolved this problem
    I have further investgated the error:
    Error(84): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}Sender" of variable "Sender" is not defined
    I followed the chain of dependicies that lead to it's definition:

    composite.xml has:
    <import
    namespace="http://xmlns.oracle.com/EnterpriseServices/Core/Invoice/V2"
    location="InvoiceEBSRef.wsdl"
    />

    InvoiceEBSRef.wsdl has:
    <import
    namespace="http://xmlns.oracle.com/EnterpriseServices/Core/Invoice/V2"
    location="oramds:/apps/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/Invoice/V2/InvoiceEBSV2.wsdl"
    />

    oramds:/apps/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/Invoice/V2/InvoiceEBSV2.wsdl has:
         <xsd:import
              namespace="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2"
              schemaLocation="../../../../../EnterpriseObjectLibrary/Core/Common/V2/Meta.xsd"
         />

    oramds:/apps/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Common/V2/Meta.xsd has:
    <xsd:include schemaLocation="../../../Infrastructure/V1/Meta.xsd"/>

    oramds:/apps/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Infrastructure/V1/Meta.xsd has:
    <xsd:element name="Sender" type="SenderType"/>


    I can't understand where the 'is not defined' error is coming from.
    Can anyone help?
    Robert
  • 3. Re: Composite errors after upgrade to 11.1.1.5.0
    781423 Explorer
    Currently Being Moderated
    check your adf-config.xml and connections.xml file content under your <composite folder>/.adf/META-INF folder and make sure they are pointing to the right mds repository.
  • 4. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    Hi,
    My connectinox.xml is as follows:
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <References xmlns="http://xmlns.oracle.com/adf/jndi"/>

    and my adf-config.xml is as follows (password removed):
    <?xml version="1.0" encoding="UTF-8" ?>
    <adf-config xmlns="http://xmlns.oracle.com/adf/config"
    xmlns:adf="http://xmlns.oracle.com/adf/config/properties"
    xmlns:sec="http://xmlns.oracle.com/adf/security/config">
    <adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
    <adf-property name="adfAppUID"
    value="RJMAIATEST101.uk.ac.uk.dev.rjm.rjmaiatest101"/>
    </adf:adf-properties-child>
    <adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
    <mds-config xmlns="http://xmlns.oracle.com/mds/config">
    <persistence-config>
    <metadata-namespaces>
    <namespace metadata-store-usage="mstore-usage_1" path="/soa/shared"/>
    <namespace metadata-store-usage="mstore-usage_2"
    path="/apps/AIAMetaData"/>
    </metadata-namespaces>
    <metadata-store-usages>
    <metadata-store-usage id="mstore-usage_1">
    <metadata-store class-name="oracle.mds.persistence.stores.file.FileMetadataStore">
    <property value="${oracle.home}/integration"
    name="metadata-path"/>
    <property value="seed" name="partition-name"/>
    </metadata-store>
    </metadata-store-usage>
    <metadata-store-usage id="mstore-usage_2">
    <metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
    <property value="DEV_MDS" name="jdbc-userid"/>
    <property value="*********" name="jdbc-password"/>
    <property value="jdbc:oracle:thin:@//ictdbs38.ad.ic.ac.uk:1530/WLSDEV2"
    name="jdbc-url"/>
    <property value="soa-infra" name="partition-name"/>
    </metadata-store>
    </metadata-store-usage>
    </metadata-store-usages>
    </persistence-config>
    </mds-config>
    </adf-mds-config>
    <sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
    <CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
    credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
    </sec:adf-security-child>
    </adf-config>

    I think that adf-config is correct. I have experimented by putting in the wrong password or port and I get a diffrent error message when I compile:

    Since I then change it to the correct password it then gives the origionial errors. This shows that the server setup is correct.

    looking at adf config could it be something to do with this part of the file:
    <sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
    <CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
    credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
    </sec:adf-security-child>

    is there some kind of security that is causing this compiler error?
  • 5. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    Hi,
    I don't think it is a problem with adf-config because the ReqTransport, EBS and ProvTransport composites all compile and deploy properley.
    It's only the ABCS's that fail with the same errors.
    I have tried other ABCS's from another project and they fail as well with exactly the same error messages.
    Robert
  • 6. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    Some more information I have found.

    If I go into the ABCS Providor's BPEL and create a variable I am able to select Element and click the magnifying glass
    Under Type Explorer I can select Partner Links->CreateInvoiceListEbizProvABCSImpl->CreateInvoiceListEbizProvABCSImpl.wsdl
    ->Inline Schemas->schema->
    I then get a list of elements. On this list I can confirm that
    Sender, Endpointreference and EBMHeader are all present

    Taking a diffrent route (Going into CreateInvoiceListEbizTransportProv2.wsdl) I can also see that ICXREF_LinkResult is present.

    So I have confirmed that JDeveloper CAN see all these types. But when JDeveloper tries to compile the composite it gets errors saying that they are not defined:
    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(75): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}Sender" of variable "Sender" is not defined
    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(77): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}EBMHeader" of variable "EBM_HEADER" is not defined
    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(443): XML element "{http://schemas.xmlsoap.org/ws/2003/03/addressing}EndpointReference" of variable "EndpointReference" is not defined
    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(620): XML element "{http://ic.ac.uk/AIAMetaData/AIAComponents/ApplicationObjectLibrary/IC_ABM_COMMON}ICXREF_LinkResult" of variable "LinkXRefReturn" is not defined

    My JDeveloper application server connectino uses the same database details.
    I have checked my SOA-MDS connection and the connect string it uses (jdbc:oracle:thin:@ictdbs38.ad.ic.ac.uk:1530:WLSDEV2) is exactly the same as what is in my adf-config file. Same username and password!

    Does anyone know of anything else I can check?
    Robert
  • 7. Re: Composite errors after upgrade to 11.1.1.5.0
    781423 Explorer
    Currently Being Moderated
    Your JDev is able to see artifacts and your composite while deploying is not able to see them, Just to rule out can you change
    from <namespace metadata-store-usage="mstore-usage_2" path="/apps/AIAMetaData"/>
    to <namespace metadata-store-usage="mstore-usage_2" path="/apps"/>
    in the mds config file and check.
  • 8. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    Hi,
    I have made this change to the adf-config
    The ABCS still do not rebuild and the error messages are the same.
    Robert
  • 9. Re: Composite errors after upgrade to 11.1.1.5.0
    780756 Explorer
    Currently Being Moderated
    Hi,

    Lets debug it!!


    [scac] error: location {ns:composite/ns:wire/ns:target.uri[.='CreateInvoiceListEbizProvABCSImplProcess/CreateInvoiceListEbizProvABCSImpl']}(77,21): Source callback port type for "CreateInvoiceListEbizProvABCSImpl" does not match target callback port type for "CreateInvoiceListEbizProvABCSImplProcess".

    The issues lies with either of the following
    +1)composite.xml in <wire></wire>. Check the source.uri and target.uri are correct.+
    +2)CreateInvoiceListEbizProvABCSImpl..componentType file - As u said its fire & forget interface and there will not be any callback port for the same. So remove the callback interface reference if any.+


    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(620): XML element "{http://ic.ac.uk/AIAMetaData/AIAComponents/ApplicationObjectLibrary/IC_ABM_COMMON}ICXREF_LinkResult" of variable "LinkXRefReturn" is not defined

    Check variable is defined with right namespace.

    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(443): XML element "{http://schemas.xmlsoap.org/ws/2003/03/addressing}EndpointReference" of variable "EndpointReference" is not defined

    Check the variable is defined      <variable name="EndpointReference"
    +          element="wsa:EndpointReference"/>+

    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(77): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}EBMHeader" of variable "EBM_HEADER" is not defined

    Check the variable is defined
    +<variable name="EBM_HEADER" element="corecom:EBMHeader"/>+

    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(75): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}Sender" of variable "Sender" is not defined

    Check the variable is defined
    +<variable name="Sender" element="corecom:Sender"/>+

    Please try the above workarounds and let us know.

    Regards,
    Rahul
  • 10. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    Rahul,
    Thank you for your response.

    I have managed to resolve one of the five errors.
    [scac] error: location {ns:composite/ns:wire/ns:target.uri[.='CreateInvoiceListEbizProvABCSImplProcess/CreateInvoiceListEbizProvABCSImpl']}(77,21): Source callback port type for "CreateInvoiceListEbizProvABCSImpl" does not match target callback port type for "CreateInvoiceListEbizProvABCSImplProcess".

    I removed the callback from the componentype file and this error is no longer appearing.

    You have suggested that for the varaible "X" is not defined error I
    Check the variable is defined and is the correct namespace.

    In the BPEL's the variables are defined:
    <variable name="SystemFaultMsg" messageType="bpelx:RuntimeFaultMessage"/>
    <variable name="SystemID" type="xsd:string"/>
    <variable name="Sender" element="corecom:Sender"/>
    <variable name="Title" type="xsd:string"/>
    <variable name="EBM_HEADER" element="corecom:EBMHeader"/>
    <variable name="InstanceID" type="xsd:string"/>
    <variable name="ServiceName" type="xsd:string"/>
    <variable name="TraceLogEnabled" type="xsd:boolean"/>
    <variable name="Invoke_1_CreateInvoiceList_OutputVariable"
    messageType="ns3:replyMessage"/>
    <variable name="InvokeCreateInvoiceListEbizTransportProv2_CreateInvoiceList_InputVariable"
    messageType="ns3:requestMessage"/>
    </variables>

    You can see Sender, and EBM_HEADER in this snippit, EndpointReference and ICXREF_LinkResult are scope level variables defined at other locations in the BPEL.

    I have been trying to trace the Sender variable to ensure it is defined.
    From the definition I can see it is defined as type corecom:Sender
    the corecom namespace is mentioned at the top of the BPEL document:
    xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2"

    and this namespace matches the namespace in the error message.

    So now I must confirm that an element Sender exists in the "http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2" namespace.

    To do this I have followed the following logic,
    starting from composite.xml I note it has an import as follows:
    <import
    namespace="http://xmlns.oracle.com/EnterpriseServices/Core/Invoice/V2"
    location="InvoiceEBSRef.wsdl"
    />

    InvoiceEBSREF.wsdl is a file in my composite. Looking at it I see:
    <import
    namespace="http://xmlns.oracle.com/EnterpriseServices/Core/Invoice/V2"
    location="oramds:/apps/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/Invoice/V2/InvoiceEBSV2.wsdl"
    />

    This goes to the MDS for the InvoiceEBSV2.wsdl. I have my JDeveloper connection set up to connect to the same MDS as adf-config has, and I have traced down the path exactly as above to find InvoiceEBSV2.wsdl and confirmed it exists. It has the following line:
    <xsd:import
    namespace="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2"
    schemaLocation="../../../../../EnterpriseObjectLibrary/Core/Common/V2/Meta.xsd"
    />

    Again I can trace through MDS to find Meta.xsd and it has:
    <xsd:include schemaLocation="../../../Infrastructure/V1/Meta.xsd"/>

    Moving on to this Meta.xsd file I can find the sender element defined:
    <xsd:element name="Sender" type="SenderType"/>

    Finally I need to confirm that this element is created under the correct schema So I look at it's schema tag:
    <xsd:schema
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:corecomcust="http://xmlns.oracle.com/EnterpriseObjects/Core/Custom/Common/V2"
    xmlns="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2"
    xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing"
    xmlns:xacml-context="urn:oasis:names:tc:xacml:2.0:context:schema:cd:04"
    xmlns:xacml="urn:oasis:names:tc:xacml:2.0:policy:schema:cd:04"
    targetNamespace="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2"
    elementFormDefault="qualified"
    attributeFormDefault="
    unqualified"
    version="2.3">


    In the above I can see: targetNamespace="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2"

    This matches the namespace of the error message.
    I am not 100% sure on the difference between include and import but this is all the AIA delivered stuff so it is not likely that it is wrong.
    All the import statements do say that they are importing the correct namespace.

    So I have traced from composite.xml -> the element and I have not found a reason why this element isn't defined.

    Is this the correct way of checking if an element is defined in a BPEL?
    As I mentioned before JDeveloper does list these elements in the define variable dialog so this would lead me to believe that the elements are properley included.

    Can you suggest any further checks I can do?
    Thanks
    Robert

    Edited by: RobertMetcalf on Jun 1, 2011 9:39 AM
  • 11. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    I am still struggling with this issue.
    I have replicated it on a second development enviroment.
    I can't think of anything else to try to remove the error:

    H:\JDev_ADF_SOA\mywork\RJMAIATEST101\CreateInvoiceListEbizProvABCSImpl\CreateInvoiceListEbizProvABCSImplProcess.bpel
    Error(75): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}Sender" of variable "Sender" is not defined

    Does anyone have any thoughts?
  • 12. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    I have found some further information.
    The main SOA tab in JDeveloper shows this:
    Buildfile: C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\jdeveloper\bin\ant-sca-compile.xml

    scac:
    [scac] Validating composite "H:\JDev_ADF_SOA\mywork\RJMAIATEST101\CreateInvoiceListEbizProvABCSImpl\composite.xml"
    [scac] Setting BPELC option 'classpath' to C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\jdeveloper\lib\aia.jar;C:\oracle\soa\lib\aia.jar;H:\JDev_ADF_SOA\mywork\RJMAIATEST101\CreateInvoiceListEbizProvABCSImpl\SCA-INF\classes
    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(75): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}Sender" of variable "Sender" is not defined
    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(77): XML element "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}EBMHeader" of variable "EBM_HEADER" is not defined
    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(443): XML element "{http://schemas.xmlsoap.org/ws/2003/03/addressing}EndpointReference" of variable "EndpointReference" is not defined
    [scac] error: in CreateInvoiceListEbizProvABCSImplProcess.bpel(620): XML element "{http://ic.ac.uk/AIAMetaData/AIAComponents/ApplicationObjectLibrary/IC/V1/IC_ABM_COMMON}ICXREF_LinkResult" of variable "LinkXRefReturn" is not defined

    BUILD FAILED
    C:\oracle\products\JDeveloper_ADF_SOA\Middleware_11_1_1_5_0\jdeveloper\bin\ant-sca-compile.xml:269: Java returned: 1 Check log file : H:\JDev_ADF_SOA\mywork\RJMAIATEST101\CreateInvoiceListEbizProvABCSImpl\SCA-INF\classes\scac.log for errors

    Total time: 13 seconds


    When I look at the file it points to I see:
    13-Jun-2011 14:31:16 oracle.adf.share.ADFContext getCurrent
    WARNING: Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
    13-Jun-2011 14:31:22 oracle.fabric.common.wsdl.SchemaManager isIncrementalBuildSupported
    INFO: XMLSchema incremental build enabled.
    13-Jun-2011 14:31:23 com.collaxa.cube.CubeLogger info
    INFO: validating "CreateInvoiceListEbizProvABCSImplProcess.bpel" ...
    oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
         at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
         at oracle.integration.platform.blocks.WLSPlatformConfigurationProvider.<clinit>(WLSPlatformConfigurationProvider.java:44)
         at oracle.integration.platform.blocks.FabricConfigManager.<clinit>(FabricConfigManager.java:155)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXpathFunctions(FabricXPathFunctionResolver.java:271)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXPathConfigFile(FabricXPathFunctionResolver.java:153)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.init(FabricXPathFunctionResolver.java:51)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.loadFabricXpathFunctions(BPELXPathFunctionNameResolver.java:57)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<init>(BPELXPathFunctionNameResolver.java:48)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<clinit>(BPELXPathFunctionNameResolver.java:44)
         at com.collaxa.cube.lang.compiler.bpel.XPathExprValidatorVisitor.<init>(XPathExprValidatorVisitor.java:122)
         at com.collaxa.cube.lang.compiler.bpel.AssignValidator.<init>(AssignValidator.java:89)
         at com.collaxa.cube.lang.compiler.bpel.BpelParser.<init>(BpelParser.java:452)
         at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:60)
         at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
         at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
         at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
         at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
         at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1117)
         at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:500)
         at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
         at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)


    I have googled for UnknownPlatformException but can't find anything useful.
  • 13. Re: Composite errors after upgrade to 11.1.1.5.0
    robert224810 Explorer
    Currently Being Moderated
    I just found a document on Oracle Support that says the oracle.jrf.UnknownPlatformException is a redhearing and it is normal to see it.
  • 14. Re: Composite errors after upgrade to 11.1.1.5.0
    GerhardDrasch(Oracle) Journeyer
    Currently Being Moderated
    Robert,
    I guess it will be very difficult to diagnose this further without having the code. I would recommend you build a package including this composite and the dependend artifacts that need to be in MDS, but that to a public download location, so that we can take a closer look.

    Gerhard
1 2 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points