How to keep mule CE 5.3.0 running - mule

I've created my mule application, and i deploy it on mule ce 5.3.0 my question now is how to keep my server running which means even if i close my CMD (the window where my mule is running) my application keep running.

See here: https://developer.mulesoft.com/docs/display/current/Starting+and+Stopping+Mule+ESB#StartingandStoppingMuleESB-StartingandStoppingMuleViatheCommandLine
Starting In the Background
Use the cd command to navigate to the $MULE_HOME/bin directory.
Run the startup script according to the options below.
Unix: ./mule start
Windows: mule.bat start

To further add on to what Ryan said, you can also install Mule as a service if you're running on Windows. From then you can also configure your Mule server to start up every time your machine boots up.
You can do so using the following command:
mule install

Related

Starting Mule 4.4.0 as a linux service

According to Mule documentation, the recommended way to install Mule as a service is to use the Java Service Wrapper by running:
$MULE_HOME/bin/mule install
After running the command, Mule just runs in the foreground. The same thing happens if I run:
$MULE_HOME/bin/mule remove
Using systemctl to start/stop
systemctl mule start
systemctl mule stop
returns the message "mule.service could not be found." Does this feature only work with the enterprise version? The documentation does not specify if this works with the community edition.
Here are links to the documentation I used:
https://help.mulesoft.com/s/article/Starting-mule-as-a-service-on-linux
https://docs.mulesoft.com/mule-runtime/4.3/starting-and-stopping-mule-esb#start-mule-as-a-linuxunix-daemon

RabbitMQ setUp Issue In windows

I am beginner to RabbitMQ. For the first time I am trying to configure RabbitMQ in my windows machine.I followed the steps given on official site www.rabbitmq.com/install-windows-manual.html.But the problem I am facing is when I run "services.msc" command, I am not able to see RABBITMQ_SERVICENAME .
What could be the issue?
Shivangi,
When you say "I am not able to see RABBITMQ_SERVICENAME", does it mean you don't see the RabbitMQ service in the list of services ?
What I usually do when RabbitMQ service fails to install correctly, I use the rabbitmq-service script located in the "sbin" installation folder and run the 2 following commands in a command prompt:
rabbitmq-service remove
rabbitmq-service install

IBM Mobilefirst CLI - Server start issue

I recently installed IBM MobileFirst CLI on my Mac, but I don't seem to be able to start the Server. See error below. I searched the internet and found that there is a bug in JDK which causes the JavaLaunchHelper error. I downloaded the beta version that supposedly fixes the issue from here - JDK Download Link
. But this doesn't help either. Any other help is appreciated.
Imayas-MBP:EmployeeDirectory imaya$ mfp start Initializing
MobileFirst Console. objc[18564]: Class JavaLaunchHelper is
implemented in both
/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/bin/java
and
/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/libinstrument.dylib.
One of the two will be used. Which one is undefined. Starting
server worklight. Server worklight start failed. Check server logs
for details.
/Users/imaya/.ibm/mobilefirst/6.3.0/server/wlp/bin/server: line 744:
18563 Abort trap: 6 "${JAVA_CMD}" "$#" > "${JAVA_CMD_LOG}"
2>&1 Error: The MobileFirst server failed to start. The port may be in
use by another instance of a running server, or the server may not
exist.
The JavaLaunchHelper error is not the problem here; Anyone using Java 7 will experience it, but things will work regardless.
The problem here is the second error:
The MobileFirst server failed to start. The port may be in use by
another instance of a running server, or the server may not exist.
Verify you do not have an already running server, that was started either by the CLI or by MFP Studio in an Eclipse installation.
In the command line, run mfp stop
In Eclipse, well, quit it
Make sure the Java process is not running
Then, start over. Using the CLI, create a new project and application and try to start the server. For example:
cd /Users/idanadar/Desktop
mfp create testProject
cd testProject
mfp add hybrid testApp
mfp start
mfp build
mfp deploy
mfp console
On OSX, you can locate and kill a process holding open a port using the following:
Run (assumes port 10080):
$ lsof -i :10080
Then if a process is shown, run the following using the shown Process ID:
$ kill -9 {PID}

IBM Worklight 6.2. Start eclipse test environment server from command line

If I'm not wrong with each new workspace a new "instance" of Liberty is configured in the folder "WorklightServerConfig" of the workspace.
Is it possible to start the worklight server from command line using those configuration files?
I have not been able to get the right "server start" command.
Thank you.
According to the documentation, you can use wl start to start the server and wl stop to stop it.
If you have installed Worklight Studio, you can also use the Liberty server command directly:
cd WL_STUDIO_INSTALL_DIR/plugins/com.worklight.studio.plugin_*/liberty/wlp/bin
Set the environment variable WLP_USER_DIR to the value defined in the file ../etc/server.env (it may be commented out).
Run the server command with arguments start worklight.
On Unix: env WLP_USER_DIR=ECLIPSE_WORKSPACE/WorklightServerConfig ./server start worklight
On Windows: set WLP_USER_DIR=ECLIPSE_WORKSPACE/WorklightServerConfig
server start worklight

Can't launch JBoss7 from Eclipse Indigo

I can't figure out where I am going wrong. I have Eclipse Indigo, JBoss 7.1, JBoss Tools installed. I have this configuration working on my Windows7 64-bit system. I am attempting to set up a co-worker's Windows XP 32-bit machine with the same configuration but am not able to get the server to launch. I have configured the server but when I attempt to start the server, I get an error indicating that it was unable to start the server but there is no specific error listed.
I am able to start JBoss from the command prompt using the standalone.bat file.
I am able to configure the standalone.xml file from within Eclipse. I have confirmed this by checking the file in the standalone/configuration directory.
When I attempt to publish the project from within Eclipse, it does not publish.
Nothing gets written to server.log
The startup parameters match what I have on my computer.
I can't figure out what I am missing. Any suggestions would be appreciated!
Edit:
I have done some more checking. I am able to publish to the server and I am able to start the server (with the published application) fine from the command prompt. That part works. When I attempt to start the server from within Eclipse it gives me "Server JBoss 7.1 Runtime Server failed to start." It never writes anything to the console tab in Eclipse either so I can't tell why it is failing to start.
Also in the Servers tab, there is an entry called "Server Details". When I expand that entry, it says "Not Connected".
The answer to my problem is that Eclipse had be configured to use the java JDK, not the JRE. As soon as I switched over to use the JDK it started working fine. For some reason JBoss will start under 64-bit windows with the JRE but under 32-bit you need to use the JDK. I found the answer here: https://community.jboss.org/thread/169097