Problems of logical port configuration

Currently we made the system X8A_100 as our integration server and we designed a service interface which can dispatch the request to a function module in A1S_100, then we generated its proxy (through the transaction code SPROXY) in the X8A_105 which act as the sender after we had finished some design and configuration work. It run successfully.
And then we expose the service interface as a web service, generated its proxy in the X8A_105, it also run successfully (didn't create any logical port). But after that, we generated a proxy of the same service interface in BBT_100, it failed and threw a exception 'GENERAL_ERROR Error during proxy processing (PART UNKNOWN (NULL) )' although we had create a default logical port of the proxy. When I create logic port of the proxy, I set the value of the URL in Call Parameters tabs 'http://pwdf2655:50050/sap/xi/engine?type=entry&version=3.0&Sender.Service=X8A_105&Interface=http%3A%2F%2Fsap.com%2Fxi%2Ftest%2Fabap%5ESayHello_ServiceInterface', I think the problem was caused by the wrong configuration of the logical port, could anyone please tell me how we can do the configuration correctly? Thanks a lot in advance.

Hi,
This might help you
http://help.sap.com/saphelp_nw04/helpdata/en/9f/c487d701c7214db8ca7a741ba3c9d0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f3/7d7b60d1e9744d9fe27b4438d9014d/frameset.htm
http://help.sap.com/saphelp_webas630/helpdata/en/ef/f9896cca8a8248a563050932b05322/content.htm
Regards
Agasthuri Doss

Similar Messages

Edit Customer Problem and Logical Port

Hi Experts,
ISSUE 1
In Web Service Administration, when I look at /iwcnt/actionitemvi_document service in details, I can see one Endpoint only, that is Binding_T_HTTP_A_HTTP.
In the Troubleshooting Guide, in section 5. No Workflow / Reports reach the SCL from backend system, there are mentioned two endpoints: Binding_T_HTTPS_A_HTTP and Binding_T_HTTP_A_HTTP - all other setting, I have, are the same on my server as mentioned in the troubleshooting guide. So why there is diffrence in binding on that particular service?
The other thing I noticed, is, that when looking closer on the logical port creation on backend system in the Behind the scene video, it mentions, that the Path Suffix include binding_t_http_a_http whereas in the Troubleshooting Guide it is showing binding_t_https_a_http - why this?
What is the right path suffix for the logical ports at the backend system?
ISSUE 2
When we edit a customer from SharePoint, we get the following error:
Error
An unexpedted error has occured
Correlation ID: ea04d908.xxxxxxxxxxxxxx
Looking closer at the correlation at SCL, everything seems to be green and no error is reported, but in the ULS Viewer, following info are displayed:
Microsoft.BusinessData.Runtime.BackendNullReturnException: LobSystem (External System) returned a null structure which is incompatible with the associated metadata.
at Microsoft.SharePoint.BusinessData.Runtime.EntityRuntime.WrapAsEntities(IMethodInstance methodInstance, IEntity thisEntity, IParameter parameter, ITypeDescriptor entityInstanceRootTypeDescriptor, Object correspondingAdapterObject, IEntity targetEntity, ISystemUtility dataSystemUtility, ILobSystemInstance lobSystemInstance)
at Microsoft.SharePoint.BusinessData.Runtime.EntityRuntime.ExecuteInternal(IDataClass thisDataClass, ILobSystemInstance lobSystemInstance, ILobSystem lobSystem, IMethodInstance methodInstanceToExecute, IMethod methodToExecute, IParameterCollection nonReturnParameters, Object[]& overrideArgs, IFilterCollection filters)
at Microsoft.SharePoint.BusinessData.Runtime.EntityRuntime.FindSpecific(IEntity thisEntity, Identity entityInstanceIdentity, String specificFinderName, ILobSystemInstance lobSystemInstance)
regards
Tariq

Hi,
ISSUE 1:
This is very likely because SSL is not configured. First of all can you go to SOAMANAGER -> Business Scenario Configuration and deactivate and activate the DUET_ENTERPRISE_ALL. When activating check if you are getting errors for the Assertion profiles (my guess would be, that you are getting errors).
In this case check the SSL configuration from SMICM -> \[Menu] Goto -> Services
Here you should see an active service HTTPS. If that is not the case, check that the SSL certificate is created (STRUST) and make sure that the required profile parameters are set (see also Deployment Guide -> "To configure the use of SSL in the SCL host" on page 33 at http://www.service.sap.com/instguides -> Duet -> Duet Enterprise 1.0 -> Duet Enterprise SAP Deployment Guide)).
Regarding the backend configuration for the logical ports in LPCONFIG. Here it depends on how you have setup the configuration on the SCL. If you released the services with HTTPS then the URL in the backend has to be HTTPS binding, if you configured it via HTTP, then it has to be HTTP binding Did you perform the connection tests as described in the videos or in the checkpoint of the troubleshooting guide?
ISSUE 2:
Can you take a look also on the SAP side in SRTUTIL? Do you see any additional error information there? You might also want to check the errors from the log viewer /IWFND/VIEW_LOG
Regards,
Holger.

Problem using logical port type "ABAP"

Hi, my problem is that I have to save a txt file with a certanly format who feeds from an IDOCs that is sended nowhere.
Instead of using a BADI the client wants that every time a PO is liberated an IDOC has to be triggered and it has to save that txt in a path, but that IDOC is not sended anywhere is just for saving the file. Dont ask why... they want to do this approach.
So I created a logical port of type ABAP, copy the function "OWN_FUNCTION" as a template and in my custom function I parse the IDOC and save the file... it works. My problem is that the IDOC is created when a PO is created but not triggered !!!
The IDOC is created with status 30 (ready to send).
What I need is that when the PO is saved the file has to be generated in the server but the function is not triggered. I try running the Program RSEOUT00 and the IDOC is not found (dont know why) the only way I can trigger the IDOC is via BD87.
Someone could help me, I dont know why the logical port type ABAP is not triggered. all my setting in WE20 is right.
Thx

The problem was in the WE20, the radio button was in mode 4 (collect IDOCs) instead of 2 (send inmediatly)

Java proxy client logical port transport to Q and prod issue in target addr

Hi All,
I have a java 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

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

Logical port error (WS_LOGICAL_PORT) when consuming WS in PI

Hi All,
I am trying to integrate simple Currency Conversion Web Service witm my ECC program.
Program displays two fields in the selection screen (Currency From and Currency To)
WS is: http://www.webservicex.com/ws/WSDetails.aspx?WSID=10&CATID=2
The scenario is as below:
Proxy (Z-PROGRAM ) <-sync-> PI <-sync-> WS (Currency Convertor)
Looks like ABAP Proxy is done ok.
PI configuration also looks ok as I am trying it in IB's Test Configuration tool - all steps are 'Green / Passed'
Based on WSDL 3 interfaces were generated:
CurrencyConvertorHttpPost
CurrencyConvertorHttpGet
CurrencyConvertorSoap
I am using Soap one... along with WS Communication Channel
CC has configuren itself based on WSDL likn provided,
Technical Transport Settings were set to:
Target Host:               www.webservicex.net
Service Name / Port:     -1
URL Access Path:          /CurrencyConvertor.asmx
Transport Binding:          SOAP 1.1 Using HTTP
Why am I getting logical port error?
Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap
I searched the web for error message and I found obsolete logical port configuration using LPCONFIG, and also some 'new' approach with SOAMANAGER LogPort configuraton
(When I try to do this as suggested in [document |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b04408cc-f10e-2c10-b5b7-af11026b2393?QuickLink=index&overridelayout=true]
then I cannot see my newly created services on the list)
... but is this the right track to follow?
Should I run Logical Port configuration in PI?
I would appreciate your comments on this.
Regards,
bob.

Hello,
Why am I getting logical port error?
Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap
WS Adapter is used for those that are using WS-RM (Webservice-Reliable Messaging)...See this blog
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b00bbb77-75bc-2a10-6b9a-a6f8161515a6, but I think for now this is limited to SAP-to-SAP connections. That is why in your error it is searching for a logical port (ABAP Proxy).
You should be using the SOAP Receiver Adapter instead.
Hope this helps,
Mark

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

Can't run form from Form Builder 10g - Port configuration problem?

Hi,
I have installed the Database (10.2.0.1.0) and the Developer Suite (10.1.2.0.2) on two Linux machines (Red Hat Enterprise Linux ES 4 Basic).
If I enter the frmservlet-URL manually everything seems to be fine.
In one case I enter http://127.0.0.1:8890/forms/frmservlet, in the other http://127.0.0.1:8889/forms/frmservlet; in BOTH cases I get eventually a dark square and the status bar says "Applet oracle.forms.engine.Main started".
HOWEVER, if I create a simple form with Form Builder and click on the Button with the green traffic light ("Run Form"), the form runs only on the machine where frmservlet listens on port 8890.
On the other machine (frmservlet configured to listen on port 8889) Firefox pops up, the URL "http://127.0.0.1:32979/6dOrpwghCqnp8PhMT7KVT533m3IaArqFbPqPBOztZXWYSsNy" gets called, and nothing else happens. The screen displays the string "ORACLE FORMS." and the status bar says "Waiting for 127.0.0.1...", and it stays like this forever.
I assume this is a port configuration problem, but I don't have a clue where to start.
Any suggestions how I should proceed are greatly appreciated.
Thank you very much in advance!

Hi Frank,
Thank you for your reply.
I doublechecked my configuration.
In the dialog Edit --> Preferences --> Runtime the Application Server URL is set to "127.0.0.1:8889/forms/frmservlet".
However, when I attempt to run the form, the URL "http://127.0.0.1:33140/W2dwbV9eXS2fPkuKlxNhCxFWdEihwDviat2uV7ycrSotqwDN" gets called.
The screen displays the string "ORACLE FORMS." and the status bar says "Waiting for 127.0.0.1...", and that's it.
I wonder how the port number 33140 got selected. Interestingly, this time it is a different number; last time it was port 32979. In fact, the port number seems to change each time; I tried again and now it is 33189.
I will now try to set the port number for the frmservlet to 8890.
I choose Edit --> Preferences --> Runtime and set the application server URL to "127.0.0.1:8890/forms/frmservlet".
I stop the container, open /home/oracle/OraHome_1/j2ee/DevSuite/config/default-web-site.xml and change the port number to 8890:
<?xml version="1.0" standalone='yes'?>
<!DOCTYPE web-site PUBLIC "Oracle Application Server 10g XML Web-site" "http://xmlns.oracle.com/ias/dtds/web-site.dtd">



<web-site port="8890" protocol="http"
display-name="Oracle Developer Suite 10g instance of Oracle Containers for J2EE Web Site">

     
     
     <default-web-app application="default" name="defaultWebApp" root="/j2ee" />

<web-app application="forms" name="formsweb" root="/forms" />


<web-app application ="reports" name="web" root="/reports" />
<web-app application = "reports" name="demo" root="/repdemo" />
     
     <access-log path="../log/default-web-access.log" />
</web-site>
I restart the container, start Form Builder, connect to the database, and open my test form.
When attempting to run the form, the URL "http://127.0.0.1:33437/Pl0n3ky9vmU5z37A7ScBnQhsGwq3jwuzJpgTAKWPMOYIzT8K" gets called (again a new port number, apparently picked radomly within a certain range) and nothing happens: "Waiting for 127.0.0.1...".
However, when I enter the URL http://127.0.0.1:8890/forms/frmservlet I do (eventually, after confirming that I trust the certificate etc.) get a darc rectangle and the status message "Applet oracle.forms.engine.Main started", which tells me that my setup can't be that far off target.
Here is the output of netstat:
[root@localhost ~]# netstat -anp --tcp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN 2779/rpc.statd
tcp 0 0 0.0.0.0:23910 0.0.0.0:* LISTEN 5269/java
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2759/portmap
tcp 0 0 0.0.0.0:1521 0.0.0.0:* LISTEN 4265/tnslsnr
tcp 0 0 0.0.0.0:113 0.0.0.0:* LISTEN 2983/xinetd
tcp 0 0 127.0.0.1:7830 0.0.0.0:* LISTEN 4429/spamd --port 7
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2928/cupsd
tcp 0 0 0.0.0.0:9240 0.0.0.0:* LISTEN 5269/java
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 3002/sendmail: acce
tcp 0 0 0.0.0.0:8890 0.0.0.0:* LISTEN 5269/java
tcp 0 0 0.0.0.0:32795 0.0.0.0:* LISTEN 4231/ora_d000_orcl
tcp 0 0 127.0.0.1:1521 127.0.0.1:32817 ESTABLISHED 4265/tnslsnr
tcp 0 0 127.0.0.1:32817 127.0.0.1:1521 ESTABLISHED 4209/ora_pmon_orcl
tcp 0 0 127.0.0.1:33425 127.0.0.1:1521 ESTABLISHED 5298/frmbld
tcp 0 0 127.0.0.1:1521 127.0.0.1:33425 ESTABLISHED 5311/oracleorcl
tcp 1 0 80.133.127.83:33485 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33484 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33494 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33520 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 0 0 80.133.127.83:33529 209.132.177.100:443 ESTABLISHED 4060/python
tcp 0 0 80.133.127.83:33528 209.132.177.100:443 ESTABLISHED 4060/python
tcp 1 0 80.133.127.83:33460 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33470 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 0 0 :::22 :::* LISTEN 2968/sshd
tcp 0 0 ::ffff:127.0.0.1:33437 :::* LISTEN 5298/frmbld
tcp 697 0 ::ffff:127.0.0.1:33437 ::ffff:127.0.0.1:33439 CLOSE_WAIT -
tcp 348 0 ::ffff:127.0.0.1:33437 ::ffff:127.0.0.1:33440 CLOSE_WAIT -
[root@localhost ~]#
The question remains: Where do those port numbers come from?
Regards,
jme

Problem while creating logical port using soamanager

Hi all,
I have created a client proxy for web service from a 3rd party system.
When i am creating a logical port for the same consumer proxy i get a error as follows:
RABAX_STATE -e: UNCAUGHT_EXCEPTION
and a dump saying
" The exception 'CX_SXMLP' was raised, but it was not caught anywhere along the call hierarchy.
Since exceptions represent error situations and this error was not adequately responded to, the running ABAP program
'CL_SXMLP_FRAGMENT=============CP' has to be terminated.
Please suggest what can be done or what can be the problem.
Thanks in advance.
Komal

Pls go to txn SM59 and check if the RFC destination for webservice is working in the test connection.
Then go to txn LPCONFIG and create the logical port using the RFC dest. Pls mention the path suffix appropriately.
Next in your code while instantiating the client proxy pass the logical port name in the constructor (if the LP is not maintained as default).
Pls reward points if the tips are helpful.

Logical Port Problem using a Web Service

Hi.
I have created a simple web service and imported the model succesfully into my webdynpro component. However, when I execute the web service method, I just get the following error:
"Logical Ports loading problem. Parser error."
I'm new to NWDS, but my application did work when I first used it, because my web service throws an exception and this was displayed correctly in the application.
Could this error be due to Internet explorer connection settings on the Duiscovery server? (We have a few exclusions in there).
If I type in the url of my web service manually into IE on the discovery server, it returns the expected results, so I know my web service is working.
There also seems to be a problem with my NWDS install, because if I change any of the properties of the Logical Port, the save icon isn't available, and shutting the properties page and reopening it restores the original settings.
Any help would be greatly appreciated, as this is driving me nuts!
Many thanks in advance.
Nigel

OK, so I've found the answer to the proxy settings on the client - they are stored in
<InstallDIR>\Workspace\ .metadata\ .plugins\com.tssap.config\pref_store.ini
For no proxy, change the contents of this file as follows:
#Tue Apr 15 10:09:09 ACT 2008
proxyHost=
sapInitialized=true
proxySet=false
applyNoProxy=true
proxyPort=
Then save it, delete the logical port on your model and then create a new logical port from your WSDL.

Problems of Port Configuration while upgrading from 4.0B to ERP 6

Hi all,
We are upgrading a system from 4.0B to ERP 6. Will there will be any problems from port configuration side? If any please tell what they might be.
thankyou.

Hello,
We have upgraded from 4.6C to ECC6.0 and did not have any port config issues.
Things to look for:
- RFC destinations, do they still work
- directories used in File type ports, are they still there (they should be)
Hope this helps a bit
Regards
Greg Kern

Logical port problem

Hi All
I create logical port in LPCONFIG for a WS and i put the proxy class and logcal port (just variable like abc ) i choose defult port
and in runtime i choose webservice and in in call parameters in URL i put the WSDl of the WS i create via se37 .
when i activate it i get message : Web service requires state management
What i need to do to overcome this issue?
Best Regards
Nina

Hi Nina,
Purpose
The options for error handling depend on the type of communication chosen:
·        Asynchronous Communication: On the sender side, the application can only handle errors that occur when the message is being sent (for example, the outbound queue is full). You can catch and persist these errors by using the exception class CX_AI_SYSTEM_FAULT. On the receiver side, as in the synchronous case, you can define fault messages, which are then only forwarded to monitoring (and not to the sender).
If you want to define how the sender is to process asynchronous errors, see the Acknowledgments section. The Web service runtime only supports synchronous communication.
·        Synchronous Communication: You can use fault messages to handle errors that have occurred on the receiver side. To confirm an error, the proxy runtime sends the fault message from the receiver back to the sender, which can then respond to it.
Process Flow
The example used here works with the XI runtime standardized structure. When using the Web service runtime, follow the same procedure to trigger an exception on the receiver side and handle it on the sender side (indicated in the source text by the comments with a hash symbol (#)). The fault message structure is defined by the WSDL description in both cases and is found in the exception class.
    1.      If an application on the receiver side triggers an error, the ABAP proxy runtime converts the corresponding exception class to a fault message and transfers it to the sender system.
       2.      In the sender system, the ABAP proxy runtime interprets the fault message and triggers the exception for the client proxy.
       3.      In the sender system, the application can catch and handle the exception using a Try/Catch block. Using the super exception class CX_AI_APPLICATION_FAULT you can - in a similar way to the statement WHEN OTHERS in a CASE statement - catch all remaining application errors.
see the following links for Possible ...
http://help.sap.com/saphelp_nw70/helpdata/EN/75/a55c3cff8ca92be10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/25/a45c3cff8ca92be10000000a114084/frameset.htm
Regards,
Prabhudas

Port configuration problem

After updating Safari, my "port configuration" does not recognize the built-in ethernet option and I can't connect to the internet using Safari. Everything else works properly - Any suggestions?

Hi Jim, and a warm welcome to the forums!
Are you saying that it doesn't show at all in Network>Show:>Network Port Configurations?
If you haven't yet try this...
Safe Boot from the HD, (holding Shift key down at bootup), it will try to repair your Disk Directory while the spinning radian is happening, so let it go, run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, when complete reboot.

Problem with the error at DIO port configuration

I am working on the design of a model of a computer controlled Fuel Injection system using Gasoline Direct Igniton technology. I am using PCI-6025E as my data card and SCB-100 Connector block. My application is to get the digital input from the shaft encoder and the solenoids[acting as Inlet and exhaust valves]get actuated according to the VI. When I am trying to run the program theres an error 10001 occured at DIO port configuration. The statement is as" The error occured at the input string, the arrangement or ordering of the characters in the string is not consistent with the expected ordering". I checked the shaft encoder[S5S-50]pin out connections using an oscillograph and the voltages are as expected. Please let me
know the possible areas where I can figure out the error.

Maruthi;
You are probably using VIs that are not supported by that DAQ device. That DAQ device of yours only allow unstrobed digital updates, meaning that the digital lines will be updated by Software calls.
Since you probably need high speed/accuracy on your digital updates, you would be better served by using the PCI-6534 instead.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

How to change a Logical Port URL-Destination/Endpoint at Runtime

Hi,
i am looking for a way to change the endpoint for a webservice-call without redeploying my application. (I am using a standalone-proxy).
In the SAP-Help from NetWeaver 2004s I found the following hint:
http://help.sap.com/saphelp_nw04/helpdata/en/9f/c487d701c7214db8ca7a741ba3c9d0/frameset.htm
Configuring Logical Ports:
Logical ports (LPs) contain the configuration of the client-side SOAP runtime, such as the access URL or security settings. These are required if Web service calls are executed using proxies.
The Web service port is part of the WSDL description. This defines a URL where the service is to be called. As a rule, this URL is generated directly into the proxy object. However, this can cause problems whenever the proxy is transported into a system landscape (for example, from the test system into the productive system). In this case, the proxy would still attempt to call the Web service on the test server although the proxy should point to the productive system. The proxy could be re-generated or the coding could be changed manually. Due to the risk of errors with this method, the configuration data in the SAP Web Service Framework is separated from the implementation. After transport or re-deployment of the proxy, the URL and other important parameters can be adapted using a simple editor.
The LPs provided correspond to the Web service configurations created for the Web service.
My Question:
Where can I change the URL of the corresponding logical port at runtime?
I don't want to redeploy my application !!!
I want to change the endpoint-destination at runtime!!!
In the Visual Administrator I can see the webservice in the "Web Services Container Service Administration". I also can see the different ports from the WebService-Configuration I made.
http://help.sap.com/saphelp_nw04/helpdata/en/9f/c487d701c7214db8ca7a741ba3c9d0/frameset.htm
But it is not possible to change the "target adresses"!
Can anybody help me finding a solution concerning my question?
Regards
Steffen

You can include below method in your code and call it.
private void UpdateConfig(string key, string value, string fileName)
var cFile = ConfigurationManager.OpenExeConfiguration(fileName);
cFile.AppSettings.Settings[key].Value = value;
cFile.Save();
Here fileName is the full path + application name (eg: c:\project\WinApp.exe)
Adnan Amin MCT, SharePoint Architect | If you find this post useful kindly please mark it as an answer :)

Problems of logical port configuration

Similar Messages

Maybe you are looking for