WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

Chapter 7. Administration of WebSphere processes 305

4. Click New.

5. Enter values for the Host Name and Port fields and click OK.

One situation that requires creating a new virtual host is the need to secure communication

between an unmanaged HTTP server and the application server.This communication can be

secured so that it accessed only one specific application from all the applications hosted by

that server. To accomplish this, follow these general steps:

1. Add a new secure port to the HTTP server configuration (other than 443, which is the

default HTTP server secure port).

2. Generate and configure new certificates for the secure port of the HTTP server.

3. Add a new web container transport chain with a new secure port to the application server.

4. Generate and configure new certificates for the secure port of the application server.

5. Create a new virtual host.

6. Add the new port of the application server and the new port of the HTTP server to the new

virtual host.

7. Restart the application server.

8. Re-generate the plug-in for the application server.

9. Manually update the plug-in and configuration of the HTTP server, and map the

application on the new virtual host.

10.Update the HTTP server plug-in key stores with the certificate for the new secure port of

the application server.

11.Restart the HTTP server.

7.9 Managing applications

WebSphere Application Server V8.5 supports J2EE 1.3, J2EE 1.4, Java EE 5, and Java EE 6,

which we refer to as

enterprise applications. WebSphere Application Server V8.5 can run the

following types of applications:

 Java EE applications

 Portlet applications

 Session Initiation Protocol applications

 Business-level applications

 OSGi applications (New in Version 8)

OSGi applications are built on an architecture for developing and deploying modular

applications and libraries. OSGi applications are built using the OSGi API and deploying it

into an OSGi container. WebSphere Application Server provides an OSGi container as part of

its basic architecture. For more information about OSGi applications, see Chapter 26,

“Working with OSGi applications” on page 921.

For more information about the ways to install enterprise applications and modules, refer to

the following information center website:

http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/com.ibm.websphere.nd.multipla

tform.doc/ae/crun_app_install.html

Important: If you create, delete, or update virtual hosts, you need to regenerate the

web server plug-in.

306 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

7.9.1 Managing enterprise applications: Administrative console

To view and manage applications using the administrative console, click Applications 

Application Types  WebSphere enterprise Applications.

In the window, you see the list of installed applications and options for performing application

management tasks. Select one or more applications by selecting the box to the left of the

application name and then click an action to perform. The exception to this action is the Install

option, which installs a new application and requires no existing application to be selected, as

shown in Figure 7-55.

Figure 7-55 Working with enterprise applications

The following list describes the actions you can choose on this window after selecting an

application:

 Start: Applications normally start when the server to which they are mapped starts.

Exceptions to this situation include when the application is initially installed and when the

application is stopped manually. To start an application, the application server that

contains the application must be started. If not, the application displays in the

administrative console as unavailable and you cannot start it.

An application can also be started from the job manager console using the Start

application job type.

 Stop: You can stop an application manually without affecting the rest of the application

server processes. This situation is common when you update an application or want to

make it unavailable to users. You can also use the job manager console to stop an

application by using the Stop application job type.

Note: Starting an application server starts the applications that are mapped to that

server. The order in which the applications start depends on the startup order you

assigned to each of them. The application with the lowest startup order value is started

first. Applications that have the same order designation are started in no particular

order. Enabling the parallel start option for the application server means to start

applications with the same weight in parallel.

To view or change the application startup order, click Applications  Application

Types WebSphere enterprise applications. Open the configuration window for the

application by clicking the application name and then click Startup behavior.