CRM Designer Unable to parse CLD XML file

I am unable to use the CRM designer to load the CLD files from CRM. Each time I try, I get "Error retrieving and parsing XML file". I save the file locally and open using notepad and these are the contents:
0001
http://sethnn058.mynetwork.ds.BLAHBLAH.net:8000/sap/bc/bsp/sap/crm_bsp_bab_dis/bpserv.htm?sap-client=200&cmd=getScreen&lang=E&appl=CRMD_SALQ&blview=SLS_REP&event=ZBT_ADDITIONAL_R3&scrpos=4&scrvar=&creq=VAQK901374&wreq=VAQK901372&xchg_id=595A1E7995AC2E45BC1723BB1260BF66
http://sethnn058.mynetwork.ds.BLAHBLAH.net:8000/sap/bc/bsp/sap/crm_bsp_bab_dis/bpserv.htm?sap-client=200&cmd=saveScreen&lang=E&appl=CRMD_SALQ&blview=SLS_REP&event=ZBT_ADDITIONAL_R3&scrpos=4&scrvar=&creq=VAQK901374&wreq=VAQK901372&xchg_id=595A1E7995AC2E45BC1723BB1260BF66
http://sethnn058.mynetwork.ds.BLAHBLAH.net:8000/sap/bc/bsp/sap/crm_bsp_bab_dis/bpservexit.htm?sap-client=200&cmd=endSession&lang=E&appl=CRMD_SALQ&blview=SLS_REP&event=ZBT_ADDITIONAL_R3&scrpos=4&scrvar=&creq=VAQK901374&wreq=VAQK901372&xchg_id=595A1E7995AC2E45BC1723BB1260BF66
It's definitely not a XML file. What could the issue be??
Thanks!!

jtahlborn wrote:
My guess is that it is a namespace issue. The ShipmentOrder element has no namespace, but the Voyage element has the namespace "http://www.xyz.com//CDM/2009/v1.0".
Yes, indeed. The posted error message does say that *"":Voyage* is one of the possible expected types, which must mean a Voyage element in no namespace.

Similar Messages

Opatch error 'Unable to parse the xml file'

Hi there,
I am new to installing patches on Oarcle and I need to install patch 12375678 on my windows system, Oracle 11.2.0.2.
I have followed the instructions in the readme.txt file, but got this error and I have not come across anywhere on the web that explain how I could fix it.
Could you please advise?
Thanks
C:\>set oracle_home=C:\oracle\product\11.2.0\dbhome_1
C:\>echo %oracle_home%
C:\oracle\product\11.2.0\dbhome_1
C:\>cd C:\oracle\product\11.2.0\dbhome_1\inventory\oneoffs\12375678
C:\oracle\product\11.2.0\dbhome_1\inventory\oneoffs\12375678>opatch apply
Invoking OPatch 11.2.0.1.1
Oracle Interim Patch Installer version 11.2.0.1.1
Copyright (c) 2009, Oracle Corporation. All rights reserved.
Oracle Home : C:\oracle\product\11.2.0\dbhome_1
Central Inventory : C:\Program Files\Oracle\Inventory
from : n/a
OPatch version : 11.2.0.1.1
OUI version : 11.2.0.2.0
OUI location : C:\oracle\product\11.2.0\dbhome_1\oui
Log file location : C:\oracle\product\11.2.0\dbhome_1\cfgtoollogs\opatch\opatch2
012-05-21_15-28-52PM.log
Patch history file: C:\oracle\product\11.2.0\dbhome_1\cfgtoollogs\opatch\opatch_
history.txt
ApplySession applying interim patch '12375678' to OH 'C:\oracle\product\11.2.0\d
bhome_1'
Running prerequisite checks...
OPatch detected non-cluster Oracle Home from the inventory and will patch the lo
cal system only.
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '12375678' for restore. This might take a
while...
Backing up files affected by the patch '12375678' for rollback. This might take
a while...
Patching component oracle.rdbms, 11.2.0.2.0...
Copying file to "C:\oracle\product\11.2.0\dbhome_1\rdbms\xml\xsl\kuexttbl.xsl"
Patching component oracle.rdbms.dbscripts, 11.2.0.2.0...
Copying file to "C:\oracle\product\11.2.0\dbhome_1\rdbms\admin\prvtbpd.plb"
Copying file to "C:\oracle\product\11.2.0\dbhome_1\rdbms\admin\prvtbpw.plb"
ApplySession adding interim patch '12375678' to inventory
Interim Patch metadata parsing failure... 'Unable to parse the xml file.'
ApplySession failed: ApplySession failed in system modification phase... 'Unable
to create patchObject'
OPatch will attempt to restore the system...
Restoring the Oracle Home...
OPatch was able to restore your system. Look at log file and timestamp of each f
ile to make sure your system is in the state prior to applying the patch.
OPatch failed with error code = 73

