Persistence/Transactions inside Service Bus

Does anything different have to be done for a proxy service to recognize persistence and transactions from JMS messages being sent to a Weblogic queue? I have a message flow designed and need to make sure AquaLogic is recognizing/acknowledging persistent transactions. Can AquaLogic automatically recognize these values?

To make sure the transaction is recognized and propagated from the JMS queue to your routing action you need to ensure 2 things:
- use a JMS XA factory for your proxy service
- use QOS exactly-once for ws-callout and routing actions.

Similar Messages

Unable to call BPM process in service bus

Hi,
I am exposing BPM process as webservice. Inside oracle service bus based on bpm process WSDL i am creating business service and proxy service. How to call BPM process? I am trying with sample client which is invoking proxy exported wsdl. But i am always getting echoed request. Any suggestions on how to call BPMProcess inside service bus?
regards,
PV

I am not able to test my proxy using test console .. I am getting following error message
The invocation resulted in an error: .
     <soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Body>
     <soapenv:Fault>
     <faultcode>soapenv:Server</faultcode>
     <faultstring>BEA-380002: CCHL-349940</faultstring>
     <detail>
     <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380002</con:errorCode>
     <con:reason>Hostname</con:reason>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>
     </detail>
     </soapenv:Fault>
     </soapenv:Body>
     </soapenv:Envelope>

Calling Oracle BPM Process Web Service from Oracle Service Bus

Hi
I am using Oracle Service Bus 10gR3.
I have developed simple BPM process through Oracle BPM studio 10.3.1.0.I then followed steps below
1. Create a Process.
2. Expose the Process as a Web Service.
3. Run the project. This starts the Process Execution Engine.
4. Create an ALSB External Resource of type Management Host.
5. Create a second ALSB External Resource for registration.
6. Register the End Point
Until this point everything is fine. Then I created one project through Oracle Service Bus console. Under that created WSDL, Proxy Service and Business Service Folders. I am using the web service created through BPM studio as teh Business Service in SB . I then created one proxy service to route the request to the Business Service.
Finally when I try to test the Proxy Service by launching test console, I get the
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380001</con:errorCode>
<con:reason>INTERNAL SERVER ERROR</con:reason>
<con:location>
<con:node>RouteNode1</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>
I also tried to debug through "Oracle Workshop for WebLogic Version 10.3 " . But I am not getting enough details as to why this is failing.
Please help me . Thanks In advance.
Thanks
Nilay
Edited by: user8950019 on Feb 1, 2010 4:11 AM

Hi,
When im calling wsdl created when BPM exposed as webservice in SOAP-ui, i first hit the startSession
Request is:-
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:exp="http://bea.com/albpm/ExpenseManagement/ExpenseReport">
<soapenv:Header/>
<soapenv:Body>
<exp:startSession>
<password>Employee</password>
<user>Employee</user>
</exp:startSession>
</soapenv:Body>
</soapenv:Envelope>
Response i Get is:-
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:startSessionResponse xmlns:ns1="http://bea.com/albpm/ExpenseManagement/ExpenseReport">
<return>3782hecq1s85h</return>
</ns1:startSessionResponse>
</soapenv:Body>
</soapenv:Envelope
but when i put this sessionId in main request:-
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:exp="http://bea.com/albpm/ExpenseManagement/ExpenseReport">
<soapenv:Header/>
<soapenv:Body>
<exp:expenseReport>
<sessionId>3782hecq1s85h</sessionId>
<reportArg>

<comments>yes</comments>

<costCenter>jaa</costCenter>

<description>aa</description>

<isApproved>y</isApproved>

<items>

<elements>

<amount>700</amount>

<date>?</date>

<description>?</description>

<receiptChecked>?</receiptChecked>
</elements>
</items>

<reviewedBy>?</reviewedBy>

<submitDate>?</submitDate>

<submittedBy>?</submittedBy>

<total>?</total>
</reportArg>
</exp:expenseReport>
</soapenv:Body>
</soapenv:Envelope>
Response coming is :-
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>fuego.lang.ComponentExecutionException: The method 'expenseReport' from class 'xobject.ExpenseReportWebServiceImpl.ExpenseReportServiceInternalAlbpmListenerImpl' could not be successfully executed.</faultstring>
<detail>
<ns1:stackTrace xmlns:ns1="http://xml.apache.org/axis/">fuego.lang.ComponentExecutionException: The method 'expenseReport' from class 'xobject.ExpenseReportWebServiceImpl.ExpenseReportServiceInternalAlbpmListenerImpl' could not be successfully executed.
     at fuego.lang.Invokeable.invokeImpl(Invokeable.java:244)
     at fuego.lang.Invokeable.invokeDynamic(Invokeable.java:188)
     at fuego.lang.Invokeable.invoke(Invokeable.java:160)
     at fuego.soaptype.SoapListener.invokeDynamic(SoapListener.java:104)
     at fuego.lang.Invokeable.invoke(Invokeable.java:160)
     at fuego.fengine.FEngineWebServiceExecutor$2.execute(FEngineWebServiceExecutor.java:133)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
     at fuego.fengine.FEngineWebServiceExecutor$1.run(FEngineWebServiceExecutor.java:65)
     at fuego.component.Message.process(Message.java:576)
     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)
     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
     at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:244)
     at fuego.fengine.FEngineWebServiceExecutor$WebServiceExecutorPrincipal.processBatch(FEngineWebServiceExecutor.java:168)
     at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
     at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
Caused by: java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "jaa"
     at xobject.ExpenseReportWebServiceImpl.ExpenseReportServiceInternalAlbpmListenerImpl.expenseReport(ExpenseReportServiceInternalAlbpmListenerImpl.xcdl:36)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
     at fuego.lang.JavaObject.invoke(JavaObject.java:227)
     at fuego.lang.Invokeable.invokeImpl(Invokeable.java:234)
     ... 21 more
