Failed To Parse Wsdl Document Xml Parser Error Createxmldoc

Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus Dennis Stevenson bracke Craig Borysowich DukeGanote Richard PCMag mircea_luca Nikki Klein iudithm AbhaiTripathi knowscognosdoi Clinton Jones Iqbalyk bluesguyAZ59 COMPANIES Dell Software Panaya Inc. Oracle VAI View All Topics View All Members View All Companies Toolbox for IT Topics PeopleSoft Groups Ask a New Question PeopleTools A forum where peers share technical expertise, solve problems, and discuss issues related to PeopleTools. Home | Invite Peers | More PeopleSoft Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. PeopleSoft Problems Importing a WSDL Jeff Dunnett asked Apr 23, 2012 | Replies (5) I am trying to import a WSDL (see below) into PeopleSoft via PIA. When I attempt import it using HTTPS I get the following message: Integration Gateway - External System Contact Error (158,10721) Integration Gateway was not able to contact the external system. The network location specified may be incorrect, or the site is permanently or temporarily down. When I attempt to import it using HTTP I get the following message: Failed to parse WSDL document.XML parser error CreateXmlDoc (159,5) (0,0) I have successful import the WSDL into other WSDL importing tools. So this seems to be how this WSDL is interacting with PeopleSoft. The WSDL - http://peoplesoft.ittoolbox.com/groups/technical-functional/peopletools-l/peoplesoft-problems-importing-a-wsdl-4748458 you continue to receive this error after following the steps below, it is most likely that some of the configuration were either not done or you are behind a firewall that preventing you from going out of the network. Configure the integration broker by changing the https://addsrikanth.wordpress.com/2008/08/25/peoplesoft-integration-broker-and-web-services-updated/ gateway URL.   2.Activate the IB domain. When PeopleSoft is initially installed you will see a lot of invalid IB domains.You can flush out the invalid entries by purging the domain status. 3. When the integration gateway is configured you should see the target connectors in the gateway configuration.       4.Configure the services schemaname and target location. Please note the "Service" in the listening connector. This is PeopleSoftServiceListeningConnector.   5.Configure the service using the web service consume wizard. 7.Create a page,record etc to test the integration.   8.Enter the following code to test the integration we created. Local SOAPDoc &SOAPDoc;     Local XmlNode &lnodeEnvNode; &SOAPDoc = CreateSOAPDoc(); &SOAPDoc.AddEnvelope(%SOAP_Custom); &lnodeEnvNode = &SOAPDoc.EnvelopeNode; &lnodeEnvNode.AddAttribute("xmlns", "urn:GoogleSearch"); &SOAPDoc.AddBody(); &SOAPDoc.AddMethod("doGoogleSearch", 1); &SOAPDoc.AddParm("key", "eDZYCx9QFHIXI/xojJqrYspYi1Geo74o"); &SOAPDoc.AddParm("q", "BPEL"); &SOAPDoc.AddParm("start", "0"); &SOAPDoc.AddParm("maxResults", "5"); &SOAPDoc.AddParm("filter", "true"); &SOAPDoc.AddParm("restrict", ""); &SOAPDoc.AddParm("safeSearch", "false"); &SOAPDoc.AddParm("lr", ""); &SOAPDoc.AddParm("ie",

here for a quick overview of the site Help Center Detailed answers to http://stackoverflow.com/questions/3133317/coldfusion-web-service-error-unable-to-parse-wsdl-as-an-xml-document any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack failed to Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Coldfusion web service error, “Unable to parse WSDL as an XML document.” up vote 1 down vote favorite I'm trying to get a web service running CF9 IIS7 failed to parse testpage.cfm #foo# test.cfc The error message is Unable to parse WSDL as an XML document. Parsing error: Fatal Error: URI=null Line=83: The element type "img" must be terminated by the matching end-tag "". It is recommended that you use a web browser to retrieve and examine the requested WSDL document to ensure it is correct. The error occurred in C:\inetpub\wwwroot\cf\testpage.cfm: line 4 2 : 6 : I can go to https://nww.eastwickpark.nhs.uk/cfcs/test.cfc in the browser and get the component info page OK. If I browse to http://nww.eaastwickpark.nhs.uk/cfcs/test.cfc?wdsl I get