Ivara EXP Installation Prerequisites

Full text

(1)

I v a r a E X P I n s t a l l a t i o n

P r e r e q u i s i t e s

(2)

used pursuant to applicable software license agreement; contains confi-dential and proprietary information of Bentley Systems, Incorporated and/or third parties which is protected by copyright and trade secret law and may not be provided or otherwise made available without proper authorization.

Bentley and the “B” Bentley logo are registered or non-registered trade-marks of Bentley Systems, Incorporated. All other trade-marks are the prop-erty of their respective owners.

Information in this document is subject to change without notice. Bentley Systems, Incorporated

5046 Mainway Burlington, Ontario Canada. L7L 5Z1 Tel: 905-632-8000 Fax: 905-632-5129 www.ivara.com

Ivara EXP Installation Prerequisites Published November 2013

Document identification code: IV-PR Document version code: 6.6

(3)

Contents

Installation Prerequisites . . . 5

Definitions. . . 5

Ivara EXP Enterprise Deployment Options . . . 6

Client Minimum Requirements . . . 8

Application Server Requirements . . . 9

Database Server Requirements . . . 10

Supported Database Software . . . 11

Citrix and Terminal Services Server Requirements . . . 12

Synchronization Service Provider for Mobile Computing . . . 13

Handheld Device Requirements . . . 14

Ivara EXP Integration to SAP® . . . 16

Ivara EXP Integration to IBM® Maximo® . . . 17

Ivara EXP Integration to Oracle® eAM . . . 18

Ivara EXP Integration to Isograph Availability Workbench® . . . . 19

(4)
(5)

Installation Prerequisites

This document defines the recommended minimum hardware and soft-ware for Ivara EXP server and client environments. Use this document as a reference before installing Ivara EXP to ensure proper configuration.

Note: While every effort is made to ensure the accuracy of this information, the specifications are a broad guide. If your system’s configuration does not meet the requirements specified in this document, contact Ivara EXP Technical Services for an evaluation or for guidance in deployment strategies that accommodate non-compliant technologies.

Definitions

Supported Configurations

Supported configurations are combinations of hardware, operating sys-tems, drivers, and other third-party software required for an Ivara EXP installation to function properly. They represent what we know to work with the confidence gained from normal quality assurance measures in multiple situations. These recommendations do not mean that other con-figurations will not support a functioning Ivara EXP installation.

Unsupported Configurations

Unsupported configurations are combinations of hardware, operating systems, drivers, and other third-party software that might degrade per-formance of an Ivara EXP installation or cause it to function improperly. While Ivara EXP will endeavour to assist customers with unsupported configurations, errors or support solutions might require fixes that involve the customer moving to a supported configuration or upgrading to the latest versions of third-party software.

(6)

Ivara EXP Enterprise Deployment Options

With release 6.0 and subsequent versions of Ivara EXP Enterprise there are a number of possible software configurations.

Smart-client Deployment

This deployment is most common and is generally recommended. It involves running a minimum software component set on the client con-nected to a physical or virtual application server. Different clients might connect to the same application server or to distinct application servers for scalability, if needed. This deployment uses a separate database server with which the application servers communicate.

Thick-client Deployment

This deployment avoids the need for a separate application server. The client computer runs the client software components, plus the application server software components, and connects to the separate database server. The application server can run either in the same process space as the client (using the -l option on the ivaraclient executable) or as a sep-arate software server instance. This deployment uses a sepsep-arate data-base server, to which the physical client communicates (via the

application server running locally on the client). Thick-client deployment with an in-process application server is required for definability (modifi-cation/extension of the core product’s object model and user interface).

(7)

Installation Prerequisites

Citrix

®

or Terminal Services Deployment

As with prior versions of Ivara EXP Enterprise, the client can be deployed using Citrix or Terminal Services if necessary. In this configu-ration, the Citrix Servers can deploy smart or thick clients.

Remote Computing Deployment

The remote computing client is a stand-alone deployment in that all soft-ware components that are required to run the application are local. The remote client software is comprised of a relatively small database, object model, and user interface.

The remote computing synchronization server is a Service Provider (pos-sibly running on its own application server) that allows remote comput-ers to synchronize with the main system.

(8)

Client Minimum Requirements

The table in this section outlines the minimum recommended hardware and software requirements for various Ivara EXP client deployments.

Smart Client Thick Client Remote Client

CPU Single or multi-core

1.5+ GHz Multi-core 2+ GHz Multi-core 1 GHz or better Memory 1 GB 2 GB 1 GB Display Resolution 1280 x 1024 1280 x 1024 1024 x 728

Operating System Microsoft® Windows® XP+ SP3, Windows

Vista® + SP1, or Windows 7 Windows 7

Database Software N/A See “Supported

Database Software” on page 11

Microsoft SQL Server 2008 R2 Express1

Other Software • Microsoft .NET 4.0 (plus the latest

patches) is required for client comput-ers

• Microsoft Office Outlook® 2003, 2007, or

2010 is required for sending emails from client computers

• Microsoft Excel® 20032, 2007, or 2010 is

required for exporting checksheets, tables, RFQ supplier bids, and so on

• Microsoft Project 2003, 2007, or 2010 is

required for exporting schedules (EAM module)

• Microsoft .NET

Framework 4.0 (plus the latest patches) is required for cli-ent computers3

• Microsoft Excel

2003, 2007, or 2010

1. If supported database software is not present on the computer, the Ivara Remote install utility prompts the user. With the user’s confirmation, the utility downloads and installs Microsoft SQL Server 2008 R2 Express.

2. Microsoft Excel 2003 has a limit of 65,000 rows. Exporting tables with more than 65,000 rows will fail.

3. If Microsoft .NET is not present on the computer, the Ivara Remote install utility prompts the user. With the user’s confirmation, the utility downloads and installs Microsoft .NET.

(9)

Installation Prerequisites

Application Server Requirements

The table in this section outlines the minimum recommended require-ments for Ivara EXP application server computers. It is based on the assumption that the application server will access the Ivara EXP data-base using a network ODBC connection.

Minimum Recommended

CPU 3 GHz Xeon multi core processor or faster.

Additional CPU cores should have significant benefit due to the multi-threaded nature of the application server software.

A minimum of one physical server core per 10 active concurrent users is recommended.

Memory A minimum of 2 GB with an additional 150 MB

per active concurrent user is recommended for each IvaraServer instance running on the appli-cation server.

Multiple instances of the application server exe-cutable or service per hardware server may improve scalability.

Operating System Microsoft Windows Server 2008 R2 Microsoft .NET

Framework

(10)

Database Server Requirements

In order for the Ivara EXP application to provide acceptable performance when accessing information stored in the database, the database server needs to be configured appropriately. Items to be considered include:

• Amount of memory • Number of CPUs

• Disk capacity and throughput • Network bandwidth

• Backup and recovery • Fault tolerance

• Configuration of the operating system and database options

Note: The database and master Ivara EXP installation can reside on the same computer. However, if the database server uses a non-Windows operating system (for example, if you are running Oracle on a Solaris™ machine), the master Ivara EXP installation

must be on a separate computer. This is because the Ivara EXP software only runs under a Windows operating system.

For help in server sizing and configuration, contact Ivara Technical Ser-vices. As a basic guideline, the Ivara EXP database consumes approxi-mately 1 GB of disk per 10,000 assets. Memory required is typically 10% of the database size. An example of a server processor on which an Ivara database has been successfully deployed is an HP Proliant DL380 G6 EE4450 with 2 CPUs.

(11)

Installation Prerequisites

Supported Database Software

This table shows which database management systems are supported for Ivara EXP Enterprise.

* The required Oracle 11.2.0.2 Client components are:

• SQL *Plus • Oracle Net

• Oracle Data Provider for .NET • Oracle Providers for ASP .NET

Note: If the 64-bit version of Ivara EXP is to be installed, be sure to install the 64-bit version of the Oracle Client components.

DBMS Client

Microsoft SQL Server 2005 SQL Server Native Client 2005 Microsoft SQL Server 2008 R2 SQL Server Native Client 2008

R2

(12)

Citrix and Terminal Services Server Requirements

The table in this section outlines the minimum recommended require-ments for setting up Ivara EXP on a Citrix® server or Windows Server

Terminal Services.

Note: We recommend that you set up your Citrix or Terminal Ser-vices server on a separate computer from your SQL Server or Ora-cle database.

The computer hosting your Citrix or Terminal Services server is subject to the same general requirements as any Ivara EXP client computer. For example, the SQL Server or Oracle Client component must be installed. The table below provides a sample of Citrix/Terminal Services configura-tions used successfully with Ivara EXP.

Memory • Average memory requirements vary from

75-256 MB per user depending on the level of customizations and the application fea-tures used

• Memory requirements can be reduced by

deploying Ivara application servers and hosting only smart clients on Citrix/Termi-nal Services Number of Concurrent Users Manufacturer (example)

Make/Type CPU Model #CPUs

per RAM Quantity 10 HP Proliant DL380 G6 EE5540 1 4 GB 1 20 HP Proliant DL380 G6 EE5540 1 8 GB 1 50 HP Proliant DL380 G6 EE5540 2 14 GB 1 100 HP Proliant DL380 G6 EE5540 2 14 GB 2

(13)

Installation Prerequisites

Synchronization Service Provider for Mobile Computing

A computer acting as a synchronization server for Ivara EXP Mobile.NET, Ivara Remote, or both has the following requirements:

Minimum Recommended

CPU 2 GHz processor, minimum. Multiple CPUs

or multiple cores are recommended. If you expect to require numerous concurrent uploads and downloads, more cores will help significantly.

Memory Minimum 4 GB. Memory requirements

depend on the total of handheld computers, tablets, or both that will be synchronized at simultaneously. 100MB RAM is required per concurrent upload or download.

Operating System1

1. The security setting “System cryptography: Use FIPS compli-ant algorithms for encryption, hashing, and signing” must be disabled. The synchronization server is not FIPS-compliant.

Windows Server 2008 R22

2. Microsoft SQL Server Native Client on Windows Server 2008 R2 is supported with SQL Server 2005 SP3 and SQL Server 2008 SP1. Install the 64-bit Native Client to see the 32-bit ODBC drivers.

The handheld synchronization server’s capacity is highly dependent on the memory (and processing power) of the server it is running on as well as the nature of the data being synchronized. Ivara has successfully tested the following using representative customer data:

40 concurrent synchronizations on a 4 core, 3 GB server. 120 concurrent synchronizations on an 8 core, 8 GB server.

Microsoft .NET Framework Microsoft .NET Framework version 4.0

(14)

Handheld Device Requirements

Handheld computers can be used to collect maintenance or inventory data to be uploaded into Ivara EXP. The Ivara Mobile.NET application is installed on each handheld device. The application is used to record indi-cator readings, which can also include attached images, or inventory counts.

Hardware and software requirements for handheld computers:

• Windows Mobile 5 • Windows Mobile 6 or 6.5

• Minimum memory requirement for the handheld device is 64 MB

with minimum free program memory of 24 MB

Note: A handheld device with 64 MB of memory will handle a lim-ited number of checksheets and indicators or count sheets and items. If you assign activities with many lines to a device, it will need more memory.

• Microsoft .NET Compact Framework 3.5. This software is provided in

the Ivara Mobile.NET installation package.

• Microsoft ActiveSync® or Windows Mobile Device Center is required

for installing Ivara Mobile.NET on the handheld computer. After installation, the handheld computer can use ActiveSync or Mobile Device Center to exchange data with the Ivara EXP database while docked to a work station. Alternatively, the handheld computer can connect to your Windows network either wirelessly or using an Ether-net® port.

• When a handheld computer is connected to the network wirelessly,

additional configuration might be needed to access the web service. This is true when a wireless security protocol such as PEAP (Pro-tected Extensible Authentication Protocol) or LEAP (Lightweight Extensible Authentication Protocol) is in use. Be sure to verify that the handheld supports your desired wireless security protocol. For example, PEAP can be supported by installing additional software on the handheld computer, such as the Juniper Networks® Odyssey

(15)

Installation Prerequisites

Ivara Mobile.NET works with the Ivara application server that performs the upload and download processes for Ivara Mobile.NET, Ivara Remote, or both. For more information, see “Synchronization Service Provider for Mobile Computing” on page 13.

Note: If you are upgrading from a previous Ivara EXP version, you must also upgrade the Ivara EXP program on each handheld computer. Review the instructions in “Upgrading Handheld Device Software” in the Ivara EXP Upgrade Guide.

(16)

Ivara EXP Integration to SAP®

Using the Computerized Maintenance Management System (CMMS) Integration functionality in Ivara EXP, you can exchange information about assets, work requests, work order tasks, standard tasks, and stan-dard jobs with SAP Plant Maintenance.

Note: The CMMS integration functionality does not work with sites where the EAM module is enabled.

Before installing or upgrading Ivara EXP, make sure that SAP® ECC and

SAP NetWeaver are installed and configured correctly. The integration solution is designed to work with the Plant Maintenance application. The integration plugin has been verified to work with:

• SAP ECC 6.0, Enhancement Pack 4 and SAP NetWeaver PI 7.1.1

(required for multi-language support and dynamic mapping) Note: The Ivara EXP integration plugin is certified by SAP for ECC 6.0, Enhancement Pack 4 and NetWeaver PI 7.1.

Ivara will make reasonable efforts to support later ECC and NetWeaver service packs.

For information about setting up and using the integration functionality, see either:

• Ivara EXP Integration Guide for SAP Plant Maintenance or • Ivara EXP Integration Guide for SAP Plant Maintenance with

(17)

Installation Prerequisites

Ivara EXP Integration to IBM® Maximo®

Using the CMMS integration functionality in Ivara EXP, you can exchange information about assets, work orders, standard tasks, and standard jobs with IBM Maximo Asset Management software.

Note: The CMMS integration functionality does not work with sites where the EAM module is enabled.

Before installing or upgrading Ivara EXP, make sure that IBM®

