When I run both app server and client on one machine, the database
connection is fine.
However, I now want to run OSEE for real in a small test project. To this
end, PostgreSQL and the app server were installed on a Windows 2008 Server
box.
When I ran the database initialisation from the client, the tables all
appeared to be created correctly but then an error appeared. I therefore
ran the database init locally on the 2008 Server box to see if the OS or
something in the way I had set up PostgreSQL on that machine was the
problem. The database initialised correctly and I could then run the
oseeLocal client and all seems to be well.
However, if I go back to running the client from another machine, it
connects to the app server but then comes up with an error 'Artifact with
name space "" and name "Root Artifact" is not available.'. This is
followed by 'The key "common" does not refer to any branch".
I've answered my own question here - the problem was that I was using the
same workspace on the remote client that I had previously used when the
app server and db were on that machine.
This leads on to a new question though - what data is put in the workspace
please? I see from the database description that artifact "binary" data is
put in there (or wherever else is specified) but what is classified as
"binary"?
I've answered my own question here - the problem was that I was using the
same workspace on the remote client that I had previously used when the
app server and db were on that machine.
This leads on to a new question though - what data is put in the workspace
please? I see from the database description that artifact "binary" data is
put in there (or wherever else is specified) but what is classified as
"binary"?