aspenONE Integration Foundation

Installation Guide
Version Number: V8.4
November 2013
Copyright (c) 1998-2013 by Aspen Technology, Inc. All rights reserved.

Aspen Integration Designer, aspenONE Integration Foundation, Aspen Enterprise Integration Framework,
aspenONE Infrastructure, Aspen Event Manager, Aspen Role-Based Visualization, Aspen Manufacturing Master Data
Manager, Aspen Operations Domain Model, Aspen Framework Server, Aspen License Manager, the aspen leaf logo
and Plantelligence and Enterprise Optimization are trademarks or registered trademarks of Aspen Technology, Inc.,
Burlington, MA.

All other brand and product names are trademarks or registered trademarks of their respective companies.

This document is intended as a guide to using AspenTechs 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.

200 Wheeler Road
Burlington, MA 01803-5501
USA
Phone: (1) (781) 221-6400
Toll Free: (888) 996-7100
URL: http://www.aspentech.com
Contents
1 Introduction .........................................................................................................3
Purpose ..........................................................................................................3
Overview.........................................................................................................3
Related Documentation .....................................................................................3
Technical Support ............................................................................................4

2 Overview ..............................................................................................................5
Purpose ..........................................................................................................5
aspenONE Overview .........................................................................................5
Packaging .......................................................................................................6
Organization of DVDs........................................................................................6
Accessing aspenONE Documentation ..................................................................7
aspenONE Integration Foundation Overview ........................................................7
Core .....................................................................................................8
Aspen Integration Designer .....................................................................9
System Requirements..................................................................................... 10
aspenONE Integration Foundation .......................................................... 10
Pre-Installation Checklist................................................................................. 12

3 Installing aspenONE Integration Foundation .....................................................13

Purpose ........................................................................................................ 13
Before You Install........................................................................................... 13
Installing Aspen Integration Foundation for the First Time ................................... 14
Verifying the Installation ................................................................................. 21
Restarting Virus-checking Software .................................................................. 21

4 Post-Installation Configuration ..........................................................................23

Purpose ........................................................................................................ 23
Aspen Integration Designer ............................................................................. 23

5 Upgrade or Repair aspenONE Integration Foundation ........................................25

Purpose ........................................................................................................ 25
Upgrading to V8.4 for existing TIBCO Users....................................................... 25
Upgrading or Repairing aspenONE Integration Foundation ................................... 26

6 Removing aspenONE Integration Foundation .....................................................27

Purpose ........................................................................................................ 27
Important Considerations ................................................................................ 27

7 Troubleshooting .................................................................................................29
Purpose ........................................................................................................ 29

1 Introduction 1
 Overview....................................................................................................... 29
EIF logging service fails to get the logs ................................................... 29
Special Considerations for Windows Server 2008 R2 and Windows 7........... 31
Oracle Error: Cannot load oramts.dll....................................................... 31

8 Frequently Asked Questions ...............................................................................33

Appendix A - Configuring Ports in Firewall for Windows Server 2008 ...................37

2 1 Introduction
1 Introduction

Purpose
This document describes how to install, upgrade, repair, and remove version
8.4 of aspenONE Integration Foundation on Microsoft Windows 2008
Server R2 SP1, Standard Edition, Windows Server 2012, Windows 8,
Professional or Enterprise Edition (for 64-bit applications), Windows 7
Enterprise SP1 (for 32- or 64-bit applications), or Windows 7 Professional SP1
(for 32-bit or 64-bit applications).

Overview
aspenONE Integration Foundation serves as a transport layer among diverse
applications, providing event-based dataflow and connectivity tailored for the
process industry. The instructions in this guide focus solely on installing Aspen
Enterprise Integration Framework (including Aspen Integration Designer) as a
single part of an integrated aspenONE Infrastructure solution.

Note: Aspen Manufacturing Master Data Manager (mMDM) V8.4 falls under
the aspenONE Integration Foundation umbrella; however, a separate
installation document, Aspen Manufacturing Master Data Manager Installation
Guide, is available from the online Customer Support site.
For information about Aspen Industry Solutions, see the aspenONE
Deployment Guide document.

Related Documentation
In addition to this document, a number of other documents are available to
help users learn and use aspenONE Integration Foundation. The
documentation set consists of the following:
aspenONE Integration Foundation Release Notes
aspenONE Integration Foundation Implementation Guide
Aspen Integration Designer Help
aspenONE Infrastructure Overview
Aspen Manufacturing Master Data Manager Installation Guide

1 Introduction 3
 Aspen Manufacturing Master Data Manager Getting Started Guide
Aspen Manufacturing Master Data Manager Implementation Guide

Technical Support
AspenTech customers with a valid license and software maintenance
agreement can register to access the online AspenTech Support Center at:
http://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-to-
date contact information is available at the AspenTech Support Center at
http://support.aspentech.com.

4 1 Introduction
2 Overview

Purpose
This chapter provides an overview of the aspenONE installation process, an
overview of aspenONE Integration Foundation, and includes the installation
requirements.
This chapter contains the following:
aspenONE Overview
Packaging
Organization of DVDs
Accessing aspenONE Documentation
aspenONE Integration Foundation Overview
System Requirements
Pre-Installation Checklist

aspenONE Overview
aspenONE is the comprehensive set of software solutions and professional
services provided by AspenTech; these are designed to help process
companies achieve their operational excellence objectives.
AspenTech releases its products on a single set of DVDs that are designed to
ease the installation of aspenONE products and/or modules. To achieve this
goal, all AspenTech products and modules use one installation procedure that
will guide you through your installation regardless of the products or modules
being installed.

Note: More information on aspenONE solutions, as well as the aspenONE

Licensing Model, can be found in the aspenONE Deployment Guide.

2 Overview 5
 Packaging
Included in your package from AspenTech, you will find the following items
that you will need prior to installation:
A packing slip listing the version of the media that you have received and
indicating whether or not a dongle and/or CD containing the license file is
included in the shipment.
Package of DVDs (see Organization of DVDs below).
If a license file is included, a dongle or separate CD (instructions on SLM
License File Installation are included on the CD).

Notes:
Before you begin installation, you will want to print copies of the
Installation Guides for products that will be installed. Those guides are
included on the Aspen Engineering and Aspen Manufacturing and Supply
Chain DVDs in your package.
An invoice noting which products you are licensed for is sent separately
from the software shipment.

Organization of DVDs
aspenONE delivers AspenTechs Process Modeling, Exchanger Design and
Rating, Economic Evaluation, Energy and Flare Analysis, Process Development
and Operations Support, Plant Operations, Process Control, and Supply Chain
Management products and documentation in a single set of easy-to-use
DVDs.
The DVDs are organized in the following way:
DVD 1, Aspen Engineering includes 32-bit versions of Aspen
Administration components (Aspen SLM, Aspen Security, Aspen SLM tools,
aspenONE Diagnostics, ALC Auto Upload Tool), Aspen PIMS and all Aspen
Engineering products and 64-bit version of Aspen Basic Engineering.
DVD 2, Aspen Manufacturing and Supply Chain includes 32-bit
versions of Aspen Administration components (Aspen SLM, Aspen
Security, Aspen SLM tools, and aspenONE Diagnostics, ALC Auto Upload
Tool), Aspen Manufacturing products (Information Management, Batch,
Production Management, and Advanced Process Control), Aspen Petroleum
Supply Chain products, Aspen Chemical Supply Chain products, and
aspenONE Infrastructure products. This DVD also includes Aspen
Inventory Management and Operations Scheduling (IMOS) and 64-bit
versions of Aspen Reporting Framework and Aspen Role-Based
Visualization.

Notes:
You do not need to insert DVDs in any particular order. Inserting any of
them will start the installation procedure, and you will be automatically
prompted to insert the next appropriate DVD to continue with your
installation.

6 2 Overview
 Some products previously available on CD-ROM or DVD are not included
on the aspenONE DVD product discs. If you do not find a product included
on the aspenONE DVD product discs, please contact AspenTech Support at
http://support.aspentech.com.
Third-party products that AspenTech delivers without any modification of
the software are delivered in their original packages.

Accessing aspenONE
Documentation
aspenONE V8.4 includes new ways to access documentation associated with
the aspenONE products. Documentation is now available directly from the
applications. This 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 clicking the
corresponding link on the first page of the Installation Browser.
Context-sensitive help can be accessed by:
o Clicking the Help button on an application dialog box
o Pressing F1
o Clicking the application Help menu and selecting Help
Additional documents in PDF format can be accessed by:
o Clicking the Online Documentation link on the products Start page or
Start tab or selecting Documentation from the products 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 and browsing the
Documentation page.
o Downloading all of the available documentation from the Customer
website by downloading the zip file that contains the documentation.

Note: The aspenONE Documentation DVD is no longer included in the DVD

package.

aspenONE Integration
Foundation Overview
aspenONE Integration Foundations Enterprise Integration Framework (EIF)
harnesses the power of Microsofts .NET Windows Communication Foundation
(WCF) to provide an alternative to the communication role formerly played by
the TIBCO product line in the aspenONE Product Suite architecture.
All of the Microsoft .NET technologies are aimed at the challenge of shifting
the developer mindset away from thinking about enterprise solutions in
object-oriented terms of objects and components. Instead, they promote

2 Overview 7
 thinking about solutions as an orchestration of loosely coupled services that
can be easily reused in other enterprise orchestrations.
Backward or legacy compatibility is an important business requirement, as is
upgrade deployment cost. WCF and the other .NET technologies (Windows
Workflow Foundation (WWF) and Windows Presentation Foundation WPF)) are
backward supported on all the Microsoft enterprise operation system
platforms, and they are provided by Microsoft without licensing cost.
Windows Communication Foundation (WCF) also plays a key role in
consolidating the myriad of technologies that are important to SOA. The WCF
can consolidate technologies because of the extensibility of its architecture.
There are many ways that distributed applications can communicate: HTTP
Web Services, message queuing, database persistence, TCP sockets, named
pipes. There are also numerous forms of dialog that distributed applications
can use: request-response, publish-subscribe, duplex, one-way. Then there
are various types of encoding and the issues surrounding evolving security
standards. The Windows Communication Foundation does not establish a
preference in any of the implementation issues surrounding all of these
options. Instead, it consolidates or embraces them all, providing the agility
required allowing the aspenONE Product Suite to be deployed in the manner
best suited for the customer.
Finally, there is often the need for the tight integration of application
communication and orchestrated workflow. The Web Services adapter allows
applications to integrate with Aspen EIF via a web service API.

Core
The Core component is a required component for all of the other Aspen
Enterprise Integration Framework (EIF) components.
This component of the Aspen EIF provides the communication platform based
on Microsofts .NET Windows Communication Foundation (WCF). It is installed
as a Windows service on each computer participating in the Aspen EIF
network.
The Aspen Enterprise Integration Framework Core has three WCF services (a
service that has specific meaning to WCF and not to be confused with a
Windows service): the Administration Service, the Discovery Service, and the
Document Exchange Service. The Aspen Enterprise Integration Framework
Core provides extensibility by exposing several interfaces for these services.
The Administration Service provides remote administration for the Aspen EIF
on or from that node. The interfaces exposed by this service are used by
Aspen Integration Designer. Aspen Integration Designer is a desktop
application that can be used to administer any Aspen EIF node or many at
once.
The Discovery Service maintains a near real-time list of all Aspen EIF nodes
on the network. The interfaces exposed by this service are used by the Aspen
EIF to discover other Aspen EIF nodes by sending multicast messages and
registering for the responses from other nodes. The list is used by the
runtime to minimize the need for static endpoint configuration.

8 2 Overview
 The Document Exchange Service encapsulates the WCF messaging
functionality and provides reliable, multi-transport communication for both
the legacy document-based messaging and service-oriented messaging.
Publish-subscribe and request-response communication is supported for both
types of messaging. The interfaces exposed by this service are used by
applications on the node as well as the Aspen EIF itself.
Separate interfaces are provided to support configuration-less service-
oriented messaging and to support adapter-configured document-based
messaging. For service-oriented messaging, the applications
programmatically specify the messaging topics. For document-based
messaging, the messaging topics are specified through configuration
managed by the Aspen Integration Designer.
The Document Exchange Service also supports certified message transport by
utilizing the Microsoft Message Queuing (MSMQ) as a message store and
forward when the destination endpoint of communication is unavailable. This
optional capability is a simple delivery option on subscription requests. No
configuration is required.
All communication handled by the Document Exchange Service is event-
driven to achieve maximum performance and low resource utilization. All of
the multi-threaded programming is performed by the Aspen Enterprise
Integration Framework and the Windows Communication Foundation.

