The AQ Service Bus showme a bad wsdl ( soap:address location )from internet

Hi,
first of all, excuse my bad english :-)
I've a problem when I tray to get a wsdl file from Internet.
In Aqualogic I've configured a wsdl file with the next content:
<wsdl:service name="EmailValidation">
<wsdl:port binding="tns:EmailValidationSoap" name="EmailValidation">
<soap:address location="http://www.axonaxis.cl:7001/email"/>
</wsdl:port>
</wsdl:service>
This file is reference from a proxy service.
when I try to get the wsdl file from a browser, showme this:
<service name="EmailValidation">
<port binding="s0:EmailValidationSoap" name="EmailValidation">
<s1:address location="http://server2005:7001/email"/>
</port>
</service>
From a browser, put in "location" the server name (of course, if I try to execute the proxy service, the server not found).
Why is doing this? How can I solve this problem?
I don't have much experience in this so try to help me.
Thank you very much (Muchas gracias!)

ARCHIVO HOST!!!!

Similar Messages

WSDL soap:address location

Having developed/tested my soap services they are almost ready for shipping as a product.
However, in the WSDL the <soap:address location=""> tag is set to my server - as used in development.
So when I deploy this EAR file from JDev (9.0.5.2) this value is fixed, and will not work for customers.
Is there anyway to make this value dynamic on deployment by customers or am I stuck with having to find out in advance customers server/port settings and then creating individual release per customer?
I have tried using a relative url but this doesnt always work for clients trying to connect, e.g.:
<soap:address location="/webservices/booking"/>
Thanks in advance for any assistance.

For now I have written a program, that is run after deployment. This program edits the web.xml and allows customers to specify the server name and port they are using.
Anyone else have any solutions to this?

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

How is licensed the Oracle Service Bus? wasnt it part of the SOA Suite?

Why
it is not clear for us how the oracle service bus is licensed, in terms that we thought it was included on the Oracle SOA Suite , we are referring to newer releases
is it licensed a part from the soa suite?
Thanks!

thanks!
so just to put it clear, In case in which we are licencing both weblogic an soa suite the enterprise edition the OSB is included on the licence fee right?
3.2 Oracle Service Bus
Oracle Service Bus is a lightweight SOA integration platform, or "enterprise service bus". Oracle Service Bus includes Oracle SOA Suite Adapters (see Chapter 5, "Oracle Fusion Middleware Adapters").
Oracle Service Bus is licensed as an option to Oracle WebLogic Suite and is also included in Oracle SOA Suite for Oracle Middleware and Oracle Mobile Suite. Users running Oracle SOA Suite for Oracle Middleware on WebLogic Server Basic may not run Oracle Service Bus (see Section 3.5, "Oracle SOA Suite for Oracle Middleware and Oracle BPEL Process Manager Option Licensing with Oracle Internet Application Server").
Prerequisite: A license to Oracle WebLogic Suite is a prerequisite to license and use Oracle Service Bus.

Change SOAP Address Location in the WSDL

When deploying a BPEL service the SOAP Address location is automatically generated to have the
http://{SERVER}:{PORT} of the SOA server where you are deploying the service but i need to have a different address location.
I basically needs this because we have a load balancer and firewall restrictions for any external third party that want to invoke our service.
So the WSDL URL we give to the third party who want to invoke our service will be
https://loadbalancer/orabpel/default/TestService/1.0/TestService?wsdl
instead of
http://soasever:soaserveport/orabpel/default/TestService/1.0/TestService?wsdl
The loadbalancer will then strip of the https connection and send it as http request to the SOA server.
So the third party is now able to access the WSDL but he is having issues while invoking the service as the SOAP address location is still having our SOA server name
Any ideas?

This can be achieved through dynamic partner linking.
http://download.oracle.com/docs/cd/E19509-01/821-0017/cnfg_bpel-se-dynamic-ptnrlink_c/index.html
HTH
-ND

Oracle Service Registry: UDDI API v3 WSDL returns unknown-location-uri

