Send a Single Message to a Client

What is the best way to send a single message from the server to a client using flex/blazeds? The one caveat is that the message could take several minutes before it is sent. Think of a long calculation that is done on the server that the client waits for. I've thought of the following options:
1) Just use a RemoteObject and call a method. Would there be any problems with the response taking several minutes to come back? I would also ideally like to have a single thread which sends all the responses to the clients in a batch, rather than the standard route of each client's remote method call spawning a thread which returns the result; anyone know where to get started here?
2) Create a new destination and consume that destination on each client. The destination and consumer could be closed on each client after the first message is received.
Which is the best option?
Thanks,
Gordon

It looks like you need a mechanism where the client registers with the server, then server does some long calculation, and then when the result is available, server sends the result back to the client. Messaging (option #2) sounds like a good fit for this.
Some thing to note:
- You can use subtopics so each client is subscribed to the same destination but has its own subtopic to receive updates from.
- You need to use a realtime channel (polling, long-polling, or streaming) so that the consumer can receive updates. I suggest long-polling with a really long wait time.

Similar Messages

Multiple Process agents to send out single message

Is it possible for multiple Outbound agents to send out a single generic message? For example 2 AP BO's, Lead and Opportunity both would require to send out a generic message to another BO in a different DU. If yes, how could this be acheived?

it use appleID for the whole communication model so you would not be able to msg her using imassages as that would imply that you're sending yourself an message

Sending a single message to two systems in an order

Hi all
I have a scenario where i need to send a message to two different systems,the messge is to be sent to the second system only after the first message has been completely prcocessed sucessfully.
Need an approach to acheive the above requirement.
Thanks all
Manohar.

Manohar,
There could be another way..
Use the option .. Operating System Command after Message processing. If your XI System is installed in Unix servers i believe it would be easy to send mail. If in windows search in google for softwares. I cant remember any names right now..
Search if sdn/google about more on the above option.
Or you can use BPM. In send step select Acknowledgement(Transport). So once the ack is received the process would move to the next Send Step(Send Mail).
Regards,
Sumit

Send Single Message to Client

What is the best way to send a single message from the server to a client using flex/blazeds? The one caveat is that the message could take several minutes before it is sent. Think of a long calculation that is done on the server that the client waits for. I've thought of the following options:
1) Just use a RemoteObject and call a method. Would there be any problems with the response taking several minutes to come back? I would also ideally like to have a single thread which sends all the responses to the clients in a batch, rather than the standard route of each client's remote method call spawning a thread which returns the result; anyone know where to get started here?
2) Create a new destination and consume that destination on each client. The destination and consumer could be closed on each client after the first message is received.
Which is the best option?
Thanks,
Gordon

Hi Gordon,
I would suggest trying to use a messaging destination for this. Seems like
an RPC that takes minutes isn't so great given all the things that could
happen (network wise and even client application wise) in that time. And
having the client poll for the result (using a polling HTTP channel) seems
reasonable.
Just an opinion. I would try both if you have the time (the RemoteObject
should be pretty quick to prototype).
Tom Jordahl

ALSB 3 roll back a transaction without sending a fault message

Hi,
I have a proxy service exposed as a web service, which has some operations that call some tuxedo systems, do some transformation of the data, etc.
When any of it's operations is invoked I have to build an XML reply in both success AND error cases. The difference between both is a response code, if the call to the backend tuxedo system responded with a stream that starts with OK then everything is fine and I build the reply and send it back, but if an error ocurred it will send back an stream that starts with ER followed by an error code, with which I will have to build the SAME XML but using this error code and send it back to the client instead as a "successful" invocation instead of sending a SOAP fault message. Also I need to roll back the whole transaction in that error case. The system works like that and it can't be changed, we are building this proxy service based on a WSDL file given to us by the partner company that invokes our service and there's lots of other clients that do it in the same way. The problem is that I haven't found a way to roll back the transaction without making the proxy service send a fault message that the client system won't understand. The "Raise error" and "Reply with failure" do roll back the transaction but both send a fault message. Is there a way to answer "successfully" to the client but make an explicit rollback?

Hi,
Check the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22017.. [original link is broken] [original link is broken] [original link is broken]
You can handle the exception on your web service and model a Notification task so that you can send e-mail notification to the sender in case of exception
Regards, Anil

Sending large messages via ABAP client proxy

Dear All,
my scenario is the following. I have an ABAP report which creates files. These files are currently moved by an FTP auto job, to a target folder and are finally imported into an 3rd party programm.
The CSV-files created consist of approx. 3000 records, each with a length of 1000. So the total size is about 3 MB. The files are send at night, once a day.
We want to distribute these files via SAP PI. My question is the following:
Is a client proxy able to send the whole (3MB) message to PI (which will just write the message to the target FTP destination) or do I have to send each record with the client proxy to PI (and append the record to the file).
If both solutions are feasible,what would be preferable? The solution of sending single records to PI, would be more generic in my opinion, because I could define a message type for the records in PI. So in future i could add also some mapping stuff. If I would want to send the whole file content with one client proxy call, i would basically have one big string.
How do both options compare in regard to performance? Sending 3000 small messages oder one big message?
What about the file adapter? Is it an option to append 3000 records to a file?
Does anyone have another solution for that scenario?
Best regards and thank you for your help!
Florian

Hi,
Is a client proxy able to send the whole (3MB) message to PI
yes it is capable.
If both solutions are feasible,what would be preferable?
yes both solutions are feasible ,but preferable is to send the whole message rather than one by one.
How do both options compare in regard to performance?
sending whole message is far more better than sending record by record.
regards,
pradeep A.

My simple chat server does not send messages to connected clients

Hi!
I´m developing a chat server. But I can not get it work. My client seems to make a connection to it, but my server does not send the welcome message it is supposed to send when a client connects. Why not?
removedEdited by: Roxxor on Nov 24, 2008 10:36 AM

Ok, I solved my previous problem and now I have got a new really annoying one.
This is a broadcasting server which meand it can handle multiple clients and when one client sends a message to the server, the server should broadcast the message to all connected clients. It almost works, except that the server just sends the message back to the last connected client. The last connected client seems to steal the PrintStream() from the other clients. How can I solve that?
import java.io.*;
import javax.microedition.io.*;
import javax.microedition.midlet.*;
import javax.microedition.lcdui.*;
import java.lang.Character;
import java.io.OutputStream;
import java.util.Vector;
public class ChatServer extends MIDlet implements CommandListener, Runnable
     private Display disp;
     private Vector connection = new Vector();
     private TextField tf_port = new TextField("Port: ", "", 32, 2);
     private Form textForm = new Form("Messages");
     private Form start_serverForm = new Form("Start server", new Item[] { tf_port });
     private Command mExit = new Command("Exit", Command.EXIT, 0);
     private Command mStart = new Command("Start", Command.SCREEN, 0);
     private Command mDisconnect = new Command("Halt server", Command.EXIT, 0);
     ServerSocketConnection ssc;
     SocketConnection sc;
     PrintStream out;
     public ChatServer()
          start_serverForm.addCommand(mExit);
          start_serverForm.addCommand(mStart);
          start_serverForm.setCommandListener(this);
          tf_port.setMaxSize(5);
          textForm.addCommand(mDisconnect);
          textForm.setCommandListener(this);
     public void startApp()
          disp = Display.getDisplay(this);
          disp.setCurrent(start_serverForm);
     public void pauseApp()
     public void destroyApp(boolean unconditional)
     public void commandAction(Command c, Displayable s)
          if(c == mExit)
               destroyApp(false);
               notifyDestroyed();
          else if(c == mStart)
               Thread tr = new Thread(this);
               tr.start();
          else if(c == mDisconnect)
               try
                    sc.close();
               catch(IOException err) { System.out.println("IOException error: " + err.getMessage()); }
               destroyApp(false);
               notifyDestroyed();
     public void run()
          try
               disp.setCurrent(textForm);
               ssc = (ServerSocketConnection)Connector.open("socket://:2000");
               while(true)
                    sc = (SocketConnection) ssc.acceptAndOpen();
                    connection.addElement(sc);
                    out = new PrintStream(sc.openOutputStream());
                    textForm.append(sc.getAddress() + " has connected\n");
                    ServerToClient stc = new ServerToClient(sc);
                    stc.start();
          catch(IOException err) { System.out.println("IOException error: " + err.getMessage()); }
          catch(NullPointerException err) { System.out.println("NullPointerException error: " + err.getMessage()); }
     class ServerToClient extends Thread
          String message;
          InputStream in;
          SocketConnection sc;
          ServerToClient(SocketConnection sc)
               this.sc = sc;
          public void run()
               try
                    in = sc.openInputStream();
                    int ch;
                    while((ch = in.read())!= -1)
                         System.out.print((char)ch);
                         char cha = (char)ch;
                         String str = String.valueOf(cha);
                         out.print(str);
                         //broadcast(str);
                         textForm.append(str);
                    in.close();
                    //out.close();
                       sc.close();
               catch(IOException err) { System.out.println("IOException error: " + err.getMessage()); }
}

