Proficy Plant Applications 4.2 Getting Started

Proficy Plant Applications 4.2 Getting Started

C

L U S T E R

I

N S T A L L A T I O N A N D

C

O N F I G U R A T I O N

Cluster Installation and Configuration

Plant Applications works with the Microsoft Cluster Administrator to ensure high availability of the Proficy server. If the primary Plant Applications node in the cluster experiences difficulties, Plant Applications is automatically started on another node to take over (a process known as failover). Server high availability is managed through the Microsoft Cluster

Administrator.

IMPORTANT:

You

must

purchase a license in order to use Plant Applications 5.0 in a clustered environment. After you purchase the cluster license, you will receive a hard key which must be installed on each Proficy Server in the cluster.

This guide will provide you with the information you need to deploy Plant Applications in a clustered environment, including:

• Overviews of the three validated and supported cluster configurations.

• Instructions for using the Microsoft Cluster Administrator to create a cluster.

• Instructions on using the Cluster Configurator to add cluster resources.

Assumptions

The information in this document assumes the reader has a thorough knowledge of the following:

• Microsoft Cluster Server

• Microsoft Windows Server 2003

• Configuring SQL Server 2005 in a cluster

Additionally, it is assumed that the instructions and guidelines provided by Microsoft for deploying server clusters using Microsoft Windows Server 2003 have been followed. For information on server clusters, visit the Microsoft TechNet Web site: http://technet2.microsoft.com/windowsserver/en/technologies/genclust.mspx

G

E T T I N G

S

T A R T E D

G

U I D E

55

P

L A N T

A

P P L I C A T I O N S

5 .0

Cluster Hardware Requirements

The hardware requirements set by Microsoft for clustered server and for clustered SQL server configurations must be met for systems deploying Plant Applications with cluster support. Consult your Microsoft operating system documentation for more information. For

Cluster Service documentation, visit the Microsoft TechNet Web site: http://technet2.microsoft.com/windowsserver/en/technologies/genclust.mspx

Supported and Validated Cluster Configurations

Before you begin installing Plant Applications, it’s important to determine what your architecture is so you can know where to install Plant Applications. There are three environments that have been validated and supported:

• One cluster, two nodes

• Two clusters, four nodes

• Three clusters, six nodes (SQL Server in its own cluster)

The only supported configuration of cluster groups is:

• Microsoft SQL Cluster Group – virtual node

• Plant Applications Server Cluster Group – virtual node

• Plant Applications Web Server Cluster Group – virtual node o

Includes IIS and FTP servers

• Proficy Historian (Archiver) Cluster Group – virtual node o

Includes both the data and alarm archivers

The following program installations should be on the local drives of the physical nodes:

• Windows Server 2003

• IIS and FTP

• SQL Server 2005

• Proficy Historian (data and alarm servers) installs (with identical options)

• Plant Applications Server and Web Server installs (with identical options)

56 G

E T T I N G

S

T A R T E D

G

U I D E

C

L U S T E R

I

N S T A L L A T I O N A N D

C

O N F I G U R A T I O N

The following data files are stored on the shared drives, which are accessed by the cluster group:

• SQL Server files

• Proficy Historian data files

• Plant Applications message buffer and log files

• Plant Applications Web site

Proficy Historian and Microsoft SQL Server must be installed and configured in the cluster according to instructions provided with those products.

One Cluster, Two Nodes

The following graphic shows an example of Plant Applications and other software installed on one cluster with two nodes.

G

E T T I N G

S

T A R T E D

G

U I D E

57

P

L A N T

A

P P L I C A T I O N S

5 .0

Two Clusters, Four Nodes

The following graphic shows an example of Plant Applications and other software installed on two clusters with four nodes.

Three Clusters, Six Nodes

The following graphic shows an example of Plant Applications and other software installed on three clusters with six nodes.

58 G

E T T I N G

S

T A R T E D

G

U I D E

C

L U S T E R

I

N S T A L L A T I O N A N D

C

O N F I G U R A T I O N

Creating a New Server Cluster

The Microsoft Cluster Administrator is included with Windows Server 2003 and is used to create the cluster and to add the nodes to the cluster. Visit the Microsoft TechNet Web site for documentation: http://technet2.microsoft.com/windowsserver/en/library/dba487bf-

61b9-45af-b927-e2333ec810b61033.mspx?mfr=true

NOTE:

Running Plant Applications in a cluster on Windows 2008 is not currently supported.

Creating Cluster Groups

