OSB 11g - JCA transport

Hi,
I have just installed OSB 11g and it seems like JCA transport is not there in the Proxy/Business service - Transport tab.
I have checked OEPE plugins folder and JCA transport folder is empty.
Is this like my installation is not proper or I have to do some configuration for JCA?
I have tried creating a JCA db adapter using 10g Jdev and it didnt work, error message when creating business service is " WSDL contains a tranport not supported".
Please help.
Regards,
AP

Hi all,
I've followed the JCA DB Adapter with OSB tutorial at:
http://www.oracle.com/technology/sample_code/products/osb/index.html
I'm using OSB 11gR1 and JDeveloper 11gR1 11.1.1.3.0 Build JDEVADF_11.1.1.3.PS2_GENERIC_100408.2356.5660
First, the JCA DB Adapter wsdl file generated by JDeveloper using the DB Adapter wizard doesn't carry binding and port information for the wsdl. I've configured a pool table adapter with the DB Adapter wizard.
So I've generated the JCA binding and port manually using the WSDL design view inside JDev.
Next when I try to create a proxy service within OSB, it says that: "The WSDL contains a binding not supported by OSB."
Has anyone faced this before? Hints appreciated...
Here's the WSDL:
<?binding.jca DatabaseInbound_db.jca?>
<wsdl:definitions name="DatabaseInbound" targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/db/DBContent/DBProject/DatabaseInbound" xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/db/DBContent/DBProject/DatabaseInbound" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:top="http://xmlns.oracle.com/pcbpel/adapter/db/top/DatabaseInbound"
xmlns:jca="http://schemas.xmlsoap.org/wsdl/jca/"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<plt:partnerLinkType name="DatabaseInbound_plt">
<plt:role name="DatabaseInbound_role">
<plt:portType name="tns:DatabaseInbound_ptt"/>
</plt:role>
</plt:partnerLinkType>
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/top/DatabaseInbound" schemaLocation="xsd/DatabaseInbound_table.xsd"/>
</schema>
</wsdl:types>
<wsdl:message name="CustomerCollection_msg">
<wsdl:part name="CustomerCollection" element="top:CustomerCollection"/>
</wsdl:message>
<wsdl:portType name="DatabaseInbound_ptt">
<wsdl:operation name="receive">
<wsdl:input message="tns:CustomerCollection_msg"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:service name="DatabaseInbound">
<wsdl:port name="DatabaseInbound_pt"
binding="tns:DatabaseInbound_binding"/>
</wsdl:service>
<wsdl:binding name="DatabaseInbound_binding" type="tns:DatabaseInbound_ptt">
<jca:binding/>
<format:typeMapping encoding="Java" style="Java">
<format:typeMap typeName="top:CustomerCollection" formatType=""/>
</format:typeMapping>
<wsdl:operation name="receive">
<jca:operation methodName="receive" InteractionSpec=""/>
<wsdl:input>
<jca:header/>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>

