Services Used by the LANSA Composer Windows Server
The LANSA Composer Windows server is a complete application execution environment supporting client/server as well as web applications. As such, it has a number of services that must be active on the server to provide the necessary application support.
When the installation is completed into a new LANSA system, the necessary services are started for you and are usually configured to be automatically started whenever the server system is restarted.
In addition to the services described below, the web server instance used by LANSA Composer must be started in order to use web components such as the .
The listener service
The LANSA listener provides communications services necessary to support both the client/server and web parts of LANSA Composer. The LANSA listener service must be active in order to start the LANSA Composer windows client or to open the LANSA Composer operations console in a web browser.
The LANSA listener service is usually identified with a service name beginning . If you have more than one LANSA product installed on your server, there may be more than one such service. In this case you can refer to the path specified in the service description to identify the listener service that is used by your LANSA Composer Windows server.
The Java Service Manager (JSM) service
The Java Service Manager service associated with the LANSA Composer installation must be started in order to use LANSA Integrator services with LANSA Composer. This is necessary for many of the activities shipped with LANSA Composer.
The Java Service Manager service is usually identified with a service name beginning . If you have more than one LANSA product installed on your server, there may be more than one such service. In this case you can refer to the path specified in the service description to identify the listener service that is used by your LANSA Composer Windows server.