Caused by: java.lang.NumberFormatException: For input string: "jaa"
     at java.lang.NumberFormatException.forInputString(Unknown Source)
     at java.lang.Integer.parseInt(Unknown Source)
     at java.lang.Integer.valueOf(Unknown Source)
     at fuego.util.Conversion.tojava_lang_Integer(Conversion.java:934)
     at fuego.xobject.runtime.ConversionUtilities.fromString(ConversionUtilities.java:56)
     at fuegoblock.xml.XmlElementDeserializer.deserializeElement(XmlElementDeserializer.java:175)
     at fuegoblock.xml.XmlElementDeserializer.deserialize(XmlElementDeserializer.java:81)
     at fuegoblock.xml.DynamicXml.createObjectFrom(DynamicXml.java:160)
     at fuegoblock.xml.DynamicXml.createObjectFrom(DynamicXml.java:119)
     at xobject.ExpenseReportWebServiceImpl.ExpenseReportServiceInternalAlbpmListenerImpl.expenseReport(ExpenseReportServiceInternalAlbpmListenerImpl.xcdl:17)
     ... 28 more</ns1:stackTrace>
<ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">D-113014550</ns2:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
can anyone explain why this error is coming.?
Edited by: user8937128 on May 19, 2010 6:58 AM

Error using the test console of the Oracle Service Bus 11gR1