Similar Messages

  • OSB 11g JCA

    The JCA Transport page of this editor contains an error which must be resolved.

    duplicate post -
    OSB11g Workbench JCA Transport page error
    Regards,
    Anuj

  • OSB 11g - FTP Transport - Active or Passive connections?

    Hi,
    When we create a Proxy Service in OSB to use FTP transport, which type of connection OSB establishes with the server? Is it active FTP or passive FTP conecction?
    Thanks,
    Sanjay
    Edited by: Sanjay Bharatiya on 20-Dec-2010 11:46 AM

    OSB uses passive mode for proxy services and active mode for business services. There is a patch available which will make both proxy and business services to use passive mode. If you need the patch please open a Service Request in MyOracle Support and mention the support Note (860423.1)
    Passive mode is desired if you want to open the firewall ports, if any, from OSB server to FTP server only and not other way from FTP Server to OSB server.

  • Is OSB 11g MQ Transport certified to use with  MQ 7.0 client libraries?

    Hi,
    Could you please point me to the OSB MQ transport certification page? I would like to find out if I could copy MQ 7.0 client libraries to OSB\lib folder
    Thank you

    interesting question...
    here http://docs.oracle.com/cd/E21764_01/doc.1111/e15867/interop.htm#OSBAG1403
    they say
    IBM WebSphere MQ 5.3, 6.0, *7.0 server support with 6.x client libraries*
    I vaguely remember having used the 6.0 jars to connect to MQ 7, but I believe that even using the 7.0 jars would work.... don't quote me on this...

  • OSB 11g - SB transport using Soap1.2

    Hi all
    I am trying to build a proxy service after converting a wsdl from soap1.1 to soap1.2.
    Problem: The proxy service was working fine with 4 operations, SB transport and soap1.1 , however as soon as I moved it to Soap1.2 the OperationalBranch is not behaving correctly i.e. the request is not routed to correct branch - and it always goes to the default branch.
    Here are few things about the wsdl I have:
    a) There are 4 operations in it so I am using OperationalBranch in my proxy service which is at the first node of my proxy service
    b) The proxy is 'SB' transport based.
    c) The selection algorithm for operation is SOAPAction Header.
    Here is what i did to change the wsdl to soap1.2:
    1. Added xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"  at the wsdl:definitions at the top.
    2. Added soapActionRequired="true" in the soap12:operation at wsdl:binding.
    Regards
    Jags

    Hi all
    I am trying to build a proxy service after converting a wsdl from soap1.1 to soap1.2.
    Problem: The proxy service was working fine with 4 operations, SB transport and soap1.1 , however as soon as I moved it to Soap1.2 the OperationalBranch is not behaving correctly i.e. the request is not routed to correct branch - and it always goes to the default branch.
    Here are few things about the wsdl I have:
    a) There are 4 operations in it so I am using OperationalBranch in my proxy service which is at the first node of my proxy service
    b) The proxy is 'SB' transport based.
    c) The selection algorithm for operation is SOAPAction Header.
    Here is what i did to change the wsdl to soap1.2:
    1. Added xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"  at the wsdl:definitions at the top.
    2. Added soapActionRequired="true" in the soap12:operation at wsdl:binding.
    Regards
    Jags

  • JCA transport not visibible in OSB

    I am using OSB 11.1.16 on Win 7
    I do not have a JCA transport available in the drop-down; after a search of forums I saw it stated that you may need this plugin below
    $OSB_home\eclipse\plugins\*com.bea.alsb.transports.jca_1.1.0*
    Where can I find the plug in? or any other ideas of resolving this issue?

    This plugin is not getting installed as part of the regular install which completes without error. Is there anywhere to download this? Why does Oracle have such a convoluted process for simply getting the the IDE working correctly?

  • Using DB Adapter for MS SQL Server 2005  SP in OSB 11g.

    Hi All,
    I have a requirement to create a DB Adapter for MS SQL Server Stored Procedure in JDeveloper and export the Adapter file to OSB 11g. I have Created the Adapter and imported it into OSB 11g successfully. Created the Datasource and Connection pool also in console.
    The problem is while trying to execute the created business Service, I am getting the error as below,
    <Oct 26, 2012 12:20:25 PM IST> <Error> <JCATransport> <BEA-381967> <Invoke JCA outbound service failed with application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/Test/CheckAppID/WL_Driver/CheckAppId_WL_Driver [ CheckAppId_WL_Driver_ptt::CheckAppId_WL_Driver(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'CheckAppId_WL_Driver' failed due to: Unimplemented string conversion.
    Conversion of JDBC type to String is not supported.
    An attempt was made to convert a Java object to String using an unsupported JDBC type: .
    ; nested exception is:
         BINDING.JCA-11804
    Unimplemented string conversion.
    My XSD is ,
    <element name="InputParameters">
    <complexType>
    <sequence>
    <element name="application_id" type="int" db:index="1" db:type="INT" minOccurs="0" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    <element name="OutputParameters">
    <complexType>
    <sequence>
    <element name="RowSet0" type="db:RowSet0_RowSet" db:type="RowSet0" minOccurs="0" maxOccurs="unbounded" nillable="true"/>
    <element name="RowSet1" type="db:RowSet1_RowSet" db:type="RowSet1" minOccurs="0" maxOccurs="unbounded" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    <complexType name="RowSet1_RowSet">
    <sequence>
    <element name="RowSet1_Row" minOccurs="0" maxOccurs="unbounded">
    <complexType>
    <sequence>
    <element name="cde" type="int" db:type="INT" minOccurs="0" nillable="true"/>
    <element name="msg" db:type="NVARCHAR" minOccurs="0" nillable="true">
    <simpleType>
    <restriction base="string">
    <maxLength value="255"/>
    </restriction>
    </simpleType>
    </element>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    <complexType name="RowSet0_RowSet">
    <sequence>
    <element name="RowSet0_Row" minOccurs="0" maxOccurs="unbounded">
    <complexType>
    <sequence>
    <element name="aaa" type="boolean" db:type="BIT" minOccurs="0" nillable="true"/>
    <element name="bbb" db:type="NVARCHAR" minOccurs="0" nillable="true">
    <simpleType>
    <restriction base="string">
    <maxLength value="10"/>
    </restriction>
    </simpleType>
    </element>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    I don't know why there is a datatype conversion error.
    Help me in resolving this.
    Regards,
    Nataraj R.

    Hi,
    I believe NVARCHAR is an unsupported type...
    The following document lists the supported data types for SQL Server stored procedures and functions... NVARCHAR is not in the list... :-(
    http://docs.oracle.com/cd/E23943_01/integration.1111/e10231/adptr_db.htm#CHDEBEEE
    Hope this helps...
    Cheers,
    Vlad

  • Problems starting Server on OSB 11g

    Hi Everybody,
    I have a problem, I just installed the Service Bus 11g on Red Hat and I have problems when I start the server.
    I particular first I start the Admin_Server without any exception and then I start the Server but I get this excedption:
    PATH=/app/olg/wlserver-10.3/wlserver_10.3/server/bin:/app/olg/wlserver-10.3/modules/org.apache.ant_1.7.1/bin:/app/jrmc-3.1.2-1.6.0//jre/bin:/app/jrmc-3.1.2-1.6.0//bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_14"
    Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
    BEA JRockit(R) (build R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32, compiled mode)
    Starting WLS with line:
    /app/jrmc-3.1.2-1.6.0//bin/java -jrockit -Xms256m -Xmx512m -Xmanagement -Dcom.sun.management.jmxremote -Djava.rmi.server.hostname=10.31.57.61 -Dcom.sun.management.jmxremote.port=17001 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder -Djava.awt.headless=true -Dweblogic.Name=Server_1 -Djava.security.policy=/app/olg/wlserver-10.3/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/app/olg/wlserver-10.3/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/app/olg/wlserver-10.3/wlserver_10.3 -Dwls.home=/app/olg/wlserver-10.3/wlserver_10.3/server -Dweblogic.home=/app/olg/wlserver-10.3/wlserver_10.3/server -Ddomain.home=/app/olg/bea-olgfwdomain/olgfwdomain -Dcommon.components.home=/app/olg/wlserver-10.3/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/app/olg/wlserver-10.3/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig -Doracle.server.config.dir=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/servers/Server_1 -Doracle.security.jps.config=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/carml -Digf.arisidstack.home=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/app/olg/wlserver-10.3/oracle_common/modules/oracle.ossoiap_11.1.1,/app/olg/wlserver-10.3/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=t3://10.31.57.61:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/olg/wlserver-10.3/patch_wls1033/profiles/default/sysext_manifest_classpath:/app/olg/wlserver-10.3/patch_ocp353/profiles/default/sysext_manifest_classpath weblogic.Server
    [JRockit] Management server started on port 17001, ssl=false, authenticate=false.
    <Dec 1, 2010 1:00:03 PM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>
    <Dec 1, 2010 1:00:05 PM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
    <Dec 1, 2010 1:00:07 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Dec 1, 2010 1:00:07 PM CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Dec 1, 2010 1:00:07 PM CET> <Notice> <Log Management> <BEA-170019> <The server log file /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/logs/Server_1.log is opened. All server side log events will be written to this file.>
    <Dec 1, 2010 1:00:12 PM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Dec 1, 2010 1:00:14 PM CET> <Warning> <Store> <BEA-280101> <The persistent file store "_WLS_Server_1" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
    <Dec 1, 2010 1:00:16 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Dec 1, 2010 1:00:16 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Dec 1, 2010 1:00:23 PM CET> <Warning> <Store> <BEA-280101> <The persistent file store "Reporting-FileStore_Server_1" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
    <Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'ALSB Domain Singleton Marker Application' is not targeted>
    <Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'ALSB Domain Singleton Marker Application' is not targeted>
    <Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'Message Reporting Purger' is not targeted>
    <Dec 1, 2010 1:00:29 PM CET> <Alert> <OSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.>
    <Dec 1, 2010 1:00:30 PM CET> <Warning> <OSB Kernel> <BEA-398316> <Error getting the Result Cache /osb/service/ResultCache because the OSB Coherence Cache Provider has not been initialized.
    Additional error messages at server startup should point to the root cause for this error.>
    <Dec 1, 2010 1:00:30 PM CET> <Warning> <OSB Kernel> <BEA-398315> <Service Result Caching functionality is disabled because the result cache is unavailable.
    Additional error messages at server startup should point to the root cause for this. If you require Service Result Caching functionality, please fix the errors and restart the server.>
    <Dec 1, 2010 1:00:31 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: ftptransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Ftp Transport Provider/elek28]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:31 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: emailtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Email Transport Provider/tbi712]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: filetransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/File Transport Provider/qwi4ym]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: ejbtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/EJB Transport Provider/kyabv]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: tuxedotransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Tuxedo Transport Provider/9oa5mj/APP-INF/lib/tuxedo_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: aldsp_transport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALDSP Transport Provider/i3u01o/APP-INF/lib/aldsp_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: sftptransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/SFTP Transport Provider/d4v5rl]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: wstransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/WS Transport Provider/wuaaoy]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: flow-transport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/FLOW Transport Provider/kgaw7k]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: bpel10gtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/BPEL 10g Transport Provider/7iyhcx]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: jcatransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m], [Extension-Name: wsif, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m], [Extension-Name: JCAFrameworkImpl, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:33 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'JCA Transport Provider' due to error java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType.
    java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType
    at com.bea.wli.sb.transports.jca.JCATransportProvider.loadAdapterList(JCATransportProvider.java:960)
    at com.bea.wli.sb.transports.jca.JCATransportProvider.getInstance(JCATransportProvider.java:80)
    at com.bea.wli.sb.transports.jca.JCATransportAppListener.preStart(JCATransportAppListener.java:16)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType
    at com.bea.wli.sb.transports.jca.JCATransportProvider.loadAdapterList(JCATransportProvider.java:960)
    at com.bea.wli.sb.transports.jca.JCATransportProvider.getInstance(JCATransportProvider.java:80)
    at com.bea.wli.sb.transports.jca.JCATransportAppListener.preStart(JCATransportAppListener.java:16)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: jejbtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JEJB Transport Provider/xyxmad], [Extension-Name: jejbtransport-jar, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JEJB Transport Provider/xyxmad]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:33 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'JEJB Transport Provider' due to error weblogic.management.DeploymentException: .
    weblogic.management.DeploymentException:
    at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
    at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: com.bea.wli.sb.transports.jejb.JEJBTransportAppListener
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:140)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: soatransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/SOA-DIRECT Transport Provider/16k7ar/APP-INF/lib/soa_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2], [Extension-Name: xbusrouting-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Routing' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c], [Extension-Name: xbustransform-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Transform' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3], [Extension-Name: xbuslogging-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Logging' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Test Framework' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: testfwk-l10n, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: testfwk-l10n, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Emergency> <Deployer> <BEA-149259> <Server 'Server_1' in cluster 'Cluster-1' is being brought up in administration state due to failed deployments.>
    Dec 1, 2010 1:00:37 PM oracle.dms.app.ServerInitializer oracle.dms.app.ServerInitializer
    INFO: DMS startup class is not started. DMS runs with reduced functionality.
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Ftp Transport Provider, EJBComponent: ftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.ftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.ftp, the provider URL is null>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Email Transport Provider, EJBComponent: emailtransport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.email. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.email, the provider URL is null>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: File Transport Provider, EJBComponent: filepoll.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.file. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.file, the provider URL is null>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: SFTP Transport Provider, EJBComponent: sftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.sftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.sftp, the provider URL is null>
    <Dec 1, 2010 1:00:41 PM CET> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Dec 1, 2010 1:00:41 PM CET> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    <Dec 1, 2010 1:00:41 PM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster-1.>
    I tried to find something on internet but nothing suitable for me.
    Thanks

    From the error messages it does not seem to find any of the transport related jars (ftp, jca, email, etc..). Looks like there was an issue while creating the domain.
    Can you retry creating the domain and let us know if you are still getting the same error?
    Regards,
    Patrick

  • Cannot create Proxy service with JCA transport

    Hello everyone.
    I have some issues while trying to create ftp service with jca transport. I follow the instruction in this tutorial:
    http://blogs.oracle.com/MarkSmith/entry/osb_and_ftp_adapter_in_11g
    I stuck in Step 4, cannot create proxy service to use JCA file that I created by JDeveloper 11g (11.1.1.5). When I specify jca file for proxy service, a error message returned:
    <ALSB Console> <BEA-494002> <Internal error occured in OSBConsole : Transport exception occurred with the following message:
    Invalid JCA file for JCA proxy service. If you are creating a Proxy from a Business Service, please select a different transport type (for example, http). If not, JCA file must contain JCA activation spec properties.And these are my jca file content that created by JDeveloper:
    <adapter-config name="myJCA_FTP_service" adapter="FTP Adapter" wsdlLocation="myJCA_FTP_service.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
      <connection-factory location="eis/ftp/MyFtpAdapter"/>
      <endpoint-interaction portType="Put_ptt" operation="Put">
        <interaction-spec className="oracle.tip.adapter.ftp.outbound.FTPInteractionSpec">
          <property name="PhysicalDirectory" value="/home/FTP-shared/upload"/>
          <property name="FileType" value="ascii"/>
          <property name="Append" value="false"/>
          <property name="FileNamingConvention" value="osb_%SEQ%"/>
          <property name="NumberMessages" value="1"/>
        </interaction-spec>
      </endpoint-interaction>
    </adapter-config>Is there anyone who had tried to use JCA transport with Ftp adapter already? Please give me a suggestion.
    Any response is appreciated
    Regards, Cuong Pham

    To get to the basics.
    You use GET to read files from an FTP location - This can be done by an OSB proxy service only.
    You use PUT to write files to an FTP location - This can be done by an OSB business service only.
    So forget that you need a proxy service for PUT.

  • Writing a file using ssh in OSB 11g

    Hi
    OSB 11G
    Once I fetch from DB, i am able to write a flat file(delimiter with pipe) using Messaging Service and MFL.
    Now, my requirement is to write using SSH .
    Can anyone let me know how do I configure it in my Business Service?
    Thanks
    Edited by: soauser on Jul 12, 2011 9:08 AM

    OSB supports SSH File Transfer Protocol (SFTP) using SSH version 2 with SFTP transport -
    section "26.5 SFTP Transport" at http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15866/http_poller.htm#i1085854
    If existing options are not sufficient, you may also create custom transport using transport SDK and use that in OSB -
    http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15866/part_tsdk.htm#sthref954
    Regards,
    Anuj

  • SOAP Header based user/password authentication in OSB 11g Proxy Service

    Hi,
    I have implemented SOAP Header based authentication in my OSB 11g Proxy Service.
    In the Security settings of my AnySOAP(Soap 1.1) HTTP Proxy service, I have amde the following changes:
    1.
    In Transport Access Control link, i selected the User predicate, and provided an user already existing on weblogic server with following roles(AppTesters, Monitors, Operators).
    The AuthorizationProvider was XACMLAuthorizer
    2.
    Under Custom Authentication, I selected the Custom User Name and Password option, and provided the below mentiioned xpaths
    User Name XPath: ./*/*:Username/text()
    User Password XPath: ./*/*:Password/text()
    3.
    In Message Access Control link, i selected the User predicate with the same user as mentioned in Transport Access Control link.
    Now, when I am testing this service from OSB Test Console, I am providing the following input.
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:N1="http://abcd.com/common/bodcomponents/transactional/model/1.0/">
    <soap:Header>
    <AuthHeader>
    <N1:Username>userXYZ</N1:Username>
    <N1:Password>passXYZ</N1:Password>
    </AuthHeader>
    </soap:Header>
    <soap:Body>
    <!-- body payload -->
    </soap:Body>
    </soap:Envelope>
    The response is "The invocation resulted in an error: ."
    The OSB server logs show the below error:
    ####<Feb 9, 2011 6:05:42 PM IST> <Error> <OSB Security> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000c92> <1297254942782> <BEA-387082> <Proxy service access denied (proxy: ABCD/Services/Common_HTTP_Proxy, subject: Subject: 0
    )>
    ####<Feb 9, 2011 6:05:42 PM IST> <Error> <OSB Kernel> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000c92> <1297254942782> <BEA-382004> <Failed to process request message for service ProxyService ABCD/Services/Common_HTTP_Proxy: com.bea.wli.sb.security.AccessNotAllowedException
    com.bea.wli.sb.security.AccessNotAllowedException
         at com.bea.wli.sb.pipeline.RouterSecurity.doAccessControl(RouterSecurity.java:136)
         at com.bea.wli.sb.pipeline.RouterSecurity.doAccessControl(RouterSecurity.java:117)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:586)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
         at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
         at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
         at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
         at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Please suggest where I am going wrong in this. I have cross checked the user/pass credentials with what I am giving in the input, and it is perfectly fine.

    I have added the Username and Password as follows, since the namespace declaration was required due to the namespace prefix 'N1' in the XPath
    declare namespace N1="http://abcd.com/common/bodcomponents/transactional/model/1.0/";./AuthHeader/N1:Username/text()
    declare namespace N1="http://abcdp.com/common/bodcomponents/transactional/model/1.0/";./AuthHeader/N1:Password/text()
    I have removed the Message Access Control conditions, have only kept Transport Access Control conditions.
    If i keep the condition in Transport Access Control as "Allow access to everyone", and test with proper credentials in the Username/Password tags in SOAP Header, then it works fine. However, if I try to give an incorrect password in the SOAP Header, it denies the access. So that means the XPaths given for Username/Password are working fine. The OSB logs show the below message
    +####<Feb 10, 2011 12:59:21 PM IST> <Error> <OSB Security> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000ef2> <1297322961536> <BEA-386008> <Message level username/password authentication failed: [Security:090304]Authentication Failed: User weblogic javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic denied>+
    However if i add the condition with predicate as "User" and user name argument as "weblogic", and try to pass the same in the SOAP Header as well with the correct password, it denies the access with below message in the logs.
    +####<Feb 9, 2011 6:05:42 PM IST> <Error> <OSB Security> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000c92> <1297254942782> <BEA-387082> <Proxy service access denied (proxy: ABCD/Services/Common_HTTP_Proxy, subject: Subject: 0+
    +)>+
    +####<Feb 9, 2011 6:05:42 PM IST> <Error> <OSB Kernel> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000c92> <1297254942782> <BEA-382004> <Failed to process request message for service ProxyService ABCD/Services/Common_HTTP_Proxy: com.bea.wli.sb.security.AccessNotAllowedException+
    com.bea.wli.sb.security.AccessNotAllowedException
    at com.bea.wli.sb.pipeline.RouterSecurity.doAccessControl(RouterSecurity.java:136)
    at com.bea.wli.sb.pipeline.RouterSecurity.doAccessControl(RouterSecurity.java:117)
    at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:586)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
    at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
    at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
    at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
    at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

  • OSB 11g Domain Configuration.

    Hello,
    I am having trouble understanding the results of the OSB 11g domain configuration. In creating the domain i have selected the following options:
    Oracle Service Bus OWSM Extension
    Oracle Service Bus Extension - All domain topologies
    Weblogic Advanced Web Services for JAX-RPC Extension
    Oracle WSM Policy Manager
    Oracle JRF
    I have selected the 'all domain topologies' as i wish to end up with an 'AdminServer' (using port 7001) and 'osb_server1' (using port 8011). Everything installs without a problem, its that i just don't understand the outcome. The OSB transport providers and adpaters (FTP, File, Db, AQ, etc) are targeted at both the admin server and the osb managed server. I also notice that the osb console is targeted only at the admin server. The confusion comes from the fact that when i use the OSB console application to create a project which i then test (successfully) it appears to all be deployed and running on the admin server? This is based on the fact that the URL used to invoke the OSB proxy service has to specify the port of the admin server. I would have thought that the url to access the proxy service would have been directed at the managed server?
    Can someone confirm / explain to me what is going on or why it works this way, please?

    The OSB transport providers and adpaters (FTP, File, Db, AQ, etc) are targeted at both the admin server and the osb managed server.Your observation is correct.
    I also notice that the osb console is targeted only at the admin server.Yes. This is by design.
    The confusion comes from the fact that when i use the OSB console application to create a project which i then test (successfully) it appears to all be deployed and running on the admin server?No. This cannot happen. When you activate the configuration, OSB deploys configuration to the managed server.
    This is based on the fact that the URL used to invoke the OSB proxy service has to specify the port of the admin server. I would have thought that the url to access the proxy service would have been directed at the managed server?Are you test console?
    Manoj
    Edited by: Manoj Neelapu on May 24, 2010 9:28 AM

  • OSB 11g help

    hello evey one,
    i have the following question which is very very important to continue my work with OSB 11g.
    i have developed two web services the first takes data from table X and the other one is insert that data to Table Y, and i created a OSB configuration project and OSB project and for now every thing is fine since i can call both web Services useing proxy service from web service client tool.
    what i need is how can i set the OSB to call web service 1 automatically every 1 hour, 1 minute its does matter, and send the data to web service two to be inserted???????
    please help!!!!!

    I suppose you are after a timer transport in OSB here..Please take a look at this article which explains a reference implementation using the weblogic timer service:
    http://blogs.oracle.com/jamesbayer/2007/11/weblogic_scheduling_a_polling.html
    There are some concrete viewpoints that a service bus is not the right place to put in timer facility.. See the discussion at this thread within this forum:
    Re: How to implement in OSB: Scheduling, Timers and Custom properties

  • OSB 11G - Routing with policy and forwarding authentication headers

    Hi there,
    I'm having problems trying to add authentication to some services developed with OSB 11G.
    One of the requirements is that the services authenticate using the "oracle/wss_username_token_service_policy" policy... So far so good...
    My problem now is that one of the services I'm trying to route messages to needs the same authentication as the OSB router... I've tried everything I found but without any success... The headers aren't being propagated...
    I've found out that the header variable has the Authentication segments so I can remove the routing, add a service callout and add the header variable to it.. But this is kind of a hammered solution...
    Is there any other solution that I'm missing?
    Thanks in advance,
    Best Regards,
    Daniel Alves
    Edited by: 863416 on Sep 18, 2012 9:49 AM

    Hi,
    transporting header setting is described here
    Yuan's SOA Blog: Retrieve and pass around http Authorization header with OSB
    but something is missing, I have to set proxy service Authentication  to Basic. But then OSB authenticate inbound request at local scope and I want to authenticate at called web service level. How to do that?

  • SOA BAM Adapter for OSB 11g ?

    Hi,
    I would like to find out if SOA 11g BAM adapter is certified for use with OSB 11g. Please let me know if you have information regarding this.
    Thank you

    pls refer
    https://svgonugu.wordpress.com/2011/10/01/using-bam-adapter-in-osb/
    http://docs.oracle.com/cd/E14571_01/doc.1111/e15866/jca.htm

Maybe you are looking for