Create File Document Filename=filedir + "\" + filename | Document = xmlMotd (filedir and filename are string variables)
Create XML Document Source Document=xmlMotd | Document=xmlMotdDoc
Get XML Document Date Document=xmlMotdDoc | XML Path:"a valid xml file on the server" | Result Data=xmlMotdGet
When I run the debug the xmlMotd variable gets the right path to the file \de_DE\IT\motd.xml (the actual location of the file on the server is c:\program files\wfavvid\Documents\user\de_DE\IT\motd.xml. However, the script fails and the debug tells me "the system cannot find the path specified".
Am I using the right approach to find and read an xml file on the server whose name and location are build up using script vaiables or must I always hard code the location of the file in the script?
The first thing that stands out to me is that you should not be referencing the local file system or using the Create File Document step. Your XML file needs to be in the Document Repository which you upload through /appadmin. This is synchronized to the disk from the database automatically for you.
The Create XML Document step has three parameters. They should look something like this:
Where xmlDocumentsUrl would be the folder within the document repository and xmlFilename is the actual file.
When the engine processes this, it will look something like this DOC[example\filename.xml]. Remember that this is inside the default language unless you qualify it with a language qualifier: DOC[example\filename.xml] @ L[de_DE]
This should be a Document type variable.
The parameters for your Get XML Document Data steps should look something like this:
XML Path: "/example_root/next/etc"
Xpath is very flexible. You should look at the W3C or W3Schools references for additional information.
upload your script we can see more cleary. are you really calling file name as filename? You are in the direction except few small checks like forward slash etc. Do you have all the steps required like create file document, create xml and then get xml.....
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.