XI support different xml versions ?

Hi Experts,
Using XI we are integrating the R/3 with the E-commerce hub(ARIBA, F4F) that uses its own xml version, how can we check that their Message schema (xml form) is supported by XI or not.
Thanks,
MK

Message schema (xml form)
XI supports schema in xsd, wsdl or dtd format only which could be imported under External Definition in IR.
Regards,
Prateek

Similar Messages

  • Compare 2 different xml versions and highlite the differences

    Hi,
    Currently we have xml and that is displayed on the web page using the css style sheets.
    The xml we have remain the same most part but with small changes (say different version created after a week).
    We want to be able to track the differences from the previous version and highlight them, the differences, when showing it in the web page.
    Please advise if this can be done and how.
    Thanks.

    try
    SQL> set serveroutput on
    SQL> set long 50000
    SQL>
    SQL> declare
      2 
      3    --main
      4    xml1 xmltype := xmltype('<ROWSET>
      5                                <ROW>
      6                                  <EMPNO>7934</EMPNO>
      7                                  <ENAME>MILLER</ENAME>
      8                                  <JOB>CLERK</JOB>
      9                                  <MGR>7782</MGR>
    10                                  <HIREDATE>1982-01-23T00:00:00</HIREDATE>
    11                                  <REMOVED>abc</REMOVED>
    12                                  <SAL>1300</SAL>
    13                                  <COMM/>
    14                                  <DEPTNO>10</DEPTNO>
    15                                </ROW>
    16                              </ROWSET>');
    17    --new
    18    xml2 xmltype := xmltype('<ROWSET>
    19                                <ROW>
    20                                  <EMPNO>7934</EMPNO>
    21                                  <ENAME>MILLER</ENAME>
    22                                  <JOB>CLERK</JOB>
    23                                  <MGR>7782</MGR>
    24                                  <ADDED>xyz</ADDED>
    25                                  <HIREDATE>1982-01-23T00:00:00</HIREDATE>
    26                                  <SAL>1300</SAL>
    27                                  <COMM/>
    28                                  <DEPTNO>10</DEPTNO>
    29                                </ROW>
    30                              </ROWSET>');
    31    diff xmltype;
    32 
    33    xtype varchar2(80);
    34    xpath varchar2(80);
    35    xpathChild varchar2(80);
    36    xnodeChild varchar2(80);
    37    new_value xmltype;
    38 
    39    new_xml xmltype;
    40 
    41 
    42  begin
    43 
    44    -- get diff
    45    select xmldiff(xml1, xml2) into diff from dual;
    46    dbms_output.put_line(diff.getclobval());
    47 
    48    -- that have
    49    select x.xtype, x.xpath, x.new_value
    50      into xtype, xpath, new_value
    51      from xmltable(
    52             xmlnamespaces('http://xmlns.oracle.com/xdb/xdiff.xsd' as "xd"
    53                          ,'http://www.w3.org/2001/XMLSchema-instance' as "xsi"
    54                          )
    55           , '/xd:xdiff'
    56             passing diff
    57             columns xtype     varchar2(80) path 'local-name(xd:insert-node-before)'
    58                   , xpath     varchar2(80) path'xd:insert-node-before/@xd:xpath'
    59                   , new_value xmltype path 'xd:insert-node-before/xd:content/*'
    60           ) x;
    61 
    62     dbms_output.put_line('type of doing: ' || xtype);
    63     dbms_output.put_line('path for doing: ' || xpath);
    64     dbms_output.put_line('value for doing: ' || new_value.getclobval());
    65 
    66     if (xtype = 'insert-node-before') then
    67       xpathChild := substr(xpath, 1, instr(xpath, '/',-1)-1);
    68       xnodeChild := substr(xpath, instr(xpath, '/',-1)+1);
    69 
    70       select insertChildXMLbefore (xml1,
    71                                    xpathChild,
    72                                    xnodeChild,
    73                                    XMLType('<HIGHLIGHT>' || new_value || '</HIGHLIGHT>'))
    74       into new_xml
    75       from dual;
    76     end if;
    77 
    78 
    79     dbms_output.put_line(new_xml.getclobval());
    80 
    81  end;
    82  /
    <xd:xdiff xsi:schemaLocation="http://xmlns.oracle.com/xdb/xdiff.xsd http://xmlns.oracle.com/xdb/xdiff.xsd" xmlns:xd="http://xmlns.oracle.com/xdb/xdiff.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><?oracle-xmldiff operations-in-docorder="true" output-model="snapshot" diff-algorithm="global"?><xd:insert-node-before xd:node-type="element" xd:xpath="/ROWSET[1]/ROW[1]/HIREDATE[1]"><xd:content><ADDED>xyz</ADDED></xd:content></xd:insert-node-before><xd:delete-node xd:node-type="element" xd:xpath="/ROWSET[1]/ROW[1]/REMOVED[1]"/></xd:xdiff>
    type of doing: insert-node-before
    path for doing: /ROWSET[1]/ROW[1]/HIREDATE[1]
    value for doing: <ADDED>xyz</ADDED>
    <ROWSET><ROW><EMPNO>7934</EMPNO><ENAME>MILLER</ENAME><JOB>CLERK</JOB><MGR>7782</MGR><HIGHLIGHT><ADDED>xyz</ADDED></HIGHLIGHT><HIREDATE>1982-01-23T00:00:00</HIREDATE><REMOVED>abc</REMOVED><SAL>1300</SAL><COMM/><DEPTNO>10</DEPTNO></ROW></ROWSET>
    PL/SQL procedure successfully completed
    SQL>
    SQL> select * from v$version where rownum=1;
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    SQL>

  • Branching Recommendation on Supporting Different Versions

    Hi Guys,
    We are a small team and barely new to TFS. I wanted to introduce branching for supporting different versions eg. SSRS 2005 and SSR2012, SSIS2005 and SSIS2012.
    We're planning to convert our codes from 2005 to 2012 but during that period we need to support the changes on both versions (2005 & 2012).
    Currently this what we have in TFS.
    I know it's a bit ugly and wanted to know how branching will make this cleaner.
    I'm thinking something like this
    SSRS
    >>v2005
    >>v2012
    SSIS
    >>v2005
    >>v2012
    Basically, i wanted to get your input on the requirements or suggestions.
    Also, a detailed procedure on how to arrive on it. I check some online tutorials but most of them branch the MAIN..so they have MAIN and DEV..
    I think at this point we're not after on the proper release or MERGING as we are just a small team. 
    We'll probably change the file in v2005 and v2012 and checkin both files in case there's some codes/component that is supported on the version.
    Many thanks

    Hi Vinxster,  
    Thanks for your post.
    Yes, we usually create branch on Main folder(whole solution in it) to generate the Dev branch and Release branch separately, then develop in Dev branch, and merge changes from Dev branch to Main branch, then merge changes from Main branch to Release branch.
    If you’re a small team, and you don’t want to create Dev and Release branches from Main folder, I think this issue not relate to branching.
    I think you want to restructure your project folders in Main folder, right? You want to create a
    SSRS folder under Main folder, then move LocalReports and LocalReports_VS2005 to this
    SSRS folder, and create SSIS folder under Main, then move SSISPackages and SSISPackages_VS 2005 to
    SSIS folder? If yes, you can manually create SSRS and
    SSIS folders under your Main folder, the right-click on that four project folders and select
    Move to move them to the right folder.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • KEY and KEYREFs support on XML DB

    First of all, sorry for my english but I am a spanish researcher who have not been abroad too much :-).
    I�m trying to use XML DB to store XML documents that represents UML models and the way I've choosed to map relationships in my schema is using KEY and KEYREFs. The fact is that It seems to me that XML DB does not use them whem it creates the different objects that results on the schema's load. Does XMLDB support the definitons of KEYs and KEYREFs in the schema?? If so, how does it do?? Defining constraints oon the objects created?? I suppose no, because the KEYs and KEYREFs are defined on 'complexTypes' and the Oracle's constraints goes to tables (not to object types).
    I'm worling with the next schema:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns="Kybele/MetaModel_Schema_All" targetNamespace="Kybele/MetaModel_Schema_All" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
    <!-- En esta version, representaremos las relaciones usando atributos KEYs y KEYREFs
    Ademas, en esta version mapeamos el metamodelo de UML por completo-->
    <!-- En las anotaciones para XML DB usaremos el prefijo MMALL(MetaModelo Completo) -->
    <!--******************** DECLARACION DE LOS ELEMENTOS DEL METAMODELO *********************-->
    <xsd:element name="MetaModel" xdb:defaultTable="MMALL_METAMODELS_TABLE">
    <xsd:complexType xdb:SQLType="MMALL_METAMODELS_TYPE">
    <xsd:sequence>
    <xsd:element name="ModelElements" type="ModelElement" maxOccurs="unbounded"/>
    <xsd:element name="Dependencies" type="Dependency" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:complexType>
    <!-- Es en este punto donde definiremos las "PRIMARYKEYS"(KEYs) Y "FOREIGNKEYS"(KEYREFs) para simular relaciones -->
    <!-- ************************************************************************************************* *-->
    <!-- RELACIONES ModelElement - Dependency -->
    <xsd:key name="Dependency_PK">
    <xsd:selector xpath="Dependencies"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:key name="ModelElement_PK">
    <xsd:selector xpath="ModelElements"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:keyref name="Requirement_FK" refer="Dependency_PK">
    <xsd:selector xpath="ModelElements"/>
    <xsd:field xpath="requirement"/>
    </xsd:keyref>
    <xsd:keyref name="Provision_FK" refer="Dependency_PK">
    <xsd:selector xpath="ModelElements"/>
    <xsd:field xpath="provision"/>
    </xsd:keyref>
    <xsd:keyref name="Client_FK" refer="ModelElement_PK">
    <xsd:selector xpath="Dependencies"/>
    <xsd:field xpath="client"/>
    </xsd:keyref>
    <xsd:keyref name="Supplier_FK" refer="ModelElement_PK">
    <xsd:selector xpath="Dependencies"/>
    <xsd:field xpath="supplier"/>
    </xsd:keyref>
    <!-- RELACIONES Generalization - GeneralizableElement -->
    <xsd:key name="Generalization_PK">
    <xsd:selector xpath="Generalization"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:key name="GeneralizableElement_PK">
    <xsd:selector xpath="GeneralizableElement"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:keyref name="Subtype_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="Generalization"/>
    <xsd:field xpath="subtype"/>
    </xsd:keyref>
    <xsd:keyref name="Type_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="Generalization"/>
    <xsd:field xpath="type"/>
    </xsd:keyref>
    <xsd:keyref name="Generalization_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="GeneralizableElement"/>
    <xsd:field xpath="generalization"/>
    </xsd:keyref>
    <xsd:keyref name="Specilization_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="GeneralizableElement"/>
    <xsd:field xpath="specialization"/>
    </xsd:keyref>
    <!-- RELACIONES Classifier - AssociationEnd -->
    <xsd:key name="Classifier_PK">
    <xsd:selector xpath="Classifier"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:key name="AssociationEnd_PK">
    <xsd:selector xpath="AssociationEnd"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:keyref name="AssociationEnd_FK" refer="AssociationEnd_PK">
    <xsd:selector xpath="Classifier"/>
    <xsd:field xpath="associationEnd"/>
    </xsd:keyref>
    <xsd:keyref name="Participant_FK" refer="AssociationEnd_PK">
    <xsd:selector xpath="Classifier"/>
    <xsd:field xpath="participant"/>
    </xsd:keyref>
    <xsd:keyref name="AssociationEnd_Type_FK" refer="Classifier_PK">
    <xsd:selector xpath="AssociationEnd"/>
    <xsd:field xpath="type"/>
    </xsd:keyref>
    <xsd:keyref name="AssociationEnd_Specification_FK" refer="Classifier_PK">
    <xsd:selector xpath="AssociationEnd"/>
    <xsd:field xpath="specification"/>
    </xsd:keyref>
    <!-- RELACIONES AssociatioEnd - Attribute -->
    <xsd:keyref name="AttributeCompose_FK" refer="AssociationEnd_PK">
    <xsd:selector xpath="Attribute"/>
    <xsd:field xpath="associationEnd_member"/>
    </xsd:keyref>
    <!-- RELACIONES AssociatioEnd - Association -->
    <xsd:keyref name="AssociationEndCompose_FK" refer="Association_PK">
    <xsd:selector xpath="Association"/>
    <xsd:field xpath="Association_member"/>
    </xsd:keyref>
    </xsd:element>
    <!--***************************** DEFINICION DE TIPOS SIMPLES *****************************-->
    <!-- TIPO ENUMERADO AGGREGATIONTYPE -->
    <xsd:simpleType name="AggregationType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="none"/>
    <xsd:enumeration value="aggregate"/>
    <xsd:enumeration value="composite"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!-- TIPO ENUMERADO SCOPETYPE -->
    <xsd:simpleType name="ScopeType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="instance"/>
    <xsd:enumeration value="classifier"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!-- TIPO ENUMERADO MULTIPLICITYTYPE -->
    <xsd:simpleType name="MultiplicityType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="0..1"/>
    <xsd:enumeration value="1..1"/>
    <xsd:enumeration value="0..N"/>
    <xsd:enumeration value="1..N"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!-- TIPO ENUMERADO CHANGEABLETYPE -->
    <xsd:simpleType name="ChangeableType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="none"/>
    <xsd:enumeration value="frozen"/>
    <xsd:enumeration value="add_only"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!--**************************** DEFINICION DE TIPOS COMPLEJOS **********************************************-->
    <!-- TIPO COMPLEJO MODELELEMENT -->
    <xsd:complexType name="ModelElement" xdb:SQLType="MMALL_ModelElement_Type">
    <xsd:sequence>
    <xsd:element name="nombre" type="xsd:string"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="requirement" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="provision" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:complexType>
    <!-- TIPO COMPLEJO DEPENDENCY -->
    <xsd:complexType name="Dependency" xdb:SQLType="MMALL_Dependency_Type">
    <xsd:complexContent>
    <xsd:extension base="ModelElement">
    <xsd:sequence>
    <xsd:element name="description" type="xsd:string"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="client" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="supplier" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO GENERALIZATION -->
    <xsd:complexType name="Generalization" xdb:SQLType="MMALL_Generalization_Type">
    <xsd:complexContent>
    <xsd:extension base="ModelElement">
    <xsd:sequence>
    <xsd:element name="discriminator" type="xsd:string"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="subtype" type="xsd:string"/>
    <xsd:element name="supertype" type="xsd:string"/>
    <!-- Al quitar minOccurs y maxOccurs obligamos a que siempre haya un (Y SOLO UNO)
    subelemento 'subtype' y 'supertype' -->
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO NAMESPACE -->
    <xsd:complexType name="NameSpace" xdb:SQLType="MMALL_NameSpace_Type">
    <xsd:complexContent>
    <xsd:extension base="ModelElement"/>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO GENERALIZABLEELEMENT -->
    <xsd:complexType name="GeneralizableElement" xdb:SQLType="MMALL_GeneralizableElement_Type">
    <xsd:complexContent>
    <xsd:extension base="NameSpace">
    <xsd:sequence>
    <xsd:element name="isRoot" type="xsd:boolean"/>
    <xsd:element name="isLeaf" type="xsd:boolean"/>
    <xsd:element name="isAbstract" type="xsd:boolean"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="generalization" type="xsd:string"/>
    <xsd:element name="specification" type="xsd:string"/>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO: ASSOCIATIONEND -->
    <xsd:complexType name="AssociationEnd" xdb:SQLType="MMALL_ASSOCIATIONEND_TYPE">
    <xsd:complexContent>
    <xsd:extension base="ModelElement">
    <xsd:sequence>
    <xsd:element name="IsNavigable" type="xsd:boolean"/>
    <xsd:element name="IsOrdered" type="xsd:boolean"/>
    <xsd:element name="Aggregation" type="AggregationType"/>
    <xsd:element name="Multiplicity" type="MultiplicityType" minOccurs="0"/>
    <xsd:element name="Changeable" type="ChangeableType"/>
    <xsd:element name="TargetScope" type="ScopeType"/>
    <!-- Subelementos para representar las relaciones -->
    <xsd:element name="Qualifier" type="Attribute" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="Association_member" type="xsd:string"/>
    <xsd:element name="Type" type="xsd:string"/>
    <xsd:element name="Specification" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO CLASSIFIER -->
    <xsd:complexType name="Classifier" xdb:SQLType="MMALL_CLASSIFIER_TYPE">
    <xsd:complexContent>
    <xsd:restriction base="GeneralizableElement">
    <xsd:sequence>
    <!-- Subelementos para representar las relaciones -->
    <xsd:element name="AssociationEnd" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="Participant" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:restriction>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO CLASS -->
    <xsd:complexType name="Class" xdb:SQLType="MMALL_CLASS_TYPE">
    <xsd:complexContent>
    <xsd:extension base="Classifier"/>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO ATTRIBUTE -->
    <xsd:complexType name="Attribute" xdb:SQLType="MMALL_ATTRIBUTE_TYPE">
    <xsd:sequence>
    <xsd:element name="associationEnd_member" type="xsd:string" minOccurs="0" maxOccurs="1"/>
    </xsd:sequence>
    </xsd:complexType>
    <!-- TIPO COMPLEJO ASSOCIATION -->
    <xsd:complexType name="Association" xdb:SQLType="MMALL_ASSOCIATION_TYPE">
    <xsd:complexContent>
    <xsd:restriction base="GeneralizableElement">
    <xsd:sequence>
    <xsd:element name="connection" type="AssociationEnd" minOccurs="2" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:restriction>
    </xsd:complexContent>
    </xsd:complexType>
    </xsd:schema>
    and when I try to load it into XMLDB it fails:
    SQL> @registerSchema oe oe /home/OE/Metamodel_Schema_All.xsd "http://kybele.escet.urjc.es/ejemplos/x
    ml_schema/Metamodel_Schema_All.xsd"
    SQL> set echo on
    SQL> connect &1/&[email protected]
    Conectado.
    SQL> alter session set events='31098 trace name context forever';
    Sesi�n modificada.
    SQL> begin
    2 dbms_xmlschema.registeruri(
    3 '&4',
    4 '&3',
    5 TRUE,TRUE,FALSE,TRUE);
    6 end;
    7 /
    antiguo 3: '&4',
    nuevo 3: 'http://kybele.escet.urjc.es/ejemplos/xml_schema/Metamodel_Schema_All.xsd',
    antiguo 4: '&3',
    nuevo 4: '/home/OE/Metamodel_Schema_All.xsd',
    begin
    ERROR en l�nea 1:
    ORA-31154: invalid XML document
    ORA-19202: Se ha producido un error en el procesamiento
    LPX-00217: invalid character 0 (\u0000) de XML
    ORA-06512: en "XDB.DBMS_XMLSCHEMA_INT", l�nea 0
    ORA-06512: en "XDB.DBMS_XMLSCHEMA", l�nea 166
    ORA-06512: en l�nea 2
    it says.
    I have done several attempts, deleting and including just some of the KEYs/KEYREFs in the schema and it seems to me that the problem is that it let me include so much keys as I want but it fails when the number of KEYREFs that I include increase.
    Help!!!
    Thanks on advance for spare your time helping us.

    Looks like known bug 2831302 fixed in (forthcoming) 10g release. In the mean time I would simply comment the key/keyref out of the schema

  • Setup Central Contract Management SRM 7.01 with differing release versions

    Hello experts,
    OSS note 1268821 explains how to configure the central contract management between a SRM 7.0 and  an ERP 6.04. So far so good, but how should it be handled if there are differing release versions such as ERP 6.04 and ERP 6.03? I guess that a technical split (xml services/ ALE distribution) is necessary?
    Assuming that there are some backends with differing release versions and in some cases with differing master data (not supported by central master data client) would you always go via PI? Independent of release version, technology and master data.
    Could you give some further detailed informations how to configure such a scenario? What has to be done to transfer existing contracts from an ERP 6.04 into SRM CM component (migration concept)?
    Thanks!!!
    KR Thorsten

    Hi Thorsten
    The minimal ECC version is 6.0 EHP4, Central Contracts require certain business functions in ECC to be activated and as these are included within ECC EHP4 you won't have these available in lower version. Therefore you won't be able to operate central contracts in such an ECC system.
    You would either have to go with patching these systems or go with GOA's for these systems.
    Operating central contracts via PI or SOA i believe provide almost similar functionality. SOA however requires an SRM EHP1 system and ECC EHP5 back-end to operate whilst central contracts configured via PI can be operated onwards from an SRM 7.0 and EHP4 system.
    I can't help you on your migration issue, maybe someone else can.
    Kind regards,
    Tim

  • Help with registering multiple XML versions with Oracle 9i

    Hello,
    I have a fundamental question. Probably someone had been in similar situation and thought of the best way to handle.
    Our product has about 15 versions that we need to support.
    Each version publishes its 'xmlschema' and is slightly different from the previous version.
    Now if I register each schema version with oracle9i it will auto-create tables for each version (even for xml elements/attributes that are same across different versions).
    2 options that we thought of so far to handle this is
    -Combine all 15 versions schema's into 1 super-set schema and register with oracle db. Fields/elements, a version does not use will be empty
    -Use XML 'extensions' in various xml schema, such that each version in 'extended' from the previous one and keeps on adding its additions attributes/elements. My question is then if I register these 15 'extended' schemas with oracle, will it create common DB tables per version or it will still create unique tables for all 15 versions.
    Anyone has any better suggestions or comments to handle this situation ?
    thanx
    -Manu

    But I'm still stuck on the problem. It still doesn't read the second object. There is no second object.
    The code is quite big, any specific portion would be helpful, please let me know?This is a minimal load and print for an XML bean:import java.io.*;
    import java.beans.*;
    import java.util.*;
    public class LoadAndPrintXMLBean {
      // run with your file name as first argument
      public static void main (String[] args) {
        try {
          XMLDecoder d = new XMLDecoder(
            new BufferedInputStream(
              new FileInputStream(args[0])));
          Object result = d.readObject();
          d.close();
          System.out.println(result);
        } catch (Exception ex) {
          ex.printStackTrace();
    }For your input, it prints[[INDEX_KEY], [7]]You have one object, a vector, containing two vectors:
      The first child vector contains the string "INDEX_KEY".
      The second child vector contains the string "7".
    This matches the structure of your XML<?xml version="1.0" encoding="UTF-8"?>
    <java version="1.4.1_01" class="java.beans.XMLDecoder">
      <object class="java.util.Vector">
        <void method="add">
          <object class="java.util.Vector">
            <void method="add">
              <string>INDEX_KEY</string>
            </void>
          </object>
        </void>
        <void method="add">
          <object class="java.util.Vector">
            <void method="add">
              <string>7</string>
            </void>
          </object>
        </void>
      </object>
    </java>There is only one object there to retrieve using readObject().
    Pete

  • DB XML version 2.5.13, php 5.2.10

    Not sure what the problem is, but I'm not getting the XML content with this piece of code:
    function getXmlDocumentByNameAsStringV1($documentName, $containerName){
    $container = $this->mgr->openContainer($containerName);
    $xmlDocument = $container->getDocument($documentName);
    $xmlDocument->fetchAllData();
    $content = $xmlDocument->getContent();
    $documentName = $xmlDocument->getName();
    echo "doc name= [$documentName]";
    print $xmlDocument->getContent();
    unset ($container);
    return $content;
    I basically created a wrapper class around the DB XML api.
    I was trying to get the full XML content as a string with this function, but all I seem to get is just a reference.
    I ended up doing a query on it instead to get me the getContent() call to get what I needed (which was full XML document with the document version and DOCTYPE refernces), but was wondering what I was doing wrong with this approach.
    Also when I was inserting XML documents into the Oracle Berkely DB XML database that referenced a DTD the database seemed
    to switch to a validate mode even though I did not turn on validation when either creating the container or opening the container.
    Is there a way to overide what appears to be a valdiation mode when the document refernces a DTD?
    I am running PHP 5.2.10 under Apache 2.2.14 with the binary release of DB XML version 2.5.13
    I figured out that I had to put my DTD in the [Apache Root] directory for it to validate properly. Stuff I read
    through the forums suggested that I needed to put the DTD at the root of where the databases are when
    referencing a DTD with just a file name without any reference to file:/// etc.. or http://
    I changed my home directory to a certain location:when I instantiated the
    $env = new Db4Env();
    $env->open($this->homeDirectory, $this->flagsDbEnvOpen)
    In any case the work around for now is to just put the DTD in the location that it expects which is the Apache Root install directory.
    It is a minor inconvenience, but thought I would mention it for others that may have run into this problem.
    (I used the Process Monitor searching on my DTD name to discover the solution to where Oracle DB XML or rather Apache Web server, I suppose through the dlls
    was expecting to find it)
    Also it appears that the binary versino works with PHP 5.2.10 of apache. I did not need to recompile the code with the new apache version.
    Is there any thing I should be worried about?
    Also I was getting the following error:
    // the code commented out below was an attempt to try and do a sub query from a valid XmlValue object.
    // was unsuccesful. starting receiving errors such as
    ////[25-Nov-2009 15:24:26] PHP Fatal error: Uncaught exception 'xmlexception' with message 'Error: Sequence does not match type document-node() - found item of type element(APP_Test_Script, {http://www.w3.org/2001/XMLSchema}untyped) [err:XPTY0004], <query>:1:12' in C:\htdocs\app1\BackEnd.php:82
    // Will attempt to reprocess xml into a php DOm node and extract out value that way, just to get something working.
    // $subQuery = "//*";
    // $categoryQContext = $this->mgr->createQueryContext();
    // $categoryQuery = $this->mgr->prepare($subQuery, $categoryQContext);
    // $testScriptValue = $AppScriptAsXmlValue->asString();
    // echo $testScriptValue;
    // echo "hello world";
    // $categoryResults = $categoryQuery->execute($testScriptAsXmlValue, $categoryQContext);
    // $categoryValue = null;
    // while($categoryResults->hasNext()){
    // $node = $categoryResults->next();
    // $categoryValue = $node->asString();
    Basically, I was trying to do a sub xquery from an initial xquery that returned a sequence of XML documents. According to the example in book The Definiitive Guide to Bekrely DB XML
    it should have worked, but wasn't.
    I also ran into an issue where I seemed to have locked up a container when I was editing an XML document in Oxygen and saving it back to the DB XML container from within Oxygen.
    after that action it wouldn't return from the save function and I coudln't ever load up that container. Even trying to access the contain from the command line dbxml it wasn't able to access
    that container again. I ended up having to blow it away from lack of knowledge on how to recover from that. If anyone has run into this and/or has some suggestions on this it would be nice.
    I'm guessing could it be because I had some meta data values defined in some of these documents that I was updating. From Oxygen, can you create metadata? I dont think you can, at least it wasn't obvious to me except perhaps fro the name of the document (which is implicitly a meta data tag).

    Hi,
    You'll have to compile yourself for different PHP API versions.
    Regards,
    George

  • An error occurred during local report processing.The definition of the report '' is invalid.The definition of this report is not valid or supported by this version of Reporting Services. he report definition may have been created with a later version of R

    Hi,
    I am trying to create rdlc file programmatically. Using Memory Table as dataset. Here is my code
    ' For each field in the resultset, add the name to an array listDim m_fields AsArrayList
      m_fields = NewArrayList()
      Dim i AsIntegerFor i = 0 To tbdataset.Tables(0).Columns.Count - 1
          m_fields.Add(tbdataset.Tables(0).Columns(i).ColumnName.ToString)
      Next i
      'Create Report 'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition' Open a new RDL file stream for writingDim stream AsFileStream
      stream = File.OpenWrite("D:\MyTestReport2.rdlc")
      Dim writer AsNewXmlTextWriter(stream, Encoding.UTF8)
      ' Causes child elements to be indented
      writer.Formatting = Formatting.Indented
      ' Report element
      writer.WriteProcessingInstruction("xml", "version=""1.0"" encoding=""utf-8""")
      writer.WriteStartElement("Report")
      writer.WriteAttributeString("xmlns", Nothing, "http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition")
      writer.WriteAttributeString("xmlns:rd", "http://schemas.microsoft.com/SQLServer/reporting/reportdesigner")
      writer.WriteStartElement("ReportSections")
      writer.WriteStartElement("ReportSection")
      writer.WriteElementString("Width", "11in")
      writer.WriteStartElement("Body")
      writer.WriteElementString("Height", "5in")
      writer.WriteStartElement("ReportItems")
      writer.WriteStartElement("Tablix")
      writer.WriteAttributeString("Name", Nothing, "Tablix1")
      writer.WriteElementString("Top", ".5in")
      writer.WriteElementString("Left", ".5in")
      writer.WriteElementString("Height", ".5in")
      writer.WriteElementString("Width", (m_fields.Count * 1.5).ToString() + "in")
      writer.WriteStartElement("TablixBody")
      ' Tablix Columns
      writer.WriteStartElement("TablixColumns")
      ForEach fieldName In m_fields
          writer.WriteStartElement("TablixColumn")
          writer.WriteElementString("Width", "1.5in")
          writer.WriteEndElement() ' TableColumnNext fieldName
      writer.WriteEndElement() ' TablixColumns' Header Row
      writer.WriteStartElement("TablixRows")
      writer.WriteStartElement("TablixRow")
      writer.WriteElementString("Height", ".25in")
      writer.WriteStartElement("TablixCells")
      ForEach fieldName In m_fields
          writer.WriteStartElement("TablixCell")
          writer.WriteStartElement("CellContents")
          writer.WriteStartElement("Textbox")
          writer.WriteAttributeString("Name", Nothing, "Header" + fieldName)
          ' writer.WriteAttributeString("CanGrow",  True)' writer.WriteAttributeString("Keeptogether", True)
          writer.WriteStartElement("Paragraphs")
          writer.WriteStartElement("Paragraph")
          writer.WriteStartElement("TextRuns")
          writer.WriteStartElement("TextRun")
          writer.WriteElementString("Value", fieldName)
          writer.WriteStartElement("Style")
          writer.WriteElementString("TextDecoration", "Underline")
          writer.WriteElementString("PaddingTop", "0in")
          writer.WriteElementString("PaddingLeft", "0in")
          writer.WriteElementString("LineHeight", ".5in")
          ''writer.WriteElementString("Width", "1.5in")''writer.WriteElementString("Value", fieldName)
          writer.WriteEndElement() ' Style
          writer.WriteEndElement() ' TextRun
          writer.WriteEndElement() ' TextRuns
          writer.WriteEndElement() ' Paragraph
          writer.WriteEndElement() ' Paragraphs
          writer.WriteEndElement() ' TexBox
          writer.WriteEndElement() ' CellContents
          writer.WriteEndElement() ' TablixCellNext
      writer.WriteEndElement() ' TablixCells
      writer.WriteEndElement() ' TablixRow'writer.WriteEndElement() ' TablixRows          Do not close Rows tag here colse it after details'End of Headers'Details Rows'writer.WriteStartElement("TablixRows")         Since Rows tag in header is not closed not need to open fresh tag
      writer.WriteStartElement("TablixRow")
      writer.WriteElementString("Height", ".25in")
      writer.WriteStartElement("TablixCells")
      ForEach fieldName In m_fields
          writer.WriteStartElement("TablixCell")
          writer.WriteStartElement("CellContents")
          writer.WriteStartElement("Textbox")
          writer.WriteAttributeString("Name", Nothing, fieldName)
          '  writer.WriteAttributeString("CanGrow", True)'  writer.WriteAttributeString("Keeptogether", True)
          writer.WriteStartElement("Paragraphs")
          writer.WriteStartElement("Paragraph")
          writer.WriteStartElement("TextRuns")
          writer.WriteStartElement("TextRun")
          'writer.WriteElementString("Value", fieldName)
          writer.WriteElementString("Value", "=Fields!" + fieldName + ".Value")
          writer.WriteStartElement("Style")
          writer.WriteElementString("TextDecoration", "Underline")
          writer.WriteElementString("PaddingTop", "0in")
          writer.WriteElementString("PaddingLeft", "0in")
          writer.WriteElementString("LineHeight", ".5in")
          ''writer.WriteElementString("Width", "1.5in")''writer.WriteElementString("Value", fieldName)
          writer.WriteEndElement() ' Style
          writer.WriteEndElement() ' TextRun
          writer.WriteEndElement() ' TextRuns
          writer.WriteEndElement() ' Paragraph
          writer.WriteEndElement() ' Paragraphs
          writer.WriteEndElement() ' TexBox
          writer.WriteEndElement() ' CellContents
          writer.WriteEndElement() ' TablixCellNext
      writer.WriteEndElement() ' TablixCells
      writer.WriteEndElement() ' TablixRow
      writer.WriteEndElement() ' TablixRows'End of Details Rows
      writer.WriteEndElement() ' TablixBody
      writer.WriteStartElement("TablixRowHierarchy")
      writer.WriteStartElement("TablixMembers")
      writer.WriteStartElement("TablixMember")
      ' Group
      writer.WriteElementString("KeepWithGroup", "After")
      writer.WriteEndElement() ' TablixMember' Detail Group
      writer.WriteStartElement("TablixMember")
      writer.WriteStartElement("Group")
      writer.WriteAttributeString("Name", Nothing, "Details")
      writer.WriteEndElement() ' Group
      writer.WriteEndElement() ' TablixMember
      writer.WriteEndElement() ' TablixMembers
      writer.WriteEndElement() ' TablixRowHierarchy
      writer.WriteStartElement("TablixColumnHierarchy")
      writer.WriteStartElement("TablixMembers")
      'writer.WriteStartElement("TablixMember")ForEach fieldName In m_fields
          writer.WriteStartElement("TablixMember")
          writer.WriteEndElement() ' TablixMemberNext' writer.WriteEndElement() ' TablixMember
      writer.WriteEndElement() ' TablixMembers
      writer.WriteEndElement() ' TablixColumnHierarchy
      writer.WriteElementString("DataSetName", "tbdataset")
      writer.WriteEndElement() ' Tablix
      writer.WriteEndElement() ' ReportItems
      writer.WriteEndElement() ' Body
      writer.WriteStartElement("Page")
      ' Page Header Element
      writer.WriteStartElement("PageHeader")
      writer.WriteElementString("Height", "1.40cm")
      writer.WriteStartElement("ReportItems")
      writer.WriteStartElement("Textbox")
      writer.WriteAttributeString("Name", Nothing, "Textbox1")
      writer.WriteStartElement("Paragraphs")
      writer.WriteStartElement("Paragraph")
      writer.WriteStartElement("TextRuns")
      writer.WriteStartElement("TextRun")
      writer.WriteElementString("Value", Nothing, "ABC CHS.")
      writer.WriteEndElement() ' TextRun
      writer.WriteEndElement() ' TextRuns
      writer.WriteEndElement() ' Paragraph
      writer.WriteEndElement() ' Paragraphs
      writer.WriteEndElement() ' TextBox
      writer.WriteEndElement() ' ReportItems
      writer.WriteEndElement() ' PageHeader
      writer.WriteEndElement() ' Page
      writer.WriteEndElement() ' ReportSection
      writer.WriteEndElement() ' ReportSections' DataSources
      writer.WriteStartElement("DataSources")
      writer.WriteStartElement("DataSource")
      writer.WriteAttributeString("Name", Nothing, "tbdata")
      writer.WriteStartElement("DataSourceReference")
      writer.WriteEndElement() ' DataSourceReference
      writer.WriteEndElement() ' DataSource
      writer.WriteEndElement() ' DataSources'DataSet
      writer.WriteStartElement("DataSets")
      writer.WriteStartElement("DataSet")
      writer.WriteAttributeString("Name", Nothing, "tbdataset")
      writer.WriteStartElement("Query")
      writer.WriteElementString("DataSourceName", Nothing, "tbdata")
      'writer.WriteElementString("CommandText", Nothing, "/* Local Query */")
      writer.WriteElementString("CommandText", Nothing, "TableDirect")
      writer.WriteEndElement() ' Query'Fields
      writer.WriteStartElement("Fields")
      ForEach fieldName In m_fields
          writer.WriteStartElement("Field")
          writer.WriteAttributeString("Name", Nothing, fieldName)
          writer.WriteElementString("DataField", fieldName)
          writer.WriteElementString("rd:TypeName", fieldName.GetType.ToString)
          writer.WriteEndElement() ' FieldNext
      writer.WriteEndElement() ' Fields' rd datasetinfo
      writer.WriteEndElement() ' DataSet
      writer.WriteEndElement() ' DataSets
      writer.WriteEndElement() ' Report' Flush the writer and close the stream
      writer.Flush()
      stream.Close()
      'Convert to StreamDim myByteArray AsByte() = System.Text.Encoding.UTF8.GetBytes("D:\MyTestReport2.rdlc")
      Dim ms AsNewMemoryStream(myByteArray)
      'Supply Stream to ReportViewer
      ReportViewer1.LocalReport.LoadReportDefinition(ms)
      ReportViewer1.LocalReport.Refresh()When I open rdlc in designer I get following error"Data at the root level is invalid."When I run the aspx I get following error
    An error occurred during local report processing.
    The definition of the report '' is invalid.
    The definition of this report is not valid or supported by this version of Reporting Services.
    The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas.
    Details: Data at the root level is invalid. Line 1, position 1.
    Can anybody guide me?

    Hi Wendy Fu,
    Thanks for your feed back. I could see Microsoft.ReportViewer.ProcessingObjectModel.dll to add as reference to my project. Actually I can open generated rdlc in designer, at run time I get error. I could not make out where is the exact mistake out of three
    options flashed.
    The definition of this report is not valid or supported by this version of Reporting Services.
    The report definition may have been created with a later version of Reporting Services
    or contain content that is not well-formed or not valid based on Reporting Services schemas
    Details: Data at the root level is invalid
    My web config has following references
    <add assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91"/>
    <add assembly="Microsoft.ReportViewer.Common, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91"/>
    May be I have to change these versions to 9 or 10.
    First I will try adding Microsoft.ReportViewer.ProcessingObjectModel.dll .
    Once thanks for your reply.
    Races

  • Leading ? xml version="1.0"? tag when creating / invoking web services

    Hello friends. I'm wondering if anyone has any insight as to why I cannot create
    a fully formed XML document when developing a web service which includes the standard
    <? xml version="1.0" ?> leading tag.
    If I include the leading tag in my XML mapping for a jws method, I am unable to
    compile the service into an ear, getting the following error: "An unexpected
    exception occurred while attempting to process the classes and annotations for
    this Web Service." If I do not include the leading tag, I can compile into an
    EAR file and invoke the web service from a HTTP POST, but I cannot include the
    leading <?xml...> tag in my request. Considering that I'll be asking other vendors
    to submit to my web services and creation of xml documents using DOM or other
    methods automatically generates the <?xml ...>, I'm hoping I'm not going to have
    to tell them to parse out this piece of the files they want to send me. Can anyone
    help?
    Thanks so much!
    CM

    CM,
    I suppose you have set 'http-xml=true' for this to work. For http-xml
    protocol, there is no way to specify the leading <?xml> tag, and hence
    unfortunately the desired functionality cannot be achieved.
    In case, this is very important for you, could you please log a support
    case, and then we can file a bug and ask the Engineering to look into it.
    Thanks,
    Anurag
    "Crackhead Millionaire" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi Anurag -
    Thanks for the response. My problem is that I would like to be able tosubmit
    straight XML (i.e., not SOAP) to a webservice from an application outsideof Weblogic.
    For example, the following code block fails on submission to BEA:
    * Example Simple Integration.
    import java.io.*;
    import java.net.*;
    public class testBEAPost {
    * Null constructor.
    public testBEAPost () {
    super();
    * This method handles creation of a PeopleSoft XML Envelope, wrapping of
    * user input into the envelope, submission of the message to theintegration
    broker
    * and display of the response message to the screen.
    * @created 3.12.2003
    * @param argv java.lang.String[] Standard user entry input
    public static void main(String[] argv) {
    try{
    URL url;
    URLConnection urlConn;
    DataOutputStream printout;
    DataInputStream input;
    // Create the internal XML document which will be to send to BEA.(hardcoded)
    >
    String internalXMLDoc = "<? xml version=\"1.0\"?><newlocationxmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"><setid>WMS</setid><l
    ocationid>1118UG0000</locationid><description>Electric
    UndergroundLocation</description><exceptionemailaddress>[email protected]<
    /exceptionemailaddress></newlocation>";
    >
    // Define the target URL.
    url = newURL("http://167.75.117.20:7001/WebServices/PeopleSoftWebServices/NewLocation
    Service.jws/createLocation");
    >
    // Open the Conection
    urlConn = url.openConnection();
    // Set necessary connection variables.
    urlConn.setDoInput (true);
    urlConn.setDoOutput (true);
    urlConn.setUseCaches (false);
    // Specify the content type.
    urlConn.setRequestProperty("Content-Type", "text/xml");
    // Send POST output.
    printout = new DataOutputStream (urlConn.getOutputStream ());
    printout.writeBytes (internalXMLDoc);
    printout.flush ();
    printout.close ();
    // Get response data.
    input = new DataInputStream (urlConn.getInputStream ());
    String str;
    while (null != ((str = input.readLine())))
    System.out.println (str);
    input.close ();
    } catch (Exception e)
    System.out.println(e);
    If I run this program, I get a java.io.IOException with the serverreturning a
    500 error code. However, if I strip out the leading <? xml version="1.0"?> tag
    and submit to the web service, it works fine. My program set I createdthis example
    for uses DOM to create the document, so I'm actually creating thedocument, getting
    the String value of it, then parsing out the leading tag beforesubmission. My
    problem is that soon I'll be dealing with third parties who may havetrouble generating
    SOAP requests (don't ask), so I'd like to be able to tell them to generatesimple
    XML documents to send to BEA if at all possible.
    Can you assist? Thanks so much.
    "Anurag Pareek" <[email protected]> wrote:
    CM,
    A SOAP message generated by a Workshop web service, when it acts as a
    client
    to another service, always contains the leading <?xml> tag. Here is a
    sample
    of a SOAP message generated by Workshop:
    POST /TestImport/TestAny/TestAny.jws HTTP/1.0
    User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
    Protocol 1.0.3705.0; BEA WLW 7.0)
    SOAPAction: "http://www.openuri.org/hello2"
    Host: localhost
    Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
    Connection: Keep-Alive
    Content-Length: 398
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
    <SOAP-ENV:Body>
    <hello2 xmlns="http://www.openuri.org/">
    <o></o>
    </hello2>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    It seems to me that what you are asking for is already there. Could you
    please elaborate your issue further, probably with a sample of a XML
    message
    which you feel is not accepted by Workshop, but should be.
    Thanks,
    Anurag
    "Crackhead Millionaire" <[email protected]> wrote in message
    news:[email protected]...
    Hello friends. I'm wondering if anyone has any insight as to why Icannot
    create
    a fully formed XML document when developing a web service which
    includes
    the standard
    <? xml version="1.0" ?> leading tag.
    If I include the leading tag in my XML mapping for a jws method, Iam
    unable to
    compile the service into an ear, getting the following error: "Anunexpected
    exception occurred while attempting to process the classes and
    annotations
    for
    this Web Service." If I do not include the leading tag, I can compileinto an
    EAR file and invoke the web service from a HTTP POST, but I cannotinclude
    the
    leading <?xml...> tag in my request. Considering that I'll be askingother vendors
    to submit to my web services and creation of xml documents using DOMor
    other
    methods automatically generates the <?xml ...>, I'm hoping I'm notgoing
    to have
    to tell them to parse out this piece of the files they want to sendme.
    Can anyone
    help?
    Thanks so much!
    CM

  • ?xml version="1.0" encoding="UTF-8"? generates error=unsupported encoding

    Why does the header with encoding set to UTF-8 get rejected by the Oracle XML C++ V2 Parser when one of the features of this version is UTF-8 support?

    Hi
    If I change my document header from <?xml version="1.0" encoding="UTF-8"?> to <?xml version="1.0"?> then it parses without error. Will this situation change if I intall ORACLE_HOME? If so, why do I need to install ORACLE_HOME to get the XML Parser to work?
    Thanks.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by xmlteam ([email protected]):
    Hi,
    Do you have your ORACLE_HOME set up correctly?
    Thanks,
    Oracle XML Team<HR></BLOCKQUOTE>

  • Append messages with out header tag " ?xml version="1.0" encoding="UTF-8"?

    Hi all,
    I am doing file to file scenario.When I use APPEND in the File adapter it is also adding <?xml version="1.0" encoding="UTF-8" ?>
    I need to send a file for every 10 minutes consolidate all files and send at the end of the day.
    <?xml version="1.0" encoding="UTF-8" ?>
    <ID>31154</ID>
    The next time when i send the file with different< ID>31155</ID>
    it should append ignoring <?xml version="1.0" encoding="UTF-8" ?>
    The consolidated file must look like this...
    <?xml version="1.0" encoding="UTF-8" ?>
    <ID>31154</ID>
    < ID>31155</ID>
    Thanks ,
    Srinivas

    Hey
    as pointed out by everyone else,there is no straight way for this,one thing u can do is that create two separate scenarios.
    in first scenario use content conversion on receiver side and keep on appending the text for 10 mins (guess this is ur pooling interval),now since ur using FCC u wont get <?xml version="1.0" encoding="UTF-8" ?>,you will get a flat file on receiver side.
    after 10 mins u can have one more scenario which picks up this flat file and this time use FCC on sender side so that it will convert this flat file to XML,in this way you will get <?xml version="1.0" encoding="UTF-8" ?> only once.
    hope this solves ur problem.
    just make sure that you specify correct polling intervals for both the scenarios.
    thanx
    ahmad

  • PRC: Create Accounting Output shows "xml version="1.0" encoding="UTF-8"

    I m getting Error in the Output of Create Accounting like <?xml version="1.0" encoding="UTF-8" ?>
    Any one have some Clue ...

    Hi,
    It is a bug, and an enhancement request (6354170: ORACLE ALERT LAUNCHING CONCURRENT PROGRAMS WITHOUT XML PUBLISHER TEMPLATES) was created for this issue. Check Metalink and see if the patch is released or not, or you may log a SR to confirm the status of this bug with Oracle support.
    Bug# 6354170 - ORACLE ALERT LAUNCHING CONCURRENT PROGRAMS WITHOUT XML PUBLISHER TEMPLATES
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=BUG&p_id=6354170
    Regards,
    Hussein

  • How to suppress ?xml version = '1.0'? in XML file generation thru PLSQL?

    Hi,
    I am using
    1. dbms_xmlgen.newContext to get the information from table.
    2. After that I am using dbms_lob.createtemporary
    3. Then I am using dbms_xmlgen.getXml
    4. Finally I am using dbms_xmlgen.closecontext
    I am using the above four steps to repatedly taking records from different tables.
    My requirement is : Each and every time I am getting the <?xml version = '1.0'?>.
    How to suppress <?xml version = '1.0'?> ?
    Regards
    Srini

    Hi,
    Use DBMS_XMLGEN.getXMLType to retrieve the XML data into an XMLType variable.
    Then, with getClobVal method, you can convert it to CLOB :
    SQL> DECLARE
      2    v_xml XMLType;
      3    v_lob CLOB;
      4  BEGIN
      5    v_xml := dbms_xmlgen.getXMLType('select * from scott.emp where rownum = 1');
      6    v_lob := v_xml.getClobVal();
      7 
      8    dbms_output.put_line(v_lob);
      9  END;
    10  /
    <ROWSET>
    <ROW>
      <EMPNO>7369</EMPNO>
      <ENAME>SMITH</ENAME>
      <JOB>CLERK</JOB>
      <MGR>7902</MGR>
      <HIREDATE>17/12/80</HIREDATE>
      <SAL>800</SAL>
      <DEPTNO>20</DEPTNO>
    </ROW>
    </ROWSET>
    PL/SQL procedure successfully completed

  • Specifying nested element with two different XML Schema

    Hello,
    I am trying to convert one xml file to another file. I figure data services would be great for this.
    My problem relates to how to have a source xml file with a certain xml schema be transformed to one of a different xml schema. I cannot build the nested elements of the target schema.
    From the source xml I only need four fields. But they need to be nested three levels in the target xml.
    Source
    <DRUG_PRODUCT_LST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <DRUG_ITEM>
          <DRUG_PRODUCT_ID>113083</DRUG_PRODUCT_ID>
          <DIN_PDIN>2317559</DIN_PDIN>
          <HC_BRAND_NAME>PMS-SILDENAFIL</HC_BRAND_NAME>
          <HC_ATC_CODE>G04BE03</HC_ATC_CODE>
       </DRUG_ITEM>
    <DRUG_PRODUCT_LST
    Target
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <CODES>
       <CODE_TYPES>
          <CODE_TYPE>
             <COD_CODE>113083</COD_CODE>
             <COD_DESCR>PMS-SILDENAFIL</COD_DESCR>
             <COD_SOURCE>G04BE03</COD_SOURCE>
             <COD_NPSA>2317559</COD_NPSA>
          </CODE_TYPE>
       </CODE_TYPES>
    </CODES>
    I have tried using an xml pipline to unnest the source, then use a query transform to re-nest for the target. But I do not know how to specify the input schemas.

    Hello,
    I am trying to convert one xml file to another file. I figure data services would be great for this.
    My problem relates to how to have a source xml file with a certain xml schema be transformed to one of a different xml schema. I cannot build the nested elements of the target schema.
    From the source xml I only need four fields. But they need to be nested three levels in the target xml.
    Source
    <DRUG_PRODUCT_LST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <DRUG_ITEM>
          <DRUG_PRODUCT_ID>113083</DRUG_PRODUCT_ID>
          <DIN_PDIN>2317559</DIN_PDIN>
          <HC_BRAND_NAME>PMS-SILDENAFIL</HC_BRAND_NAME>
          <HC_ATC_CODE>G04BE03</HC_ATC_CODE>
       </DRUG_ITEM>
    <DRUG_PRODUCT_LST
    Target
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <CODES>
       <CODE_TYPES>
          <CODE_TYPE>
             <COD_CODE>113083</COD_CODE>
             <COD_DESCR>PMS-SILDENAFIL</COD_DESCR>
             <COD_SOURCE>G04BE03</COD_SOURCE>
             <COD_NPSA>2317559</COD_NPSA>
          </CODE_TYPE>
       </CODE_TYPES>
    </CODES>
    I have tried using an xml pipline to unnest the source, then use a query transform to re-nest for the target. But I do not know how to specify the input schemas.

  • How to change XML version in outbound XML file generated in XI

    Hi, I am getting following two records in the beginnning of my out bound XML file.
    <?xml version="1.0" encoding="utf-8" ?>
    <ns0:MT_WPUUMS01_Salesdata xmlns:ns0="http://ws-sapretail-pos.com/salesdata">
    Is there any control in XI to modify these two lines, in outbound files.
    Also, for inbound files, is there any way to process messages successfully, even if XML files from other systesm comes in different formats (xml version tag and nso tag lines)

    <?xml version="1.0" encoding="utf-8" ?>
    <ns0:MT_WPUUMS01_Salesdata xmlns:ns0="http://ws-sapretail-pos.com/salesdata">
    these two lines will be added when you create the  Message type name
    MT_WPUUMS01_Salesdata  is the message type name
    http://ws-sapretail-pos.com/salesdata"> is the name of your namespace......
    so if you want to chage these two lines in each XML build your MT and namespace accordingly.......
    even when you are importing the XML from o ther systems, you dnt have to worry about these tages as you import them in external definitation and select them only in message interface........should not be a problem if you import the XML from other systems
    whole conecpt is when you add these two lines it will convert the XSD to XML so when you have the XML form other system you only need to crer ate the WSDL out of it...
    let me know if i am not clear or if i understood your question wrong....

Maybe you are looking for

  • Abend Bad Resource Tag passed to LSLReturnRcvECB

    Server with 6.5 SP7 GRW 7.04 +FTF , BM 3.8 sp5 , GWIA WEBACC , ARCSERVE R11 SP3 today had 2 Abends at 13:37 and 16:12 for the same reason , never had this reason before . Does this happen elsewhere? Any idea as to reason or cause ? Possible fixes suc

  • Powerbook G4 as HTPC to 4:3 CRT TV / app and box recommendation?

    Hi-- My first post here.  I've done quite a bit of research here and elsewhere, and I still can't figure out the best solution for my particular setup. I'm getting a new MacBook Pro very soon, and my 1.5 Ghz Powerbook G4 is still alive and (sort of)

  • Best practices of integration with SAP Netweaver

    Hi All, I'm totally new to SAP Netweaver but I have a task to integrate our system with SAP ECC (R/3). We are using SAP Netweaver 6.4. The goal of integration is to provide for user list of available modules (Sales and Distribution, Human Resource, P

  • Editing music info in itunes

    I recently bought a new computer and reloaded my itunes into it. I had to deauthorize all of my other computers to get it to work. Everything is fine now except I cannot edit any of the info of a song, such as title or artist. When I go into get info

  • Rendering exception

    Hi, I am calling a webservice in Adobe form. The log - - Processing exception during a "Render" operation.    Request start time: Wed Jun 02 11:04:09 EST 2010 com.adobe.ProcessingException: CORBA Connection to XMLForm failed, please verify the binari