Endpoint destination

Hi all.
I got the problem to use a BAPI from R/3.
The endpoint destination is defined and I can use a BAPI in Visual Composer.
However if I use a callable object with callable object type "external service"
I get the notification "Cannot load BAPIs: set password"!
But I set the password in NetWeaver Administration of SAP NetWeaver CE when I defined the destination of my R/3 system.
It's weird because I can call a BAPI in Visual Composer.
Does anyone knows a solutions or was concerned with that problem?
Thanks a lot!
Stefen

check out line 49 where there's obviously something missing in the SOAP message that you're trying to retrieve from it outside a try/catch block.

Similar Messages

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

Air for Iphone NavigateToUrl

I am having an issue with using the navigateToUrl method when developing for the IOS using Flash Pro.
I am using the Addthis.com functionality to share things to twitter, facebook, etc. I use their api, which is actually super simple and just utilizes the navigatetourl method. When I test the method normally, it will successfully open up the iphone / ipod browser and navigate to the page. However, when I use it via the addthis class, clicking on the button to open the browser simply does nothing. The only real difference in how I tested it and the addthis work is that the addthis calls an additional class which then calls the navigateToUrl.
So my question would be "Does calling a class that does not initiate the navigatetoUrl method directly somehow break the method in IOS?" Using the same exact structure works 10)% in Air for Android btw.
Test code:
var request:URLRequest = new URLRequest("http://www.google.com");
navigateToURL(request);
addThis Code:
private function addThisToFacebook(e:MouseEvent):void{
     var share_url:String = "http://www.google.com";
        trace("Facebook Share Hit");
            api.share(share_url, 'facebook');
in the api class, the code is called up here:
    This is addThis.com api's code
public function share( url:String, destination:String='menu', options:Object=null ):void {
options ||= {};
var params:URLVariables = new URLVariables();
for (var k:String in DEFAULT_OPTIONS)
if ( DEFAULT_OPTIONS[k] || options[k] )
params[k] = options[k] || DEFAULT_OPTIONS[k];
params.url = url;
if ( stage ) {
if ( params.width == -1 )
params.width = stage.stageWidth;
if ( params.height == -1 )
params.height = stage.stageHeight;
if ( username )
params.username = username;
if ( destination == 'menu' )
destination = '';
var request:URLRequest = new URLRequest(ENDPOINT + (destination ? '/' + destination : '') + '/offer');
request.data = params;
navigateToURL(request, '_blank');
Is there something I can do/add for the navigateToUrl to work in IOS?

Hi,
Yes, that's reproducible at our end.
Thanks for reporting the issue,we're looking into the issue.
-Pahup
Adobe AIR

Best way to publish a collection to multiple publish services

Hi
I post a collection of images to Facebook, SmugMug and to a Hard Drive folder for syncing with my iPhone.
Currently I add all the photos I want to a regular collection. Once complete I select all and drag to each of the three Publish Services Collections and hit publish on all three. I've considered making the three Publish Services Collections Smart and telling them to include from the Collection that includes the name of my collection (really it would be helpful if there was a drop down list, but I digress).
Is there a better way of doing this? What is everybody else doing?
cheers, Lewis

I use export instead of publish.
Granted, I'm not using the web photo services that don't support change detection without the publishing (or are there export plugins that do support change detection and removal of obsolete photos - true sync stuff like publishing except via export?).
TreeSync - for hard drive export-based "publishing".
WebPhotos - for exporting photos for web consumption.
ExportManager - for one-click exporting of all changed photos to all endpoint destinations.
I have requested a feature, as have other publish plugin developers, for a hook so that publishing can be started programmatically (via plugins). If this feature is added to the Plugin SDK, then export-manager will be upgraded and renamed export+publish-manager...
Rob

BlazeDS and Flex Client Deployed on Different Servers

Hi, I setup a BlazeDS AMF endpoint on a different server from the server where my Flex app is deployed. I get the following error from my Flex app when trying to use this endpoint:
   faultCode: Client.Error.MessageSend
   faultDetail: Channel.Security.Error error Error #2048 url: 'http://cafrfd1y5css50.itsdo.abc.com:7000/sfaflexservice/amf'
   faultString: Send failed
   rootCause:
       [ChannelFaultEvent
        faultCode="Channel.Security.Error"
        faultString="error"
        faultDetail="Error #2048 url: 'http://cafrfd1y5css50.itsdo.abc.com:7000/sfaflexservice/amf'"
        channelId="my-amf"
        type="channelFault"
        bubbles=false
        cancelable=false
        eventPhase=2]
Btw, this setup works fine when my Flex app runs on AIR or as a Flex app (in a browser) from Flex Builder.
This looks like a crossdomain policy issue, so I setup a crossdomain.xml file on the BlazeDS server. When I point my browser to http://cafrfd1y5css50.itsdo.abc.com:7000/crossdomain.xml, I see the following:
    <?xml version="1.0" encoding="UTF-8" ?>
    <cross-domain-policy>
       <allow-access-from domain="*.abc.com" />
    </cross-domain-policy>
Looks good, but I get the same error...
So I monitored the interaction with Fiddler to see if the crossdomain.xml file is loaded. It is. When the service is activated, I see the following GET command in Fiddler:
     GET /crossdomain.xml HTTP/1.1
     Host: cafrfd1y5css50.itsdo.abc.com:7000
And the response contains the contents of the crossdomain.xml file, so I don't know what's going on.
My configuration is:
-- Browser: IE7 or FireFox v3.5 with Flash Player v10.
-- Flex app uses the 3.4 SDK and is deployed on a Tomcat v6 server.
-- BlazeDS server is WebLogic v9.
-- Endpoint definition from services-config.xml on the BlazeDS server is:
   <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">
     <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
   </channel-definition>
-- Endpoint in the Flex app is defined as follows:
   <channel alias="FlexBean">
      <channel_def>my-amf</channel_def>
      <endpoint>http://cafrfd1y5css50.itsdo.abc.com:7000/sfaflexservice/amf</endpoint>
      <destination>FlexService</destination>
   </channel>
Any ideas would be much appreciated...
thanks,
matt

Thanks for the reply, Alex.
I tried setting the domain in the crossdomain policy file to "*", but I got the same error, so I turned on client side logging. The error in the log was:
Error: [strict] Ignoring policy file at http://cafrfd1y5css50.itsdo.abc.com:7000/crossdomain.xml due to missing Content-Type.
See http://www.adobe.com/go/strict_policy_files to fix this problem.
Using Fiddler, I checked the content-type that WebLogic was using for crossdomain.xml. Much to my surprise, there wasn't a content-type in the response, only content-length. So in the web.xml file for this application, I added the following:
<mime-mapping>
    <extension>xml</extension>
    <mime-type>text/xml</mime-type>
</mime-mapping>
Now, the crossdomain.xml file is served with a content-type of "text/xml", and the call to the BlazeDS endpoint works.
Thanks for steering me in the right direction, Alex.
cheers!
matt

Deleting list of assets

Hello,
i want to delete a list of assets with a criteria. Assets are related objects to accounts.
With other objects i can do it but the help said it's only possible with lists of accounts, contacts, opportunities, leads, service requests, or activities.
Has somenone an idea how to realize this.
Regards,

Hello i tried to use a web service in C# to delete the Assets but my skills are rudimentary.
I managed to see the Assets of the accounts in a web service, but i do not get the next step with the deletion auf the child object. I do not know which Parameters i have to give to the AccountChildDelete command.
This is the code for the deletion but it does not work
//Create the input paramaters for the Delete web Service call
objAccountDeleteChildParam = new Account.WSOD_Account.AccountWS_AccountDeleteChild_Input();
objAccountDeleteChildParam.ListOfAccount = objListOfAccount;
//Create a new Account proxy\web service object
prxySrvcAccount = new Account.WSOD_Account.Account();
//Set the endpoint\destination for the web service call
prxySrvcAccount.Url = mSession.GetURL();
//Call the account delete method on the account web service
objAccountDeleteChildOut = prxySrvcAccount.AccountChildDelete(objAccountDeleteChildParam);
Could somenone give me plz an example, if he managed to delete ChildObjects?
Regards,

[svn:bz-trunk] 19769: Add destination and two streaming endpoints to test the invalidate-messageclient-on-streaming-close setting .

Revision: 19769
Revision: 19769
Author:   [email protected]
Date:     2011-01-14 12:05:23 -0800 (Fri, 14 Jan 2011)
Log Message:
Add destination and two streaming endpoints to test the invalidate-messageclient-on-streaming-close setting.
Modified Paths:
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/messaging-config.mods.xml
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/services-config.mods.xml

Originally Posted by namal
Hello,
can you please reupload the file again? The link doesn't work. I really need this driver pack for the Audigy 2 NX. I had Windows 7 and i don't want to buy a new external Sound Card for my notebook. Much thanks for the great work.
In case you still require your driver and Alchemy, here are the links for the Audigy 2 NX
Downloads Page
http://support.creative.com/Products...05&prodID=9103
Driver
http://support.creative.com/download...wnloadId=11994
Alchemy
http://support.creative.com/download...wnloadId=12579

JMS Distributed Destinations as proxy service endpoints

We have a cluster of 2 ALSB servers with a proxy service deployed
listening on a JMS queue which is a distributed destination (DD) on a
WLS 8.1 system.
The JMS DD is spread across 4 JMS servers and 4 JVM's.
When ALSB starts up - we only get consumers on 2 of the 4 DD members,
which makes sense as a JMS proxy service is essentially an MDB, and this
is normal MDB/distributed destination behaviour - it will bind to the
queue member where it first makes the connection to the JVM.
How do I make sure my messages are consumed from all 4 DD queue members?
There is a JMS option to forward messages to queues with consumers if no
consumers exist - is that the way to do it?
Someone must have come across this before and I'd be grateful for any
advice.
Also - how do you reduce the consumers on the JMS queue - seems to
default to 16. Perhaps you don't.
Thanks,
Pete

Meghan Pietila wrote:
Update: I see your exchange with Tom over on the JMS forum, Pete. We just switched everything to WLS 9.2, so maybe the ALSB internal extension will work for us. It's not working by default, so possibly it's something that must be activated... I'll follow up with BEA.
http://forums.bea.com/thread.jspa?threadID=570001317
I'd still like to hear what you end up working with, if you don't mind sharing once it's running. :)
MeghanI only have 8.1 as an option - a JMS proxy service is essentially an
MDB, and if you deploy an MDB in the same way, it will only bind to a
single destination, so it's actually behaving as I would expect.
The forward delay on the queue probably won't be an issue for us, as
we're not talking about high volumes and large messages, but for some
sites there will be alot of moving around queues, access jms filestore
etc which you could do without.
I reckon the trick is (as Tom mentioned) to bind to individual
distributed queue members from the proxy service somehow.
I'll let you know what I find out.
Pete

Error while testing the endpoints in Service Registry

Hi,
I am getting the following error while testing the endpoint in the Service Registry
Invalid Response Code: (404) Not Found. The request URL was:"http://<server>:8000/sap/bc/srt/wsdl/bndg_DD73518A3AD471F18558001D0910D3CA/wsdl11/binding/ws_policy/document?sap-client=800". Check, whether the URL is correct, and the Web Service that you are requesting is up and running.
I have created an Enterprise Service at the backend and have published to the Service Registry of the CE server , but while testing the endpoint in service registry i am getting error.
Can any one please help me to solve this issue.
Thanks & Regards,
Hamsa Shree

Hi hamsa,
Have you tested the service? If It works, maybe there's something wrong with your destination configuration.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/705459a3-bf1c-2b10-8a9d-d300ada5f0fc
You may find a solution in the above article.
Good luck!
Wenhao

Destination does not exist (help please)

Background:
- Using Flex Builder 3 plugin for Eclipse
- Downloaded latest BlazeDS release build
- Running Tomcat 6.0.16
=======
First I want to note the samples that come with BlazeDS run
absolutely fine.
So I created a new project in Flex Builder 3. I'm just trying
to get something simple working at first so my one mxml file is as
follows (I stripped out everything except the code in question):
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
<mx:RemoteObject id="ro"
destination="enrollmentService"/>
<mx:DataGrid
dataProvider="{ro.getEnrollmentList.lastResult}" width="100%"
height="100%"/>
<mx:Button label="Get Data"
click="ro.getEnrollmentList()"/>
</mx:Application>
=====
I created and EnrollmentService class and I'm sure it's
getting compiled to WEB-INF/class...I see .class file there.
I added the flex folder to the WEB-INF folder. My
remoting-config.xml is as follows (because of problems I specified
a default and repeated it to be sure):
<?xml version="1.0" encoding="UTF-8"?>
<service id="remoting-service"
class="flex.messaging.services.RemotingService">
<adapters>
<adapter-definition id="java-object"
class="flex.messaging.services.remoting.adapters.JavaAdapter"
default="true"/>
</adapters>
<default-channels>
<channel ref="my-amf"/>
</default-channels>
<destination id="enrollmentService">
<properties>
<source>test.service.EnrollmentService</source>
</properties>
<channels>
<channel ref="my-amf"/>
</channels>
</destination>
</service>
My services-config has the following channel defined:
<channel-definition id="my-amf"
class="mx.messaging.channels.AMFChannel">
<endpoint url="
http://{server.name}:{server.port}/{context.root}/messagebroker/amf"
class="flex.messaging.endpoints.AMFEndpoint"/>
<properties>
<polling-enabled>false</polling-enabled>
</properties>
</channel-definition>
My web.xml is a follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD
Web Application 2.3//EN" "
http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<display-name>RemoteTest</display-name>
<context-param>
<param-name>flex.class.path</param-name>
<param-value>/WEB-INF/flex/hotfixes</param-value>
</context-param>

<listener>
<listener-class>flex.messaging.HttpFlexSession</listener-class>
</listener>

<servlet>
<servlet-name>MessageBrokerServlet</servlet-name>
<display-name>MessageBrokerServlet</display-name>
<servlet-class>flex.messaging.MessageBrokerServlet</servlet-class>
<init-param>
<param-name>services.configuration.file</param-name>
<param-value>/WEB-INF/flex/services-config.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>MessageBrokerServlet</servlet-name>
<url-pattern>/messagebroker/*</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
</welcome-file-list>
</web-app>
====
So I start Tomcat from Eclipse and run the app by clicking
the Run button in Eclipse. The app comes up fine, but when I press
the "Get Data" button. I get the error message below. For the life
of me I don't understand why. I clearly have a default channel AND
I have specified a channel. This is so frustrating...any help would
be greatly appreciate.
====
[RPC Fault faultString="[MessagingError message='Destination
'enrollmentService' either does not exist or the destination has no
channels defined (and the application does not define any default
channels.)']" faultCode="InvokeFailed" faultDetail="Couldn't
establish a connection to 'enrollmentService'"]
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::invoke()[E:\dev\3.0.x\frameworks\projects\rpc\ src\mx\rpc\AbstractInvoker.as:257
at mx.rpc.remoting.mxml::Operation/
http://www.adobe.com/2006/flex/mx/internal::invoke()[E:\dev\3.0.x\frameworks\projects\rpc\ src\mx\rpc\remoting\mxml\Operation.as:197
at
mx.rpc.remoting::Operation/send()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\remotin g\Operation.as:113]
at Function/
http://adobe.com/AS3/2006/builtin::apply()
at
mx.rpc.remoting.mxml::Operation/send()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\re moting\mxml\Operation.as:170]
at Function/
http://adobe.com/AS3/2006/builtin::apply()
at mx.rpc::AbstractService/
http://www.adobe.com/2006/actionscript/flash/proxy::callProperty()[E:\dev\3.0.x\frameworks \projects\rpc\src\mx\rpc\AbstractService.as:285
at
FlexJ2EE_test/___FlexJ2EE_test_Button1_click()[C:\Prj\workspace\RemoteTest\flex_src\Remot eTest.mxml:36]

While creating a Flex project using Flex builder, did you
select the server type for your project? If you did not select a
server type for your flex project, did you configure your compiler
to include your services-config.xml using the -services argument?
In your project's compiler settings, add -services
"configurationfiles/services-config.xml" argument to the compiler
arguments. The path should point to your services-config.xml.
If the above mentioned steps were completed and still your
facing problem, can you please try running "clean" on your project.
Hope this helps.

Error while publishing a service with WSPUBLISH: Error publishing Endpoint

Hallo,
I've a problem while publishing a service which a had created via proxy. I configured the service and one endpoint (binding) in SOAMANAGER. When I publish the service in WSPUBLISH I get the error:
'Error publishing Endpoint for SD : <Proxy>, Service : <Service>, EP : <Endpoint>.
with details:
'10160A save request exceeded the quantity limits for a given structure type .#Number of BusinessEntities exceeds your limit of 1 (2)'
In the Service Registry I can find the service but without endpoints.
Does anybody know what happend ?
We use a SAP NetWeaver 7.10 with SP05 (SAPKB71005) but the same error happens if I publish a service from a CRM 5.0 with SP15 (SAPKB70015) to the Service Registry of the 7.10
Christoph

This is my steps to publish ES to SR:
1. Create RFC destination in SM59
2. Create ES Parameter in WSPARAM
3. Create logical port for SR in LPCONFIG
4. Release Web Service for SOA Runtime in WSCONFIG
5. Publish ES in WSPUBLISH.
When i was using SOAMANAGER to manually create the endpoint, the endpoint in the SR doesnt works though.
eg, Business Administration -> WS Administration -> Search for CRM_BPBASICDATABYIDQR -> Apply selection -> Configuration -> Create Service -> enter new service name and new binding name -> user id/password for HTTP Authentication -> save.
It works after i released it in WSCONFIG (ya, i know it's old way) and re-publish.
-julius

EJB 3.0 - Destinations not specified

Hi,
I am trying to deploy a J2EE application supporting EJB 3.0 on SAP CE 7.1 . During the deployment using NWDS , i am getting the error as "Destinations not specified".
However , i have already preformed below listed steps :
--> I have specified the queue and connection factory in the ejb-j2ee-engine.xml
--> I have created the queue and the connection factory on the SAP server.
--> I have included them in the jms-factories.xml , jms-destinations.xml and jms-resources.xml in the EAR file.
Please provide suggest proper steps to be taken to resolve this error.
Thanks
Swati
Error Details :
#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle##
#1.5 #00505633661C001B000015CE000006880155CE07CF9994EF#1268287309660#/System/Server/Deployment##com.sap.engine.services.tcbldeploy_controller#Administrator#87021####5c9611f02aaa11dfabca00505633661c#Thread[RMI/IIOP Worker [4],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcbldeploy_controller#Plain###Exception has been returned while the 'JavaEE/wpServerPlus' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 9620950:com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean JavaEE/wpServerPlusxml|wpServer.jarxml|ServerAutomatedActivityMDBean
     at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:893)
     at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:425)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.services.ejb3.container.ActionException: Cannot activate endpoint for message-driven bean JavaEE/wpServerPlusxml|wpServer.jarxml|ServerAutomatedActivityMDBean
     at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:94)
     at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
     at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:59)
     at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:887)
     ... 34 more
Caused by: javax.resource.spi.InvalidPropertyException: Destination not specified!
     at com.sap.jms.resourceadapter.ActivationSpecBean.validate(ActivationSpecBean.java:88)
     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:446)
     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByName(EndpointActivationImpl.java:154)
     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:85)
     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:58)
     at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:84)
     ... 37 more

Hi
[Help|http://help.sap.com/saphelp_nw04/helpdata/en/37/30c557fad05341a951cfd051bf0b44/frameset.htm]
BR
Satish Kumar

FYI: Extension Builder project w/ LCDS: channel-definition endpoint having context.root

This is an FYI of an issue and its workaround.
If developing a CS SDK Extension in Flash Builder / Extension Builder and the project is configured to use LCDS (LiveCycle DataServices), then if your services-config.xml contains Channel definitions having the variable {context.root} in the endpoint URL, then the following error will occur. This will happen even if you are not using that Channel in your Destination channel list.
The services-config.xml laid down when using LCDS integrated into ColdFusion has by default some channel definitions using context.root in the endpoint URLs.   This is how I encountered the issue. On the other hand, the free developer edition of LCDS on Tomcat puts down a services-config.xml that does not have any reference to {context.root} in channel definitions, so the problem will not be encountered there.
Since I was not using a context root (was using the default of just "/"), I commented out the offending channels in services-config.xml to resolve the issue. One could also leave the (unused) channel definitions and then remove the {context.root} part from the endpoint.
ERROR
The services configuration includes a channel-definition 'java-amf' that has an endpoint with a context.root token but a context root has not been defined. Please specify a context-root compiler argument.
CHANNEL DEFINITION

        <channel-definition id="java-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint uri="http://{server.name}:{server.port}{context.root}/flex2gateway/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
        </channel-definition>

Make sure your context root is defined in the project properties. This is at "project/properties/Flex Server" from the menubar or package explorer context menu. Alternately, you can hardcode your context root in the services-config.xml file/channel definition.

Endpoints not published in Service Registry

Hi all,
I have published all the Enterprise services from the Discovery system(ECC) and they are available within the service registry.
But somehow the endpoints are not published to the Service Registry because of which I am not able to consume the services for UI development in VC.
I have the following concerns :
1) The ES are being tested successfully but not being sure why the endpoints were not published when the Services were published from the Discovery System.
2) Can we forcefully create the endpoints in the Service Registry. If so, plz let me know the procedure.
3) SP13 is applied on Discovery System, so I am not able to execute TCode SOAMANAGER to create Endpoints, so is there any other alternative, other than upgrading ECC to SP14.
Points will be rewarded for any help
Regards Brian

Hi Brian,
Maybe the issue is wrt the Service Registry destination definition. The correct system name should be picked from the SLD system name (under http://host:port/sld) definition (I think it CE1 by default). You can also refer other issues I faced in a similar situation that i documented in thread [Endpoints not published in Service Registry;
I take my earlier comment about using the Publish function in Service Registry. I learn it should be not be used.
As regards the ServicesRegistrySi(Proxy Definition) URL, I guess you can use http://localhost:port/ServicesRegistrySiService/ServicesRegistrySiPort?wsdl&mode=sap_wsdl
Regads
Suresh

Web Service Endpoint URI expected. Not found endpoint with URI /wssproc

Hi All,
We are following the steps mentioned here http://help.sap.com/saphelp_nwpi71/helpdata/en/ea/c91141e109ef6fe10000000a1550b0/frameset.htm to configure the message level security in our new PI 7.1 system.
We have created the RFC destination with prefix /wssproc/plain?style=document. But when we test the RFC connectioon, we get the following error message:
Status HTTP Response 404
Status Text Not Found
And response body is: Web Service Endpoint URI expected. Not found endpoint with URI /wssproc.
Are we missing a configuration point? Do we need to create the endpoint manually? And if yes, how?
Regards,
Masoud
Edited by: Masoud Ahanchian on Jul 23, 2009 4:58 PM

Well, in addition to the 404 message I get the following error as well (i.e. if I go to the link http://<server>:<port>/wssproc/plain?style=document)
Web Service Endpoint URI expected. Not found endpoint with URI /wssproc.
Regards,
Masoud

Endpoint destination

Similar Messages

Maybe you are looking for