No client certificate available, sending empty certificate message

Dear Experts,
    I am trying to establish SSL client certificate connection to external partner. What puzzles me is that the certificate is not picked up by SAP PI. The intermediate and root CA for the partner are OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign,OU=VeriSign International Server CA - Class 3,OU=VeriSign, Inc.,O=VeriSign Trust Network and OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US, respectively. You will be able to spot them in the Accepted Certificate Authority list, yet PI insists on sending empty certificate.
    Below is trace gathered from J2EE default trace. Please help shed some light
Date : 11/16/2011
Time : 8:49:11:423
Message : additional info ssl_debug(9): Starting handshake (iSaSiLk 4.3)...
ssl_debug(9): Sending v3 client_hello message to preprod.connect.elemica.com:443, requesting version 3.2...
ssl_debug(9): Received v3 server_hello handshake message.
ssl_debug(9): Server selected SSL version 3.1.
ssl_debug(9): Server created new session 22:E7:C0:9E:C1:D2:78:83...
ssl_debug(9): CipherSuite selected by server: TLS_RSA_WITH_AES_256_CBC_SHA
ssl_debug(9): CompressionMethod selected by server: NULL
ssl_debug(9): Received certificate handshake message with server certificate.
ssl_debug(9): Server sent a 1024 bit RSA certificate, chain has 2 elements.
ssl_debug(9): ChainVerifier: No trusted certificate found, OK anyway.
ssl_debug(9): Received certificate_request handshake message.
ssl_debug(9): Accepted certificate types: RSA, DSA
ssl_debug(9): Accepted certificate authorities:
ssl_debug(9):   CN=QuoVadis Global SSL ICA,OU=www.quovadisglobal.com,O=QuoVadis Limited,C=BM
ssl_debug(9):   CN=AAA Certificate Services,O=Comodo CA Limited,L=Salford,ST=Greater Manchester,C=GB
ssl_debug(9):   CN=CSF - Classe III - Sign et Crypt,OU=Certification Professionnelle,O=Autorite Consulaire
ssl_debug(9):   CN=GTE CyberTrust Global Root,OU=GTE CyberTrust Solutions, Inc.,O=GTE Corporation,C=US
ssl_debug(9):   CN=Entrust.net Certification Authority (2048),OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.),O=Entrust.net
ssl_debug(9):   CN=DPWN SSL CA I2 PS,OU=I2 PS,O=Deutsche Post World Net
ssl_debug(9):   CN=CSF,O=Autorite Consulaire
ssl_debug(9):   C=BE,O=GlobalSign nv-sa,OU=RootSign Partners CA,CN=GlobalSign RootSign Partners CA
ssl_debug(9):   CN=Dell Inc. Enterprise Utility CA1,O=Dell Inc.
ssl_debug(9):   EMAIL=premium-server(a)thawte.com,CN=Thawte Premium Server CA,OU=Certification Services Division,O=Thawte Consulting cc,L=Cape Town,ST=Western Cape,C=ZA
ssl_debug(9):   CN=TC TrustCenter Class 2 L1 CA XI,OU=TC TrustCenter Class 2 L1 CA,O=TC TrustCenter GmbH,C=DE
ssl_debug(9):   CN=VeriSign Class 3 Extended Validation SSL SGC CA,OU=Terms of use at https://www.verisign.com/rpa (c)06,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9):   OU=VeriSign Trust Network,OU=(c) 1998 VeriSign, Inc. - For authorized use only,OU=Class 3 Public Primary Certification Authority - G2,O=VeriSign, Inc.,C=US
ssl_debug(9):   CN=TC TrustCenter SSL CA I,OU=TC TrustCenter SSL CA,O=TC TrustCenter GmbH,C=DE
ssl_debug(9):   CN=Entrust Root Certification Authority,OU=(c) 2006 Entrust, Inc.,OU=www.entrust.net/CPS is incorporated by reference,O=Entrust, Inc.,C=US
ssl_debug(9):   CN=VeriSign Class 3 International Server CA - G3,OU=Terms of use at https://www.verisign.com/rpa (c)10,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9):   CN=Meijer ipprod,OU=IT,OU=Merch,O=Meijer Stores Limited,L=Walker,ST=MI,C=US
ssl_debug(9):   CN=COMODO Certification Authority,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
ssl_debug(9):   OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign,OU=VeriSign International Server CA - Class 3,OU=VeriSign, Inc.,O=VeriSign Trust Network
ssl_debug(9):   CN=UTN - DATACorp SGC,OU=http://www.usertrust.com,O=The USERTRUST Network,L=Salt Lake City,ST=UT,C=US
ssl_debug(9):   CN=Deutsche Telekom CA 5,OU=Trust Center Deutsche Telekom,O=T-Systems Enterprise Services GmbH,C=DE
ssl_debug(9):   CN=TC TrustCenter Class 2 CA II,OU=TC TrustCenter Class 2 CA,O=TC TrustCenter GmbH,C=DE
ssl_debug(9):   CN=VeriSign Class 3 Secure Server CA - G2,OU=Terms of use at https://www.verisign.com/rpa (c)09,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9):   OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign,OU=VeriSign International Server CA - Class 3,OU=VeriSign, Inc.,O=VeriSign Trust Network
ssl_debug(9):   CN=Thawte SGC CA,O=Thawte Consulting (Pty) Ltd.,C=ZA
ssl_debug(9):   CN=Bertschi CA,O=Bertschi AG (Schweiz),L=Duerrenaesch,ST=Switzerland,C=CH
ssl_debug(9):   CN=Cybertrust SureServer CA,O=GlobalSign Inc
ssl_debug(9):   CN=VeriSign Class 3 Secure Server CA,OU=Terms of use at https://www.verisign.com/rpa (c)05,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9):   EMAIL=server-certs(a)thawte.com,CN=Thawte Server CA,OU=Certification Services Division,O=Thawte Consulting cc,L=Cape Town,ST=Western Cape,C=ZA
ssl_debug(9):   CN=Mark Van Hamme,O=Brain2 BVBA,L=Brussels,ST=Brabant,C=BE
ssl_debug(9):   CN=DigiCert High Assurance EV Root CA,OU=www.digicert.com,O=DigiCert Inc,C=US
ssl_debug(9):   EMAIL=bis.at(a)siemens.com,CN=bis.siemens.at,OU=SBS ORS EDO,O=Siemens Business Services,L=Vienna,ST=Vienna,C=AT
ssl_debug(9):   CN=VeriSign Class 1 Public Primary Certification Authority - G3,OU=(c) 1999 VeriSign, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9):   CN=mail2.adr-logistics.hu,O=ADR Logistics Kft.,L=Gyu00E1l,ST=Pest,C=HU
ssl_debug(9):   EMAIL=brent.kemp(a)sscoop.com,CN=bacchusdevp.sscoop.com,OU=IS,O=Southern States Cooperative Inc,L=Richmond,ST=VA,C=US
ssl_debug(9):   CN=Cybertrust SureServer Standard Validation CA,O=Cybertrust Inc
ssl_debug(9):   OU=Go Daddy Class 2 Certification Authority,O=The Go Daddy Group, Inc.,C=US
ssl_debug(9):   CN=Certipost E-Trust Secondary Normalised CA for Legal Persons,O=Certipost s.a./n.v.,C=BE
ssl_debug(9):   EMAIL=cert(a)bit-serv.de,CN=BIT-SERV GmbH Root CA,O=BIT-SERV GmbH,C=DE
ssl_debug(9):   CN=SAP_elemica_tester
ssl_debug(9):   CN=GeoTrust Global CA,O=GeoTrust Inc.,C=US
ssl_debug(9):   OU=Class 1 Public Primary Certification Authority,O=VeriSign, Inc.,C=US
ssl_debug(9):   CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE
ssl_debug(9):   CN=Montova Root CA,OU=Root CA,O=Montova,C=BE
ssl_debug(9):   CN=Baltimore CyberTrust Root,OU=CyberTrust,O=Baltimore,C=IE
ssl_debug(9):   CN=Dell Inc. Enterprise CA,O=Dell Inc.
ssl_debug(9):   CN=COMODO High-Assurance Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
ssl_debug(9):   EMAIL=support(a)tamgroup.com,OU=Engineering,O=Tamgroup,ST=California,L=San Anselmo,C=US,CN=Tamgroup
ssl_debug(9):   CN=GlobalSign Organization Validation CA,O=GlobalSign,OU=Organization Validation CA
ssl_debug(9):   CN=Certinomis AC 1 u00E9toile,OU=0002 433998903,O=Certinomis,C=FR
ssl_debug(9):   CN=GlobalSign ServerSign CA,OU=ServerSign CA,O=GlobalSign nv-sa,C=BE
ssl_debug(9):   CN=QuoVadis Root CA 2,O=QuoVadis Limited,C=BM
ssl_debug(9):   CN=AddTrust Class 1 CA Root,OU=AddTrust TTP Network,O=AddTrust AB,C=SE
ssl_debug(9):   CN=Equifax Secure Global eBusiness CA-1,O=Equifax Secure Inc.,C=US
ssl_debug(9):   CN=GlobalSign Organization Validation CA,O=GlobalSign,OU=Organization Validation CA
ssl_debug(9):   CN=thawte Primary Root CA,OU=(c) 2006 thawte, Inc. - For authorized use only,OU=Certification Services Division,O=thawte, Inc.,C=US
ssl_debug(9):   CN=Certipost E-Trust Primary Normalised CA,O=Certipost s.a./n.v.,C=BE
ssl_debug(9):   CN=Thawte DV SSL CA,OU=Domain Validated SSL,O=Thawte, Inc.,C=US
ssl_debug(9):   OU=Equifax Secure Certificate Authority,O=Equifax,C=US
ssl_debug(9):   CN=preprod.connect.elemica.com,OU=CONNECTED SOLUTIONS,O=Elemica,L=Wayne,ST=Pennsylvania,C=US
ssl_debug(9):   CN=Certinomis - Autoritu00E9 Racine,OU=0002 433998903,O=Certinomis,C=FR
ssl_debug(9):   CN=DPWN Root CA R2 PS,OU=IT Services,O=Deutsche Post World Net,DC=com
ssl_debug(9):   CN=Thawte Test CA Root,OU=TEST TEST TEST,O=Thawte Certification,ST=FOR TESTING PURPOSES ONLY,C=ZA
ssl_debug(9):   OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US
ssl_debug(9):   EMAIL=santiago.tolosa(a)eu.rhodia.com,CN=Rhodia Development CA,OU=ISF - WARTE,O=Rhodia,L=La Villette,ST=France,C=FR
ssl_debug(9):   CN=Entrust.net Secure Server Certification Authority,OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS incorp. by ref. (limits liab.),O=Entrust.net,C=US
ssl_debug(9):   CN=DigiCert High Assurance CA-3,OU=www.digicert.com,O=DigiCert Inc,C=US
ssl_debug(9):   CN=Groep H. Essers TEST (99805D6DA33FCC1700010002),O=Montova,C=BE
ssl_debug(9):   serialNumber=07969287,CN=Go Daddy Secure Certification Authority,OU=http://certificates.godaddy.com/repository,O=GoDaddy.com, Inc.,L=Scottsdale,ST=Arizona,C=US
ssl_debug(9):   CN=VeriSign Class 3 Secure Server 1024-bit CA - G2,OU=Terms of use at https://www.verisign.com/rpa (c)09,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9):   serialNumber=10688435,CN=Starfield Secure Certification Authority,OU=http://certificates.starfieldtech.com/repository,O=Starfield Technologies, Inc.,L=Scottsdale,ST=Arizona,C=US
ssl_debug(9):   CN=Conextrade,OU=Swisscom IT,O=Swisscom AG,L=Zurich,ST=Zurich,C=CH,EMAIL=ccc.eTrade(a)swisscom.com
ssl_debug(9):   CN=b2bproto.basf-corp.com,OU=Corporate IS,O=BASF Corporation,L=Mount Olive,ST=New Jersey,C=US
ssl_debug(9):   CN=GlobalSign Domain Validation CA - G2,O=GlobalSign nv-sa,C=BE
ssl_debug(9):   CN=Swisscom Root CA 1,OU=Digital Certificate Services,O=Swisscom,C=ch
ssl_debug(9):   CN=GeoTrust DV SSL CA,OU=Domain Validated SSL,O=GeoTrust Inc.,C=US
ssl_debug(9):   EMAIL=!sysadmin(a)elemica.com,CN=www.elemica.com,OU=Connected Solutions,O=Elemica, Inc,L=Wayne,ST=Pennsylvania,C=US
ssl_debug(9):   CN=GeoTrust SSL CA,O=GeoTrust, Inc.,C=US
ssl_debug(9):   CN=RapidSSL CA,O=GeoTrust, Inc.,C=US
ssl_debug(9):   CN=Entrust Certification Authority - L1E,OU=(c) 2009 Entrust, Inc.,OU=www.entrust.net/rpa is incorporated by reference,O=Entrust, Inc.,C=US
ssl_debug(9):   CN=EAS,O=COMPUDATA EDI Dienstleister,C=CH,EMAIL=helpdesk.dl(a)compudata.ch
ssl_debug(9):   CN=GlobalSign Domain Validation CA,O=GlobalSign nv-sa,OU=Domain Validation CA,C=BE
ssl_debug(9):   CN=GlobalSign Primary Secure Server CA,OU=Primary Secure Server CA,O=GlobalSign nv-sa,C=BE
ssl_debug(9):   CN=AddTrust External CA Root,OU=AddTrust External TTP Network,O=AddTrust AB,C=SE
ssl_debug(9):   CN=Entrust Root Certification Authority,OU=(c) 2006 Entrust, Inc.,OU=www.entrust.net/CPS is incorporated by reference,O=Entrust, Inc.,C=US
ssl_debug(9):   CN=Thawte SSL CA,O=Thawte, Inc.,C=US
ssl_debug(9):   CN=Entrust Certification Authority - L1C,OU=(c) 2009 Entrust, Inc.,OU=www.entrust.net/rpa is incorporated by reference,O=Entrust, Inc.,C=US
ssl_debug(9):   CN=UTN-USERFirst-Hardware,OU=http://www.usertrust.com,O=The USERTRUST Network,L=Salt Lake City,ST=UT,C=US
ssl_debug(9):   EMAIL=vladimir.polak(a)esa.ch,CN=Vladimir Polak,O=Einkaufsorganisation des Schweizerischen Auto- und Motorfahrzeuggewerbes,C=CH
ssl_debug(9):   CN=IT Directions and Strategies,OU=ITDS EDI,ST=WI,C=US,L=Hartland,EMAIL=aklumpp(a)itdsllc.com,O=ITDS EDI
ssl_debug(9):   CN=Entrust Certification Authority - L1B,OU=(c) 2008 Entrust, Inc.,OU=www.entrust.net/CPS is incorporated by reference,OU=CPS CONTAINS IMPORTANT LIMITATIONS OF WARRANTIES AND LIABILITY,OU=AND ADDITIONAL TERMS GOVERNING USE AND RELIANCE,O=Entrust, Inc.,C=US
ssl_debug(9):   CN=GlobalSign Organization Validation CA - G2,O=GlobalSign nv-sa,C=BE
ssl_debug(9):   CN=VeriSign Class 1 Individual Subscriber CA - G3,OU=Persona Not Validated,OU=Terms of use at https://www.verisign.com/rpa (c)09,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9):   CN=VeriSign Class 1 Individual Subscriber CA - G2,OU=Persona Not Validated,OU=Terms of use at https://www.verisign.com/rpa (c)05,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9):   CN=TeleSec ServerPass CA 1,OU=Trust Center Services,O=T-Systems International GmbH,C=DE
ssl_debug(9):   CN=TC TrustCenter Class 3 L1 CA V,OU=TC TrustCenter Class 3 L1 CA,O=TC TrustCenter GmbH,C=DE
ssl_debug(9):   C=NL,ST=Zuid-Holland,L=Spijkenisse,O=De Rijke Transport,OU=ICT,CN=smtphost.derijke.com
ssl_debug(9):   CN=VeriSign Class 3 Secure Server CA - G3,OU=Terms of use at https://www.verisign.com/rpa (c)10,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9):   CN=Comodo Class 3 Security Services CA,OU=(c)2002 Comodo Limited,OU=Terms and Conditions of use: http://www.comodo.net/repository,OU=Comodo Trust Network,O=Comodo Limited,C=GB
ssl_debug(9):   CN=UTN-USERFirst-Hardware,OU=http://www.usertrust.com,O=The USERTRUST Network,L=Salt Lake City,ST=UT,C=US
ssl_debug(9):   OU=Starfield Class 2 Certification Authority,O=Starfield Technologies, Inc.,C=US
ssl_debug(9):   EMAIL=ftp(a)csx.com,C=US,O=CSX Corporation Inc,CN=CSX_CORPORATION_AS2_02062009
ssl_debug(9):   CN=EssentialSSL CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
ssl_debug(9):   CN=Network Solutions Certificate Authority,O=Network Solutions L.L.C.,C=US
ssl_debug(9):   CN=VeriSign Class 3 Public Primary Certification Authority - G5,OU=(c) 2006 VeriSign, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(9): Received server_hello_done handshake message.
ssl_debug(9): No client certificate available, sending empty certificate message...
ssl_debug(9): Sending client_key_exchange handshake...
ssl_debug(9): Sending change_cipher_spec message...
ssl_debug(9): Sending finished message...
ssl_debug(9): Received alert message: Alert Fatal: bad certificate
ssl_debug(9): SSLException while handshaking: Peer sent alert: Alert Fatal: bad certificate
ssl_debug(9): Shutting down SSL layer...
Severity : Error
Category : /Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK
Location : com.sap.aii.messaging.net.HTTPClientConnection.call(Object)
Application : sap.com/com.sap.xi.rwb
Thread : SAPEngine_Application_Thread[impl:3]_0
Datasource : 7662250:E:\usr\sap\T37\DVEBMGS00\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 00505688007A006A0000005100001B8C0004B1CF78E9602A
Source Name : com.sap.aii.messaging.net.HTTPClientConnection
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : cc6d1cee0fec11e1c90200000074eaaa
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : /Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK
Resource Bundlename :
Session : 365
Source : com.sap.aii.messaging.net.HTTPClientConnection
ThreadObject : SAPEngine_Application_Thread[impl:3]_0
Transaction :
User : CPWONG
Dsr Root Context ID :
Dsr Connection :
Dsr Counter : -1

