Oracle用バージョン9.0.1または9.1.0からのアップグレード

10.2 HotFix 1

前へ次へ

Prepare the BPM Upgrade

Perform the following tasks to prepare for the BPM upgrade:

Choose a workflow adapter

Review the following upgrade options for workflow adapters, and choose the upgrade option that suits your needs:

Current Workflow Adapter	Upgrade Options
SIPERIAN	Deprecated. Option 1 Keep SIPERIAN as the primary workflow adapter. Option 2 Upgrade to the BE ActiveVOS workflow adapter based on business entities. You must have a business entity configuration to use the BE ActiveVOS workflow adapter. For more information, see Migrating IDD Applications to the Business Entity Data Model .
Informatica ActiveVOS	This workflow adapter is based on subject areas and operates using SIF APIs. Option 1 Keep Informatica ActiveVOS as the primary workflow adapter. Option 2 Upgrade to the BE ActiveVOS workflow adapter based on business entities. You must have a business entity configuration to use the BE ActiveVOS workflow adapter. For more information, see Migrating IDD Applications to the Business Entity Data Model .
BE ActiveVOS	This workflow adapter is based on business entities and operates using business entity services. You must use the version of ActiveVOS that is defined in the Product Availability Matrix. If an older version is detected in your environment, the upgrade process installs the required version of ActiveVOS.

Configure the Java Environment Variable for ActiveVOS

If you use ActiveVOS, perform the following task to configure the Java environment variable:

Upgrade Task	Details
Configure INSTALL4J_JAVA_HOME_OVERRIDE	ActiveVOS requires JDK 1.7, whereas MDM Multidomain Edition requires JDK 1.8. Configure INSTALL4J_JAVA_HOME_OVERRIDE to ensure that JDK 1.7 is used during ActiveVOS installation. For example, set INSTALL4J_JAVA_HOME_OVERRIDE to the following path: INSTALL4J_JAVA_HOME_OVERRIDE=/root/jdk1.7.0_53/jre If you do not configure this environment variable, ActiveVOS is not installed. You are not notified if ActiveVOS is not installed.

Upgrade Task

Details

Configure INSTALL4J_JAVA_HOME_OVERRIDE

ActiveVOS requires JDK 1.7, whereas MDM Multidomain Edition requires JDK 1.8. Configure INSTALL4J_JAVA_HOME_OVERRIDE to ensure that JDK 1.7 is used during ActiveVOS installation.

For example, set

INSTALL4J_JAVA_HOME_OVERRIDE

to the following path:

INSTALL4J_JAVA_HOME_OVERRIDE=/root/jdk1.7.0_53/jre

If you do not configure this environment variable, ActiveVOS is not installed. You are not notified if ActiveVOS is not installed.

Prepare to move from standalone ActiveVOS to embedded ActiveVOS (In-place Upgrade)

If you are upgrading existing machines and want to move from standalone ActiveVOS to embedded ActiveVOS, perform the following upgrade tasks:

Upgrade Task	Description
Remove the ActiveVOS data sources	If the standalone ActiveVOS server is in the same JBoss instance, WebSphere profile, or WebLogic domain as MDM Multidomain Edition, remove the data source for ActiveVOS from the application server.
Edit the URN mapping in a WebSphere environment	Launch the ActiveVOS Console. In a browser, type the following URL, substituting the correct host name and port number: Secure connections. https://<host>:<port>/activevos Non-secure connections. http://<host>:<port>/activevos In the ActiveVOS Console, on the Home page, click Administration Configure Server URN Mappings . Ensure that URN java:comp/env/jdbc/ActiveVOS maps to URL java:comp/env/jdbc/ActiveVOS .

Upgrade Task

Description

Remove the ActiveVOS data sources

If the standalone ActiveVOS server is in the same JBoss instance, WebSphere profile, or WebLogic domain as MDM Multidomain Edition, remove the data source for ActiveVOS from the application server.

Edit the URN mapping in a WebSphere environment

Launch the ActiveVOS Console. In a browser, type the following URL, substituting the correct host name and port number:

Secure connections.

https://<host>:<port>/activevos

Non-secure connections.

http://<host>:<port>/activevos

In the ActiveVOS Console, on the Home page, click

Administration

Configure Server

URN Mappings

Ensure that URN

java:comp/env/jdbc/ActiveVOS

maps to URL

java:comp/env/jdbc/ActiveVOS

Edit the build.properties file (In-place Upgrade)

If you use ActiveVOS, perform the following tasks to edit the build.properties file:

Upgrade Task	Details
Configure the database connection properties for IBM DB2	IBM DB2環境では、アップグレード前に、ActiveVOSデータベース接続プロパティを < MDM Hub installation directory: MDM Hubのインストールディレクトリ >/hub/server/bin の build.properties ファイルに追加します。次のサンプルは、サンプルエントリが含まれるActiveVOSデータベース接続プロパティを示しています。 activevos.db.type=db2 activevos.db.server=localhost activevos.db.port=50000 activevos.db.user=AVOS activevos.db.dbname=INFA102 activevos.db.schemaname=AVOS activevos.db.jdbc.url=jdbc:db2://localhost:50000/INFA102 activevos.b4p.url=http://localhost:9080/active-bpel/services/AeB4PTaskClient-taskOperations
Configure the ActiveVOS installation directory	If the upgrade process detects that the installed version of ActiveVOS does not meet the system requirements, the upgrade process installs the required version of ActiveVOS in a new directory. To install ActiveVOS in the same directory as a previous installation, delete or comment out the following entry in the build.properties file: activevoslinstall.dir=<ActiveVOS installation directory>

Upgrade Task

Details

Configure the database connection properties for IBM DB2

IBM DB2環境では、アップグレード前に、ActiveVOSデータベース接続プロパティを

MDM Hub installation directory: MDM Hubのインストールディレクトリ

>/hub/server/bin

の

build.properties

ファイルに追加します。

次のサンプルは、サンプルエントリが含まれるActiveVOSデータベース接続プロパティを示しています。

activevos.db.type=db2
activevos.db.server=localhost
activevos.db.port=50000
activevos.db.user=AVOS
activevos.db.dbname=INFA102
activevos.db.schemaname=AVOS
activevos.db.jdbc.url=jdbc:db2://localhost:50000/INFA102
activevos.b4p.url=http://localhost:9080/active-bpel/services/AeB4PTaskClient-taskOperations

Configure the ActiveVOS installation directory

If the upgrade process detects that the installed version of ActiveVOS does not meet the system requirements, the upgrade process installs the required version of ActiveVOS in a new directory.

To install ActiveVOS in the same directory as a previous installation, delete or comment out the following entry in the build.properties file:

activevoslinstall.dir=<ActiveVOS installation directory>

アップグレード前のタスク

ガイドをダウンロード

ページをウォッチ

フィードバックを送信

コミュニティ

Knowledge Base

Success Portal

Rename Saved Search

目次

Oracle用バージョン9.0.1または9.1.0からの アップグレード

Oracle用バージョン9.0.1または9.1.0からの アップグレード

Prepare the BPM Upgrade

Prepare the BPM Upgrade

Choose a workflow adapter

Configure the Java Environment Variable for ActiveVOS

Prepare to move from standalone ActiveVOS to embedded ActiveVOS (In-place Upgrade)

Edit the build.properties file (In-place Upgrade)

Oracle用バージョン9.0.1または9.1.0からのアップグレード

Oracle用バージョン9.0.1または9.1.0からのアップグレード