DFS Operations Guide

PDM INSTALLATION ADDENDUM

Document History

Initial Release: Thursday, October 22, 2009

Latest Release: Wednesday, December 30, 2009

Release Number: 1

Printed: Monday, January 11, 2010

The information contained in this document represents the current view of Adenium Systems on the issues discussed as of the date of publication. Because Adenium Systems must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Adenium Systems, and Adenium Systems cannot guarantee the accuracy of any information presented after the date of publication.

This document is for informational purposes only. Adenium Systems MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Adenium Systems is the registered trademarks or trademarks of Adenium Systems in the United States and/or other countries.

Other product and company names mentioned herein may be the trademarks of their respective owners.

Adenium Systems • 34103 Lakeshore Blvd • Cleveland, OH 44095• USA

Contents

1.0 Server and Network Infrastructure 5

1.1 DNS Configuration 5

1.2 Database Server Configuration 5

1.2.1 SQL Server 5

1.3 Web Server Configuration 6

1.3.1 Load Balancer 6

1.3.2 PDM Web Server A 6

1.3.3 PDM Web Server B (Only If Load Balancing) 6

1.4 Import Server Configuration 7

1.5 File Vault Configuration 7

1.6 SMTP Configuration 7

1.7 Domain User Requirements 7

2.0 Application Information 8

2.1 PDM Configuration 8

2.2 PDM SQL Configuration 8

2.3 PDM Service Accounts 9

2.4 Remote Access For Servers 10

2.5 .NET Session State Configuration 10

2.6 Licensing Information 10

2.7 Backup Plan 10

3.0 System Design Information 11

3.1 Customer Specific Document Types 11

3.2 Customer Specific Notification Types 11

3.3 Customer Specific Lists 12

3.4 Customer Specific Project Template (Folder Structure) 12

3.5 Customer Specific Folder Defaults 13

3.6 PDM Licensing 13

3.7 Customer Specific Security Architecture 13

3.8 Internal Users 14

3.9 Customer Subcontractor Database 14

3.10 Print and Scan Locations 14

3.11 Subcontractor Portal Options 15

PDM Server Configuration

1.0 Server and Network Infrastructure

Record the necessary information below about the network and server infrastructure for the PDM system. You will need to record information about the DNS configuration, SQL server, web server, import server, file vault, SMTP setup, and domain user. This information will be needed during the PDM installation.

Make sure that server and network configurations meet the hardware and software requirements for PDM. Refer to the “PDM Hardware and Software Requirements Guide” for details.

Keep this information readily available after the PDM installation as a reference guide for administrators and support personnel.

1.1 DNS Configuration

· Domain Name (DNS):

· IP Address for DNS:

1.2 Database Server Configuration

1.2.1 SQL Server

· Operating System:

· Local IP Address:

· Hostname:

· Database Engine: Microsoft SQL Server 2005 / Microsoft SQL Server 2008

· Version: Standard / Enterprise

· Database Instance Name:

· Configured as Mixed Mode?: Yes / No

· Processor:

· RAM:

· Disk Size:

· Disk Speed:

1.3 Web Server Configuration

1.3.1 Load Balancer

· PDM Load Balancing?: Yes/No

· DNS Name:

· Local IP Address:

· Hostname:

· Load Balancer Device Name:

· DNS Accessible from Intranet (Internal)?: Yes / No

· DNS Accessible from Internet (External)?: Yes / No

· SSL Certificate?: Yes / No

1.3.2 PDM Web Server A

· Operating System: Windows 2003 Enterprise Edition R2 SP2 (32bit)

· DNS Name:

· Local IP Address:

· Hostname:

· Processor:

· RAM:

· DNS Accessible from Intranet (Internal)?: Yes / No

· DNS Accessible from Internet (External)?: Yes / No

· DNS Accessible from Web Server A?: Yes / No

· SSL Certificate?: Yes / No

· Code Signing Certificate?: Yes / No

· Code Signing Certificate Password:

1.3.3 PDM Web Server B (Only If Load Balancing)

