Install the Transflo DMS Workflow Web Client
The Transflo DMS Workflow requires that you create a website known as the Workflow Web client to host the Workflow Web pages and provide end-users with a workflow user interface. Previously limited to Edge, IE, and Firefox browsers, this workflow or workspace browser for DMS was updated in early 2024 to support the Google Chrome browser.

In order for the Workflow Web Client to work in Windows 2008, ensure the following permissions have been set:
-
Give the tfwfadmin UserOwner permissions of the D:\swserver\TFLOWF\bin and D:\swserver\TFLOWF\Util folders.
-
Grant the IIS_IUSRS User read permissions to all binaries in the D:\swserver\TFLOWF\bin and D:\swserver\TFLOWF\Util folders.

Workflow Web Client installations require the ISAPI and CGI Restriction IIS windows components installed and enabled. To install these components:
-
From the Administrative Tools, start the Server Manager.
-
Expand the Roles node in the tree view and select Web Server (IIS).
-
Click the Add Role Services link on the right.
-
Under Application Development select ISAPI Extensions, and click Next.
-
Click Install.
-
Click on and expand the Internet Information Services (IIS) node then click on the Workflow Server node.
-
Double-click the ISAPI and CGI Restrictions icon and allow the extensions for the Microsoft.NET framework.
Note: See the Third Party Software Requirements section of the TRANSFLO® Hardware Specification System Administrator's Knowledge Base, for .NET Framework requirements and installation instructions.

If your Web Forms uses JavaScript Object Notation, you must enable the .json and .forms mime types for your forms to work. If a form requires these MIME types and they have not been enabled, when the user attempts to open a Document in the Document Viewer, the Document Viewer will throw an error and fail opening the form.
To enable MIME types in IIS, do the following:
-
Access Administrative Tools / Internet Information Services (IIS) Manager.
-
In the Internet Information Services (IIS) Manager window, choose one of the following methods:
-
Click on a virtual directory, either for the iProcess Client or TIBCO Forms (WebDAV directory), in the left pane. If you choose to add the required MIME types for individual virtual directories, you will need to perform this procedure twice; once for the iProcess Client virtual directory, and again for the TIBCO Forms virtual directory (WebDAV directory),
-
Click on the machine name or the web site in the left pane; MIME types at the machine or web site level are inherited by the virtual directories below them.
-
-
Scroll down the list in the MIME Types dialog and verify whether or not .json has been added. If it has, proceed to step 7.
-
If .json is not in the list, click Add. In the Add MIME Type dialog:
-
File name extension: .json
-
MIME type: application/json
-
Click OK to save the new MIME type.
-
-
Scroll down the list in the MIME Types dialog and verify whether or not .form has been added. If it has, no further action is required. Exit the MIME Types dialog and IIS.
-
If .form is not in the list, click Add. In the Add MIME Type dialog, enter:
-
File name extension: .form
-
MIME type: text/xml
-
Click OK to save the new MIME type.
-
11. Exit Internet Information Services (IIS) Manager.
Note:IIS does not need to be restarted to recognize new MIME types.

-
To access the workflow workspace browser externally:
-
Navigate to C:\inetpub\ wwwroot\Transflo.Workflow\JSXAPPS\ipc and open the config file.
-
Search for the following lines:
<record jsxid= "ActionProcessors" type="ipc" ><ActionProcessor weighting="100" baseUrl= "http://2K8WKFLW47/ TFWFActProc/ ActionProcessor.aspx"/> </record>
and
<record jsxid="webDAVRoot" URL="http://2K8WKFLW47/TFClientForms/Forms"/>
-
-
To install the TRANSFLO® Workflow Web Client, launch TRANSFLO Workflow Web Client Setup.exe from the installation CD.
-
The Setup TRANSFLO® Workflow Web Client Welcome window opens. Click Next.
-
The TRANSFLO® Server Web Service URL window opens. Verify that the Web Service URL is correct. If your server name is not TRANSFLO change the URL to http://<Transflo Server Name>/ Transflo.WebService.Wse3/TransfloWS- wse3.asmx where <Transflo Server Name> is the name of your TRANSFLO® Server. Click Next.
-
Setup prompts you for the host name of your TRANSFLO® Workflow Engine.
-
Enter the host name in the text box.
-
Click Next.
-
If you prefer that the Workflow Server name not be used in the URL of the Web Clients do the steps below.
-
Enter “Workflow” in the Workflow Engine Host Name text box.
-
Once installation is complete, open your hosts file with a text editor
(C:\Windows\System32\drivers\etc\hosts), and add the following entry:
<IP Address> Workflow where <IP Address> is the IP address of your Workflow Web Server.
-
-
-
The Select Web Site window opens. If you are not using the IIS Default Web Site for your TRANSFLO® web applications, select the appropriate Web site from the Web Site drop down.
-
To refresh the Web Site list, click the Refresh button.
-
Click Next.
-
-
Setup begins installation of the Workflow Web Client. This may take a few seconds.
-
After the Completing the TRANSFLO® Workflow Web Client Setup Wizard window opens, click Finish.

