How Were the Application and Web Servers Configured at Installation?

Task	Description
Virtual host(s) created	Lawson recommends that you define a virtual host in a separate httpd.conf file for each Environment you plan to install. Each Environment httpd.conf is referenced in a master httpd.conf file.
Web server name defined	A unique web server definition name was created for each Environment. Lawson recommends you include the Environment name in the web server name.
Document root directory defined	Lawson recommends that you use `lawenv1/webdocs`.
Ports defined	For a complete lists of ports defined during installation, see the installation guides for Landmark and for the Landmark applications you have. The listening port for web servers for this Environment. The virtual host listening ports for this Environment defined in each httpd.conf file. The WCInboundDefault and WCInboundDefaultSecure ports defined in the application server created for this Environment. These ports are listed in the Web Container Settings > Web container transport chains page in the application server configuration. The BOOTSTRAP_ADDRESS port for the application server.
Web server(s) federated in WebSphere	The web server(s) were added to WebSphere using the WebSphere administrative console.
Application server(s) defined and federated	Completed by the installation program, based on values supplied in the interview panels. These values are recorded in the `$LACFGDIR/install.cfg` file. System settings related to Landmark application server administration are maintained in the `$LACFGDIR/environment.properties` file. environment.properties
Lawson Environment and applications deployed	Completed with the `activatelandmark` command, after configuring system services and identities. Deploying the Landmark Environment
Modules mapped to servers	The Environment and applications modules were mapped to the appropriate servers. Deploying the Landmark Environment

Virtual host(s) created

Lawson recommends that you define a virtual host in a separate httpd.conf file for each Environment you plan to install. Each Environment httpd.conf is referenced in a master httpd.conf file.

Web server name defined

A unique web server definition name was created for each Environment. Lawson recommends you include the Environment name in the web server name.

Document root directory defined

Lawson recommends that you use


                lawenv1/webdocs

.

Ports defined

For a complete lists of ports defined during installation, see the installation guides for Landmark and for the Landmark applications you have.

The listening port for web servers for this Environment.
The virtual host listening ports for this Environment defined in each httpd.conf file.
The WCInboundDefault and WCInboundDefaultSecure ports defined in the application server created for this Environment. These ports are listed in the Web Container Settings > Web container transport chains page in the application server configuration.
The BOOTSTRAP_ADDRESS port for the application server.

Web server(s) federated in WebSphere

The web server(s) were added to WebSphere using the WebSphere administrative console.

Application server(s) defined and federated

Completed by the installation program, based on values supplied in the interview panels. These values are recorded in the $LACFGDIR/install.cfg file.

System settings related to Landmark application server administration are maintained in the $LACFGDIR/environment.properties file. environment.properties

Lawson Environment and applications deployed

Completed with the activatelandmark command, after configuring system services and identities. Deploying the Landmark Environment

Modules mapped to servers

The Environment and applications modules were mapped to the appropriate servers. Deploying the Landmark Environment