Hi I am facing a an issue while using the test console of the Oracle Service Bus 11gR1 .
Every time I try to execute a business service or a proxy service I end up getting the following message.
Error Accessing Test Configuration
*"Test Console" service is not running. Contact administrator to start this service.*
In fact to add to my frustration I am unable to execute any of my proxy services from outside clients like SOAPUI as well.
Is anyone else facing this too ??
Also every time the server starts I can see some diagnostic error messages on my Eclipse console.
*[ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.*
Attached the whole log at the end below.
To provide an update on my trouble shooting
1. ) I tried to give the IntegrationAdmin and IntegrationDeployer roles to my admin user. in fact i also tried to give it all the possible privileges.
Result: Still the same error message.
Error Accessing Test Configuration
"Test Console" service is not running. Contact administrator to start this service.
2.) I have already tried to change the following entry <java:alsb-test-console-debug>true</java:alsb-test-console-debug> in my C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\alsbdebug.xml
I am also attaching the file contents here
<java:sb-debug-logger xmlns:java="java:com.bea.wli.debug">
<java:alsb-stages-transform-runtime-debug>false</java:alsb-stages-transform-runtime-debug>
<java:alsb-alert-manager-debug>false</java:alsb-alert-manager-debug>
<java:alsb-credential-debug>false</java:alsb-credential-debug>
<java:alsb-jms-reporting-provider-debug>false</java:alsb-jms-reporting-provider-debug>
<java:alsb-management-credential-debug>false</java:alsb-management-credential-debug>
<java:alsb-management-dashboard-debug>false</java:alsb-management-dashboard-debug>
<java:alsb-management-debug>false</java:alsb-management-debug>
<java:alsb-management-user-mgt-debug>false</java:alsb-management-user-mgt-debug>
<java:alsb-module-debug>false</java:alsb-module-debug>
<java:alsb-monitoring-aggregator-debug>false</java:alsb-monitoring-aggregator-debug>
<java:alsb-monitoring-debug>false</java:alsb-monitoring-debug>
<java:alsb-pipeline-debug>false</java:alsb-pipeline-debug>
<java:alsb-security-wss-debug>false</java:alsb-security-wss-debug>
<java:alsb-service-account-manager-debug>false</java:alsb-service-account-manager-debug>
<java:alsb-service-provider-manager-debug>false</java:alsb-service-provider-manager-debug>
<java:alsb-service-repository-debug>false</java:alsb-service-repository-debug>
<java:alsb-service-security-manager-debug>false</java:alsb-service-security-manager-debug>
<java:alsb-service-validation-debug>false</java:alsb-service-validation-debug>
<java:alsb-test-console-debug>true</java:alsb-test-console-debug>
<java:alsb-transports-debug>false</java:alsb-transports-debug>
<java:alsb-uddi-debug>false</java:alsb-uddi-debug>
<java:alsb-wsdl-repository-debug>false</java:alsb-wsdl-repository-debug>
<java:alsb-wspolicy-repository-debug>false</java:alsb-wspolicy-repository-debug>
<java:alsb-security-encryption-debug>false</java:alsb-security-encryption-debug>
<java:alsb-security-module-debug>false</java:alsb-security-module-debug>
<java:alsb-sources-debug>false</java:alsb-sources-debug>
<java:alsb-custom-resource-debug>false</java:alsb-custom-resource-debug>
<java:alsb-mqconnection-debug>false</java:alsb-mqconnection-debug>
<java:alsb-throttling-debug>false</java:alsb-throttling-debug>
<java:alsb-flow-resource-debug>false</java:alsb-flow-resource-debug>
<java:alsb-flow-transport-debug>false</java:alsb-flow-transport-debug>
<java:alsb-flow-deployment-debug>false</java:alsb-flow-deployment-debug>
<java:alsb-debugger-debug>false</java:alsb-debugger-debug>
<java:alsb-console-debug>false</java:alsb-console-debug>
<java:alsb-result-caching-debug>false</java:alsb-result-caching-debug>
<java:alsb-bpel-debug>false</java:alsb-bpel-debug>
<java:alsb-jca-framework-adapter-debug>false</java:alsb-jca-framework-adapter-debug>
</java:sb-debug-logger>
starting weblogic with Java version:
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\home11g\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server -Ddomain.home=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1 -Dcommon.components.home=C:\Oracle\MIDDLE~1\home11g\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\AdminServer -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\home11g\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\home11g\patch_oepe1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\home11g\patch_ocp353\profiles\default\sysext_manifest_classpath weblogic.Server
<30-Jun-2010 16:22:43 o'clock BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 16.0-b13 from Sun Microsystems Inc.>
<30-Jun-2010 16:22:47 o'clock BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<30-Jun-2010 16:22:48 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<30-Jun-2010 16:22:48 o'clock BST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<30-Jun-2010 16:22:49 o'clock BST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<30-Jun-2010 16:22:49 o'clock BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log00005. Log messages will continue to be logged in C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log.>
<30-Jun-2010 16:22:49 o'clock BST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
<30-Jun-2010 16:22:56 o'clock BST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<30-Jun-2010 16:22:58 o'clock BST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<30-Jun-2010 16:22:58 o'clock BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log00005. Log messages will continue to be logged in C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log.>
<30-Jun-2010 16:23:06 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<30-Jun-2010 16:23:06 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<30-Jun-2010 16:23:59 o'clock BST> <Warning> <JDBC> <BEA-001110> <No test table set up for pool "wlsbjmsrpDataSource". Connections will not be tested.>
<30-Jun-2010 16:23:59 o'clock BST> <Warning> <JDBC> <BEA-001552> <The Logging Last Resource (LLR) data source wlsbjmsrpDataSource will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.>
<30-Jun-2010 16:25:35 o'clock BST> <Alert> <OSB Security> <BEA-387068> <There is no PKI credential mapper provider configured in your security realm. Service key provider management will be disabled. Configure a PKI credential mapper provider if you need service provider support. This is typically the case if you have Oracle Service Bus proxy services with web service security enabled or outbound 2-way SSL connections.>
<30-Jun-2010 16:25:40 o'clock BST> <Warning> <WliSbTransports> <BEA-381917> <MQ Transport could not be registered due to : Missing MQ Library>
[ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log00005. Log messages will continue to be logged in C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log.>
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.128.2.170:7001 for protocols iiop, t3, ldap, snmp, http.>
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "OSB_domain" running in Development Mode>
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
This is really putting me off and its really disappointing to see all these issues in this new release.
How can oracle let a release slip in with such a Major Issue.
Please can any one help or provide a work around atleast.
Regards
Nitin

I guess till version 10gr3.1 you only needed to start one server and it allowed to access both admin and service bus console.Yes, in 11g as well you may access the admin and OSB console by just starting the admin server but in 11g OSB configuration gets deployed on OSB server (managed server) and test service also runs over this server.
Are you saying there is some other server I need to start just for running the test console ????Yes. Managed server osb_server1 needs to be started for deploying, testing and accessing OSB resources.
As If the OSB server was not running how can I check my published services, modify them and do all the bits and pieces after opening the open the service bus console but not just test them???You can modify and save your configuration without staring OSB server but if you will check in change centre then all the changes being done without starting OSB server will remain in partially activated state.
I have been using the service bus for 3 years and I have never faced any such issue.With each new release you may get new features and with a major release like 11g, architecture and functionality may change.
If it all there is some other server I need to start then whats the process to do so ??Open command prompt. Navigate to $Domain_Home/bin and run command
startManagedWeblogic.cmd <nameOfManagedServer>
for eg. -
D:\OFMW11g\mw\user_projects\domains\ofmw_domain\bin>startManagedWebLogic.cmd osb_server1
Once this server is up and running, try using test console.
Regards,
Anuj

AquaLogic Service Bus and XQuery Mapper

Hi all,
I'm new about using AquaLogic Service Bus and XQuery Mapper. I'm using alsb250_wls920.
To understand better the details I've developed two very simple EJBs stateless related to a generic CarRental scenario.
The idea is the following:
- EJB1 exposes a method for retrieving available cars from company A
- EJB2 exposes a method for retrieving available cars from company B
The method signature is the same:
public CarVO[] getAvailableCars(Category category, Double price)
the only difference is about the CarVO definition where one exposes more attributes than the second one (and also the package is different).
The goal is designing a new proxy service called getAvailableCars that calls the two above services and returns a set including all available cars from both companies.
The returned CarVO is the sum of all attributes from two above CarVOs plus a string company attribute.
So in AquaLogic I've defined:
- a JAR resource for importing my CarRental.jar
- two BusinessService resources related to the two above getAvailableCars services (from company A & B), called getAVISAvailableCars & getHertzAvailableCars;
- I've exported the two WSDLs from the two above BusinessService resources directly from AquaLogic console;
- I've written manually the WSDL 'getAvailableCars' that I use in the next proxy service definition
- a getAvailableCars_1 proxy service resource
Before completing the proxy service definition, I've decided to use XQuery Mapper for defining my trasformations.
But I got some errors when I try to import the WSDLs.
For importing simply I've created a wsdl folder inside my project and copied into it the 3 WSDLs definitions.
Because there are errors in 2 of these WSDLs (getHertzAvailableCars.wsdl, getAvisAvailableCars.wsdl) when I create a XQuery Transformation, I'm not able to select any source schema.
But getHertzAvailableCars.wsdl, getAvisAvailableCars.wsdl have been generated directly from AquaLogic console and I don't understand why XQuery Mapper complains about them.
If needed I can post also the CarRental.zip eclipse prj (that contains the above two EJBs) and CarRentalAqualogicPrj.jar AquaLogic prj (passphrase is aqualogic).
I thank you in advance for any suggestion.
Regards
Patrizio

Could you send me the WSDLS?
My email address [email protected]

Access Oracle Service Bus objects from within a PBL program

Followed instructions from Studio Reference documentation for cataloging Oracle Service Bus objects and embedded sample code but encountered http 404 not found error. Is there anyway to trace the call made to the Service Bus? I change the log message severity level for Workspace application to debug but the call is not logged. The following is the output from the log:
================Oracle® BPM - WorkSpace================
RUNTIME:fuego.papi.exception.ActivityFailedException: Activity '/ExpenseReport#Default-1.0/GlobalCreation[CreateExpenseReport]' task '' could not execute successfully.
RUNTIME:Detail:Method: '', Exception: 'The method 'CIL_createExpenseReportCreateExpenseReportIN' from class 'oracle.ExpenseReport.Default_1_0.Instance' could not be successfully executed.'
RUNTIME:
RUNTIME:     at fuego.papi.exception.ActivityFailedException.create(ActivityFailedException.java:66)
RUNTIME:     at fuego.server.AbstractProcessBean.createActivityFailedException(AbstractProcessBean.java:3561)
RUNTIME:     at fuego.fengine.FEngineProcessBean.createActivityFailedException(FEngineProcessBean.java:371)
RUNTIME:     at fuego.server.AbstractProcessBean.runGlobalActivity(AbstractProcessBean.java:2968)
RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
RUNTIME:     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
RUNTIME:     at java.lang.reflect.Method.invoke(Unknown Source)
RUNTIME:     at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
RUNTIME:     at fuego.lang.JavaObject.invoke(JavaObject.java:227)
RUNTIME:     at fuego.component.Message.process(Message.java:585)
RUNTIME:     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)
RUNTIME:     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
RUNTIME:     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
RUNTIME:     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
RUNTIME:     at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:244)
RUNTIME:     at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
RUNTIME:     at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
RUNTIME:     at fuego.component.CustomExecution.next(CustomExecution.java:176)
RUNTIME:     at fuego.papi.impl.rmi.RMIExecution.next(RMIExecution.java:109)
RUNTIME:     at fuego.web.execution.InteractiveExecution.process(InteractiveExecution.java:177)
RUNTIME:     at fuego.web.execution.impl.WebInteractiveExecution.process(WebInteractiveExecution.java:54)
RUNTIME:     at fuego.web.execution.InteractiveExecution.process(InteractiveExecution.java:223)
RUNTIME:     at fuego.web.papi.TaskExecutor.runApplicationTask(TaskExecutor.java:349)
RUNTIME:     at fuego.web.papi.TaskExecutor.execute(TaskExecutor.java:95)
RUNTIME:     at fuego.workspace.servlet.ExecutorServlet.doAction(ExecutorServlet.java:117)
RUNTIME:     at fuego.workspace.servlet.BaseServlet.doPost(BaseServlet.java:229)
RUNTIME:     at fuego.workspace.servlet.BaseServlet.doGet(BaseServlet.java:220)
RUNTIME:     at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
RUNTIME:     at fuego.workspace.servlet.AuthenticatedServlet.service(AuthenticatedServlet.java:83)
RUNTIME:     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
RUNTIME:     at fuego.web.filter.SingleThreadPerSessionFilter.doFilter(SingleThreadPerSessionFilter.java:64)
RUNTIME:     at fuego.web.filter.BaseFilter.doFilter(BaseFilter.java:63)
RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
RUNTIME:     at fuego.web.filter.CharsetFilter.doFilter(CharsetFilter.java:48)
RUNTIME:     at fuego.web.filter.BaseFilter.doFilter(BaseFilter.java:63)
RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
RUNTIME:     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
RUNTIME:     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
RUNTIME:     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
RUNTIME:     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
RUNTIME:     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
RUNTIME:     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
RUNTIME:     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
RUNTIME:     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
RUNTIME:     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
RUNTIME:     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
RUNTIME:     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
RUNTIME:     at java.lang.Thread.run(Unknown Source)
RUNTIME:Caused by: fuego.lang.ComponentExecutionException: The method 'CIL_createExpenseReportCreateExpenseReportIN' from class 'oracle.ExpenseReport.Default_1_0.Instance' could not be successfully executed.
RUNTIME:     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:519)
RUNTIME:     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:273)
RUNTIME:     at fuego.fengine.FEEngineExecutionContext.invokeMethodAsCil(FEEngineExecutionContext.java:219)
RUNTIME:     at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1280)
RUNTIME:     at fuego.server.execution.TaskExecution.invoke(TaskExecution.java:401)
RUNTIME:     at fuego.server.execution.GlobalTaskExecution.invoke(GlobalTaskExecution.java:146)
RUNTIME:     at fuego.server.execution.TaskExecution.executeCIL(TaskExecution.java:513)
RUNTIME:     at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:697)
RUNTIME:     at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:657)
RUNTIME:     at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:154)
RUNTIME:     at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:116)
RUNTIME:     at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:96)
RUNTIME:     at fuego.server.execution.microactivity.GlobalCreationMicroActivity.execute(GlobalCreationMicroActivity.java:109)
RUNTIME:     at fuego.server.execution.microactivity.GlobalInteractiveMicroActivity.execute(GlobalInteractiveMicroActivity.java:73)
RUNTIME:     at fuego.server.AbstractProcessBean$44.execute(AbstractProcessBean.java:2961)
RUNTIME:     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
RUNTIME:     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
RUNTIME:     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
RUNTIME:     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
RUNTIME:     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
RUNTIME:     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
RUNTIME:     at fuego.server.AbstractProcessBean.runGlobalActivity(AbstractProcessBean.java:2954)
RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
RUNTIME:     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
RUNTIME:     at java.lang.reflect.Method.invoke(Unknown Source)
RUNTIME:     at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
RUNTIME:     at fuego.lang.JavaObject.invoke(JavaObject.java:227)
RUNTIME:     at fuego.component.Message.process(Message.java:585)
RUNTIME:     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)
RUNTIME:     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
RUNTIME:     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
RUNTIME:     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
RUNTIME:     at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:244)
RUNTIME:     at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
RUNTIME:     at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
RUNTIME:Caused by: fuego.lang.RuntimeCILExecutionException: <?xml version="1.0" encoding="UTF-8" ?>
RUNTIME:<string>return code: 404
RUNTIME:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
RUNTIME:<HTML>
RUNTIME:<HEAD>
RUNTIME:<TITLE>Error 404--Not Found</TITLE>
RUNTIME:<META NAME="GENERATOR" CONTENT="WebLogic Server">
RUNTIME:</HEAD>
RUNTIME:<BODY bgcolor="white">
RUNTIME:<FONT FACE=Helvetica><BR CLEAR=all>
RUNTIME:<TABLE border=0 cellspacing=5><TR><TD><BR CLEAR=all>
RUNTIME:<FONT FACE="Helvetica" COLOR="black" SIZE="3"><H2>Error 404--Not Found</H2>
RUNTIME:</FONT></TD></TR>
RUNTIME:</TABLE>
RUNTIME:<TABLE border=0 width=100% cellpadding=10><TR><TD VALIGN=top WIDTH=100% BGCOLOR=white><FONT FACE="Courier New"><FONT FACE="Helvetica" SIZE="3"><H3>From RFC 2068 <i>Hypertext Transfer Protocol -- HTTP/1.1</i>:</H3>
RUNTIME:</FONT><FONT FACE="Helvetica" SIZE="3"><H4>10.4.5 404 Not Found</H4>
RUNTIME:</FONT><P><FONT FACE="Courier New">The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.</p><p>If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.</FONT></P>
RUNTIME:</FONT></TD></TR>
RUNTIME:</TABLE>
RUNTIME:
RUNTIME:</BODY>
RUNTIME:</HTML>
RUNTIME:</string>
RUNTIME:
RUNTIME:     at fuego.components.ScreenFlow.rethrowUserException(ScreenFlow.java:274)
RUNTIME:     at fuego.components.ScreenFlow.propagateParentException(ScreenFlow.java:239)
RUNTIME:     at xobject.Fuego__AutoGen__Screenflows__.__SubmitReport.Begin_Invocator(__SubmitReport.xcdl:13)
RUNTIME:     at oracle.ExpenseReport.Default_1_0.Instance.CIL_createExpenseReportCreateExpenseReportIN(Instance.xcdl:3)
RUNTIME:     at oracle.ExpenseReport.Default_1_0.Instance.CIL_createExpenseReportCreateExpenseReportIN(Instance.xcdl)
RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
RUNTIME:     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
RUNTIME:     at java.lang.reflect.Method.invoke(Unknown Source)
RUNTIME:     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:512)
RUNTIME:     ... 35 more

