Web logic port

Do anybody know what port web logic listens to by default? I am trying to browse an JSP page. I do not know how. Thanks - Malathi.

Monowai was perfectly rite but to be more precise..
          7001 for the non-secure mode and
          7002 for the secure (SSL) mode but you wud have to configure that.
          Regards
          -Manav
          "Monowai" <[email protected]> wrote in message
          news:3a913739$[email protected]..
          >
          > 7001
          >
          > Malathi Sekkappan <[email protected]> wrote:
          > >Do anybody know what port web logic listens to by default? I am trying
          > >to browse an JSP page. I do not know how. Thanks - Malathi.
          >

Similar Messages

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

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

Logical port error when accessing e-recruiting web pages

Hi,
We are trying to set up our e-recruiting 3.0 and web dispatcher systems. We were receiving an error in our e-recruiting system in transaction SM20 that states Logon Failed (Reason=34, Type=H). The user is SAPSYS for client 000. The system was attempting to log on to our web dispatcher system. SAP suggested creating an entry in SM30, table VUSREXTID, mapping the External ID to our web dispatcher system. This entry helped in that we are not receiving the above error message anymore. However, when we attempt to access the web pages we are receiving the error Name of logical port &lp_name& is invalid. Prior to adding this entry we were able to access the logon page by entering the following url using an external alias (ex. https://recruiting.mphi.org/internal). Recruiting.mphi.org is our web dispatcher system. We do not want our e-recruiting system to be accessible from the outside. We want everything to go through our web dispatcher. Has anyone had a similar issue setting these up?
Thanks!
Heather

Hello Heather,
I am no specialist in network infrastructure but i remember a customer setting up a web dispüatcher szenario. I also encountered this &lp_name& error from time to time during my work.
The error points towards damaged urls and the customer also encountered such problems when setting up the web dispatcher landscape. Sometimes the last parameter of the URL was ignored or lost. Sometimes the web dispatcher transformed the URL including the parameters. But as parameters are case sensitive transforming them to upper/lower result in errors as the system no longer recognizes them.
Perhaps you can check the URL with which the web dispatcher is calling the sap server to find out if it does any funny things w/ the links.
Best Regards
Roman Weise

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

How to check web service (logical port) accessibility

Before call some web services, a check needs to be done to make sure the web service connection is accessible. In fact, a logical port is used; and its accessibility needs to be checked in ABAP code.
Besides calling the web service method itself and catching the exception, is there any other general way to check whether the web service connection available?
more details in respect of this question:
The executing of web services will take a relative long time while sometimes only the availability checking for web services is needed. So I'm finding other ways to check that.
In the code, the logical port will be used for accessing web services. Any way to check whether a logical port works OK in code?
Thanks!
Said
Message was edited by:
Sayid Tong

Hi Prashant,
Thanks for your attention.
Do you mean give the web service url and check it? Neither do I know which method can be used in this regarding from program RSDEMO_HTML_VIEWER.
I'd like to give more details in respect of this question:
The executing of web services will take a relative long time while sometimes only the availability checking for web services is needed. So I'm finding other ways to check that.
In the code, the logical port will be used for accessing web services. Any way to check whether a logical port works OK in code?
Thanks.
Said

Calling external Web Service: PI is looking for a logical port and proxy.

Hi,
My scenario is ECC Proxy -> PI -> External Webservice (WS adapter).
the Web service adapter fails with the error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">WS_ADAPTER_SYS_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>System error while calling Web service adapter: Error when initializing SOAP client application: 'error_text'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When I debug the message processing, it is looking for a port in table SSRVRTCONFIG, finds it(entry created automatically when WS adapter and the corresponding receiver agreement is activated in ID.
Then the program looks for an entry in "SRT_CFG_CLI_ASGN" for a proxy and logical port combination and errors out.
to be able to call an external web service, do we need a proxy to be created? I tried to create but the proxy creation fails because the external WSDL has some unsupported tags.
Also do we need to do any other configuration in SOAMANAGER? I am assuming not because the Web service is external.
Any help would be appreciated.
Thanks
Vijay

I already checked that note and made sure that the points mentioned are met. I have a trace set up on the target system and would know if the call reaches them and then fails in authorization. Right now the call doesnt even reach the target system and also from debugging I know that the program is looking for a proxy and then fails.

About logical port used to call Web service

Hi Experts:
I found that logical port can be created either from "LPCONFIG" or "SOAMANAGER"， They can't be found from the other transaction. What's the difference between them? Which one should be used in cases?
Wayne

One is a SAP GUI based transaction and the other is a WebDynpro based transaction. SOAMANAGER controls many more things than just logical port maintenance though and is the central location for runtime web service configuration. It's available with NW 7.0 SP14 or higher. You can still use either transaction after NW 7.0 SP14, but get in the habit of using SOAMANAGER.

No logical port to call web services

Hi all,
Via MOPZ, after I selected files to my download basket, and reached Download Files steps, the following message is prompted and the Download button is disabled:
No logical port to call web services
What are the setting I should do to setup the logical port ?
Thanks in advance.

I fix the S-User assignment and it works

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.

Change default port number for web logic!

Hi folks,
In my scenario, i already installed obiee 11g with simple install along with web logic on windows xp machine.where this will creates default port number for all services. now i want to change default port number of web logic that is 7001 to some to other port number. how to change this ??.plss help me asap.
regards,
mahesh

Refer tohttp://www.oracle.com/technology/documentation/1012_solaris/install.1012/install/ports.htm

** Logical Port in Client Proxy

Hi Friends,
I am doing proxy to web service scenario. My proxy is client proxy. After I created proxy, I checked that. There is no standard method 'EXECUTE_ASYNCHRONUS'. I read the Michal's blog /people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method and understand that this method is not created. The reason is that SAP_BASIS support package level is 15. (Release 700) in our R/3 ECC 6.0 system.
Now, I am not able to test my proxy from SPROXY tcode. It asks Logical Port.
1. Can you tell me, what is logical port ? How do I create this in LPCONFIG tcode ?
2. Once this is done, can I call the class with the method like in older version ?
3. Currently I am getting the information 'No vendor specified' while test proxy withe empty logical port.
Expecting your reply.
Kind regards,
Jegathees P.

Hi Rene,
If a logical port is not configured, the X/PI Runtime will be used instead.
In Jegathees' case, this is probably what happened. If you want to route your message through PI then you need to make sure that you are pointing to your Integration Server (i.e. PI), on ECC use transaction code SXMB_ADM --> Integration Engine Configuration. Role of Business System should be "Application System" and "Corresp. Integration Server" should be your PI server.
You will see when you test your client proxy (using TCode SPROXY) you have the option of choosing XI Runtime - or - Logical port too.
Regards, Trevor

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 :)

Error while creating logical port for Reporting

Hi,
In one of the training materials for Duet Enterprise, i saw the steps for creating logical port for the consumer proxy /IWTNG/CO_PXY_RECORDS_REPOSITO.
When i am trying to create the logical port, i am getting an error saying,
" SRT Framework exception: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:500 Native SSL error
https://<server:port>/_vti_bin/OBAFileReceiver.asmx?wsdl "
I would like to know is it really necessary to create this logical port for "Reporting Scenario" and is it not created automaticallly using the Installation Wizard??
And in case it has to be created, how to resolve this SRT framework exception?
~ Ramanath.

Hi,
the consumer proxy /IWTNG/CO_PXY_RECORDS_REPOSITO was used in Duet Enterprise SP01. Now with SP02 the consume proxy /IWTNG/CO_OBAFILE_RECEIVER_SOA is created.
However, the SSL error that you are getting looks a little strange (it does not mean that there is an error, but it is worth checking):
So can you go to SOAMANAGER -> Service Administration -> Single Service Configuration. In here select "Consumer Proxy" from the "Search by", Search Pattern "/IWTNG/CO_OBAFILE_RECEIVER_SOA" and Field: Both.
You should find one entry. Select it and click "Apply Selection".
Now go to the Configurations tab. Here you should see one Logical Port with name "LOGICALPORTFORREPORTING" with Creation Type "Manually Created". In fact this logical port was created by the Wizard.
Click on Display and scroll down again. Now in the "Additional Information" tab there is a string after HTTP Destination, e.g. 0050568E3F5A1ED096F22339C44BAF83.
Copy this value and go to your SAP GUI -> Transaction SM59.
Here click on Find/Search and search for this HTTP Destination. You should find one Type G RFC Destination that has the target host of your SharePoint server and the path prefix /_vti_bin/OBAFileReceiver.asmx.
Now you can test the service. Just click on Connection Test. The result should be a HTTP Response: 200.
If not, then something went wrong with the automatic configuration and we should take another look at it (for example maybe the SSL certificate from SharePoint that was imported by the Wizard is not valid)
Regards,
Holger.
PS. Don't use the "Ping Web Service" test from SOAMANGER -- unfortunately this is not working consistently.

Web logic port

Similar Messages

Maybe you are looking for