Hi,
I've tried to access the UDDI API v3 wsdl and it's showing unknown-location-uri for all 3 APIs (security, publication, inquiry). I've tried updating tModels related to these 3 APIs and the results are the same. Does anyone know how to make it return a valid address location?
WSDL link: http://192.100.1.1:8021/registry/uddi/doc/wsdl/uddi_api_v3.wsdl
Result:
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="UDDI_API_V3" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:api_v3_binding="urn:uddi-org:api_v3_binding" xmlns:tns="urn:uddi-org:api_v3" targetNamespace="urn:uddi-org:api_v3">
<documentation>Copyright 2001-2005 Systinet Corp. All rights reserved. Use is subject to license terms. WSDL SOAP/HTTP binding for UDDI V3 Security, Publication and Inquiry APIs.</documentation>
<import namespace="urn:uddi-org:api_v3_binding" location="uddi_api_v3_binding.wsdl" />
- <service name="UDDI_Security_SoapService">
- <port name="UDDI_Security_PortType" binding="api_v3_binding:UDDI_Security_SoapBinding">
<soap:address location="urn:unknown-location-uri" />
</port>
</service>
- <service name="UDDI_Publication_SoapService">
- <port name="UDDI_Publication_PortType" binding="api_v3_binding:UDDI_Publication_SoapBinding">
<soap:address location="urn:unknown-location-uri" />
</port>
</service>
- <service name="UDDI_Inquiry_SoapService">
- <port name="UDDI_Inquiry_PortType" binding="api_v3_binding:UDDI_Inquiry_SoapBinding">
<soap:address location="urn:unknown-location-uri" />
</port>
</service>
</definitions>

perhaps it may help others .
It SSL handshake which is failing and that's because certificate is not trusted. certificates need be added to keystore of server.

Wsdl soap address errors

Hi,I have a question with web service.
I configured my web service in soamanager and it produced wsdl document.
İtu2019s soap address location <soap:addresslocation =" http://kgtest.calik.com:443/sap/bc/srt/rfc/sap/zor/300/zor/zor " />
But this address is wrong.In other words it produced wrong soap address.
True adress is; <soap:addresslocation =" http://kgtest.calik.com:5000/sap/bc/srt/rfc/sap/zor/300/zor/zor " />
I donu2019t know how I can correct and I donu2019t know why it produce wrong address.
I hope you can help me.
Thank you.

Hi,
Can you check the wsdl options. perhaps you are using an alternate port.
regards,
Bert

Disable the soap address location

Hi,
I wonder if it’s possible to disable the soap:address location in the WSDL?
My problem is that I use a proxy (SOAP) between my WebService Client and the WebLogic
WebService.
When I ask the WSDL through my proxy, it’s work well. But the next call, the client
goes directly to the WebLogic and does not use anymore the proxy. I think the
problem comes from the soap:address location.
Thanks for your help.
Charles

Hi Charles,
You could post your own WSDL, see the docs [1] for details, or you could
use a dynamic client without the WSDL; there are a number of examples of
how to do this such as Manoj's [2].
Regards,
Bruce
[1]
http://edocs.bea.com/wls/docs81/webserv/webxml.html#1007638
[2]
http://manojc.com/?sample25
Charles Desmoulins wrote:
>
Hi,
I wonder if it’s possible to disable the soap:address location in the WSDL?
My problem is that I use a proxy (SOAP) between my WebService Client and the WebLogic
WebService.
When I ask the WSDL through my proxy, it’s work well. But the next call, the client
goes directly to the WebLogic and does not use anymore the proxy. I think the
problem comes from the soap:address location.
Thanks for your help.
Charles

Since upgrading to iOS 8.3 the maps apps on my ipad do not show current location from my gps

Since upgrading to iOS 8.3 the maps apps on my ipad do not show current location from my gps DUALXGPS150A
The data is still being received by the ipad but not appearing on any of the maps.
Everything was working fine before the upgrade.

Hi davidisleta,
If you are having issues with your iPad not showing location information, you may want to try some things to troubleshoot.
First, quit all running applications and test again -
Force an app to close in iOS
Next, I would try restarting and if needed resetting the iPhone -
Restart or reset your iPhone, iPad, or iPod touch
If the issue is still present, you may want to restore the iPhone as a new device -
How to erase your iOS device and then set it up as a new device or restore it from backups
Thanks for using Apple Support Communities.
Best,
Brett L

What is the customer service phone number before I rip my hair out from frustration

I need it for Canada, hopefully without getting a useless and clueless foreign individual (not being racist only speaking from experience from the last time I called)

Adobe Connect Support phone numbers

How to control the location of the SOAP:address element in the WSDL

