Document upload in web service

Hi,
I am creating a webservice to upload a document, how can I upload the content without using Options.CONTENTSTREAM as it is mentioned that it cant be used for webservices.
I tried to upload using HttpConnection but I could not pass the entire session information to maintain the same session for the next operations.
Can anyone let me know how this can be done.
Thanks,
John

Hi John!
Have You read this before?
http://www.oracle.com/technology/products/contentdb/dev/devfaq.html#ws-updown
and (same site):
http://www.oracle.com/technology/products/contentdb/dev/devfaq.html#cdbdevkit-clientfeat
Best Regards,
Tamas

Similar Messages

  • Purchase Requisition Document Upload Though Web Service

    Hi!
    I really hope someone can help me with this one. My client creates purchase requisitions from an external system that interfaces into SAP. In SAP there is functionality to attach documents to a purchase req by choosing "Services for object". However, the client now has a new requirement that they want to upload and attach certain documents to the purchase req from their external system through a web service.
    Is this possible? If not, is there another way they can upload the document to SAP? I stumbled upon the following web service: ECC_DOCUMENTCRTRC1. I have not been able to find any documentation on this web service. Can I use this web service for my requirement? If not, what does this web service do and does anyone maybe have some example code where this service is used?
    Thank you!
    Iwan Ferreira

    Hi Iwan,
    Where you able to perform this? Dis you find the WS? I'm facing the same situation...
    Thanks a lot and best regards!
    Maria Margarita

  • Send a map of documents via Invoke Web Service

    Hi,
        I have one process with map of documents and 2nd process on other server, where input variable is map od documents too. How can I send this map between these processes via "Invoke Web Service" component? Simple datatypes I can.
    Petr

    Take a look at Quick Start: Assembling a PDF document using the web service API
    It shows how to create an input map for multiple documents.
    But it sounds like you're asking how to create a WSDL that allows you to use an input map as an argument in a Web Service invocation. If so, take a look at the Assembler services WSDL. For 8.2, access
    http://myServer:myPort/soap/services/AssemblerService?wsdl

  • Refreshing a document with Restful Web Services

    Hello,
    I want to refresh a document with Restful Web Services. The document is based on a BEx query with a date variable, which is set as a prompt.
    In order to refresh I send a PUT request like:
    PUT <webiURL>/documents/{documentId}/parameters
    and add the parameter, which is the prompt variable, to the body:
    {"parameters":{"parameter":[{"id":0,"answer":{"@type":"Date","values":{"value":"2014-07-01T00:00:00.000+00:00"}}}]}}
    Then I get a result like:
    {"success":{"message":"The resource of type 'Document' with identifier '1234' has been successfully updated.","id":1234}}
    Now I assume that the document is refreshed. However if I now read the properties with:
    GET <webiURL>/documents/{documentId}/properties
    the lastrefreshtime is not changed.
    Has anybody an idea what happens during a refresh and what is updated?
    Kind regards,
    Michael

    Hi,
    I have analyzed that the refresh seems to be only valid for the current session. This means, if I logon, refresh the document and determine the properties, I get the new refresh time.
    However, if I logoff, I still get the old refresh time. So the refresh is lost or only valid for a session.
    Is this the default behaviour?
    Regards,
    Michael

  • NULL ARRAY PROBLEM... in DOCUMENT/LITERAL type web service

    let method signature is like this,
    public int ABC(String[] a);
    i am sending an null array from client side, like
    ABC(null);
    but on web service layer i am getting an array with length 1
    and element of this array is null.
    for example, {null} where i should get simple null, not an array with null element.

    My guess is that it is because .NET defaults to generating a document style interface whereas JDeveloper defaults to generating an RPC style interface. The end result is that JDeveloper wraps the document interface in something that looks document like - thus your client. To see how to handle this right now, check out this sample - you have to parse the XML:
    http://otn.oracle.com/tech/webservices/htdocs/series/net/content.html
    In the preview of JDeveloper 9.0.3 which is due quite soon - next few weeks roughly (crossing my fingers) - JDeveloper will wrap .NET document based Web services in a much more elegant wrapper - giving you exactly what you are looking for - a method called Validate rather than a vector of Elements.
    What I don't understand in your sample, however, is that you have WSDL generated from JDeveloper versus WSDL generated from .NET. Did you also do an implementation of the validate method in Java too?
    Mike.

  • JAX-rpx document literal type web services

    I was trying to create a Document centric Web service. I followed all the steps in the document "Patterns and Designs for Building Document based Web Services" available at java.sun.com. I created the XSD's and WSDL files (top down approach). i used the following command of wscompile tool to generate the java source code.
    wscompile -import -d build/classes -keep -s build/src -model build/model.xml.gz
    to publich the web service on a server.
    When the tool generates the code, the parameters for the method are the elements of the schema, instead of being an object, specified in the WSDL.
    // This class was generated by the JAXRPC SI, do not edit.
    // Contents subject to change without notice.
    // JAX-RPC Standard Implementation (1.1.2_01, build R29)
    // Generated source version: 1.1.2
    package com.galaxyplus.tranentry.services;
    public interface IPurchaseOrder extends java.rmi.Remote {
        public com.galaxyplus.tranentry.services.PurchaseOrderStatus acceptPO(com.galaxyplus.tranentry.services.Address billTo, java.util.Calendar createDate, com.galaxyplus.tranentry.services.LineItem[] items, java.lang.String poID, com.galaxyplus.tranentry.services.Address shipTo) throws
             java.rmi.RemoteException;
    }It was supposed to be
    // This class was generated by the JAXRPC SI, do not edit.
    // Contents subject to change without notice.
    // JAX-RPC Standard Implementation (1.1_03, build R65)
    package com.examples.docliteral;
    public interface IPurchaseOrder extends java.rmi.Remote {
        public com.examples.docliteral.PurchaseOrderStatus
             acceptPO(com.examples.docliteral.PurchaseOrder parameters) throws
                 java.rmi.RemoteException;
    }Does any one have any inputs on this. I am using the same example as in the Document.
    Thanks

    More Information
    PurchaseOrder.xsd
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- edited with XMLSpy v2005 sp1 U (http://www.xmlspy.com) by Dan Carnell (Fiserv) -->
    <schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="uri:X" targetNamespace="uri:X">
         <element name="PurchaseOrderDocument" type="tns:PurchaseOrder"/>
         <complexType name="Address">
              <sequence>
                   <element name="street" type="string" nillable="false"/>
                   <element name="city" type="string" nillable="false"/>
                   <element name="state" type="string" nillable="false"/>
                   <element name="zipCode" type="string" nillable="false"/>
              </sequence>
         </complexType>
         <complexType name="LineItem">
              <sequence>
                   <element name="itemname" type="string" nillable="false"/>
                   <element name="price" type="decimal" nillable="false"/>
                   <element name="quantity" type="int" nillable="false"/>
              </sequence>
         </complexType>
         <complexType name="PurchaseOrder">
              <sequence>
                   <element name="billTo" type="tns:Address" nillable="false"/>
                   <element name="createDate" type="dateTime" nillable="false"/>
                   <element name="items" type="tns:LineItem" nillable="false" minOccurs="0" maxOccurs="unbounded"/>
                   <element name="poID" type="string" nillable="false"/>
                   <element name="shipTo" type="tns:Address" nillable="false"/>
              </sequence>
         </complexType>
    </schema>Status.xsd
    <?xml version="1.0" encoding="UTF-8"?>
    <schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="uri:X" targetNamespace="uri:X">
         <element name="Status" type="tns:PurchaseOrderStatus"/>
         <complexType name="PurchaseOrderStatus">
              <sequence>
                   <element name="orderid" type="string" nillable="false"/>
                   <element name="timestamp" type="string" nillable="true"/>
              </sequence>
         </complexType>
    </schema>Abstract.wsdl
    <!-- edited with XMLSpy v2005 sp1 U (http://www.xmlspy.com) by Dan Carnell (Fiserv) -->
    <definitions xmlns:tns="urn:poservice" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="uri:X" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    targetNamespace="urn:poservice" name="POService">
         <types>
              <xs:schema>
                   <xs:import namespace="uri:X" schemaLocation="PurchaseOrder.xsd"/>
                   <xs:import namespace="uri:X" schemaLocation="Status.xsd"/>
              </xs:schema>
         </types>
         <message name="IPurchaseOrder_acceptPO">
              <part name="parameters" element="ns1:PurchaseOrderDocument"/>
         </message>
         <message name="IPurchaseOrder_acceptPOResponse">
              <part name="result" element="ns1:Status"/>
         </message>
         <portType name="IPurchaseOrder">
              <operation name="acceptPO">
                   <input message="tns:IPurchaseOrder_acceptPO"/>
                   <output message="tns:IPurchaseOrder_acceptPOResponse"/>
              </operation>
         </portType>
    </definitions>poservice.wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions xmlns:tns="urn:poservice"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    targetNamespace="urn:poservice" name="POService">
         <import namespace="urn:poservice" location="Abstract.wsdl"/>
         <binding name="IPurchaseOrderBinding" type="tns:IPurchaseOrder">
              <soap:binding style="document"
                             transport="http://schemas.xmlsoap.org/soap/http"/>
              <operation name="acceptPO">
                   <soap:operation/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
              </operation>
         </binding>
         <service name="POService">
            <port name="IPurchaseOrderPort" binding="tns:IPurchaseOrderBinding">
              <soap:address location="http://127.0.0.1:8080/docliteralfromjava/jaxrpc"/>
            </port>
         </service>
    </definitions>Thanks

  • Creating a Document type Asynchronous Web Services

    Hi,
    I am trying to create a Document typ Asynchronous webservice, following the request/reply pattern. Can anyone point me to some tutorial which explains this, or explain the way the service implementation has to be.
    I want to know how to do the call back or polling faclity in the service implementation.

    Hello,
    The OracleAS Core Web Service stack currently (10.1.3 and earlier) does not have any API/DevModel, to create an Asynch service.
    However you can still use JAX-RPC/SAAJ APIs to manipulate the WS-Addressing information to faciliate the call back. For the implementation itself you will have to choose what fits you the best, for example using JMS under the cover to process the event that will do the call back.
    It is also true that today, we have lot of customers that use Oracle BPEL to create asynchronous services since it is 100% declarative.
    Regards
    Tugdual Grall

  • Document Security in web service.

    Hi all,
    I am trying to implement document security in the web service. here for that i have create a Ejb and exposed it as web service. now that i have enabled the Document security for the SOAP message. i want to know that which certificate (Keys) are used for the encryption and decryption of the message.
    I saw in help.sap.com that i have to use view WebServiceSecurity in which their is a key XMLEncryption.
    Now i have following issues with it.
    <b>I found no key in the view with name XMLEncryption</b>
    Should i create one or not.
    Now i created one key with that name.
    Now when i am using that key from .Net client to access the web service i get following responce form the web service.
    <b>0002E3562FFE004A00000012000003200003FB109FE6903A : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:CostCenterSecureSignatureVi'; Key name:'SoapRequestWrapper' key value:'getDetail'</b>
    How do i correct above problem?.

    sorry for the post in wrong area.....

  • Support for document and documentwrapped web services

    List,
    Are "document" and "documentwrapped" style web services supported in WSL 8.1 SP1?
    The
    documentation referenced below [1] [2] indicates that these styles are supported,
    but in the
    Unsupported Features section of the Web Services overview [3] states the RPC literal
    style and
    Document encoded style are not supported. It is my understanding that the style
    attribute
    values of the servicegen ant task map to the SOAP encodings as follows:
    RPC -> SOAP RPC
    documentwrapped -> SOAP RPC-literal
    document -> SOAP document-literal
    Is this correct?
    Regards,
    Kent
    [1] http://edocs.bea.com/wls/docs81/webserv/design.html#1038901
    [2] http://edocs.bea.com/wls/docs81/webserv/anttasks.html#1063540
    [3] http://edocs.bea.com/wls/docs81/webserv/overview.html#1074641

    So is it a true statement that if I use the documentwrapped style, I don't have
    the restriction
    of having only one void method while gaining the scalability and performance benefits
    [1] of
    SOAP document-literal encoding? Does the documentwrapped style have any restrictions
    regarding out and in-out parameters? If so, what is the correct way in Java to
    specify a
    parameter as "IN" only?
    Thanks again,
    --Kent
    [1] http://dev2dev.bea.com/products/wlworkshop/articles/Cohen.jsp
    "manoj cheenath" <[email protected]> wrote:
    This is correct. In the doc/lit bare case, a
    method with no parameter will have an empty
    soap envelope. If you look at the schema for
    this operation, it will be an empty complexType.
    So in the style, you can only have one void
    method. WLS tools (servicegen/source2wsdd) do
    not enforce this. Which I think is a bug.
    Hope this helps,
    -manoj
    http://manojc.com
    "manoj cheenath" <[email protected]> wrote in message
    news:[email protected]...
    This is correct. In the doc/lit bare case, a
    method with no parameter will have an empty
    soap envelope. If you look at the schema for
    this operation, it will be an empty complexType.
    So in the style, you can only have one void
    method. WLS tools (servicegen/source2wsdd) do
    not enforce this. Which I think is a bug.
    Hope this helps,
    -manoj
    http://manojc.com
    "Kent Kvarfordt" <[email protected]> wrote in message
    news:[email protected]...
    Bruce,
    How do the restrictions apply to methods that do not have any paramters?
    >>>
    I have attached a copy of the weblogic webservice complex example that I
    modified
    to use
    document style encoding and contains two noarg methods, getVersion
    and
    getAnotherVersion. I also modified the buy and sell methods to take single arguments.
    Following are the results from the test web page for a call to getAnotherVersion.
    <!--REQUEST.................-->
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <env:Header>
    </env:Header>
    <env:Body>
    </env:Body>
    </env:Envelope>
    <!--RESPONSE.................-->
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <env:Header>
    </env:Header>
    <env:Body>
    <n1:buy
    xmlns:n1="http://www.bea.com/examples/Trader">getVersion</n1:buy>
    </env:Body>
    </env:Envelope>
    What am I missing? BTW - I am using Weblogic Server 8.1 SP1.
    Also, how does the weblogic documentwrapped style map to the SOAP encodings
    SOAP RPC, SOAP RPC-literal, and SOAP document-literal? Are the messages encoded
    SOAP doc/lit, but the programming model allows for multiple parameters? Is
    the documentwrapped style specific to weblogic webservices?
    And finally, given Java is a pass by value language, do I need to
    do
    anything
    special to the webservice method signatures to specify the parameters
    as
    "IN"
    parameters?
    Thanks for all the help. From looking at the list traffic, your
    keeping
    busy.
    Regards,
    Kent
    Bruce Stephens <[email protected]> wrote:
    Hi Kent,
    There are restrictions on the doc/lit style of encoding, such as
    the
    methods that implement each operation of the Web Service can have only
    one parameter and the methods that implement each operation cannot use
    out and in-out parameters. The documentwrapped generates a resulting
    Web Service operations that can take any number of parameters, although
    the parameter values will be wrapped into one complex data type in the
    SOAP messages. Manoj has an example of documentwrapped [1].
    We do not support rpc/lit. You might want to review this note by Yasser
    Shohoud, it explains this in exquisite detail [2]
    Regards,
    Bruce
    [1]
    http://manojc.com/?sample14
    [2]
    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebsrv/h
    tml/rpc_literal.asp
    Kent Kvarfordt wrote:
    List,
    Are "document" and "documentwrapped" style web services supported
    in
    WSL 8.1 SP1?
    The
    documentation referenced below [1] [2] indicates that these styles are supported,
    but in the
    Unsupported Features section of the Web Services overview [3]
    states
    the RPC literal
    style and
    Document encoded style are not supported. It is my understanding
    that
    the style
    attribute
    values of the servicegen ant task map to the SOAP encodings as
    follows:
    RPC -> SOAP RPC
    documentwrapped -> SOAP RPC-literal
    document -> SOAP document-literal
    Is this correct?
    Regards,
    Kent
    [1] http://edocs.bea.com/wls/docs81/webserv/design.html#1038901
    [2] http://edocs.bea.com/wls/docs81/webserv/anttasks.html#1063540
    [3] http://edocs.bea.com/wls/docs81/webserv/overview.html#1074641

  • How to make Service Callout to Document (XML) Based Web Service Proxy

    Hi,
    I am receiving a String which is basically XML via MQ.
    I want to do a Web Service Callout using the String based XML to a Proxy Service that is a Document Based Web Service.
    When I make the call using the String as the input parameter, I get many PipeLine Exception errors on the console and it does not reach the Web Service.
    Based on my readings, I believe that I need to place an XMLObject variable in the Service Callout instead of a String.
    How do I do this?
    I've tried the fn-bea:inlinedXML function but that does't seem to work.
    Regards
    Aziz

    Hi Anuj, seems that the problem was an invalid character in the Mq Message when I tried to apply the inlinedXML method to it.
    This is resolved now.
    The solution:
    1) Assign Mq $Body to variable
    2) Use Java Callout to remove special characters fn:string(body)
    3) convert Java Output String to XML using inlinedXML xquery function
    4) Do a replace on the $body node contents using the XML variable
    5) Call Web Service.
    if you dont do the XML conversion, the web service throws a Pipeline Exception.

  • Converting XDP documents into PDF web service

    http://help.adobe.com/en_US/livecycle/9.0/programLC/help/index.htm?content=000526.html
    Why there is an error and how to use this WebService?
    Why this WebService URL is not be connected?
    tks
    pls help me asap

    Hi,
    I think you have startged two discussions for the same question:
    Please check the below mentioend
    http://forums.adobe.com/message/5318601#5318601
    ~Pranav

  • WEB Service Upload File

    Dear all,
    I have some files (50 files).
    if web service have a service flollowing:
    upload (String fileName,byte[] content);
    But if file more than 10M, how to upload to web service.
    Please show me a solution to upload 50 files or more with web service.
    Thank and regards.

    It looks like you just invoke that method with an array of bytes. If you have 50 files, do it 50 times (say, in a loop). You can get the array of bytes with a FileInputStream and a ByteArrayOutputStream, but I'll bet something in the java.nio package can do it more smoothly. (Check the docs; your googling will be as good as mine for that part.)
    The details will depend a lot on the web service itself; for that, talk to the provider of the service.

  • 10gAS 10.1.2 document literal web service

    I need to write a document literal style web service to deploy to 10gAS 10.1.2.
    I don't really know where to start. I references to mostly j2ee 1.4, which doesn't help me.
    Can anyone point me to example code or documentation on this?
    Thanks so much,

    Hello,
    We do not support any tool in 10.1.2 to create Document Literal WS. you can do it by modifying manually the WSDL and the implementation of the service.
    Another solution would be to use Apache Axis deployed in OracleAS 10.1.2, and when moving to 10.1.3/J2EE 1.4 you can use the WSDL to move the implementation to JAX-RPC using a top down generation.
    Regards
    Tugdual Grall

  • Jdeveloper 10.1.2 document literal web service

    I need to write a document literal style web service to deploy to 10gAS 10.1.2.
    I don't really know where to start. I understand that JDeveloper 10.1.2 doesn't have any wizards that do that for me.
    Can anyone point me to example code or documentation on this?
    Thanks so much,

    Or can jdeveloper 10.1.3 create a document/literal web service that can be deployed in 10gAS 10.1.2?

  • Return XML document through Web Service?

    Hello,
    Is it possible to return a XML document from a web service?
    For example, I have a Oracle Report that outputs in XML format, is it possible to return that through a web service?
    Any suggestions or pointers will be most appreciated.
    Nilan

    Hi Nilan,
    You can see a simple example here.,on how to pass and receive XML elements as web service params.
    http://otn.oracle.com/sample_code/tech/java/codesnippet/webservices/docservice/content.html
    A tutorial on Using Web Services with Oracle9i Reports
    http://otn.oracle.com/tech/webservices/htdocs/series/reports/content.html
    Regards
    Elango.

Maybe you are looking for