You are receiving a 404 error which means that the binding to the SB is not correct or there is a problem with the SB end part of the integration.
Are you able to test this successfully from an automatic activity for example aside from trying to use it within a screenflow ?
Thanks !
eduardoc.

Resilience in oracle service bus

HI to all,
I'm getting a problem because i have have a process in oracle service bus, that have a split-join and when a OSB server is shutdown the split-join stop and when the server are started up it don't restart i can i have resilience to overcome this problem.
Best Regards

Hi,
Documentation states:
Split-Joins provide support for propagating transactions. Operations set with a QoS of Exactly Once are executed in the transaction. Operations set with a QoS of Best Effort do not execute in the context of a transaction.
Split-Joins do not handle transaction rollback in the case of exceptions. It is the responsibility service component that called the Split-Join to handle transaction exceptions and rollback.
The last statement is quite difficult to understand... I believe you need to handle a fail in the caller of the split join and possibly do a retry from there... The split join won't restart by itself...
Ref doc...
http://docs.oracle.com/cd/E28280_01/dev.1111/e15866/tasks.htm#i1150626
Cheers,
Vlad

Question on installing Oracle Service Bus

Hello
I am new to this so if there is another forum I should write to please let me know.
I am doing a simple development install on my lap top running windows 7 of the last version of OSB but at the end the server does not start. I am using the default derby DB, I do not know its user name or password. I did not install the RCU but some are suggesting that I should. At the end the server does not start and as you can see the error is pointing to an SQL database related problem.
1) Should I install the RCU so it will install the schema that I need ?
2) I dowloaded the RCU but it is 580M !! ? is this correct ? why do I need 580M to isntall a schema ? or am I in the wrong place and I dowloaded the wrong file ?
3) what is the derby user name and password ? how can I access this DB ?
web logic Admin console is running fine
I start the OSB configuration window and I am creating a new domain
I check the following
Oracle Service Bus Extension - Single Server Domain Topology - 11.1.1.3
the following options are also selected, by default:
■ Oracle JRF - 11.1.1.0 [oracle_common]
■ WebLogic Advanced Web Services for JAX-RPC Extension - 10.3.3.0 [wlserver_10.3]
I am continuing the configuration accepting all the default values.
The Database connection testing fails but according to the manual it should fail
at the end I check the start the admin server but there is a problem and the server does not start
Any idea ?
Thank you
Eyal
This is the error message:
####<17:00:19 IDT 13/07/2010> <Notice> <Log Management> <eyal-PC> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1279029619074> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
####<17:00:19 IDT 13/07/2010> <Critical> <WebLogicServer> <eyal-PC> <AdminServer> <main> <<WLS Kernel>> <c5a9d0e4c1e078a4:1c51aa09:129cc1afd41:-7ff3-0000000000000001> <1279029619245> <BEA-000362> <Server failed. Reason: [JTAExceptions:119002]A logging last resource failed during initialization. The server cannot boot unless all configured logging last resources (LLRs) initialize. Failing reason:
javax.transaction.SystemException: weblogic.transaction.loggingresource.LoggingResourceException: java.sql.SQLException: JDBC LLR, table verify failed for table 'WL_LLR_ADMINSERVER', row 'JDBC LLR Domain//Server' record had unexpected value 'base_domain//AdminServer' expected 'eyal//AdminServer'*** ONLY the original domain and server that creates an LLR table may access it ***
####<17:00:19 IDT 13/07/2010> <Notice> <WebLogicServer> <eyal-PC> <AdminServer> <main> <<WLS Kernel>> <c5a9d0e4c1e078a4:1c51aa09:129cc1afd41:-7ff3-0000000000000001> <1279029619256> <BEA-000365> <Server state changed to FAILED>
####<17:00:19 IDT 13/07/2010> <Error> <WebLogicServer> <eyal-PC> <AdminServer> <main> <<WLS Kernel>> <c5a9d0e4c1e078a4:1c51aa09:129cc1afd41:-7ff3-0000000000000001> <1279029619257> <BEA-000383>
####<17:00:19 IDT 13/07/2010> <Notice> <WebLogicServer> <eyal-PC> <AdminServer> <main> <<WLS Kernel>> <c5a9d0e4c1e078a4:1c51aa09:129cc1afd41:-7ff3-0000000000000001> <1279029619260> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Edited by: user_eyal on 07:33 29/07/2010
Edited by: user_eyal on 07:36 29/07/2010

