Customize OSB proxy endpoint

Hello,
We have a server running OSB and created a simple proxy service. When we access the WSDL it returns the following endpoint.
http://oldname:7001/MyTest/MyProxy
In proxy configuration is only possible changing service endpoint URI from /MyTest/MyProxy. It's not possible setting servername nor port.
Anyone knows where these parameters come from? Maybe hosts? Is possible chaning/setting this server name/port instead of getting from system? I'm asking this question because we already have the name "oldname" in hosts and now we need that this server uses an additional name other than that for OSB.
Thanks
Rogério

Hello Hisaak,
In the previous post I just simplified explanation - we have a cluster setup with two servers and a virtual server name in load balancer called "soadomain". This pool redirects to two servers S1 and S2. The problem is that after install client wants to change the name of the pool from "soadomain" to "osbdomain". The reason why they want this change is because OSB shares these machines with a previous Soa Suite cluster installation and the name change is unavoidable.
My opinion is the same: clients should not take service endpoint from WSDL. The problem is that we created the pool osbdomain, restarted weblogic server and when we call a WSDL from the cluster address it brings the old address in service definition.
In OWSM gateway, for example, I may change the hostname to specify cluster address and redeploy that component, not a hard task.
In Oracle ESB the same: in System Group I may specify the host and port which will be provided to client. Just simple as applying a new setting.
But in OSB? The WSDL in the new URL provides the older endpoint and product documentation does not clarify how this can be changed. As an administrator I don't want to question development approaches, but in this case in particular product does not provide the right address, even if the clients don't take the endpoint from WSDL.
Edited by: user11130232 on 28/09/2009 13:18

Similar Messages

Modify OSB Proxy "HTTPS required" setting through customization file

Is it possible to modify the "HTTPS Required" setting on the OSB Proxy service? We have different settings to be used for different environments like . DEV, IT, UAT, PROD etc
My understanding of the OSB customization is as below, and I get a feeling that its not possible through the customization.
There are 3 types of customizations possible: EnvVariables, FindAndReplaceString, ReferenceType
EnvVariables allows only pre-defined set of variables to be changed thru the customization file. , HTTPS setting is not there in the list.
Allowed variables are listed @ http://docs.oracle.com/cd/E23943_01/admin.1111/e15867/customization.htm
FindAndReplaceString: it’s possible to change the value of the xml elements in the proxy file, but since its boolean value for HTTPS, we cannot use this option, it would replace other settings as well.
ReferenceType: is used to refer to alternate references like xquery or business services in the proxy service.

I know that ALSB used to provide APIs for SOME customizations, monitoring and control of services. I have not tried APIs in OSB for a long time and dont know if the APIs are still the same or if some of them have been deprecated. But I can say that the APIs for customization of end point values will definitely be available.
However, I do not think there will be an API for marking HTTPS as enabled in proxy configuration, that you will need to do using the sbconsole UI or by importing an updated version of service.
You can find the APIs here:
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e15033/toc.htm
http://docs.oracle.com/cd/E23943_01/admin.1111/e15867/app_apis.htm#OSBAG739
If you do need more info then search for ALSB APIs and you will get older docs but they might have more details.

OSB Project redeployment, Proxy endpoint uri not changed

Hi,
We have a problem when redeploying a OSB project with a new proxy Endpoint URI. When we deploy the changed project, through the OSB console Administration->Import, the OSB deployes successfully but still works with the old EndPoint URI ?
On the disk at <domain_home>/osb/config/core/<project>/PollXYZ.proxy.xml we can see that the old EndPoint URI is still present even though all files have a new modified date. When we try change another property, like "all-headers" the changes are reflected sucessfully when redeployed. So it is only the EndPoint URI that is somehow not changeable?
Any ideas?
TIA

No. url is changeable and it works perfectly fine for us. Are you sure the jar which you are deploying has the latest url for sure.
P.S: Post OSB related queries in SOA Suite forum:
SOA Suite

OSB proxy service lookup

I am creating a dynamic route in an OSB proxy service. Is there a way to lookup a proxy service using its "Endpoint URI" ?
Thank you for any help!
Jeff

