Using Enterprise services in Visual composer - Cannot see meta data

[Former Member]

Hi

I have done the configuration to use enterprise service in Visual composer. I am able to see the services. But not able to get the meta data information. Kindly let me know what could be the issue and how to solve this.

Regards

Aruna

[Former Member]

Can't believe that nobody (including SAP) has provided a Solution for this. I don't know what it is worth for providing a ES Workplace if nobody can use it properly.

Dieter

[Former Member]

Hi Dieter!

I have the same problem (NW 2004s SP17). No solution found.

CU

Peter

[Former Member]

Hi there,

did anybody out there ever resolve this issue.

I am running NW04s SP17 and followed the HowTo to setup ES Workplace integration with Visual Composer. When using the data service ESR_WORKPLACE_800 in VC to access the Workplace I receive a list of all services. However when I click on the + sign in the list of services returned nothing appears to happen.

When I use ESR_WORKPLACE_800_METADATA instead I donu2019t get anything at all returned (Search is complete. There are no results to display).

I than switched on the Web service trace on the J2EE engine to see whether any helpful messages are returned. Also my system is not protected by a proxy\firewall therefore I did not do configure any proxy settings in Visual Admin and the Portal.

The messages I found in the trace are shown below but didnu2019t give me any indication on how to resolve this.

I have also tried to test this against my 7.0 ABAP instance in which I do have a couple of service defined. I defined the two connections as outlined in the HowTo pointing to my instance. The results is the same. I can see my four services but when I click on the + sign nothing happens and the same messages appear in the trace.

Any information on resolving this would be great.

Also I have tried all suggestions mentioned in this message and other messages regarding this problem including note 1128064 and SAAJ setting for WS connector sap.com/com.sap.portal.connectors.ws. None of them were successfull in resolving this.

Thanks. Dieter

Details from the Trace:

Selection in Visual Composer was for ESR_WORKPLACE_800 with search criteria CustomerSimple*

ESP API findWSInterfaces() for lmt=ESR_WORKPLACE_800 took 75875 ms. Number of results: 2#

#1.5 #000C29E60DAD006D000061520000114C0004658523F78C00#1237522415399#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Debug##Plain###RegExpMatcher.match(String,String) regExp: CustomerSimple* str: CustomerSimpleByNameAndAddressQueryResponse_In#

#1.5 #000C29E60DAD006D000061530000114C0004658523F78EF5#1237522415399#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Debug##Plain###RegExpMatcher.match(String,String) converting regExp to: (?i)CustomerSimple*#

#1.5 #000C29E60DAD006D000061540000114C0004658523F83078#1237522415446#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Debug##Plain###RegExpMatcher.match(String,String) regExp after convertStarToDotStar: (?i)CustomerSimple.*#

#1.5 #000C29E60DAD006D000061550000114C0004658523F8360A#1237522415446#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Debug##Plain###LMTFunctionsMetadata getInterfacesNamesSorted(String) groupRegularExpression=CustomerSimple* returning 1 results#

#1.5 #000C29E60DAD006D000061560000114C0004658523F83A72#1237522415446#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###LMTFunctionsMetadata getGroupNames(String) getGroupNames("CustomerSimple*") ended. Found 1 group names. Time to process (ms): 76016#

#1.5 #000C29E60DAD006D000061570000114C0004658523F84131#1237522415446#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###CCIConnection close()#

#1.5 #000C29E60DAD006D000061580000114C0004658523F8477D#1237522415446#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Debug##Plain###WSManagedConnection: close() Closing the CCI connection#

#1.5 #000C29E60DAD006D000061590000114C0004658523F84946#1237522415446#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Debug##Plain###WSManagedConnection: sendEventToListeners() Sending CONNECTION_CLOSED Event#

#1.5 #000C29E60DAD006D0000615A0000114C0004658523F91871#1237522415493#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Debug##Plain###WSManagedConnection: cleanup()#

#1.5 #000C29E60DAD006D0000615B0000114C0004658523F91B60#1237522415493#com.sap.portal.connectors.WebServices#sap.com/irj#com.sap.portal.connectors.WebServices#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_33##0#0#Debug##Plain###CCIConnection destroy()#

When I than click on the + sign I get the following messages in the trace.

#1.5 #000C29E60DAD0064000062B10000114C0004658529D54ECA#1237522513899#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###com.sap.guimachine.portalconnector.commandhandler.CommandException: No service was found for search criteria.#

#1.5 #000C29E60DAD0064000062B20000114C0004658529D590F7#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sap.portal.guimachine.htmlbkit.utils.CommandHandlerService.doDiscovery(CommandHandlerService.java:175)#

#1.5 #000C29E60DAD0064000062B30000114C0004658529D5917E#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#

#1.5 #000C29E60DAD0064000062B40000114C0004658529D59234#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#

#1.5 #000C29E60DAD0064000062B50000114C0004658529D59297#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#

#1.5 #000C29E60DAD0064000062B60000114C0004658529D592F1#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at java.lang.reflect.Method.invoke(Method.java:324)#

#1.5 #000C29E60DAD0064000062B70000114C0004658529D5934B#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sap.guimachine.portalconnector.commandhandler.AbstractCommandService.invoke(AbstractCommandService.java:83)#

#1.5 #000C29E60DAD0064000062B80000114C0004658529D593A9#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sap.guimachine.portalconnector.dispatcher.Dispatcher.handleCommandHandler(Dispatcher.java:180)#

#1.5 #000C29E60DAD0064000062B90000114C0004658529D59403#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sap.guimachine.portalconnector.dispatcher.Dispatcher.doContent(Dispatcher.java:127)#

#1.5 #000C29E60DAD0064000062BA0000114C0004658529D5945C#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)#

#1.5 #000C29E60DAD0064000062BB0000114C0004658529D5952F#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)#

#1.5 #000C29E60DAD0064000062BC0000114C0004658529D5958B#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#

#1.5 #000C29E60DAD0064000062BD0000114C0004658529D59634#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#

#1.5 #000C29E60DAD0064000062BE0000114C0004658529D5968D#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#

#1.5 #000C29E60DAD0064000062BF0000114C0004658529D596EA#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#

#1.5 #000C29E60DAD0064000062C00000114C0004658529D59744#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)#

#1.5 #000C29E60DAD0064000062C10000114C0004658529D5979B#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#

#1.5 #000C29E60DAD0064000062C20000114C0004658529D597F5#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#

#1.5 #000C29E60DAD0064000062C30000114C0004658529D59852#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#

#1.5 #000C29E60DAD0064000062C40000114C0004658529D598AC#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)#

#1.5 #000C29E60DAD0064000062C50000114C0004658529D59906#1237522513915#System.err#sap.com/irj#System.err#BAUERD#8188##OXMNFX399XI70_X34_344126550#BAUERD#ff987e90150411deb498000c29e60dad#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)#

[former_member307192]

Hi,

Did you solve your problem. I'm on SP14 and I have the same problem.

Let me know.

Jeff

[Former Member]

Hi

Please find more details on the error. In the log file this is the error i can see

An error occured while copying configurations for application sap.com/DynamicWSProxies/ESWPC_METADATA. Reason: com.sap.engine.frame.core.configuration.NameNotFoundException A configuration with the path "webservices/proxies/sap.com/DynamicWSProxies/ESWPC_METADATA/ESWPC/default/wss" does not exist.

Regards

Aruna

[Former Member]

Hi

I am not able to access the ES of the SDN.

You people are able to see them, I am even not able to see them.

I also made the 2 Proxies.

I set the parameters as follows:

Proxy Name: HU2_800

URL:http://erp.esworkplace.sap.com:80/

System ID: HU2

Client: 800

Language:EN

Authentication:BASIC

Username and Password: valid user name and password to access ES of SDN.

Proxy Name:HU2_800_METADATA

URL:http://erp.esworkplace.sap.com:80/sap/bc/srt/wsil

Rest of the parameters are same.

Please tell me where I am wrong.

Thanks

Vivek

[Former Member]

Hello Everybody

The ES available at SDN cannot be accessed outside SAP network because if we see the XML of the service available, the URLs within the XML are pointing to the internal hostname iwdf1030.dmzwdf.sap.corp of the system and not to the external hostname erp.esworkplace.sap.com. Unfortunately the internal hostname is not accessible or known to the internet and that is why we are not able to connect and retrieve the interface definition.

May be it will take some time to resolve this issuse, till then have a great time.

Regards

Vivek

Reward points if satisfied by the solution

[Former Member]

Hi Moderators

I kindly request you to please update the forum members regarding this issue because lot of us are facing it. Also if the comments posted by Mr. Vivek Mishra are valid then is there any possible work-around to consume ES in VC 2004s.

Any pointers/help will be greatly appreciated.

Regards

Kapil S Kamble

[Former Member]

Hi Vivek

Why am I able to successfully test and query the ESOA HU2_800 web services from my web service navigator but not able to connect to the same web service operations via the Visual Composer (VC)?

As an example, if I navigate to

http://mypotal:myportnumber/wsnavigator

and search for the following ESOA web service:

CustomerSimpleByNameAndAddressQueryResponse_In

using the following WSDL url

http://erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ecc_customer002qr?sap-client=800&wsdl=1.1&mode=sap...

I'm able to view the web service and test it through my web browser as expected.

Yet when I view the ESOA HU2_800 web services through Visual Composer, I see the web service tree as expected, but the web service operations within the tree nodes are not visible

For reference, my web service connection via the VC is through my local NW2004s portal which has direct access to the internet without having to go through a proxy

[former_member203343]

Hi David,

Can you please check whether note 1128064 is applicable here? It is applicable if you are on this SP level - I'll explain why:

1. Visual Composer uses the WebService connector to connect to all sorts of web services.

2. The WS connector is using an underlying layer of the J2EE that actually connects to the WS itself.

3. There are 2 underlying layers that can be used: The first (and the default one) is ESP. The second is SAAJ.

4. You can check which one is configured by going to Visual Admin->server->services->Connector Container->sap.com/com.sap.portal.connectors.ws->WebServicesFactory->ManagedConnectionFactory->Properties.

5. Change the currently configured "RuntimeMode" value to SAAJ and save. You'll need to restart the J2EE service.

6. Now, try to search for the operations in VC it should work (but only if you implemented the note - or you are on SP 14 and above.

Hope this helps,

Natty

[Former Member]

Thanks for the detailed response Natty

I've read the SAP Note (1128064) and it's clear that the issue described there , i.e.

Symptom

You are trying to use Web services that require authentication but either you get a "Portal request failed" or the connection test fails.

applies in the following circumstances

Reason and Prerequisites

You have SAP NetWeaver 7.0 SP12 or SP13.

My portal is at SP9. I have 5 NW2004s portal instance all at that same SP level, all displaying the same issue as I've described

The fixes in the SAP Note (1128064) are clearly for an SP12 or SP13 portal, and, based on this, are not applicable in my case

I should add that, I currently see the following when viewing the ESOA web services and in the Visual Composer, i.e. I can see the web services but do not see the web service operations.

[screenshot 1|http://www.flickr.com/photos/26324305@N02/2470532368/sizes/o/]

[screenshot 2|http://www.flickr.com/photos/26324305@N02/2470532534/sizes/o/]

Any other ideas?

Thanks in advance

[former_member203343]

Hi David,

We fixed it for SP12 and SP13 and on SP14. Unfortunately, you have to be on these SP level to have it work correctly... But from your description and the screenshots - it looks like you have the exact problem that was fixed by the fix in this note. Sorry, there is no other solution I can think about other than somehow be on SP14 or SP12-13 with the fixes.

Regards,

Natty

[Former Member]

Thanks again for the reply Natty

Based on this, it appears we'll have to bring our NW2004s portals up to SP14.

We've a number of issues which are also resolved in SP14 so we already have a plan to move up to this support pack

Hopefully this thread will help others facing the same issue

Thanks again

[Former Member]

Hi,

Can you give some details about your Problem with Clear Picture

Regards,

Govindu

[Former Member]

Hi

I am able to see the enterprise services listed when I do find data using ESWP_800. But when I use ESWP_800_METADATA I am not able to see the services. I have configured ESWP_800 and ESWP_800_METADATA. I have created dynamic proxies with this name.

Regards

Aruna