Point a logical Port in the backend to XI

Hi friends,
how do i point a logical port in backend to XI,how do i derive the XI url to be
pointed.
regards
kaushik

Are you asking about setting the Port in WE21?
This just points to a standard RFC ABAP Connection to the XI System.
Or are you asking about the integration engine config in SXMB_ADM? - again, it points to SM59 HTTP Connection to ABAP System (the port for this would be 80<sysno>)

Similar Messages

Read logical port for the proxy

HI ,
There is method or FM that can bring all the logical port that available for proxy class,
logical port that defined on SOAMANAGER or LPCONFIG .
Regards
Joy

Try this way
    call function 'RFC_READ_TABLE'
         destination                rfc_sys
         exporting
              query_table          = 'SRT_LP' " Table for Logical Ports
         tables
              options              = options1
              fields               = nametab1
              data                 = i_srt_lp[]. " Output table contains call values for proxy class after fm call
a®

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.

SM59 : change the field comment (logical Port by wsdl)

Hello,
I consume a webservice.
I have created a logical Port by wsdl in the soamanager. After saving the logical Port, a http connection is created in SM59.
In the transaction SM59 'HTTP CONNECTIONS TO EXTERNAL SERVER" <Automatische Web Service Konfiguration> is automatically written into the comment field.
http://www.pictureupload.de/originals/pictures/090312102328_sm59_G_typ.JPG
My problem is, this comment cannot be changed by hand.
Does anybody know, how I can change the field comment by hand in SM59 (when I have created a logical Port in the soamanager)?
best regards,
Stephan

hI,
Please go through this link , you will get the solution
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/media/uuid/20eb3174-41ab-2a10-a383-907faf60eed3

Error in Logical port for Consumer proxy in SOAMANAGER

HI Experts,
While creating Logical port for Consumer proxy in SOAMANAGER I am facing problem
"SRT Framework exception: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL ".
Kindly suggest.

Hi Milan,
this kind of error occurs when there is no service and end point description in the WSDL of provider who's service you are trying to consume using Consumer Proxy.
Just open the provider's WSDL URL that you have given while creating Logical port for the consumer proxy and check if service and end point exists there.
Thanks
Sunil Singh

Example wsdl and logical port for consumer proxy anyone ?

Hi,
Could please somebody give me an example of external WSDL file and logcial port created for the WSDL file in SOAMANAGER ?
I need to create manually logical port for my consumer proxy and I am missing something because my logical port is not active.
Any example is more than welcome.
I need to know how to populate fields manually on the following tabs based on the info in a WSDL file:
Consumer Security Additional Information Web Service Addressing Messaging Transport settings Message Attachments Operation specifi
Thanks and Regards
Agnieszka
The message, I am getting, when creating logical port is:
Operation 'SrtFmStatefulTf' not found [NS: 'urn:sap-com:document:sap:soap:functions:mc-style']
I think that maybe something is wrong with my wsdl.
Edited by: Agnieszka Domanska on Nov 17, 2010 5:41 PM

Hi Milan,
this kind of error occurs when there is no service and end point description in the WSDL of provider who's service you are trying to consume using Consumer Proxy.
Just open the provider's WSDL URL that you have given while creating Logical port for the consumer proxy and check if service and end point exists there.
Thanks
Sunil Singh

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.

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.

Error while creating logical port from WSDL in SOAMANAGER

Hi,
I am trying to create a logical port for the webservice TerritoryCRMBasicDataByIDQueryResponse_In with the WSDL
http://usciq9e.wdf.sap.corp:50077/sap/bc/srt/wsdl/sdef_TERRITORYCRMBASICDATABYIDQUERY/wsdl11/ws_policy/document?sap-client=506
In SOA Manager, I selected the proxy object and clicked on 'Create Logical Port' ,
gave the name and description for the port and set it as default.
The other settings are :
Configuration type : WSDL based configuration
WSDL base is : Via HTTP Access
Then I gave the address of the WSDL in the URL and the proper username and password. When I clicked on 'Apply Settings' I get the following error:
"Error when building binding view: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL "
Please advise me on how to approach the problem.
Thanks,
Sashi

Creating logical ports is done here:
http://help.sap.com/saphelp_nwpi71/helpdata/en/44/cc8fd368c873dfe10000000a11466f/frameset.htm

Change the backend doc type from PR to PO in BADI BBP_TARGET_OBJECTS.

