Dear everyone,I am heading to build a automatic user registration process for new users.Please help me by providing FME documents how to do that.I will have a new web page and new users will request for registrations by proving their user name,email and password,then they will receive one reply link in their provided email and by clicking on that link their credentials will be stored inside database and their account will be activated.Be aware,we will use activedirectory for storing our users.Please provide me some hints and documents for this solution.

With kind Regards

Muqit

Is there any way to convert a file of x format to y format using cmd.I'm able to do it only i when i created fmw file but i wanted to convert it on the fly is that possible?

or is there any way to automate the whole process.

I'm trying to build a web app which is able to view only x format files only so i want to view also some z format files(which my app cannot load),so i want to use fme to convert z format file to x format with a single click is it possible without opening manually(conversion should happen in backend).Please do comment if you didn't get my question or if you have any solution.

Is there anyone who is using FME scheduler to automate SAP jobs?Our company is using SAP ERP software and we want to automate SAP jobs.SAP has its own job scheduler but it lacks many advanced features we are looking for.Like we want the scheduler to run periodic jobs which can ran only on working days with different parameters and dependencies like the next job should start only after finishing the first job;the second job should run after n +1 days after the first job etc...Some jobs will run on some days but it should have different run date like if it is running tonight,it should populate yesterdays' date as the job date.

Can anyone please let me know if FME server has these kind of advanced features to automate jobs?

There had been several suggestions to make design of FME Server automation 亚搏在线workflows more graphical,and provide a higher level overview:

https://knowledge.亚搏在线safe.com/idea/42491/system-architecture-design-view.html

https://knowledge.亚搏在线safe.com/idea/18987/automation-亚搏在线workflows.html

https://knowledge.亚搏在线safe.com/idea/19014/better-亚搏在线workflow-control-of-multi-step-workspace-jo.html

I think a good addition to these ideas is the ability to display the status of each 亚搏在线workflow step on this graphical framework,which makes this a visual monitoring / debugging interface,as well.

In the first 5 parts of this tutorial,we look at different stages a 亚搏在线workflow can go through and how changes (Updates & Deletes) can be deployed,migrated & rolled back on a staging (FME Server STG) and a production (FME Server PROD) server.Now that we understand the basic functionality and capabilities of Project in FME Server we are ready to automate our Deployment to not only keep our 2 Servers in sync and reduce risk but also to save time and minimize manual interaction.

To do that let's create a workspace (download here:automate-deployments.fmw) that uses theFME Server REST APIto carry out all the tasks that we completed in this tutorial so far in one single job:

1. Export our project fromFME Server STGand save it as a backup.
2. Export our project fromFME Server PRODand save it as a backup.
3. Delete our project fromFME Server PROD.This step makes sure that the automated deployment job can handle Updates (seepart 4) and Deletes (seepart 5).
4. Import the project fromFME Server STGtoFME Server PROD

To be able to use the REST API of FME Server we need to authenticate to FME Server to make sure we are authorized to use the REST API.We can generate a token for this purpose.Please note that we will need tokens for users with the fmesuperuser role to be able to use the migration REST API.Make sure to check out the FME Serversecurity documentationfor more details.In the attached workspace,the base URLs of the 2 FME Server installations and the tokens are specified via published parameters.This way we only need to specify them once to call several different REST API calls in one workspace.Another published parameter will be used to specify the name of the project which is a parameter that is needed in all REST API calls used in this example.The last published parameter holds the location for the backups.

We can use the HTTPCaller to make FME Server REST API calls.There are 3 essential REST endpoints that are used in this workspace.Let's start with exporting our project:

/fmerest/v3/migration/backup/download

To download a project we use the migration endpoint.To only download a specific project from FME Server and not an entire FME Server project we need to make sure that we specify the project name as a form parameter.Check out the HTTPCaller transformers in for exporting fromFME Server STG&FME Server PRODin the attached workspace and make sure to check outREST API documentationfor further details.The downloaded projects can then be written to a designated location for backups of the staging & production environment with an AttributeFileWriter.To create a history of backups the @DateTimeNow() function can be used a prefix to the file names to add a unique timestamp to all backups.

