Why won't RTC install?
I'm trying to install RTC onto a Linux box just to evaluate it (Ubuntu 16.04). Things aren't working and I'm not sure what the cause is.
I downloaded the CLM-Web-Installer-Linux-6.0.2 file, but when I execute `launchpad.sh` it just spits out some warnings and errors and sits there. I can't tell if it's actually doing anything.
I'm also unclear on what prerequisite software needs to be installed. This requirements document (link) lists a bunch of software, such as IBM Installation Manager and various application servers, but I'm not sure why those are all listed as the installer should install those, shouldn't it? I mean, doesn't the installer install the IBM Installation Manager, a web server, a database, and an application server?
Could the problem merely be that I'm using Ubuntu instead of a supported OS like Redhat? I see that an older version of Ubuntu is listed as compatible, but does that mean that I need to use that version for things to work, or just that nothing newer is "supported"?
Here's an exerpt from the installation log.
jberman@JazzUbu:~/Downloads/CLM-Web-Installer-Linux-6.0.2$ sudo ./launchpad.shThanks! |
One answer
For the same CLM installer also on Ubuntu 16.04, with Firefox 48.0, I see the same problem with launchpad.sh. When the -chrome chrome: URL is left off the command-line firefox call, an instance of Firefox DOES open immediately. Therefore, something is screwy in that chrome://commonlaunchpad/content/commonlaunchpad.xul resource.
This is all a bit frustrating: I have turned to the UI installer because the command-line repotools setup script also has complications.
Perhaps the 6.0.3 Milestone releases have attended to restoring support of modern Linux systems to CLM? Many users are not likely to try to resurrect 32-bit Ubuntu 12.04. Forcing users to RedHat Linux is also not an appreciated policy for some of us.
Comments
Lonnie VanZandt
commented Sep 03 '16, 4:18 p.m.
Well, a chrome://*.xul URL is a reference to a Add-On extension in Mozilla-derivative browsers. Firefox as of version 43 blocks automated installation of unsigned extensions. IBM's commonlaunchpad xpi extension (found in the extensions directory of the new Profile being used by launchpad.sh) is unsigned.
Therefore, unless an older version of Firefox is used (perhaps that is why the process works on RH?) or the commonlaunchpad extension gets signed, Firefox will have to drop out of the supported browsers set.
To workaround this Oops!, downgrade Firefox with a version prior to 43, for example:
sudo dpkg -i ~/Downloads/firefox-mozilla-build_42.0-0ubuntu1_amd64.deb
I verified that this downgrade does allow firefox in new Profiles to auto-install the IBM extension and, most importantly, that the launchpad.sh script will run, will open the firefox browser, will install the commonlaunchpad, and one can run that launchpad app.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
The error suggests that the folder is not correctly copied, or the user cannot access that folder.
Well, yes... but why? Am I doing something wrong?
Sorry, no idea. It works fine on my Red Hat machine.