Port web service

Hello,
I wanted to know if there is an easy way to change port 443 to port 8443 for the default web service ?
Thanks

Hello,
In fact, I used the Wiki tool and try to reproduce the configuration to use on another port.
Each time, I reboot the server, the configuration disapear and I have to redo all.
That should be an improvement.
Thanks,

Similar Messages

Which port Web Services uses?

Hi there,
Which port of TCP/IP does Web Services runs on? As far as from Java Web Services, there is this Java-RPC and WSDL, which ports they each runs?
Thanks for answer to newbies!

Hi,
It depends really on what port you servlet engine is running on. For example, if I run tomcat as usual on 8080, then that is thwe port that the web service runs. BUT. I can also run it on other ports too, at any time (just to confuse matters).
Can I suggest going to www.wrox.com and do a search for AXIS and download the samples (sourcecode) - most of it works with tomcat to a point. If in any doubt, the book is well worth a buy,but the source runs on earlier versions of AXIS, so there may be a few erors.
best
kev

Does ws adapter only work with asynchronous web service?

Hi all,
can you please confirm whether or not ws adapter (PI 7.1) only works with asynchronous web service?
I have created an async. outbound service interface in PI 7.1, generated the client proxy in ECC, created an web service based on the proxy, wrote a test program to call the web service (PI scenario uses ws adapter in the sender CC). Everything works fine.
Then I did the same thing with sync. outbound service interface. I got exception while calling the web service in ECC.
I've heard that ws adapter is designed for async. communication. Does it mean that it won't work with sync. web service?
I haven't seen any official SAP document saying taht ws adapter only works for async. web service. If you have any, can you please share it?
Thanks
Jayson

Thank you all for your information.
The error I got when calling the proxy with logical port (web service) is:
SOAP:1,007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")
I will debug it to see what exactly happens. And will keep you guys updated.
Just debugged, the error is because the http header's content type is text/html while it should be test/xml. However this type is set by the ws runtime, not by the application. Anybody has an idea about this?
Jayson
Edited by: Jayson on Feb 18, 2009 10:04 AM
Edited by: Jayson on Feb 18, 2009 12:11 PM

Following error occours when running a BI Publisher report in Siebel: Operation ' ? ' of Web Service ' ? . ? ' at port ' ? ' failed with the following explanation: " ? ".(SBL-EAI-04308)

I am installing a new reporting server.
When running a report I get the above error:
Operation '<?>' of Web Service '<?>.<?>' at port '<?>' failed with the following explanation: "<?>".(SBL-EAI-04308)
Any ideas?

Have a look here for Oracle's guidelines on troubleshooting such errors:
http://download.oracle.com/docs/cd/E14004_01/books/Reports/ReportsTroubleshoot.html

Web Service Proxy with Dynamic IP and Port

hi,
I am currently looking at the Web Service Proxy generation in JDev 11g. I can generate proxies fine, but the proxies are generated with static host and port. I want to substitute the host and port during runtime if required, for instance read the values from a database. I need to do this to avoid compiling the application for every deployment we make dev, test and production. Is there an easy way to set the generated proxy host and port? Are there any examples?
Thanks in advance!
Stephen

Hi,
Maybe you should have a look on XML Catalogs feature, but I am not sure if JDeveloper support it and how to support it.
-LJ

Error Message "No logical port exists to call web services" installing SM7

I am trying to use SLM to download a service stack. However, the option is not available in step 2.5. There is an error message "No logical port exists to call web services". I have performed the Wizard install, but the Wizard seems to have left out this step. I have looked around for documentation on how to configure the port, but cannot find anything more useful than comments to the effect that I should configure the port.

I found the problem, I think, although I am now on to the next problem. "Web Services for software lifecycle manager not available'.
The documentation is lacking. When the RFC connection is set up, the user id is j2ee_admin, using the install password. This is not specified anywhere in the install instructions that I could find, there is only a reference to a 'user id and password'.
The LPCONFIG is used to create a logical port, that ties the RFC to the LP. However, no name is specified that is to be used for the LP.

Client proxy consuming web service provider using logical port issue

Hi All,
I have a proxy client having a logical port (configured using NWDS) to consume a web service in the provider system.
In the logical port, I have given target address, and logical port name. While moving this client proxy NWDI dev track to Q and prod,
how do I change this target address to point to Q and prod respectively. In other words, even though I am using Visual admin to configure the destination url for the logical port, to point to Q and prod, its still referring to the dev environment provider service after moving the proxy client to Q and prod. What is the suggested approach to take care of this issue
Thx
mike

