Question
Raytheon Company
US
Last activity: 6 Dec 2019 14:40 EST
Version 8.3 upgrade issue ; tomcat and Oracle
Migrating from 7.4 to 8.3
I performed the migrate.sh step successfully to the new schema RULES_NEW. started the upgrades.sh step. Towards the end of the step the upgrade starts a temporary tomcat instance.
That step seems to be grabbing the wrong network interface card ( we have three network interfaces in the system ). Is there a way of preventing the upgrade from grabbing one of the interfaces ?
Disable that particular interface for the duration of the upgrade ?
***Edited by Moderator: Lochan to update platform capability tags***
Pegasystems Inc.
IN
Hi David,
You can force Hazelcast to use one NIC over another by specifying "cluster/hazelcast/interface" setting in the prconfig.xml file. Here's an example :
<env name="cluster/hazelcast/interface" value="xxx.xx.xx.xx" />
Hi David,
You can force Hazelcast to use one NIC over another by specifying "cluster/hazelcast/interface" setting in the prconfig.xml file. Here's an example :
<env name="cluster/hazelcast/interface" value="xxx.xx.xx.xx" />
Thanks,
Abhinav
Raytheon Company
US
Thanks; but it's part of the upgrade.sh script that upgrades the schema created by the migrate.sh script. Part of that upgrade starts a temporary tomcat instance. Believe it's using ANT. Don't know how it grabs it's network interface and if that's somewhere define in the upgrade83/scripts