I have an EJB exposed as webservice in WebLogic 10.3. Further, the EJB has been annotated with the WebService annotation as in:
@WebService(name = "S_CALCULATORname", serviceName = "S_CALCULATORserviceName",
targetNamespace = "http://tempuri.org/SCalculator/")
@Stateless(name = "S_CALCULATOR")
public class S_CALCULATOR_Beanxxxxxx
The location attribute of the SOAP:address element in the WSDL document generated by the Test Client facility is of the form
http://host:port/ejb-java-class-name/service-name-attribute-value as in:
<soap:address location="http://123.4.5.678:1234/S_CALCULATOR_Beanxxxxxx/S_CALCULATORserviceName" />
Is there a way to control the value of the context root portion of the URL, ejb-java-class-name in this case, either using annotations or deployment descriptor files?
thanks in advance for any replies,
octavio

Hi,
While building the WebService Application you can use the following ANT task...
<target name="build-service4">
<jwsc
srcdir="src"
destdir="output/TestEar">
<jws file="examples/webservices/jwsc/TestServiceImpl.java">
<WLHttpTransport contextPath ="TestContext" serviceUri="TestServiceUri" portName="TestServicePortHTTP"/>
</jws>
</jwsc>
</target>
Or if you are developing JAXRPC EJB based WebService in that case you can even define the Context root using *@weblogic.jws.WLHttpTransport* annotation....
@WLHttpTransport(contextPath="simple", serviceUri="SimpleService", portName="SimpleServicePort")
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Feb 4, 2010 10:22 PM

AquaLogic Service Bus Perspective - WSDL Files with External Schemas

I am using the AquaLogic Service Bus Perspective in WebLogic Workshop to create my proxy services, business services, wsdls, schemas, etc. I have a wsdl that imports a schema based on its registered namepsace...not its schemaLocation. This works fine in the ALSB console, but in the WebLogic Workshop perspective, I cannot Publish my WSDL because the WSDL is not aware of any global resources...such as this Schema definition that is external to the WSDL. How do you make Globally aware resources in WebLogic Workshop? The same thing works in through the ALSB Web-based console...but that same file produces a wsdl validation error in my IDE because it has no idea about that schema.
Thanks -jay

Thanks to both of you who replied to my question - it is very much appreciated
We had a theory that you could just store everything under 'sbconfig' in CVS and restore it - but I thought that might be a bit hacky and less upgrade resistant.
Do you use build scripts for setting up dev/qa/prod endpoints because 'customisation files' are new or did you find a problem with 'customisation files' that made you resort to using a build script?
We were hoping to have some process like
Export JAR
Export Customisation File for Dev/QA/Prod
In Dev, we import the JAR + dev customisation file
In QA, we import the JAR + QA customisation file
In Prod, we import the JAR + prod customisation file
I know I have no chance, but you wouldn't care to share said document for my reading (not copying) pleasure? No worries if you don't :)
Thanks for your comments guys :)
Dan.
just in case
email is daniel prosser at gmail com
dots between my name and com
Edited by dan_prosser at 08/14/2007 6:33 PM

Unable to call BPM process webserivce from Proxy in oracle Service bus

I created business service in oracle service bus through BPM process WSDL. later Created proxy out of business service. In proxy service MessageFlow I created a route node with service as my BPM process business service. When i invoke proxy I am always getting the following error.
Request :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:proc="http://bea.com/albpm/Sapme_test_1/Process">
<soapenv:Header/>
<soapenv:Body>
<proc:startSession>
<password>Participant</password>
<user>Participant</user>
</proc:startSession>
</soapenv:Body>
</soapenv:Envelope>
Response :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-380000: General runtime error: socket write error: Connection aborted by peer</faultstring>
<detail>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380000</con:errorCode>
<con:reason>General runtime error: socket write error: Connection aborted by peer</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>
I tried the same example with general webservice instead of BPM Process it is working fine.
regards,
pv

Even Some times I am getting the following error
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-380000: BAD REQUEST</faultstring>
<detail>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380000</con:errorCode>
<con:reason>BAD REQUEST</con:reason>
<con:location>
<con:node>RouteNode1</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
regards,
pv

Oracle service bus and composing two web services

All,
Do let me know your thoughts on this.
Currently we have two web services
Web Service 1 - Verify Eligibility
Web Service 2 - Approve Proposal
Web Service 1 has one operation and accepts a well defined set of input parameters similarly web service 2 also exposes a single operation and accepts a set of input parameters.
These are deployed and running in our environment.
Now we have a requirement to stitch together these two web services and expose them as one single composite web service on the Oracle Service Bus 11g.
I want to create a proxy service on the OSB as unified web service (having its own WSDL) by composing the operations and input plus output parameters of the aforementioned two web services.
This way we can publish the WSDL to the front-end apps and they will trigger it with the required parameters and the proxy service will orchestrate the call to WS1 and WS2 and send the final output back to the calling client.
I was able to create an outbound call from the Proxy service to the underlying business services but I am not able to expose the Proxy service as web service with a WSDL i.e. create the proxy service by choosing operations of Web service 1 and web service 2
Please let me know your thoughts on this.
Regards,
Sushant

