Add Servers to Runtime Manager
To add a Mule server to the Runtime Manager console so that you can manage it, you must first register it with the Runtime Manager agent. Use the
amc_setup script to configure the Runtime Manager agent to communicate with Runtime Manager.
Your enterprise license is current.
You are running Mule 3.6.0 or later, and API gateway 2.1 or later.
For Mule 3.6.x, install the Runtime Manager agent.
For Mule 3.7.x and later Mule 3.x versions, you can optionally update the Runtime Manager agent to the latest version to take advantage of all bug fixes and new features.
For information, see Install or Update the Runtime Manager Agent.
If you must download the agent, you have an Enterprise support account.
If the server is already registered with another Runtime Manager instance, remove that registration first.
To add a Mule server to Runtime Manager:
From Anypoint Platform, select Runtime Manager.
Click Servers in the left menu.
Click the Add Server button.
Enter a name for your server.
Server names can contain up to 60 alphanumeric characters (a-z, A-Z, 0-9), periods (.), hyphens (-), and underscores (_), but not spaces or other special characters. Runtime Manager supports Unicode characters in server names.
The server name must be unique in the environment, but it can be the same for the same organization in different environments.
Runtime Manager generates the
amc_setupcommand. This command includes the server name you specified (
server-name) and the registration token (
token) required to register Mule in your environment. The registration token includes your organization ID and the current environment.Figure 1. The arrow shows the
amc_setupcommand in the Add Server window.
Click Copy command to copy the
This button appears only if the server name you specify is valid.
In a terminal window, change to the
$MULE_HOME/bindirectory for the Mule instance that you’re registering.
Paste the command on the command line.
Include any other parameters on the
For information, see amc_setup Parameters.
If your environment requires all outbound calls to go through a proxy, specify proxy settings in either the
$MULE_HOME/conf/mule-agent.ymlfile or the
If you are using the IBM JVM, see IBM JVM.
amc_setup command completes successfully, you see:
Mule Agent configured successfully Connecting to Access Management to extract client_id and client_secret Credentials extracted correctly, updating wrapper conf file
After the script completes successfully, the name of your server appears on the Servers tab of Runtime Manager with a status of
If the server was running when you ran the
amc_setup script, restart the server to reconnect with Runtime Manager.
When creating a server using the IBM Java Virtual Machine (JVM), you must use a different truststore file than the default truststore installed by the Runtime Manager agent.
Download the custom truststore from this knowledgebase article:
Depending on your Mule version, rename the
$MULE_HOME/confto one of these file names:
Mule 4.1.3 (Agent 2.1.4) and later
Mule 4.1.2 (Agent 2.1.3)
Copy the custom truststore into the
If the server you want to add is already registered with a different instance of Runtime Manager, you must remove it before you can register.
To remove the server from Runtime Manager:
In Runtime Manager, delete the server from the Server tab.
$MULE_HOME/confdirectory, delete the