Generic document services - web

hi folks,
we're in planning/doing to migrate a part of an application (abap / dynpro) to a webdynpro abap application for the frontend part, and in the old one we're using the generic object/document services (cl_gos_manager etc.).
does anyone has some good tips how to handle these attachments? as they need the sapgui for the whole management?
kind regards,
oliver

you can follow the program logic explained in the following weblog. the code sample given in the weblog dosent require SAPGUI unlike cl_gos_manager
<a href="/people/rammanohar.tiwari/blog/2005/10/10/generic-object-services-gos--in-background">Generic object services (GOS) - in Background</a>
Regards
Raja

Similar Messages

How do I create a "document-centric" Web Service?

By document-centric I'm talking about receiving a SOAP message on the server-side, where the initial parsing and security processing (this aspect is very important) is performed but then allowing the developer to access the delivered "payload", i.e. the XML, and perform whatever mapping/processing that is required without automatically mapping to the "standard" auto-generated Java objects.
It is important that the client receives the "full" complex WSDL and can therefore generate their proxy classes with whatever tool (or language) that is appropriate.
On the server side we do not want to create hundreds (if not thousands) of Java Bean clases as we already have the legacy code to map XML to Java. The idea is that JAX-RPC only instantiates the SOAPElements that represent the "raw" message, or, if possible, doesn't instantiate any objects whatsoever.
I've spent many days now trying to find a single well-worked example for this type of Web Service without success - many, many references of the style "..and you can then create a document style web service.." but without the all important "how".
From what I've read a custom type-mapping and/or serializer/deserializer could be the answer but again no good, solid examples are forthcoming.
Another alternative seems to be to create the server side stub-classes using a "dummy" WSDL with the elements set to "anyType" but then distribute the "genuine" WSDL to the clients - we've got a simple example of the kind working but I don't like the idea of "tricking" the system in this way.
I'm working with WASD 5.1, which in theory conforms with JAX-RPC so any ideas offered here should also apply in that environment.
Has ANYONE successfully created a service of this type?
Any help with this issue would be very much appreciated and rewarded (with Duke Dollars of course).
Chris.

Chris,
I too noticed that most vendors take the RPC centric approach. Its because most of the industry examples of how WSs were used were simple enough to implement using RPC and anything more (document literal) would add to the complexity of implementation. This is something that is feared by many developers, especialy the .Net crowd who seem to want everything done through a wizard menu interface and don't care about other WS implementations at all.
This is sort of changing. J2EE 1.4 is WS-I compliant, so when you compile server side ties from WSDL you can specify a document literal option and WS-I compliance. This gives you access to the SOAPElement objects. There's still issues with going between W3C DOM and SOAP elements but that's just API inconvenience, not a show stopper. As the inudustry develops more complex WSs we will see the vendors change their tools to better support this...
Anyway, some more help...
I use the the following wscompile options to build from WSDL for document literal WSs.
wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -import config.xml
wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -gen:server config.xml
My "wrapper" elements look like this...
<xs:element name="AComplexXMLResponse">
     <xs:complexType>
          <xs:sequence>
               <xs:element ref="myNS:MYComplexXMLType"/>
          </xs:sequence>
     </xs:complexType>
</xs:element>
If I do this:
<xs:element name="ASimpleXMLResponse">
     <xs:complexType>
          <xs:sequence>
               <xs:element name="AName" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
</xs:element>
I still get the JAXRPC language bindings to a string, but in my case I don't really care. This may well be different for you.
What I do to manage these elements is to split up the WSDL, WS wrapper element definitions and actual data XML schema definitions into separate documents. This means I have a WSDL which IMPORTS my message schema (this is where I define wrappers for in and out XML) which INCLUDES the actual DATA XML schema that I have.
The WSDL import looks like this:
<types>
     <xs:schema>
          <xs:import namespace="http://schemaURI" schemaLocation="./relativePath/WrapperElementSchema.xsd"/>
     </xs:schema>
