CMDBuild Forum

Using CMDBuild1.5 with shark

Old Versions
#1

CMDBuild 1.5 is bundled with a cmdbuild-shark.zip (1.5.4 has it as a cmdbuild-shark-webapp-1.5.4.war) which seems to contain only configuration and metadata files. I have edited these as per the Technical Manual pages 13-14, to match the data base names/paths etc, with the exception of two entries that do not exist in the Shark.conf file:-

CMDBuild.WS.ExtSync.EndPoint and CMDBuild.WS.ConfigPath

I have built Shark 4.4.1 and put the resulting sharkWebServices.war file in my tomcat7/webapps folder. This means I now have in webapps:-

cmdbuild/
cmdbuild-shark/
cmdbuild-shark.war
cmdbuild.war
ROOT/
sharkWebServices/
sharkWebServices.war

In the setup web page I have set the workflow server url to be http://localhost:8080/sharkWebServices.

I have tried this on two systems, neither of which seem to be working fully, and I am wondering if I have misunderstood the manual which is unclear in referring to "In the file of the shark webapp" (P13). Should this be the cmdbuild-shark version or the sharkWebServices version, or should I have merged the one into the other?

Also should I add in the missing config entries (CMDBuild.WS.ExtSync.EndPoint and CMDBuild.WS.ConfigPath)?



#2

Hi Tim,

 
cmdbuild-shark-webapp-1.5.4.war does not contain only configuration and metadata files, but all the webapp libraries are located in the WEB-INF/lib directory. The archive is a complete Shark 2.3 distribution enhanced with everything needed to work with CMDBuild. You should just deploy the provided war and configure the properties as documented in the manual, without any need for the official Shark war.
 
Shark 4.4 is not supported at the moment. It is going to be one of the main feature of the next 2.0 release of CMDBuild. We are writing the workflow support from scratch, so the development branch is not yet working properly (so don't try to use it).
 
Paolo
#3

Tecnoteca ha scritto:

Hi Tim,
 
cmdbuild-shark-webapp-1.5.4.war does not contain only configuration and metadata files, but all the webapp libraries are located in the WEB-INF/lib directory. The archive is a complete Shark 2.3 distribution enhanced with everything needed to work with CMDBuild. You should just deploy the provided war and configure the properties as documented in the manual, without any need for the official Shark war.
 
Shark 4.4 is not supported at the moment. It is going to be one of the main feature of the next 2.0 release of CMDBuild. We are writing the workflow support from scratch, so the development branch is not yet working properly (so don't try to use it).
 
Paolo
Thanks for that clarification. Could you just confirm the status of the missing configs ( CMDBuild.WS.ExtSync.EndPoint and CMDBuild.WS.ConfigPath)
#4

Tecnoteca ha scritto:

Hi Tim,
 
cmdbuild-shark-webapp-1.5.4.war does not contain only configuration and metadata files, but all the webapp libraries are located in the WEB-INF/lib directory. The archive is a complete Shark 2.3 distribution enhanced with everything needed to work with CMDBuild. You should just deploy the provided war and configure the properties as documented in the manual, without any need for the official Shark war.
 
Shark 4.4 is not supported at the moment. It is going to be one of the main feature of the next 2.0 release of CMDBuild. We are writing the workflow support from scratch, so the development branch is not yet working properly (so don't try to use it).
 
Paolo

I also note in Shark.conf there is:-

 

"CMDBuild.Groovy.Repository=${shark-webapp}/script

"

 

Which is not mentioned in the manual. Now I could change ${shark-webapp} to [.....]cmdbuild-shark/script in line with other changes, but there is no script directory in cmdbuild-shark...

 

#5

After unzipping the war file in the webapp directory of Tomcat, the configuration will be found in the conf/Shark.conf file.

 
Let's say that Tomcat is installed in /opt/tomcat (so the webapp directory is /opt/tomcat/webapp) and it is listening on the 8080 port on localhost with two deployed webapps:
This should be the relevant part of Shark's configuration file (/opt/tomcat/webapp/shark/conf/Shark.conf):
 
#=============================================================================
# SHARK webapp properties
#-----------------------------------------------------------------------------
DatabaseManager.ConfigurationDir=/opt/tomcat/webapp/shark/conf/dods

#=============================================================================


SHARK CMDBuild properties


#-----------------------------------------------------------------------------

CMDBuild.Groovy.Repository=/opt/tomcat/webapp/shark/script

CMDBuild.WS.EndPoint=http://localhost:8080/cmdbuild/services/soap/Private

CMDBuild.EndPoint=http://localhost:8080/cmdbuild/shark/

CMDBuild.WS.MaxConn=100
 
The "Server URL" setting in CMDBuild's configuration should be http://localhost:8080/shark
 
CMDBuild.Groovy.Repository is optional and it is only used if you use the Groovy Tool Agent taking the input script from file.
 
Paolo
#6

Tecnoteca ha scritto:

After unzipping the war file in the webapp directory of Tomcat, the configuration will be found in the conf/Shark.conf file.
 
Let's say that Tomcat is installed in /opt/tomcat (so the webapp directory is /opt/tomcat/webapp) and it is listening on the 8080 port on localhost with two deployed webapps:
This should be the relevant part of Shark's configuration file (/opt/tomcat/webapp/shark/conf/Shark.conf):
 
#=============================================================================
# SHARK webapp properties
#-----------------------------------------------------------------------------
DatabaseManager.ConfigurationDir=/opt/tomcat/webapp/shark/conf/dods

#=============================================================================


SHARK CMDBuild properties


#-----------------------------------------------------------------------------

CMDBuild.Groovy.Repository=/opt/tomcat/webapp/shark/script

CMDBuild.WS.EndPoint=http://localhost:8080/cmdbuild/services/soap/Private

CMDBuild.EndPoint=http://localhost:8080/cmdbuild/shark/

CMDBuild.WS.MaxConn=100
 
The "Server URL" setting in CMDBuild's configuration should be http://localhost:8080/shark
 
CMDBuild.Groovy.Repository is optional and it is only used if you use the Groovy Tool Agent taking the input script from file.
 
Paolo

Thanks, thats clearer, although I had to rename "cmdbuild-shark-webapp-1.5.4.war" to "shark.war" for the URL to work correctly....

Although still unclear about the references to "CMDBuild.WS.ExtSync.EndPoint" and "CMDBuild.WS.ConfigPath" on page 13 of the technical manual...