· Operating System: Windows 2003 Enterprise Edition R2 SP2 (32bit)

· DNS Name:

· Local IP Address:

· Hostname:

· Processor:

· RAM:

· SSL Certificate?: Yes / No

· Code Signing Certificate?: Yes / No

· Code Signing Certificate Password:

1.4 Import Server Configuration

· Operating System: Windows 2003 Enterprise Edition R2 SP2 (32bit)

· Local IP Address:

· Hostname:

· Processor:

· RAM:

1.5 File Vault Configuration

· Disk Size:

· Disk Speed:

· Local Vault Share Location:

· Share Name:

· Server Name:

1.6 SMTP Configuration

· SMTP DNS Name:

· SMTP Local IP Address:

· SMTP Hostname:

· SMTP Port:

· SMTP User Name:

· SMTP Password:

· SMTP Use SSL?: Yes/No

1.7 Domain User Requirements

· Domain Username With Read-Write Access to the Share Name:

· Domain Password:

· Domain Username Contains “Log On as Batch Job” Local Security Privilege?: Yes / No

· Domain Username Contains Read-Write Access to Share Name?: Yes / No

2.0 Application Information

Enter the information requested below for PDM configuration information, PDM SQL information, PDM service accounts, .NET session state information, and license information. This information applies to this environment only and will change in additional installations.

2.1 PDM Configuration

· Base Directory:

· Installation Directory:

· PDM Administrator Username:

· PDM Administrator Password:

· Send As Email Address:

· Reply to Email Address:

· Aurigma Upload License:

· Aurigma Download License:

· Fax Provider:

· Fax Provider Username:

· Fax Provider Send Code:

· Report Server URL:

· Import Server URL:

2.2 PDM SQL Configuration

· PDM SQL Account

o Username:

o Password:

· PDM SQL Account Contains “dbCreator” Privilege?: Yes / No

· PDM Databases

o PDM Database Name: PDM_<CUSTOMERNAME>

o PDM Import Server Database Name: PDMImportServer

· ASPState20 (only applicable if using SQL Session State)

o Username:

o Password:

· File Paths

o Data:

o Logs:

2.3 PDM Service Accounts

The usernames and passwords for the PDM services should be the same as the Domain User information listed in the Domain User Requirements section.

· PDM Import Service I Account

o Username:

o Password:

· PDM Import Service O Account

o Username:

o Password:

· PDM Import Service V Account

o Username:

o Password:

· DFS Notification Processor

o Username:

o Password:

· DFS Order PreProcessor

o Username:

o Password:

· MHC Company Transfer Queue Processor

o Username:

o Password:

· MHC Project Transfer Queue Processor

o Username:

o Password:

· MHC Project File Transfer Queue Processor

o Username:

o Password:

2.4 Remote Access For Servers

· Remote Access Allowed?: Yes / No

· Remote Access Method:

· Remote Access IP/DNS:

· Remote Access Username:

· Remote Access Password:

2.5 .NET Session State Configuration

· Machine Key (only applicable if using SQL Session State):

· Validation Key Length: 64

· Encryption Key Length: 24

· Type: 3DES

· Validation Value: 1EA958EF3FC040F079ADA5C28B52B5CC75F64BA2DFCC3690CEE955AC6C1F9AED5380E3E0CA01C6CC4841FB8BD455D2B92EA0EC5B13201CD0CE819B61194A8672

· Decryption Value: B52692C67FF7AEE6B06DFB29F0975A07B53C9FB283A54EBD

2.6 Licensing Information

· Company Name:

· McGraw-Hill License Number:

· PDM Server License: Planroom / Collaboration / Pro / Enterprise

· Number of PDM Client Licenses:

· License Admin Email Address:

· License Admin Password:

2.7 Backup Plan

· Database Backup Plan:

· Vault Backup Plan:

· Full Image of All Servers Plan:

· Backups Stored Off-Server: Yes / No

· Backups Stored Off-Site: Yes / No

· Disaster Recovery Plan: Yes / No

3.0 System Design Information

