This example shows you how to create a job which validates an XML Schema file. The validation job uses the valany RaptorXML function built into FlowForce Server. For a list of RaptorXML functions, see the RaptorXML documentation (https://www.altova.com/documentation).
•Required licenses: FlowForce Server, RaptorXML (or RaptorXML+XBRL) Server
•FlowForce Server is running at the configured network address and port (see Setting the Network Address and Port)
•You have a FlowForce Server user account with permissions to one of the containers (by default, the /public container used in this example is accessible to any authenticated user).
Demo files used
•This example uses the address.xsd file available in the RaptorXML Server installation folder. On a Windows 8 system running 32-bit FlowForce Server, the path would be C:\Program Files (x86)\Altova\RaptorXMLServer2020\examples\address.xsd, unless you installed RaptorXML Server in a different folder.
Creating the job
1.Click Configuration, and then click the "RaptorXML" container.
2.Click the valany function (you can also find this function in any container that corresponds to a specific RaptorXML release, for example 2016r2).
3.Click the Create Job button at the bottom of the page. This creates a job with the default name "valany.job". Edit the job name if necessary.
The parameters applicable to the valany function are now visible on the page. Note that the mandatory parameter that you need to supply is shown as an expanded field.
4.In the File field, enter the path and file name of the file that you want to validate, for example, C:\Program Files (x86)\Altova\RaptorXMLServer2020\examples\address.xsd.
5.Under Triggers, click new Timer and create a trigger that will run the job at a specific time in future (see also Timer Triggers).
6.Under Credentials, select an existing credential record or specify a local credential (see also Credentials).
7.Click Save. The job will run at the time specified in the trigger. To see whether the job executed successfully, refer to the job log (see Viewing the Job Log). Specifically, in the log entry details page, result="OK" means that the validation process was successful, for example:
file:///C:/Program%20Files%20(x86)/Altova/RaptorXMLServer/examples/address.xsd: runtime="0ms" result="OK"
If the file did not validate, the log entry displays result="Fail".