How To: Deploy DriveWorks Pro
This topic explains how to deploy DriveWorks Pro and covers the
alternatives available for installing and scaling DriveWorks Pro
within an organization.
About
DriveWorks Groups and Project FilesDriveWorks Groups
DriveWorks Pro works with 2 different formats of Group
(DriveWorks Data Storage)
Individual Group
Individual groups should only be used where only one application
will connect at any one time. They are not suitable for
multi-application installations.
Individual Groups are a single file format that can either be on
a network, or on the same machine as DriveWorks Administrator.
Individual Groups can be up-sized to a Shared Group using the
DriveWorks Group Upscale tool, which is installed with DriveWorks
Administrator.
Shared Groups
For multi-application installations, Shared groups require a
connection to Microsoft SQL Server (see note below). The connection
is made and managed by DriveWorks Pro Server (free utility). All
other applications then connect to the Group via DriveWorks Pro
Server.
Microsoft SQL Server Editions
This topic refers to
Microsoft SQL Server, please refer to the
DriveWorks Pro Server
Prerequisites
for information on which editions of SQL Server are supported.
It is recommended that DriveWorks Pro Server is installed on the
same machine as the SQL database.
DriveWorks Pro Server runs as a service.
DriveWorks Administrator includes an upscale utility to upgrade
from an Individual Group to a Shared Group.
A Shared Group cannot be down-sized to an individual group.
DriveWorks Project Files
The master files, as well as the clones (files created
automatically by DriveWorks every time the forms are filled out)
should be on a networked drive accessible to all DriveWorks
Applications via either a mapped network drive, or a UNC path.
The only exception to this is if a single DriveWorks
Administrator is installed, in which case the files can be local to
that machine.
The free tool, DriveWorks Data Management, can be used if files
are moved from one location to another.
Deployment Scenarios
DriveWorks can be used in a single application deployment,
where a single seat of DriveWorks Administrator is used to capture
parameters, create user forms and rules for outputs, create
new specifications and generate all of the outputs.
It can also be set up, by installing further modules, in a
multi-application deployment where each machine serves a specific
function.
Single Application Deployment
Implementation of a single seat of DriveWorks Administrator can
use either an Individual or Shared Group.
If using an individual group, the group file itself can be local
or on a network drive. If a Shared Group is used (SQL Server), it
can also be local or on a networked machine.
The master files and clones can also be local or on a network
path (Mapped or UNC)
Multi-Application Deployment
Multi-application installations must use a Shared Group (SQL
Server) and must have the master files and clones in the same
location relative to each application (Using a mapped drive or a
UNC path)
The SQL Server can be on the same machine as one of the
applications, as can the master files and clones, as long as they
are still accessible through a mapped drive or UNC path.
Decisions on where to place the database and files is largely
one of available machines. The more you can spread the load the
better.
In the following scenarios, only one seat of each application is
shown. Multiple seats would be deployed in the same way.
Where the typical deployment scenario cannot be implemented, the subsequent
headings are alternative scenarios in order of recommendation.
1. Typical Deployment ScenarioSeparate machine for each application
The most typical scenario would have each DriveWorks application on a separate machine, with a separate file server and a separate SQL Server.
# | Application(s) | Notes |
|---|
| 1 | DriveWorks Pro Administrator | |
|---|
| 2 | DriveWorks Pro Autopilot | DriveWorks Autopilot can perform all or any of the following functions: - Specification Processing
- Email Processing
- Model Generation - Requires SOLIDWORKS to be installed on the same machine.
- 3D Preview
To balance the loading of the Autopilot machine these functions can be split over several machines. In this instance separate licenses of Autopilot are required. |
|---|
| 3 | DriveWorks Pro User | |
|---|
| 4 | DriveWorks Pro Live | |
|---|
| 5 | External Users via Web Browser | |
|---|
| 6 | Database Server, DriveWorks Pro Server, DriveWorks License Management | |
|---|
| 7 | File Server | All DriveWorks project data is located here. All new data generated by Autopilot is located here. |
|---|
Use the same machine for the files and database
# | Application(s) | Notes |
|---|
| 1 | DriveWorks Pro Administrator | |
|---|
| 2 | DriveWorks Pro Autopilot | DriveWorks Autopilot can perform all or any of the following
functions: - Specification Processing
- Email Processing
- Model Generation - Requires SOLIDWORKS to be installed on the
same machine.
- 3D Preview
To balance the loading of the Autopilot machine these functions
can be split over several machines. In this instance separate
licenses of Autopilot are required. |
|---|
| 3 | DriveWorks Pro User | |
|---|
| 4 | DriveWorks Pro Live | |
|---|
| 5 | External Users via Web Browser | |
|---|
| 6 | Database Server, DriveWorks Pro Server, DriveWorks License Management, FileServer | All new data generated by Autopilot is located here. |
|---|
Locate the master files and clones on the same machine as
DriveWorks Autopilot
# | Application(s) | Notes |
|---|
| 1 | DriveWorks Pro Administrator | |
|---|
| 2 | DriveWorks Pro Autopilot, File Server | DriveWorks Autopilot can perform all or any of the following
functions: - Specification Processing
- Email Processing
- Model Generation - Requires SOLIDWORKS to be installed on the
same machine.
- 3D Preview
To balance the loading of the Autopilot machine these functions
can be split over several machines. In this instance separate
licenses of Autopilot are required. All DriveWorks project data is located here. All new data
generated by Autopilot is located here. |
|---|
| 3 | DriveWorks Pro User | |
|---|
| 4 | DriveWorks Pro Live | |
|---|
| 5 | External Users via Web Browser | |
|---|
| 6 | Database Server, DriveWorks Pro Server, DriveWorks License Management | All DriveWorks project data is located here. All new data generated by Autopilot is located here. |
|---|
Locate the master files, clones and SQL Server on the same
machine as DriveWorks Autopilot
# | Application(s) | Notes |
|---|
| 1 | DriveWorks Pro Administrator | |
|---|
| 2 | DriveWorks Pro Autopilot, Database Server,
DriveWorks Pro Server, DriveWorks License Management, File Server | DriveWorks Autopilot can perform all or any of the following
functions: - Specification Processing
- Email Processing
- Model Generation - Requires SOLIDWORKS to be installed on the
same machine.
- 3D Preview
To balance the loading of the Autopilot machintable style="width:100%"e these functions
can be split over several machines. In this instance separate
licenses of Autopilot are required. All DriveWorks project data is located here. All new data generated by Autopilot is located here. |
|---|
| 3 | DriveWorks Pro User | |
|---|
| 4 | DriveWorks Pro Live | |
|---|
| 5 | External Users via Web Browser | |
|---|
Using DriveWorks Live in a Demilitarized Zone (DMZ)
To use DriveWorks inside a DMZ, it will need access to
DriveWorks Pro Server and file server. You may need to open the
relevant ports in the firewall between the corporate network and
DriveWorks Live.
Using
DriveWorks Live in a DMZ
# | Application(s) | Notes |
|---|
| 1 | DriveWorks Pro Administrator | |
|---|
| 2 | DriveWorks Pro Autopilot | DriveWorks Autopilot can perform all or any of the following
functions: - Specification Processing
- Email Processing
- Model Generation - Requires SOLIDWORKS to be installed on the
same machine.
- 3D Preview
To balance the loading of the Autopilot machine these functions
can be split over several machines. In this instance separate
licenses of Autopilot are required. |
|---|
| 3 | DriveWorks Pro User | |
|---|
| 4 | DriveWorks Pro Live | |
|---|
| 5 | External Users via Web Browser | |
|---|
| 6 | Database Server, DriveWorks Pro Server, DriveWorks License Management | |
|---|
| 7 | File Server | All DriveWorks project data is located here. All new data
generated by Autopilot is located here. |
|---|
Ports used for DriveWorks Deployment
The table below defines which ports are required to be opened for each use case.
| Use Case | Application / Machine needing access | Protocol | Port Number |
|---|
| Web Access (HTTP) | DriveWorks Live / IIS | TCP | 80 |
| Web Access (HTTPS) | DriveWorks Live / IIS | TCP | 443 |
| DriveWorks Network Licensing Server | Any DriveWorks application | TCP | 27000 (Unless modified) |
| DriveWorks Live Licensing Server | DriveWorks Live / IIS | TCP | 27080 (Unless modified) |
| DriveWorks Pro Server - Data | Any DriveWorks application | TCP | 8000 |
| DriveWorks Pro Server - Discovery | Any DriveWorks application | UDP | 8025 |
| DriveWorks Autopilot - 3D Preview Service | Any DriveWorks application requiring 3D Previews | TCP | 8900 |
| DriveWorks Live - Web & Application Theme | DriveWorks Live / IIS | TCP | 8020 (See Web Access if ran through IIS) |
| DriveWorks Live - Integration Theme | DriveWorks Live / IIS | TCP | 5500 |
| Windows File Sharing | Any DriveWorks application | TCP | 445 |
| SQL Server - Connection | Any DriveWorks application requiring access to SQL | TCP | 1433 |
| SQL Server - Browser | Any DriveWorks application requiring access to SQL | UDP | 1434 |
Hosted Web Integration
If DriveWorks Live is to be integrated into a hosted web site,
there are two options.
- Install DriveWorks Applications in the same hosted location.
- This option is best if the 3rd party hosting the web site can
make machines available for the DriveWorks Applications, Database
and files. Remote access would then be required to administer
the projects in DriveWorks.
- It is recommended that the implementation be done locally to
start with, and then transferred to the hosted environment when
ready to be used.
- Install DriveWorks Applications at the company offices and
connect via a single public IP address.
• With this option, the Hosted web site would point to
the single public IP address at the company's premises.
When redirecting to a DriveWorks Live installation within your
company an alias can be applied so the IP address does not show in
the web address..
For instance, DriveWorks has a demonstration web site at
http://www.configuremyproduct.com
(externally hosted site by 3rd Party)
When clicking to configure any of the products (Cupboard,
Trailer etc) there is an iframe that shows DriveWorks Live running
in a completely different location, using the URL:
http://live.configuremyproduct.com
In the configuremyproduct example, each product link also sends
through information into DriveWorks Live, including the login
details, and name of the project to run.
| Knowledge Base Article Ref: | KB13010804 |
|---|