</types>
The wrapper element schema has:
<xs:include schemaLocation="./ActualDataSchema.xsd"/>
This way I can easily replace the wrapper documents with just anyType references if something doesn want to play nice. The data schema file and the WSDL stay the same. This minimises the impact on what you have to change in your distribution. This is important as the WSDL is often generated on the fly by your WS environment and so can not be easily changed once you build your WSs, but the schema files it references are easily changed without affecting your code.
Another reason for the wrapper elements was a JWSDP 1.2 issue (I don't know if this has been fixed in 1.3), where if you had the same method parameter signature in a web service (the parameters it took were the same XML types, for instance if you have an add and update methods for the same document input) JWSDP would get confused at runtime. It did not take account of the SOAP action that came along with the request to determine which operation to call. It just took the incoming XML, saw that it was of a certain type and it passed it to the first operation that took this element, which is VERY wrong. By using the wrapper elements, I could give all my input and output elements for each method different names (I used a naming stragegy that appended a 'request' or 'response' string to the method name to form a method parameter element name. This is a pain in the ass, but works and does wonders for interoperability with other WS vendors. Like I said before, I've got this working with JWSDP, BEA and .Net servers and clients.
Hope this helps,
If you think there is a real need for a public HOWTO on this, I could write one with a full step by step guideline that shows where I broke my legs getting this stuff to work. But this would eat into my sleep time :-/ TO JUDGE INTEREST I call on all people interested in a tutorial to respond to this thread (esp people involved with the JWSDP WS tutorial documentation). If I get 5 or more different people responding I will loose some sleep for the good of this community. Otherwise, I will just try to help you when I have time to read the forums.
Kuba

AxisFault seen while invoking document style web service

I am seeing the following stacktrace when I try to invoke a document-style web service.
<partnerRole name="MyWebService1_Role">
<ServiceName>{http://idm.oracle.com/}MyWebService1</ServiceName>
<PortType>{http://idm.oracle.com/}MyWebService1</PortType>
<Address>null</Address>
</partnerRole>
<conversationId>bpel://localhost/default/ProvisioningFromDAS~1.0/4202-BpInv0-BpSeq0.3-3</conversationId>
<properties>{}</properties>
</partnerLink>
<2005-09-06 09:23:37,650> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
What could this mean ?

Hi,
I am getting a similar issue. I created a Document-style/literal webservice and deployed on Weblogic 9.2 . Then I generated client stubs using clientgen. I get the following exception stack trace:
java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SOAPException:
failed to serialize class java.lang.Objectweblogic.xml.schema.binding.SerializationException: type mapping lookup failure on
class=class com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl TypeMapping=TYPEMAPPING SIZE=3
ENTRY 1:
class: java.lang.Object
xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocumentResponse
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@1125127
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@18dfef8
ENTRY 2:
class: java.lang.Object
xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocument
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@15e83f9
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@2a5330
ENTRY 3:
class: java.lang.Object
xsd_type: ['http://www.w3.org/2001/XMLSchema']:xsd:anyType
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@bb7465
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@d6c16c

Attach Documents to Custom Program Using Generic Object Services

Hi There,
         I created Object type ZGOS and used in the custom program, when i try to attach documents it allows and then shows in attachment list.
        But When I use that program next time that document attached is not available.
Is there any separate save Class or FM available for saving the document to the specified custom program.
I am using following code in the program,
CLEAR obj.
SET OBJECT TYPE TO 'ZGOS'
obj-objtype = objtype.
SET OBJECT KEY = REPORT NAME
SELECT SINGLE name
FROM trdir
INTO obj-objkey
WHERE name = sy-repid.
CALL GOS MANAGER WITHOUT CONTAINER (WILL BE DISPLAYED IN THE TOOLBAR)
CREATE OBJECT manager
    EXPORTING
      is_object = obj
    EXCEPTIONS
      OTHERS    = 1.
Thanks in advance.

Check the Naimesh Patel Blog he explain very well
http://help-abap.blogspot.com/2009/02/generic-object-services-gos-toolbar.html

Calling a document style web service using a pl/sql wrapper method

Just wanted to find out if anybody has a working example of invoking a document style web service from Oracle 10g database on a Unix environment.
We have java test class that invokes the web service, and we are trying to use a pl/sql wrapper to invoke a Java Web Service client. So far, we are encountering an End of File Communication error from Oracle which essentially terminates the session with the database.
On the Oracle application server side we are able to see a successful HTTP request made to the application server via server log, which is hosting the web service, since we are registering HTTP 200 success codes. However, we do not see any other errors from the application in the server logs. Most likely since the client side fails, before actually getting a chance to invoke the web service. This has been verified by commenting the client code leaving the print statements. The first call to the Service Factory method (XFire) to look up the service is where the PL/SQL procedure fails with an End of File communication error.

Remove the when others section and see the actual error and post that.
http://tkyte.blogspot.com/2008/06/when-others-then-null-redux.html
http://tkyte.blogspot.com/2007/03/dreaded-others-then-null-strikes-again.html

Document style web service receive and send org.w3c.Element

All,
I have created a simple Document-oriented web service and deployed to a standalone OC4J container using the following code:
********************* Interface ***********************
import org.w3c.dom.*;
interface PrimeNumberService
//method to check the primality of the number passed in Element variable
public Element isPrime(Element e) ;
******************** Implementation *******************
@version 1.0
Development Environment : Oracle9i JDeveloper
Name of the File : PrimeNumberServiceImpl.java
Creation/Modification History :
13-Apr-2002 Created
Overview:
This class file defines methods to implement PrimeNumberWebService.
The method isPrime() is exposed by the Web Service.
import org.w3c.dom.*;
import oracle.xml.parser.v2.*;
import java.io.*;
public class PrimeNumberServiceImpl implements PrimeNumberService
public PrimeNumberServiceImpl()
* This method is exposed by the Web Service to check if the number is
* prime. It extracts the number for input element and checks if it is
* prime or not and return the output in the XML Element.
* The input element is of the form <number>23</number>
public Element isPrime(Element e)
// define an XML Element that will be returned to the client
Element processedEl=null;
try{
// get the first clild of input element
Node enode = e.getFirstChild();
//get the value of input element and parse it
String value= enode.getNodeValue();
double number = Double.parseDouble(value);
String answer=null;
// check if the input number is prime
answer = checkPrime(number);
// create element from the answer
processedEl =createElement(answer);
}catch(Exception ex){
ex.printStackTrace();
return null;
// return output to client
return processedEl;
* This method creates an XML element from the input string values and return it
* The Element is of the form <answer>value</answer>
private Element createElement(String value){
// create a Document object
Document xmldoc = new XMLDocument();
// create an element with name "answer"
Element e1 = xmldoc.createElement("answer");
// append the element to document object
xmldoc.appendChild(e1);
// create a Text object from input values and append it to above element
Text t = xmldoc.createTextNode(value);
e1.appendChild(t);
return (Element)xmldoc.getFirstChild();
* This method check if the input number is prime or not
private String checkPrime(double num){
//For a prime number mod(power(2,number),number) is equal to 2
if ( Math.IEEEremainder( Math.pow(2.0,num) ,num)==2){
System.out.println ("the number is: " + num);
return "The number " + num + " is prime";}
else{
System.out.println ("the number is: " + num);
return "The number " + num + " is not prime";}
************************ Generated WSDL ***************
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="PrimeNumberService"
targetNamespace="http://tempuri.org/PrimeNumberService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://tempuri.org/PrimeNumberService.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" >
<documentation>
WSDL for Service: PrimeNumberService, generated by Oracle WSDL toolkit (version: 1.1)
</documentation>
<types>
<schema targetNamespace="http://tempuri.org/PrimeNumberService.xsd" xmlns:tns="http://tempuri.org/PrimeNumberService.xsd" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
</types>
<message name="isPrimeOutput">
<part name="return" element="xsd:any"/>
</message>
<message name="isPrimeInput">
<part name="param0" element="xsd:any"/>
</message>
<portType name="PrimeNumberServicePortType">
<operation name="isPrime">
<input message="tns:isPrimeInput"/>
<output message="tns:isPrimeOutput"/>
</operation>
</portType>
<binding name="PrimeNumberServiceBinding" type="tns:PrimeNumberServicePortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="isPrime">
<soap:operation soapAction="urn:PrimeNumberService/isPrime"/>
<input>
<soap:body use="literal" namespace="urn:PrimeNumberService"/>
</input>
<output>
<soap:body use="literal" namespace="urn:PrimeNumberService"/>
</output>
</operation>
</binding>
<service name="PrimeNumberService">
<port name="PrimeNumberServicePort" binding="tns:PrimeNumberServiceBinding">
<soap:address location="http://hp-xeon-01:9799/primenumberws/primenumberService"/>
</port>
</service>
</definitions>
I get the following error when trying to deploy:
Error:
[Error ORABPEL-10902]: compilation failed
[Description]: XML parsing failed because "undefined part element.
In WSDL at "http://hp-xeon-01:9799/primenumberws/primenumberService?WSDL", message part element "{http://www.w3.org/2001/XMLSchema}any" is not defined in any of the schemas.
Please make sure the spelling of the element QName is correct and the WSDL import is complete.
[Potential fix]: n/a.
Please let me know what I'm doing wrong.
Regards,
Jeff

Here is the error code that I'm getting at the invoke:
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
<part name="code">
<code>Client</code>
</part>
<part name="summary">
<summary>parsing error: oracle.xml.parser.v2.XMLParseException: Expected name instead of /.</summary>
</part>
<part name="detail">
<stackTrace xmlns="http://xml.apache.org/axis/">parsing error: oracle.xml.parser.v2.XMLParseException: Expected name instead of /. at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221) at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128) at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:226) at org.collaxa.thirdparty.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645) at org.collaxa.thirdparty.apache.axis.Message.getSOAPEnvelope(Message.java:424) at org.collaxa.thirdparty.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.collaxa.thirdparty.apache.axis.client.AxisClient.invoke(AxisClient.java:173) at org.collaxa.thirdparty.apache.axis.client.Call.invokeEngine(Call.java:2725) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:2708) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:1738) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeAXISMessaging(WSIFOperation_ApacheAxis.java:1902) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1464) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1029) at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:455) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:359) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:161) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:605) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317) at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3501) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1906) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:101) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:186) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5604) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1301) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:117) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:146) at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.syncCreateAndInvoke(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:483) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:489) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:425) at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:132) at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:82) at IDeliveryBean_StatelessSessionBeanWrapper22.request(IDeliveryBean_StatelessSessionBeanWrapper22.java:479) at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:101) at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:65) at ngDoInitiate.jspService(_ngDoInitiate.java:220) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121) at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267) at displayProcess.jspService(_displayProcess.java:303) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220) at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:138) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192) at java.lang.Thread.run(Thread.java:534)</stackTrace>
</part>
</remoteFault>