In the Microsoft Cluster Administrator, create the necessary groups on each of the nodes.

Typically, a group is created for each of the following:

• SQL Server

• Proficy Server

• Plant Applications Web Server

• Proficy Historian

Each group requires a Physical Disk resource. The Proficy Server and Plant Applications

Web server groups require an IP Address and Network Name resource.

To create a cluster group

Please visit Microsoft’s Web site for complete and up-to-date instructions for creating a cluster group: http://msdn.microsoft.com/en-us/library/dd897474(BTS.10).aspx

G

E T T I N G

S

T A R T E D

G

U I D E

59

P

L A N T

A

P P L I C A T I O N S

5 .0

Installing and Configuring IIS and FTP

IIS is not installed by default with Windows 2003 Server. Therefore, it must be manually installed. Furthermore, in Windows 2003 Server, the following two scripts are available to configure clustering for IIS. Both these files are located in the Windows\System32\Inetsrv folder.

• For WWW services, Clusweb.vbs

• For FTP services, Clusftp.vbs

These steps are required only on the nodes that will be running the Plant Applications Web server.

To install and configure IIS and FTP

Please visit Microsoft’s Web site for complete and up-to-date instructions on installing and configuring IIS and FTP: http://support.microsoft.com/kb/887417

SQL Server 2005

Before you create a Microsoft SQL Server failover cluster, you must configure Microsoft

Cluster Service (MSCS) and use Cluster Administrator in Windows 2003 Server, Enterprise

Server to create at least one cluster disk resource on a shared drive.

You must install SQL Server on the active node of the cluster. If you are using SQL Client tools, they must be manually installed on each computer.

IMPORTANT:

Make note of the location of the shared drive in the Cluster Administrator before you run SQL Server Setup; you need this information to create a new failover cluster.

To create a new failover cluster with SQL Server 2005

Please visit the Microsoft MSDN Web site for complete and up-to-date instructions on creating a failover cluster with SQL Server 2005: http://technet.microsoft.com/enus/library/ms179530(SQL.90).aspx

60 G

E T T I N G

S

T A R T E D

G

U I D E

C

L U S T E R

I

N S T A L L A T I O N A N D

C

O N F I G U R A T I O N

Before Installing Plant Applications

Before you begin installing any Proficy software, please ensure that you have:

1

Purchased and installed the cluster key.

2

3

4

Installed Windows 2003 Server on each node that will be part of the cluster.

Used the Cluster Administrator (included with Windows 2003 Server) to:

a

Create the cluster.

b c

Add the nodes to the cluster.

Create the cluster groups.

Installed and configured IIS on the Web Server node.

5

6

Installed FTP on the Web Server node.

Installed Adobe Acrobat on the Web Server node.

Installed Microsoft Word and Excel on the Web Server node.

7

8

Installed any Microsoft updates on all nodes.

9

Installed SQL Server 2005.

10

Installed Proficy Historian (see the Proficy Historian documentation for installation instructions).

11

Installed Proficy Enterprise Connector.

12

Installed Proficy Real-time Information Portal 3.0 or newer (see the Proficy Realtime Information Portal documentation for installation instructions).

Installing the Proficy Enterprise Connector

In the supported cluster group configuration, the Enterprise Connector service runs in the

Plant Applications Server cluster group. The BizTalk server runs outside the cluster.

G

E T T I N G

S

T A R T E D

G

U I D E

61

P

L A N T

A

P P L I C A T I O N S

5 .0

A single BizTalk Server may talk to several Plant Applications Servers, by configuring separate locations (using the Plant Applications Adapter) for each Plant Applications Server.

To install the Proficy Enterprise Connector

Please see the Proficy Enterprise Connector documentation for instructions on installing and using the Proficy Enterprise Connector.

Installing the Proficy Server

NOTE:

If you are installing Proficy Server and SQL Server 2005 on separate nodes, you must manually enable the TCP/IP protocol. It cannot be enabled remotely.

NOTE:

The Proficy Server services ports can be modified using the CXS_Service table in the Plant

Applications database.

The Proficy Server services are automatically installed on the node from which the Proficy

Server installation is run. If you want the Proficy Server services installed on one node and the Proficy database installed on a different node, you must run the Proficy Server installation on the node where you want the Proficy Server services installed. During the installation, you are asked to identify the SQL Server node where you want to install the

Proficy database.

62 G

E T T I N G

S

T A R T E D

G

U I D E

C

L U S T E R

I

N S T A L L A T I O N A N D

C

