Skip to content

sag-um-cluster template is not quite working correctly #320

@kfam-marcink

Description

@kfam-marcink

Hi, I have uploaded modified 3nodes cluster to Command Central and started the layer creation. The template installed the UM products and created the instances but didn't create the cluster.
There are also some issues with the instances created, since all of them had the same name. Though that it's impossible to open the realms in the Enterprise Manager nor to create a cluster.
The template I used you can find below:

###############################################################################
#  Copyright 2013 - 2018 Software AG, Darmstadt, Germany and/or its licensors
#
#   SPDX-License-Identifier: Apache-2.0
#
#     Licensed under the Apache License, Version 2.0 (the "License");
#     you may not use this file except in compliance with the License.
#     You may obtain a copy of the License at
#
#        http://www.apache.org/licenses/LICENSE-2.0
#
#     Unless required by applicable law or agreed to in writing, software
#     distributed under the License is distributed on an "AS IS" BASIS,
#     WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#     See the License for the specific language governing permissions and
#     limitations under the License.                                                            
#
###############################################################################

alias: sag-um-cluster
description: Universal Messaging realm server

environments:
  default:
    nodes:               ${}
    um.numrealmserver.license.key: "*_NUMWF_10.*_*_*" # UM license key
    um.instance.name:    tstUMCluster1015            # server instance name
    um.cluster:          cluster
    um.instance.port:    9000               # main listener port number
    um.jmx.port:         9999               # jmx port number
    um.memory.init:      128                 # initial memory size in MB
    um.memory.max:       512                # maximum memory size in MB
    um.memory.direct:    1G                 # direct memory size
    um.fixes:            ALL                # minimal recommended set of fixes to apply

layers: 
  runtime:
    productRepo: ${repo.product}
    fixRepo:     ${repo.fix}
    templates:
     # - um-server
      - um-cluster-${runtime.nodes.count}

templates:
   um-cluster-3:
    description: Cluster configuration for 3 node cluster
    products:
      NUMRealmServer:
        ${um.instance.name}:
          runtimeComponentId: Universal-Messaging-${instance.name} 
          configuration:
            Universal-Messaging-${instance.name}:
              COMMON-CLUSTER:                       
                COMMON-CLUSTER:  
                  Name: ${um.cluster}
                  Servers:                                      
                    Server:
                      - "@name": ${runtime.nodes[1]}
                        URL: "nsp://${runtime.hosts[1]}:${um.instance.port}"
                      - "@name": ${runtime.nodes[2]}
                        URL: "nsp://${runtime.hosts[2]}:${um.instance.port}"
                      - "@name": ${runtime.nodes[3]}
                        URL: "nsp://${runtime.hosts[3]}:${um.instance.port}"

provision:
  default:
    runtime: ${nodes}

I expect the script should create three nodes ie like in this example tstum-1, tstum-2, tst-um3 and a cluster with tstum-1, tstum-2, tstum-3 nodes in it, which for now it doesn't do.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions