On-demand Deployment of Internal Applications

Home

Newsflash

Belgacom TV has said its customer base grew by 75,000 customers compared to 52,000 for the same period last year. “The number of net adds in the third quarter 2009 was positively influenced by the launch of “FAIR”, a company-wide programme to address cable competition,” according to the incumbent.

One of the reasons cited by the operator is the launch of the “Free TV” campaign, which refers to the monthly saving customers realize by signing up for this offer. The launch of new multi-play offer in July 2009 led to an all-time high sales figure for bundled offers (the so-called ‘Packs’) and Belgacom TV, adding respectively 70,000 and 75,000 customers in the third quarter 2009.

By end of September 2009, the total Belgacom TV customer base amounted to 663,000, including 88,000 second stream users. In one year time, Belgacom’s TV customer base grew by 220,000 customers. The continued customer growth is the main driver of the Belgacom TV revenue growth.

Compared to September 2008, the revenue grew by 51.2% to €94 million and now contributes for 5% to the total CBU revenue.

The television ARPU per household end of September 2009 was €20.10, or an increase of 1.8% compared to a year ago, driven by a lower impact of promotions. The third quarter ARPU of €20.6 significantly improved compared to the previous quarter as a result of increased sales of set-top boxes and slightly higher usage of on-demand services.

Main Menu

Forums

On-demand Deployment of Internal Applications

Written by Schelstraete Bart

Saturday, 01 August 2009 13:33

On-demand Deployment of Internal Applications

There are many internal applications that are deployed during startup. These internal applications consume memory and require CPU time during deployment. This contributes to the WLS startup time and base memory footprint. Since many of these internal applications are not needed by every user, WLS has been modified to wait and deploy these applications on the first access (on-demand) instead of always deploying them during server startup. This reduces startup time and memory footprint.

Internal Application Types

There are two different types of internal applications. The first type displays a user interface, and includes the Administration Console, UDDI explorer, and WLS test client. The second type does not display a user interface, and includes UDDI and internal servlets for deployment and management file distribution.

For applications with a user interface, WLS displays a status page indicating that on-demand deployment is in progress. This page refreshes every two seconds. When the internal application completes deployment, you are redirected to the internal application. This status page is displayed on the first access of each application. Subsequent invocations do not deploy the application and go directly to the user interface for the internal application.

Configuring On-Demand Deployment

For a development domain, the default is for WLS to deploy internal applications on demand. For a production-mode domain, the default is for WLS to deploy internal applications as part of server startup. You can control the default behavior by configuring the InternalAppsDeployOnDemandEnabled attribute in the Domain MBean. You can change the configuration setting using the Administration Console or by using the WebLogic Scripting Tool (WLST).

Configuring On-Demand Deployment Using the Administration Console

To change the InternalAppsDeployOnDemandEnabled attribute using the Administration Console, perform the following steps:

Start an edit session with the Lock and Edit button.
Select the domain to bring up the Configuration -> General tab.
Change the setting of the Enable on-demand deployment of internal applications check box.
Click Save and then click Activate Changes to activate the changes that will take effect at the next restart of WLS.

Configuring On-Demand Deployment Using WLST

To change the InternalAppsDeployOnDemandEnabled attribute using the WLST, perform the following steps:

  connect()
  edit()
  startEdit()
  cmo.setInternalAppsDeployOnDemandEnabled(false)
  activate()

Comments

Only registered users can write comments!

Newsflash

Main Menu

Forums

On-demand Deployment of Internal Applications

Internal Application Types

Configuring On-Demand Deployment

Configuring On-Demand Deployment Using the Administration Console

Configuring On-Demand Deployment Using WLST

!joomlacomment 4.0 Copyright (C) 2009 Compojoom.com . All rights reserved."

Login