Hi,
Did you create the multiple domains.i observed this when we create multiple domains. Typically seems to be we have to create single MDS schema using RCU for each domain. I have seen this in one of the Manoj posts in this forum thought did not get the link.
you can modify the doamin name in the table WL_LLR_ADMINSERVER by logging into db using mds user. update with expected value as shown in the error.

Service Bus (JNDI look up failed due to: String index out of range: -1)

Good Day!
I have Service Bus 10gR3 at last time i see in log ManagerServer_1 many errors.
<20.11.2013 10:51:04 MSK> <Warning> <JCA_FRAMEWORK_AND_ADAPTER> <BEA-000000> <servicebus:/WSDL/NA_BB_RBO/wsdl/pl_sql/AggregateMsg [ AggregateMsg_ptt::AggregateMsg(InputParameters,OutputParameters) ] - JNDI look
up of 'jca.integro.IntegroDB' failed due to: String index out of range: -1>
DBAdapter configured. JDBC IntegroDB working.
How understand what means this error? That this index means?
I think second error its consequence first.
JCA-11624
DBActivationSpec Polling Exception.
Query name: [GetTimedOut], Descriptor name: [GetTimedOut.AggregatorTimedOutData]. Polling the database for events failed on this iteration. [Caused by: Attempt to resume an inactive transaction: BEA1-572DC7461
E6].
If the cause is something like a database being down successful polling will resume once conditions change. Caused by javax.resource.ResourceException: oracle.tip.adapter.sa.api.JCABindingException: [JCATransprt:381951]JCA inbound request only invocation failed, exception: java.security.PrivilegedActionException: com.bea.wli.sb.transports.TransportException: General runtime error: Attempt to resume an inactive tran
action: BEA1-572DC7461DE6
java.security.PrivilegedActionException: com.bea.wli.sb.transports.TransportException: General runtime error: Attempt to resume an inactive transaction: BEA1-572DC7461DE6
Can some body help me understand this error?

