Table of Contents

Search

  1. Abstract
  2. Introduction
  3. Installation and Upgrade
  4. 10.3 HotFix 3
  5. 10.3 HotFix 2
  6. 10.3 HotFix 1
  7. 10.3

ActiveVOS Installation in WebSphere Cluster Environments

ActiveVOS Installation in WebSphere Cluster Environments

When you install embedded ActiveVOS in a WebSphere cluster environment, you cannot connect to the MDM identity service provider in the ActiveVOS Console.
Workaround: Perform the following steps after you install the Hub Server, embedded ActiveVOS, and the Process Server:
  1. In the ActiveVOS
    install.properties
    file set
    install.web.application
    to
    false
    .
  2. In the
    deployer.xml
    file in the ActiveVOS installation directory, comment out the following code:
    <!-- <target name="deploy.resources" depends="deploy.timer.manager,deploy.work.manager"/> <target name="deploy.timer.manager"> <echo message="$ {basedir}"/> <run.wsadmin script="${basedir} /scripts/timermanager.jacl"/> </target> <target name="deploy.work.manager"> <run.wsadmin script="$ {basedir}/scripts/workmanager.jacl"/> <run.wsadmin script="${basedir} /scripts/systemworkmanager.jacl"/> </target> <target name="deploy.jaas"> <run.wsadmin script="$ {basedir}/scripts/jaaslogin.jacl"/> </target> <target name="deploy.apps"> <run.wsadmin script="${basedir} /scripts/installapp.jacl"/> </target> -->
  3. In the
    <MDM installation directory>/hub/server/bin
    directory, run the following commands:
    sip_ant.bat deploy_mdm_identity_resolution sip_ant.bat deploy_avos_server
  4. Deploy the ActiveVOS EAR files. For information about deploying EAR files, see the
    Multidomain MDM Installation Guide
    .
(MDM-13269)

0 COMMENTS

We’d like to hear from you!