your actions.xml must not be able to be read.
open it in notepad yourself to see does it open, if so its not corrupt, if doesnt open download patch again.
More then likely will be fine so try locate the patch in a shorter home path, like c:\patches\12375678 and see does it install from there.
Only other thing I can think of is the main inventory.xml, usually c:\program files\oracle\inventory\inventory.xml
try notepad with that too.

Unable to parse the xml file

I have a xml file with the xsd ,when i try to parse it using Xerces2-j i am getting an error msg like this
XML Document has Error:true cvc-complex-type.2.4.a: Invalid content was found starting with element 'Voyage'. One of '{"":Parties, "":Voyage, "":Carrier, "":Ports, "":Commodities}' is expected.
and mu xml file is
<?xml version = "1.0" encoding = "UTF-8"?>
     <ShipmentOrder
          AllocationNumber = "AL12345"
          CustomerReferenceNumber = "FORD123"
          OrderType = "NEW"
          ShipmentNumber = "USEDN12345"
          ShipmentType = "IMPORT">
     <Parties
          PartyName = "XYZ INC"
          PartyNumber = ""
          PartyType = "Shipper">
     <Address
          Address1 = "1234"
          Address2 = "Avenue Road"
          Address3 = ""
          City = "DETROIT"
          Country = "USA"
          State = "MI"
          ZIPCode = "098081"
          xmlns = "http://www.xyz.com//CDM/2009/v1.0"/>
     <Contact
          ContactPerson = "John Smith"
          ContactPoint = "7324120987"
          ContactType = "Work Phone"
          xmlns = "http://www.xyz.com//CDM/2009/v1.0"/>
     </Parties>
     <Voyage
          EndDate = ""
          FlagShipCountry = "INDIA"
          LlyodsCode = "12345467"
          StartDate = ""
          VesselCode = "PAZ"
          VesselName = "BLUESHIP"
          VoyageMode = "OCEAN"
          VoyageNumber = "NA2345-PAZ"
          xmlns = "http://www.xyz.com//CDM/2009/v1.0"/>
     <Carrier CarrierName = "XYZ OCEAN CARRIER" SCAC = "XYZO" TaxID = "" xmlns = "http://www.xyz.com//CDM/2009/v1.0"/>
     <Ports
          Code = "USBAL"
          Name = "BALTIMORE"
          Terminal = "TERMINAL1"
          TerminalName = "DUNDALK"
          Type = "LOAD">
          <Berth
          Code = "USBAL1"
          Name = "ATLANTIC TERMINAL"
          PierNumber = "19"
          Type = "LOAD"/>
     </Ports>
     <Ports Code = "BEZEE"
          Name = "ZEEBRUGE"
     Terminal = "TERMINAL C"
     TerminalName = "MASTER STEO"
     Type = "DISCHARGE">
          <Berth Code = "BEZEE4"
     Name = "BELGIAN TERMINAL"
     PierNumber = "12"
     Type = "DISCHARGE"/>
     </Ports>
     <Commodities BarCode = "123456" CommodityClass = "AUTO" CommodityCode = "8703000" CommodityDescription = "FORD 4X4 PICKUP TRUCK" CommodityType = "CAR" LadingLineItem = "1" LadingQuantity = "1" MarksandNumbers = "123456">
          <Weight UnitOfMeasurement = "KGS" UnitOfWeight = "GROSS" Weight = "1234"/>
          <Measurement CubicDimensions = "8" Height = "1.65" Length = "5" UnitOfMeasurement = "FEET" Width = "3"/>
          <ManufacturerDeatils CommodityDescription = "FORD 4X4 PICKUP TRUCK" MakeCode = "FORD" ManufacturerName = "FORD MOTOR CO" ModelCode = "TAURUS" ModelType = "LX" ModelYear = "2009"/>
          <HazardousDetails CalssificationDescription = "12" ClassificationCode = "124" ClassificationCodeQualifier = "W" FlashpointTemperature = "23" FlashpointUnitOfMeasurement = "C" MarinePollutant = "Y" MaterialCode = "N" MaterialDescription = "N" MaterialsPage = "N" PackagingGroupCode = ""/>
          <EquipmentDetails EquipmentNumber = "1234" EquipmentType = "CONTAINER"/>
     </Commodities>
