I have a stand alone Mule Community Edition instance running an app, which I'd like to view in the Mule Management Console.
I've downloaded the MMC Trial and successfully connected to the trial's Enterprise Mule instance. When trying to add a new server on MMC, connecting to my Community Edition instance, it displays an error with Connection Refused.
Some Googling shows that it I should start the MMC Agent on that server.
How can I do that?
To be able to connect to MMC, you need a agent running along your esb server, which is the one that sends data to MMC and receives commands such as stop/restart/etc.
ESB EE runtime comes in 2 flavors: with or without the MMC agent included. In the case is not included, you can add it later as an addon. But you can't add it to a Community Edition (CE).
You need the EE version, that is why the mmc trial version comes with the ee runtime trial version.
So, in the case you want to test your application running along with the MMC, you have to deploy it in the Mule EE instance (you can deploy the application from MMC).
In the first place I am not sure if Mule MMC agent working with Community Edition. As per MuleSoft MMC is an enterprise only feature.
For running an MMC Agent.
First download an MMC agent from MuleSoft (Mule Enterprise Trail will provide you with MMC and MMC Agent)
Then copy the MMC agnet zip file to Mule standalone server apps folder.
Then start Mule standalon server.
Mule starts and shows that MMC agent is deployed and running.
Then your MMC should be able to detect the server instance.
Refer to the following link for more details on MMC
http://www.mulesoft.org/documentation/display/current/Installing+the+Trial+Version+of+MMC
Hope this helps.
Related
I just finished the deployment of a mule entreprise standalone server on a VM, added the server to the Runtime Manager, then proceeded to add the mule applications into the server.
The problem i'm having is that the version of the app doesn't appear on runtime manager.
You can see here what the problem actually is, the app deployed on Cloudhub shows it's runtime version but the one deployed on the server doesn't .
Is this a known problem, does it have a fix or not ?
I'm trying to install IBM Mobilefirst 7.0 server on production Ubuntu server in Amazon. The server has no GUI. I installed Websphere Application Server and IBM Mobilefirst server using silent installation of IBM Installation Manager and response file created on server with GUI. But now I'm stuck at a point where I have to configure MobileFirst server using server configuration tool. But I'm not able to find out how to do this without GUI since server configuration tool is GUI based. Any pointers or help would be highly appreciated!
You can use ant tasks to proceed with the configuration without the GUI.
Detailed steps for this can be found in the link below.
http://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.deploy.doc/devref/t_transporting_apps_and_adapters.html
What I was asking for is way to implement MobileFirst Server administration without using GUI as given in step number 6 in this link: http://www-01.ibm.com/support/knowledgecenter/#!/SSHSCD_6.3.0/com.ibm.worklight.installconfig.doc/install_config/t_ov_server_install.html. Since the server I was working on does not have a GUI, I was stuck at step 6. But I found the way out now and for someone who is looking for this, the way to do is using ant scripts. Steps are listed at this link : http://www-01.ibm.com/support/knowledgecenter/#!/SSHS8R_7.0.0/com.ibm.worklight.installconfig.doc/devref/t_ant_tasks_configure_dbs_wlconsole.html
I am updating Mule ESB, MMC to 3.5.2 from 3.3.2
I could access Server, flow information of apps deployed in mule esb except Agent App using MMC Rest API http://www.mulesoft.org/documentation/display/current/REST+API+Reference (e.g. /mmc/api/servers and /mmc/api/servers/local$70951c37-4d9a-4eb8-96f6-b358433a85a6/flows).
In this API I could access all the apps deployed in mule ESB except MMC Agent App.What configuration I need to deploy mmc agent as mule app. I have downloaded mule esb enterprise version in which mule mmc and Agent comes. so its not license issue.
What are detailed steps to migrate to Mule ESB, MMC 3.5.2?
PFA.
MMC 3.5.x agent is not a Mule application anymore, it's bundled with Mule ESB EE, so you won't find it when listing applications.
Hello Folks,
We are recently working on IBM worklight and what we want to try is:
We have two machine, one we want to set as server and other one is for my developer to build the app.
Currently we have installed Apache Tomcat server on the machine which we want to make as server. We even have IBM Worklight installed on it. Now What I want to achieve is to deploy the app from other machine to this server. But I am not able to set up the things properly.
Things done so far:
Installed Apache Tomcat server software on a machine (server)
Installed IBM Installation Manager
I am not getting how will I set up the Worklight Server on this machine. Can anyone provide some information?
You cannot directly deploy from Worklight Studio (the Eclipse plug-in) to a remote Worklight Server.
The steps you need to take are:
Setup your application for a remote server, via the Build Settings and Deploy Target window
Build the app
Take the .wlapp/.adapter file and deploy it to the remote Worklight Server via it's Worklight Console
If you have done any server-related changes (authenticationConfig.xml, Java code, ...) you will need to first deploy the project's .war file to the application server that hosts the remote Worklight Server, and then the .wlapp.
By reading this:
"The Mule ESB management console centralizes management for all your Mule Enterprise Edition deployments, both the standalone variety and those embedded in application servers." source
one can infer that MMC is not for Community ESB. Is that correct?
Your assumption is correct. In fact MMC communicate with the Mule ESB server through an agent that is available only for the enterprise version.