Thank you both for helpful and correct answers. In the end I addressed the issue by exporting a customization script and running the below xquery on it to generate a route mapping file. My client still passes in the endpoint URI as planned, and the proxy uses that to lookup the physical service name when routing. Not ideal, because I will have to needlessly maintain this file, but it is workable and gets my app moving. At least I can now do my security through a single entry point, which will be much less work than securing each of my many services.
declare namespace tns="ld:ProcessOSBMappings/processOSBCustomizations";
declare namespace cus="http://www.bea.com/wli/config/customizations";
declare namespace xt="http://www.bea.com/wli/config/xmltypes";
let $data := doc('ALSBCustomizationFile.xml')
return
<Mappings>
for $tmp in $data//cus:envValueAssignments[xt:envValueType eq 'Service URI' and xt:owner/xt:type eq 'ProxyService']
return
<Proxy>
<PhysicalPath>{$tmp/xt:owner/xt:path/text()}</PhysicalPath>
<EndpointURI>{$tmp/xt:value/text()}</EndpointURI>
</Proxy>
</Mappings>

Extracting MIME attachment from email using OSB proxy service - email transport

Hi,
I'm reading email messages(multipart/mixed) with attachments(pdf, zip, xml and csv) from MS Exchange Server 2010 using OSB proxy service email transport.I need to save the attachments to a local folder and process one of the attachments, an XML file. Below is the proxy service config.
Proxy Service Configuration (Test1/Proxy Services/GetEmail)
Actions:
General Configuration
Service Type   Messaging Service
Message Type Configuration
Request Message Type
Text
Response Message Type
None
Transport Configuration
Protocol   email
Endpoint URI   mailfrom:mailserver.net:143
Get All Headers   No
Headers
EMAIL Transport Configuration
Email Protocol   imap
Service Account   Test1/Proxy Services/email_acc
Managed Server   WLS_OSB1
Polling Interval   30
Read Limit   2
Pass By Reference   false
Pass Attachments By Reference   false
Post Read Action   move
IMAP Move Folder   processed
Attachments   archive
Download Directory   \\soasup-stor01\Vacancy\test\download
Archive Directory   \\soasup-stor01\Vacancy\test\archive
Error Directory   \\soasup-stor01\Vacancy\test\error
Request Encoding   iso-8859-1
Message Handling Configuration
Transaction Required   Disabled
Same Transaction For Response   Disabled
Content Streaming   Disabled
The polling is working fine. I've encoded the attachment variable to Base64 using a java callout.$attachments/ctx:attachment/ctx:body/ctx:binary-content has been passed as the byte[] input to the java method and the response is captured in $encodedAttachment. I've created a SaveFile BS(file type) with Request Message Type = Binary and Response Message Type = None. I've tried replacing the node ./ctx:binary-content in body variable with encodedAttachment in the request action of the Publish action to call the BS. One file is getting created with contents of the entire email, MIME headers and boundary parts along with the base64 encoded attachments.
<Contents from the created file>
MIME-Version: 1.0
Content-Type: multipart/related; boundary=MIME_Boundary;
type="binary/octet-stream"
--MIME_Boundary
Content-Type: binary/octet-stream
Content-Transfer-Encoding: 8bit
Thanks & Regards,
Samyajit Talukdar
: [email protected]
-----Original Message-----
From: Samyajit Talukdar
Sent: 10 April 2015 14:11
To: MS MLRP Returns
Subject: FW: 22222
Thanks & Regards,
Samyajit Talukdar
: [email protected]
--MIME_Boundary
Content-Type: application/vnd.ms-excel; name="soainfra_v$session.xls"
Content-Transfer-Encoding: base64
Content-Description: soainfra_v$session.xls
Content-Disposition: attachment; filename="soainfra_v$session.xls";
size=25618; creation-date="Thu, 27 Nov 2014 09:56:35 GMT";
modification-date="Fri, 10 Apr 2015 09:28:23 GMT"
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAAQAAAAAAAAAA
EAAAJgAAAAEAAAD+////AAAAAAAAAAD/////////////////////////////////////////////
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAA=
--MIME_Boundary--
If I put a delete action in the request to Publish action for SaveFile BS to delete the $attachments, the created file contains only the email body part and the attachment boundary part is missing.
I've uploaded the OSB log with full trace enabled.
How can I pass the encodedAttachment to the BS for saving the files?
Would iterating through the $aatachment/ctx:attachment give me the individual attachments for saving and processing, as there are separate binary-content refs in them?
Any help to achieve my requirement is highly appreciated.
Thanks in advance.

Hi Manoj,
Thanks for the quick reply to my query.
The thing is, the link you have provided talks more from changing the business Service configurations i.e. the type of the service etc, but the concern is, that the Business Service is already Implemented and hence the change would not be an appropriate option for me.
Please let me know, if any more information is required.
Thanks & Regards,
Anu

