Changing Mashery Local Mom Key for the same area

Products	Versions
TIBCO Cloud API Management - Local Edition	-

Description

This article explains the steps to change/update the MOM Key of an existing cluster with a newly created Mom Key created for the same area.
Please note that the MOM Keys should be created for the same area.

Example use case: You have a trial Mom key for an Area A and you decided to get a new Prod Mom Key for the same Area A and instead of creating a new cluster and do the setup, you can update the existing cluster with the newly created Prod Mom Key.

Issue/Introduction

Changing Mashery Local Mom Key with a new key for the same area

Resolution

Steps to follow for Mashery Local OVA
1. Login as root
2. Stop Javaproxy using command “sudo monit stop proxy"
3. Open the proxy configuration file
vi /etc/mashery-proxy-config.json
4. Under the “com.mashery.proxy.onpremloader” section update the value of "apiKey": “<old Mom key>” to <new Mom key>
5. Under the “com.mashery.proxy.onpremloader” section update the value of "apiSecret": “<old Mom secret>” to <new Mom Secret>

Sample format of com.mashery.proxy.onpremloader
    "com.mashery.proxy.onpremloader": {
        "packagesEndpoint": "https://api-mom.mashery.com/mom/packages",
        "tokensLastModifiedShift": 5000,
        "apiKey": “xxxxxxx",
        "packageKeysEndpoint": "https://api-mom.mashery.com/mom/packagekeys",
        "devclassesEndpoint": "https://api-mom.mashery.com/mom/devclasses",
        "servicesEndpoint": "https://api-mom.mashery.com/mom/services",
        "tokensLastPushedShift": 5000,
        "apiSecret": “xxxxxx",
        "developersEndpoint": "https://api-mom.mashery.com/mom/developers",
        "tokensEndpoint": "https://api-mom.mashery.com/mom/tokens",
        "httpsClientSecurityEndpoint": "https://api-mom.mashery.com/mom/httpsclientsecurity",
        "updatesEndpoint": "https://api-mom.mashery.com/mom/p2",
        "momReadTimeout": 120000,
        "momConnectTimeout": 30000,
        "maxUploadLogSizeMB": 10,
        "logsEndpoint": "https://api-mom.mashery.com/mom/logs",
        "appsEndpoint": "https://api-mom.mashery.com/mom/apps"
    }
6. Validate that the Json formatting is intact
7. Start Javaproxy using "sudo monit start proxy"
8. Verify that the syncs are functioning

Steps to follow for Mashery Local Docker
1. Login as root
2. Stop Javaproxy using command “service stop Javaproxy"
3. Open the proxy configuration file
vi /etc/mashery-proxy-config.json
4. Under the “com.mashery.proxy.onpremloader” section update the value of "apiKey": “<old Mom key>” to <new Mom key>
5. Under the “com.mashery.proxy.onpremloader” section update the value of "apiSecret": “<old Mom secret>” to <new Mom Secret>

Sample format of com.mashery.proxy.onpremloader
    "com.mashery.proxy.onpremloader": {
        "packagesEndpoint": "https://api-mom.mashery.com/mom/packages",
        "tokensLastModifiedShift": 5000,
        "apiKey": “xxxxxxx",
        "packageKeysEndpoint": "https://api-mom.mashery.com/mom/packagekeys",
        "devclassesEndpoint": "https://api-mom.mashery.com/mom/devclasses",
        "servicesEndpoint": "https://api-mom.mashery.com/mom/services",
        "tokensLastPushedShift": 5000,
        "apiSecret": “xxxxxx",
        "developersEndpoint": "https://api-mom.mashery.com/mom/developers",
        "tokensEndpoint": "https://api-mom.mashery.com/mom/tokens",
        "httpsClientSecurityEndpoint": "https://api-mom.mashery.com/mom/httpsclientsecurity",
        "updatesEndpoint": "https://api-mom.mashery.com/mom/p2",
        "momReadTimeout": 120000,
        "momConnectTimeout": 30000,
        "maxUploadLogSizeMB": 10,
        "logsEndpoint": "https://api-mom.mashery.com/mom/logs",
        "appsEndpoint": "https://api-mom.mashery.com/mom/apps"
    }
6. Validate that the Json formatting is intact
7. Start Javaproxy using "service start Javaproxy"
8. Verify that the syncs are functioning

Welcome to "KB Articles"