Generic Object Services using Web Dynpro

I am using Web Dynpro for ABAP and would like to access Generic Object Services (GOS) to view attachments to an SAP Business Object. Using the cl_gos* classes does not work when running WebDynpro as it uses the controls framework.
How can I access the functionality of GOS from a Web Dynpro application?
Regards,
Bob

Hi,
I assume that you wantted to have the attachements in a mail.
Please check out the Adobe Forms(ie PDF attachements) and Office Control UI elements in WDA.
Regards
Lekha

How to attach document using Generic Object Service

Hi all,
How can i create attachment to the parked invoice using Generic Object services? i want function modules which are used to do it.
Actually I want to do this from the business object method. I am having word document as one of the workitem step. once i get this document I need to attach this document to the parked invoice so that users can see that document by view object list.
Its urgent.
thanks.

Hello,
Check your configuration of document type assignement to required business document - object type, Archivelink table, content repository in OAC3 transaction.
Goto respective business document > Click on GOS > Create > Store business document - Here you can see defined document type with desctiption. Double click on this the assign your document to this business document. Save it.
This will help in attaching the document to your required business document.
To verify you can check the archivelink table or by transaction OAAD.
Hope this will help you.
-Thanks,
Ajay

Attach Documents using Generic Object Services

With reference to Manual Bassani's SDN Contribution of code examples on how to attach documents using Generic Object Services - we have found that since implementing ECC 6 the following code no longer works (at the end of page 9):
CALL CREATE ATTACHMENT SERVICE FROM TOOLBAR
WHEN 'ATTACH'.
CALL METHOD MANAGER->START_SERVICE_DIRECT
EXPORTING
IP_SERVICE = 'CREATE_ATTA'
IS_OBJECT = OBJ
EXCEPTIONS
NO_OBJECT = 1
OBJECT_INVALID = 2
EXECUTION_FAILED = 3
OTHERS = 4.
It is necessary to use IP_SERVICE = 'PCATTA_CREA' to get this to function correctly.
The original document can be found at [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0e6b0d95-0a01-0010-4696-ca0a48de5fb3]

