DriveWorks Live can run directly as an application or as a service through Internet Information Services (IIS) v7.5 or later (Requires Windows 7 or Windows Server 2008 R2 operating systems or later).
IIS provides faster transmission times between IIS and compression-enabled browsers.
Dynamic Compression means faster load times for your DriveWorks user forms that display dynamic content (Pictures, DriveWorks 3D Files etc.) on the clients browser.
IIS runs as a service on your computer.
This means that care must be taken when setting up credentials in IIS but has the benefit that you don't need to be logged on to a machine to run an application.
This article explains how to set up IIS so DriveWorks Live can be accessed without having to run the application.
Setup DriveWorks Live (the application) on the Server machine before attempting to run through IIS
This includes the following steps:
IIS and mapped network drives
To run DriveWorks Live through IIS your project should not use any mapped network drives. Mapped network drives are user specific, therefore it is much harder to ensure that the user you set up in IIS can access them.
All network locations should therefore be specified using a UNC (Uniform Naming Convention) path, for example:
\\< ServerName>\< ShareName>\ProjectFile.
Paths that should be specified using UNC include:
Microsoft Excel and Word Document Generation
Ensure the projects being specified through DriveWorks Live have any Microsoft Excel or Word documents generated by an Automatic State in the Specification Flow. This will allow these documents to be created by DriveWorks Autopilot and not DriveWorks Live (which it will not be able to do when running as a service through IIS).
Services do not have access to many programs, especially COM programs such as Microsoft Word and Excel
To maximize performance and for the best user experience, we recommend that as much processing as possible happens when in an Automatic state (Since the processing will be performed by DriveWorks Autopilot).
All DriveWorks plugins used must be installed locally on the machine hosting IIS.
Network located plugins will not run through IIS.
By default, the Web Server role (IIS) is not installed on Windows Server 2008 R2 and Windows 7. Additionally, some of the IIS Manager features and IIS 7 functionality are not available on all editions of Windows 7.
Please refer to the external links below for procedures to install IIS 7.
Follow the steps below to add your site to the IIS Manager.
Launch Internet Information Services (IIS) Manager.
This can be found by launching the Control Panel (from the Windows Start Button), selecting System and Security, then select Administrative Tools and then double clicking Internet Information Services (IIS) Manager.
From the connections pane expand the computer name link and select the Sites node.
Right click on the Sites link and select Add Web Site.
On the Add Web Site dialog enter a Site Name - This name identifies the site in the IIS Manager only, it does not appear externally, although it is good practice to use the same name as your site (for instance www.driveworkslive.com).
Click the button at the end of the Physical Path field.
Browse to the location of the DriveWorks Live theme that contains the web.config file required to be used with this site.
This will be one of the following locations:
Set the Port number to 80
Port 80 is the default port for HTTP traffic.
If port 80 is in use by another web service on your web server you may need to change this to the next available port.
For more on assigning bindings to sites please see the TechNet article Add a Binding to a Site (external link).
From the IIS Manager select Application Pools from the Connections panel.
From the Application Pools list locate the site that was added above and click the Advanced Settings link in the Actions panel.
This will launch the Edit Application Pool dialog.
From the .NET Framework version drop down select .NET Framework v4.0.
From the Enable 32-Bit Applications drop down select:
Check the Identity the service is to run under is correct.
This should be the login credentials DriveWorks Live was installed and run under on the machine IIS is being set up on.
If the Identity is correct, click OK and proceed to Step 9.
If the Identity requires to be changed:
From the Identity field launch the Application Pool identity by clicking the button at the end of the field. Proceed to Step 8.
From the Application Pool Identity dialogue select the Custom account type and click the Set.. button.
Enter the User name, Password and Confirm Password.
Click OK in the Advanced Settings dialogue to apply the changes.
Select the site from the Connections panel.
Click the browse link in the Actions Panel.
This will launch your default web browser with the landing page of DriveWorks Live loaded.
You will not be able to login until you have set up your group connection string (see below).
DriveWorks Live needs to know which Group to use (Including which server the group is on).
When using IIS this is done using a connection string in a config file.
The Group Connection String holds two pieces of information critical to ensuring DriveWorks Live runs with Internet Information Services (IIS).
To change the Group Connection String:
Where MachineName is the name of the machine hosting DriveWorks Pro Server.
And GroupName is the name of the Shared Group to connect to.
|ProServerMachine||DriveWorks Pro Server is located on a machine named ProServerMachine.|
DriveWorks Pro Server is located on the local machine i.e. the same machine running IIS (not ideal scenario).
|ProductionGroup||The name of the Shared Group hosted on the DriveWorks Pro Server machine to connect to.|
The name of the Shared Group hosted on the DriveWorks Pro Server machine to connect to.
Taking the first example from the Server Examples and Name Examples above your Group Connection String should now look like this:
DriveWorks Autopilot can generate models based on user requests from a browser in DriveWorks Live.
If you are using DriveWorks Autopilot in this way, you will need to tell DriveWorks Live which machine you are using.
The 3D Preview Service Location is the location (if local) or name of the computer running DriveWorks Autopilot that has 3D Preview enabled.
To change the 3D Preview Service location:
The DriveWorks Autopilot that hosts the 3D Preview service is located on the local machine.
The DriveWorks Autopilot that hosts the 3D Preview service is located on the machine named AutopilotMachine.
Web Themes can be customized, and the customization files can be moved from their default location.
In this case DriveWorks Live needs to know where the customized files are.
The pathToConfiguration string holds information that tells IIS where the Theme customizations are located, when they have been moved from the default location (as specified in the note box above).
To change the Path to Configuration String:
The full path of the new location should be noted.
If you have followed step 3 above you will see the groupConnectionString has been inserted.
<driveworksLive pathToConfiguration="NewLocation" groupConnectionString="Provider=RemoteGroupProvider;Server=MachineName;Name=GroupName;">
Where NewLocation is the full path to the location of the customized Theme files.
<driveworksLive pathToConfiguration="C:\DriveWorks\MyWebConfigurationFiles" groupConnectionString="Provider=RemoteGroupProvider;Server=MachineName;Name=GroupName;">
From Section 2, Step 3 above you browsed to the location of the Theme to use with your site. DriveWorks provides two themes that can be chosen to be loaded:
To customize the web theme please see the topic Web Theme.
|Knowledge Base Article Ref:||KB13103033|
See Also: How To: Troubleshoot IIS