I am trying to install and understand ODE.
I set up Tomcat7 no problem
I set up ODE WAR distribution
I copied the examples folder as per instructions.
Then I ran it, and it failed.
Then I RTM some more and saw
The sendsoap executable can be found in the distribution bin directory. The urls should be updated according to the address defined in the WSDL file for the process service.
The executable script using the command line given fires an exception.
could not find or load main class org.apache.ode.tools.sendsoap.cline.HttpSoapSender
latest version.
If there is some update to URLs required there are no directions to do that anywhere in the install instructions. Given that new users do installs this has to be one of the most brain dead careless instruction sets I have read in years regardless of the fix. But can someone enlighten me?
Just to be clear, the startup screen on port 8080 comes up just fine.
The command line tools seem to have some class path issues. I'd suggest to use SoapUI instead, it provides a better UX as well.
Update: Quickstart to verify the installation:
For a simple test, just copy the helloworld2 example from the dist package to tomcat/webapps/ode/processes. The process should then appear in the web console. Copy the Axis2 WSDL URL of the helloworld process http://localhost:8080/ode/deployment/services/, which is most likely
http://localhost:8080/ode/processes/helloWorld?wsdl. Open SoapUI, start a new SOAP project, paste the WSDL URL into the "Initial WSDL" form and create the project. SoapUI will create sample request "Request 1" for the hello operation. Double click, play with the content and invoke the method using the green "play" button.
Due to a build problem the JAR files in the lib directory of the 1.3.6 WAR/JBI distributions don't work (Bug Report). Use the 1.3.5 distribution instead until this is fixed.
Related
A little backstory:
I am creating my first Go web app for school. The professor said that I could use Go. I asked him if I could use the latest version, 1.13, rather than the version installed on the server, 1.10, to leverage the module management feature and the updated errors module. He did not say that I was restricted to 1.10 and even gave me the contact information of the server admin. I reached out to the server admin with my professor CC'd and he said he doesn't want to update the server's version of Go in the middle of the semester. He then included instructions on how to download, install, and use whatever version of Go that I need in my home directory.
Pick your version:
https://golang.org/dl/
Set it up for your own use:
https://golang.org/doc/install
I installed go 1.13 and updated my own envvars to reflect this version and everything works.
Well, the other requirement is that I have to hand my professor my project and that it has to compile on the server. I am thinking that if I hand him a bundle and give him directions on how to build it, then I've technically met the requirements of the project so far.
My question is, does Go have anything that takes my Go v1.13 environment and packages everything up so that the project can compile on the target server? I have only been able to find solutions along the lines of "just copy the project binary to your production server" but that doesn't help me. I need it to compile on the production server. Besides, I tried copying my binary to the production server and it couldn't find my html templates (stored in ./ui/html/ directory) but I guess that will be solved in this discussion or saved for another SO question later.
student#universityserver:~$ ./web
INFO 2019/09/22 10:21:52 Starting server on :5089
INFO 2019/09/22 10:23:03 <ipaddress>:63527 - HTTP/1.1 GET /
ERROR 2019/09/22 10:23:03 handlers.go:29: open ./ui/html/home.page.tmpl: no such file or directory
The only thing I can think of right now is to basically add everything they need (the go amd64 binary distribution and all modules) and write a script that handles it all (extract go in local folder, export envvars, build, etc.)
Dear, Professor.
Copy this tarball to your home directory, extract, run build_my_goapp.sh script.
Sincerely,
Your student
The answer in my case was that I can supply a Makefile that does anything I need it to do.
(It's actually good practice, if not an expectation, of a project that is turned in.)
The requirements were that my project needs to compile on the server and that I had to supply a Makefile. Therefore, any downloading, installing, and setting up of a Go environment for my project can be done, as long as everything happens in the user's environment and is not something that needs sudo to install correctly. The server does not have Docker.
I am fairly new to TeamCity and have recently been tasked with creating various builds, which I have done with no real issues.
What I am trying to do now though is include an external text file into the build output.
The external text file will be received from a service call made during the build.
These are my intended build steps:
Check out solution.
Restore packages.
Run tests.
Call web service with a configurable parameter and receive text file back.
Include text file in build.
Deploy.
Steps 1,2,3 and 6 are covered.
What are my options here? I must confess I do not really know where to begin.
I've spent some time today googling but it has been tricky getting the correct search term to return information on what I am trying to achieve.
I've seen some confusing articles on a 'meta runner'.
Any pointers to get me started in the right direction would be much appreciated.
Thanks.
Use a TeamCity command line build step - https://confluence.jetbrains.com/display/TCD9/Command+Line
I assume you are using build steps for all the other steps you listed so this is simply another of those.
The command line process would run somewhere under your checkout folder and thus anything it downloads would be made available as an artifact for your build
Hi sorry about this issue, i'm run out of ideas of how to access my deployed project on our main domain server.
By following the Guidelines provided in the GitHub I installed properly the keter, put the .keter file in the /opt/keter/incoming path but once i access it on the browser it always see the nginx page.
Also I use fpcomplete IDE for my project and I just download the file executable file there.
Thank in advance
I've solve this by following the instruction given to me on Github
I have to use d3 graph at my web page. I never worked with d3. That's why, I'm facing some problem using it. Basically, I've to work at dropbox folder. So, my clients can see the worked file locally at their browser. Consider, I put a d3 chart at file.html file and my folder structure is like this
D:\Projects\Dropbox (Company)\MyName\FolderName\file.html
But, I saw that to run and see/show d3 examples I need run web server or run a python server. So, I've downloaded Python 3.4.1 and installed by double click. It's installed at this directory: C:\Python34
After that, I tried to follow d3's documentation for installing python server. So, I opened my cmd and type:
python -m http.server 8888 &
But, it gives me this error:
So, my question is:
How can I install python web server?
After installing that web server, is it possible see the d3 chart via this link: file:///D:/Projects/Dropbox (Company)/MyName/FolderName/file.html or I've put my files inside htdocs and run via http://localhost/folderName/file.html (I don't want to put files inside htdocs. It'll be tough for my clients see the output of the files directly from their pc)?
If it can't be seen without putting inside htdocs folder, I may find solution for running d3.js locally without installing any additional software/server(though I've found this type of solution for some d3.js chart but not for all). Thanks in advance and please don't mind if it's a lame question. Basically, it's my first day working with d3.js and I'm only ameture level skilled with javascript and jQuery.
OK, browsers are designed with security in mind, by default they don't let scripts go and grab a file from anywhere for very good reasons. They allow you to grab a file from the server or through requests. So to share your work with your client you will either need to use a hosting service - I would recommend bl.ocks, design your visualisation so it doesn't require any external data or provide instructions on how to disable browser security. You can read more about this here, here and here.
On python, in many cases python is already installed on people machines, so running a server from python shouldn't be an issue. All you have to do (on a windows machine) is launch your command prompt navigate to your directory and start your python server. Then open a browser and navigate to the localhost. Please note that python needs to be set as an environmental variable (i.e. your system path), the python documentation might help you here.
I'm trying to install/configure FishEye as per the instructions on Atlassian's website, but either the web server for the install doesn't start properly (and I see multiple exception message in the command window), or I get a 503 Response code when I try to access the installation link.
How can I get past this?
The installation instructions currently aren't clear, especially on a Windows environment.
Here's what you need to do (in my case on a Windows system).
Extract the fisheye archive to the directory where you're intending to run Fisheye from. (on my system, I made this <drive>:\Atlassian\FishEye).
Create a directory for your data. (I made this <drive>:\Application Data\FishEye)
Create an environment variable (Window System Variable) named 'FISHEYE_INST' and set it to the path you created in Step 2. ('INST' in this case means instance and not installation folder.
Copy the 'config.xml' file from <extracted_archive> to your FISHEYE_INST folder.
Open a command prompt and run the <extracted archive>\bin\run.bat file. (ie :\Atlassian\FishEye\bin\run.bat).
The online documentation is a little misleading at this point. They indicate that you run 'start.bat', which won't work (or at least, it wouldn't work for me...)
Open a browser and point it to 'http://localhost:8060'.
Following the steps above let me get FishEye up and running without any further issues.