Check the Naimesh Patel Blog he explain very well
http://help-abap.blogspot.com/2009/02/generic-object-services-gos-toolbar.html

Connect a Word document instance to Generic Object Services/BDS

Hello all,
how can I manage to get a word document created via the Doc_template step to a certain Business Object (like Business Partner). I tried to trace that but I got lost in generations of codes like archivelink, sap office, knowledge provider etc.) I guess it should not be that difficult as I have the key of the word doc instance and the key of the business partner instance. What I want at last is to have that word document linked via attachments/linked objects or something similar....
Kindest regards from Germany,
Markus

Markus,
Welcome to the forum!
I have done this sometime ago at a past client site and will see if I can find the code.
If I remember correctly, this involves converting the attachment to an SOFM object (using method CREATESOFM of BO WF_DOC) and then using function module BINARY_RELATION_CREATE to attach it to the BO. The links below will give you more info. Also Google for BINARY_RELATION_CREATE which should give you more links.
Re: Link Workflow Document to BKPF object
<a href="/people/rammanohar.tiwari/blog/2006/03/25/generic-object-services-gos--in-background--part-ii">Generic object services (GOS) - in Background - Part II</a>
http://mailman.mit.edu/pipermail/sap-wug/2005-September/019547.html
Cheers,
Ramki Maley

