Aspen InfoPlus.21 Product Family
Installation Guide
Version: V10
June 2017
Copyright (c) 1998 – 2017 by Aspen Technology, Inc. All rights reserved.
Aspen Audit & Compliance Manager, Aspen Data Source Architecture Directory Server, Aspen InfoPlus.21,
InfoPlus.21 Administrator, Aspen KPI Builder, Definition Editor, Aspen Local Security Server, Aspen Framework
Server, Software License Manager, Business Process Explorer, Event.21, Aspen Process Explorer, Aspen Production
Execution Manager, Aspen Production Record Manager, Aspen SQLplus, Aspen Tag Browser, Aspen Real-Time SPC
Analyzer, the aspen leaf logo, and Plantelligence & Enterprise Optimization Solutions are trademarks or registered
trademarks of Aspen Technology, Inc., Bedford, MA.
All other brand and product names are trademarks or registered trademarks of their respective companies.
This manual is intended as a guide to using AspenTech’s software. This documentation contains AspenTech
proprietary and confidential information and may not be disclosed, used, or copied without the prior consent of
AspenTech or as set forth in the applicable license agreement. Users are solely responsible for the proper use of
the software and the application of the results obtained.
Although AspenTech has tested the software and reviewed the documentation, the sole warranty for the software
may be found in the applicable license agreement between AspenTech and the user. ASPENTECH MAKES NO
WARRANTY OR REPRESENTATION, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THIS
DOCUMENTATION, ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR
PURPOSE.
Aspen Technology, Inc.
20 Crosby Drive
Bedford, MA 01730
USA
Phone: + (781) 221-6400
Toll Free: (1) (888) 996-7100
http://www.aspentech.com
Contents
1 Introduction .........................................................................................................1
InfoPlus.21 Product Family ................................................................................1
Technical Support ............................................................................................2
2 Overview ..............................................................................................................3
aspenONE Overview .........................................................................................3
Licensing...............................................................................................3
aspenONE Media ....................................................................................4
Organization ..........................................................................................4
aspenONE Licensing Model ......................................................................5
Accessing aspenONE Documentation ........................................................6
aspenONE Manufacturing and Supply Chain Overview ...........................................6
System Requirements.......................................................................................7
Additional Notes.....................................................................................7
User Requirements .................................................................................8
Directory Locations and References ....................................................................9
References in this Document ...................................................................9
File Locations for New V7.2 and Later Installations .....................................9
Programs Requiring Administrator Rights .......................................................... 11
3 Installing for the First Time................................................................................13
Before You Install........................................................................................... 14
Installing the InfoPlus.21 Family of Products...................................................... 14
Getting Started .................................................................................... 14
aspenONE Installer Welcome ................................................................. 17
License Terms and Conditions ................................................................ 18
Prerequisite Validation .......................................................................... 19
Product Selection ................................................................................. 20
File Location ........................................................................................ 21
Specify Licensing and Security ............................................................... 22
Specify Account Information .................................................................. 23
Verify Your Installation ......................................................................... 24
Installation Progress ............................................................................. 24
Installation Complete............................................................................ 25
4 After Installing for the First Time.......................................................................27
After Installing InfoPlus.21 .............................................................................. 27
Set Maximum Point Count ..................................................................... 27
Starting InfoPlus.21.............................................................................. 28
Verifying the InfoPlus.21 Installation ...................................................... 29
After Installing Aspen Calc............................................................................... 29
Verifying the Aspen Calc Installation ....................................................... 29
Contents
iii
After Installing Cim-IO .................................................................................... 30
Verifying the Cim-IO Installation ............................................................ 30
After Installing ADSA ...................................................................................... 30
Verifying the ADSA Installation .............................................................. 31
After Installing Process Explorer....................................................................... 32
Verifying the Process Explorer Installation ............................................... 32
Load and Test Process Data Add-In in Microsoft Excel ............................... 33
After Installing SQLplus................................................................................... 33
Verifying the SQLplus Installation........................................................... 34
After Installing aspenONE Process Explorer ....................................................... 34
Configuring ADSA................................................................................. 34
Verifying the aspenONE Process Explorer Installation................................ 35
Populating the Search Database............................................................. 35
Check for Updates .......................................................................................... 36
5 Upgrading or Repairing an Existing Installation .................................................37
Before You Upgrade........................................................................................ 38
Saving a Snapshot ............................................................................... 38
Saving the Group Configuration File........................................................ 41
Save the SQLplus ODBC Link Files .......................................................... 41
Copying the oktomodify.inp File to the group200 Folder ............................ 41
Stopping Cim-IO Processes.................................................................... 42
Shutting Down Services ........................................................................ 42
Upgrading the InfoPlus.21 Family of Products .................................................... 43
After You Upgrade .......................................................................................... 43
After Upgrading InfoPlus.21................................................................... 43
After Upgrading Cim-IO ........................................................................ 46
After Upgrading ADSA........................................................................... 47
After Upgrading Process Explorer ........................................................... 47
After Upgrading SQLplus ....................................................................... 47
Check for Updates .......................................................................................... 47
6 Replication Upgrade Planning ............................................................................49
Introduction .................................................................................................. 49
Pre-Installation .............................................................................................. 49
Post-Installation............................................................................................. 50
7 Removing Features and Subfeatures ..................................................................51
Before You Remove ........................................................................................ 51
Backing up Additional Files .................................................................... 52
Removing Features and Subfeatures................................................................. 53
After You Remove .......................................................................................... 53
Removing User Application and Registry files ........................................... 54
Removing Shares ................................................................................. 54
8 Transferring InfoPlus.21 from One Computer to Another ...................................55
Using the Data and Configuration Transfer Wizard.............................................. 55
Enabling Logging of Messages................................................................ 56
Data and Configuration Transfer Wizard Interruption ................................ 57
Manually Transferring Data and Configuration Information .................................. 57
iv
Contents
9 Troubleshooting .................................................................................................63
Aspen InfoPlus.21 .......................................................................................... 63
Manual resetting of SETCIM_GROUP_NAME registry key............................ 63
Missing “InfoPlus.21” from InfoPlus.21 Administrator................................ 64
Missing InfoPlus.21 data source from InfoPlus.21 Administrator ................. 65
InfoPlus.21 Administrator Access Denial.................................................. 66
InfoPlus.21 Administrator Cannot Access InfoPlus.21 v4.x (or earlier)......... 66
ADSA............................................................................................................ 67
Class not registered (The specified Windows NT host is not an ADSA
Directory Server) ................................................................................. 67
A remote activation was necessary but the server name provided was
invalid (Unable to resolve server hostname to IP address.)........................ 67
Access denied ...................................................................................... 68
Process Explorer ............................................................................................ 68
Cannot open a new file in Aspen Process Explorer .................................... 68
Cannot save a file in Aspen Process Explorer ........................................... 68
Cannot open VBA in Aspen Process Explorer ............................................ 69
Cannot open the Graphics Editor ............................................................ 69
Cannot access a data source.................................................................. 69
Error message during the installation of Aspen Process Explorer: ............... 70
Error message when you try to start Aspen Process Explorer: .................... 70
Error message when uninstalling:........................................................... 70
Data does not pass through a firewall ..................................................... 71
Glossary ................................................................................................................73
Appendix A – InfoPlus.21 Product Family Overview ..............................................77
Aspen Calc .................................................................................................... 77
Aspen Cim-IO ................................................................................................ 78
ADSA Directory Server.................................................................................... 78
ADSA Server ....................................................................................... 79
ADSA Client......................................................................................... 79
Data-consuming client versus data-producing applications ........................ 79
ADSA Client installs versus ADSA Directory Server installs ........................ 80
Data Source ........................................................................................ 80
Service Component .............................................................................. 81
Logical Collections of Databases ............................................................. 81
Aspen InfoPlus.21 .......................................................................................... 81
Aspen Process Explorer ................................................................................... 82
Aspen SQLplus............................................................................................... 82
Appendix B - Related Documentation ....................................................................83
Printed documentation .......................................................................... 83
Help files............................................................................................. 83
Appendix C - Installing Internet Information Services (IIS) .................................85
Appendix D - Aspen Manufacturing Suite S95 Solution..........................................89
Aspen S95 Naming Conventions....................................................................... 89
mMDM Database ............................................................................................ 90
Tag Browser and Tag Search ........................................................................... 90
Contents
v
Installing and Configuring an AMS S95 Solution ................................................. 90
Creating an mMDM Database ................................................................. 91
Creating an mMDM XML File .................................................................. 91
Setting Up ADSA .................................................................................. 91
Adding Additional Tags and Aliases................................................................... 91
Searching for S95 Tag Aliases.......................................................................... 91
Aliases in Graphics ......................................................................................... 92
Appendix E – Virtual Machine Recommendations ..................................................93
vi
Contents
1 Introduction
This document describes how to install the Aspen InfoPlus.21 (InfoPlus.21)
product family V10. Installations are supported on the operating systems
detailed in the System Requirements section in the “Overview” chapter.
This guide is ideally suited to system administrators or anyone who is
required to install, configure, and manage the products and aspenONE
application implementation.
InfoPlus.21 Product Family
The instructions in this guide focus solely on installing the InfoPlus.21 product
family. The InfoPlus.21 product family includes:

Aspen InfoPlus.21

Aspen Calc

Aspen Cim-IO

Aspen Cim-IO Interfaces

Aspen Data Source Architecture (ADSA)

Aspen KPI Builder

Aspen OPC UA Explorer

Aspen Process Data

Aspen Process Explorer

Aspen Real-Time SPC Server

Aspen SQLplus

aspenONE Process Explorer
There are other Aspen Manufacturing products that you may use in
conjunction with the Aspen InfoPlus.21 product family. When installing other
products, see those particular products’ installation guides.
For more information about the InfoPlus.21 product family, see “Appendix A
– InfoPlus.21 Product Family Overview” on page 77.
For a list of related documentation that may be of help to you, see
“Appendix B - Related Documentation” on page 83.
1 Introduction
1
Technical Support
AspenTech customers with a valid license and software maintenance
agreement can register to access the online AspenTech Support Center at:
https://support.aspentech.com
This Web support site allows you to:

Access current product documentation

Search for tech tips, solutions and frequently asked questions (FAQs)

Search for and download application examples

Search for and download service packs and product updates

Submit and track technical issues

Send suggestions

Report product defects

Review lists of known deficiencies and defects
Registered users can also subscribe to our Technical Support
e-Bulletins. These e-Bulletins are used to alert users to important technical
support information such as:

Technical advisories

Product updates and releases
Customer support is also available by phone, fax, and email. The most up-todate contact information is available at the AspenTech Support Center at
https://support.aspentech.com.
2
1 Introduction
2 Overview
This chapter provides an overview of aspenONE, including the installation
requirements and process. It contains the following:

aspenONE Overview

Aspen Manufacturing Suite Overview

System Requirements

Directory Locations and References

Programs Requiring Administrator Rights
aspenONE Overview
aspenONE® is AspenTech’s comprehensive set of software solutions and
services. aspenONE products enable process industry companies to optimize
their engineering, manufacturing and supply chain operations. As a result,
AspenTech customers are better able to increase capacity, improve margins,
reduce costs, become more energy efficient, and achieve operational
excellence goals.
aspenONE solutions include the industry’s leading:

Simulation and design products in the aspenONE Engineering suite

Plant operations products in the aspenONE Manufacturing suite

Supply chain management products in the aspenONE Supply Chain suite

Predictive and prescriptive analytic products in the aspenONE Asset
Performance Management suite
The token-based aspenONE Licensing Model gives customers the flexibility to
access and use any aspenONE product at precisely the time it is needed. This
is especially critical in the dynamic market conditions of the process industries
‒ whether during down economies or in high-growth periods. This enables
customers to lower their risk while maximizing the return on their software
investment.
Licensing
To manage your product entitlement, you will receive one of the following
separately:
2 Overview
3

A license file if you are using the SLM Server to manage the products to
which you are entitled.

A pre-configured dongle containing your customer license file if you are
operating using a dongle to manage the products to which you are
entitled.
Note: An invoice noting which products you are licensed for is also sent
separately from the software shipment.
aspenONE Media
Unless you have specifically requested a USB drive, you will receive
instructions on how to download the aspenONE V10 media.
You will have access to one or more of the following:
o
aspenONE Token Media – Contains the media that supports the
aspenONE Licensing Model token-based system. This all-inclusive
token-based licensing model was introduced in July 2009. Under this
licensing model, customers are entitled to install and run all of
AspenTech’s products as long as they have purchased sufficient
tokens. To install software purchased under this commercial
agreement, use this media. Software installed from the aspenONE
Token media requires run-time token-based license keys.
o
aspenONE Standard Media – Contains the media that supports
perpetual and pre-aspenONE Licensing Model token-based systems. If
you have perpetual license agreements or token-based license
agreements by product (pre-July 2009), you should use the media
labeled Standard. Software installed from the aspenONE Standard
media requires older license keys that have been in use since the
aspenONE 2004 release.
o
Informatica – If you have an MSC perpetual license purchased prior
to 2011 and are entitled to Informatica upgrades, you will receive both
the Standard media and a standalone Informatica media containing a
new version of Informatica PowerCenter.
Note: The Getting Started brochure and the product Release Notes and
Installation Guides are included under each suite’s folder.
Organization
The aspenONE media delivers AspenTech’s Process Modeling, Exchanger
Design and Rating, Economic Evaluation, Energy and Flare Analysis, Process
Development and Operations Support, Plant Operations, Process Control,
Supply Chain Management, and Asset Performance products and
documentation.
The media is organized in the following folders:

4
Aspen Engineering (32-bit and 64-bit) – includes all Aspen Engineering
products, Aspen PIMS and Aspen Administration components (Aspen SLM,
Aspen SLM tools, ALC Auto Upload Tool).
2 Overview

Aspen Manufacturing and Supply Chain – includes all Aspen
Manufacturing products (Information Management, Batch, Production
Management, and Advanced Process Control), Aspen Petroleum Supply
Chain products, aspenONE Supply Chain Management products, and
aspenONE Infrastructure products as well as Aspen Administration
components (Aspen SLM, Aspen Security, Aspen SLM tools, aspenONE
Diagnostics, ALC Auto Upload Tool).

aspenONE Asset Performance Management – includes all APM
products (Aspen Asset Analytics, Aspen Fidelis Reliability, Aspen Mtell,
Aspen ProMV).

aspenONE Software License Manager includes all Aspen
Administration components (Aspen SLM, Aspen SLM tools, ALC Auto
Upload Tool).
Installation Guides and Release Notes are included in the Documentation subfolders under each family of products.
Notes:


When you deploy aspenONE V10 software on client machines, the SLM
server should be from the V10 release. When migrating to a new version
of aspenONE, the SLM Server should always be upgraded first, followed by
the SLM clients. This is done to avoid any potential incompatibility issues.
During this transition period, it is possible to have clients at a lower
version than the SLM Server.
Some products previously available on CD-ROM or DVD are not included
on the aspenONE media. If you do not find a product, please contact
AspenTech Support at https://support.aspentech.com.
aspenONE Licensing Model
The aspenONE Licensing Model is a flexible token-based approach to software
licensing. This unique and innovative commercial model makes it easier for
customers to use software when and where they need it. Customers have
access to all current and future AspenTech products with just one contract.
Upgrading to the aspenONE Licensing Model for
Manufacturing and Supply Chain V8.x and above
If you have recently signed a new aspenONE Licensing Model agreement or if
you have superseded an old license agreement with an aspenONE Licensing
Model token-based license agreement for aspenONE Manufacturing and
Supply Chain, you will receive a new token-based license file for V9. During
installation of any product in Aspen Manufacturing and Supply Chain, you will
get a message indicating that the newly installed software will use the tokenbased license key. Accepting the warning message enables you to install the
software.
Note: If you do not have the updated token-based license file, please contact
AspenTech Customer Support.
2 Overview
5
Accessing aspenONE Documentation
Documentation is available directly from the applications. This eliminates the
need to search for the documents that you need and ensures that you can
always find the most current version of the document that you are looking
for.
Documentation can be found in the following ways:

Installation Guides and Release Notes can be found by selecting Browse
contents of USB on the suite selection page or by clicking the
corresponding link on the Welcome page of the aspenONE Installer.

Context-sensitive help can be accessed by:

o
Clicking the Help button on an application dialog box
o
Pressing F1 while in the application
o
Clicking the application’s Help menu and selecting Help
o
Clicking
on the uBar. Some help systems display Help for the
current page, while others open the Help at a higher level, where you
can browse or search for the desired help topic.
Additional documents in PDF format can be accessed by:
o
Clicking Online Documentation on the product’s Start page or Start
tab or selecting Documentation from the product’s Help menu. This will
open the Online Documentation Center from which you can view
and/or download the product-specific documents.
o
Logging onto the AspenTech Customer Support site, clicking
to
display the left-hand navigation menu, clicking Find the Answer from
that menu, and selecting Product Documentation. Your home page
displays the Browse for Documentation section; you can select a
Family, Product, and Version. Click Go and a list of the available
documentation is displayed.
o
Downloading all of the available documentation (other than Help files)
from the AspenTech Customer Support website via the zip file of the
aspenONE Documentation.
aspenONE Manufacturing and
Supply Chain Overview
The aspenONE Manufacturing and Supply Chain applications deliver
production dispatching, production execution, historical data management,
advanced control, inferential modeling, process analysis, process monitoring,
production tracking, and quality management services for manufacturing and
supply chain environments. The InfoPlus.21 product family is part of the
aspenONE Manufacturing and Supply Chain suite of products.
6
2 Overview
System Requirements
For the most up-to-date hardware and software requirements that must be
met in order to install AspenTech products, refer to the following website:
https://www.aspentech.com/platform-support/
Additional Notes
2 Overview

Mixed versions of AspenTech software on the same machine is not
supported and will likely cause some applications to be non-functional.

When running software on a virtual machine, the machine should also
meet these requirements.

Memory requirements are highly dependent on the number and type of
applications. Additional disk space may be required for larger applications
and data sets. The numbers listed above are guidelines.

Aspen InfoPlus.21 server, while not a web server, should meet the
requirements for web servers.

It is recommended that you do not install InfoPlus.21 on a computer
that is also functioning as a primary domain controller. When acting as a
domain controller, the operating system sets the authentication tasks
higher than InfoPlus.21, thus degrading the performance of InfoPlus.21.

It is recommended that you install web applications on a dedicated
Windows Server.

It is strongly recommended that you do not install Aspen web applications
on a Windows Terminal Server.

Memory allocation for Historian purposes is not included. Disk space for
Historian depends on number of points, time averages compression factor,
and number of the historized months. Additional disk space is also
required by InfoPlus.21 replication queues if InfoPlus.21 replication is
enabled.

With the exception of SanDisk® storage on a dedicated fiber optic
network, using remote drives seriously degrades performance and
increases potential connectivity issues that may result in data loss;
therefore, AspenTech recommends installing history repositories and file
sets on a local drive to optimize performance and minimize the possibility
of losing the connection to the repository drive.

If both the Sun and Microsoft JVM are installed on the same computer,
disable the Microsoft JVM plug-in before using the web application to
ensure that the Microsoft JVM does not conflict with Sun's JVM.

AspenTech provides best practices to assist customers who may use
Microsoft Application Virtualization 5.1 for deployment of our Engineering
products. Implementation of aspenONE applications with Microsoft
Application Virtualization requires the user to create packages while
accounting for the target computing environment and corporate software
deployment policy. Due to external technical reasons beyond our control,
AspenTech cannot guarantee support for all possible combinations of
7
product packages, target computing environments and corporate software
deployment policies. Please contact Customer Support for assistance.

Open File Manager software, like Legato, can interfere with InfoPlus.21
archiving methods. Therefore, to avoid substantial data loss, we
recommend that Open File Manager software exclude open InfoPlus.21
files.

Installation of Microsoft .NET Framework (a required component) changes
the PathWWWRoot Registry keys to the default C:\inetpub\wwwroot. For
installation and configuration of IIS, see Appendix C - Installing
Internet Information Services (IIS) on page 85.

Microsoft does NOT support moving IIS 7.0 and later from its default
location. Please see Microsoft KB article
//support.microsoft.com/kb/2752331

Both 32-bit and 64-bit drivers must be installed for third-party databases.

ODBC drivers delivered with supported database versions are also
supported and tested.

Microsoft Message Queue (MSMQ) is required for IP.21 Server database
replication backward compatibility. MSMQ can be installed before or after
InfoPlus.21. Port required by MSMQ must be open in the firewall.

For appropriate network speed, Microsoft TCP/IP network (minimum 100
Mbps LAN) is required for all InfoPlus.21 family products.

Aspen Framework (AFW) should be installed prior to installing Aspen
InfoPlus.21.

Aspen Local Security (ALS) can be installed at the same time as Aspen
InfoPlus.21 if they are installed on the same system.

AFW or ALS can be installed on the server computer or on a different
computer on the same network.

For customers who use other LDAP servers for authentication, AspenTech
requires Microsoft Active Directory.
User Requirements
The following is required for installers and administrators
of all InfoPlus.21 family products:

The user installing the software must have administrator privileges.
The following is required for users of InfoPlus.21:

8
The InfoPlus.21 host computer platform must be able to authenticate any
remote users that connect to InfoPlus.21.
2 Overview
Directory Locations and
References
File locations for AspenTech applications depend on your operating system.
For details, see “References in this Document.”
In addition, some file locations for new V7.2 and later installations have
changed from previous versions. For details, see “File Locations for New V7.2
and Later Installations.”
Note: If you install to a location other than the default system drive, file
locations are unchanged from V7.1 and earlier.
References in this Document
This guide uses the following terms to refer to the folders for installed V7.2
and later AspenTech program files.
<ASPENROOT>
Root directory chosen during installation for AspenTech program files.
Typically, this is:

32-bit Windows 7, Windows 8
C:\Program Files\AspenTech

64-bit Windows 7, Windows 8, Windows Server 2008 R2, Windows
Server 2012
C:\Program Files (x86)\AspenTech
<ASPENSHARED>
Directory for installed AspenTech shared program files. Typically, this is:

32-bit Windows 7, Windows 8
C:\Program Files\Common Files\AspenTech Shared

64-bit Windows 7, Windows 8, Windows Server 2008 R2, Windows
Server 2012
C:\Program Files (x86)\Common Files\AspenTech Shared
File Locations for New V7.2 and Later
Installations
Note: If you install to a location other than the default system drive, file
locations are unchanged from V7.1 and earlier.
Some file locations have changed for new V7.2 and later installations. The
default root location for application program files in Windows is CSIDL
_PROGRAM_FILES or CSIDL _PROGRAM_FILES (x86) which maps to disk
locations such as C:\Progam Files (64-bit applications) or C:\Program Files
(x86) (32-bit applications).
2 Overview
9
The default root location for common application data in Windows is CSIDL
_COMMON_APPDATA which maps to disk locations such as C:\Documents and
Settings\All Users\Application Data (32-bit applications) or C:\ProgramData
(64-bit applications). The default root location for user specific application
files in Windows is CSIDL _APPDATA which maps to disk locations such as
C:\Documents and Settings\username\Application Data (32-bit applications)
or C:\Users\username\AppData (64-bit applications).
Note: If you are upgrading from a previous version, your file locations
will not change. (A CSIDL is used in conjunction with one of four Shell
functions to retrieve a special folder's path.)
CSIDL_PROGRAM_FILES or CSIDL_PROGRAM_FILES (x86)
The default root location for application program files.

32-bit Windows 7, Windows 8
C:\Program Files

64-bit Windows 7, Windows 8, Windows Server 2008 R2, Windows
Server 2012
C:\Program Files (x86)
CSIDL_COMMON_APPDATA
The default root location for common application data.

32-bit platforms
C:\Documents and Settings\All Users\Application Data

64-bit platforms
C:\ProgramData
CSIDL_APPDATA
The default root location for user specific application files.

32-bit platforms
C:\Documents and Settings\username\Application Data

64-bit platforms
C:\Users\username\AppData
The following table contains some representative default folder locations for
V7.2 and later versus V7.1.
10
V7.1 and Earlier Versions
Location
V7.2 and Later Location
Program Files\AspenTech\
InfoPlus.21\db21\group200
<CSIDL_COMMON_APPDATA>\AspenTech\
InfoPlus.21\db21\group200
Program Files\AspenTech\
InfoPlus.21\c21\h21\arcs
<CSIDL_COMMON_APPDATA>\AspenTech\
InfoPlus.21\c21\h21\arcs
Program Files\AspenTech\
InfoPlus.21\c21\h21\dat
<CSIDL_COMMON_APPDATA>\AspenTech\
InfoPlus.21\c21\h21\dat
Program Files\AspenTech\
InfoPlus.21\c21\h21\backups
<CSIDL_COMMON_APPDATA>\AspenTech\
InfoPlus.21\c21\h21\backups
2 Overview
V7.1 and Earlier Versions
Location
V7.2 and Later Location
Program Files\AspenTech\
InfoPlus.21\db21\group200\logs
<CSIDL_COMMON_APPDATA>\AspenTech
\DiagnosticLogs\InfoPlus.21
Program Files\AspenTech\
ProcessData\Data\log
<CSIDL_COMMON_APPDATA>\AspenTech
\DiagnosticLogs\ProcessData
Program Files\AspenTech
Shared\KPI\Data\log
<CSIDL_COMMON_APPDATA>\AspenTech
\DiagnosticLogs\KPI
Program Files\Common
Files\AspenTech Shared
<CSIDL_PROGRAM_FILES>\Common
Files\AspenTech Shared
-or<CSIDL_PROGRAM_FILES (x86)>\
Common Files\AspenTech Shared
Program Files\AspenTech\
InfoPlus.21\db21\temp
<CSIDL_PROGRAM_FILES>\AspenTech\
InfoPlus.21\db21\temp
-or<CSIDL_PROGRAM_FILES (x86)>\
AspenTech\InfoPlus.21\db21\temp
Program Files\AspenTech\
InfoPlus.21\db21\sql
<CSIDL_PROGRAM_FILES>\AspenTech
\InfoPlus.21\db21\sql
-or<CSIDL_PROGRAM_FILES (x86)>
\AspenTech \InfoPlus.21\db21\sql
Programs Requiring
Administrator Rights
Some Aspen InfoPlus.21 Product Family programs require elevated privileges
that are provided by the Run As Administrator command. These products
include the following:
2 Overview

AeBRSClientConfigure.exe

MES Cluster Administrator

ADSA Config Tool (when setting system-wide ADSA settings)

IP21 Administrator (when configuring Cim-IO).

Process Data Admin Tool (for certain things like log settings)

Addgroup and RemoveGroup

Cim-IO Properties
11
12
2 Overview
3 Installing for the First Time
This chapter explains how to install the current version of the InfoPlus.21
family products. This installation assumes that you do not currently have any
version of Aspen Manufacturing Suite products on your computer.
All Manufacturing Execution System products installed on the same computer
must be of the same version. An MES product of one version should not coexist, on the same computer, with any other Aspen products of a different
version.
MES products installed on one computer can interoperate with MES, or other
Aspen products, on another computer, even if the two computers have
different versions. Of course, both computers should hold supported versions
of the software.
Important! If you are adding to an existing V10 installation, follow the
instructions in this chapter, but be sure to use the Custom Install option.
Currently installed component(s) are already selected. Then add a selection
for the component(s) that you want to add.
If you have a previous version of an InfoPlus.21 family product installed and
you want to upgrade to the latest version, follow the instructions in the
"Upgrading or Repairing an Existing Installation" chapter.
If you have the latest version of an InfoPlus.21 family product that is not
functioning properly, follow the instructions in the "Upgrading or Repairing
an Existing Installation" chapter.
If you have the latest version of InfoPlus.21 installed and need to transfer
InfoPlus.21 data and configuration files to a new computer, see the
“Transferring InfoPlus.21 from One Computer to Another” chapter.
Notes:

This chapter discusses how to install the InfoPlus.21 family of products
only. Due to bundling and dependency rules adapted to implement the
aspenONE V8.0 and later installer, other AspenTech products may be
installed along with InfoPlus.21 family products. Refer to the various
product installation manuals for those products to get information
regarding prerequisites and post-installation configuration.
3 Installing for the First Time
13

There is an Aspen Silent Install tool available that allows system
administrators to control the unattended installation of Aspen products to
individual computers without requiring user interaction. System
administrators can create several configurations for deployment to
different groups of computers. For details about using this client
application deployment utility, see the aspenONE Deployment Guide.
Before You Install
Before installing the InfoPlus.21 family of products, you must perform the
following pre-installation tasks.

Read the aspenONE Deployment Guide. Read the release notes for the
product(s) you are installing. All release notes are available on the product
installation media.

Confirm that Hardware, Software, and User requirements for the
product(s) you are installing have been met. For details, see “System
Requirements” on page 7.

Verify that the Software License Manager (SLM) software is installed on
your SLM server and that the appropriate licenses are in place. Users may
also have a Standalone License File and possibly a hardware dongle. (For
more information, see the Software License Manager (SLM) Installation
and Reference Guide.)

Confirm that SLM is running.

Confirm that the Windows Firewall Service is started. Note that the service
must be running even if the firewall is not turned on.

Shut down the Microsoft SQL Server if it is running on the same computer
to which you are installing.

Shut down the World Wide Web Publishing Service if it is running on the
same computer to which you are installing.
Installing the InfoPlus.21
Family of Products
Log on using the account name and password of an account in the
Administrators group of the target computer.
Note: Before you begin installation, you will want to review the What’s new
document and Release notes and print copies of the Installation Guides for
products that will be installed. Those documents are included under each
suite’s folder on the media included in your package.
Getting Started
1
14
You can begin your software installation by clicking on the media
download or inserting the aspenONE USB into the USB drive. The
AutoPlay dialog box is displayed.
3 Installing for the First Time
2
Select Run aspenONE Install Browser. The AspenTech Suite selection
screen is displayed.
The following links are available:
o
Browse contents of USB – Allows you to browse the contents of the
media to access Installation guides and Release Notes for the products
that you want to install.
o
Custom Install checkbox (available after selecting suite) – Most
customers can use the standard installation for the V10 media. We
recommend using the standard install because that is the configuration
where we focus our testing.
If you cannot use the standard install (you have disk space limitations,
for example) you can check Custom Install before beginning the
install process. This simply allows a more granular selection of which
elements of a suite to install or not install when selecting
programs. Note that Custom Install is not available for all suites.
o
Need Help? – Connects to the AspenTech Support Web site, where
you can find knowledge base articles, tips, and solutions to known
problems.
o
Getting Started - Links to brochure containing information about
prerequisites, installing and upgrading the software, documentation
and translated versions.
o
What’s New in V10 – Displays a list and explanation of new features
included in V10.
3
Select aspenONE Manufacturing and Supply Chain.
4
Select Begin Install.
Before you see the Welcome page, you may see the following:
3 Installing for the First Time
15
You must click Yes to continue.
If you do not see this dialog box or something similar, you may have
accessed the installation incorrectly and in doing so, appropriate settings
may not occur. The consequence is that the applications may not run
correctly or errors may appear even though the installation seems to
complete successfully. If this dialog box does not appear, cancel the
installation and re-launch setup.exe to start the installation again.
Carefully read the instructions on the following dialog boxes, make your
selections, and proceed with the installation.
Note: If patches are available for the product that you are installing, a screen
may appear that lets you view the patches before you install. You will also
have an opportunity to view the updates after you finish the installation
process.
16
3 Installing for the First Time
aspenONE Installer Welcome
The aspenONE Installer Welcome Page provides options to install or
upgrade aspenONE products, configure licensing, and create install scripts for
unattended installations.
The following links are available on the left side of the aspenONE Installer
Welcome Page:

Get Started. Opens the AspenTech Deployment Solutions Web site.

Installation Guides. Opens a folder on the media that contains all the
Installation Guides for the products on the media.

Release Notes. Opens a folder on the media that contains all the Release
Notes for the products on the media.

aspenONE Product Documentation. Opens the AspenTech Support
Web site.

aspenONE Update Center. Connects to the Aspen Support Update
Center so that you can check to see if there are patches available for the
product(s) that you are installing. You must be a registered user on the
Support Web site to access the Update Center.

Unattended Install Notes. Provides instruction on creating an
unattended installation.

Support Services. Connects to the AspenTech Support Web site, where
you can find knowledge base articles, tips, and solutions to known
problems.

AspenTech Home. Connects to the AspenTech Web site.

Contact Us. Connects to the AspenTech Support Web site, where you can
obtain the latest e-mail and telephone contact information and find the
3 Installing for the First Time
17
AspenTech Support location closest to you. You can see hours of operation
for global support and submit your support issues.
The following installation options are available on the aspenONE Installer
Welcome page:

Install aspenONE products. Launches the installation process during
which you will select new products to be installed on this computer.

Upgrade or repair existing products. Upgrade earlier versions of
products or repair existing installation errors.

Prepare Deployments. Create install scripts and copy media to
automate software deployment.

Install and configure SLM (Software License manager) software. Install
and configure the SLM server running on a network.
Note: Click Install aspenONE products.
License Terms and Conditions
Note: Select the I accept the terms of this agreement check box.
18
3 Installing for the First Time
Prerequisite Validation
Note: If you have not installed all prerequisites, the missing products are
displayed here and the installation will not continue until you have installed
those products.
If you have all prerequisites installed, you will not see this screen.
3 Installing for the First Time
19
Product Selection
Notes:


Hover over a selection and a list of all included products will display in the
right informational pane.
All products in a bundle will be installed. You cannot select individual
products within a bundle to install or deselect products to prevent
installing. For example, selecting Aspen Cim-IO Interfaces will install all
Cim-IO interfaces.
Notes:


The 64-bit InfoPlus.21 Server and the 64-bit Aspen Production Record
Manager require license keys that are only available to customers who
have adopted AspenTech's new, token-based licensing models.
The license keys for 64-bit InfoPlus.21 and 64-bit Aspen Production
Record Manager are not available to customers who are still on the
perpetual license model. Consequently, such customers should install the
32-bit InfoPlus.21 and 32-bit Aspen Production Record Manager instead.
Note: Both 32-bit and 64 SQLplus executables are installed with 64-bit
InfoPlus.21. With a new installation, the InfoPlus.21 task start list will point to
the 64-bit executables. The 32-bit executables are provided in case the user
has SQLplus queries that invoke methods in 32-bit COM components. Such
components can only be loaded by 32-bit processes.
20
3 Installing for the First Time
If you want to check or change the installation location, click the File
Location tab.
File Location
Notes:



Once the installation of any AspenTech product to the default folder has
been completed, this folder cannot be changed and the Change Current
Destination Folder dialog box will no longer display. Any further
AspenTech installations on the computer are made to that folder by
default.
Common features are always installed in the Program files\Common
Files\AspenTech Shared folder regardless of the destination location
selected.
Do not install in the root folder on any drive other than C:\. If you must
install on a drive other than C:\, be sure to specify a directory.
3 Installing for the First Time
21
Specify Licensing and Security
Notes:


22
Enter License server information. After adding the license server, you
can click the server name and the View Buckets button becomes
enabled, allowing you to specify buckets if you use them. Alternatively,
use the SLM Configuration Wizard to specify buckets after installation.
For client installations, enter NONE for the Security server name.
3 Installing for the First Time
Specify Account Information
Note: Enter your Administrators group user account.
3 Installing for the First Time
23
Verify Your Installation
Installation Progress
24
3 Installing for the First Time
Installation Complete
Before using the software, follow all instructions in the “After Installing for the
First Time” chapter.
3 Installing for the First Time
25
26
3 Installing for the First Time
4 After Installing for the First
Time
After you install, you will need to perform post-installation procedures for
each product. This guide provides instructions for the InfoPlus.21 product
family only.
After Installing InfoPlus.21
To complete the installation process for InfoPlus.21, you must follow these
post-installation steps.
1
Set maximum point count. See “Set Maximum Point Count” in this
chapter.
2
Start InfoPlus.21. See “Starting InfoPlus.21” in this chapter.
3
Verify the installation. See “Verifying the InfoPlus.21 Installation” in this
chapter.
4
Configure your InfoPlus.21 system. This includes replacing the demo
database, configuring history repositories, and optionally, activating audit
trail generation, altering startup parameters, configuring database
security, and changing your InfoPlus.21 user name. For configuration
instructions, see the Aspen InfoPlus.21 Product Family Configuration
Guide.
Set Maximum Point Count
New InfoPlus.21 installations set the license point count to "4000" by default.
If you are not licensed for this number of points, InfoPlus.21 will fail to check
out a license. To correct this issue, you must reset the license point count in
InfoPlus.21 to a number that is less than or equal to the number of points for
which you are licensed.
Note: The InfoPlus.21 database cannot be running during this procedure.
4 After Installing for the First Time
27
To set the point count:
1
Click Start | Programs | AspenTech | Aspen Manufacturing Suite
|Aspen InfoPlus.21 | InfoPlus.21 Administrator. The InfoPlus.21
Administrator is displayed.
2
Click on the database object.
3
Click Administrator | Set Point Count. The Set Maximum Point
Count dialog box is displayed. The current point count information is
displayed in this dialog box.
Note: You can also right-click the database object and click Set Point
Count to display the Set Maximum Point Count dialog box.
4
Enter the new point count in the Maximum Point Count field.
5
Click OK to set the new value.
Note: When Aspen InfoPlus.21 is started, the new maximum point count will
be shown in the Total field of the Licensed Points section of the Record
Utilization tab. The tab is part of the Properties screen, accessed by rightclicking the InfoPlus.21 node in the InfoPlus.21 Administrator.
Starting InfoPlus.21
Use the InfoPlus.21 Manager to start the database the first time.
To start the InfoPlus.21 database:
28
1
Click Start | Programs | AspenTech | Aspen Manufacturing Suite |
Aspen InfoPlus.21 | InfoPlus.21 Manager. The InfoPlus.21
Manager is displayed.
2
Click START InfoPlus.21.
4 After Installing for the First Time
3
After the tasks finish starting up, confirm that the database is running.
(The message on the Status bar should read, “InfoPlus.21 Manager has
been started successfully.”)
Note: For more information about using the InfoPlus.21 Manager, see the
InfoPlus.21 Administration Help file.
Verifying the InfoPlus.21 Installation
During a new installation of InfoPlus.21, a demo database is installed. This
demo database provides a means to test your installation and ensure that it is
working properly.
Note: The demo database simulation will not run without SQLplus.
The demo database is loaded when you start InfoPlus.21. If SQLplus is
running, records in the demo database cause standard tag records to be
updated periodically with new data.
These tags store data into a history repository named TSK_DHIS. After
installation, this repository has three file sets: arc1, arc2, and arc3.
(Located in
<CSIDL_COMMON_APPDATA>\AspenTech\InfoPlus.21\c21\
h21\arcs.)
After you start InfoPlus.21, you should be able to retrieve data from the demo
database tags with Aspen Process Explorer (insert tag named ATCAI and
confirm existence of points on the trend plot).
Note: For more information about using Aspen Process Explorer, see the
Aspen Process Explorer Help file.
Alternatively, use the InfoPlus.21 Administrator’s Find | InfoPlus.21 record
feature to find the tag ATCAI and then verify that the IP_INPUT_TIME value
periodically increments over time.
After Installing Aspen Calc
After installing Aspen Calc, complete the following:
1
Verify the installation. See “Verifying the Aspen Calc Installation” below.
2
If employing role-based security, import the Calc XML file to the security
server. For instructions, see the Aspen InfoPlus.21 Product Family
Configuration Guide.
Verifying the Aspen Calc Installation
Verify the installation by clicking Start | Programs | AspenTech | Aspen
Manufacturing Suite | Aspen Calc. If the Aspen Calc application launches
successfully, your installation was successful.
4 After Installing for the First Time
29
After Installing Cim-IO
To complete the installation process for Cim-IO core, you must complete the
following configuration steps:
1
Verify the installation. See “Verifying the Cim-IO Installation” below.
2
Complete configuration tasks such as setting up the Cim-IO environment
and configuring Cim-IO clients and servers for operation. For instructions,
see the Aspen InfoPlus.21 Product Family Configuration Guide.
Verifying the Cim-IO Installation
Verify the Cim-IO Core installation
1
Verify that cimio.dll is in the <ASPENSHARED> folder.
2
Verify that the Cim-IO Manager program (CimioManager.exe) and that
six Store and Forward programs (cimio_sf*.exe) are in the
<ASPENROOT>\CIM-IO\code folder.
Verify Cim-IO Core operation
Use the Simulation Server, if it was installed, and the Cim-IO Test Utility
to test various standard Cim-IO functions. (If you did not install the
Simulation Server, you will need another Cim-IO device configured in order to
use the Test Utility.) See the Aspen Cim-IO User’s Guide for configuration and
operating instructions for the Simulation Server and the Cim-IO Test Utility.
See these specific chapters of the document:

“Cim-IO Test Utility Program”

“Cim-IO Simulation Server”
Verify the Simulation Server Installation
If you installed the Simulation Server:

Verify that the cimio_x_*.* files are in the folder <ASPENROOT>\CIMIO\io\simulation.
Verify the example code installation
If you selected to install Cim-IO example files:

Verify the example source code is in the folder <ASPENROOT>\CIMIO\example source\client and <ASPENROOT>\CIM-IO\example
source\server.
After Installing ADSA
The ADSA post-installation tasks you must complete depend on your bundle
or product choices in either Typical or Custom Install and how you fill in the
ADSA Administrator Configuration dialog if it appears.
1
30
Verify the ADSA installation. See” Verifying the ADSA Installation” below.
4 After Installing for the First Time
2
Configure data sources for each client computer, and optionally, add
service components to the data sources. See the Aspen Data Source
Architecture Help.
Note: You will need to configure data sources for each new ADSA
installation that is on a computer other than the InfoPlus.21 server. You
may need to add data source components to the data source on a
computer that has both ADSA and InfoPlus.21 installed depending on what
other products are installed on the InfoPlus.21 host machine.
Verifying the ADSA Installation
After the installation of the ADSA Directory Server, confirm the installation by
performing one or both of the following tests.
Test One
Perform Test One on either the ADSA Directory Sever or the ADSA client.
1
On the ADSA client computer, click Start | Programs | AspenTech |
Common Utilities | ADSA Client Config Tool. The ADSA Properties
screen appears.
2
In the Directory Server box, enter the name or IP address of the
computer where you installed the ADSA Directory server.
3
Click Test.
o
If the installation was successful, a message displays indicating that
the connection between the client computer and the ADSA Directory
Server was successful.
o
If the connection is unsuccessful, the ADSA Client Config Tool shows
this message: "A remote activation was necessary but the server
name provided was invalid. (Unable to resolve server hostname to IP
address)." See the “Troubleshooting” chapter for a solution.
4 After Installing for the First Time
31
4
Click OK.
Test Two
Perform Test Two on the computer where you installed the ADSA Directory
server.
1
Click Start | Settings | Control Panel on the computer where you
installed the ADSA Directory Server. The Control Panel screen displays.
2
Open Administrative Tools.
3
Open Services.
4
Look for the service Aspen Data Source Directory in the Services
screen along with a status of Started. If the service appears in the
Services screen, the installation was successful.
After Installing Process
Explorer
After installing Aspen Process Explorer:
1
Verify the installation.
2
If employing role-based security, import the Process Explorer XML file to
the security server. For instructions, see the Aspen InfoPlus.21 Product
Family Configuration Guide.
3
Optionally, load and test the Process Data Add-In in Microsoft Excel. See
“Load and Test Process Data Add-In in Microsoft Excel” on page 33.
4
If planning to publish data from the V8.8 or later Process Data Excel Addin, you will need to configure Excel Services in Microsoft Office SharePoint
Server. For instructions, see the Aspen InfoPlus.21 Product Family
Configuration Guide.
Verifying the Process Explorer Installation
To verify that the Aspen Process Explorer installation was successful,
complete the following steps:
32
1
Click Start |Programs | AspenTech | Aspen Manufacturing Suite |
Aspen Process Explorer| Process Explorer to open Aspen Process
Explorer. The Aspen Process Explorer main window is displayed.
2
Click File | New. The New Document window is displayed.
4 After Installing for the First Time
3
Select the Trend object.
4
Click OK. A blank trend plot is displayed.
5
Click the Aspen Tag Browser icon. The Aspen Tag Browser window is
displayed.
Load and Test Process Data Add-In in
Microsoft Excel
If you installed the Process Data Add-in, you will need to load and test it.
To load the Process Data Add-in into Excel 2010 or 2013:
1
Launch Excel.
2
Launch Options and then Add-Ins.
3
Be sure that Excel Add-ins is selected in the Manage box and then click
Go.
4
Select the desired Aspen Process Data Add-in check box.
Note: If the Process Data Add-in check box does not appear as an Add-in
choice, verify that AtData.xlma is present in the appropriate Office library
directory. If you do not see AtData.xlam, locate and select AtData.xlam.
5
Click OK.
6
Verify that the Aspen menu appears, displaying the Aspen Process Data
Add-In options.
After Installing SQLplus
After installing SQLplus:
1
Verify the installation. See “Verifying the SQLplus Installation” below.
4 After Installing for the First Time
33
2
Optionally, import the SQLplus XML file to the security server. For
instructions see the Aspen InfoPlus.21 Product Family Configuration
Guide.
3
Optionally, if using SQLplus Reporting, change the query execution
timeout value, and if the Web Server and the InfoPlus.21 Server will be on
different computers, specify the SQLplus server. For instructions, see the
Aspen InfoPlus.21 Product Family Configuration Guide.
Verifying the SQLplus Installation
To verify the SQLplus installation, click Start | Programs | AspenTech |
Aspen Manufacturing Suite | SQLplus. The application will launch and you
will be prompted to select the SQLplus Server. Select the server and click OK.
Note: In order to verify the SQLplus installation, InfoPlus.21 must be
running.
After Installing aspenONE
Process Explorer
After installing aspenONE Process Explorer:
1
Configure ADSA if needed. See “Configuring ADSA” below. Note that if you
installed aspenONE Process Explorer on the same machine as InfoPlus.21,
you do not need to perform this step.
2
Verify the installation. See “Verifying the aspenONE Process Explorer
Installation” below.
3
If using aspenONE Process Explorer in standalone mode, you must
populate your search content. See “Populating the Search Database”
below.
4
If using aspenONE Process Explorer in aspenONE suite mode, you must
register with aspenONE and populate your search content. See the Aspen
InfoPlus.21 Product Family Configuration Guide for details.
5
Configure OEE records if you plan to use the OEE feature of aspenONE
Process Explorer. See the Aspen InfoPlus.21 Product Family Configuration
Guide for details.
Configuring ADSA
You must configure ADSA in order to view data in aspenONE Process Explorer.
To configure aspenONE Process Explorer in ADSA:
1
34
Select Start | Programs | AspenTech | Common Utilities | ADSA
Client Config Tool or from the Start menu, click:
4 After Installing for the First Time
2
From the Configuration tab, click the Public Data Sources button. The
Aspen Public Data Sources dialog box displays.
3
Select an entry from the Data Sources list and click Edit to edit that
source. The Data Source Name dialog box appears.
4
Click Add. The Add Service dialog box displays.
5
On the Add Service dialog box, select the Aspen Process Subscription
(Generic) Service and click OK.
6
Click OK on three successive dialog boxes to return to the ADSA
Properties dialog box.
7
Add the remaining services required by aspenONE Process Explorer if they
do not already exist in the data source:
o
Aspen SQLplus service component.
o
Aspen Process Data (IP.21)
o
Aspen DA for IP.21
Verifying the aspenONE Process Explorer
Installation
Verify the installation by opening the browser. Then enter the aspenONE
Process Explorer address, http://<servername>/ProcessExplorer/, to test the
installation. It should display similar to below.
Populating the Search Database
Before you use Search, you must populate the Search Database. If the Search
Database is not populated, searches for tags or other items will return no
results.
Periodically, you will need to manage search data as tags and other items are
added, modified, renamed, or deleted.
4 After Installing for the First Time
35
Note: These instructions are for using aspenONE Process Explorer in
standalone mode. For instructions when using aspenONE Process Explorer in
aspenONE suite mode, see the Aspen InfoPlus.21 Product Family
Configuration Guide.
From the Start menu or Start page, click
aspenONE Process Explorer
Admin under the aspenONE Process Explorer group. The ADMIN tool will
open in the browser, displaying the Manage Search Data page.
Search data is broken into three categories:

All

Files

Tags
Use the tabs on the Manage Search Data page to manage each category.
After the initial population, use the Manage Search Data page to manage your
search data. See the “Managing Search Data” Help topic for instructions (click
from the application to access Help).
Check for Updates
For all products, check the online AspenTech Support Center for updates to
the software, technical advisories and other important information. For
details, see “Technical Support” on page 2.
36
4 After Installing for the First Time
5 Upgrading or Repairing an
Existing Installation
This chapter explains how to upgrade from a previous version of the
InfoPlus.21 family of products to V10.
Important!



If you are adding to an existing V10 installation, follow the instructions in
“Installing for the First Time” beginning on page 13.
If you are upgrading from a previous version and plan to use InfoPlus.21
replication, see “Replication Upgrade Planning” on page 49. You will
need to have a replication upgrade plan in place before you initiate an
InfoPlus.21 upgrade.
If you are upgrading to the 64-bit version of Aspen InfoPlus.21 Server,
you cannot directly upgrade. You must use the instructions in “Upgrading
to InfoPlus.21 Server 64-bit” below.
If you are upgrading from InfoPlus.21 version 2.5.1, please see the
AspenTech Online Support Center. You can download any Aspen InfoPlus.21
Installation Guide V7.1 or earlier and then follow the instructions for
upgrading from version 2.5.1.
Caution! If you have previously installed more than one Aspen Manufacturing
Suite product on the same computer, you must upgrade all previously
installed products at the same time.
If you are moving an InfoPlus.21 system to a different computer, follow the
instructions in “Transferring InfoPlus.21 from One Computer to
Another” on page 55.
Upgrading to InfoPlus.21 Server 64-bit
If you are upgrading to InfoPlus.21 Server 64-bit, you must follow this
sequence of events:
1
Perform all “Before You Upgrade” tasks for InfoPlus.21. See the following
sections in this chapter. Do not proceed to the actual upgrading
procedure.
2
Remove InfoPlus.21 Server 32-bit using the instructions in “Removing
Features and Subfeatures” beginning on page 51.
5 Upgrading or Repairing an Existing Installation
37
3
Install InfoPlus.21 Server 64-bit using the instructions in “Installing for
the First Time” beginning on page 13.
Before You Upgrade
Before installing the InfoPlus.21 family of products, you must perform the
following pre-upgrade tasks. Some tasks are required for all InfoPlus.21
family products, while others are only required when upgrading a particular
product.

Read the aspenONE Deployment Guide.

Read the release notes for the products you are upgrading.

Confirm that Hardware, Software, and User requirements for the
product(s) you are installing have been met. For details, see “System
Requirements” on page 7.

Confirm that the Software License Manager (SLM) is upgraded and that
current license key files are in place. For more about licensing and SLM,
see the Software License Manager (SLM) Installation and Reference Guide.

Confirm that SLM is running.

If upgrading InfoPlus.21, perform these InfoPlus.21 tasks:
o
Save a snapshot of your database. See the “Saving a Snapshot”
section in this chapter.
o
Save the group configuration files. See “Saving the Group
Configuration File” on page 41.
o
Save the SQLplus ODBC link files. See “Save the SQLplus ODBC
Link Files” on page 41.
o
Copy the oktomodify.inp file to the group200 folder. See “Copying
the oktomodify.inp File to the group200 Folder” on page 41.

If upgrading Cim-IO, stop all Cim-IO processes. See “Stopping Cim-IO
Processes” on page 42.

Shut down the Microsoft SQL Server if it is running on the same computer
to which you will install.

Close all AspenTech products that are currently open.
Note: Before shutting down InfoPlus.21, first stop the database and clear
the Start on Reboot check box (if selected).

Shut down services. You will shut down all Aspen services except the SLM
service. You will also shut down other non-Aspen services. See “Shutting
Down Services” on page 42.
Saving a Snapshot
If upgrading InfoPlus.21, save a snapshot of the database before upgrading.
A snapshot is a copy of the contents of the memory-resident database at a
certain moment in time.
1
38
Click Start | Programs | AspenTech | Aspen Manufacturing Suite |
Aspen InfoPlus.21 | InfoPlus.21 Manager. The InfoPlus.21 Manager is
displayed.
5 Upgrading or Repairing an Existing Installation
2
Confirm that the database is running. If it is not running, click START
InfoPlus.21 to start the database.
3
Type Ctrl+U on your keyboard. The InfoPlus.21 Utilities window is
displayed.
4
Click the Snapshot tab.
5
Click Browse to display the Save Snapshot As dialog box.
6
Browse to the <ASPENROOT>\InfoPlus.21\
db21\groupxxx folder.
5 Upgrading or Repairing an Existing Installation
39
7
In the Save Snapshot As dialog box, click
8
Enter a folder name.
to create a new folder.
Note: In this example, the folder is named Aspentemp. AspenTech
recommends backing up all the files in the same folder.
9
Click Open.
10 In the File name box, enter a name for the snapshot, including the file
extension .snp.
Note: In this example, the snapshot is named PreUpgrade.snp.
11 Click Save. The InfoPlus.21 Utilities window displays.
12 In the InfoPlus.21 Utilities window, confirm that the Save and Binary
options are checked.
13 Click Execute to complete a binary save. A program completed message
box is displayed over the InfoPlus.21 Utilities window.
14 Click OK.
15 Review the information and confirm that it is accurate.
16 Click Exit in the InfoPlus.21 Utilities dialog box. The InfoPlus.21
Manager is displayed.
40
5 Upgrading or Repairing an Existing Installation
Saving the Group Configuration File
If upgrading InfoPlus.21, save the group configuration file.
1
Click Start | Programs | AspenTech | Aspen Manufacturing Suite |
Aspen InfoPlus.21 | InfoPlus.21 Manager to open the InfoPlus.21
Manager.
2
Click File | Save Group Configuration. The Save Group Configuration
dialog box is displayed.
3
Browse to the Aspentemp folder.
4
In the File name box, enter a file name for the group configuration file.
Note: In this example, the file is named PreUpgrade.ipg.
5
In the Save as type box, confirm that the file extension is .ipg.
6
Click Save.
7
Stop the InfoPlus.21 database by clicking the STOP InfoPlus.21 button.
Save the SQLplus ODBC Link Files
If upgrading InfoPlus.21, save the SQLplus OBDC Link Files to a temporary
location for safekeeping (for example, Aspentemp). The DAT files are located
in the directory AspenTech\InfoPlus.21\db21\sql\ and contain ODBC link
information used by SQLplus.
Copying the oktomodify.inp File to the
group200 Folder
If upgrading InfoPlus.21, copy the oktomdify.inp file to the group200
folder. The InfoPlus.21 Upgrade Database Wizard moves records and data
from the previously saved “source” database snapshot into the new “target”
database. By default, any records that are only in the source database are
simply copied to the target database. The InfoPlus.21 Upgrade Database
Wizard will also modify some of the target database records with data from
corresponding records in the source database. By default, the wizard will only
modify existing target database records if they are listed in the
oktomodify.inp file located in the group200 folder.
As distributed, the oktomodify.inp file lists those standard records in the
source database that may have legitimately been modified by the user. It is
possible, however, that you may have reasons for adding additional record
names to this file.
During a new installation, the installation setup program copies a standard
oktomodify.inp file to both the etc folder and the group200 folder, typically
located at <ASPENROOT>\InfoPlus.21\db21\.
Nevertheless, during an upgrade, the installation setup program only copies
the standard oktomodify.inp file to the etc folder. The oktomodify.inp file in
the group200 folder is not overwritten because it may have been modified
by the user; that is a user that may have added some record names to the
oktomodify.inp file.
5 Upgrading or Repairing an Existing Installation
41
Of course, AspenTech may have modified the oktomodify.inp file written to
the etc folder. Therefore, before running the InfoPlus.21 Upgrade Database
Wizard, you should manually copy the oktomodify.inp to the group200
folder, merging in any additional user record names as necessary.
Stopping Cim-IO Processes
If the Cim-IO client was running under InfoPlus.21, the client tasks should
have been stopped when InfoPlus.21 was stopped in the previous section.
If one or more Cim-IO servers are installed on the computer where you are
upgrading, you must stop all the Cim-IO server processes. To do so, run the
appropriate shutdown command procedure to terminate the processes. The
following steps will help to verify that all cimio processes are shutdown.
1
Display the Task Manager by pressing the Ctrl+Alt+Del keys. The
Windows Security screen is displayed.
2
Click Task Manager. The Windows Task Manager is displayed.
3
Click the Processes tab to display the processes running on the system.
4
Click the Image Name column heading to sort the process names
alphabetically.
5
Stop the Cimio Manager service.
6
Verify that there are no processes that start with “cimio” nor any
processes running with names such as "asyncdlgp.exe" or other
executable names from the specific Cim-IO server you are running.
Shutting Down Services
When upgrading any InfoPlus.21 family product, you must first shut down
services.
You will shut down all AspenTech services except the Software License
Manager service. You will also shut down some non-AspenTech services that
are listed in the steps below.
1
Make sure that you are logged on using the administrator account, or an
account that is in the administrator group.
2
Click Start | Settings | Control Panel.
3
Double-click the Services icon.
4
In the Services dialog box, stop all Aspen services, such as:
o
Aspen Data Source Directory
o
Aspen Registry Security Server
o
Aspen Timezone Information
o
Each InfoPlus.21 Task Service
o
InfoPlus.21 Browser service
o
Cim-IO Manager service
Note: The AspenTech services on your computer will depend on the
Aspen software you have on that computer.
5
In addition, shut down these services, if running:
o
42
NobleNet Portmapper for TCP service
5 Upgrading or Repairing an Existing Installation
o
IIS Admin Service
o
World Wide Web Publishing Service (this service is only required if
certain Aspen web-based products or Aspen Local Security are
installed).
Upgrading the InfoPlus.21
Family of Products
1
Log on to the network using the account name and password of an
account in the Administrators group of the target computer.
2
Do one of the following:
o
If you are installing from a local drive, locate the aspenONE media
drive and folder for Aspen Manufacturing and Supply Chain, and
double-click setup.exe.
o
If you are installing from a network drive, map to the drive that
contains the aspenONE software installation for Aspen Manufacturing
and Supply Chain, and double-click setup.exe.
Carefully read the instructions on each dialog box before making your
selections.
3
From the aspenONE Installer dialog box, click Upgrade or repair
existing products. Then follow the instructions in chapter 3, “Installing
for the First Time,” noting that you may not see all screens depicted
there.
Note: In the V8.0 and later version of the aspenONE installer, upgrading an
existing installation may result in some additional products being installed
than what originally existed. This is due to dependency and bundle
relationships established in order to implement the V8.0 and later installer
changes.
Continue to the next section for post-upgrade tasks.
After You Upgrade
Depending on the products that you upgraded, there may be post-upgrade
tasks that must be performed. The following sections provide details.
After Upgrading InfoPlus.21
After upgrading InfoPlus.21 you will:

Upgrade the database

Verify the upgrade
5 Upgrading or Repairing an Existing Installation
43
Upgrading the Database
Important: The Upgrade Database Wizard distributed with InfoPlus.21
version 2006 and later can only handle databases created on version 4.1 or
later.
After you upgrade InfoPlus.21, you must upgrade your database. In other
words, you should run a utility that creates a new database snapshot from an
older, previously saved database snapshot. The new database snapshot will
have records with an internal structure that is required by the upgraded
version of InfoPlus.21. InfoPlus.21 includes the InfoPlus.21 Database
Upgrade Wizard that aids in upgrading the InfoPlus.21 database snapshot.
When upgrading the database, you can either complete the automatic
upgrade (Typical option) or the manual (Custom option) upgrade. During an
automatic upgrade, you are required to accept the defaults for each screen
that is displayed. (Not all screens will be displayed for the automatic
upgrade.) During the manual upgrade, you will be required to enter
information in the screens before you can complete the upgrade.
Note: For more information about upgrading the database, see the
InfoPlus.21 Administration Help.
To open the wizard:
1
Click Start | Programs | AspenTech | Aspen Manufacturing Suite |
Aspen InfoPlus.21 | InfoPlus.21 Manager to open the InfoPlus.21
Manager.
2
Confirm that the InfoPlus.21 database is not running.
3
Click Actions | Upgrade Database. The InfoPlus.21 Database Upgrade
Wizard is displayed.
Note: You can click Cancel on any of the screens to stop the upgrade.
To use the Typical option to upgrade the database:
1
Click the Typical option to select the default upgrade options.
2
Click Next. The InfoPlus.21 Database Upgrade Wizard Source/Output
Screen is displayed.
3
In the Source field, enter the source snapshot filename you want to
upgrade, or click Browse… to locate a snapshot file. Click on a file to
select it and click Open. The selected file name is displayed in the Source
field.
4
In the Output field, enter the name of the database snapshot where you
want to save the upgraded database, or browse to locate the snapshot
file. Click on the file to select it and click Save. The selected file name is
displayed in the Output field.
5
Click Finish. The upgrade process starts. A message is displayed when
the upgrade is successful.
To use the Custom option to upgrade the database:
44
1
Select the Custom option to begin a manual entry upgrade.
2
Click Next. The InfoPlus.21 Database Upgrade Wizard Source
Database screen is displayed.
5 Upgrading or Repairing an Existing Installation
3
In the Snapshot filename field, enter the name of the database
snapshot that you want to upgrade, or browse to locate a snapshot file.
Click on a file to select it and click Open. The selected file name is
displayed in the Source field.
Note: This field will only display the filename that InfoPlus.21 loads if that
particular snapshot needs to be upgraded. The field remains blank if the
snapshot is up-to-date.
4
Optionally, in the Optional list of records that should not be created
or modified field, select a file that contains records that should not be
created or modified. Enter the name of a text file, or browse to locate the
text file. Click on the file to select it and click Open. The selected file is
displayed in the field.
Note: You can click View to see the contents of the text file.
5
Click Next. The InfoPlus.21 Database Upgrade Wizard Target
Database Screen is displayed.
6
To use the default Build and load a new snapshot option, click Next.
The InfoPlus.21 Database Upgrade Wizard Base Database
Snapshot screen is displayed.
Note: To use the Load an existing snapshot option, select the option,
enter a snapshot name, click Next, and go to Step 10. For more
information, see the InfoPlus.21 Administration Help.
7
In the Base field, select a snapshot file that contains RLD files to be
loaded or accept the default file (InfoPlus21DB.snp). Enter the name of a
snapshot file, or click Browse… to locate the snapshot file. Click on the
file to select it and click Open. The selected file is displayed in the Base
field.
Note: The Base database is the standard database distributed with
InfoPlus.21 (normally the InfoPlus21DB.snp file is stored in
…\AspenTech\InfoPlus.21\db21\group200 under
CSIDL_PROGRAM_FILES or CSIDL_PROGRAM_FILES (x86).
8
Optionally, click on an RLD file from the Available list and click the right
arrow to move it to the Selected list. Within the Selected list, you can
reorder RLD files using the up and down arrows.
9
Click Next. The InfoPlus.21 Database Upgrade Wizard Upgrade
Options Screen is displayed.
10 To use the default Modify some records option, and then click Next.
The InfoPlus.21 Database Upgrade Wizard Output Database Screen is
displayed.
Note: Aspen Technology strongly recommends using the default option.
11 In the Save database field, enter the name of the database snapshot
where you want to save the new database, or browse to locate the
snapshot file. Click on the file to select it and click Save. The selected file
name is displayed in the Save database field.
12 Optionally, change the name and destination of the output message file.
13 Optionally, click the Copy ACLs for created records option to specify to
only copy ACLs for records that will be created in the target database. The
default selection is the Modify all record ACLs option.
5 Upgrading or Repairing an Existing Installation
45
14 Click Finish. The upgrade process starts. A message is displayed when
the upgrade is successful.
15 When the upgrade is completed, select the Start on Reboot check box in
the InfoPlus.21 Manager (if it was selected before upgrading to V10).
16 Before restarting InfoPlus.21, make sure that the upgraded database is
named the same as the previous InfoPlus.21 database. Then restart the
InfoPlus.21 database.
Verify the InfoPlus.21 Upgrade
To verify the upgrade, see “Verifying the InfoPlus.21 Installation” on
page 29.
After Upgrading Cim-IO
After upgrading Cim-IO, complete the following:
46
1
Edit any Cim-IO server batch files (*.bat) that are using Cim-IO
environment variables. Replace the environment variables with the
appropriate path.
2
If the upgrade was from a Cim-IO version prior to version 6.0.1, the
following files can safely be removed. The functionality of these programs
has been replaced by CimioProperties.exe
o
Program Files\AspenTech\Cim-IO\code\cimio_sf_reject.exe
o
Program Files\AspenTech\Cim-IO\code\CimioSecurity.exe
o
Program Files\AspenTech\Cim-IO\commands\cimio_sf_accept_old.bat
o
Program Files\AspenTech\Cim-IO\commands\cimio_sf_reject_old.bat
3
If the upgrade was from a Cim-IO version prior to version 5.0, copy the
cimio_logical_devices.def and cimio_errors.def files from the
AspenTech\Cim-IO\etc directory of the old Cim-IO to the
<ASPENROOT>\CIM-IO\etc directory of the new Cim-IO installation.
4
If the upgrade was from a Cim-IO version prior to version 5.0, we
recommend that you reinstall any Cim-IO servers that were using the old
Cim-IO version. The reinstall places the Cim-IO server files in the new
Cim-IO directory tree. After all reinstalls are completed, the old Cim-IO
directory tree can be removed from the system.
5
If the upgrade was from a Cim-IO version prior to version 5.0, edit the
PATH environment variable to remove the Cim-IO code directory.
o
Click Start | Settings | Control Panel.
o
Double-click the System icon.
o
In the System Properties screen, click the Advanced tab, and then
click the Environment Variables button.
o
In the System Variables list, click the path environment variable and
then click Edit.
o
Remove the directory path %CIMIOROOT%\code from the Value box.
o
Click OK.
5 Upgrading or Repairing an Existing Installation
Verify the Cim-IO Upgrade
To verify the upgrade, see “Verifying the Cim-IO Installation” on page 30.
After Upgrading ADSA
No configuration is necessary after you upgrade ADSA. However, you will
need to verify the upgrade. See “Verifying the ADSA Installation” on page
31.
After Upgrading Process Explorer
After upgrading Aspen Process Explorer on a client computer, you can:

Load and test Process Data Add-In in Microsoft Excel. See “Load and
Test Process Data Add-In in Microsoft Excel” on page 33.

Verify the upgrade. See “Verifying the Process Explorer Installation”
on page 32.
After Upgrading SQLplus
No configuration is necessary after you upgrade SQLplus. However, you will
need to verify the upgrade. See “Verifying the SQLplus Installation” on
page 34.
Check for Updates
Check the online AspenTech Support Center for updates to the software,
technical advisories and other important information. For details, see
“Technical Support” on page 2.
5 Upgrading or Repairing an Existing Installation
47
6 Replication Upgrade
Planning
Introduction
The improved InfoPlus.21 replication functionality no longer depends on
AspenTech Enterprise Integration Framework (EIF) as the transport for
communication. Additionally, the configuration is done via Infoplus.21
database records instead of a configuration file. This chapter provides some
guidelines on how to upgrade an existing replication implementation to V8.0
and later.
Since there could be a number of ways that replication is set up, by no means
does this chapter cover all scenarios. However, this chapter can provide some
useful planning strategies. Finally, be aware that an upgrade process of the
InfoPlus.21 systems can result in loss of replicated data. During a shutdown
of the subscriber process, there may be data in memory between the EIF and
the subscriber task. In addition, there may also be data in the subscriber’s
memory which may be lost as well.
Note: Data and tag replication requires Microsoft Message Queue (MSMQ).
MSMQ can be installed before or after InfoPlus.21 V8.4 and later.
Pre-Installation
There are three options available.
Option 1
1
Upgrade both plant and central systems at the same time.
2
Follow the instructions in the Aspen InfoPlus.21 Administration Help on
how to configure replication.
Option 2
1
Disable all replication on the plant systems.
2
Monitor the central system so that no more updates occur from the plant
systems.
6 Replication Upgrade Planning
49
3
Upgrade the subscriber and follow the instructions in the Aspen
InfoPlus.21 Administration Help on how to configure replication.
4
Upgrade the publisher and follow the instructions in the Aspen InfoPlus.21
Administration Help on how to configure replication.
Option 3
1
Stop the publish task on all plant systems while replication is still enabled.
Since replication is still enabled, tag updates are saved to the replication
queue files.
2
Monitor that the central system has no more updates from the plant
systems.
3
Upgrade the subscriber and follow the instructions in the Aspen
InfoPlus.21 Administration Help on how to configure replication.
4
Before upgrading the plant system and while the InfoPlus.21 system is
down, back up the queue files. Typically, their path is specified in the
ReplicationPublisher.exe.config file. Look for the “path” attribute of the
“app_options” element in the file. If the path is not defined, the default
path is
C:\ProgramData\AspenTech\InfoPlus.21\db21\group200\Replication. The
queue file names are IP21Replication_primary.queue and
IP21Replication_secondary.queue. It is also possible that there will be a
third file named IP21Replication_overflow.queue. All three files must be
backed up.
5
Upgrade the plant system and then see “Post-Installation” below for
further instructions.
Warning! Choosing option 3 has an implication on disk usage because the
queue files can grow while the central system is being upgraded. The growth
rate depends on the frequency of updates, number of tags being replicated,
and the duration of down time of the central system. In addition, when both
the plant system and central system are ready to replicate again, the saved
updates may take a while to finish before the more current updates are
replicated. In other words, the shorter the down time for the upgrade of
central system, the less impact on the disk usage and the performance of the
replication to deal with the sudden burst of saved updates.
Post-Installation
This is only needed if option 3 is chosen in the “Pre-Installation” section.
1
Copy the saved replication queue files to the following location:
o
C:\ProgramData\AspenTech\InfoPlus.21\db21\group200\Replication
If the folder does not exist, create it manually.
2
50
Follow the instructions in the Aspen InfoPlus.21 Administration Help on
how to configure replication.
6 Replication Upgrade Planning
7 Removing Features and
Subfeatures
This chapter describes removing Aspen InfoPlus.21 family products using the
Microsoft Start Menu.
Before You Remove
Before you remove InfoPlus.21 family features or subfeatures, there are tasks
you must complete for all products, and tasks you must complete depending
on which product you are removing.
Complete the following in the order presented:
1
Before removing InfoPlus.21:
o
Save a snapshot of your database. See “Saving a Snapshot” on page
38.
o
Save the group configuration files. See “Saving the Group
Configuration File” on page 41.
o
Shut down the InfoPus.21 database.
o
Back up additional files. See “Backing up Additional Files” in this
chapter.
2
Before removing Cim-IO, stop Cim-IO processes. See “Stopping Cim-IO
Processes” on page 42.
3
Before removing ADSA, reconnect all ADSA Client computers linked to
your Directory Server to another ADSA Directory Server. For more
information about connecting to a data source, see the Aspen InfoPlus.21
Product Family Configuration Guide.
4
Then complete the following:
o
Close each application.
o
Shut down services. See the “Shutting Down Services on page 42.
o
Save all user-created files for each product that you are removing.
o
Complete a system backup.
7 Removing Features and Subfeatures
51
Backing up Additional Files
Important! The location of the folders referenced below will depend on your
operating system. Additionally, the location will depend on whether your files
reside in the V7.2 and later folder locations or pre-V7.2 folder locations. For
more information, see “
Directory Locations and References” on page 9.
After you shut down InfoPlus.21, you must back up additional files. You can
back up the files to the temporary folder that you created when you saved
your snapshot.
Note: For more information on the History files, see the Aspen InfoPlus.21
Product Family Configuration Guide and the InfoPlus.21 Administration Help
files.
The following InfoPlus.21 folders and their contents must be backed up:

…\AspenTech\InfoPlus.21\c21\h21\dat\, including the map.dat file
A map.dat file is required to interpret the data in InfoPlus.21 history
(archive) file sets. Whenever history file sets are moved to a new system,
their map.dat file must also be moved.
Important: Backups of history file sets without the map.dat file could be
useless, causing complete loss of historical data if the map.dat file is lost.

…\AspenTech\InfoPlus.21\c21\etc\
Important: Make sure that you back up any history repositories that are
not in the default locations.

…\AspenTech\InfoPlus.21\db21\sql\
DAT files in this directory contain ODBC link information used by SQLplus.
The following Cim-IO file must be backed up:

…\AspenTech\InfoPlus.21\db21\etc\cimio_logical_devices.def
Backing up the h21\dat folder
To back up the h21\dat folder and its contents:
1
In Windows Explorer, locate the
…\AspenTech\InfoPlus.21\c21\h21\dat folder.
2
Select the dat folder.
3
Right-click and then select Copy.
4
Locate the Aspentemp folder.
5
Paste the dat folder in the Aspentemp folder.
Backing up the c21\etc folder
52
1
In Windows Explorer, locate the …\AspenTech\InfoPlus.21\c21\etc
folder.
2
Select the etc folder.
3
Right-click and select Copy.
4
Locate the Aspentemp folder.
7 Removing Features and Subfeatures
5
Paste the etc folder in the Aspentemp folder.
Backing up the db21\sql folder
1
In Windows Explorer, locate the …\AspenTech\InfoPlus.21\db21\sql
folder.
2
Select the sql folder.
3
Right-click and select Copy.
4
Locate the Aspentemp folder.
5
Paste the sql folder in the Aspentemp folder.
Backing up the cimio_logical_devices.def file
1
In Windows Explorer, locate the
…\AspenTech\InfoPlus.21\db21\etc\ folder.
2
Select the cimio_logical_devices.def file.
3
Right-click and select Copy.
4
Locate the Aspentemp folder.
5
Paste the cimio_logical_devices.def file in the Aspentemp folder.
Removing Features and
Subfeatures
Use the following method to remove AspenTech products.
1
Click Start | Programs | AspenTech | Uninstall AspenTech
Software. The AspenTech Uninstaller – Select Products dialog box
appears.
2
Select the features that you want to remove or click Select All to remove
all features listed.
3
Click Uninstall. Removal of the selected features begins.
4
When the removal is complete, click Close on the AspenTech
Uninstaller – Uninstall Progress dialog box.
After You Remove
When removing a product, product files that were added or modified since the
product was installed are not removed. Furthermore, any folders or
subfolders that contain such files are not removed. As a result, for example,
you would typically see that the InfoPlus.21 application folder remains and
includes a number of subfolders following the removal of InfoPlus.21. For
more about the locations of these folders, see “
Directory Locations and References” on page 9.
Generally, you should manually delete the InfoPlus.21 application folder and
its subfolders after verifying that you have backed up any files that you might
7 Removing Features and Subfeatures
53
need later on. You should have already done this if you followed the
instructions described earlier in this chapter in "Backing Up Additional Files."
If you intend to later re-install InfoPlus.21 family products on the same
computer, you should delete the InfoPlus.21 family application folders and
their subfolders first. You should also delete any history archives that were
created by the InfoPlus.21 family system that was just removed.
Removing User Application and Registry
files
User Application Files:

For Windows Server 2008
<local disk>\Users\%USER%\Application Data\[product]
User Registry Entries:

HKEY_USERS\%USER%\Software\Aspentech\[product]

HKEY_CURRENT_USER\Software\Aspentech\[product]
Removing Shares
After removing Aspen InfoPlus.21 family products and any user files, remove
share permissions on any folders that were established during the installation
or use of the product.
54
7 Removing Features and Subfeatures
8 Transferring InfoPlus.21
from One Computer to
Another
There are times when it is necessary to move an InfoPlus.21 system from one
computer to another. You can either:

Use the Aspen InfoPlus.21 Data and Configuration Transfer Wizard

Manually transfer data and configuration information
Notes:



In order to use the Data and Configuration Transfer Wizard, the source
computer and the target computer must have InfoPlus.21 V7.1 or later
installed.
“Target computer” refers to the new computer and “source computer”
refers to the old computer.
The Aspen InfoPlus.21 Data and Configuration Transfer Wizard is intended
for use over a local area network (LAN) only.
Important! The Data and Configuration Transfer Wizard will only transfer
archive files; it will not transfer archive file backups.
Firewall Considerations
If a firewall is between the source and target InfoPlus.21 systems, you may
need to manually open ports to allow the Data and Configuration Transfer
Wizard to run. The default ports are 17229 and 17230. In some situations,
however, you will simply be prompted to allow the unblocking of the firewall.
Using the Data and
Configuration Transfer Wizard
Using the Data and Configuration Transfer Wizard to move an InfoPlus.21
system from one computer to another involves the following steps.
8 Transferring InfoPlus.21 from One Computer to Another
55
1
On the target computer, install InfoPlus.21 as described in the “Installing
for the First Time” chapter of this guide.
2
On the target computer, start InfoPlus.21 and verify the installation as
described in the “After Installing for the First Time” chapter.
3
On the target computer, stop InfoPlus.21 using the InfoPlus.21 Manager.
4
On the source computer, start the Data and Configuration Transfer Wizard
by clicking Start | Programs | AspenTech | Aspen Manufacturing
Suite | Aspen InfoPlus.21 | Data and Configuration Transfer
Wizard.
5
On the source computer, at the Source and Target Identification
screen, click Source Computer and then click Next.
Note: The Wizard will remain open on the source computer until the files
have been successfully transferred to the target computer.
6
On the target computer, start the Data and Configuration Transfer Wizard
by clicking Start | Programs | AspenTech | Aspen Manufacturing
Suite | Aspen InfoPlus.21 | Data and Configuration Transfer
Wizard.
7
Follow the wizard instructions on both the target and source computers.
8
Manually transfer the data and configuration files for other applications
such as Local Security Server and Aspen Calc. For instructions on moving
Aspen Calc, see “Moving Aspen Calc” on page 61.
9
On the target computer, start InfoPlus.21 and verify that all old history
files can be viewed.
10 Configure Cim-IO on the target InfoPlus.21 system to collect process data
from the same data acquisition systems (DCS) that are currently
supplying the source InfoPlus.21 system.
Enabling Logging of Messages
By default, the Data and Configuration Transfer Wizard will save messages to
log files in C:\ProgramData\AspenTech\InfoPlus.21\SettingsWizard\Log when
it exits.
However, there is also an advanced way to view live messages. This requires
having a file named Infoplus21SettingsWizard.exe.config with the content
below along with the executable. In addition, an external program from
Microsoft named DebugView must be run. You can obtain this file from
<http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx>.
<configuration>
<system.diagnostics>
<switches>
<!-- possible values for SwitchLevel -->
<!-- 0 : Off -->
<!-- 1 : Errors -->
<!-- 2 : Warnings -->
<!-- 3 : Informational -->
<!-- 4 : Verbose -->
<add name="SwitchLevel" value="3"/>
</switches>
56
8 Transferring InfoPlus.21 from One Computer to Another
</system.diagnostics>
</configuration>
Data and Configuration Transfer Wizard
Interruption
You can stop the Data and Configuration Transfer Wizard by clicking the
Cancel button.
However, if the Data and Configuration Transfer Wizard is interrupted by
some other occurrence, you should restart it from the beginning. You should
also note the following:
During the transfer, all original files are renamed in their respective folder.
The new name is a concatenation of the original file name and a randomly
generated number. The number is actually a globally unique identifier or
GUID. This GUID is generated when the Data and Configuration Transfer
Wizard is launched and is used throughout the session. As a result, each
invocation of the Wizard has a different GUID. For example, the snapshot file,
Infoplus21.snp, would be renamed to something like:
Infoplus21.snp_3F2504E0-4F89-11D3-9A0C-0305E82C3301
All other files that are part of the transfer will have a similar extension. For
history filesets, only the root folder that contains them is renamed.
When the Wizard is interrupted, you can do either of the following to clean up
these files and prevent overloading the disk:

Restore the files to the original names.

Remove the temporary files.
One easy way to look for the files is to search for all files that have a similar
GUID extension. Typically, InfoPlus.21 files are in the …\AspenTech
\Infoplus.21 folder. For more about folder locations, see “
Directory Locations and References” on page 9.
Manually Transferring Data and
Configuration Information
For versions of InfoPlus.21 earlier than V7.1, you must use this manual
procedure for transferring data and configuration information. The Data and
Configuration Wizard can only be used with V7.1 and later.
1
On the target computer, install InfoPlus.21 as described in the “Installing
for the First Time” chapter of this guide.
2
On the target computer, start InfoPlus.21 and verify the installation as
described in the “After Installing for the First Time” chapter of this
guide.
3
On the target computer, stop InfoPlus.21 using the InfoPlus.21 Manager.
8 Transferring InfoPlus.21 from One Computer to Another
57
4
If the target computer has a different name (not the same as the source
computer), stop any Cim-IO interfaces that are updating InfoPlus.21 on
the source computer.
5
On the source computer, save a database snapshot using the InfoPlus.21
Manager.
6
On the source computer, stop InfoPlus.21 using the InfoPlus.21 Manager.
7
On the source computer, save the InfoPlus.21 group configuration as an
.ipg file (ip21.ipg) using the InfoPlus.21 Manager.
8
Copy InfoPlus.21 files from the source computer to corresponding
locations on the target computer.
o
InfoPlus.21 database snapshot(s)
o
Saved InfoPlus.21 group configuration file (ip21.ipg)
o
All files in the …\AspenTech\InfoPlus.21\c21\h21\dat folder.
Files to be copied include: map.dat, config.dat, and tune.dat.
o
Dbclock.config file.
o
SnaspshotsList.config file.
o
Files from the history repository and file set folders. You will probably
need to create history repository and archive file-set folders as
required to match corresponding folders on the source computer. If
the file folder hierarchy is the same, you can just use Windows
Explorer to simply drag-and-drop repository and file set folders.
o
Verify that you have copied (in the previous step) the cache.dat files
from the history repositories on the source computer to the history
repositories on the new computers. Also make sure to copy any
event.dat and save.dat files if they exist.
Note: Later, after InfoPlus.21 is restarted, the save.dat file (if any)
should disappear immediately. The event.dat file should unbuffer after
some time.
9
On the target computer, restore the ip21.ipg file using the InfoPlus.21
Manager. Then, inspect the tasks in the Defined Tasks list to confirm that
task list upgrade was successful and to ensure their parameters are what
you intend them to be (especially TSK_DBCLOCK).
10 On the target computer, ensure that the TSK_DBCLOCK command line
parameter references the database snapshot to be loaded on startup.
11 On the target computer, ensure that the database size (in 16-bit words),
as shown on the TSK_DBCLOCK command line, exceeds the size of the
database to be loaded.
12 If the target computer has a different name, then use h21chgpaths to
update the history config.dat file, replacing all references to the source
computer name with references to the new computer name.
Note: h21chgpaths.exe resides in the
…\AspenTech\Infoplus.21\c21\h21\bin folder. h21chgpaths is run
from the command line with path parameters passed on the command
line. Execute this program with no parameters to see usage information
output.
This is necessary if history repository and/or file set paths are specified in
UNC format; otherwise, the new InfoPlus.21 system would attempt to
write history to file sets on the source computer. This step is not
58
8 Transferring InfoPlus.21 from One Computer to Another
necessary if history paths are not specified in UNC format. File path
syntax is in UNC format if it embeds computer and share names. For
example, \\MYBOX\IP21g200His\arc2 is the UNC path for an archive file
set. In contrast, “c:\program
files\AspenTech\InfoPlus.21\c21\h21\arcs\arc2” is an example of a nonUNC designation of the same file set.
13 You may also need to use the h21chgpaths utility if you are setting up
different history folder hierarchies. This would be necessary, for example,
if the d: drive was used on the new computer and the c: drive was used
on the source computer.
14 On the target computer, configure Cim-IO.
o
Perform the Cim-IO “Client and Server Configuration” as documented
in the “Cim-IO Installation and Setup” chapter of the Cim-IO User’s
Manual. This involves editing three files: services,
cimio_logical_devices.def, and cimio_errors.def. You should be able to
simply copy relevant portions from corresponding files on the source
computer.
o
Copy the cimio_autostart.bat and cimio_autostop.bat files from the
source computer.
o
Remove environment variable references from the .bat files.
o
If there were Cim-IO Interfaces installed on the same node as
InfoPlus.21, re-install each interface then copy the Cim-IO Server
specific configuration/startup files that may have been manually
changed since the last installation of each interface (Please refer to
each Cim-IO Interface specific manual).
o
Optionally execute the CimioSecurity.exe program (if desired) as
documented in the “Cim-IO Installation and Setup” chapter of the CimIO User’s Manual.
o
Use the Cim-IO Test Utility program to verify access to the Cim-IO
servers defined in the “Cim-IO Installation and Setup” chapter of the
Cim-IO User’s Manual.
15 Perform the following if the ADSA Directory server was installed.
o
On the source computer, export the old ADSA data source information
as XML.
o
Invoke the ADSA Client Config Tool.
o
Click Public Data Sources to invoke Aspen Public Data Sources.
o
Click Export to invoke the Get Export File Name dialog box.
o
Browse to an appropriate folder, specify a filename, and click Save.
o
On the target computer, copy the XML file just saved from the source
computer.
o
On the target computer, import the source ADSA data source
information.
o
Invoke the ADSA Client Config Tool.
o
Click Public Data Sources to invoke Aspen Public Data Sources.
o
Click Import to invoke the Get Import File Name dialog box.
o
Find the XML file and click Open to restore.
8 Transferring InfoPlus.21 from One Computer to Another
59
o
Make sure all client machines that pointed to the ADSA Directory
server on the source computer now point to the ADSA Directory server
on the target computer.
16 Perform the following if SQLplus was installed.
o
Copy any compressed query source files from the existing source
directory to the same directory on the target system.
o
Copy any user created query files to the target system.
o
Copy the file "links.dat" from the existing source directory to the same
directory on the target system. This contains the database link
information.
17 If you are upgrading to a new version of InfoPlus.21, then you probably
need to upgrade your database snapshot. You can upgrade a database
snapshot using the InfoPlus.21 Database Upgrade Wizard.
18 Start InfoPlus.21 and verify that it is working properly.
19 Verify that any InfoPlus.21 Administrator application on other computers
can access this new InfoPlus.21 if they were previously able to access the
source InfoPlus.21 system. If you encounter problems, see the relevant
section in “Appendix D: Troubleshooting” in this manual.
20 If Local Security Server was moved, then copy AFWDB.mdb from the
source computer to the new computer. The AFWDB.mdb file resides in the
...\AspenTech\LocalSecurity\Access97 folder.
21 If Local Security Server was moved, then make sure all client machines
that pointed to the Local Security Server on the source computer now
point to the Local Security Server on the target computer.
22 On the target computer, use the InfoPlus.21 Administrator to configure
the following:
o
InfoPlus.21 database-level permissions are set via the Permissions
tab of the database Properties dialog box. You will probably want to
set them to same settings as on the source system.
o
Audit trail message generation is enabled or disabled via the Audit
Trail tab of the database Properties dialog box.
o
Compliance-enabling features are enabled via the Compliance tab of
the database Properties dialog box. Caution: Be sure you really want
to do this, as this action is irreversible.
23 If the target computer has a different name, you may need to make
corresponding edits to the Hosts file on any computers that directly access
the new computer. This includes computer hosting desktop applications
(such as Process Explorer) and Cim-IO interfaces.
24 If the target computer has a different name, the cimio_logical_devices.def
files on any Cim-IO interface computers will need to be updated to reflect
the new nodename associated with the logical device.
25 If the target computer has a different name, delete the Cim-IO store file
of any Cim-IO interface that was previously updating the source system.
26 If the target computer has a different name, re-start any Cim-IO interface
that was previously updating the source system.
60
8 Transferring InfoPlus.21 from One Computer to Another
Moving Aspen Calc
Aspen Calc can be moved after InfoPlus.21, using the following steps:
1
Stop TSK_CLC1 on the source system.
2
Stop and then disable the "AspenTech Calculator Engine" service on the
source system.
3
Copy all the .atc files from the "calc" and "lib" folders on the source
computer to the same folders on the target computer.
4
Move any COM objects or Excel spreadsheets that the calculations use.
5
Stop the task TSK_CLC1 on the new system using the InfoPlus.21
manager.
6
Restart the "AspenTech Calculator Engine" service on the target system.
7
Start Aspen Calc, right-click on the calculation server and select "Change
InfoPlus.21 server". Enter the new InfoPlus.21 server name. This changes
all calculations to use the new InfoPlus.21 server.
8
Stop the "AspenTech Calculator Engine" service.
9
Copy the .atc files from the "bin" folder on the source computer to the
same folder on the target computer. The "bin" folder contains schedule
group and engineering unit information.
10 Restart the "AspenTech Calculator Engine" service on the target system.
This will start executing scheduled calculations.
11 Start the task TSK_CLC1 on the target system using the InfoPlus.21
manager.
Notes:


The above instructions pertain to moving InfoPlus.21, SQLplus, and Aspen
Calc. They do not cover moving other products (such as Production Record
Manager, and so on).
Cim-IO store files embed the node name of the destination computer. So,
if the target computer has a different name, then any Cim-IO store files
should be deleted since they will not forward to the target computer. See
Knowledge Base article 103176 (Clean start of Cim-IO w/ S&F).
8 Transferring InfoPlus.21 from One Computer to Another
61
62
8 Transferring InfoPlus.21 from One Computer to Another
9 Troubleshooting
This chapter contains:

Information that may help you if you have problems installing.

Some typical error messages.
The details within this chapter are solutions for common issues. Updates to
these and other solutions are available to licensed users on the AspenTech
Support Center at https://support.aspentech.com.
In addition, the Aspen InfoPlus.21 Product Family Configuration Guide has a
“Troubleshooting” chapter for issues that are not related to the installation of
these products.
Aspen InfoPlus.21
Manual resetting of SETCIM_GROUP_NAME
registry key
Starting with V7.1 of InfoPlus.21, all system-level environment variables are
no longer used. This includes the SETCIM_GROUP_NAME variable. This was
replaced by entries in the registry located under
HKLM\SOFTWARE\AspenTech\InfoPlus.21\11.1. As a default entry, there is a
“group200” registry entry and inside this entry is a leaf named
SETCIM_GROUP_NAME, which is assigned a string value of “group200”.
As part of the removal of NT group dependence, the InfoPlus.21 installation,
version 2006.x, always set the SETCIM_GROUP_NAME environment variable
to group200. Consequently, when upgrading a previous version of InfoPlus.21
where the active database group is NOT group200 (for example, group201 or
group300), the SETCIM_GROUP_NAME environment variable will point to the
wrong group after the post-installation reboot. If this happens, you may see
an error message that indicates one or more services failed to start during the
reboot. When you open the InfoPlus.21 Manager after the reboot is complete,
the InfoPlus.21 Manager will start up blank, which indicates that no database
configuration information was loaded.
In addition, if the previous version installation had a group200 service still
listed (but disabled), the V7.1 or later installation may enable that service,
9 Troubleshooting
63
thereby preventing the appropriate service (group201, group300) from
starting.
Note: “Group” is the name used by InfoPlus.21 to denote the database’s
main directory. It is not related to Windows server groups.
Workaround:
To manually change the SETCIM_GROUP_NAME registry
key to point to the appropriate group name such as
group201 or group300:
1
Click Start | Run.
2
Type regedit and then press Enter.
3
Navigate to “My
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\InfoPlus.21\nn.
n” (where nn.nn = 11.2 for v7.2 systems).
4
Right-click the group200 key and select Rename. Enter the desired
group number.
5
Enter the group registry key and double-click the
SETCIM_GROUP_NAME key. Enter the same group number that was
entered in step 4.
6
Click OK.
7
Reboot the host machine again before attempting to start the database.
To solve the task service problem:
1
Click Start | Settings | Control Panel.
2
Double-click the Services icon. The Services dialog box is displayed.
3
Stop and disable InfoPlus.21 Task Service for group200.
4
Reboot the host machine.
Missing “InfoPlus.21” from InfoPlus.21
Administrator
Symptom:
The “InfoPlus.21” node does not show up in the InfoPlus.21 Administrator.
Cause:
The atinfoplus21object.dll is not registered properly.
Solution:
Try to register the atinfoplus21object.dll.
64
1
Invoke Windows Explorer.
2
Go to the <ASPENSHARED> folder.
9 Troubleshooting
3
Double-click atinfoplus21object.dll.
4
If registering a dll is the default action on your computer, double-clicking
atinfoplus21object.dll will cause another program, regsvr32.exe, to
register atinfoplus21object.dll. If not, an Open With dialog box is
displayed. In the dialog box, select Microsoft Register Server, and then
click OK.
Missing InfoPlus.21 data source from
InfoPlus.21 Administrator
Symptom:
A desired Infoplus.21 system does not show up after expanding the
“Neighborhood” node.
Cause 1:
The desired InfoPlus.21 system may not be configured as an ADSA data
source with “Aspen DA for InfoPlus.21”as a configured service.
Solution 1:
Make sure the desired InfoPlus.21 system is configured as a data source. For
more information on configuring public or user data sources, see the Aspen
InfoPlus.21 Product Family Configuration Guide.
Cause 2:
There may be network configuration problems that affect communication
between the two computers.
Solution 2:
Check the network configuration between the computer hosting the
InfoPlus.21 system and the computer hosting the InfoPlus.21 Administrator.
1
Invoke a command window on the InfoPlus.21 Administrator computer.
2
At the command prompt, type ping IP21_server_name where
IP21_server_name is the host name of your InfoPlus.21 system. Verify
that this command successfully returns the IP address of the remote
InfoPlus.21 system.
3
At the command prompt, type ping IP21_server_ip_address where
IP21_server_ip_address is the address returned from the first ping.
4
At the command prompt, type nslookup IP21_server_name. Verify that
this command succeeds and returns the IP address of the InfoPlus.21
server.
5
At the command prompt, type nslookup IP21_server_ip_address. Verify
that this command is successful.
6
All of the above tests should show a consistent host name and IP address.
7
Invoke a command window on the InfoPlus.21 system.
9 Troubleshooting
65
8
At the command prompt, type ping IP21_admin_name where
IP21_admin_name is the host name of the remote computer hosting
InfoPlus.21 Administrator. Verify that this command successfully returns
the IP address of the remote system.
9
At the command prompt, type ping IP21_admin_ip_address where
IP21_admin_ip_address is the address returned from the previous ping.
10 At the command prompt, type nslookup IP21_admin_name. Verify that
this command succeeds and returns the IP address of the remote system.
11 At the command prompt, type nslookup IP21_admin_ip_address. Verify
that this command is successful.
12 All of the above tests should show a consistent host name and IP address.
Cause 3:
The InfoPlus.21 Task Service is not running on the computer hosting
InfoPlus.21.
Solution 3:
Start or re-start the InfoPlus.21 Task Service from the operating system
Services applet on the computer hosting InfoPlus.21.
InfoPlus.21 Administrator Access Denial
Symptom:
Expanding an InfoPlus.21 server node results in the message “The user’s
access permission does not allow the operation”.
Cause:
The InfoPlus.21 Administrator user does not a have role that grants him or
her database READ permission.
Action:
Give the user a role that grants him or her database READ access. Verify that
the user can access InfoPlus.21 via ENGCON.
InfoPlus.21 Administrator Cannot Access
InfoPlus.21 v4.x (or earlier)
Symptom:
InfoPlus.21 Administrator V10 cannot access an InfoPlus.21 version 4.x (or
earlier) system although it can access an InfoPlus.21 version 5.x (or later)
system.
66
9 Troubleshooting
Cause:
The InfoPlus.21 Administrator computer and InfoPlus.21 system computer are
not within trusted domains. The InfoPlus.21 Administrator can only access
InfoPlus.21 version 4.x (or earlier) systems that are in the same domain or
within trusted domains.
ADSA
Class not registered (The specified
Windows NT host is not an ADSA Directory
Server)
The network connection is OK, but the ADSA Directory Server is not installed
on the specified computer.
Verify that the computer you are connecting to has the ADSA directory server
installed.
A remote activation was necessary but the
server name provided was invalid (Unable
to resolve server hostname to IP address.)
The ADSA server computer could not be located by name on the network. An
incorrect name may have been entered, the name may not be defined in the
network name lookup service, or the named server may be disconnected from
the network or powered off.
Enter a different name or IP address of a second computer where you
installed the ADSA Directory server.
This computer was unable to communicate with the computer providing the
server. (Could not connect to the specified host.)
Possible causes:

Cannot find the server

An error occurred during the TCP/IP setup

A firewall is blocking DCOM connection between the computers

The IP address provided is invalid
Possible Solution:
Verify that the name of the computer specified is correct. Try different naming
conventions for the computer name, such as:

The full DNS name. For example, myserver.mycompany.com

The Microsoft Networking computer name. For example, MYSERVER

The computer’s IP address. For example 001.002.003.004
9 Troubleshooting
67
Access denied
The remote ADSA Directory Server could not verify the identity of the user.
Possible Solution:
Log on again. You may have incorrectly typed the user name or password.
Process Explorer
Cannot open a new file in Aspen Process
Explorer
Meaning:
Aspen Process Explorer comes with four options that can be secured. File |
New is one of these options.
Possible Solutions:
Confirm that:

Security is configured for this option and that network access to a security
server (if appropriate) is available.

You are permitted to open a new file.
Note: For more about security, see the Aspen InfoPlus.21 Product Family
Configuration Guide.
Cannot save a file in Aspen Process
Explorer
Meaning:
Aspen Process Explorer comes with four options that can be secured. File |
Save is one of these options.
Possible Solutions:
Confirm that:

Security is configured for this option.

You are permitted to save a new file.
Note: For more about security, see the Aspen InfoPlus.21 Product Family
Configuration Guide.
68
9 Troubleshooting
Cannot open VBA in Aspen Process Explorer
Meaning:
Aspen Process Explorer comes with four options that can be secured. Opening
VBA is one of these options.
Possible Solutions:
Confirm that:

Security is configured for this option.

You are permitted to open VBA.
Note: For more about security, see the Aspen InfoPlus.21 Product Family
Configuration Guide.
Cannot open the Graphics Editor
Meaning:
Aspen Process Explorer comes with four options that can be secured. File |
Save is one of these options.
Possible Solutions:
Confirm that:

Security is configured for this option.

You are permitted to open the Graphics Editor.
Note: For more about security, see the Aspen InfoPlus.21 Product Family
Configuration Guide.
Cannot access a data source
Meaning:
The Aspen Data Source Architecture (ADSA) Directory Server or ADSA Client
on the computer where you installed Aspen Process Explorer is not configured
to “speak” to the data source.
Possible Solution:
Re-configure the data source with the ADSA Directory Server or the ADSA
Client on the computer.
Note: For more information, see the Aspen InfoPlus.21 Product Family
Configuration Guide.
9 Troubleshooting
69
Error message during the installation of
Aspen Process Explorer:
The installation of the Core Component Microsoft Data
Access 2.1 failed. Setup cannot continue.
Meaning:
Anti-virus software can slow down data transfer and thereby cause an
installation failure. This installation failure typically happens on slower
machines.
Possible Solution:
If you encounter this problem, temporarily disable your anti-virus software
and repeat the installation.
Error message when you try to start Aspen
Process Explorer:
Process Explorer failed to initialize VAO components.
Meaning:
Aspen Process Explorer may not function correctly if installed via a third-party
install utility, such as WinInstall.
Possible Solution:
Do not use a third-party install utility to install Aspen Process Explorer.
Error message when uninstalling:
Uninstall.ini should not be deleted when a user re-runs a
product install.
Meaning:
This error occurs when you install Process Data. It can also occur at a later
time, when you install Process Data with other subcomponents.
To work around the problem of the uninstall.ini getting duplicate entries
(which causes errors at uninstall with IDK 1.5), install and delete the
uninstall.ini first, then re-generate it.
Possible Solution:
Alternatively, you can rename the uninstall.ini file prior to reinstalling.
70
9 Troubleshooting
Data does not pass through a firewall
Meaning:
If using DCOM, ADSA cannot pass through a firewall.
Possible Solution:
Use Web Service if using ADSA with a firewall.
9 Troubleshooting
71
72
9 Troubleshooting
Glossary
ADO
ActiveX Data Objects (ADO) is the Microsoft standard for data access. ADO
allows data to be read from a large range of sources including Relational
Databases and text files. ADO can also read data using ODBC.
ADSA
ADSA is an application that provides an additional method to connect to a
data source. The SQLplus Query Writer and the Desktop ODBC can both use
the ADSA Directory Server to find and connect to SQLplus servers.
When the Query Writer starts up, it will get the list of SQLplus servers from
the ADSA and add these to the Query menu. You can then select a server
from the Query menu. ADSA provides an easy way to switch between servers
without having to remember the TCP/IP port number.
ADSA Client Config Tool
A common utility within the AspenTech Manufacturing Suite that allows you to
choose between configuring a User Data Source and a Public Data Source,
and that allows you to connect to a Public Data Source with the ADSA
Directory Server.
ADSA Directory Server
A shared computer on a network that stores connection data for AspenTech
applications and databases that allows the computer to identify and connect
to Data Sources.
Aspen Framework (AFW)
If implemented for a given site, Aspen Framework (AFW) provides an
environment for role-based security for AspenTech applications. Using AFW,
users can be associated with defined roles. Examples of roles include
Administrator, Engineer, Plant Operator #5, and User, each associated with a
set of privileges or tasks, such as read and write. Also see “Security.”
Glossary
73
Calculation
A Calculation consists of a Formula and a specification of Parameters, or
where the inputs are to be read from and the outputs written to (for example,
what tags are to be used).
A Calculation can either contain a Formula definition or can reference a
Formula from a Formula Library.
The input parameters can be read from InfoPlus.21 database fields, ADO data
sources, or other Calculations. The output Parameters can be written to an
InfoPlus.21 database field.
A Calculation can run in Test mode. In Test mode, outputs are not written to
the InfoPlus.21 database. They can be viewed from the Aspen Calc user
interface.
A Calculation can belong to several Schedule Groups.
COM
COM is the Microsoft standard for object components. Support for COM allows
Aspen Calc to include Calculations written in Visual Basic, Visual C++, and
Java.
Data Source
The name of the access services and their configuration parameters for a
database or other source of data. A Data Source could be called "Refinery A"
or "Acme Plastics, Plant Section B.” This name is associated with a list of
Service Components.
Desktop ODBC
Desktop ODBC provides access to SQLplus with ODBC-compliant applications
like Microsoft Access and Crystal Reports. For more information about
Desktop ODBC, see the SQLplus for InfoPlus.21 Help.
The Desktop ODBC Driver is an ODBC Version 2 driver that supports the Level
1 ODBC API and the Core ODBC SQL language (with extensions). The driver is
also compatible with the ODBC Version 3 driver manager and ODBC version 3
applications.
Domain
The domain name associated with a given UserID.
Formula
A Formula is a definition of how a Calculation is performed without specifying
from where the inputs are read and to where the outputs are written.
A Formula can be defined in the following ways:
74

CalcScript

VBScript

COM Object
Glossary

Excel Spreadsheet

Executable program
CalcScript is a simple language for defining Formulas. It can use other
formulas as functions and handles quality status propagation automatically.
(For detailed information on CalcScript, see CalcScript.)
Formulas are defined in Libraries. Before you define a Formula, you are asked
to select a Library in which it will be defined.
A Formula is not used by itself; it is always included in a Calculation. A
Formula can be used by many Calculations.
InfoPlus.21
AspenTech’s proprietary process information management system consisting
of a real-time database and process historian providing plant-wide operations
information, data monitoring, and analysis capabilities.
InfoPlus.21 Database
The InfoPlus.21 database resides in memory and consists of a number of
different types of records and associated structures that are used to locate
and process the records. It gathers process data from Cim-IO interfaces and
stores history in the InfoPlus.21 history repository. It is also capable of
storing data in a Microsoft SQL Server Relational Database.
The structure and behavior of a record is defined by its definition record. The
name, data type, location, display format, and behavior of every field in a
record are also defined by its definition record. Generally, many records are
defined by the same definition record. You can create new record types by
creating new definition records.
The fields within a record are grouped into areas. A record consists of a fixed
area and zero or more repeat areas. All the fields within the fixed area have
different names. In contrast, a repeat area can contain multiple occurrences
of the same fields. Each repeat area has an associated repeat count field in
the fixed area that indicates the number of occurrences within the repeat
area.
History is maintained for records that have one or more history repeat areas.
Tags are a special type of record that hold the process values (for example,
temperatures, flows, and so forth). InfoPlus.21 provides a set of 15 definition
records for creating standard tags.
Public Data Source
A Data Source stored on a directory server available to more than one user
on a public directory server. The configuration process is normally conducted
once per network, making it efficient for enterprise-wide solutions. This
process has the advantage of being able to limit users and groups that can
view the Data Sources. Furthermore, you can set security with this type of
Data Source.
Glossary
75
Query Writer
The Query Writer is a graphical user interface that creates, edits, and
executes SQL statements. You can run the Query Writer from a client
computer, or on the InfoPlus.21 server.
Role-Based Security
Role-based security is used to authorize and authenticate users of AspenTech
applications and data sources. By assigning users to roles that define work
activities, administrators can grant security privileges to members of a given
role instead of individual users.
Use Aspen Framework (AFW) Server or Aspen Local Security (ALS) to
establish roles and associate users with them.
Roles
Job-specific functions (such as Administrator, Engineer, Area #5 Operator) to
which user IDs or NT user groups are associated in order to assign users to
specific servers and a defined set of permissions. These roles provide profiles
for role-based security while giving users consistent access to tasks,
regardless of their network location.
Snapshot
A snapshot is a copy of the database at a particular time. A snapshot saves
the current state of the database. Snapshots can be saved manually, and a
snapshot is saved into a file specified in the TSK_SAVE task when you quit
InfoPlus.21
Selector Record
A selector record is a record that is used to associate user-specified character
strings (for example, NO and YES) with integer values (for example, 0 and 1).
Table
All data in a relational database is contained in tables. Each table consists of
rows and columns. For InfoPlus.21, a table is a "record" and a column is a
"field". A row is a single record or a single occurrence in a repeat area.
Tag
A tag is a database record with historical data.
User Data Source
A Data Source available to a single user on the user’s client machine. This
configuration process is normally conducted once per client and you cannot
set security with this type of Data Source.
76
Glossary
Appendix A – InfoPlus.21
Product Family Overview
The InfoPlus.21 product family includes many products that are used in
conjunction with InfoPlus.21. Their descriptions are in the following sections.
Aspen Calc
The Aspen Calc user interface lets users of all skill levels define, use, and see
the results of Calculations. It also provides a safe environment for ad-hoc
testing and “what if” Calculations and a secure public environment where
Calculations and formulas can be shared and used throughout the enterprise.
Calculations can be defined in a number of different ways, including CalcScript
Formula, Microsoft Excel Spreadsheets, Visual Basic Script, COM objects, and
user-written programs. COM is the Microsoft standard for object components.
Support for COM allows Aspen Calc to include calculations written in Visual
Basic, and Visual C++.
Aspen Calc lets you easily add Calculations and applications to the InfoPlus.21
system and provides automatic Quality Status propagation and engineering
unit conversion.
Calculations can use data from InfoPlus.21, ADO data sources, and other
Calculations. ADO (ActiveX Data Objects) is the latest Microsoft standard for
data access. ADO allows data to be read from a large range of sources
including Relational Databases and text files. ADO can also read data using
ODBC.
Calculations can be executed at regularly scheduled time intervals, on user
request, and for events such as InfoPlus.21 database changes. One feature of
Aspen Calc involving user requests is On-Demand Calculations. This feature
allows you to manually create and execute “on the fly” Calculations with
current data from multiple Aspen client applications, including Aspen Calc and
others, only when an application needs the results.
If you have Aspen Calc installed along with other Aspen applications on your
client or server, both Ad-Hoc Calculations and Stored Calculations are
available; if you do not have Aspen Calc installed along with Aspen Process
Appendix A – InfoPlus.21 Product Family Overview
77
Explorer, only Ad-Hoc Calculations are available but formulas cannot be used.
Along with Aspen Calc, these applications support On-Demand Calculations:

Aspen Calc

Aspen IQ

Aspen Process Explorer (including Process Data Add-in, Process Graphics
Editor, Real-Time SPC Configuration, and Tag Browser)

Aspen Watch

Process Data

SQLplus
Aspen Cim-IO
Aspen Cim-IO allows data transfer between Aspen products such as
InfoPlus.21 and external devices. Aspen Cim-IO has a client-server
architecture and is composed of three components: Cim-IO core, Cim-IO
client, and Cim-IO server.
The Cim-IO core consists of a set of subroutines that Cim-IO client and server
components call in order to communicate with each other. The Cim-IO core
must reside on all computers running a Cim-IO client or a Cim-IO server.
The Cim-IO client resides between the Aspen Product and the Cim-IO core.
The Cim-IO client’s function is to make requests such as get or put requests
to a Cim-IO server. The Cim-IO clients are specific to the AspenTech product.
The Cim-IO server resides between the Cim-IO core and the external device.
The Cim-IO server’s function is to communicate to a device. Each Cim-IO
server is specific to a device.
ADSA Directory Server
This manual explains how to install and configure the Aspen Data Source
Architecture (ADSA) Directory Server, and describes how to use the ADSA
Client, which is automatically installed. Whether your system configuration is
a network server, network workstation, stand-alone workstation, or any
combination of those, ultimately you must use AspenTech applications and
databases with an ADSA Directory Server or ADSA Client.
The ADSA Directory Server is a shared computer on a network that stores
connection data for AspenTech applications and databases that allows the
computer to identify and connect to data sources.
Important: The ADSA Directory Server connection does not cross most
firewalls.
The server in the ADSA allows you to configure the connection to the
following AspenTech databases:
78

File (a demonstration database)

InfoPlus.21

Simulator
Appendix A – InfoPlus.21 Product Family Overview
ADSA allows you to configure the connection to the following AspenTech
applications as well:

Aspen Calc

Aspen mMDM

Aspen Tag Browser

Aspen Production Record Manager

Event.21

Aspen Process Explorer

Aspen SQLplus

Transition Manager
It is important to familiarize yourself with these major elements of the ADSA
Directory Server to use AspenTech products in the AMS Suite:

ADSA Server

ADSA Client

Data Source

Service Component
ADSA Server
The ADSA Server stores the connection information for various data sources
and their constituent service components.
The ADSA Server reduces the work required to administer and maintain
AspenTech applications by centralizing the information needed to connect to
AspenTech databases such as InfoPlus.21. Users of client products such as
Aspen Process Explorer can easily discover connection parameters from an
ADSA Server or define and maintain personal data sources from an ADSA
Client. You can create one or more data source that contains the same
database.
ADSA Client
The ADSA Client allows you to configure and connect to User Data Sources
and connect to Public Data Sources.
Data-consuming client versus dataproducing applications
The ADSA Client is the actual interface between a data-consuming client and
data-producing applications, although ADSA Client may consult an ADSA
Directory Server to perform its function.
Some applications, Process Explorer is the main example, are pure data
consumers. They obtain data from other applications/products but do not
produce any data for other applications/products.
InfoPlus.21 databases are data-producing in that other applications obtain
data from them but they do not obtain data via ADSA from any other
application/product (CIM-IO and interfaces to the actual processes do not
Appendix A – InfoPlus.21 Product Family Overview
79
count here because they are more part of the “database” than not and, in any
case, do not use ADSA).
ADSA Client installs versus ADSA Directory
Server installs
Finally, some applications are both data-consuming and data-producing, like
SQLplus, Aspen Production Record Manager, and Aspen Calc. All three of
these applications appear to be data sources to some clients (like Process
Explorer), but they are in fact transforming data from some more
fundamental data source like InfoPlus.21. In this respect, SQLplus, Aspen
Production Record Manager, and Aspen Calc are data-consumers in the same
way as Process Explorer.
The issues of where ADSA Client installs versus where ADSA Directory Server
installs are only loosely related to producer/consumer distinctions. Any data
consumer (Aspen Process Explorer, Aspen Production Record Manager, Aspen
Calc, etc.) uses the ADSA Client to obtain a connection to a data producer.
To use a telephone analogy, the ADSA Client is akin to directory assistance. A
data consumer wants to call a data producer to obtain data. The data
consumer knows the producer’s name but not its number, so it asks directory
assistance—the ADSA Client. ADSA Client may be able to obtain the
producer’s number (all of the service parameters from the service property
pages) from information that is on hand: the User Data Source list on the
computer with the calling consumer. If the ADSA Client does not have the
“number” in its local exchange, it consults long-distance information: the
ADSA Directory Server.
In terms of which ADSA features run where, the ADSA Client must be local to
(on the same computer as) any consumer application. ADSA Client
automatically installs as part of the AMS core components.
On the other hand, the ADSA Directory Server is only used directly by ADSA
Client and ADSA Client knows how to communicate remotely with an ADSA
Directory Server.
Caution: The mechanism used by the ADSA Client to find possible ADSA
Directory Servers may not work across subnet boundaries (similar to, but
different, from the issues with DCOM across both subnets and firewalls). The
mechanism used by ADSA Client to find ADSA Servers is Windows “mailslots.”
If any network filtering device (for example, a router or firewall, or even
possibly a bridge) is between the Client and Directory Server, the network
device must forward mailslot broadcast packets.
Data Source
A data source is a name for the services and parameters needed to
configure a database. This configuration will enable the Aspen client products
to retrieve data from their associated databases. A data source could be
called “Refinery A” or “Acme Plastics, Plant Section B.” This name is
associated with a list of service components.
Two types of data sources are available to you:
80
Appendix A – InfoPlus.21 Product Family Overview

Public Data Source is a data source stored on a directory server
available to any users of that server. The configuration of Public Data
Sources is normally conducted once per network on an ADSA Directory
Server, making it efficient for enterprise-wide deployment and
maintenance. Each data source contains security data, an Access Control
List (ACL) that lists the users allowed or forbidden to view the Data
Source. This limits the users and groups that can view the data sources.

User Data Source is a data source available to a user on a user’s client
computer. The configuration process for a User Data Source is normally
conducted once per client, making it efficient for point solutions. ADSA
User Data Source lists are stored in the Windows profile for each user.
Therefore, each user generally possesses a personal User Data Source list.
Service Component
The service component, akin to a service running on a Windows operating
system, represents a piece of software that implements a protocol for
accessing data. Service components—also referred to as services—must
be configured to “talk to” a specific database or file instance or, in some
cases, another service component. It provides a mechanism for client
products to connect to servers and to a specific data source.
A named, configured service component is termed a configured service
component. Each type of service is represented by a unique identifier. This
identifier allows AspenTech products to map to only those data sources that
can provide a specific type of service. For example, a Batch application will
find Batch data sources, and a History application will find History data
sources.
Logical Collections of Databases
A system administrator may create a logical collection of databases. For
instance, classes of users are allowed access to different combinations of
Aspen products. Plant floor operators are allowed to see the process data in
InfoPlus.21 only, plant area supervisors are allowed to see process data and
batch data, and engineers are allowed to access all three. The system
administrator may want to define three data sources with different access
controls that correspond to these groups and InfoPlus.21 would be in all
three, Aspen Production Record Manager would be in two, and Aspen Calc
would be in only one.
Aspen InfoPlus.21
The InfoPlus.21 database resides in memory and consists of a number of
different types of records and associated structures that are used to locate
and process the records. InfoPlus.21 gathers process data from Cim-IO
interfaces and stores history in the InfoPlus.21 history repository.
The InfoPlus.21Administrator is a general-purpose graphical user interface
(GUI) used for performing system administration tasks for some AspenTech
products.
Appendix A – InfoPlus.21 Product Family Overview
81
The Definition Editor is a tool that helps customize and manage definition
records in the InfoPlus.21 database. A definition record defines the structure
and behavior of other records.
Aspen Process Explorer
Aspen Process Explorer is an AspenTech client application used to plot and
analyze data in real time from one or more data sources. It is a powerful tool
because of its data analysis and reporting capabilities integrated through
Microsoft ActiveX technology.
Aspen Process Explorer tools include:

Process Data components, distributed with the Aspen Process Explorer
core components. When used with InfoPlus.21, Process Data requires
SQLplus and Desktop ODBC.

Process Data Add-in components for Microsoft Excel, distributed with the
Aspen Process Explorer core components.

Aspen Tag Browser, distributed with the Aspen Process Explorer core
components, requires Desktop ODBC when used with InfoPlus.21.

Automation Interfaces and VBA for Process Explorer, distributed with the
Aspen Process Explorer core components.

Process Graphics Editor, which works with Aspen Process Explorer and the
Aspen Tag Browser, is distributed with the Aspen Process Explorer core
components.
The Aspen Process Explorer is a client program that displays data from these
databases:

InfoPlus.21 2006.5 and later
–OR–

OPC-HDA
Aspen SQLplus
Aspen SQLplus™ is an SQL-based application that can retrieve, update,
delete, and insert data based on user-specified criteria with the following
InfoPlus.21 database.
The SQLplus product consists of the SQLplus Client, SQLplus ODBC, Web
Server, and Web Service features.
Note: SQLplus allows you to create and execute an Ad-Hoc Calculation if
Aspen Calc is installed. By having Aspen Calc installed along with SQLplus,
queries with Calculations written with the SQLplus Query Writer can be stored
as text files or as records in the InfoPlus.21 database. For more information
about how to use On-Demand Calculations in SQLplus, see the “Using OnDemand Calculations in SQLplus” topic of the SQLplus Help for InfoPlus.21.
82
Appendix A – InfoPlus.21 Product Family Overview
Appendix B - Related
Documentation
In addition to this document, a number of other documents are provided to
help users learn and use the InfoPlus.21 family of products. The
documentation set consists of the following:
Printed documentation
Aspen InfoPlus.21 Product Family Configuration Guide
Aspen InfoPlus.21 Product Family Release Notes
Aspen InfoPlus.21 Database Developer’s Manual
Aspen InfoPlus.21 Database User’s Manual
Aspen InfoPlus.21 Database API Manual
Aspen Local Security Server Installation Manual
Aspen Real-Time SPC Analyzer User’s Guide
Software License Manger Installation and Reference Guide
Help files
Aspen Calc Help
Aspen Calc Server Help
Aspen Calc Web User’s Guide
Aspen Cim-IO Interface Manager Help
Aspen Cim-IO IP.21 Connection Manager Help
Aspen Data Source Architecture Directory Server Help
Aspen InfoPlus.21 Administration Help
Aspen InfoPlus.21 Administrator Help
Aspen IP.21 Configuration Tool Add-In Help
Aspen IP.21 Browser Graphic Studio Help
Appendix B - Related Documentation
83
Aspen KPI Builder Help
Aspen MES Cluster Administrator Help
Aspen Process Data Add-In Help
Aspen Process Explorer Help
Aspen Process Graphics Editor Help
Aspen Real-Time SPC for Process Explorer Help
Aspen SQLplus Help for InfoPlus.21
Aspen SQLplus Reporting Help
Aspen Tag Browser Help
aspenONE Process Explorer Help
Definition Editor Help
Event.21 Help
Event.21 Server Help
GCS Migration Tool Help
Replace Definition Editor Help
OPC Address Scan Help
84
Appendix B - Related Documentation
Appendix C - Installing
Internet Information
Services (IIS)
This chapter contains information about installing and configuring Internet
Information Server (IIS) for Windows Server 2008 and Windows Server 2012.
IIS must be installed and configured for aspenONE Process Explorer to
function. Additionally, ASP.NET must be installed and configured for Tag
Search to function.
Notes:


FTP Server and SMTP Service are not required and can be omitted from the IIS
install.
On Windows 2008 Server, the following additional IIS components must
be enabled:
Management tool items - IIS6 Management Compatibility (all sub items
selected)
Application development items – ASP Windows Server 2008
Configuration
Prior to installing aspenONE Process Explorer, you must install and configure
Internet Information Server.
To install and configure IIS on Windows Server 2008:
1
From Control Panel, select Programs and then Programs and
Features.
2
In the Tasks list, click the Turn Windows features on or off link. The
Server Manager dialog box is displayed.
3
Expand the Roles node, and select Web Server (IIS).
If Web Server (IIS) is not one of the enabled roles, then click Add
Roles, and add it.
After the role is added, then add Role Services, as described next.
Appendix C - Installing Internet Information Services (IIS)
85
4
In the right pane of the Server Manager dialog box, find the Web
Server (IIS) section, and click Add Role Services.
Add the following Role Services. (NOTE: When you are selecting them,
allow Windows to add the required dependent role services, if prompted.):
Common HTTP Features
Security




 Basic Authentication
 Windows Authentication
 Request Filtering
Static Content
Default Document
Directory Browsing
HTTP Errors
Performance
Application Development





ASP.NET
.NET Extensibility
ASP
ISAPI Extensions
ISAPI Filters
 Static Content Compression
Management Tools
 IIS Management Console
 IIS 6 Management Compatibility
(NOTE: Enable ALL sub-items for
this service.)
Health and Diagnostics
 HTTP Logging
 Request Monitor
Note: CGI is not directly used by our software and is not listed as a
requirement for IIS applications. However, some customers have found that
CGI is required for IIS Windows Authentication to work successfully for all
users. If CGI is used, the following command should be executed from a
command prompt on your server to address a Proxy Header Security
Vulnerability with CGI:
appcmd set config /section:requestfiltering
/+requestlimits.headerLimits.[header='proxy',sizelimit='0']
See (https://support.microsoft.com/en-us/help/3179800/iis-cgi-http-proxyheader-requests-may-be-redirected) for details.
5
Close the Server Manager dialog box and Programs and Features
window when complete.
To install and configure IIS on Windows Server 2012:
1
From Control Panel, in the Programs section, click the Turn Windows
features on or off link.
The Server Manager Dashboard is displayed. Afterwards, the Add
Roles and Features Wizard is displayed.
86
2
If the Before you Begin page is displayed, click Next.
3
On the Installation Type page, select the Role-based or featurebased installation option. Then click Next.
4
On the Server Selection page, confirm that the appropriate server is
selected in the Server Pool frame, and then click Next.
5
On the Server Roles page, select the Web Server (IIS) row from the
Roles list. The Add Roles and Features Wizard dialog box is displayed.
6
In the Add Roles and Features Wizard dialog box:
Appendix C - Installing Internet Information Services (IIS)
o
Select the Include management tools (if applicable) check box.
o
Then click the Add Features button to add web server and
management tools features.
As a result, the Add Roles and Features Wizard dialog box closes.
Focus returns to the Server Roles page, where the Web Server (IIS)
check box is now enabled and selected.
7
On the Server Roles page, now that the Web Server (IIS) role check
box is enabled and selected, click Next.
8
On the Features page, select the following items from the Features list.
Note: As you select items, allow the wizard to add required dependent
features and services.
9
.NET Framework 3.5 Features
.NET Framework 4.5 Features
 .NET Framework 3.5




.NET Framework 4.5
ASP.NET 4.5
WCF Services | HTTP Activation
WCF Services | TCP Port Sharing
Return to the Server Roles page.
From the Roles list, expand the Web Server (IIS) node and, under it,
expand the Web Server node. This enables you to select the following
items.
Note: As you select items, allow the wizard to add required dependent
features and services.
Common HTTP Features
Application Development













Default Document
Directory Browsing
HTTP Errors
Static Content
HTTP Redirection
Health and Diagnostics
 HTTP Logging
 Request Monitor
Performance
 Static Content Compression
Security




Request Filtering
Basic Authentication
Digest Authentication
Windows Authentication
.NET Extensibility 3.5
.NET Extensibility 4.5
ASP
ASP.NET 3.5
ASP.NET 4.5
ISAPI Extensions
ISAPI Filters
Server Side Includes
Management Tools
 IIS Management Console
 IIS 6 Management Compatibility
(NOTE: Enable ALL sub-items for
this service.)
 IIS Management Scripts and Tools
Note: FTP Server and SMTP Service are not required and can be omitted
from the IIS install.
Appendix C - Installing Internet Information Services (IIS)
87
Note: CGI is not directly used by our software and is not listed as a
requirement for IIS applications. However, some customers have found that
CGI is required for IIS Windows Authentication to work successfully for all
users. If CGI is used, the following command should be executed from a
command prompt on your server to address a Proxy Header Security
Vulnerability with CGI:
appcmd set config /section:requestfiltering
/+requestlimits.headerLimits.[header='proxy',sizelimit='0']
See (https://support.microsoft.com/en-us/help/3179800/iis-cgi-http-proxyheader-requests-may-be-redirected) for details.
10 On the Confirmation page, click Install.
11 After the features are installed, the Results page is displayed. Click
Close.
12 Close the Server Manager Dashboard when all tasks are completed.
88
Appendix C - Installing Internet Information Services (IIS)
Appendix D - Aspen
Manufacturing Suite S95
Solution
The Aspen S95 solution allows you flexibility for large-scale installations by
providing a method and associated tools for supporting S95 tag aliases.
An S95 tag alias fully describes an object and where it resides within an
installation hierarchy. S95 tag aliases offer an easy way to retrieve data for
specific equipment, rather than looking up individual tag names.
The form of an S95 tag alias is S95 Equipment@Tag Alias. An example is
“Plant.Area.Machine@Temperature.”
The AMS S95 solution provides the following areas of support for S95 tag
aliases:

mMDM Database

Tag Browser – for Aspen Windows client applications

Tag Search – for Aspen Web client applications
Aspen S95 Naming Conventions
AspenTech's implementation of S95 includes the following naming
conventions:

The "hierarchy" name under which the S95 tag aliases are defined is
always S95.

The "class" name under which the S95 tag aliases are defined is always
TagAlias.

The tag attribute used with the tag mappings is always the field defined in
the map record by MAP_VALUE.
Appendix D - Aspen Manufacturing Suite S95 Solution
89
mMDM Database
The mMDM database stores and matches tag names with their associated tag
aliases. This mMDM database can be exported into an XML file and made
available for clients. In some cases, you can improve performance of mMDM
client applications by using the XML file option (for more details, see the
mMDM Installation Guide).
Tag Browser and Tag Search
The Tag Browser and Tag Search tools are updated to support S95 tag alias
searches in the mMDM. In addition, these tools have been added as standard
components to various AMS products.
The data from an S95 tag alias can be used in supported AMS products in the
same way as tag names. S95 tag alias display is optional in supported AMS
products; tag names will remain the default identification method. For
example, the plot legend will offer NAME as a column by default. If you want
to display the S95 tag alias, you must first add the S95 Tag Alias column to
the legend.
Installing and Configuring an
AMS S95 Solution
To install and configure an AMS S95 solution:
1
Install and configure the mMDM database according to the mMDM
Installation Guide.
2
Install and configure the AMS products, including the ADSA Directory
Server (ADSA). Any products that support S95 browsing will also install
the required mMDM S95 Web Service and its associated components.
3
Configure the mMDM Web Service and component configuration files
according to the installation and configuration guides for all installed S95enabled applications (InfoPlus.21, Aspen Process Explorer, ADSA, Aspen
Production Record Manager, SQLplus, and Aspen Calc).
4
Refer to the user guides and online help of installed S95-enabled
applications for product-specific S95 tools.
Note: AspenTech recommends the following computer system hierarchy for
AMS products:


90
Server Computer – mMDM data source, InfoPlus.21, ADSA, Aspen web
server (Aspen Calc or Production Record Manager)
Client Computer– Client applications (Aspen Process Explorer, Aspen
Production Record Manager)
Appendix D - Aspen Manufacturing Suite S95 Solution
Creating an mMDM Database
By default, AMS clients will assume that the mMDM database is the desired
target for resolving S95 tag aliases. Even if you choose to use the XML file
option for performance, the data remains in the mMDM; the XML is only an
image of the actual data.
Creating an mMDM XML File
Creating an XML file is optional. In some cases, it may offer improved
performance and a method for redundancy in the event of a problem with the
mMDM database. For details about the XML file option, see the mMDM
Installation Guide.
Once the XML file has been created, you will need to direct your data requests
to it by modifying the mMDM S95 Web Service and component configuration
files. See the installation and configuration guides for all installed S95enabled applications—such as InfoPlus.21, ADSA, Production Record Manager,
SQLplus, and Aspen Calc.
Setting Up ADSA
As with all AMS products, ADSA is required. ADSA is automatically configured
at installation time to resolve S95 tag aliases using the mMDM Web Service.
Alternatively, you can configure ADSA to use locally-cached XML copies of the
mMDM data instead of going to the mMDM S95 Web Service (this may
improve performance over a WAN, for example). For more information about
the configuration of the mMDM S95 Web Service, see the Aspen InfoPlus.21
Product Family Configuration Guide.
Adding Additional Tags and
Aliases
Tag aliases can be added and removed through the mMDM Administration
Tools after the mMDM database has been created. For more information, see
the mMDM Administration Manual.
Searching for S95 Tag Aliases
The Tag Browser and Tag Search tools both support searching and adding
S95 tag aliases to S95-enabled applications.
Note: The Tag Search tool does not support drag and drop.
Appendix D - Aspen Manufacturing Suite S95 Solution
91
Aliases in Graphics
Aspen Process Explorer Graphics Editor does not provide a field for entering
S95 tag aliases. But if an S95 tag alias is placed into the tag name field, it will
be resolved and displayed as the correct tag name.
92
Appendix D - Aspen Manufacturing Suite S95 Solution
Appendix E – Virtual Machine
Recommendations
While AspenTech supports the use of the AspenTech Manufacturing Suite
applications in virtual environments, this support is dependent on the virtual
environments themselves being implemented using the best practices
recommended by Microsoft and VMware. Likewise, the combination of
hardware and virtualization configuration must be in a manner supported by
the virtualization supplier.
Virtual environments, by their very nature, require additional resources such
as memory and CPU overhead, over and above those required by normal
operating systems and physical hardware. Likewise, networking, storage
requirements, and other I/O considerations can vary depending on hardware
type and usage. Therefore, AspenTech recommends that users should be very
thorough in their planning for the use of an aspenONE application in a virtual
environment.
Even if the virtualization system is perfectly configured, InfoPlus.21 would run
slower within a virtual machine than a similarly “equipped” physical machine,
especially if the virtualization software has to handle contention for resources
by multiple virtual machines.
If Aspen software runs fine on a physical machine, but very poorly on a
virtual machine, then possible causes might include:

Improper configuration of the system

Virtualization server overloading

Too many virtual CPUs
The latter problem may seem counter-intuitive as many people assume that
the adding CPUs will improve performance when doing so can actually
degrade performance. For example, Infoplus.21 performance could potentially
suffer when the hosting virtual machine has more than one virtual CPU.
The rest of this chapter explains why this is so and provides recommendation
regarding virtual CPU count.
Microsoft or VMWare virtualization servers can host multiple virtual machines
where each virtual machine has one or more virtual CPUs. The virtualization
software maps virtual CPUs to physical CPUs.
Appendix E – Virtual Machine Recommendations
93
Suppose you have physical server with four physical cores. Also suppose that
it is hosting ten single-CPU virtual machines. In this case, only four of the ten
virtual machines can be running at any given time. The other six virtual
machines have to wait for a physical CPU to go idle. When a virtual machine
relinquishes its CPU time (for example, waiting on disk I/O), the physical CPU
can be reallocated for use by another virtual machine that is ready for CPU.
But what happens if some of the virtual machines have been configured with
multiple virtual CPUs? For example, suppose your four-core physical server is
hosting ten single-vCPU virtual machines and one four-vCPU virtual machine.
With some virtualization scheduling algorithms, the four-vCPU virtual machine
may have to wait until all four physical CPUs are idle before it can become
active. In other words, it would be waiting for all ten single-vCPU virtual
machines to become idle. Obviously, it could be waiting for a very long time,
with an obvious degradation of perform imposed on the virtual machine with
more virtual CPUs.
Another potential problem relates to CPU cache if a virtual machine is given
access to a core on a different physical CPU. If a virtual CPU is remapped to a
different physical CPU, then the processor cache for the new core may need
to be re-loaded with information previously cached on the old processor.
It is important to stress that the CPU contention problems described above
may occur with some, but not all, virtualization platforms.
Another concern that is of special relevance for Aspen InfoPlus.21 is that
context switches may be much more expensive on virtual machines than on
physical machines.
If an InfoPlus.21 system of many processes (for example, more SQLplus IQ
tasks than necessary) is constantly contending for IP21 database access, then
there will likely be frequent process context switches. Context switches are
reportedly much more expensive on virtual machines, especially those with
multiple virtual CPUs. Furthermore, processes contending for InfoPlus.21
database access perform better if they are running on the same virtual CPU.
Better performance might be obtained by setting process affinity so that
processes that frequently interact with the InfoPlus.21 database are assigned
to the same CPU while other applications run on other CPUs.
94
Appendix E – Virtual Machine Recommendations