Aspen Integration Designer

The Aspen Integration Designer provides an overall view and administrative
control for the aspenONE Integration Foundation services and adapters
throughout your network. The Aspen Integration Designer is a Windows
desktop application that can be installed without configuration on any
machine in the network where the Aspen Enterprise Integration Framework is
installed. It can also be installed and used on any number of machines.

Routing Service
The Router Communication Service provides seamless messaging between an
Aspen EIF network and any number of other Aspen EIF networks installed on
different subnets. It is installed as a Windows service on a computer on each
Aspen EIF network where seamless messaging is desired.

Aspen EIF Communication Service

For existing TIBCO customers, the Aspen EIF Communication service provides
seamless messaging between an Aspen Enterprise Integration Framework
network and any number of TIBCO Rendezvous networks. It is installed as a
Windows service on a computer that has a network presence on both the
Aspen EIF network and any number of Rendezvous networks.

Web Services Adapter

The Web Services adapter allows applications to integrate with Aspen EIF via
a web service API. This allows any outside application to participate in the

2 Overview 9
 Aspen EIF without being in a Windows or .NET environment. Web Service to
web service communication is used to exchange messages in an event-driven
fashion. Configuration information can be found in the appendices to this
document.

Aspen Enterprise Logging

Aspen Enterprise Logging is comprised of three components:
Aspen Enterprise Logging Server - A windows service that can be
discovered and configured in the Aspen Integration Designer.
Aspen Enterprise Logging Client - APIs that are provided to other
AspenTech products which write logs to the logging server.
Aspen Enterprise Logging Viewer - A test tool that can help you test and
query logs in the logging server.
Note: The Aspen Enterprise Logging Viewer application is a separate
query and diagnostic tool. You can use it to test writing logs to the logging
server and to view and filter the log messages. Because it lists log
messages from all EIF computers on a single display, it lets you easily
analyze EIF message flows between applications. You can launch it from
the executable file found in your program file bin.

Software Development Kit

AspenTech provides a set of developer's guide, reference guide and example
code targeted to the development of Aspen Enterprise Integration Framework
based adapters or Services.

System Requirements
This section provides the hardware, software, and user requirements for the
various components of aspenONE Integration Foundation.

Note: Windows XP is no longer supported.

aspenONE Integration Foundation

aspenONE Integration Foundation as a whole has the following hardware,
software, and user requirements.

Hardware Requirements
Resource Recommended Requirements for Server
Computer
Single or multi-processor Intel Pentium (or
Platform
compatible) 1.0 GHz
512 MB RAM minimum; 1 GB RAM
Physical Memory
recommended

10 2 Overview
 Resource Recommended Requirements for Server
Computer
Approximately 500 MB of available hard disk
Hard Disk Space
space for a system installation of aspenONE
Integration Foundation and all related products
RAID 5 with 3 9GB disk units (dependent on the
amount of data stored) for storage
DVD or network access to install product
Approximately 10 GB per year of online data
Database Space
1024768 16-bit
Display
TCP/IP network connection
Other
100 Mbps LAN or T3 WAN

Software Requirements
Type Component Notes

System Operating Server

System Microsoft Windows Server 2008 (Standard Edition)
R2, SP1 (64-bit)
-or-
Microsoft Windows Server 2012 (64-bit)
Client
Windows 8, Standard or Enterprise Edition (for 64-
bit applications)
-or-
Windows 7 Enterprise SP1 (for 32- or 64-bit
applications)
-or-
Windows 7 Professional SP1 (for 32- or 64-bit
applications)
-or-
Internet Internet Explorer 8 or higher
Browser
.NET Aspen Integration Designer relies on the Microsoft
Framework .NET Framework version 4.0 or 4.5. You may obtain
4.0 or 4.5 .NET Framework and updates from Microsoft.
.NET
Framework
3.5 SP1
Microsoft Aspen Enterprise Integration Framework requires
Message Microsoft Message Queuing (MSMQ). Obtain from
Queuing Microsoft if not previously installed. You will be
(MSMQ) prompted during installation if MSMQ is not installed.

2 Overview 11
 Type Component Notes

Software Licensing component. Required to install the

Aspen
License product. Can be found on any aspenONE 8.4
Products
Manager product disc.
(SLM) Note: Aspen V8.4 products require SLM Server 8.4 or
higher, but we recommend that you upgrade to SLM
Server 8.5 to take advantage of the latest
improvements. Before you install any Aspen products,
we recommend that you install and configure the SLM
License Server software on the computer you have
chosen to be your license server.

User Requirements
If you intend to install the product on a network drive, you must change
the user in Services Configuration from Local System to a user that has
permission to access the networked drive. You should also map the drive
before installing.
You must have Administrator privileges to the computer on which the
aspenONE Integration Foundation Adapters are being installed.
You must have Administrator privileges (or the equivalent) to the
applications with which adapters are communicating.

Note: We recommend that you install mMDM with the 64-bit installer on a
64-bit Windows OS.

Pre-Installation Checklist
Before installing aspenONE Integration Foundation components, refer to the
following checklist to ensure a smooth installation.
Confirm that the Aspen Software License Manager (SLM) is installed and
running.
Obtain IP Address or name of the SLM server.
For more information, see the Aspen Software License Manager
Installation and Reference Guide.
Check the system requirements for all components of aspenONE
Integration Foundation.
Ensure you have the required permissions. (See User Requirements
above.)
Since AspenTech no longer delivers TIBCO, existing customers who want
to use Aspen EIF with TIBCO must ensure that the TIBCO.Rendezvous.dll
version 1.0.2028.26472 or greater is installed to GAC. The Integration
Designer EIF Communication Service will not be discovered and configured
if this .dll file has not been manually delivered to GAC. To obtain the
correct version of the TIBCO.Rendezvous.dll, please go to the AspenTech
Support Center at http://support.aspentech.com.
It is recommended that you stop or disable any virus-checking software
before installing aspenONE Integration Foundation.

12 2 Overview
3 Installing aspenONE
Integration Foundation

Purpose
This chapter describes installing aspenONE Integration Foundation for the first
time.

Important: This guide assumes that you are only installing aspenONE
Integration Foundation. If you choose to install other AspenTech software
concurrently with the installation of aspenONE Integration Foundation, you
may encounter screens not described in this guide. Refer to the appropriate
product installation guides for those screens not described within this guide.
Additionally, the computer may have other AspenTech products installed,
which may result in screens not described in this guide.

Before You Install

1 Confirm the system requirements.
2 Print and review the aspenONE Integration Foundation Implementation
Guide for a discussion of Aspen Integration project deployment.
3 Print and review the Aspen Manufacturing Master Data Manager
Installation Guide, which includes installation information pertaining to the
Manufacturing Master Data Manager feature.
4 Take into consideration the following points:
o The Aspen Integration Designer must be installed on at least one
computer in the network that is running the aspenONE Integration
Foundation.
o There are two additional optional components which you should decide
whether to install: the Web adapters or Rendezvous adapters.
Note: The Internet Explorer installation forces a restart of the
computer.

3 Installing aspenONE Integration Foundation 13

 Installing Aspen Integration
Foundation for the First Time
When installing products from more than one disc, complete the installation of
all desired software from that disc before proceeding to the next.

Important: You must follow computer-restarting instructions at the end of

each disc installation.
1 Log on using the account name and password of an account in the
Administrators group of the target computer.
2 Insert aspenONE 8.4 Disc 2 in your DVD drive.
The AspenTech Installation Browser dialog box appears.
Note: If this dialog box does not appear a few seconds after inserting a
DVD, browse to the DVD drive and start setup.exe in the DVD folder.
Carefully read the instructions on the following dialog boxes, make your
selections, and proceed with the installation.

AspenTech Installation Browser

Note: Aspen Integration Framework can be installed as either 32-bit or 64-

bit. We recommend that you install mMDM with the 64-bit installer on a 64-
bit Windows OS.

14 3 Installing aspenONE Integration Foundation

 License Terms and Conditions

Prerequisite Validation