Hi Michael,
I can only help from that point of view that I believe this question belongs to the forum
Service-Oriented Architecture (SOA) and SAP
Please try to raise this question there.
Thanks and Regards,
Ervin

"Missing port information" when calling web service

I have implemented a web service that works fine as long as I use primitive types as arguments and return types, but when I add a method that takes a user-defined class as an argument, I receive the following error when calling any of the methods in the web service:
[java] java.rmi.RemoteException: received fault: "Missing port information"
(code: "Server" namespace: "http://schemas.xmlsoap.org/soap/envelope/"); nested
exception is:
[java] received fault: "Missing port information" (code: "Server" names
pace: "http://schemas.xmlsoap.org/soap/envelope/")
[java] java.rmi.RemoteException: received fault: "Missing port information"
(code: "Server" namespace: "http://schemas.xmlsoap.org/soap/envelope/"); nested
exception is:
[java] received fault: "Missing port information" (code: "Server" names
pace: "http://schemas.xmlsoap.org/soap/envelope/")
[java] received fault: "Missing port information" (code: "Server" namespace
: "http://schemas.xmlsoap.org/soap/envelope/")
[java] at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingS
ender.java:321)
[java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.
java:211)
[java] at qsws.MyItf_Stub.HelloWorld(Unknown Source)
[java] at qsws.WSClient.main(Unknown Source)
The class I pass as an argument implements Serializable and a user-defined interface and it has two public member variables (int and String).
Anyone know why I receive this error?
/Magnus

I am also seeing this same error. I have rebuilt and redeployed the service several times, but am still stuck getting this error. Strangely enough, the Tomcat server where the service is hosted is not reporting this type of error. Instead, it is recording an error 500 (Server Internal Error) each time I try to execute one of my services. I trimmed out the meat of the service and configured it so that it would echo the input parameters to the output (they are actually in/out params) but even this reduced configuration gives an error 500. I am inclined to suspect my deployment, but I have checked it several times against the examples.
Anyone else see the error 500 reported as missing port information?

Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING

hello colleagues,
In the phase Connect Diagnostics dont show the Agent available in SLD, but when go to SLD i have the agents,
Error,
Connect Diagnostics Agent
The table does not contain any data
Agent availables in all SLD
SOAP:1.007 SRT: Unupported xstream found: ("HTTP Code 401 : Unauthorized")
Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING
Thanks

OK, then pls follow below steps;
- Go to step 'Create Users' in solman_setup System Preparation scenario and make sure the user SM_INTERN_WS has a green status. Use the 'Test Login' button to make sure the user is not locked and has correct credentials maintained in solman_setup
- Immediately after checking the user status, navigate to Configure Connectivity->Enable Web Services and execute again the 'Create Logical Ports' automatic activity, in order to propagate the correct credentials to the Logical Port definitions.
- If the above operation is not successful, repeat the two steps above, providing a different user Id in 'Create Users' step, eg SM_INTERN_W1. This will prevent situations where the user gets locked by Logical Ports using an obsolete password.
Let me know the results.
Regards,
Vivek

Wcf web service send port retry?

We are contacting external wcf web services. We don't control these services and they could be returning an exception for a short while (which is "ok"), so we need to retry for a given period of time, without suspending the orchestration/sendport.
It used to be simple with web services (.asmx) since the send port would handle the retries as soon as an exception was returned from the web services. With wcf services and the soap fault, it is much more cumbersome.
I know how to do it from an orchestration, but it does add a lot of clutter (have an extra "initialization" construct block so visual studio shuts up about the uninitialized message coming back from the wcf service, define documentspecnames in
our case, define xpath expressions for the fault and the expected response, have a loop, a delay, more variables/expressions, scope, exception block, etc. etc.) for such a simple requirement. We need to contact a couple of wcf services in an orchestration
and the handling of the retries makes it quite large and unfriendly (and this is mostly the retry logic for these wcf services).
So, is there any way to have the send port adapter handle the retries when receiving an exception from a wcf service like it used to be with regular web services?

Thanks for you answer, yes I understand that the SOAP fault is just another message and that I need to act accordingly in the orchestration. I'm not refuting that, I'm just looking for a better solution than the one I have now (which seems overly complicated
to me).
I have to specify the documentspecname because we use the built-in xmlreceive pipeline and the type of the exception that the wcf services return is standardized in our organisation... so there are many copies of the schema of this exception deployed on
the servers. I need to specify the schema of the exception coming from my wcf reference in my assembly otherwise I get the "I can't find the right schema blabla" exception.
Of course, if I can stop using the XMLReceive pipeline, I wouldn't have to specify the documentspecname... I'll have to research in detail what this pipeline is doing and see if I can replicate it's functionality, with the addition of the check for the error
in the returned message.
I just want to be sure before proceeding... If I raise an exception in a custom pipeline, the send port retry configuration would apply?

