8.1 Task: Configure the Java Service Manager on Windows
After you have installed the LANSA Integrator, please check that the Default instances are suitable as described in 8.3 Task: Specify Default Server for JSM Client.
Before You Begin
Before you begin to configure the JSM Server on Windows, check the following requirements:
- Is the JSM Server software installed?
- Has your license been recorded or updated?
- Do you know the selected directory structure used by the LANSA Integrator install?
- Do you know the IP address of the JSM Server?
- Is JRE 1.4 or greater installed?
LANSA Integrator can be installed without a Java Runtime Environment (JRE) or a Java Development Kit (JDK) on the machine. However, it will not execute until the appropriate JRE has been installed.
Step 1. JSM Administrator and Log File
Check that the JSM Administrator has been installed. An entry should appear in Microsoft Service Control Manager. For more details about the JSM Administrator, refer to the LANSA Integrator Guide.
If the JSM Administrator service's Start-up Type is set to , Microsoft Service Control Manager will start the service automatically during system startup. If it is set to Manual, you need to use Microsoft Service Control Manager to start the JSM Administrator. JSM Administrator starts the Java Virtual Machine and launches the Java Service Manager. Install automatically starts the JSM Administrator, which performs an upgrade process. JSM Administrator will then terminate.
Log files will be produced in the JSM instance directory (…\Integrator\JSMInstance). The files are STDOUT.TXT & STDERR.TXT, which are also used for tracing.
Review the log files before using the JSM Server. These files may contain information regarding any updates required to property files.
If you attempt to start the JSM Administrator again, it should start successfully.
Step 2. JSMDirect
Check that JSMDirect is installed in a cgi-bin enabled directory under your Web Server.
If IIS is installed on the target PC, the install/upgrade software will automatically configure IIS to cgi-bin enable the JSMCGI folder, which is where JSMDirect.exe is installed.
If IIS is not installed, you will need to manually configure the Web Server.
Next, you must manually specify the Windows logon for executing the JSMDirect.exe CGI program. By default, IIS would use the default Windows logon IUSR_<machinename> to execute CGI programs. Normally, the default Windows logon does not have enough privileges to access the LANSA installation directory and will not be able to run LANSA applications properly.
To specify the Windows logon:
1. Start the Internet Services Manager.
2. Browse to the virtual directory and right-click on the file in the virtual directory and select menu item to open the dialog box.
3. Select the tab and then press the button in the frame titled to open the dialog box.
4. Check (select) the option and click on the button next to the label to open the dialog box.
5. Uncheck (i.e. deselect) the this is IMPORTANT if you specify a Windows logon username which is not located on the workstation - then specify the Windows logon username and password of the user profile used to run LANSA applications. The case of the password must match the case of the password as it was entered into . Note that if a workstation belongs to a Windows domain and a Windows User exists on both the Domain and the Local (on the workstation), the Domain User logon takes precedence.
6. Close all the opened dialogs by clicking on .
Note: Depending on your version of Windows, the corresponding administration programs may be different to those described above. In the event of a query, check the documentation for your Windows operating systems for more information.
Note that the specific Windows logon must have as a minimum read/write access rights to the LANSA installation directory in order to run LANSA applications properly. Check the corresponding documentations for more information.
The specific Windows logon is also required for obtaining log files from JSMDirect.exe. For more details refer to Log files (Windows) in the .
Ensure that x_lansa.pro contains an entry USER=(the LANSA user profile that JSM http requests will be given) or PSTC=Y. When a request is received by JSM to run a function, this is the LANSA user profile that the job will run under. Also provide the DBUS and PSWD parameters, unless database trusted connections are being used or the user id and password are contained in the ODBC DSN.
Step 3. JSMProxy
If you are using JSMProxy, check that JSMProxy is installed in a cgi-bin enabled directory under your Web Server.
If IIS is installed on the target PC, the install/upgrade will automatically configure IIS to cgi-bin enable the JSMCGI folder, which is where JSMProxy.exe is installed.
If IIS is not installed, the user will need to manually configure their Web Server.
As in Step 4. JSMDirect, you need to specify the Windows logon for executing the JSMProxy.exe CGI program.
Apply the same procedure as in Step 4. JSMDirect for the CGI program jsmproxy.exe in the virtual directory "cgi-bin ".
The specific Windows logon is also required for obtaining log files from JSMProxy.exe. See "Log files (Windows)" for more information.
Step 4. Locate Properties Files
If you have used the default installation directory, you will find the following directory structure installed on your server:
- <drive>:\Program Files\LANSA\Integrator\JSMInstance\…
Within the JSM_INSTANCE directory are several directories, which contain files used to configure the JSM server. You should be aware of the contents of the following directories:
- <drive>:\Program Files\LANSA\Integrator\JSMInstance\properties
- <drive>:\Program Files\LANSA\Integrator\JSMInstance\system
If you are using tracing, you will also need to locate the directory:
- <drive>:\Program Files\LANSA\Integrator\JSMInstance\trace