Note: The aspenONE Installer will display the Prerequisite Check Results
and Required Actions before proceeding. Click Detailed Report for more
information.

3 Installing aspenONE Integration Foundation 15

 Install Type

Product Selection

16 3 Installing aspenONE Integration Foundation

 Custom Install

Note: With Custom Install, you can choose to install only Aspen EIF and
select Web Adapters or Rendezvous adapters. Installing Aspen mMDM
requires Aspen EIF and installs both adapter options.

3 Installing aspenONE Integration Foundation 17

 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 appear. 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.

18 3 Installing aspenONE Integration Foundation

 Specify Licensing and Security

Specify Windows Account Information

3 Installing aspenONE Integration Foundation 19

 Verify Your Installation

Installation Progress

20 3 Installing aspenONE Integration Foundation

 Verifying the Installation
To verify that the components you selected were successfully installed:
Use Microsoft Windows Explorer to verify that files were copied to the
target program directory (<AspenRoot>\
Enterprise\Integration\Framework, where <AspenRoot> is the
directory in which AspenTech products were installed, typically
C:\Program Files\AspenTech).

Restarting Virus-checking
Software
If you stopped or disabled your virus-checking software, be sure to restart it
after you finish installing the components of aspenONE Integration
Foundation.

3 Installing aspenONE Integration Foundation 21

22 3 Installing aspenONE Integration Foundation
4 Post-Installation
Configuration

Purpose
This chapter will discuss the post-installation steps required for aspenONE
Integration Foundation.

Note: If you are using Aspen EIF with Windows Server 2008, please follow
the detailed directions in Appendix A to configure ports for Windows Server
2008.

Aspen Integration Designer

There are no post-installation configuration requirements for Aspen
Integration Designer. However, because AspenTech no longer delivers TIBCO,
existing customers who want to use Aspen EIF with TIBCO must ensure that
the Tibco.Rendezvous.dll is installed to GAC. The Integration Designer EIF
Communication Service will not be discovered and configured if this .dll file
has not been manually delivered to GAC.

4 Post-Installation Configuration 23
24 4 Post-Installation Configuration
5 Upgrade or Repair
aspenONE Integration
Foundation

Purpose
This chapter describes how to upgrade or repair aspenONE Integration
Foundation.

Upgrading to V8.4 for existing

TIBCO Users
Since AspenTech no longer delivers TIBCO, existing authorized customers
who want to use Aspen EIF with TIBCO must ensure that the following TIBCO
Rendezvous dlls are installed to GAC:
TIBCO Runtime Agent 5.3.2 (contains TIBCO Rendezvous 7.4.0, TIBCO
Third Party Libraries, and Java Runtime Engine 1.4.2)
TIBCO BusinessWorks 5.3.1 (contains only the process engine)
TIBCO Designer 5.3.0
An authorized user is a customer that has Aspen Integration Infrastructure
version 2006.5 and is current on SMS.
The Integration Designer EIF Communication Service will not be discovered
and configured if these .dll files have not been installed to GAC.

Important: Make sure that the TIBCO.Rendezvous.dll is version

1.0.2028.26472 or greater, particularly if you are upgrading from V2006 or
earlier, since AspenTech no longer installs the dll.
To obtain the correct version of the TIBCO.Rendezvous.dll, go to the
AspenTech Support Center at http://support.aspentech.com.

5 Upgrade or Repair aspenONE Integration Foundation 25

 Upgrading or Repairing
aspenONE Integration
Foundation
To upgrade or repair aspenONE Integration Foundation:
1 Insert aspenONE 8.4 Disc 2 into your DVD drive.
The AspenTech Installation Browser dialog box appears.
Note: If this dialog box does not appear a few seconds after inserting a
DVD, browse to the DVD drive and start setup.exe in the DVD folder.
2 Select Upgrade or Repair Existing Products, and follow the
instructions on the subsequent dialog boxes.

Note: We recommend that you install mMDM with the 64-bit installer on a
64-bit Windows OS.

26 5 Upgrade or Repair aspenONE Integration Foundation

6 Removing aspenONE
Integration Foundation

Purpose
This chapter describes removing aspenONE Integration Foundation and its
subcomponents.
If you need to reinstall aspenONE Integration Foundation after removing it,
use the instructions in Chapter 3, Installing aspenONE Integration
Foundation.