Good Day!
I have Service Bus 10gR3 at last time i see in log ManagerServer_1 many errors.
<20.11.2013 10:51:04 MSK> <Warning> <JCA_FRAMEWORK_AND_ADAPTER> <BEA-000000> <servicebus:/WSDL/NA_BB_RBO/wsdl/pl_sql/AggregateMsg [ AggregateMsg_ptt::AggregateMsg(InputParameters,OutputParameters) ] - JNDI look
up of 'jca.integro.IntegroDB' failed due to: String index out of range: -1>
DBAdapter configured. JDBC IntegroDB working.
How understand what means this error? That this index means?
I think second error its consequence first.
JCA-11624
DBActivationSpec Polling Exception.
Query name: [GetTimedOut], Descriptor name: [GetTimedOut.AggregatorTimedOutData]. Polling the database for events failed on this iteration. [Caused by: Attempt to resume an inactive transaction: BEA1-572DC7461
E6].
If the cause is something like a database being down successful polling will resume once conditions change. Caused by javax.resource.ResourceException: oracle.tip.adapter.sa.api.JCABindingException: [JCATransprt:381951]JCA inbound request only invocation failed, exception: java.security.PrivilegedActionException: com.bea.wli.sb.transports.TransportException: General runtime error: Attempt to resume an inactive tran
action: BEA1-572DC7461DE6
java.security.PrivilegedActionException: com.bea.wli.sb.transports.TransportException: General runtime error: Attempt to resume an inactive transaction: BEA1-572DC7461DE6
Can some body help me understand this error?

Transaction Recovery Service failover

