Assumptions:
1) Ability to work on Windows environment;
2)Posses a basic understanding of the iSM by now;
Now that, we have completed our first simple scenario successfully, some might have possibly ran into issues and errors. Some might also want to see what does iSM do in the background while how the engine processes the messages. To get an in-sight on this, we look at the two standard methods, a managed server in an iSM, can be started up. And they are:
1) Via Microsoft Windows Services
2) Via Command prompt
Starting up a service from Windows services panel is quite easy and self-explanatory. Select the service to start-up, right-click on it, choose start. If iWay Service Manager is installed and configured successfully, the managed server will start-up successfully.
Starting up a service from Command prompt uses the following command line argument to be executed from the bin directory of the iWay root directory:
iwsrv.exe base -d -l iWay61.cmd
Where iwsrv.exe is the core executable file that initiates the start-up process with the debug flag switched on [-d] and the JVM option explicitly set in a file called iWay61.cmd that will created by iSM automatically during the installation. iSM will locate the file although the location from where the command is executed is from bin directory.
This way, one can easily figure out how a message is processed by iSM.
Until next time with something interesting, bye for now. ;-)