</ShipmentOrder>
can any one help me out with the problem

jtahlborn wrote:
My guess is that it is a namespace issue. The ShipmentOrder element has no namespace, but the Voyage element has the namespace "http://www.xyz.com//CDM/2009/v1.0".
Yes, indeed. The posted error message does say that *"":Voyage* is one of the possible expected types, which must mean a Voyage element in no namespace.

Can someone help me with a problem of parsing an XML file?

Hello,
I'm having some problems parsing an xml file. I get a SAXNotSupportedException when setting a property value.
Here is the piece of code where I have the problem:
SAXParserFactory spf = SAXParserFactory.newInstance();
spf.setNamespaceAware(true);
SAXParser saxParser = spf.newSAXParser();
XMLReader xmlReader = saxParser.getXMLReader();
DefaultHandler defHandler = new DefaultHandler();
xmlReader.setProperty("http://xml.org/sax/properties/lexical-handler", defHandler);
and the log is:
Problem with the parser org.xml.sax.SAXNotSupportedException: PAR012 For propertyID "http://xml.org/sax/properties/lexical-handler", the value "org.xml.sax.helpers.DefaultHandler@4ff4f74a" cannot be cast to LexicalHandler.
http://xml.org/sax/properties/lexical-handler org.xml.sax.helpers.DefaultHandler@4ff4f74a LexicalHandler
I've been working on this problem but I can't find the error.
Does anyone have an idea of what to do to solve it?
Thanx in advance,
M@G

before deciding which XML technology to use, you should see if your application fit in the category below:
use SAX:
1. The XML file is rather large (30 or 40+ MB)
2. I don't need the xml document in memory. I will parse the document and store the data in my own object.
use DOM or JDOM
1. The XML file is relatively small (less than 30 MB) or I can increase the runtime memory for larger xml file.
2. I will need to walk up and down the xml document tree severals time.
3. My application is in Java and it's not going to be rewritten in C++, etc (use JDOM)
NOTE:
JDOM is rather easier to use (for Java developer), but it's not an www.org.com standardlized xml parser.
personally, i like JDOM for traversing the DOM.

Parsing of xml file in oracle stored procedure on linux server

We have an XML file in the "/database/stats/dev/xml1/" path and tried to parse the file using the below code :
p := xmlparser.newParser;
xmlparser.setValidationMode(p, FALSE);
-- xmlparser.setErrorLog(p, errfile);
xmlparser.setBaseDir(p, dir);
xmlparser.parse(p, inpfile);
doc := xmlparser.getDocument(p);
xmlparser.freeParser(p);
The above procedure is throwing below mentioned exception at "xmlparser.parse(p, inpfile);".
SQLCODE: ORA-31001
SQLERRM: ORA-31001: Invalid resource handle or path name "/xml1.dtd"
The xml file contains the following line, which is giving an error, while parsing the xml file.
<!DOCTYPE CCIOrder SYSTEM "xml1.dtd">
Directory Structure:
OWNER DIRECTORY_NAME DIRECTORY_PATH
SYS XML1 /database/stats/dev/xml1

