To start iSM in a command window:

1. Open a Command Prompt window and navigate to the iSM home \bin directory. For example:

   C:\Program Files\iWay61\bin

2. At the command prompt, type:

   iwsrv

   By default, the iSM base configuration is started.

   Note: To start other iSM configurations, type the iSM configuration name after the iwsrv command. For example:

   iwsrv TestConfig

   iSM configuration names are case-sensitive.

3. Press Enter.

   Messages are displayed in the command window detailing the iSM startup process. The following prompt is displayed when the iSM startup process is completed:

   Enter command:>

   If you receive the following error message, then iSM is probably already running as a Windows service:

   ERROR (HTTP1) Unable to create server socket 9980:
   java.net.BindException: Address already in use: JVM_Bind
   ERROR (SOAP1) Unable to create server socket 9000:
   java.net.BindException: Address already in use: JVM_Bind

   You cannot run the same iSM configuration at the same time as an iSM Windows service and in the command window.

To stop iSM in a command window:

1. Go to the iSM command prompt:

   Enter command:>

2. Type the following:

   stop

3. When any listeners that are running have stopped, type the following:

   quit

   Note: If you close the command window without typing these commands, iSM stops. However, typing the commands is the recommended procedure.

To install an iSM Windows service:

1. Open a Command Prompt window and navigate to the iSM home \bin directory. For example:

   C:\Program Files\iWay61\bin

2. At the command prompt, type

   iwsrv config_name -s install

   where:

   config_name

   Is the name of the iSM configuration for which you are creating a Windows service.

   To create a Windows service with Java running in a separate process, type

   iwsrv config_name -s install -l java

   where:

   config_name

   Is the name of the iSM configuration for which you are creating a Windows service.

   A message is displayed, indicating that the iSM Windows service was installed successfully.

   You must now start the iSM configuration as a Windows service. For more information, see How to Start an iSM Configuration as a Windows Service.

To delete an iSM Windows service that you created to start an iSM configuration:

1. Open a Command Prompt window and navigate to the iSM home \bin directory. For example:

   C:\Program Files\iWay61\bin

2. At the command prompt, type

   iwsrv config_name -s remove

   where:

   config_name

   Is the name of the iSM configuration for which you are deleting a Windows service.

   A message is displayed, indicating that the iSM Windows service was deleted successfully.

   You can now delete the iSM configuration from the iWay Service Manager Administration Console. For more information, see How to Remove a Configuration From the Console.

To start an iSM configuration as a Windows service:

1. From the Windows Start menu, select Control Panel.

   The Control Panel opens.

   

2. Double-click Administrative Tools.

   The Administrative Tools are displayed.

   

3. Double-click Services.

   The Windows Services are displayed.

4. Scroll down to display the iSM Windows service, as shown in the following image.

   

5. Right-click the service you created (for example, iWay Service Manager 6.1 - TestConfig) and select Start from the context menu.

   The service Status changes to Started. The default Startup Type is Automatic.

To query the install options:

1. Open a Command Prompt window and navigate to the iSM home \bin directory. For example:

   C:\Program Files\iWay61\bin

2. At the command prompt, type

   iwsrv config_name -s query

   where:

   config_name

   Is the name of the iSM configuration for which you are running a query.

3. Press Enter.

   Information showing the options that were used to install the iSM Windows service is displayed in the command window. For example:

   Copyright (C) iWay Software. 2001-2012 All Rights Reserved
   "iWay Service Manager 6.1 - base" is currently installed
     Installation date  : 11/23/2012
     Installed via         : iwsrv.exe base -s install -l java -h C:\iway61x23
     Installed by       : Administrator

Command files can make use of the iWay Functional Language during their execution. For example, consider a properties file that contains the following lines:

1. dostart=start
2. whattoday=chan3

Now consider the following command file:

1. // this is a test file
2. set debug on
3. _properties('c:/testprop','dostart',';') file1
4. _if(sreg('true')='true'),'start file1',';')
5. // last line of test file

The first line is a comment. Any line beginning with a // or a semicolon is a comment. The second line enables debug tracing. The next line is an IFL statement, testing the dostart property in the testprop properties file. If the property is not found, the semicolon is returned and the line is ignored. If it is found, the value start is returned, and the line now reads:

start

The first line is a comment. Any line beginning with a // or a semicolon is a comment. The second line sets the debug trace to on. Line 3 is an IFL statement, testing the dostart property in the testprop properties file. If the property is not found, the semicolon is returned and the line is ignored. If it is found the value start is returned, and the line now reads:

start file1

This line starts the named channel.

Line 4 is another IFL statement. In this case, if the special register condition1 is set to true, then the start file1 command is executed.

So there are two methods for conditionally executing lines in the command file.

The command file also supports the special command goto <label>. A label is a named point in the file ahead of the goto command. A label ends with a colon and must exist on a line with no other commands.

1. // this is a test file with goto
2. goto point
3. _if (_properties('c:/props','whattoday')=='chan3','goto point3')
4. start chan1
5. start chan2
6. goto end
7. point3:
8. start chan3
9. end:
10. // last line of test file

In this command file, the IFL statement on line 3 instructs the server that if the whattoday property is set to chan3, then the commands pick up on line 7. Else, the commands on lines 4 through 6 will execute.