How can we call a OSB proxy service from a BPEL process?

Hi,
I want to call a OSB proxy service from a BPEL process. Can you please explain me the procedure?

Get the wsdl of the OSB proxy service and create webservice parnerlink in BPEL based on this wsdl to invoke the service
To form the wsdl url, copy the Endpoint URI configured to the proxy service(just click on the proxy service in the console) from the sbconsole - /ATHGPUM_GlidePathService/ProxyService/ATHGPUM_GlidePathProxyService
Pre append <<protocol://OSB Hostname:OSB Port>> - http://localhost:8000/ and post append with ?WSDL
The final WSDL url look like - http://localhost:8000/ATHGPUM_GlidePathService/ProxyService/ATHGPUM_GlidePathProxyService?WSDL
Regards
Albin I

OSB Proxy service request is echoed

Hi All
When I test my OSB proxy service, the request is being echoed back and the invocation trace just shows "No Service has been invoked, the request is echoed". I have created a Business service for my BPEL process and this is working fine. Only problem is when invoked from the proxy. The call is not even going to the BS. And there is no authentication or security policy attached to any of my services. Can someone please help?
Also, when I put the endpoint of the proxy service into my browser, it shows a Forbidden-403 error
The log file shows access denied exceptions. The trace from the log file is
Failed to process request message for service ProxyService OracleEbizProductServices/ProxyServices/GetOracleProductInventory: 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
Any suggestions on what's going on?
Thanks in advance
Raja

Hi
We saw a similar issue in our environment. Suddenly all the proxy services were denying access. This happened after an IP address change on the servers running WLS Admin and OSB.
By clearing all the temp/cache files on both servers, and ensuring that the WLS Authentication Setting did not 'cache' results we were able to resolve the problem. Obviously we needed to restart the WLSAdmin and OSB managed servers as well.
Hope this helps.
Thanks

OSB Proxy Service routing

Hi,
I have a simple Proxy Service which consumes messages from a remote endpoint queue (source queue). The Proxy Service simply routes consumed messages to a Business Service which puts messages into another remote endpoint queue (destination queue).
When I test passing a message to the Proxy Service using the OSB's Test Console, the Proxy Service routes the message to the Business Service okay where the message is then placed into the remote endpoint queue (destination queue) as expected. But, if I put a message into the remote source queue, I can see that the message gets consumed by the Proxy Service but the message remains as 'pending' and, either the Proxy Service does not route the message to the Business Service or, the Business Service does not put the message into the remote destination queue. What could the problem be?
Thanks in advance for any help on this.

Hello,
Still looking for an answer to this.
Scenario:
When enabled, OSB Proxy Service removes any messages placed in remote endpoint URI queue, but it seems the messages do not flow within the Proxy Service's message flow itself. When the Proxy Service is enabled, the messages in the remote queue get removed but are seen to stay in a 'pending' state. When the Proxy Service is disabled, the messages get put back in the queue. What are the possible reasons as to why messages would not get processed within the Proxy Service's message flow? All the message flow does is, route the messages to a Business service which then sends the messages to another remote endpoint URI queue.
PS: When a message is injected into the Proxy Service via the Test Console, the message flows/routes to Business Service okay without problems so I assume that the problem must lie in the inital remote queue/Proxy Service interface somewhere. Maybe permissions or transaction related issue? But I can't see any hints to anything wrong in configurations or server(s) logs...
Thanks in advance for any help on this.

URGENT: SOAP 1.1 and 1.2 Support in OSB Proxy

Gurus,
My OSB proxy services should support SOAP 1.1 and 1.2 versions. However, WSDL based Proxy service has only one endpoint. (This is the limitation as per an Oracle document.) This endpoint is one which you select while creating a proxy service from WSDL.
Now, as a result, the service is not able to serve both the 1.1 and 1.2 requests.
As a workaround, I've created two proxy services from the same WSDL (which has both the endpoints/bindings).
And, i publish two endpoints to the user.
Is there any way to trick the proxy WSDL (effective WSDL) to have two ports (endpoints) in it ?
If not, what are the best practices to tackle this situation?
Thanks in advance for your help on this.
With regards-
Ashish
Edited by: user570355 on 2012. 9. 24 오후 3:47

