The Best WAM!NET Alternative… Period!
WAM!NET, the once mighty global provider of shared services for content management, archiving and enterprise networking is shutting it’s doors.
This move has many of their customers scrambling to find a viable WAM!NET alternative.
- FileCatalyst will ensure business continuity, and minimal disruptions while being able to scale to accommodate your ever growing file transfer requirements.
- FileCatalyst has been viewed as an industry leader in the file transfer space with robust and reliable file transfer solutions that can fit into any workflow. Whether your solution is built on premise or you are looking for a cloud service, FileCatalyst can address your needs.
- All FileCatalyst products are offered as either an on-premise as FileCatalyst Workflow or as a cloud service via FileCatalyst Spaces.
- If you are looking for a fully hosted, managed and private implementation, FileCatalyst partners with Tata Communications to provide a fully managed WAM!NET replacement, including all the software, private connectivity and hardware required to build a complete solution for your existing business model.
Main Workflows For Your WAM!NET Alternative
Here is how FileCatalyst can be used to achieve all the workflows covered by WAM!NET.
This is achieved by installing FileCatalyst HotFolder at two different sites, automated tasks can be created to transfer files between the two sites. Usually these files will have to be transferred via a FileCatalyst Server in a hub and spoke deployment. If file transfer acceleration is not needed, a non-accelerated Direct Server can be deployed at any of the sites to allow Direct to Site deployment at an affordable cost.
First let’s define a web user, in WAM!NET, it usually means an internet gateway user hosted on the cloud, any data pushed to this user has to be uploaded to the specific internet gateway server so the user can then login using their web browser to pick up the files.
In the FileCatalyst world a web user is an account on either FileCatalyst Workflow or Spaces. The main difference between Workflow and Spaces is that Workflow can be installed on premise and have direct access to directories on the corporate SAN/NAS. Local on-premise deployment of Workflow also provides integration with SSO or LDAP, which is not available via Spaces. Spaces is a cloud based version of Workflow where all the accounts, data and storage reside on the cloud, there is an option in Spaces to connect to an on premise Direct server which inturn might have access to local corporate NAS, this option kind of blurs the lines between the 2 products. In case when Spaces connects to a local on-premise FileCatalyst Server, the user’s folders will be able to point to local NAS.
For this use case we will use a local on premise Workflow instance that usually runs in the main corporate DMZ and is connected to a local Direct Server that has access to the corporate NAS, usually via a FileCatalyst reverse proxy server also residing in the DMZ. In this case moving any content to a web user requires copying of the file to the appropriate NAS folder assigned to the workflow user that will have access to it via FileArea. If a remote Site is required to share files with a web user, FileCatalyst HotFolder can be created to automate the transfer of the file from site to the specific folder assigned to the web user in Workflow.
If we were using Spaces instead of on-premise Workflow deployment, HotFolder at the site would copy the files directly to the correct folder on the cloud storage, this folder will be accessible to the user via the web.
This flow is very similar to number 2 but in reverse where, the web users would upload content to their assigned file area and the HotFolder at the Site would automatically download the files to the appropriate site.
In Workflow, there is an option to create a FileArea and share it amongst many users defined in Workflow, the users that are assigned to access a given file area will be able to upload/download files from the given FileArea and share files between them.
This flow is essentially the same as number 3, however the files uploaded by the web user has to go through an interim step where the replication of the files to appropriate NAS directories can occur. We will use a locally installed HotFolder at the main hub that will copy files as they arrive from the web users into the correct folders. Once the files are copied the process of picking up the files via the web or via a HotFolder is essentially the same as in the previous use cases. The HotFolder installed at the central location will make sure that it watches the correct input directory and replicates the files to the correct directories on the SAN to other parts of the workflow.
This flow is very similar to number 5 where an interim HotFolder is installed on the same machine as the Direct server and helps to replicate the files to correct paths on the web or other sites, optionally if a site does have a Direct Server installed, then the HotFolder can transfer the files directly to the Site.
Library feature in WAM!NET is very similar to a group FileArea in Workflow, where there is a repository of files which can be shared with other Workflow users or via email to other non-workflow web users. To invite other external users to upload files into a FileArea, the “Invite Others” feature in Workflow can be used where the temporary users get automatically assigned upload only rights to a specific FileArea.