Note: For instructions on removing Aspen Framework Server, see the Aspen
Framework Server Installation Manual.

Important Considerations
Important information to know during the removal process:
To preserve configuration and undelivered data (ledger files), do not
delete the ledger, log, and SQL files.
The Software License Manager (SLM) Service must be running during the
upgrade/uninstall process.

To remove AspenTech software:

1 Log on using the account name and password of an account in the
Administrators group of the target computer.
2 Click Start | Programs | AspenTech | Uninstall AspenTech
Software.
The AspenTech Uninstaller Select Products dialog box appears.
3 Select Products to uninstall.

6 Removing aspenONE Integration Foundation 27

28 6 Removing aspenONE Integration Foundation
7 Troubleshooting

Purpose
This chapter describes troubleshooting information for Aspen Enterprise
Integration Framework (EIF) and its subcomponents.

Overview
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 http://support.aspentech.com.

EIF logging service fails to get the logs

The Aspen Logging server may not work properly if your Database server and
your Logging server are installed on different machines, and both of them did
not join in any domain.

Workaround
To solve this issue, you must change the MS DTC (Microsoft Distributed
Transaction Coordinator) configurations on both machines (your Database
server and your Logging server) using the following steps:
1 Invoke Component Services from Administrative tools.
2 Expand Console Root | Components Services | Computers | My
Computer.
3 Right-click My Computer and select Properties.
4 In the My Computer Properties window, click the MSDTC tab.
5 In the Transaction Configuration section, click Security Configuration
to open the Security Configuration dialog box.
6 On the Security Configuration dialog box, in the Security Settings:
a. Enable Network DTC Access.
b. Enable Allow Remote Clients and Allow Remote
Administration in Client and Administration.

7 Troubleshooting 29
 c. Enable Allow Inbound and Allow Outbound in Transaction
Manager Communication.
d. Select No Authentication Required in Transaction Manager
Communication.
7 Restart the Logging Service.

Note: The Oracle client component used to connect to the database must be
32-bit (64-bit is not supported).

30 7 Troubleshooting
 Special Considerations for Windows Server
2008 R2 and Windows 7
If you are using Windows Server 2008 R2 or Windows 7, you will need to
allow Distributed Transaction Coordinator to communicate through windows
firewall, as shown below.

Oracle Error: Cannot load oramts.dll

Error: EIF logging server displays the error message Cannot load oramts.dll
even though oramts.dll is already installed.
Description: The error occurs because the ORAMTS.DLL originally shipped
with the Oracle 9i Release 2 was a debug version of the actual ORAMTS.DLL
component. The incorrect component has a dependency on msvcrtd.dll (a
debugging component included in Microsoft Visual C++) and will not function
correctly on any machine that does not have msvcrtd.dll installed.
Solution: Obtain and install Oracle 9i Patch 2428356, which contains the
correct version of ORAMTS.DLL. Customers with a valid Oracle support
contract can obtain this patch directly from Oracle.

7 Troubleshooting 31
32 7 Troubleshooting
8 Frequently Asked
Questions

This section discusses known issues and frequently asked questions.

Q. How do I administer my distributed business

processes?
When coordination is necessary, everything in the network can be
administered from any location in the network. The Aspen Enterprise
Integration Framework provides the Aspen Integration Designer with a
graphical user interface for administration. Using the Aspen Integration
Designer, an administrator can send configuration settings to any machine on
the network.

Q. How do I integrate my custom applications?

A. The Aspen Enterprise Integration Framework makes it easy for your
existing applications and your new application built with Service Oriented
Architecture in mind. AspenTech has simplified the complexity of point-to-
point distributed communication into topic based publish-subscribe and
request-response messaging.
You define the messages associated with a topic, and any number of
applications can subscribe to receive them as they are published. Or, if you
want, your application can choose to respond to a request from another
application using the request-response paradigm. In either situation, no
configuration or end-point addressing is required.

Q. How do you define a callback web service so you can