you'll need to use server-side code to check the xml file names in that folder, return that list to flash and display the list to the user.
or, if you can get by presenting a hard-coded list of xml files, you won't need any server-side coding.

How to Parse an XML file using SAXParser in java.

Hi all
Am a bit new to XML files and have no idea about SAXParsers ... Now my problem is to parse this XML file below
<?xml version="1.0" encoding="UTF-8"?>
<sc:memory_segmentation xmlns:sc="sc_memory_segmentation.xsd">
   <sc:architecture name="MPC55xx"></sc:architecture>
   <sc:derivative name=""></sc:derivative>
   <sc:configuration name=""></sc:configuration>
   <sc:memory name="Internal ROM" type="ROM">
      <sc:area-list>
         <sc:area name="Bootmanager" type="BOOTMANAGER">
             <sc:segment-list>
               <sc:segment name="ROM page 1">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
             </sc:segment-list>
         </sc:area>
         <sc:area name="Bootloader SWE" type="BOOTLOADER">
             <sc:segment-list>
               <sc:segment name="ROM page 2">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="ROM page 3">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
            </sc:segment-list>
         </sc:area>
         <sc:area name="Application SWE 1" type="APPLICATION">
            <sc:segment-list>
               <sc:segment name="ROM page 4">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="ROM page 5">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="ROM page 6">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="ROM page 7">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
            </sc:segment-list>
         </sc:area>
         <sc:area name="Application SWE 2" type="APPLICATION">
            <sc:segment-list>
               <sc:segment name="ROM page 8">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
            </sc:segment-list>
         </sc:area>
         <sc:area name="Application SWE 3" type="APPLICATION">
            <sc:segment-list>
               <sc:segment name="ROM page 9">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
            </sc:segment-list>
         </sc:area>
         <sc:area name="Application SWE 4" type="APPLICATION">
            <sc:segment-list>
               <sc:segment name="ROM page 10">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
            </sc:segment-list>
         </sc:area>
      </sc:area-list>
   </sc:memory>
   <sc:memory name="Internal RAM" type="RAM">
      <sc:area-list>
         <sc:area name="RAM" type="RAM">
            <sc:segment-list>
               <sc:segment name="RAM page 1">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="RAM page 2">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="RAM page 3">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="RAM page 4">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="RAM page 5">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
            </sc:segment-list>
         </sc:area>
      </sc:area-list>
   </sc:memory>
   <sc:memory name="Internal EEPROM" type="EEPROM">
      <sc:area-list>
         <sc:area name="EEPROM" type="EEPROM">
            <sc:segment-list>
               <sc:segment name="EEPROM page 1">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="EEPROM page 2">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="EEPROM page 3">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="EEPROM page 4">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
               <sc:segment name="EEPROM page 5">
                  <sc:start></sc:start>
                  <sc:end></sc:end>
               </sc:segment>
            </sc:segment-list>
         </sc:area>
      </sc:area-list>
   </sc:memory>
</sc:memory_segmentation> And from this file I need to make 3 Hashtables out of it one for ROM , RAM and EEPROM containg Segment information i.e. Segment start and end addresses and Area type of the segment....
If anyone could at least guide me with the basic commands and structure of the parser it would be really really great ...
Thanks a lot
Anisha

Normally if you have no idea about X, the first thing you should do is google "X tutorial". You will find plenty of them out there. And the advantage is, they are better written than whatever we spend two minutes throwing together here. Not to mention that it saves us the two minutes.
But if you have specific questions with your SAX parser when you get it going, then ask them here. Actually, ask them in the XML forum here, not this one.

Parsing an XML file

I've written a program which is partly responsible for parsing an XML file that can be found on the web. I appear to be accessing the XML file correctly, but when I try to parse it I am running into a problem. I try to create a List object that contains all of the children of the root element. The code looks like this:
Document doc = parser.build(xmlFile);
Element root = doc.getRootElement();
List rootChildren = root.getChildren();But I get an error that say that "the type List is ambiguous". I am importing java.util.*. I am trying to do this exactly like a few examples I found on the web, but I can't seem to get past this issue. What do I need to keep Eclipse from telling me that List is not an ambiguous type.