How do I set up Mozilla to accept connections on port "The World Wide Web service (HTTP)"?

When attempting to embed a video in PowerPoint 2013, the message "Sorry we are having some temporary service issues" appears.
In researching the problem at Microsoft. com, the following message was received: Mozilla is not set up to accept connections on port "The World Wide Web service (HTTP)."

Hmm... PowerPoint should use Windows to connect to the internet and not Firefox.
Which method are you using?
(1) Insert > Video > Online Video
Apparently there was an update this month that enables this, as described in this support post (see top Answer just after the question): [http://answers.microsoft.com/en-us/office/forum/office_2013_release-powerpoint/embedding-online-you-tube-video-in-powerpoint-2013/0bc00dde-420c-4c6a-bd47-3fb105ce40fc Embedding online you tube video in powerpoint 2013 - Microsoft Community]
Here's how it should work after the update: [http://office.microsoft.com/en-us/powerpoint-help/insert-or-link-to-a-video-on-youtube-HA104192855.aspx Insert or link to a video on YouTube - PowerPoint]
(2) Developer > More Controls > Shockwave Flash Object
As documented on other sites, such as: https://www2.palomar.edu/pages/atrc/2013/09/17/how-to-embed-youtube-video-in-powerpoint-2013/

What are the system ports that XI uses to invoke web services?

Hi guys,
Anyone knows what are the system ports that XI uses to invoke and to be invoked from web services?
I think it uses the port of AFW but I dont have sure
Thanks in advance,
Ricardo.

hi,
if you want to invoke a WS on the XI use
the j2ee port (5XX00)
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

UTL_DBWS accessing web service gives 'not contain port' error

Hello
I am trying to call a web service from https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl
In the WSDL xml, i get the targetNamespace (http://PlanonWebServices.ws),
the service name (PlanonSession),
the wsdl URL (https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl),
the portType name (PlanonSessionHttpEndpoint),
the operation name (login).
When i call the web service, i get an error about the port :
-29532 - ORA-29532: Java call terminated by uncaught Java exception: service:
{http://PlanonWebServices.ws}PlanonSession does not contain port:
{http://PlanonWebServices.ws}PlanonSessionHttpEndpoint
The code is :
CREATE OR REPLACE PROCEDURE planon_Login AS
planon_username     VARCHAR2(50):= 'XXXXXX'; --- removed for security
planon_passwd     VARCHAR2(50):= 'XXXXX'; --- removed for security
service_ sys.utl_dbws.SERVICE;
call_ sys.utl_dbws.CALL;
service_qname sys.utl_dbws.QNAME;
port_qname sys.utl_dbws.QNAME;
operation_qname sys.utl_dbws.QNAME;
string_type_qname sys.utl_dbws.QNAME;
username     sys.utl_dbws.QNAME;
password      sys.utl_dbws.QNAME;
--retx               ANYDATA;
retx_string VARCHAR2(1000);
l_namespace     VARCHAR2(1000);
l_wsdl_url VARCHAR2(1000);
l_input_params      sys.utl_dbws.ANYDATA_LIST;
outputs      sys.utl_dbws.ANYDATA_LIST;
output_retx VARCHAR2(1000);
xml_string sys.xmltype;
retx sys.xmltype;
qname_list_     sys.utl_dbws.QNAME_LIST;
qname_list_string sys.utl_dbws.QNAME_LIST;
BEGIN
dbms_output.put_line('Step 1');
dbms_output.put_line('Step 1 : Set l_wsdl_url');
l_wsdl_url := 'https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl';
dbms_output.put_line('Step 1 : Set l_namespace');
l_namespace := 'http://PlanonWebServices.ws';
dbms_output.put_line('Step 1 : Set service_');
service_qname := sys.utl_dbws.to_qname(l_namespace,'PlanonSession');
service_ := sys.utl_dbws.create_service (URIFACTORY.getURI(l_wsdl_url), service_qname);
dbms_output.put_line('Step 1 : Set port_qname_');
port_qname := sys.utl_dbws.to_qname(l_namespace,'PlanonSessionHttpEndpoint');
dbms_output.put_line('Step 1 : Set operation_qname');
operation_qname := sys.utl_dbws.to_qname(l_namespace, 'login');
dbms_output.put_line('Step 1 : Set call_');
call_ := sys.utl_dbws.create_call(service_,port_qname,operation_qname);
dbms_output.put_line('Step 2');
sys.utl_dbws.set_property(call_,'USERNAME', planon_username);
sys.utl_dbws.set_property(call_,'PASSWORD', planon_passwd);
sys.utl_dbws.set_property(call_,'SOAPACTION_USE','TRUE');
sys.utl_dbws.set_property(call_,'SOAPACTION_URI','https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession');
sys.utl_dbws.set_property(call_,'ENCODINGSTYLE_URI', 'https://schemas.xmlsoap.org/soap/encoding/');
sys.utl_dbws.set_property(call_,'OPERATION_STYLE','document');
dbms_output.put_line('Step 3');
string_type_qname := sys.utl_dbws.to_qname('https://www.w3.org/2001/XMLSchema', 'string');
/* first return parameter in the WSDL should not be specified in the parameter list or errors occur
sys.utl_dbws.add_parameter(call_, 'loginResponse', string_type_qname, 'ParameterMode.OUT');
sys.utl_dbws.set_return_type(call_,string_type_qname);
xml_string := xmltype('<PlanonSession xmlns="https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services">'
|| '</PlanonSession>');
retx := sys.utl_dbws.invoke(call_,xml_string);
dbms_output.put_line('Step 6');
dbms_output.put_line('Step 7');
dbms_output.put_line('Call Web Service:services:PlanonSession: ' || retx.getStringVal());
dbms_output.put_line('Step 10');
sys.utl_dbws.release_call(call_);
sys.utl_dbws.release_service(service_);
dbms_output.put_line('Step 11');
EXCEPTION
when others then
dbms_output.put_line(SQLCODE || ' - ' || SQLERRM);
END;
The WSDL document is :
?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:ns="http://PlanonWebServices.ws" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" targetNamespace="http://PlanonWebServices.ws">
<wsdl:documentation>PlanonSession</wsdl:documentation>
<wsdl:types>
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://PlanonWebServices.ws">
<xs:complexType name="Exception">
<xs:sequence>
<xs:element minOccurs="0" name="Exception" nillable="true" type="xs:anyType"/>
</xs:sequence>
</xs:complexType>
<xs:element name="logout">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="logoutResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setReferenceDate">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="param1" nillable="true" type="xs:dateTime"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setReferenceDateResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setSessionDataSection">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="param1" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setSessionDataSectionResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="login">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="param1" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="loginResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
<wsdl:message name="logoutRequest">
<wsdl:part name="parameters" element="ns:logout"/>
</wsdl:message>
<wsdl:message name="logoutResponse">
<wsdl:part name="parameters" element="ns:logoutResponse"/>
</wsdl:message>
<wsdl:message name="loginRequest">
<wsdl:part name="parameters" element="ns:login"/>
</wsdl:message>
<wsdl:message name="loginResponse">
<wsdl:part name="parameters" element="ns:loginResponse"/>
</wsdl:message>
<wsdl:message name="setSessionDataSectionRequest">
<wsdl:part name="parameters" element="ns:setSessionDataSection"/>
</wsdl:message>
<wsdl:message name="setSessionDataSectionResponse">
<wsdl:part name="parameters" element="ns:setSessionDataSectionResponse"/>
</wsdl:message>
<wsdl:message name="setReferenceDateRequest">
<wsdl:part name="parameters" element="ns:setReferenceDate"/>
</wsdl:message>
<wsdl:message name="setReferenceDateResponse">
<wsdl:part name="parameters" element="ns:setReferenceDateResponse"/>
</wsdl:message>
<wsdl:portType name="PlanonSessionPortType">
<wsdl:operation name="logout">
<wsdl:input message="ns:logoutRequest" wsaw:Action="urn:logout"/>
<wsdl:output message="ns:logoutResponse" wsaw:Action="urn:logoutResponse"/>
</wsdl:operation>
<wsdl:operation name="login">
<wsdl:input message="ns:loginRequest" wsaw:Action="urn:login"/>
<wsdl:output message="ns:loginResponse" wsaw:Action="urn:loginResponse"/>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<wsdl:input message="ns:setSessionDataSectionRequest" wsaw:Action="urn:setSessionDataSection"/>
<wsdl:output message="ns:setSessionDataSectionResponse" wsaw:Action="urn:setSessionDataSectionResponse"/>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<wsdl:input message="ns:setReferenceDateRequest" wsaw:Action="urn:setReferenceDate"/>
<wsdl:output message="ns:setReferenceDateResponse" wsaw:Action="urn:setReferenceDateResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="PlanonSessionSoap11Binding" type="ns:PlanonSessionPortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="logout">
<soap:operation soapAction="urn:logout" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="login">
<soap:operation soapAction="urn:login" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<soap:operation soapAction="urn:setSessionDataSection" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<soap:operation soapAction="urn:setReferenceDate" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="PlanonSessionSoap12Binding" type="ns:PlanonSessionPortType">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="logout">
<soap12:operation soapAction="urn:logout" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="login">
<soap12:operation soapAction="urn:login" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<soap12:operation soapAction="urn:setSessionDataSection" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<soap12:operation soapAction="urn:setReferenceDate" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="PlanonSessionHttpBinding" type="ns:PlanonSessionPortType">
<http:binding verb="POST"/>
<wsdl:operation name="logout">
<http:operation location="PlanonSession/logout"/>
<wsdl:input>
<mime:content type="text/xml" part="logout"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="logout"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="login">
<http:operation location="PlanonSession/login"/>
<wsdl:input>
<mime:content type="text/xml" part="login"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="login"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<http:operation location="PlanonSession/setSessionDataSection"/>
<wsdl:input>
<mime:content type="text/xml" part="setSessionDataSection"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="setSessionDataSection"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<http:operation location="PlanonSession/setReferenceDate"/>
<wsdl:input>
<mime:content type="text/xml" part="setReferenceDate"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="setReferenceDate"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="PlanonSession">
<wsdl:port name="PlanonSessionHttpSoap11Endpoint" binding="ns:PlanonSessionSoap11Binding">
<soap:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpSoap11Endpoint/"/>
</wsdl:port>
<wsdl:port name="PlanonSessionHttpSoap12Endpoint" binding="ns:PlanonSessionSoap12Binding">
<soap12:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpSoap12Endpoint/"/>
</wsdl:port>
<wsdl:port name="PlanonSessionHttpEndpoint" binding="ns:PlanonSessionHttpBinding">
<http:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpEndpoint/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Any help is greatly appreciated.
Thanks in advance

I got the same error... did you find a solution?
tks
Mário Cardia

Send Port to internally hosted IIS web service needs to run on the SAME IIS SERVER from multiple orchestrations

Hi
We have a multi-server BizTalk environment. We have an Orchestration with multiple call orchestrations in it. Each called orchestration is calling a web service through a 2 way Send Port (which is hosted in IIS on each BizTalk server in our multi server
environment). We have to ensure that each called orchestration is calling these web services on the same IIS server.
I could create a dedicated host instance that the Send Port runs under to run only on one server but then this means that all our DBase traffic is happening on one server. We also thought about using the load balancer some how to achieve this through sticky
sessions etc.
This is all necessary because we are using Entity Framework exposed through web services and we need to manage transactions.
Any ideas on how we may achieve this. I have inserted a picture to try and show the scenario
Biztalk Developer

Haha, Entity Framework strikes again! But seriously, that is a rather odd architectural requirement, double check first. But anyway...
Try this: Configure the Send Port URI to point to something like http://localservicehost/[yourEFService]
Then in the local hosts file (the DNS/IP hosts file), define localservicehost to the local IP address where the service is listening.
That way, the connection will always be made to the local machine. Essentially the same as localhost.

Dynamic Logical Port for Web Service Client

Hi *!
We want to use the same Web Service Client code with different Web Service instances running on different systems. So I need to configure the logical port (especially the URL of the endpoint) dynamically at runtime.
Please give me a hint, how this is done.
(we are using WebAS 6.40 SP7)...
Thanks in advance,
Frank

Hi Frank,
I hope you were able to solve your issue on you own in the meantime.
I was looking for the answer to this question today. This was the only thread I found on SDN. Unfortunately, it did not contain an answer yet. I was able to figure out a way to set the endpoint address dynamically after searching help.sap.com and after examining the interfaces offered by the Stub (logical port in this case) classes.
Here's an extract from my code:
// Connect to JNDI context
InitialContext ic = new InitialContext();
// Get reference to web service proxy from JNDI context
Z_MSC_GET_SCHEDULE_WSDService service =
(Z_MSC_GET_SCHEDULE_WSDService) ic.lookup("wsclients/proxies/iot-online.de/msc~srv_ejb~proxy/de.iot_online.msc.proxy.ScheduleReaderProxy");
// Get reference to logical port from web service proxy
Z_MSC_GET_SCHEDULE_WSD logicalPort = service.getLogicalPort();
// Set URL of web service Endpoint
logicalPort._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, "http://<FQDN>:8010/sap/bc/srt/rfc/sap/Z_MSC_GET_SCHEDULE_WSD?sap-client=100");
This is explained on
http://help.sap.com/saphelp_nwce10/helpdata/en/45/113a1221337249e10000000a155369/frameset.htm
You can also set the credentials (username / password) with the method _setProperty.
Best regards
Christian

Port web service

Similar Messages

Maybe you are looking for