Release Notes

Back Next

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:

In the ActiveVOS

install.properties

file set

install.web.application

false

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

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

Deploy the ActiveVOS EAR files. For information about deploying EAR files, see the

Informatica MDM Multidomain Edition Installation Guide

(MDM-13269)

Installation and Upgrade

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Release Notes

Release Notes

ActiveVOS Installation in WebSphere Cluster Environments