Thanks Atheek
The proxy service I tried to create orchestrate 2 web services.
But where we are struggling is How can i make this proxy service (composite) as a web service along with the WSDL.
The proxy service should be able to accept calls from the client with set of inputs representing both the underlying web services and coordinate calls b/w these two services and return consolidated output back to the calling client.
I am not finding a way to create a proxy service (web service along with the wsdl) which is representative of the underlying web services in a consolidated manner that can accepts inputs on behalf of both the underlying web services, orchestrate calls b/w the 2 web services and return the final output back to the calling client.
example modified to keep it brief
web service1
operation name: Verify Eligibility
Input: Complex type (String name, int Id, String address)
Output: Complex type(String approval status, int Id, String reason)
web service2
operation name: Approve Proposal
input: Complex type(String approval status, int Id, String reason, int Amount, int EmployeeCount)
Output: Complex type (String final status, String recommendation)
Composite Proxy Web Service
name: Composite Eligibility and Approval
Input: Complex type ( String name, int Id, String address, int Amount, int EmployeeCount)
Output: Complex type(String approval status, int Id, String reason,String final status, String recommendation)
The composite proxy should be created in a manner to jam the inputs of both the underlying web services and expose a representative interface on behalf of both the web services. This composite web service interface creation (WSDL) is where we are struggling a bit.
Because the calling clients need a unified WSDL to able to communicate with the composite web service.
Do post your thoughts.
Thanks Again,
Sushant

BizTalk 2013 R2: SB-Messaging Windows Service Bus On Premise 1.1 (Not Windows Azure)

Let me preface this by saying that I have been able to connect to the destination Service Bus Topics and Queue using traditional .NET methods (e.g. System.ServiceBus.Messaging namespace) and the applications using those components are running fine on the
same local VM. This uses the connection string that is provided from GET-SBAuthorizationRule.
Development Environment:
Windows Server 2012
SQL Server 2014
BizTalk 2013 R2
Local VM that is not on the Domain (but can connect to computers on the network)
I am trying to create a simple BizTalk 2013 R2 Messaging Solution that will use the SB-Messaging adapter features with Windows Service Bus On-Premise. My solution is using a Static One-Way Send Port to send messages to an existing topic on with Windows
Service Bus 1.1 using the SB-Messaging Adapter. After using the programmatic approach, the configurations were not as intuitive, but I believe I am close to the resolution. I have tried several combinations of key data but I am still not able to
connect. This seems like I am missing something small that is causing the problem but I am at a loss for the moment. The error I receive is below:
A message sent to adapter "SB-Messaging" on send port "SBSendPort" with URI "sb://<SERVERNAME>/NsServiceBus/collateraltopic" is suspended.
Error details: System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://<SERVERNAME>:7355/WRAPv0.9/'. Token provider returned message: '<Error><Code>400</Code><Detail>Namespace cannot be resolved 'https://<SERVERNAME>:7355/WRAPv0.9/'.TrackingId:6bcd22e8-1741-41fc-a84c-9aa3f7146ab5_GUS2522512,TimeStamp:6/30/2014 8:35:35 PM</Detail></Error>'. ---> System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security token while accessing 'https://<SERVERNAME>:7355/WRAPv0.9/'. Token provider returned message: '<Error><Code>400</Code><Detail>Namespace cannot be resolved 'https://<SERVERNAME>:7355/WRAPv0.9/'.TrackingId:6bcd22e8-1741-41fc-a84c-9aa3f7146ab5_GUS2522512,TimeStamp:6/30/2014 8:35:35 PM</Detail></Error>'. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.ServiceBus.TokenProviderHelper.TokenRequestAsyncResult.<GetAsyncSteps>b__8(TokenRequestAsyncResult thisPtr, IAsyncResult r)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
--- End of inner exception stack trace ---
Server stack trace:
Exception rethrown at [0]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(TokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(TokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationToken(String appliesTo, String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken, String parentLinkId, RetryPolicy policy, TrackingContext trackingContext)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.GetOverheadSize()
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender..ctor(String path, SbmpMessagingFactory messagingFactory, SbmpMessageCreator messageCreator, RetryPolicy retryPolicy)
at Microsoft.ServiceBus.Messaging.Sbmp.CreateSenderLinkSettings..ctor(SbmpMessagingFactory messagingFactory, String entityName, Nullable`1 entityType, String transferDestinationEntityName, RetryPolicy retryolicy)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginCreateMessageSender(String transferDestinationEntityName, String viaEntityName, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.CreateMessageSenderAsyncResult.<GetAsyncSteps>b__52(CreateMessageSenderAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.Start()
Exception rethrown at [0]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult`1.End(IAsyncResult asyncResult)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.<>c__DisplayClass4`1.<Begin>b__3(IAsyncResult r, T& output)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1.OperationComplete(IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult.SyncContinue(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1.BeginOperation()
at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1.OpenComplete(IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult.SyncContinue(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1..ctor(OpenOnceManager openOnceManager, TimeSpan openTimeout, AsyncCallback callback, Object state, Func`3 beginOperation, EndOperation`1 endOperation)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.Begin[T](AsyncCallback callback, Object state, Func`3 beginOperation, Func`2 endOperation)
at Microsoft.ServiceBus.Messaging.MessagingFactory.BeginCreateMessageSender(String transferDestinationEntityPath, String viaEntityPath, Boolean tryPairSender, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Channels.ServiceBusOutputChannel.OpenMessagingFactoryAndMessageSenderAsyncResult.CreateFactoryComplete(IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult.SyncContinue(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Channels.ServiceBusOutputChannel.OpenMessagingFactoryAndMessageSenderAsyncResult..ctor(ServiceBusOutputChannel outputChannel, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Channels.ServiceBusOutputChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open()
at Microsoft.BizTalk.Adapter.SBMessaging.SBMessagingOutputChannelFactory.OnCreateChannel(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.ChannelFactoryBase`1.InternalCreateChannel(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.ChannelFactoryBase`1.CreateChannel(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.ServiceChannelFactory.ServiceChannelFactoryOverOutput.CreateInnerChannelBinder(EndpointAddress to, Uri via)
at System.ServiceModel.Channels.ServiceChannelFactory.CreateServiceChannel(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.ServiceChannelFactory.CreateChannel(Type channelType, EndpointAddress address, Uri via)
at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)
at System.ServiceModel.ChannelFactory`1.CreateChannel()
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.GetChannel[TChannel](IBaseMessage bizTalkMessage, ChannelFactory`1& cachedFactory)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.SendMessage(IBaseMessage bizTalkMessage)
MessageId: {28428716-88C2-437B-953F-D471DA00C5A6}
InstanceID: {18C48B89-D9C0-47A8-ADF0-0CA62746FBB1}
Below are my Send Port Adapter Configurations:
URI is blacked out
/Namespace/Topic/ are next in the path
Can someone confirm that the Issuer Name is the Namespace and the Issuer Key is the Primary Key from the get-SBAuthorizationRule? I also tried Shared Access Signature (SAS) but that service was connecting to a default port and do not believe that is
how I need to connect.
Also, there is nothing on the Properties Tab as I do not have anything custom for the initial step.
Any and all help is appreciated.

Glenn,
Thank you very much for the response, I will go down this route in further detail. A couple of quick questions for you to help further my understanding.
Where is the SAS limitation documented? I am sure I glossed over it and it did not register, but your help in where to look next time will be helpful.
Also, can I change the default Port for which it is listening on the BizTalk Server or the Service Bus Location? The connection string I get from get-SBAuthorization Rule is as follows:
Endpoint=sb://{ServiceBusLocation}/NsServiceBus;StsEndpoint=https://{ServiceBusLocation}:7355/NsServiceBus;RuntimePort=7354;ManagementPort=7355;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey={KeyValue}
The exception I get is:
A message sent to adapter "SB-Messaging" on send port "SBSendPort" with URI "sb://<ServiceBusLocation>/NsServiceBus/collateraltopic" is suspended.
Error details: System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://<ServiceBusLocation>:9354/. The connection attempt lasted for a time span of 00:00:04.0250873. TCP error code 10061: No connection could be made because the target machine actively refused it <IPAddress>:9354. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.ServiceModel.Channels.SocketConnectionInitiator.ConnectAsyncResult.OnConnect(IAsyncResult result)
--- End of inner exception stack trace ---
It looks like it is going to 9354 for the authentication when the Service Bus is configured for
7355. I believe I have opened the ports on both ends but do not think it will matter since it looks like it is sending the
request to a different location.
Thank you

The AQ Service Bus showme a bad wsdl ( soap:address location )from internet

Similar Messages

Maybe you are looking for