Error Deploying Environment in clustered Environment

Hi Everyone,

I m Facing issue while deploying Environment in Clustered Environment

Steps Followed

Node 1

  1. Install Optimize components on node 1
  2. Assign the Cluster Address to node 1
  3. Start the Optimize Components on node 1
  4. Deploy Environment on node 1
  5. Deployment was successful on node 1 an AE came up without any issues.
  6. Shut optimize components
  7. Remove Clustered address assigned node 1

Node 2

  1. Assign the Cluster Address to node 2
  2. Install Optimize components on node 2
  3. Start the Optimize Components on node 2
  4. Deploy Environment on node 2
  5. Deployment FAILED with below error.

Please Advice on how to fix this issue.

Error deploying logical server type “Analytic Engine v9.10.0.0” version “9.10.0.0” to host “ptb2b5ofiae.ikeadt.com
Deployment Error: java.rmi.ConnectException: url = http://ptseelm-lx4673.ikeadt.com:15000/services/IRemoteConfiguration
One or more of the following configurations could not be deployed

System Identity
System Endpoint Registry
Membership management
JDBC alias configuration type “Analytic Repository” version “7.0.0.0”
JDBC alias configuration type “Common Directory Repository” version “7.1.0.0”
JDBC alias configuration type “Process History Repository” version “7.0.0.0”
JDBC alias configuration type “Process Model Repository” version “7.0.0.0”
JDBC alias configuration type “Process Work Repository” version “7.0.0.0”
JDBC pool configuration “OPT_JDBC_POOL”
JDBC pool configuration “MWS_JDBC_POOL”
Configuration type “Data Maintenance Settings” version “7.1.0.0”
Configuration type “Event Publication Settings” version “9.8.0.0”
Configuration type “Mail Settings” version “7.0.0.0”
Configuration type “Monitor Behavior Settings” version “7.1.0.0”
Configuration type “Process Tracker Test Settings” version “7.0.0.0”
Configuration type “Station Settings” version “7.0.0.0”
Configuration type “Service Discovery Settings” version “7.0.0.0”
Configuration type “WSAction Settings” version “7.0.0.2”
Configuration type “Process Tracker Settings” version “9.10.0.0”
Configuration type “SNMPAlert Settings” version “7.0.0.2”
Configuration type “JMSEventAction Settings” version “8.0.0.0”
Configuration type “Terracotta Server Array Configuration” version “9.0.0.0”
Configuration type “Lock Configuration” version “7.0.0.0”
Configuration type “Journal Logging” version “7.0.0.0”
Configuration type “JNDI Configuration” version “9.6.0.0”
Configuration type “Analysis Engine Settings” version “9.8.0.0”
Configuration type “Database Settings” version “7.1.0.0”

Deployed logical server “Infrastructure Data Collector v9.10.0.0” version “9.10.0.0” to host “ptb2b5ofiae.ikeadt.com
System Identity
System Endpoint Registry
Membership management
Configuration type “UM Cluster Resource Module Settings” version “9.10.0.0”
Configuration type “MashZone NextGen Resource Module Settings” version “9.10.0.0”
Configuration type “Collector Settings” version “9.10.0.0”
Configuration type “Broker Resource Module Settings” version “8.0.0.0”
Configuration type “Adabas SOA Gateway Resource Module Settings” version “8.2.1.0”
Configuration type “IS Resource Module Settings” version “9.5.0.0”
Configuration type “Com-plete Resource Module Settings” version “8.2.1.0”
Configuration type “EntireX Resource Module Settings” version “8.2.1.0”
Configuration type “ETS Resource Module Settings” version “8.2.1.0”
Configuration type “MWS Resource Module Settings” version “9.0.0.0”
Configuration type “Presto Resource Module Settings” version “9.8.0.0”
Configuration type “UM Resource Module Settings” version “9.5.0.0”
Configuration type “TC Resource Module Settings” version “9.7.0.0”
Configuration type “Apama Resource Module Settings” version “9.9.0.0”
Configuration type “JNDI Configuration” version “9.6.0.0”

Deployment of environment “B2B_OPT_ENV_PTE-TST” FAILED due to errors. Note that one or more logical servers may have been successfully deployed. The most common deployment failure is that the component was not started on the host specified in the logical to physical server mapping or was unreachable during deployment.

Hi Krishnendu,

can you describe your pattern in detail please?

Please have a look at the “Configure BAM” Guide, section about clustering.

Regards,
Holger

Its working now :slight_smile:
Issue was with Cluster Address acquiring on the server.