Hi Ashish,
I don't think there's a way to trick the proxy but, as you know, soap 1.1 and 1.2 have slightly different envelope formats (e.g. fault handling) so you'll probably need some kind of specific message processing or transformation, sometime in the future, for handling both soap 1.1 and soap 1.2 requests. This makes your approach correct, in my opinion.
Do you have a local proxy for handling service logic?
I think you should follow something similar to this: http://docs.oracle.com/cd/E23943_01/dev.1111/e15866/local.htm#i1075772.
Your minimum configuration - 3 proxies:
SOAP 1.1 Proxy, SOAP 1.2 proxy and a Local Proxy
Using this approach:
*1 -* The Local Proxy should handle Business Service calls, additional logic, etc. You'll probably have to configure this as "Any XML" proxy and use some kind of internal message format (your own schema) because, if you configure it as "Any SOAP", you'll be forced to choose between SOAP 1.1 and SOAP 1.2.
- routes responses from Business Services to the correct SOAP 1.x Proxy
*2 -* For each SOAP 1.x Proxy
- receives soap 1.x messages and transforms them to some kind of internal schema -> routes them to the Local Proxy for processing
- transforms any kind of responses coming from the Local Proxy back to soap 1.x format and routes responses to the client
I hope this can be of any help to you,
Regards,
Filipe

Not receiving MQ custom header (PutDateTime) in OSB Proxy service using MQ

Hi,
I am using OSB 11g and Websphere MQ version 7.0.
I am trying to get PutDateTime header of message which is being polled from MQ through OSB proxy service using MQ transport.
While logging inbound variable i found out that except this put date time header i am getting all other headers.
Please suggest me something to get this header also.
Regards,
Naveen

Hi Anuj,
I am using OSB 11.1.0.3 version.
By MQ client libraries, do you mean com.ibm.mq jar? i have this jar file put in lib section of my OSB home.
Its really happening like when i am trying to log inbound variable for MQ request headers i am not getting put date time in that.
####<Sep 23, 2011 1:40:34 PM IST> <Error> <ALSB Logging> <wcrbtcsinbom222> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <647137b87487c06a:2875c7c7:13290bb7c1c:-8000-000000000000238b> <1316765434885> <BEA-000000> < [RouteToJMSQueue, null, null, REQUEST] inbound>>>>>>>>>>>>>>>: <con:endpoint name="ProxyService$CSPSPrj$EBooking$ProxyServices$AT_MQFrontRunner" xmlns:con="http://www.bea.com/wli/sb/context">
<con:service/>
<con:transport>
<con:uri>mq://CSPS_GCS_DEV_TST?conn=CSPSPrj/EBooking/Utils/MQConnectionResource</con:uri>
<con:mode>request</con:mode>
<con:qualityOfService>exactly-once</con:qualityOfService>
<con:request xsi:type="mq:MQRequestMetaData" xmlns:mq="http://www.bea.com/wli/sb/transports/mq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<tran:headers xsi:type="mq:MQRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
<mq:AccountingToken>FgEFFQAAACrQN1yT42JIgoumKNeOEgAAAAAAAAAAAAs=</mq:AccountingToken>
<mq:ApplicationIdData></mq:ApplicationIdData>
<mq:ApplicationOriginData></mq:ApplicationOriginData>
<mq:BackoutCount>0</mq:BackoutCount>
<mq:CharacterSet>1208</mq:CharacterSet>
<mq:CorrelationId>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</mq:CorrelationId>
<mq:Encoding>546</mq:Encoding>
<mq:Expiry>-1</mq:Expiry>
<mq:Feedback>0</mq:Feedback>
<mq:Format>MQSTR</mq:Format>
<mq:GroupId>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</mq:GroupId>
<mq:MessageFlags>0</mq:MessageFlags>
<mq:MessageId>QU1RIENTUFNfR0NTX0RFVsqwcE4gEaMC</mq:MessageId>
<mq:MessageSequenceNumber>1</mq:MessageSequenceNumber>
<mq:MessageType>8</mq:MessageType>
<mq:Offset>0</mq:Offset>
<mq:OriginalLength>-1</mq:OriginalLength>
<mq:Persistence>0</mq:Persistence>
<mq:Priority>0</mq:Priority>
<mq:PutApplicationName>re MQ\java\jre\bin\javaw.exe</mq:PutApplicationName>
<mq:PutApplicationType>11</mq:PutApplicationType>
<mq:ReplyToQueueName></mq:ReplyToQueueName>
<mq:ReplyToQueueManagerName>CSPS_GCS_DEV_QM</mq:ReplyToQueueManagerName>
<mq:Report>0</mq:Report>
<mq:UserId>SACRBTCSDEFR</mq:UserId>
</tran:headers>
</con:request>
</con:transport>
<con:security>
<con:transportClient>
<con:username><WLS Kernel></con:username>
</con:transportClient>
</con:security>
</con:endpoint>>

