This example shows you how to create a FlowForce Server job from a MapForce mapping. First, you will deploy a demo mapping file from MapForce to FlowForce Server. Deploying a mapping means that MapForce organizes the resources used by the mapping into an object and passes it to FlowForce Server. Once the mapping is deployed to FlowForce Server, you can create a server job from it. This particular example instructs you how to configure the mapping job to run daily at a specific time.
|•||Required licenses: MapForce Enterprise or Professional edition, MapForce Server or MapForce Server Advanced Edition, FlowForce 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).|
|•||The mapping job created in this example generates an XML file every time when it runs. Therefore, on the operating system where FlowForce Server runs, you must have rights to create files in some directory (this example uses the C:\temp directory).|
Demo files used
|•||CompletePO.mfd, available at the following path: <Documents>\Altova\MapForce2019\MapForceExamples.|
Creating the job
|1.||Open the CompletePO.mfd file in MapForce.|
|2.||If you haven't done so already, set the transformation language of the mapping to "Built-in".|
|3.||On the File menu, click Deploy to FlowForce Server.|
|4.||Enter the server name and port of the Web administration interface in the respective fields (for example, localhost and 8082, if FlowForce Server is running on the same machine at the default host and port).|
|5.||Enter your FlowForce Server user name and password, and, next to Login, leave the Default option as is.|
If Directory Service integration is enabled, enter your domain user name and password, and then select your domain name from the Login drop-down list. For more information, see Changing the Directory Service Settings
|6.||Make sure the Open web browser to create new job check box is selected. Although you can change the path where the mapping should be deployed, for the purpose of this example, leave the selected path as is.|
|7.||Click OK. When deployment finishes, the FlowForce Server Administration Interface opens in your web browser, and a partially filled in job page is displayed. As shown below, an execution step is created automatically with some pre-filled parameters. For the scope of this example, leave the parameter values as is.|
|8.||In the Working-directory box, enter the path to a directory where FlowForce Server must save the job output. This example uses C:\temp as working directory.|
A working directory is a parameter required by execution steps if the job needs a location to unpack any input files or save output files. FlowForce Server also uses the working directory to resolve any relative paths that occur during step execution. When asked to provide a working directory, you should supply a valid path on the operating system where FlowForce Server runs. If you do not supply a working directory when creating the step, FlowForce Server uses a temporary directory.
|9.||Under Triggers, click new Timer.|
|10.||Next to Run, set the timer to run Daily every 1 days. Next to Start, select a date and time when the job must start, for example:|
|11.||Under Credentials, select an existing credential record or specify a local credential (see also Credentials).|
A credential record is the combination of user name and password associated with a user account on the operating system where the FlowForce Server job runs. When you define a job in FlowForce Server, you must supply the credentials with which the job must be executed. Note that if the user account associated with the supplied credentials does not have sufficient rights on the operating system, the job cannot execute successfully.
|12.||Click Save. At the time and date specified in the trigger, FlowForce Server executes the mapping job. If the job executes successfully, the file generated as a result (CompletePO.xml) becomes available in the working directory specified previously. To see whether the job executed successfully, refer to the job log (see Viewing the Job Log).|
© 2019 Altova GmbH