Enter the information that was gathered during the System Design Meetings below. This information will be needed to properly configure PDM after the installation.

3.1 Customer Specific Document Types

Record the custom attributes or types that the customer needs (if any).

Custom Document Type / Attributes / Type / Required
<Custom DocType 1> / · <Attr1>
· <Attr2> / <Type>
<Type> / <Y/N>
<Y/N>
<Custom DocType 2> / · <Attr1>
· <Attr2> / <Type>
<Type> / <Y/N>
<Y/N>
<Custom DocType 3> / · <Attr1>
· <Attr2> / <Type>
<Type> / <Y/N>
<Y/N>

Record the customer specific duplicate keys, file parsing rules, and display names.

Custom Document Type / Duplicate Key / File Parsing Rule / Display Name
<Custom DocType 1>
<Custom DocType 2>
<Custom DocType 3>

3.2 Customer Specific Notification Types

Record the custom notification types that the customer needs (if any).

Custom Notification Types / Definition
<Custom Notification Type 1> / <Definition>
<Custom Notification Type 2> / <Definition>
<Custom Notification Type 3> / <Definition>

3.3 Customer Specific Lists

Record the custom lists and values that the customer needs.

Customer Specific Lists / Values
<List1> / <ListValue1>
<ListValue2>
<ListValue3>
<List2> / <ListValue1>
<ListValue2>
<ListValue3>
<List3> / <ListValue1>
<ListValue2>
<ListValue3>

3.4 Customer Specific Project Template (Folder Structure)

Record the customer specific folder structure that the customer has defined for their project templates.

Recommended Folder / Folder Options
Project Folders / System folder, cannot be edited.
<Folder 1>


<Folder 2>

3.5 Customer Specific Folder Defaults

Use the following table to define the defaults and default values for the specific folders. If some defaults apply to all folders in a project, it is advised that these be set on the Project and not the Folder.

Folder / Default / Default Value
Project Folders / System folder, no defaults can be set.
<Folder 1> / <Default>
<Default>
<Default> / <DefaultValue>
<DefaultValue>
<DefaultValue>


<Folder 2>

3.6 PDM Licensing

Enter the number of licenses purchased by the customer. Make sure that it matches their needs.

License / Number of Users
PDM Enterprise / <Number>, Site
PDM Pro / <Number>, Site
PDM Collaboration / <Number>, Site
PDM Bidding / N/A
PDM Planroom / PDM Planroom users do not need to be licensed.

3.7 Customer Specific Security Architecture

Enter the Roles and their definition that your customer needs.

Role / Definition

3.8 Internal Users

Use the table below to verify you have received the list of users.

Items Needed / Have Received
Master Lists of Users? / Yes / No
Are SysAdmins Identified? / Yes / No
Are Eval Admins Identified? / Yes / No
Are Prequal Admins Identified? / Yes / No
Are Users Identified? / Yes / No

3.9 Customer Subcontractor Database

Use the table below to verify you have received the listing of subcontractors.

Items Needed / Have Received
Subcontractor Database / Yes / No
Has it been cleaned? / Yes / No
Has it been formatted into the Contact Import Template? / Yes / No

3.10 Print and Scan Locations

Enter the address and contact information for the reprographers that the customer will use as their print and scan locations.

Reprographer / Location
<Reprographer 1> / Contact Name:
Address:
City, State, Zip:
Phone Number:
Fax Number:
Email:
<Reprographer 2> / Contact Name:
Address:
City, State, Zip:
Phone Number:
Fax Number:
Email:

3.11 Subcontractor Portal Options

Indicate in the table below when you have received the logos and other information for the subcontractor portal.

Option / Ready to Install
Portal Header / Yes / No
EULA (Rich Text Format) / Use Default EULA / Use Customer Specific EULA
Help Page (Rich Text Format) / Yes / No
Notification Logo / Yes / No
Prequalification Logo / Yes / No
Company Color Scheme / Yes / No

PDM Server Configuration

Adenium Systems

34103 Lakeshore Boulevard

Cleveland, OH 44095