|
Mike, WRKLNK 'fully_qualified_path_to_xml_file' Then take option 8 to display attributes. We have had some problems with different editors putting invisible 'garbage' characters into file and wreaking havoc. I don't know anything about TextPad though. I always use wordpad to edit, and have not had any problems (always save as plain text). Frances Stewart WebSphere Application Server for iSeries 400 IBM Rochester Mike Perez <MPEREZ@tycoint.com>@midrange.com on 03/21/2001 01:58:46 PM Please respond to JAVA400-L@midrange.com Sent by: owner-java400-l@midrange.com To: "'JAVA400-L@midrange.com'" <JAVA400-L@midrange.com> cc: Subject: RE: XMLConfig Tool Frances, I tried the example given, but I got the same errors as before. Unfortunately, I don't know how to check the code page of the .xml file, but I used a text editor(Textpad) to create it. Do I need to change anything in the xmlconfig.dtd file? Seems the last couple of errors point to something not set up in the dtd file. Thanks, Mike -----Original Message----- From: Frances Stewart [mailto:francess@us.ibm.com] Sent: Wednesday, March 21, 2001 11:08 AM To: JAVA400-L@midrange.com Subject: Re: XMLConfig Tool The correct XML file contents to stop your app server is (see http://www-1.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/ docs/as400v35std/docs/admshdwn.html for example as well): <?xml version="1.0"?> <!DOCTYPE websphere-sa-config SYSTEM "$XMLConfigDTDLocation$$dsep$xmlconfig.dtd" > <websphere-sa-config> <node name="GRIN400" action="locate"> <application-server name="grinnell" action="stop"> </application-server> </node> </websphere-sa-config> Make sure your xml file's code page is 819 (ASCII) also. Frances Stewart WebSphere Application Server for iSeries 400 IBM Rochester Mike Perez <MPEREZ@tycoint.com>@midrange.com on 03/21/2001 10:03:48 AM Please respond to JAVA400-L@midrange.com Sent by: owner-java400-l@midrange.com To: "Java400 (E-mail)" <java400-l@midrange.com> cc: Subject: XMLConfig Tool I'm trying to start and stop a particular app server within WAS 3.5.2 Std Ed. using the XML Config tool, but have been unsuccessful. I start the qsh session, change dir to the bin directory, type the import command that is supposed to stop the app server, but instead I receive the following error messages, and I'm not sure where I'm going wrong. I haven't changed the dtd file, but I've done a full export, and it seems to match the import file (for what I need). I've also removed the <virtual-host> lines from the import file, with the same results. Any help would be appreciated. Mike Perez $ cd /QIBM/ProdData/WebASAdv/bin $ XMLConfig -adminNodeName GRIN400 -import grinnell.xml No -instance value specified, using default file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 57: Whitespace expected. file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 143: Attribute, "name", is not declared in element, "virtual-host". file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 165: Attribute, "action", is not declared in element, "virtual-host". file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 188: Attribute, "name", is not declared in element, "node". file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 216: Attribute, "action", is not declared in element, "node". file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 254: Attribute, "name", is not declared in element, "application-server". file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 272: Attribute, "action", is not declared in element, "application-server". file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 304: Element, "application- server" is not declared in the DTD file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 314: Element, "node" is not declared in the DTD file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 330: Element, "virtual-host " is not declared in the DTD file:/QIBM/ProdData/WebASAdv/bin/grinnell.xml: 1, 352: Element, "websphere-sa -config" is not declared in the DTD [01.03.21 15:03:27:213 GMT+00:00] 82190417 XMLConfig X !Illegal input file: grinnell.xml $ Below is grinnell.xml (located in the bin directory): <?xml version="1.0"?> <!DOCTYPE websphere-sa-config SYSTEM "$XMLConfigDTDLocation$$dsep$xmlconfig.dtd" > <websphere-sa-config> <virtual-host name="default_host" action="update"> <node name="GRIN400" action="update"> <application-server name="grinnell" action="stop"> </application-server> </node> </virtual-host> </websphere-sa-config> +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.