Maybe you haveimport java.util.*;
import java.awt.*;Both packages contains a List class.
In that case, the compiler doesn't know which one you're talking about.
If you don't need the java.awt.List class here, try not to import it.
If you need it, use the fully qualified class name in your code.

Unable to open the XML files in Nakisa

Hi Gurus,
We are unable to open certain XML files in Nakisa. They show up as encrypted in the notepad or fail to open using the XML Marker. The files in question are
AppResources.xml
LoginConfiguration_SAP_Standard
LoginConfiguration_Anonymous
Purpose: We want to enable the SSO with the portal . We have checked the radio button but nakisa does not recognize the SSO ticket from the portal (Any folder in Nakisa where we need to place the Portal ticket?)
Also we want Nakisa to show the org chart for the logged in user. Luke had mentioned that some changes need to be made in the AppResources.xml (hope i correctly remember this) and we were looking to make these changes (rather try out.. any pointers please..?)
Thanks and Regards,
Arun E V

Hi Arun,
These files are encrypted. If your organisation is a partner with Nakisa you can obtain the decrypter from them.
Portal SSO works without any configuration directly in the XML files. If you are getting an error stating that the Portal ticket cannot be interpreted then your configuration is not correct. In your URL iView you need to ensure the fully qualified domain name (FQDN) is used for the application URL. In the Administrator Console you need to ensure you enter the system details (Host, Sys Nr and Client) for the backend system which holds your SSO ticket for that Portal. You need to use FQDN here too.
There is additional security configuration that can be done in the XML files but SSO will still work with just the Administrator Console configuration.
I hope that helps!
Luke

Parse exisitng xml file and recreate another xml file with different struct

Is it possible in java using dom parser to parse an exisiting xml file and recreate a new xml file from data obtained by parsing old xml file.
I checked on old forum threads and everywhere either parsing xml file has been explained or creating new xml file from scratch has been shown.
Any examples/guidance will be appreciated....

The general process is:
Document dom1 = ... // the parsed document
Document dom2 = ... // new document constructed on the fly
Node nD1 = ... // some random node found in dom1
// copy the node from dom1 and associate with dom2
Node nD2 = dom2.importNode(nD1, true);
// ... treat nD2 as a node which can now be inserted into dom2 ...
Node otherD2 = ... // some other node already in dom2
otherD2.appendChild(nD2);Note, in this example the nD1 node is copied (including any sub-nodes) into a new node, nD2. You can alternately move the node from one Document to another using Document.adoptNode(), however this may fail (see the javadoc).

Parsing a XML file using Jdom-Problem.