To verify the TRANSFLO® Workflow Web Client is started and running, perform the following steps:
-
Open a browser and enter the TRANSFLO® Workflow Web Client URL. Syntax for the URL is
http://<Web Server>/TRANSFLO.Workflow/
Do not use localhost for your <Web Server> in the URL. You must use your fully qualified web server name.
-
If Client Access was installed on this machine the Workflow Web client may not install properly. See the following IBM article:
http://www- 01.ibm.com/support/docview.wss?u id=nas284158c400658982b8625761 1003c6d21.
Also see the TRANSFLO® Workflow Knowledge Base, for more suggestions.
-
If opening the Workflow Web Client fails with the error "Unable to establish a connection to the Action Processor" occurs:
-
Check that the TFWFActProc virtual directory under the Default Web Sites in IIS is running as the DefaultAppPool (Integrated Authentication) and not as Classic .NET AppPool.
-
Verify that ASP.net has been installed as an IIS Role Service.
-
If you are still using Internet Explorer or Edge in IE compatibility mode, the Workflow Web Client URL must be added to the list of trusted sites in order for the Workflow Web Client to display properly. If not a blank page will appear when browsing to the URL.
-
-
The Web Client opens at the login page.
-
The TRANSFLO® Workflow Web Client authenticates the user and opens the home page.
-
(Optional) The Document Viewer ActiveX component can also be deployed to all of your users with the TRANSFLO® Deployment Agent. If you do this make sure that the TRANSFLO Document Viewer Setup.exe is the same version as the installed TRANSFLO® Workflow Web Client.
-
Click the Install... button at the top right corner of the page to install the TRANSFLO® Document Viewer ActiveX component on your computer.
-
The File Download window opens. Click Run.
-
The Internet Explorer – Security Warning window opens. Click Run.
-
The Setup – TRANSFLO® Document Viewer welcome window opens. Click Next.
-
The Select Destination Location window opens. Click Next.
You may be prompted to close your TRANSFLO Web browser sessions.
-
The Ready to Install window opens. Click Install.
-
Setup installs the TRANSFLO® Document Viewer ActiveX component.
-
The Completing the TRANSFLO® Document Viewer Setup Wizard window opens. Click Finish.
-
The TRANSFLO® Document Viewer ActiveX component starts. The TRANSFLO® Workflow Web Client home page opens indicating a successful installation of all of the TRANSFLO® Workflow Server components.
-
If the ActiveX control does not start automatically, right-click on the yellow information bar at the top of your page and select “Install ActiveX” from the context menu.
-
If you get the following error at the top of your page: Error: Connection to the server failed. Communication Error, open C:\Inetpub\wwwroot\Transflo.Workflow\default.htm with a text editor and search for “var tfURL”. In the URL on that line ensure that your TRANSFLO® Server name is correct. The URL should be:
http://<Transflo Server Name>/Transflo.WebService/TransfloWS-wse3.asmx
<Transflo Server Name> is the name of your TRANSFLO® Server.
-
Secure Sockets Layer (SSL) can be used to secure communications between the Action Processor and the client. However, the way in which it is implemented is specific to the Web Application Server (WAS) you are using. See the documentation for your WAS.
-
If you access the TIBCO iProcess Workspace (Browser) through HTTPS, you must also access the Action Processor through HTTPS, and vice versa. In other words, you cannot access one through HTTP and the other one through HTTPS.
-

There are occasions when it is desirable to remove the TRANSFLO® Workflow Web Client from your server. If you want to remove TRANSFLO® Workflow completely from a server and move it to a different server is one scenario.
Another example would be if you wanted to separate your Workflow Engine from your Workflow Web Client by moving the Workflow Web Client to a separate Web server.

To uninstall the TRANSFLO® Workflow Web Client from your 32 bit server:
1. Log in as an Administrator.
2. Open the Internet Information Services (IIS) Manager from Windows® Administrative Tools.
3. Expand the Web Sites node and expand the Default Web Site node.
4. Delete the following Virtual Directories:
-
TFClientForms
-
TFWFActProc
-
TIBCOActProc
-
Transflo.Workflow
5. Open Windows Explorer and navigate to: C:\Inetpub\wwwroot\
6. Delete the following sub-folders:
-
TFClientForms
-
TFWFActProc
-
TIBCOActProc
-
Transflo.Workflow

To uninstall the TRANSFLO® Workflow Web Client from your 64 bit server:
1. Log in as an Administrator.
2. Open the Internet Information Services (IIS) Manager from Windows® Administrative Tools.
3. Expand the Sites node and expand the Default Web Site node.
4. Remove the following Virtual Directories:
-
TFClientForms
-
TFWFActProc
-
Transflo.Workflow
5. Open Windows Explorer and navigate to: C:\Inetpub\wwwroot\
6. Delete the following sub-folders:
-
TFClientForms
-
TFWFActProc
-
Transflo.Workflow