Deploy the WAS CE sample virtual application pattern with
routing policy to learn about working with routing policies.
Before you begin
The IBM® Db2® with BLU Acceleration® Pattern is not installed to
the system by default. If you want to use the deploy database function in the WAS CE sample virtual application pattern with routing policy, you must
download the IBM Db2 with BLU Acceleration Pattern from IBM Passport Advantage® and import it to the system. After
you import the pattern to the system, accept the license agreement and enable it. If you attempt to
deploy the sample application and the IBM Db2 with BLU Acceleration Pattern pattern is not installed, the
deployment will fail. For more information about downloading and importing
pattern types, see the Related tasks.
Procedure
Start the ELB proxy shared service and
obtain its IP address
- Do one of the following actions:
- Click .
- Click .
- Select ELB Proxy Service.
- If there is an instance in the cloud, skip to step 8.
Otherwise, click Deploy.
- Complete the following information in the Configure
and deploy a shared service window:
- ELB instances range
- Specify the minimum and maximum number of ELBInstances.
- Enable autowiring
- Select this check box if you want all new virtual application pattern deployments
in the cloud group to
automatically use elastic load balancing (ELB).
If you clear this check box, you can manually enable ELB for specific
deployments.
- Virtual Host
- If you selected the Enable autowiring check
box, specify the default virtual host for virtual applications in
the cloud group.
- Scaling Properties
- In the list, specify options for scaling ELBInstances.
- To automatically scale instances, select CPU based.
To disable automatic scaling, select Disable automatic
scaling.
- If you selected an automatic scaling option, specify a threshold
range and minimum time to trigger automatic scaling. The default values
are 20% processor usage to scale in and 80% processor usage to scale
out. The default trigger time is 900 seconds.
- Click OK.
- Complete the following steps in the Deploy Virtual
Application window:
- Select the target cloud group.
- Select the IP version: IPv4 or IPv6.
- Select the cloud group from the menu.
- Click OK. Wait for the service to
deploy.
- Click .
- Click ELB Proxy Service - Shared.
- Obtain the Public IP for the shared service instance from
the Public IP column in the Virtual
Machine perspective section of the page.
Note: If
there are multiple ELB proxy shared service instances,
you can use the IP address for any of the available instances.
Deploy the WAS CE Sample with Routing Policy
- Click .
- In the list of pattern types, select WASCE Sample
Pattern.
- Select the WAS CE Web application with routing
policy.
- Click Open.
- Click the Routing policy that is
on canvas.
- Obtain the virtual host for the application, such as myhost,
from the Virtual host attribute.
Note: When
you apply a routing policy to your virtual application patterns,
you use this attribute to set the virtual host for the application.
- In the hosts file for the workstation
that you use to access the virtual application, map the IP address
for the ELB proxy shared service that
you obtained in Step 10 to the virtual host.
For example:
<IP that you obtained in Step 10> myhost
- Return to the console.
- Click Deploy in the toolbar.
The Deploy Virtual Application dialog box
displays.
- Select the IP type and target for
the deployment.
- Click OK.
The virtual application pattern is
deployed.
- Click to view
the deployed virtual application instance.
- Select the virtual application instance.
- In the details pane, find the virtual machine with the
name Web_Application-wasce.XXXX,
where XXXX is a set of digits. The Middleware
Status column has a link to display the endpoint of the application.
Use this endpoint to form the URL for the application. In this sample
application, the endpoint is
sample
, so the URL for
the application is http://<virtual host that you set in
Step 16>/sample
.
What to do next
To explore the sample virtual application pattern in
more detail, you can create a clone of it and then customize the clone
before you deploy it.