Document Literal Web Service Stub Error

I am using jdeveloper 9.0.3 (necessary because we are doing OAF) and have created a Document Literal Web Service Stub. The stub runs perfectly in Jdeveloper, but when I move it to our 9iAS server (1.0.2.2.2), I get the error that it can not find the class \oracle\jdeveloper\webservices\runtime\WrappedDocLiteralStub.
On my local machine this file is located in jdev-rt.jar, which is in /jdevbin/jdev/lib. Is there a special way to package the web service so that the jar file is included? Or is there a patch I need to apply to the apps server?
Any help would be much appreciated.

I am using jdeveloper 9.0.3 (necessary because we are doing OAF) and have created a Document Literal Web Service Stub. The stub runs perfectly in Jdeveloper, but when I move it to our 9iAS server (1.0.2.2.2), I get the error that it can not find the class \oracle\jdeveloper\webservices\runtime\WrappedDocLiteralStub.
On my local machine this file is located in jdev-rt.jar, which is in /jdevbin/jdev/lib. Is there a special way to package the web service so that the jar file is included? Or is there a patch I need to apply to the apps server?
Any help would be much appreciated.

Document/literal web service with WSDL

Hi
I is so hard to get an easily written example of how to do a Document/literal web service in java, to generate a WSDL descripbing it and then deploying it on Apache.
I first belived that I should use JAXM. But I think it is just SOAP and there is no way to generate a WSDL file for the JAXM service, or??
It seems that u can to document/literal style using JAX-RPC, but this is VERY strange since RPC style is the direct opposite of Document style.
well, well
I would be very greatful for information here.
regards
/Rassol

JWSDP 1.2 includes the WS-I sample application in JWSDP_HOME/wsi-sampleapp. Several components of
this application use document-literal operations. The architecture of the application is described
here http://ws-i.org/SampleApplications/SupplyChainManagement/2003-04/SCMArchitecture1.0-BdAD.pdf
The WSDL for the services is availabe from URLs in the document.
As you say, the trick is generating the WSDL for a new service. You have two options: 1. Modify
existing WSDL yourself. This might be fairly easy, since the only major changes will be in the
schema. Then use a tool to generate Java source code from the WSDL. 2. Use a tool to generate WSDL
from source files.
I prefer option 1 myself, since that gives me total control over the schema. It allows me to
serialize certain parts of the SOAP message as body elements, others as attributes, and others as
header elements. Then I use the Apache Axis tool WSDL2Java with the "-s" option to generate skeleton
service files. One big advantage to this approach is that WSDL2Java generates JavaBean class for the
types in the WSDL schema, so I don't need to build the SOAP message with SAAJ. A service client
generates stubs and calls the service exactly as it would for an rpc/encoded service.
wscompile also generates service files from WSDL if you give the "-gen:server" option, but I've only
used Axis for my services.
Here's a sample WSDL for a document/literal service you can modify as you need. I checked it with
the WS-I testing tools to be sure it conforms to the WS-I Basic Profile 1.0a (available at www.ws-
i.org). Notice that the processPo operation is a request-response type operation, even though it has
a document/literal style. This follows the recommendations in the Basic Profile.
Cheers,
Mike
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://www.ltree.com/wsdl/po" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:impl="http://www.ltree.com/wsdl/po" xmlns:intf="http://www.ltree.com/wsdl/po" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="http://www.ltree.com/types/po" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          xmlns:tns1="http://www.ltree.com/types/po"
          xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
          targetNamespace="http://www.ltree.com/types/po"
          elementFormDefault="qualified">
     <xsd:import namespace="http://schemas.xmlsoap.org/soap/envelope/"
                 location="http://schemas.xmlsoap.org/soap/envelope/"/>
     <xsd:complexType name="LineItem">
         <xsd:sequence>
             <xsd:element name="itemId" type="xsd:string"/>
             <xsd:element name="quantity" type="xsd:int"/>
         </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="PurchaseOrder">
         <xsd:sequence>
             <xsd:element name="customerName" type="xsd:string"/>
             <xsd:element name="lineItem" type="tns1:LineItem"
                      minOccurs="1" maxOccurs="unbounded" />
         </xsd:sequence>
         <xsd:attribute name="purchaseOrderId" type="xsd:string" use="required"/>
     </xsd:complexType>
     <xsd:element name="purchaseOrder" nillable="true" type="tns1:PurchaseOrder"/>
     <xsd:complexType name="CallbackEndpoint">
         <xsd:attribute name="location" type="xsd:anyURI" use="required"/>
     </xsd:complexType>
     <xsd:element name="callbackEndpoint" nillable="false" type="tns1:CallbackEndpoint"/>
     <xsd:complexType name="PurchaseOrderAck">
         <xsd:sequence>
             <xsd:element name="poId" type="xsd:string"/>
         </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="purchaseOrderAck" nillable="true" type="tns1:PurchaseOrderAck"/>
     <xsd:complexType name="InvalidCustomerNameException">
      <xsd:sequence>
       <xsd:element name="message" nillable="true" type="xsd:string"/>
       <xsd:element name="customerName" type="xsd:string"/>
      </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="invalidCustomerNameException" nillable="true"
                  type="tns1:InvalidCustomerNameException"/>