Hi all,
I am reposting it as I was told to format the code and send it again.
I am trying to parse a xml file using a jdom java code.This code works fine if I remove xmlns attribute in the root element. (I get the expected result) .If the "xmlns" attribute is put in the xml as it should be then the parsing and retrieving returns null. Please tell me how to fix this issue.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Xml
<process name="CreateKBEntryService" targetNamespace="http://serena.com/CreateKBEntryService" suppressJoinFailure="yes" xmlns:tns="http://serena.com/CreateKBEntryService" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:nsxml0="http://localhost:8080/axis/services/CreateKBEntryService" xmlns:nsxml1="http://DefaultNamespace" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/">
<partnerLinks>
<partnerLink name="client" partnerLinkType="tns:CreateKBEntryService" myRole="CreateKBEntryServiceProvider"/>
<partnerLink name="CreateKBEntryPartnerLink" partnerLinkType="nsxml0:CreateKBEntryLink" partnerRole="CreateKBEntryProvider"/>
</partnerLinks>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
Java:
import java.io.*;
import java.util.*;
import org.jdom.Document;
import org.jdom.Element;
import org.jdom.input.SAXBuilder;
public class sample1 {
public static void main(String[] args) throws Exception {
// create a XML parser and read the XML file
SAXBuilder oBuilder = new SAXBuilder();
Document oDoc = oBuilder.build(new File("**xml file location**"));
Element root = oDoc.getRootElement();
System.out.println(root.getName());
String tgtns= root.getAttributeValue("targetNamespace");
System.out.println("tgt ns "+ tgtns);
List list= root.getChildren("partnerLinks");
Iterator it1= list.iterator();
System.out.println("Iterator 1 - "+list.size());
while(it1.hasNext()){
Element partnerlinks = (Element)it1.next();
List list2= partnerlinks.getChildren("partnerLink");
System.out.println("iterator 2 - "+list2.size());
}~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Result:
Without Xmlns in xml file(Expected and correct output)
process
tgt ns http://serena.com/CreateKBEntryService
Iterator 1 - 1//expected and correct result that comes when I remove xmlns attribute from xml
iterator 2 - 2
Result with xmlns:
process
tgt ns http://serena.com/CreateKBEntryService
Iterator 1 - 0 //instead of 0 should return 1

LOL
This is what you get for working 12 hours straight....
I changed:
xmlObject["mydoc"]["modelglue"]["event-handlers"]["event-handler"][i].xmlAttrib utes["name"]<br>
to:
#mydoc["modelglue"]["event-handlers"]["event-handler"][i].xmlAttrib utes["name"]#<br>
xmlObject is the name of my xml object in memory, and then you reference from the root of the xml doc down the chain.
Sorry for the inconvenience,
Rich

Unable to generate users.xml file

Hi All,
I have installed OCS 10.1.2.0.0.and applied the cumulative patchset and now on OCS 10.1.2.3.0
Now i am trying to migrate users and their mail box from exchange 5.5 running on Windows NT 4 server.
I have installed the esmigration tool on a machine running Windows XP SP2, Outlook 2003 client installed. I ran the tool and successfully created the system profile. Once done when i try extract users which should generate a users.xml file, i get an error saying "Unable to generate users.xml" file. When i look at the log file i can see the error which says invalid domain which is not true. The domain name is right and i have repeated the process more than 10 times, but still keep getting the same error. I tried using IMPA to IMAP as well as with MBOX , but still the same error. Has anyone seen such a behavior ?
So i tried to choose plan B. As i do not have too many users i decided to export the users mail box as a pst file and then import it. This is not a problem, but what i do not know is that what do i need to do to enable coexistence mode on exchange, meaning when an email arrives, it first goes to exchange and then forwards a copy to OCS.Please note on my research i have found some notes on how to do this on exchange 2000 on a windows 2000 server with AD, but i couldn't find anything for Exchange 5.5 on NT4.
Any assistance on this would be very helpful.
Regards,
Dipak

Hi Dipak,
If you do the migration from the Windows 2000 machine with outlook 2000 installed, and connected to Exchange 5.5 via an admin profile, then you will not see this issue.
In case, it is not possible for you to move to new machine where above said environment exists, then you can request for a patch of migration tool that has fix for this issue. Please send an email to [email protected] or [email protected], for the fixed version.
For your co-existence query: Please make use of alternate-recipient setup that exists on exchange 5.5 user properties. So, the emails will be routed to both exchange, and ocs server mailboxes of that user.
If you have any further queries please send an email to [email protected]
Thanks,
Venkat

How to parse a XML file

I am a new learner to XML & JAVA,I dont't know how to parse the XML file using JAXP,Who can tell me,Who can write an Example?
thx
Best Regards.

Using the SAXParser in JAXP the parsing of the XML file is event driven.
Instantiate the parser:
SAXParserFactory factory = SAXParserFactory.newInstance();
SAXParser parser = factory.newSAXParser();
InputSource is = new InputSource(new FileReader(theXML));call the parse method:
parser.parse(is, this);The following events are fired as the parser works through the XML public void startElement(String namespaceURI, String localName, String qName, Attributes atts) throws org.xml.sax.SAXException
public void endElement(String namespaceURI, String localName, String qName) throws org.xml.sax.SAXException
characters(char[] ch, int start, int length)etc.
You write what you want within each of these sections to handle the structure of your data. Keep in mind SAX is useful only when you know the structure of your XML.

Can Document Builder parse an XML file from a URL?

Warning: Java newbie here...
My problem is that I am able to parse an XML file if it is copied into my project, but not if it is a full URL. Here is what I got so far, that works.
import java.io.*;
import java.net.*;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
try {
    File file = new File("path/to/file.xml");
    DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
    DocumentBuilder db = dbf.newDocumentBuilder();
    Document doc = db.parse(file);
    doc.getDocumentElement().normalize();
    NodeList nodeLst = doc.getElementsByTagName("Names");
    for (int s = 0; s < nodeLst.getLength(); s++) {
        Node parentNode = nodeLst.item(s);
        if (parentNode.getNodeType() == Node.ELEMENT_NODE) {
            Element parentElmnt = (Element) parentNode;
            NodeList nameElmntLst = parentElmnt.getElementsByTagName("Name");
            //etc.
} catch (Exception e){
    e.printStackTrace();
}So building off of this I have tried to parse an input stream like this:
URL url = new URL("http://example.com/file.xml");
InputStream is = url.getInputStream();
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
Document doc = db.parse(is);which gives me the following error
[Fatal Error] :-1:-1: Premature end of file.
LOG: HME receiver connected
org.xml.sax.SAXParseException: Premature end of file.
I also even tried to write the file locally like this:
URL url = new URL("http://example.com/file.xml");
HttpURLConnection urlcon = (HttpURLConnection) url.openConnection();
urlcon.connect();
InputStream is = urlcon.getInputStream();
File file = new File("path/to/file.xml");
OutputStream out = new FileOutputStream(file);
byte buf[] = new byte[1024];
int len;
while((len=is.read(buf))>0)
    out.write(buf,0,len);
out.close();
is.close();
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
Document doc = db.parse(file);This gives the same error.
If anyone can point me in the right direction I would forever thankful. I've tried search Google and the Sun forums, but haven't quite found the solution. I think it is because I need to try something else completely. Thank you for reading.
~~~~ Jeremy

jmose wrote:
If I copy the page, it works as shown in the first code block. In the third codeblock the file is never even created, so I cannot tell if that works or not.So: having the parser access the URL fails, and having some other Java code access the URL also fails in the identical way? That suggests the problem is simply accessing the URL via Java code. Presumably when you downloaded the data from the URL, you used a browser to do it and not wget or something like that?

Error "Cannot parse appinfo xml file."

Periodically my users are getting the error below when trying to launch BPC for Excel:
"Cannot parse appinfo xml file."
Seems this file is getting corrupted somehow. If I remove the file from their citrix profile and they relogin, the file is recreated and then they can launch BPC for Excel. Until then though, they get this error and sometimes it says the Web App server is unavailable, when it indeed is available.
Anyone experience this, or have any ideas as to the problem?
Thanks,
Greg

Please notice that inquiries related to BPC topics should now be posted to dedicated forums.
Business Planning and Consolidations, version for SAP NetWeaver
<a class="jive_macro jive_macro_community" href="" __jive_macro_name="community" modifiedtitle="true" __default_attr="2065"></a>
Business Planning and Consolidations, version for the Microsoft Platform
<a class="jive_macro jive_macro_community" href="" __jive_macro_name="community" modifiedtitle="true" __default_attr="2066"></a>
Please adjust any bookmarks or shortcuts you may have set previously to point to this forum.
Best regards,
[Jeffrey Holdeman|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/jeffrey+holdeman]
SAP BusinessObjects
Enterprise Performance Management
Regional Implementation Group

How quickly parse big XML file (60 MB) ???

How quickly parse big XML file (60 MB) ???

I assume you mean load it into XML DB ?. Fundamentally your document is about the upper limit for 9.2.x. I would strongly recommend trying to break it up into a set of smaller documents using a SAX parser before trying to load it into XML DB. In 10g it should be possible to load much bigger documents than this.

CRM Designer Unable to parse CLD XML file

Similar Messages

Maybe you are looking for