I can install the javaMail-1.5 feature fine using the following command "installUtility install javaMail-1.5" on my running liberty server and following the prompts.
However according to the liberty documentation I should be able to install it by adding the following to my server.xml config in the featureManager tag:
javaMail-1.5
This doesn't work and I see the following error in the server startup logs:
[11/30/16 1:22:43:342 UTC] 00000021 id= com.ibm.ws.kernel.feature.internal.FeatureManager E CWWKF0042E: A feature definition cannot be found for the javamail-1.5 feature. Try running the command, bin/installUtility install javamail-1.5, to install the feature. Alternatively, you can run the command, bin/installUtility install authentication, to install all features that are referenced by this configuration.
My server details are as below:
product = WebSphere Application Server 16.0.0.3 (wlp-1.0.14.cl160320160831-1555)
java.version = 1.8.0
java.runtime = Java(TM) SE Runtime Environment (pxa6480sr3fp20-20161019_02 (SR3 FP20))
Does anyone have any idea why this doesn't work?
If the feature hasn't been installed, you will need to use installUtility to install it as you mentioned.
The error is an indication that the feature -- think binaries -- is not on the system i.e. hasn't been installed.
Specifying it in your server.xml will configure the runtime to use it. But, it will not install the feature automatically for you. The server.xml is a server runtime configuration.
Now, what you can do is to try installUtility install <yourServer> or installUtility install <pathToServerXml>, which will have installUtility inspect your server or server.xml and install any features that aren't already installed on the system.
I think you may be confusing the documentation for the featureManager command which has been superseded by the installUtility command. Adding a feature to the featureManager element of your server.xml doesn't install the feature, it enables it. In order to enable a feature in server.xml, you must first install it using one of the methods described here.
Related
I am looking to play with apache-superset on a cloud-based ide. I have it on my local. I tried unsuccessfully to set it up on gitpod. I wanted suggestions on where can I set it up, opensource preferably not necessarily. I believe cloud9 is 1 such place, but I am looking for other options before I settle. If you've ever set it up on any such platform, even if it is on gitpod and can help me, kindly do so.
[Disclaimer: Gitpod staff]
You can indeed use Gitpod to work on apache-superset, and for that you'll just need a working configuration.
From what I can see in apache-superset's requirements, you'll need to get:
PostgreSQL (e.g. by using Gitpod's official gitpod/workspace-full-postgres Docker base image)
Redis (e.g. by installing it in a Dockerfile via sudo apt-get install)
Various Python dependencies (e.g. by running pip install . after cloning)
Various Node.js dependencies for the front-end (e.g. by running npm install)
Here is a basic configuration I wrote to achieve this:
https://github.com/jankeromnes/incubator-superset/commit/0d345a76ec8126fd1f8b9bc7b6ce4961bf3b593d
What it does is:
Create a Docker image with PostgreSQL and Redis
Once the repository is cloned, open 4 separate Terminals ("tasks"):
Redis server
Superset backend
Superset worker
Superset front-end
All dependencies will be installed automatically, and once the front-end is ready, it will automatically open in a web preview IDE side panel.
You can try it out by opening my personal fork of the apache-superset repository in Gitpod, e.g. by following this link:
https://gitpod.io/#https://github.com/jankeromnes/incubator-superset
h all ,
i am trying to uninstall sonarqube from the ubuntu machine using command "sudo apt-get remove --purge autoremove sonarqube-6.4.1" but I am getting error as no packages foun some one kindly help me with uninstalling soanrqube complaetly from ubuntu machine
Your purge isn't working because SonarQube likely wasn't installed via apt-get. So how was it installed? The docs offer clues:
Installing the Web Server tells you to download the SonarQube zip, expand it, and configure the properties file. So your first step would be to wipe out the SonarQube directory.
Of course, if SonarQube is running as a service on your machine, just deleting the diretory could lead to errors at the next startup, so you'll need to unwind that part too. For setting up a service, the docs advise you to:
create /etc/init.d/sonar
create a link in /usr/bin/sonar to the SonarQube start script
update your defaults
So you'll want to back those things out too.
Here is the original question: https://community.openproject.com/topics/7851
I'm trying to install Open Project 7 in a brand new Ubuntu instance at Digital Ocean.
I've follow the instructions at https://www.openproject.org/download-and-installation/, but it's not working.
After the complete of installation and the run of the openproject configure command, i have selected options to install both MySQL and Apache server. When it's all done, i'm unable to connect to my server.
My enviroment:
Ubuntu 16.04
http://159.203.191.172
At logs, i can see two strange messages.
First:
bundler: failed to load command: unicorn (/opt/openproject/vendor/bundle/ruby/2.4.0/bin/unicorn)
Second is a warning:
WARN -- : You are setting a key that conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at /opt/openproject/vendor/bundle/ruby/2.4.0/bundler/gems/omniauth-8385bc0da47e/lib/omniauth/auth_hash.rb:34. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-06-13T01:01:17.860764 #25822]
I don't know if the warning is related to problem, but i think that the unicorn problem is.
Answering my own question here:
I suspected that the package had some problems so i decided to install it using manual installation. The newest documentation i found was an old Ubuntu 14 step-to-step tutorial, adapted from older versions of Open Project. I decided to follow it and after a lot of adaptations i got able to finish the installation process.
This is the tutorial: https://github.com/opf/openproject-ce/blob/stable/7/docs/installation/manual/README.md
Now I'm writing another step-to-step tutorial based on it, modifying all required steps to perform a clean installation on Ubuntu 16.
I've followed this (https://github.com/IntersectAustralia/acdata/wiki/Setting-up-OpenLDAP) tutorial for set up LDAP server in my local machine.
I've done all these steps
Installed Homebrew
Installed openldap using brew command, including berkeley db
Updated the slapd.conf file
Started the server using command "sudo /usr/local/libexec/slapd"
Now how do i know the LDAP server is running?
I tried a lot but i could'nt succeed,later i deiced to go with ADS (http://directory.apache.org/studio/). Its easy to set up. Believe me i made the installation and configuration in 5 mins. Thank you apache.
Use -d3 suffix.
Run sudo /usr/libexec/slapd -d3, it will show you the details.
Can some guide me .. for installing Mule ESB(mule-standalone-3.3.1) in Ubuntu . I am unable to find any documentation for installing. i want to automate it through Chef.
It's can be as simple as downloading and unpacking the archive file from: http://dist.codehaus.org/mule/distributions/mule-standalone-3.3.1.zip
Note: You need jdk 6/7 installed first.
Here's a chef cookbook that does this: https://github.com/ryandcarter/mule-cookbook
And here's a Vagrant script for running the mule cookbook on ubuntu etc: https://github.com/ryandcarter/vagrant-mule
It is very simple.
Download and unpacking the archive file from: http://dist.codehaus.org/mule/distributions/mule-standalone-3.3.1.zip or whatever version you want to install.
put this unpack file to anywhere where you want like /opt/ or /usr/local/
put you mule application inside apps folder.
& go to bin directory and run ./mule start command. Now mule server is running. You can also check mule log inside log folder mule.log file
This is an old question, but in case there are others who are looking.
You want to install Mule as a Ubuntu Service, so that it restarts when The server restarts. There are a couple of basic steps to this
I detailed out instructions and installation files at my github repository
https://github.com/jamesontriplett/mule_linux_service_install
Steps in general:
Install a startup script in /etc/init.d
Install a startup parameter file in /etc/mule
Customize parameters in the wrapper.conf file in /conf/wrapper.conf
Install the license file onto the server if using enterprise
Add the startup script to the run levels.
To test, you want to reboot the linux service to make sure that it will come back after a reboot. If it doesn't you have a reliability issue.