</xsd:schema>
</wsdl:types>
   <wsdl:message name="processPoRequest">
      <wsdl:part name="callbackEndpoint" element="tns1:callbackEndpoint"/>
      <wsdl:part name="purchaseOrder" element="tns1:purchaseOrder"/>
   </wsdl:message>
   <wsdl:message name="processPoResponse">
      <wsdl:part name="purchaseOrderAck" element="tns1:purchaseOrderAck"/>
   </wsdl:message>
   <wsdl:message name="invalidCustomerNameException">
      <wsdl:part name="fault" element="tns1:invalidCustomerNameException"/>
   </wsdl:message>
   <wsdl:portType name="PurchaseOrderHandler">
      <wsdl:operation name="processPo">
         <wsdl:input message="impl:processPoRequest" name="processPoRequest"/>
         <wsdl:output message="impl:processPoResponse" name="processPoResponse"/>
         <wsdl:fault message="impl:invalidCustomerNameException" name="invalidCustomerNameException"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="PurchaseOrderHandlerPortSoapBinding" type="impl:PurchaseOrderHandler">
      <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="processPo">
         <wsdlsoap:operation soapAction="" style="document"/>
         <wsdl:input name="processPoRequest">
            <wsdlsoap:header message="impl:processPoRequest" part="callbackEndpoint" use="literal"/>
            <wsdlsoap:body parts="purchaseOrder" use="literal"/>
         </wsdl:input>
         <wsdl:output name="processPoResponse">
            <wsdlsoap:body use="literal"/>
         </wsdl:output>
         <wsdl:fault name="invalidCustomerNameException">
            <wsdlsoap:fault name="invalidCustomerNameException" use="literal"/>
         </wsdl:fault>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="PurchaseOrderHandlerService">
      <wsdl:port binding="impl:PurchaseOrderHandlerPortSoapBinding" name="PurchaseOrderHandlerPort">
         <wsdlsoap:address location="http://localhost:8080/po/services/PurchaseOrderHandlerService"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

Leverage Inheritance Benefits in 'document/literal' Web Services

Greetings,
I have developed a document/literal web service that receives an object I created, say ParentObject.
I developed it under the assumption that once I create a web service for ParentObject, I'll be able to use the same web service for ChildObject as well, which is a sub-class from ParentObject. Unfortunately, it did not work.
Please correct me if I'm wrong; is it really not possible to leverage inheritance capabilities web services? And if it's not possible, what workaround(s) do you use in such scenarios when you don't want to create a new web service for each object type despite that they all have the same logic?
Your thoughts are highly appreciated.
Thanks in advance,
Ahmed Motaz

