NetStream client handler

Hi,
I want to add an handler for onMetaData on my netStream Client.
The onMetaData function is never called, but I know that the .flv file I'm playing contains metadata...
public class CustomNetStream extends NetStream
     public function CustomNetStream(connection:NetConnection)
        super(connection);
        client = new NetClient();
        NetClient(client).addHandler(NetStreamCodes.ON_META_DATA, onMetaData);
        addEventListener(NetStatusEvent.NET_STATUS, onNetStreamStatus);
     public function onMetaData(value:Object):void
           NetClient(client).removeHandler(NetStreamCodes.ON_META_DATA, onMetaData);
           trace("Got metadata.");
    private function onNetStreamStatus(event:NetStatusEvent):void
       trace("onNetStreamStatus() - event.info.code=" + event.info.code);

Hello!
Do you need to handle metadata in NetStream descendant?
If not I would have used a different approach.
LightWeightedVideoElement has a property "client" that is being set to NetClient upon element load.
So you may want to load an element and use that property instead of subclassing netstream.
Regards!

Similar Messages

Is there a way to detect a bad http client handle before it locks up LabVIEW?

The attached VI demonstrates a simple way to hang LabVIEW such that the only way to recover full use of it is to kill the LabVIEW process. LabVIEW version is 11.0.1f2 and this problem will occur in both WinXP and Win7.
Is there a way to detect when an HTTP Client Handle refnum is stale and should not be used?
Is this a known bug?
Attachments:
Hang after Bad HTTP Client Handle.vi ‏15 KB

Have you tried the bad reference comparator?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

NetStream.client can't be a class instance?

I tried this:
netStream = new NetStream(netConnection, NetStream.DIRECT_CONNECTIONS);
netStream.addEventListener(NetStatusEvent.NET_STATUS, streamStatus);
netStream.publish("gamestate");
netStream.client = this;
public function onPeerConnect(ns:NetStream):Boolean {
     trace("onPeerConnect", ns.farID);
Inside a class called ClientStream. However I found that onPeerConnect was not being called. I changed .client to this:
netStream.client = {
     onPeerConnect:function(ns:NetStream):Boolean {
          trace("onPeerConnect", ns.farID);
And it works. Does this mean that you have to use a generic object like that for the client? Is there something I'm not understanding in the first example?

I can confirm that you need to use a generic object for this callback.
It's not a bug as much as it's an oddity.

Problem in SOAP Client Handler configuration

Hi all,
I am working on a webservice project where i have to send SOAP headers in the SOPA Request from Client and retrive the same at webservice end. I have configured server Handler in webservices.xml of the Webservice and it is working fine. (It is going into the handleRequest(MessageContext ctx) method.). Also i have configured a client Handler in the client and configured it in the web.xml. But this client side handler is not working. (call is not going in the handleRequest(MessageContext ctx) method of this handler).
Now i have two probs -
1. What can be the prob in the client side Handler configuration? And how to resolve this so that call goes in handleRequest() method.
2. I want to send SOAP header from client, so where i will have to set these headers? For client side i have generated client classes from WSDL, written a ClientTest.java class which calls the webservice. (It is perfectly calling the webservice) and created & configured SOAPHandlerClient.java. In which class should i add the code to set (or add) SOAP headers?
Note : -I am using RAD and websphere server.
Thanks in advance.

Check the URL.
the communication channel that u assign is not valid. Also I am seeing that u are sending the SOAP request to XI using the SOAP adapter??
So your URL should contains the SOAP sender channel right??
Thanks
Farooq.

IDoc to SOAP: client handler for response

Hello All,
I have a scenario with IDOC to Web services.
Is it possible to establish synchronous communication?
We do not want to use BPM.
I tried with importing IDOC structure into External definition, and then defining it as Synchronous Interface like this
IDOC Interface(Outbound) -> output:'ZINVOIC'
                                           input: 'Response'
WSDL Interface(Inbound) ->   input:'Request'
                                           output:'Response'
But this did not work as the response is still going from Web services to the sender channel which is IDoc adapter
If asynchronous, the web service party is telling me to set up a client handler to listen to the responce that web service is sending. Is it possible? and if possible, please explain the steps.
Please help me out with this!
Thanks,
Lakshmi

Hello Lakshmi,
We also had similar requirement. This cannot be synchronous. IDOC to Webservice is always an asyn communication.
Hope this helps.
Thanks
-Kulwant

JAX-RPC Client Handler

Hi All,
I am trying to get a simple example client handler to work using JAX-RPC DII.
The web serivice is a simple one that just returns Hello + name..
Here is the client code:
public class Main {
     * @param args the command line arguments
    private static String BODY_NAMESPACE_VALUE = "http://helloservice/";
    private static String NS_XSD = "http://www.w3.org/2001/XMLSchema";
    private static String ENCODING_STYLE_PROPERTY = "javax.xml.rpc.encodingstyle.namespace.uri";
    private static String URI_ENCODING ="http://schemas.xmlsoap.org/soap/encoding/";
    public static void main(String[] args) {
        try {
                 String url ="http://localhost:8080/HelloService/MyHelloService";
                 QName serviceName   = new QName(BODY_NAMESPACE_VALUE,"MyHelloServiceService");
                 QName portTypeName = new QName(BODY_NAMESPACE_VALUE, "MyHelloServicePort");
                 ServiceFactory factory = ServiceFactory.newInstance();
                 Service service = factory.createService(serviceName);
                 Call call = service.createCall();
                 call.setPortTypeName(portTypeName);
                 call.setOperationName(new QName(BODY_NAMESPACE_VALUE, "sayHello"));
                 call.setTargetEndpointAddress(url);
                 call.setProperty(ENCODING_STYLE_PROPERTY,"");
                 //call.setProperty(ENCODING_STYLE_PROPERTY,URI_ENCODING);
                 call.setProperty(Call.OPERATION_STYLE_PROPERTY, "rpc");
                 QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
                 call.setReturnType(QNAME_TYPE_STRING);
                 call.addParameter("name", QNAME_TYPE_STRING, ParameterMode.IN);
                 String[] params = { "Murph!" };
                 HandlerRegistry hr = service.getHandlerRegistry();
                 List<HandlerInfo> list = new ArrayList<HandlerInfo>();
                 HandlerInfo hi = new HandlerInfo(ClientSOAPHandler1.class, null,null);
                 list.add(hi);
                 HandlerInfo hi2 = new HandlerInfo(ClientLogicalHandler1.class, null,null);
                 list.add(hi2);
                 hr.setHandlerChain(portTypeName, list);
                 String result = (String)call.invoke(params);
                 System.out.println(result);
        } catch (ServiceException e)
            e.printStackTrace();
        catch (RemoteException e)
            e.printStackTrace();
}And the code for the Handlers:
public class ClientSOAPHandler1 extends ClientSOAPHandlerBase
    private final String HANDLERNAME="ClientSOAPHandler1";
    public ClientSOAPHandler1(){
       super();
       super.setHandlerName(HANDLERNAME);
import javax.xml.transform.Source;
import java.util.Set;
import java.util.TreeSet;
import javax.annotation.PreDestroy;
import javax.annotation.PostConstruct;
import javax.xml.namespace.QName;
import javax.xml.ws.handler.MessageContext;
import javax.xml.ws.handler.soap.SOAPHandler;
import javax.xml.ws.handler.soap.SOAPMessageContext;
import javax.xml.soap.SOAPMessage;
import java.io.ByteArrayOutputStream;
public class ClientSOAPHandlerBase implements SOAPHandler<SOAPMessageContext>
    private String handlerName=null;
    public void setHandlerName(String h) {
        this.handlerName=h;
    public String getHandlerName() {
        return this.handlerName;
    @PostConstruct
    public void myInit() {
        System.out.println("------------------------------------");
        System.out.println("in "+handlerName+":myInit");
        System.out.println("exiting "+handlerName+":myInit");
        System.out.println("------------------------------------");
    @PreDestroy
    public void myDestroy() {
        System.out.println("------------------------------------");
        System.out.println("in "+handlerName+":myDestroy");
        System.out.println("exiting "+handlerName+":myDestroy");
        System.out.println("------------------------------------");
    public Set<QName> getHeaders() {
        return new TreeSet<QName>();
    public boolean handleMessage(SOAPMessageContext context) {
        System.out.println("------------------------------------");
        System.out.println("in "+handlerName+":handleMessage");
        boolean direction= ((Boolean)context.get(SOAPMessageContext.MESSAGE_OUTBOUND_PROPERTY)).booleanValue();
        if (direction) {
            System.out.println("direction = outbound");
        } else {
            System.out.println("direction = inbound");
        dumpMsg(context);
        System.out.println("exiting "+handlerName+":handleMessage");
        System.out.println("------------------------------------");
        return true;
    public void close(MessageContext context) {
        System.out.println("------------------------------------");
        System.out.println("in "+handlerName+":close");
        System.out.println("exiting "+handlerName+":close");
        System.out.println("------------------------------------");
    public boolean handleFault(SOAPMessageContext context) {
        System.out.println("------------------------------------");
        System.out.println("in "+handlerName+":handleFault");
        System.out.println("exiting "+handlerName+":handleFault");
        System.out.println("------------------------------------");
        return true;
    public void dumpMsg(MessageContext context) {
       try {
          SOAPMessage soapmsg = ((SOAPMessageContext)context).getMessage();
          System.out.println("MSG="+getMsgAsString(soapmsg));
       } catch (Exception e) {
           e.printStackTrace();
       return;
    public String getMsgAsString(SOAPMessage message) {
        String msg = null;
        try {
            ByteArrayOutputStream baos = new ByteArrayOutputStream();
            message.writeTo(baos);
            msg = baos.toString();
        } catch (Exception e) {
            e.printStackTrace();
        return msg;
}The output is as follows:
run:
Hello Murph!
BUILD SUCCESSFUL (total time: 1 second)
This should print out the various println statements in the Handler, but it doesnt :(- How come? What am I missing?
I have searched everywhere trying to find the proper way to get a client side handler to work and have had luck. Additionally, I really really need this to work....if anyone could provide help, it would be VERY appreciated...pretty please
Thanks,
Daniel

Any Ideas Anyone?????

NetStream.onStatus handler for end of FLV

Hey,
Basically I want to cue an event when an FLV playing through
a netConnection/netStream is finished - if anybody has any tips
it'd be much appreciated.
I could put a CuePoint on the last frame of each FLV and use
an onCuePoint Event Handler - but there must be an easier way?
I'm assuming the 'NetStream.Play.Stop' Code Property won't do
the job because then simply pausing the Video would cause the event
to trigger, whereas I only want to trigger it at the very end of
the stream.
Is there a way of coding 'When my_ns.time == the last second
of the stream then perform function X'?
Thanks in advance for any assistance,
Justin.

It would really depend on how you are getting the video into
you .swf: if it's embeded or you're creating your own video
instance. Assuming you're creating your own instance of the video
player, you could set and event listening for a net status event
like so:
private function onNetStatus(evt:NetStatusEvent):void
if(evt.info.code == "NetStream.Play.Start")
isPlaying = true;
}else if (evt.info.code == "NetStream.Play.Stop") {
isPlaying = false;
trace("video stopped");
Then if you're watching the isPlaying variable, if it's shows
up as false you know the video isn't playing anymore and you could
then call another function.

Client handler is invoking for every request.

Hi EveryOne
i am new to JAXWS welogic.
i have a web consumer/client, while sending the request from client the handler is invoking for every request. I could not able to restrict.
i would like to intialize only once and need to use that instance like (init() method initialization). How to resolve this issue.
can anyone come across a solution for JAX-WS in general? Please throw your thoughts here.
Any help in this regard would be appreciated.
Thanks & Regards
Suresh

Two common reasons for this are:
(1) Problem with the system clock: date, time, or time zone differs substantially from the rest of the internet
(2) Firefox not set up to work with your security software that filters your web traffic
In order to filter secure traffic, your security software needs to present "fake" certificates to Firefox so it can be the "man in the middle" and see everything sent to and from the site. Firefox distrusts the fake certificates until instructed otherwise.
Do you use any software with that kind of feature? On Windows, products with that feature include avast! 2015, Bitdefender, ESET, and Kaspersky.
A less common problem is malware performing a "man in the middle" attack.

Client Handling of EJB Exceptions

I am using a session facade to interact with a series of entity beans through local
interfaces. One of the entity beans has a "name" property that must be unique
in the database. If I attempt to create one of these entity beans with a "name"
that is already being used I need to throw an exception back to the client to
request that a new "name" be provided. What is the best way to provide this functionality?
Here is some sample code to explain the process:
Session Facade
public ... intitiateTeam(...) {
TeamLocal team = teamHome.create(name, ...);
Team Entity Bean
public Integer ejbCreate(String name, ...) {
setName(name);
Should I throw an exception from the entity bean that the session facade catches
and then forwards back to the client?

It's either a boolean return or an exception or similar. An exception is
suitable if the request is to register because the registration has failed.
Peace,
Cameron Purdy
Tangosol Inc.
Tangosol Coherence: Clustered Coherent Cache for J2EE
Information at http://www.tangosol.com/
"willie" <[email protected]> wrote in message
news:3c10fadd$[email protected]..
>
I am using a session facade to interact with a series of entity beansthrough local
interfaces. One of the entity beans has a "name" property that must beunique
in the database. If I attempt to create one of these entity beans with a"name"
that is already being used I need to throw an exception back to the clientto
request that a new "name" be provided. What is the best way to providethis functionality?
>
Here is some sample code to explain the process:
Session Facade
public ... intitiateTeam(...) {
TeamLocal team = teamHome.create(name, ...);
Team Entity Bean
public Integer ejbCreate(String name, ...) {
setName(name);
Should I throw an exception from the entity bean that the session facadecatches
and then forwards back to the client?

Client-side handler: static config?

I would like to provide a client-side JAX-RPC handler that would
be invoked without any modification to existing client code.
The idea is that user's would only need to modify a config file
(something like the web-services.xml file, but on the client-
side) to use our handler.
We are already doing this in axis (uses a client-side deployment
descriptor: client_deploy.wsdd), but based on another thread
("Client Handler Chain - help ??"), it looks like there is
currently no equivalent in WLS?
Are there plans to add the ability to statically configure
client-side handlers in WLS via some sort of client-side config
file/descriptor, or is the programmatic method of modifying
the HandlerRegistry in the client code the only way?
Any help/ideas would be greatly appreciated!
--Terry

In 7.0, you can do this in a handler:
import weblogic.webservice.binding.soap.HttpClientBinding;
String url = http://my/new/address/;
sslAdapter = null; //only needed for ssl
Binding binding = new HttpClientBinding( url, sslAdapter );
context.setProperty( WLMessageContext.BINDING_PROP,
binding );
HTHs
-manoj
http://manojc.com
"William Cassidy" <[email protected]> wrote in message
news:[email protected]...
>
Is there a similar way to set the endPointAddress.
"manoj cheenath" <[email protected]> wrote:
Ok, I will add this as a feature request.
If you are ok with using WLS internal APIs (This APIs may change in
the future), try this:
weblogic.webservice.Operation operation
=
((weblogic.webservice.WLMessageContext)messageContext).getOperation();
>>
weblogic.webservice.Port port = operation.getPort();
String endPointAddress = port.getAddress();
regards,
-manoj
"Terry Martin" <[email protected]> wrote in message
news:[email protected]...
Manoj, thanks for the response.
We'd definitely like to see a client side dd at some point, but
can work with the API's for now. Thanks much for adding this as
a feature request.
On another subject:
I need to determine the target/endpoint URL from my client-side
request handler. Again, this was something we were able to do in
axis, but is currently not part of the JAX-RPC standard (JSR101).
I could be missing something, but haven't seen any way of
determining the target URL given only the SOAPMessageContext.
The only way seems to be if it were passed as a "standard"
property in the SOAPMessageContext (this is one way it is done
in axis).
I imagine this will someday be standardized in JAX-RPC (I can
think of many uses for this feature, other than our own). In the
meantime, could you also add this as a feature request for WLS?
Thanks again,
-Terry
"manoj cheenath" <[email protected]> wrote:
True. In WLS 7.0 there are no client side dd in which you can specify
the handler chain. We did not comeup with ourown client side dd,
hopeing that JSR109 will define the dd.
It is quite easy to register the handlers through APIs. Let us know
if
that will not help you.
I will add client side dd as a feature requst for the next release.
regards,
-manoj
"Terry Martin" <[email protected]> wrote in message
news:[email protected]...
I would like to provide a client-side JAX-RPC handler that would
be invoked without any modification to existing client code.
The idea is that user's would only need to modify a config file
(something like the web-services.xml file, but on the client-
side) to use our handler.
We are already doing this in axis (uses a client-side deployment
descriptor: client_deploy.wsdd), but based on another thread
("Client Handler Chain - help ??"), it looks like there is
currently no equivalent in WLS?
Are there plans to add the ability to statically configure
client-side handlers in WLS via some sort of client-side config
file/descriptor, or is the programmatic method of modifying
the HandlerRegistry in the client code the only way?
Any help/ideas would be greatly appreciated!
--Terry

Client(mandt) Handling in SAP Business Suite (ERP) on HANA

Hi Experts,
What are the possible ways to do client handling in native application developments for ERP on HANA?
Is there a best practice for automatic client handling?
Regards
Manas

Hi Manas
for information models you simply set the client property of the models.
For SQL processes you can leverage the session_context ('CLIENT') parameter as a filter.
The modelling/development guide actually covers that.
- Lars

StartTransmit / stopTransmit reference error on NetStream when connecting to device

Hi all,
I'm trying to create a P2P connection between a mobile device (Android) and a PC using the NetStream class.
When the connection is established, the Flash Player Instance on the PC is crashing with a reference error:
“Property startTransmit not found on flash.net.NetStream”
I have seen the thread located located here: http://stackoverflow.com/questions/9676496/adobe-cirrus-error-on-direct-connectproperty-st arttransmit-not-found-on-flash-n
but was not successfull in making it work with my code.
I have tried extending the NetStream class like so:
import com.frimastudio.cosy.util.NetConsole;
import flash.net.NetConnection;
import flash.net.NetStream;
public class NetStreamProvider extends NetStream
public function NetStreamProvider (connection:NetConnection, peerID:String)
   super(connection, peerID);
// For AIR Android projects: when the device is put to sleep for a moment, this function will be
// called so we need to implement it to prevent flash from crashing.
public function startTransmit($p1:*, $p2:*):void
   COSY::console { NetConsole.WarningInternal("NetInterfaceSlot", "startTransmit", "startTransmit called"); }
public function stopTransmit():void
   COSY::console { NetConsole.WarningInternal("NetInterfaceSlot", "stopTransmit", "stopTransmit called"); }
and using the NetStreamProvider instead. Without success.
Any help would be greatly appreciated.
Thanks.
Guillaume

>> i suspect this is AIR-specific (probably if AIR is the sender) -- in my experience it doesn't happen with plain Flash Player.
[Guillaume] -> Right, it does not happen on NetStreams between 2 Flash Players and 2 AIR app. Only between AIR-FlashPlayer NetStreams. Basically, after a stream is opened between AIR and Flash Player, the AIR is calling "starTransmit" on the FlashPlayer NetStream, wich is not implemented.
>> try making an object with those method names and assign it to netStream.client
[Guillaume] -> I tried the following:
Implement starTransmit/stopTransmit functions in the NetStream.client object
Implement startTransmit/stopTransmit functions in the NetStream instance (subclassed)
Without success. Basically, it works fine if I just create a "dummy" client object for the NetStream that has those 2 functions. But If I want to use my own client it was still crashing.
I found a work around for my problem.
My NetStream object is sub classed as such:
public class NetStreamProvider extends NetStream
public var customClient:Object;
public function NetStreamProvider (connection:NetConnection, peerID:String)
   super(connection, peerID);
   customClient = new Object();
   this.client = customClient;
   // Implement startTransmit and stopTransmit here for dummy client
   customClient.onPeerConnect = function(subscriber:NetStream): Boolean{
    var subClient:Object=new Object();
    subClient.stopTransmit=function($p1:*,$p2:*):void{
     trace("Cosy: stopTransmit called",$p1,$p2);
    subClient.startTransmit=function():void{
     trace("Cosy: startTransmit called");
    subscriber.client = subClient;
    return true;
public function SetClient(c:Object):void
   this.client = c;
public function OnNetStreamAsyncError(event:AsyncErrorEvent):void
And in the stream status event handler, when the stream is ready (events "NetStream.Play.PublishNotify" and "NetStream.Play.Start") I set the correct client, which has the receive handler. At that point startTransmit was already called:
And in the stream status event handler, when the stream is ready (events "NetStream.Play.PublishNotify" and "NetStream.Play.Start") I set the correct client, which has the receive handler. At that point startTransmit was already called:
private function OnNetStreamStatus(e:NetStatusEvent)
switch(e.info.code)
case "NetStream.Play.PublishNotify":
           stream = e.target as NetStreamProvider;
           stream.SetupClient(client);
break;
case "NetStream.Play.Start":
           stream = e.target as NetStreamProvider;
           stream.SetupClient(client);
break;
At this point, i'm not blocked anymore. However, it would be good to know why, when and who are calling those functions to understand the issue. this is not documented anywhere, and might be an issue to a lot of people now that we are starting to see more and more cross-platform connectivity.
Cheers.
Guillaume

Insert client side video to an app

I have to builld an application which has two videos. One video comes from the server side with the support of flash media server. and second video comes from client side from a web cam. I was able to include server video to the app but I have no idea how to include client video to the app, because the client does not have a flash media server or flash media encoder running. Can any one please help me

So here's what you can do :
1. From the client publish the web cam stream to your FMS server like so :
var nc:NetConnection;
var ns:NetStream;
var camera:Camera;
var microphone:Microphone;
nc = new NetConnection();
nc.addEventListener(NetStatusEvent.NET_STATUS, onStatus);
nc.connect("rtmp://<server-ip>/<app>/<app-inst>");                       //connect to an FMS side application
functiononStatuss(event:NetStatusEvent):void{
     if(info.code=="NetConnection.Connect.Success"){
          ns = new NetStream(nc);
          ns.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);   //you can define an event listener for the netstream and handle events like Netstream.Publish etc
          camera = Camera.getCamera();    //Get the client side webcam and microphone
          microphone= Microphone.getMicrophone();
          ns.attachCamera(camera);                         //Attach it to the netstream
          ns.attachAudio(microphone);
          ns.publish("myWebcam","record");              //Publish that stream to FMS application. The streamname is myWebcam
2. To playback this Wnb cam stream on any client you just need to connect to the same application instance and do a ns.play();
See here for more information : http://livedocs.adobe.com/flashmediaserver/3.0/hpdocs/help.html?content=00000185.html
Hope this helps.
Thanks,
Apurva

HTTPs without client authentication, error while posting through Altova

Hi Experts
I am doing a SOAP- XI-Proxy synchronous scenario where i have to use HTTPs without client authentication for the first time in my system.
I have made the scenario and WSDL out of it.
When i am trying to test it through Altova, i am getting the following error:
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Body>
        <SOAP:Fault>
            <faultcode>SOAP:Server</faultcode>
            <faultstring>Server Error</faultstring>
            <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                    <context>XIAdapter</context>
                    <code>ADAPTER.JAVA_EXCEPTION</code>
                    <text><![CDATA[
java.security.AccessControlException: https scheme required
    at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:918)
    at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103)
    at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:296)
    at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
    at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:187)
    at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:496)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
          ]]></text>
                </s:SystemError>
            </detail>
        </SOAP:Fault>
    </SOAP:Body>
</SOAP:Envelope>
i saw a few discussion on web but nowhere the solution was provided.
the url is
http://abc.sap.point:1234/XISOAPAdapter/MessageServlet?channel=:system:communicationchannel&version=3.0&Sender.Service=x&Interface=x%5Ex
i changed it to https also but in that case it was not even posting the request.
i have set the sender adapter like this
is there any setting that i am missing.
What is the setting the i need to do in SM59.
Please help me getting through this.
Your help is highly appreciated. Thanks in advance.
Neha

HI Neha,
1. Enable the https service in the ICM: you can follow the way to do it like is pointed out in the page 4 of this document (PI 7.1 and PI 7.0 has the same smicm abap transaction) http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60ff2883-70c5-2c10-f090-a744def2ba66?overridelayout=t…
2. Generate the certificate. Use the STRUST transaction. Chech this document SSL Configuration in SAP ABAP AS and JAVA AS – Step-by-step procedure
Hope this helps.
Regards.

DynamicRFCException with JCO.client problem

Hi,
Iam trying to execute an RFC from webdynpro.Iam getting the following error.So as a result i dont get any result as expected on my screen as the RFC is not getting executed due to JCO problem.Please kindly let me know the reason.In the last line of the exception it talks about user authentication.I dont have any idea whats the reason.This happens as soon as my bapi execute statement in my controller is executed.
could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.test.Getmodel. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.prepareExecute(DynamicRFCModel.java:179) at com.test.Getmodel.bapi_Ben_Bus3029_Get_Evt_List(Getmodel.java:141) at com.test.Bapi_Ben_Bus3029_Get_Evt_List_Input.doExecute(Bapi_Ben_Bus3029_Get_Evt_List_Input.java:137) at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92) at com.avid.benefits.Benefitscust.executebapi(Benefitscust.java:128) at com.avid.benefits.wdp.InternalBenefitscust.executebapi(InternalBenefitscust.java:162) at com.avid.benefits.AvidusbenefitsView.wdDoInit(AvidusbenefitsView.java:97) at com.avid.benefits.wdp.InternalAvidusbenefitsView.wdDoInit(InternalAvidusbenefitsView.java:129) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61) at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215) at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445) at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200) at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709) at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579) at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295) at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183) at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Caused by: com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException: Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.test.Getmodel. Please assure that you have configured the RFC connections and/or logical system name properly for this model! at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel.getCurrentlyUsedJcoClient(AiiModel.java:210) at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.prepareExecute(DynamicRFCModel.java:170) ... 42 more Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.getJCOClientConnection(WDSystemLandscape.java:30) at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel.getCurrentlyUsedJcoClient(AiiModel.java:189) ... 43 more Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for 'WD_MODELDATA_DEST' at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:649) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:476) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) ... 45 more Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: User not authenticated - unable to establish JCO connection with SSO. at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:584) ... 50 more
Error connecting using JCO.Client: null
Error connecting using JCO.Client: null: Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.test.Getmodel. Please assure that you have configured the RFC connections and/or logical system name properly for this model!: Error while obtaining JCO connection.: Failed to resolve connection parameter for 'WD_MODELDATA_DEST': User not authenticated - unable to establish JCO connection with SSO.

Hi Swathi,
The problem may be with JCo destinations. If you have authorization in Portal, navigate to Content Administration -> Web Dynpro.
In the left side you can see deployed web dynpro applications. Check in local, sap, or any of your custom namespace. Browse & select to your application. Right side you can see JCo destinations for your application. If they are in green color , means they are created. If not, ask your basis team to create them. If they are n green color, ping and test them. if they are working fine or not.
If they are fine, try to deploy after you have logged into the portal.
Regards,
Siva

NetStream client handler

Similar Messages

Maybe you are looking for