ADF Mobile : Rest call to a webservice using https - Certificate Error

I'm trying to connect to a web service giving json and which uses https. I am using the following code.
Also SalesApp connects to https://abc.com
RestServiceAdapter restServiceAdapter = Model.createRestServiceAdapter();
restServiceAdapter.clearRequestProperties();
restServiceAdapter.setConnectionName("SalesApp");
restServiceAdapter.setRequestType(RestServiceAdapter.REQUEST_TYPE_GET);
restServiceAdapter.setRetryLimit(0);
restServiceAdapter.setRequestURI("/sales/rest/v1/resources");
try {
response = restServiceAdapter.send("");
I am getting an error of " Certificate was issued by an unrecognized entity ".
Is there anyway to ignore the certificate warning ? Any request properties which can help with this?
I'm not looking at adding any private certificates/verfying the certificate issued by server, just want to ignore the warning
and proceed with the rest call.

Hi, sure you will need to register your private certificate with ADF Mobile's embedded JVM. This is a security mechanism - the JVM we embed will only recognize certificates from well-know CA out of box. However, you can register your private certificate with the JVM. The steps are described in the ADF Mobile Developer Guide: http://docs.oracle.com/cd/E35521_01/doc.111230/e24475/security.htm#CDDCCDFF.
Please note that you will need to be very careful when registering the JVM - extra spaces for example will cause certificate error and it could be hard to diagnose. Please ensure all the fields matches exactly with your private certificate's fields.
Thanks,
Joe Huang

Similar Messages

  • Is it possible to call a SOAP webservice using HTTP POST adapter

    Hello Experts,
    Is it possible to call a webservice using a HTTP adapter with POST method? If yes, how?
    Regards,
    Diptee

    No this will not work since you have additional SOAP information (i.e. SOAP envelope, security information) in addition to the payload. If you need a simple HTTP-Post for example, then you don't need SOAP, you can use the more simple http protocol without the additional features of SOAP.
    Also refer to this link for differences: Difference b/w SOAP and HTTP

  • Web Dynpro application calling external web server using HTTPS giving error

    Hello,
    I don't know whether this is the right question in this forum but my ABAP web-dynpro applicaiton is expected to call another HTTP application on external web server through HTTPS. Presently it is calling through plain HTTP but we want to have HTTPS.
    Here are the steps that we followed based on the link from help.sap.com
    1] Received the certificate files from external web server
    2] Created SSL Anonymous client
    3] Imported the certificate files under this client and added into the certificate list
    4] Re-started ICM
    5] Created RFC Destination of type HTTP to connect to external server with SSL option and basic authentication. This RFC destination was working under plain HTTP.
    When tried with Test connection it gave error "ICM_HTTP_CONNECTION_FAILED".
    Any idea what might be missing. Thanks in advance.
    Regards
    Rajeev

    Used proper certificate after which the error went away

  • Problem in calling webservice using https from livecycle designer

    I  want to call a webservice written in .net(c#) using https  from livecycle  designer.I can call webservice using http ,but when i try with https it is  failing.If there any special configuration have to do in server for this ?I have  already put crossdomain in server.
    Waiting  for your reply
    thank's

    How did you call from LC? Please help me out either one is fine to me http or https
    Srujan

  • Calling A Secured webservice using Username and password in the Soap header

    I want to call a secured webservice.
    The Username and password should be sent with the payload in the SOAP Header
    as
    <wsse:Security S:mustunderstand="0" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <wsse:UsernameToken wsu:Id="SecurityToken-XXXXXXXXXXXXXXXXXXXXXXXXX" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <wsse:Username>uname</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">pwd</wsse:Password>
    </wsse:UsernameToken>
    </wsse:Security>
    Can you please send me the steps?
    I tried with giving the username and password under Service Account.
    I tried to create a wspolicy under business service. But nothing works...
    Please help me at the earliest.
    Also please give me steps in sequence.

    Now i made sure that the endpoint is available!
    Now am getting this error:
    <soapenv:Fault>
    <faultcode>soapenv:Server</faultcode>
    <faultstring>BEA-380002: localhost1</faultstring>
    <detail>
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-380002</con:errorCode>
    <con:reason>localhost1</con:reason>
    <con:location>
    <con:node>RouteNode1</con:node>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>
    </detail>
    </soapenv:Fault>
    Also in the invocation trace i can observe the following things:
    Under Invocation Trace:-
    ========================
         Receiving request =====> Initial Message context
         ===============================================
         under added header:-
         ==================
         <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
         </soap:Header>
         under RouteNode1
    ================
         Route to "TargetMyService_BS"
    $header (request):-
    <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    </soap:Header>
    Under Message Context changes:-
    *===============================*
    I can find this element also:-
    con:security>
    *<con:doOutboundWss>false</con:doOutboundWss>*
    *</con:security>*
    eventhough we enabled ws security, how the above tag can be false?
    I think its getting failed to populate the header with the required login credentials.
    The other doubt i have is:-
    =================
    I have chosen the service account type is static...is this right?

  • Calling a WL Webservice using wsse from a java class

    One of the business partners I am integrating with needs to call my web service
    which is secured with UserTokens. The buiness partner is running in a J2EE environment,
    but not BEA. They will be calling the web service using a Java Class. Do I need
    to create a Java proxy for them to be able to reach my web service? Do I run the
    java proxy file on my side, or do i give it to them to run? Do i need to provide
    them with a client security policy file?
    Any help is appricated
    Thanks
    Linda

    Hi Linda,
    Currently we support only two types of tokens: UsernameToken and
    BinarySecurityToken, see the docs [1] for additional details. The
    policy file you are referring to is WLW specific and will not be
    portable. We are working towards the (yet to be finalized) WS-Policy
    framework for the next major release.
    Regards,
    Bruce
    [1]
    http://edocs.bea.com/wls/docs81/webserv/security.html#1082126
    [2]
    http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/security/ws-security/ovwWebServiceSecurity.html
    [3]
    http://ftpna2.bea.com/pub/downloads/WS-Policy.pdf
    Linda Gilligan wrote:
    >
    One of the business partners I am integrating with needs to call my web service
    which is secured with UserTokens. The buiness partner is running in a J2EE environment,
    but not BEA. They will be calling the web service using a Java Class. Do I need
    to create a Java proxy for them to be able to reach my web service? Do I run the
    java proxy file on my side, or do i give it to them to run? Do i need to provide
    them with a client security policy file?
    Any help is appricated
    Thanks
    Linda

  • RFC-to-SOAP webservice using HTTPS

    Hi experts,
    I have a RFC-to-SOAP (sync) and the URL of the webservice is using HTTPS. I'm not the owner of the webservice.
    Encountered these errors
    - for sender comm :
    com.sap.aii.af.ra.ms.api.DeliveryException: Peer sent alert: Alert Fatal: illegal parameter
    - receiver comm :
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Peer sent alert: Alert Fatal: illegal parameter: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: illegal parameter
    We are not using certificate authentication so I don't think that's the cause.
    Have checked that the https is running ok for ABAP but I don't think that got anything to do with the errors. Is there something wrong with SSL setting for J2EE? If yes, how may I check?
    Are there some parameters to be set up? In the RFC sender comm & SOAP receiver comm, I do not find any special settings for https.
    I have read this link : http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm. Is it necessary to set the Exchange Profile Parameters? My BASIS colleague is now checking it.
    Thanks for reading and will appreciate any advice!

    Thanks Prateek for the quick reply!
    Re HTTPS certificate, do you mean the cert for my XI server or the cert from the web service?
    I have tested calling the web service using SOAPUI and it works fine without using the cert given by the web service (which is expired anyway)...

  • OSB 10.3.1 : Calling externall MTOM webservice through HTTPS

    Hi,
    We have OSB process that calls MTOM webservice via Business Service. It's works fine over HTTP connection.
    We secure the connection one-way ssl client, we imported public certificate to trusted keystore in wls.
    The business service calls the webservice over https, the Webservice receive the streaming and generates file.
    The problem is when the webservice returns result, the connection is froze and the wls where is the webservice generates this exception
    Couldn't create SOAP message due to exception: org.jvnet.mimepull.MIMEParsingException: Missing start boundary
    com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: org.jvnet.mimepull.MIMEParsingException: Missing start boundary
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:292)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:93)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:432)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
    at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: org.jvnet.mimepull.MIMEParsingException: Missing start boundary
    at org.jvnet.mimepull.MIMEParser.skipPreamble(MIMEParser.java:290)
    at org.jvnet.mimepull.MIMEParser.access$200(MIMEParser.java:62)
    at org.jvnet.mimepull.MIMEParser$MIMEEventIterator.next(MIMEParser.java:130)
    at org.jvnet.mimepull.MIMEParser$MIMEEventIterator.next(MIMEParser.java:117)
    at org.jvnet.mimepull.MIMEMessage.makeProgress(MIMEMessage.java:186)
    at org.jvnet.mimepull.MIMEMessage.parseAll(MIMEMessage.java:168)
    at org.jvnet.mimepull.MIMEMessage.<init>(MIMEMessage.java:85)
    at com.sun.xml.ws.encoding.MimeMultipartParser.<init>(MimeMultipartParser.java:88)
    at com.sun.xml.ws.encoding.MimeCodec.decode(MimeCodec.java:180)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:279)
    I tested over https the same webservice using java client WS (generated by jdeveloper) and that works fine.
    Any idea
    Thanks,
    Maroun

    Resolved
    The problem is coming from OSB it happens when Business Service invoke WS in HTTPS, BS sends twice the request the first one contains the right envelop and the second one contains in empty request.
    The Oracle Support helped me to resolve the problem; we changed the QoS (Quality Of Service) to Exactly once
    Maroun

  • Invokation of Webservices using HTTP

    Can I invoke webservices in SAP using HTTP instead of SOAP? If so How?

    Hi Vijay,
    yes we can do it with HTTP
    Configuring the Receiver Plain HTTP Adapter
    Use
    The plain HTTP outbound channel is a service provided by the Integration Engine. The system is addressed when technical routing determines a corresponding communication channel for the logical receiver from logical routing. The system sends the payload of the message to an HTTP address using HTTP, without being enhanced with an envelope.
    Integration
    You configure the adapter on the Parameters tab page during the definition of a communication channel in the Integration Server.
    Activities
    The plain HTTP adapter gives the receiver system the following specifications:
    Transport Protocol
    HTTP 1.0
    Message Protocol
    XI payload in HTTP body
    Adapter Engine
    Integration Server
    Addressing Type
    URL Address
    HTTP Destination
    Specify the target host, service number, and path prefix including query string:
    http://<hostname:port>/<path>?<query-string>
    You can identify the target host (HTTP port) of a SAP Web Application Server using the ICM monitor.
    Host and port of the HTTP proxy (optional if there is a firewall between the plain HTTP adapter and the receiver system)
    Authentication data for the receiver system, see also: transaction Display and Maintain RFC Destinations (SM59)
    Specify the RFC destination.
    Parameters from the Communication Channel for Technical Routing
    ●      Content type (the entry text/XML is expected as default)
    Specifies the content format  (payload) that the message should have.
    ●      (Optional) header fields for the receiver-specific protocol
    ●      Select Additional Query String Attributes:
    ○       Sender party
    ○       Sender service
    ○       Receiver interface
    ○       Message ID
    ○       Quality of service
    ○       Queue ID
    The queue ID is only required if the quality of service is EOIO.
    ●      Specifications for payload manipulation
    ○       XML code (default UTF-8)
    Specifies the character set.
    ○       URL escaping
    Presents the XML in a URL-enabled format.
    Special characters that could be interpreted as control characters are replaced with escape characters (masked).
    ○       Prolog
    Enhances the payload for particular servers (optional, see below).
    ○       Epilog
    Enhances the payload for particular servers (optional, see below).
    Adapter-Specific Message Attributes
    ●      To evaluate adapter attributes in the message header of the XI message, select Set Adapter-Specific Message Attributes.
    ●      If you want missing message attributes to trigger an error message, select Fail If Adapter-Specific Message Attributes Missing.
    If the indicator is set and the header for adapter-specific message attributes or one of the set attributes is missing from the message, this leads to a system error (red flag).
    If you do not set the indicator, and message attributes are missing, the adapter accesses information from the adapter configuration.
    ●      If you want to use an HTTP destination or URL set by the mapping, select URL orHTTP Destination.
    (The indicator displayed depends on the Addressing Type you selected above). If you set the indicator, the URL or HTTP destination set dynamically is called by HTTP.
    If the message header does not contain the URL or the HTTP destination, and you have set the Fail If Adapter-Specific Message Attributes Missingindicator, the XI message is set to status System Error.
    If you do not set the indicator, the URL or HTTP destination defined statically in the communication channel is used.
    The technical names of the fields are:
    ○       URL: TargetURL
    ○       HTTP Destination: HTTPDest
    ●      If you want to use HTTP header fields, select Apply HTTP Header Fields and enter the fields in Field 1 to Field 6.
    The fields are embedded in the HTTP request under the names you enter here.
    The technical names of the fields are HeaderFieldOne, .... HeaderFieldSix.
    ●      If you want to use URL parameters, select Apply URL Parameters and enter the parameters in the fields Parameter 1 to Parameter 6.
    The parameters are included in the HTTP request under the names specified here.
    The technical names of the fields are URLParamOne, u2026, URLParamSix.
    ●      If you want to save HTTP header fields from the synchronous response in the XI message header, choose HTTP Header Fields (Synchronous Response) and enter the fields in the fields Field 1 to Field 6.
    The fields must have the same names as the fields that are also to be sent in the HTTP response.
    The technical names of the fields are HeaderFieldOne,...,HeaderFieldSix.
    ●      The attribute namespace for the adapter is http://sap.com/xi/XI/System/HTTP.

  • Generating Webservice using HTTPS in  XI.

    Hi Experts,
         I have generated webservice in XI using http , and i have tested using infopath soap client, its working fine.  I have generated webservice in XI using htpps using the same scenario,  when i am testing using infopath as soap client and tested, its giving error, request is not hitting the XI system at all. do i need to configure any certificate in infopath or in XI server, please can anyone advice. i have configured HPPTS without client authentication in SOAP adapter.
    Thanks,
    Dhanush

    Hi Experts,
      I am not able to get exact answer after reading the sap.help.com, sap notes.
    My scenario is RFC < ---> SOAP ( webservice) ,  i have generated webservice with the HTTPS and secured port of XI,  When i copy and past in IE browser, its showing status is OK,  but request is not hitting the XI system. what are things to be taken care at soap client and XI server side, do i need to install any certificats at client side or server side. please advice me.
    Thanks,
    Siva

  • Consume webservice using HTTP adapter

    Hi PI Experts,
    Can we consume a webservice using a HTTP adapter?
    If yes can anyone share some knowledge, how to do so?
    Thanks & REgards,
    Krishna

    Hi Krishna,
    I think this can be done using FLEX.(not sure).
    Ref:  http://wiki.sdn.sap.com/wiki/display/EmTech/ConsumingABAPWebServicesusing+Flex
    Thanks,

  • Accessing External Url using Http Utility | Error when using from Weblogic on Solaris

    We are using Http Utility (http://jakarta.apache.org/commons/httpclient/) from
    Apache for accessing external URL. A XML string is sent as POST parameter to the
    URL and the response is also an XML string. The URL is accessed over HTTPS protocol.
    I am setting the following parameters in the java class:
    Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
    // set the property
    System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
    The java class written to access the external URL using Http Utility works perfectly
    fine when it is run from either the command line (of Windows or Solaris using
    main() ) or from weblogic on windows. The same java class throws an exception
    when run from Solaris instance of Weblogic
    2003-09-30 11:02:12,411 FATAL [com.bp.beyondbp.presentation.userregistration.action.LloydsValidator]
    EXCEPTION: com.bp.beyondbp.presentation.userregistration.exception.LlyodsValidationFailedException,
    MESSAGE: Write Channel Closed, possible SSL handshaking or trust failure;
    CAUSE: (java.io.IOException: Write Channel Closed, possible SSL handshaking or
    trust failure)
    at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.postXMLtoLloyd(LloydsValidator.java:243)
    at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.validateLlyodsForNewUser(LloydsValidator.java:95)
    at com.bp.beyondbp.presentation.userregistration.action.PreferencesActionForm.validate(PreferencesActionForm.java:326)
    at org.apache.struts.action.RequestProcessor.processValidate(RequestProcessor.java:942)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:255)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
    at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    java.io.IOException: Write Channel Closed, possible SSL handshaking or trust failure
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown
    Source)
    at com.certicom.tls.record.ReadHandler.interpretContent(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown
    Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown
    Source)
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at org.apache.commons.httpclient.HttpConnection$WrappedOutputStream.write(HttpConnection.java:1344)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:67)
    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:125)
    at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:779)
    at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2179)
    at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2534)
    I tried to debug the problem by looking at system properties on windows and solaris,
    the difference that I found was
    On Windows
    [exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol
    On Solaris
    [exec] tModelInstanceInfo_description : weblogic.utils|weblogic.tils|weblogic.net|weblogic.management
    After this I changed the startWLS.sh on Solaris and set
    -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol in java options.
    On looking the system properties again, the output was
    [exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol|weblogic.utils|weblogic.utils|weblogic.net|weblogic.management
    But still the error is same. Can somebody help me out here as to what is going
    wrong? Please find the java class attached for reference, please have a look at
    postXMLtoLloyd() method in the class file..
    [LloydsValidator.java]

    We are using Http Utility (http://jakarta.apache.org/commons/httpclient/) from
    Apache for accessing external URL. A XML string is sent as POST parameter to the
    URL and the response is also an XML string. The URL is accessed over HTTPS protocol.
    I am setting the following parameters in the java class:
    Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
    // set the property
    System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
    The java class written to access the external URL using Http Utility works perfectly
    fine when it is run from either the command line (of Windows or Solaris using
    main() ) or from weblogic on windows. The same java class throws an exception
    when run from Solaris instance of Weblogic
    2003-09-30 11:02:12,411 FATAL [com.bp.beyondbp.presentation.userregistration.action.LloydsValidator]
    EXCEPTION: com.bp.beyondbp.presentation.userregistration.exception.LlyodsValidationFailedException,
    MESSAGE: Write Channel Closed, possible SSL handshaking or trust failure;
    CAUSE: (java.io.IOException: Write Channel Closed, possible SSL handshaking or
    trust failure)
    at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.postXMLtoLloyd(LloydsValidator.java:243)
    at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.validateLlyodsForNewUser(LloydsValidator.java:95)
    at com.bp.beyondbp.presentation.userregistration.action.PreferencesActionForm.validate(PreferencesActionForm.java:326)
    at org.apache.struts.action.RequestProcessor.processValidate(RequestProcessor.java:942)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:255)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
    at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    java.io.IOException: Write Channel Closed, possible SSL handshaking or trust failure
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown
    Source)
    at com.certicom.tls.record.ReadHandler.interpretContent(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown
    Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown
    Source)
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at org.apache.commons.httpclient.HttpConnection$WrappedOutputStream.write(HttpConnection.java:1344)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:67)
    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:125)
    at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:779)
    at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2179)
    at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2534)
    I tried to debug the problem by looking at system properties on windows and solaris,
    the difference that I found was
    On Windows
    [exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol
    On Solaris
    [exec] tModelInstanceInfo_description : weblogic.utils|weblogic.tils|weblogic.net|weblogic.management
    After this I changed the startWLS.sh on Solaris and set
    -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol in java options.
    On looking the system properties again, the output was
    [exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol|weblogic.utils|weblogic.utils|weblogic.net|weblogic.management
    But still the error is same. Can somebody help me out here as to what is going
    wrong? Please find the java class attached for reference, please have a look at
    postXMLtoLloyd() method in the class file..
    [LloydsValidator.java]

  • ADF mobile application - Unable to deploy webservices on Integrated weblogi

    hi,
    I have followed video given in.
    https://blogs.oracle.com/shay/entry/developing_with_oracle_adf_mobile
    Following steps are being followed by me:
    File -> New -> General -> Application -> Fusion Web Application (ADF) Created one application 2. Right clicked on model New-> Business Tier -> Business Component from table and created Entity object and view object for department table.
    Then followed the steps as per the video. But not able to deploy webservice as given in video.
    It is not generating that link after running AppModuleServiceTest.java.
    , 2013 7:23:25 PM IST> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 127.0.0.1:57,071 during the configured idle timeout of 5 secs>
    This is the last line I am getting in the logs generated.
    Can you please tell whether the steps followed are correct or not?
    Or what else needs to be done?
    Please help.

    Try searching following file
    BB_ADFNMC_Bindings
    and all files with BB_ADFNMC_*
    these are approx 10 files , copy all of them into simulator folder inside RESERCH IN MOTION folder
    or load these through simultor->File->Load Blackberry Application .
    I hope it should help :)

  • How to call java function with parameter from javascript in adf mobile?

    how to call java function with parameter from javascript in adf mobile?

    The ADF Mobile Container Utilities API may be used from JavaScript or Java.
    Application Container APIs - 11g Release 2 (11.1.2.4.0)

  • How to add ADMOB advertisement into Android app using ADF Mobile

    hi,
    i need to integrate ADMOB advertisement into Android app.
    can i do that using Oracle ADF mobile?
    regards,
    ad

    Hi,
    I think, there is one example for ADF Mobile push notification with Google Cloud Messaging.
    http://deepakcs.blogspot.in/2013/06/adf-mobile-push-notifications-with.html
    Eba

Maybe you are looking for

  • Macbook gma 950 driver

    is there a driver update for my macbooks gma 950 grafics card ?

  • Single Subcon Vendor for multiple Plants - CTM

    Dear friends, We are planning some materials with Subcontracting scenario using CTM Facing issue when same vendor is executing sub-con process of same material for multiple plants Total demand of lower level material is flowing to a single plant inst

  • Should I close this account?

    So I have been thinking about closing my secured card with SDFCU. When I got it, I never thought Id get unsecured cards so quick and never use it anyways. However, I was worried about score dropping. I have no idea what my AAOA is. My credit history

  • Error while using Tag Library in Weblogic !

    Hi, I am trying to run a JSP in weblogic which makes use of tag library in it. I am getting the following error C:\bea\weblogic81\samples\domains\examples\.\examplesServer\.wlnotdelete\extract\examplesServer_Bidla_Bidla\jsp_servlet\_registration\__fi

  • Can't create Test package

    Hello, After updating up to 22 version new problem has apeared in Test management. I can't create test package in newly created Test Plan. There are disabled buttons like a "create package" and "change package" on the "Test package management" screan