There are a couple of utilities and executables present in MOCADIR\bin that are worth exploring for a JDA WMS Developer or Application Administrator. I’ve been writing about them like my guide on msql utility or how to install/Uninstall MOCA service and generating env.bat. There is also mocaserver.exe which provides a lot of functionality when it comes to tracing server-level issues.
The default methodology to start/stop a MOCA Server is through windows services (services.msc) on a Windows Server and using rp start or rp stop by logging in from the Unix user to the instance. However, there are times when you need to explore why MOCA Server is crashing or to debug abnormal activity, stability issues, for newer versions in JDA WMS the longer time it takes for an instance to come online and how to optimize its startup time or whatever the issue is that is specific to your use case.
Let’s see what parameters can be passed on to mocaserver by using mocaserver -h:
As you can see there are a lot of options. So let’s talk about a few.
Let’s say you’re debugging which task is causing issues, you can run the MOCA server without tasks by using MOCASERVER -T flag
Similarly, if you want to run with jobs, you can use the -J flag and if you want to only run the MOCA Server without both tasks and jobs you can do so by using MOCASERVER -JT
Let’s say you want to run troubleshoot an issue with MOCA Server, but unable to create any new connections and don’t want to disrupt existing users connected on let’s say a production system. You can use the -p flag to create a new MOCA server to open a new port with no tasks and jobs and connect to it. You can also use the classic port if you’re connecting from a legacy client/server.
To explain:
- -T flag inhibits tasks from starting
- -J flag inhibits jobs from starting
- -R flag inhibits RMI port from starting (Remote Method Invocation)
Server Started:
I am also able to connect via client:
If you have a related question or query, please feel free to drop a comment below.
