VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
5 Replies Last post: Aug 20, 2009 8:13 PM by mvaughn25  

Lifecycle Manager: default webview for LCM does not contains content posted: Apr 18, 2008 10:50 PM

Click to view ThomasV's profile Enthusiast
ThomasV
37 posts since
Jan 18, 2007

After configuring the VMO platform by browsing to http://lcmserver:3944/ and after starting the service from that interface, I try to browse to http://lcmserver:8080/vmo/lifecycle as indicated in the installation manual provided from vmware, but all I get is a message saying that the Lifecycle Manager webview doesn't contains any default.hml or index.html files. It's a VMO tomcat page who states this, not a standard 404 page. If I browse to http://lcmserver:8080/ I actually get some links and I'm able to click through the lifecycle manager, but again no luck.

When connecting with the VMO client I can actually see that the LCM webview indeed doesn't contains any files to host.

Did I forget something very basic? Those packages provided by VMware for "existing customers" do I need them perhaps? Or is that just for upgrade/migrtion purposes from the Dunes platform.


Re: Lifecycle Manager: default webview for LCM does not contains content

1. Jan 13, 2009 11:13 AM in response to: ThomasV
Click to view uushaggy's profile Novice
uushaggy
21 posts since
May 2, 2006

Yes, I have seen this and for those who have been looking for this here's some info:

The link that is in the Orchestrator Configuraion Webview screen has an errant URL. It should be http://<LCM_SERVER>/:8080/vmo/weboperator

If you login into the Orchestrator Client and check the "Webviews" tab and look at the "General" tab. You will notice that both "lifecycle" and "weboperator" are under the same URL root of "weboperator" This is because both apps were placed in the same root.

Problem is still observed with 3.2.1. Maybe this can get fixed at some point?

Re: Lifecycle Manager: default webview for LCM does not contains content

2. Jan 14, 2009 7:13 AM in response to: uushaggy
Click to view Texiwill's profile Guru
Texiwill
10,213 posts since
Jan 13, 2004
Hello,

Moved to Lifecycle manager forum.


Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs: http://www.astroarch.com/wiki/index.php/Blog_Roll
Top Virtualization Security Links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

Re: Lifecycle Manager: default webview for LCM does not contains content

3. Jan 28, 2009 2:04 AM in response to: ThomasV
Click to view robjohnson's profile Enthusiast
robjohnson
14 posts since
Feb 11, 2008

Hi,

it sounds like your LCM plugin did not install properly - the package containing the webview should've loaded at first boot. It's possible to extract the package from the dar file you can find in the plugins directory and try to load it by hand. the dar file is just a zip (rename it and unzip it) you should find a *.package file inside containing the workflows and webview. go to the My VMO page in the java client and click 'load package' and browse to the .package file you extracted. let us know what happens with that.

Rob.


Re: Lifecycle Manager: default webview for LCM does not contains content

4. Mar 26, 2009 10:21 AM in response to: robjohnson
Click to view rlafleur's profile Lurker
rlafleur
1 posts since
Mar 26, 2009

I am currently having the same problem. In summary, after completing VMO install, I tried to open http://server:8080/vmo/lifecycle and the following is displayed:

No default page defined
The webview 'VMware Lifecycle Manager' has no default page defined. A default page is a page located at th root of the webview and named default.html or index.html.

Did the recommedation to import *.packaged fix the problem?

Re: Lifecycle Manager: default webview for LCM does not contains content

5. Aug 20, 2009 8:13 PM in response to: rlafleur
Click to view mvaughn25's profile Novice
mvaughn25
15 posts since
Aug 17, 2006

I did as you suggested and redeployed the "com.vmware.lcm.package" file and that resolved the problem for me. Be prepared to spend 10-15 minutes checking the MANY MANY boxes for each of the elements of the package to import. The java client is in dire need of a "check all" button;-)


Mark Vaughn
Enterprise Architect
vExpert 2009
http://communities.vmware.com/servlet/JiveServlet/download/1200101-20223/vExpert_logo_100x57.jpg

Actions

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities