Mapping files created with Altova MapForce and transformation files created with Altova StyleVision can be automated with the help of the following server counterpart products: MapForce Server (or MapForce Server Advanced Edition) and StyleVision Server. MapForce Server and StyleVision Server make it possible to execute mappings and transformations in a server environment (Windows, macOS, Linux), either at the command line, or from an API call. If these products do not run alongside FlowForce, automation entails developing programs or writing scripts which call the API or invoke the command line of MapForce Server or StyleVision Server.
When MapForce Server and StyleVision Server run under FlowForce Server management, automation can be taken to the next level. Namely, the mappings and transformations can be deployed directly to FlowForce Server and be run as jobs (see also How It Works). This way, the mapping or transformation will benefit from all the advantages of a FlowForce Server job: scheduled or on demand execution, execution as a Web service, AS2 integration, configuration by means of FlowForce expressions, error handling, conditional processing, email notifications, and so on. The instructions to deploy a mapping/transformation to FlowForce Server are similar in MapForce and StyleVision, and are as follows:
|•||On the File menu of MapForce or StyleVision, click Deploy to FlowForce (Server).|
For the list of prerequisites, tips, as well as reference to the deployment settings, refer to the documentation of MapForce and StyleVision, specifically:
Once deployed, the mapping or transformation appears in the FlowForce container to which you deployed it. In FlowForce, such mappings or transformations become functions, and thus can be turned into jobs. They can also be called from other jobs, and accept various inputs (typically, files) as parameters. Note that FlowForce Server does not execute such mapping or transformation functions by itself; MapForce Server or StyleVision Server (or both, depending on the case) are invoked to perform the actual execution.
FlowForce Server function automatically generated from a deployed mapping
To create a job from a deployed MapForce mapping or StyleVision transformation:
|1.||Navigate to the FlowForce container where you deployed the MapForce mapping or StyleVision transformation (for example, the container "/public").|
|2.||Click the required mapping or transformation. By default, MapForce mappings have a naming convention SomeFile.mapping and StyleVision transformations have a naming convention like SomeFile.transformation.|
|3.||Click Create Job.|
You can now configure the job according to your needs: for example, the settings in the "Trigger" section defines how and when the job should run (see Managing Triggers). The input parameters corresponds to the inputs defined by the original MapForce mapping (or StyleVision transformation).
The output of the step which executes the mapping or transformation function represents a generic FlowForce type (let's call it result), not an actual file or a stream. To convert result to actual files or streams, FlowForce expression functions must be used, see Accessing the Result of a Mapping or Transformation Job.
For a step-by-step example which illustrates deploying a StyleVision transformation and creating a job from it, see Creating a Job from a StyleVision Transformation. For a similar example for MapForce, see Creating a Job from a MapForce Mapping. For an example job which requires calling both MapForce Server and StyleVision Server, see Example: Generating Multiple PDFs from Multiple XMLs.
© 2019 Altova GmbH