Files to modify

Files to modify

Note: Only Single zone deployment is supported for on-premise deployment.
After building the Mashery Local images, copy the /var/jenkins_home/docker-deploy folder in the tml-installer container to the host. If your build and deployment host are the same, the following sample command will copy the tmgc-deploy folder from the container to the current working directory on the local machine. Sample command: 
docker cp tml-installer:/var/jenkins_home/docker-deploy .
Navigate to the /docker-deploy/onprem/swarm/ folder on the host. Update the reference manifest deployment manifest-onprem-swarm.json file for customizing your deployment. 
docker-deploy/onprem/swarm/manifest-onprem-swarm.json

Mashery Local Components Configuration

Navigate to the docker-deploy/onprem/swarm.json file and edit the cluster properties.

The following are the cluster level properties: 
"tml_cluster_name": "Tibco Mashery Gateway Reference Cluster",

"tml_cluster_mode": "untethered",

"tml_zones": ["local"],
Note: The valid values for tml_cluster_mode are:
  • tethered : In this mode, Mashery Local gets the configuration data from ML cloud. For this you need to have mom key and secret.
  • untethered : In this mode, you configure data through Mashery Local config manager.
Variable Prefix Description
tml_cm Mashery Local Cluster Manager Component
tml_tm Mashery Local Traffic Manager Component
tml_cache Mashery Local Cache Component
tml_sql Mashery Local SQL Component
tml_log Mashery Local Log Component
tml_nosql Number of Cassandra Component 
{
"tml_cluster_name": "Tibco Mashery Local Reference Cluster",
"tml_cluster_mode": "untethered",
"tml_zones": ["local"],

"tml_image_tag": "v5.2.0.1",
"tml_image_registry_host" : "<docker-registry-host>",
"tml_image_repo": "tml",
"tml_cm_count": 1,
"tml_tm_count": 1,
"tml_cache_count": 1,
"tml_sql_count": 1,
"tml_log_count": 1,
"tml_nosql_count": 1,

"tml_tm_http_enabled": "true",
"tml_tm_http_port": 80,
"tml_tm_https_enabled": "true",
"tml_tm_https_port": 443,
"tml_tm_oauth_enabled": "true",
"tml_tm_oauth_port": 8083,

"tml_api_http_enabled": "true",
"tml_api_http_port": 7080,
"tml_api_https_enabled": "true",
"tml_api_https_port": 7443,

"tml_cm_http_enabled": "true",
"tml_cm_http_port": 8080,
"tml_cm_https_enabled": "true",
"tml_cm_https_port": 8443,

"cassandra_max_heap": "512M",
"cassandra_replication_factor": 1
}

Setting up Mashery Service Configuration Data

Set tml_cluster_mode as untethered in docker-deploy/aws/k8s/manifest-single-zone.json file.

TIBCO Mashery Local offers the capability to sync data from an active MoM host at the time of cluster creation. To load the data using the MoM sync configuration, specify the following three properties in the tml_cluster_properties.json: 
"mom_key": "<MOM_API_KEY>",
"mom_secret": "<MOM_API_SECRET>",
The tmgc_sql_properties.json file is located in the docker-deploy/properties/ directory.
Note: Set tml_cluster_mode as tethered in docker-deploy/onprem/swarm/ /manifest-onprem-swarm.json file.

Generating Deployment Scripts and Configuration

For single-zone deployment, run the following command and find generated deployment scripts and configuration in the folder "manifest-onprem-swarm": 
./compose.sh manifest-aws-swarm.json