Hi,
We have followed below approach for backend document type determination.
1. A custom function module contains the logic to determine the backend document type of a Shopping cart line item. THis function module, performs many checks and hence cannot be called in any BADI that is executed in Foreground.
2. I am using BADI BBP_TARGET_OBJECTS to change the follow document type by calling the custom function module.
Issue here is, if the backend document type of a line item is Purchase requisition (2) by SAP standard, and if I try to change it to Purchase order, it gives run time error and ends up in creation of Purchase order.
After further investigation I found that this line item (with default backend doc type as 2) has a desired vendor. If we change the desired vendor of this line item to fixed(To Partner function 19 from partner function 39), it allows us to change the doc type from Purchase requisition to purcahse order in BADI BBP_TARGET_OBJECTS.
But changing the partner function is possible only in BBP_DOC_CHANGE BADI, and I cannot call the custom function module there, as it may impact the performance.
Is there any other way, I can change the partner function in any of the BADIs called in background?
Or Is there any way by which I can change the backend document type from PR to PO in BBP_TARGET_OBJECTS?

Hi Parab
if you swaping 39 to 19 viadoc change badi
REQUESTER has a control on Purchase ORDER Vendor and BUYER lost a control so your business has to decide.In this case procurement department lost their control.
Fixed vendors are like inforecord and contract negotiated for best price ..
Muthu

Error in Logical Port Creation

Hi,
When I try to create a logical port in my consumer system I am getting error
"Error: HTTP: Error in interface for management of HTTP destinations; "
Any ideas on how to fix this?

Sorry - I should have been more clear earlier.
I am using SOAMANAGER to create the logical port. The error occurs when I choose 'WSDL Access Settings' to obtain the WSDL. I was able to get around the problem by going into SOAMANAGER on my provider system, locating the service & binding I want, and then downloading that file. This is a workaround as I would like to get the file via HTTP access.
I suspect this has to do with configuration but I do not know where this needs to be setup.

Logical Port

Hi.
I have downloaded a wsdl file from a BAPI in r/3 4.7. I have created a Proxy object in neatwever 2004s client. I created the logical Port for the Proxy Class.
When I tested the Proxy class I get the followinf error
<CODE>ERROR_WEBSERVICE_RUNTIME_INIT</CODE>
<ERRORTEXT>Error when instantiating the Web service runtime (Logical port 'DEMO' for proxy class 'ZDEMO_ BAPI_SERVNOT_CREATEPOR' is not active )</ERRORTEXT>
Please Advice

I found the problem. The Logical Port needed to be activated indeed.

Preserving SOA Logical Ports and Trust Relationships during DB Refresh

Hi,
I have been searching for this for a while and have not had any luck so far. I thought maybe the vast experience in this community might be able to help me.
I am trying to preserve the SOA Logical Ports and the SMT1 Trust relationships of the target server during DB Refresh. Is there a list of tables that we could export (Much like exporting/transporting RFC Destination)?
Regards
Shantanu

Hi
Check the here under tables if they fits to your needs
Regards
SRT_LP                       Logical Ports
SRT_LP_FEAT            Logical Port Feature
SRT_LP_OP_FEAT     Logical Port Feature (Operation-Dependent)
SRT_LP_SXI_ADDR   Logical Ports: XI Addressing
RSECACTB                 Table for ABAP Access Authorization for Secure Memory
RSECTAB                    Secure Memory: Memory for Encrypted Data
RFCTRUST                 List of existing trusting systems
RFCSYSACL               List of permitted trusted systems for the current system

Logical port creation error through SOAMANAGER

Hi,
When I try to create a logical port through SOAMANAGER I got the following error.
Error: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL
When I actually look into the class CL_SRT_WSP_CONFIG_SIDL I could'nt find the method CREATE_CLNT_CFG_FROM_WSDL_D in SAP 720 version.
I had seen some discussions in the forum on this error but I could'nt find a proper solution.
Can someone explain me on how to resolve this issue.
Do I need to apply a oss note ? Is it mandatory. Also in one thread they talked of SICF transaction usage which is also not clear. Is there any other way.
Thanks,
Shashi

Sorry - I should have been more clear earlier.
I am using SOAMANAGER to create the logical port. The error occurs when I choose 'WSDL Access Settings' to obtain the WSDL. I was able to get around the problem by going into SOAMANAGER on my provider system, locating the service & binding I want, and then downloading that file. This is a workaround as I would like to get the file via HTTP access.
I suspect this has to do with configuration but I do not know where this needs to be setup.

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

Point a logical Port in the backend to XI

Similar Messages

Maybe you are looking for