Jason, have you made any progress with CF7 and WS Security?
It doesn't seem like enough information on this is available. Is it
even possible? and how?

Problem Generating Document/Literal Web Service

Hi folks..
I am currently using JDeveloper 10.1.3 (Preview Edition) and I am having trouble getting the Create Java Web Service wizard to work correctly when generating a document/literal web service. After going through the wizard selecting the appropriate settings to generate a document/literal web service from my implementation I get the following error during generation.
oracle.j2ee.ws.common.tools.api.SeiValidationException
oracle.j2ee.ws.common.processor.modeler.rmi.RmiModeler.modelPort(RmiModeler.java:587)
oracle.j2ee.ws.common.processor.modeler.rmi.RmiModeler.buildModel(RmiModeler.java:455)
oracle.j2ee.ws.common.processor.config.ModelInfo.buildModel(ModelInfo.java:160)
oracle.j2ee.ws.common.processor.Processor.runModeler(Processor.java:76)
oracle.j2ee.ws.common.tools.wscompile.CompileTool.run(CompileTool.java:510)
oracle.j2ee.ws.tools.wsa.JavaToWsdlTool.createWSDL(JavaToWsdlTool.java:234)
oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:313)
oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:205)
oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:131)
oracle.j2ee.ws.tools.wsa.Util.processAnnotations(Util.java:77)
oracle.jdeveloper.webservices.model.java.JavaGenerator.generateWSDLFromAnnotations(JavaGenerator.java:1188)
oracle.jdeveloper.webservices.model.java.JavaGenerator.doGeneration(JavaGenerator.java:362)
oracle.jdeveloper.webservices.model.Generator.generateImpl(Generator.java:330)
oracle.jdeveloper.webservices.model.Generator.access$1000071(Generator.java:100)
oracle.jdeveloper.webservices.model.Generator$1$ReturningRunnable.run(Generator.java:250)
oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:344)
oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:526)
java.lang.Thread.run(Thread.java:534)
When I googled this error I actually get a hit for a thread here on this board, that looks VERY promising... but when I attempt to access it I get a message "Duscussion Forms Error" and I cant access it. (Very frustrating believe me.. :-)
Any help that you can give would be appreciated...
Thanks
Dave

Hi Dave,
One reason to have the SeiValidationException is when you do not follow the java bean convention for getter/setter or some of the public methods you want to expose are not throwing the right execption.
Using the command line utility genProxy [or the ant task] with the debug flag may give you some informations about the WSDL constructs WSA do not understand. Look at the following how-to to get started:
http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-ws-bottomup/doc/how-to-ws-bottomup.html
If this does not help, can you share your WSDL with us ?
Thanks,
Eric

Trouble Communicating with Document-Style Web Service

I have a flash app that currently communicates with a
RPC-style web service. I changed the web service to be
document-style, and the flash app no longer sends valid requests. I
was under the impression that one could simple swtich styles, and
flash would play along. Apparently, this is not the case. Does
anyone have an insight in this area?

Clarified with Partick Calahan, who is maintaining this tool.
Currently, doc style is not handled by this tool. I guess it will be
supported in the future.
Thanks.
"Karthik V" <[email protected]> wrote in message
news:[email protected]..
I'm using WebLogic Webservice Explorer v.02 (WEX).
I'm able to test rpc style web services without any problem.
But whenever I try to open a document style web service WSDL, I get the
following exception.
I would appreciate if you have any suggestions for the to over come this
issue.
java.lang.IllegalArgumentException at
weblogic.webservice.tools.wex.MessagePanel.<init>(MessagePanel.java:33)at
>
weblogic.webservice.tools.wex.ServicePanel.operationChanged(ServicePanel.jav
a:153) at
weblogic.webservice.tools.wex.ServicePanel.portChanged(ServicePanel.java:133
) at
weblogic.webservice.tools.wex.ServicePanel.serviceChanged(ServicePanel.java:
121) at
weblogic.webservice.tools.wex.ServicePanel.<init>(ServicePanel.java:69)at
>
weblogic.webservice.tools.wex.tasks.FetchWsdlTask.perform(FetchWsdlTask.java
:45) at
weblogic.webservice.tools.wex.tasks.TaskQueue.run(TaskQueue.java:47) at
java.lang.Thread.run(Unknown Source)

Generic document services - web

Similar Messages

Maybe you are looking for