You can create representations of unmanaged Web applications
so that the on demand router (ODR) can route requests to applications
that are installed outside of the product environment to assisted
life cycle middleware servers.
Before you begin
- Create and configure your middleware servers and dynamic clusters.
Read about middleware servers and dynamic clusters for more information.
- Deploy the application to your assisted life cycle middleware
servers, using the steps that are specified for the software that
your middleware server runs. Be sure that you know or have access
to the deployment information for the application, including the module
name, context root, virtual host name, and the server or cluster names
on which you want to deploy the application.
About this task
To route HTTP requests to applications that are deployed
on other middleware servers and classify these requests to service
policies, the runtime environment needs information about the application.
By creating an unmanaged Web application, you create a representation
of the application that is installed on the middleware server that
includes this information. Intelligent Management does
not manage the life cycle of the application in any way, but can route
requests to the application. The status of unmanaged Web applications
is directly linked to the status of the server to which the unmanaged
Web applications are deployed. The ODR can only route HTTP requests
to these applications.
An unmanaged application for WebSphere® Application
Server Community Edition is a representation
of an application that has been installed in the WebSphere Application
Server Community Edition Version 1 console, specifically.
With middleware discovery, an unmanaged WebSphere Application
Server Community Edition application can also
be a representation of a discovered application. Middleware discovery
locates existing installations of WebSphere Application
Server Community Edition servers and their installed
applications, and creates the corresponding configuration to include
servers and applications in the Intelligent Management cell.
Procedure
- Navigate to the unmanaged Web application installation
wizard.
In the administrative console, click .
- Enter the general properties for the application.
Specify
a name for the application that is unique among all of the applications
in the cell, and edition information about the application.
About
application editions for unmanaged Web applications: Because the
application is unmanaged, you cannot perform edition control commands
such as rolling out or validating new editions. However, if you install
another edition on the externally created servers, then you can create
a new edition of the application in the administrative console by
creating a new representation of the unmanaged Web application with
a different edition name. You can then specify routing policies to
control how to route the requests to the multiple editions.
- Define the deployment properties of the application.
Specify module, context root, and virtual host information for
the application. Choose the servers and clusters on which the application
is deployed by selecting deployment targets. You can filter the list
of deployment targets by only clusters, only servers, or by entering
a name. Click Add or Remove to
specify which servers and clusters run the application. Click Apply to
add the module and deployment targets to the module list.
The
dynamic cluster to which you deploy an unmanaged Web application must
be homogenous, which means the same application must be deployed to
all the members of the dynamic cluster, and all members must be running
the same middleware software, including the same version. When you
add a cluster member that does not contain the same application as
the cluster, the status of the application becomes partially deployed.
The application is not automatically deployed to the newly added cluster
member.
- Confirm the new unmanaged Web application representation,
and save the changes.
- Start the application.
With middleware applications,
applications display as started in the administrative console when
the middleware server on which the application runs is started. Read
about configuring middleware server operations for more information
about starting middleware servers from the administrative console.
Attention: If the server or node agent stops, the application
might still show as started or partially deployed in the administrative
console.
What to do next
Define service policies and routing policies for the application.