Can anyone explain what the suggested configuration is for the default persistence store? In particular, this is to ensure the proper failover / migration of the Transaction Recovery Service which is required to use the Default Persistence Store which is file based. Based on the following statement from the docs:
Preparing to Migrate the Transaction Recovery Service
To migrate the Transaction Recovery Service from a failed server in a cluster to another server (backup server) in the same cluster, the backup server must have access to the transaction log records from the failed server. Therefore, you must store default persistent store data files on persistent storage available to all potential backup servers in the cluster. Oracle recommends that you store transaction log records on a Storage Area Network (SAN) device or a dual-ported disk. Do not use an NFS file system to store transaction log records. Because of the caching scheme in NFS, files on disk may not always be current. Using transaction log records stored on an NFS device for recovery may cause data corruption.
A SAN storage device is recommended for this but my understanding is that the SAN can only be mounted by one machine at a time. Does this imply then that our failover process needs to include mounting the SAN before starting the failover server (as part of the whole server migration)? The docs here (http://download.oracle.com/docs/cd/E15523_01/core.1111/e12036/net.htm#CIHBDDAA) indicate that a NAS can be used and even give examples of configuring it using NFS mount points:
The following commands show how to share the SOA TX logs location across different nodes:
SOAHOST1> mount nasfiler:/vol/vol1/u01/app/oracle/stores/soadomain/soa_cluster/tlogs
+/u01/app/oracle/stores/soadomain/soa_cluster/tlogs -t nfs+
SOAHOST2> nasfiler:/vol/vol1/u01/app/oracle/stores/soadomain/soa_cluster/tlogs
+/u01/app/oracle/stores/soadomain/soa_cluster/tlogs -t nfs+
Can anyone describe a best-practices approach for how to configure the expected persistent storage solution that will work with proper failover of the transaction recovery service?
Thanks!
Gary

have a look at this article and see if it helps.
http://el-caro.blogspot.com/2008/11/parallel-rollback.html

Implementing Oracle Service Bus - Architectural Question

Hi Experts,
If you were implementing Oracle SOA Suite and were intending on using it to support your legacy file based peer to peer integration solution (Enterprise scale) by utilising file adapters to extract, mediators to transform/route and custom built services to push that data into a transactional system would you look at using an Enterprise Service Bus to implement any of this functionality.
The principle here is to move away from peer to peer into a pseudo SOA solution where semi generic services are developed to accept the data currently sent in the files and sending that into an open interface table in the target system. The seperation of the file handling from the interface service is key to moving towards a service orientated solution.
It has been suggested to me that you could use the ESB to collect the files, extract the data and push it into the services in the SOA middleware. This is as opposed to building the file polling applications as composite applications in Oracle SOA suite.
Any thoughts would be appreciated on either of these approaches.
Thanks
K

there is no "one size fits all" SOA, you must evaluate the complexity of your interfaces and see whether it's worth having a 2 layers approach (OSB + SOA Suite) or condensating all in SOA Suite (or, why not, ditching the heaviness of SOA Suite and use only OSB)
Anyway on the "OSB vs SOA Suite" topic people have already written caterpillions of posts
http://www.javamonamour.org/2010/11/osb-vs-soa-suite.html
very popular is this http://www.slideshare.net/gschmutz/oracle-soa-suite-11g-mediator-vs-oracle-service-bus-osb

Service Bus Auditing

Hi there,
We are using Windows Server Service Bus 1.1 to distribute some sensitive information and would like to implement some sort of auditing around the bus. As far as we understand, Service bus does not provide any form of auditing out of the box and does not
generate any logs (would be happy if someone corrects me here)
One way of auditing the payload is using "ForwardTo" auditing subscription to write to an audit topic but this does not tell us "who" sent the message. We can harness custom message properties but then it means we rely on the client to
provide us this information. We can use a separate WCF logging service but then i would have to worry about distributed transactions.
Is this audit information available in any form am not aware of, any events that we could possibly intercept?
Any pointers will be appreciated. Thanks in advance.
http://btsbee.wordpress.com/

Hi
If you're using Windows Server 2012 or above, you can use the User Access Logging feature (Which SB has opted in) to get the Service Bus Server Access infos. Some cmdlet you could use are Get-UalDailyAccess, Get-UalUserAccess, etc. We're logging
client IPs and user names (if you're using windows auth) to UAL. You should be able to see "Service Bus 1.1" as a product in UAL logs.
For more information about UAL, please visit
http://technet.microsoft.com/en-us/library/hh849634.aspx.
If you're using any OS version below Windows Server 2012, then this feature is not available for you.
Thanks
Jacky

What is SAP ESB (Enterprise Service Bus)?

Hi fellow sdners gurus I have been reading threads about SAP SOA and ESB.
I do not want to start a debate on wether XI is an ESB, but more of a statement to what is SAP ESB (if XI it is, then be it).
1) What is SAP ESB (Enterprise Service Bus) today (I could not find a clear answer to is)?
2) Who uses this SAP ESB in production currently and what kind of environment (i.e. strictly SAP backend systems, or combination of various vendors backend systems)?
Can someone share some light on this topic?
As a reminder, an ESB is expected to exhibit the following characteristics (source Wikipedia):
     It is usually operating-system and programming-language agnostic; for example, it should enable interoperability between Java and .NET applications.
     It uses XML (eXtensible Markup Language) as the standard communication language.
     It supports web-services standards.
     It supports various MEPs (Message Exchange Patterns) (e.g., synchronous request/response, asynchronous request/response, send-and-forget, publish/subscribe).
     It includes adapters for supporting integration with legacy systems, possibly based on standards such as JCA
     It includes a standardized security model to authorize, authenticate and audit use of the ESB.
     To facilitate the transformation of data formats and values, it includes transformation services (often via XSLT or XQuery) between the format of the sending application and the receiving application.
     It includes validation against schemas for sending and receiving messages.
     It can uniformly apply business rules, enriching messages from other sources, the splitting and combining of multiple messages and the handling of exceptions.
     It can provide a unified abstraction across multiple layers
     It can route or transform messages conditionally, based on a non-centralized policy (i.e. no central rules-engine needs to be present).
     It is monitored for various SLA (Service Level Agreement) threshold message latencies and other SLA characteristics.
     It (often) facilitates "service classes," responding appropriately to higher and lower priority users.
     It supports queuing, holding messages if applications are temporarily unavailable.
Your help is greatly appreciated.
Kind Regards,
Jean-Michel

