In FME Server there is currently no way to manage the names of your repositories either through the Web Interface or via the Rest API.It would be nice if there was an option to easily rename repositories rather than having to create a new one and republish workspaces.
Hi,
Is it possible to rename Repositorys by changing the text in the .fsproject file?and then reimport the file.It does not seam to be possible,but would be a great function to implement in future versions of FME.
Best/
Johan
We have just started using Version Control in FME-Server,instead of Tortoise SVN.While the functionality is nice we realized there were no way of telling if the workspace has been version controlled in the repositories or otherwise.
Is there something we are missing?I would like to see it as a column in the repositories with a simple checkmark or similar.
Marcus
the FME Server documentation (https://docs.亚搏在线safe.com/fme/2017.1/html/FME_Server_Documentation/Content/AdminGuide/AccessControl.htm) indicates than you can assign ownership of something to another user,however it doesn't describe how to do this.I see the sharing options button for the repository and I can give full access,run and download permissions there,but I can't change ownership.Can you describe the steps I need to take to do this?
I'm using FME Server 2017.1.1.1 and REST API to create a repository and publish workspace into it.This is fairly straightforward.Once done,I'd like to share that repository with other users already existing on the server.有通过REST API的方法吗?I wasn't able to find it in API documentation.
@akoning,
Do you think it would be possible to add filtering to the completed jobs by repository?You can currently filter by user and the webinar for 2018 showed filtering by status.It would be nice to see the jobs within a repository that succeeded or failed.
Thanks,
Tyson
Does it say anywhere on FME Server (logs or something) which user removes workspace from repository?
thank you
Are you encountering issues accessing the FME Server Repository folders?Please read below for some common troubleshooting tips,questions and resources.
Troubleshooting Tips
- Does the FME Server User have properpermissions to access (or run)the Repository / Workspace?
- Is the Userable to create an empty Repositoryusing the web interface?
- There are manyLog Filesthat may help identify errors related to issues with FME Server Repositories.Start by checking those listed below.
\resources\logs\core\current\ fmeserver.log
\resources\logs\core\current\ fmesharedresource.log
\resources\logs\engine\current\ *.log
Common Issues
"After installing FME Server,the Repository page is blank in the web interface."
This may occur if the post-installation configuration scripts have not been run.Pleasesee this articlefor more information.
"‘Repository home directory is not a directory' error when using a network share for FME Server Repositories."
This error might be encountered if the user account running the FME Server Windows Services does not have proper network permissions.Pleasesee this articlefor more information.
Common Questions from FME 亚搏国际在线官网Community Q&A
Popular Ideas by the FME 亚搏国际在线官网Community
- Rename Files/Folders/Repositories in FME Server
- Copy or Move Workspaces between Repositories
- Create Sub-Folders in Repository Folders-2
- Display Username of User who Uploaded Workspace
- "Find Function" to Search Repositories for a Workspace
Other Resources
Documentation: FME Server Repositories
Are you still experiencing issues?
Please consider posting to theFME 亚搏国际在线官网Community Q&Aif you are still experiencing issues that are not addressed in this article.There are alsodifferent support channelsavailable.
Have ideas on how to improve this?
You can add ideas or product suggestions to ourIdeas Exchange.
I wasn't able to find any schema documentation for the FME Server repository,is there any public details I might have missed?
Essentially just trying to query source and targets for each workspace.Was able to query this information for readers and writers but we often use "SQL Creators" and/or "Joiners" to pull in tabular information.Is there a way to access those from the repository database?To list out the connection name would be great or even grab the SQL?
Here is what we have so far:
SELECT fme_item.name AS "Workspace",fme_item.title AS "Workspace Title",fme_item.username AS "Username",fme_item.lastpublishdate AS "Publish Date",fme_dataset.location AS "Data Location",fme_dataset.format AS "Data Format",fme_feature_type.name AS "Table/Feature Name",fme_repositoryinfo.name AS "Repository",fme_dataset.is_source AS "Is Source"FROM public.fme_item,public.fme_dataset,public.fme_feature_type,public.fme_repositoryinfoWHERE fme_item.item_id = fme_dataset.item_id AND fme_item.repositoryinfo_id = fme_repositoryinfo.repositoryinfo_id AND fme_dataset.dataset_id = fme_feature_type.dataset_id AND fme_repositoryinfo.name != 'Dashboards'ORDER BY fme_repositoryinfo.name ASC,fme_item.name ASC;
Any ideas on how to query all the sources and targets would be great.Thanks a lot!
It would be great if within your repository you could create sub-repositories.Like Sub folders.I find I end up with so much within one repository and wish I could organise it better.
I could create new repository but the workspace is relevant to the repository its in and I don't want to end up with 50 repositories either- it would be handy to be able to drill down through a repository so I can organise better
In a situation where multiple FME servers are spun up andrun standardized workbenches,what's the recommendation for managing helperscripts?We have a set of Python scripts that aid the startup/shutdown of theseworkbenches.But having multiple servers,it is difficult to ensure the versionsof these scripts are the same across the board.Anyone have any recommendationsfor a code repository?
We do have a subscription to Visual Studio Team Service.If anyone has used VSTS with FME server,I aminterested to hear about your experenice in that as well.
Have the ability to show who uploaded (owner) of the workspace within a repository (much like how you can now see who owns each repository).
Is it possible in FME Server 2016 or 2017 to upload Linked custom Transformers to one particular Workspace Repository (for instance called "Common linked Custom transformers") and have several workspaces in different workspace repositories use this - so you only need to upload the Linked Custom Transformers one place,and all workspaces that uses this will get updated?Instead of having to upload every fmx file to all workspace repositories that uses these for each change?
Sorry for the long explanation,I hope it is clear enough!
Introduction
In this scenario the goal is to have FME Server automatically run a workspace that extracts data from a database and refreshes a set of Shapefiles,on a daily basis.
We'll make use of the 亚搏国际在线官网CommunityMapping.fmw workspace already published to FME Server,which reads layers from a file geodatabase and writes out to one of four formats.
In part 4 of this tutorial,you'll learn how to set up an FME Workspace to run automatically on a schedule.
1.Create a New Scheduled Task and See Results
a) From the FME Web User Interface,click on the Schedules button
This opens the Schedules page.
b) Click New to create a new schedule.
- Give the task a Name.Call it 亚搏国际在线官网CommunityMapping
- Create a Category to put this task in: Production.Give it a description "Scheduled tasks which extract data from production database."
- Leave the default checkmark on next to Enabled
c) Set up Test Schedule
- This workspace is to run daily at the same time,but for now set this up to run immediately and then every 5 seconds,just so we can see it in action right away.To do this:
- Check Run Immediately
- Set the Recurrence to Repeat on Interval
- Set Repeat Every to 5 Seconds.
- Ensure Schedule Does Not Expire is checked
d) Set up the workspace details.
- Select the repository the workspace belongs in (Server Tutorial)
- Select the 亚搏国际在线官网CommunityMapping.fmw workspace.
- For output format select Esri Shapefile.
- Process all the layers in the workspace,so select all the options under Feature Types to Read.
- Ignore the Notifications and Advanced options.
- Click OK.Make a note of the current time.
e) See Results
Go to the Jobs > Completed.Notice the 亚搏国际在线官网CommunityMapping workspace is running every 5 seconds.
f) Disable Current Scheduled Task.
Go to Schedules.Check the box for the 亚搏国际在线官网Community Mapping workspace and then click on the Disable button to disable this schedule:
2.Set up Actual Schedule
再次编辑任务。
- Click on the 亚搏国际在线官网CommunityMapping row to start editing.Scroll down to the scheduling options.
- This time change Start Time to tomorrow at 1:00 am.
- Change Repeat Every to 1 Days for daily.
If desired,notifications can be set up to send upon successful or unsuccessful execution of the task.The Advanced Settings is where specific job settings can be entered.We'll leave these for now.
b) Click OK.
We've now set up FME Server to perform a scheduled task once a day.You can confirm the schedule is in place by looking at the Start Time column in your Schedules page;it should show the workspace will run tomorrow at 1:00 am.
Conclusion
We hope you have found these Getting Started with FME Server tutorials useful.If you have any questions about using FME Server,check out theQ&A Forum,read theFME Server Documentation,or post your question in the comments below.If you want more tutorials to try out other features of FME Server,check out theQuickstart(also accessible from the web user interface login page).You can also view a recorded training course or sign up for a live online training on ourtraining page.Thanks!
Introduction
Inpart 2,you learned how to publish a workspace to FME Server and run it from the Web User Interface.Now,in part 3,you will modify that workspace so it allows for "self-serve" data access.To accomplish this,perform the following:
- Create published parameters in FME Workbench to:
- Allow users to pick the layers they want to download
- Allow users to pick which output format they want
- Publish the workspace to FME Server
- Run workspace from Web User Interface (to see how published parameters are reflected in the Web User Interface)
In part 3 of this tutorial,you'll learn how to enable an FME Workspace for self-serve data access so anyone can download your data.This involves creating published parameters in FME Workbench,publishing the workspace to FME Server,and running the workspace from the Web User Interface.
Downloads
1.Create Published Parameters
a) Open workspace
Open the workspace frompart 2in FME Workbench.Alternatively,open the template attached to this article (亚搏国际在线官网CommunityMapping.fmwt) in FME Workbench.
On the Generic Writer,the default writer format is set to Esri Shapefile.But,the goal is for the user to select the format of their choice,from a small list,at run time.This is accomplished with published parameters.
Parameters in FME control how FME operates.They exist in many places,such as readers,writers,and transformers.
b) Take a closer look at one of the parameters for the Generic Writer: Output Format
Double-clicking on this parameter shows that it's been set up so the user can select from any format in the formats gallery.But that's not what we want.The goal is to present the user with a list of 4 common formats.
所以,create a new user parameter,and define it accordingly...
c) In the Navigator,find the User Parameters > Published Parameters node,right-click,and select Create User Parameter
- For Type,select Choice with Alias
- For Name,enter Output_Format
- For Prompt,enter Output Format
- Click the button next to Configuration.We're going to Import the formats we want.
- Click on Import,then Writer Formats.Search and select Esri Shapefile,GML,Bentley Microstation Design V8,and MapInfo TAB.Click OK,and OK again.Select Esri Shapefile for the default value.Note that Published is checked by default - when a user parameter is published,a user is prompted for a value when the workspace runs.Your dialog should look like this:
d) Link Published Parameter to Output Format Parameter
Our new Output_Format parameter appears under Published Parameters,but we still have to link it to the Generic Writer's Output Format parameter.Locate the Output Format parameter of the Generic Writer,right-click on Output Format,select Link to User Parameter,then select the new Output Format parameter we just created.
Notice how the cogwheel icon turned purple.
e) Run the workspace
If you run the workspace immediately it will use the default value and output Esri Shapefile.However,if you click the "Set Workbench to Prompt Before Running Workspace" icon (a green question mark icon) in your toolbar and then run,you will be prompted to choose the output format.Notice only those 4 formats are presented now in the drop down list.选择GML。The workspace runs successfully.
f) Publish Features Types to Read Parameter
Set up the workspace so the user gets to choose which layers they want to request!It's actually quite simple.
- Expand the File Geodatabase Reader > Parameters > Features to Read.This parameter lets the user decide which feature types to process when the workspace runs.
- Right-click on Feature Types to Read and select Create User Parameter.Go with the defaults for the definition,and click OK.Confirm the new parameter appears under Published Parameters.
g)工作区提示和跑
- Make sure that from the Run menu that Run with Prompt is checked,otherwise,this workspace will run with default values.
- Run the workspace again.
Notice that this time there are 2 parameters to set.For more information on published parameters,check outthis chapterof the Server training.
2.Publish Workspace to FME Server
a) In Workbench,go to File > Publish to FME Server,or select the Publish to FME Server tool.
b) Connect to your FME Server
- If you are setting it up for the first time,under Connection choose "Add Web Connection"
- Enter your Connection Name,Visibility,Server URL,username & password and authenticate.
c) Select a repository and workspace name.
Click on the New button to create a new repository.Enter Server Tutorial for the name,and a description "FME Server 2018 Tutorial".Rename the workspace to 亚搏国际在线官网CommunityMapping.fmw.
d) Upload data files
- Click on the Select Files button
- Select Location
- Click the "Upload to a shared resource folder" radio button and then select the Data folder and hit OK
- Select the checkbox for 亚搏国际在线官网communitymap.gdb.OK
- Ensure "Upload data files" is checked and then hit Next
- Note: if you completedpart 2and kept the same workspace name (亚搏国际在线官网CommunityMapping.fmw),you will be prompted "The Workspace ‘亚搏国际在线官网CommunityMapping.fmw' already exists in this repository.Are you sure you want to update this Workspace?" Click Yes to overwrite it,or click No and go back and change the Workspace Name if you do not want to overwrite.
- Ensure the Data Download Service is selected and click Publish
3.Run Workspace from FME Server Web User Interface
a) Open the FME Server Web User Interface
Log in with the author/author username/password.
b) Click Run Workspace
On the Run Workspace page,select Server Tutorial for the repository and the 亚搏国际在线官网CommunityMapping workspace.Select Data Download for the Service.
Check out the Published Parameters.The 2 that were set up and just tested in FME Workbench are shown.Just as before,select an output format,and select one or more layers.
Click Run Workspace.
c) Results
The Data Download service presents a URL link to the translation results in a zip file.A quick inspection of the contents of the zip file confirms the results are what we expected.
Note: The parameters in this workspace were all set up manually to demonstrate how to work with published parameters.A quicker way to create the workspace is select the Dynamic Schema option when generating the new workspace.
Continue to Next Article:
Schedule a Workspace to Run with FME Server