OSB: Issue while testing OSB proxy service using SOAPUI

Hi,
I am trying to test an OSB proxy service using SOAPUI.
The below are the steps i have followed in SOAPUI:
1. File->New SOAPUI project
2. Opens the dialog to create REST service
3. Given service endpoint as: http://<osb servername>:<port>
4. Opens dialog to create a REST resource
5. Resource Path/EndPoint is the OSB proxy service end point.
6. HTTP method = POST
The proxy service accepts 'text' input so i have given Media Type as 'text/plain'
But, when i give the request message and run the request. The request is not running. I am not seeing the processing symbol at the bottom right of the SOAP UI request. Whereas i am able to run other services.
Kindly help me resolve this issue.
Thanks,
Kalpana.

your problem:
Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
Loader: oracle.bpel.common:10.1.3
Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
Configuration: <code-source> in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
It happens when server is custom installed, try to reinstall it as full version and problem should disappear otherwise your need another full installation to retrieve and replace orabpel.jar file from (or maybe more)

Adding Jax-RPC Handlers to OSB Proxy Service

Hi All,
I am new to OSB and wanted to know if I can add a Client side (My proxy Service -> external business service) Handler chain to OSB Proxy Services. I know how to add handlers to general webservice. But is there any way to intercept the request by adding handlers to OSB proxy service before it goes to business service?
Any help is highly appreciated.
Thanks,
Swetha

Hi Eric,
Thanks for your response. we are trying to access WSRR( manages end point urls for 7 different environments) and generate the end point dynamically at the design time. As we figured out WSRR is not compatible with OSB we are trying to implement these client side (OSB Proxy service) handlers which would get the dynamic endpoint depending on the environment used. I was able to create the handlers for this and set the jar in the classpath but the client service which should be using these handlers have to have these handlers defined in the deployment descriptor(web.xml) which am unable to see with a OSB project.
Will there be a deployment descriptor(web.xml/webservices.xml) associated with Proxy services on OSB? Or Is there any other way to add custom JAX-RPC Handlers to a proxy service? Or is there any way to connect to WSRR directly?
Thanks,
Swetha

Error while calling secured OSB proxy from BPEL

Hi,
I have a OSB Proxy service to which I have applied OWSM Policy:
oracle/wss_username_token_service_policy
In the Setting:
Process WS-Security Header is set to Yes
While calling this Proxy from BPEL I tried to append binding properties, I tried the following options:
option1:
wsseHeaders=credentials
wssePassword=welcome1
wsseUsername=weblogic
option2:
oracle.webservices.auth.password=welcome1
oracle.webservices.auth.username=weblogic
But neither of them work and I get the following error:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-386200</con:errorCode>
<con:reason>General web service security error</con:reason>
<con:location>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
<Sep 21, 2010 9:49:30 AM PDT> <Error> <OSB Security> <BEA-387022> <An error ocur
red during web service security inbound request processing [error-code: Security
HeaderUnmarshallingError, message-id: 3659922647318344420--645cdd1d.12b2fe0c158.
-7e45, proxy: OSBTest/Proxy Services/PrivatePersonnelDB_PS, operation: null]
--- Error message:
oracle.wsm.security.SecurityException: WSM-00069 : The security header is missin
g.
at oracle.wsm.security.policy.scenario.processor.UsernameTokenProcessor.
verify(UsernameTokenProcessor.java:218)
at oracle.wsm.security.policy.scenario.executor.WssUsernameTokenScenario
Executor.receiveRequest(WssUsernameTokenScenarioExecutor.java:123)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor
.execute(SecurityScenarioExecutor.java:530)
at oracle.wsm.policyengine.impl.runtime.AssertionExecutor.execute(Assert
ionExecutor.java:41)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.executeS
impleAssertion(WSPolicyRuntimeExecutor.java:608)
Truncated. see log file for complete stacktrace
I have even tried to enable HTTP basic Authentication for the service, but did not work.
Any help is highly appreciated.
Thanks.