PI or XI is the ESB from SAP side. PI is not a full pledged ESB on a reference model of ESB idea but it is the the framework SAP provide as a ESB product.
A Standard Based ESB Reference Model should fullfil the following features in a framework.
ESB Features    Service Enablement Phase (1, 2, 3)
1)     Message brokering between heterogeneous environments
2)     Supports asynchronous, synchronous, publish and subscribe messaging
3)     Supports synchronous and asynchronous bridging
4)     Supports message formats of SOAP
5)     Support for message format of SOAP with attachments
6)     Support for xml message
7)     Support for structured non-XML data
8)     Support for raw data message
9)     Support for text data message
10)     Sport for e-mail with attachment message
11)     Heterogeneous transports between service end points
12)     Supports for FILE protocols
13)     Supports for FTP protocols
14)     Supports for HTTP protocols
15)     Supports for HTTPS protocols
16)     Supports for Multiple JMS providers
17)     Supports for RMI protocols
18)     Supports for web service protocols
19)     Supports for CORBA protocols
20)     Supports for DCOM protocols
21)     Supports for E-mail (POP, SMTP, IMAP) protocols
22)     Support for advanced transformation engine
23)     Support for configuration-driven routing
24)     Message routing based policies
25)     Support for call-outs to external services to support complex routing
26)     Support for point-to-point routing
27)     Support for one-to-many routing scenarios
28)     Support for request response model
29)     Support for publish-subscribe models
30)     Service monitoring
31)     Service logging
32)     Service auditing with search capabilities.
33)     Support for capture of key statistics for message and transport attributes including message invocations, errors, and performance, volume, and SLA violations.
34)     Supports clusters and gathers statistics across the cluster to review SLA violations
35)     Support for service provisioning
36)     Support deployment of new versions of services dynamically through configuration
37)     Migrates configured services and resources between design, staging and production
38)     Supports multiple versions of message resources that are incrementally deployed with selective service access through flexible routing
39)     Configurable policy-driven security
40)     Supports the latest security standards for authentication, encryption-decryption, and digital signatures
41)     Supports SSL for HTTP and JMS transports
42)     Supports multiple authentication models
43)     Policy-driven SLA enforcement
44)     Establishes SLAs on a variety of attributes including
a.     Throughput times
b.     Processing volumes
c.     Success/failure ratios of message processes
d.     Number of errors
e.     Security violations
f.     Schema validation issues
45)     Initiates automated alerts or enables operator-initiated responses to rule violations using flexible mechanisms including
a.     E-mail notifications
b.     Triggered JMS messages
c.     Triggered integration processes with a JMS message
d.     Web services invocations with a JMS message
e.     Administration console alerts.
46)     Support for having multiple LOBs manage their own service bus based on their policies, and a service bus at an enterprise level that could act as a broker for sharing services across the various business units.
47)     Support for agent plug-in to support following features
48)     External providers service access for security
49)     External providers service management
50)     External providers transaction container
a.     External providers business orchestration (BPEL Engine) and business work flow service container
51)     Transaction support on message level
52)     IDE Integration
53)     Open standards

Issue in deploying Service Bus projects using maven

Hi,
I am following the following documentation for deploying service bus projects to my OSB server.
http://docs.oracle.com/middleware/1213/core/MAVEN/osb_maven_project.htm#MAVEN8973
I was able to issue mvn package as described in documentation and also able to see sbar files in .data/Maven directory of each project.
But i am seeing following error when i issue mvn pre-integration-test. Am i missing any steps.
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ System ---
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-System-1424718369010.
java.io.IOException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'w
eblogic.management.mbeanservers'
        at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.ja
va:237)
        at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.j
ava:120)
        at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:369)
        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
        at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.getJMXConnector(MBeanHel
per.java:228)
        at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.invoke(MBeanHelper.java:
131)
        at com.sun.proxy.$Proxy16.createSession(Unknown Source)
        at oracle.sb.maven.plugin.DeployMojo.createSession(DeployMojo.java:141)
        at oracle.sb.maven.plugin.DeployMojo.execute(DeployMojo.java:89)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j
ava:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter
.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.d
omainruntime'. Resolved 'weblogic.management.mbeanservers' [Root exception is javax.naming.NameNotFo
undException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic
.management.mbeanservers']; remaining name 'domainruntime'
        at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180
        at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:270)
        at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:187)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:210)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:701)
        at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:231)
        at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:527)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:523)

Hi Siva,
I am facing same issue I am bale to create package but while deployment goal I am facing problem.I am following same document as you do.
I can see my mvn-pre-integration ..show me sucees in result
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:3.0.3
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracl
-servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package' with basic configurator -->
[DEBUG]   (f) oracleHome = C:\Oracle\Middleware\Oracle_Home
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG]   (f) system = false
[DEBUG] -- end configuration --
[INFO]
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ TestOSBLinux ---
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
[DEBUG]   (f) oraclePassword = Oracle123
[DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
[DEBUG]   (f) oracleUsername = weblogic
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG] -- end configuration --
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888616161.
[INFO]
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (deploy) @ TestOSBLinux ---
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
[DEBUG]   (f) oraclePassword = Oracle123
[DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
[DEBUG]   (f) oracleUsername = weblogic
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG] -- end configuration --
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888623126.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building LinuxMachine 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-so
rces, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, i
tegration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN ================================================
[DEBUG] Project:       LinuxMachine:LinuxMachine:1.0-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): []
[DEBUG] Repositories (dependencies): [central (https://repo.maven.apache.org/maven2, default, releases)]
[DEBUG] Repositories (plugins)     : [central (https://repo.maven.apache.org/maven2, default, releases)]
[DEBUG] =======================================================================
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] TestOSBLinux ....................................... SUCCESS [ 20.752 s]
[INFO] LinuxMachine ....................................... SUCCESS [ 0.009 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
But not get deployed .....
When i run mvn com.oracle.servicebus.plugin:oracle-servicebus-plugin:deploy** to invoke deployment goal it fails which below logs
org.apache.maven.plugin.MojoNotFoundException: Could not find goal 'deploy*.*' in plugin com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0 amon
goals deploy, package
        at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:275)
        at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:239)
        at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:233)
        at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:103)
        at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:83)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:85)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR]
[ERROR]
Thanks&Regards
Prabhat

How to log the exception using Log action in Oracle Service Bus

Hi,
Whenever an exception is raised how to log the exception using Log action in oracle service bus.After logging where I have to find the logged message.

It would be in the log file for the managed server which ran the request. If you are logging the message at a lower level than your app server, however, you won't see it. You should be logging the exception at Error level.

Persistence/Transactions inside Service Bus

Similar Messages

Maybe you are looking for