I am able to check all the features using features:list
I wanted to install certain features in JBOSS Fuse, but the command
features:install camel-blueprint
is not working
I am getting error
Error executing command: The container is managed by fabric, please use fabric:profile-edit --featur
es camel-blueprint/0.0.0 target-profile instead. See fabric:profile-edit --help for more information.
How can install the required features in JBOSS FUSE.
in JBOSSFUSE_HONE/etc/org.apache.karaf.features.cfg file I have entry called featuresBoot and added all the needed features to be loaded in startup
But, the status for all the features are uninstalled.
JBoss Fuse uses profiles (fabric) to define what to install on container, so you edit profiles, and then assign profile(s) to containers.
Frankly its easier to watch a few videos to get more familiar
http://vimeo.com/album/2635012
For example the loan broker video is a good start.
If you do not want to use fabric, then you can install like old-school with manually commands like you do on Apache Karaf. But this requires you NOT to install fabric in JBoss Fuse.
Also there is the Red Hat JBoss Fuse documentation you can dive into (links to documentation from here)
http://www.jboss.org/products/fuse
You can also find more details at the fabric8 project (community project of JBoss Fuse) documentation at:
http://fabric8.io/#/site/book/doc/index.md?chapter=profiles_md
The short answer here is that you have probably already set up this instance of JBoss Fuse / Fuse Fabric to be container managed, via fabric:create.
To "reset" your local installation (be careful! this deletes all containers and related configuration), run this command in cygwin to delete data, instances and lock:
cd /wherever/fabric8-karaf-1.0.0.redhat-412
$ rm -rf data instances lock
Now, when you restart Fuse, you should be able to install features directly.
I have copied the text below from the error messages. It should work.
"please use 'fabric:profile-edit --features camel-blueprint/0.0.0 target-profile'"
Related
I am trying to install Discovery on the same server as IIS which already has a DB2 instance. As the Discovery installation guide says, to install with an existing DB2 instance the repository database must be manually configured. It then goes on to say that this can be done using scripts which are found under the install directory. In other words, before I install I have to use something only available after installation.
Has anyone got a workaround - a link to somewhere I can get the scripts perhaps?
I managed to get it working by installing onto a clean VM and then copying the scripts from the installation folder and other files referenced in the scripts onto the IIS server and running from there. Had to search and replace the DB2 install directory within the scripts as they expect a default install of :\Program Files\IBM\SQLLIB whereas the IIS default install of DB2 is to \IBM\SQLLIB.
Thanks in advance. I am working on to upgrade JBOSS As7 to Wildfly 10. Manually I am able to do it. But I am looking for scripted solution that works without manual intervention as I need to upgrade 1000s of client. Please suggest some tools or scripts to do this.
Thanks,
Naga
I prefer to use CLI scripts to configure a server.
You are able to use variables and use the sript on different installations.
Also you are able to configure a new instance the same way as before.
If you use a newer version the CLI run check whether all is applicable.
I don't think that there is a general tool to migrate the config.
For minor versions you are able to copy the configuration folder, but you might loose new enhancements or features.
The apiman (http://www.apiman.io/latest/download.html) tell to use the (WildFly 8.1.0.Final) but the latest version of WildFly is 8.2
Can I install apiman on 8.2 version ?
Yes, that shouldn't be a problem. In fact, if you check out the latest apiman releases it uses WildFly 8.2 for its quickstarts and quick development setup (server-all).
If you want something that will allow you get apiman up and running quickly for playing, testing or developing with, then clone the apiman repo (https://github.com/apiman/apiman.git), and run:
cd apiman
mvn clean install -Pinstall-all-wildfly8
cd tools/server-all/target/wildfly-8.2.0.Final/
./bin/standalone.sh
After that fires up, open http://localhost:8080/apiman-manager and log in with u: admin p: admin123!
It's seeded with some basic data so you can dive right in: roles, users, an attached gateway, etc.
I'm looking for a way to integrate Docker containers with the Eclipse platform.
I would like to run all build/test/debug command inside containers and use same containers in Continuous Integration build and later in production.
The simplest way I looked on, was just to configure custom command but besides permissions problem (docker must run as sudo/root) it doesn't give me all the flexibility of real integration.
Any ideas on the best way to proceed?
it is not a full answer to your question but we (JBoss Tools team) started working on this and here are a few blogs about what is possible todo today and where we are with Eclipse docker tooling.
http://tools.jboss.org/blog/2015-03-02-getting-started-with-docker-and-wildfly.html
http://tools.jboss.org/blog/2015-03-03-docker-and-wildfly-2.html
http://tools.jboss.org/blog/2015-03-30-Eclipse_Docker_Tooling.html
To do that, i think you work on a Linux platform :-)
What i do for a classic java project :
Build a Docker image that contains a jdk and maven for example
In Eclipse, via "Run Configurations", create a "build in Docker" configuration that launch a command like this :
docker run --rm -v <eclipse_workspace_dir>:/usr/src/myapp -w /usr/src/myapp myrepo/myimage mvn clean install
it should work.
For your continuous integration, you can use Docker Jenkins plugin to do the same or with a sh script.
There is Docker Tooling for Eclipse, available from this update site (you also need to add this update site as for now).
Try Eclipse-Che
https://eclipse.org/che/
You can install it as a Docker runs.
These links were very useful to me :
https://github.com/docker/labs/blob/master/developer-tools/java-debugging/Eclipse-README.md
https://github.com/docker/labs/blob/master/developer-tools/java/chapters/ch07-eclipse.adoc
https://docs.docker.com/samples/
It is all about Tutorial: Debugging Java Applications in Docker, Install Docker Tooling in Eclipse
You can also Watch a quick video explaining the key steps in https://www.youtube.com/watch?v=XmhEZiS26os
To configure remote debugging in Eclipse, click on Run > Debug Configurations...
Tomcat for instance supports remote debugging the Java Platform Debugger Architecture (JPDA). Make sure that the remote debugging was enabled when the tomcat image (registration-webserver) was built.
virtual machines hold great promise as a way to distribute hard to configure applications. i have been using jeos vmbuilder (and some bash scripts) to generate my appliances, but i'm looking for something more elegant.
in my case, i'm looking for a solution that will build a linux-based vm with configured versions of tomcat and mysql as a base. each future release would be a new war file and a sql update script. it'd be really nice if already deployed vms could self-update and test builds could be pushed to ec2.
in my brief search, i've found rpath rbuilder, turnkey linux,
vagrant up, suse studio, jeos vmbuilder, and vmware studio. rather than try all of these, i figure i'd ask what this community uses to build and distribute appliances...
I use pungi myself.