Documentation for doc literal processing

I'm struggling with an existing that uses doc literal services, but I can't get it to work in oc4j 10g preview.
I've tried the doc_lit demo that Oracle provides -- loading the WSDL from the original source (ws-i.org) works fine, but trying to load it locally produces errors. The first error is a complaint that the WSDL doesn't define a service, so I added the service as suggested in another thread. However, at that point although the first pass through wsa generates things, it does not generate the correct type classes, so the second pass (update-impl) through wsa fails.
I'm confused as to why the WSDL processing is different depending on whether it's loaded from ws-i.org or the filesystem. And I'm confused about how the WSDL should properly look to generate the type classes.
Any pointers to documentation I may have missed, or any other clues or help would be very much appreciated.

I'm looking for the same thing -
Were you able to location any documentation?
I've been trying to get my hands on the documentation
for the C4. Sun's doc site does not have this product
listed at all. The product documentation link
(http://docs.sun.com/app/docs/prod/1878#hic) just
returns " The requested item could not be found."
I've even tried opening up a case with Sun. First,
the support people had no idea what the C4 was. After
3 days and 3 support engineers, I finally found one
who understood what this product was, but I was then
told that getting the documentation would be on a
time and materials basis. I'd rather not have to pay
$400+ for documentation that should be on their
website, just like all their other equipment. I'm
currently using the Quantum PX502 documentation as a
reference, but I'd really like to see Sun specific
documentation.
Any ideas?
Thanks.I'm looking for the same thing -
Were you able to location any documentation?

Similar Messages

Problem with DII client for Doc/Literal with non built-in type in WL8.1 Sp2

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<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:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<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:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<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:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<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:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

Any documentation for sequence of process

Hello all,
I hope this is easy for every one.
I need help to find out how can I find out what function modules/methods/programs will execute when I press Save ICON in CIC0.
If that is in configuration how could I locate.
Thanks in Advance.
Raman

Hi Raman,
The easiest way might be going into debuging mode. just start debugging mode (/h) and click on save. This will take you into the code where save is getting called.
If tihs helps, please credit forum.
Regards
Pankaj

OutPut as a PDF doc for Output Determination process of a PO

Hi
Can I get the OutPut as a PDF document for OutPut Determination process of a PO for a Vendor.
My schema should produce a PDF file and get transmitted to that Vendor as soon i save my PO.
Also can i get any SAP document on this.
Pls help me. Swifty reply me.
cheers
MaruthiRam

Hi,
PO can be sent to using Outlook email or the Internal send within SAP.
Message via E-Mail
Use
You can send purchasing documents to a vendor by e-mail.
You can also send memos to an internal user from within the purchasing document, in which case the recipient can directly access the relevant document when processing the e-mail (executable mail).
Prerequisites
External Transmission
Make the necessary Customizing settings
The SAP system is configured for the transmission of external mails.
The message determination facility has been set up in Customizing for Purchasing.
You have defined a communication strategy in Customizing under Messages Output Control -> Message Types -> Define Message Types for <Purchasing Document> -> Maintain Message Types for <Purchasing Document> on the Default Values tab page, so that if no e-mail address can be found, for example, the system sends a fax.
The following information is necessary:
1.Data
2.Value
3.Comment
Message type:
Communication strategy
E.g. NEU
Choose a communication strategy or create a new one. Via the input help, you can branch to the maintenance function for communication strategies. Choose in the following window.
Enter the necessary data on the Default Values tab page on the detail screen for the message type ().
Processing routines
Medium
Program
FORM routine
5 (external transmission)
SAPF06P (e.g. for PO)
ENTRY_NEU
The entries are identical to those of the print output.
Partner roles
E.g. external transmission/LF
Maintain master data
Message records must have been created through master data maintenance (Purchasing menu). (See Creating Message Records)
Enter the necessary data u2013 for example, role LF (vendor), medium 5 (external transmission) and time spot 4 (send immediately upon saving).
SAP recommends that you work with time spot 4, so that the e-mails generated are sent immediately.
If you work with processing time spot 1 (send via periodically scheduled job), you must schedule the program RSNAST00 periodically for message output, so that messages are generated and e-mails sent.
An e-mail address is stored in the vendor master record.
An e-mail address is stored in the user master record.
Please note that you must also maintain an e-mail address for user IDs with which batch-jobs are carried out.
Internal Transmission
Make the necessary Customizing settings:
You have maintained the Customizing settings for Purchasing under Messages, Output Control -> Message Types ->Define Message Types for <Purchasing Document> -> Maintain Message Types for <Purchasing Document>.
The following information is necessary:
1.Data
2.Value
3.Comment
Message type:
Time-spot
Transmission medium (output medium)
Partner role
E.g. MAIL
E.g. 4 (send immediately upon saving)
7 (SAPoffice)
MP (mail partner)
Enter the necessary data on the Default Values tab page on the detail screen for the message type ().
Mail title and texts
E.g. mail from purchase order
Processing routines
Medium
Program
FORM routine
7 (SAPoffice)
RSNASTSO
SAPOFFICE_AUFRUF
Partner roles
E.g. SAPoffice/MP
SAPoffice/LF
Maintain master data
Message records must have been created for the message type MAIL through master data maintenance (Purchasing menu). (See Creating Message Records)
For more information on the internal and external transmission of e-mails, refer to the Basis documentation under Business Workplace (BC-SRV-GBT).
Further information on external transmission is available in the Basis documentation under SAPconnect and in the section External Sending in the SAP System.
Activities
External Transmission
If you have specified the processing time-spot 4 (send immediately upon saving), the system will immediately generate and transmit a message when you save the purchasing document.
If you have specified the processing time-spot 1 (send via periodically scheduled job), you must initiate the output of e-mails manually.
Result
You see the documents generated in the SAP system under Office ->Work center -> Outbox -> Documents.
Internal Transmission
On the message screen of the Purchasing application (e.g. in the purchase order), enter the message type, the medium (SAPoffice) and the role (MP = mail partner).
Choose Means of communication and enter your text on the following screen (<Purchasing document>: Send with note). Enter the useru2019s first and last names, for example, in the Recipient field.
Executable mail
If you wish to insert a transaction (because you want the recipient to view a purchase order, for example), choose Goto -> Execution parameters. Enter the necessary data, such as execution type (T = transaction), execution element (ME22N = Change Purchase Order), execution system, and the SET/GET parameters (BES for purchase order).
Result
If you have specified send immediately as the processing time-spot, the user will immediately receive a message or document when the purchase order is saved.
The user can view the message sent to him or her via Office -> Work center -> Inbox.
If the document in your inbox is an executable mail, you can click the right-hand mouse button and directly access the relevant purchase order, for example, via the menu thus displayed.
Hope it works...
Regards,
Kiran

Documentation for the As-Is and To-Be process.

Can any one send some material regarding how to write documentation for the AS-IS and TO-BE business process for the business blue print.
My requirement is to <u>automate the process which are receiving goods from the gate entry to GR level and finally posting goods issue</u> all should done automatically .
Now we are gathering information from the client according to their business process.
Our client is digital meter product based company.
Its an urgent thanks in advance.

Probably the best thing to do is go to your boss/team lead/project manager/client contact and ask them what documentation they want you to produce and what should go in it. No-one here can guess at that.
Gareth.

Making the doc.bat to create the documentation for classes & Tests

Hello
I have created a file called "documentation.bat" to created the documentation in html for my src and test classes.
I havent got any problem to do it for my classes, but i also want to do it for my Tests and i dont know how to put it in the same .bat file
To create documentation for the classes i use this:
set CLASSPATH=.\sources;.\lib\cacheLRU-lib-1.1.jar;.\tests
javadoc -d .\doc -linkoffline http://java.sun.com/j2se/1.5.0/doc/api .\doc -sourcepath sources -author -subpackages es.ubu.lsi.cacheLRU.controladorTo create documentation for the Tests classes i was using this, that show my decents for warnings :S :
set CLASSPATH=.\sources;.\lib\cacheLRU-lib-1.1.jar;.\tests
javadoc -d .\doc -linkoffline http://java.sun.com/j2se/1.5.0/doc/api .\doc -sourcepath sources;tests -author -subpackages es.ubu.lsi.cacheLRU.controlador es.ubu.lsi.cacheLRU.testsWhats the problem in the second code?
How to put two folders and two packages to do it?
Lots of thanks, sry for my language :S

Try generating just to Word and then creating the PDF from
there. There is a known problem which affects some users but not
others. Cause not known.

Experience Using CE for publishing BPMN Processes for documentation?

Dear all,
has anybody some experience in using the Netweaver CE for publishing BPMN Processes only for documentation purpose? One part of our process pools contains only processes, that will not be used for process automation within CE Applications. We want to do do it this way, because theese processes describes our business on a higher level.

You can write a Java program using the BOE SDK that does that. HEre are some examples:
http://wiki.sdn.sap.com/wiki/display/BOBJ/JavaBusinessObjectsEnterpriseSDKSamples
Regards,
Stratos

Using doc/literal wrapped?

I'm working on a J2EE 1.4 web application that is required to be portable accross as many different app servers as possible. We're adding web services to the applciation, so am looking for a portable approach.
I decided upon using J2EE 1.4 (so JAX-RPC 1.1), doc/literal wrapped, and using JWSDP 1.6 to generate interface types from the WSDL, in "wsi,unwrap" mode. This works fine on JBoss 4.0.4. However when running the same code on WebLogic 9.2, the SOAP requests are invalid because WebLogic generates the wrapper tags twice. For example:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header/>
<soapenv:Body>
<b><m:Search xmlns:m="http://www.abm-uk.com/abmpegasus/v4.0/gms">
<m:Search></b>
<Item>
<m:BarCode>1234</m:BarCode>
</Item>
<Item>
<m:BarCode>9876</m:BarCode>
</Item>
<Item>
<DPCI>
<m:DepartmentNumber>010</m:DepartmentNumber>
<m:ClassNumber>11</m:ClassNumber>
<m:ItemNumber>4444</m:ItemNumber>
</DPCI>
</Item>
<b></m:Search>
</m:Search></b>
</soapenv:Body>
</soapenv:Envelope>
Is this a known issue with WebLogic? Or does WebLogic perhaps not support the JAX-RPC 1.1 "unwrap" mode?

As I've investigated the issue some more, I've found that the real issue is receiving an attachment on the SOAP response from the BPEL process. Using a Doc/Lit-Wrapped WSDL, I can receive a request with an attachment, and add it to outgoing requests successfully. But when I do a straight copy from the request message to the response message (Echo Service), the response contains the correct "href" attribute but there is no attachment, and moreover, no MIME multipart message is returned.
NOTE: I was successful in using an RPC/Literal WSDL to accomplish the successful echo of the attachment.
Also, when looking in the OPMN logs, I see the following line for the RPC-based BPEL process, but not for the Doc/Lit:
<2009-11-23 13:43:35,684> <DEBUG> <attachment.collaxa.cube.engine> <CXBinaryDataHandler::createDataSource> for binary location=uuid:aaa091d17e1b5545:67c00c53:1252285bf07:-7fc2
<2009-11-23 13:43:35,716> <DEBUG> <attachment.collaxa.cube.engine.data> <ConnectionFactory::getConnection> GOT CONNECTION 1 Autocommit = false
<2009-11-23 13:43:35,716> <DEBUG> <attachment.collaxa.cube.engine> <CXBinaryDataHandler::createDataSource> for binary location=uuid:aaa091d17e1b5545:67c00c53:1252285bf07:-7fc1
and the "binary location" value corresponds with the "href" attribute seen in the BPEL audit logs.

Documentation for PostProcessingPluginHelper

Does documentation for the PostProcessingPluginHelper class exist? I have not been able to find it in the Java SDK docs. I'm trying to determine the arguments to the PostProcessingPluginHelper.createInfoObject(...) method. My objective is to add a dynamically generated Word document to the artifacts to be delivered by the publication.
Thanks!
-m

The question about the documentation still stands, but as far as adding word documents, there is a comparable example in the developer guide.
At the bottom of the "handle" method in the post processing plugin, use the following code to add a word doc:
File addedFile = new File(tmpDir + "\\MyFile.doc");
IWord addedFileInfoObject =
(IWord)PostProcessingPluginHelper.createInfoObject(context, CeProgID.WORD, "application/msword", null, null);
addedFileInfoObject.getFiles().addFile(addedFile);
// return the list of info object artifacts that should be delivered by the publication
IInfoObjects newInfoObjects = context.getInfoStore().newInfoObjectCollection();
newInfoObjects.add(addedFileInfoObject);
return newInfoObjects;

Network Protocol Documentation for ARD or ANA?

Is anyone aware of any documentation on the network protocols used by ARD? I have plenty of docs on RFB/VNC, but Apple is doing something more with ARD than standard RFB. It looks like they are still making some use of Apple Network Assistant (UDP port 3283) protocol and clearly performing other tasks that aren't part of the RFB standards. Could anyone point to any documentation for this?
I'm trying to develop some utilities that will make working with ARD in a multi-thousand Mac environment a bit more tolerable. I'm not very interested in remote desktop control; this is about asset management and patch management. Once you have more than a couple-thousand Macs in ARD, it seems to slow to a crawl.
For example, we have a very large number of large (21-bit) subnets, and the ARD scanner takes forever to scan them. I've written a small utility that will scan a subnet in seconds, and provide a text file containing only active computers that are Macs. This output loads into ARD much, much faster. I did this after discovering that a UDP packet sent to port 3283 will cause a Mac to respond with its name, ethernet address, etc. I'm trying to figure out what else is in that response packet, and what more I can do. I'd rather have an ARD API that allows me to add/remove computers into ARD (anyone?) but that appears to be the one area that Apple forgot. I'm still new to the Mac world, so I could have missed any number of things. Pointers would be welcome.
Thanks!

Ok, I've figured out why I dropped the AppleScript route. The ARD dictionary command to "add" a computer to a list appears to require a computer descriptor for a machine that is already in ARD. So, doesn't look like it can actually add a computer to ARD via that route.
Regarding import from file:
I've used the scanner to scan IP addresses from a text file that is the output from my utility. While manual, this does work. I then have to "add" the computers to the "All Computer" list manually, specifying the credentials. This has been my process to date. Better than nothing, but very manually intensive. It also appears that the scanner is limited to scanning only the first 4096 addresses from a text file, we have about 20x that number of Macs.
I have not tried writing a plist from my utility and importing directly (bypassing the scanner). I'll give that a shot. Assuming this works, it might take one manual step out of the process. Still not sure if I can automate list import any further.
I'd still like to find some protocol-level documentation so that I can improve the precision of my scanner utility. I'd like to verify my credentials on each system discovered, and verify that the ARD client-upgrade is an authorized task before going to the trouble of adding them into ARD only to find these problems later. So far, a significant percentage of my Macs are still running ARD 2.x and 1.x so the upgrade process is important. On a related note, it doesn't look like the "Upgrade Client" task can be relegated to the local task server. Wonder why...
Thanks again.

Does anybody know something about developer's documentation for BPM 11.1.1.7 Case Management ?

I found only "Javadoc" and "Modelling and Implementation Guide". Both documents seems to be scarce to start development. Of course there are a lot of blogs and one example on java.net, but where is a documentation ???

In fact the Modeling and Implementation Guide it is an official documentation.
Oracle® Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management 11g Release 1 (11.1.1.7)
31 Working with Case Management
http://docs.oracle.com/cd/E28280_01/doc.1111/e15176/case_mgmt_bpmpd.htm#CIHJBBCA
But I would also strongly recommend you to read this series of posts from the Oracle A-Team (start from the end of the list below):
Case Management In-Depth: Cases & Case Activities Part 2 – Case Rules
http://www.ateam-oracle.com/case-management-in-depth-cases-case-activities-part-2-case-rules/
Case Management In-Depth: Cases & Case Activities Part 1 – Acivity Scope
http://www.ateam-oracle.com/case-management-in-depth-cases-case-activities-part-1-acivity-scope/
Case Management In-Depth: Stakeholders & Permissions
http://www.ateam-oracle.com/case-management-in-depth-stakeholders-permissions/
Case Management Part 3: Runtime Lifecycle of a Project
http://www.ateam-oracle.com/case-management-part-3-runtime-lifecycle-of-a-project/
Case Management Part 2: Anatomy of a Project
http://www.ateam-oracle.com/case-management-part-2-anatomy-of-a-project/
Case Management Part 1: An Introduction
http://www.ateam-oracle.com/case-management-part-1-an-introduction/

Develop Doc/Literal WS with a bottom up approach

Hi all,
I am trying to work with the jax rpc implementation of OC4J 10.1.2.
I saw on OTN how build doc/literal web services with a top down approach but not with a bottom up approach. I can t see any tool like java2wsdl and wsdl2java of axis in the official documentation.
I know that the next release 10.1.3 will provide these fonctionalities by ANT scripts but no for current production's release.
Is there, somewhere ant scripts or librairies which could help me ?
Thanks in advance.
Alexandre
My environment
OC4J 10.1.2
JDK 1.4.2
Maven, Ant, Eclipse

In 10.1.2, the was to build Web services using the bottom-up development pattern is to use the WebServicesAssemble.jar file. If you specify the document style for the message format, in your configuration file, you will be able to assemble such application.
As to the ant integration, it will be limited to using the java task:
<target name="createpackage">
<java jar="${ORACLE_HOME}/webservices/lib/WebServicesAssembler.jar" fork="yes"
failonerror="true">
<arg value="-config"/>
<arg value="./config.xml"/>
</java>
</target>
Hope this helps,
Eric

Doc/Literal service on 10g R2

hi all,
Can you please provide pointers to any Oracle documentation that can help me build Document/Literal web services on OAS 10g R2.
Thanks,
M.

For anyone interested - I have found the following gem hidden deep inside OTN:
http://www.oracle.com/technology/sample_code/tech/java/codesnippet/webservices/docservice/index.html
Its a simple Doc literal WS with client.jsp that can be deployed on 9.0.3/9.0.4. Just got it working on my standalone 904 - beautiful stuff!

AIA documentation for operations

I am looking fror documentation to operate and monitor AIA.
- How to monitor ESB/BPEL processes
- Error handling
- Stop/start server
- Retry failed processes
- Analyze errors
This information is probably scattered in BPEL PM, Enterprise Manager, ESB and AIA documentation.
Is there also an overview document referencing the detailed manuals?
We're using AIA 2.0.1 on 10.1.3.3
Thanks,
Jan Willem

In the doc folder inside the dev tools zip file you downloaded from MetaLink is the documentation for how to use the tools.

Any pointers to good documentation for APD....

Can someone point out a site or drop here documentation for APD, I have been throught the SDN site already, I am looking for a comprehensive documentation.

Check this link for How to doc on APD.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/96939c07-0901-0010-bf94-ac8b347dd54.
Check this link for help
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/96939c07-0901-0010-bf94-ac8b347dd541
Check this answer for APD's
[APD]: How to transfer data to SAP CRM?.
APD
Check these blogs and links...
Start with Analysis Process Designer
Launching an APD analysis process from an ABAP program
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/96939c07-0901-0010-bf94-ac8b347dd541
and sap help
http://help.sap.com/saphelp_nw2004s/helpdata/en/39/e45e42ae1fdc54e10000000a155106/frameset.htm
and service.sap.com/bi
https://websmp206.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000585703&
http://help.sap.com/saphelp_nw04/helpdata/en/49/7e960481916448b20134d471d36a6b/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/39/e45e42ae1fdc54e10000000a155106/frameset.htm
SDN;
APD and T-ODS automation questions
Hello Info on APD
Hello Info on APD
APD and T-ODS automation questions
The analysis process designer is the application environment for the SAP data mining solution
"The Analysis Process Designer (APD) makes it possible to find and identify these hidden or complex relationships between data in a simple way.
Various data transformations are provided for this purpose, such as statistical and mathematical calculations, and data cleansing or structuring processes"
Analyzing Customers buying trends using Analysis Process Designer
Start with Analysis Process Designer
Launching an APD analysis process from an ABAP program
Closed loop applications in real world
Thanks...
Shambhu

Documentation for doc literal processing

Similar Messages

Maybe you are looking for