Hi ,
Is the above problem solved , can you share the solution.
Thanks

[svn:bz-trunk] 19160: fix the regression of failed send out unsubscription message to the message client .

Revision: 19160
Revision: 19160
Author:   [email protected]
Date:     2010-12-08 11:31:26 -0800 (Wed, 08 Dec 2010)
Log Message:
fix the regression of failed send out unsubscription message to the message client.
Basically when the MessageClient is in shutting down stage (still valid) the shutdown procedure needs to push message back to the client still. It is a regression introduced by change 18858
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageClient.java
    blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.java

Hello,
Here is my 2 cents.
Oracle recommends you set the Oc4jCacheSize parameter to reduce the occurrences of MOD_OC4J_0087 and
related errors in your Apache error logs. To change this parameter, follow these steps:
1. Stop the OPMN processes on the middle tier.
2. On the middle-tier computer, open a terminal window and go to $ORACLE_HOME/Apache/Apache/conf.
3. Enter the following command:
cp mod_oc4j.conf mod_oc4j.conf.pre3604573
4. Edit the mod_oc4j.conf file by adding the following line after the </IfModule> line, but before the
Oc4Jmount /j2ee/* line:
Oc4jCacheSize 0
5. Start the OracleOPMN processes on the middle tier.
I would still suggest to analyze the stack trace further for exact issues.
Rgds,Ramesh

Why can't i send a single text message to more than 10 contacts??

Why can't i send a single text message to more than 10 contacts?? I use AT&T

calfonsi wrote:
Why can't i send a single text message to more than 10 contacts?? I use AT&T
That's a built in limitation of iOS. If you need to send messages to larger groups of people, you'll either need to send them in batches of 10 or use a dedicated group messaging app. GroupMe works pretty well. Blackberry Messenger is also an option, though I don't like the interface as much.

Can I get both time and date in every single message that I receive or send?

I have been usine iPhone for a while now, and I was wondering if you can change the message-settings somehow, so that I can see both date and time in every single message, instead of every 30 minutes, is this possible?

Sorry, no.
Suggest such to Apple here:
http://www.apple.com/feedback/iphone.html

Could I send a immediately message to client??

Hi all:
I wanna send a imeediately message when I want my user know something on my web site.Is there any tech can make it????
plz give me a suggestion....
Thanx alot.

Are your users always connected to the net?
If so, use an applet which connects your server and waits
for messages. When it encounters one, it can display it.

Pending Messages waiting for Client Acknowledgement

          Hi,
          I have tried to search the Internet for an answer to this question but failed.
          Any clue???
          I have setup a queue on BEA WLS 7.4. I have four consumers which connect concurrently
          to dequeue messages. Each of the consumers serve as a proxy to other clients
          waiting for the messages.
          The proxy application (consumer) is developed such that it will send the client_acknowledge
          to the Q manager after it finishes processing the received message and sends it
          successfully to the external client.
          I noticed that in some exceptional cases which I cannot reproduce, the proxy application
          would fail to send the message to client and therefore wouldn't send the client_acknowldege.
          Although I tried to catch all possible exceptions, i cannot catch this single
          exception that causes my proxy to continue processing the messages in a proper
          way. The problem is that I end up with some Pending Messages on the queue which
          cannot be available to other consumers and would stay that way till the consumer
          that was attempting to dequeue it is killed.
          Isn't there any way to configure an expiry period for this client_acknowledge
          wait state??? In other words, is it possible to configure a time after which
          the JMS provider would no longer be waiting for the client_acknowledge and sends
          the pending message back to the Q in a state that makes it available to other
          consumers.


Sorry. Once a message has been received in "CLIENT_ACKNOWLEDGE" mode, it
          remains pending and unavailable to other consumers until either the consumer
          is closed, acknowledge is called, or the client disconnects.
          Have you tried using a transacted session? In that case, the transaction
          will time out eventually, which will roll back the transaction and make the
          message visible again. You can control the length of this timeout using the
          "TransactionTimeout" parameter on the JMS connection factory.
          greg
          "Muhannad" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Hi,
          > I have tried to search the Internet for an answer to this question but
          failed.
          > Any clue???
          >
          > I have setup a queue on BEA WLS 7.4. I have four consumers which connect
          concurrently
          > to dequeue messages. Each of the consumers serve as a proxy to other
          clients
          > waiting for the messages.
          >
          > The proxy application (consumer) is developed such that it will send the
          client_acknowledge
          > to the Q manager after it finishes processing the received message and
          sends it
          > successfully to the external client.
          >
          > I noticed that in some exceptional cases which I cannot reproduce, the
          proxy application
          > would fail to send the message to client and therefore wouldn't send the
          client_acknowldege.
          > Although I tried to catch all possible exceptions, i cannot catch this
          single
          > exception that causes my proxy to continue processing the messages in a
          proper
          > way. The problem is that I end up with some Pending Messages on the queue
          which
          > cannot be available to other consumers and would stay that way till the
          consumer
          > that was attempting to dequeue it is killed.
          >
          > Isn't there any way to configure an expiry period for this
          client_acknowledge
          > wait state??? In other words, is it possible to configure a time after
          which
          > the JMS provider would no longer be waiting for the client_acknowledge and
          sends
          > the pending message back to the Q in a state that makes it available to
          other
          > consumers.

How I send Instant system message to All online terminals

Hi gurus,
For sending the instant system message to online user, I am using SM02.
Problem is-
Some times one user login on two different PCs.
When I send the message to all users, message flash on only single PC in case of same user logon two different machine.
I would like to know , have any other options for send the instant message to all online terminals (PCs) which are connected to SAP server.
Regards,
Tapovardhan
Message was edited by: Tapovardhan Singh
Message was edited by: Tapovardhan Singh

Hi,
To send the message to just one user, you can "test" the function module directly from transaction se37.
If you want to send it to all logged on users, the following code could maybe be useful:
REPORT Z_MESSAGE_TO_ALL.
PARAMETERS: MESSAGE(128) default ' Error ! Please logoff now ! '.
DATA: OPCODE TYPE X VALUE 2.
DATA: BEGIN OF USR_TABL OCCURS 5.
       INCLUDE STRUCTURE UINFO.
DATA: END OF USR_TABL.
CALL 'ThUsrInfo' ID 'OPCODE' FIELD OPCODE
                 ID 'TAB' FIELD USR_TABL-SYS.
LOOP AT USR_TABL.
   CALL FUNCTION 'TH_POPUP'
        EXPORTING
             CLIENT         = SY-MANDT
             USER           = USR_TABL-BNAME
             MESSAGE        = MESSAGE
           MESSAGE_LEN    = 0
           CUT_BLANKS     = ' '
        EXCEPTIONS
             USER_NOT_FOUND = 1
             OTHERS         = 2.
ENDLOOP.
Regards
Rolf

Sending email using system default mail client

I'm working on a project right now, and I have no desire to develop a new mailing system. What would be very convienient for me is to have a call, opening the systems default mail client. Preferrably with some of the fields, like "to" and "Subject" being specifed by me.
I'm not really aware of how the JavaMail system works, but it seems to me like a backend API, able to transmit the mail, but not much else.
Could anyone give some hints on how to open the system default mailer?

I found this example here. Seems pretty good - just what I was looking for too!
from https://jdic.dev.java.net/documentation/Examples.html
Case# 6: Launch the system default mailer and send the constructed message with UI or without UI.
import java.util.List;
import java.util.ArrayList;
import org.jdesktop.jdic.desktop.Desktop;
import org.jdesktop.jdic.desktop.DesktopException;
import org.jdesktop.jdic.desktop.Message;
public class MailTest {
    public static void main(String[] args) {
        Message msg = new Message();
        List toList = new ArrayList();
        toList.add("[email protected]");
        msg.setToList(toList);
        List ccList = new ArrayList();
        ccList.add("[email protected]");
        ccList.add("[email protected]");
        msg.setCcList(ccList);
        msg.setSubject("Hello");
        msg.setBody("Test");
        List attachList = new ArrayList();
        attachList.add("C:\\test\\test.txt");
        msg.setAttachmentList(attachList);
        try {
            // Send mail in UI mode.
            Desktop.mail(msg);
        } catch (DesktopException e) {
            e.printStackTrace();
}

Send a Single Message to a Client

Similar Messages

Maybe you are looking for