How to configure the Monitoring and Management (MM) Console to deploy multiple APIX applications.
Article ID: KB0094322
Updated On:
| Products | Versions |
|---|---|
| TIBCO API Exchange | - |
| Not Applicable | - |
Description
Resolution:
To use the ASG MM to deploy multiple projects, say CoreEngine and CentralLogger, here are the changes needed.
1). Change the Cluster name in the cdd file (asg_cl.cdd). The cluster name must be unique for each application configured.
===================
</revision>
<name>ASGCL</name>
<message-encoding>UTF-8</message-encoding>
===================
2). For this new cluster (ASGCL), create a new site topology file (asg_cl.st). Refer the default asg_default.st file as a template and modify the necessary fields needed for new project cluster deployment and create a site topology (asg_cl.st) file.
3). Place the multiple site topology files in the $BE_HOME\mm\config directory mainly for deployments of one or more cluster (asg_default.st and asg_cl.st). Make sure both .st files have the same site name (name="ASG_SITE") in Site Topology and the cluster name must be unique for each cluster configured.
4). Remove the property "be.mm.topology.file" in the MM.cdd file or set its value to “” (the empty string). When the MM engine starts, it will load the multiple site topology files from $BE_HOME\mm\config folder rather than using the single asg_default.st file by this property be.mm.topology.file.
5). Start the MM engine and both CoreEngine and CentralLogger will be displayed in the MM UI. They will ready to be deployed and started.
To use the ASG MM to deploy multiple projects, say CoreEngine and CentralLogger, here are the changes needed.
1). Change the Cluster name in the cdd file (asg_cl.cdd). The cluster name must be unique for each application configured.
===================
</revision>
<name>ASGCL</name>
<message-encoding>UTF-8</message-encoding>
===================
2). For this new cluster (ASGCL), create a new site topology file (asg_cl.st). Refer the default asg_default.st file as a template and modify the necessary fields needed for new project cluster deployment and create a site topology (asg_cl.st) file.
3). Place the multiple site topology files in the $BE_HOME\mm\config directory mainly for deployments of one or more cluster (asg_default.st and asg_cl.st). Make sure both .st files have the same site name (name="ASG_SITE") in Site Topology and the cluster name must be unique for each cluster configured.
4). Remove the property "be.mm.topology.file" in the MM.cdd file or set its value to “” (the empty string). When the MM engine starts, it will load the multiple site topology files from $BE_HOME\mm\config folder rather than using the single asg_default.st file by this property be.mm.topology.file.
5). Start the MM engine and both CoreEngine and CentralLogger will be displayed in the MM UI. They will ready to be deployed and started.
Issue/Introduction
How to configure the Monitoring and Management (MM) Console to deploy multiple APIX applications.
Environment
Product: TIBCO API Exchange
Version:2.x
OS: All Supported Operating Systems
--------------------
Feedback
Yes
No
Powered by