receive subscribed messages and requests messages from
Aspen EIF?
Your web service is registered via the Aspen Integration Designer. When you
open the Aspen Integration Designer, you can search for services on the
network. You will locate the Web Services Adapter you want to communicate
with, and inside the configuration for it, you can define your callback address.
Refer to the Aspen Integration Designer documentation for further
information about usability.

8 Frequently Asked Questions 33

 Q. Why does Aspen EIF not support certified
request/response?
Request/response is meant to be a real-time request to application. It is very
likely that a request made hours or even days before would no longer be
valid. If you are looking for disconnected communication, you may want to
reevaluate your problem and look at certified publish/subscribe as an
alternative.

Q. How is Aspen Integration Designer licensed?

The Aspen Integration Designer is licensed with the rest of the Aspen
Enterprise Integration Framework components.

Q. What is the array of WsTrackingPair in Web Service

Adapter used for?
The array of WsTrackingPair is used for adding additional header
information into the message. This allows information about the message to
be added without altering the message itself.

Q. What are the WsAttributes in Web Service Adapter

used for and what do they mean?
WsAttributes are used to describe a message coming off of the Enterprise
Integration Framework. It describes the message and the application it
was sent from. It contains:
o Message ID: The identifier generated when the message was sent to
uniquely identify the message.
o Publish Time: The publish time is the time the message was received
for sending on Aspen EIF in UTC format.
o Sender Address: The sender address represents where the message
originated on the physical machine.
o Source: This is the messaging source defined by the application. This
is application-context specific.
o Track: This is the message tracking information. This is the additional
header information about the message described by the application.

Q. Why does WsMessage in Web Service Adapter use

string as the payload of the message?
The string type is used to allow XML data to be transferred across web
services without the definition of an encoding for a set of bytes.

Q. What do I need to implement the callback contract

associated with the Web Service Adapter? Why cant I
write my own?
The callback WSDL contract is bound to the Web Service Adapter for calling
back applications. Implementing your own contract can lead to increased
development time, less reliability, and more configuration for the user.

34 8 Frequently Asked Questions

 Therefore, we selected the unified WSDL model for ease of development and
usability.
A Software Development Kit (SDK) is available with reference documentation,
example programs, and a Developers Guide to make the integration simple.

8 Frequently Asked Questions 35

36 8 Frequently Asked Questions
Appendix A - Configuring
Ports in Firewall for Windows
Server 2008

To configure ports in Firewall for Windows Server 2008:

1 Launch Windows Firewall by clicking Programs | Administrative Tools |
Windows Firewall with Advanced Security.
2 On the User Access Control dialog box, click Continue.
This screen may not appear, depending on the permissions you have
already set.

Appendix A - Configuring Ports in Firewall for Windows Server 2008 37

 The Firewall opens.

3 Scroll down to Getting Started View and create firewall rules.

38 Appendix A - Configuring Ports in Firewall for Windows Server 2008

 4 Click the Inbound Rules link.

Appendix A - Configuring Ports in Firewall for Windows Server 2008 39

 5 In the Actions pane on the right, click New Rule.
A new window appears.

6 Select the Port radio button, and then click Next.

40 Appendix A - Configuring Ports in Firewall for Windows Server 2008

 7 Type the port number and click Next.

8 Select the Allow the connection radio button and click Next.

Appendix A - Configuring Ports in Firewall for Windows Server 2008 41

 9 Select all rule options and click Next.

10 Type a name for the rule and click Finish.

42 Appendix A - Configuring Ports in Firewall for Windows Server 2008

 The new Inbound Port rule is now available in the Firewall.

11 In the left pane, click the Outbound Rules link.

Appendix A - Configuring Ports in Firewall for Windows Server 2008 43

 12 In the Actions pane on the right, click New Rule.
A new window appears.

13 Select the Port radio button, and then click Next.

44 Appendix A - Configuring Ports in Firewall for Windows Server 2008

 14 Type the port number and click Next.

15 Select the Allow the connection radio button and click Next.

Appendix A - Configuring Ports in Firewall for Windows Server 2008 45

 16 Select all rule options and click Next.

17 Type a name for this rule and click Finish.

46 Appendix A - Configuring Ports in Firewall for Windows Server 2008

 The new Outbound Port rule is now available in the Firewall.

Appendix A - Configuring Ports in Firewall for Windows Server 2008 47