I have a bundle up and running in servicemix. I wanted to know if there is a way I could make some configuration changes and have it started automatically at say 7:30 in the morning.
I am new to servicemix.
thanks for your help.
Thanks.
No this is not possible to schedule bundles being started|stopped out of the box. But ServiceMix / Karaf is scriptable, so you can have some perl script (or any other) and have it trigger at 7:30 in the morning to execute a script that starts the bundle.
For example check out the karaf client example here: http://fusesource.com/docs/esb/4.4.1/esb_runtime/ESBRuntimeConnect.html
You can google a bit more about karaf client script.
Related
~We have some projects still running in AEM 6.1 SP2 (the move to newest version of AEM is in progress) and new projects in AEM 6.5.
AEM 6.1 runs in java 8 and AEM 6.5 runs in java 11.
For us developers this switching between jdk versions is difficult in our local environment, quite often we get our AEM instances corrupted or maven project imports are no longer working properly in IDE.
Anyone else had this situation? What are the best practices for such a situation?
My recommendation would be to set up vagrant box instances to your specs (AEM version + Java) and use automated deployments. This way, you can bring up a preconfigured instances in minutes by executing a single vagrant up command, run your automated deployment, and test your projects. If your instance gets corrupted, run a vagrant destroy command, bring up a new instance again with 0 configurations needed for the next deployment. You willincrease your productivity manifolds with this approach.
I have been using this approach for years and it has saved hours of devops work during critical project timelines
If you are using MAC [OSX], you can try Jenv. It can help you to have a unique Java Environment to a specific directory. We did find it very useful.
https://github.com/jenv/jenv
Thanks!
If you are running your AEM instances via shell scripts E.g. ./crx-quickstart/bin/start you can always specify the JAVA_HOME variable to be used in this particular file.
E.g.
export JAVA_HOME="path to your JVM"
export PATH=$JAVA_HOME/bin:$PATH
I received a Scala project to be run locally.
I'm on Windows, I've installed MySql (needed by the project), Apache 2.4 configured and started on port 9000 as suggested on Play Framework website, installed sbt and scala.
Now.. I got lost.. I don't understand how am I supposed to publish/deploy the project locally?
Which directory is supposed to be the www Apache directory?
How am I supposed to tell sbt that I'm running Apache?
I cant find any hint around.
Any structured suggestion to help my nut crawling on a bit?
Thank you!
Not sure if that would be helpful, but you've mentioned play framework. If your project is made with play, you should be able just to execute sbt run in your project directory, and then your application should be accessible via http://localhost:9000.
Details here: https://www.playframework.com/getting-started
I'm currently working on developing a custom workflow with many custom behaviors and scripts. I'm using the Alfresco Maven SDK to build and test my project as I develop it. This necessitates that I restart the repository-tier tomcat server every time I want to make a change/update my workflow files. I am getting quite frustrated with how long this takes each time, and it means that I'm wasting time while waiting for the server to restart, especially when I've made a small typo in one of my files.
I'm looking for a way (if it's possible) to update my files (in particular the bpmn process file) and apply these changes to my Alfresco instance without having to restart the tomcat servers each time. I've set to true in my service-context.xml, and I have also tried to redeploy the workflow from the admin-workflow-console, but my changes do not take place unless I manually restart the server.
I am using: Alfresco Community 5.2, Maven SDK 2.2
Any tips or suggestions would be very welcome!
Yes, you can do it by
workflow admin console
URL
http://<server>:<port>/alfresco/s/admin/admin-workflowconsole
Ex :: deploy alfresco/workflow/<workflow-definition>.xml
path for your workflow definition file.
Refer this docs for more information
https://community.alfresco.com/docs/DOC-5079-workflow-console
I am looking for a way to run Hudson jobs from an Electric Commander pipeline, I know it doesn't make much sense. We are migrating from a Hudson box to Electric Commander and cannot migrate all of the jobs immediately. I have read that ECTool can run Hudson jobs and get the info back within the same pipeline
http://www.electric-cloud.com/blog/2012/05/01/pushing-information-from-external-systems-into-electriccommander/
I can't find what exactly I need to do to kick it off though any tips?
Thanks
Additional Info
I have been studying http://docs.electric-cloud.com/commander_doc/4_2/Help_4_2_3/usingapi.htm and also playing around in the EC command line, I think I need to make a bash file to call the Hudson jobs but I am not sure where to start
The Jenkins plugin at http://plugins.electric-cloud.com/ will work for Hudson as well, I didn't know that
Question from a first-time Jenkins user. So I hope you wouldn't mind if the question is too silly.
I have installed jenkins on a Ubuntu machine, and is accessible at localhost:8080. I have successfully configured it to work with Maven2 and Git as well. Next, I created a job/project (A Java/Spring application), and got it to build without error on Jenkins as well.
Now my question is, where do I see this application running? :)
Best Regards
James
To deploy : http://mojo.codehaus.org/tomcat-maven-plugin/plugin-info.html to do it with maven or https://wiki.jenkins-ci.org/display/JENKINS/Deploy+Plugin to do it with jenkins
You can see the console output in the running job if you click the running job and look for the link on the left hand side.
Building and deploying are two different things. Jenkins can do the latter for you too but you need to have it configured in your maven project. Typically this is accomplished (for tomcat) using the tomcat maven plugin