Max-imo® Enterprise Suite 6.x or 7.1.x is installed and configured correctly.

Note: For information about setting up Maximo 6.x, see the

Max-imo Enterprise Adapter System Adminstrator’s Guide. For

infor-mation about setting up Maximo 7.1.x, see the Integration Guide for IBM Maximo Asset Management 7.1.

The plugin has been verified to work with Maximo Enterprise Suite 6.0 and 7.1 (with Maximo Basic Services Release 7.1.1.4 Hot Fix Build:017). Ivara will make reasonable efforts to support later Enterprise Suite ser-vice packs.

Note: The Ivara EXP integration plugin for Maximo is certified “Ready for Tivoli” for IBM Maximo Enterprise Suite 6.0 and 7.1. For information about setting up and using the integration functionality, see Ivara EXP Integration Guide for IBM Maximo.

(18)

Ivara EXP Integration to Oracle® eAM

Using the Computerized Maintenance Management System (CMMS) Integration functionality in Ivara EXP, you can exchange information about assets, work requests, work orders, standard tasks, and standard jobs with Oracle eAM software.

Note: The CMMS integration functionality does not work with sites where the EAM module is enabled.

Before installing or upgrading Ivara EXP, make sure that Oracle®

E-Business Suite is installed and configured correctly. The integration solu-tion is designed to work with the Enterprise Asset Management (eAM) application.

The Ivara EXP application server computer requires:

• Oracle 11.2.0.2 Client components: • SQL *Plus

• Oracle Net

• Oracle Data Provider for .NET • Oracle Providers for ASP .NET

Note: If the 64-bit version of Ivara EXP is installed, be sure to install the 64-bit version of the Oracle client components.

The Oracle 11.2.0.2 client components must reside on the computer where the Oracle integration adapter is installed, typically, where the Ivara EXP integration server is installed.

These components can be downloaded from the Oracle web site.

The plugin has been verified to work with Oracle E-Business Suite 12.0.6 and 11.5.10. Ivara will make reasonable efforts to support later Oracle E-Business Suite service packs.

(19)

Installation Prerequisites

Ivara EXP Integration to Isograph Availability Workbench®

Using the integration functionality in Ivara EXP, you can export failure modes from MTA and RCM2 analyses to the Isograph Availability Work-bench (AWB), where you can analyze and optimize the data. You can then import optimization results into the Ivara EXP analysis, review the recommendations in the Optimization view, and make appropriate changes to the action plans.

Before installing or upgrading Ivara EXP, make sure that the following requirements are met:

• Isograph Availability Workbench v1.0 or later must be installed and

configured correctly.

For information about installing Availability Workbench, see

Avail-ability Workbench Installation and Licensing Guide from Isograph.

• Valid Isograph Availability Workbench license.

The plugin has been verified to work with Availability Workbench 1.0.0.36.1. Ivara will make reasonable efforts to support later Availabil-ity Workbench service packs.

For information about setting up and using the integration functionality, see Ivara EXP Integration Guide for Isograph Availability Workbench.

(20)

ODC Services Requirements

Description Requirements

OPC DA1

1. To use a smart client to browse data tags, install OPC Core Components Redistributable (x86) on the client computer, as well as OPC .NET API Redistibutable.

OPC Real Time

Data Access • OPC Core Components 3.00 (105.1) (x64) Redistributable

• Microsoft Visual C++ 2008

(x64) Redistributable

• OPC Core Components 3.00

(105.1) (x86) Redistributable

• OPC .NET API 2.0 (105.1)

Redistributable

• OPC DA 2.XX and OPC DA

3.0 Servers

OPC HDA2

2. To use a smart client to browse data tags, install OPC Core Components Redistributable (x86) on the client computer, as well as OPC .NET API Redistibutable.

OPC Historical

Data Access • OPC Core Components 3.00 (105.1) (x64) Redistributable

• Microsoft Visual C++ 2008

(x64) Redistributable

• OPC Core Components 3.00

(105.1) (x86) Redistributable

• OPC .NET API 2.0 (105.1)

Redistributable

• OPC HDA 1.2 Servers OSI Pi3 OSI Pi connectivity Pi SDK from OSISoft installed

and configured4

(21)

Installation Prerequisites

3. When running Ivara EXP in a 32-bit environment, install the 32-bit Pi SDK on both server and client computers.

When running Ivara EXP in a 64-bit environment, install the 32-bit Pi SDK first and then the 64-bit Pi SDK on the server. Note that a 64-bit thick client cannot browse data tags. To use a smart client to browse tags, install the 32-bit Pi SDK on the client computer.

4. Ivara EXP is validated with OSISoft SDK version 1.3.8.388 with Patch 1.3.8.391 for both 32-bit and 64-bit versions of the SDK.

Figure

Updating...

References

Updating...

Related subjects :