O N F I G U R A T I O N

IMPORTANT:

You must install your hardware key BEFORE installing the Proficy Server and

in the cluster must have a hardware key.

local drive

(not shared drive) on each node in the

must

be running.

except each node

for Proficy

You must install the Proficy Server on the

cluster that will support the Plant Applications processes. Additionally, you must install it in the same location on all nodes.

If you are using SQL Server 2005, the SQL Server Browser service

If you have installed the Proficy Server on the first node, before you install Proficy Server on other

nodes, you must stop all Proficy Server and Plant Applications services,

Licensing service; it must be running.

If SQL Server is active on the node on which you are installing Plant Applications, you must fail

it over to a different node on the cluster because the Plant Applications installation program stops the cluster services.

To install the Proficy Server

See page 28 for instructions on installing the Proficy Server.

Installing the Plant Applications Web Server

Before you install the Plant Applications Web Server software, you must first install the

Proficy Server. You also need to determine the account the Plant Applications engines will be using to start up. The account must have Log on as a service rights. The Plant

Applications engines will not start up under the Local System account.

To install the Plant Applications Web Server

Please see page 38 for instructions on installing the Plant Applications Web Server.

G

E T T I N G

S

T A R T E D

G

U I D E

63

P

L A N T

A

P P L I C A T I O N S

5 .0

Installing the Plant Applications Clients

IMPORTANT:

If you installed the Plant Applications Clients on the first node, before you install Plant

Applications Clients on other nodes, you must stop all Proficy Server and Plant Applications services,

except

for Proficy Licensing service; it must be running.

If SQL Server is active on the node on which you are installing Plant Applications, you must fail

it over to another node on the cluster because the Plant Applications installation program stops the cluster services.

To install the Plant Applications Clients

Please see page 50 for instructions on installing the Plant Applications clients.

Adding the Plant Applications Resources

Before adding the Plant Applications resources to the appropriate cluster groups, you must first install the Proficy Server, Proficy Web Server, and Plant Applications on the appropriate nodes in the cluster.

NOTE:

The following steps need to be completed on only one node because the resources are added to the resource group and not a specific node.

To add Plant Applications resources

1

2

3

4

5

On an active node, open Windows Explorer and locate ClusterConfigurator.exe.

By default, it is installed at:

C:\Program Files\Proficy\Proficy Server\Server

Double-click ClusterConfigurator.exe. The Plant Applications Cluster

Configurator appears.

Select Add resource to cluster and click Next.

From the Resource type list, select the Proficy Server resource.

From the Group list, select the Proficy Server cluster group and click Next.

64 G

E T T I N G

S

T A R T E D

G

U I D E

C

L U S T E R

I

N S T A L L A T I O N A N D

C

O N F I G U R A T I O N

6

Add the appropriate nodes and click Next.

7

Click Finished to accept the default restart parameters, or adjust the parameters and click Finished.

– or –

Click Restart to restart a resource or click Do not restart to allow the resource to fail.

If you want the Cluster service to restart the resource, you must specify whether to affect the group. If you want the group to fail over when this resource fails, select

Affect the group, and then enter the values you want in Threshold and Period.

These values determine how many times the Cluster service attempts to restart the resource before failover and the amount of time in which the threshold number of restart attempts takes place. If Affect the group is not selected, a failure of this resource never causes the group to fail over.

Under “Looks Alive” poll interval, specify how often the Cluster service checks the registered state of the resource to determine whether the resource appears to be active. Select Use value from resource type to use the default interval for the resource type or select Specify value to specify an interval (in milliseconds).

G

E T T I N G

S

T A R T E D

G

U I D E

65

P

L A N T

A

P P L I C A T I O N S

5 .0

Under “Is Alive” poll interval, specify how often the Cluster service checks the state of the resource to determine whether the resource is active. Select

Use value

from resource type to use the default interval for the resource type or select

Specify value to specify an interval (in milliseconds).

In the Pending timeout box, type the amount of time, in seconds, that a resource in a pending state (Online Pending or Offline Pending) has to resolve its status before the Cluster service puts the resource in Offline or Failed status.

66

8

Repeat steps 3 – 7 to add the Web Server resource to the Plant Applications Web server group and to add the Remote Data Service resource to the Cluster group or to the cluster group that has Proficy Historian configured.

9

Bring all groups online.

10

Open Excel on all nodes where it is installed and log in to the Plant Applications

Add-in.

G

E T T I N G

S

T A R T E D

G

U I D E

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents