Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Prepare the BPM Upgrade

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 the
Multidomain MDM Data Director Migration Guide
.
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.

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
Multidomain MDM
, remove the data source for ActiveVOS from the application server.
Edit the URN mapping in a WebSphere environment
  1. 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
  2. In the ActiveVOS Console, on the Home page, click
    Administration
    Configure Server
    URN Mappings
    .
  3. 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
In IBM DB2 environments, before you upgrade, add the ActiveVOS database connection properties to the
build.properties
file in
<
MDM Hub installation directory
>/hub/server/bin
.
The following sample shows the ActiveVOS database connection properties with sample entries:
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>

0 COMMENTS

We’d like to hear from you!