Hi,
I have applied oracle/wss_username_token_service_policy for my proxy service and trying to test that from OSB Test Console. I am getting below error,
"[OSB Security - OWSM:387253]Failed to initialize Owsm Credential Manager. Please validate the Keystore Configuration"
When i have launched Test Console for this proxy, i have observed in Security part, oracle/wss_username_token_client_policy is appearing. I am not sure why oracle/wss_username_token_client_policy is appearing there when i applied oracle/wss_username_token_service_policy to my proxy service.
Also do i have to need to configure any Keystore for oracle/wss_username_token_service_policy, If so please tell me the process.
If no key store is required where will the credentials be stored.
Thanks
Rajesh

Model/IPolicySet$POLICYSET_STATUS eroor while invoking OSB proxy from BPEL

Hi,
I am calling an OSB proxy from BPEL .While testing the BPEL , i am getting the following error
oracle/wsm/policy/model/IPolicySet.getStatus()Loracle/wsm/policy/model/IPolicySet$POLICYSET_STATUS;
But i have no policies attached in the OSB.
Kindly let me know if any resolution to this issue.
Edited by: Lalit on Mar 18, 2012 11:15 PM

I am getting the same error..
Someone have any idea how to resolve it??
which proxy i need to delete in console and redeploy???
I redeployed my project many times but still same error..

Could not create/access the TopLink Session.While invoking OSB proxy.

Hi,
While testing an OSB proxy ,which uses a multi datasource to connect to a remote database, from the sbconsole.I am getting exceptions and it is not able to create/access the TopLink Session.
I have checked the multi datasource jndi name ,which is correct.
The stack trace which I am getting while invoking the service is posted below:
oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/CRN_CommonServices/SaveTransactionBSV2 [ SaveTransactionBSV2_ptt::SaveTransactionBSV2(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'SaveTransactionBSV2' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
; nested exception is:
JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception.
Missing Property: [DBManagedConnectionFactory.userName].
Make sure the property is set in the interaction (activation) spec by editing its definition in the wsdl.
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:225)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundBindingServiceImpl.invoke(JCATransportOutboundBindingServiceImpl.java:136)
at com.bea.wli.sb.transports.jca.JCAOutboundMessageContext.sendRequestResponse(JCAOutboundMessageContext.java:152)
at com.bea.wli.sb.transports.jca.JCAOutboundMessageContext.send(JCAOutboundMessageContext.java:113)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:464)
at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:82)
at $Proxy76.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:543)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:478)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:544)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:422)
at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:583)
at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatchSync(PipelineContextImpl.java:466)
at stages.transform.runtime.WsCalloutRuntimeStep$WsCalloutDispatcher.dispatch(WsCalloutRuntimeStep.java:1401)
at stages.transform.runtime.WsCalloutRuntimeStep.processMessage(WsCalloutRuntimeStep.java:236)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:866)
at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:866)
at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:866)
at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:191)
at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:75)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:508)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:506)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:505)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:263)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:68)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:125)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:123)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:128)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:441)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:169)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:136)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:572)
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(Unknown Source)
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)
Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/CRN_CommonServices/SaveTransactionBSV2 [ SaveTransactionBSV2_ptt::SaveTransactionBSV2(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'SaveTransactionBSV2' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
; nested exception is:
JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception.
Missing Property: [DBManagedConnectionFactory.userName].
Make sure the property is set in the interaction (activation) spec by editing its definition in the wsdl.
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:619)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:331)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:220)
... 57 more
Caused by: JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception.
Missing Property: [DBManagedConnectionFactory.userName].
Make sure the property is set in the interaction (activation) spec by editing its definition in the wsdl.
at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:473)
at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:216)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:638)
at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:457)
at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:222)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:1001)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:232)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:463)
... 59 more
Caused by: javax.resource.spi.InvalidPropertyException: Missing Property Exception.
Missing Property: [DBManagedConnectionFactory.userName].
Make sure the property is set in the interaction (activation) spec by editing its definition in the wsdl.
at oracle.tip.adapter.db.exceptions.DBResourceException.missingPropertyException(DBResourceException.java:348)
at oracle.tip.adapter.db.DBManagedConnectionFactory.createServerSession(DBManagedConnectionFactory.java:932)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:413)
... 64 more
Looking forward for your help.
Thanks a lot in advance.
Sumit

Have you created XA data source? If yes then make sure that in connection factory you are assigning the JNDI name of data-source in XAdataSource property (NOT in datasource property). Also make sure that your datasource is up and running and you are updating the dbadapter after creating connection factory.
Regards,
Anuj

Customize OSB proxy endpoint

Similar Messages

Maybe you are looking for