/fmerest/v3/projects/projects/$(projectName)/deleteall

Before we upload/deploy our project to the production server we need to delete the existing project to make that changes that include deletions in the project will be respected.For more details on this REST endpoint check outthe documentationand the HTTPCaller deleting the project in the attached workspace.

/fmerest/v3/migration/restore/upload?importMode=INSERT&pauseNotifications=false

Now we can upload/deploy the project that was exported fromFME Server STGearlier toFME Server PROD.For this task,we will again use the migration REST API to upload the project to our production environment.Make sure to check out theREST API documentationand compare it with the settings in the HTTPCaller to get familiar with the concept of using the REST API of FMEServer in a workspace.

To capture all information if anything goes wrong and a couple of Loggers can be added.A Terminator can also help to stop a workspace at a certain point if we already know something went wrong.

The provided workspace is an example to showcase some ideas for automating deployments following the concepts we examined in this Tutorial using FME Server Projects.There are a lot of things and functionality provided by FME that can be added to this,so please use this example as starting point to explore the possibilities.

Inpart 4of this tutorial,we rolled back some changes that we made to our 亚搏在线workflow.In this part of the tutorial,we will again deploy changes to our 亚搏在线workflow.The key difference topart 3,where we also deployed changes,is that we will now deal with changes that include deletions of components of the 亚搏在线workflow and only updates or additions.This little difference is very important to be aware of because simply exporting and importing projects will not delete any components of a 亚搏在线workflow on FME Server.We need to find a different way keep our environments in sync after we delete parts of the 亚搏在线workflow.

An important step during this part of the tutorial is to make a backup of the current state of the production environment (FME Server PROD).This will make sure that we have a full history of all changes that were made to this environment.Once we have done that we will remove the entire project ofFME Server PRODbefore we deploy or import the project including the changes (deletions).This way we can make sure that the 亚搏在线workflow is in sync again in both environments.

Procedure 1:

• Open the FME Server Web UI for the staging server and login:
  • Server URL: URL ofFME Server STG
  • User Name: user250
  • Password: fmeworkshop
• Delete the schedule.
• Export the project.
• Note: it's a good idea to verify that the project file is valid by uploading it to the same FME Server you exported it from.

Procedure 2:

• Open the FME Server Web UI for the production server and login:
  • URL: URL ofFME Server PROD
  • User Name: deployer
  • Password: fmeworkshop
• Export the project and enter ‘prodbackup' or similar as part of the name.
• Note: it's a good idea to verify that the project file is valid by uploading it to the same FME Server you exported it from.

Procedure 3:

• Open the FME Server Web UI for the production server and login:
  • URL: URL ofFME Server PROD
  • User Name: deployer
  • Password: fmeworkshop
• Completely Remove the project from the production server.
  • Also remove contents: check this on
• Import the project using the project file from the staging server.
• Check to see that the workspace is present and the schedule is not.

Both of our environments hold the exact same version of the 亚搏在线workflow again and we have a history of all changes that we made to the workflow in form of backups of the FME Server project.

Congratulations,you successfully moved a 亚搏在线workflow from a staging environment to a production environment and deploy changes (updates & deletions),rolled back changes and created a history of the changes.

Inpart 3of this tutorial we used FME Server projects to deploy changes between two FME Server environments.In this part of the tutorial we will simply rollback our changes on both environments (FME Server PRODandFME Server STG).

Procedure 1:

• Open the FME Server Web UI for the production server and login:
  • URL: URL ofFME Server PROD
  • User Name: deployer
  • Password: fmeworkshop
• Open Projects and import the project using the backup project file you exported from production prior to the last update from staging.
  • Overwrite Existing Items: check this on
• Check to see the original schedule setting (Repeat every: 1 month) has been restored.

Procedure 2:

• Perform the same restore procedure,but for the staging server (FME Server STG).

Now that we know how to restore the states of our two environments to a previous version of our 亚搏在线workflow we will look at a method that allows us to not only deploy changes that include updates and additions of our workflow,but also changes that include deletions of parts of our 亚搏在线workflow in thenext partof this tutorial.

Inpart 2of this tutorial we created a project containing a FME Server 亚搏在线workflow on the FME Server staging environment and deployed it to the FME Server Production environment.This part of the tutorial will introduce a method to deploy or migrate changes of a 亚搏在线workflow between two FME Server environments.First we will change our 亚搏在线workflow in the FME Server staging environment (FME Server STG).Then we will migrate the changes utilizing the import & export functionality of FME Server projects again.Please note that the changes that we will deploy only include an update or a addition to our existing 亚搏在线workflow.How to deploy and migrate changes that include deletions of components of the 亚搏在线workflow will be discussed inpart 5of this tutorial.Additionally we will also preserve the current state of the 亚搏在线workflow on the FME Server production environment (FME Server PROD).

Procedure 1:

• Open the FME Server Web UI for the staging server and login:
  • Server URL: URL ofFME Server STG
  • User Name: user250
  • Password: fmeworkshop
• Open the schedule you created previously and make a small change:
  • Repeat every: 1 week
• Export the project.
• Note: it's a good idea to verify that the project file is valid by uploading it to the same FME Server you exported it from.

Procedure 2:

• It is a good idea to backup the production project prior to updating it from staging.
• Open the FME Server Web UI for the production server and login:
  • URL: URL ofFME Server PROD
  • User Name: deployer
  • Password: fmeworkshop
• Export the project and enter ‘prodbackup' or similar as part of the name.
• Note: it's a good idea to verify that the project file is valid by uploading it to the same FME Server you exported it from.

Procedure 3:

• Open the FME Server Web UI for the production server and login:
  • URL: URL ofFME Server PROD
  • User Name: deployer
  • Password: fmeworkshop
• Open Projects and import the project using the project file exported from the staging server.
  • Overwrite Existing Items: check this on
• Run the important_process.fmw workspace to ensure it works.
• Check to see updated schedule setting (Repeat every: 1 week) has been deployed.

Once again both environments have access to an in sync version of our 亚搏在线workflow.The backup of the project onFME Server PRODpreserves the initial state of the 亚搏在线workflow.In thenext partof this tutorial we will use this backup to rollback our changes on both environments.

Inpart 1of this tutorial we created a simple FME Server 亚搏在线workflow on the FME Server staging environment (FME Server STG).In the second part of this tutorial we will create a FME Server project.By utilizing the import and export functionality of FME Server projects we will deploy the 亚搏在线workflow to the FME Server production environment (FME Server PROD).Once we deployed the 亚搏在线workflow onFME Server PROD,we will verify that the workspace that is part of the 亚搏在线workflow runs successfully onFME Server PROD.

Procedure 1:

• Open the FME Server Web UI for the staging server and login:
  • Server URL: URL ofFME Server STG
  • User Name: user250
  • Password: fmeworkshop
• Open Projects and create a new project.
  • Name: user250
  • Add the workspace you published.
  • Add the schedule you created.
• Click OK.
• Export the project.

Procedure 2:

• Open the FME Server Web UI for the production server and login:
  • URL: URL ofFME Server PROD
  • User Name: deployer
  • Password: fmeworkshop
• Open Projects and import a project using the project file exported from the staging server.
• Run the important_process.fmw workspace to ensure it works.

Both,FME Server STGandFME Server PROD,can now run the exact same workspace and the schedule contained in the 亚搏在线workflow created in at the beginning of this tutorial.

In thenext partof the tutorial we will modify our 亚搏在线workflow onFME Server STGand deploy the changes toFME Server PROD.

In the first part of this tutorial we will create a basic FME Server 亚搏在线workflow.On the basis of this 亚搏在线workflow we will carry out different operations,including updates,deletes & rollbacks,while keeping the state of the 亚搏在线workflow in sync on both FME Server installations (FME Server STG & FME Server PROD).

The FME Server 亚搏在线workflow consist of 2 main components:

1. A workspace using a database connection to read from a PostGIS database
2. A schedule to run the workspace in a certain interval on FME Server

Follow the steps of both procedures to create the FME Server 亚搏在线workflow:

Procedure 1:

• Open FME Workbench 2017
  • Create a workspace that reads the PostGIS database
  • Add a PostGIS Reader and Add a Database Connection:
    
    • Name: important database
    • Host:Postgis.train.亚搏在线safe.com
    • Port: 5432
    • Database: fmedata
    • Username: fmedata
    • Password: fmedata
  • Select the schema and table in the Parameters window:
    • Schema: public
    • Table: DrinkingFountains
  • Delete the published parameter SourceDataset_POSTGIS
• Save the workspace:
  • Workspace file name: important_process.fmw
• Publish the workspace to FME Server using the following settings:
  • Add a web connection:
    
    • Connection Name:FME Server STG
    • Server URL: URL ofFME Server STG
    • User Name: user250
    • Password: fmeworkshop
  • Create a repository: user250
  • Database connection: check it on to upload
  • Register Services: Job Submitter

Procedure 2:

• Open the FME Server Web UI for the staging server and login:
  • Server URL: URL ofFME Server STG
  • User Name: user250
  • Password: fmeworkshop
• Run the important_process.fmw workspace to ensure it works.
• Create a schedule that runs the workspace once every month.
  • Name: important schedule
  • Category: user250
  • Repeat every: 1 month
  • Under Advanced:
  • Set Running Job Expiry Time: 60 seconds

Now we created a FME Server 亚搏在线workflow in our staging environment (FME Server STG).In thenext partof this tutorial we will create a project containing the 亚搏在线workflow and we will use the project to deploy the exact same workflow on our production environment (FME Server PROD).

Don't get caught fighting fires with your shoelaces tied together!Stay nimble by embracing a multi-stage environment,from development to test to staging to production.We'll explore how to reduce risks using a stepwise approach to developing,deploying,and verifying your solutions.Along the way,we'll look at a number of new features in FME Server 2017,including projects,user-based security,and job management.

Overview:

In this Tutorial we will work with two FME Server environments.One staging serverFME Server STGand one production serverFME Server PROD.We will use the FME Server Projects to deploy a FME Server 亚搏在线workflow with all it's dependencies: Workspace,Database Connection and Schedule.Utilizing the export and import functionality of FME Server Projects we will go through several stages of deployment including updates,deletes & rollbacks.The ultimate goal is to keep both environments in sync at all times and to keep a history of changes in form of backups:

1. Create a 亚搏在线Workflow:We will create a simple 亚搏在线workflow on our FME Server staging environment.The example 亚搏在线workflow includes a FME Workspace a Web Connection and a Schedule to run the workspace.
2. Create & deploy a Project:We will save our 亚搏在线workflow as a Project on our staging server and deploy it to our production environment.The 亚搏在线workflow will be in sync on both the staging and the production server.
3. Deploy Changes (updates):We will make a simple change to our 亚搏在线workflow on our staging server and will deploy the changes to our production server to keep them in sync.We will also make a backup of our 亚搏在线workflow.
4. Rollback changes:Using our backup from the last exercise we will rollback the changes to restore both servers to the state before the update.
5. Deploy Changes (delete):We will delete one component of our 亚搏在线workflow on the staging server and deploy the change to the production server.

Requirements:

This Tutorial requires2 machineswithFME Server 2017.0or higher installed andFME Desktop 2017.0or higher.A easy way to spin up to2 FME Server 2017 machinesto run through this Tutorial is to simply sign up for aFME Cloud trialaccount and start2 Starter instances here.You will get a free 250$ credit which will be enough to finish this tutorial.

The Users & Security settings used in this tutorial are stored in 2 Project files,one for each FME Server environment:

FME Server STG(Staging environment)

FME Server PROD(Production environment)

To apply the User & Security settings to your FME Server installations,download this zip fileusers-security.zip,extract the Project files and login to the WebUI of your FME Server machines.Go to Projects >Import and upload the Project file for the respective environment.

After the import of both Project files to the 2 FME Server environments you will be able to use the following credentials during this Tutorial:

Once both FME Server environments (FME Server STG &FME Server PROD) are set up,we can jump right into it,starting withPart 1 - Create a 亚搏在线Workflow.