Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3 HotFix 2
  • All Products

Table of Contents

Search

  1. Preface
  2. MDM and Embedded ActiveVOS
  3. Configuring Workflow Tasks and Triggers
  4. Running the Migration Script
  5. Frequently Asked Questions

ActiveVOS® Setup Guide

ActiveVOS® Setup Guide

Back Next

Running the Migration Script

Running the Migration Script

To work with ActiveVOS tasks that were created before
Multidomain MDM
 version 10.1, run the migration script to populate the tasks with the required presentation parameters. If you do not run the migration script, you cannot see the tasks in the Task Manager. Routinely run the script until all the tasks are complete.
To run the script, you can use a properties file. If you do not want to store passwords in a properties file, you can run the script with the properties in the command.
  1. Create an MDM Hub user that belongs to all roles involved in task management. The out-of-the-box roles are DataSteward, Manager, and SrManager.
    The ActiveVOS migration utility requires that you create a user that belongs to all task management roles.
    After the migration, the tasks are assigned to the same users that the tasks were assigned to before the upgrade.
    You can run the script with the properties in a file or with the properties on the command line.
  2. To run the script with a properties file, perform the following steps.
    1. Open the following file in a text editor:
      <
      MDM Hub installation directory
      >\hub\server\bin\build.properties
    2. Add the following properties to the
      build.properties
       file.
      Property
      Description
      avos.jdbc.database.driver.jar
      Path to the JAR file that contains the JDBC driver for ActiveVOS database.
      This parameter is populated during the Hub Server installation without the avos prefix in <infamdm installation directory>\conf\avos.install.properties.
      avos.jdbc.database.driver.class
      JDBC driver class for ActiveVOS database.
      This parameter is populated during the Hub Server installation without the avos prefix in <infamdm installation directory>\conf\avos.install.properties.
      avos.jdbc.database.url
      ActiveVOS database connection URL.
      This parameter is populated during the Hub Server installation without the avos prefix in <infamdm installation directory>\conf\avos.install.properties.
      avos.jdbc.database.username
      ActiveVOS database user name.
      This parameter is populated during the Hub Server installation without the avos prefix in <infamdm installation directory>\conf\avos.install.properties.
      avos.jdbc.database.password
      ActiveVOS database password.
      avos.ws.protocol
      The protocol for the ActiveVOS server connection. Can be http or https.
      avos.ws.host
      Host name of the application server where ActiveVOS runs.
      avos.ws.port
      Port number of the application server connection.
      avos.ws.trusted.username
      User name of the trusted user.
      The trusted user is created as part of the
      Multidomain MDM
       installation and upgrade process.
      avos.ws.trusted.password
      Password for the trusted user.
      The trusted user is created as part of the
      Multidomain MDM
       installation and upgrade process.
      avos.hub.username
      MDM Hub user that belongs to all roles involved in task management. The out-of-the-box roles are DataSteward, Manager, and SrManager.
      avos.ws.pagesize
      Number of tasks processed in one database transaction and batch-loaded from ActiveVOS.
      avos.ws.statuses
      Optional. Comma-separated list of ActiveVOS task statuses to be processed. For example, READY or IN_PROGRESS. By default all tasks are processed.
    3. Open a command prompt.
    4. Navigate to the following directory:
      <
      MDM Hub installation directory
      >/hub/server/bin
    5. Run the
      MDM Hub Master Database
       upgrade script with the following command:
      • On UNIX.
        sip_ant.sh migrate-avos-sa-tasks
      • On Windows.
        sip_ant.bat migrate-avos-sa-tasks
  3. To run the script with the properties on the command line, perform the following steps.
    1. Open a command prompt.
    2. Navigate to the following directory:
      <
      MDM Hub installation directory
      >/hub/server/bin
    3. Run the
      MDM Hub Master Database
       upgrade script with the properties in the command. For example, you can run the following command:
      • On UNIX. 
        sip_ant.sh migrate-avos-sa-tasks -Davos.jdbc.database.password=!!cmx!!
-Davos.ws.protocol=http -Davos.ws.host=localhost -Davos.ws.port=8080 -Davos.ws.pagesize=100
-Davos.ws.trusted.username=avos -Davos.ws.trusted.password=avos -Davos.hub.username=admin
      • On Windows. 
        sip_ant.bat migrate-avos-sa-tasks -Davos.jdbc.database.password=!!cmx!!
-Davos.ws.protocol=http -Davos.ws.host=localhost -Davos.ws.port=8080 -Davos.ws.pagesize=100
-Davos.ws.trusted.username=avos -Davos.ws.trusted.password=avos -Davos.hub.username=admin
  4. Run the script on a regular schedule.
  5. After all the tasks for the subject area workflow adapter are processed, you do not need to run the script and you can delete the user.
0 COMMENTS
We’d like to hear from you!