Pre-Installation Steps

Log on to all servers as a local administrator user.

Attention:

Logging on as DOMAIN ADMIN does not ensure you are a member of the local Administrators group.

Verify that the account you are using to log on to each machine belongs to the local Administrators group before you continue!

Make sure you use compatible software versions:

Gather the installation media on CD or DVD for ArtiosCAD, WebCenter, and Automation Engine (OBGE).

Only very specific versions of ArtiosCAD, WebCenter, and Automation Engine (OBGE) work with each other.

You CANNOT assume that a new version or build of one product will be compatible with older versions of the other products.

Software	Version	Build
ArtiosCAD	. . . . . .	. . . . . .
WebCenter	. . . . . .	. . . . . .
Automation Engine	. . . . . .	. . . . . .

Check the licenses for the Esko installers:

Gather Graphics and CAD licenses.
If this is an upgrade, you will need to ask for updated license files.
Check the license files against your software order.
Verify that the licenses have the correct number of users, the expiration date if applicable, and the correct ArtiosCAD, WebCenter, and Automation Engine (OBGE) version information.

Gather the required mail server information:

Note:

The mail server must be on the same network as the WebCenter Application Server.

Also, ensure this mail server has a send-only e-mail account already created for specific use with WebCenter notifications (this usually requires creation of an account such as webcenter@mycompany.com).

Mail Server Information	Value
Mail Server Name	. . . . . .
Mail Server IP Address	. . . . . .
SMTP Port	. . . . . .
WebCenter Sender Address	. . . . . .
SMTP Authentication User Name	. . . . . .
SMTP Authentication Password	. . . . . .

Gather the required database information from the database administrator:

Database	Item	Value
SQL Server	server name	. . . . . .
	“sa” password	. . . . . .
	database instance name	. . . . . .
	database port (default is 1433)	. . . . . .
Oracle Server	server name	. . . . . .
	‘sys’ password	. . . . . .
	TNS name	. . . . . .
	System ID (SID)	. . . . . .
	database port (default is 1527)	. . . . . .

Ask the database administrator whether a custom password for the 'webcenter' database user will be required and if so, retrieve the expected target password for this database user.

Perform a Web Server health check:

We highly recommend not to begin the install with the Web Server inside the DMZ. It is best to configure on a local LAN first.
Get all applications installed, configured, and fully functional before moving the Web Server inside the DMZ. Otherwise any required troubleshooting will be difficult and will take longer than needed.
Verify that Internet Information Services (IIS) is installed and its services are started: IISADMIN and W3SVC (World Wide Web Publishing).
Make sure the Server service is running.

Test the mail server connection:

Note:

Ensure that you can use telnet commands and that its port is not blocked in any way.

Make sure you test this before starting the installation. IT Administrators often block the required SMTP ports.

From the Application Server, open a command prompt.
Use a telnet command with the following syntax: telnet <mail_server_name_or_ip> <smtp_port#>.
For example, my mail server name is mail.eskowebcenter1.com and my SMTP port is 25.

I would type: telnet mail.eskowebcenter1.com 25.

You are looking for a successful response (for example like the one below); a 220 response is good.
```
telnet mail.eskowebcenter1.com 25Trying 62.204.32.250...Connected to mail.eskowebcenter1.com (62.204.32.250).220 mail.eskowebcenter1.com Mail Server; Mon, 2 Jun 2014 11:26:40 EST
```
Type QUIT to exit the telnet command.

Make sure the Server service is running on the Application Server.

Check the Database Server:

Ensure the correct database engine, version and service pack are installed. See section Install SQL Server 2012 Express Edition on the Database Server.
For SQL Server 2008/2012 or Express 2008/2012 verify these configurations:
- Must be configured to run in Mixed Mode for authentication;
- Language/Character set of SQL Server must match the Operating System language;
- TCP/IP must be enabled.
- If a named instance is used, the SQL Server Browser must be set to start automatically (and must be running).
This assumes that the system is protected by an external firewall.

Check performance for all servers:

For all servers (Web, Application, Database), ensure Windows System Performance is set to Adjust for Best Performance:
Go to Control Panel > System > Advanced and select Adjust for Best Performance from the Performance list.
Ensure Control Panel > Automatic Updates is set to Download updates for me, but let me choose when to install.
Windows Updates have been known to interfere with WebCenter operation: some updates lock down ports and stop services related to web and internet.

It is your responsibility to test Microsoft updates before applying them to production servers.
Ensure Windows Firewall is disabled:
Go to Control Panel > Network Connections , right-click on the active network connection and choose Properties. On the Advanced tab, ensure Internet Connection Firewall is disabled.
Stop and temporarily disable virus software.
Temporarily stop virus services on the Web Server and the Application Server as they are known to interfere with the WebCenter installation script.

Only after the software is installed should you enable the virus software again.